[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



On Thu, 16 Mar 2023 at 16:01:47 +0100, Paul Gevers wrote:
> 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)

Oh I see, thanks for the info and sorry for not doing the homework!
That might also explain why src:cryptsetup 2:2.6.1-2 was blocked from
entering testing in time.  That's unfortunate though, as it'll block
unblock requests for src:cryptsetup unless src:argon2 is unblocked as
well.  Leaving it to kibi if the #1028250 mitigation warrants an unblock
or not :-)

>> 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.

Sure, will file a bug against initramfs-tools and X-Debbugs-Cc:
debian-release@l.d.o.

-- 
Guilhem.

Attachment: signature.asc
Description: PGP signature


Reply to: