non port: www/py-dj22-django-cors-headers/Makefile |
Number of commits found: 6 |
Wednesday, 24 Jun 2020
|
21:13 kai
Set a few repo-copied py-dj22- ports to expire
* These ports were already set as DEPRECATED some time ago and now have no
consumers left as those have been switched back to the original ports.
|
Wednesday, 27 May 2020
|
00:17 swills
www/py-django-cors-headers: Update to 3.3.0
While here, mark the repo-copied port www/py-dj22-django-cors-headers as
DEPRECATED
PR: 246757
Submitted by: kai
|
Tuesday, 25 Feb 2020
|
21:38 kai
www/py-dj22-django-cors-headers: Update to 3.2.1
* Update WWW field as the repository has a new maintainer.
Changelog:
https://github.com/adamchainz/django-cors-headers/blob/3.2.1/HISTORY.rst
|
Friday, 13 Dec 2019
|
10:19 kai
www/py-django-{dj21,dj22}-cors-headers: Update to 3.2.0
Notable changes since 3.0.2:
* Drop Python 2 support, only Python 3.5-3.8 is supported now.
* Support the value "file://" for origins, which is accidentally sent by
some versions of Chrome on Android.
https://github.com/adamchainz/django-cors-headers/blob/3.2.0/HISTORY.rst
|
Friday, 21 Jun 2019
|
09:36 kai
www/py-{dj21,dj22}-django-cors-headers: Update to 3.0.2
Changelog:
https://github.com/ottoyiu/django-cors-headers/blob/3.0.2/HISTORY.rst
|
Saturday, 25 May 2019
|
10:10 kai
net-mgmt/netbox: Update to 2.5.12 and switch to Django 2.2
Upstream decided to switch from Django 2.1 to the 2.2 LTS release to fix a
rather annoying bug that generated intermittent errors when objects were
deleted/manipulated.
Therefore the same procedure must be done in almost the same way as in
r492690 to make NetBox compatible with Django 2.2 in the ports tree.
That means to repocopy the required Django 1.11 ports, assign them to
Django 2.2, limit them to Python 3.5+ and update all related
CONFLICTS_INSTALL entries accordingly:
* www/py-dj22-django-cors-headers [1]
* www/py-dj22-django-debug-toolbar (Only the first 15 lines of the commit message are shown above )
|
Number of commits found: 6 |