As this release fixes some bugs from previous stable version http://bugs.gentoo.org/show_bug.cgi?id=125348 http://bugs.gentoo.org/show_bug.cgi?id=132006 please test and mark stable
ppc stable
stable on ppc64
Stable on hppa, mips, sparc.
x86 done
not for me : http://bugs.gentoo.org/show_bug.cgi?id=125348
stable on amd64 not last and either least ;)
This Bug Report from Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375077 happened with me? I had a working installation with 239-r1, with 249 it failed with this problem. Had to downgrade to 239-r1 (everything worked fine with no conf changes).
Just like the last reporter, I also got bitten by Debian bug 375077 (both on x86 and amd64), so I had to downgrade to 239-r1. This is actually pretty serious, as it caused our systems to take half a day in order to boot up! Tracking down that ldap was the problem was far from trivial.
*** Bug 139868 has been marked as a duplicate of this bug. ***
pbienst: please test nss_ldap-253 instead for your boot problems. it will be going stable in two weeks if there are no issues.
*** Bug 149935 has been marked as a duplicate of this bug. ***
The update to 253 did not solve the issue. Only 239-r1 works fine. The Debian bug report contains lots of background info, BTW.
pbienst: the 253 change and the changes it introduces to /etc/ldap.conf resolve the insanely long timeout issues on EVERY machine that I've tested it on. I did get some initial reports of it not working, but it was user error because they didn't apply the changes to /etc/ldap.conf with etc-update. Also, make SURE you are using new enough baselayout (/etc/init.d/bootmisc has chown commented out) and udev (the tpm/tss entries are removed) where our folks have removed all other lookups that would go to ldap because the entries weren't in files. Yes, our solution path is different than debians, but that is because 'bind_policy soft' and changing ldap.conf/nsswitch.conf isn't a nice thing to do, and you won't find automatic config file changes in Gentoo init scripts last time I checked - we opted to fix the problem at it's source instead, rather than trying to avoid it. If there are still lookups going to LDAP during early, you need to fix them on your system - the latest baselayout makes certain they don't happen, but you should check your system esp if you have other stuff that may do said lookups.
Thanks, that helped. udev-087-r1 did not have tpm commented out in udev-rules, so I did that manually. Which udev version has this fix?
pbienst: >=udev-99 is where it's removed. i'm going to close this bug now, as the actual nss_ldap issues have been fixed for quite some while.