Ports with version numbers going backwards: devel/py-pytest, devel/py-pytest...
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. The ports tree was updated at Thu Aug 26 2021 12:30:00 UTC. - *devel/py-pytest* : py38-pytest-4.6.11 < py38-pytest-6.2.4 - *devel/py-pytest-flask* : py38-pytest-flask-0.15.1 < py38-pytest-flask-1.2.0 - *devel/py-pytest-translations* : py38-pytest-translations-2.0.0 < py38-pytest-translations-3.1.0 - *devel/py-pytest-xdist* : py38-pytest-xdist-1.32.0 < py38-pytest-xdist-2.3.0 - *x11/xdotool* : xdotool-3.20210804.2 < xdotool-3.20160805.1,1
[Bug 257131] [NEW PORT] devel/py-cadquery-pywrap: C++ binding generator for Python
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257131 Neal Nelson changed: What|Removed |Added Attachment #226459|0 |1 is obsolete|| Attachment #227451||maintainer-approval+ Flags|| --- Comment #5 from Neal Nelson --- Created attachment 227451 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=227451&action=edit Git diff of new port. - Fixed all the hard coded file roots. Sorry about that. - Updated category and USES. - Serendipitously upstream has removed the Jinja version requirement as it was nonsense. Unsurprisingly the version in ports works fine. Everything worked fine before though. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 257131] [NEW PORT] devel/py-cadquery-pywrap: C++ binding generator for Python
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257131 Neal Nelson changed: What|Removed |Added Flags|maintainer-feedback?(ports@ |maintainer-feedback+ |nicandneal.net) | -- You are receiving this mail because: You are on the CC list for the bug.