[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#972875: marked as done (lintian: fix override usage detection for renamed tags)



Your message dated Sun, 25 Oct 2020 11:20:07 -0700
with message-id <CAFHYt56HgdfWL_zoyM7M9CETny0fDNStp2RpQyaspz3YriZLvg@mail.gmail.com>
and subject line Re: lintian: fix override usage detection for renamed tags
has caused the Debian Bug report #972875,
regarding lintian: fix override usage detection for renamed tags
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
972875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972875
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.99.0

I’ve been recompiling musescore2_2.3.2+dfsg3-10.dsc (currently
in sid) on latest sid, to test it for Qt 5.14 compatibility and
latest lintian overrides (modulo #969398, still unfixed).

I’m getting this:

N: Using profile debian/main.
N: Starting on group musescore2/2.3.2+dfsg3-10
N: Finished processing group musescore2/2.3.2+dfsg3-10
E: musescore2 source: malformed-override Unknown tag testsuite-autopkgtest-missing in line 5
N:
E: malformed-override
N:
N:   Lintian discovered an override entry with an invalid format. An
[…]

The overrides file contains just this:

-----
# github doesn’t expose those
musescore2 source: debian-watch-does-not-check-gpg-signature

# not usable / suitable / useful, unfortunately
musescore2 source: testsuite-autopkgtest-missing

# oh really?! what the ever…
musescore2 source: cute-field
-----

Something really weird is happening here; lintian output has
become less reliable and more hard to parse in the last few
months…

--- End Message ---
--- Begin Message ---
Hi Thorsten,

> 2. The override comes up as unused, but that does not seem to be true.
> Your sources do not declare a d/tests/control.

Your sources do not trigger the tag because they do not declare a
Testsuite in d/control. The override detection works fine.

It's possible that the tag meaning changed when the tag was renamed
(and we possibly did not record the old name for that reason). Either
way, this is not a bug.

Please remove the override from your sources. Closing.

Kind regards
Felix Lechner

--- End Message ---

Reply to: