Description and rationale

Debusine offers desirable features that allow Debian developers to easily build (or rebuild) Debian packages against the official distribution, or against alternate package repositories, in a variety of situations. However they will only truly benefit from those improvements if Debian switches to debusine and provides its developers with an access to it. For this to happen, debusine needs to reach feature-parity with the existing infrastructure, even for those very specific niche workflows that Debian is currently supporting.

The missing features implemented as part of this milestone enable Debian to switch to debusine and not be limited compared to what can be achieved right now with the existing production infrastructure. As another important prerequisite, the relevant Debian team is invited during development to experiment with debusine and gain confidence in its ability to meet their needs.

Developer perspective

This is about mapping, and feature-matching, the current most important use-cases of buildd in Debian. Debusine will also gain new features in terms of orchestration, accounting for the fact that a source package needs to be built on multiple architectures, and that this set of architectures varies depending on the target distribution. Deploying debusine for internal Freexian workloads serves as a real-world, production benchmark.