Terje Elde <[EMAIL PROTECTED]>:
> > That shouldn't happen. You may wish to try the unstable branch
> > which should stabilize Really Soon Now.
>
> I take it you're referring to the international version, as you know i need
> the crypto support.
no, unstable != international
> Is it possible for mortals (wrt mutt at least ;) to track the cvs head
> branch?
$ cvs -d :pserver:[EMAIL PROTECTED]:/home/roessler/cvs login
$ cvs -d :pserver:[EMAIL PROTECTED]:/home/roessler/cvs co mutt
Then do "cvs mutt ; cvs update" every now and then.
(I have two local copies, one with my patches, and one without, so
that I can diff between them. Which means my own diffs are not under
CVS control. If anyone knows of a better solution to this problem -
updating a private CVS repository from a remote one that is only
visible when I dial up - I'd be interested to hear about it.)
> > > Isn't there a c for check key thing you can use?
> >
> > Yes, but that's rather inefficient and not the thing you want to use
> > for quick key selection.
>
> Neither is a 6 minute delay for the list to show up :)
Which is the gpg command that is taking 6 minutes? I'm guessing it's:
set pgp_list_pubring_command="gpg --no-verbose --batch --with-colons --list-keys %r"
Has anyone checked the GnuPG mailing lists (which are archived at
www.gnupg.org) whether anyone over there is aware of the problem or
planning to do anything about it?
Edmund
