On Wed, 2012-03-07 at 15:56 +0100, David Kalnischkies wrote: > Note also that we haven't made a changed in 0.8.15.10 to apt-key. > The last changes were in 0.8.15.6 and 0.8.15.3, but both do not > really interact with the removed keyring. Yeah I've had seen that,... > The 'apt-key update' command is triggered in apt (and debian-archive-keyring) > postinst and works with this keyring, but it only does --list-keys on it - > which should be a read-only operation in gpg… Yep,.. I know that what I've reported is really strange/unlikely... it's just that it happened on all of my four servers.... and that made me suspicious... > Does the file /etc/apt/trustdb.gpg exists on your system and has correct > permissions? (600 aka -rw-------) gpg seems to complain about it. Seem to be like that... which message to you refer to? Well I have no further ideas how to trace this down,.. have you any? If not we can let it either open some time (perhaps some other people stumble across the same issue) or we close it. Cheers, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature