Bug#1030586: lintian: Testsuite failure on some systems: 1h time offset in test ancient-source

[Axel Beckert]

Hi Russ,

Russ Allbery wrote:
> > # -ancient-source (source): unpack-message-for-source tar: 
> > ancient-source-1.0/README: implausibly old time stamp 1969-12-31 23:59:59
> > # +ancient-source (source): unpack-message-for-source tar: 
> > ancient-source-1.0/README: implausibly old time stamp 1970-01-01 00:59:59
> 
> The exactly one hour difference makes me suspicious something is going on
> with time zone conversions.  That's also consistent with the one hour time
> difference between UTC and Europe/Zurich at New Years.
> 
> Looking at the source of tar, the output timestamp for this error seems to
> be in local time by default, which would certainly explain the problem but
> not why we're not seeing it everywhere.  I would be curious if it went
> away if you added --utc to the flags to tar in
> Lintian::IO::Select::unpack_and_index_piped_tar

Nice idea! Will definitely try.

> or (bigger hammer) just set TZ=UTC when running Lintian.

I tried with TZ=GMT. I also tried TZ=UTC, but that had no effect. I
think you need to use TZ=Etc/UTC there instead.

> Lintian should probably force all output it controls to UTC for
> reproducibility, including tar's, but I'm still mystified as to why it
> works on the other system.  This part of tar doesn't seem to have changed,
> and as you mentioned replacing tar didn't change anything.

Exactly. All of that. :-)

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

Bug#1030586: lintian: Testsuite failure on some systems: 1h time offset in test ancient-source

[Axel Beckert]

Hi Vagrant,

Vagrant Cascadian wrote:
> On 2023-02-05, Axel Beckert wrote:
> > While running Lintian's testsuite on a much faster system compared to
> > my Sid amd64 running development workstation, I noticed the following
> > test suite failure when running "private/runtests" or trying to build
> > the package on a more modern and more performant box with Bookworm
> > amd64. (Use "private/runtests -o test:ancient-source" to just run the
> > affected test.)
> >
> > # Hints do not match
> > # 
> > # --- 
> > debian/test-out/eval/checks/unpack/ancient-source/hints.specified.calibrated
> > # +++ debian/test-out/eval/checks/unpack/ancient-source/hints.actual.parsed
> > # -ancient-source (source): unpack-message-for-source tar: 
> > ancient-source-1.0/README: implausibly old time stamp 1969-12-31 23:59:59
> > # +ancient-source (source): unpack-message-for-source tar: 
> > ancient-source-1.0/README: implausibly old time stamp 1970-01-01 00:59:59
> 
> Wild guess would be timezone differences between the build
> environments?

Yeah, that's what I looked for first, but both boxes have
"Europe/Zurich" as timezone and prepending "env TZ=GMT" didn't make a
difference on either side.

Thanks for caring nevertheless!

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

Bug#1007922: false positive spelling: substract and subtract is both correct

[Brian Thompson]

I like the idea of keeping the spelling correction in place.  I've never seen 
"substract" being used.  Keeping the correction reduces ambiguity and keeps 
language consistent.

Motion to close.

Sincerely,

Brian

publickey - brianrobt@pm.me - 0xC8F2EC48.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#1030586: lintian: Testsuite failure on some systems: 1h time offset in test ancient-source

[Vagrant Cascadian]

On 2023-02-05, Axel Beckert wrote:
> While running Lintian's testsuite on a much faster system compared to
> my Sid amd64 running development workstation, I noticed the following
> test suite failure when running "private/runtests" or trying to build
> the package on a more modern and more performant box with Bookworm
> amd64. (Use "private/runtests -o test:ancient-source" to just run the
> affected test.)
>
> # Hints do not match
> # 
> # --- 
> debian/test-out/eval/checks/unpack/ancient-source/hints.specified.calibrated
> # +++ debian/test-out/eval/checks/unpack/ancient-source/hints.actual.parsed
> # -ancient-source (source): unpack-message-for-source tar: 
> ancient-source-1.0/README: implausibly old time stamp 1969-12-31 23:59:59
> # +ancient-source (source): unpack-message-for-source tar: 
> ancient-source-1.0/README: implausibly old time stamp 1970-01-01 00:59:59

