Your message dated Sat, 21 Mar 2020 18:55:29 +0000
with message-id <[email protected]>
and subject line Bug#954446: Removed package(s) from unstable
has caused the Debian Bug report #760717,
regarding monkeysign should deal with --no-auto-check-trustdb configurations
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 [email protected]
immediately.)


-- 
760717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760717
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: monkeysign
Version: 2.x
Severity: normal

with current master (commit 5a8d12914a8d4388c6543056098276f6e756e483)
when I try to sign a key, gpg emits an error message about needing to
run with --check-trustdb, and apparently monkeysign is choking on this
output with the following debug info:

Sign all identities? [y/N] y
Really sign key? [y/N] y
command: ['gpg', '--command-fd', '0', '--with-fingerprint',
'--list-options',
'show-sig-subpackets,show-uid-validity,show-unusable-uids,show-unusable-subkeys,show-keyring,show-sig-expire',
'--status-fd', '2', '--quiet', '--batch', '--fixed-list-mode',
'--no-tty', '--with-colons', '--use-agent', '--secret-keyring',
'/home/me/.gnupg/secring.gpg', '--homedir', '/tmp/pygpg-dPlODL',
'--sign-key', 'somefingerprinthere']
SKIPPED: gpg: please do a --check-trustdb
Traceback (most recent call last):
  File "/usr/local/bin/monkeysign", line 4, in <module>
    __import__('pkg_resources').run_script('monkeysign==2.0-dev',
'monkeysign')
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 534, in
run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 1445,
in run_script
    exec(script_code, namespace, namespace)
  File
"/usr/local/lib/python2.7/dist-packages/monkeysign-2.0_dev-py2.7.egg/EGG-INFO/scripts/monkeysign",
line 41, in <module>
      File "build/bdist.linux-x86_64/egg/monkeysign/cli.py", line 69, in
main
  File "build/bdist.linux-x86_64/egg/monkeysign/ui.py", line 296, in
sign_key
  File "build/bdist.linux-x86_64/egg/monkeysign/gpg.py", line 464, in
sign_key
monkeysign.gpg.GpgRuntimeError: [Errno 0] cannot sign: gpg: please do a
--check-trustdb
"

when run interactively, gpg is able to proceed with creating the
signature. but if the uninteractive nature of the interaction with gpg
via monkeysphere restricts us from actually signing keys, then maybe
just handling the exception better around line 464 in sign_key would be
enough.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to en_CA.utf8)
Shell: /bin/sh linked to /bin/dash

Versions of packages monkeysign depends on:
ii  gnupg                 1.4.18-2
ii  python                2.7.8-1
ii  python-pkg-resources  5.5.1-1

Versions of packages monkeysign recommends:
ii  python-gtk2       2.24.0-4
ii  python-qrencode   1.01-4
ii  python-zbar       0.10+doc-9+b2
ii  python-zbarpygtk  0.10+doc-9+b2

monkeysign suggests no packages.

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Version: 2.2.4+rm

Dear submitter,

as the package monkeysign has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954446

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to