architecture requalification status for forky

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.

An explanation of this table can be derived from our architecture criteria page.

amd64 arm64 armhf i386 loong64 ppc64el riscv64 s390x
available yes yes yes yes yes yes yes yes
portbox yes yes yes yes yes yes yes yes
porters - (w) 2 2 1 2 3 4 1
installer d-i d-i d-i d-i d-i d-i d-i d-i
archive-coverage 99 99 98 98 96 98 96 97
archive-uptodate 99 99 99 99 99 99 99 99
upstream-support yes yes glibc has trouble finding qualified persons to implement security fixes considering purpose of port only mild concern yes yes yes yes
buildds 6 9 13 6 6 2 9 2
buildd-dsa yes yes yes yes no yes yes yes
autopkgtest yes yes yes yes yes yes yes yes
concerns-rm no no some builds are hitting the address space limit only one porter has volunteered,
some builds are hitting the address space limit
? - lots of hardware is slow no
concerns-srm as RM concerns as RM concerns as RM concerns as RM concerns ? - as RM concerns as RM concerns
concerns-dsa no Mostly OK Mostly OK no ? no host performance and OOB management (mild concern) rely on sponsors for hardware (mild concern)
concerns-sec no no no no ? no ? no
candidate yes yes yes yes no yes yes 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.