Summary: | dev-python/libvirt-python - python3.3: ERROR: failed virDomainFSFreeze/virDomainFSThaw/virDomainGetTime | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | [OLD] Development | Assignee: | Virtualization Team <virtualization> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | mikemol |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 509858 | ||
Attachments: |
dev-python:libvirt-python-1.2.3:20140812-182224.log.gz
build-python3.3.log |
Description
Toralf Förster
2014-08-12 18:30:19 UTC
dev-python/libvirt-python-1.2.5 emerged fine at x86 Created attachment 382786 [details]
build-python3.3.log
I also hit this bug, and can confirm that installing dev-python/libvirt-python-1.2.5 works on stable amd64.
Please stabilize 1.2.5 since libvirt-1.2.5 is stabilized. (I guess the version numbers have to match?)
So, we know that libvirt-python should be the same version of installed libvirt. I'd suggest to change the r/DEPEND. What is app-virtualization/libvirt-${PV} ? *** Bug 519814 has been marked as a duplicate of this bug. *** Starting with 1.2.10, libvirt-python will (R)DEPEND on libvirt:0/${PV}. Is this issue resolved with libvirt-1.2.10-r2 and matching libvirt-python-1.2.10? If no, please reopen. |