Processed: Bug#1009679 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1009679 [lintian] lintian: False positive for OCaml info files
Added tag(s) pending.

-- 
1009679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#880701 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #880701 [lintian] lintian: Please update the Debian archive sections
Added tag(s) pending.

-- 
880701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#973308 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973308 [lintian] lintian: Automate importation of valid archive sections 
via http://
Added tag(s) pending.

-- 
973308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1013331: lintian: Tag hints inside Lintian's own test suite should support wild cards to allow running it on non-amd64 hosts

[Axel Beckert]

Package: lintian
Version: 2.115.1
Severity: wishlist

Citing from
https://ci.debian.net/data/autopkgtest/unstable/arm64/l/lintian/22908861/log.gz
-O debci-lintian-sid-arm64-22908861.log.gz:

# Hints do not match
# 
# --- 
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/hints.specified.calibrated
# +++ 
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/hints.actual.parsed
# -gir1.2-good-42 (binary): typelib-not-in-multiarch-directory 
usr/lib/x86_64-linux-gnu/girepository-1.0 
[usr/lib/girepository-1.0/GoodExtras-42.typelib]
# -gir1.2-good-42 (binary): typelib-not-in-multiarch-directory 
usr/lib/x86_64-linux-gnu/girepository-1.0 
[usr/lib/girepository-1.0/Good-42.typelib]
# +gir1.2-good-42 (binary): typelib-not-in-multiarch-directory 
usr/lib/aarch64-linux-gnu/girepository-1.0 
[usr/lib/girepository-1.0/GoodExtras-42.typelib]
# +gir1.2-good-42 (binary): typelib-not-in-multiarch-directory 
usr/lib/aarch64-linux-gnu/girepository-1.0 
[usr/lib/girepository-1.0/Good-42.typelib]
# 
#   Failed test 'Lintian passes for gir'
#   at /usr/share/lintian/lib/Test/Lintian/Run.pm line 343.
# Looks like you failed 1 test of 1.
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t
 ... 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests 
# Hints do not match
# 
# --- 
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/files/config-scripts/files-old-config-script/hints.specified.calibrated
# +++ 
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/files/config-scripts/files-old-config-script/hints.actual.parsed
# -config-ma-foreign (binary): old-style-config-script-multiarch-path full text 
contains architecture specific dir x86_64-linux-gnu 
[usr/bin/arch-foreign-config]
# -config-ma-foreign (binary): old-style-config-script-multiarch-path full text 
contains architecture specific dir i386-linux-gnu 
[usr/bin/x86_64-linux-gnu_-arch-cross-foreign-config]
# -config-ma-foreign (binary): old-style-config-script-multiarch-path full text 
contains architecture specific dir i386-linux-gnu 
[usr/bin/arch-cross-foreign-config]
# -config-ma-foreign (binary): old-style-config-script 
[usr/bin/x86_64-linux-gnu_-arch-foreign-config]
# -config-ma-foreign (binary): old-style-config-script 
[usr/bin/x86_64-linux-gnu_-arch-cross-foreign-config]
# -config-all (binary): old-style-config-script-multiarch-path-arch-all full 
text contains architecture specific dir x86_64-linux-gnu 
[usr/bin/arch-all-config]
# -config-all (binary): old-style-config-script-multiarch-path-arch-all full 
text contains architecture specific dir i386-linux-gnu 
[usr/bin/x86_64-linux-gnu_-arch-cross-all-config]
# -config-all (binary): old-style-config-script-multiarch-path-arch-all full 
text contains architecture specific dir i386-linux-gnu 
[usr/bin/arch-cross-all-config]
# -config-all (binary): old-style-config-script 
[usr/bin/x86_64-linux-gnu_-arch-cross-all-config]
# -config-all (binary): old-style-config-script 
[usr/bin/x86_64-linux-gnu_-arch-all-config]
# +config-ma-foreign (binary): old-style-config-script-multiarch-path full text 
contains architecture specific dir x86_64-linux-gnu 
[usr/bin/arch-cross-foreign-config]
# +config-ma-foreign (binary): old-style-config-script-multiarch-path full text 
contains architecture specific dir x86_64-linux-gnu 
[usr/bin/aarch64-linux-gnu_-arch-cross-foreign-config]
# +config-ma-foreign (binary): old-style-config-script-multiarch-path full text 
contains architecture specific dir aarch64-linux-gnu 
[usr/bin/arch-foreign-config]
# +config-ma-foreign (binary): old-style-config-script 
[usr/bin/aarch64-linux-gnu_-arch-foreign-config]
# +config-ma-foreign (binary): old-style-config-script 
[usr/bin/aarch64-linux-gnu_-arch-cross-foreign-config]
# +config-all (binary): old-style-config-script-multiarch-path-arch-all full 
text contains architecture specific dir x86_64-linux-gnu 
[usr/bin/arch-cross-all-config]
# +config-all (binary): old-style-config-script-multiarch-path-arch-all full 
text contains architecture specific dir x86_64-linux-gnu 
[usr/bin/aarch64-linux-gnu_-arch-cross-all-config]
# +config-all (binary): old-style-config-script-multiarch-path-arch-all full 
text contains architecture specific dir aarch64-linux-gnu 
[usr/bin/arch-all-config]
# +config-all (binary): old-style-config-script 
[usr/bin/aarch64-linux-gnu_-arch-cross-all-config]
# +config-all (binary): old-style-config-script 
[usr/bin/aarch64-linux-gnu_-arch-all-config]
# 
#   Failed test 'Lintian passes for files-old-config-script'
#   at /usr/share/lintian/lib/Test/Lintian/Run.pm line 343.
# Looks like you failed 1 test of 1.
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/files/config-scripts/files-old-config-script/generic.t
  
