Blame SOURCES/0024-doc-Describe-how-gpg-keys-are-stored-for-repo_ggpche.patch

bc72d2
From 00f3016ec0d79186f08c2f0ebf450bdc3dab1311 Mon Sep 17 00:00:00 2001
bc72d2
From: =?UTF-8?q?Ale=C5=A1=20Mat=C4=9Bj?= <amatej@redhat.com>
bc72d2
Date: Thu, 23 Jun 2022 09:33:45 +0200
bc72d2
Subject: [PATCH] doc: Describe how gpg keys are stored for `repo_ggpcheck`
bc72d2
 (RhBug:2020678)
bc72d2
bc72d2
https://bugzilla.redhat.com/show_bug.cgi?id=2020678
bc72d2
---
bc72d2
 doc/conf_ref.rst | 6 ++++++
bc72d2
 1 file changed, 6 insertions(+)
bc72d2
bc72d2
diff --git a/doc/conf_ref.rst b/doc/conf_ref.rst
bc72d2
index 885a4560..decb49ff 100644
bc72d2
--- a/doc/conf_ref.rst
bc72d2
+++ b/doc/conf_ref.rst
bc72d2
@@ -906,6 +906,12 @@ configuration.
bc72d2
     :ref:`boolean <boolean-label>`
bc72d2
 
bc72d2
     Whether to perform GPG signature check on this repository's metadata. The default is False.
bc72d2
+    Note that GPG keys for this check are stored separately from GPG keys used in package signature
bc72d2
+    verification. Furthermore, they are also stored separately for each repository.
bc72d2
+
bc72d2
+    This means that dnf may ask to import the same key multiple times. For example, when a key was
bc72d2
+    already imported for package signature verification and this option is turned on, it may be needed
bc72d2
+    to import it again for the repository.
bc72d2
 
bc72d2
 ``retries``
bc72d2
     :ref:`integer <integer-label>`
bc72d2
-- 
bc72d2
2.36.1
bc72d2