Hi On Wed, Jun 12, 2019 at 05:57:00PM +0200, Ivo De Decker wrote: > If you create such a package, having a binary per architecture as you > describe, should do what you want. It can be added to the list as soon as it > is in testing.
Okay, thank you. > Also, just as a suggestion: if it is feasible, you could add an autopkgtest to > that source to build (or even test) the cloud images. That would prevent > migration to testing of packages that break your images. The code in the package is not used to actually build the images we release for Debian. We use the unreleased code from the git repository to do all the automated stuff. I'm also not sure if the Debian autopkgtest infrastructure would be able to do that and build images. The actual testing runs via the Gitlab CI.[1] Regards, Bastian [1]: https://salsa.debian.org/cloud-team/debian-cloud-images/pipelines -- Dismissed. That's a Star Fleet expression for, "Get out." -- Capt. Kathryn Janeway, Star Trek: Voyager, "The Cloud"