On 5/11/25 1:40 PM, Wol wrote: > On 11/05/2025 16:04, Eli Schwartz wrote: >>> I followed the instructions at the end - depclean, -1uVD, and it just >>> fails completely with "requires just one of 3_11 or 3_12". Including >>> important stuff like most of kde, systemd-dbus, and so on. >>> >>> I thought I'd try increasing backtrack like I usually do - to 100 - but >>> that made no difference. >> >> >> You must have done something more than just emerge --sync followed by >> emerge -uDU @world. >> > What else would I have done? I ran the sync, read the news, and followed > the instructions at the bottom. The emerge failed with loads of errors. > > The only thing else I did was delete avidemux (which I think was broken > anyway), because that was an obvious problem that wouldn't cause > problems if I deleted it.
You didn't post full output so it's difficult to say for sure. But,
"requires just one of" sounds like this:
$ PYTHON_SINGLE_TARGET='python3_13 python3_12' emerge -1a glib-utils
These are the packages that would be merged, in order:
Calculating dependencies -
!!! Problem resolving dependencies for dev-util/glib-utils
... done!
Dependency resolution took 1.01 s (backtrack: 0/20).
!!! The ebuild selected to satisfy "glib-utils" has unmet requirements.
- dev-util/glib-utils-2.82.5::gentoo USE="" ABI_X86="(64)"
PYTHON_SINGLE_TARGET="python3_12 python3_13 -python3_11"
The following REQUIRED_USE flag constraints are unsatisfied:
exactly-one-of ( python_single_target_python3_11
python_single_target_python3_12 python_single_target_python3_13 )
The "exactly-one-of" means you have set two USE flags for the package
and can only choose one at the same time.
The ::gentoo repository of ebuilds does not set both at the same time.
In order to get both, you must have one somewhere outside of the gentoo
repository...
>> OR you must have had old package.use entries setting duplicate USE flags
>> already.
... which is why I suggested this.
> And I can see what happened now. It doesn't help that I didn't have my
> glasses, but the news item says:
>
> "At this point, you have a few configuration options to choose from:"
>
> I jumped straight to option 4, so I didn't read option 1 - why should I?
> Especially if I'm having difficulty reading.
Sorry? What? This wasn't part of option 1, this was from the paragraph
before "at this point you have a few configuration options".
You jumped straight over the paragraph before the one telling you to
make a choice.
>> And why on earth would you assume they are comments?
>
> Because the news item, as written, led me up the garden path!
>
> "Safer upgrade procedure
> =======================
> A safer approach is to add Python 3.13 support to your system first,
> and only then remove Python 3.12. However, note that this involves two
> rebuilds of all the affected packages, so it will take noticeably
> longer.
>
> First, enable both Python 3.12 and Python 3.13, and then run the upgrade
> commands:
>
> */* PYTHON_TARGETS: -* python3_12 python3_13
> */* PYTHON_SINGLE_TARGET: -* python3_12"
>
> It says "run the upgrade commands - COLON". As I understand English,
> that says that what follows is a list of COMMANDS. And "*/*" looks like
> a weird comment marker. Why would I assume it's a declaration snippet?
First, enable both python 3.12 an python 3.13:
<package.use stuff>
and then run the upgrade commands.
It is not lacking the quality of being idiomatic, to write the colon
after the full sentence rather than splitting the sentence in two. I see
both quite often. But regardless,
it certainly isn't a weird comment marker given:
- it looks EXACTLY like package.use syntax (because it is)
- there are no COMMANDS. No "emerge" either. Did you try to copy/paste
it into a bash shell?
>> You don't need to know python and aren't expected to either. The news
>> item describes the fact that:
>
> That's clear now. But the combination of not reading a paragraph that
> clearly appeared to be irrelevant,
This is not what happened, so the news item is not responsible for your
failure to read the paragraph *before* the one you felt was irrelevant.
Sorry.
--
Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
