Bug#1030325: lintian: archive-liberty-mismatch (in section for firmware-nvidia-gsp) non-free-firmware vs non-free
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/root 21 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 <abe@debian.org>, 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
Reply to: