[gentoo-dev] Re: openrc-0.5.1 arrived in the tree
Hi, Tomáš Chvátal : > Actualy i would like to hear what we in KDE did too, we publish into > the tree as 0 days bump mostly since 4.2 and 4.1 was in the tree > right away when we had working configuration. Your bumping is excellent, no discussion here. Gnome does a really good job in figuring out what packages need to go stable along with their newest release, maybe that is easier for them. With the ongoing KDE 4 stabilisation, I have seen a lot of stabilisation requests filed by Samuli, which should have been already there, filed by the KDE team. Figuring out what will be broken with such a major release and trying to get the stable tree on par is what eats a lot of time for us architecture developers...you can ease that by researching beforehand (with a stable chroot for example). V-Li -- Christian Faulhammer, Gentoo Lisp project http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode http://gentoo.faulhammer.org/> signature.asc Description: PGP signature
[gentoo-dev] Re: openrc-0.5.1 arrived in the tree
Matthias Schwarzott posted on Fri, 09 Oct 2009 19:57:07 +0200 as excerpted: > sys-apps/openrc-0.5.1 Just a heads-up for anyone reading this and thinking about upgrading, who hasn't yet. rc_start_wait is now in SECONDS, NOT the former MS, or at least it seems to be for some of us. So at the default /etc/rc.conf setting of 100 (which I had doubled to 200 here), it'll wait for 100 seconds on several scripts. That's longer than the 60-second wait others have built-in to wait for their dependencies, causing various problems. So until this gets fixed, you may wish to set rc_start_wait=1 in /etc/rc.conf, if you're trying the upgrade. http://bugs.gentoo.org/show_bug.cgi?id=288495 https://bugs.gentoo.org/show_bug.cgi?id=288495 (Also see 288494, which I filed not realizing the long timeout, thus believing it had hung. It'll be marked a dup of the above momentarily...) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
