Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1077744 > unrolled thread

Bug#973313: The locales package not installed in salsa lintian Docker image

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#973313: The locales package not installed in salsa lintian Docker image xiao sheng wen(肖盛文) <atzlinux@sina.com> - 2021-10-24 06:00 +0200
    Bug#973313: The locales package not installed in salsa lintian Docker image Felix Lechner <felix.lechner@lease-up.com> - 2021-10-24 06:20 +0200
      Bug#973313: The locales package not installed in salsa lintian Docker image xiao sheng wen(肖盛文) <atzlinux@sina.com> - 2021-10-24 12:00 +0200
        Bug#973313: The locales package not installed in salsa lintian Docker image Felix Lechner <felix.lechner@lease-up.com> - 2021-10-24 12:30 +0200
          Bug#973313: The locales package not installed in salsa lintian Docker image xiao sheng wen(肖盛文) <atzlinux@sina.com> - 2021-10-24 15:50 +0200
            Bug#973313: The locales package not installed in salsa lintian Docker image Felix Lechner <felix.lechner@lease-up.com> - 2021-10-24 18:40 +0200
              Bug#973313: Is the "LC_ALL=C.UTF-8" export to forked bash child process that run man check? xiao sheng wen(肖盛文) <atzlinux@sina.com> - 2021-10-25 06:40 +0200
                Bug#973313: Is the "LC_ALL=C.UTF-8" export to forked bash child process that run man check? Felix Lechner <felix.lechner@lease-up.com> - 2021-10-25 18:40 +0200
                  Bug#973313: ssh to salsa-runner.debian.net debug xiao sheng wen(肖盛文) <atzlinux@sina.com> - 2021-10-26 09:40 +0200
                    Bug#973313: add one locale command in Executing "step_script" stage xiao sheng wen(肖盛文) <atzlinux@sina.com> - 2021-10-26 10:00 +0200
      Bug#973313: The locales package not installed in salsa lintian Docker image xiao sheng wen(肖盛文) <atzlinux@sina.com> - 2021-10-24 17:20 +0200

#1077744 — Bug#973313: The locales package not installed in salsa lintian Docker image

[Multipart message — attachments visible in raw view] — view raw

Hi,

     The Docker images provided by Salsa CI:

registry.salsa.debian.org/salsa-ci-team/pipeline/lintian:unstable

It has not install the locales package.

The locales.postinst of locales package can set the LC_ALL, LANG and 
generate some files,etc.

Is this  the root case of this bug?


-- 
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB

[toc] | [next] | [standalone]

#1077746

Hi 肖盛文

On Sat, Oct 23, 2021 at 8:51 PM xiao sheng wen <atzlinux@sina.com> wrote:
>
> Is this  the root case of this bug?

Possibly. I thought I had looked into the locales question with Iñaki
Malerba from the Salsa CI Team about a year ago. If you found it, I am
going to have a party!

The messages have never been reported in any other setting. Just this
morning, I was again unable to reproduce the messages on my local
system with

    docker run --rm -it --privileged
registry.salsa.debian.org/salsa-ci-team/pipeline/lintian:unstable bash

and concluded that Salsa's host system was probably to blame. The
shared runner operates in 'privileged' mode. [1]

I also contemplated other methods making the C.UTF-8 locale available
via the Docker file. [2]

I'll look into the Salsa runner package list again, unless you beat me to it.
Thanks!

Kind regards
吴大菲 (Felix Lechner)

[1] https://www.educba.com/docker-privileged/
[2] https://leimao.github.io/blog/Docker-Locale/

[toc] | [prev] | [next] | [standalone]

#1077782

[Multipart message — attachments visible in raw view] — view raw

Hi,

在 2021/10/24 下午12:13, Felix Lechner 写道:
> Hi 肖盛文
> Possibly. I thought I had looked into the locales question with Iñaki
> Malerba from the Salsa CI Team about a year ago. If you found it, I am
> going to have a party!
I hope. :-)
>
> The messages have never been reported in any other setting. Just this
> morning, I was again unable to reproduce the messages on my local
> system with
>
>      docker run --rm -it --privileged
> registry.salsa.debian.org/salsa-ci-team/pipeline/lintian:unstable bash
>
> and concluded that Salsa's host system was probably to blame. The
> shared runner operates in 'privileged' mode. [1]

The Salsa's host system, Can ssh to it?

SSH to it, login into  the lintian docker, then run debug tools like 
strace -p ,etc. on the lintian's groff-message process.

If we has lucky, we perhaps find some thing. We also can check the 
/var/log dir to find error infos.

The Salsa's host system's /var/log dir, check it too.

>
> I also contemplated other methods making the C.UTF-8 locale available
> via the Docker file. [2]

Install locales package is preferably in Docker image, 
/etc/default/locale and /etc/locale.gen will exist in the docker after 
install it.

At present, these two files don't exist in the docker of

registry.salsa.debian.org/salsa-ci-team/pipeline/lintian:unstable

>
> I'll look into the Salsa runner package list again, unless you beat me to it.
> Thanks!
>
> Kind regards
> 吴大菲 (Felix Lechner)
>
> [1] https://www.educba.com/docker-privileged/
> [2] https://leimao.github.io/blog/Docker-Locale/

-- 
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB

[toc] | [prev] | [next] | [standalone]

#1077786

Hi,

On Sun, Oct 24, 2021 at 2:46 AM xiao sheng wen(肖盛文) <atzlinux@sina.com> wrote:
>
> The Salsa's host system, Can ssh to it?

I do not think either one of us can.

> Install locales package is preferably in Docker image,
> /etc/default/locale and /etc/locale.gen will exist in the docker after
> install it.

For now, I requested locales-all. [1]

Kind regards
Felix Lechner

[1] https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/312

[toc] | [prev] | [next] | [standalone]

#1077855

[Multipart message — attachments visible in raw view] — view raw

Hi,

lintian-explain-tags groff-message

[...]

N:   You can see the warnings yourself by running the command used by 
Lintian:
N:
N:       LC_ALL=en_US.UTF-8 MANROFFSEQ='' MANWIDTH=80 \
N:           man --warnings -E UTF-8 -l -Tutf8 -Z <file> >/dev/null

[...]


The "LC_ALL=en_US.UTF-8" strings is outdated in this command.

I also suggest to update.


Thanks!

-- 
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB

[toc] | [prev] | [next] | [standalone]

#1077871

Hi,

On Sun, Oct 24, 2021 at 6:45 AM xiao sheng wen <atzlinux@sina.com> wrote:
>
> The "LC_ALL=en_US.UTF-8" strings is outdated in this command.

With a Chinese default locale, you probably have a lot more experience
with all this, but I do not understand. Lintian does not use
en_US.UTF-8 but C.UTF-8. [1]

Should it only use LANG? How does that jibe with the recommendation
here [2][3] to always use LC_ALL when running programs? Thanks!

Kind regards
Felix Lechner

[1] https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/Documentation/Manual.pm#L295
[2] https://stackoverflow.com/a/30480596
[3] https://pubs.opengroup.org/onlinepubs/7908799/xbd/envvar.html

[toc] | [prev] | [next] | [standalone]

#1077904 — Bug#973313: Is the "LC_ALL=C.UTF-8" export to forked bash child process that run man check?

[Multipart message — attachments visible in raw view] — view raw

在 2021/10/25 上午12:35, Felix Lechner 写道:
> With a Chinese default locale, you probably have a lot more experience
> with all this, but I do not understand. Lintian does not use
> en_US.UTF-8 but C.UTF-8. [1]

I can reproduce this bug in my test server.

My notebook use zh_CN.UTF-8 locale, ssh to the test server.

1. The test server has not any other locale except default.
2. I also already apt purge locale package on test server.
3. The ssd_config of the test server has the following config to accept my notebook locale zh_CN.UTF-8
:

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

----------------------------------------------------------------------------

atzlinux@hwymini:~$ locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
C.UTF-8
POSIX

atzlinux@hwymini:~$ locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=zh_CN.UTF-8
LANGUAGE=
LC_CTYPE="zh_CN.UTF-8"
LC_NUMERIC="zh_CN.UTF-8"
LC_TIME="zh_CN.UTF-8"
LC_COLLATE="zh_CN.UTF-8"
LC_MONETARY="zh_CN.UTF-8"
LC_MESSAGES="zh_CN.UTF-8"
LC_PAPER="zh_CN.UTF-8"
LC_NAME="zh_CN.UTF-8"
LC_ADDRESS="zh_CN.UTF-8"
LC_TELEPHONE="zh_CN.UTF-8"
LC_MEASUREMENT="zh_CN.UTF-8"
LC_IDENTIFICATION="zh_CN.UTF-8"
LC_ALL=

atzlinux@hwymini:~$ LC_ALL=C.UTF-8

atzlinux@hwymini:~$ locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=zh_CN.UTF-8
LANGUAGE=
LC_CTYPE="zh_CN.UTF-8"
LC_NUMERIC="zh_CN.UTF-8"
LC_TIME="zh_CN.UTF-8"
LC_COLLATE="zh_CN.UTF-8"
LC_MONETARY="zh_CN.UTF-8"
LC_MESSAGES="zh_CN.UTF-8"
LC_PAPER="zh_CN.UTF-8"
LC_NAME="zh_CN.UTF-8"
LC_ADDRESS="zh_CN.UTF-8"
LC_TELEPHONE="zh_CN.UTF-8"
LC_MEASUREMENT="zh_CN.UTF-8"
LC_IDENTIFICATION="zh_CN.UTF-8"
LC_ALL=

atzlinux@hwymini:~$ MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z /usr/share/man/man1/ls.1.gz > /dev/null
man: can't set the locale; make sure $LC_* and $LANG are correct
--------------------------------
The same error infos display.

--------------------------------
atzlinux@hwymini:~$ export LC_ALL=C.UTF-8
atzlinux@hwymini:~$ locale
LANG=zh_CN.UTF-8
LANGUAGE=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_PAPER="C.UTF-8"
LC_NAME="C.UTF-8"
LC_ADDRESS="C.UTF-8"
LC_TELEPHONE="C.UTF-8"
LC_MEASUREMENT="C.UTF-8"
LC_IDENTIFICATION="C.UTF-8"
LC_ALL=C.UTF-8

