In CloudSIG, we can't install python3 package when building package against cloud7-openstack-* targets on CBS.
cloud7-openstack-*
From https://cbs.centos.org/koji/taskinfo?taskID=1938110 see below the error:
--> python3-3.6.8-18.el7.x86_64 Error: Package: python3-3.6.8-18.el7.x86_64 (build) Requires: python3-pip You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
Though, it's working locally with mock.
I created a testing package with only /usr/bin/python3 as BR to reproduce the issue, follow the links below to see the results: https://cbs.centos.org/koji/taskinfo?taskID=1947474 building againt cloud7-openstack-train-el7-build https://cbs.centos.org/koji/taskinfo?taskID=1947478 building againt cloud7-openstack-stein-el7-build
/usr/bin/python3
cloud7-openstack-train-el7-build
cloud7-openstack-stein-el7-build
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: cbs, doc, need-more-info
hi @jcapitao
Well, python3-pip is a base package but your SIG built a different variant and so you're blocking the real pkg to enter your buildroot
cbs list-pkgs --tag cloud7-openstack-train-el7-build|grep pip python-pip cloud7-openstack-train-el7-build amoralej
As you can see your built pkg by your SIG is tagged for your tags, and so not accepting the one from distro (your tag has always higher priority) and you can also see that your tagged pkg is python2 and not python3 :
https://cbs.centos.org/koji/buildinfo?buildID=11281
@jpena , @amoralej : can you explain to your team mates how and why you decided to build it/tag it and so now in conflict ? I'll let you discuss this, as it's not a problem per se, but koji just acts the way it should. Assuming that you don't need your specific python-pip build (python2 only at that time, don't know the reason, but again something your SIG decided), you can untag it, remove that pkg , wait for buildroot/repo to be regenerated and try another build ?
Metadata Update from @arrfab: - Issue priority set to: Waiting on Reporter (was: Needs Review)
Thanks @arrfab , sorry i didn't check it before. That's coming from some of our package requiring python2 pip as BR (i don't recall which one, we need to check it). In fact i see that in the base repo there is only python3-pip, not python2 version, so this may be an issue to untag current python-pip from the tag.
Thank you @arrfab for the explanation Sorry for having wasted your time with that.. I'll triple check next time
Metadata Update from @jcapitao: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.