Wild guess would be timezone differences between the build environments?

live well,
  vagrant

Bug#1030586: lintian: Testsuite failure on some systems: 1h time offset in test ancient-source

[Russ Allbery]

Axel Beckert  writes:

> While running Lintian's testsuite on a much faster system compared to
> my Sid amd64 running development workstation, I noticed the following
> test suite failure when running "private/runtests" or trying to build
> the package on a more modern and more performant box with Bookworm
> amd64. (Use "private/runtests -o test:ancient-source" to just run the
> affected test.)

> # Hints do not match
> # 
> # --- 
> debian/test-out/eval/checks/unpack/ancient-source/hints.specified.calibrated
> # +++ debian/test-out/eval/checks/unpack/ancient-source/hints.actual.parsed
> # -ancient-source (source): unpack-message-for-source tar: 
> ancient-source-1.0/README: implausibly old time stamp 1969-12-31 23:59:59
> # +ancient-source (source): unpack-message-for-source tar: 
> ancient-source-1.0/README: implausibly old time stamp 1970-01-01 00:59:59

The exactly one hour difference makes me suspicious something is going on
with time zone conversions.  That's also consistent with the one hour time
difference between UTC and Europe/Zurich at New Years.

Looking at the source of tar, the output timestamp for this error seems to
be in local time by default, which would certainly explain the problem but
not why we're not seeing it everywhere.  I would be curious if it went
away if you added --utc to the flags to tar in
Lintian::IO::Select::unpack_and_index_piped_tar or (bigger hammer) just
set TZ=UTC when running Lintian.

Lintian should probably force all output it controls to UTC for
reproducibility, including tar's, but I'm still mystified as to why it
works on the other system.  This part of tar doesn't seem to have changed,
and as you mentioned replacing tar didn't change anything.

-- 
Russ Allbery (r...@debian.org)  

Bug#1030586: lintian: Testsuite failure on some systems: 1h time offset in test ancient-source

[Axel Beckert]

Package: lintian
Version: 2.116.3
Severity: important
Tags: ftbfs

While running Lintian's testsuite on a much faster system compared to
my Sid amd64 running development workstation, I noticed the following
test suite failure when running "private/runtests" or trying to build
the package on a more modern and more performant box with Bookworm
amd64. (Use "private/runtests -o test:ancient-source" to just run the
affected test.)

# Hints do not match
# 
# --- 
debian/test-out/eval/checks/unpack/ancient-source/hints.specified.calibrated
# +++ debian/test-out/eval/checks/unpack/ancient-source/hints.actual.parsed
# -ancient-source (source): unpack-message-for-source tar: 
ancient-source-1.0/README: implausibly old time stamp 1969-12-31 23:59:59
# +ancient-source (source): unpack-message-for-source tar: 
ancient-source-1.0/README: implausibly old time stamp 1970-01-01 00:59:59
# 
debian/test-out/eval/checks/unpack/ancient-source/generic.t .. 1/1 #   Failed 
test 'Lintian passes for ancient-source'
#   at /home/abe/debian/lintian/lib/Test/Lintian/Run.pm line 343.
# Looks like you failed 1 test of 1.

