On Mon, 07 Oct 2019 at 07:22:53 +0200, Johannes Schauer wrote:
> Specifically, currently autopkgtest is limited to providing a read-only layer
> for certain backends and its upstream has no intention of widening the scope
> of
> the software [1]. This means that to upgrade an autopkgtest backend, the user
> has to apply backend-specific actions
I think "re-bootstrap, don't upgrade" is an equally good principle for
autopkgtest and sbuild? Both will be equally susceptible to accumulating
cruft during upgrades that wouldn't have been there in a fresh debootstrap,
which is undesired if you want the invariant that you are (building|testing)
in "today's" minimal environment.
smcv
