On Aug 21, 2015, at 04:07 PM, Alberto Milone wrote: >I can build the same code in a vivid chroot without seeing any failures. >My guess is that something else (python-apt? python-aptdaemon?) changed >in the archive.
Oh yes, they surely have. python-apt | 0.9.3.11build1 | vivid | source, amd64, arm64, armhf, i386, powerpc, ppc64el python-apt | 1.0.0~beta3.1ubuntu1 | wily | source, amd64, arm64, armhf, i386, powerpc, ppc64el python-aptdaemon | 1.1.1+bzr982-0ubuntu3 | vivid | all python-aptdaemon | 1.1.1+bzr982-0ubuntu3.1 | vivid-security | all python-aptdaemon | 1.1.1+bzr982-0ubuntu3.1 | vivid-updates | all python-aptdaemon | 1.1.1+bzr982-0ubuntu8 | wily | all -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1487223 Title: 1:0.4.7 FTBFS in wily-proposed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: This version fails to build from source in wily-proposed, although I don't understand why. Attached is the full build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1487223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp