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.1-2). Unlike >> what I initially claimed in #1014110's msg#20 that change can't be >> reverted or fixed in src:argon2 since it's caused by building with a >> newer libc; a binNMU would therefore have caused the same regression, > > 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 the archive, but also for downstreams > and other users that do rebuilds). Yup, any rebuilt of src:argon2 in bookworm using the bookworm toolchain would break cryptsetup-initramfs <<2:2.6.1-2. That would include src:argon2 uploads to security-master and s-p-u. > For the record, with my current understanding I prefer the scenario of > keeping the versions of argon2 and cryptsetup in bookworm as they are. With the clarification I hope you agree that src:cryptsetup ≥2:2.6.1-2 should be in bookworm :-) -- Guilhem.
Attachment:
signature.asc
Description: PGP signature