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.
signature.asc
Description: This is a digitally signed message part.
