© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
[Impact]
* Without SRUing the never version users get issues running on more
recent hypervisors.
* This is not backporting a single fix, but the version of a latter
Ubuntu release
[Test Case]
* TL;DR is "use open-vm-tools" but that can be quite complex for the
variety of potential Host versions.
* VMWare itself took ownership of verifying these backports and will test the same bits from a PPA and the SRU for the official "ack"
* We tried upgrading and the setup that I had available, everybody that
has different setups is invited to test theirs.
* In general I recommend to give this some extra time in -proposed to see if
anybody comes up with issues on this.
[Regression Potential]
* It is a new version which might contain new issues, and other than in
most MRE cases this isn't a just a stable-release (Of courese we are
not switching major releases, but also no pure fix release).
* As agreed back when processing bug 1741390 the real verification of
open-vm-tools for having the test matrix and project ownership is on
VMWare which verified this from [1] already.
[Other Info]
* After bug 1741390 was sort of first of its kind we do this on a
once-per-cycle schedule with bug 1784638 beign the last one.
The intention is to get regular updates not only into new -dev releases
but also as SRU to the latest LTS under term [2] "Long Term Support releases
we regularly want to enable new hardware" being "virtual hardware" in
this case.
[1]: https:/
[2]: https:/
---
There is a new Upstream version available.
https:/
We left 10.3.5 some time in 19.04 to see if any issues come up, but none appeared.
So lets do the backport to the LTSes.