Bug#1060288: locales: Please allow selection of C.UTF-8 when (re)configuring locales
Hi, On Tue, Jan 9, 2024 at 11:54 PM Aurelien Jarno wrote: > The problem is that you end-up with two C.UTF-8 locales on the system. > The one generated and the one provided by libc6. Normally that should > work fine, but there is no 100% guarantee that the C.UTF-8 working is > working fine during a major upgrade, between the time libc6 and locales > are unpacked. Ah ok I understand, thanks for explaining. > I have just implemented that in git, the current behaviour is a > left-over from before the time C.UTF-8 existed. Thanks! Kind regards, Axel Scheepers
Processed: Bug#1060288 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1060288 [locales] locales: Please allow selection of C.UTF-8 when (re)configuring locales Added tag(s) pending. -- 1060288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060288: locales: Please allow selection of C.UTF-8 when (re)configuring locales
Hi, On 2024-01-09 17:47, Axel Scheepers wrote: > Hello, > > On Tue, Jan 9, 2024 at 7:18 AM Aurelien Jarno wrote: > > C.UTF-8 is not shown on purpose, because it doesn't need to be > > generated, it is always available on the system. What you want is > > probably to be able to select it as a default locale. > > Ah yes indeed. I was confused because it's an entry in /etc/locale.gen > and uncommenting it and running dpkg-reconfigure locales showed it was > generating it. This is the first time I had to use C.UTF-8. Can you > elaborate on why it would be problematic to include it in the list? The problem is that you end-up with two C.UTF-8 locales on the system. The one generated and the one provided by libc6. Normally that should work fine, but there is no 100% guarantee that the C.UTF-8 working is working fine during a major upgrade, between the time libc6 and locales are unpacked. > > A better workaround is probably to select a random locale to be > > generated, then you should be able to select the C.UTF-8 locale as > > default. > > Thanks, yes indeed that's better. I have just implemented that in git, the current behaviour is a left-over from before the time C.UTF-8 existed. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
[Git][glibc-team/glibc][sid] debian/debhelper.in/locales.config: always ask for the default locale, even if...
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: 79dd4ae0 by Aurelien Jarno at 2024-01-09T23:54:17+01:00 debian/debhelper.in/locales.config: always ask for the default locale, even if none are generated. This enables choosing C.UTF-8 as the default locale. Closes: #1060288. - - - - - 2 changed files: - debian/changelog - debian/debhelper.in/locales.config View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/79dd4ae0f78f434c990752329a74f84802588ee1 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/79dd4ae0f78f434c990752329a74f84802588ee1 You're receiving this email because of your account on salsa.debian.org.
Bug#1060288: locales: Please allow selection of C.UTF-8 when (re)configuring locales
Hello, On Tue, Jan 9, 2024 at 7:18 AM Aurelien Jarno wrote: > C.UTF-8 is not shown on purpose, because it doesn't need to be > generated, it is always available on the system. What you want is > probably to be able to select it as a default locale. Ah yes indeed. I was confused because it's an entry in /etc/locale.gen and uncommenting it and running dpkg-reconfigure locales showed it was generating it. This is the first time I had to use C.UTF-8. Can you elaborate on why it would be problematic to include it in the list? > A better workaround is probably to select a random locale to be > generated, then you should be able to select the C.UTF-8 locale as > default. Thanks, yes indeed that's better. Kind regards, Axel Scheepers
