QGIS 3.4 LTR, the first long-term release (LTR) of QGIS 3.
This is a major upgrade and users should consult the UPDATING entry
provided for further information on how to progress.
http://changelog.qgis.org/en/qgis/version/3.4-LTR/
PR: 233726
Submitted by: Rainer Hurling <rhurlin@gwdg.de> (maintainer)
I completely misunderstood the config file location for goaccess.conf.
The config file hasn't moved to ETCDIR, only the sample file has. The
config file is still read from PREFIX/etc.
Remove the UPDATING/pkg-message instructions about this, and install
the config file to the correct place, along with a PORTREVISION bump.
Pointy hat: adamw
With this release:
- The config file has moved from PREFIX/etc to ETCDIR
- The web assets are no longer installed separately (they
are compiled into the binary so this should not affect
end-users)
- NLS support (and OPTION) added
pkg-message and UPDATING entry added for conf file location
change.
Changes: https://goaccess.io/release-notes
PR: 234047
Approved by: maintainer (sbz)
* unbreak the port in the tier architectures
* add a bsd makefile to build and install the port instead of a gnu makefile
* run the author regression test as part of the build process
* do the proper changes to be able to disable the documentation
The new generated lib is named libtrio.so.2 ( previously misnamed libtrio.so.2.0.0)
and the libtrio.so symlink is generated. An entry in the UPDATING file was added
about those changes
Bump portrevision.
PR: 234288
Submitted by: mi
After some discussions within the x11 team, it was decided to move to a new
nomenclature for the LinuxKPI-based DRM ports that correctly reflects the
FreeBSD version the ports are for. This will also allow us to move to dedicated
branches per FreeBSD release and eases porting work.
Functionally, this commit is a no-op as we are not moving to new snapshots.
Reflect the move in UPDATING and MOVED. Users using the graphics/drm-kmod meta
port should not be affected. Direct consumers of the DRM ports shall move, as
in MOVED, as follows:
drm-stable-kmod is drm-fbsd11.2-kmod
drm-next-kmod is drm-fbsd12.0-kmod
drm-devel-kmod is drm-current-kmod
Reviewed by: zeising (x11)
Approved by: zeising (x11)
Differential Revision: https://reviews.freebsd.org/D18328
- Rename the files installed to /usr/local/etc/newsyslog.conf.d/ to end
with a '.conf' suffix.
- Add pkg-install script to automatically move any copies of the old
newsyslog file to the new location if it was modified from the default
or delete the old file if it is has not been modified.
- Add a note to UPDATING and pkg-message to warn users of this, in case
they are using provisioning/configuration management tools which need
to be modified.
Recent changes to /etc/newsyslog.conf (r340318) will only include files
from the /usr/local/etc/newsyslog.conf.d/ directory which end with
'.conf' and do not beginning with a '.' character.
Reviewed by: mandree (D17088)
Approved by: mat (maintainer)
Differential Revision: https://reviews.freebsd.org/D17089
Update to the latest major release of Node.js. Upstream has dropped
support for FreeBSD 10.x, so mark the port as BROKEN on FreeBSD 10.
Regenerate patches with `make makepatch`.
https://nodejs.org/en/blog/release/v11.0.0/
Sponsored by: Miles AS
Release notes: <https://github.com/openexr/openexr/releases/tag/v2.3.0>
Adjust LIB_DEPENDS of all ports that require ilmbase or openexr to chase
the new lower-case spelling of the name, and to omit the version from the
library name to ease future maintenance.
Bump PORTREVISION of all ports that depend on ilmbase or openexr directly,
so that they all get rebuilt on upgrades.
Add patches to graphics/ampasCTL to keep it alive, with (a) ilmbase now
that its Iex::BaseExc class is no longer derived from std::string,
details were given upstream through https://github.com/ampas/CTL/issues/71
and (b) to unwind semicolon/;-lists in cmake that stem from openexr/
ilmbase pkg-config variables.
(Note ampasCTL is unmaintained as FreeBSD port, and upstream,
and I cannot run-time test it.)
Poudriere build tests on 11.2-RELEASE-p1 amd64 of ALL ports depending
directly or indirectly on ilmbase and/or openexr have passed without
regressions. Thus invoking due diligence, I believe I have done the
equivalent of an -exp run, and do not require approval for the dependency
chases to third-party ports.
versions of our database system, including 10.5, 9.6.10, 9.5.14, 9.4.19,
9.3.24. This release fixes two security issues as well as bugs reported over
the last three months.
If you have untrusted users accessing your system and you are either running
PostgreSQL 9.5 or a newer version OR have installed the "dblink" or
"postgres_fdw" extensions, you must apply this update as soon as possible. All
other users can upgrade at the next convenient downtime.
Please note that PostgreSQL changed its versioning scheme with the release of
version 10.0, so updating to version 10.5 from any 10.x release is considered a
minor update.
The PostgreSQL Global Development Group also announces that the third beta
release of PostgreSQL 11 is now available for download. This release contains
previews of all features that will be available in the final release of
PostgreSQL 11 (though some details of the release could change before then) as
well as bug fixes that were reported during the second beta.
This release also changes the default option for the server packages to *not*
include XML support per default. If you need this, please check the XML option
knob and build the port.
Releasenotes: https://www.postgresql.org/about/news/1878/
PR: 229523, 198588
Security: 96eab874-9c79-11e8-b34b-6cc21735f730
Security: CVE-2018-10915, CVE-2018-10925
This update separates Java Gateway componentes from the Zabbix Server port,
creating an additional slave port for each version.
This way is possible to deploy a Java Gateway without the need to install
Zabbix Server components.
In the current state there wasn't an rcfile for the Java Gateway. [1]
PR: 217777
Reported by: Juan Garcia <juan@ish.com.au> [1]
Approved by: Pakhom Golynga <pg@pakhom.spb.ru> (maintainer)
