[gentoo-dev] LC_ALL=C Set by default for portage
Hi, lately i see that in our bugzilla most of the build reports are reported with localized build logs which we dont understand. This leads to us asking the user to run the emerge once more with LC_ALL=C. Wont it be nice to have this variable set by default in portage so users reporting bugs report in English? Since if everything goes fine they dont even bother about the warnings/errors and if something goes wrong it ends up on us to solve the mess :] The LC_ALL should be set for all relevant configure/compile/install phases at least. Regards Tomas signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] LC_ALL=C Set by default for portage
Hi, lately i see that in our bugzilla most of the build reports are reported with localized build logs which we dont understand. This leads to us asking the user to run the emerge once more with LC_ALL=C. Wont it be nice to have this variable set by default in portage so users reporting bugs report in English? Since if everything goes fine they dont even bother about the warnings/errors and if something goes wrong it ends up on us to solve the mess :] Moreover this would automagically solve the [a-z] friends regexp failures; though that's still good QA to fix them but we wouldn't encounter them anymore. Alexis. signature.asc Description: PGP signature
Re: [gentoo-dev] LC_ALL=C Set by default for portage
On Sun, Mar 08, 2009 at 09:20:14PM +0100, Tomáš Chvátal wrote: Hi, lately i see that in our bugzilla most of the build reports are reported with localized build logs which we dont understand. This leads to us asking the user to run the emerge once more with LC_ALL=C. Wont it be nice to have this variable set by default in portage so users reporting bugs report in English? I can't speak for others, but I'd like to find and fix bugs with strange locales, at least for the packages I maintain. If portage were to force LC_ALL=C on me, I'd have a very hard time doing so.
Re: [gentoo-dev] LC_ALL=C Set by default for portage
On Sun, Mar 08, 2009 at 09:27:20PM +0100, Alexis Ballier wrote: Moreover this would automagically solve the [a-z] friends regexp failures; though that's still good QA to fix them but we wouldn't encounter them anymore. We would encounter them when using the programs outside of portage, but not when running the testsuite (if available) from within portage. It would succeed in working around compile-time only bugs, but it would be a major pain for locale bugs that can also cause problems at run time.
Re: [gentoo-dev] LC_ALL=C Set by default for portage
On Sunday 08 March 2009 16:20:14 Tomáš Chvátal wrote: lately i see that in our bugzilla most of the build reports are reported with localized build logs which we dont understand. This leads to us asking the user to run the emerge once more with LC_ALL=C. LC_ALL does a lot more than localization of messages. this topic has come up before on the list, so i'd search the archives for all the reasons why this is not the thing to do. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] LC_ALL=C Set by default for portage
Dne pondělí 09 Březen 2009 01:35:07 Mike Frysinger napsal(a): On Sunday 08 March 2009 16:20:14 Tomáš Chvátal wrote: lately i see that in our bugzilla most of the build reports are reported with localized build logs which we dont understand. This leads to us asking the user to run the emerge once more with LC_ALL=C. LC_ALL does a lot more than localization of messages. this topic has come up before on the list, so i'd search the archives for all the reasons why this is not the thing to do. -mike Well if complete LC_ALL is not option so how about reseting at least LC_MESSAGES... signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] LC_ALL=C Set by default for portage
On Sunday 08 March 2009 20:38:01 Tomáš Chvátal wrote: Dne pondělí 09 Březen 2009 01:35:07 Mike Frysinger napsal(a): On Sunday 08 March 2009 16:20:14 Tomáš Chvátal wrote: lately i see that in our bugzilla most of the build reports are reported with localized build logs which we dont understand. This leads to us asking the user to run the emerge once more with LC_ALL=C. LC_ALL does a lot more than localization of messages. this topic has come up before on the list, so i'd search the archives for all the reasons why this is not the thing to do. Well if complete LC_ALL is not option so how about reseting at least LC_MESSAGES... that would be a lot safer, but i still dont agree it should be done. document the process in the bugzilla howto and call it a day. see #198077 and #260477. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] LC_ALL=C Set by default for portage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harald van Dijk yazmış: On Sun, Mar 08, 2009 at 09:27:20PM +0100, Alexis Ballier wrote: Moreover this would automagically solve the [a-z] friends regexp failures; though that's still good QA to fix them but we wouldn't encounter them anymore. We would encounter them when using the programs outside of portage, but not when running the testsuite (if available) from within portage. It would succeed in working around compile-time only bugs, but it would be a major pain for locale bugs that can also cause problems at run time. I agree. There are quite a number of bugs, either compile time or runtime, that can be spotted and reported to upstream (and hope that they get fixed) in Turkish locale and I posted on my dev blog why[1] this happens. I choose to translate the messages after the build.log if I reproduce the bug only in Turkish locale. If our bug reporting guide is not guiding people (yeah people don't read docs and especially ones that are longer than a paragraph and in a language that they can't read) portage could say a few words on sending the bug report in English if it spots another locale with the exception of the bug being a locale specific issue. 1: http://blogs.gentoo.org/serkan/2008/11/16/applications_failing_with_turkish_locale - -- Sincerely, Serkan KABA Gentoo Developer -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkm0kPgACgkQRh6X64ivZaKsKgCfYPtokmwM6G1jyBM1tbBZOrc5 RVwAnAwkHu+nIN4Khtj0lZYgSRnjKiMC =9n5G -END PGP SIGNATURE-
