[lintian] 01/01: spelling: Add another correction

[Paul Wise]

This is an automated email from the git hooks/post-receive script.

pabs pushed a commit to branch master
in repository lintian.

commit 1142b4cde160ce959a32877022e81c9330136c21
Author: Paul Wise 
Date:   Wed Jan 24 20:18:45 2018 +0800

spelling: Add another correction
---
 data/spelling/corrections | 1 +
 1 file changed, 1 insertion(+)

diff --git a/data/spelling/corrections b/data/spelling/corrections
index e8c8626..0e8206f 100644
--- a/data/spelling/corrections
+++ b/data/spelling/corrections
@@ -2294,6 +2294,7 @@ intrument||instrument
 intruments||instruments
 intuative||intuitive
 invaid||invalid
+invalide||invalid
 invalud||invalid
 invarient||invariant
 invididual||individual

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/lintian/lintian.git

[lintian] branch master updated (2d71fba -> 1142b4c)

[Paul Wise]

This is an automated email from the git hooks/post-receive script.

pabs pushed a change to branch master
in repository lintian.

  from  2d71fba   Move spelling-error-in-binary exceptions to a data file.
   new  1142b4c   spelling: Add another correction

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.


Summary of changes:
 data/spelling/corrections | 1 +
 1 file changed, 1 insertion(+)

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/lintian/lintian.git

Build failed in Jenkins: lintian-tests_sid #2471

[jenkins]

See 


Changes:

[pabs] spelling: Add another correction

