info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work
228 views
Skip to first unread message
Kai Weber
Mar 1, 2023, 5:40:04 PM3/1/23
to
As a workaround I created a file /etc/initramfs-tools/hooks/libgcc:
. /usr/share/initramfs-tools/hook-functions
copy_file library /lib/x86_64-linux-gnu/libgcc_s.so.1 /lib/x86_64-linux-gnu/libgcc_s.so.1
With this hook the lib is copied an I am able to provide a password at
login.
. /usr/share/initramfs-tools/hook-functions
copy_file library /lib/x86_64-linux-gnu/libgcc_s.so.1 /lib/x86_64-linux-gnu/libgcc_s.so.1
With this hook the lib is copied an I am able to provide a password at
login.
Christoph Anton Mitterer
Mar 7, 2023, 9:50:04 PM3/7/23
to
Hey Guilhem.
Is it possible that your fix doesn't work on not-yet-usr-merged
systems?
I get here:
$ env --unset=LD_PRELOAD ldd /sbin/cryptsetup | sed -nr '/.*=>\s*(\S+)\/libargon2\.so\..*/ {s//\1/p;q}'
/usr/lib/x86_64-linux-gnu
but:
$ dpkg -L libgcc-s1
/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu/libgcc_s.so.1
On non-usr-merged systems, copy_libgcc doesn't seem to include it then.
Please don't solve this by depending on usr-merge (not that I'd have
anything against it, but I'd like to migrate my systems only when this
becomes the next stable).
Cheers,
Chris.
Is it possible that your fix doesn't work on not-yet-usr-merged
systems?
I get here:
$ env --unset=LD_PRELOAD ldd /sbin/cryptsetup | sed -nr '/.*=>\s*(\S+)\/libargon2\.so\..*/ {s//\1/p;q}'
/usr/lib/x86_64-linux-gnu
but:
$ dpkg -L libgcc-s1
/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu/libgcc_s.so.1
On non-usr-merged systems, copy_libgcc doesn't seem to include it then.
Please don't solve this by depending on usr-merge (not that I'd have
anything against it, but I'd like to migrate my systems only when this
becomes the next stable).
Cheers,
Chris.
Guilhem Moulin
Mar 8, 2023, 8:30:05 AM3/8/23
to
On Wed, 08 Mar 2023 at 14:11:05 +0100, Christoph Anton Mitterer wrote:
> On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote:
>> No please don't, #-1 is RC so that would block transitioning into
>> Bookworm which only supports merged-usr… Will fix that later during
>> the
>> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
>> further delay the transition.
>
> Well but at least right now people without merged /usr will still end
> up in a broken system?
Yes. Been the case for a week (since the argon2=0~20190702-0.1 upload).
However the TC has ruled that these systems are no longer supported, so
the issue isn't RC. Not saying we should shove it under the carpet,
only that it shouldn't delay transition.
> And there is no guarantee that /usr has already been merged at that
> point... I mean it should, when the upgrade to bookwork completes...
> but can it happen that it's interrupted? Or that people do it in
> several steps? Then they could upgrade argon2, reboot and have the
> missing libgcc.
Correct, but AFAICT that's would be a FrankenDebian so not something
supported either. Either way that's not something src:cryptsetup can
fix. One could upload src:argon2 again adding “Break: cryptsetup-initramfs
(<< 2:2.6.1-2)” to libargon2-1, though I'm not sure it's worth doing
given the freeze and the fact that covered that supported systems are
covered.
--
Guilhem.
> On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote:
>> No please don't, #-1 is RC so that would block transitioning into
>> Bookworm which only supports merged-usr… Will fix that later during
>> the
>> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
>> further delay the transition.
>
> Well but at least right now people without merged /usr will still end
> up in a broken system?
Yes. Been the case for a week (since the argon2=0~20190702-0.1 upload).
However the TC has ruled that these systems are no longer supported, so
the issue isn't RC. Not saying we should shove it under the carpet,
only that it shouldn't delay transition.
> And there is no guarantee that /usr has already been merged at that
> point... I mean it should, when the upgrade to bookwork completes...
> but can it happen that it's interrupted? Or that people do it in
> several steps? Then they could upgrade argon2, reboot and have the
> missing libgcc.
Correct, but AFAICT that's would be a FrankenDebian so not something
supported either. Either way that's not something src:cryptsetup can
fix. One could upload src:argon2 again adding “Break: cryptsetup-initramfs
(<< 2:2.6.1-2)” to libargon2-1, though I'm not sure it's worth doing
given the freeze and the fact that covered that supported systems are
covered.
--
Guilhem.
Guilhem Moulin
Mar 8, 2023, 7:20:04 PM3/8/23
to
Control: tag -1 pending
On Wed, 08 Mar 2023 at 14:04:42 +0100, Guilhem Moulin wrote:
> On Wed, 08 Mar 2023 at 13:42:53 +0100, Christoph Anton Mitterer wrote:
>> @Guilhem, I'm reopening this for now.
https://salsa.debian.org/cryptsetup-team/cryptsetup/-/commit/369cb651abad11a3844fa38ea86ece40f4f40078
solves the regression on non merged-/usr systems, but I didn't have such
a system at hand so please confirm :-)
--
Guilhem.
On Wed, 08 Mar 2023 at 14:04:42 +0100, Guilhem Moulin wrote:
> On Wed, 08 Mar 2023 at 13:42:53 +0100, Christoph Anton Mitterer wrote:
>> @Guilhem, I'm reopening this for now.
>
> No please don't, #-1 is RC so that would block transitioning into
> Bookworm which only supports merged-usr… Will fix that later during the
> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
> further delay the transition.
I believe
> No please don't, #-1 is RC so that would block transitioning into
> Bookworm which only supports merged-usr… Will fix that later during the
> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
> further delay the transition.
https://salsa.debian.org/cryptsetup-team/cryptsetup/-/commit/369cb651abad11a3844fa38ea86ece40f4f40078
solves the regression on non merged-/usr systems, but I didn't have such
a system at hand so please confirm :-)
--
Guilhem.
Guillem Jover
Mar 13, 2023, 10:40:05 AM3/13/23
to
Hi!
On Wed, 2023-03-08 at 14:26:13 +0100, Guilhem Moulin wrote:
> On Wed, 08 Mar 2023 at 14:11:05 +0100, Christoph Anton Mitterer wrote:
> > On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote:
> >> No please don't, #-1 is RC so that would block transitioning into
> >> Bookworm which only supports merged-usr… Will fix that later during
> >> the
> >> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
> >> further delay the transition.
> >
> > Well but at least right now people without merged /usr will still end
> > up in a broken system?
>
> Yes. Been the case for a week (since the argon2=0~20190702-0.1 upload).
> However the TC has ruled that these systems are no longer supported, so
> the issue isn't RC. Not saying we should shove it under the carpet,
> only that it shouldn't delay transition.
That's not what the TC ruled though, see:
https://lists.debian.org/debian-devel/2021/10/msg00190.html
Where this is covered explicitly:
,---
- Because Debian 11 installations with the non-merged-/usr layout
already exist, all packages in Debian 12 should be installable onto a
non-merged-/usr system along with their dependencies, and work
correctly on the resulting system.
+ The key reason for this is that apt is not required to perform the
upgrade between stable releases in any particular order, so long
as package dependency relationships are respected; therefore the
upgrade can happen in whatever order apt chooses, which can vary
between machines. Debian has not traditionally required use of a
special upgrade tool similar to Ubuntu's do-release-upgrade(8) and
we believe the upgrade to Debian 12 should be no different (see
below for more details on this topic).
+ Another reason for this is that during the development of Debian
12, testing/unstable systems undergo a series of partial upgrades,
which similarly will happen in an undefined order.
+ We do not require that the resulting system remains
non-merged-/usr: if the packages involved in this installation
transaction are part of the implementation of a transition to
merged-/usr, then installing them might result in the system
becoming merged-/usr.
- The same expectations apply to packages uploaded to testing/unstable
during the development cycle that will lead to Debian 12.
`---
> > And there is no guarantee that /usr has already been merged at that
> > point... I mean it should, when the upgrade to bookwork completes...
> > but can it happen that it's interrupted? Or that people do it in
> > several steps? Then they could upgrade argon2, reboot and have the
> > missing libgcc.
>
> Correct, but AFAICT that's would be a FrankenDebian so not something
> supported either. Either way that's not something src:cryptsetup can
> fix. One could upload src:argon2 again adding “Break: cryptsetup-initramfs
> (<< 2:2.6.1-2)” to libargon2-1, though I'm not sure it's worth doing
> given the freeze and the fact that covered that supported systems are
> covered.
Partial upgrades is the expected state you get when upgrading from
Debian N to Debian N+1.
Thanks,
Guillem
On Wed, 2023-03-08 at 14:26:13 +0100, Guilhem Moulin wrote:
> On Wed, 08 Mar 2023 at 14:11:05 +0100, Christoph Anton Mitterer wrote:
> > On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote:
> >> No please don't, #-1 is RC so that would block transitioning into
> >> Bookworm which only supports merged-usr… Will fix that later during
> >> the
> >> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
> >> further delay the transition.
> >
> > Well but at least right now people without merged /usr will still end
> > up in a broken system?
>
> Yes. Been the case for a week (since the argon2=0~20190702-0.1 upload).
> However the TC has ruled that these systems are no longer supported, so
> the issue isn't RC. Not saying we should shove it under the carpet,
> only that it shouldn't delay transition.
https://lists.debian.org/debian-devel/2021/10/msg00190.html
Where this is covered explicitly:
,---
- Because Debian 11 installations with the non-merged-/usr layout
already exist, all packages in Debian 12 should be installable onto a
non-merged-/usr system along with their dependencies, and work
correctly on the resulting system.
+ The key reason for this is that apt is not required to perform the
upgrade between stable releases in any particular order, so long
as package dependency relationships are respected; therefore the
upgrade can happen in whatever order apt chooses, which can vary
between machines. Debian has not traditionally required use of a
special upgrade tool similar to Ubuntu's do-release-upgrade(8) and
we believe the upgrade to Debian 12 should be no different (see
below for more details on this topic).
+ Another reason for this is that during the development of Debian
12, testing/unstable systems undergo a series of partial upgrades,
which similarly will happen in an undefined order.
+ We do not require that the resulting system remains
non-merged-/usr: if the packages involved in this installation
transaction are part of the implementation of a transition to
merged-/usr, then installing them might result in the system
becoming merged-/usr.
- The same expectations apply to packages uploaded to testing/unstable
during the development cycle that will lead to Debian 12.
`---
> > And there is no guarantee that /usr has already been merged at that
> > point... I mean it should, when the upgrade to bookwork completes...
> > but can it happen that it's interrupted? Or that people do it in
> > several steps? Then they could upgrade argon2, reboot and have the
> > missing libgcc.
>
> Correct, but AFAICT that's would be a FrankenDebian so not something
> supported either. Either way that's not something src:cryptsetup can
> fix. One could upload src:argon2 again adding “Break: cryptsetup-initramfs
> (<< 2:2.6.1-2)” to libargon2-1, though I'm not sure it's worth doing
> given the freeze and the fact that covered that supported systems are
> covered.
Debian N to Debian N+1.
Thanks,
Guillem
0 new messages