On Tuesday 18 August 2009, Karsten Bräckelmann wrote: >On Tue, 2009-08-18 at 06:40 -0400, Gene Heskett wrote: >> One of the channels I use, yerp, has a failing gpg key despite my >> importation of that key. Several times. >> >> How should I proceed? > >General advice: Post the error messages. Do a debug run. Post the >relevant parts of the debug info. > >Gene -- with your headstrong, infamous around here user setup, you >should first check exactly that -- users. Which one runs the cron job? >Which one do you sudo to? And which one imported the GPG key?
Thanks for the complement. I have studied on trying to do it right for almost 75 years now. And the user gene is the user that is doing all that. Now, let me see if I can find that set of errors. Yes, here they are: ============================ [25964] dbg: channel: found mirror http://yerp.org/rules/stage/ [25964] dbg: channel: selected mirror http://yerp.org/rules/stage [25964] dbg: http: GET request, http://yerp.org/rules/stage/320805296.tar.gz [25964] dbg: http: GET request, http://yerp.org/rules/stage/320805296.tar.gz.sha1 [25964] dbg: http: GET request, http://yerp.org/rules/stage/320805296.tar.gz.asc [25964] dbg: http: IMS GET request, http://yerp.org/rules/stage/MIRRORED.BY, Thu, 23 Jul 2009 01:24:48 GMT [25964] dbg: sha1: verification wanted: 91eb07b6a6bdd27d5b99e6612e35e209cd1fba9c [25964] dbg: sha1: verification result: 91eb07b6a6bdd27d5b99e6612e35e209cd1fba9c [25964] dbg: channel: populating temp content file [25964] dbg: gpg: populating temp signature file [25964] dbg: gpg: calling gpg [25964] dbg: gpg: gpg: Signature made Tue 18 Aug 2009 03:24:59 AM EDT using DSA key ID 6C6191E3 [25964] dbg: gpg: [GNUPG:] SIG_ID XMBVEC+9EnYV7uMWvdrn/1H/+Hw 2009-08-18 1250580299 [25964] dbg: gpg: [GNUPG:] GOODSIG DC85341F6C6191E3 Justin Mason Signing Key (Code Signing Only) <signing...@jmason.org> [25964] dbg: gpg: gpg: Good signature from "Justin Mason Signing Key (Code Signing Only) <signing...@jmason.org>" [25964] dbg: gpg: [GNUPG:] VALIDSIG 8D25B5E91DAF0F715F60B588DC85341F6C6191E3 2009-08-18 1250580299 0 3 0 17 2 00 8D25B5E91DAF0F715F60B588DC85341F6C6191E3 [25964] dbg: gpg: [GNUPG:] TRUST_UNDEFINED [25964] dbg: gpg: gpg: WARNING: This key is not certified with a trusted signature! [25964] dbg: gpg: gpg: There is no indication that the signature belongs to the owner. [25964] dbg: gpg: Primary key fingerprint: 8D25 B5E9 1DAF 0F71 5F60 B588 DC85 341F 6C61 91E3 [25964] dbg: gpg: found signature made by key 8D25B5E91DAF0F715F60B588DC85341F6C6191E3 [25964] dbg: gpg: key id 6C6191E3 is not release trusted error: GPG validation failed! The update downloaded successfully, but the GPG signature verification failed. channel: GPG validation failed, channel failed =============================== Obviously this is a trust setting, not a gpg failure as I assumed when I posted. Which then begs the question of who is untrusted, me, or yerp.org? If me, then what file, in a 3.002005 install, do I edit to set this? Thanks. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) The NRA is offering FREE Associate memberships to anyone who wants them. <https://www.nrahq.org/nrabonus/accept-membership.asp> Even the best of friends cannot attend each other's funeral. -- Kehlog Albran, "The Profit"