Hi all
The problem is, we keep fixing it in new spots. The last time this
occured was a couple of python versions ago. Now it seems they again
found a way to trigger this edge case.
We can forcefully set LANG when calling python but that variable can
leak into the program at anytime from your ENV. Thus in general Please
use a UTF-8 locale. Any UTF-8 locale will do. C.UTF-8 for root is
preffered wince we always test with that but any UTF-8 locale will do.
If you have an application or user that needs a non UTF-8 locale try to
limit the override as close to just the application as possible.
We tried to fight upstream python on this before but it's a Cat and
mouse game and we are loosing that. As long as pkg is written in python
this kind of error will keep happening with non UTF-8 locales.
I know this is not the good answer but it's what we can do given the
circumstances. No other OS is fighting python on the UTF-8 issue anymore.
Hope this clarifies situation.
In short. Try to limit the usage of non UTF-8 locales to non IPS related
informations.
-Till
On 15.05.23 22:40, Tim Mooney via openindiana-discuss wrote:
In regard to: Re: [OpenIndiana-discuss] pkg update fails, Predrag
Zečević...:
But, why suddenly that is required? I never had to do it...
Will that be fixed in near future?
I remember a thread about a very similar issue, and I found it:
Subject: pkg update is failing
Date: Sept 4, 2019
Predrag posted in that thread (as did I). At the time, it was suggested
that
any of the UTF8 locales would be enough.
Tim
_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
