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

Bug#974946: lintian fails hard with disabled changelog-should-mention-nmu tag in vendor profile



Package: lintian
Version: 2.101.0
Severity: important

Hi,

using the following lintian profile:

,---- [ /etc/lintian/profiles/example or ~/.lintian/profiles/example/main.profile ]
| Profile: example/main
| Extends: debian/main
| Disable-Tags: changelog-should-mention-nmu
`----

... then lintian 2.101.0 + 2.101.0~bpo10+1 fails hard with:

,---- [ example run ]
| % lintian --profile=example example_0.42.dsc
| Unknown tags in profile example/main: changelog-should-mention-nmu at /usr/share/lintian/bin/../lib/Lintian/Profile.pm line 612.
|         Lintian::Profile::read_profile(Lintian::Profile=HASH(0x558b15a7e538), "example") called at /usr/share/lintian/bin/../lib/Lintian/Profile.pm line 283
|         Lintian::Profile::load(Lintian::Profile=HASH(0x558b15a7e538), "example", ARRAY(0x558b15b0f4c8), HASH(0x558b15b7c6b0)) called at /usr/bin/lintian line 614
| % echo $?
| 255
`----

AFAICT this issue is caused by the commit:

| "Mass-rename tags for consistency according to the RFC, with some latitude. (Closes: #922544)"
| commit bab2ca64e407e81bbcf625ad8ae945f60f7dcffa
| https://salsa.debian.org/lintian/lintian/-/commit/bab2ca64e407e81bbcf625ad8ae945f60f7dcffa

I'm all for cleaning up, though it would be nice to have backwards
compatibility for such changes. Otherwise it's impossible to use
such a lintian profile on e.g. buster and bullseye systems at the
same time.

regards
-mika-

Attachment: signature.asc
Description: Digital signature


Reply to: