Bug#376404: locale settings within pbuilder sessions

[Mattia Rizzolo]

control: tag -1 wontfix
control: close -1

On Sun, Sep 18, 2016 at 09:15:35PM +0100, Sandro Tosi wrote:
> I just had to force C.UTF-8 to prevent a FTBFS when using python3 -
> can we move forward with this?

packages has to be able to build in whatever locale they are.
policy doesn't mandate any particular locale, nor builder, nor anything,
and instead I expect every person to be able to rebuild any package
(reproducibly, even) in whatever locale they find themselves in.

I looked up what sbuild is doing here: it doesn't do anything locale
related, the only difference is that it filters out all env variables
before starting.


Instead, I'm thinking about removing the 'export LANG=C' and
'export LC_ALL=C' that are there already.


Please see #838175 for a similar thing about sbuild.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pbuilder-maint/attachments/20160919/a1b929c4/attachment.sig>