On 2024-06-05, Arve Barsnes <arve.bars...@gmail.com> wrote:
> On Wed, 5 Jun 2024 at 20:05, Grant Edwards <grant.b.edwa...@gmail.com> wrote:
>> What I found misleading (and tripped over) was the implication that
>> the three step migration process outlined in the news item had a
>> reasonable likelyhood of working for a large percentage of users.
>>
>> If the new items had warned that anybody using one of <hundreds?>
>> packages that won't work with 3.12 are going to have to stop after
>> step 1 until those packages have been brought "up to date" so that
>> they can build with 3.12. Had I known that, I wouldn't have tried the
>> three step migration and would have simply postponed the upgrade.
>
> Maybe I've been using gentoo too long, but I never assumed these
> three steps were a 'single upgrade' recipe, I assumed each step were
> to be undertaken as the portage tree allowed.
>
> Reading the news item again, I see that no such thing is implied,
> but perhaps it should have been? Otherwise, what is the point of
> these steps as opposed to the automatic upgrade portage initially
> attempts?
I wondered about that too. But, I decided that whoever wrote the news
item probably knew what they were talking about, and chose the "Safer
upgrade procedure". As you said, there's no mention of waiting between
steps for various packages to catch up:
First, enable both Python 3.11 and Python 3.12, and then run the upgrade
commands:
*/* PYTHON_TARGETS: -* python3_11 python3_12
*/* PYTHON_SINGLE_TARGET: -* python3_11
Then switch PYTHON_SINGLE_TARGET and run the second batch of upgrades:
*/* PYTHON_TARGETS: -* python3_11 python3_12
*/* PYTHON_SINGLE_TARGET: -* python3_12
Finally, switch to the final version and upgrade:
*/* PYTHON_TARGETS: -* python3_12
*/* PYTHON_SINGLE_TARGET: -* python3_12
--
Grant
