Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#28866 - [task] Key used to sign the package can't be imported with pacman-key

Attached to Project: Community Packages
Opened by Wieland Hoffmann (Mineo) - Sunday, 11 March 2012, 12:58 GMT
Last edited by Peter Lewis (petelewis) - Friday, 16 March 2012, 10:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Peter Lewis (petelewis)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: I'm unable to import the key that signed the package with pacman-key -r.

Additional info:

* package version(s)
task: Version : 1.9.4-3
pacman: Version : 4.0.2-1

* config and/or log files etc.
» LC_ALL=en_US.utf8 sudo pacman -Su
(209/209) checking package integrity [-------------------------------------------] 100%
error: task: key "22AD5874F39D989F" is unknown
^C
Interrupt signal received

» LC_ALL=en_US.utf8 sudo pacman-key -r 22AD5874F39D989F
gpg: requesting key F39D989F from hkp server keys.gnupg.net
gpgkeys: key 22AD5874F39D989F not found on keyserver
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
==> ERROR: Remote key not fetched correctly from keyserver.
This task depends upon

Closed by  Peter Lewis (petelewis)
Friday, 16 March 2012, 10:56 GMT
Reason for closing:  Not a bug
Comment by Jochen Maes (Gcool) - Thursday, 15 March 2012, 21:26 GMT
The related keyID seems to be "E19DAA50".

(1/1) checking package integrity [####################################################################] 100%
error: task: key "22AD5874F39D989F" is unknown
:: Import PGP key E19DAA50, "Peter Richard Lewis <pete@muddygoat.org>", created 2006-03-01? [Y/n] Y
(1/1) checking package integrity [####################################################################] 100%
(1/1) loading package files [####################################################################] 100%
(1/1) checking for file conflicts [####################################################################] 100%
(1/1) checking available disk space [####################################################################] 100%
(1/1) installing task [####################################################################] 100%
Comment by Wieland Hoffmann (Mineo) - Thursday, 15 March 2012, 22:29 GMT
How long did it take for that message to appear? I remember waiting for quite a while before killing pacman.
Comment by Jochen Maes (Gcool) - Friday, 16 March 2012, 08:19 GMT
I got the "Import PGP key" prompt pretty much instantaneously.

I just tried importing the key "manually" on a system which didn't have the key yet. Works fine here; perhaps try the same again.

$sudo pacman-key -r E19DAA50
gpg: requesting key E19DAA50 from hkp server keys.gnupg.net
gpg: key E19DAA50: public key "Peter Richard Lewis <pete@muddygoat.org>" imported
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 5 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 5 signed: 29 trust: 0-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2 valid: 29 signed: 1 trust: 29-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2012-08-10
gpg: Total number processed: 1
gpg: imported: 1
==> Updating trust database...
gpg: next trustdb check due at 2012-08-10
Comment by Peter Lewis (petelewis) - Friday, 16 March 2012, 10:29 GMT
Hi can you try another of my packages (e.g. rekonq, ascii or something) and see if you get the same behaviour with that? I'd like to know if the issue is with the task package (perhaps corrupted?) or with pacman's handling of my key.

Also see  FS#27612 , which might be related.
Comment by Wieland Hoffmann (Mineo) - Friday, 16 March 2012, 10:48 GMT
No, I'm not seeing the same behaviour with neither rekonq (currently not signed by you) nor ascii, nor task itself for that matter. I'm wondering if the problem is unrelated and is maybe a connection problem or something to the keyserver.

Bottom line is, I'm not experiencing that problem (which I tried several times to reproduce) anymore.
Comment by Peter Lewis (petelewis) - Friday, 16 March 2012, 10:55 GMT
Ah yeah, I forgot someone else rebuilt rekonq. Okay, thanks for letting me know. Closing...

Loading...