[Bug 1779757] Re: Ubuntu 18.04 installer failure related time synchronization issues on a DELL server

2018-12-27 Thread Evade Flow
Adding this comment as a Note to Self, for future reference. I just had
to reinstall Ubuntu 18.04 on the same server. This time, after setting
the (Linux) system time using the `date` command, I then ran:

```
$ sudo hwclock --systohc
```

so that my local change would 'back-propagate' to the H/W clock.

I'm mentioning this because my previous comment implied such a thing was
impossible, due to the BIOS being password-protected with a
(lost/unknown) password. But 10 seconds of Googling cleared up that
misconception. And—if you find yourself in this situation—it really
doesn't make sense to NOT set the H/W clock, too...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779757

Title:
  Ubuntu 18.04 installer failure related time synchronization issues on
  a DELL server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1779757/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1779757] Re: Ubuntu 18.04 installer failure related time synchronization issues on a DELL server

2018-11-21 Thread Evade Flow
I just encountered this same problem while trying to install Ubuntu
18.04 on a server I inherited from another team. Unfortunately, its BIOS
is password-protected and nobody knows the password, so... I had to find
a different workaround. It turns out that—instead of changing the BIOS
to store time in UTC—you can just change the system time to the
(correct) UTC time.

To do this, I just hit CTRL + ALT + F2 near the beginning of the
installation to bring up a terminal prompt, and then ran:

```
$ date
Wed Nov 21 11:36:20 UTC 2018
```

Note that it was *not* 11:36 am in Greenwich when I ran this, it was
11:36 am in Detroit(!) So I simply advanced the system time 5 hours by
running:

```
$ sudo date --utc --set "Wed Nov 21 16:37:00 UTC 2018"
```

This was enough to trick the installer into thinking that the system
time was correct, I guess, because the installation completed without a
hitch after that. (I just fixed the system time manually afterwards...)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779757

Title:
  Ubuntu 18.04 installer failure related time synchronization issues on
  a DELL server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1779757/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

2018-05-09 Thread evade
Thank you all for your help!
I'll get this version and test as soon as I'm able.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/xenial-backports/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

2018-03-22 Thread evade
Thank you all for your work on this!

Christian, my original bug (which this came out of) was about needing
updates for both open-vmtools AND the open-vm-tools-desktop package.  I
understand that the open-vm-tools-desktop packages needs to be updated
in step with OVT.  Is it being addressed please?

Thank you

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/xenial-backports/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

2018-02-18 Thread evade
Hi Emily,

I'm sorry, I posted my previous message in a hurry without checking out
what the vulnerabilities involved.

Thanks for your response and the CVE link for open-vm-tools.  That's
helpful!

Can you please tell me the URL for the companion open-vm-tools-desktop
package?  It wasn't obvious.


Although this bug has been turned in to one about a specific package in Xenial, 
I see this as a bigger issue for all LTS releases.  If an LTS release won't be 
patched to resolve a low priority vulnerability, what level of vulnerability 
will trigger a patch?

If such a patch is required, will the maintainer(s) attempt to write a
mitigation or back-port a fix, or will they upgrade these packages in
the process anyway?

Unlike many packages used in an LTS, Open VM Tools does not have a long-
term stable release, it's always moving forward.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/xenial-backports/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

2018-02-15 Thread evade
Update: There are security vulnerabilities in the current version OVT
10.0.7.  Can you please update this ticket appropriately?


I don't yet know where the CVE's are publicly published but VMware support tell 
me:

"
Later releases of VMware Tools specifically 10.0.9 for CVE listed in VMSA - 
VMSA-2017-0013 and 10.2.0 has fixes for CVE Listed in VMSA - VMSA-2018-0003
"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/xenial-backports/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

2018-02-15 Thread evade
PS: IMO this ticket should address the issue of rebasing OVT across LTS
releases, not just backporting one package from bionic to xenial.

We need to rely on the latest stable OVT being available in all LTS
releases when we upgrade to 18.04 later this year.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/xenial-backports/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

2018-02-15 Thread evade
Hi,

VMware Tools Product Management Team (indirectly) responded to me.  They
are also disappointed that Canonical is not rebasing open-vm-tools for
LTS releases.  (I too would suggest it is in Canonical's interest to
keep open-vm-tools updated for LTS releases)

