Re: [gentoo-user] Python upgrade problem, maybe???

[Dale <rdalek1967@gmail.com>]

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

Eli Schwartz wrote:
> On 5/4/25 12:29 AM, Dale wrote:
>> So I can either leave it with it set to use both or do individual
>> packages settings, which can be quite a few packages? 
>>
>> My thinking is this.  Leave it with it set to both and only have two
>> lines in packages.use.  Then I can comment out those lines to see if
>> everything has caught up so I can just remove those lines, until the
>> next big upgrade.  Two lines with emerge/portage managing what is used
>> might be safer and more stable than me trying to force it one way or the
>> other given I might forget.  I don't mind having both python 3.12 and
>> 3.13 on here at the same time.  It should be a temporary thing. 
>>
>> I'd like to have a easy way to manage this but at the same time, make
>> sure I have a stable system.  KDE and some other stuff has enough quirks
>> already, adding a mixed up python won't likely help much.  LOL 
> Yes, that sounds quite okay. Personally, I do per-package settings, but,
> well... I'm a software developer who develops software written in
> python, so I have a biiiit more patience than most people for juggling
> lots of python packages for multiple versions. :) Don't be me. :)

I do per package when it is a small number of packages.  The biggest
thing, I don't want to forget about setting this in package.use and some
things getting stuck in a way that begins to cause trouble later on. 
Usually I put temporary things at the top of package.use.  That way when
I open it, it helps remind me that I may need to remove or otherwise
adjust those settings.  Some settings have specific USE flags that may
never change so they go further down the file.


>
>
>> Just so I'm clear on where my live OS stands, this is the current
>> package.use setting.
>>
>>
>> */* PYTHON_TARGETS: -* python3_12 python3_13
>> */* PYTHON_SINGLE_TARGET: -* python3_13
>>
>>
>> This is the output of my normal emerge update with the above setting. 
>>
>>
>> root@Gentoo-1 / # emerge -aukDN world
>>
>> These are the packages that would be merged, in order:
>>
>> Calculating dependencies... done!
>> Dependency resolution took 45.20 s (backtrack: 0/500).
>>
>>
>> Total: 0 packages, Size of downloads: 0 KiB
>>
>> !!! The following installed packages are masked:
>> - sys-kernel/gentoo-sources-6.14.0::gentoo (masked by: package.mask)
>> /etc/portage/package.mask/package.mask:
>> # =media-libs/opencv-4.10.0
>>
>> For more information, see the MASKED PACKAGES section in the emerge
>> man page or refer to the Gentoo Handbook.
>>
>>
>> Nothing to merge; quitting.
>>
>> root@Gentoo-1 / #
> Sounds perfect. :)
>
>
>
>> So at the moment, my main OS is happy with that setting, no skipping
>> anything.  I figure in a week or so, most other packages will catch up,
>> due to the bug reports being filed, and then when the number of packages
>> get small, I can then do individual packages in package.use or unmerge
>> those packages if I don't need them.  I figure --depclean will take care
>> of python when it is all clear. 
> Hopefully yes. There's no great guarantee since there's usually a very
> small tail end of packages which are very challenging to upgrade and
> take absolutely ages to migrate to newer python due to upstream
> developers not yet supporting it, and it needing "work", but whether
> those packages are important to any given person is very
> situation-dependent.
>
> Hopefully kicad is your only issue. That one is tracked by
> https://bugs.gentoo.org/952659 and using ACCEPT_KEYWORDS="**" will
> install kicad-9999.ebuild, which does support python 3.13.
>
> (Not saying you want to install totally unstable packages. But on the
> other hand, this does imply it's close to being ready. So... good news,
> right?)
>
>
> -- Eli Schwartz


This all sounds good.  Hopefully at some point soon most or all of this
will sort itself out.  If I end up with just a few packages, I can add
them to package.use on a per package basis and remove the other lines. 
I just know that a global setting like that over time will cause
problems, such as when python 3.14 comes along as a default and 3.12
goes away and is cleaned out. 

Anyway, sounds like I'm good to go for now.  I'll logout and back in,
update my backups and such as I do each weekend. 

Keep up the good work and thanks for helping me make sure I'm as stable
as I can get for now.  I won't be nervous about logging out.  ;-) 

Thanks much.

Dale

:-)  :-) 

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