But I neither get that failure on my Sid amd64 development workstation
nor on SalsaCI (https://salsa.debian.org/lintian/lintian/-/pipelines)
nor in pbuilder nor on the buildd
(https://buildd.debian.org/status/package.php?p=lintian).

So I tried to find differences.

$ als 
debian/test-out/packages/checks/unpack/ancient-source/ancient-source_1.0.orig.tar.gz
 ancient-source-1.0/README
-rw-r--r-- root/root21 1970-01-01 00:59 ancient-source-1.0/README
$ env TZ=GMT als 
debian/test-out/packages/checks/unpack/ancient-source/ancient-source_1.0.orig.tar.gz
 ancient-source-1.0/README
-rw-r--r-- root/root21 1969-12-31 23:59 ancient-source-1.0/README

But these two outputs are identical on both hosts, the one where the
test fails and one of those where it doesn't fail.  So the timestamp
actually seems to be the same and it's just Lintian's parsing of it
seems to differ.

The only potentially relevant package version difference I found was
tar, which is at 1.34+dfsg-1.1 in Sid and 1.34+dfsg-1 in Bookworm due
to a recent FTBFS on 32-bit architectures. But the sole change was in
debian/copyright and also downgrading the tar version in Sid to the
one from Bookworm didn't make the test failing on Sid.

Also running the test suite with "env TZ=GMT" prepended didn't make a
difference.

Additionally, build 2.116.2 did work on that very same box where
2.116.3 now FTBFS. So it seems to have caused been a recent change
(since 2023-01-29) in Bookworm. Or maybe such a change just uncovered
an older bug.

The locales of two systems where it builds and where it no more
builds:

Builds fine:

LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_PAPER="C.UTF-8"
LC_NAME="C.UTF-8"
LC_ADDRESS="C.UTF-8"
LC_TELEPHONE="C.UTF-8"
LC_MEASUREMENT="C.UTF-8"
LC_IDENTIFICATION="C.UTF-8"
LC_ALL=

No more builds fine (but hasn't change since when it still built
fine):

LANG=C
LANGUAGE=
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=

Also both systems have "Europe/Zurich" in their /etc/timezone.

So I currently have no idea where the difference comes from or which
environmental change (variables or package versions) triggers
it. Cc'ing the Reproducible Builds project in the hope that they have
an idea what could have caused the 1h offset in the testsuite on that
one box.

Bug report written on the system where the test failed.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages lintian depends on:
ii  binutils2.40-2
ii  bzip2   1.0.8-5+b1
ii  clzip [lzip-decompressor]   1.13-5
ii  diffstat1.65-1
ii  dpkg1.21.19
ii  dpkg-dev1.21.19
ii  file1:5.44-3
ii  gettext 0.21-10
ii  gpg 2.2.40-1
ii  intltool-debian 0.35.0+20060710.6
ii  iso-codes   4.12.0-1
ii  libapt-pkg-perl 0.1.40+b2
ii  libarchive-zip-perl 1.68-1
ii  libberkeleydb-perl  0.64-2+b1
ii  libcapture-tiny-perl0.48-2
ii  libclass-xsaccessor-perl1.19-4+b1
ii  libclone-perl   0.46-1
ii  libconfig-tiny-perl 2.28-2
ii  libconst-fast-perl  0.014-2
ii  

Bug#1013417: lintian: dkms updates

[Axel Beckert]

Hi Andreas,

Andreas Beckmann wrote:
> attached is a patch that fixes the lintian warning about a missing
> dh-dkms dependency for using dh_dkms.

Applied without the (IMHO bogus) debian/changelog changes as
https://salsa.debian.org/lintian/lintian/-/commit/d50a732a00a7596d078a9e8f6919cb6362ca0067

> I'm not closing this bug since it does not address the
> autopkgtest-pkg-dkms recommendation.

Ok. I've allowed myself to nevertheless add a reference to this bug
report as "(See #1013417)" in a way that it will also show up in the
later generated debian/changelog entry.

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

[Git][lintian/lintian][master] 2 commits: Post-release version bump

[Axel Beckert (@abe)]

Axel Beckert pushed to branch master at lintian / lintian


Commits:
1e177f85 by Axel Beckert at 2023-02-05T11:30:30+01:00
Post-release version bump

Gbp-Dch: Ignore

- - - - -
d50a732a by Andreas Beckmann at 2023-02-05T11:37:36+01:00
dh_dkms is now provided by dh-dkms instead of dkms

(See #1013417)

Gbp-Dch: Full

- - - - -


2 changed files:

- debian/changelog
- lib/Lintian/Check/Debhelper.pm


Changes:

=
debian/changelog
=
@@ -1,3 +1,9 @@
+lintian (2.116.4~git) UNRELEASED; urgency=medium
+
+  * WIP (generated at release time: please do not add entries below.)
+
+ -- Axel Beckert   Sun, 05 Feb 2023 11:30:30 +0100
+
 lintian (2.116.3) unstable; urgency=medium
 
   The "FFP3 (Fixing False Positives, Three Small Changes)" Release.


=
lib/Lintian/Check/Debhelper.pm
=
@@ -81,7 +81,7 @@ my %DH_COMMAND_MANUAL_PREREQUISITES = (
 'dh-autoreconf:any | debhelper:any (>= 9.20160403~) | debhelper-compat:any',
 dh_autoreconf =>
 'dh-autoreconf:any | debhelper:any (>= 9.20160403~) | debhelper-compat:any',
-dh_dkms => 'dkms:any | dh-sequence-dkms:any',
+dh_dkms => 'dh-dkms:any | dh-sequence-dkms:any',
 dh_girepository => 'gobject-introspection:any | dh-sequence-gir:any',
 dh_gnome => 'gnome-pkg-tools:any | dh-sequence-gnome:any',
 dh_gnome_clean => 'gnome-pkg-tools:any | dh-sequence-gnome:any',



View it on GitLab: 
https://salsa.debian.org/lintian/lintian/-/compare/cac78dd88e1171e88ee8c3d6f5b1155b8081863d...d50a732a00a7596d078a9e8f6919cb6362ca0067

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

Bug#1030325: lintian: archive-liberty-mismatch (in section for firmware-nvidia-gsp) non-free-firmware vs non-free

[Axel Beckert]

Hi Andreas,

Andreas Beckmann wrote:
> > And then release Lintian 2.116.3.
> 
> Please include the dkms patch (see other bug), too.

Sorry, just like 10 minutes too late and I indeed forgot to include it
that one today. Meh.

But there might be a 2.116.4 as I ran into a test suite failure on a
Bookworm system which seems new (as the test suite ran their fine a
week ago or so) and which I currently neither see on autokpkgtest nor
my Sid system nor in pbuilder (2.116.3 built fine there). And it's a
part of Lintian which hasn't been touched recently, so it looks like
being something the Reproducible Build team might find.

I just didn't want to wait further with the upload. :-/ I'm currently in
the release early, release often mode, at least for Lintian. ;-)

Anyway, will probably file a bug report about that non-reproducible
test suite failure soon if I can't find the cause for it:

-ancient-source (source): unpack-message-for-source tar: 
ancient-source-1.0/README: implausibly old time stamp 1969-12-31 23:59:59
+ancient-source (source): unpack-message-for-source tar: 
ancient-source-1.0/README: implausibly old time stamp 1970-01-01 00:59:59

But:

$ env TZ=GMT als 
debian/test-out/packages/checks/unpack/ancient-source/ancient-source_1.0.orig.tar.gz
 ancient-source-1.0/README
-rw-r--r-- root/root21 1969-12-31 23:59 ancient-source-1.0/README

Both hosts have the same timezone (Europe/Zurich aka CET aka GMT+0100)
and one has the "C.UTF-8" locale and the other one (the one which
fails) has "C" locale.

No other difference found so far, except tar which currently doesn't
migrate to testing due to FTBFS on 32-bit architectures. But
downgrading tar on the Sid box didn't make it start failing the test,
so that's not the cause.

Also prepending env TZ=GMT to any command didn't help to get the same
result either.

> On 05/02/2023 06.47, Axel Beckert wrote:
> > Unfortunately firmware-nvidia-gsp/nvidia-graphics-drivers is rather
> > large and I ran out of disk space when first unpacking it in my home
> 
> Then you should try src:nvidia-cuda-toolkit ;-) Lintian needs 3-4 hours and
> about 50GB in /tmp to process a binary build. On nvme.

Ouch. :-)

> I'll probably come back with a bug report about lintian crashing (after a
> few hours) when processing cuda 12 (but first need to check with the latest
> lintian version again and also check that there was enough free space in
> /tmp)

