January 2014 - openSUSE Factory - openSUSE Mailing Lists

[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] Btrfs under heavy write makes system sluggish-er than ext
by Claudio Freire 06 Feb '14

06 Feb '14

So, the subject says it all. I've been testing a huge database on 13.1 RC1, well actually factory, with a btrfs partition (not the system partition, just a dedicated partition), and under heavy write it chokes the system much more than ext4 does. It also seems to have lower thoughput on what should be mostly parallel sequential access (ie: multiple sequential threads), but I'll have to perform more accurate benchmarks to be sure. It may be an fsync issue. It's not a critical issue, of course, but I'm in a position to assist with tests, benchmarks and diagnostics... so... what do I need to do to provide useful info here? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 7

[opensuse-factory] Timeline and roadmap V2
by Michal Hrusecky 03 Feb '14

03 Feb '14

Hi all, As you know we had a week-long meeting in Nuremberg. Quite a few of the things we've been working on (openQA, OBS workflow etc) were shared by now. Besides discussing features, we scheduled our work. In the previous thread on $SUBJECT, Simon noted that going for a release in November seemed a far smarter compromise between the benefits of releasing and getting some improvements in our tool chain than skipping a release. Most of the team agreed on this right away and we'd like to go for that. However. This does not mean the initial idea of doing a more 'relaxed' release is off the table. Planning software development is hard, planning experimentation (like the staging projects we are toying with) is impossible so we can not predict when we will be done. This means that we still intend to take those of you who stepped forward to help out with the release up on their offer. The exact nature of what we release is still to be determined and we'd like to make a more final decision on how much effort we can and will put in in August. So far it is sure that we would need some volunteer to keep eye on Factory and release milestones at least till then. So, for now, this will be a 'community release'. This might mean less QA but also no security updates provided by SUSE! Especially if it comes to the latter case we should communicate this carefully to our users as it will be more like a slightly more stabilized milestone than a successor to openSUSE 13.1. How to call it, how to communicate and what exactly it will look like - August. When exactly we will be fully back to working on Factory, releasing milestones, and working on the release we will hopefully be able to determine in August as well. Thoughts? The openSUSE Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

26 43

[opensuse-factory] rc* symlinks and systemd
by Ludwig Nussel 03 Feb '14

03 Feb '14

Hi, openSUSE has a packing policy of requiring rc* symlinks for each init script. So for e.g. /etc/init.d/foo there must be a symlink /usb/sbin/rcfoo -> /etc/init.d/foo. There is an rpmlint check for this policy (suse-missing-rclink). Now that more and more packages correctly switch to systemd only and drop the init scripts the rpmlint check doesn't work anymore. So we are slowly losing a nice convenience feature of openSUSE. Techically the feature works also for systemd units by making the rc symlinks point to /usr/sbin/service. When in involked as e.g. "rcfoo start" this script would then run "systemctl start foo.service". Personally I'd like to see us keeping the rc* feature also in the future so I'd like to propose introducing an rpmlint check to complain about missing rc* symlinks also for systemd unit files. Any objections on that? Otherwise I'd extend the suse-missing-rclink rpmlint check to .service files at some point. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 21

[opensuse-factory] Factory currently does not boot in VirtualBox
by Wolfgang Rosenauer 31 Jan '14

31 Jan '14

Hi, I've updated a VM to Factory today and now it doesn't boot anymore in VirtualBox. The last thing I can see is "Loading initial ramdisk" and afterwards VirtualBox (4.3.6) switches into "Guru Meditation" and fails to boot further. Any ideas how to solve that? Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] Announce: 13.2 release in November
by Stephan Kulow 31 Jan '14

31 Jan '14

Hi, After reviewing the mailing list thread - and verifying with SUSE management that there is no other news, I guess I need to clarify some bits. To avoid any further uncertainties let's put this whole discussion to rest and name the beast: 13.2 will be released in November 2014. As 12.2 has shown, summer releases are *bad* - especially with conferences in spring, so I just don't want to go there and avoid the July release. This means: I will take the 13.1 release schedule and adapt it and start releasing milestones soon enough. IMO enough people volunteered to help and I sure hope they stick to their claim. As a reminder: http://s.kulow.org/131-issues shows what tasks the openSUSE team collected as TODO - so please be ready to say which of those tasks you volunteer for. 13.1 Milestone1 was in May - so openSUSE conference in April is the perfect time to bootstrap a release team. Naturally the release after 13.2 would be again in July - and the same argument applies then too, but let's talk about the future schedule once we have experience with the 12 months. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

