https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741
Guangyuan Yang changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741
--- Comment #6 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=05b7e3cafd96d3f91ef928be712ead113bc7e445
commit 05b7e3cafd96d3f91ef928be712ead113bc7e445
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741
Guangyuan Yang changed:
What|Removed |Added
Assignee|ports-b...@freebsd.org |y...@freebsd.org
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741
John W. O'Brien changed:
What|Removed |Added
Attachment #230474|0 |1
is obsolete|
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
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
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741
Guangyuan Yang changed:
What|Removed |Added
CC||y...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741
John W. O'Brien changed:
What|Removed |Added
Attachment #230474||maintainer-approval+
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260741
John W. O'Brien changed:
What|Removed |Added
CC||python@FreeBSD.org
10 matches
Mail list logo