Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1135916

Bug#1030271: dpkg-buildpackage: misleading error message when no signing key available

From Guillem Jover <guillem@debian.org>
Newsgroups linux.debian.bugs.dist, linux.debian.maint.dpkg
Subject Bug#1030271: dpkg-buildpackage: misleading error message when no signing key available
Date 2023-02-01 23:20 +0100
Message-ID <FUtCp-2KUr-1@gated-at.bofh.it> (permalink)
References <FUsdj-2JSq-1@gated-at.bofh.it> <FUsdj-2JSq-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


Control: tag -1 moreinfo

On Wed, 2023-02-01 at 21:40:23 +0100, Thorsten Glaser wrote:
> Package: dpkg
> Version: 1.21.19
> Severity: minor
> X-Debbugs-Cc: tg@mirbsd.de

> gpg: skipped "Thorsten Glaser <tg@mirbsd.de>": secret key not available
> gpg: dpkg-sign.IRqYlate/dygraphs_2.2.0-4.dsc: clearsign failed: secret key not available
> dpkg-buildpackage: error: failed to sign dygraphs_2.2.0-4.dsc file: key is not signature-capable
> 
> The error message is a bit misleading here.

Could you expand a bit, it's not directly obvious from the short
report. Is this about the "secret key not available" vs the
"key is not signature-capable"? Either of them? Something else?

Thanks,
Guillem

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1030271: dpkg-buildpackage: misleading error message when no signing key available Thorsten Glaser <tg@mirbsd.de> - 2023-02-01 21:50 +0100
  Bug#1030271: dpkg-buildpackage: misleading error message when no signing key available Guillem Jover <guillem@debian.org> - 2023-02-01 23:20 +0100
    Bug#1030271: dpkg-buildpackage: misleading error message when no signing key available Thorsten Glaser <tg@mirbsd.de> - 2023-02-02 00:50 +0100

csiph-web