Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Locale settings are not being registered #80

Closed
cmorgenstern opened this issue Jun 4, 2022 · 5 comments
Closed

Locale settings are not being registered #80

cmorgenstern opened this issue Jun 4, 2022 · 5 comments

Comments

@cmorgenstern
Copy link

clean-chroot-manager-2.222-1

With the recent update of Perl to 5.36, a number of locale warnings have been cropping up when building packages via ccm s. Here is an example of the output from building lib32-libusb-compat:

...
==> Extracting sources...
  -> Extracting lib32-libusb-compat-0.1.7.tar.gz with bsdtar
bsdtar: Failed to set default locale
==> Starting prepare()...
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LANG = "C.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
...

I nuked and re-created the buildroot, and confirmed that locale-gen ran as expected as part of the setup:

...
Generating locales...
  en_US.UTF-8... done
  de_DE.UTF-8... done
Generation complete.

However, the locale warnings are still cropping up during builds. I have not customised any of the locale-related files such as /etc/locale.gen and /etc/locale.conf within the chroot, and the locale generation step on creation appears to have completed successfully.

@graysky2
Copy link
Owner

graysky2 commented Jun 4, 2022

Have you verified that this issue doesn't also affect devtools alone?

@cmorgenstern
Copy link
Author

cmorgenstern commented Jun 4, 2022

Thanks for the tip - it looks like something is preventing LANG from being persistently set. This is the output when checking the current setting of LANG in the chroot:

[user@system ~]$ sudo arch-nspawn /home/user/chroot/.chroot64/root printenv | grep LANG
[sudo] password for user: 
LANG=C.UTF-8

When I log into the chroot and toggle LANG by unsetting it and then sourcing /etc/profile.d/locale.sh, it does not persist:

[user@system ~]$ sudo arch-nspawn /home/user/chroot/.chroot64/root
[sudo] password for user: 
[root@root ~]# echo $LANG
C.UTF-8
[root@root ~]# unset LANG
[root@root ~]# source /etc/profile.d/locale.sh 
[root@root ~]# echo $LANG
en_US.UTF-8
[root@root ~]# 
logout
[user@system ~]$ sudo arch-nspawn /home/user/chroot/.chroot64/root printenv | grep LANG
[sudo] password for user: 
LANG=C.UTF-8

Since devtools has not had an update since March 2022, I wonder if there is something else that is hijacking LANG - I'll keep digging.

I take it you are not experiencing this issue, though?

@graysky2
Copy link
Owner

graysky2 commented Jun 4, 2022

I have seen it but have not dug into it as it defaults to something sane. Need to figure out what is to blame, ccm or devtools.

Seems to be happening with devtools on Arch ARM as well (no ccm in the mix):

==> Extracting sources...
  -> Extracting xbmc-20.x.60475.fc29968341.tar.gz with bsdtar
bsdtar: Failed to set default locale
  -> Extracting ArchARM-kodi-init-v1.136.tar.gz with bsdtar
bsdtar: Failed to set default locale
...

@graysky2
Copy link
Owner

graysky2 commented Jun 5, 2022

Confirmed, I do not believe this is a bug within ccm. I opened FS#74967

EDIT: And I didn't do a throughout job searching: FS#74864

Anyway, unrelated to ccm. Closing.

@graysky2 graysky2 closed this as completed Jun 5, 2022
@cmorgenstern
Copy link
Author

Thanks @graysky2, appreciate you opening a bug in FS - I should have checked there too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants