[Bug 296649] lang/python3: port still depends on old python311. Is freebsd-python (Nobody) defunct?
- Reply: bugzilla-noreply_a_freebsd.org: "maintainer-feedback requested: [Bug 296649] lang/python3: port still depends on old python311. Is freebsd-python (Nobody) defunct?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 296649] lang/python3: port still depends on old python311. Is freebsd-python (Nobody) defunct?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 296649] lang/python3: port still depends on old python311. Is freebsd-python (Nobody) defunct?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 09 Jul 2026 19:12:34 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296649
Bug ID: 296649
Summary: lang/python3: port still depends on old python311. Is
freebsd-python (Nobody) defunct?
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: Individual Port(s)
Assignee: python@FreeBSD.org
Reporter: p5B2EA84B3@t-online.de
Assignee: python@FreeBSD.org
Flags: maintainer-feedback?(python@FreeBSD.org)
Obviously the mysterious maintainer "python@FreeBSD.org" missed to patch this
after upgrading to a new default Python version.
BTW which maintainers/committers belong to python@ as it references to
"Nobody"?
"Nobody" looks like a dispersion of responsibility.
We should really really stop this "Nobody" thing.
freebsd-python (Nobody) seems not to read "their" PRs as bug 296340 already
pointed to this problem days ago at 2026-06-28.
--
You are receiving this mail because:
You are the assignee for the bug.