Based on public discussion on the centos-devel list, we'll have to implement a specific new tag (to be considered like a SIG but in fact a special group of other SIG members) that will be used as a way to push Extras for 8-Stream and 9-Stream repositories.
This Extras repositories will only be used to provide the centos-release-<sig_name>-<project> package that can be used by users to have both the .repo and gpg pub key and so able to install packages from SIGs repositories
centos-release-<sig_name>-<project>
Metadata Update from @arrfab: - Issue assigned to arrfab - Issue tagged with: cbs, high-gain, medium-trouble
@bstinson : when you have informations about the repo structure (so basically which repo name to use under http://mirror.stream.centos.org/SIGs/9-stream/extras// , corresponding to SIG tag naming convention) we can create quickly the needed tags and GPG key for this to happen, and then document it in the https://sigs.centos.org/guide doc (updated SIGGuide)
Metadata Update from @arrfab: - Issue priority set to: Waiting on External (was: Needs Review)
let's create extras9s-extras-common-{candidate,testing,release} and a sig-extras group in ACO for this. i think that means we'll have repos landing here: http://mirror.stream.centos.org/SIGs/9-stream/extras/x86_64/extras-common
extras9s-extras-common-{candidate,testing,release}
WFM .. and we can then later for c8s have it landing also on mirror under /centos/8-stream/extras/x86_64/extras-common too but let's try c9s first
Here is the current situation :
sig-extras
@bstinson : do we want to test with a SIG first, document process as we go and then push doc and announce on centos-devel for all other SIGs ?
per discussion in #centos-stream , extras9s-extras-common-release is now unlocked, permitting SIGs to push their centos-release-* pkgs for Stream 9
centos-release-*
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.