Hello, Am Samstag, 29. Januar 2022, 00:42:52 CET schrieb Jan Engelhardt:
On Friday 2022-01-28 22:37, Cristian Rodríguez wrote:
Huh.. shouldn't the locale be C on every build step ?
Should, yes. But you need only grep for LC_CT across factory and find...
httpie.spec:export LC_CTYPE=en_US.UTF-8 libmodulemd.spec:export LC_CTYPE=C.utf8 log4net.spec:export LC_CTYPE=en_US.UTF-8 [...]
Most of your grep results are en_US.utf8 or C.utf8, and the good thing is that /usr/lib/locale/en_US.utf8 and /usr/lib/locale/C.utf8 are part of glibc-locale-base. So even with glibc-locale-base, these packages shouldn't have any build issues. The only exception from your list is
words.spec: american*) LC_CTYPE=en_US.UTF-8 ;; words.spec: british*) LC_CTYPE=en_GB.UTF-8 ;; words.spec: canadian*) LC_CTYPE=en_CA.UTF-8 ;;
and since there are words-british and words-canadian subpackages, I'm not too surprised that it uses en_GB and en_CA. (However, I'm surprised that this is needed in the spec.)
this can only be described by a medium not carryable by plaintext email, https://en.meming.world/wiki/Cat_Standing_in_the_Snow
I think my (random!) signature can easily beat this picture ;-)
Yes, especially the "@UTF-8" one.
Just curious - what's the difference between ".UTF-8" and "@UTF-8"? Or is "@UTF-8" just wrong and broken? (Needless to say: There's no "*@UTF-8" in /usr/lib/locale/ on my system, with the full glibc-locale installed.) Regards, Christian Boltz --
AAAAAAAAAHHHHHHHHHHHHHH *inDieTastaturBeiß* ^^^^^^^^^^^^^ Mahlzeit! [> Michael Born und Kara in opensuse-de]
(For those not speaking german: "inDieTastaturBeiß" means "biting the keyboard", and "Mahlzeit" translates to "enjoy your meal".)