Ariel Bar-David wrote:
I had the same problem (bad keys generated after dist-upgrade),
and I updated my source.list (in a most newbie way, without
investigating anything)
from:
deb http://mirror.isoc.org.il/pub/debian/ etch main non-free contrib
deb-src http://mirror.isoc.org.il/pub/debian/ etch main non-free
contrib
to:
deb http://security.debian.org/ etch/updates main
deb-src http://security.debian.org/ etch/updates main
deb http://mirror.isoc.org.il/pub/debian etch main contrib
deb-src http://mirror.isoc.org.il/pub/debian etch main contrib
and dist-upgraded again. That did the trick.
Hope that helps.
Actually, it's better to have the "security" repository after the isoc
one. This way, if both have the same package, you will get it from the
geographically closer one.
But, yes, failing to have the security source in source.list will cause
the problem described.
Shachar
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
