Date: Tue, 21 Apr 2026 23:14:24 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 294629] Staging (some) installed Python ports fails in Uses/uniquefiles.mk Message-ID: <bug-294629-21822-T5NmMIMKLq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-294629-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294629 --- Comment #7 from Chad Jacob Milios <milios@ccsys.com> --- this doesnt only happen when "it" is already installed, but happens when "any flavor of it" is currently installed to the system (i think; i have only been concerned with py312-* and py311-*) furthermore, when staging the two ive found susceptible so far (py-build & py-wheel), whether i build @py311 or @py312, upon reaching the error/stop, ${STAGEDIR}/bin is populated with foo-3.12 regardless of FLAVOR and/or DEFAULT_VERSIONS, yet, its shebang line is correctly versioned (#!/.../python3.11 appears atop foo-3.12 when FLAVOR=py311) i wonder if the problem actually stems from the recently commited py-installer 1.0.x becoming too "clever" and "helpful" for our purposes, since we have our own way of dealing with these system namespace conflicts, i.e. ${STAGEDIR} and Uses/uniquefiles.mk just a hunch. that's where i'm at right now but alas i have a dinner i must attend. praying this is fixed by the time i return lol godspeed fellas -- You are receiving this mail because: You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-294629-21822-T5NmMIMKLq>