Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Add C.UTF-8 locale to /etc/default/glibc-locales
Date: Sun, 17 Mar 2024 05:27:22 +0100	[thread overview]
Message-ID: <20240317042722.4070628B68@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49162@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 3073 bytes --]

Closed issue by beginner3456789 on void-packages repository

https://github.com/void-linux/void-packages/issues/49162

Description:
### Is this a new report?

Yes

### System Info

Void 6.7.7_1 x86_64 GenuineIntel uptodate rrFFF

### Package(s) Affectedhttps://sourceware.org/glibc/wiki/Proposals/C.UTF-8

glibc-locales-2.38_5 GNU C library - locale data files

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

commented at https://github.com/archlinux/mkinitcpio/commit/5db56e248463033f3d70f192d517498e906b2569

### Expected behaviour

The mkinitcpio was changed to locale C.UTF-8 except the /etc/default/glibc-locales doesn't have that choice. So I had to add the choice `C UTF-8` to the /etc/default/glibc-locales and now there are no errors with mkinitcpio:
```
$ xbps-reconfigure -f glibc-locales
glibc-locales: configuring ...
Generating GNU libc locales...
  en_US.UTF-8... done.
  en_US.ISO-8859-1... done.
  C.UTF-8... done.
glibc-locales: configured successfully.

```

### Actual behaviour

```
==> Starting build: '6.7.7_1'
  -> Running build hook: [base]
/usr/lib/initcpio/functions: line 838: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8): No such file or directory
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'advansys'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'isci'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
==> WARNING: Possibly missing firmware for module: 'ums_eneub6250'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
/usr/lib/initcpio/functions: line 838: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8)
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.7.7_1.img'
bsdtar: Failed to set default localebsdtar: 
Failed to set default locale
==> Initcpio image generation successful
```

### Steps to reproduce

This problem maybe only affects mkinitcpio and started after updating mkinitcpio from v37.3 to v38 and installing kernel 6.7.7_1. Then downgrading to mkinitcpio 37.7 returned the error free behaviour. Then adding the `C UTF-8` choice to /etc/default/glibc-locales allowed installing mkinitcpio 38 and kernel 6.7.7_1 without the above errors about the "cannot change locale". 

So glibc 2.35 changes about C.UTF-8 need to appear in the locales. This should be easy to fix except I am unsure about the correct syntax for the C.UTF-8 entry in the /etc/default/glibc-locales. For reference: https://sourceware.org/glibc/wiki/Proposals/C.UTF-8


      parent reply	other threads:[~2024-03-17  4:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  1:16 [ISSUE] " beginner3456789
2024-03-07  1:31 ` classabbyamp
2024-03-07  1:41 ` beginner3456789
2024-03-07  1:42 ` oreo639
2024-03-07  1:44 ` oreo639
2024-03-07  1:44 ` oreo639
2024-03-07  1:45 ` oreo639
2024-03-07  1:49 ` beginner3456789
2024-03-17  4:27 ` ahesford [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=20240317042722.4070628B68@inbox.vuxu.org \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).