Hi,
The upstream author of CUPS-PDF recently agreed to publish package
signatures for future releases. While I share the sentiment of the
reporting party, the specific point regarding CUPS-PDF may be moot.
Thank you!
Kind regards,
Felix Lechner
Mattia Rizzolo wrote:
> Yes, if upstream does not publish gpg signatures, you are stuck with
> that tag. You may override it if you wish so (I personally wouldn't),
> but the idea is that you should talk with upstream and "convince" him to
> start doing so.
Martin-Éric, does this resolve your qu
On Sun, Feb 26, 2017 at 01:13:47PM +0200, Martin-Éric Racine wrote:
> No, it does not. Adding a pgpurlmangle option won't magically make
> upstream produce GPG signatures.
Oh, sorry, I misread your first email, reading that your upstream does
provide signatures, and even with that lintian was nagg
2017-02-26 12:07 GMT+02:00 Mattia Rizzolo :
> Control: tag -1 moreinfo
>
> On Sat, Feb 25, 2017 at 01:04:54PM +, Martin-Éric Racine wrote:
>> It appears that debian-watch-may-check-gpg-signature generates false
>> positives.
>>
>> On src:cups-pdf Lintian reports debian-watch-may-check-gpg-sign
Control: tag -1 moreinfo
On Sat, Feb 25, 2017 at 01:04:54PM +, Martin-Éric Racine wrote:
> It appears that debian-watch-may-check-gpg-signature generates false
> positives.
>
> On src:cups-pdf Lintian reports debian-watch-may-check-gpg-signature
> yet upstream does not publish any GPG signat
Package: lintian
Version: 2.5.50.1
Severity: normal
It appears that debian-watch-may-check-gpg-signature generates false positives.
On src:cups-pdf Lintian reports debian-watch-may-check-gpg-signature yet
upstream does not publish any GPG signature. However, upstream does publish
foo.tar.gz.md5
6 matches
Mail list logo
