Nikolaus Schulz <[EMAIL PROTECTED]> wrote: > Package: debian-keyring > Version: 2005.05.28 > Severity: normal > > Hi, > > as suggested in the debian-keyring README, I've added the Debian keyrings > directly: > > ,----[ ~/.gnupg/gpg.conf ] > | keyring /usr/share/keyrings/debian-keyring.gpg > | keyring /usr/share/keyrings/debian-keyring.pgp > | keyserver wwwkeys.de.pgp.net > `---- > > Here's a typescript of what happens importing a key: > > penelope[nikolaus]$ gpg --recv-keys XXXXXXXX > gpg: requesting key XXXXXXXX from hkp server wwwkeys.de.pgp.net > gpg: key XXXXXXXX: public key "<id>" imported > gpg: can't create `/usr/share/keyrings/debian-keyring.gpg.tmp': Read-only > file system
Hi Nikolaus, I think this is not a bug. You just missed the next paragraph in the README, telling you ,---- | GPG cannot modify keys in these root-owned files. In order to edit or | sign keys in the Debian keyring you will first need to import them to | your personal keyring. If ~/.gnupg/gpg.conf lists the debian-keyring | files, keys already in the Debian keyring will not be imported to your | personal keyring. You can use "gpg --no-options --import" to force | GPG to ignore gpg.conf and import keys to your personal keyring only. `---- Should we close this bug? Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
