When we made the epel10.0 / epel10.1 tags, we didn't make infra tags. We use these for packages not in epel that we need on infrastructure machines.
So, we should add the epel10 infra infra-stg and infra-candidate tags like we have for epel9.
Metadata Update from @patrikp: - Issue assigned to patrikp
Metadata Update from @phsmoura: - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @phsmoura: - Issue untagged with: low-gain - Issue tagged with: medium-gain
So I think what needs to happen is:
PRIMARY_ARCHES="i686 x86_64 aarch64 ppc64le s390x" add-tag --parent "epel10.0-build" --arches="${PRIMARY_ARCHES}" "epel10-infra" add-tag --parent "epel10-infra" --arches="${PRIMARY_ARCHES}" "epel10-infra-stg" add-tag --parent "epel10-infra-stg" "epel10-infra-candidate" add-tag --parent "epel10-infra-stg" --arches="${PRIMARY_ARCHES}" "epel10-infra-build" edit-tag -x tag2distrepo.enabled=True -x tag2distrepo.keys=?????????? "epel10-infra" edit-tag -x tag2distrepo.enabled=True -x tag2distrepo.keys=?????????? "epel10-infra-stg" edit-tag --perm=infra "epel10-infra" edit-tag --perm=infra "epel10-infra-build" edit-tag --perm=infra "epel10-infra-stg" edit-tag --perm=infra "epel10-infra-candidate" add-target "epel10-infra" "epel10-infra-build" "epel10-infra-candidate"
...based off of the Fedora make-koji-release-tags script.
I'm not sure what key to use for tag2distrepo.keys, also not sure if we want to use epel10.0-build or epel10.1-build as the parent, at this point. Also don't know why epel10-infra-candidate doesn't have an --arches option.
The key should be the same as all the other infra tags (we have just one infra key for all of them).
We use rhel, so likely we want to target epel10.0-build for now.... unless I'm confused.
CC: @carlwgeorge
Running it now. We will need to change it on rhel minor releases to point to the current one...
ok, run. Thanks @james !
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)