Please note that we have two different issues here, with different solutions:
- Packages using an embedded waf: as the upstream waf script uses a
shebang like '#! /usr/bin/env python', these packages fail due to the
removal of the unversioned Python binary and should call their waf
copy using one of the %{__python2} or %{__python3} macros, and BR on
python2-devel or python3-devel to get the macros.
- Packages using the system-wide waf script in the Python3 variant
(note that waf is using alternatives, so /usr/bin/waf can be either
using Python2 or Python3, depending on the declared BRs): these will
currently fail in rawhide, as the version in rawhide is not fully
Python3-compatible, which will be fixed soon.
(Of course packages using embedded waf, and calling it via
%{__python3} will likely also see the second issue, and should simply
update their embedded waf script.)
2018-07-23 12:55 GMT+02:00 Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl>:
> Please don't recommend that. Instead of munging all packages that use
> waf, waf should be fixed. In the other thread the maintainer said they
> can do it next week. If more speed is needed, prepare a PR in src.fp.o
> and maybe have a provenpackager push the build.
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/SONWVTWZTYIINDPK33IQ6MLVX6227PHF/
