Bug#636086: [PATCH] Use C.UTF-8 from current libc-bin, rather than our own private en_US.UTF-8

2011-08-23 Thread Jakub Wilk
* Niels Thykier ni...@thykier.net, 2011-08-22, 21:44: +if (-d $LINTIAN_ROOT/locale/C.UTF-8) { + $ENV{LOCPATH} = $LINTIAN_ROOT/locale; +} elsif (-d '/var/lib/lintian/locale/C.UTF-8') { + $ENV{LOCPATH} = '/var/lib/lintian/locale'; +} Hmm, but we never generate C.UTF-8 (if

Bug#636086: [PATCH] Use C.UTF-8 from current libc-bin, rather than our own private en_US.UTF-8

2011-08-22 Thread Niels Thykier
On 2011-08-13 17:12, Niels Thykier wrote: On 2011-08-08 07:06, Josh Triplett wrote: On Sat, Aug 06, 2011 at 03:23:12PM +0200, Niels Thykier wrote: [...] Hi, I think that is really outside the scope of a Lintian backport. If such a package was created for backports, I would consider it,

Bug#636086: [PATCH] Use C.UTF-8 from current libc-bin, rather than our own private en_US.UTF-8

2011-08-22 Thread Jakub Wilk
* Niels Thykier ni...@thykier.net, 2011-08-22, 21:44: --- a/debian/control +++ b/debian/control @@ -22,6 +22,7 @@ Build-Depends: binutils, intltool-debian, javahelper (= 0.32~), libapt-pkg-perl, + libc-bin (= 2.13) | locales,

Bug#636086: [PATCH] Use C.UTF-8 from current libc-bin, rather than our own private en_US.UTF-8

2011-08-13 Thread Niels Thykier
On 2011-08-08 07:06, Josh Triplett wrote: On Sat, Aug 06, 2011 at 03:23:12PM +0200, Niels Thykier wrote: [...] This sounds reasonable to me. However, I have a suggestion for a slight variation. Rather than implementing a private C.UTF-8 locale in lintian (and preserving the LOCPATH

Bug#636086: [PATCH] Use C.UTF-8 from current libc-bin, rather than our own private en_US.UTF-8

2011-08-07 Thread Josh Triplett
On Sat, Aug 06, 2011 at 03:23:12PM +0200, Niels Thykier wrote: How about we migrate to C.UTF-8 in all cases; if the system provides one in /usr/lib/locale/C.UTF-8, then we use that otherwise we fall back to our internal locale. postinst/prerm are modified to remove the old en_US.UTF-8

Bug#636086: [PATCH] Use C.UTF-8 from current libc-bin, rather than our own private en_US.UTF-8

2011-08-06 Thread Niels Thykier
On 2011-08-02 18:23, Niels Thykier wrote: On 2011-07-31 00:56, Josh Triplett wrote: I've attached a git patch fixing this bug. I omitted the debian/changelog entry to avoid spurious conflicts, but the contents of the git changelog should work for that purpose. Please consider applying this

Bug#636086: [PATCH] Use C.UTF-8 from current libc-bin, rather than our own private en_US.UTF-8

2011-08-02 Thread Niels Thykier
On 2011-07-31 00:56, Josh Triplett wrote: I've attached a git patch fixing this bug. I omitted the debian/changelog entry to avoid spurious conflicts, but the contents of the git changelog should work for that purpose. Please consider applying this patch. Thanks, Josh Triplett Hi

Bug#636086: [PATCH] Use C.UTF-8 from current libc-bin, rather than our own private en_US.UTF-8

2011-07-30 Thread Josh Triplett
I've attached a git patch fixing this bug. I omitted the debian/changelog entry to avoid spurious conflicts, but the contents of the git changelog should work for that purpose. Please consider applying this patch. Thanks, Josh Triplett From ba67a2231b3ed9801debcd227f24c20e62c74149 Mon Sep 17