Bug#913930: lintian: Potentially false-positive public-upstream-key-unusable upstream/signing-key.asc

To: Chris Lamb <lamby@debian.org>
Cc: becue@crans.org, 913930@bugs.debian.org
Subject: Bug#913930: lintian: Potentially false-positive public-upstream-key-unusable upstream/signing-key.asc
From: Felix Lechner <felix.lechner@lease-up.com>
Date: Sun, 18 Nov 2018 15:56:42 -0800
Message-id: <[🔎] CAFHYt57DfNq3Rer_SnbnRQ2kiB5yRPGFJx0Kwr8Q0uGrQjEnFQ@mail.gmail.com>
Reply-to: Felix Lechner <felix.lechner@lease-up.com>, 913930@bugs.debian.org
In-reply-to: <[🔎] 1542579909.3075836.1581189240.41CF5A78@webmail.messagingengine.com>
References: <154244374197.17517.3724526434094595537.reportbug@pimeys.fr> <[🔎] 1542579909.3075836.1581189240.41CF5A78@webmail.messagingengine.com> <154244374197.17517.3724526434094595537.reportbug@pimeys.fr>

Hi Pierre-Elliott,

Looks like the call to 'gpg --list-packets' failed, but I cannot
reproduce the issue. Your report mentioned lintian 2.5.112~bpo9+1 and
stable, while the build log was for lintian 2.5.112 on experimental.
With which release are you working, please? Thank you!

Kind regards,
Felix Lechner

Reply to:

Follow-Ups:
- Bug#913930: lintian: Potentially false-positive public-upstream-key-unusable upstream/signing-key.asc
  - From: Pierre-Elliott Bécue <becue@crans.org>

References:
- Bug#913930: lintian: Potentially false-positive public-upstream-key-unusable upstream/signing-key.asc
  - From: Chris Lamb <lamby@debian.org>

Prev by Date: Build failed in Jenkins: lintian-tests_sid #3424
Next by Date: Bug#913930: lintian: Potentially false-positive public-upstream-key-unusable upstream/signing-key.asc
Previous by thread: Processed: Re: Bug#913930: lintian: Potentially false-positive public-upstream-key-unusable upstream/signing-key.asc
Next by thread: Bug#913930: lintian: Potentially false-positive public-upstream-key-unusable upstream/signing-key.asc
Index(es):
- Date
- Thread