Date: Thu, 09 Apr 2026 09:07:34 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 270358] devel/py-setuptools: update to 81.0.0 Message-ID: <bug-270358-21822-VdClA2F6zm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-270358-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=270358 --- Comment #151 from Charlie Li <vishwin@freebsd.org> --- (In reply to Kevin Bowling from comment #150) Because this is anything but standard. Highly unusual, even. Here is my last full run on only USE_PYTHON=distutils: https://people.freebsd.org/~vishwin/2026-03-18_18h03m52s/ however there has been churn since then. Even on just this portion, ie not including USE_PYTHON=pep517 although some are also built as dependencies of the USE_PYTHON=distutils items, the errors do not fall under any similar category. These include bad version metadata, extension module compile errors, pre-existing breakages, non-Python dependencies failing, etc etc. I've been re-running the USE_PYTHON=distutils portion incrementally, as in using the repository of successfully built ports per run (compared to clearing everything). Doing any build run is extremely time- and resource-consuming. I'm trying to figure out how to reduce this with package fetching, however for operational reasons on my end it has to run on -CURRENT. -- 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-270358-21822-VdClA2F6zm>