[Midnightbsd-cvs] [MidnightBSD/mports] 82c240: mail/py-email-validator: update to 2.3.0 (#711)

[Lucas Holt]

  Branch: refs/heads/master
  Home:   https://github.com/MidnightBSD/mports
  Commit: 82c240c54d7572b5f7311a5735010469e8d8b2b7
      https://github.com/MidnightBSD/mports/commit/82c240c54d7572b5f7311a5735010469e8d8b2b7
  Author: Lucas Holt <luke at foolishgames.com>
  Date:   2026-08-09 (Sun, 09 Aug 2026)

  Changed paths:
    M mail/py-email-validator/Makefile
    M mail/py-email-validator/distinfo

  Log Message:
  -----------
  mail/py-email-validator: update to 2.3.0 (#711)

Update `mail/py-email-validator` from 2.1.0 to 2.3.0, and correct the
license.

## LICENSE correction — CC0-1.0 → unlicense

The port declared `LICENSE= CC0-1.0`, but 2.3.0's `setup.cfg` says
`license = Unlicense`, `PKG-INFO` says `License: Unlicense` /
`Classifier: License :: OSI Approved :: The Unlicense`, and the
`LICENSE` file is verbatim Unlicense text ("This is free and
unencumbered software released into the public domain") — not CC0.
mports has a valid `unlicense` identifier
(`Mk/components/licenses.db.mk:392`). `bmake check-license` passes.

FreeBSD also carries `CC0-1.0`, which suggests the error is
long-standing rather than introduced at 2.3.0 — but that's inference:
the 2.1.0 distfile is no longer in `Distfiles/`, so it couldn't be
verified against the old metadata.

Because this port uses `autoplist`, the license identifier is part of
the packing list (`share/licenses/py312-email-validator-2.3.0/CC0-1.0` →
`unlicense`), so this is a real plist change. Verified after a clean
rebuild: the staged catalog reads `_LICENSE=unlicense` and the installed
license file is named `unlicense`.

## Version bump

**No build-backend change.** 2.3.0 does add a `pyproject.toml`, but it
contains only `[tool.mypy]` and `[tool.pytest.ini_options]` — no
`[build-system]` — and the real metadata still lives in `setup.cfg` with
`setup.py` present. So this remains a setuptools build; `USE_PYTHON=
autoplist concurrent distutils` stays and no `${PY_SETUPTOOLS}` is
needed. FreeBSD reached the same conclusion at this version.

**Dependencies unchanged.** Both origins exist and `bmake missing` was
empty.

**Verification:** makesum/build/fake/package all OK →
`py312-email-validator-2.3.0.mport`. distinfo matches FreeBSD
byte-for-byte. No `files/` dir. amd64 only; no `TEST_TARGET` defined.

## Noted, not changed

Upstream raised its floor to `dnspython>=2.0.0` while the port (and
FreeBSD) still declares `>=1.15.0`. Not a practical hazard —
`dns/py-dnspython` is at 2.8.0, so the stale floor is unreachable in
this tree. Tightening it would be a correctness improvement but is a
separate maintainer call.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

## Summary by Sourcery

Update the py-email-validator port to the latest upstream release and
correct its recorded license.

Build:
- Bump DISTVERSION from 2.1.0 to 2.3.0 and drop PORTREVISION for the
mail/py-email-validator port.

Chores:
- Correct the port's license metadata from CC0-1.0 to unlicense,
updating the installed license identifier accordingly.

Signed-off-by: Lucas Holt <luke at foolishgames.com>



To unsubscribe from these emails, change your notification settings at https://github.com/MidnightBSD/mports/settings/notifications