To: team@security.debian.org
To: debian-gcc@lists.debian.org
To: debian-glibc@lists.debian.org
Copy: debian-release@lists.debian.org
Copy: debian-ports@lists.debian.org

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Os8h3B1OR1zP7byy1IvRKKmjD4M6MV3jb
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi,


As part of the interim architecture qualification for buster, we request
that DSA, the security team and the toolchain maintainers review and
update their list of known concerns for buster 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.
* Concerns from the GCC maintainers about armel, armhf, mips, mips64el
and mipsel have been carried over from stretch.

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 and debian-ports@l.d.o in CC to ensure both parties 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]


[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)

* Concern for armel and armhf: only secondary upstream support in GCC
(Raised by the GCC maintainer; carried over from stretch)

* Concern for mips, mips64el, mipsel and ppc64el: no upstream support
in GCC
(Raised by the GCC maintainer; carried over from stretch)


Architecture status
===================

These are the architectures currently being built for buster:

* Intel/AMD-based: amd64, i386
* ARM-based: arm64, armel, armhf
* MIPS-based: mips, mipsel, mips64el
* Other: ppc64el, s390x

If the blocking issues cannot be resolved, affected architectures are at
risk of removal from testing before buster is frozen.

We are currently unaware of any new architectures likely to be ready in
time for inclusion in buster.

On behalf of the release team,
Niels Thykier


--Os8h3B1OR1zP7byy1IvRKKmjD4M6MV3jb--

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAlsz7YoACgkQBUu7n32A ZELAFRAAiU0VqE3jgfz8l/t62aTQejzQOSZhqH2bzasZE5bPMDFZEl9kKcKv9O7R EsJmWoSOu0ZfmgDXlaT4N2NAdH3BF8w5Gm/LvlUxLPnp1ikpqPLIhT9fDfpppp1p h+VYW0Oqpu9N1iyELX1oRnv5k/kdHlrP255PHRtte8TxuQTMNVs4DE8niafGtSc7 EOgnaXtuFTO25fG8Szi7MvMhpNrH+k7nBfzkCsaHlfSzMR9ZLP5I1PpQqB/M467p VI/uG1wH2WbpwI1DWXeZgItDUib6IPjUrSqHcj/CezzGMY9V+W0mFrN3/5fGSyDE xnM62BAsfBD9EOsl13FWa36/F2rtH/hFIkfFJ77khIK6Kz/VyTSU29vnBVEewQLe J4Ogne4y8gEHPy/3o94LiC1vwq4rvUzxaSH8iF40TTOgMXvsSDkMcKxal8wbXC68 fkaPi6hl79cQxs34qPYe5n3XAkDCDILH85G2pLURemAaBWNvxqmm9FkN+Xqi4iWt k8yKClVAU9vB4pvqZ9MPuAfHbvUXR92XLmR/KFZ1J4Xu9S/j9T4mccyYrk15P+QI EIoc6hXgMF30jtqQl18jGkdHS/uy3/0ysBv/kblu6DZp/SQx0dumcAsT3UKAZ86O Ml2YHPT7FhFnjmWaDiRFoEtuv91NJwdSoVYBbbwG85XVtES8nGA=
=42wV
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)