We'd like to use the proposed-updates SIG content in the hyperscale buildroots, please add it to our package and image build tags. We'd like to use this to get fixes we make in that SIG for our stuff.
FYI @salimma @dcavalca
Metadata Update from @gwmngilfen: - Issue assigned to gwmngilfen
Metadata Update from @gwmngilfen: - Issue tagged with: cbs, low-trouble, medium-gain
OK, so just to clarify...
For the parent tag, do you want to inherit from testing, candidate, or release?
For the hyperscale tags, I currently see:
hyperscale9s-images-experimental-el9s-build hyperscale9s-images-main-el9s-build hyperscale9s-packages-experimental-el9s-build hyperscale9s-packages-facebook-el9s-build hyperscale9s-packages-gnome-el9s-build hyperscale9s-packages-hotfixes-el9s-build hyperscale9s-packages-intel-el9s-build hyperscale9s-packages-main-el9s-build hyperscale9s-packages-spin-el9s-build hyperscale9s-spin_media-experimental-el9s-build hyperscale9s-spin_media-main-el9s-build hyperscale10s-images-experimental-el10s-build hyperscale10s-images-main-el10s-build hyperscale10s-packages-experimental-el10s-build hyperscale10s-packages-facebook-el10s-build hyperscale10s-packages-gnome-el10s-build hyperscale10s-packages-intel-el10s-build hyperscale10s-packages-kernel-el10s-build hyperscale10s-packages-main-el10s-build hyperscale10s-packages-spin-el10s-build
Do you want the parent added to all of these? And is there a specific priority, or shall I just add it to the end of the list?
Above CentOS base repos, below everything else.
And we want the packages in the -release tag.
So CentOS base repos are external, this is an inherited tag, and it's not clear to me how the priorities of the differing lists interact. I've gone ahead and added PU-release to all the tags listed above, as the last inheritance. For example:
$ cbs taginfo hyperscale10s-images-experimental-el10s-build ... External repos: 5 centos10s-baseos (http://mirror.stream.centos.org/10-stream//BaseOS/$arch/os/, merge mode: bare), arches: inherited from tag 10 centos10s-appstream (http://mirror.stream.centos.org/10-stream//AppStream/$arch/os/, merge mode: bare), arches: inherited from tag 15 centos10s-crb (http://mirror.stream.centos.org/10-stream//CRB/$arch/os/, merge mode: bare), arches: inherited from tag 20 epel10 (https://dl.fedoraproject.org/pub/epel/10/Everything/$arch/, merge mode: bare), arches: inherited from tag Inheritance: 5 .... buildsys10s-release [2893] 10 .... hyperscale10s-images-experimental-candidate [3073] 25 .... hyperscale10s-packages-experimental-release [2921] 30 .... hyperscale10s-packages-main-release [2917] 35 .... hyperscale10s-packages-spin-release [2925] 40 .... hyperscale10s-packages-kernel-release [3063] 45 .... hyperscale10s-packages-gnome-release [2929] 50 .... extras10s-extras-common-release [2913] 55 .... proposed_updates10s-packages-main-release [3087]
I hope that's what you're looking for, I can change it tomorrow if not.
I assume "highest one (ie. lowest number) wins"?
just having a look at opened tickets : is that one done ? @gwmngilfen is on PTO for a week so either I can finish (but need to know the status) or just close ticket if all was implemented ?
Metadata Update from @arrfab: - Issue priority set to: Waiting on Reporter (was: Needs Review)
Log in to comment on this ticket.