Dubious, 

Processed: unmerging 973308

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # a completely differnt issue than 880701 (which is long fixed btw.)
> unmerge 973308
Bug #973308 [lintian] lintian: Automate importation of valid archive sections 
via http://
Bug #880701 [lintian] lintian: Please update the Debian archive sections
Disconnected #973308 from all other report(s).
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
880701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880701
973308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

lintian_2.115.1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Jun 2022 20:53:27 +0200
Source: lintian
Architecture: source
Version: 2.115.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Axel Beckert 
Changes:
 lintian (2.115.1) unstable; urgency=medium
 .
   The "Things we never tested" Release.
 .
   [ Axel Beckert ]
   * Write a test which catches run-time errors of lightweight private
 scripts. Triggered by libconfig-model-dpkg-perl's autopkgtest failure
 since it runs private/latest-policy-version and failed.
   * Fix private/latest-policy-version: $p…->policy_releases →
 $p…->data->policy_releases. Seems to have been forgotten when
 policy_releases() moved from Lintian::Profile to Lintian::Data.
 Should fix libconfig-model-dpkg-perl's autopkgtest failure.
   * Fix documentation of Lintian::Data->new().
   * Switch all GPL URLs in boilerplates and debian/copyright to HTTPS.
   * Add a debian/duck-override file with some false positives. Lintian is
 now also DUCK-clean!
 .
   [ Simon McVittie ]
   * data: Register *.xcf as binary files
Checksums-Sha1:
 d919ecdd26b29d9028b09dccca7c5b6036399dc3 2503 lintian_2.115.1.dsc
 4d7b13853a4d5889d00742685ea56f276e9d630b 2171672 lintian_2.115.1.tar.xz
 3f264a42b7e6c6d190a8b13d8ff1ffbdec8367c2 7274 lintian_2.115.1_source.buildinfo
Checksums-Sha256:
 39352be26e12cbf1a49e72417f9cf98825a880614b5a1a047e31c3f27fbc48a3 2503 
lintian_2.115.1.dsc
 ca81204bc872ddb87335a49dc8726d48f142f00c312fe753b27f4125b8e801a9 2171672 
lintian_2.115.1.tar.xz
 b83732d8ae9a2576a73b764fd4d257f3c596a45de25d2b74871a4cc52b4ec990 7274 
lintian_2.115.1_source.buildinfo
Files:
 a23264442084f9abd8c74a3ba1e0db64 2503 devel optional lintian_2.115.1.dsc
 57de0872650272ad8987f7d6b45bd08f 2171672 devel optional lintian_2.115.1.tar.xz
 d778c4b160d604309557d7cff573f970 7274 devel optional 
