From 5aab077dbdc7ff4fd9f99ee275cead938b2d8b2c Mon Sep 17 00:00:00 2001 From: Ryan Lerch Date: Mon, 27 May 2024 15:15:49 +1000 Subject: [PATCH] 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 --- modules/sysadmin_guide/pages/infra-repo.adoc | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/modules/sysadmin_guide/pages/infra-repo.adoc b/modules/sysadmin_guide/pages/infra-repo.adoc index fd34bdd..6a84977 100644 --- a/modules/sysadmin_guide/pages/infra-repo.adoc +++ b/modules/sysadmin_guide/pages/infra-repo.adoc @@ -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 +.... \ No newline at end of file