The GNU project does not list proprietary software as GPG-Shell

Done in the SVN trunk and to be released with GnuPG 2.0.5.
The option to set the creation date is opnly available through
the unattended key generation; see DETAILS (Creation-Date).
All timestamps used during key generation are now the same. Withy card keys the
current scdaemon needs to be used to achive this for cards.

-----BEGIN PGP SIGNED MESSAGE-----

Well, I understand.

I put the status to deferred, as the final decision to keep or remove
gpgme_data_seek will be done when the other deprecated interfaces will be removed.

-----BEGIN PGP SIGNED MESSAGE-----

Why are you using gpg2? Me seems that for your application gpg 1.4 is better
suited.

It is hard to tell what exactly failed. This needs some printf debugging.
Start at g10/keyserser.c:keyserver_spawn.

Oh, and here's my current memory usage in case it's useful:

jh@gir:~$ free -m

total       used       free     shared    buffers     cached

Mem: 160 97 62 0 1 33
-/+ buffers/cache: 61 98
Swap: 63 39 24

jh@gir:~$ gpg --refresh --debug 1024
gpg: reading options from `/home/jh/.gnupg/gpg.conf'
gpg: keyserver communications error: general error
<snipped warnings about specific keys>
gpg: refreshing 1099 keys from hkp://subkeys.pgp.net
gpg: keyserver communications error: general error
gpg: keyserver refresh failed: general error
secmem usage: 1408/1408 bytes in 2/2 blocks of pool 1408/32768

Please add the option

--debug 1024

and run again.

Available in 1.4.7

I have sympathy with you, and if gpgme_data_seek were the only user of off_t in
the GPGME API, there would be some force behind your suggestion. However, it
isn't, and I don't think that keeping around multiple interfaces for essentially
the same function is useful in the long run. That said, I have two things that
may help you:

Implemented for gpg2 (SVN). Will also be backported to gpg1 for 1.4.7.

This is indeed useful.

Implemented in Libgcrypt trunk.

I have commited a similar fix to the SVN (-r1214).

D36: 114_verify-show-primary-only.patch

Moved to libgcrypt until we have implemented this feature.

Date: 2007-01-29 17:03
Sender: Werner Koch

Scheduled for 1.3

We install all the documentaion we consider as useful. If you do not like that,
delete these files after installation.

I think whether --disable-nls is exclusively related to the software may be a
matter of interpretation.

--disable-nls is only related to the software and not to the documentation.

Please quote the releavnt parts of the Makefile (+-10 lines). Makefiles are
generated at configure time and thus I can't see what's wrong. It might also be
useful to send the entire Makefile (use the File field to upload it).

I've implemented this one as --passphrase-repeat. Users may set this to however
many repeats they feel will help them remember the passphrase. If they make an
error, GPG will start over. It defaults to 1 of course, which is the old behavior.

Yes there is ...: Here is the reason why you need it for :

I've found out the problem ... their was a problem with your configure
worked with automake but not with ./configure ....your configure program
has a error then because when I tried to configure with configure & not
automake it did need gnu make to compile otherwise it complained about
line 250 in the makefile being bad for some reason.
can't remember what exactly and will look it up.

There is no need for GNU make with libgpg-error. Automake which creates the
Makefiles won't do any GNU make specific things. If it did, it is an automake
bug and needs to be reported to the automake folks. The next versions will

Actually this is not urgent, but a feature request.

There is a HKP keyserver now running at hkp://demokeys.gnupg.org .
I am currently loading up a snapshot of another keyserver. There won't be any
syncing unless people manually sync.