databases/py-ormar0.23.1

databases/py-ormar: Add CPE information

databases/py-ormar: Security update 0.21.0 => 0.23.1

Changelogs:
* https://github.com/ormar-orm/ormar/releases/tag/0.22.0
* https://github.com/ormar-orm/ormar/releases/tag/0.23.0
* https://github.com/ormar-orm/ormar/releases/tag/0.23.1

PR:		294382
Reported by:	Goran Mekić <meka@tilda.center> (maintainer)
Approved by:	osa (mentor)
MFH:		2026Q2
Security:	CVE-2026-26198
Security:	CVE-2026-27953

databases/py-ormar: Update 0.20.2 => 0.21.0

Changelog:
https://github.com/collerek/ormar/releases/tag/0.21.0

PR:	292295

databases/py-ormar: Update 0.20.1 => 0.20.2

Changelog:
https://github.com/collerek/ormar/releases/tag/0.20.2

Pet portclippy.

PR:	286388

databases/py-ormar: Use USE_PYTHON=cryptography instead of direct dependency

PR:	282065

databases/py-ormar: Fix incorrect py-poetry* usage

Approved by:	portmgr (blanket)
With hat:	python

databases/py-ormar: update 0.20.0 → 0.20.1

Changelog:
https://github.com/collerek/ormar/releases/tag/0.20.1

PR:	280372

databases/py-ormar: Update to 0.20.0

ChangeLog:	https://github.com/collerek/ormar/releases/tag/0.20.0
PR:		278070

devel/py-pydantic: bump PORTEPOCH

databases/py-ormar: Update to 0.12.2

Changelog: https://github.com/collerek/ormar/releases/tag/0.12.2

PR:		273016

*: Replace USES=pycryptography* with USE_PYTHON=cryptography{,_build,_test}

- Introduce USE_PYTHON=cryptography{,_build,_test}
- Switch all 96 ports from USES=pycryptography to with USE_PYTHON=cryptography{,_build,_test}
- Remove Mk/Uses/pycryptography.mk

PR:		273727
Approved by:	tcberner (portmgr)
Exp-run by:	antoine

framework: convert tree to use USES=pycryptography

A future commit will update to security/py-cryptography will introduce a
rust dependency.

PR:		254853

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>

databases/py-ormar: Update to 0.12.1

Changelog: https://github.com/collerek/ormar/releases/tag/0.12.1

PR:	269507

*/*: rename CHEESESHOP to PYPI in MASTER_SITES

PR:			267994
Differential revision:	D37518
Approved by:		bapt

databases/py-ormar: Update to 0.12.0

Changelog:	https://github.com/collerek/ormar/releases/tag/0.12.0

PR:		267602

databases/py-ormar: Bump pydantic version in RUN_DEPENDS

- Fix fallout by bumping pydantic version in RUN_DEPENDS
 - Bump PORTREVISION

PR:		266533

databases/py-ormar: Update to 0.11.3

Changelog: https://github.com/collerek/ormar/releases/tag/0.11.3

PR:	266376

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)

databases/py-ormar: Update to 0.11.2

ChangeLog: https://github.com/collerek/ormar/releases/tag/0.11.2

PR:		265013

databases/py-ormar: Update to 0.11.1

ChangeLog: https://github.com/collerek/ormar/releases/tag/0.11.1

PR:		264608

databases/py-ormar: Adjust dependencie

- adjust dependencie to latest databases/py-databases version

PR:		264516

databases/py-ormar: Update to 0.11.0

Changes: https://github.com/collerek/ormar/releases/tag/0.11.0

PR:	263554

databases/py-ormar: Update to 0.10.25

Changelog:	https://github.com/collerek/ormar/releases/tag/0.10.25

PR:		262313

databases/py-ormar: update to 0.10.24

While here, loosen version ranges of some dependencies to avoid build
error.

PR:		261190
Reported by:	Goran Mekić <meka@tilda.center> (maintainer)
Reviewed by:	koobs

databases/py-ormar: add port: Simple async ORM with fastapi in mind and pydantic validation

The ormar package is an async mini ORM for Python, with support for Postgres,
MySQL, and SQLite.

The main benefit of using ormar are:
* getting an async ORM that can be used with async frameworks (fastapi,
  starlette etc.)
* getting just one model to maintain - you don't have to maintain pydantic and
  other orm model (sqlalchemy, peewee, gino etc.)

The goal was to create a simple ORM that can be used directly (as request and
response models) with fastapi that bases it's data validation on pydantic.

WWW: https://github.com/collerek/ormar

PR:		257370
Reported by:	Goran Mekić <meka@tilda.center> (new maintainer)
Reviewed by:	koobs