Arch qualification for bookworm: call for DSA, Security, toolchain concerns
Hi,
As part of the interim architecture qualification for bookworm, we
request that DSA, the security team, Wanna build, and the toolchain
maintainers review and update their list of known concerns for bookworm
release architectures.
If the issues and concerns from you or your team are not up to date,
then please follow up to this email (keeping debian-release@l.d.o in CC
to ensure we are notified).
In particular, we would like to hear any new concerns for riscv64
(see below).
Whilst porters remain ultimately responsible for ensuring the
architectures are ready for release, we do expect that you / your team
are willing to assist with clarifications of the concerns and to apply
patches/changes in a timely manner to resolve the concerns.
List of concerns for architectures
==================================
The following is a summary from the current architecture qualification
table [1].
* Concern for ppc64el and s390x: we are dependent on sponsors for
hardware.
(Raised by DSA; carried over since stretch)
* Concern for armel and armhf: glibc upstream has trouble
finding qualified persons to implement security fixes for
the 32-bit Arm architectures.
(Raised by glibc upstream; carried over from bullseye)
* Concern for armel: might be special because the use of the
libatomics library is mandatory.
(Raised by the GCC maintainer; carried over from bullseye)
* Concern for mips64el and mipsel: no upstream support in GCC;
Debian carries patches in binutils and GCC that haven't been
integrated upstream even after a long time. Unaddressed test
failures in binutils.
(Raised by the GCC maintainer; carried over from bullseye)
* Concern for mips64el and mipsel: builders are extremely slow.
(Raised by kernel team; carried over from bullseye)
* Concern for arm*, i386, mips* and ppc64el: only one porter
has volunteered for each of these architectures.
(Raised by release team)
* Concerns for mips64el and mipsel: builders are slow and hold up
transitions, lack of autopkgtest infrastructure, future availability of
hardware due to MIPS (the company) pivoting to RISC-V [2].
(Raised by release team)
* Concern for 32-bit architectures (armel, armhf, i386 and mipsel):
some builds are hitting the address space limit on these architectures.
(Raised by release team)
Architecture status
===================
These are the architectures currently being built for bookworm:
* Intel/AMD-based: amd64, i386
* ARM-based: arm64, armel, armhf
* MIPS-based: mipsel, mips64el
* Other: ppc64el, s390x
If the blocking issues cannot be resolved, affected architectures are at
risk of removal from testing before bookworm is frozen.
We are aware of efforts to have riscv64 ready in time for inclusion in
bookworm.
On behalf of the release team,
Graham Inggs
[1] https://release.debian.org/bookworm/arch_qualify.html
[2] https://riscv.org/blog/2022/05/mips-pivots-to-risc-v-with-best-in-class-performance-and-scalability-mips/
Reply to: