aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorMicah Anderson <micah@riseup.net>2010-12-07 13:44:30 -0500
committerMicah Anderson <micah@riseup.net>2010-12-07 13:44:30 -0500
commitb59bdb0a89bad0a83bda141aa19213b760e6896c (patch)
tree894bea073725fe286c0f955a929efc438a55aa21 /README
parent7e1a187f243d64073f660ba8928896e7a1d81db3 (diff)
downloadpuppet-apt-b59bdb0a89bad0a83bda141aa19213b760e6896c.tar.gz
puppet-apt-b59bdb0a89bad0a83bda141aa19213b760e6896c.tar.bz2
README update: clarify that the debian-archive-keyring is managed already
Just so people are clear that they do not need to specify a $custom_key_dir to manage the debian archive keyring, I've added some clarifying text so you know that this is not necessary
Diffstat (limited to 'README')
-rw-r--r--README3
1 files changed, 3 insertions, 0 deletions
diff --git a/README b/README
index 97a398b..b448859 100644
--- a/README
+++ b/README
@@ -92,6 +92,9 @@ apt keyring, you can set this variable to a path in your fileserver
where individual key files can be placed. If this is set and keys
exist there, this module will 'apt-key add' each key.
+The debian-archive-keyring package is installed and kept current up to the
+latest revision (this includes the backports archive keyring).
+
$apt_proxy / $apt_proxy_port
----------------------------