Changes:
- http://xmlgraphics.apache.org/fop/2.1/releaseNotes_2.1.html
Add PreloaderRawPNG to handle images ImageIO cant
Support Barcode4J page number
Support CMYK JPEG in AFP
Support IPD change on last page
Support PDF/UA
Support TrueType fonts in PCL
Support TrueType fonts in AFP
Support for PDF/A-3
PR: 209023
Submitted by: delphij
Approved by: geoff@sea-incorporated.com (maintainer)
This is just to support the initial v5 firmware for one of the PHY-N
NICs I'm going to do some development.
It only pulls out the specific v5 mimo firmware for the BCM4312 NIC
I am playing with; I'm adding it so we at least have the framework
to pull things out of the v5 firmware.
The existing NICs still use v4 firmware and I don't plan on changing
that for some time as bwn(4) doesn't yet support the newer firmware API
and descriptor layouts.
This patch is cherry-picked from 4 different PRs and one upstream bug report [1]
Changes are:
- fix build and runtime (based on [1]). I also tried patches and solutions from
PR's, but they didn't worked for some reason
- update to 1.6.4
- convert to options helpers and add other simplifications to Makefile
- sync installed files with Makefile, bundled into distribution
- add upstream patch to fix some GTK3 warnings
This was tested both at build and runtime with both GTK versions.
Also HTML5 video playback was tested - there was a report that it doesn't work.
[1] https://github.com/conformal/xombrero/issues/131
PR: 192779 203939 205646 209301
Submitted by: various persons
Changes:
- ACE_SSL_Context::set_mode() can no longer be used to select a specific
SSL/TLS protocol version, use ACE_SSL_Context::filter_versions() for that.
This follows general advice by the OpenSSL project to go through
SSL_CTX_set_options() to limit the list of protocols available. The purpose
of ACE_SSL_Context::set_mode() is now limited to explicitly restricting
behaviour to client or server (defaults to both).
- Improve Oracle Studio support
- CIAO and DAnCE are forked to their own github repositories
and are not part anymore of the ACE+TAO release packages
- Fixed several Coverity reported issues
- Added ACE configuration for FACE safety profiles (see config-face-safety.h).
FACE, or Future Airborne Capability Environment http://www.opengroup.org/face,
specifies a restricted subset of OS functions and rules for controlling
dynamic memory allocation. When built in this configuration on a platform
that supports it, ACE conforms to the FACE requirements.
- ACE uses new netdb.h functions (getaddrinfo/getnameinfo) if they are
available, in place of deprecated functions (gethostbyname/addr).
PR: 209292
Submitted by: tkato432@yahoo.com
Changes:
- Complete refactor of the package extraction:
* safer: ensure that only what is in the plist is actually extracted
* ensure the package can be properly on the filesystem before actually
replacing the files
* move atomicity to the package level meaning that in case of failure only
the non upgraded packages has to be proceed not the entire upgrade process
* in case of upgrade only extract the files that are unchanged
- Now pre install script failure can properly be catched and stoping the onging
process (at last!).
- New mechanism in the library events to allow frontend to know what they should
run in case of interruption
- handle ^C proprely and cleanup ongoing procedure
- lots of fixes of bugs reported by coverity
- finish implementation of the 'vital' feature
TFTP is a class implementing a simple
TFTP client in Perl as described in RFC783.
WWW: http://search.cpan.org/dist/TFTP/
PR: 209254
Submitted by: Rihaz Jerrin <rihaz.jerrin@gmail.com>
This release fix targets stability issues which have had a history and
have been hard to reproduce. Issues that have been reported over the
past half year have been fixed that may have even come up earlier as
rare occasions.
Stability should be improved, running OpenDNSSEC as a long term service.
Changes in TTL in the input zone that seem not to be propagated,
notifies to slaves under heavy zone activity load that where not handled
properly and could lead to assertions.
NSEC3PARAM that would appear duplicate in the resulting zone, and
crashes in the signer daemon in seldom race conditions or re-opening due
to a HSM reset.
No migration steps needed when upgrading from OpenDNSSEC 1.4.9.
Also have a look at our OpenDNSSEC 2.0 beta release, its impending
release will help us forward with new development and signal phasing out
historic releases.
Fixes:
- SUPPORT-156 OPENDNSSEC-771: Multiple NSEC3PARAM records in signed
zone. After a resalt the signer would fail to remove the old
NSEC3PARAM RR until a manual resign or incoming transfer.
Old NSEC3PARAMS are removed when inserting a new record, even if
they look the same.
- OPENDNSSEC-725: Signer did not properly handle new update while still
distributing notifies to slaves.
An AXFR disconnect looked not to be handled gracefully.
- SUPPORT-171: Signer would sometimes hit an assertion using DNS output
adapter when .ixfr was missing or corrupt but .backup file available.
- Above two issues also in part addresses problems with seemingly
corrected backup files (SOA serial). Also an crash on badly
configured DNS output adapters is averted.
- The signer daemon will now refuse to start when failed to open a
listen socket for DNS handling.
- OPENDNSSEC-478,750,581 and 582 and SUPPORT-88:
Segmentation fault in signer daemon when opening and closing HSM
multiple times. Also addresses other concurrency access by avoiding
a common context to the HSM (a.k.a. NULL context).
- OPENDNSSEC-798: Improper use of key handles across hsm reopen,
causing keys not to be available after a re-open.
- SUPPORT-186: IXFR disregards TTL changes, when only TTL of an RR is
changed. TTL changes should be treated like any other changes to
records.
- When OpenDNSSEC now overrides a TTL value, this is now reported in
the log files.
PR: 209261
Submitted by: jaap@NLnetLabs.nl (mainainer)
New port: www/node5, to ease migration from node-5.x to node-6.x
This new major version of Node.js delivers significant improvements
in performance, reliability, usability and security. Module loading
is nearly four times faster than in Node.js v4, tests and documentation
have seen significant improvements, usability of the Buffer and
File System APIs have been improved, and Node.js now supports 93%
of ES6 language features, thanks to V8 version 5.0.
The full release announcement can be read here:
https://nodejs.org/en/blog/release/v6.0.0/
The full changelog is available on Github:
ce3e3c5fe1
For node5:
node.js v5.x will only be supported for a few months to give people
time to move to v6. This new port is marked as deprecated with an
expiration date of July 1, allowing all of May and June to transition.
See https://nodejs.org/en/blog/release/v6.0.0/#what-about-node-js-v5
PR: 209215, 209216
Submitted by: Bradley T. Hughes <bradleythughes@fastmail.fm> (maintainer)
Upstream's CHANGELOG since test12:
* Check return-code of inet_pton() when parsing dhcp-option. Bad
addresses could fail to generate errors and result in garbage
dhcp-options being sent. Thanks to Marc Branchaud for spotting this.
* Fix wrong value for EDNS UDP packet size when using --servers-file to
define upstream DNS servers. Thanks to Scott Bonar for the bug report.
