On 19/11/17 22:57, Axel Beckert wrote: > Hi again, > > Axel Beckert wrote: >> Indeed. It still depends on libc6 < 2.25 despite being rebuilt against >> libc6 2.25 according to >> https://buildd.debian.org/status/package.php?p=libnih > > Nope, the rebuilt against libc6 2.25 went wrong and was still against > version 2.24, at least on amd64: > https://buildd.debian.org/status/fetch.php?pkg=libnih&arch=amd64&ver=1.0.3-8%2Bb1&stamp=1511115842&raw=0 > > And a local rebuilt in pbuilder (as of Git HEAD in the packaging repo) > worked fine and shows the proper dependencies. > > So for now, it just seems necessary to fix the binary rebuild > (BinNMU). > > And since the release team is tracking this at > https://release.debian.org/transitions/html/glibc-2.25.html anyway, I > expect them to notice that, too, very soon, or already have. > Nevertheless, Cc'ing them to make sure they're aware of this bug > report. As far as I can see, this bug can be closed when the fixed > rebuild on amd64 hits unstable.
Yep, my bad. I (again) forgot to add --extra-depends to the binNMUs, as libc is installed on the chroots and they don't get updated for each build. I'll fix this, either by adding --extra-depends on libc-bin (as there are too many different libc SONAMEs) or by waiting a few hours as the chroots will be updated soon. Cheers, Emilio