Changes 1.7.28:
* Write proper copyright year for zlib, depending upon ZLIB_VERNUM

Changes 1.7.27:
* Increased row_buf malloc to row_bytes+64 instead of row_bytes+16, to
  match the size of big_row_buf in pngrutil.c (it is 48 in libpng14, 15, 16,
  and 64 in libpng10, 12.  Otherwise there is a double-free crash when the
  row_buf is destroyed.

Changes 1.7.26:
* Increased the text_text buffer from 2048 to 10*2048 (Ralph Giles), and
  changed an incorrect test for keyword length "< 180" to "< 80".  The
  text_text buffer was inadvertently reduced from 20480 to 2048 in
  pngcrush-1.7.9.
* Added -DZ_SOLO to CFLAGS, needed to compile zlib-1.2.6.
* Changed user limits to width and height max 500000, malloc max 2MB,
  cache max 500.
* Added -nolimits option which sets the user limits to the default
  unlimited values.
Updated graphics/pngcrush to 1.7.28
Update for net/haproxy to 1.4.21.

ChangeLog:

2012/05/21 : 1.4.21
    - MINOR: patch for minor typo (ressources/resources)
    - CLEANUP: fix typo in findserver() log message
    - DOC: cleanup indentation, alignment, columns and chapters
    - DOC: fix some keywords arguments documentation
    - MINOR: stats admin: allow unordered parameters in POST requests
    - MINOR: stats admin: use the backend id instead of its name in the form
    - BUG/MAJOR: trash must always be the size of a buffer
    - DOC: fix minor regex example issue and improve doc on stats
    - BUG/MAJOR: possible crash when using capture headers on TCP frontends
    - MINOR: config: disable header captures in TCP mode and complain
    - BUG/MEDIUM: balance source did not properly hash IPv6 addresses
    - CLEANUP: http: message parser must ignore HTTP_MSG_ERROR
    - CLEANUP: remove a few warning about unchecked return values in debug code
    - CLEANUP: http: remove unused http_msg->col
    - BUG/MINOR: http: error snapshots are wrong if buffer wraps
    - BUG/MAJOR: checks: don't call set_server_status_* when no LB algo is set
    - MINOR: proxy: make findproxy() return proxies from numeric IDs too
    - BUILD: http: stop gcc-4.1.2 from complaining about possibly uninitialized values
    - BUG/MINOR: stop connect timeout when connect succeeds

2012/03/10 : 1.4.20
    - BUG/MINOR: fix typo in processing of http-send-name-header
    - BUG/MEDIUM: correctly disable servers tracking another disabled servers.
    - BUG/MEDIUM: zero-weight servers must not dequeue requests from the backend
    - MINOR: halog: add some help on the command line     (cherry picked from commit 615674cdec067066a42f53f5d55628ab7b207e6c)
    - BUILD: fix build error on FreeBSD
    - BUG: queue: fix dequeueing sequence on HTTP keep-alive sessions
    - BUG: http: disable TCP delayed ACKs when forwarding content-length data
    - BUG: checks: fix server maintenance exit sequence
    - BUG/MINOR: stream_sock: don't remove BF_EXPECT_MORE and BF_SEND_DONTWAIT on partial writes
    - DOC: enumerate valid status codes for "observe layer7"
    - BUILD: make it possible to look for pcre in the default system paths
Note update of net/haproxy
Update to 2.6:

2.6
===
	* [CVE-2012-2417] Fix LP#985164: insecure ElGamal key generation.
	  (thanks: Legrandin)

	  In the ElGamal schemes (for both encryption and signatures), g is
	  supposed to be the generator of the entire Z^*_p group.  However, in
	  PyCrypto 2.5 and earlier, g is more simply the generator of a random
	  sub-group of Z^*_p.

	  The result is that the signature space (when the key is used for
	  signing) or the public key space (when the key is used for encryption)
	  may be greatly reduced from its expected size of log(p) bits, possibly
	  down to 1 bit (the worst case if the order of g is 2).

	  While it has not been confirmed, it has also been suggested that an
	  attacker might be able to use this fact to determine the private key.

	  Anyone using ElGamal keys should generate new keys as soon as practical.

	  Any additional information about this bug will be tracked at
	  https://bugs.launchpad.net/pycrypto/+bug/985164

	* Huge documentation cleanup (thanks: Legrandin).

	* Added more tests, including test vectors from NIST 800-38A
	  (thanks: Legrandin)

	* Remove broken MODE_PGP, which never actually worked properly.
	  A new mode, MODE_OPENPGP, has been added for people wishing to write
	  OpenPGP implementations.  Note that this does not implement the full
	  OpenPGP specification, only the "OpenPGP CFB mode" part of that
	  specification.
	  https://bugs.launchpad.net/pycrypto/+bug/996814

	* Fix: getPrime with invalid input causes Python to abort with fatal error
	  https://bugs.launchpad.net/pycrypto/+bug/988431

	* Fix: Segfaults within error-handling paths
	  (thanks: Paul Howarth & Dave Malcolm)
	  https://bugs.launchpad.net/pycrypto/+bug/934294

	* Fix: Block ciphers allow empty string as IV
	  https://bugs.launchpad.net/pycrypto/+bug/997464

	* Fix DevURandomRNG to work with Python3's new I/O stack.
	  (thanks: Sebastian Ramacher)

	* Remove automagic dependencies on libgmp and libmpir, let the caller
	  disable them using args.

	* Many other minor bug fixes and improvements (mostly thanks to Legrandin)
Updated security/py-crypto to 2.6
Add fix for http://secunia.com/advisories/49125/, taken from
http://bugzilla-attachments.gnome.org/attachment.cgi?id=212053.
Bump pkgrevision.
Add fix for http://secunia.com/advisories/49125/, taken from
http://bugzilla-attachments.gnome.org/attachment.cgi?id=212053.
lang/clang: USE_TOOLS+= pod2man pod2html, fix DragonFly

For some reason, LLVM is using autoconf files from 2003 which is before
DragonFly even existed.  I submitted a bug report #12944 at llvm.org's
bugzilla to request they use versions from 2012.

Also, installation fails at document generation without some extra tools.
No need to revbump, either built or it didn't without these packages.