Bug#555408: private locale copy is never updated

2010-02-05 Thread Piotr Engelking
Russ Allbery r...@debian.org: en_US.UTF-8 certainly does change from time to time, for an example to add new characters to the LC_CTYPE character classes when new Unicode versions are released. I do not know if these changes would affect the man-db warnings, but the above changelog entry

Bug#555408: private locale copy is never updated

2010-02-04 Thread Piotr Engelking
+ [RA] Generate an en_US.UTF-8 locale in /var/lib/lintian/locale for use for tests, particularly man page tests. (Closes: #555408) The private copy of the en_US.UTF-8 locale that lintian generates is not updated when the locale definitions change. This looks like asking for

Bug#555408: private locale copy is never updated

2010-02-04 Thread Piotr Engelking
Russ Allbery r...@debian.org:      + [RA] Generate an en_US.UTF-8 locale in /var/lib/lintian/locale for        use for tests, particularly man page tests.  (Closes: #555408) The private copy of the en_US.UTF-8 locale that lintian generates is not updated when the locale definitions change.

Bug#374899: lintian: aspell-* packages should be Architecture: all

2006-06-21 Thread Piotr Engelking
Package: lintian Version: 1.23.21 Severity: wishlist As far as I am aware, aspell-* packages contain only architecture independent data and should therefore be tagged Architecture: all. This seems not to be the case with aspell-{da,et,fi,it,no,pt,pt-br,pt-common,ru}. I believe that lintian could

Bug#344269: lintian: false executable-not-elf-or-script warning with perl magic header

2006-04-19 Thread Piotr Engelking
I believe that this bug has been resolved incorrectly. Section 10.4 of the Debian Policy says: All command scripts, including the package maintainer scripts inside the package and used by dpkg, should have a #! line naming the shell to be used to interpret them. In the case of