<stenur>
jaeger: i see (mostly updating saturdays' only)
<farkuhar>
stenur: actually it was the glibc version bump that prompted me to revise the section about locales in the handbook. Manually running localedef (the old handbook instructions) creates the file /usr/lib/locale/locale-archive, but the glibc post-install script removes the archive file before even checking whether there are uncommented lines in /etc/locale.gen !
<stenur>
what do you mean by "removes the archive?"
<stenur>
i hope not, still running; maybe recreation wouldn't be that bad, 'forgotten how standardized all this is
<stenur>
did indeed! oops. Thanks for mentioning this! Maybe the port should check whether there are any non-comment non-empty lines in /etc/locale.gen, and bail if not?
<farkuhar>
the script /usr/sbin/locale-gen is copied directly from the ports tree (not from an unpacked tarball), so it's something we could easily modify if there was a desire to do so. I think it's just easier to change the handbook instructions so that /etc/locale.gen is guaranteed to have uncommented lines on a properly-configured system.
<jue>
for what? locale.gen will not be overwritten if you install glibc, only i you tell rejmerge to that, so locale-gen recreates locale-arhive
<jue>
what is what you want
<stenur>
but it did not exist before 2.36, and anything was removed
<stenur>
in fact i saw myriads of: spamrate: .43 114/26 /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
<jue>
before 2.36 you do not have a locale.gen
<stenur>
in the mail terminal before i uncommented lines in /etc/locale.gen and manually run locale-gen
<stenur>
..i am running a 2019 CRUX that is just updated over and over again..
<stenur>
yes. /etc/locale.gen only had commented fields, so the post-install did not actually create locales
<jue>
before 2.36 you have to run localedef manualy
<stenur>
..so i had a few seconds without my actual locale on the system..
<jue>
yeah, that's normal, with each major update ot glibc you have to recreate the locale
<farkuhar>
the CRUX 3.7 release ISO will be shipping with glibc 2.36, so there will be a file /etc/locale.gen and a script /usr/sbin/locale-gen to process it. The sandbox handbook now refers to these files, rather than the old method of running localedef manually.
<stenur>
yes.
<jue>
fine, but I still do not understand why you complain about the remove of locale-archive?
<stenur>
i never did
<stenur>
i suggested pimping the post-install script to check whether there are any non-empty non-comment lines in /etc/locale.gen or what its name is
<jue>
my question was meant for farkuhar
<stenur>
whatever you say
<farkuhar>
no complaint here, just an observation about possible side effects if /etc/locale.gen contained only comment-lines at the time of running glibc/post-install.
<jue>
ok
<farkuhar>
which is how it would have looked for an upgrade from glibc-2.35. But the upgrade path is only encountered by us early testers, and installing from a 3.7 release ISO will not have the same side effects.
<stenur>
yeah shit onto upgraders!
<stenur>
boooooooooh!
<jaeger>
The effect of having a fully-commented locale.gen is the same as the pre-3.7 behavior. If you upgraded/rebuilt glibc, you needed to recreate your locales.
<stenur>
i never did. i only added C.utf8 or what last year.
<stenur>
but don't mind, everything is fine here! outta a bit while my brave laptop does the non-glibc non-kmod build while a massive storm front approaches, 'hope i be back in time. ciao
farkuhar has quit [Ping timeout: 268 seconds]
groovy3shoes has quit [Remote host closed the connection]
groovy3shoes has joined #crux-devel
SiFuh has quit [Read error: Connection reset by peer]
SiFuh has joined #crux-devel
SiFuh has quit [Ping timeout: 268 seconds]
SiFuh has joined #crux-devel
jue has quit [Ping timeout: 252 seconds]
stenur has quit [Remote host closed the connection]
stenur has joined #crux-devel
farkuhar has joined #crux-devel
<jaeger>
ran into a problem updating pipewire-32, it couldn't find glib for some reason... don't have time to dig into it more now, leaving soon... but I'll check it out later