lintian_2.115.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAmKyMacACgkQa+Zjx1o1
yXWIQg//aAlA+zSZZXJQu6bmkDFbaFv3rwTMLpDqmLm6qHiaXCBH8qL//m0lxpbD
aSgEEwW4FEiQhrSXFPQZhgv9vi18bHXABRYXeV0t+YbeHNacrb+tQCezRL2Tqwi/
yXvemt7HYjoKZcff0XOEYDsJ4gbaY0I7tk7T4CFQ8FTJ3Un6i/0aelftlw9SaBQr
ZvzpqtT+PDc1BjaxHZlkVyZ6PYoqwGzKsSuUaLRXy8uau79filIpKYu3gVRWq4LM
R1+1CScVxZI39D5FLnPla4ZY9mB8jxnPW27v3B1jeDaWpClClEIvNRbAYrJ9d9P9
jHfKakFXlbtE/tRPGPQKzH/H9c52EVsHadwAA1Dg/nzvYm+5O2CNjqe9EdczYNL/
OriqBL7VmS5RwvuY5Vb31sUnIENv1WNAgEkeRtZyQqngiX45ZCazhD1gpwmaPZRR
ocVhp3Yqxm7Eivlrm9sV8iv1Q5hkoDWPEOuZqTkEJhl6/O8/m0XwTjCkVDoFxr8M
8hScAieXFtS+jG4r7RSSiUN/0zY2SQYZGB74ibN+T7vnospuTy3XhJDKgijgGIvN
XMS2ZA3JD2zrpZTqsqGy/5/Q4yldN/o41sEWT78NH0ByUKX+EF42Mb0z1Pz7FY8m
5pWN32ufAMaIY+b0hZT3+ax4jZGEujIj4EbCzSeT/YdXs1e0+Ac=
=11L6
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processed: severity of 950455 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 950455 important
Bug #950455 [lintian] override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS 
should not be emitted for compat level >= 13
Bug #960807 [lintian] lintian: Don't emit 
override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS with debhelper 13
Bug #960878 [lintian] lintian: do not emit 
override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS tag for debhelper-compat 
>= 13
Bug #969170 [lintian] lintian: fpos for 
override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS
Severity set to 'important' from 'normal'
Severity set to 'important' from 'normal'
Severity set to 'important' from 'normal'
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
950455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950455
960807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960807
960878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960878
969170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processing of lintian_2.115.1_source.changes

[Debian FTP Masters]

lintian_2.115.1_source.changes uploaded successfully to localhost
along with the files:
  lintian_2.115.1.dsc
  lintian_2.115.1.tar.xz
  lintian_2.115.1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

[Git][lintian/lintian] Pushed new tag 2.115.1

[Axel Beckert (@abe)]

Axel Beckert pushed new tag 2.115.1 at lintian / lintian

-- 
View it on GitLab: https://salsa.debian.org/lintian/lintian/-/tree/2.115.1
You're receiving this email because of your account on salsa.debian.org.

Re: Bug#968000: libconfig-model-dpkg-perl: Get policy release dates in another way

[gregor herrmann]

On Tue, 21 Jun 2022 19:35:42 +0200, Axel Beckert wrote:

> chiming in as the new Lintian maintainer. :-)

Thanks, both for caring about lintian and about
libconfig-model-dpkg-perl :)
 
> private/latest-policy-version also seems to be the current way, how
> libconfig-model-dpkg-perl interacts with this data in Lintian.

Yup.
 
> So I'll soon upload lintian 2.115.1 to fix this issue to finally get
> the current Lintian version into testing.

Great, thanks.
 
> Hence I suggest that libconfig-model-dpkg-perl, cme, etc. are then
> using this planned data packages in the future as well.

Sounds like a plan.
 
> I currently the following:
> * Create a new binary package lintian-data, which is built from
>   src:lintian. It will more or less contain /usr/share/lintian/data/.
> * Additionally I will create a file named
>   /usr/share/lintian/data/debian-policy/latest.txt (or similar) at
>   lintian build time based on the output of
>   private/latest-policy-version. (Can even do that already before
>   splitting off that data package.)

Sounds good.

With the only caveat, that this will still lag (at least by some
hours :)) behind debian-policy releases.
But as the cloned policy bug #968154 didn't see any activity lately …
 
> That way you have the wanted data in an easily consumable form without
> having to call any script or module from Lintian and without having to
> parse a huge bunch of JSON.

Since nice.
 
> Would that work out for you?

