On Nov 19, Sven Joachim <svenj...@gmx.de> wrote: > I am not one of them, but AFAICS that would introduce a fatal circular > dependency between libc6 and libcrypt1: libc6 needs libcrypt1 to be > configured before it can be unpacked, but libcrypt1 depends on libc6 so > it cannot be configured before libc6 is at least unpacked. Good point, you are right. :-( Then we are up to plan B, which is a bit more complex but should still be approachable:
Another option might be to have the new libc6 Conflict with old versions of Essential:yes packages that need libcrypt1, forcing those Essential:yes packages to get upgraded first. A quick check based on libcrypt1 reverse dependencies in sid shows perl-base, login and util-linux. I'm not sure if this list is exhaustive, though. -- ciao, Marco
signature.asc
Description: PGP signature