[EMAIL PROTECTED] wrote:
You know, it is a 1000 times easier to just do
$ sa-update --nogpg
than to try to figure our the right way from the messages that
surround "channel: GPG validation failed, channel failed", or the
sa-update man page, or writing this group and asking what to do. So
there, the result is gpg is defeated.
The cure is to have the error message to say
"Do sa-update --import bbblllaaa", with the exact name it wants.
I challenge you to figure it out just from the failure message to
sa-update -D. One ends up lost reading
http://www.gnupg.org/faq/subkey-cross-certify.html.
It is 1000 times easier to just do
$ sa-update --nogpg.
curl -o sa.gpg http://spamassassin.apache.org/updates/GPG.KEY
echo "24F434CE" >> gpg.keys
sa-update --import sa.gpg
echo "updates.spamassassin.org" >> channel.list
curl -o jm.gpg http://yerp.org/rules/GPG.KEY
echo "6C6191E3" >> gpg.keys
sa-update --import jm.gpg
echo "sought.rules.yerp.org" >> channel.list
curl -o sare.gpg http://daryl.dostech.ca/sa-update/sare/GPG.KEY
echo "856AA88A" >> gpg.keys
sa-update --import sare.gpg
#echo "...." >> channel.list
sa-update --gpgkeyfile gpg.keys --channelfile channel.list
I see no gpg failure...
