On Nov 01, 2003, at 08:21, Florin wrote:
So i have spent some more energy in providing fixed nss_ldap-211 rpms I called them -3mdk to avoid further confusion. I also uploaded a newer 207 with fixed buildrequires
I had a look at your packages and they seem fine to me ... so I have copied on my web site aswell ... thank you for your work again.
And, again, I would recommend this for an errata.
Ok... I'm confused.
Where does this bug exhibit itself? Only in cooker? Or with 9.2, and under what conditions? Surely a buildrequires error would make it work, or not, for all installs, no?
I'm using nss_ldap-207-2mdk here on a workstation and a laptop and I don't see the errors you describe with dbopen and getent. Just tried it on both and re-read your message, but I'm still confused.
If this is a buildrequires problem, and nss_ldap is "broken", then shouldn't it be broken *everywhere*? Why would you get the dbopen errors and I don't?
Ohhh... wait a sec. Your cert7.db file is what is causing the problem? When nss_ldap tries to open it to get the cert before connecting to the LDAP server, right?
So your -3mdk packages fix that? No more dbopen errors when nss_ldap tries to open your cert7.db file?
If yes, and it's verified that it works, then I'll build packages to put into updates. I don't use a db here and really have no clue how to make a db file to test this, so unless you can give me a quick "test howto" kinda thing, I have to rely on your testing results to put it through.
Thanks
--- MandrakeSoft Security; http://www.mandrakesecure.net/ Online Security Resource Book; http://linsec.ca/ "lynx -source http://linsec.ca/vdanen.asc | gpg --import" {FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
PGP.sig
Description: This is a digitally signed message part
