Updated graphics/p5-cairo to 1.104

(obache)

Update p5-cairo to 1.104.
(with fixes configure requirements from DEPENDS to BUILD_DEPENDS)

Overview of changes in Cairo 1.104
==================================

* Avoid misusing the macro PL_na, thus preventing potential issues when Cairo
  is used in conjunction with certain XS modules, among them XML::Parser and
  String::Approx.

(obache)

Remove FETCH_USING, not for package Makefiles to set.

(wiz)

Put sections in standard order.
Remove FETCH_USING because it's not intended to be put in package Makefiles.

(wiz)

+p5-Glib-Object-Introspection

(obache)

Added devel/p5-Glib-Object-Introspection version 0.019

(obache)

Import p5-Glib-Object-Introspection-0.019 as devel/p5-Glib-Object-Introspection.

Glib::Object::Introspection uses the gobject-introspection and libffi projects
to dynamically create Perl bindings for a wide variety of libraries.  Examples
include gtk+, webkit, libsoup and many more.

(obache)

require libffi>=3.0.0

(obache)

Updated devel/p5-glib2 to 1.304

(obache)

Updated devel/p5-glib2 to 1.304

(obache)

Update p5-glib2 to 1.304.

Overview of changes in Glib 1.304 (stable)
==========================================

* Fix compilation against glib < 2.34.0.

Overview of changes in Glib 1.303 (stable)
==========================================

* Revert the change to ref counting of initial wrappers of custom subclasses,
  introduced in Glib 1.300.  It caused issues with subclasses inheriting from
  Glib::InitiallyUnowned.
* Fix a test failure with perl >= 5.19.4.
* Create a GType for GSpawnFlags and register it with the bindings.

Overview of changes in Glib 1.302 (stable)
==========================================

* Avoid misusing the macro PL_na, thus preventing issues when Glib is used in
  conjunction with certain XS modules, among them XML::Parser and
  String::Approx.
* Avoid memory corruption when registering boxed synonyms repeatedly.

Overview of changes in Glib 1.301 (stable)
==========================================

* t/options.t: skip tests in non-UTF-8 locales; fixes RT#83490

Overview of changes in Glib 1.300 (stable)
==========================================

* Stable release to coincide with the release of Perl 5.18.0