Re: [opensuse-factory] Announce: 13.2 release in November
by Stephan Kulow 31 Jan '14

31 Jan '14

Richard asked me to bounce it while he's "mobile" ;) Greetings, Stephan -------- Original Message -------- Subject: Re: [opensuse-factory] Announce: 13.2 release in November Date: Fri, 31 Jan 2014 14:14:15 +0100 From: Richard Brown <RBrownCCB(a)opensuse.org> To: Stephan Kulow <coolo(a)suse.de> Coolo, Thank you a whole bunch for this clear, concise announcement I'm looking forward to a November release, and I think its an excellent idea to use oSC14 to bring together the new release volunteers. A note to everyone who is willing to join the Release Team, don't forget the TSP is there, available and willing to help sponsor you to get to oSC14 :) On 31 Jan 2014 13:33, "Stephan Kulow" <coolo(a)suse.de <mailto:coolo@suse.de>> wrote: Hi, After reviewing the mailing list thread - and verifying with SUSE management that there is no other news, I guess I need to clarify some bits. To avoid any further uncertainties let's put this whole discussion to rest and name the beast: 13.2 will be released in November 2014. As 12.2 has shown, summer releases are *bad* - especially with conferences in spring, so I just don't want to go there and avoid the July release. This means: I will take the 13.1 release schedule and adapt it and start releasing milestones soon enough. IMO enough people volunteered to help and I sure hope they stick to their claim. As a reminder: http://s.kulow.org/131-issues shows what tasks the openSUSE team collected as TODO - so please be ready to say which of those tasks you volunteer for. 13.1 Milestone1 was in May - so openSUSE conference in April is the perfect time to bootstrap a release team. Naturally the release after 13.2 would be again in July - and the same argument applies then too, but let's talk about the future schedule once we have experience with the 12 months. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org <mailto:opensuse-factory%2Bunsubscribe@opensuse.org> To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org <mailto:opensuse-factory%2Bowner@opensuse.org> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] wicked: How to override MAC address?
by Andreas Färber 31 Jan '14

31 Jan '14

Hi, On one of my ARM boards the MAC address gets initialized randomly on power-up. On Android that's band-aided by running a shell script with the netcfg equivalent of: ip link set enp1s0 down ip link set enp1s0 address 00:... ip link set enp1s0 up http://mydragonboard.org/2013/updating-ifc6410-software/ Older openSUSE posts advertised using LLADDR='00:...' in ifcfg-*, but for 13.1 that caused network.service (well, network(a)enp1s0.service) to timeout and in Factory wicked seems to simply ignore that option. Is that a bug? How to set the MAC address each boot before DHCP potentially sends out traffic from the wrong address? Should I write a custom .service with the above working commands and somehow intertwine that with network@.service? Or use ifup.d and somehow limit it to enp1s0? Any other place to easily set such an option? Thanks, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- 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] How to add a local mirror as a repositorie
by Luiz Alberto Saba 31 Jan '14

31 Jan '14

Hi guys Sorry if my question is dumb, but I'm a new user... I have a local mirror (rsynced with opensuse.c3sl.ufpr.br) and I'm trying (without success) to configure it as my main repositorie. If someone could give the "stones path"... Thanks Luiz Alberto Saba -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] NOTE: auto-cleanup of ~:branches: projects is active now!
by Adrian Schröter 30 Jan '14

30 Jan '14

To reduce the build load of our build.opensuse.org instance we did activate the new auto-cleanup mechanism of OBS now. This means, by default all default branch projects (home:<ACCOUNT>:branches:...) get an attribute to self-destruct after a given time (currently 60 days). No panic, this is less grave as you may think now, because: * The deletion will happen via a request. If you decline that one the project will stay. * Delete requests will not created if there are still running requests involving this project. * there is the "osc undelete" command to bring the project sources back * You can Opt-Out by removing the OBS:AutoCleanup attribute This will free hopefully lots of build power and make us more responsive again :) thank you adrian -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4