Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#33653 - libvirt python bindings are broken in 1.0.2
Attached to Project:
Community Packages
Opened by Lars Kellogg-Stedman (larsks) - Thursday, 31 January 2013, 14:27 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 31 January 2013, 15:52 GMT
Opened by Lars Kellogg-Stedman (larsks) - Thursday, 31 January 2013, 14:27 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 31 January 2013, 15:52 GMT
|
Detailslibvirt 1.0.2 has a critical error in the python bindings that stops a variety of tools (in particular virtinst) from working correctly:
https://www.redhat.com/archives/libvir-list/2013-January/msg02157.html The libvirt maintainers suggest that distributions should apply this patch to their 1.0.2 packages. The patch will be included in the next release of libvirt, but at the moment the Python bindings are very broken. |
This task depends upon