Sorry for not looking at this earlier. I'm not sure that this was
caused by an upgrade. In any event, it looks like to me like it's
unable to find the key that was used to sign the dsc file. One solution
to this might be to coerce gpgme to read keys from
/usr/share/keyrings/debian-keyring.gpg, but I'm not sure exactly how to
do that.
I think what I'll do for now is to add an option to indicate whether the
signature should be verified or not, and default to not verify.
On Tue, 12 Jun 2018 11:27:47 +, Lumin said:
> Package: whalebuilder Version: 0.6 Severity: serious Justification:
> functionality totally broken
> ~/p/skimage.pkg ❯❯❯ whalebuilder build debdev ./skimage_0.13.1-3.dsc
> Traceback (most recent call last): 13: from
> /usr/bin/whalebuilder:331:in `' 12: from
> /usr/lib/ruby/2.5.0/tmpdir.rb:89:in `mktmpdir' 11: from
> /usr/bin/whalebuilder:338:in `block in ' 10: from
> /usr/lib/ruby/vendor_ruby/gpgme/crypto.rb:311:in `verify' 9: from
> /usr/lib/ruby/vendor_ruby/gpgme/ctx.rb:79:in `new' 8: from
> /usr/lib/ruby/vendor_ruby/gpgme/crypto.rb:313:in `block in verify' 7:
> from /usr/lib/ruby/vendor_ruby/gpgme/crypto.rb:313:in `each' 6: from
> /usr/lib/ruby/vendor_ruby/gpgme/crypto.rb:314:in `block (2 levels) in
> verify' 5: from /usr/bin/whalebuilder:339:in `block (2 levels) in
> ' 4: from /usr/lib/ruby/vendor_ruby/gpgme/signature.rb:81:in
> `to_s' 3: from /usr/lib/ruby/vendor_ruby/gpgme/signature.rb:42:in
> `from' 2: from /usr/lib/ruby/vendor_ruby/gpgme/ctx.rb:79:in `new' 1:
> from /usr/lib/ruby/vendor_ruby/gpgme/signature.rb:43:in `block in
> from' /usr/lib/ruby/vendor_ruby/gpgme/ctx.rb:333:in `get_key':
> EOFError (EOFError)
> ruby/unstable,unstable,now 1:2.5.1 amd64 [installed,automatic]
> ruby-gpgme/unstable,unstable,now 2.0.16-1+b1 amd64
> [installed,automatic]
--
Hubert Chathi -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8 72DE B2DE 88D3 113A 1368
