sysutils/py-docker 7.2.0

sysutils/py-docker: Update to 7.2.0

ChangeLog:	https://github.com/docker/docker-py/releases/tag/7.2.0
Approved by:	hrs (mentor, blanket)

security/libsodium: Update to 1.0.21

The API remains compatible but bumping all dependent ports as SHLIB
has changed.

Changelog: https://github.com/jedisct1/libsodium/releases/tag/1.0.21-RELEASE
Security: https://00f.net/2025/12/30/libsodium-vulnerability/
PR: 279347

sysutils/py-docker: Fix build error

Approved by:	hrs (mentor, blanket)

sysutils/py-docker: Update to 7.1.0

ChangeLog:	https://github.com/docker/docker-py/compare/7.1.3...6.1.3
Approved by:	hrs (mentor, blanket)

security/libsodium: update to 1.0.19, bump dependent ports

PR:	278259
Reported by:	Andrey Korobkov <alster-vinterdalen.se>

devel/py-setuptools-scm: update to 8.0.4

Directory and PORTNAME changed to match normalised name in release
tarball; consumers updated to match.

Although setuptools itself is specified as a run dependency in the
Python package metadata, it is currently left out here to prevent
environment pollution until at least PR 270510 is committed.
Additionally, this version of setuptools-scm requires setuptools>=61,
which means this version is only meant for USE_PYTHON=pep517 ports
as all USE_PYTHON=distutils ports will switch to devel/py-setuptools58
also after PR 270510. science/py-emmet-core is switched to
devel/py-setuptools_scm7 accordingly, as it specifies setuptools-scm<8.
devel/py-{flit-scm,hatch-vcs} have ${PY_SETUPTOOLS} added to
RUN_DEPENDS to compensate.

Further details: https://wiki.freebsd.org/Python/setuptools

Reported by: yuri
Co-authored by: matthew
Exp-run by: antoine (earlier iteration)
Approved by: yuri (science/py-emmet-core, previous iteration)
PR: 272134
Differential Revision: https://reviews.freebsd.org/D39288

sysutils/py-docker: Update to 6.1.3

PR:		275494
Reported by:	wen@(via email)
Approved by:	maintainer

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>

USE_PYTHON=pep517: bump PORTREVISION

sysutils/py-docker: Change MAINTAINERship to myself

Approved by: hrs (mentor)

Revert "Mk/Uses/python.mk: Fix USE_PYTHON=pep517: always compile and install bytecode"

Despite installer's default behaviour to compile and install bytecode,
we are not doing so going forward at stage/package time. [0] During
initial development and qualification of PEP-517 framework support,
compiling and installing bytecode at stage/package time was considered,
but was found problematic, fragile and ultimately unreliable, both
currently and historically (with USE_PYTHON=distutils), due to our
fixed plist requirement. While the living binary distribution format
(wheel) specification [1] says to compile bytecode, that is in the
pure Python package management context (pip, etc); nuance always
exists when interacting with "system" package management.

Additionally, "bytecode is an implementation detail of the CPython
interpreter. No guarantees are made that bytecode will not be added,
removed, or changed between versions of Python," thus "should not
be considered to work across Python VMs or Python releases." [2]
This is important to ensuring correctness for those ports specifying
NO_ARCH.

Instead of compiling and installing bytecode at stage/package time,
there is a WIP, review D34739, that compiles and installs bytecode
at install time instead, using triggers.

The aforementioned build_fs_violations will be investigated.

This reverts commit de6965254c3a007efcf697c3d455b54d2aeb2383.

With hat:	python
Approved by:	tcberner (mentor, portmgr)
Reference:	https://wiki.freebsd.org/Python/PEP-517 [0]
		https://packaging.python.org/en/latest/specifications/binary-distribution-format/ [1]
		https://docs.python.org/3/library/dis.html [2]

Mk/Uses/python.mk: Fix USE_PYTHON=pep517: always compile and install bytecode

- While I'm here, use long options for easier reading [1][2]
- Bump PORTREVISION of dependent ports (USE_PYTHON=pep517) for package change

It fixes build_fs_violation of dependent ports in poudriere (with -t flag).
It is also the default behavior of installer [2].

from py-sphinx log:
=>> Checking for staging violations... done
=>> Error: Filesystem touched during stage (files must install to ${STAGEDIR}):
extra: usr/local/lib/python3.9/site-packages/importlib_metadata/__pycache__
=>> Cleaning up wrkdir

from installer documentation:
--compile-bytecode
    Possible choices: 0, 1, 2
    generate bytecode for the specified optimization level(s) (default=0, 1)
--no-compile-bytecode
    don’t generate bytecode for installed modules
    Default: False

With hat:	python
Reference:	https://pypa-build.readthedocs.io/en/stable/ [1]
		https://installer.pypa.io/en/stable/cli/installer/ [2]

sysutils/py-docker: Adopt/Update to 6.0.1

- Submitter becomes maintainer
 - Switch to pep517 build

ChangeLog:	https://github.com/docker/docker-py/compare/5.0.3...6.0.1
PR:		266681

*/*: rename CHEESESHOP to PYPI in MASTER_SITES

PR:			267994
Differential revision:	D37518
Approved by:		bapt

sysutils/py-docker: Release maintainership

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)

sysutils/py-docker: Update to 5.0.3

Changelog:	https://github.com/docker/docker-py/releases/tag/5.0.3

sysutils/py-docker: Update to 5.0.2

Changelog:	https://github.com/docker/docker-py/releases/tag/5.0.2

sysutils/py-docker: Update to 5.0.0 and take maintainership

Approved by:	lwhsu (mentor)

*: reset lifanov's ports after safekeeping their ports bit.

Hat:	portmgr-secretary

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

Remove # $FreeBSD$ from Makefiles.

Simplify ports using PYTHON_SUFFIX and Python 3.6+

Remove empty PY_IPADDRESS from ports using Python 3.6+

Also remove one manual declaration (net-mgmt/py-aggregate6)

Drop python 2.7 support from a few ports

With hat:	portmgr

- Update to 3.7.0 - Unbreak

Submitted by:	Kevin Day <kevin@your.org>

Use PY_FLAVOR for dependencies.

FLAVOR is the current port's flavor, it should not be used outside of
this scope.

Sponsored by:	Absolight

Simplify Makefile: use PY_IPADDRESS

- Add NO_ARCH

With hat:	python

update sysutils/py-docker to 2.7.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

update sysutils/py-docker to 2.6.1

update sysutils/py-docker to 2.5.1

update sysutils/py-docker to 2.5.0

update sysutils/py-docker to 2.4.2

This contains a couple of bugfixes.

update sysutils/py-docker to 2.4.0

Changes: https://github.com/docker/docker-py/releases/tag/2.4.0

update sysutils/py-docker to 2.3.0

Changelog: https://github.com/docker/docker-py/releases/tag/2.3.0

fix sysutils/py-docker: uses pip in setup.py

Reported by:	pkg-fallout

add sysutils/py-docker: Docker SDK for Python