You are not logged in.
when I issue makepkg, I get the following output:
==> Making package: abs 2.4.4-2 (Wed Jan 21 05:31:23 UTC 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found abs-2.4.4.tar.gz
-> Found abs-2.4.4.tar.gz.sig
==> Validating source files with md5sums...
abs-2.4.4.tar.gz ... Passed
abs-2.4.4.tar.gz.sig ... Passed
==> Verifying source file signatures with gpg...
abs-2.4.4.tar.gz ... FAILED (the public key 487EACC08557AD082088DABA1EB2638FF56C0C53 is not trusted)I have imported the key. I have signed the key. what is wrong?
Offline
Consult the wiki or the many threads on the same topic.
Offline
Offline
thank you, but this happens when I try to add the key
gpg --recv-keys 1EB2638FF56C0C53
gpg: enabled debug flags: memstat
gpg: keyserver receive failed: No data
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: secmem usage: 0/32768 bytes in 0 blocksOffline
gpg --recv-key 1EB2638FF56C0C53fails to reach the server however using
sudo gpg --recv-key 1EB2638FF56C0C53] yields [gpg: key F56C0C53: "Dave Reisner <d@falconindy.com>"
gpg: Total number processed: 1
gpg: unchanged: 1however, this means the key is in root's keyring and I don't use makepkg as root. am I correct in this?
Last edited by shoelesshunter (2015-01-21 11:55:33)
Offline
Try following the directions in the GnuPG 2.1 release announcement. I had a similar problem and migrating my keyring to the new keybox format solved it for me. My guess is that when you ran it with sudo, it created a new keybox (that is, in the new format) so you didn't have any error.
Last edited by jakobcreutzfeldt (2015-01-21 15:32:04)
Offline