I don't know what discussions you folks are having internally, but what
happened to the response Steve Langasek made above (#6)?


Also, I wonder if your expectation of them testing Ubuntu is a bit
unrealistic.

Perhaps a compromise might be reached between the two organisations where they 
assist you to set up automated testing?
Perhaps they might at least provide you some cloud instances on their 
Hypervisors so you don't have to bear the hardware/compute cost?


Thanks again!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Please backport open-vm-tools 2:10.2.0-3 (main) from bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/xenial-backports/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-02-14 Thread evade
I've had an unofficial response that VMware will continue to include
Xenial in the supported OSes list for ESXi if VMware tools is updated.
However I'm waiting for the support person to get an official statement,
which I hope I can quote for you.

They're still talking internally

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-02-08 Thread evade
Thank you again for your help.

I'm very disappointed by the overall response to this issue. If you've
already contacted the VMware staffers working on the GitHub repo, then I
wouldn't expect much from the business critical support ticket I've
raised.

We need to know that the distros we use will maintain packages necessary
for integration.  I imagine there are few in the community using VMware
(I use KVM when I have a choice) who are so dependent on running the
latest ESXi release.

If you could please get this to compile that would be very helpful.  At
this stage I'd consider using a test version in production!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-02-06 Thread evade
It's take a few days to get through some internal delays about raising
the ticket.  It should be acted on soon, although as I said before I'm
unsure if it will get the right result.

Have you tried to contact the VMware people who maintain the open-vm-tools repo 
in Github by any chance?  I wonder if that might be a better way to get to the 
right people.
At least you could ask them about the build problem?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-01-28 Thread evade
Thanks again.  It will be a few days until I'm able to do it, but I will
raise a job and request assistance from VMware.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-01-16 Thread evade
Sorry to hear that the build is messy.

Thanks for putting the time in that you have.  I've got plenty of other
things to do so I'm just checking every few days for the build to
succeed.

Would this be much easier if the new packages were in backports only?  In 
hindsight that is OK with me.
If so does it mean the priority of building new releases of these packages 
would also be lower?  This wouldn't be ideal, since we'll need the packages in 
a timely fashion.  (I'm also thinking ahead of when we move to the 2018 LTS 
release)


Could you please explain what you would like me to ask VMware to do?

As much as we'd both like it, I highly doubt they would be willing to
directly maintain a package of the software they provide for any linux
distro.  They do say that they will provide "assistance" but whatever I
ask will need to be more specific.

Thanks again!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-01-15 Thread evade
Thank you again.

If you have something specific you'd like VMware to act on, I can raise
a support ticket with them but it will take a few days before there's
any chance of action.  I'm not sure I can get much traction, but it's
worth a try.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-01-11 Thread evade
Hello Christian,
Thank you for your work on this!  Sorry to hear about build problem.  I hope 
it's not difficult to resolve.  I am looking forward to trying this.

I do not feel this  is a "comfort feature" but instead a compatibility
requirement for Xenial to be supported on the latest ESXi 6.5 update(s).
If there are any problems on our Ubuntu VMs and I raise a support ticket
with VMware, they will insist we update VMware tools before working
further.  I also have a specific problem I mentioned in the original
post, but I won't know the impact on that until I can try an updated
version.


The VMware article you linked is out of date.  Note that even though the whole 
page was updated on May 30th 2017, if you read the "Update History" section, 
the actual content changed last in December 2015.

The advice I've read from VMware [1] is to always use a vendor's open-vm-tools 
package.
That advice is linked from their first announcement of planning to release 
Open-VM-tools [2].  Apparently the same advice is also displayed if you try to 
install VMware Tools directly from ESXi [3]!

I briefly tried to compile the open-vm-tools package from VMWare's
github page, but it failed.  I'm a sysadmin responsible for multiple
systems aside from these Ubuntu desktops.  As soon as I recognized that
I needed an updated open-vm-tools package I knew either I'd be
maintaining the package for our Ubuntu systems forever, or I could ask
the distribution to update this vendor-required component.  I cannot be
the only person affected by this [4]!

Thank you again.


[1]: https://kb.vmware.com/s/article/2073803 (VMware support policy section)
[2]: 
https://blogs.vmware.com/vsphere/2015/09/open-vm-tools-ovt-the-future-of-vmware-tools-for-linux.html
[3]: https://www.thomas-krenn.com/en/wiki/VMware_Tools_or_open-vm-tools (VMware 
Tools section)
[3]: https://communities.vmware.com/thread/547675

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-01-09 Thread evade
Thank you very much!
I will try the package from your ppa as soon as I'm able.

Please note that the related open-vm-tools-desktop package also needs to be 
kept at the same version as open-vm-tools.  As I mentioned we're using VMware's 
"Horizon View" product so I require this also.
Do I need to raise a bug against that package also?


