Disclaimer: This is not an issue solely for the centos-infra, but involves some discussion. Still I think this is the best place to discuss this.
Since CentOS Linux 8 went EOL a few days ago all content provided by SIGs who have not opted into building for rhel8 is gone from mirror.c.o. However the extras repository for c8 is still available on mirror.c.o and contains centos-release-* packages with repository configs now pointing to content not available anymore. This might be confusing for users and makes it difficult for users running RHEL/Rocky/Alma/... 8 to consume SIG content built for rhel8. After all that's the main reason SIGs do build for rhel8.
centos-release-*
My suggestion is to do the following to clean-up the current situation:
centos-stream-repos
extras8-extras-common-{candidate,testing,release}
Once this is done there are two options to easily consume these centos-release-* packages:
[centos-extras-common] name=CentOS $releasever - Extras mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras-extras-common #baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/extras-common/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Extras
Metadata Update from @arrfab: - Issue tagged with: cbs, centos-stream, high-gain, medium-trouble
Metadata Update from @arrfab: - Issue marked as depending on: #698
Just wanted to ask about the current status. I'm mainly interested in adding the extras8-extras-common-{candidate,testing,release}. As already mentioned before this would allow SIGs who build content for rhel8 to also provide centos-release-* packages for rhel8. There is currently no convenient way for rhel8 users to consume SIG content built for rhel8. I'm only asking for these tags, similar to the one already existing for c8s and c9s, to be created, afaik no further work by infra is required.
A possible work-around is for every SIG to build their centos-release-* packages in one of their tags. However this would very likely lead to different ways how to consume SIG content depending on how a particular SIG implements it. This is confusing for the users.
Thanks.
[backlog refinement] We had a quick look and discussion around these two points you mentioned :
Thanks for the update!
@bstinson Concerning the discussion with the board about new centos-release* pkgs for rhel: Is there some way to provide further input? If it is being discussed, I would like to avoid leaving important questions unanswered. Usually issues for the centos-board are posted under https://git.centos.org/centos/board/issues, but I cannot find anything related there.
Please note that I opened an issue with the CentOS board 1 which also concerns the open question about new centos-release* pkgs for RHEL.
Now that we can build for rhel9 in cbs [#786], is there any update concerning centos-release-* packages for rhel8 and 9? Directly addressed, I ask for the creation of extras{8,9}-extras-common-{candidate,testing,release} tags in CBS analogous to the existing extras{8,9}s-extras-common-{candidate,testing,release} tags.
extras{8,9}-extras-common-{candidate,testing,release}
extras{8,9}s-extras-common-{candidate,testing,release}
Any updates concerning this request?
@bstinson ?
Metadata Update from @arrfab: - Issue assigned to bstinson
@bstinson Anything you want to add to this ticket? Otherwise we will close it.
Closing this as there is no response from @bstinson for long time.
Metadata Update from @zlopez: - Issue close_status updated to: Insufficient Data - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.