Given the rapid pace of development of libvirt as well as virt-manager and no stable API I wonder if the best solution to this bug might be to backport libvirt 0.6.1 to hardy as opposed to trying to patch virt-manager. Any thoughts?
Given the rapid pace of development of libvirt as well as virt-manager and no stable API I wonder if the best solution to this bug might be to backport libvirt 0.6.1 to hardy as opposed to trying to patch virt-manager. Any thoughts?