atzlinux@hwymini:~$ MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z /usr/share/man/man1/ls.1.gz > /dev/null
atzlinux@hwymini:~$
---------------------------------
There is not errors after export.

So,my question is: Is the "LC_ALL=C.UTF-8" export to forked bash child process that run man check?

--------
BTW, "You could not reproduce the error in Docker locally with the Salsa CI Lintian image—and your host uses the default locale|en_US.UTF-8|. "

I think is that the screen output of console running Docker inherit the|en_US.UTF-8|  locale from your host, you may run locale to see the LANG in Docker. Is it|en_US.UTF-8|?

I guess the Dcoker can use|en_US.UTF-8|  locale come from your host, even the Docker itself has not the|en_US.UTF-8|  locale produced.

Thanks!

xiao sheng wen

[toc] | [prev] | [next] | [standalone]

#1078036 — Bug#973313: Is the "LC_ALL=C.UTF-8" export to forked bash child process that run man check?

Hi,

On Sun, Oct 24, 2021 at 9:33 PM xiao sheng wen <atzlinux@sina.com> wrote:
>
> I can reproduce this bug in my test server.

I can't believe it. Finally!

> My notebook use zh_CN.UTF-8 locale, ssh to the test server.

Is the test server an sshd inside Docker?

> So,my question is: Is the "LC_ALL=C.UTF-8" export to forked bash child process that run man check?

It is. I confirmed that just now by replacing the call to 'man' with
'/bin/sh -c "echo $LC_ALL"'. The output was C.UTF-8.

> I think is that the screen output of console running Docker inherit the en_US.UTF-8 locale from your host, you may run locale to see the LANG in Docker. Is it en_US.UTF-8?

Here is the complete output in Docker:

root@5fc85dcffb70:/# locale -a
C
C.UTF-8
POSIX

root@5fc85dcffb70:/# locale
LANG=
LANGUAGE=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=

And here on the server:

On the host, I use:

➤ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

The output from 'locale -a' is too long. I must have 'locales-all' installed.

Kind regards
Felix Lechner

[toc] | [prev] | [next] | [standalone]

#1078089 — Bug#973313: ssh to salsa-runner.debian.net debug

[Multipart message — attachments visible in raw view] — view raw

> Is the test server an sshd inside Docker?
NO, it's a vm on cloud, not a Docker.
> It is. I confirmed that just now by replacing the call to 'man' with
> '/bin/sh -c "echo $LC_ALL"'. The output was C.UTF-8.

In your personal test environment, Docker's  $LC_ALL is no problem.

The best way to debug this bug still is that ssh to 
|salsa-runner.debian.net.|


Kind regards

-- 
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB

[toc] | [prev] | [next] | [standalone]

#1078091 — Bug#973313: add one locale command in Executing "step_script" stage

[Multipart message — attachments visible in raw view] — view raw

|From pipeline output, we can see the following:
|

|Executing "step_script" stage of the job script|||||

||Using docker image 
sha256:24afe9d1b53c4fce05efee899c534326551d551d36185dd2e440c5bf8d6f3684 
for registry.salsa.debian.org/salsa-ci-team/pipeline/lintian:unstable 
with digest 
registry.salsa.debian.org/salsa-ci-team/pipeline/lintian@sha256:1a5f17beebf2450027bd100e0481627f8e86bf04f3988528263a9c9981e841b7 
...
||
||
$ lintian --version
||

||||||

||Lintian v2.110.0||
||||
$ if lintian --fail-on error --allow-root > /dev/null ; then # collapsed 
multi-line command
||$ lintian --suppress-tags "${SALSA_CI_LINTIAN_SUPPRESS_TAGS}" 
--display-info --pedantic ${SALSA_CI_LINTIAN_FAIL_ARG} --allow-root 
${WORKING_DIR}/*.changes | tee lintian.output || ECODE=$?||

||
||

||How about ||||||add one locale command in |||||Executing "step_script" 
stage?|||||

|||||So we can find the locale which the Docker use.
|||||

|||
|||

|
|

[toc] | [prev] | [next] | [standalone]

#1077864

[Multipart message — attachments visible in raw view] — view raw

> and concluded that Salsa's host system was probably to blame.

I guess the Salsa's host system use LANG=en_US.UTF-8.

Even lintian had set local $ENV{LC_ALL} = 'C.UTF-8'; , But if only reset 
LC_ALL ,it don't reset LANG,

So, the docker still use LANG=en_US.UTF-8(inherit from Salsa's host 
system), this will casue this bug.

So the other way to fix this bug is:

set LANG='C.UTF-8' in lib/Lintian/Check/Documentation/Manual.pm.


I hope has chance to do so to prove my guess.

If it fix the bug, this way will do better than that install locales-all 
in docker.


Thanks!

-- 
肖盛文 xiao sheng wen Faris Xiao

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web