I'm faced with a similar issue.  Starting sa-update from a terminal
revealed more details.  The update file was claimed to be signed by an
unknown gpg key.  However, the mentionded key exists in the pubring.  I
was able to update using "sa-update --nogpg", but this is just a


Reply via email to