From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] gnupg upgraded, problems arised
Date: Tue, 2 Jan 2007 18:28:32 +0000 [thread overview]
Message-ID: <20070102182832.0c97f340@krikkit.digimed.co.uk> (raw)
In-Reply-To: <200701021932.41735@goldspace.net>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
On Tue, 2 Jan 2007 19:32:41 +0300, Andrew Gaydenko wrote:
> Any news on this? I'd like to upgrade to gnupg-2.0*, but I don't want
> to lose access to my existing keys. Does a bug exist?
http://bugs.gentoo.org/show_bug.cgi?id=159505
You need to install pinentry.
--
Neil Bothwick
Machine-independent: Does not run on any existing machine.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-02 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 10:20 [gentoo-user] [OT] gnupg upgraded, problems arised Andrew Gaydenko
2006-12-29 13:21 ` Andrew Gaydenko
2006-12-29 13:30 ` Boyd Stephen Smith Jr.
2007-01-02 16:10 ` Boyd Stephen Smith Jr.
2007-01-02 16:32 ` Andrew Gaydenko
2007-01-02 17:16 ` Boyd Stephen Smith Jr.
2007-01-02 18:28 ` Neil Bothwick [this message]
2007-01-02 18:55 ` Andrew Gaydenko
2007-01-02 19:42 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070102182832.0c97f340@krikkit.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox