Related: https://pagure.io/koji/issue/3281
Metadata Update from @tkopecek: - Pull-request tagged with: doc, no_qe
Might be worth adding a note in docs/source/signing.rst as well
Suggested for grammar and clarity.
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.
distrepos <exporting_repositories>
koji write-signed-rpm
1 new commit added
additional clarifications
rebased onto 7958d1ca5ff30fb89730ab75b211bfa7cf92a4f0
Minor adjustments needed in signing.rst. Otherwise good to go.
signing.rst
--- a/docs/source/signing.rst +++ b/docs/source/signing.rst @@ -74,8 +74,8 @@ A lower-level command that shows the signature on an RPM file (the Learn more about RPM signatures and digests in `RPM's reference manual <https://rpm-software-management.github.io/rpm/manual/signatures_digests.html>`_. -Uploding signed RPMs to Koji ----------------------------- +Uploading signed RPMs to Koji +----------------------------- Koji does not sign RPMs. Instead, Koji imports RPMs that are signed with a separate key. @@ -95,8 +95,8 @@ The ``koji import-sig`` command uploads the signed RPM headers to the Koji Hub, which stores the headers on disk alongside the main unsigned RPM. It also writes out a full signed RPM. -Other variant is to import whole signed rpms (e.g. during :doc:`bootstrapping -<server_bootstrap>` via ``koji import`` command.) If such imported rpm contains +Another variant is to import whole signed rpms (e.g. during :doc:`bootstrapping +<server_bootstrap>` via ``koji import`` command.) If such an imported rpm contains an rpm signature, the import does not automatically write out a signed copy for that signature (in contrast with ``import-sig``). The primary copy will be the signed rpm, and the signature will be noted. If a signed copy is desired (e.g.
rebased onto e720df320b0400168bed64b71f179bf28b9a9db0
Commit 5fdaf591 fixes this pull-request
Pull-Request has been merged by tkopecek
Related: https://pagure.io/koji/issue/3281