From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: [PATCH 0/2] Last fixes for locales
Date: Tue, 15 May 2018 18:30:50 +0300 [thread overview]
Message-ID: <20180515153052.4946-1-asmirnov@ilbers.de> (raw)
Hi all,
for today there are two locale problems in Isar:
1. During application's build the following is in log:
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
2. Log for isar-bootstrap contains messages like:
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_IN.ISO8859-1"
This series does the following:
1. Moves locale settings from configscripts to isar-bootstrap.
2. Generate en_US.UTF-8 locale as the default one.
Now I haven't observed any locale-related messages.
Alex
Alexander Smirnov (2):
isar-bootsrtap: Setup locale
isar-bootstrap: Generate en_US.UTF-8 locale
.../images/files/debian-configscript.sh | 22 --------------------
.../images/files/raspbian-configscript.sh | 22 --------------------
meta/recipes-core/isar-bootstrap/files/locale | 4 ++++
.../isar-bootstrap/files/locale.nopurge | 10 +++++++++
meta/recipes-core/isar-bootstrap/isar-bootstrap.bb | 16 +++++++++++++--
.../buildchroot/files/configscript.sh | 24 +---------------------
6 files changed, 29 insertions(+), 69 deletions(-)
create mode 100644 meta/recipes-core/isar-bootstrap/files/locale
create mode 100644 meta/recipes-core/isar-bootstrap/files/locale.nopurge
--
2.1.4
next reply other threads:[~2018-05-15 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 15:30 Alexander Smirnov [this message]
2018-05-15 15:30 ` [PATCH 1/2] isar-bootsrtap: Setup locale Alexander Smirnov
2018-05-22 8:04 ` Claudius Heine
2018-05-15 15:30 ` [PATCH 2/2] isar-bootstrap: Generate en_US.UTF-8 locale Alexander Smirnov
2018-05-23 13:18 ` [PATCH 0/2] Last fixes for locales Claudius Heine
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=20180515153052.4946-1-asmirnov@ilbers.de \
--to=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