[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1032235: Bug#1014110: libargon2 0~20190702-0.1 no longer links against libpthread which breaks cryptsetup-initramfs



Hi Guilhem,

On 16-03-2023 14:31, Guilhem Moulin wrote:
cryptsetup can only migrate when argon2 migrates,

I see that in the excuse page now but don't understand the reason why,

It took me a while and the help of colleagues, but it's libcryptsetup12-udeb that has:
Depends: libargon2-1-udeb (>= 0~20190702)

While writing this up and discussing with others, I realized that the error
is coming from one of glibc's binaries. It has been stated that the issue

started with with a change there, but is that change done on purpose, or a
bug? I.e. is one of glibc's binaries missing a dependency?

It was intentional, see the article
https://developers.redhat.com/articles/2021/12/17/why-glibc-234-removed-libpthread .
Unfortunately that change broke initramfs-tools' fix for https://bugs.debian.org/950254
which we (src:cryptsetup maintainers) relied on for cryptsetup-initramfs.
Until last week src:argon2 had never been rebuilt with the newer glibc,
so it's just unfortunate that we missed that at the time.

I'm very happy that we found this well before the release, even thought it's late in the freeze.

I wonder if other packages are affected.  Another fix would be to change
initramfs-tools' inclusion logic for LIBGCC_S_SO.  (I don't know if
autodetection is still doable, otherwise it could still copy the library
unconditionally at the expense of a larger initramfs image.)

Can you elaborate and/or can you discuss with the initramfs-tools maintainers? I lack the background of how this all works and interconnects, so you'll need to explain everything or come with a proposal that the stakeholders (you and other involved maintainers) agree with.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: