Your message dated Thu, 29 Dec 2016 12:48:49 +1100
with message-id <20161229014844.nvwvh5lejl5yp...@benfinney.id.au>
and subject line Re: Bug#849455: dput: gpgme reports “Invalid value” when
checking signature
has caused the Debian Bug report #849455,
regarding dput: gpgme reports “Invalid value” when checking signature
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
849455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dput
Version: 0.11.0
Severity: important
Dear Maintainer,
Recently I wanted to sign my package with debsign and then upload to
debian mentors but I got an error, the steps was the following:
$ debsign gpick_0.2.5+git20161221-1_i386.changes
Successfully signed dsc and changes files
$ dput mentors gpick_0.2.5+git20161221-1_i386.changes
Checking signature on .changes
gpgme: /tmp/gpick_upload/gpick_0.2.5+git20161221-1_i386.changes: error
55: Invalid value
(7, 55, u'Invalid value')
I've tried with: debsign -pgpg2 gpick_0.2.5+git20161221-1_i386.changes
but I got the same "Invalid value".
Do you know about this error? Thanks!
Versions:
debsign: 2.16.13
dput: 0.11.0
Best regards,
Elías Alejandro
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 4.6.0-rc6+ (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dput depends on:
ii python-debian 0.1.27
ii python-gpgme 0.3-1.2
ii python-pkg-resources 20.10.1-1.1
pn python:any <none>
dput recommends no packages.
Versions of packages dput suggests:
ii lintian 2.5.49
pn mini-dinstall <none>
ii openssh-client 1:6.7p1-5
ii rsync 3.1.1-3
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: tags -1 - moreinfo + unreproducible
Control: notfound -1 dput/0.11.0
On 28-Dec-2016, Elías Alejandro wrote:
> On Wed, Dec 28, 2016 at 12:21 AM, Ben Finney <bign...@debian.org> wrote:
> > The message from ‘dput’ implies that it does not recognise the
> > result from GPGME about the signature. So this is a valuable test
> > case, thank you for reporting it.
I have reported bug#849519, requesting improved output in cases like
this.
> I've upgraded gnupg to the last version (2.1.17-2) and dput 0.11.0
> works.
> summary:
> gnupg (last version) works with dput 0.11.0
> gnupg (stable version) works with dput 0.11.1
Thank you for verifying that was the problem.
--
\ “A learning experience is one of those things that say, “You |
`\ know that thing you just did? Don't do that.”” —Douglas Adams, |
_o__) 2000-04-05 |
Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature
--- End Message ---