--
[...truncated 20.62 KB...]
I: Validating liblocale-gettext-perl 1.07-3+b3
I: Retrieving liblogging-stdlog0 1.0.6-3
I: Validating liblogging-stdlog0 1.0.6-3
I: Retrieving liblognorm5 2.0.3-1
I: Validating liblognorm5 2.0.3-1
I: Retrieving libmnl0 1.0.4-2
I: Validating libmnl0 1.0.4-2
I: Retrieving libnetfilter-conntrack3 1.0.6-2
I: Validating libnetfilter-conntrack3 1.0.6-2
I: Retrieving libnfnetlink0 1.0.1-3+b1
I: Validating libnfnetlink0 1.0.1-3+b1
I: Retrieving libseccomp2 2.3.1-2.1
I: Validating libseccomp2 2.3.1-2.1
I: Retrieving libselinux1 2.7-2
I: Validating libselinux1 2.7-2
I: Retrieving libsemanage-common 2.7-2
I: Validating libsemanage-common 2.7-2
I: Retrieving libsemanage1 2.7-2
I: Validating libsemanage1 2.7-2
I: Retrieving libsepol1 2.7-1
I: Validating libsepol1 2.7-1
I: Retrieving libtasn1-6 4.13-2
I: Validating libtasn1-6 4.13-2
I: Retrieving libtext-charwidth-perl 0.04-7.1
I: Validating libtext-charwidth-perl 0.04-7.1
I: Retrieving libtext-iconv-perl 1.7-5+b6
I: Validating libtext-iconv-perl 1.7-5+b6
I: Retrieving libtext-wrapi18n-perl 0.06-7.1
I: Validating libtext-wrapi18n-perl 0.06-7.1
I: Retrieving libunistring2 0.9.8-1
I: Validating libunistring2 0.9.8-1
I: Retrieving logrotate 3.11.0-0.1
I: Validating logrotate 3.11.0-0.1
I: Retrieving lsb-base 9.20170808
I: Validating lsb-base 9.20170808
I: Retrieving dmsetup 2:1.02.145-4.1
I: Validating dmsetup 2:1.02.145-4.1
I: Retrieving libdevmapper1.02.1 2:1.02.145-4.1
I: Validating libdevmapper1.02.1 2:1.02.145-4.1
I: Retrieving liblz4-1 0.0~r131-2+b1
I: Validating liblz4-1 0.0~r131-2+b1
I: Retrieving mawk 1.3.3-17+b3
I: Validating mawk 1.3.3-17+b3
I: Retrieving nano 2.9.2-1
I: Validating nano 2.9.2-1
I: Retrieving libncurses5 6.0+20171125-1
I: Validating libncurses5 6.0+20171125-1
I: Retrieving libncursesw5 6.0+20171125-1
I: Validating libncursesw5 6.0+20171125-1
I: Retrieving libtinfo5 6.0+20171125-1
I: Validating libtinfo5 6.0+20171125-1
I: Retrieving ncurses-base 6.0+20171125-1
I: Validating ncurses-base 6.0+20171125-1
I: Retrieving ncurses-bin 6.0+20171125-1
I: Validating ncurses-bin 6.0+20171125-1
I: Retrieving netbase 5.4
I: Validating netbase 5.4
I: Retrieving libhogweed4 3.4-1
I: Validating libhogweed4 3.4-1
I: Retrieving libnettle6 3.4-1
I: Validating libnettle6 3.4-1
I: Retrieving libnewt0.52 0.52.20-1+b1
I: Validating libnewt0.52 0.52.20-1+b1
I: Retrieving whiptail 0.52.20-1+b1
I: Validating whiptail 0.52.20-1+b1
I: Retrieving libssl1.1 1.1.0g-2
I: Validating libssl1.1 1.1.0g-2
I: Retrieving libp11-kit0 0.23.9-2
I: Validating libp11-kit0 0.23.9-2
I: Retrieving libpam-modules 1.1.8-3.6
I: Validating libpam-modules 1.1.8-3.6
I: Retrieving libpam-modules-bin 1.1.8-3.6
I: Validating libpam-modules-bin 1.1.8-3.6
I: Retrieving libpam-runtime 1.1.8-3.6
I: Validating libpam-runtime 1.1.8-3.6
I: Retrieving libpam0g 1.1.8-3.6
I: Validating libpam0g 1.1.8-3.6
I: Retrieving libpcre3 2:8.39-8
I: Validating libpcre3 2:8.39-8
I: Retrieving perl-base 5.26.1-4
I: Validating perl-base 5.26.1-4
I: Retrieving libpopt0 1.16-10+b2
I: Validating libpopt0 1.16-10+b2
I: Retrieving libprocps6 2:3.3.12-3
I: Validating libprocps6 2:3.3.12-3
I: Retrieving procps 2:3.3.12-3
I: Validating procps 2:3.3.12-3
I: Retrieving readline-common 7.0-3
I: Validating readline-common 7.0-3
I: Retrieving rsyslog 8.32.0-1
I: Validating rsyslog 8.32.0-1
I: Retrieving sed 4.4-1
I: Validating sed 4.4-1
I: Retrieving sensible-utils 0.0.11
I: Validating sensible-utils 0.0.11
I: Retrieving login 1:4.5-1
I: Validating login 1:4.5-1
I: Retrieving passwd 1:4.5-1
I: Validating passwd 1:4.5-1
I: Retrieving libslang2 2.3.1a-1
I: Validating libslang2 2.3.1a-1
I: Retrieving libsystemd0 236-3+b1
I: Validating libsystemd0 236-3+b1
I: Retrieving libudev1 236-3+b1
I: Validating libudev1 236-3+b1
I: Retrieving systemd 236-3+b1
I: Validating systemd 236-3+b1
I: Retrieving systemd-sysv 236-3+b1
I: Validating systemd-sysv 236-3+b1
I: Retrieving udev 236-3+b1
I: Validating udev 236-3+b1
I: Retrieving sysvinit-utils 2.88dsf-59.10
I: Validating sysvinit-utils 2.88dsf-59.10
I: Retrieving tar 1.29b-2
I: Validating tar 1.29b-2
I: Retrieving tasksel 3.42
I: Validating tasksel 3.42
I: Retrieving tasksel-data 3.42
I: Validating tasksel-data 3.42
I: Retrieving tzdata 2018b-1
I: Validating tzdata 2018b-1
I: Retrieving bsdutils 1:2.30.2-0.3
I: Validating bsdutils 1:2.30.2-0.3
I: Retrieving fdisk 2.30.2-0.3
I: Validating fdisk 2.30.2-0.3
I: Retrieving libblkid1 2.30.2-0.3
I: Validating libblkid1 2.30.2-0.3
I: Retrieving libfdisk1 2.30.2-0.3
I: Validating libfdisk1 2.30.2-0.3
I: Retrieving libmount1 2.30.2-0.3
I: Validating libmount1 2.30.2-0.3
I: Retrieving libsmartcols1 2.30.2-0.3
I: Validating libsmartcols1 2.30.2-0.3
I: Retrieving libuuid1 2.30.2-0.3
I: Validating libuuid1 2.30.2-0.3
I: Retrieving mount 2.30.2-0.3
I: Validat

