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

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