www/py-django-cors-headers 4.9.0_1

*: Switch consumers over to Django 5.2

Django 4.2 reached its End-of-Life on 7th April 2026 and Django 5.2 is
the new LTS (= Long Term Support) release which will be supported until
April 2028.

* Switch most ports that use www/py-django42 to www/py-django52.

* Where necessary, remove PORTSCOUT, which is no longer needed because
  an update to a newer version that no longer supports Django 4.2 should
  now be possible.

* Bump PORTREVISION due dependency change where necessary.

PR:		291707
Reviewed by:	sunpoet (python)
Differential Revision:	https://reviews.freebsd.org/D56966

*: Revise USES=python:... version range constraints

and strip all lower bounds of 3.9 or 3.10 because they are implied now.

python:3.9-X  -> python:-X
python:3.9+   -> python
python:3.10-X -> python:-X
python:3.10+  -> python
(options such as ,build preserved)

www/py-django-cors-headers: Update to 4.9.0

* Switch to the more preferred DISTVERSION while I'm here.
Changelog since 4.7.0:

https://github.com/adamchainz/django-cors-headers/blob/4.9.0/CHANGELOG.rst

www/py-django-cors-headers: Update to 4.7.0

Changelog:

https://github.com/adamchainz/django-cors-headers/blob/4.7.0/CHANGELOG.rst

www/py-django-cors-headers: Update to 4.6.0

* Support for Python 3.8 was dropped with release 4.5.0, adjust
  USES=python accordingly.

Changelog since 4.3.1:

https://github.com/adamchainz/django-cors-headers/blob/4.6.0/CHANGELOG.rst

*: Switch consumers over to Django 4.2

Django 3.2 reached its End-of-Life on 1st April 2024 and Django 4.2 is
the new LTS (= Long Term Support) release which will be supported until
April 2026.

* Switch most ports that use www/py-django32 to www/py-django42.

* Ports that are not compatible with Django 3.2 have already been set
  with an expiration date were not taken into account.

* Bump PORTREVISION due dependency change where necessary.

PR:		276319
Reviewed by:	dvl, grembo, ultima
Approved by:	bofh (implicit), dvl, grembo, Kevin Golding, sunpoet,
		ultima, maintainer timeout (remaining maintainers)
Differential Revision:	https://reviews.freebsd.org/D44637

www/py-django-cors-headers: Update to 4.3.1

Changelog:

https://github.com/adamchainz/django-cors-headers/blob/4.3.1/CHANGELOG.rst

www/py-django-cors-headers: Update to 4.3.0

Changelog:

https://github.com/adamchainz/django-cors-headers/blob/4.3.0/CHANGELOG.rst

www/py-django-cors-headers: Update to 4.2.0

Changelog:

https://github.com/adamchainz/django-cors-headers/blob/4.2.0/CHANGELOG.rst

devel/py-setuptools: convert individual consumers to ${PY_SETUPTOOLS}

Currently a no-op, but in the future outputs the correct setuptools
port depending on whether USES_PYTHON=distutils is specified.

With hat: python
PR: 270510, 270358

all: remove explicit versions in USES=python for "3.x+"

The logic in USES=python will automatically convert this to 3.8+ by
itself.

Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.

finance/quickfix: mark BROKEN with PYTHON

libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++ -DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable -Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong -fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi -Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings -Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x -MT _quickfix_la-QuickfixPython.lo -MD -MP -MF .deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp  -fPIC -DPIC -o .libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
          ^~~~~~~~~~
1 warning and 1 error generated.

Reviewed by:	portmgr, vishwin, yuri
Differential Revision:	<https://reviews.freebsd.org/D40568>

www/py-django-cors-headers: Update to 4.1.0

Changelog:

https://github.com/adamchainz/django-cors-headers/blob/4.1.0/CHANGELOG.rst

www/py-django-cors-headers: Update to 4.0.0

Changelog:

https://github.com/adamchainz/django-cors-headers/blob/4.0.0/CHANGELOG.rst

USE_PYTHON=pep517: bump PORTREVISION

www/py-django-cors-headers: Update to 3.14.0

* Switch to PEP517 build framework.

Changelog:

https://github.com/adamchainz/django-cors-headers/blob/3.14.0/CHANGELOG.rst

MFH:		No (PEP517 support not present in 2023Q1 branch)

