All checksums have been double-checked against existing RMD160 and
SHA512 hashes
Not committed (merge conflicts...):
net/radsecproxy/distinfo
The following distfiles could not be fetched (fetched conditionally?):
./net/citrix_ica/distinfo citrix_ica-10.6.115659/en.linuxx86.tar.gz
./net/djbdns/distinfo dnscache-1.05-multiple-ip.patch
./net/djbdns/distinfo djbdns-1.05-test28.diff.xz
./net/djbdns/distinfo djbdns-1.05-ignoreip2.patch
./net/djbdns/distinfo djbdns-1.05-multiip.diff
./net/djbdns/distinfo djbdns-cachestats.patch
avahi 0.8 release brings a number of new features and bug fix changes
including a backward-compatible addition to the D-Bus API and the avahi-core
API.
The existing API is still fully supported however clients using the new
API will not work with older Avahi releases. The avahi-client library is not
affected. See the "API Changes" section for further details.
New Features:
- New options for filtering reflected queries between networks (reflect-filter)
- New mainloop integration for Qt5 and libevent
- docs/THREADS: Information for multi-threaded avahi-client apps
- Listen on loopback interfaces by default, allowing local-only services to be
consumed by the local machine
- New D-Bus V2 API and additions to the avahi-core API for splitting "New"
calls into "Prepare" and "Start". See "API Changes" for more details.
* Add support for binary values in TXT records in XML service files by
specifying value-format="text|binary-hex|binary-base64". If not specified,
defaults to the normal value of "text" (thus backwards compatible)
* avahi-gobject: Allow starting the client in a custom GMainContext by
passing context to ga_client_start_in_context instead of ga_client_start
(avahi-gobject minor version has been incremented)
Security Fixes:
- Drop legacy unicast queries from address not on local link which can lead to
UDP traffic amplification attacks (CVE-2017-6519)
For full details, see:
https://github.com/lathiat/avahi/blob/v0.8/docs/NEWS
pkglint -r --network --only "migrate"
As a side-effect of migrating the homepages, pkglint also fixed a few
indentations in unrelated lines. These and the new homepages have been
checked manually.
Unsorted entries in PLIST files have generated a pkglint warning for at
least 12 years. Somewhat more recently, pkglint has learned to sort
PLIST files automatically. Since pkglint 5.4.23, the sorting is only
done in obvious, simple cases. These have been applied by running:
pkglint -Cnone,PLIST -Wnone,plist-sort -r -F