Yup.
I'm cc'ing dod as the Config::Model::* tsar to make sure I'm not
missing anything.
 
> If so: What are your requirements for such a transition? Do we have to
> just care about Unstable and Testing or are Stable-Backports a topic,
> too?

I believe we never backported libconfig-model-dpkg-perl. Dominique?

So I guess we can just depend on a new enough lintian or lintian-data
with /usr/share/lintian/data/debian-policy/latest.txt (or whatever)
and use it, and from the lintian side you can then add a versioned
Breaks on old libconfig-model-dpkg-perl versions still using
private/latest-policy-version, when you remove it.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Re: Bug#968000: libconfig-model-dpkg-perl: Get policy release dates in another way

[Axel Beckert]

Hi,

chiming in as the new Lintian maintainer. :-)

Felix Lechner wrote:
> Your package is the only known consumer of Lintian's internal Perl
> modules. []

I haven't read all the discussion in this bug report, but I stumbled
upon it due to these lines in debian/lintian.install:

  # the next line will be removed when libconfig-model-dpkg-perl stops using 
Lintian data (Bug#968000)
  private/latest-policy-version   usr/share/lintian/private

private/latest-policy-version also seems to be the current way, how
libconfig-model-dpkg-perl interacts with this data in Lintian.

Actually the fact that this script is used in
libconfig-model-dpkg-perl's autopkgtest caused a regression in (or by
and for) lintian 2.115.0 because Felix moved one method used in this
script from Lintian::Profile to Lintian::Data and forgot to update
this script (which Lintian itself doesn't seem to use).

So I'll soon upload lintian 2.115.1 to fix this issue to finally get
the current Lintian version into testing.

On the other it seems as if no lintian-internal check caught this
issue, so I'm kinda happy that this has happend. But it also shows
what happens if internal modules or so are used. ;-)

For a potential long term solution:

