Disable-libudev as pkg-config can not find libudev.pc.
Updated graphics/fotoxx to 13.01
Update to 16.0.1

Changelog:
aria2 1.16.1
============

Release Note
------------

This release adds the ability to persist GID across sessions. The GID
will be saved with --save-session. There are several restrictions how
GID is persisted. See the manual for details. For this change, now GID
is 64 bits binary data and represented by 16 characters hex string in
RPC query.  The disk cache feature was added, which may reduce disk
activity. The console readout was redesigned. The warning displayed
when --file-allocation=falloc is used on MinGW32 build was removed as
a bug.

Changes
-------

* mingw32: Re-open files with read-only mode enabled on seeding

  On Mingw32 build, if aria2 opens file with GENERIC_WRITE access
  right, some programs cannot open the file aria2 is seeding. To avoid
  this situation, re-open files with read-only enabled when seeding is
  about to begin.

* Save gid option with --save-session option

* Added --gid option

  This option sets GID manually. aria2 identifies each download by the
  ID called GID. The GID must be hex string of 16 characters, thus
  [0-9a-zA-Z] are allowed and leading zeros must not be stripped. The
  GID all 0 is reserved and must not be used. The GID must be unique,
  otherwise error is reported and the download is not added.  This
  option is useful when restoring the sessions saved using
  --save-session option. If this option is not used, new GID is
  generated by aria2.

* Use 64 bits random bytes as GID

  This change replaces the current 64 bit sequential GID with 64 bits
  random bytes GID in an attempt to support persistent
  GID. Internally, the GID is stored as uint64_t. For human
  representation and RPC interface, GID is represented as 16 bytes hex
  string. For console readout, 16 bytes are too long, so it is
  abbreviated to first 6 bytes.  When querying GID in RPC calls, user
  can speicfy the prefix of GID as long as the prefix is shared by
  more than 1 GID entries.

* Fixed BitfieldMan::getOffsetCompletedLength overflow on 32-bit systems

* mingw32: Use HANDLE only for MinGW32 build

* Changed console readout, making it more compact

  "SIZE:" is removed because it is obvious. SEEDING, SEED, SPD and UP
  are now replaced with SEED, SD, DL and UL respectively.

* Compact readout when more than 1 simultaneous downloads are going on

  If more than 1 simultaneous downloads are going on, use more compact
  format in readout. Currently, at most 5 download stats are
  displayed.

  util::abbrevSize() is rewritten to support "Gi" unit and provides
  more compact abbreviation.

* Console color output

  Log level and download result string is now colored.

* Logger: Simplified console output and change level format in log

  The date and time are now removed from console output.  The log
  level is now formatted as "[LEVEL]".

* Start to find faster host before the number of missing segments becomes 1

  The old implementation starts to find faster host when the number of
  missing segment becomes 1. Because of --min-split-size option,
  before the number of missing segment becomes 1, the number of
  connection becomes 1 and it can be slow. In this case, we have to
  wait until the last segment is reached. The new implementation
  starts to find faster host when the remaining length is less than
  --min-split-size * 2, to mitigate the problem stated above.

* Removed warning when --file-allocation=falloc is used in MinGW32 build

  The warning was just a mistake. SetFilePointerEx + SetEndOfFile
  actually allocate disk space.

* Write data in 4K aligned offset in write with disk cache enabled

  This greatly reduces disk activity especially on Win + NTFS.  Not so
  much difference on Linux.

* mingw32: Removed FSCTL_SET_SPARSE set

* Added --disk-cache option

  This option enables disk cache. If SIZE is 0, the disk cache is
  disabled. This feature caches the downloaded data in memory, which
  grows to at most SIZE bytes. The cache storage is created for aria2
  instance and shared by all downloads. The one advantage of the disk
  cache is reduce the disk seek time because the data is written in
  larger unit and it is reordered by the offset of the file. If the
  underlying file is heavily fragmented it is not the case.
Updated net/aria2 to 1.16.1
When using USE_PKGSRC_GCC_RUNTIME, ensure the fortran wrapper uses the
custom specs file too, so that the correct runtime is used.
Remove ftp.opendylan.org, no ping some time.
Upgrade to Asterisk 11.1.1;  this is a security fix to fix AST-2012-14
and AST-2012-015.

