On Sun, Feb 16, 2025 at 08:38:03PM +0100, Johannes Schauer Marin Rodrigues wrote: > Hi, > > Quoting Marc Haber (2025-02-16 20:26:12) > > The way how sbuild, autopkgtest and piuparts do (not) interface with each > > other, not being able (or willing) to even share their chroot tarballs, is > > especially frustrating. There is much more than just calling each other. > > > > But autopkgtest is way worse than sbuild is. I just got started with > > sbuild before moving on to autopkgtest. > > this is a difficult problem because each of these tools has different > requirements. In a tarball for subild you usually want build-essential > installed. A tarball for autopkgtest has to to be set up by running the script > /usr/share/autopkgtest/setup-commands/setup-testbed (which installs python3, > dpkg-dev and other stuff) and a piuparts chroots should be as minimal as > possible. How would you solve this?
This is not quite true. autopkgtest-virt-unshare says this: | By default it searches for tarballs in ~/.cache/sbuild to reuse the those created for sbuild. So in some form it has to be prepared to use an sbuild-managed tarball already. And in practice, it seems to work fine for me, provided sbuild keeps its tarball around. I think a lot of people would benefit from tighter integration here, and it seems we are so close ... Chris
