Greetings, 

First a spot of background information:
I've been hammering my head against the LDAP server running on dev.g.o
and cvs.g.o for more than a week now. Several users will attest to the
strange bugs that have been seen (eg two near identical sets of user
information, one user can login, the other can't!). It's OpenLDAP
2.0.27-r4. The latest offical stable OpenLDAP is 2.1.22 and the current
testing is 2.2.0alpha. 2.0 is not even supported upstream anymore for
new deployments and everybody else is encouraged to upgrade. But wait a
minute you say, Gentoo is on the cutting edge! What is holding up
OpenLDAP?

The answer is quite simply: DB4.

pauldv has bug #23571 open to track what is stopping DB4 from going out.
They are (with my comments):
#22876 Heimdal 0.6 - this has a patch, just needs testing
#23575 nvi
#23578 dev-perl/DB_File-1.803-r2 - possible obsolete? 
#23583 net-mail/courier-0.42.2 - the author last said he wasn't supporting DB4 yet.
#23586 net-mail/maildrop-1.5.2 - same as #23583.
#23587 net-misc/cfengine-2.0.6 - FreeBSD has it working
#23590 x11-misc/hotkeys-0.5.7.1 - last release Dec 8 2002

These 7 bugs are holding up a large number of packages.

Previously the packages being held up were all hardmasked in
packages.mask, and AMD64 came along, removed the hardmask and instead
changed ACCEPT_KEYWORDS to amd64 only.

I have several production systems running fine at work with DB4 (4.1.25
actually) and several packages that depend on DB4, but that is only
because I don't use those packages that are broken anyway.

Could I suggest for the moment that these packages that still don't work
with DB4 just have blocks applied for DB4, and DB4 (and 4.1) released in
the meantime?

-- 
Robin Hugh Johnson
E-Mail     : robbat2@orbis-terrarum.net
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85