Date: Wed, 25 Dec 2019 13:24:56 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: "Montgomery-Smith, Stephen" <stephen@missouri.edu> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: XXX needs Python 3.4 at least, but 2.7 was specified Message-ID: <20191225212456.GA53727@troutmask.apl.washington.edu> In-Reply-To: <771433ef-9fe6-a8fa-a5de-a3f9cee7e5f8@missouri.edu> References: <1fe096e1-30e8-7739-3cbd-3575e32fbe18@utanet.at> <9a97aecf-a50e-e16a-a222-ea7844245e28@utanet.at> <9b0c65a4-07ad-9743-687a-81ec0b1d36ee@druid.net> <DD6313B0-7AE6-43DD-B6A5-2E532869C6D6@lastsummer.de> <771433ef-9fe6-a8fa-a5de-a3f9cee7e5f8@missouri.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 25, 2019 at 07:05:50PM +0000, Montgomery-Smith, Stephen wrote: > > I agree with Franco. I am surprised that this error has been known for > so long, and not fixed, when at least one effective solution exists. > Surely, you're joking. It took more than 2 years to get a 2-line patch to the python committed, and AFAICT, the commit was done by portmgr instead python@. https://lists.freebsd.org/pipermail/freebsd-ports/2019-December/117300.html https://lists.freebsd.org/pipermail/svn-ports-all/2019-December/235695.html -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191225212456.GA53727>