[14:38] <balloons> pitti, I lost my notes on the best way to mimic autopkgtest runs locally. I believe you recommended qemu instead of lxd for instance. Do I adt-buildvm-ubuntu-cloud, then use that image?
[14:42] <pitti> balloons: -qemu approximates best what happens in production, but if a test works in lxd or lxc, do use that of course
[14:42] <pitti> balloons: http://packaging.ubuntu.com/html/auto-pkg-test.html is the official docs
[14:42] <pitti> balloons: but I run most tests in lxd these days (man adt-virt-lxd)
[14:43] <pitti> balloons: note that there are no yakkety cloud images yet, so if you want to use qemu, you need to build a xenial image, launch that in qemu, and dist-upgrade
[14:43] <balloons> pitti, so I'm trying to debug the juju failures in yakkety, so I ran sudo adt-run juju-core --apt-pocket=proposed --- lxd lco:ubuntu/yakkety/amd64 to get around that
[14:43] <balloons> which complained about needing source uris :-)
[14:47] <balloons> so I guess either way I need to make a xenial image and upgrade it?
[14:48] <pitti> balloons: no sudo with lxd, please
[14:48] <pitti> balloons: and lco: is spelled images: now (and present by default); current manpages are adjusted to that
[14:49] <pitti> balloons: anyway, images.linuxcontainers.org don't ship deb-src indeed, so --apt-source tests don't work
[14:49] <pitti> balloons: hence adt-build-lxd
[14:49] <pitti> (which is also explained in adt-virt-lxd manpage)
[14:49] <pitti> you also want that to use your local proxy, use eatmydata, etc.
[14:55] <balloons> ack, ty pitti. You are right, it is in the manpage rather succintly.