what is the reason why that package is not moving forward?
I assume you're referring to the dpkg upload that's in proposed-updates waiting for the point release in two weeks time?
I'm also getting very tired of the repeated vilification of SRM over
this, and if there were any doubt can assure you that it is not
increasing at least my inclination to spend my already limited free
time on Debian activity.
i don't know: i'm an outsider who doesn't have the information in
short-term memory, which is why i cc'd the debian-riscv team as they
have current facts and knowledge foremost in their minds. which is
why i included them.
It would have been wiser to do so *before* stating that nothing was
happening as if it were a fact.
ah. so what you're saying is, you could really do with some extra
help?
I don't think that's ever been in dispute for basically any core team
in Debian.
That doesn't change the fact that the atmosphere around the change in question has made me feel very uncomfortable and unenthused about SRM
work. (I realise that this is somewhat of a self-feeding energy
monster.)
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
On Tue, Dec 11, 2018 at 09:46:21PM +0100, Gregor Riepl wrote:
The build and package delivery infrastructure should offer the same features
for both first and second class archs, including installer image building for
all "tiers" (stable, testing, unstable).
It seems to me that the important bit is the testing suite. As a (now lapsed) x32 porter, I tried to implement that on my own (goal being an unofficial, weakly security supported[1] Jessie for x32). And tracking testing on my own proved to be too hard.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 399 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 99:03:55 |
| Calls: | 8,363 |
| Calls today: | 2 |
| Files: | 13,162 |
| Messages: | 5,897,780 |