[Bug 260741] security/py-gssapi: Update to 1.7.2

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741 --- Comment #4 from Guangyuan Yang --- (In reply to John W. O'Brien from comment #3) I understand. If it doesn't build against 3.11, IMO we should limit the upper bound - and I believe that you are already tracking the supported versions p

[Bug 260741] security/py-gssapi: Update to 1.7.2

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741 --- Comment #3 from John W. O'Brien --- (In reply to John W. O'Brien from comment #2) I take it back. This port does *not* build successfully against 3.11. I am working on updates to two different ports, and got this one confused with the

[Bug 260741] security/py-gssapi: Update to 1.7.2

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741 --- Comment #2 from John W. O'Brien --- (In reply to Guangyuan Yang from comment #1) Since this port builds successfully against 3.11.0a3, my preference is to omit an upper bound on the python version. Upstream is unlikely to make support

[Bug 260742] security/py-pycryptodome: Update to 3.12.0

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260742 John W. O'Brien changed: What|Removed |Added URL|https://github.com/Legrandi |https://github.com/Legrandi

[Bug 260742] security/py-pycryptodome: Update to 3.12.0

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260742 John W. O'Brien changed: What|Removed |Added Summary|security/py-pycryptodome: |security/py-pycryptodome:

[Bug 260741] security/py-gssapi: Update to 1.7.2

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741 Guangyuan Yang changed: What|Removed |Added CC||y...@freebsd.org Stat

[Bug 260742] security/py-pycryptodome: Update to 3.11.0

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260742 John W. O'Brien changed: What|Removed |Added Attachment #230475|0 |1 is obsolete|

[Bug 260742] security/py-pycryptodome: Update to 3.11.0

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260742 --- Comment #3 from John W. O'Brien --- (In reply to Daniel Engberg from comment #2) Thank you, @diizzy. I had figured that much out myself, and then spun in circles for a while until it dawned on me that I needed another "make makesum". C

[Bug 260644] multimedia/py-soco: Update to 0.25.2

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260644 Hiroki Tagato changed: What|Removed |Added Resolution|--- |FIXED Status|In Progre

[Bug 260644] multimedia/py-soco: Update to 0.25.2

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260644 --- Comment #7 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=29c87c781a97279355e2cf1b25f088c35d0c7887 commit 29c87c781a97279355e2cf1b25f088c35d0c7887 Author:

[Bug 260644] multimedia/py-soco: Update to 0.25.2

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260644 Hiroki Tagato changed: What|Removed |Added Assignee|ports-b...@freebsd.org |tagat...@freebsd.org S

[Bug 260742] security/py-pycryptodome: Update to 3.11.0

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260742 Daniel Engberg changed: What|Removed |Added CC||dii...@freebsd.org --- Comment #2

[Bug 260644] multimedia/py-soco: Update to 0.25.2

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260644 Conall O'Brien changed: What|Removed |Added Attachment #230431|0 |1 is obsolete|

[Bug 260742] security/py-pycryptodome: Update to 3.11.0

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260742 --- Comment #1 from John W. O'Brien --- I am aware that 3.12.0 has been released, but the project published source as zip instead of tar.gz, and my ports-fu has so far failed me. -- You are receiving this mail because: You are on the CC l

[Bug 260742] security/py-pycryptodome: Update to 3.11.0

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260742 John W. O'Brien changed: What|Removed |Added CC||python@FreeBSD.org

[Bug 260741] security/py-gssapi: Update to 1.7.2

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741 John W. O'Brien changed: What|Removed |Added Attachment #230474||maintainer-approval+

[Bug 260741] security/py-gssapi: Update to 1.7.2

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741 John W. O'Brien changed: What|Removed |Added CC||python@FreeBSD.org

[Bug 259981] devel/py-setuptools_scm: Fix incorrect *_DEPENDS, causing devel/py-pyparsing (and others) Fails to configure: The 'packaging>=20.0' distribution was not found

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259981 Kai Knoblich changed: What|Removed |Added Resolution|--- |FIXED Flags|maintainer

Ports with version numbers going backwards: devel/py-pytest, devel/py-pytest...

2021-12-27 Thread portmgr
** 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 Convention

[Bug 260704] devel/py-bidict: Update to 0.21.4, Remove BROKEN

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260704 William Grzybowski changed: What|Removed |Added Assignee|w...@freebsd.org |b...@freebsd.org

[Bug 260644] multimedia/py-soco: Update to 0.25.2

2021-12-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260644 Li-Wen Hsu changed: What|Removed |Added CC||lw...@freebsd.org --- Comment #5 from