Lintian: next upload to Debian archive?

2024-05-28 Thread Martin-Éric Racine
Greetings, Standards-Version was updated to 4.7.0 a while back, without any new Lintian version to acknowledge it. Looking at Git, I notice that the last commit to Lintian was made 3 weeks ago. Is there any ETA on uploading to unstable and deploying to relevant hosts? Cheers! Martin-Éric

Bug#1029187: depends-on-obsolete-package: exessive severity, should be Warning

2023-01-19 Thread Martin-Éric Racine
Package: lintian Version: 2.116.0 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 depends-on-obsolete-package currently is at severity Error. This is excessive. This should be a mere Warning. - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT

Bug#1016364: lintian: spelling-error-in-binary should be more precise

2022-07-29 Thread Martin-Éric Racine
Package: lintian Version: 2.104.0 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When building dhcpcd5 version 9.4.1-4 against Stable, Lintian 2.104.0 reports the following: I: dhcpcd-base: spelling-error-in-binary usr/sbin/dhcpcd addres address $ grep -rw addres $ i.e. not

Bug#1009967: lintian: improbable-bug-number-in-closes produces incorrect results

2022-04-22 Thread Martin-Éric Racine
On Fri, Apr 22, 2022 at 10:05 PM Mattia Rizzolo wrote: > > On Fri, Apr 22, 2022 at 09:59:50PM +0300, Martin-Éric Racine wrote: > > On Fri, Apr 22, 2022 at 3:57 PM Mattia Rizzolo wrote: > > > > > > Control: notfound -1 2.114.163 > > > Control: found -1

Bug#1009967: lintian: improbable-bug-number-in-closes produces incorrect results

2022-04-22 Thread Martin-Éric Racine
On Fri, Apr 22, 2022 at 3:57 PM Mattia Rizzolo wrote: > > Control: notfound -1 2.114.163 > Control: found -1 2.111.0 > Control: close -1 2.113.0 > > On Thu, Apr 21, 2022 at 03:38:32PM +0300, Martin-Éric Racine wrote: > > Package: lintian > > Versi

Bug#1009967: lintian: improbable-bug-number-in-closes produces incorrect results

2022-04-21 Thread Martin-Éric Racine
Package: lintian Version: 2.114.163 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The Lintian on mentors.debian.net incorrectly reports: W: improbable-bug-number-in-closes 1008784 The relevant changelog entry: Replaces part of the cron job that we used to provide (Closes:

Bug#1003817: lintian: fpos for update-debian-copyright

2022-04-21 Thread Martin-Éric Racine
Package: lintian Version: 2.114.0 Followup-For: Bug #1003817 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 That one bites me too. # Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Contact: Martin-Éric Racine Files: * Copyright: © 2004-2022 Martin

Bug#1006482: lintian: non-standard-dir-in-var var/db/

2022-02-26 Thread Martin-Éric Racine
Package: lintian Version: 2.114.0 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Lintian incorrectly reports /var/db/ as non-standard-dir-in-var. /var/db Data bank store. - -- System Information: Debian

Bug#856128: debian-watch-may-check-gpg-signature: false positives

2017-02-26 Thread Martin-Éric Racine
2017-02-26 12:07 GMT+02:00 Mattia Rizzolo <mat...@debian.org>: > Control: tag -1 moreinfo > > On Sat, Feb 25, 2017 at 01:04:54PM +0000, Martin-Éric Racine wrote: >> It appears that debian-watch-may-check-gpg-signature generates false >> positives. >> >>

Bug#856128: debian-watch-may-check-gpg-signature: false positives

2017-02-25 Thread Martin-Éric Racine
Package: lintian Version: 2.5.50.1 Severity: normal It appears that debian-watch-may-check-gpg-signature generates false positives. On src:cups-pdf Lintian reports debian-watch-may-check-gpg-signature yet upstream does not publish any GPG signature. However, upstream does publish

Bug#405454: lintian: [new check] init script in level S must only use commands from /sbin:/bin

2016-04-12 Thread Martin-Éric Racine
2016-04-12 4:46 GMT+03:00 Felipe Sateler : > On Wed, 03 Jan 2007 19:53:01 +0200 =?utf-8?q?Martin-=C3=89ric_Racine?= > wrote: >> On systems with a separate /usr filesystem, several boot scripts in level S >> break because they use commands from /usr/bin or

Bug#814521: lintian: package-installs-apt-preferences and package-installs-apt-sources report duplicates

2016-02-12 Thread Martin-Éric Racine
Package: lintian Version: 2.5.40.2 Severity: normal Getting an error was expected (this package enforces standard configurations such as APT sources and preferences onto all my hosts): E: funkyware-common: package-installs-apt-preferences etc/apt/preferences.d/ E: funkyware-common:

Bug#405454: [new check] init script in level S must only use commands from /sbin:/bin

2008-06-23 Thread Martin-Éric Racine
Checking for the existence of a string /usr/ anywhere in the init script could already be a simple way to do this. -- Martin-Éric Racine http://q-funk.iki.fi

erroneous Lintian report

2007-12-27 Thread Martin-Éric Racine
$ file debian/copyright debian/copyright: UTF-8 Unicode English text [EMAIL PROTECTED]:/home/q-funk/Projects/rus-ispell-0.99g4$ Did I miss anything? Isn't UTF-8 the standard these days? -- Martin-Éric Racine http://q-funk.iki.fi

Re: erroneous Lintian report

2007-12-27 Thread Martin-Éric Racine
On 12/27/07, Russ Allbery [EMAIL PROTECTED] wrote: Martin-Éric Racine [EMAIL PROTECTED] writes: My Lintian report at http://lintian.debian.org/reports/maintainer/q-funk%40iki.fi.html states that: Source package: rus-ispell (0.99g4-7) W: irussian binary: debian-copyright-file

Bug#405454: lintian: [new check] init script in level S must only use commands from /sbin:/bin

2007-01-03 Thread Martin-Éric Racine
Package: lintian Version: 1.23.27 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On systems with a separate /usr filesystem, several boot scripts in level S break because they use commands from /usr/bin or /usr/sbin. Culprits include scripts for essential packages that perform

Bug#384424: closed by Russ Allbery [EMAIL PROTECTED] (Re: Re: Bug#384424: lintian: possible mishandling of similarily-named shlibs with dashes)

2006-11-11 Thread Martin-Éric Racine
dh_makeshlibs or open another bug against debhelper to see if its matching logic can be improved. Since the issue itself is not resolved, reassigning this bug to debhelper makes more sense than closing it. Doing this now. -- Martin-Éric Racine http://q-funk.iki.fi

Bug#384424: lintian: possible mishandling of similarily-named shlibs with dashes

2006-08-24 Thread Martin-Éric Racine
Package: lintian Version: 1.23.23 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have been getting this error on my package for a long time: E: planner binary: duplicate-entry-in-shlibs-control-file libmrp The tree view shows: /usr/lib/planner/ |-- file-modules | |--

Bug#384424: lintian: possible mishandling of similarily-named shlibs with dashes

2006-08-24 Thread Martin-Éric Racine
On Thu, August 24, 2006 19:24, Russ Allbery said: Martin-Éric Racine [EMAIL PROTECTED] writes: Package: lintian Version: 1.23.23 Severity: normal I have been getting this error on my package for a long time: E: planner binary: duplicate-entry-in-shlibs-control-file libmrp /usr/lib