** Description changed: - Hi, + + [Rationale] + virt-manager 3.2 is out for more than a year now and upstream git includes many fixes. That was brought up upstream in [1] already and the estimation is somewhere around our feature freeze [2]. But we also need time to do this in Debian and test it and so on, therefore to be transparent and prepared I wanted to file an FFe bug right away. - As there is no release yet I can't provide a diff just yet, but main [3] - vs the 3.2 tag [4] shows this and the many fixes and improvements - contained. + There was no release by upstream in time before Feature Freeze. + But now there is [3] v4.0.0 since last week. + + In addition many of the changes in there are also needed for bug 1959976 + [4] + + And finally today's virt-manager (3.2) in jammy would be an FTBFS + without some fixes that are in 4.0 (due to the much newer libvirt + version we have) - just another motivation to move to the new version. + + + + [Proposed upload] + + Since the release last week Debian packaged 4.0 (thanks). + I have test built this for jammy in a PPA [5]. + + The full diff out of that is available there [6]. + + No Delta needed - once the FFe is approved I'd sync the package. + + + + [Tests] + + The package has self tests on its own at build and autopkgtest. + On that PPA [5] I was then also running the autopkgtests which passed on all architectures [7-11] on autopkgtest infrastructure. + + There are not too many reverse dependencies that we could break, actually just cockpit-machines and image-factory (for virtinst). + The options used in image-factory (just one call to virt-install) all are still present. + The calls from cockpit-machines do proper feature checking (app.jsx) to only use what is present and it seems to be ready for the new version. + The tests it has are integration tests not run at build/autopkgtest time so I have no results of them available atm. + + Upgrade log of virt-inst can be found at [12] + Install log of virt-manager can be found at [13] + + + + [References] [1]: https://listman.redhat.com/archives/virt-tools-list/2022-January/msg00016.html [2]: https://listman.redhat.com/archives/virt-tools-list/2022-January/msg00017.html - [3]: https://github.com/virt-manager/virt-manager/commits/main - [4]: https://github.com/virt-manager/virt-manager/commit/cd788e93030a6c24934c96851b23af59c12dc2a7 + [3]: https://github.com/virt-manager/virt-manager/releases/tag/v4.0.0 + [4]: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1959976 + [5]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4802/+packages + [6]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4802/+files/virt-manager_1%3A3.2.0-3.1_1%3A4.0.0-1ubuntu1~jammyppa2.diff.gz + [7]: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ci-train-ppa-service-4802/jammy/amd64/v/virt-manager/20220310_090145_cd4f0@/log.gz + [8]: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ci-train-ppa-service-4802/jammy/arm64/v/virt-manager/20220310_090149_9209e@/log.gz + [9]: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ci-train-ppa-service-4802/jammy/armhf/v/virt-manager/20220310_085939_9209e@/log.gz + [10]: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ci-train-ppa-service-4802/jammy/ppc64el/v/virt-manager/20220310_090213_a7fb9@/log.gz + [11]: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-ci-train-ppa-service-4802/jammy/s390x/v/virt-manager/20220310_085546_00842@/log.gz + [12]: https://paste.ubuntu.com/p/2S2jmJrxQf/ + [13]: https://paste.ubuntu.com/p/xfGFwWG4gs/
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961027 Title: [FFE] merge virt-manger >3.2 for Jammy once released To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1961027/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
