** Summary changed: - Backport open-vm-tools version 2:13.0.0-1 to plucky, noble, jammy + Backport open-vm-tools version 2:13.0.0-1 to plucky, noble
** Description changed: [Impact] * Without SRUing the never version users get issues running on more recent hypervisors. * This is not backporting a single fix, nor an MRE, but backporting the version of a latter Ubuntu release for platform enablement. * See https://documentation.ubuntu.com/sru/en/latest/reference/exception- OpenVMTools-Updates for more details * Changes from version: - 2:12.5.0-1 in Plucky: - 2:12.4.5-1 in Noble: - - 2:12.3.5-3 in Jammy: * Upstream release notes for the latest version: https://github.com/vmware/open-vm-tools/blob/stable-13.0.0/ReleaseNotes.md [Test Plan] See https://documentation.ubuntu.com/sru/en/latest/reference/exception- OpenVMTools-Updates/#verification * VMWare QA Team does the qualification of these uploads as we don't have - a matrix of Host versions for that around. Once made available in -proposed - and passing build time tests the Server team will reach out to VMware to to - run their verification harness against the new build and confirming that - with a statement on the bug. + a matrix of Host versions for that around. Once made available in -proposed + and passing build time tests the Server team will reach out to VMware to to + run their verification harness against the new build and confirming that + with a statement on the bug. * As an additional safety net we want to keep this in -proposed longer - than usual, suggesting >=14 days. + than usual, suggesting >=14 days. The package builds are in <TBD> Results of local autopkgtest runs are <TBD> [ Where problems could occur ] * It is a full new version which might contain new issues, but also - new fixes and we've had cases where this brought CVE coverage before - we needed backports for those. Still, worst you'd expect all that you - expect on a release-upgrade like deprecated features gone, handling - configuration differently or in general behaving differently by adding - (even wanted) new features. - Gladly the toolset has proven to be very stable at all that. + new fixes and we've had cases where this brought CVE coverage before + we needed backports for those. Still, worst you'd expect all that you + expect on a release-upgrade like deprecated features gone, handling + configuration differently or in general behaving differently by adding + (even wanted) new features. + Gladly the toolset has proven to be very stable at all that. [Other Info] * Mostly regressions seen on those backports would be the same as seen on - an upgrade to a new Ubuntu version with the new version of open-vm-tools. - Hence, unless other reasons like a former delay or an urgent need - cause a change, we try to do this early in the Ubuntu cycle backporting - the version released just recently. - For example the version that will go out with 24.10 is expected to be - proposed for 24.04 shortly, but after 24.10 is released so that we'd have - a chance to pick those regression reports up. - - This is a recurring effort. For reference, previous previous Open VM Tools SRU backports: + an upgrade to a new Ubuntu version with the new version of open-vm-tools. + Hence, unless other reasons like a former delay or an urgent need + cause a change, we try to do this early in the Ubuntu cycle backporting + the version released just recently. + For example the version that will go out with 24.10 is expected to be + proposed for 24.04 shortly, but after 24.10 is released so that we'd have + a chance to pick those regression reports up. + + This is a recurring effort. For reference, previous previous Open VM + Tools SRU backports: * <TBD> ** Changed in: open-vm-tools (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2112528 Title: Backport open-vm-tools version 2:13.0.0-1 to plucky, noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2112528/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
