Your message dated Mon, 26 Sep 2016 23:51:02 +0200
with message-id <[email protected]>
and subject line Re: Bug#838175: change default locale to C.UTF-8 in chroots
has caused the Debian Bug report #838175,
regarding change default locale to C.UTF-8 in chroots
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
838175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838175
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: sbuild
version: 0.71.0-2
severity: wishist
(if this should go to debootstrap, then please reassign)
Many packages now expect a UTF-8 locale and we have to manually specify
LC_ALL=C.UTF-8. I think it is better to make C.UTF-8 as the default
locale for chroots to avoid fixing so many packages.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi!
On Sun, 2016-09-18 at 20:41:39 +0530, Pirate Praveen wrote:
> On Sunday 18 September 2016 08:17 PM, Guillem Jover wrote:
> > The request is not very clear, so let me try to run it down. If it
> > is about binary packages, then that cannot be done, please refer to
> > policy ยง9.9.
> >
> > I'm assuming, though, that this is related to source packages and
> > building them? In that case as josch has mentioned package cannot
> > assume that anything will set up their environment as they should
> > (still) support being called simply as debian/rules, which is the
> > only defined entry point.
>
> It about providing a UTF-8 locale as default in build environment.
Thanks, and as stated above, in that case I don't think this
can/should be (currently) fixed in a central place.
> > In addition C.UTF-8 locales provided by default were a Debianism not
> > until recently, and even now might be a glibc-ism. So not something
> > that even dpkg-buildpackage might be able to rely on, given that it
> > is being used beyond glibc and Debian.
> >
> > If a (binary/source) package requires the current locale to be UTF-8
> > then it should set it itself. Even debootstrap might be able to set a
> > default, but that does not mean the user might not modify it later on.
>
> Usually the problem is only in build chroots, most users already have a
> UTF-8 locale.
I don't think that does matter much, see below.
> > So as things stand now I don't think this can be fixed centrally, and
> > I'm in principle planning on closing this report in a bit if no
> > clarifications or compelling arguments are put forwards.
>
> Most tools (even languages like python allows variable names in UTF-8)
> now supports UTF-8 and many are adding support. It is only natural to
> change defaults when situations change. I think doing it centrally is
> the best thing to do.
If those source packages *require* an UTF-8 locale they should really
set it up in their debian/rules, in the same way you'd set up any
other variable or build requirement. The user might have a non-UTF-8
locale and packages still need to work in that case, because as stated
above, the canonical building entry point is still debian/rules.
It's certainly true that setting such defaults globally, would be
easier, but I think whether that'd be best is arguable. I've written
about this in the past, please have a look at:
<https://lists.debian.org/debian-dpkg/2012/02/msg00086.html>
So I'm closing this report with this mail, if you still think this
needs to be pursued, then you'd probably need project-wide consensus
that debian/rules is not the canonical build entry point anymore. :)
(And I should probably also add a new dpkg FAQ entry. :)
Thanks,
Guillem
--- End Message ---
