A lot of changes:
* Merge some options with the port because they aren't project options any more
* Enable JACK and PULSEAUDIO by default
* Install additonal executables required for the package to run
* Remove the bundled vamp-plugin-sdk directory because the port dependency is used
* Cleanly remove all internal links with vamp-plugin-sdk, not rebuilding it many times any more
* Change WWW to the https URL
PR: 236000
Submitted by: kunda <chitty_cloud@me.com> (preliminary patch version 3.2.1)
Approved by: uddka@student.kit.edu (maintainer timeout; 1 year and 50 days)
* Repeated warnings due to 'Recache Event Detected for Device'
* No error is recorded to log file when database is incorrect
* MySQL retry logic is not working as expected
* When using IPv6 address, segmentation fault can occur due to incorrectly
using IPv4 ping
* When polling results are null, segmentation errors may occur
* When collecting data, spine should be stripping alpha characters from output
This release introduces two handy features, please take a look
on http://mailman.nginx.org/pipermail/unit/2020-April/000199.html
for details.
<ChangeLog>
*) Feature: a "return" action with optional "location" for immediate
responses and external redirection.
*) Feature: fractional weights support for upstream servers.
*) Bugfix: accidental 502 "Bad Gateway" errors might have occurred in
applications under high load.
*) Bugfix: memory leak in the router; the bug had appeared in 1.13.0.
*) Bugfix: segmentation fault might have occurred in the router process
when reaching open connections limit.
*) Bugfix: "close() failed (9: Bad file descriptor)" alerts might have
appeared in the log while processing large request bodies; the bug
had appeared in 1.16.0.
*) Bugfix: existing application processes didn't reopen the log file.
*) Bugfix: incompatibility with some Node.js applications.
*) Bugfix: broken build on DragonFly BSD; the bug had appeared in
1.16.0.
</ChangeLog>
* Upstream's repository seems stale and no longer maintained. There was no
official release at PyPI since 2015 and the code isn't compatible with
Django 2.2 or later.
Thus deprecate the port and set an expiration date.
PR: 245644
Approved by: Kevin Golding <ports@caomhin.org> (maintainer)
* Repo-copy from www/py-django-happenings because it's an official fork and
also available at PyPI. The forked version has support for newer Django
releases.
* Update CONFLICTS_INSTALL entries accordingly but omit www/py-django-mptt
as it can co-exist (once assigned to Django 2.2) with
www/py-django-happenings-update.
PR: 245644
Approved by: Kevin Golding <ports@caomhin.org> (maintainer)