Yes, please do. We managed to get improvements after such bug reports
with src:linux, PostgreSQL and the Firefox packages. It's always good
to have real-life examples of such issues. (And these are the type of
issues you don't test in test suites. ;-)

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

lintian_2.116.3_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 Feb 2023 09:10:20 +0100
Source: lintian
Architecture: source
Version: 2.116.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Axel Beckert 
Closes: 1030325
Changes:
 lintian (2.116.3) unstable; urgency=medium
 .
   The "FFP3 (Fixing False Positives, Three Small Changes)" Release.
 .
   [ Axel Beckert ]
   * Refresh data. (Loong64 removed from two lists, some fonts and dh_cruft
 added.)
 .
   [ Simon McVittie ]
   * obsolete-packages: libegl1-mesa-dev is not obsolete.
 .
   [ Andreas Beckmann ]
   * archive-liberty-mismatch: Add exception for 'non-free-firmware binary
 package build from non-free source package'. (Closes: #1030325)
Checksums-Sha1:
 130a23df8ed994592043cea87ff16c350f8dbaf9 3922 lintian_2.116.3.dsc
 8f8831848acff9c08f215d1f73dd8e22133f6a3c 2230340 lintian_2.116.3.tar.xz
 f219d27fe3dfd9d58813be0ae70e1b63809b7d49 27774 lintian_2.116.3_source.buildinfo
Checksums-Sha256:
 784b953ddccf4a258d49b63da03c70577852a16f5bcc5d5b4caaf75bfed37a22 3922 
lintian_2.116.3.dsc
 97c76a71920be1f18a72fc741155f6694a8eb0cbfb073ab3e6d6678262801a91 2230340 
lintian_2.116.3.tar.xz
 12d579cd41ee84c4d54cbee650da5e16f4d2e7f8b1529e48b1a03ae8760beaa5 27774 
lintian_2.116.3_source.buildinfo
Files:
 b5e01bd7a59aa80afd4df59eeebe4e17 3922 devel optional lintian_2.116.3.dsc
 ff8bf51113c6707e1eaf7db3c415df9b 2230340 devel optional lintian_2.116.3.tar.xz
 9d20fa47abd2c67614e23eb0e97d262d 27774 devel optional 
lintian_2.116.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAmPfd0kACgkQa+Zjx1o1
yXVtww//VB7FjjjNzHxhUMokcLadihhJpyAUrWhDNlMFyTA0GB32R0kzJHa4Qz4T
xnO3eT1pQQwww4lped+OBdal+7M3SVSVUbvn2z3e2aUMnIHTI6bo6vMLUG5qIDSI
BtjHRW/l3D7MrLKtHCj9js/s+4BF7PRjLGZlna7AoRKynBgr877/xnvY/fwGyVkI
xBaSAkXQEO6JtP1gXDyoenIFglR94ys/8C79MvmQomsyvpRzcmKjkbaBYnx6ZswG
+iXTryKvMHx7R5l1hig8CO5ek5g6poOmL2sWtLMhhruBo0w5P7siPDRVxvJyo00u
mCvCEIw8/lWG3K4ZGMUMPMfJwPtEkRp+m8mFYhen92V/Ge6h9dWmHBQdNLdzemMT
ax7Kgvwv8NMzkJW7cXM1Fke9/ShVBR9XFgKPjW2OB2oZRPWxDrrwCo59hIHZ8ngn
ABRpa99M+15ns2jCpDo/NuSOW3N9PTTLXN5oHg8GU7/p8TAItWI1RuUOS8qA7IKB
dY0lSBnnxFstaazNK1XKx0JkAZRpC1oqx2UNhTLxoOCVxB0pddUKN7bFkMsmt9lD
cR7t50Yz7p0CzWAretDtddgzVVP/yluE2YhOQtbyRY7S0ZI7wK6SvYtoYC/nuBvz
7yNs5uhevM3Z05zH4S9akQy8JXXFk4yOZHc1ZzXHgLrz/mrqzxk=
=PoAC
-END PGP SIGNATURE-

Bug#1030325: marked as done (lintian: archive-liberty-mismatch (in section for firmware-nvidia-gsp) non-free-firmware vs non-free)

[Debian Bug Tracking System]

Your message dated Sun, 05 Feb 2023 09:53:31 +
with message-id 
and subject line Bug#1030325: fixed in lintian 2.116.3
has caused the Debian Bug report #1030325,
regarding lintian: archive-liberty-mismatch (in section for 
firmware-nvidia-gsp) non-free-firmware vs non-free
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 ow...@bugs.debian.org
immediately.)


