Re: [arch-general] python2-lockfile signature failure

2014-06-10 Thread Chris Tonkinson
> I had to modify the default signature verification in > `/etc/pacman.conf` to > > SigLevel = Required DatabaseOptional TrustAll > > and now it's looking good. FYI, turns out this wasn't enough for all cases. No combination of signature levels, updating mirrors/databases, clearing /etc/pacm

Re: [arch-general] python2-lockfile signature failure

2014-06-09 Thread Chris Tonkinson
Thanks Michael. After having cleared local keys and running `pacman-key --init` I began seeing even more of these "unknown trust" errors. As you recommend, I had to modify the default signature verification in `/etc/pacman.conf` to SigLevel = Required DatabaseOptional TrustAll and now it's lo

Re: [arch-general] python2-lockfile signature failure

2014-06-09 Thread Michael Boyle
I would check your pacman.conf and make sure you put your siglevels back. They aren't there by default any more. — Sent from Mailbox On Mon, Jun 9, 2014 at 7:31 AM, Chris Tonkinson wrote: > Having just refreshed my desktop system with a clean Arch install, I am > seeing a signature failure in

[arch-general] python2-lockfile signature failure

2014-06-09 Thread Chris Tonkinson
Having just refreshed my desktop system with a clean Arch install, I am seeing a signature failure in the python2-lockfile package (dependency for duplicity). Is anyone else seeing this? `pacman --debug` isn't giving me any additional useful information that I can see. Where might I look next? He