Date: Mon, 15 Jul 2024 21:06:47 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 280298] net/miniupnpc: in 2.2.8 changed API for UPNP_GetValidIGD: build error net-p2p/transmission-components and other Message-ID: <bug-280298-7788-UTvgpr99DN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280298-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-280298-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280298 --- Comment #16 from Anton Saietskii <vsasjason@gmail.com> --- (In reply to Stefan Ehmann from comment #8) Obviously, maintainer of net-p2p/transmission components can't approve patch for games/0ad, so the first guess would be separate PRs for each broken port (with 'See Also' here as earliest PR). However, some time ago there was a similar breakage with net-p2p/tremotesf which is maintained by me. The committer (and change author) reported issue= to upstream and did other required stuff to make my port (and probably others affected) build again. But current breakage requires change not in miniupnpc, but rather all or at least some of ports depend on it. Perhaps dinoex@ as a committer whose chan= ge caused this can be politely asked to check dependent ports (and fix them?), however I'm unaware of policies to process such situations, and unsure if my guess of asking that is correct. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280298-7788-UTvgpr99DN>