Bug#1033090: unblock: dhcpdump/1.8-6

2023-03-16 Thread Boian Bonev
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: dhcpd...@packages.debian.org, kilob...@debian.org Control: affects -1 + src:dhcpdump Please unblock package dhcpdump [ Reason ] Patches in 1.8-6 fix: - a severe bug (OOB acce

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

2023-03-16 Thread Paul Gevers
Hi, [@aurel32, glibc question at the bottom] On 16-03-2023 11:57, Bastian Germann wrote: Am 16.03.23 um 09:13 schrieb Paul Gevers: I'm not 100% sure I parse that sentence as you intended, so let me ask explicitly: if we binNMU (now or in the future) src:argon2 version 0~20171227-0.3 in bookwo

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 and the help of colleagues, but it's libcr

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

2023-03-16 Thread Paul Gevers
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 (

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

2023-03-16 Thread Aurelien Jarno
Hi, On 2023-03-16 13:44, Paul Gevers wrote: > Hi, > > [@aurel32, glibc question at the bottom] > > On 16-03-2023 11:57, Bastian Germann wrote: > > Am 16.03.23 um 09:13 schrieb Paul Gevers: > > > I'm not 100% sure I parse that sentence as you intended, so let me > > > ask explicitly: if we binNMU

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 (mitigated in src:cryptsetup 2:2.6.

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

2023-03-16 Thread Bastian Germann
Am 16.03.23 um 09:13 schrieb Paul Gevers: I'm not 100% sure I parse that sentence as you intended, so let me ask explicitly: if we binNMU (now or in the future) src:argon2 version 0~20171227-0.3 in bookworm, would it also loose its linking to libpthread? That would be a time bomb (not only in th

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

2023-03-16 Thread Paul Gevers
Hi all, On 15-03-2023 23:28, Guilhem Moulin wrote: 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 cry