> Hm, I can't seem to reproduce this in the lintian testsuite. After adding:
>
> --- a/t/tests/legacy-debconf/debian/debian/debconf-test.templates
> +++ b/t/tests/legacy-debconf/debian/debian/debconf-test.templates
> @@ -99,3 +99,15 @@ Type: boolean
>_Description: Decide, lintian
> U
Hi Vincent,
> Great idea, I gave it a try. libxml-simple-perl and lintian
> were installed.
(Please 100% clarify which lintian version you are using)
> E: hello source: not-using-po-debconf
This might be relevant... (The Standards-Version warning can be
On Wed, Nov 21, 2018 at 03:38:01AM -0500, Chris Lamb wrote:
> Hi Vincent.
>
> > Version: 2.5.50.4
> […]
> > I also had a look at the git repository and could not see recent
> > work related to either of the tags involved here.
>
> Granted and will try and reproduce later but just an FYI that
> 2.
Processing commands for cont...@bugs.debian.org:
> tags 914256 + moreinfo
Bug #914256 [lintian] lintian: conflict between no-template-description and
untranslatable-debconf-templates
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
914256: h
Chris Lamb pushed to branch master at lintian / lintian
Commits:
fc77f001 by Felix Lechner at 2018-11-21T17:25:55Z
t/tests/cruft-empty-diff: Remove unnecessary debian/debian/compat.in.
- - - - -
ca2b92e0 by Felix Lechner at 2018-11-21T17:25:55Z
t/runtests: Pass "Dh-Compat-Level" to test template
tags 914256 + moreinfo
thanks
Hi Vincent,
> [..]
Hm, I can't seem to reproduce this in the lintian testsuite. After adding:
--- a/t/tests/legacy-debconf/debian/debian/debconf-test.templates
+++ b/t/tests/legacy-debconf/debian/debian/debconf-test.templates
@@ -99,3 +99,15 @@ Type: boolean
> This suggests that you know tools that behave wrongly.
Unfortunately, I cannot help. I remember having issues when
experimenting with less common version numbers, but that may not have
been with dashes. My hope was to build a fence around policy to save a
maintainer from potential headaches (whi
Hi Felix,
Quoting Felix Lechner (2018-11-21 15:52:02)
> Well, I also agree with Josch's well-articulated argument. A merge
> request to remove the tag is pending (!72). Thank you for bringing
> this to our attention!
in your original commit you were talking about "some tools".
This suggests that
tags 914271 + pending
thanks
Applied in Git, pending upload. Thanks, Felix.
https://salsa.debian.org/lintian/lintian/commit/09d86b2fd208f95a816430e8ce5595b08fe0f3b3
checks/source-changelog.desc | 8
checks/source-changelog.pm | 3 ---
debian/chan
Processing commands for cont...@bugs.debian.org:
> tags 914271 + pending
Bug #914271 [lintian] lintian: Rationale behind
hyphen-in-upstream-part-of-debian-changelog-version
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
914271: https://bugs
Well, I also agree with Josch's well-articulated argument. A merge
request to remove the tag is pending (!72). Thank you for bringing
this to our attention!
[adding felix.lech...@lease-up.com to CC]
Hi Johannes,
> my package rss-bridge was just tagged with […]
As it wasn't immediately obvious from the bug report-alone
rss-bridge | 2018-07-17-1.2 | buster | source, all
rss-bridge | 2018-07-17-1.2 | sid| source, all
> N:
Package: lintian
Version: 2.5.112
Severity: normal
Hi,
my package rss-bridge was just tagged with
hyphen-in-upstream-part-of-debian-changelog-version. The description
text reads:
N: The upstream version in the debian changelog contains one ore more
N: hyphens. While that is okay according to
Hi Vincent.
> Version: 2.5.50.4
[…]
> I also had a look at the git repository and could not see recent
> work related to either of the tags involved here.
Granted and will try and reproduce later but just an FYI that
2.5.112~bpo9+1 is in stretch-backports so it should be easy to
install and recon
Hi Felix,
> As far as the test suite is concerned, the following 23 tags appear to
> be completely untested. (I realize the archive provides great
> validation too.) If you see one of them often, please add a test case:
Can we make the current testsuite print this out as an advisory? That way we
15 matches
Mail list logo
