Date: Fri, 31 May 2019 06:06:10 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 238254] print/harfbuzz: Build fails due to undeclared bogus dependency on lang/python36 Message-ID: <bug-238254-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238254 Bug ID: 238254 Summary: print/harfbuzz: Build fails due to undeclared bogus dependency on lang/python36 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: terry-freebsd@glaver.org CC: gnome@FreeBSD.org, python@FreeBSD.org CC: gnome@FreeBSD.org, python@FreeBSD.org Attempting to update a 12-STABLE (amd64) system to the latest version of ports, but retaining python 2.7 as the default via "DEFAULT_VERSIONS+=python=2.7" in /etc/make.conf fails during the build phase with the error "env: /usr/local/bin/python3.6: No such file or directory". Looking at the change history for the port, it doesn't seem as though this was a change in the harfbuzz port itself, but a result of the Python default version change having (yet another*) unexpected impact. Due to non-response to other reports about the Python change, I'm reporting this bug against harfbuzz as it should be possible for this port to override whatever is causing the issue. * I won't repeat my rants about the ill-advised change to 3.6 as the default, other than to point to https://wiki.freebsd.org/Python/Python3Default which shows a large number of ports incompatible with 3.x which were not addressed before the default version was changed. -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238254-21822>