-- 
1030325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.116.2
Severity: important
X-Debbugs-Cc: Cyril Brulebois 

Hi,

while preparing the move of firmware-nvidia-gsp from non-free to
non-free-firmware I noticed this error from lintian:

E: nvidia-graphics-drivers source: archive-liberty-mismatch (in section for 
firmware-nvidia-gsp) non-free-firmware vs non-free [debian/control:106]


Andreas
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.116.3
Done: Axel Beckert 

We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1030...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated lintian package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 Feb 2023 09:10:20 +0100
Source: lintian
Architecture: source
Version: 2.116.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Axel Beckert 
Closes: 1030325
Changes:
 lintian (2.116.3) unstable; urgency=medium
 .
   The "FFP3 (Fixing False Positives, Three Small Changes)" Release.
 .
   [ Axel Beckert ]
   * Refresh data. (Loong64 removed from two lists, some fonts and dh_cruft
 added.)
 .
   [ Simon McVittie ]
   * obsolete-packages: libegl1-mesa-dev is not obsolete.
 .
   [ Andreas Beckmann ]
   * archive-liberty-mismatch: Add exception for 'non-free-firmware binary
 package build from non-free source package'. (Closes: #1030325)
Checksums-Sha1:
 130a23df8ed994592043cea87ff16c350f8dbaf9 3922 lintian_2.116.3.dsc
 8f8831848acff9c08f215d1f73dd8e22133f6a3c 2230340 lintian_2.116.3.tar.xz
 f219d27fe3dfd9d58813be0ae70e1b63809b7d49 27774 lintian_2.116.3_source.buildinfo
