On Mon, Oct 19, 2009 at 09:00:02PM +0200, Aurelien Jarno wrote: > On Mon, Oct 19, 2009 at 01:32:32PM -0400, Roberto C. Sánchez wrote: > > On Mon, Oct 19, 2009 at 07:21:06PM +0200, Aurelien Jarno wrote: > > > > > > I don't understand something. Is nscd installed inside the chroot? And > > > outside? > > > > > Yes, it is installed inside and outside. Though, I do not run the > > Sorry, but I still don't understand: > > > > widespread the problem is. If it makes a difference, the sid > > > installation being affected by this is an amd64 Sid chroot on an amd64 > > > Lenny system that I use for development. > > If your host is a Lenny installation, how did you installed nscd 2.10.1-1? > It was installed into the Sid chroot. I am not sure how, but something else pulled it in as a recommends. I have now removed it. > > daemon inside the chroot. I guess that on that realization, perhaps > > nscd itself is not the cuplrit. The packages I ended up reverting were: > > > > libc-bin > > libc-dev-bin > > libc6-dev > > libc6 > > nscd > > nscd should not be needed in the chroot. > I have removed it. I can confirm that the behavior persists even when upgrading just the other four packages. > Could you try to rebuild the libnss-ldap package in a sid environment > (at least with libc6-dev 2.10.1-1) and see if it helps? > I have rebuilt libnss-ldap in a sid pbuilder with libc6-dev 2.10.1-1. Then I installed in the Sid chroot along with upgrading libc-bin, libc-dev-bin, libc6-dev and libc6 in that chroot to 2.10.1-1. Even with the rebuilt libnss-ldap, the behavior persists. -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
Attachment:
signature.asc
Description: Digital signature