On 2019-02-18 19:05:00 +0100, Jörg Sommrey wrote:
> 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
> workaround.

And probably unsecure.

-- 
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Reply via email to