Cloud SIG requests the following build targets:
cloud9s-okd-4.19-el9s cloud9s-okd-4.20-el9s cloud9s-okd-4.21-el9s cloud10s-okd-4.19-el10s cloud10s-okd-4.20-el10s cloud10s-okd-4.21-el10s
Thank you!
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: cbs, high-gain, low-trouble
@ausil : created all the tags/targets and without any specific ask for s390x arch (now available for some months ) , I just created the build targets based on existing other okd tags (so for x86_64, aarch64 and ppc64le) :
* Checking distribution el9s configuration... -> Checking cloud config... Using default options for cloud/okd Creating tag : cloud9s-okd-4.19-candidate Creating tag : cloud9s-okd-4.19-testing Creating tag : cloud9s-okd-4.19-release -> creating cloud9s-okd-4.19-el9s Added external repo centos9s-baseos to tag cloud9s-okd-4.19-el9s-build (priority 5) Added external repo centos9s-appstream to tag cloud9s-okd-4.19-el9s-build (priority 10) Added external repo centos9s-crb to tag cloud9s-okd-4.19-el9s-build (priority 15) * Checking distribution el9s configuration... -> Checking cloud config... Using default options for cloud/okd Creating tag : cloud9s-okd-4.20-candidate Creating tag : cloud9s-okd-4.20-testing Creating tag : cloud9s-okd-4.20-release -> creating cloud9s-okd-4.20-el9s Added external repo centos9s-baseos to tag cloud9s-okd-4.20-el9s-build (priority 5) Added external repo centos9s-appstream to tag cloud9s-okd-4.20-el9s-build (priority 10) Added external repo centos9s-crb to tag cloud9s-okd-4.20-el9s-build (priority 15) * Checking distribution el9s configuration... -> Checking cloud config... Using default options for cloud/okd Creating tag : cloud9s-okd-4.21-candidate Creating tag : cloud9s-okd-4.21-testing Creating tag : cloud9s-okd-4.21-release -> creating cloud9s-okd-4.21-el9s Added external repo centos9s-baseos to tag cloud9s-okd-4.21-el9s-build (priority 5) Added external repo centos9s-appstream to tag cloud9s-okd-4.21-el9s-build (priority 10) Added external repo centos9s-crb to tag cloud9s-okd-4.21-el9s-build (priority 15) * Checking distribution el10s configuration... -> Checking cloud config... Using default options for cloud/okd Creating tag : cloud10s-okd-4.19-candidate Creating tag : cloud10s-okd-4.19-testing Creating tag : cloud10s-okd-4.19-release -> creating cloud10s-okd-4.19-el10s Added external repo centos10s-baseos to tag cloud10s-okd-4.19-el10s-build (priority 5) Added external repo centos10s-appstream to tag cloud10s-okd-4.19-el10s-build (priority 10) Added external repo centos10s-crb to tag cloud10s-okd-4.19-el10s-build (priority 15) * Checking distribution el10s configuration... -> Checking cloud config... Using default options for cloud/okd Creating tag : cloud10s-okd-4.20-candidate Creating tag : cloud10s-okd-4.20-testing Creating tag : cloud10s-okd-4.20-release -> creating cloud10s-okd-4.20-el10s Added external repo centos10s-baseos to tag cloud10s-okd-4.20-el10s-build (priority 5) Added external repo centos10s-appstream to tag cloud10s-okd-4.20-el10s-build (priority 10) Added external repo centos10s-crb to tag cloud10s-okd-4.20-el10s-build (priority 15) * Checking distribution el10s configuration... -> Checking cloud config... Using default options for cloud/okd Creating tag : cloud10s-okd-4.21-candidate Creating tag : cloud10s-okd-4.21-testing Creating tag : cloud10s-okd-4.21-release -> creating cloud10s-okd-4.21-el10s Added external repo centos10s-baseos to tag cloud10s-okd-4.21-el10s-build (priority 5) Added external repo centos10s-appstream to tag cloud10s-okd-4.21-el10s-build (priority 10) Added external repo centos10s-crb to tag cloud10s-okd-4.21-el10s-build (priority 15)
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
could we please add s390x to the tags
Metadata Update from @ausil: - Issue status updated to: Open (was: Closed)
@ausil : before I do that (and then disappear in PTO mode for some days) : do you have all satisfied BuildRequires: built for s390x ? if not, that would be the first thing to work on (especially in case of existing - and so conflicting - similar NVR). If so, the procedure linked above (mail sent to devel) would apply. If you don't need existing s390x BuildRequires: , I can easily add s390x to all arches (and other tags to push artifacts out to mirror network)
Asking before adding blindly s390x, as build failing for one arch would fail all other arches ;-)
AFAIK we have the deps, though we only really need it for future work. only adding to the tags created in this request is preferable if possible
s390x arch now added on all these tags
Log in to comment on this ticket.