Bug#1034696: libargon2-1-udeb: should build with threading support

2023-04-21 Thread Guilhem Moulin
This is beneficial for cryptsetup-udeb, see #1028250. Removing threading +support in libargon2-1-udeb was done for historical reasons no longer +relevant since Debian Bookworm. + + -- Guilhem Moulin Fri, 21 Apr 2023 19:48:56 +0200 + argon2 (0~20190702+dfsg-2) unstable; urgency=medium

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

2023-03-16 Thread Guilhem Moulin
Hi, On Thu, 16 Mar 2023 at 13:44:11 +0100, Paul Gevers wrote: >> As I already mentioned on this or some related bug, I would find it nice >> for #1014110 to be fixed in bookworm (threaded argon2 executable) but I >> do not insist on it. > > cryptsetup can only migrate when argon2 migrates, I see

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

2023-03-16 Thread Guilhem Moulin
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 a

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

2023-03-16 Thread Guilhem Moulin
Hi, On Thu, 16 Mar 2023 at 09:13:44 +0100, Paul Gevers wrote: > On 15-03-2023 23:28, Guilhem Moulin wrote: >> Yes there is, namely the fact that libargon2-1 no longer links against >> libpthread, which in turn caused a major regression in >> cryptsetup-initramfs (mitigate

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

2023-03-15 Thread Guilhem Moulin
Hi, On Wed, 15 Mar 2023 at 22:43:31 +0100, Bastian Germann wrote: > Am 15.03.23 um 22:39 schrieb Paul Gevers: >> Do I understand correctly that: >> 1) argon2 in testing isn't affected >> 2) this bug isn't solved yet, despite the closure? >> 3) the issue for cryptsetup is worked around in cryptsetu