Since 1.28x (The previous stable release)
-----------------------------------------
* Ensure timely destruction of initial wrapper of custom subclasses
* Start changing module version numbers in all Perl modules in the
  distribution, not just lib/Glib.pm; (Bugzilla #690464)
* Make Glib::Object subclassing more robust.  This should in particular fix
  issues revealed by the change to hash randomization introduced in perl
  5.17.6.
* Correctly handle utf8-encoded strings in GPerlArgv.  This should fix issues
  seen with utf8-encoded strings in @ARGV with, for example, Gtk2->init.

Overview of changes in Glib 1.291 (unstable)
============================================

* Ensure timely destruction of initial wrapper of custom subclasses
* Start changing module version numbers in all Perl modules in the
  distribution, not just lib/Glib.pm; (Bugzilla #690464)

Overview of changes in Glib 1.290 (unstable)
============================================

* Make Glib::Object subclassing more robust.  This should in particular fix
  issues revealed by the change to hash randomization introduced in perl
  5.17.6.
* Correctly handle utf8-encoded strings in GPerlArgv.  This should fix issues
  seen with utf8-encoded strings in @ARGV with, for example, Gtk2->init.

Overview of changes in Glib 1.280 (stable)
==========================================

Since 1.26x (the previous stable series)
----------------------------------------
* Correctly handle the boxed type for GError.
* Ensure that custom signal marshallers are always used irregardless of
  the spelling used for the signal name.
* Make the stack handling of some marshallers more robust, in
  preparation for custom Glib::Boxed converters that call back into
  Perl code.
* Add new C API gperl_register_boxed_synonym.

Since 1.270
-----------
* Fix building with perl <= 5.14.

Overview of changes in Glib 1.270 (unstable)
============================================

* Correctly handle the boxed type for GError.
* Ensure that custom signal marshallers are always used irregardless of the
  spelling used for the signal name.
* Make the stack handling of some marshallers more robust, in
  preparation for custom Glib::Boxed converters that call back into Perl
  code.
* Add new C API gperl_register_boxed_synonym.

(obache)

scamper update.

(markd)

Fix typo in comment.

(wiz)

Update scamper to 20140122

from PR pkg/48546

scamper-dealias:
* many slight improvements to the implementation of the 'ally' alias
  resolution algorithm.
* add flag to prefixscan that says the alias was inferred using a common
  source address
* for json output, print flags, bump version.

scamper-ping:
* record ICMP parameter problem responses to ping.
* for json output, print tx time on probes.

sc_attach:
* add support for starting as a daemon.
* add support for specifying a command which will be used with each address
* document these options in manual page

sc_analysis_dump:
* update manual page to document unintuitive behaviour of -e option.

misc:
* getopt returns an int, not a char.  important on arm.  fixed in
  sc_wartscat, sc_speedtrap, and sc_analysis_dump,
* silence benign warnings from clang on MacOS and cppcheck.

(markd)

Update comment:
Assembler support is still broken under Mac OS X in version 3.2.9.
Somebody should re-check Solaris as well.

(tron)

+ clutter-gst-2.0.10 [require gstreamer1>=1.2.0]

(obache)

Note mksh update

(bsiegert)

Update mksh to R49.

R49 is a recommended bugfix release:

- [tg] dot.mkshrc: fix two issues with the cd wrapper
- [tg] Unbreak set +p (wider issue still to be addressed)
- [Steffen Daode Nurpmeso] Use WCONTINUED with waitpid(2)
- [millert] Add proper suspend builtin handling tty(4) and setpgrp(2)
- [tg] Sanitise and slightly optimise control character handling
- [tg] Add O_BINARY to all open(2) calls for OS/2 kLIBC support
- [tg] Generate option strings for shell, set, ulimit at compile time
- [Steffen Daode Nurpmeso] Drop ISTRIP termios(4) mode
- [tg] Mention negative history numbers, octals in the manpage
- [tg] Make check.pl work with Perl < 5.6.1 again
- [tg] Detect getsid(2) and skip the oksh suspend builtin otherwise
- [tg] Document that set -o noclobber is unsafe for tempfiles
- [tg] Update to Unicode 6.3.0
- [RT] Restore some portability
- [tg] Fix parsing positional argument variable names
- [tg] Sprinkle a few __attribute__((__pure__)); fix warnings
- [tg] Fix build on OSX: always use our wcwidth code; only use our strlcpy(3)
  code if the OE doesn窶冲 provide one (prompted by jonthn on IRC)
- [tg] Optimise sh -c to exec even in MKSH_SMALL
- [tg] Use new BAFH for hashing

(bsiegert)

Updated graphics/clutter to 1.16.4

(obache)

Update clutter to 1.16.4.

Clutter 1.16.4                                                      2014-01-24
===============================================================================

  • List of changes since Clutter 1.16.2

    - Performance improvements
    Avoid using hardware picking as much as possible; do not queue redraws
    when not needed, and rely on clipped redraws more.

    - Accessibility fixes

  • List of bugs fixed since Clutter 1.16.2

    #710227 - ClutterGestureAction memory corruption
    #719747 - ClutterStage: Don't add empty actors to the stage clip
    #712563 - Fixes for cogl journal usage when picking
    #722220 - Incorrect string reported in accessible text-changed events
              when text is removed
    #722188 - atk_text_get_n_selections() should return 0 when no text is
              selected
    #719901 - ClutterStageCogl: Ignore a clip the size of the stage
    #719563 - input-device: Guard against double free
    #719367 - Bind constraints: Don't force redraws on source relayout
    #719368 - Don't queue redraws when reallocating actor that haven't moved

Many thanks to:

  Owen W. Taylor, Alejandro Piñeiro, Jasper St. Pierre, Florian Müllner,
  Lionel Landwerlin, Sphinx Jiang, Wylmer Wang.

(obache)

py-amqp works with python-3.x, as does this.

(wiz)

Updated graphics/cogl to 1.16.2

(obache)

Update cogl to 1.16.2.

Cogl 1.16.2                                                        2014-01-20

  • List of changes since Cogl 1.16.0

  » YV12/I420 support in cogl-gst is fixed.
  » cogl_framebuffer_push_path_clip is fixed.
  » MSVC build updates

  • Gnome Bugzilla bugs closed since 1.16.0:

    #706808 - "Unable to locate required kms libraries" message is really
              uninformative
    #710135 - Fix build on big endian
    #710926 - Build fails without declaration of wl_resource
    #719582 - cogl-framebuffer: Don't mark the clear clip dirty from the
              journal
    #721450 - Re-enable swap_region for mesa 10.1+ llvmpipe / swrast

Many thanks to:

  Robert Bragg
  Adel Gadllah
  Lionel Landwerlin
  Chun-wei Fan
  Emilio Pozuelo Monfort
  Jasper St. Pierre

(obache)

specify gl-libname without extension and shlib major version.
default ligGL.so.1 match to pkgsrc one with ELF, but not for builtin one.

(obache)

Updated textproc/asciidoc to 8.6.9nb2

(wiz)

Fix interpreter path in more files. Bump PKGREVISION.

(wiz)

Updated www/ikiwiki to 3.20140125

(schmonz)

Update to 3.20140125. From the changelog:

* inline: Allow overriding the title of the feed. Closes: #735123
  Thanks, Christophe Rhodes
* osm: Escape name parameter. Closes: #731797

(schmonz)

Use gcc46 under OpenBSD to suppress warning as error

(ryoon)

Fix build under OpenBSD/amd64 5.4

* Pass -liconv to LDFLAGS

(ryoon)

Forgot to add this... Fixes unportable cfmakeraw() for SunOS.

(rodent)

Fix library names under OpenBSD for consistent PLIST

(ryoon)

Add OpenBSD/amd64 5.4 support

(ryoon)

Darktable now needs GraphicsMagick headers (if not also libraries) to
build.

(jakllsch)

Updated devel/py-coverage to 3.7.1

(wiz)

Update to 3.7.1:

3.7.1 -- 13 December 2013
-------------------------

- Improved the speed of HTML report generation by about 20%.

- Fixed the mechanism for finding OS-installed static files for the HTML report
  so that it will actually find OS-installed static files.

3.7 --- 6 October 2013
----------------------

- Added the ``--debug`` switch to ``coverage run``.  It accepts a list of
  options indicating the type of internal activity to log to stderr.

- Improved the branch coverage facility, fixing `issue 92`_ and `issue 175`_.

- Running code with ``coverage run -m`` now behaves more like Python does,
  setting sys.path properly, which fixes `issue 207`_ and `issue 242`_.

- Coverage can now run .pyc files directly, closing `issue 264`_.

- Coverage properly supports .pyw files, fixing `issue 261`_.

- Omitting files within a tree specified with the ``source`` option would
  cause them to be incorrectly marked as unexecuted, as described in
  `issue 218`_.  This is now fixed.

- When specifying paths to alias together during data combining, you can now
  specify relative paths, fixing `issue 267`_.

- Most file paths can now be specified with username expansion (``~/src``, or
  ``~build/src``, for example), and with environment variable expansion
  (``build/$BUILDNUM/src``).

- Trying to create an XML report with no files to report on, would cause a
  ZeroDivideError, but no longer does, fixing `issue 250`_.

- When running a threaded program under the Python tracer, coverage no longer
  issues a spurious warning about the trace function changing: "Trace function
  changed, measurement is likely wrong: None."  This fixes `issue 164`_.

- Static files necessary for HTML reports are found in system-installed places,
  to ease OS-level packaging of coverage.py.  Closes `issue 259`_.

- Source files with encoding declarations, but a blank first line, were not
  decoded properly.  Now they are.  Thanks, Roger Hu.

- The source kit now includes the ``__main__.py`` file in the root coverage
  directory, fixing `issue 255`_.

.. _issue 92: https://bitbucket.org/ned/coveragepy/issue/92/finally-clauses-arent-treated-properly-in
.. _issue 164: https://bitbucket.org/ned/coveragepy/issue/164/trace-function-changed-warning-when-using
.. _issue 175: https://bitbucket.org/ned/coveragepy/issue/175/branch-coverage-gets-confused-in-certain
.. _issue 207: https://bitbucket.org/ned/coveragepy/issue/207/run-m-cannot-find-module-or-package-in
.. _issue 242: https://bitbucket.org/ned/coveragepy/issue/242/running-a-two-level-package-doesnt-work
.. _issue 218: https://bitbucket.org/ned/coveragepy/issue/218/run-command-does-not-respect-the-omit-flag
.. _issue 250: https://bitbucket.org/ned/coveragepy/issue/250/uncaught-zerodivisionerror-when-generating
.. _issue 255: https://bitbucket.org/ned/coveragepy/issue/255/directory-level-__main__py-not-included-in
.. _issue 259: https://bitbucket.org/ned/coveragepy/issue/259/allow-use-of-system-installed-third-party
.. _issue 261: https://bitbucket.org/ned/coveragepy/issue/261/pyw-files-arent-reported-properly
.. _issue 264: https://bitbucket.org/ned/coveragepy/issue/264/coverage-wont-run-pyc-files
.. _issue 267: https://bitbucket.org/ned/coveragepy/issue/267/relative-path-aliases-dont-work

Version 3.6 --- 5 January 2013
------------------------------

- Added a page to the docs about troublesome situations, closing `issue 226`_,
  and added some info to the TODO file, closing `issue 227`_.

.. _issue 226: https://bitbucket.org/ned/coveragepy/issue/226/make-readme-section-to-describe-when
.. _issue 227: https://bitbucket.org/ned/coveragepy/issue/227/update-todo

Version 3.6b3 --- 29 December 2012
----------------------------------

- Beta 2 broke the nose plugin. It's fixed again, closing `issue 224`_.

.. _issue 224: https://bitbucket.org/ned/coveragepy/issue/224/36b2-breaks-nosexcover

Version 3.6b2 --- 23 December 2012
----------------------------------

- Coverage.py runs on Python 2.3 and 2.4 again. It was broken in 3.6b1.

- The C extension is optionally compiled using a different more widely-used
  technique, taking another stab at fixing `issue 80`_ once and for all.

- Combining data files would create entries for phantom files if used with
  ``source`` and path aliases.  It no longer does.

- ``debug sys`` now shows the configuration file path that was read.

- If an oddly-behaved package claims that code came from an empty-string
  filename, coverage.py no longer associates it with the directory name,
  fixing `issue 221`_.

.. _issue 80: https://bitbucket.org/ned/coveragepy/issue/80/is-there-a-duck-typing-way-to-know-we-cant
.. _issue 221: https://bitbucket.org/ned/coveragepy/issue/221/coveragepy-incompatible-with-pyratemp

Version 3.6b1 --- 28 November 2012
----------------------------------

- Wildcards in ``include=`` and ``omit=`` arguments were not handled properly
  in reporting functions, though they were when running.  Now they are handled
  uniformly, closing `issue 143`_ and `issue 163`_.  **NOTE**: it is possible
  that your configurations may now be incorrect.  If you use ``include`` or
  ``omit`` during reporting, whether on the command line, through the API, or
  in a configuration file, please check carefully that you were not relying on
  the old broken behavior.

- The **report**, **html**, and **xml** commands now accept a ``--fail-under``
  switch that indicates in the exit status whether the coverage percentage was
  less than a particular value.  Closes `issue 139`_.

- The reporting functions coverage.report(), coverage.html_report(), and
  coverage.xml_report() now all return a float, the total percentage covered
  measurement.

- The HTML report's title can now be set in the configuration file, with the
  ``--title`` switch on the command line, or via the API.

- Configuration files now support substitution of environment variables, using
  syntax like ``${WORD}``.  Closes `issue 97`_.

- Embarrassingly, the `[xml] output=` setting in the .coveragerc file simply
  didn't work.  Now it does.

- The XML report now consistently uses filenames for the filename attribute,
  rather than sometimes using module names.  Fixes `issue 67`_.
  Thanks, Marcus Cobden.

- Coverage percentage metrics are now computed slightly differently under
  branch coverage.  This means that completely unexecuted files will now
  correctly have 0% coverage, fixing `issue 156`_.  This also means that your
  total coverage numbers will generally now be lower if you are measuring
  branch coverage.

- When installing, now in addition to creating a "coverage" command, two new
  aliases are also installed.  A "coverage2" or "coverage3" command will be
  created, depending on whether you are installing in Python 2.x or 3.x.
  A "coverage-X.Y" command will also be created corresponding to your specific
  version of Python.  Closes `issue 111`_.

- The coverage.py installer no longer tries to bootstrap setuptools or
  Distribute.  You must have one of them installed first, as `issue 202`_
  recommended.

- The coverage.py kit now includes docs (closing `issue 137`_) and tests.

- On Windows, files are now reported in their correct case, fixing `issue 89`_
  and `issue 203`_.

- If a file is missing during reporting, the path shown in the error message
  is now correct, rather than an incorrect path in the current directory.
  Fixes `issue 60`_.

- Running an HTML report in Python 3 in the same directory as an old Python 2
  HTML report would fail with a UnicodeDecodeError. This issue (`issue 193`_)
  is now fixed.

- Fixed yet another error trying to parse non-Python files as Python, this
  time an IndentationError, closing `issue 82`_ for the fourth time...

- If `coverage xml` fails because there is no data to report, it used to
  create a zero-length XML file.  Now it doesn't, fixing `issue 210`_.

- Jython files now work with the ``--source`` option, fixing `issue 100`_.

- Running coverage under a debugger is unlikely to work, but it shouldn't fail
  with "TypeError: 'NoneType' object is not iterable".  Fixes `issue 201`_.

- On some Linux distributions, when installed with the OS package manager,
  coverage.py would report its own code as part of the results.  Now it won't,
  fixing `issue 214`_, though this will take some time to be repackaged by the
  operating systems.

- Docstrings for the legacy singleton methods are more helpful.  Thanks Marius
  Gedminas.  Closes `issue 205`_.

- The pydoc tool can now show docmentation for the class `coverage.coverage`.
  Closes `issue 206`_.

- Added a page to the docs about contributing to coverage.py, closing
  `issue 171`_.

- When coverage.py ended unsuccessfully, it may have reported odd errors like
  ``'NoneType' object has no attribute 'isabs'``.  It no longer does,
  so kiss `issue 153`_ goodbye.

.. _issue 60: https://bitbucket.org/ned/coveragepy/issue/60/incorrect-path-to-orphaned-pyc-files
.. _issue 67: https://bitbucket.org/ned/coveragepy/issue/67/xml-report-filenames-may-be-generated
.. _issue 82: https://bitbucket.org/ned/coveragepy/issue/82/tokenerror-when-generating-html-report
.. _issue 89: https://bitbucket.org/ned/coveragepy/issue/89/on-windows-all-packages-are-reported-in
.. _issue 97: https://bitbucket.org/ned/coveragepy/issue/97/allow-environment-variables-to-be
.. _issue 100: https://bitbucket.org/ned/coveragepy/issue/100/source-directive-doesnt-work-for-packages
.. _issue 111: https://bitbucket.org/ned/coveragepy/issue/111/when-installing-coverage-with-pip-not
.. _issue 137: https://bitbucket.org/ned/coveragepy/issue/137/provide-docs-with-source-distribution
.. _issue 139: https://bitbucket.org/ned/coveragepy/issue/139/easy-check-for-a-certain-coverage-in-tests
.. _issue 143: https://bitbucket.org/ned/coveragepy/issue/143/omit-doesnt-seem-to-work-in-coverage
.. _issue 153: https://bitbucket.org/ned/coveragepy/issue/153/non-existent-filename-triggers
.. _issue 156: https://bitbucket.org/ned/coveragepy/issue/156/a-completely-unexecuted-file-shows-14
.. _issue 163: https://bitbucket.org/ned/coveragepy/issue/163/problem-with-include-and-omit-filename
.. _issue 171: https://bitbucket.org/ned/coveragepy/issue/171/how-to-contribute-and-run-tests
.. _issue 193: https://bitbucket.org/ned/coveragepy/issue/193/unicodedecodeerror-on-htmlpy
.. _issue 201: https://bitbucket.org/ned/coveragepy/issue/201/coverage-using-django-14-with-pydb-on
.. _issue 202: https://bitbucket.org/ned/coveragepy/issue/202/get-rid-of-ez_setuppy-and
.. _issue 203: https://bitbucket.org/ned/coveragepy/issue/203/duplicate-filenames-reported-when-filename
.. _issue 205: https://bitbucket.org/ned/coveragepy/issue/205/make-pydoc-coverage-more-friendly
.. _issue 206: https://bitbucket.org/ned/coveragepy/issue/206/pydoc-coveragecoverage-fails-with-an-error
.. _issue 210: https://bitbucket.org/ned/coveragepy/issue/210/if-theres-no-coverage-data-coverage-xml
.. _issue 214: https://bitbucket.org/ned/coveragepy/issue/214/coveragepy-measures-itself-on-precise

Version 3.5.3 --- 29 September 2012
-----------------------------------

- Line numbers in the HTML report line up better with the source lines, fixing
  `issue 197`_, thanks Marius Gedminas.

- When specifying a directory as the source= option, the directory itself no
  longer needs to have a ``__init__.py`` file, though its subdirectories do, to
  be considered as source files.

- Files encoded as UTF-8 with a BOM are now properly handled, fixing
  `issue 179`_.  Thanks, Pablo Carballo.

- Fixed more cases of non-Python files being reported as Python source, and
  then not being able to parse them as Python.  Closes `issue 82`_ (again).
  Thanks, Julian Berman.

- Fixed memory leaks under Python 3, thanks, Brett Cannon. Closes `issue 147`_.

- Optimized .pyo files may not have been handled correctly, `issue 195`_.
  Thanks, Marius Gedminas.

- Certain unusually named file paths could have been mangled during reporting,
  `issue 194`_.  Thanks, Marius Gedminas.

- Try to do a better job of the impossible task of detecting when we can't
  build the C extension, fixing `issue 183`_.

- Testing is now done with `tox`_, thanks, Marc Abramowitz.

.. _issue 82: https://bitbucket.org/ned/coveragepy/issue/82/tokenerror-when-generating-html-report
.. _issue 147: https://bitbucket.org/ned/coveragepy/issue/147/massive-memory-usage-by-ctracer
.. _issue 179: https://bitbucket.org/ned/coveragepy/issue/179/htmlreporter-fails-when-source-file-is
.. _issue 183: https://bitbucket.org/ned/coveragepy/issue/183/install-fails-for-python-23
.. _issue 194: https://bitbucket.org/ned/coveragepy/issue/194/filelocatorrelative_filename-could-mangle
.. _issue 195: https://bitbucket.org/ned/coveragepy/issue/195/pyo-file-handling-in-codeunit
.. _issue 197: https://bitbucket.org/ned/coveragepy/issue/197/line-numbers-in-html-report-do-not-align
.. _tox: http://tox.readthedocs.org/

Version 3.5.2 --- 4 May 2012
----------------------------

No changes since 3.5.2.b1

Version 3.5.2b1 --- 29 April 2012
---------------------------------

- The HTML report has slightly tweaked controls: the buttons at the top of
  the page are color-coded to the source lines they affect.

- Custom CSS can be applied to the HTML report by specifying a CSS file as
  the extra_css configuration value in the [html] section.

- Source files with custom encodings declared in a comment at the top are now
  properly handled during reporting on Python 2.  Python 3 always handled them
  properly.  This fixes `issue 157`_.

- Backup files left behind by editors are no longer collected by the source=
  option, fixing `issue 168`_.

- If a file doesn't parse properly as Python, we don't report it as an error
  if the filename seems like maybe it wasn't meant to be Python.  This is a
  pragmatic fix for `issue 82`_.

- The ``-m`` switch on ``coverage report``, which includes missing line numbers
  in the summary report, can now be specifed as ``show_missing`` in the
  config file.  Closes `issue 173`_.

- When running a module with ``coverage run -m <modulename>``, certain details
  of the execution environment weren't the same as for
  ``python -m <modulename>``.  This had the unfortunate side-effect of making
  ``coverage run -m unittest discover`` not work if you had tests in a
  directory named "test".  This fixes `issue 155`_ and `issue 142`_.

- Now the exit status of your product code is properly used as the process
  status when running ``python -m coverage run ...``.  Thanks, JT Olds.

- When installing into pypy, we no longer attempt (and fail) to compile
  the C tracer function, closing `issue 166`_.

.. _issue 82: https://bitbucket.org/ned/coveragepy/issue/82/tokenerror-when-generating-html-report
.. _issue 142: https://bitbucket.org/ned/coveragepy/issue/142/executing-python-file-syspath-is-replaced
.. _issue 155: https://bitbucket.org/ned/coveragepy/issue/155/cant-use-coverage-run-m-unittest-discover
.. _issue 157: https://bitbucket.org/ned/coveragepy/issue/157/chokes-on-source-files-with-non-utf-8
.. _issue 166: https://bitbucket.org/ned/coveragepy/issue/166/dont-try-to-compile-c-extension-on-pypy
.. _issue 168: https://bitbucket.org/ned/coveragepy/issue/168/dont-be-alarmed-by-emacs-droppings
.. _issue 173: https://bitbucket.org/ned/coveragepy/issue/173/theres-no-way-to-specify-show-missing-in

(wiz)

Do not use py-distrbute with Python 3.x, but always use py-setuptools
(as was the default for Python-2.x in this file).

py-distribute is by now obsolete, and py-setuptools the standard way.

(wiz)

Do not insist on py-distribute on python-3.x.
Times have changed, and py-setuptools is now the cool kid again.

(wiz)

Add missing egg to PLIST. Bump PKGREVISION.
(breakage happened during previous commit, sorry)

(wiz)

Updated graphics/py-OpenGL to 3.0.1nb5

(wiz)

Add missing egg to PLIST (happened during big python-3.x commit, sorry).
Fix interpreter path in installed file.
Bump PKGREVISION.

(wiz)

Remove py-fann, it seems deprecated upstream.
At least there is no release available for the current stable
release, 2.2.0.
ok maintainer gdt@

(wiz)

Updated lang/openjdk7 to 1.7.51

(ryoon)

Update to 1.7.51

I cannot find release notes for OpenJDK7, I will quote from Oracle's
JDK 7u51 release notes.

Changelog:
7u51: http://www.oracle.com/technetwork/java/javase/7u51-relnotes-2085002.html
Olson Data 2013h
JDK 7u51 contains Olson time zone data version 2013h.

New Features and Changes
Jarsigner updated to encourage timestamping

Timestamping for a signed jar is now strongly recommended. The Jarsigner tool will print out an informational warning at signing or verifying when timestamp is missing. For more information, see Signing JAR Files.

See 8023338.
Changes to Security Slider:

The following changes to Security Slider were included in this release(7u51):

    Block Self-Signed and Unsigned applets on High Security Setting
    Require Permissions Attribute for High Security Setting
    Warn users of missing Permissions Attributes for Medium Security Setting

For more information, see Java Control Panel documentation.
Prompt users to clear previously remembered decisions:

In JDK 7u51, users are given an option to restore the security prompts, for any prompts that were hidden prior to installing the latest release. For more information, see Install Documentation for Windows.

It is recommended that users restore security prompts after every 30 days to ensure better protection.

Note: This option is offered only during Auto update on Mac OS.
Exception Site List:

The Exception Site List feature allows end users to run Java applets and Java Web Start applications that do not meet the latest security requirements. Rich Internet Applications that are hosted on a site in the exception site list are allowed to run with the applicable security prompts.

For more information, see Exception Site List documentation.
Change in Default Socket Permissions

The default socket permissions assigned to all code including untrusted code have been changed in this release. Previously, all code was able to bind any socket type to any port number greater than or equal to 1024. It is still possible to bind sockets to the ephemeral port range on each system. The exact range of ephemeral ports varies from one operating system to another, but it is typically in the high range (such as from 49152 to 65535). The new restriction is that binding sockets outside of the ephemeral range now requires an explicit permission in the system security policy.

Most applications using client tcp sockets and a security manager will not see any problem, as these typically bind to ephemeral ports anyway. Applications using datagram sockets or server tcp sockets (and a security manager) may encounter security exceptions where none were seen before. If this occurs, users should review whether the port number being requested is expected, and if this is the case, a socket permission grant can be added to the local security policy, to resolve the issue.

See 8011786 (not public).
Change in JAXP Xalan Extension Functions

In JDK 7u51, a change has been made in JAXP Xalan Extension functions to always use the default DOM implementation when Security Manager is present. This change affects the NodeSet created by DOM Document.

Before this change, the DOM implementation is located through the DOM factory lookup process. With this change, when security is enabled, the lookup process is skipped and the default DOM implementation is used.

This change will only affect those applications that use a 3rd party DOM implementation. In general, the NodeSet structure is expected to be compatible with that of the JDK default implementation.
Bug Fixes

This release contains fixes for security vulnerabilities. For more information, see Oracle Java SE Critical Patch Update Advisory.

For a list of bug fixes included in this release, see JDK 7u51 Bug Fixes page.

The following are some of the notable bug fixes in this release:

Area: tools/jar
Synopsis: Clarify jar verifications

The jarsigner tool prints out more messages when there are severe warnings and -strict is on. For details, see the jarsigner tool documentation (Windows)(Solaris/Linux).

See 8024302 (not public).

(ryoon)

Updated lang/gcc46 to 4.6.4

(ryoon)

Update to 4.6.4

* Add OpenBSD/amd64 5.4 support

Changelog:
* Bugfixes

(ryoon)

Move (BUILD_)DEPENDS after the maintainer section. Requested by wiz@

(prlw1)

Removed math/gcalctool-gtk3 successor math/gnome-calculator

(prlw1)

Removed gcalctool-gtk3 successor gnome-calculator

(prlw1)

Added math/gnome-calculator version 3.10.2

(prlw1)

Add gnome-calculator 3.10.2

gcalctool ported to vala and renamed gnome-calculator.

(prlw1)

Fix build under SunOS

(ryoon)

Updated finance/moneyguru to 2.7.1

(wiz)

Update to 2.7.1. Packaging-tested only, but 2.6.1 didn't package
any longer. Change LICENSE to modified-bsd per upstream.

Changes:

2.7.1 (2013-09-07)

Improved OFX parsing. (#369)
Fixed rounding error when changing split amounts. (#367)
Fixed Qt import window glitch. (#371)
Improved currency rates fetching reliability.
Fixed occasional hard crashes on accounts drag & drop. [Mac] (#354)

2.7.0 (2013-05-26)

Added support for custom currencies. (#33)
Fixed amount parsing bug with currencies with many decimals.
Fixed cache folder bug causing cached files to be misplaced. [Linux, Windows]
Dropped 32-bit support on Mac OS X.

2.6.3 (2013-03-23)

Fixed a selection glitch on New Account. (#358)
Fixed a schedule spawning bug. (#362)
Removed the fairware dialog (More Info).
Added a 64-bit build for Windows.
Added Spanish localization by Enrique G. Paredes.

2.6.2 (2013-01-06)

Fixed a bug causing transaction imbalance after import. (#351)
Fixed glitch in bar graph drawing. (#352)
Fixed a bug in QIF exports. (#353)
Fixed a crash on print. [Linux, Windows] (#349)

(wiz)

Updated security/gnutls to 3.2.9

(wiz)

Update to 3.2.9 based on patch from Richard Palo.
Assembler issues still seem to be there at least on SunOS.

* Version 3.2.9 (released 2014-01-24)

** libgnutls: The %DUMBFW option in priority string only
appends data to client hello if the expected size is in the
"black hole" range.

** libgnutls: %COMPAT implies %DUMBFW.

** libgnutls: gnutls_session_get_desc() returns a more compact
ciphersuite description.

* libgnutls: In PKCS #11 allow deleting multiple non-certificate data.

** libgnutls: When a PKCS #11 trust store is specified (e.g. using the
configure option --with-default-trust-store-pkcs11), then the PKCS #11
token is used on demand to obtain the trusted anchors, rather than
preloading all trusted certificates. That delegates CA certificate management
and blacklist checking to the PKCS #11 module.

** libgnutls: When a PKCS #11 trust store is specified in configure option
or in gnutls_x509_trust_list_add_trust_file(), then the module is used
to obtain the verification anchors and any required blacklists as in
http://p11-glue.freedesktop.org/doc/storing-trust-policy/storing-trust-pkcs11.html

** libgnutls: Fix in OCSP certificate status extension handling
in non-blocking servers. Patch by Nils Maier.

** p11tool: Added --so-login option to force login as security
officer (admin).

** API and ABI modifications:
No changes since last version.

(wiz)

Updated x11/xf86-video-ati to 7.3.0

(wiz)

Update to 7.3.0 with glamor support disabled (not packaged).

Alex Deucher (16):
      radeon: disallow glamor on pre-R600 asics
      radeon/kms: add berlin pci ids
      radeon: enable glamor by default (v4)
      glamor: require 0.5.1 or newer
      radeon: fix limit handling for cards with >4G of ram
      radeon: add glamor Xv support (v2)
      Revert "radeon: add glamor Xv support (v2)"
      drm/radeon: fix non-glamor build
      radeon: fix the non-glamor build harder...
      radeon: enable tiling on SI by default (v2)
      radeon: add support for Hawaii
      radeon/kms: add Hawaii pci ids
      drm/radeon: fix SUMO2 pci id
      radeon/exa: Always use a scratch surface for UTS to vram
      Require glamor 0.6.0
      radeon: bump version for release

Christopher James Halse Rogers (1):
      EXA/evergreen: Paranoia around linear tiling. (v2)

Dave Airlie (1):
      radeon: use glamor Xv support if present.

Jerome Glisse (1):
      radeon/glamor: with new pixmap for dri2 drawable no need to
create new texture

Maarten Lankhorst (1):
      bump version post release

Mark Kettenis (1):
      Fix shadowfb on big-endian machines

Michel D舅zer (3):
      DRI2: Install client callback only once
      dri2: Make last_vblank_seq local unsigned to match dpms_last_seq
      Don't require the glamoregl module to be pre-loaded with xserver >= 1.15

Robert Millan (2):
      radeon: Set first parameter of drmOpen() to NULL
      radeon: Restore kernel module load on FreeBSD.

Vadim Girlin (1):
      radeon: disable 2D tiling on buffers < 128 pixels

(wiz)

Updated x11/xterm to 301

(wiz)

Update to 301:
This release adds minor bugfixes and documentation improvements.

(wiz)

+ gnutls-3.2.9, py-Scientific-2.8.1, xf86-video-ati-7.3.0.

(wiz)

Updated sysutils/cdrtools to 3.01alpha22

(wiz)

Update to 3.01a22:

3.01a22:

mkisofs includes a new option, -legacy, that allows it to reenable
the short options -H/-L/-P; these have been disabled in 2006 for
compatibility with scripts that have not been updated during the
past 10 years. libsiconv now only tries to open a file when the
argument includes a slash in its name. libschily::printf() now
includes support for %n$ argument reordering for the first 30
arguments.

(wiz)

Updated x11/libdrm to 2.4.52

(wiz)

Update to 2.4.52:

Ben Widawsky (3):
      intel: squash unused variable 'bo_gem'
      intel: Handle malloc fails in context create
      intel: Merge latest i915_drm.h

Eric Anholt (2):
      drm: Initialize or valgrind-clear modesetting ioctl arguments.
      intel: Track whether a buffer is idle to avoid trips to the kernel.

Hyungwon Hwang (1):
      tests/kmstest: support exynos

Keith Packard (1):
      Mark debug_print with __attribute__ ((format(__printf__, 1, 0)))

Kenneth Graunke (2):
      intel: Create a new drm_intel_bo offset64 field.
      Bump the version to 2.4.52

Rob Clark (1):
      freedreno: add fd_device_new_dup()

Vincent ABRIOU (1):
      modetest: add the possibility to select the refresh frequency for a mode

(wiz)

Remove support for PYTHON_PATCH_SCRIPTS; use REPLACE_PYTHON.

(wiz)

No need to have two variables for the same logic.
Replace PYTHON_PATCH_SCRIPTS with REPLACE_PYTHON.

(wiz)

Remove PYTHON_VERSIONS_INCLUDE_3X.
Allow python-3.x by default.

(wiz)

Mark packages as not ready for python-3.x where applicable;
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE=  33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE=  33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.

Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.

Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.

Whitespace cleanups and other nits corrected, where necessary.

(wiz)

Updated x11/py-gtk2 to 2.24.0nb17

(wiz)

Convert to versioned_dependencies.mk for cairo.
Fix interpreter path in installed files.
Mark as not ready for python-3.x.
Bump PKGREVISION.

(wiz)

Add MASTER_SITE_HASKELL_HACKAGE

(obache)

Mark this is as major version 3 of the module
(compare py-beautifulsoup4)

(wiz)

Update HOMEPAGE. Mark as not ready for python-3.x.

(wiz)

Move LICENSE to correct place.

(wiz)

Updated multimedia/py-ming to 0.4.5nb2

(wiz)

Convert to distutils.mk. Mark as not ready for python-3.x.
Bump PKGREVISION.

(wiz)

Mention this is the python-2.x version of the module.

(wiz)

Add geography to CATEGORIES.
Mark as not ready for python-3.x.

(wiz)

Update HOMEPAGE. Mark as not ready for python-3.x (use py-numpy there).

(wiz)

Update HOMEPAGE. Mark as not ready for python-3.x.

(wiz)

Mark as not useful for python-3.x (included since 3.3, the only version
currently in pkgsrc).

(wiz)

Update HOMEPAGE. Mark as not ready for python-3.x.

(wiz)

Remove unnecessary USE_X11=yes.
Mark as not ready for python-3.x.

(wiz)

Set PY_PEP3147=no as package does not support it.
Mark as not ready for python-3.x.

(wiz)

Update HOMEPAGE.
Mark as not ready for python-3.x.

(wiz)

Updated devel/py-gobject-shared to 2.28.6nb11

(wiz)

Since this only installs header files, we do not need any real
py-cairo dependency here. Fake presence for configure script using cairo
flags.
Bump PKGREVISION.

This change allows using this package for both python-2.x and python-3.x.

(wiz)

Adapt PLIST for python-3.x.
Mark as not ready for python-3.x though.
Set PY_PEP3147=no since the infrastructure doesn't support it.
Use versioned_dependencies.mk for cairo.

(wiz)

Mark as not ready for python-3.x.
Also set PY_PEP3147=no since the package infrastructure does not handle
__pycache__ correctly.

(wiz)

Use .PHONY correctly.

(wiz)

Update HOMEPAGE and MASTER_SITES.
Mark as not ready for python-3.x.

(wiz)

Mark as not ready for python-3.x.
Remove CONFIGURE_ARGS that is not supported any longer by the configure
script.

(wiz)

Updated devel/py-ipython1 to 1.1.0nb1

(wiz)

Fix interpreter path in installed files.
Bump PKGREVISION.
Fix build and PLIST for python-3.x

XXX: strangely, this isn't happy with py-distribute for python-3.x.
XXX: I don't understand why, but a build dependency on setuptools fixes
XXX: installation, so I've done that.

(wiz)

Updated emulators/suse131_qt4 to 13.1nb1

(obache)

Update libqt4 RPMs to 4.8.5-5.9.2 for CVE-2013-4549.

Bump PKGREVISION.

(obache)

Note update of sysutils/libvirt to 1.2.1

(agc)