doc: clarify rpm imports

Related: https://pagure.io/koji/issue/3281
This commit is contained in:
Tomas Kopecek 2022-03-24 12:57:10 +01:00
parent 75b3cc4fea
commit e720df320b
2 changed files with 17 additions and 3 deletions

View file

@ -12,7 +12,7 @@ Koji repo administration daemon (``kojira``) is properly configured and
running, and at least one Koji builder (``kojid``) is properly
configured and running. All koji cli commands assume that the user is a
Koji *admin*. If you need help with these tasks, see the
`ServerHowTo <Koji/ServerHowTo>`__ .
:doc:`ServerHowTo <server_howto>`.
- Download all source rpms and binary rpms for the arches you're
interested in
@ -29,6 +29,12 @@ the need to upload them to the hub and **very significantly** increasing
import speed. When using ``--link``, you must run as root. It is
**highly** recommended that you use ``--link``.
If an imported rpm contains an rpm signature, the import does not automatically
write out a signed copy for that signature. The primary copy will be the signed
rpm, and the signature will be noted. If a signed copy is desired (e.g. for
generating :doc:`distrepos <exporting_repositories>`), you can use the koji
write-signed-rpm command.
- Import all binary rpms using the same method as above
- Create a new tag