Bug#831449: lintian on Sid amd64 reports volatile false spelling errors in binaries

[Jakub Wilk]

* Chris Lamb , 2018-01-24, 08:04:
I'm not sure what to do about it on Lintian side. Perhaps we should 
spell-check only long (say, >= 12 bytes) strings in binaries?
Wouldn't that mean we would only find spelling problems for very long 
words?


No, not necessarily. For example, if this sentence were embedded in a 
binary, Lintain would find the misspelling: even though the misspelled 
word is short, it's part of a longer chunk of text, which would be 
spell-checked.


--
Jakub Wilk

Bug#831449: lintian on Sid amd64 reports volatile false spelling errors in binaries

[Thomas Schmitt]

Hi,

Chris Lamb wrote:
> I'm not sure what lintian can do here, indeed.

First to say: I am not aware whether the problem still exists.

But in general it seems that "strings" on the binaries is not the right way
to obtain a list of message texts. After all, the purpose of a compiler is
to put out binary code as it deems appropriate for the given source and
target. Any assumption about the binary is courageous.

I tried to find some source code localization suite which would extract
messages from source code and present them for translation. No luck yet.
(Maybe the task is totally trivial and i just don't see how ?)


Have a nice day :)

Thomas

Bug#888304: lintian: False-positive brace-expansion-in-debhelper-config-file

[Niels Thykier]

Package: lintian
Version: 2.5.70
Severity: minor

Hi,

lintian is flagging the following file with a brace expansion:

"""
usr/lib/lightning 
usr/lib/thunderbird/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}
"""
(Source: 
https://anonscm.debian.org/cgit/pkg-mozilla/icedove.git/tree/debian/lightning.links)

However, a brace expansion requires a comma between the braces.  E.g. in bash:

"""
  $ echo {a,b}  ; echo {ab}
  a b
  {ab}
"""

I have confirmed this holds for debhelper as well (mind the regression
#888251; affects 10.6 until the next release).

Thanks,
~Niels

Bug#888304: lintian: False-positive brace-expansion-in-debhelper-config-file

[Chris Lamb]

Hi Niels,

> a brace expansion requires a comma between the braces

So, the implementation actually matches a test case in the testsuite:

  
https://anonscm.debian.org/git/lintian/lintian.git/tree/t/tests/debhelper-brace-expansion/debian/debian/debhelper-brace-problem-6.install#n1

Whilst the testsuite could be wrong (!) I just thought it requires
double- checking. (Is this a dh_install vs. dh_link distinction…?)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#888304: lintian: False-positive brace-expansion-in-debhelper-config-file

[Niels Thykier]

Chris Lamb:
> Hi Niels,
> 
>> a brace expansion requires a comma between the braces
> 
> So, the implementation actually matches a test case in the testsuite:
> 
>   
> https://anonscm.debian.org/git/lintian/lintian.git/tree/t/tests/debhelper-brace-expansion/debian/debian/debhelper-brace-problem-6.install#n1
> 
> Whilst the testsuite could be wrong (!) I just thought it requires
> double- checking. (Is this a dh_install vs. dh_link distinction…?)
> 
> 
> Best wishes,
> 

That particular test is wrong.  It would need a comma to be a true brace
expansion.

Also, note that dh_link do not do any glob expansion at all, so it
cannot have this problem in the first place.  If you use a {a,b} in
links, then you will always get a literal {a,b}.  That said, there is no
current need for literal {a,b}, so I would not bother coding support for
it right now.  It would just needlessly complicate the implementation.

Thanks,
~Niels