Hi, Johannes Schauer <jo...@debian.org> writes:
> Quoting Simon McVittie (2017-08-20 01:16:12) >> On Sun, 20 Aug 2017 at 00:26:26 +0900, Johannes Schauer wrote: >> > since sbuild already supports autopkgtest as a backend (and thus also >> > autopkgtest-virt-qemu which vectis seems to be using) I'd be especially >> > interested in hearing which features are missing from sbuild that prevent >> > vectis from making use of that functionality. >> >> The reason vectis doesn't do this is a design choice, not an omission >> in sbuild. > > Thanks for your explanation! I now see how vectis is indeed doing something > that is not in the scope of sbuild itself and that vectis indeed has to be a > wrapper around sbuild and other tools. > > Though maybe it would be a good idea to add parts of your explanations from > your mail to the README.md and package description. It seems at least me and > Raphael were fooled into thinking that vectis' purpose was a different one > than > it actually is. > > Thanks for writing this! So, I take it vectis is out of the picture for the purpose of this bug. Raphaël, Benjamin, what’s the current status? It’s been quite a number of months since https://bugs.debian.org/859867#122, and I’m still very interested in having sbuild easily installable. Thanks! -- Best regards, Michael
