architecture requalification status for bookworm

Debian Release Management

NOTE: This document should be a living document, but experience learns that the main part of the qualification process only happens near the end.

amd64 arm64 armel armhf i386 mips64el mipsel ppc64el riscv64 s390x
available yes yes yes yes yes yes yes yes yes yes
portbox yes yes yes yes yes yes yes yes - yes
porters - (w) 2 2 2 1 1 1 1 4 2
installer d-i d-i d-i d-i d-i d-i d-i d-i d-i d-i
archive-coverage 99 99 97 98 98 97 97 98 96 97
archive-uptodate 99 99 99 99 99 99 99 99 99 99
upstream-support yes yes glibc has trouble finding qualified persons to implement security fixes,
might be special because the use of the libatomics library is mandatory
glibc has trouble finding qualified persons to implement security fixes no: missing CPU security mitigations in Linux kernel no: no upstream support in GCC,
unaddressed test failures in binutils
no: no upstream support in GCC,
unaddressed test failures in binutils
yes yes yes
buildds 5 8 8 10 5 10 10 2 6 2
buildd-dsa yes yes yes yes yes yes yes yes no yes
autopkgtest yes yes yes yes yes no no yes available yes
concerns-rm no no some builds are hitting the address space limit some builds are hitting the address space limit only one porter has volunteered,
some builds are hitting the address space limit
builders are extremely slow (also per kernel team),
only one porter has volunteered,
lack of autopkgtest infrastructure,
future availability of hardware
builders are extremely slow (also per kernel team),
only one porter has volunteered,
some builds are hitting the address space limit,
lack of autopkgtest infrastructure,
future availability of hardware
only one porter has volunteered ? no
concerns-srm as RM concerns as RM concerns as RM concerns as RM concerns as RM concerns as RM concerns as RM concerns as RM concerns ? as RM concerns
concerns-dsa no no no no no no no rely on sponsors for hardware (mild concern) ? rely on sponsors for hardware (mild concern)
concerns-sec no no no no no no no no ? no
candidate yes ? ? ? ? ? ? ? ? ?

Waivers

amd64

Porters

Our toolchain maintainers are happy to support amd64 as-is.

The source for this page can be found in the Release Team's git archive.