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

2021-04-15 Thread Niko Tyni
On Wed, Apr 14, 2021 at 08:50:46PM +0200, Paul Gevers wrote: > Hi Ivo, Marco, > > On 06-04-2021 22:10, Ivo De Decker wrote: > > I ran a number of (partial and full) upgrade tests, and they all seem to > > work > > fine. In all cases, libcrypt1 is installed before libc6, and there is no > >

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

2021-04-15 Thread Ivo De Decker
Hi Marco, On Thu, Apr 15, 2021 at 02:27:10PM +0200, Marco d'Itri wrote: > On Apr 14, Paul Gevers wrote: > > > The patch looks sensible after reading the discussion in these bugs. Can > > we have an upload soon to have exposure? > Unless there are any objections I will do a libxcrypt upload in a

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

2021-04-15 Thread Marco d'Itri
On Apr 14, Paul Gevers wrote: > The patch looks sensible after reading the discussion in these bugs. Can > we have an upload soon to have exposure? Unless there are any objections I will do a libxcrypt upload in a couple of days. I think that I can leave the udeb library in /usr/lib/. --

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

2021-04-14 Thread Paul Gevers
Hi Ivo, Marco, On 06-04-2021 22:10, Ivo De Decker wrote: > I ran a number of (partial and full) upgrade tests, and they all seem to work > fine. In all cases, libcrypt1 is installed before libc6, and there is no > intermediate situations where libcrypt.so.1 is missing. The patch looks sensible

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

2021-04-06 Thread Ivo De Decker
Hi, On Fri, Mar 19, 2021 at 04:52:57PM +0100, Ivo De Decker wrote: > > > I wonder if all this might be caused by the breaks from libcrypt1 (against > > > libc6 (<< 2.29-4)). Is there a way to remove the breaks without causing > > > issues? Maybe this is somewhat similar to the situation in > >