FS#47371 - [gnupg] Gnupg-2.1 does not work well with pacman-key upon fresh install
Attached to Project:
Arch Linux
Opened by kozaki (kozaki) - Monday, 14 December 2015, 16:38 GMT
Last edited by Gaetan Bisson (vesath) - Thursday, 24 December 2015, 04:01 GMT
Opened by kozaki (kozaki) - Monday, 14 December 2015, 16:38 GMT
Last edited by Gaetan Bisson (vesath) - Thursday, 24 December 2015, 04:01 GMT
|
Details
Description:
Upon new installation with archiso 2015-12-01 dual, I tried to add a signed repository and couldn't go further than pacman-key -r <KEY>: gpg: connecting dirmngr at '/root/.gnupg/S.dirmngr' failed: IPC connect call failed gpg: keyserver receive failed: No dirmngr ==> ERROR: Remote key not fetched correctly from keyserver. Continuing from While it's closed I had the same issue on my latest two Arch Linux install. Tip provided in #42798 allowed me to go on each time. Additionally the information to allow for adding a signed unofficial repo has been removed from the [wiki](https://wiki.archlinux.org/index.php/Pacman/Package_signing#Adding_unofficial_keys) Steps to reproduce: 1. Install Arch from the latest official ISO 2. Enable a signed unofficial repository in pacman.conf 3. Update pacman 4. Try to add custom key eg: pacman-key -r E6366A92 Additional info: * package version(s) - pacman 4.2.1-4 - archlinux-keyring 20151206-1 - gnupg 2.1.10-1 * Miscellaneous Deleting ~/.gnupg content then add a TU key has same gnupg error message. |
This task depends upon
Closed by Gaetan Bisson (vesath)
Thursday, 24 December 2015, 04:01 GMT
Reason for closing: Fixed
Additional comments about closing: gnupg-2.1.10-3 in [testing]
Thursday, 24 December 2015, 04:01 GMT
Reason for closing: Fixed
Additional comments about closing: gnupg-2.1.10-3 in [testing]
If we are talking on the newly booted system, does running `dirmngr </dev/null &>/dev/null` fix it? It's currently run on upgrade only.
Happened on the *installed* system, twice (I replayed it to check some steps better). Sorry I thought it would be clear from my initial report eg. "Upon new installation with archiso 2015-12-01" and "1. Install Arch from the latest official ISO".
Yes the workarround that worked is the one listed in the former (closed)
FS#42798. And this bit of information that's needed to allow for adding a signed unofficial repo has been removed from the [wiki](https://wiki.archlinux.org/index.php/Pacman/Package_signing#Adding_unofficial_keys leads nowhere). Adds a layer of unnecessary complexity in case one *needs* to get some stuff from a TUR.In short and as to allow for adding a first signed TUR without the following error
gpg: connecting dirmngr at '/root/.gnupg/S.dirmngr' failed: IPC connect call failed
E.g. to quote Maurizio D'Addona in
FS#42798: dirmngr still ignores the --homedir option and tries to use /root/.gnupg instead. So you may have to create it yourself on the first launch.At least display a note on the cause with a link to the workarround, that will also increases the opportunities for the average Arch user to get the relationship between gpg and Pacman. At any case, letting this error as it is with no explanation on why and how to deal with it, even on. the wiki, is not satisfying, is it?
`dirmngr </dev/null &>/dev/null` needs to be run in post_install, not just in post_upgrade.