The changelog:
#7434: Add an option to export only responses over protobuf #7430:
Reduce systemcall usage in protobuf logging
Also add a fix (pulled in from OpenBSD) for rec_control's buffer
being too small to handle output of some commands. This could be
remedied by setting net.local.dgram.maxdgram=131072 in
/etc/sysctl.conf, but this patch omits that requirement.
PR: 235392
Submitted by: maintainer
2019-02-15 dns/p5-pgeodns: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
2019-02-15 ftp/proftpd-mod_geoip: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
2019-02-15 net/go-geoip: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
2019-02-15 net/py-GeoIP: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
2019-02-15 net/pecl-geoip: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
2019-02-15 net/pen: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
2019-02-15 net/subnetcalc: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
2019-02-15 net/p5-Geo-IP: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
2019-02-15 net/rubygem-geoip: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
2019-02-15 security/sguil: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
2019-02-15 devel/go-sql-driver: Go source should not be packaged
2019-02-15 devel/geoip-java: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
2019-02-15 dns/go-geodns: Uses legacy GeoIP 1 format which no longer works; switch to GeoIP 2 where possible
- New indexer 'response_time'
- Support for MaxMind DB (GeoIP2)
- Update 'pcap_layers' with fixes for 'scan-build' warnings
- Fix port in debug output of DNS message
Changes made in addition to the PR supplied patch:
- The port had USES=shebangfix but none of the SHEBANG_ variables
were set; replace the cron_upload-prep.pl patch with a working
shebangfix setup and then use REINPLACE_CMD to adjust the conf
path in upload-prep.pl
- While we're here use REINPLACE_CMD to obey PREFIX in other
files
PR: 235711
Submitted by: Leo Vandewoestijne (maintainer)
Reviewed by: ler (mentor)
Approved by: ler (mentor)
Differential Revision: https://reviews.freebsd.org/D19187
Flamethrower is a small, fast, configurable tool for functional
testing, benchmarking, and stress testing DNS servers and networks.
It supports IPv4, IPv6, UDP and TCP, and has a modular system for
generating queries used in the tests.
It was built as an alternative to dnsperf, and many of the command
line options are compatible.
WWW: https://github.com/DNS-OARC/flamethrower
PR: 235521
Submitted by: Leo Vandewoestijne <freebsd@dns.company>
If required upgraded version to work correctly with rails50.
Fixed some cosmetic issue to make portlint happy.
Reviewed by: sunpoet
Differential Revision: https://reviews.freebsd.org/D18957
- This keeps the port name aligned with the project name
Approved by: araujo (mentor), miwi (mentor)
Differential Revision: https://reviews.freebsd.org/D18959
a symbol matches multiple clauses the last one takes precedence. If the
catch-all is last it captures everything. In the case of Qt5 libraries
this caused all symbols to have a Qt_5 label while some should have
Qt_5_PRIVATE_API. This only affects lld because GNU ld always gives the
catch-all lowest priority.
Older versions of Qt5Webengine exported some memory allocation symbols from
the bundled Chromium. Version 5.9 stopped exporting these [1] but the
symbols were kept as weak wrappers for the standard allocation functions to
maintain binary compatibility. [2][3] The problem is that the call to the
standard function in these weak wrappers is only resolved to the standard
function if there's a call to this standard function in other parts of
Qt5Webengine, because only then is there a non-weak symbol that takes
precedence over the weak one. If there's no such non-weak symbol the call
in the weak wrapper resolves to the weak wrapper itself creating an infinite
call loop that overflows the stack and causes a crash. Some of the
allocation functions are variants of C++ new and delete and it probably
depends on the compiler whether these variants are used in other parts of
Qt5Webengine.
Remove the weak wrappers (make them Linux specific). This isn't binary
compatible but we are already breaking that with the changes to the symbol
versions.
[1] 5c2cbfccf9
[2] 2ed5054e3a
[3] 009f5ebb4b
Bump all ports that depend on Qt5.
PR: 234070
Exp-run by: antoine
Approved by: kde (adridg)
While here, patch init script to support automatically determining
config type
PR: 234751
Submitted by: Leo Vandewoestijne <freebsd@dns.company> (maintainer)