Checksums-Sha256:
 784b953ddccf4a258d49b63da03c70577852a16f5bcc5d5b4caaf75bfed37a22 3922 
lintian_2.116.3.dsc
 97c76a71920be1f18a72fc741155f6694a8eb0cbfb073ab3e6d6678262801a91 2230340 
lintian_2.116.3.tar.xz
 12d579cd41ee84c4d54cbee650da5e16f4d2e7f8b1529e48b1a03ae8760beaa5 27774 
lintian_2.116.3_source.buildinfo
Files:
 b5e01bd7a59aa80afd4df59eeebe4e17 3922 devel optional lintian_2.116.3.dsc
 ff8bf51113c6707e1eaf7db3c415df9b 2230340 devel optional lintian_2.116.3.tar.xz
 9d20fa47abd2c67614e23eb0e97d262d 27774 devel optional 
lintian_2.116.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAmPfd0kACgkQa+Zjx1o1
yXVtww//VB7FjjjNzHxhUMokcLadihhJpyAUrWhDNlMFyTA0GB32R0kzJHa4Qz4T
xnO3eT1pQQwww4lped+OBdal+7M3SVSVUbvn2z3e2aUMnIHTI6bo6vMLUG5qIDSI
BtjHRW/l3D7MrLKtHCj9js/s+4BF7PRjLGZlna7AoRKynBgr877/xnvY/fwGyVkI
xBaSAkXQEO6JtP1gXDyoenIFglR94ys/8C79MvmQomsyvpRzcmKjkbaBYnx6ZswG
+iXTryKvMHx7R5l1hig8CO5ek5g6poOmL2sWtLMhhruBo0w5P7siPDRVxvJyo00u
mCvCEIw8/lWG3K4ZGMUMPMfJwPtEkRp+m8mFYhen92V/Ge6h9dWmHBQdNLdzemMT
ax7Kgvwv8NMzkJW7cXM1Fke9/ShVBR9XFgKPjW2OB2oZRPWxDrrwCo59hIHZ8ngn
ABRpa99M+15ns2jCpDo/NuSOW3N9PTTLXN5oHg8GU7/p8TAItWI1RuUOS8qA7IKB
dY0lSBnnxFstaazNK1XKx0JkAZRpC1oqx2UNhTLxoOCVxB0pddUKN7bFkMsmt9lD
cR7t50Yz7p0CzWAretDtddgzVVP/yluE2YhOQtbyRY7S0ZI7wK6SvYtoYC/nuBvz
7yNs5uhevM3Z05zH4S9akQy8JXXFk4yOZHc1ZzXHgLrz/mrqzxk=
=PoAC
-END PGP SIGNATURE End Message ---

Processing of lintian_2.116.3_source.changes

[Debian FTP Masters]

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

Greetings,

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

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

[Axel Beckert (@abe)]

Axel Beckert pushed new tag 2.116.3 at lintian / lintian

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