I linked open-vm-tools version 10.2.0 as it is the stable latest available.  My 
thinking is that if an update is necessary (and with the testing that involves) 
why not go to the latest now?!


Could you please clarify this:
"
The maintainer scripts have not a lot (actually none) version dependent special 
cases that sometimes wreaking havok for such backports.
"
as I don't understand.  The statement seems to contradict itself.

Thank you again!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-01-07 Thread evade
Also, I hate to burden you more, but VMware tools seems to be updated
every 3/4 months in line with ESXi patches.  IMO it should be updated at
least quarterly.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-01-07 Thread evade
Thank you both for your responses!

What needs to happen for a "platform enablement" bugfix?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-01-05 Thread evade
Hello Christian,

Thank you for your fast response and the explanation.


Despite the difference in release time, I don't see this as a major upgrade but 
instead a required bugfix to maintain compatibility with another vendor's 
products.


I work in an enterprise environment and am working on a project building a new 
network.

We specifically chose an LTS release for our virtual developer desktops
because we didn't want developers to have to upgrade their desktops on
the normal release cycle.

Sadly we are stuck with VMware's Horizon View (which I wouldn't
recommend).  As Horizon View's Linux support is still maturing and we're
still in the build phase of our Network, we've had to keep up with the
latest version of that product.  (For example, the latest version
allowed us to offer KDE instead of only a GNOME desktop!)

We have to patch VMware software, especially including the ESXi
hypervisors for security updates.  However VMware don't offer security-
only patches, only whole updates.

We're working with a whole matrix of software which we've learned the
hard way has to be kept on equal supported versions.  Also, as I
mentioned previously, we've had experience with out of date VMware tools
causing difficult to diagnose problems (like with the virtual NIC
driver, for example).

I raised this ticket because a horrid combination of old VMware tools,
NVIDIA proprietary graphics driver (Tesla acceleration is required for
the number of monitors used) and VMware's Horizon view agent is causing
desktop sessions to crash regularly.  I've updated all the other
software, only VMware tools is now old.

(I'm not convinced that older versions of VMware tools are more "stable"
anyway, just that their problems are more likely known!)


I recognise the situation might be very different, but as an example, Red Hat 
provide the latest stable open-vm-tools and open-vm-tools-desktop packages for 
RHEL even though RHEL has a much older kernel and (many) older packages than 
16.04.  (We do of course pay them well for their support though)


I'll ask my project manager about investing time in the Backport Process.  I'm 
afraid I have 0 personal time which I could invest in this.


Thanks for your time!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-01-04 Thread evade
I can't find any security bugs fixed, but there are good fixes like
this:

"Kernel modules were not upgraded after upgrading OSPs using the recommended 
procedure 
The package vmware-tools-esx-kmods is a meta package that depends on the kernel 
module package. Installing it with yum/apt/zypper gets the kmod packages. An 
upgrade of vmware-tools-esx-kmods might not automatically upgrade the kmod 
packages because the dependency was not versioned.
This issue is fixed in this release."

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] Re: Package two years out of date

2018-01-04 Thread evade
PS: There are multiple significant bugfixes for Linux in the updated
version.

Here are the release notes, I believe the latest does not include the
fixes from previous versions (all these releases are newer than the
Xenial version)

https://docs.vmware.com/en/VMware-Tools/10.2/rn/vmware-tools-1020-release-notes.html
https://docs.vmware.com/en/VMware-Tools/10.1/rn/vmware-tools-1015-release-notes.html
https://docs.vmware.com/en/VMware-Tools/10.1/rn/vmware-tools-1010-release-notes.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741390] [NEW] Package two years out of date

2018-01-04 Thread evade
Public bug reported:

The latest Xenial open-vm-tools package is almost two years out of date.

I'm building Xenial systems in an up-to-date VMware environment and I
need VMware tools updated to the latest stable version.  We have
experienced problems with VMware products when different components were
mismatched.

We also require open-vm-tools-desktop updated as a bug in either it or
this package are causing problems with a VMware's Horizon view virtual
desktop environment.


Version 10.0.7 of open-vm-tools was first released in February 2016.  The 
current stable is 10.2.0 released in December last year.

See: https://github.com/vmware/open-vm-tools
And: https://github.com/vmware/open-vm-tools/releases/tag/stable-10.2.0


Could these packages please be updated for Xenial?  We're relying on them.

Thank you!

** Affects: open-vm-tools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741390

Title:
  Package two years out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1741390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs