particle-os/debian-koji
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

PR#422 doc: use tag-build instead of alias cmd tag-pkg

Browse source 
Merges #422
https://pagure.io/koji/pull-request/422
This commit is contained in:
Mike McLean 2017-05-16 09:11:13 -04:00
commit 323e4d7511
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/source/HOWTO.rst
View file

@ -118,7 +118,7 @@ detailed explanations of them:
``--skip-tag``
Normally the package is tagged after the build completes. This
option causes the tagging step to be skipped. The package will be in
the system, but untagged (you can later tag it with the tag-pkg
the system, but untagged (you can later tag it with the tag-build
command)
``--scratch``
This makes the build into a scratch build. The build will not be

4
docs/source/server_bootstrap.rst
View file

@ -48,7 +48,7 @@ you just imported.
$ koji list-pkgs --quiet | xargs koji add-pkg --owner <kojiuser> 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.
@ -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 <nowiki>https://$ARCH.koji.fedoraproject.org/kojihub</nowiki> 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.