Migrated to Python 12, now rebuilds skipped due to dep con

figueroa

Last night I followed the steps for safer migration from Python 3.11 to 3.12. However, I'm left with many: "updates/rebuilds have been skipped due to a dependency conflict." Even after completing this morning's updates, I'm left with:

pjp · Administrator Joined: 16 Apr 2002 Posts: 20485

It looks to me as if you need more per package "target" settings.

Looking at the first part of the output for pygobject indicates the new version with 3.12 conflicts with packages that require 3.11. I think adding avahi with 3.11 to your package.use settings will make that one go away. I presume there are others in the list too.
_________________
Quis separabit? Quo animo?

figueroa · Posted: Tue Jun 04, 2024 4:22 am Post subject:

This was way more difficult than I'd experienced with other Python version migrations. It turns out that the problem was not net-dns/avahi, or many of the other packages I tried by adding them to /etc/portage/package.use. In fact, in the end, by trial and error, I had added 25 packages to package.use with USE python_targets_python3_11 or python_single_target_python3_11, but ended up with only 9.

You can see my trial and error in the following selection from /etc/portage/package.use and the 16 packages that were added then commented out:

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2428

figueroa · Posted: Tue Jun 04, 2024 6:13 am Post subject:

I followed the steps for safer migration from the news item (three steps).
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi

pjp · Administrator Joined: 16 Apr 2002 Posts: 20485

Sometimes I can make sense of the output, other times its much more difficult. Your first one _seemed_ straight forward.

Out of curiosity, I copied the info to a file to try and parse. I haven't gotten very far yet, but I'll see what happens.

So far *knock on wood* my laptop doesn't look like it will be a problem. 80 packages to rebuild. My other non-gui system had 76. I was expecting the laptop to be more difficult.

Unless I have major problems with stuff failing, this may turn out to be the easiest migration I've ever had. Both systems may potentially "just work" without any finagling.

Although my upgrade to Profile 23 stopped hard at the first attempt to compile, so there's that. But I'll take the easy 3.12 upgrade if that happens.
_________________
Quis separabit? Quo animo?

mhex · Posted: Tue Jun 04, 2024 6:32 am Post subject:

Maybe this helps

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2428

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2428

mhex · Posted: Tue Jun 04, 2024 12:12 pm Post subject:

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2428

mhex · Posted: Tue Jun 04, 2024 1:05 pm Post subject:

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2428

mhex · Posted: Tue Jun 04, 2024 1:34 pm Post subject:

yayo · Tux's lil' helper Joined: 19 May 2014 Posts: 100

I have exactly the same problem of figueroa.

I usually do system update every 1-2 days. I noticed the problem 2 days ago and waited for it to be fixed (I supposed it was just a matter of some late packages to be moved on 3.12 support, as usual), but it got worse.
Now I have an output so long that goes out of the terminal buffer.

And I did absolutely nothing "unrequired" for it to happens. No python flags written anywhere. And I touched nothing.

Why do I have this feeling that anytime a python update is required, I'm told to do nothing (unless I want forcing or deferring it, and I don't want to) because the system "will do it on it's own", but anytime I'm then forced to do a lot of work to fix a mess?

Wouldn't it be better to move all the packages depending on python to support the new version BEFORE planning a version update? : /

Even trying the so called "safe procedure" (that is not "portage will do it", but "you must fix it"!), at the present time I couldn't reach the 3rd step (both python_targets and python_single_target set to just 3.12), because some packages (like for example cdemu and gcdemu) still depend on 3.11.

How is this supposed to be fixed now?

figueroa · Posted: Tue Jun 04, 2024 2:48 pm Post subject:

By the way, towards the end of migrating, I depcleaned elogviewer. Not only I don't use it (read elog files in terminal shell), it had a long chain of ugly python version and other dependencies. That was a big step in my trials and errors.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi

pjp · Administrator Joined: 16 Apr 2002 Posts: 20485

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2428

rab0171610 · Guru Joined: 24 Dec 2022 Posts: 423

Edit after looking at my command history:
I had similar output to others, packages wanting to retain Python 3_11, even thought I knew the ebuilds now support 3.12.

My issues were because I accidentally left off --changed-use from the update command due to a typo:

figueroa · Posted: Tue Jun 04, 2024 5:27 pm Post subject:

rab0171610 · Guru Joined: 24 Dec 2022 Posts: 423

Thank you for pointing that out, It was a typo! My intentions were good. The pitfalls of dyslexia.

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2428

Princess Nell · l33t Joined: 15 Apr 2005 Posts: 926

I finally came out of the mess the other end, without any python_single_target-* band aids. Lost a few ebuilds on the way and probably don't need them anyway.
This is the last problem: