On Wed, Jul 29, 2009 at 03:52:28AM +0200, Aurelien Jarno wrote: > On Wed, Jul 29, 2009 at 12:28:30AM +0200, Vincent Danjean wrote: > > Hi, > > > > Aurelien Jarno wrote: > > > The only difference with the unstable version is that libc-bin and > > > libc-dev-bin are splitted out of libc6 and libc6-dev. This way it > > > complies with the Debian Policy requirement that the libraries should > > > not contain binaries, which is also a requirement for multiarch. > > > > I just tried to upgrade libc6 with experimental. The upgrade has been > > smooth but libc-dev-bin has not been pulled in (whereas libc6-dev has been > > upgraded). Is it the expected behavior ? > > > > Thanks for noticing that. It's not normal that libc-dev-bin is not > pulled, but if you look at the dependencies it actually normal. > > I'll try to understand why the dependency is declared in the > debian/control file, but does not appear is in the final binary. Stay > tuned. >
I have just found, the problem, it will be fixed in the next upload. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
