| 1 |
On 5/7/22 14:24, wkuz@××.pl wrote: |
| 2 |
> Dnia 2022-07-05, o godz. 13:04:07 |
| 3 |
> William Kenworthy <billk@×××××××××.au> napisał(a): |
| 4 |
> |
| 5 |
>> I synced portage a couple of days now and now my systems are |
| 6 |
>> rebuilding python modules for 3.10 without any input from me (prior |
| 7 |
>> to this 3.10 was on the system but wasn't picked up by applications.) |
| 8 |
>> This is breaking non portage apps like homeassistant which are still |
| 9 |
>> not fully 3.10 safe - ok that's sort of expected and in this case |
| 10 |
>> will be fixed, but I cant find anything definitive on the task of "I |
| 11 |
>> want to control which python is used" and when to update. |
| 12 |
>> |
| 13 |
>> I eventually found that changing the order in python-exec.conf helped |
| 14 |
>> on the homeassistant system. There is a LOT of out of date |
| 15 |
>> documentation out there, particularly with eselect being used but is |
| 16 |
>> actually not used with python anymore (why? - from a user point of |
| 17 |
>> view having consistent access to configuration is a no brainer!) - so |
| 18 |
>> how can one get python to behave reliably and override its automatic |
| 19 |
>> get things wrong installation system? Is manually editing |
| 20 |
>> python-exec.conf the way (which seems to get overwritten - shouldn't |
| 21 |
>> that be a protected config file then?) |
| 22 |
>> |
| 23 |
>> BillK |
| 24 |
>> |
| 25 |
>> |
| 26 |
>> |
| 27 |
>> |
| 28 |
> Hello! |
| 29 |
> |
| 30 |
> In "eselect news" info about python update there is a paragraph about |
| 31 |
> blocking the upgrade. It just means adding: |
| 32 |
> |
| 33 |
> */* PYTHON_TARGETS: -* python3_9 |
| 34 |
> */* PYTHON_SINGLE_TARGET: -* python3_9 |
| 35 |
> |
| 36 |
> to /etc/portage/make.conf or /etc/portage/package.use or |
| 37 |
> /etc/portage/package.use/zz-somename - whichever suites you best. |
| 38 |
> |
| 39 |
> You can also change these settings just for some packages, by adding: |
| 40 |
> |
| 41 |
> cat/pkg PYTHON_TARGETS: -* python3_9 PYTHON_SINGLE_TARGET: -* python3_9 |
| 42 |
> |
| 43 |
> to one of aforementioned files. |
| 44 |
> |
| 45 |
> Hope that helps! |
| 46 |
|
| 47 |
|
| 48 |
I did read the news item and set the systems as above with multiple |
| 49 |
python targets - there is no mention of python-exec and its role in |
| 50 |
which python version is in use for packages that just call "python". |
| 51 |
Perhaps I should have been clearer - what I see is with multiple python |
| 52 |
targets present the python ebuild automatically selects the latest |
| 53 |
version that is stable via python-exec - ok, some would want that. But |
| 54 |
what it should do is respect the users choice of running version and not |
| 55 |
automaticly overide it without asking. It looks like python-exec is the |
| 56 |
controlling factor so I'll try CONFIG_PROTECTon that file and manually |
| 57 |
manage it via ansible. |
| 58 |
|
| 59 |
BillK |
Archives