On 4/17/25 12:16 PM, Paul Gevers wrote:
Removing the autopkgtest or excluding unreliable architectures will be needed
instead. I don't really want to do either, but nuking the autopkgtest from the
package resolves this class of issues forever.
Let's work together to improve the situation. I understand this is frustrating
from your side, but autopkgtesting has been a great improvement for Debian
release management so it would be sad if for this reason you would remove them.
Adding `Architecture: !arm64` to the control file sounds like the best solution
to deal with unreliable infrastructure.
To avoid having to do this on the package side, I (ci.d.n maintainer hat on)
could add your package to the ci.d.n reject_list until we have a way to disable
needs-internet testing per host and can direct tests that need it to hosts
which support needs-internet [1]. We currently can only switch needs-internet
per architecture and I consider that a too big hammer for arm64 (release team
member hat on).
That doesn't sound like a good idea because then two people need to do work to
re-enable arm64 again.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
