On Friday 2022-01-28 22:37, Cristian Rodríguez wrote:
On Fri, Jan 28, 2022 at 11:43 AM Dirk Müller <dirk@dmllr.de> wrote: < if
you're behind crappy internet like a german citizen would be, then you love the speedup.
I am behind fast internet but osc seems to talk to snail mirrors so this change actually helps me too.
It might be more of a concern for bs_worker-type workers than it is for an osc-type worker, since osc certainly keeps a cache in /var/tmp/osbuild-packagecache.
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 procps.spec:unset LC_CTYPE python-eliot.spec:export LC_CTYPE=en_US.UTF-8 python-Flask-Gravatar.spec:export LC_CTYPE=en_US@UTF-8 python-Flask-Migrate.spec:export LC_CTYPE=en_US.UTF-8 python-nose2.spec:export LC_CTYPE=C.UTF8 readline6.spec: unset LC_CTYPE readline.spec:unset LC_CTYPE ruby2.7.spec:export LC_CTYPE="en_US.UTF-8" ruby3.0.spec:export LC_CTYPE="en_US.UTF-8" texlive.spec: echo LC_CTYPE=en_US.UTF-8 texlive.spec: echo export LANG LC_CTYPE 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 ;; this can only be described by a medium not carryable by plaintext email, https://en.meming.world/wiki/Cat_Standing_in_the_Snow Yes, especially the "@UTF-8" one.