---
- branch: MAIN
  date: Wed Jun 18 11:35:38 UTC 2014
  files:
  - new: '1.20'
    old: '1.19'
    path: pkgsrc/www/ap2-wsgi/Makefile
    pathrev: pkgsrc/www/ap2-wsgi/Makefile@1.20
    type: modified
  - new: '1.13'
    old: '1.12'
    path: pkgsrc/www/ap2-wsgi/distinfo
    pathrev: pkgsrc/www/ap2-wsgi/distinfo@1.13
    type: modified
  id: 20140618T113538Z.796be626e71985aba1c640d332287a127a331965
  log: |
    Update to 4.2.4 for a security fix.

    =============
    Version 4.2.4
    =============

    Version 4.2.4 of mod_wsgi can be obtained from:

      https://github.com/GrahamDumpleton/mod_wsgi/archive/4.2.4.tar.gz

    Bugs Fixed
    ----------

    1. Fixed one off error in applying limit to the number of supplementary
    groups allowed for a daemon process group. The result could be that if
    more groups than the operating system allowed were specified to the option
    ``supplementary-groups``, then memory corruption or a process crash could
    occur.

    2. Improved error handling in setting up the current working directory and
    group access rights for a process when creating a daemon process group. The
    change means that if any error occurs that the daemon process group will be
    restarted rather than allow it to keep running with an incorrect working
    directory or group access rights.

    New Features
    ------------

    1. Added the ``--setup-only`` option to mod_wsgi express so that it is
    possible to create the configuration when using the Django management command
    ``runmodwsgi`` without actually starting the server.

    =============
    Version 4.2.3
    =============

    Version 4.2.3 of mod_wsgi can be obtained from:

      https://github.com/GrahamDumpleton/mod_wsgi/archive/4.2.3.tar.gz

    Bugs Fixed
    ----------

    1. The feature for starting mod_wsgi express using the Django management
    command ``runmodwsgi`` was broken by the 4.2.2 release.

    =============
    Version 4.2.2
    =============

    Version 4.2.2 of mod_wsgi can be obtained from:

      https://github.com/GrahamDumpleton/mod_wsgi/archive/4.2.2.tar.gz

    Bugs Fixed
    ----------

    1. The ``envvars`` file was being overwritten even if it existed and had
    been modified.

    New Features
    ------------

    1. Output the location of the ``envvars`` file when using the
    ``setup-server`` command for ``mod_wsgi-express`` or if using the
    ``start-server`` command and the ``--envars-script`` option was being used.

    2. Output the location of the ``apachectl`` script when using the
    ``setup-server`` command for ``mod_wsgi-express``.

    =============
    Version 4.2.1
    =============

    Version 4.2.1 of mod_wsgi can be obtained from:

      https://github.com/GrahamDumpleton/mod_wsgi/archive/4.2.1.tar.gz

    Bugs Fixed
    ----------

    1. The auto generated configuration would not work with an Apache
    installation where core Apache modules were statically compiled into Apache
    rather than being dynamically loaded.

    =============
    Version 4.2.0
    =============

    Version 4.2.0 of mod_wsgi can be obtained from:

      https://github.com/GrahamDumpleton/mod_wsgi/archive/4.2.0.tar.gz

    New Features
    ------------

    1. Added ``mod_wsgi.server_metrics()`` function which provides access to a
    dictionary of data derived from the Apache worker scoreboard. In effect this
    provides access to the same information that is used to create the Apache
    server status page.

    Note that if ``mod_status`` is not loaded into Apache, or the compile time
    configuration of Apache prohibits the scoreboard from being available, this
    function will return ``None``.

    Also be aware that only partial information about worker status, and no
    information about requests, will be returned if the ``ExtendedStatus``
    directive is not also set to ``On``.

    Although ``mod_status`` needs to be loaded, it is not necessary to enable
    any URL to expose the server status page.

    2. Added support for a platform plugin for New Relic to ``mod_wsgi-express``
    which will report server status information up to New Relic if the
    ``--with-newrelic`` option is supplied when running mod_wsgi express.

    That same option also enables the New Relic Python agent. If you only want
    one or the other, you can instead use the ``--with-newrelic-agent`` and
    ``--with-newrelic-platform`` options.

    The feature of ``mod_wsgi-express`` for reporting data up to the New Relic
    Platform is dependent upon the separate ``mod_wsgi-metrics`` package being
    installed.
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/www/ap2-wsgi'
  unixtime: '1403091338'
  user: wiz