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-b...@freebsd.org
Reporter: terry-free...@glaver.org
CC: gn...@freebsd.org, pyt...@freebsd.org
CC: gn...@freebsd.org, pyt...@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.
_______________________________________________
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
