On Mon, Aug 21, 2000 at 01:12:53PM +0200, Morten Liebach wrote:
> I just upgraded lbdb from 0.15.1 (debian package) to 0.19.9 (self
> compiled), and when I tested it I got: _________
>
> morten@pc89225:~$ lbdbq
> /usr/local/bin/lbdbq: line 8: 3754 Aborted $GPG --list-keys
>--with-colons "$@" 2>/dev/null
> 3755 Done(1) | grep '^\(pub\|uid\):\([^:]*:\)\{8,8\}[^<>:]*
><[^<>@: ]*@[^<>@:
> ]*>[^<>@:]*:'
> 3756 Done | sed -e 's/^\([^:]*:\)\{9,9\}\([^<:]*\)
><\([^>:]*\)>.*:.*$/\3 \2 (GnuPG)/'
> 3757 Done | sed -e 's/ \([^ ]\{27,27\}\)[^ ]*
>/\1... /'
> __________
>
> ... and after these lines all of my data base is printed, but that's as it
> should be.
What happens if you run the GPG query by hand? For example:
,----
| gpg --list-keys --with-colons
`----
do you get output?
Also, have a look at m_gpg (probably in /usr/local/lib/m_gpg). Is the GPG
variable set correctly?
--
Take a look in Hagbard's World: | mutt.octet.filter - autoview octet-streams
http://www.hagbard.demon.co.uk/ | mutt.vcard.filter - autoview simple vcards
http://www.acemake.com/hagbard/ | muttrc2html - muttrc -> HTML utility
Free software, including........| muttrc.sl - Jed muttrc mode
