virt-manager

[silver.bullet at zoho.com]

On Sat, 29 Aug 2015 09:40:38 +0200, Petter Adsen wrote:
>Does anyone know why the version of virt-manager in vivid and wily is
>still at 1.0.1?

Because Vivid already is released.

Because Wily follows Debian and a newer release was accepted this month
for experimental and unstable.
https://tracker.debian.org/pkg/virt-manager

>Also, has anyone tried to do a manual upgrade from the sources
>available at virt-manager.org on vivid? I'm wondering if there is a
>specific reason that we are still at 1.0.1, and if an upgrade to 1.2.1
>could/would break something?

Take a look if something .1 depends on a dedicated version of
virt-manager and 2. if virt-manager requires dedicated versions that
are or are not provided by Vivid or Wily.

For Wily library releases might change, so if you successfully build
for Wily, you might need to recompile against changing releases of
libraries. However, I don't know what "Beta 1 Freeze" exactly is for,
https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule.

I don't know why you expect a new release for Vivid, since it already
was released, but assumed you successfully compile virt-manager for
Vivid, then you unlikely need to recompile it, because there won't be
release upgrades for packages,
https://wiki.ubuntu.com/VividVervet/ReleaseSchedule.

If you build a package or packages, e.g. by using the Ubuntu source
package and replacing the old with the new upstream source code, then
there is no risk. It works or don't work and if it doesn't work, then
simply replace installed new packages by the old packages provided by
the official repositories to fix a broken system.