Hi Guilhem, On Tue, Feb 27, 2024 at 02:00:05PM +0100, Guilhem Moulin wrote: > The first message of this bug reads: > > | * Please upload these changes to experimental first. That allows > | running them past QA systems such as piuparts, dumat and others and > | also lets us double check the version constraints. > > There is also a coming freeze for Ubuntu 24.04 and I hear they'd like to > have 2.7.0. My bad for delaying this, but right now I want 2.7.0 to > transition to testing first and not risk blocking on cryptsetup-nuke-password > or potential regressions. I intend to upload to sid after the > transition.
Thank you! The reason you give makes sense to me. Indeed, we should have both cryptsetup and cryptsetup-ask-password in experimental (with verified version constraints) before proceeeding to unstable. You are correct that cryptsetup-nuke-password did not make it to experimental and hence you were not good to proceed to unstable. I call that attention to detail. :) Please reupload the patch to experimental (with a version higher than unstable) assuming that cryptsetup-nuke-password will use version 5 as I am in contact with Raphael Hertzog. Your concern with the Ubuntu freeze also is valid, but it actually is the other way round. Ubuntu already has made the changes in base-files at al that this bug is blocking in Debian. Ubuntu needs this change even more urgently than Debian does. I hope cryptsetup makes it to testing soon (it'll migrate with lvm2) such that we can move forward here. Helmut
