Package: gnupg Version: 1.4.2-1 Severity: normal (I sent this report a few days ago but didn't get an ack from [EMAIL PROTECTED])
The new version of GnuPG doesn't like my keyring: pacem:/tmp$ gpg --check-trustdb gpg: mpi larger than indicated length (2 bytes) gpg: keyring_get_keyblock: read error: invalid packet gpg: keyring_get_keyblock failed: invalid keyring gpg: failed to rebuild keyring cache: invalid keyring gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model gpg: mpi larger than indicated length (2 bytes) gpg: keyring_get_keyblock: read error: invalid packet gpg: keydb_get_keyblock failed: invalid keyring gpg: validate_key_list failed zsh: exit 2 gpg --check-trustdb pacem:/tmp$ If I go back to version 1.4.1-1, --check-trustdb works as intended: pacem:/tmp$ gpg --check-trustdb gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model gpg: depth: 0 valid: 1 signed: 8 trust: 0-, 0q, 0n, 0m, 0f, 1u gpg: depth: 1 valid: 8 signed: 58 trust: 8-, 0q, 0n, 0m, 0f, 0u gpg: next trustdb check due at 2005-11-13 pacem:/tmp$ How do I know which key in my keyring causes the problem? I tried running the command with --debug-all but I doesn't show the key IDs. Thanks, -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (700, 'unstable'), (650, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages gnupg depends on: ii libbz2-1.0 1.0.2-9 high-quality block-sorting file co ii libc6 2.3.5-6 GNU C Library: Shared libraries an ii libldap2 2.1.30-12 OpenLDAP libraries ii libreadline5 5.0-11 GNU readline and history libraries ii libusb-0.1-4 2:0.1.10a-21 userspace USB programming library ii makedev 2.3.1-78 creates device files in /dev ii zlib1g 1:1.2.3-4 compression library - runtime gnupg recommends no packages. -- no debconf information -- ,''`. : :' : Romain Francoise <[EMAIL PROTECTED]> `. `' http://people.debian.org/~rfrancoise/ `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
