[opensuse-buildservice] python3 macros broken on CentOS_7
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... https://build.opensuse.org/packages/python3-imbox/job_history/home:sebix:int... I guess that this is a configuration error, but I am not sure where (and by whom) this can be fixed. Sebastian
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
On 09/05/2019 03.14, Julio González Gil wrote:
Seems to me you are maybe affected by: https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproj...
Thanks! That was it. And in March they announced the final switch to 3.6: https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproj... I thought that the macros are wrong, and did not think of the possibility that EPEL would actually change it's python version.
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: Yeah, it is not so easy to get the specfiles compatible with openSUSE, Fedora and CentOS as CentOS uses a different naming scheme for packages and binaries. 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:
I now did it the other way round and switched the macros to Python 3.6, but now RHEL_7 has a problem :/ Sebastian
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
On Thu, May 9, 2019 at 6:41 AM Sebastian <sebix@sebix.at> wrote:
On 09/05/2019 03.14, Julio González Gil wrote:
Seems to me you are maybe affected by: https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproj...
Thanks! That was it. And in March they announced the final switch to 3.6:
https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproj...
I thought that the macros are wrong, and did not think of the possibility that EPEL would actually change it's python version.
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: Yeah, it is not so easy to get the specfiles compatible with openSUSE, Fedora and CentOS as CentOS uses a different naming scheme for packages and binaries. 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:
I now did it the other way round and switched the macros to Python 3.6, but now RHEL_7 has a problem :/
Well, this should hopefully get simpler after this is done: https://bugzilla.redhat.com/show_bug.cgi?id=1639030 -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi Neal, On 09/05/2019 12.43, Neal Gompa wrote:
On Thu, May 9, 2019 at 6:41 AM Sebastian <sebix@sebix.at> wrote:
[...] but now RHEL_7 has a problem :/ Well, this should hopefully get simpler after this is done: https://bugzilla.redhat.com/show_bug.cgi?id=1639030
I'm not sure. The problem I have is: nothing provides libcrypto.so.10(OPENSSL_1.0.2)(64bit) needed by python36-libs Where python36-libs is from EPEL. Sebastian
On Thu, May 9, 2019 at 6:48 AM Sebastian <sebix@sebix.at> wrote:
Hi Neal,
On 09/05/2019 12.43, Neal Gompa wrote:
On Thu, May 9, 2019 at 6:41 AM Sebastian <sebix@sebix.at> wrote:
[...] but now RHEL_7 has a problem :/ Well, this should hopefully get simpler after this is done: https://bugzilla.redhat.com/show_bug.cgi?id=1639030
I'm not sure. The problem I have is:
nothing provides libcrypto.so.10(OPENSSL_1.0.2)(64bit) needed by python36-libs
Where python36-libs is from EPEL.
Is the RHEL_7 target actually refreshed with latest RHEL 7 content? Because if it isn't, of course it'll break, because at the minimum, there was an OpenSSL rebase recently to OpenSSL 1.0.2. -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi, On 09/05/2019 12.51, Neal Gompa wrote:
On Thu, May 9, 2019 at 6:48 AM Sebastian <sebix@sebix.at> wrote:
Hi Neal,
On 09/05/2019 12.43, Neal Gompa wrote:
On Thu, May 9, 2019 at 6:41 AM Sebastian <sebix@sebix.at> wrote:
[...] but now RHEL_7 has a problem :/ Well, this should hopefully get simpler after this is done: https://bugzilla.redhat.com/show_bug.cgi?id=1639030 I'm not sure. The problem I have is:
nothing provides libcrypto.so.10(OPENSSL_1.0.2)(64bit) needed by python36-libs
Where python36-libs is from EPEL.
Is the RHEL_7 target actually refreshed with latest RHEL 7 content? Because if it isn't, of course it'll break, because at the minimum, there was an OpenSSL rebase recently to OpenSSL 1.0.2. I had no idea that something like that is necessary, how can that be done?
Hi, On 09/05/2019 12.56, Sebastian wrote:
Hi,
On 09/05/2019 12.51, Neal Gompa wrote:
On Thu, May 9, 2019 at 6:48 AM Sebastian <sebix@sebix.at> wrote:
Hi Neal,
On 09/05/2019 12.43, Neal Gompa wrote:
On Thu, May 9, 2019 at 6:41 AM Sebastian <sebix@sebix.at> wrote:
[...] but now RHEL_7 has a problem :/ Well, this should hopefully get simpler after this is done: https://bugzilla.redhat.com/show_bug.cgi?id=1639030 I'm not sure. The problem I have is:
nothing provides libcrypto.so.10(OPENSSL_1.0.2)(64bit) needed by python36-libs
Where python36-libs is from EPEL.
Is the RHEL_7 target actually refreshed with latest RHEL 7 content? Because if it isn't, of course it'll break, because at the minimum, there was an OpenSSL rebase recently to OpenSSL 1.0.2. I had no idea that something like that is necessary, how can that be done?
Does someone know how to do that? Sebastian
participants (4)
-
Julio González Gil -
Neal Gompa -
Sebastian -
Sebix