Hi, Simon is completely right.
On 29-05-2025 01:34, Simon McVittie wrote:
in your position I'd want to add this test coverage in experimental first, and delay adding it in unstable until the forky cycle opens unless there's a reason why it's particularly important.
As a related remark, uploads to experimental will automatically trigger autopkgtest test *in unstable* like we trigger tests *in testing* for uploads to unstable, but only on amd64 and arm64. If you go this route (and want to upload to unstable despite the recommendation of Simon) I highly recommend to trigger the package's own tests on all the other relevant architectures via the self-service on ci.d.n to see if they pass.
A further related note: source packages that build only arch:<arch> binaries are only tested on the architectures where they are built, but packages that build at least one arch:all binary are tested everywhere where the arch:all binaries are installable. Unfortunately packages that meet the following characteristics need an hint from the release team (to avoid the busy work for maintainers to keep an Architecture field in the d/t/control file up-to-date):
* build both arch:<arch> and arch:all binaries * some architectures fail to build (or are not build at all)* the autopkgtest fails because of the missing arch:<arch> binaries (either via install failure or because the binaries are missing)
Please contact us if this is the case for you Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
