Source: libvirt-python Version: 1.2.1-2 Severity: serious Tags: jessie sid User: [email protected] Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python2 > dh_testdir > dh_auto_configure > dh_auto_build > running build > /usr/bin/python generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml > Found 380 functions in /usr/share/libvirt/api/libvirt-api.xml > Found 0 functions in libvirt-override-api.xml > Generated 323 wrapper functions > /usr/bin/python generator.py libvirt-qemu > /usr/share/libvirt/api/libvirt-qemu-api.xml > Found 5 functions in /usr/share/libvirt/api/libvirt-qemu-api.xml > Found 0 functions in libvirt-qemu-override-api.xml > Generated 4 wrapper functions > Missing type converters: > virConnectDomainQemuMonitorEventCallback:1 > ERROR: failed virConnectDomainQemuMonitorEventRegister > error: command '/usr/bin/python' failed with exit status 1 > dh_auto_build: python setup.py build --force returned exit code 1 > make: *** [build] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/01/libvirt-python_1.2.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
