sys-fs/cryptsetup-2.0.3-r1 stabilization request Gentoo minimal installation CD should use cryptsetup >= 2 because sys-fs/cryptsetup-1.7.5-r1 does not support LUKS2 headers.
This will require some re-keywording effort.
We need to choose a new version to stabilize.
(In reply to Andrius Štikonas from comment #2) > We need to choose a new version to stabilize. Sure. 2.0.6 is the newest version in Portage tree.
Looks like alpha and arm are the only arches whose keywords are still missing from cryptsetup-2.0.6... Maybe it is time to start stabilising for arches that are already there? After all that will not happen overnight either.
(In reply to Marek Szuba from comment #4) > Looks like alpha and arm are the only arches whose keywords are still > missing from cryptsetup-2.0.6... Maybe it is time to start stabilising for > arches that are already there? After all that will not happen overnight > either. I think arm can safely be keyworded. It seems to work on my Odroid U2 (armv7a). (argon2 also needs to be stabilized on arm before cryptsetup stabilization).
1.7.5-r1 is getting really old, can we have 2.06 or 2.1.0 stabilized?
We should change stabilization target to 2.1.0. On arm64 it was already stabilized as part of another bug.
sparc stable
Already stable for arm64: 46454e00527a51f015d8ba1b74e229529700b2b3
arm stable
ppc stable
ppc64 stable
x86 stable
amd64 stable
alpha stable
ia64 stable
s390 will want this for stabilizing sys-apps/s390-tools-2.9.0. Adding to cc.
s390 stable. Closing.
hppa stable Reopening for sh
sh was added by accident, all done. Closing.