Simon McVittie wrote:
> The reason I brought it up is that you mentioned detecting such bugs as
> a reason to prefer not to force TZ=UTC for related packages' builds;
> but if that makes a package's build fail, then it becomes "artificially"
> RC, whether it would have been RC on its own merits or
On Thu, 11 Jan 2018 at 11:36:57 +0530, Chris Lamb wrote:
> > > Just as one example, a timezone library that did not work properly
> > > in timezones beyond UTC+0800, etc.
> >
> > That's a bug, sure, but is it necessarily a release-critical bug?
>
> I'm not sure I see the value in discussing
> the
Simon,
> > Just as one example, a timezone library that did not work properly
> > in timezones beyond UTC+0800, etc.
>
> That's a bug, sure, but is it necessarily a release-critical bug?
Although I don't disagree with anything in particular you said on the
question of what is "reasonable" and on
On Tue, 09 Jan 2018 at 19:52:23 +0530, Chris Lamb wrote:
> Just as one example, a timezone library that did not work properly
> in timezones beyond UTC+0800, etc.
That's a bug, sure, but is it necessarily a release-critical bug? The
answer is usually "it's up to the maintainer", whereas FTBFS on a
> It's avaiable only since libc-bin 2.13-1 (so since wheezy I think).
Ah, that explains why not in my case. Thanks!
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13 fp: F7D
Hi Chris,
> In other words, simply forcing the *build* to do the right thing
> can mean we are hiding issues that should be fixed elsewhere
Indeed, but in this case it was simply a .mo file based on a latin1
encoding instead of UTF8, while the main program was loading/running
the files/translatio
> No, C.UTF-8 is guaranteed to be available in Debian.
Thanks, good to know - I couldn't find it/set it up, but this is
probably my very old chroot.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian De
On Tue, Jan 09, 2018 at 11:52:47PM +0900, Norbert Preining wrote:
> > No, C.UTF-8 is guaranteed to be available in Debian.
>
> Thanks, good to know - I couldn't find it/set it up, but this is
> probably my very old chroot.
It's avaiable only since libc-bin 2.13-1 (so since wheezy I think).
--
WB
Hi Norbert et al.,
> it seems that msgfmt has problems when run in a C locale
[…]
> [force a] utf8 locale during the build process
I'm not sure whether the following applies in the case of msgfmt;
this is more of a general remark.
One thing I picked up via the Reproducible Builds project (has it
On Tue, Jan 09, 2018 at 10:31:53PM +0900, Norbert Preining wrote:
> Hi all,
>
> (please Cc)
>
> it seems that msgfmt has problems when run in a C locale, because what
> is produced is not utf8 parsable.
>
> For calibre I need proper utf8 stuff, but I don't see a way to enforce
> an utf8 locale d
Hi all,
(please Cc)
it seems that msgfmt has problems when run in a C locale, because what
is produced is not utf8 parsable.
For calibre I need proper utf8 stuff, but I don't see a way to enforce
an utf8 locale during the build process. I can depend on locales etc,
but en_US.utf8 or C.utf8 seems
11 matches
Mail list logo
