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

[Niels Thykier <niels@thykier.net>]

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 propagation and related bits), how about
> creating a new backport-specific package "c-utf8-locale-backport" or
> similar, which generates the locale system-wide?  Lintian could then
> depend on libc-bin (>= 2.13-1) | c-utf8-locale-backport, and (with some
> coordination) the libc-bin maintainers could add a
> conflicts/replaces/provides on c-utf8-locale-backport.  Then, lintian
> and any other package wanting to count on C.UTF-8 could use this
> dependency (and drop the alternative when wheezy releases).
> 
> How does that sound?
> 
> - Josh Triplett
> 
> 
> 

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, but I will not
introduce one in(/for) Lintian.

Also as far as I can tell, all packages can drop their private C.UTF-8
maintenance scripts at wheezy + 1 if they migrate correctly during Wheezy.

~Niels