public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fragile python update is wedged.
Date: Sun, 18 May 2025 09:26:03 -0500	[thread overview]
Message-ID: <d09eba7b-e191-b609-317f-8f2ea308357e@gmail.com> (raw)
In-Reply-To: <3892846.kQq0lBPeGt@rogueboard>

[-- Attachment #1: Type: text/plain, Size: 4171 bytes --]

Michael wrote:
> On Saturday, 17 May 2025 08:17:34 British Summer Time Dale wrote:
>> Dale wrote:
>>> <<<< SNIP >>>>
>>> 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
>>>
>>> :-)  :-) 
>> Little update.  I just went to the third step in the python update news
>> item, safer method.  The only package I have left at 3.12 is
>> media-libs/avidemux-plugins.  It is a lonely package for python 3.12. 
>> Even Kicad is up to 3.13 now. 
>>
>> So, for those still stuck at step 2, may want to give step three a try
>> and see how close you are to being able to fully switch. 
>>
>> Dale
>>
>> :-)  :-) 
> First, a big thank you to devs and maintainers for making this python upgrade 
> so seamless and for me at least, painless.  Four PCs were updated without any 
> intervention by me whatsoever.
>
> The fifth upgrade involved an old laptop which had not seen an update for more 
> than 9 months.  I thought this would present some problems and require my 
> manual intervention, if only because portage and its contents have moved on 
> some distance over this time.
>
> Emerge added a load of python target related USE flags in zz-autounmask, which 
> I accepted.  Then I added '--backtrack=99' before I let it rip.  It took 
> overnight, emerged close to 900 packages and arrived at a fully working system 
> and desktop.  After a --depclean session I removed the zz-autounmask USE 
> flags, whereby a number of python related packages were re-emerged and 
> everything is working as expected.
>
> Finally, another laptop with a very similar collection of packages had an 
> almost seamless upgrade ... except that I stopped it some way through.  When I 
> restarted emerge a day later there were problems.  Packages were asking to be 
> emerged in a different order.  Rust had a circular hissy fit as Alan reported 
> initially and qt-base and friends were blocking because they didn't like some 
> of the recently emerged dependencies - or something like that.  Anyway, I 
> emerged rust-bin for now, unmerged qt-base and left the emerge well alone to 
> proceeded with further issues.
>
> Given this anecdotal experience, I made a mental note for next time to leave 
> systems complete a major upgrade once I commit to it, rather than interrupt 
> emerge from doing its thing.  


I agree.  The devs did a good job with the safer method.  Some of us
just had some packages that were a little behind, for me, Kicad and a
couple other packages that likely not many people use compared to
something like Chrome, Firefox or LOo which was ready.  Still, the devs
can't help that some packages lag behind.  The important part, they gave
use a upgrade method that works even if it requires us to either delay
some packages or just delay the final step.  Once my odd packages caught
up, I was left with one package that still needs the old python.  Thing
is, my system remained stable during the whole thing. 

I have to say, emerge has come a LONG ways since 2003 when I started
using Gentoo.  Someone coming up with the idea of being able to inform
us of changes, with the news items, is also a HUGE help.  We get a
notice that something important is changing and might require certain
steps.  We not hitting these major changes blindly anymore.  I remember
the old days when I would sync and then emerge would puke all over my
keyboard with something most of us couldn't make sense of.  Today, we
sync, get a alert of serious changes that require attention and then
tells us how to navigate the change, usually with more than one way to
do it. 

Yea, Gentoo has come a long ways.  The devs do some awesome work.  Wish
I could win the lottery.  LOL  :-D 

Dale

:-)  :-) 

P. S.  I'm still trying to figure out how to redo my drive setup.  I got
one large LVM that I want to transfer to a encrypted file system.  I'm
trying to figure out how to put the new drives in or move the old drives
to the NAS box for the transfer.  Either way requires a lot of work.  :/ 

[-- Attachment #2: Type: text/html, Size: 5399 bytes --]

  reply	other threads:[~2025-05-18 14:27 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
2025-05-17  7:17         ` Dale
2025-05-18 12:06           ` Michael
2025-05-18 14:26             ` Dale [this message]
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=d09eba7b-e191-b609-317f-8f2ea308357e@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