also sprach martin f krafft <[EMAIL PROTECTED]> [2006.08.11.1546 +0100]: > fyi, drop [0] into your $PATH before /usr/bin and make it 755.
I've been running this now for a few days and I've seen loads of strangeness, but could not pinpoint an error now. At first, pubring.gpg~ got left over every few runs, but I think that's simply a backup when a new key got downloaded. Then, I started seeing pubring.gpg.tmp being left over, but completely weirdly: -rw------- 1 madduck madduck 16490496 2006-08-13 14:36 pubring.gpg -rw------- 1 madduck madduck 3546722 2006-08-14 08:23 pubring.gpg.tmp -rw------- 1 madduck madduck 17968679 2006-08-12 18:53 pubring.gpg~ Now looking at this, I figure something's broken, and thus I move the .tmp file, only to then see gpg: /home/madduck/.gnupg/pubring.gpg: copy to `/home/madduck/.gnupg/pubring.gpg.tmp' failed: file read error gpg: error writing keyring `/home/madduck/.gnupg/pubring.gpg': file read error on next invocation. It may have spit this out the first time, but I didn't notice, it would explain the .tmp file leftover. Anyway, the weird thing is that the modtime of pubring.gpg did not change, yet all of a sudden gpg reports file read errors. lapse:~> gpg --list-keys >/dev/null gpg: please do a --check-trustdb gpg: keyring_get_keyblock: read error: invalid packet gpg: keydb_get_keyblock failed: invalid keyring Using the ~ file I got it back to working. Unfortunately I got all too confused while doing other stuff, so I don't really have straces yet. But I will try to obtain them from now on. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system
signature.asc
Description: Digital signature (GPG/PGP)
