public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: locales are not set in buildchroot
Date: Thu, 26 Apr 2018 14:48:07 +0200	[thread overview]
Message-ID: <303d39b0-5dcb-12bf-0448-39087e1f1d54@siemens.com> (raw)
In-Reply-To: <25d8b95d-6fcf-2ab3-1eb7-45a00fcd26a8@ilbers.de>

Hi Alex,

On 2018-04-23 11:33, Alexander Smirnov wrote:
> Hi all,
> 
> I've noticed that locales are now broken again in buildchroot, dpkg 
> produces tons of garbage in current 'next':
> 
> Log data follows:
> | DEBUG: Executing shell function do_build
> | /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
> | Ign file: isar InRelease
> | Ign file: isar Release.gpg
> | Get:1 file: isar Release [3554 B]
> | Ign file: isar/main Translation-en
> | Reading package lists...
> | perl: warning: Setting locale failed.
> | perl: warning: Please check that your locale settings:
> |     LANGUAGE = (unset),
> |     LC_ALL = "en_US.UTF-8",
> |     LANG = (unset)
> |     are supported and installed on your system.
> | perl: warning: Falling back to the standard locale ("C").
> | /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
> | perl: warning: Setting locale failed.
> | perl: warning: Please check that your locale settings:
> |     LANGUAGE = (unset),
> |     LC_ALL = "en_US.UTF-8",
> |     LANG = (unset)
> |     are supported and installed on your system.
> 
> I guess this caused by migration to debootstrap, please consider to fix 
> this in next series.

While those are just warnings (and we had other warnings in the 
multistrap approach as well), I will take a look at it and fix those.

Thanks,
Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

      reply	other threads:[~2018-04-26 12:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23  9:33 Alexander Smirnov
2018-04-26 12:48 ` Claudius Heine [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=303d39b0-5dcb-12bf-0448-39087e1f1d54@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=asmirnov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox