is there any particular reason (apart from lack of time, obviously), why virt-manager is still at version 1.0.1, while upstream is at 1.1.0?
openSUSE 13.2 pulls from Factory for updated packages. We want to keep os13.2 with version 1.0.1 (same version found on the just released SLES 12).
When Gold Master is cut for 13.2 this week (Oct 30th) I will be push out the 1.1.0 virt-manager to the Virtualization repo and it can then be submitted to Factory.
I tried to get a working package in my home:-project (https://build.opensuse.org/project/show/home:ojkastl_buildservice:Virt-Mana ger), but I had to disable all but one of the many (200?) patches, because otherwise the build failed due to patches being not applicable. The packages builds, can be installed, and virt-manager launches. But I'm not sure what the package is missing. Or doing wrong.
I have it cleaned up and working and will make it available this week.
Are these patches included upstream? Who knows what these patches do? If it was just one or two, I'd try to figure it out myself, but the spec contains Patch1 to Patch167...
Virt-manager 1.0.1 contains 93 patches. 50 of the patches are upstream bug fix patches contained in 1.1.0 and newer. The remaining 43 are a mix of platform specific patches and some patches that need to be pushed upstream but have not yet been. The 'Patch 167' is because there is unused space between upstream and local patches in the spec file.