*/*: rename CHEESESHOP to PYPI in MASTER_SITES

PR:			267994
Differential revision:	D37518
Approved by:		bapt

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.

There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.

The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.

Approved by:		portmgr (tcberner)

www/py-django-cors-headers: Update to 3.13.0

Changelog since 3.11.0:

https://github.com/adamchainz/django-cors-headers/blob/3.13.0/HISTORY.rst

net-mgmt/netbox: Create Django 4.0 consumers

* Django 3.2 is currently the "default" version in the ports tree due
  its long term support until April 2024.  Thus ports that are assigned
  to that version will exist until then.

  The following ports are required to make the upgrade of
  net-mgmt/netbox to the 3.2 release possible because it requires Django
  4.0.

  All of the ports listed below were created on the basis of their
  respective original ports:

  - devel/py-dj40-django-rq
  - devel/py-dj40-graphene-django
  - www/py-dj40-django-auth-ldap
  - www/py-dj40-django-cors-headers
  - www/py-dj40-django-debug-toolbar
  - www/py-dj40-django-filter
  - www/py-dj40-django-graphiql-debug-toolbar
  - www/py-dj40-django-js-asset
  - www/py-dj40-django-mptt
  - www/py-dj40-django-prometheus
  - www/py-dj40-django-redis
  - www/py-dj40-django-tables2
  - www/py-dj40-django-taggit
  - www/py-dj40-django-timezone-field
  - www/py-dj40-djangorestframework
  - www/py-dj40-drf-yasg

* Simplify the related CONFLICTS_INSTALL entries as well.  This also
  reduces editing of the Makefiles if another ports need to be
  "repo-copied" (e.g. for Django 4.1) based on the original ports in the
  future. [1]

Reviewed by:	se [1], sunpoet
Differential Revision:	https://reviews.freebsd.org/D35444

www/py-django32: Switch consumers over to Django 3.2

Django 2.2 became End-of-Life on 11th April 2022 and Django 3.2 is the
new LTS (= Long Term Support) release which will be supported until
April 2024.

* Switch the most ports that use www/py-django22 to www/py-django32

* Switch www/seahub over to www/py-djangorestframework

* Ports that are not yet ready for Django 3.2 (only three so far) or
  those that have already been set with an expiration date were not
  taken into account.

* Bump PORTREVISION due dependency change where necessary.

PR:		261313
Reviewed by:	bofh, dvl, koobs, ultima
Approved by:	bofh, dvl, koobs, ultima, sunpoet, Kevin Golding, Ivan Rozhuk,
		Alexander Sieg (maintainers)
		maintainer timeout (remaining maintainers)
Differential Revision:	https://reviews.freebsd.org/D34859

www/py-django-cors-headers: Update to 3.11.0

Changelog:

https://github.com/adamchainz/django-cors-headers/blob/3.11.0/HISTORY.rst

www/py-django-cors-headers: Update to 3.10.1

Changelog:

https://github.com/adamchainz/django-cors-headers/blob/3.10.1/HISTORY.rst

MFH:		2022Q1

www/py-django-cors-headers: Update to 3.10.0

Changelog since 3.7.0:

https://github.com/adamchainz/django-cors-headers/blob/3.10.0/HISTORY.rst

*: Create Django 3.2 ports for net-mgmt/netbox

* Django 2.2 is currently the "default" version in the ports tree due
  its long term support until April 2022.  Thus ports that are assigned
  to that version will exist until then.

  The following ports are required to make the upgrade of
  net-mgmt/netbox to the 2.11 release possible because it requires
  Django 3.2.  All of the ports listed below were created on the basis
  of their respective original ports:

  - devel/py-dj32-django-rq
  - www/py-dj32-django-auth-ldap
  - www/py-dj32-django-cacheops (updated to a newer release)
  - www/py-dj32-django-cors-headers
  - www/py-dj32-django-debug-toolbar
  - www/py-dj32-django-filter
  - www/py-dj32-django-js-asset
  - www/py-dj32-django-mptt
  - www/py-dj32-django-prometheus
  - www/py-dj32-django-redis
  - www/py-dj32-django-tables2 (updated to a newer release)
  - www/py-dj32-django-taggit (updated to a newer release)
  - www/py-dj32-django-timezone-field
  - www/py-dj32-djangorestframework
  - www/py-dj32-drf-yasg

* Add/update the related CONFLICTS_INSTALL entries as well.

Reviewed by:	koobs, sunpoet
Differential Revision:	https://reviews.freebsd.org/D30977

One more small cleanup, forgotten yesterday. Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

www/py-django-cors-headers: Update to 3.7.0

Changelog since 3.5.0:

https://github.com/adamchainz/django-cors-headers/blob/3.7.0/HISTORY.rst

www/py-django-cors-headers: Update to 3.5.0

Changelog:

https://github.com/adamchainz/django-cors-headers/blob/3.5.0/HISTORY.rst

Create some ports that are assigned to Django 3.1 instead Django 2.2

* Django 2.2 is currently the "default" version in the ports tree due its
  long term support until April 2022.  Thus ports that are assigned to that
  version will exist until then.

  The following ports are required to make the upgrade of net-mgmt/netbox to
  the 2.9 release possible because it requires Django 3.1 and provides no
  backwards compatibility for previous versions of Django.

  - www/py-dj31-django-rq
      (copied from r539662 to use the 2.3.2 release for now)
  - www/py-dj31-django-auth-ldap
  - www/py-dj31-django-cacheops
  - www/py-dj31-django-cors-headers
  - www/py-dj31-django-debug-toolbar
  - www/py-dj21-django-filter
  - www/py-dj31-django-js-asset
  - www/py-dj31-django-mptt
  - www/py-dj31-django-prometheus
  - www/py-dj31-django-redis
  - www/py-dj31-django-tables2
  - www/py-dj31-django-taggit
  - www/py-dj31-django-timezone-field
  - www/py-dj31-djangorestframework
  - www/py-dj31-drf-yasg

* Also limit the new ports to Python 3.6+ due the requirements of Django 3.1
  and add/update the related CONFLICTS_INSTALL entries.

Reviewed by:	sunpoet
Differential Revision:	https://reviews.freebsd.org/D27083

www/py-django-cors-headers: Update to 3.4.0

* The upstream repository has moved, update the WWW field accordingly.

Changelog:

https://github.com/adamchainz/django-cors-headers/blob/3.4.0/HISTORY.rst

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

www/py-django-cors-headers: update to 3.1.1

www/py-django-cors-headers: update to 3.1.0

www/py-django-cors-headers: update to 3.0.2

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
* www/py-dj22-django-filter
* www/py-dj22-django-js-asset
* www/py-dj22-django-mptt
* www/py-dj22-django-tables2
* www/py-dj22-django-taggit-serializer
* www/py-dj22-django-timezone-field
* www/py-dj22-drf-yasg

[1] www/py-django-cors-headers was repocopied from r500510 to keep on the
    2.5.x branch as 3.x introduced some backward incompatibilities that
    haven't been fully tested, yet.

Changelog since 2.5.10:

Enhancements:

* Improve natural ordering of device components
* Add support for filtering cables by connected device
* Add decommissioning status for devices

Bug Fixes:

* Fix natural ordering of device components (after it has been improved
  before)
* Upgrade Django requirement to 2.2 to fix object deletion issue in the
  changelog middleware
* Preserve multiselect filter values when updating per-page count for list
  views
* Fix ordering of interface connections list by termination B name/device
* Fix tagged_items count in tags API endpoint
* Disable last_login update on login when maintenance mode is enabled

Reviewed by:	koobs, miwi
Differential Revision:	https://reviews.freebsd.org/D20103

www/py-django-cors-headers: update to 3.0.1

www/py-django-cors-headers: update to 3.0.0

www/py-django-cors-headers: update to 2.5.3

www/py-django-cors-headers: Update to 2.5.2

PR:		237564
Submitted by:	kai

Create some ports that are assigned to Django 2.1 instead Django 1.11.

Django 1.11 is currently the "default" version in the ports tree due its
long term support until April 2020 thus ports that are assigned to that
version will exist until then.

The following packages are required to make the upgrade of net-mgmt/netbox
to 2.5.x possible because upstream has decided to switch from Django 1.11
to Django 2.1:

* www/py-dj21-django-cors-headers
* www/py-dj21-django-debug-toolbar
* www/py-dj21-django-filter
* www/py-dj21-django-js-asset
* www/py-dj21-django-mptt
* www/py-dj21-django-tables2
* www/py-dj21-django-taggit
* www/py-dj21-django-timezone-field
* www/py-dj21-djangorestframework
* www/py-dj21-drf-yasg

Also limit the new ports to Python 3.5 and later to match the requirements
for Django 2.1 and to reduce some overhead in the building infrastructure.

Reviewed by:	miwi, tcberner (mentors)
Approved by:	miwi
Differential Revision:	https://reviews.freebsd.org/D19059

www/py-django-cors-headers: Update to 2.4.0

PR:		231086
Submitted by:	Kai <freebsd_ports@k-worx.org>

www/py-django-cors-headers: update to 2.3.0

www/py-django-annotations: switch to django 1.11

PR:		228229
Submitted by:	Kai <freebsd_ports@k-worx.org>
Approved by:	rene (devel/py-django-rq maintainer)

www/py-django-cors-headers: update to 2.2.0

Convert Python ports to FLAVORS.

Ports using USE_PYTHON=distutils are now flavored.  They will
  automatically get flavors (py27, py34, py35, py36) depending on what
  versions they support.

  There is also a USE_PYTHON=flavors for ports that do not use distutils
  but need FLAVORS to be set.  A USE_PYTHON=noflavors can be set if
  using distutils but flavors are not wanted.

  A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
  added to cope with Python ports that did not have the Python
  PKGNAMEPREFIX but are flavored.

  USES=python now also exports a PY_FLAVOR variable that contains the
  current python flavor.  It can be used in dependency lines when the
  port itself is not python flavored.  For example, deskutils/calibre.

  By default, all the flavors are generated.  To only generate flavors
  for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
  BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.

  In all the ports with Python dependencies, the *_DEPENDS entries MUST
  end with the flavor so that the framework knows which to build/use.
  This is done by appending '@${PY_FLAVOR}' after the origin (or
  @${FLAVOR} if in a Python module with Python flavors, as the content
  will be the same).  For example:

    RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}

PR:		223071
Reviewed by:	portmgr, python
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D12464

www/py-django-cors-headers: update to 2.1.0

www/py-django-cors-headers: create port

A Django App that adds CORS (Cross-Origin Resource Sharing) headers to
responses.

WWW: https://github.com/ottoyiu/django-cors-headers