On #debian-qa, pabs (Cc'ed) was suggesting to the Lintian and DUCK
maintainers (Cc'ed as well) to use a common data package for data
currently synced occassionally between both source packages. I
suggested to build that data out of src:lintian and the duck
maintainer was happy with that.

Hence I suggest that libconfig-model-dpkg-perl, cme, etc. are then
using this planned data packages in the future as well.

I currently the following:

* Create a new binary package lintian-data, which is built from
  src:lintian. It will more or less contain /usr/share/lintian/data/.

* Additionally I will create a file named
  /usr/share/lintian/data/debian-policy/latest.txt (or similar) at
  lintian build time based on the output of
  private/latest-policy-version. (Can even do that already before
  splitting off that data package.)

That way you have the wanted data in an easily consumable form without
having to call any script or module from Lintian and without having to
parse a huge bunch of JSON.

And we can easily ship that file in a pure data package, not requiring
you to pull in all dependencies of Lintian, either.

Would that work out for you?

If so: What are your requirements for such a transition? Do we have to
just care about Unstable and Testing or are Stable-Backports a topic,
too?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: PGP signature

Processed: Re: Bug#1013314: lintian: REUSE license text should suppress very-long-line-length-in-source-file

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1013314 [lintian] lintian: REUSE license text should suppress 
very-long-line-length-in-source-file
Added tag(s) patch.
> forwarded -1 https://salsa.debian.org/lintian/lintian/-/merge_requests/396
Bug #1013314 [lintian] lintian: REUSE license text should suppress 
very-long-line-length-in-source-file
Set Bug forwarded-to-address to 
'https://salsa.debian.org/lintian/lintian/-/merge_requests/396'.

-- 
1013314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1013314: lintian: REUSE license text should suppress very-long-line-length-in-source-file

[Simon McVittie]

Control: tags -1 + patch
Control: forwarded -1 
https://salsa.debian.org/lintian/lintian/-/merge_requests/396

On Tue, 21 Jun 2022 at 13:36:49 +0100, Simon McVittie wrote:
> I'll send a patch when I get a bug number back from the BTS.

Please see the MR linked above.

smcv

[Git][lintian/lintian] Pushed new branch salsa-debug

[Axel Beckert (@abe)]

Axel Beckert pushed new branch salsa-debug at lintian / lintian

-- 
View it on GitLab: https://salsa.debian.org/lintian/lintian/-/tree/salsa-debug
You're receiving this email because of your account on salsa.debian.org.

Bug#1013314: lintian: REUSE license text should suppress very-long-line-length-in-source-file

[Simon McVittie]

Package: lintian
Version: 2.115.0
Severity: minor

The REUSE specification  encourages upstreams
to put complete license text in files with SPDX-based names (for example
LICENSES/MIT.txt for Expat's license), and reference the licenses from
source code using SPDX declarations like "SPDX-License-Identifier: MIT".

Upstreams are encouraged to use a canonical form for the license text,
which can be fetched with the `reuse download` command. This canonical
form is soft-wrapped (no line length limit, no newlines except where
semantically significant) and therefore has very long lines.

It would be good for Lintian to suppress
very-long-line-length-in-source-file for these license files: none of
the reasons cited in the tag description seem like they apply to license
text. I'll send a patch when I get a bug number back from the BTS.

smcv

[Git][lintian/lintian][master] 4 commits: Write a test which catches run-time errors of lightweight private scripts

[Axel Beckert (@abe)]

Axel Beckert pushed to branch master at lintian / lintian


Commits:
8ec7fc75 by Axel Beckert at 2022-06-21T12:43:39+02:00
Write a test which catches run-time errors of lightweight private scripts

Triggered by autopkgtest failure of libconfig-model-dpkg-perl which
runs private/latest-policy-version and failed.

Gbp-Dch: Full

- - - - -
74e9fe65 by Axel Beckert at 2022-06-21T12:45:13+02:00
Fix private/latest-policy-version: $p…-policy_releases → 
$p…-data-policy_releases

Seems to have been forgotten when policy_releases() moved from
Lintian::Profile to Lintian::Data.

Should fix libconfig-model-dpkg-perl
autopkgtest.

Gbp-Dch: Full

- - - - -
65a0c7db by Axel Beckert at 2022-06-21T12:45:13+02:00
Fix documentation of Lintian::Data-new()

- - - - -
6dd3c1b1 by Axel Beckert at 2022-06-21T12:45:13+02:00
Switch all GPL URLs in boilerplates to HTTPS

- - - - -


30 changed files:

- bin/lintian
- bin/lintian-annotate-hints
- bin/lintian-explain-tags
- commands/reporting-harness.pm
- commands/reporting-html-reports.pm
- commands/reporting-lintian-harness.pm
- commands/reporting-sync-state.pm
- lib/Lintian/Archive.pm
- lib/Lintian/Changelog.pm
- lib/Lintian/Changelog/Version.pm
- lib/Lintian/Check.pm
- lib/Lintian/Check/Apache2.pm
- lib/Lintian/Check/ApplicationNotLibrary.pm
- lib/Lintian/Check/AppstreamMetadata.pm
- lib/Lintian/Check/Apt.pm
- lib/Lintian/Check/Archive/File/Name/Length.pm
- lib/Lintian/Check/Archive/Liberty/Mismatch.pm
- lib/Lintian/Check/Archive/NonFree/Autobuild.pm
- lib/Lintian/Check/Binaries.pm
- lib/Lintian/Check/Binaries/Architecture.pm
- lib/Lintian/Check/Binaries/Architecture/Other.pm
- lib/Lintian/Check/Binaries/Corrupted.pm
- lib/Lintian/Check/Binaries/DebugSymbols.pm
- lib/Lintian/Check/Binaries/DebugSymbols/Detached.pm
- lib/Lintian/Check/Binaries/Hardening.pm
- lib/Lintian/Check/Binaries/LargeFileSupport.pm
- lib/Lintian/Check/Binaries/Location.pm
- lib/Lintian/Check/Binaries/Obsolete/Crypt.pm
- lib/Lintian/Check/Binaries/Prerequisites.pm
- lib/Lintian/Check/Binaries/Prerequisites/Numpy.pm


The diff was not included because it is too large.


View it on GitLab: 
https://salsa.debian.org/lintian/lintian/-/compare/9891622bd15d0a72c0ff1802706be863b2811fbe...6dd3c1b15e2e58fb2dfd0d5507850e115e798251

-- 
View it on GitLab: 
https://salsa.debian.org/lintian/lintian/-/compare/9891622bd15d0a72c0ff1802706be863b2811fbe...6dd3c1b15e2e58fb2dfd0d5507850e115e798251
You're receiving this email because of your account on salsa.debian.org.