On 12/11/14 at 15:06 +0100, Martin Quinson wrote: > retitle 768732 plm: FTBFS in non-UTF-8 settings > thanks > > Hello, > > thanks for this additional information, that's indeed the source of > the problem. The PLM package builds correctly if I set LC_ALL=C.UTF-8 > in addition to your settings and fails without it. > > But, it seems to me that the package built with non-utf locale > settings will not be functionnal for non-english speakers. At least > that's what I understand from the msggrep warnings. > > Could you please point me to the part of the policy that is relevant > to the locale settings of the builder? I fail to find anything > relevant by myself, sorry.
I'm not sure if this is specified. my chroot is generated by sbuild-createchroot, without any further customization. One could argue that sbuild could default to C.UTF-8, but OTOH, all other packages build fine (or fail for unrelated reasons). > In the meanwhile, I will patch most of the java files to not use the > UTF encoding. I'm just reluctant do so in some cases where it would > not be an improvement. For example, it would request to write the name > of "Gérald Oster" as "Gerald Oster". Not a big deal, but not nice. couldn't you build with javac -encoding "UTF-8"? See http://stackoverflow.com/questions/1726174/how-to-compile-a-java-source-file-which-is-encoded-as-utf-8 Regarding the msggrep warnings, I'm not sure if they are really harmless. > I guess that it would not be ok to set LC_ALL=C.UTF-8 in the rules > file, right? That would probably work, yes. Lucas
signature.asc
Description: Digital signature
