Hi, Guido Günther wrote (14 May 2014 15:57:27 GMT) : > On Wed, May 14, 2014 at 03:52:47PM +0200, Kwadronaut-debian wrote: >> For both me and #706196 this is sort of fixed upstream when it are local >> storage pools: >> https://git.fedorahosted.org/cgit/virt-manager.git/tree/virtinst/CloneManager.py?id=v0.10.0 >> Virt-inst is now merged in virt-manager. With attached patch (which >> comes from upstream) I'm happy.
Can you please confirm that the problem is gone with the package (based on upstream 1.0.1) that's currently in testing/sid? >> I don't know if this patch should get >> into backports or the other 2 bugs can be closed because of this and/or >> upstream changes, an explanation of bug-flow would be welcome. > Backports would mean backporting the whole virt-manager 1.0 so we can > only onsider a update via a point update. This would mean we need to > fix it in unstable first which we should do by bringing virt-manager > 1.0 into sid (currently only in experimental). I try to find the time > to finally package 1.0 (instead of a git snapshot). That's now been done, not sure what's the next thing to do here. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