[Git][lintian/lintian][master] Release and upload as 2.116.3 to unstable

[Axel Beckert (@abe)]

Axel Beckert pushed to branch master at lintian / lintian


Commits:
cac78dd8 by Axel Beckert at 2023-02-05T10:29:00+01:00
Release and upload as 2.116.3 to unstable

- - - - -


1 changed file:

- debian/changelog


Changes:

=
debian/changelog
=
@@ -1,8 +1,19 @@
-lintian (2.116.3~git) UNRELEASED; urgency=medium
+lintian (2.116.3) unstable; urgency=medium
 
-  * WIP (generated at release time: please do not add entries below.)
+  The "FFP3 (Fixing False Positives, Three Small Changes)" Release.
 
- -- Axel Beckert   Sun, 29 Jan 2023 16:34:44 +0100
+  [ Axel Beckert ]
+  * Refresh data. (Loong64 removed from two lists, some fonts and dh_cruft
+added.)
+
+  [ Simon McVittie ]
+  * obsolete-packages: libegl1-mesa-dev is not obsolete.
+
+  [ Andreas Beckmann ]
+  * archive-liberty-mismatch: Add exception for 'non-free-firmware binary
+package build from non-free source package'. (Closes: #1030325)
+
+ -- Axel Beckert   Sun, 05 Feb 2023 09:10:20 +0100
 
 lintian (2.116.2) unstable; urgency=medium
 



View it on GitLab: 
https://salsa.debian.org/lintian/lintian/-/commit/cac78dd88e1171e88ee8c3d6f5b1155b8081863d

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

Bug#1030325: lintian: archive-liberty-mismatch (in section for firmware-nvidia-gsp) non-free-firmware vs non-free

[Andreas Beckmann]

On 05/02/2023 08.47, Axel Beckert wrote:
Thanks for the lengthy analysis!

IMO only these cases should appear in the archive:
source:$area binary:$area # same $area, mandated by policy
source:main binary:contrib # iirc there is a policy exception for that
source:non-free binary:non-free-firmware # recently added, may need to 
be addressed in the policy, together with non-free-firmware


any other source:$area1 binary:$area2 combination (regardless of liberty 
order) should be prohibited (i.e. E: archive-liberty-mismatch)


There is one special case: for source:$area1 binary:$area2 mixed area 
exceptions there must be at least one other binary2:area1 package

(i.e. source must build at least one package in its area).

Do the existing test cases cover all these cases?

There should probably be
for sarea in $areas
  for barea in $areas
try Source:spkg #Section:
Package:pkg1 Section:foo/$sarea
Package:pkg2 Section:foo/$barea
try Source:spkg #Section:
Package:pkg2 Section:foo/$barea
Package:pkg1 Section:foo/$sarea
try Source:spkg #Section:
Package:pkg2 Section:foo/$barea
try Source:spkg Section:foo/$sarea
Package:pkg1 #Section:foo/$sarea
Package:pkg2 Section:foo/$barea
try Source:spkg Section:foo/$sarea
Package:pkg2 Section:foo/$barea

That should generate tests for all (im-)possible combinations.
The first three are for guessing the area from the first binary package 
if the Source stanza has no section.



Will apply that one with some fine-tuning wrt. to line length, etc.

And then release Lintian 2.116.3.


Please include the dkms patch (see other bug), too.

On 05/02/2023 06.47, Axel Beckert wrote:
> Unfortunately firmware-nvidia-gsp/nvidia-graphics-drivers is rather
> large and I ran out of disk space when first unpacking it in my home

Then you should try src:nvidia-cuda-toolkit ;-) Lintian needs 3-4 hours 
and about 50GB in /tmp to process a binary build. On nvme.
I'll probably come back with a bug report about lintian crashing (after 
a few hours) when processing cuda 12 (but first need to check with the 
latest lintian version again and also check that there was enough free 
space in /tmp)


Andreas

Processed: tagging 1030325

[Debian Bug Tracking System]

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

> tags 1030325 + pending
Bug #1030325 [lintian] lintian: archive-liberty-mismatch (in section for 
firmware-nvidia-gsp) non-free-firmware vs non-free
Added tag(s) pending.
> thanks
Stopping processing here.

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