Approved for commit during freeze by: agc

The Asterisk Development Team has announced security releases for Certified
Asterisk 1.8.11 and Asterisk 1.8, 10, and 11. The available security releases
are released as versions 1.8.11-cert10, 1.8.19.1, 10.11.1, 10.11.1-digiumphones,
and 11.1.1.

The release of these versions resolve the following two issues:

* Stack overflows that occur in some portions of Asterisk that manage a TCP
  connection. In SIP, this is exploitable via a remote unauthenticated session;
  in XMPP and HTTP connections, this is exploitable via remote authenticated
  sessions.

* A denial of service vulnerability through exploitation of the device state
  cache. Anonymous calls had the capability to create devices in Asterisk that
  would never be disposed of.

These issues and their resolutions are described in the security advisories.

For more information about the details of these vulnerabilities, please read
security advisories AST-2012-014 and AST-2012-015, which were released at the
same time as this announcement.

For a full list of changes in the current releases, please see the ChangeLogs:

http://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-11.1.1

The security advisories are available at:

 * http://downloads.asterisk.org/pub/security/AST-2012-014.pdf
 * http://downloads.asterisk.org/pub/security/AST-2012-015.pdf

Thank you for your continued support of Asterisk!
Updated comms/asterisk to 11.1.1
Upgrade to Asterisk 10.11.1;  this is a security fix to fix AST-2012-14
and AST-2012-015.

Approved for commit during freeze by: agc

The Asterisk Development Team has announced security releases for Certified
Asterisk 1.8.11 and Asterisk 1.8, 10, and 11. The available security releases
are released as versions 1.8.11-cert10, 1.8.19.1, 10.11.1, 10.11.1-digiumphones,
and 11.1.1.

The release of these versions resolve the following two issues:

* Stack overflows that occur in some portions of Asterisk that manage a TCP
  connection. In SIP, this is exploitable via a remote unauthenticated session;
  in XMPP and HTTP connections, this is exploitable via remote authenticated
  sessions.

* A denial of service vulnerability through exploitation of the device state
  cache. Anonymous calls had the capability to create devices in Asterisk that
  would never be disposed of.

These issues and their resolutions are described in the security advisories.

For more information about the details of these vulnerabilities, please read
security advisories AST-2012-014 and AST-2012-015, which were released at the
same time as this announcement.

For a full list of changes in the current releases, please see the ChangeLogs:

http://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-11.1.1

The security advisories are available at:

 * http://downloads.asterisk.org/pub/security/AST-2012-014.pdf
 * http://downloads.asterisk.org/pub/security/AST-2012-015.pdf

Thank you for your continued support of Asterisk!
de to Asterisk 1.8.19.1;  this is a security fix to fix AST-2012-14
and AST-2012-015.

Approved for commit during freeze by: agc

The Asterisk Development Team has announced security releases for Certified
Asterisk 1.8.11 and Asterisk 1.8, 10, and 11. The available security releases
are released as versions 1.8.11-cert10, 1.8.19.1, 10.11.1, 10.11.1-digiumphones,
and 11.1.1.

The release of these versions resolve the following two issues:

* Stack overflows that occur in some portions of Asterisk that manage a TCP
  connection. In SIP, this is exploitable via a remote unauthenticated session;
  in XMPP and HTTP connections, this is exploitable via remote authenticated
  sessions.

* A denial of service vulnerability through exploitation of the device state
  cache. Anonymous calls had the capability to create devices in Asterisk that
  would never be disposed of.

These issues and their resolutions are described in the security advisories.

For more information about the details of these vulnerabilities, please read
security advisories AST-2012-014 and AST-2012-015, which were released at the
same time as this announcement.

For a full list of changes in the current releases, please see the ChangeLogs:

http://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-11.1.1

The security advisories are available at:

 * http://downloads.asterisk.org/pub/security/AST-2012-014.pdf
 * http://downloads.asterisk.org/pub/security/AST-2012-015.pdf

Thank you for your continued support of Asterisk!
update comms/asterisk10 to 10.11.1
update comms/asterisk18 to 1.8.19.1