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.
www/py-django-timezone-field: Update to 4.0
* Also assign it to Django 2.2 (current LTS release) as Django 1.11 is
End-of-Life since April 2020.
* Set the repo-copied port www/py-dj22-django-timezone-field as DEPRECATED
because it's obsolete now. Don't set an expiration date yet as it's still
used by net-mgmt/netbox and a few more Django 1.11 ports need to be
assigned to Django 2.2 first.
* Also update the CONFLICTS_INSTALL entries as the repo-copied port
py-dj21-django-timezone-field no longer exists in the Ports tree.
Changelog:
* Add support for Django 3.0 and Python 3.8
* Drop support for Django 1.11, 2.0, 2.1 and Python 2.7, 3.4
PR: 245309
www/py-dj22-django-timezone-field: Update to 4.0
Changelog:
* Add support for Django 3.0 and Python 3.8
* Drop support for Django 1.11, 2.0, 2.1 and Python 2.7, 3.4
www/py-{dj21,dj22}-django-timezone-field: Update to 3.1
Changelog:
* Officially support django 2.2 (already worked)
* Add option to display TZ offsets in form field
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 )
