midnight coral
I'm trying to update my system because I was away from home for a while, but I came across an odd issue (claims a slot conflict) that I don't quite understand:
https://bpa.st/raw/VXBA
It complains about some Qt5 stuff, mostly, and I'm not really clear on what I'm supposed to be doing to keep it happy so I can update.
(To clarify, I've been using Plasma6 for a while so I have no idea if this is related)
clever cave
!!! The ebuild selected to satisfy "dev-python/wxpython" has unmet requirements.
- dev-python/wxpython-4.2.1::gentoo USE="-debug -test -webkit" ABI_X86="(64)" PYTHON_TARGETS="-python3_10 -python3_11"
The following REQUIRED_USE flag constraints are unsatisfied:
any-of ( python_targets_python3_10 python_targets_python3_11 )``` Seems to be the crust of it. What is your PYTHON_TARGETS set to? It's neither python3_1.0 nor python3_11. python3_11 became the dafult last monthEmerge info says it's 3_12 for some reason
clever cave
oh. You're right. python 3.12 became the default on 2024-06-01. uh. Guess this package has not been updated for it yet
Hm. It should be though. Update portage database (emerge --sync)
midnight coral
Just synced again; it still thinks it doesn't have a 3_12
clever cave
Unless it's the unstable package that supports 3_12 only
Yeah that is the case. You'll need to either accept testing version of wxpython or enable python3_11 for wxpython until it is updated
midnight coral
Ah, okay
waxen lark
Unless it's the unstable package that supports 3_12 only
"testing"
midnight coral
I'm getting a lot of autounmask prompts for python3_11 now...
clever cave
I'm getting a lot of autounmask prompts for python3_11 now...
Yes, all dependencies will need python3_11 as well
midnight coral
To clarify, I set wxpythong for testing (for 3_12), but other packages are causing this chain of 3_11 prompts
clever cave
Oh. Do you have any references to python3_11 in package.use?
midnight coral
Just this:
/etc/portage/package.use/zz-autounmask:1265:>=dev-python/setuptools-70.0.0 python_targets_python3_11
# required by dev-python/fs-2.4.16::gentoo
# required by dev-python/fonttools-4.51.0::gentoo
# required by dev-python/notofonttools-0.2.17-r1::guru
# required by media-fonts/twemoji-14.0.2::guru
# required by @selected
# required by @world (argument)
>=dev-python/setuptools-70.0.0 python_targets_python3_11
It might be a good idea at this point to drop them all and run through the py312 migration. 🙂
waxen lark
That will only make it worse.
Especially enabling a python that's been removed for most packages
midnight coral
It might be a good idea at this point to drop them all and run through the py312...
It's going to take a while to do the migration; I'm about to start it but I've been gone for about a month, so there's a lot that's pending
I'll come back to check in
midnight coral
@waxen lark https://bpa.st/raw/C2ZA
When doing the step where I set */* PYTHON_TARGETS: -* python3_12 and */* PYTHON_SINGLE_TARGET: -* python3_12 in the migration process, I seem to still get a flood of messages about dependency conflicts
midnight coral
(Following the 2024-05-09-python3-12 eselect news)
midnight coral
Not exactly sure how to proceed with the migration with so many python packages seeming to be upset about it
waxen lark
Hm. grep -rsin python /etc/portage
midnight coral
Hm. `grep -rsin python /etc/portage`
waxen lark
Hm. I wonder if something in an overlay is causing it.
I'll look over your portage logs at a machine soon.
waxen lark
I can't see anything immediately wrong
midnight coral
That's why I was confused too :/
waxen lark
if you have py311 in the python_targets it works though?
there has to be something that depends on it that we aren't seeing
midnight coral
if you have py311 in the python_targets it works though?
Yeah, portage doesn't have any complaint if I do that but the moment I change it to 3_12, to attempt finishing the migration, it gets upset.
It'll still let me do the transaction, but it'll say a bunch of packages have the dep conflict.
waxen lark
hm.
midnight coral
@waxen lark
Now it seems to want dev-python/fonttools to use python_targets_python3_11, specifically, instead of spitting a bunch of python dep conflicts?
I do, however, now have a flood of Qt messages instead
midnight coral
Ugh
waxen lark
But that should still be fine
I bet the font just needs it's python targets updated.
The qt slot conflict though...
I think it's fine
QT will shake out over a little bit
It's probably all plasma 6.1 😦
:)*
midnight coral
Ah, but the python dep conflicts come back if I add that python_targets_python3_11 to the autounmask it asks for:
https://bpa.st/raw/H3ZA
And the Qt ones dissappear
waxen lark
Because it aborts I guess
Honestly do you use the font?
Just unmerge it if you don't actively use it.
It'll eventually be updated
midnight coral
It's the font Discord uses for emojis, isn't it?
waxen lark
Dunno, I get that via web font magic
midnight coral
I do use it over on Matrix, though
waxen lark
required by dev-python/notofonttools-0.2.17-r1::guru
# required by media-fonts/twemoji-14.0.2::guru
# required by @selected
# required by @world (argument)
>=dev-python/fonttools-4.53.0 python_targets_python3_11
Ok. I do noto emoji for code point coverage but honestly to fix this
Update the ebuilds.
Shadow them in a local overlay if you need to
They probably just haven't been tested with python 3.12
midnight coral
Shadow them in a local overlay if you need to
I don't really know how to do that Lol
I've never had to do that before
waxen lark
it's a good day to learn
literally
eselect repository create <ebuild_repository_name>
midnight coral
Guess I should call it "override" or something?
waxen lark
then you can copy the ones from guru into your repository
'neko-san' for all portage cares 🙂
(mine is just
'kangie'
then you can just update they relevent python variable and see what happens.
midnight coral
Should I copy all the other files included with the ebuild(s) too?
waxen lark
copy the whole ebuild directory
note that it needs to be in category/package
(there might be patches (etc) in files
midnight coral
Should I change PYTHON_COMPAT=( python3_{10..11} ) to this PYTHON_COMPAT=( python3_{10..12} )? I'm assuming that's what it's supposed to be
midnight coral
I'm getting this (backtrack: 1/20) for some reason when attempting an update now but it's not vomiting dep conflicts anymore
I'm confused as to what could be causing that though
waxen lark
That seems fine?