For now, the immediate impact are difficult to root-cause-analyse warnings raised with koji/mock builds against Rawhide (F28?). Later on, the builds may fail completely (unless %__python -> %__python3). Fedora change related to the build environment should not interfere with this very environment. # rpm -q rpm-build redhat-rpm-config > rpm-build-4.14.1-8.fc28.x86_64 > redhat-rpm-config-105-1.fc29.noarch
> Fedora change related to the build environment should not interfere > with this very environment. (meant bidirectionally/mutually, indeed) And see also [bug 1506355], might be wise to limit infuence of environment variables etc. here as well.
We are aware of that. Workaround is to set __python to either python2 or python3 explicitly.
Added https://fedoraproject.org/wiki/Changes/Avoid_usr_bin_python_in_RPM_Build#Python_bytecompilation Do you have a specific example where this breaks the build? It shouldn't.
No breakage to report, just extrapolating the declared plan. And that warning was just slightly annoying when I was after what cases of plain python invocation I might have missed when fine-tuning clufter package as it invokes some python scripts in %build, sometimes even indirectly.
This should eventually be superseded by https://fedoraproject.org/wiki/Changes/No_more_automagic_Python_bytecompilation
Thanks, I now see that I should have been following https://fedoraproject.org/wiki/Packaging:Python_Appendix#Manual_byte_compilation for non-standard paths in the first place, as otherwise I am spreading Python 2 bytecode even when not desired. (Fixed in clufter now.)
See also https://pagure.io/packaging-committee/issue/755