Your message dated Mon, 22 Jul 2013 14:58:10 +0200 with message-id <[email protected]> and subject line Re: Bug#409124: [aesthetics] report trailing blank lines and whitespace has caused the Debian Bug report #409124, regarding lintian: Add pedantic checks for whitespace (EOL, End of buffer) 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.) -- 409124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409124 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: lintian Version: 2.4.3 Severity: wishlist I'd like to suggest couple of typical "non seeable" editing mishaps that appear easily: - End of line whitesapce /\s+$/ - And of file whitespace (extra newlines at the end; more than the standaed "<last line>\n") Perhaps lintian could angage these checks with the --pedantic option. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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.20.1-16 The GNU assembler, linker and bina ii diffstat 1.54-1 produces graph of changes introduc ii dpkg-dev 1.15.8.10 Debian package development tools ii file 5.04-5 Determines file type using "magic" ii gettext 0.18.1.1-3 GNU Internationalization utilities ii intltool-debian 0.35.0+20060710.1 Help i18n of RFC822 compliant conf ii libapt-pkg-perl 0.1.24+b1 Perl interface to libapt-pkg ii libclass-accessor-perl 0.34-1 Perl module that automatically gen ii libipc-run-perl 0.89-1 Perl module for running processes ii libparse-debianchangel 1.1.1-2.1 parse Debian changelogs and output ii libtimedate-perl 1.2000-1 collection of modules to manipulat ii liburi-perl 1.58-1 module to manipulate and access UR ii locales 2.11.2-11 Embedded GNU C Library: National L ii man-db 2.5.9-4 on-line manual pager ii perl [libdigest-sha-pe 5.10.1-17 Larry Wall's Practical Extraction lintian recommends no packages. Versions of packages lintian suggests: pn binutils-multiarch <none> (no description available) ii libtext-template-perl 1.45-2 Text::Template perl module ii man-db 2.5.9-4 on-line manual pager -- debconf-show failed
--- End Message ---
--- Begin Message ---On 2011-12-22 22:44, jari wrote: > 2009-03-08 Russ Allbery <[email protected]>: > | 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 ---
