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 Russ Allbery
Piotr Engelking inkerma...@gmail.com writes: + [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

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#555408: private locale copy is never updated

2010-02-04 Thread Russ Allbery
Piotr Engelking inkerma...@gmail.com writes: Russ Allbery r...@debian.org: Do you think the man-db warning results would ever change based on things that would change about the locale, particularly at this point in the maturity of en_US.UTF-8?  It seems unlikely to me on first glance.