From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fragile python update is wedged.
Date: Sun, 11 May 2025 09:52:30 -0500 [thread overview]
Message-ID: <3695511e-29f7-f38c-9413-0431652c78a0@gmail.com> (raw)
In-Reply-To: <aCClgYrrDAgRY_j3@ca.inter.net>
Philip Webb wrote:
> I noticed others reporting Python update problems & didn't follow it,
> but in my regular Sat update today encountered a big mess.
> 'setuptools-scm' offered 13 screens of conflicts,
> which were reduced to 10 by ' --backtrack=60 '.
> I tried a 'quickpkg' + 'emerge -k', but was refused as the ebuild was missing.
> Finally, I did a few 'emerge -C' brute-forces on some listed pkgs,
> which allowed a straightforward 'emerge' of 18 Python pkgs.
> The underlying problem seemed to be a jump to Python 3.13 .
>
> That solution is risky, but it has always worked before + today.
> I don't understand why Python can't do it automatically,
> but am tired of complaining & remain a strong fan of Gentoo.
>
> PS I've never done 'emerge World' without '-pv' since 2003 :
> I always pick/choose which pkgs to update a few at a time.
>
I think a lot of it depends on what packages we have installed. For me,
it was Kicad and a couple others, plus all their friends. It became a
lengthy list tho. You may have a completely different set of packages
installed but with the same problem as me, doesn't support 3.13 yet.
I think Eli said that as long as a version of python is installed for
emerge, one can fix most problems if we remove something by mistake. We
just need to make sure emerge stays happy.
I started using Gentoo in about 2003 as well. Over the years, I've put
some options that are always wanted in make.conf and then I put others,
depending on what I'm doing, on the command line. I have backtrack set
to 500. It rarely goes higher than 4 or 5 tho. Still, it has it if it
needs it. I have build deps turned on as well. Over the years tho,
I've found settings and methods that result in a very stable system. I
always sync, do a emerge -auDN world and then look at any USE flag
changes, or any other changes, before letting it go. Sometimes a new
USE flag pops up that I know I need or don't need. I adjust and then
rerun emerge -auDN world. I've found that letting emerge figure it out
is usually the best and most stable. It may result in a little more
compiling but it's rare that anything crashes on my system. That's
important to me.
We all have our own ways tho. If it works, why do it differently???
Oh, tried to do the last step on my main rig, emerge spit out a nice
loud and hard to miss, NO!!!. There's still a lot of packages not ready
for python 3.13 yet. Maybe next week. If I don't forget. Again.
Dale
:-) :-)
next prev parent reply other threads:[~2025-05-11 14:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 17:07 [gentoo-user] Fragile python update is wedged Alan Mackenzie
2025-05-02 17:22 ` Pramod V U
2025-05-02 17:47 ` [gentoo-user] Fragile rust update is wedged. (Was: Fragile python update is wedged.) Eli Schwartz
2025-05-02 19:07 ` [gentoo-user] Fragile rust update is wedged Alan Mackenzie
2025-05-02 20:07 ` Eli Schwartz
2025-05-02 21:15 ` [gentoo-user] Fragile python update is wedged [Was: Fragile rust update is wedged] Alan Mackenzie
2025-05-02 21:35 ` Wol
2025-05-02 21:44 ` Jay Faulkner
2025-05-02 22:17 ` Alan Mackenzie
2025-05-02 22:21 ` Jay Faulkner
2025-05-02 21:56 ` Eli Schwartz
2025-05-04 16:41 ` Alan Mackenzie
2025-05-04 17:01 ` Eli Schwartz
2025-05-03 3:14 ` [gentoo-user] " Grant Edwards
2025-05-03 4:07 ` [gentoo-user] Fragile rust update is wedged Nate Eldredge
2025-05-11 11:54 ` [gentoo-user] Fragile python " Wol
2025-05-11 12:42 ` Dale
2025-05-11 13:26 ` Philip Webb
2025-05-11 14:52 ` Dale [this message]
2025-05-17 7:17 ` Dale
2025-05-18 12:06 ` Michael
2025-05-18 14:26 ` Dale
2025-05-11 15:14 ` Eli Schwartz
2025-05-11 12:43 ` Frank Schletz
2025-05-11 13:37 ` Wol
2025-05-11 14:55 ` Dale
2025-05-11 15:04 ` Eli Schwartz
2025-05-11 17:40 ` Wol
2025-05-11 18:06 ` Michael
2025-05-11 18:08 ` Eli Schwartz
2025-05-11 19:10 ` Wol
2025-05-11 19:47 ` Eli Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3695511e-29f7-f38c-9413-0431652c78a0@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox