February 2014 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] libav and multimedia idea
by Tomáš Chvátal 14 May '14

14 May '14

Hello guys, I have created proof of concept libav library with disabled patented codecs in my home project [1]. This means that this library si up par with what we have in chromium and it should be legal to distribute. Apart from the library the repo contains vlc chromium and xbmc (built localy fails on obs, meh) which seems to run fine, just not to play almost anything ^_^. The possibility here is to include all the media players and stuff around it into openSUSE release, where one has to flip the switch in libav (see the spec file) and can build full-fledged-european-edition which can play our sweet movies. Let me know what you think about this plan and what would you use as base devel project for this. Cheers Tom [1] https://build.opensuse.org/project/show?project=home%3Ascarabeus_iv

8 11

[opensuse-factory] wow
by Peter Czanik 02 Apr '14

02 Apr '14

Hello, I just did a fresh installation of factory. Network manager in KDE displays an error, but networking seems to work fine. $SUBJECT is "wow" because I don't recall openSUSE booting ever so fast! What was changed? I did not check with a timer, but it seems to be faster now than other distros, while earlier openSUSE was among the slow starters. Not that it matters on a machine I turn on only once a day, but still :-) Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 25

[opensuse-factory] libwrap still broken over 2 years later...
by Linda Walsh 01 Apr '14

01 Apr '14

Just rebooted (it had been 60 days since last reboot), and it picked up the new tcpd/libwrap0 files from 13.1 (am pretty sure it's not fixed in factory, given it hasn't been fixed in over 2 years)... This is still a problem: http://lists.opensuse.org/opensuse/2011-10/msg00351.html Thought it was reported as I have a patch file... making sure it is reported here: https://bugzilla.novell.com/show_bug.cgi?id=861989 (had problems w/attachment, so am including it here as well..).

4 4

[opensuse-factory] Releases going forward
by Robert Schweikert 31 Mar '14

31 Mar '14

Hi, Releases going forward, or, how do we release without full time paid worker bees? With all the discussion toward the end of last year I suppose that today's e-mail "Timeline and roadmap V2" [1] finally shed light on the inevitable conclusion, the openSUSE team (@SUSE) will spend more time on other stuff and less time, if any, on turning the release crank. This is the team's prerogative just like everyone is free to work on the project, or not, in areas of interest to them. We can argue whether the way this is coming about is giving the project the best chance to succeed or whether the transition is being put worth in a nice and friendly way, but I think we should not go down that path. Thanks! to the openSUSE Team for the hard work they have put forth in the past to turning the release crank, it is much appreciated. I think the time has come to move forward and deal with the new situation. As of right now we still have a release cycle of 8 month. That would put us into May for openSUSE 13.2. This brings about two questions: - Given the current situation can we meet a May release date? - Do we skip the May release and move to a yearly cycle and release 13.2 in November of 2014? During last year's discussions there were a number of people favoring a yearly release cycle. We have to make a decision, - stick to 8 month or move to 12 month? Voice your opinion but stick to the point and please be concise. For simplicity lets just assume that there will be no full time paid help to turn the release crank and that the work is all on those that are not part of the openSUSE Team. Under any circumstances I'd say our first go around will be a bit rough around the edges and that's OK, we have to learn. What do I have to offer? After all stuff will not get done by me sending an e-mail into the world. I offer to take on part of the role of "Release Manager". I will not be able to do all of it and I have a new definition for the role (see below.) Stephan did way more and was always the tireless worker that brought everything together. No one that does not work on openSUSE full time can obviously fulfill that role, thus we have to split things up. I figure there are about 60 to 70 hours worth of work per week that we have to distribute. I'll define "Release Manager" as: The person or group that runs after people, keeps an eye on the schedule and tries to herd the cats to get the stuff fixed that is broken. I am willing to take part of that role, and with this mail hopefully be a rallying point to put openSUSE releases on a bit more of a solid footing than where we are today, after [1]. If we go this route it implies that everyone that has stuff in Factory, what will become the next release, nothing there changes, has more responsibility in helping out than they do today. We no longer have people that can fix everything and get to spend all their time on the distribution and integration of stuff. Every maintainer has more responsibility. So where do we go from here? Do we bootstrap an effort to get a release out the door without openSUSE @SUSE or do we drift along in the uncertainty of "maybe we know something in August"? I am happy to be a rallying point and fulfill part of the role of "Release Manager" as outlined above. Maintainers/Packagers be heard, speak up, but lets not drift into rat holes, the situation is actually quite simple. Later, Robert [1] http://lists.opensuse.org/opensuse-factory/2014-01/msg00350.html -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

30 62

[opensuse-factory] Virt-Manager 1.0
by Christian Grassi 22 Mar '14

22 Mar '14

Hi all, Is there any plan to have virt-manager 1.0 in Tumbleweed. Thanks Christian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 15

[opensuse-factory] New package apache2-mod_authn_otp
by Archie Cobbs 02 Mar '14

02 Mar '14

I'd like to add this package to factory. It's been in Apache:Modules and used in production for several years now. apache2-mod_authn_otp mod_authn_otp is an Apache web server module for two-factor authentication using one-time passwords (OTP) generated via the HOTP/OATH algorithm defined in RFC 4226. This creates a simple way to protect a web site with one-time passwords, using any RFC 4226-compliant hardware or software token device. mod_authn_otp supports both event and time based one-time passwords. It also supports "lingering" which allows the repeated re-use of a previously used one-time password up to a configurable maximum linger time. This allows one-time passwords to be used directly in HTTP authentication without forcing the user to enter a new one-time password for every page load. mod_authn_otp supports both basic and digest authentication, and will auto-synchronize with the user's token within a configurable maximum offset (auto-synchronization is not supported with digest authentication). mod_authn_otp is especially useful for setting up protected web sites that require more security than simple username/password authentication yet also don't require users to install special VPN software, and is compatible with software tokens that run on cell phones. Thanks, -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] bluetooth audio performance
by Alejandro Bonilla 02 Mar '14

02 Mar '14

Hi there, I got a few bluetooth speakers that behave very well but not when the source is my laptop. I'm inclined to think there is either a power management issue or a degradation? of the bluetooth signal after several minutes (10-15). for which I need to go into the Control Panel, disable Bluetooth, set it back on and off it goes well. While misbehaving, the audio is cutting off and is pretty behind to my play/pause actions. Is there some performance tuning that could be done to fix this? Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] I don't see much help with btusb vermagic: 3.11.10-7-desktop SMP preempt mod_unload modversions parm: ignore_dga:Ignore devices with id 08fd:0001 (bool) parm: ignore_csr:Ignore devices with id 0a12:0001 (bool) parm: ignore_sniffer:Ignore devices with id 0a12:0002 (bool) parm: disable_scofix:Disable fixup of wrong SCO buffer size (bool) parm: force_scofix:Force fixup of wrong SCO buffers size (bool) parm: reset:Send HCI reset command on initialization (bool) and bluetooth parm: disable_esco:Disable eSCO connection creation (bool) parm: disable_ertm:Disable enhanced retransmission mode (bool) parm: enable_hs:Enable High Speed support (bool) I wonder if anyone else is having a similar problem and if any of these were any good? Thanks, Alejandro -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] LXC in factory/Tumbleweed?
by Johannes Kastl 01 Mar '14

01 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, as LXC got quite a lot of attention in the last weeks, I thought I would give it a spin. But I do not find any recent lxc in tumbleweed, and factory still has beta1 (AFAICS). Before I try building it myself, are there any plans to upgrade/add a package for the latest stable release? Maybe I am missing a repo, if so please tell me to RTFM. ;-) Regards, Johannes - -- `You place too much importance, and you always have done, on the so-called purity of blood. You fail to recognise that it matters not what someone is born, but what they grow to be!´ (Albus Dumbledore, Harry Potter and the Goblet of Fire) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlMPks0ACgkQzi3gQ/xETbJ5/QCbBYOeFuI2zT83Fjvt7RLoQhi6 iVAAniw0EWtgPKFOZLdqo6LA0oXkKaJH =Jii+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] Fedora exploring using XFS as it's default filesystem
by Greg Freemyer 28 Feb '14

28 Feb '14

I don't know if anyone cares, but I was surprised to see: <http://oss.sgi.com/pipermail/xfs/2014-February/034582.html> It looks like early phase exploration on the one hand, but on the other hand Red Hat Beta 7 is already using XFS as the default filesystem: <http://www.internetnews.com/ent-news/red-hat-enterprise-linux-7-beta-uses-x…> Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 24

[opensuse-factory] Re: [opensuse-buildservice] CI rights management
by Jos Poortvliet 28 Feb '14

28 Feb '14

On Monday 24 February 2014 09:37:52 Sascha Peilicke wrote: > On Sunday 23 February 2014 16:06:26 Jos Poortvliet wrote: > > On Feb 19, 2014 5:32 PM, "Sascha Peilicke" <speilicke(a)suse.com> wrote: > > > Hi guys, > > > > > > since more and more openSUSE projects start to make use of our CI > > > infrastructure, we have to organize who's allowed to do what. In the > > > past > > > > we > > > > > just added more and more people with rights to organize everything. So > > > I > > > > tried > > > > > to reduce the global list of users with admin rights. Instead, we now > > > > have a > > > > > per-project (translates to Jenkins job) ACL matrix where each project > > > can > > > organize stuff themselves. In simple words, you now can configure per > > > job > > > who's allowed to change things. There should be no need to bug me again > > : > > :-) > > : > > > That said, the list of ci.o.o admins now is: > > > coolo, jdsn, bmwiedemann and saschpe (me). > > > > > > The following openSUSE projects currently use ci.opensuse.org: > > > - Open Build Service / osc > > > - OpenStack > > > - Yast / libyui > > > > > > The first two projects have per-job based access rules set already. If > > > you > > > have a ci.o.o job and want to grant somebody the right to modify it, > > > just > > > check "Enable project-based security" and add the (already registered) > > > > user in > > > > > question. > > > > > > And if you want to add your openSUSE-related project to our CI, please > > > > get in > > > > > touch with any of the guys mentioned above. That's it. > > > > I am guessing there is a wiki page where this is documented, perhaps it > > would be possible to link to that page from http://ci.openSUSE.org? > > I have to admin that ci.opensuse.org is slightly under-documented. However, > I'd like to avoid creating huge wiki pages that run out of sync. Instead, > the CI boys already agreed to add/extend Jenkins job descriptions and > similar things so that this is more obvious. I guess having a small wiki > page about "how to get your stuff tested" wouldn't hurt... Yeah, I'm not a big fan of huge wiki pages either... More than something like: --- If you have a ci.o.o job and want to grant somebody the right to modify it, just check "Enable project-based security" and add the (already registered) user in question. And if you want to add your openSUSE-related project to our CI, please get in touch on openSUSE=packaging (?). --- is probably not needed... Might even fit on the jenkins page.

1 0