Log message:
Update to 10.3.0

Changelog:
Resolved Issues

    The open-vm-tools process might take a long time and consume 100% CPU of a \ 
core in a Linux OS with many IPv6 routes

    Prior to open-vm-tools 10.3.0, gathering network adapter information in a \ 
Linux guest OS with many IPv6 routes was a time-consuming process with 100% use \ 
of the CPU of a core. The exported data contained only a maximum of 100 routes. \ 
IPv4 routes took precedence over IPv6, leading to data loss in reporting IPv6 \ 
routes. If there were more than 100 IPv4 routes, IPv6 routes were not reported.

    This performance issue has been resolved in this release. The default routes \ 
gathering behavior can be overridden by configuring the values in the \ 
/etc/vmware-tools/tools.conf file:

    [guestinfo]
    max-ipv4-routes=0
    max-ipv6-routes=0

    Note: If they are not manually set, or an invalid value (over 100 or less \ 
than 0) is set, 'max-ipv4-routes' and 'max-ipv6-routes' are set to 100 by \ 
default. They can be set to 0 to disable the data collection.

    This issue is resolved in this release.

    Installation of the libvmtools package might fail the installation of VMware \ 
Tools

    When the package "libvmtools0" is installed in SUSE Linux 12 and \ 
open-vm-tools is not installed, the VMware Tools installer fails. This is done \ 
to prevent an incomplete installation. Users have to uninstall both \ 
open-vm-tools and libvmtools0 packages to install VMware Tools.

Log message:
Recursive revbump from textproc/icu-62.1

Log message:
Remove PKGREVISION after update

Log message:
Update to 10.2.5

Changelog:
open-vm-tools release 10.2.5 based on build 8068406

Resolved Issues

  * open-vm-tools 10.2.0 does not recognize UFS filesystem partitions

    open-vm-tools 10.2.0 has dropped UFS from the list of known
    file system type. As a result, the default filesystem of Solaris
    and FreeBSD is not recognized. open-vm-tools Services in the
    GuestInfo for the virtual machine do not report these filesystems.
    You might not be able to monitor the disk usage of UFS filesystems
    with vRealize Operations or vCenter Managed Object Browser.

    This issue is resolved in this release.

  * Information about non-existing device mounted to a file system
    was not reported

    Few Linux guest operating systems might have a non-existing
    device mounted to a filesystem. For example /dev/root/.
    open-vm-tools does not report this information.

    This issue is resolved in this release.

Log message:
Recursive bump for new fribidi dependency in pango.

Log message:
revbump after icu update

Log message:
Recursive bumps for fontconfig and libzip dependency changes.

Log message:
Set PKGNAME properly

Log message:
Update to 10.2.0

* Use x11/gtkmm3

Changelog:
Compatibility
  * open-vm-tools 10.2.0 is compatible with all supported versions
    of VMware vSphere ESXi 5.5 and later, VMware Workstation 14.0 and
    VMware Fusion 10.0. See VMware Compatibility Guide for more information.

  * Starting with VMware Tools version 10.2.0, Perl script based VMware
    Tools installation for FreeBSD has been discontinued. Going forward,
    FreeBSD systems are supported only through the open-vm-tools packages
    directly available from FreeBSD package repositories. FreeBSD packages
    for open-vm-tools 10.1.0 and later are available from FreeBSD package
    repositories.

Resolved Issues
  * Summary page of the VM does not list the IP address of the VMs in
    the right order

  * Guest authentication fails with a SystemError fault when the requested
    password is expired

  * The free space reported in vim.vm.GuestInfo.DiskInfo for a Linux guest
    does not match with df command in the guest

  * VMware user process might not restart after upgrades of open-vm-tools

Log message:
Revbump after textproc/icu update