I was able once (1!) to reproduce outside of launchpad by using the
following steps to become more like launchpad:
# Prep needed packages
$ sudo apt-get install sbuild ubuntu-dev-tools
# misuse a mk-sbuild to set up all around that might be needed (despite
throwing most away afterwards)
$ SID=LP-zesty-repro
$ mk-sbuild zesty --arch amd64 --name=${SID}
# replace content with the tarball from launchpad
$ sudo rm -rf /var/lib/schroot/chroots/${SID}-amd64/*
# launchpad tells you where to get the original chroot used by LP
(https://api.launchpad.net/devel/ubuntu/zesty/amd64)
# get it and replace the local chroot content with it
$ wget
http://launchpadlibrarian.net/289945545/chroot-ubuntu-zesty-amd64.tar.bz2
$ sudo tar --directory /var/lib/schroot/chroots/${SID}-amd64/ -xzf
~/Downloads/chroot-ubuntu-zesty-amd64.tar.bz2
$ sudo mv /var/lib/schroot/chroots/${SID}-amd64/chroot-autobuild/*
/var/lib/schroot/chroots/${SID}-amd64/
$ sudo rmdir /var/lib/schroot/chroots/${SID}-amd64/chroot-autobuild
# Update to all packages and proposed as build env would
$ printf "deb http://archive.ubuntu.com/ubuntu zesty main universe\ndeb
http://archive.ubuntu.com/ubuntu zesty-security main universe\ndeb
http://archive.ubuntu.com/ubu
$ sudo sbuild-update -udcar ${SID}-amd64
# build as usual (this env sticks around so feel free to reuse)
$ DEB_BUILD_OPTIONS="parallel=4" sbuild -Ad${SID}-amd64
libvirt_2.1.0-1ubuntu10.dsc
Unfortunately that only triggered once, and retrying is hard as it either takes
quite a while (full build) or behaves slightly differently when e.g. only
running all tests but not rebuilding in the schroot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641615
Title:
FTBFS of libvirt 2.1 in zesty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1641615/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
