Am 23.03.23 um 09:58 schrieb Paul Gevers:
Bastian, if you really want that threaded bug fixed, please prepare a targeted fix based on the version currently in
bookworm and revert all other changes. We can then review the targeted fix. But I'll not unblock the version of argon2
as it's currently
Control: tags -1 d-i
Hi Bastian, Guilhem,
On 16-03-2023 13:44, Paul Gevers wrote:
cryptsetup will need to migrate to mitigate the time bomb.
Ack.
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
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
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
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
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
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
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
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
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
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
Am 15.03.23 um 22:39 schrieb Paul Gevers:
Hi,
[Release Team here]
On Thu, 2 Mar 2023 18:42:56 +0100 Bastian Germann wrote:
On Thu, 2 Mar 2023 05:10:41 +0100 Guilhem Moulin wrote:
> Ah no my bad, the changelog entry is probably incorrect and the
> cryptsetup-initramfs breakage is caused by
Hi,
[Release Team here]
On Thu, 2 Mar 2023 18:42:56 +0100 Bastian Germann wrote:
On Thu, 2 Mar 2023 05:10:41 +0100 Guilhem Moulin wrote:
> Ah no my bad, the changelog entry is probably incorrect and the
> cryptsetup-initramfs breakage is caused by the recent libargon2 upload
> indeed, but
13 matches
Mail list logo
