infra repo docs -- make adding package to tag clearer

Previously it was a little ambiguous what tag to add a package to
when adding a package to an infra yum repo. This commit tweaks it a
little bit to make it more obvious, and provide a real example.

Signed-off-by: Ryan Lerch <rlerch@redhat.com>
This commit is contained in:
Ryan Lercho 2024-05-27 15:15:49 +10:00
parent 9756062cdc
commit 5aab077dbd

View file

@ -99,8 +99,8 @@ koji move epel7-infra-stg epel7-infra test2-1.0-1.el7.infra
If you try to build a package into the infra tags, and koji says
something like: `BuildError: package test not in list for tag
epel7-infra-candidate`. That means that the package has not been added to
the list for building in that particular tag. Either add the package to
f40-infra-candidate`. That means that the package has not been added to
the list for building in the `f40-infra` tag. Either add the package to
the respective Fedora/EPEL branches (this is the preferred method, since
we should always aim to get everything packaged for Fedora/EPEL), or add
the package to the listing for the respective tag.
@ -110,3 +110,8 @@ To add package to infra tag, run:
....
koji add-pkg $tag $package --owner=$user
....
for example:
....
koji add-pkg f40-infra mediawiki-theme-fedora --owner=ryanlerch
....