Bug#833585: lintian: Check presence of upstream signature if signing key available
- To: 833585@bugs.debian.org, debian-devel@lists.debian.org
- Subject: Bug#833585: lintian: Check presence of upstream signature if signing key available
- From: Vincent Bernat <bernat@debian.org>
- Date: Mon, 21 Aug 2017 09:30:41 +0200
- Message-id: <[🔎] 87wp5xv0m6.fsf@luffy.cx>
- Reply-to: Vincent Bernat <bernat@debian.org>, 833585@bugs.debian.org
- In-reply-to: <1500156416.1354371.1042070488.19E6D487@webmail.messagingengine.com> (Chris Lamb's message of "Sat, 15 Jul 2017 23:06:56 +0100")
- References: <1500147744.738245.1041997312.7BA6D725@webmail.messagingengine.com> <1231675f-5445-6c35-7986-ee8633af2eca@thykier.net> <1500156416.1354371.1042070488.19E6D487@webmail.messagingengine.com> <20160806120427.GA30480@roeckx.be>
❦ 15 juillet 2017 23:06 +0100, Chris Lamb <lamby@debian.org> :
> Dear Niels,
>
>> You need the $group parameter (the 5th parameter to the run sub).
>
> <snip valuable and much-appreciated guidance>
>
> Bingo, that works. Will tidy a bunch of things up and push it tomorrow.
> Thanks again!
So, this adds a new Lintian "error". I am using gbp and I have no clue
on how to include this signature file. Integration with uscan is not
done either.
Why is it even an error? Could these kind of changes be discussed more
widely?
--
10.0 times 0.1 is hardly ever 1.0.
- The Elements of Programming Style (Kernighan & Plauger)
Attachment:
signature.asc
Description: PGP signature
Reply to: