[dput-ng-maint] Bug#769598: dput-ng: Not finding configured secret key
Ritesh Raj Sarraf
rrs at debian.org
Wed Feb 24 13:13:02 UTC 2016
Package: dput-ng
Version: 1.10
Followup-For: Bug #769598
Can the developers please confirm if this bug is valid ? If not, please
close the bug report.
FYI, I've run into the same problem.
rrs at learner:/tmp$ dcut --force dm --uid D3284E4E61A9278A511ABC9655DB1ABC3818B08C --allow open-iscsi
Uploading commands file to ftp.upload.debian.org (incoming: /pub/UploadQueue/)
Failed to make cleartext signature to commands file:
gpg: no default secret key: secret key not available
gpg: /tmp/tmprz3Ogn: clearsign failed: secret key not available
2016-02-24 / 18:37:46 ♒♒♒ ☹ => 3
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.6+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dput-ng depends on:
ii python-dput 1.10
pn python:any <none>
Versions of packages dput-ng recommends:
ii bash-completion 1:2.1-4.2
dput-ng suggests no packages.
-- no debconf information
More information about the dput-ng-maint
mailing list