pgp as a C programming library in Linux?

Tie Kan tie.kan at
Wed Dec 19 21:27:01 CET 2001

About why some of the tests failed after the package is installed, I
think this is because gpgme library uses only keys in default keyring. 

For example, in 't-encrypt', two keys are added: 'Bob' and 'Alpha'.
These two keys are not added to my default keyring in
~/.gnupg/pubring.gpg. As a result, the keys are invalid and an error of
"no recipient" is thrown. After I modified the lines where keys for
'Bob' and 'Alpha' are added to some valid keys in my default keyring,
everything works fine.

This raises another question: how can I test gpgme library using a user
specified keyring rather than the default keyring? (For example, the
pubring.gpg file that locates in the tests/gpg directory?)

Thanks in advance,

Tie Kan

> Just another thing that you might be interested ...
> 'make check' gives the following results (I add the numeric at the
> to count number of instances):
> 	1.  PASS: t-encrypt
> 	2.  FAIL: t-sign
> 	3.  FAIL: t-signers
> 	4.  FAIL: t-decrypt
> 	5.  PASS: t-verify
> 	6.  FAIL: t-decrypt-verify
> 	7.  PASS: t-keylist
> 	8.  PASS: t-export
> 	9.  PASS: t-import
> 	10. PASS: t-trustlist 
> 	4 tests out of 10 failed.
> I am not really concerned with this problem. Rather, I'll spend a lot
> time trying to understand gpgme.

I see this sometimes, but it doesn't seem to be reproducible.  Esp, I
this when I do funny things, like configuring in the source tree and in
subdirectory (after a make distclean).  Something very strange must go
Usually starting with a fresh copy of the CVS repository works for me.
you try if this fixes it for you?

`Rhubarb is no Egyptian god.' Debian
brinkmd at
Marcus Brinkmann              GNU
marcus at
Marcus.Brinkmann at

More information about the Gnupg-devel mailing list