Hi,
[Release Team here]
On Thu, 2 Mar 2023 18:42:56 +0100 Bastian Germann <bage@debian.org> wrote:
On Thu, 2 Mar 2023 05:10:41 +0100 Guilhem Moulin <guilhem@debian.org> 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 AFAICT not by anything particular in the upload.
I am sorry for having caused that issue, Daniel. Thanks for investigating, Guilhem.
The changelog entry is correct because it fixes a formerly made change.
0~20171227-0.1 intended to compile only udeb without threads:
"Build udeb without a dependency on pthreads"
But it unintentionally compiled the .deb executable with the .a compiled without threads.
The additional "make clean" fixes accidentally picking up the wrong .a.
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 cryptsetup
libargon2-1 is linked by more packages. Are they all OK without this unintentional change unfixed? Why is the
unintentional change not reverted or fixed?