On 2018-01-23 19:56, James Cloos wrote: > AJ> Do you have a list of other packages from the glibc src that are > AJ> upgraded before? > > The following packages have unmet dependencies: > libc-dev-bin : Depends: libc6 (> 2.26) but 2.25-6 is installed > libc6-dev : Depends: libc6 (= 2.26-4) but 2.25-6 is installed > libc6-i386 : Depends: libc6 (= 2.26-4) but 2.25-6 is installed > libc6-pic : Depends: libc6 (= 2.26-4) but 2.25-6 is installed > libc6-x32 : Depends: libc6 (= 2.26-4) but 2.25-6 is installed > locales : Depends: libc-bin (> 2.26) but 2.25-6 is installed > nscd : Depends: libc6 (> 2.26) but 2.25-6 is installed > > And on another box: > > The following packages have unmet dependencies: > libc-dev-bin : Depends: libc6 (> 2.26) but 2.25-6 is installed > libc6-dev : Depends: libc6 (= 2.26-2) but 2.25-6 is installed > libnih1 : Depends: libc6 (> 2.26) but 2.25-6 is installed > locales : Depends: libc-bin (> 2.26) > > And a third: > > The following packages have unmet dependencies: > libc-dev-bin : Depends: libc6 (> 2.26) but 2.25-6 is installed > libc6-dev : Depends: libc6 (= 2.26-4) but 2.25-6 is installed > locales : Depends: libc-bin (> 2.26) but 2.25-6 is installed > > Those are after one previous attempt at --fix-broken.
All the above packages have a proper dependency on libc6 >= 2.26. It's apt which decide they can already be unpacked before libc6 preinst is ran. > AJ> In any case it's not something we can control, the abort is done > AJ> inside the libc6 preinst, there is no way the libc6 package can > AJ> do that earlier. > > Of course it is. Just make every deb from the glibc src do that abort. No, that simply doesn't scale. Other packages than the one in src:glibc depends on libc6 >= 2.26, and more and more are going to pick up this dependency in the next months. They might also be unpacked before libc6 preinst is ran. We can't add this check in every package. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net