From 6964416371fb01a84407659c390bfd7df1e961b2 Mon Sep 17 00:00:00 2001 From: Yuming Zhu Date: May 16 2017 10:05:15 +0000 Subject: [PATCH 1/2] doc: use `tag-build` instead of alias cmd `tag-pkg` --- diff --git a/docs/source/server_bootstrap.rst b/docs/source/server_bootstrap.rst index 05efe95..874ade3 100644 --- a/docs/source/server_bootstrap.rst +++ b/docs/source/server_bootstrap.rst @@ -48,7 +48,7 @@ you just imported. $ koji list-pkgs --quiet | xargs koji add-pkg --owner dist-foo $ koji list-untagged | xargs -n 1 koji call tagBuildBypass dist-foo -We call the *tagBuildBypass* method instead of using ``koji tag-pkg`` +We call the *tagBuildBypass* method instead of using ``koji tag-build`` because it doesn't require the builders to process *tagBuild* tasks one at a time, but does the tagging directly. This will save a significant amount of time, especially when tagging a large number of packages. From 747497ec9b382b12fbdabb04c428d1f5e833ae80 Mon Sep 17 00:00:00 2001 From: Yuming Zhu Date: May 16 2017 12:11:02 +0000 Subject: [PATCH 2/2] doc: remove nowiki tag --- diff --git a/docs/source/server_bootstrap.rst b/docs/source/server_bootstrap.rst index 874ade3..f91ca07 100644 --- a/docs/source/server_bootstrap.rst +++ b/docs/source/server_bootstrap.rst @@ -76,7 +76,7 @@ amount of time, especially when tagging a large number of packages. the minimal buildroot You can find out what the current build group for Fedora is by running -``koji -s https://$ARCH.koji.fedoraproject.org/kojihub list-groups f17-build`` +``koji -s https://$ARCH.koji.fedoraproject.org/kojihub list-groups f17-build`` against the Fedora Koji instance for your $ARCH. This is probably a good starting point for your minimal buildroot.