Re: Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

2020-11-19 Thread Marco d'Itri
On Nov 19, Sven Joachim  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


Re: Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

2020-11-19 Thread Sven Joachim
On 2020-11-19 19:47 +0100, Marco d'Itri wrote:

> On Nov 16, Niko Tyni  wrote:
>
>> As to the fix, I suspect we need a pre-dependency from libc6 to libcrypt1
>> for one release cycle, so that libc6 cannot be unpacked before libcrypt1
>> is fully installed.
> I think that Niko is right, so I would like to know the opinion of the
> glibc maintainers.

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.

Cheers,
   Sven



Re: Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

2020-11-19 Thread Marco d'Itri
On Nov 16, Niko Tyni  wrote:

> As to the fix, I suspect we need a pre-dependency from libc6 to libcrypt1
> for one release cycle, so that libc6 cannot be unpacked before libcrypt1
> is fully installed.
I think that Niko is right, so I would like to know the opinion of the 
glibc maintainers.

-- 
ciao,
Marco


signature.asc
Description: PGP signature