Bug#376404: locale settings within pbuilder sessions
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 `- signature.asc Description: PGP signature
Bug#376404: locale settings within pbuilder sessions
I just had to force C.UTF-8 to prevent a FTBFS when using python3 - can we move forward with this? thanks! -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#376404: [Pbuilder-maint] Bug#376404: locale settings within pbuilder sessions
On Fri, Nov 06, 2015 at 02:36:30PM +0100, Paul Gevers wrote: > What do you people think of even setting it to C.UTF-8? (Or am I now > hijacking this bug report for something else) "of course" (to me at least) this would be C.UTF-8, but I don't feel right at owerwriting LC_ALL that way, I'll have to think more about this, sorry. (Yes, I'm part of the reproducible builds team, but I don't think putting LC_ALL in the builder is a sane choice) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#376404: [Pbuilder-maint] Bug#376404: locale settings within pbuilder sessions
On Wed, 05 Jul 2006 00:37:56 +0900 Junichi Uekawawrote: > > Probably all helper scripts that do chroot / $CHROOTEXEC should set > > LC_ALL=C first: > > > > LC_ALL=C chroot $CHROOTEXEC > > pbuilder-buildpackage* * > > pbuilder-buildpackage-funcs* > > pbuilder-checkparams > > pbuilder-createbuildenv* > > pbuilder-loadconfig > > pbuilder-modules ** > > I think most of the time, pbuilder-modules should be included, and > setting LC_ALL=C should cover most cases. What do you people think of even setting it to C.UTF-8? (Or am I now hijacking this bug report for something else) (This idea came up from discussions on reproducible-builds. I see that two of my packages had a slight flaws in building them because they were missing the UTF-8 support). Paul signature.asc Description: OpenPGP digital signature
Bug#376404: [Pbuilder-maint] Bug#376404: locale settings within pbuilder sessions
Hi, On Wed, Jul 05, 2006, Junichi Uekawa wrote: I would have thought LC_ALL=C should override LC_CTIME. I'm suspecting something is wrong. It does: LC_ALL=C LC_TIME=fr_FR.UTF-8 locale [...] LC_TIME=C ... but it's LC_TIME, not LC_CTIME. I second this wish, I want the uploaded result to be touched mostly by commands run within LC_ALL=C, but it would be nice to keep some commands withing the default locale, for example debsign (as it relies on the locale to convert the encoding of the UIDs on keys to the encoding of the terminal and might also spawn a passphrase prompt). -- Loïc Minier [EMAIL PROTECTED]
Bug#376404: [Pbuilder-maint] Bug#376404: locale settings within pbuilder sessions
Hi, I've tried setting 'export LC_ALL=POSIX' in my .pbuilderrc, but this made no difference (while 'export debian_chroot=pbuild$$' works well). Do you explicitly set LC_CTIME? Yes. I would have thought LC_ALL=C should override LC_CTIME. I'm suspecting something is wrong. Probably all helper scripts that do chroot / $CHROOTEXEC should set LC_ALL=C first: LC_ALL=C chroot $CHROOTEXEC pbuilder-buildpackage* * pbuilder-buildpackage-funcs* pbuilder-checkparams pbuilder-createbuildenv* pbuilder-loadconfig pbuilder-modules ** I think most of the time, pbuilder-modules should be included, and setting LC_ALL=C should cover most cases. regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#376404: [Pbuilder-maint] Bug#376404: locale settings within pbuilder sessions
Junichi Uekawa wrote: Hi, I've tried setting 'export LC_ALL=POSIX' in my .pbuilderrc, but this made no difference (while 'export debian_chroot=pbuild$$' works well). Do you explicitly set LC_CTIME? Yes. Probably all helper scripts that do chroot / $CHROOTEXEC should set LC_ALL=C first: LC_ALL=C chroot $CHROOTEXEC pbuilder-buildpackage* * pbuilder-buildpackage-funcs* pbuilder-checkparams pbuilder-createbuildenv* pbuilder-loadconfig pbuilder-modules ** pbuilder-runhooks * pbuilder-satisfydepends* pbuilder-updatebuildenv* pdebuild-checkparams pdebuild-internal I hope, I didn't miss an occurrence. I didn't check the call-graph/source-graph, the two LC_ALL settings might cover most $CHROOTEXEC invokations. Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#376404: locale settings within pbuilder sessions
Package: pbuilder Version: 0.155 Severity: wishlist Hi, I'd like pbuilder to run commands in cleaned locale settings (e.g. LC_ALL=POSIX) in the chroot environment, because - in a minimal and clean build environment no locales (besides the default) are available - some programs (e.g. perl) complain about missing locales My locale settings are the following: LANG= LC_CTYPE=en_US.UTF-8 LC_TIME=en_DK.UTF-8 LC_COLLATE=POSIX LC_ALL= and I've seen the following warnings while using pbuilder: ... dh_installdebconf perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_COLLATE = POSIX, LC_TIME = en_DK.UTF-8, LANG = (unset) are supported and installed on your system. perl: warning: Falling back to the standard locale (C). ... I've tried setting 'export LC_ALL=POSIX' in my .pbuilderrc, but this made no difference (while 'export debian_chroot=pbuild$$' works well). Testing with 'pbuilder login' or 'pbuilder execute -- /usr/bin/locale' shows the following settings: LANG=C LC_ALL=C A fix grep shows settings of LC_ALL=C in pbuilder-buildpackage and pbuilder-modules. Probably this needs to be done at more places. Andreas -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable'), (30, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-k7 Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages pbuilder depends on: ii cdebootstrap 0.3.11 Bootstrap a Debian system ii coreutils 5.96-3 The GNU core utilities ii debianutils 2.16.1 Miscellaneous utilities specific t ii debootstrap 0.3.3 Bootstrap a basic Debian system ii gcc 4:4.0.3-4 The GNU C compiler ii wget 1.10.2-1 retrieves files from the web Versions of packages pbuilder recommends: ii devscripts2.9.20 Scripts to make the life of a Debi ii fakeroot 1.5.8 Gives a fake root environment ii sudo 1.6.8p12-4 Provide limited super user privile -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#376404: [Pbuilder-maint] Bug#376404: locale settings within pbuilder sessions
Hi, I've tried setting 'export LC_ALL=POSIX' in my .pbuilderrc, but this made no difference (while 'export debian_chroot=pbuild$$' works well). Do you explicitly set LC_CTIME? This is at most a cosmetic thing (perl would complain loudly, but that's because it's braindead; but it does fall back to something sane, so it's not a real problem) regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]