path: root/doc/forum/can__39__t_get_Apt.trustsKey_to_work
diff options
authordavid2018-08-24 00:29:50 +0000
committeradmin2018-08-24 00:29:50 +0000
commit087e468877d45be7853e0ff1432ccad8293efb04 (patch)
treed9a2928543d105842c6bcffa889ca76e05aaac9e /doc/forum/can__39__t_get_Apt.trustsKey_to_work
parent4cfeffeffbdea84e96de396425a20d427786b766 (diff)
Added a comment: GPG keybox database version 1
Diffstat (limited to 'doc/forum/can__39__t_get_Apt.trustsKey_to_work')
1 files changed, 9 insertions, 0 deletions
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=""
+ 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