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

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-

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

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 >

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

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 sig

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

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 performa

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

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

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

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

Bug#1013417: lintian: dkms updates

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

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

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 #1013

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 Book

lintian_2.116.3_source.changes ACCEPTED into unstable

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

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

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.

Processing of lintian_2.116.3_source.changes

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 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 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

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

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 #

Processed: tagging 1030325

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.