From 087e468877d45be7853e0ff1432ccad8293efb04 Mon Sep 17 00:00:00 2001 From: david Date: Fri, 24 Aug 2018 00:29:50 +0000 Subject: Added a comment: GPG keybox database version 1 --- .../comment_2_d5d1611896fa72bda22e5406285ade2e._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/forum/can__39__t_get_Apt.trustsKey_to_work/comment_2_d5d1611896fa72bda22e5406285ade2e._comment (limited to 'doc/forum/can__39__t_get_Apt.trustsKey_to_work') diff --git a/doc/forum/can__39__t_get_Apt.trustsKey_to_work/comment_2_d5d1611896fa72bda22e5406285ade2e._comment b/doc/forum/can__39__t_get_Apt.trustsKey_to_work/comment_2_d5d1611896fa72bda22e5406285ade2e._comment new file mode 100644 index 00000000..90151369 --- /dev/null +++ b/doc/forum/can__39__t_get_Apt.trustsKey_to_work/comment_2_d5d1611896fa72bda22e5406285ade2e._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="david" + avatar="http://cdn.libravatar.org/avatar/22c2d800db6a7699139df604a67cb221" + subject=" GPG keybox database version 1" + date="2018-08-24T00:29:50Z" + content=""" +I have propellor 5.3.6 running on debian testing. If I spin to the testing host, trustsKey works fine. On stretch I get at 'GPG keybox database version 1' installed. I guess on stretch it's still building propellor from the old sources? In any case, gpg doesn't know what do do with that keybox file (i.e. gpg < file craps out). Weird but true. In any case this breaks apt-key on that host, which is unfortunate. I guess I'll try overriding the trustsKey function in my config.hs + +"""]] -- cgit v1.2.3