| Summary: | app-crypt/gnupg: pubring.gpg suddenly non-existing | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
| Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | bircoph |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | http://bugs.debian.org/725138 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
How can I regenerate the public key from private one? Thanks for the info (In reply to Pacho Ramos from comment #1) > How can I regenerate the public key from private one? Thanks for the info Yes, just import your secring: $ gpg --import ~/.gnupg/secring.gpg Alternatively you may --recv-key required keys from public gpg servers (if they were uploaded there before). I fail to see anything in the log regarding why the pubring is removed, only that gpg is recreating it because it is missing. This is the message that makes me suspect something went wrong :/ gpg: borrando fichero de bloqueo residual (creado por 2624) -> "Removing residual lock file (created by 2634) (In reply to Pacho Ramos from comment #4) > This is the message that makes me suspect something went wrong :/ > gpg: borrando fichero de bloqueo residual (creado por 2624) -> "Removing > residual lock file (created by 2634) The only thing related I've seen is [0, 1], but at least nothing that indicates it is specific to 2.0.28. References: [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725138 [1] https://support.gpgtools.org/discussions/problems/12363-gpg-keychain-access-deletes-gnupgpubringgpg (lets drop the block as I have no idea how did it occur or how to make it happen again... :S) (In reply to Pacho Ramos from comment #6) > (lets drop the block as I have no idea how did it occur or how to make it > happen again... :S) Without any way to reproduce the issue or information on how it occurred in the first place I will have to close this bug due to insufficient information. Please reopen if it ever occurs again (hopefully it won't, but if it does, make sure to check if you have a pubring.gpg~ file still in the GNUPGHOME which is a backup during certain operations). I've been speaking with the debian maintainers and they have no idea how the situation occurred in their reported situation. This isn't necessarily linked to GnuPG itself, and if were is it is an upstream issue, not something we can solve downstream. OK, thanks |
I have just seen this while committing with repoman: /var/cvsroot/gentoo-x86/www-client/epiphany/epiphany-3.16.2.ebuild,v <-- epiphany-3.16.2.ebuild initial revision: 1.1 /var/cvsroot/gentoo-x86/www-client/epiphany/ChangeLog,v <-- ChangeLog new revision: 1.318; previous revision: 1.317 /var/cvsroot/gentoo-x86/www-client/epiphany/epiphany-3.12.1.ebuild,v <-- epiphany-3.12.1.ebuild new revision: delete; previous revision: 1.5 >>> Creating Manifest for /home/pacho/gentoo-x86/www-client/epiphany gpg: borrando fichero de bloqueo residual (creado por 2624) -> "Removing residual lock file (created by 2634) gpg: almacén `/home/pacho/.gnupg//pubring.gpg' creado -> storage... created gpg: clave A188FBD4: clave secreta sin clave pública - omitida -> secret key without public key - omitted gpg: no default secret key: No secret key gpg: /home/pacho/gentoo-x86/www-client/epiphany/Manifest: clearsign failed: No secret key !!! !!! gpg exited with '2' status !!! Disabled FEATURES='sign' /var/cvsroot/gentoo-x86/www-client/epiphany/Manifest,v <-- Manifest new revision: 1.373; previous revision: 1.372 Commit complete. RepoMan sez: "If everyone were like you, I'd be out of business!" As you can see gpg has decided to replace the working pubring.gpg file by and empty one! :S