Added a comment: gpg needs --armor for apt-get to be happy
authordavid@8b8bbbce1f5e71b934fb04fc3ec00c5b9b561e2a <david@web>
Sat, 14 Dec 2019 12:00:14 +0000 (13:00 +0100)
committerStefano Zacchiroli <zack@upsilon.cc>
Sat, 14 Dec 2019 12:00:14 +0000 (13:00 +0100)
blog/posts/2009/04/howto:_uploading_to_people.d.o_using_dput/comment_7_21ee46829cf490fbec01706f12002bdb._comment [new file with mode: 0644]

diff --git a/blog/posts/2009/04/howto:_uploading_to_people.d.o_using_dput/comment_7_21ee46829cf490fbec01706f12002bdb._comment b/blog/posts/2009/04/howto:_uploading_to_people.d.o_using_dput/comment_7_21ee46829cf490fbec01706f12002bdb._comment
new file mode 100644 (file)
index 0000000..b9078c8
--- /dev/null
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="david@8b8bbbce1f5e71b934fb04fc3ec00c5b9b561e2a"
+ nickname="david"
+ avatar="http://cdn.libravatar.org/avatar/eba25123b3225dd8f0d6189c4f8ebac5"
+ subject="gpg needs --armor for apt-get to be happy"
+ date="2019-12-14T12:00:13Z"
+ content="""
+It seems that apt now expects Release.gpg to be in ASCII armored format, so sign-remote needs to be edited to add --armor to the gpg invocation, otherwise you'll get an error message like:
+
+Detached signature file '/var/lib/apt/lists/partial/blablabla_Release.gpg' is in unsupported binary format
+"""]]