Re: lwt compile issue | may be related to the gpg issue both binary and from source

On 3 December 2016 at 14:35, Thomas Leonard <[email protected]> wrote:
> On 2 December 2016 at 02:39, ciryat <[email protected]> wrote:
>> on this system
>>
>> ./0install -vvc selecthttp://repo.roscidus.com/utils/bash  2>&1 | curl -sF 'sprunge=<-' http://sprunge.us
>>
>> This stacktrace
>> => http://sprunge.us/SGGi
>>
>> seems to point to lwt then.
>
> I think something is broken in GnuPG. It's just started happening on
> Debian/unstable too.
>
> On Debian/jessie (GnuPG 2.1.7), I get:
>
> $ curl http://0install.net/tests/newkey -o newkey
> $ gpg --status-fd 1 --keyserver-options no-auto-key-retrieve --verify newkey
> [...]
> [GNUPG:] ERRSIG 9B1F5D7F9721DA90 17 2 01 1118513305 9
>
> According to http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob_plain;f=doc/DETAILS:
>
> *** ERRSIG  <keyid>  <pkalgo> <hashalgo> <sig_class> <time> <rc>
>     It was not possible to check the signature.  This may be caused by
>     a missing public key or an unsupported algorithm.  A RC of 4
>     indicates unknown algorithm, a 9 indicates a missing public
>     key.
>
> So, the 9 at the end means the key was missing, which is 0install's
> trigger to download it.
>
> However, with GnuPG 2.1.16 I get:
>
> [GNUPG:] ERRSIG 9B1F5D7F9721DA90 17 2 01 1118513305 33554441

I've reported this at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846834 and added a
workaround to the 0install source:
https://github.com/0install/0install/commit/a1adaa3b72f7c5251b9bbae0d024fc0b2825b2a3


-- 
talex5 (GitHub/Twitter)        http://roscidus.com/blog/
GPG: 5DD5 8D70 899C 454A 966D  6A51 7513 3C8F 94F6 E0CC
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot