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
> >
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
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/.
--
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
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
>
>
Hi,
On Fri, Mar 19, 2021 at 03:51:34PM +0100, Aurelien Jarno wrote:
> > However, in all of my tests, between the unpack of the new libc6 and
> > libcrypt1
> > only other unpacks where done, and no dpkg hooks where run. If you have a
> > way
> > to reproduce the upgrade where dpkg ran the hook
On 2021-03-19 15:24, Ivo De Decker wrote:
> Hi,
>
> On Fri, Nov 20, 2020 at 01:44:50PM +0100, Alois Wohlschlager wrote:
> > Am Freitag, den 20.11.2020, 09:13 + schrieb Niko Tyni:
> > > I don't think this is related to the recent perl 5.30 -> 5.32
> > > transition.
> > > The report is about a
Hi,
On Fri, Nov 20, 2020 at 01:44:50PM +0100, Alois Wohlschlager wrote:
> Am Freitag, den 20.11.2020, 09:13 + schrieb Niko Tyni:
> > I don't think this is related to the recent perl 5.30 -> 5.32
> > transition.
> > The report is about a buster -> bullseye upgrade, and perl in
> > bullseye
> >
Hi,
On Fri, 20 Nov 2020 13:44:50 +0100 Alois Wohlschlager
wrote:
> > > > 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
Am Freitag, den 20.11.2020, 09:13 + schrieb Niko Tyni:
> I don't think this is related to the recent perl 5.30 -> 5.32
> transition.
> The report is about a buster -> bullseye upgrade, and perl in
> bullseye
> was still at 5.30 at the time.
>
> In any case, the report says perl (presumably
On Fri, Nov 20, 2020 at 09:30:23AM +0100, Aurelien Jarno wrote:
> On 2020-11-16 16:39, Niko Tyni wrote:
> > On Fri, Nov 13, 2020 at 08:48:19PM +0100, Sven Joachim wrote:
> > > On 2020-11-13 18:23 +0100, Niels Thykier wrote:
> > >
> > > > Control: reassign -1 perl-base
> > > > Control: affects -1
Hi,
On 2020-11-16 16:39, Niko Tyni wrote:
> On Fri, Nov 13, 2020 at 08:48:19PM +0100, Sven Joachim wrote:
> > On 2020-11-13 18:23 +0100, Niels Thykier wrote:
> >
> > > Control: reassign -1 perl-base
> > > Control: affects -1 upgrade-reports
> > > Control: severity -1 grave
> > >
> > > Hi Perl
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
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
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.
--
On Fri, Nov 13, 2020 at 08:48:19PM +0100, Sven Joachim wrote:
> On 2020-11-13 18:23 +0100, Niels Thykier wrote:
>
> > Control: reassign -1 perl-base
> > Control: affects -1 upgrade-reports
> > Control: severity -1 grave
> >
> > Hi Perl team,
> >
> > I have reassigned this bug to perl because
On Sat, Nov 14, 2020 at 03:01:10PM +0100, Marco d'Itri wrote:
> On Nov 14, Dominic Hargreaves wrote:
>
> > This seems to be same as #953562 which was reported in March.
> Why do you think that this is the same?
The symptoms seem identical, at least. Maybe there is more than one
root cause that
On Nov 14, Dominic Hargreaves wrote:
> This seems to be same as #953562 which was reported in March.
Why do you think that this is the same?
--
ciao,
Marco
signature.asc
Description: PGP signature
Control: reassign -1 libcrypt1
Control: forcemerge -1 953562
On Fri, Nov 13, 2020 at 08:48:19PM +0100, Sven Joachim wrote:
> On 2020-11-13 18:23 +0100, Niels Thykier wrote:
>
> > Control: reassign -1 perl-base
> > Control: affects -1 upgrade-reports
> > Control: severity -1 grave
> >
> > Hi Perl
On 2020-11-13 18:23 +0100, Niels Thykier wrote:
> Control: reassign -1 perl-base
> Control: affects -1 upgrade-reports
> Control: severity -1 grave
>
> Hi Perl team,
>
> I have reassigned this bug to perl because perl-base being essential
> must remain functional during an upgrade and AFAICT
20 matches
Mail list logo
