[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#540162: marked as done ([aesthetics] check for trailing whitespace in debian/* files)

Your message dated Mon, 22 Jul 2013 14:58:10 +0200
with message-id <51ED2C62.1020802@thykier.net>
and subject line Re: Bug#409124: [aesthetics] report trailing blank lines and whitespace
has caused the Debian Bug report #409124,
regarding [aesthetics] check for trailing whitespace in debian/* files
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 owner@bugs.debian.org
immediately.)


-- 
409124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409124
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.2.13
Severity: wishlist


Please add (pedantic?) check for trailing empty spaces or tabs in files
under debian/*

Also check for multiple trailing empty lines at the end of files.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lintian depends on:
ii  binutils              2.19.51.20090723-1 The GNU assembler, linker and bina
ii  diffstat              1.47-1             produces graph of changes introduc
ii  dpkg-dev              1.15.3.1           Debian package development tools
ii  file                  5.03-1             Determines file type using "magic"
ii  gettext               0.17-6             GNU Internationalization utilities
ii  intltool-debian       0.35.0+20060710.1  Help i18n of RFC822 compliant conf
ii  libapt-pkg-perl       0.1.23             Perl interface to libapt-pkg
ii  libipc-run-perl       0.84-1             Perl module for running processes
ii  libparse-debianchange 1.1.1-2            parse Debian changelogs and output
ii  libtimedate-perl      1.1600-9           Time and date functions for Perl
ii  liburi-perl           1.37+dfsg-1        Manipulates and accesses URI strin
ii  man-db                2.5.5-3            on-line manual pager
ii  perl [libdigest-sha-p 5.10.0-24          Larry Wall's Practical Extraction 

lintian recommends no packages.

Versions of packages lintian suggests:
pn  binutils-multiarch            <none>     (no description available)
pn  libtext-template-perl         <none>     (no description available)
ii  man-db                        2.5.5-3    on-line manual pager

-- no debconf information

--- End Message ---
--- Begin Message --- 
On 2011-12-22 22:44, jari wrote:
> 2009-03-08 Russ Allbery <rra@debian.org>:
> | Anything that doesn't handle whitespace in that way is buggy and needs to
> | be fixed.  I don't think warning (even as a pedantic warning) about
> | packages that follow Policy's requirements for debian/control is a good
> | idea.  I have added a pedantic tag for fields that don't use a single
> | space after the colon; that's the one thing that's present in Policy as a
> | pseudo-recommendation.
> 
> I's not about Debian tools to be unable to handle these things. 
> 
> It is just logical to add these checks to "Lintian" to help keeping
> packages in best possible shape.
> 
> Who would deliberately add EOL whitespaces?
> 
> It's usually added by mistake because the editor may be unable (or not
> configured to) to show trailing white spaces.
> 
> When data is exchanged between parties:
> 
> 	- By email
> 	- By patches (NMUs, diffs, etc)
> 	- Injected into VCS (if configured to warn EOL whitespaces)
> 
> It helps when there are no EOL whitespaces to worry about.
> 
> Jari
> 

I think we have to say no to including this tag in Lintian itself.
However, you can still write a check for it (even if only for
local/personal use)[1].

~Niels

[1] http://lintian.debian.org/manual/section-3.3.html

--- End Message ---
Reply to: