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 | armel | armhf | i386 | loong64 | mips64el | ppc64el | riscv64 | s390x | |
|---|---|---|---|---|---|---|---|---|---|---|
| available | yes | yes | yes | yes | yes | yes | yes | yes | yes | yes |
| portbox | yes | yes | yes | yes | yes | yes | yes | yes | yes | yes |
| porters | - (w) | 2 | 2 | 2 | 1 | 2 | 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 | 96 | 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 | yes | no: no upstream support in GCC, unaddressed test failures in binutils |
yes | yes | yes |
| buildds | 6 | 9 | 13 | 13 | 6 | 6 | 8 | 2 | 9 | 2 |
| buildd-dsa | yes | yes | yes | yes | yes | no | yes | yes | yes | yes |
| autopkgtest | yes | yes | yes | yes | yes | yes | no | yes | yes | 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 |
? | yes: upgrading buildds is impossible due to kernel bugs kernel bugs are hitting some of the buildds making them unusable builders are extremely slow (also per kernel team), only one porter has volunteered, lack of autopkgtest infrastructure, future availability of hardware |
only one porter has volunteered | no | 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 | yes: unstable and ageing hardware | yes: unstable and ageing hardware | yes: unstable and ageing hardware | no | ? | yes: non-server-grade hardware time sink for DSA and hosters |
hosting is not great, effectively not redundant. Unclear what our options are regarding purchasing hardware. |
? | rely on sponsors for hardware (mild concern) |
| concerns-sec | 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.