Hi,
[Note, this e-mail may look familiar as it is mostly copied over from
the buster call, not much has changed, AFAICT].
As part of the interim architecture qualification for bullseye, we
request that DSA, the security team, Wanna build, and the toolchain
maintainers review and update their list of known concerns for bullseye
release architectures.
Summary of the current concerns and issues:
* DSA have announced a blocking issue for armel and armhf (see below)
* Concerns from DSA about ppc64el and s390x have been carried over from
(stretch and) buster.
* Concerns from the GCC maintainers about i386, armel, armhf, mips64el
and mipsel have been carried over from (stretch and) buster.
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).
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 blocking issues by architecture
=======================================
The following is a summary from the current architecture qualification
table.
armel/armhf:
------------
* Undesirable to keep the hardware running beyond 2020. armhf VM
support uncertain. (DSA)
- Source: [DSA Sprint report]
- I was under the impression that this issue has been resolved (at
least for armhf) by now, but we like a fresh statement on this.
[DSA Sprint report]:
https://lists.debian.org/debian-project/2018/02/msg00004.html
List of concerns for architectures
==================================
The following is a summary from the current architecture qualification
table.
* Concern for ppc64el and s390x: we are dependent on sponsors for
hardware.
(Raised by DSA; carried over from stretch and buster)
* Concern for armel and armhf: only secondary upstream support in GCC
(Raised by the GCC maintainer; carried over from stretch and buster)
* Concern for mips, mips64el, mipsel and ppc64el: no upstream support
in GCC; Debian carries patches in binutils and GCC that haven't been
integrated upstream even after a long time.
(Raised by the GCC maintainer; carried over from stretch and buster)
Architecture status
===================
These are the architectures currently being built for bullseye:
* 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 bullseye is frozen.
We are currently unaware of any new architectures likely to be ready in
time for inclusion in bullseye.
On behalf of the release team,
Paul Gevers
Attachment:
signature.asc
Description: OpenPGP digital signature