Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: James Broadhead <jamesbroadhead@...>
Subject: Re: Re: So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
Date: Sun, 4 Dec 2011 14:09:03 +0000
On 4 December 2011 06:51, Ryan Hill <dirtyepic@g.o> wrote:
> On Sun, 4 Dec 2011 04:50:00 +0100
> Jeroen Roovers <jer@g.o> wrote:
>
>> Subject says it all. More and more bug attachments appear that have
>> been generated with non-English locales, and it's a nuisance for both
>> bug reporters and bug wranglers to request/provide the sane alternative
>> that every developer should be able to read.
>
> How many times have you needed to request build logs in english since the last
> time you brought this up?  How many times have you had to request emerge
> --info or build logs in general?

Surely this can be automated?

"Error - Bug not filed!
No emerge --info attachment detected. Either tag one of your
attachments as `emerge --info`, or upload one"

> I think adding a note to bugzilla reminding reporters that logs need to be in
> english would be a better solution than forcing it on everyone.

Again, automation should be moderately easy to achieve. Having bugzie
grep for "Error" / "Warning" in the top ten non-English languages
should be enough. On a positive, reject the output with a popup
explaining how to get an English version.


Am I wrong, or is LC_MESSAGES=C a non-UTF-8 locale? Why is this
considered a good idea? Why not en-UTF-8?


Replies:
Re: Re: So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
-- Michał Górny
References:
So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
-- Jeroen Roovers
Re: So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
-- Ryan Hill
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
Next by thread:
Re: Re: So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
Previous by date:
Re: So now that we have --quiet-build as default, can we talk about a forced LC_MESSAGES=C again?
Next by date:
Re: Re: So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.