Seems to me you are maybe affected by: https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproj...
After a small timeframe (not determined how long yet), the macros will change and python36 will be the main python3 in EPEL.
As at the prjconfig you are forcing python34, that could explain it: https://build.opensuse.org/project/prjconf/home:sebix:intelmq
%if 0%{?rhel_version} || 0%{?centos_version} Substitute: python3 python34 (and a lot of other substitutions)
Do you really need to force 3.4 for your packages? If so, I am not 100% sure, but maybe if you define %python3_pkgversion at the prjconfig to be 34, your problem will be fixed: https://fedoraproject.org/wiki/PackagingDrafts:Python3EPEL#Example_Spec On miércoles, 8 de mayo de 2019 19:20:02 (CEST) Sebix wrote:
Dear list,
On my CentOS_7 builds on build.opensuse.org the %python3_sitelib/%python3_sitearch macros do not work anymore:
-bash-4.2$ rpmspec -E '%python3_sitelib' sh: /usr/bin/python3.6: No such file or directory
-bash-4.2$ rpmspec -E '%python3_sitearch' sh: /usr/bin/python3.6: No such file or directory
The correct binary would be python3.4
In the job history I see that there was a meta change at April 04, 2019 18:58 and the builds failed from this time on, e.g.: https://build.opensuse.org/packages/python3-psutil/job_history/home:sebix:in telmq/CentOS_7/x86_64 https://build.opensuse.org/packages/python3-imbox/job_history/home:sebix:in telmq/CentOS_7/x86_64
I guess that this is a configuration error, but I am not sure where (and by whom) this can be fixed.
Sebastian
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com