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.

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.

Idealy, w/ a warning on how to hold them so that the rest of the
upgradable packages can do so.

-JimC
-- 
James Cloos <cl...@jhcloos.com>         OpenPGP: 0x997A9F17ED7DAEA6

Reply via email to