https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Comment #17 from Mina Galić ---
bumping this bug because it hasn't seen a reply in 3 months,
because I just stumbled over bug 267648, which does basically the same thing,
and now I'm wondering if I should've modelled my netlink patches
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
Mina Galić changed:
What|Removed |Added
Attachment #244076|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Comment #15 from Matthias Andree ---
I am not a member of portmgr@. But I still feel, as a long-time FreeBSD
committer, that there is a certain amount of obstructionism going on here that
annoys me, in the form of requiring meena to ju
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Comment #14 from Charlie Li ---
(autotools) configure patches, against the generated-by-autoconf output, are
unwieldy by default; this is no exception. The existing local as in ${PATCHDIR}
patch against configure deals with LTO support,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
Dave Cottlehuber changed:
What|Removed |Added
CC||d...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
Matthias Andree changed:
What|Removed |Added
CC||mand...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Comment #11 from Charlie Li ---
(In reply to Mina Galić from comment #10)
Just close the pull requests yourself "immediately" after creation. No harm no
foul, I've done it myself, albeit not as immediately and after triage
(issue/pull r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Comment #10 from Mina Galić ---
(In reply to Charlie Li from comment #9)
> Python upstream brought this upon themselves. In many other software
> projects, this would be a bug fix, not a new feature. If anyone there cares
> enough …
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Comment #9 from Charlie Li ---
We've done this with at least earlier iterations of graphics/mesa{,-devel}, and
it all works as intended. It's not just about keeping track, but ensuring that
everything is applied in the correct order, an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
Daniel Engberg changed:
What|Removed |Added
CC||dii...@freebsd.org
--- Comment #8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Comment #7 from Joseph Mingrone ---
(In reply to Charlie Li from comment #6)
I get what you are asking for now, but are all these hoops to jump through
necessary. Mina's proposed changes overlap by one line in one file
(configure)? C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Comment #6 from Charlie Li ---
(In reply to Mina Galić from comment #4)
It's not a mystery if you comment the URL of the upstream issue in the
${PATCHFILES} line. The commit also lists the original issue. If you are that
worried, create
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
Joseph Mingrone changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Comment #4 from Mina Galić ---
it makes no sense to use
https://github.com/python/cpython/commit/eaa3bd080ef2299cbe614c348e3b8fdfacb66b48
in ${PATCH_SITES}/${PATCHFILES}
as GitHub says:
> This commit does not belong to any branch on t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Comment #3 from Charlie Li ---
You need to redo the existing ${PATCHDIR} patches on top of your stuff accepted
upstream.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Comment #2 from Mina Galić ---
i would've done that, if it applied.
The only branch it applies on is 3.12, and we don't currently have a port for
that.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
Charlie Li changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
Bug ID: 273122
Summary: lang/python311: backport netlink support
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severit
Bugzilla Automation has asked freebsd-python (Nobody)
for maintainer-feedback:
Bug 273122: lang/python311: backport netlink support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122
--- Description ---
this patch backports GH-107812: extend socket's netlink support to FreeBSD
see
19 matches
Mail list logo
