net/tigervnc*: Update to 1.16.2 Changes: https://github.com/TigerVNC/tigervnc/releases/tag/v1.16.1 Changes: https://github.com/TigerVNC/tigervnc/releases/tag/v1.16.27e05dc92d3
Port details
net/tigervnc-viewer1.16.2_1
TigerVNC Viewer
- Maintainer
- meta@FreeBSD.org
- Packages
- tigervnc-viewer 1.16.2_1
- Upstream
- up to date
- CPE
tigervnc:tigervncfrom the port- WWW
- https://tigervnc.org/
- Links
- cgit · VuXML
Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE
None. There is no CVE without a VuXML entry for this version.
VuXML only (0) · listed, port not fixed yet
None.
pkg audit reports nothing for this version.Fixed (0)
No VuXML entries for this package.
Commits (27)
net/tigervnc-viewer: Explicitly enable H.264 decoder not to rely on autodetect. It is enabled via autodetect by ffmpeg dependency though.461975fd20
net/tigervnc*: Update to 1.16.0 It now depends on GNU make (abspath). While here cleanup Xorg configure arguments. Changes: https://github.com/TigerVNC/tigervnc/releases/tag/v1.16.035f59fb7e6
multimedia/ffmpeg: bump revision to chase lib version change18ea9c7108
graphics/ImageMagicks*: bump dependent ports9a9c1ba205
net/tigervnc-*: Update to 1.14.1 Changes: https://github.com/TigerVNC/tigervnc/releases/tag/v1.14.115992b14fc
net/tigervnc-viewer: Apply a fix for ZRLE exception Reported by: Keith White <Keith.White@uottawa.ca> Obtained from: https://github.com/TigerVNC/tigervnc/issues/1809ca5d9506c4
net/tigervnc-*: Update to 1.14.0 Changes: https://github.com/TigerVNC/tigervnc/releases/tag/v1.14.0 A prominent change that affects FreeBSD port is: * The viewers and servers now follow the XDG Base Directory Specification, like "~/.config", for storing files in the home directory. Existing users will continue using the legacy "~/.vnc" directory, but new users will get the XDG directories. While here, - Adjust BUILD_DEPENDS and LIB_DEPENDS reported in stage-qa3d472dc668
*/*: Bump jpeg-turbo users treewide New major version 3.0.0664a2fa1e5
Mk/Uses/magick.mk: Bump all consumers Bump all consumers of ImageMagick ports after flavorizing them. Approved by: tcberner (mentor, implicit)a6bb2f8c5e
net/tigervnc-{server,viewer,viewer-java}: Update to 1.13.0
Changes: https://github.com/TigerVNC/tigervnc/releases/tag/v1.13.0
Sponsored by: Miracle Linuxae256a0661Remove WWW entries moved into port Makefiles Commit b7f05445c00f has added WWW entries to port Makefiles based on WWW: lines in pkg-descr files. This commit removes the WWW: lines of moved-over URLs from these pkg-descr files. Approved by: portmgr (tcberner)fb16dfecae
Add WWW entries to port Makefiles It has been common practice to have one or more URLs at the end of the ports' pkg-descr files, one per line and prefixed with "WWW:". These URLs should point at a project website or other relevant resources. Access to these URLs required processing of the pkg-descr files, and they have often become stale over time. If more than one such URL was present in a pkg-descr file, only the first one was tarnsfered into the port INDEX, but for many ports only the last line did contain the port specific URL to further information. There have been several proposals to make a project URL available as a macro in the ports' Makefiles, over time. This commit implements such a proposal and moves one of the WWW: entries of each pkg-descr file into the respective port's Makefile. A heuristic attempts to identify the most relevant URL in case there is more than one WWW: entry in some pkg-descr file. URLs that are not moved into the Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr files in order to preserve them. There are 1256 ports that had no WWW: entries in pkg-descr files. These ports will not be touched in this commit. The portlint port has been adjusted to expect a WWW entry in each port Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as deprecated. Approved by: portmgr (tcberner)b7f05445c0
net/tigervnc-viewer: fix pkg-plist use share/man Approved by: portmgr (blanket)a9eeb18948
framework: Add new USES 'magick' for graphics/ImageMagick*
A new USES has been added to depend on ImageMagick.
USES=magick
adds a LIB_DEPENDS on graphics/ImageMagick${IMAGEMAGICK_DEFAULT}.
If a specific version is required, use for example
USES=magick:6 resp. USES=magick:7
If only a build, run or test is required, use for example
USES=magick:build resp. USES=magick:6,build,test
If a dependency on the nox11 flavor is required, use for example
USES=magick:nox11 resp. USES=magick:7,nox11,run,test
See magick.mk for more details on the available flags.
The tree has been completely converted to make use of this.
Approved by: bapt
Differential Revision: https://reviews.freebsd.org/D3275445526ecbeenet/tigervnc-{server,viewer}: Update to version 1.12.0
PR: 259966
Approved by: meta16464822d1INSTALLS_ICONS: retire the macro and rework the related dependencies While here, make sure gtk-update-icon-cache is only on run dependency where added as a dependency Enforce gtk3 to depend on gtk-update-icon-cache (previously it was inheriting the dependency)2c672a4de9
One more small cleanup, forgotten yesterday. Reported by: lwhsucf118ccf87
Remove # $FreeBSD$ from Makefiles.305f148f48
net/tigervnc-{server,viewer}:
Relnotes: https://github.com/TigerVNC/tigervnc/releases/tag/v1.11.0
Sponsored by: HAW Internationalfc8f1a8f11net/tigervnc-viewer: Fix pkg-descr was incorrectly taken from the master port. PR: 248226 Reported by: serpent7776@gmail.com Sponsored by: HAW International3d88863b58
net/tigervnc-{server,viewer}: Update to 1.10.1
This is a security release to fix a number of issues that were found by
Kaspersky Lab. These issues affect both the client and server and could
theoretically allow an malicious peer to take control over the software
on the other side.
No working exploit is known at this time, and the issues require the
peer to first be authenticated. We still urge users to upgrade when
possible.
Relnotes: https://github.com/TigerVNC/tigervnc/releases/tag/v1.10.1
Sponsored by: HAW International9ce84f7e52net/tigervnc-{server,viewer}: Update to 1.10.0
Lots of changes have been made since the last release, but the highlights are:
* The clipboard now supports full Unicode in the native viewer, WinVNC and Xvnc/libvnc.so
* The native client will now respect the system trust store when verifying server certificates
* Improved compatibility with VMware's VNC server
* Improved compatibility with some input methods on macOS
* Improvements to the automatic "repair" of JPEG artefacts
* Better handling of the Alt keys in some corner cases
* The Java web server has been removed as applets are no longer support by most browsers
* x0vncserver can now be configured to only allow local connections
* x0vncserver has received fixes for when only part of the display is shared
* Polling is now default in WinVNC as that works better for most
Relnotes: https://github.com/TigerVNC/tigervnc/releases/tag/v1.10.0
Sponsored by: HAW International, Inc.be72a54dbbAdd USES=xorg USES=gl, ports categories n Add USES=xorg and USES=gl to ports in categories starting with 'n'. While here, try to sprinkle other USES (mostly gnome and sdl) as needed.897ad0b36e
net/tigervnc: Remove non-essential meta port Reported by: hrs [1] [1] https://lists.freebsd.org/pipermail/svn-ports-all/2019-April/212975.htmlc3426fa8c4
Fix the issue tigervnc-server and -viewer cannot be installed together
when DOCS=on because both ports install LICENSE_FILE into the same place.
Also, following changes are made.
net/tigervnc-{server,viewer}:
- bump PORTREVISION due to plist & dependency change
- do build tests, it introduces unnecessary dependencies on fltk
net/tigervnc-server:
- add missing dependency on devel/m4
- remove unnecessary dependency on x11-toolkits/fltk
MFH: 2019Q2843cfb439cnet/tigervnc: separate port into -server -and -viewer since usually people want to install either server or client on the same box. Formerly, net/tigervnc had options to build & install vncviewer(client) but vncviewer could not be installed alone. Server components was necessary. Now TigerVNC server and viewer are completely separeted and can be installed independently. Tested by: Juan Molina Differential Revision: https://reviews.freebsd.org/D197096ccd55baec