Your message dated Thu, 21 Jan 2016 20:01:47 +0000
with message-id <[email protected]>
and subject line Re: lintian: "(il)legal" is used in a wrong sense in the
"checks"-directory
has caused the Debian Bug report #803518,
regarding lintian: "(il)legal" is used in a wrong sense in the
"checks"-directory
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 [email protected]
immediately.)
--
803518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803518
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lintian
Version: 2.5.30+deb8u4
Severity: minor
Dear Maintainer,
The general fact is mentioned in the GNU Coding Standard.
An appropriate word is (in)valid.
Examples from "/usr/share/lintian/":
checks/files.desc:Tag: run-parts-cron-filename-contains-illegal-chars
checks/fields.desc:Tag: illegal-multi-arch-value
checks/fields.pm: tag 'illegal-multi-arch-value', $arch, $march if
($arch eq 'all');
checks/files.pm: tag
'run-parts-cron-filename-contains-illegal-chars', $file;
checks/source-copyright.pm: # only attempt to evaluate globbing if
commas could be legal
checks/testsuite.desc:Tag: illegal-runtime-test-name
checks/testsuite.pm: tag 'illegal-runtime-test-name', $name,
-- System Information:
Debian Release: 8.2
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500,
'proposed-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.7-ckt11-u5 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages lintian depends on:
ii binutils 2.25-5
ii bzip2 1.0.6-7+b3
ii diffstat 1.58-1
ii file 1:5.22+15-2
ii gettext 0.19.3-2
ii hardening-includes 2.6
ii intltool-debian 0.35.0+20060710.1
ii libapt-pkg-perl 0.1.29+b2
ii libarchive-zip-perl 1.39-1
ii libclass-accessor-perl 0.34-1
ii libclone-perl 0.37-1+b1
ii libdpkg-perl 1.17.25
ii libemail-valid-perl 1.195-1
ii libfile-basedir-perl 0.03-1
ii libipc-run-perl 0.92-1
ii liblist-moreutils-perl 0.33-2+b1
ii libparse-debianchangelog-perl 1.2.0-1.1
ii libtext-levenshtein-perl 0.11-1
ii libtimedate-perl 2.3000-2
ii liburi-perl 1.64-1
ii man-db 2.7.0.2-5
ii patchutils 0.3.3-1
ii perl [libdigest-sha-perl] 5.20.2-3+deb8u1
ii t1utils 1.38-4
Versions of packages lintian recommends:
pn libperlio-gzip-perl <none>
ii perl 5.20.2-3+deb8u1
ii perl-modules [libautodie-perl] 5.20.2-3+deb8u1
Versions of packages lintian suggests:
pn binutils-multiarch <none>
ii dpkg-dev 1.17.25
ii libhtml-parser-perl 3.71-1+b3
ii libtext-template-perl 1.46-1
pn libyaml-perl <none>
ii xz-utils 5.1.1alpha+20120614-2+b3
-- Configuration Files:
/etc/lintianrc changed [not included]
-- no debconf information
--
Bjarni I. Gislason
--- End Message ---
--- Begin Message ---
On Fri, 30 Oct 2015 22:40:28 +0000 Bjarni Ingi Gislason
<[email protected]> wrote:
> Package: lintian
> Version: 2.5.30+deb8u4
> Severity: minor
>
> Dear Maintainer,
>
> The general fact is mentioned in the GNU Coding Standard.
>
> An appropriate word is (in)valid.
>
> Examples from "/usr/share/lintian/":
>
> checks/files.desc:Tag: run-parts-cron-filename-contains-illegal-chars
>
> checks/fields.desc:Tag: illegal-multi-arch-value
>
> checks/fields.pm: tag 'illegal-multi-arch-value', $arch, $march if
> ($arch eq 'all');
>
> checks/files.pm: tag
> 'run-parts-cron-filename-contains-illegal-chars', $file;
>
> checks/source-copyright.pm: # only attempt to evaluate globbing if
> commas could be legal
>
> checks/testsuite.desc:Tag: illegal-runtime-test-name
>
> checks/testsuite.pm: tag 'illegal-runtime-test-name', $name,
>
>
> [...]
Closing as wontfix for the same reason as #803519.
Thanks,
~Niels
signature.asc
Description: OpenPGP digital signature
--- End Message ---
