El 5/1/25 a las 14:04, Niels Thykier escribió:
Package: release.debian.org
Severity: wishlist
X-Debbugs-Cc: ni...@thykier.net
Hi,
I just file a bug for the build times of riscv possibly being too slow
(#1092153). Thinking about it in a more general view, I think it would make
sense for Debian to require build times on buildds to have an upper limit for
an architecture to qualify. My concrete proposal would be something like 48
hours.
I have not validated if all architectures can meet the proposed 48 hour limit,
so take that proposal with some amount of salting. Nevertheless, this metric
should be fairly easy to extract automatically from the buildd/wanna-build
database.
As for the rationale, slow build times beyond 48 hours affect Debian in ways
such as:
* Delays deployment of security fixes in all suites.
* Delays testing migration (and thereby RC bug fixes) for packages with
autopkgtests. After 5 days of build-time, even packages without
autopkgtests get delayed.
If I was an user of a "slow" architecture, I would much prefer to have delayed
security fixes
than not having security fixes at all.
Regarding testing migration, remember that we started with 10 days. I don't
think that
waiting 7 days for a migration in some exceptional cases is a big problem.
For the normal "keeping up" cases, I assume that slow architectures should have
more autobuilders available to compensate for their slowness.
So, I hope we can think of other solutions before dropping an architecture for being
"slow".
(Bcc:Niels, please reply to the bug address).
Thanks.
