nightmare @world update attempt

[wrc1944]

I'm on profile 17.1,and python-3.11. Should I update python to 3.12 first before dealing with the profile update?? Any other advice greatly appreciated!

[asturm]

Please define "nightmare"?

[wrc1944]

I was syncing for the python-3-12 auto update on june 1, and got the posted output below. unsure of the prudent steps to take.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.40-r5, gcc-14
kernel-6.11.3 USE=experimental python3_12.7-final-0

[NeddySeagoon]

wrc1944,

Do the @world update first. The output you posted shows it would have run.
Then, without --syncing, do the profile migration.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[asturm]

Just go on with the update as it presents itself to you, py 3.12 obviously ain't yet there.

Only make a profile change without any pending updates.

[wrc1944]

Thanks Neddy & asturm

So, run the presented @world, and if 3.12 is still not there, do the python update ala eselect news instruction, then the profile update, correct?
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.40-r5, gcc-14
kernel-6.11.3 USE=experimental python3_12.7-final-0

[NeddySeagoon]

wrc1944,

If the python update is not there, you don't need it yet.

Do @world then the profile.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[asturm]

[wrc1944]

Hmmmmmmmm.Eeselect news says 3.12 becomes the gentoo default python on june 1 and to remove all python reference in .make.confi and package.use for the automatic update.

I'm running ~amd64 over 20 years now, so I figured I needed to move to 3.12. Is this Wrong? How can I udate my profile if python is not updated to the current default?
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.40-r5, gcc-14
kernel-6.11.3 USE=experimental python3_12.7-final-0

[asturm]

Why do you think that is in any way related?

For the profile update, just make sure that your system is consistent after your latest sync.

[flysideways]

[asturm]

You complete the updates *of your current sync*. Did I say anything else?

Is the python switch part of your current sync? Very much apparently no.

[Hu]

The configuration most likely to be tested by the maintainers if the one where, immediately prior to the unusual update (such as a profile change), the regular update process (emerge --update --deep --changed-use @world) finds nothing to do. Thus, getting your system to the state of no pending regular updates is a way to most closely track what the maintainers tested, and therefore the way most likely to work. If you are feeling adventurous, you may be able to combine multiple unrelated updates. However, this path is less tested, and may require more work on your part to resolve any problems.

[flysideways]

The news article for the profile change says the following

[wrc1944]

OK.

All 59 @world packages emerged fine Gurss I'll depcleand then see what an emerge -1vUD @world -pv reports.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.40-r5, gcc-14
kernel-6.11.3 USE=experimental python3_12.7-final-0

[wrc1944]

gentoo-audio ~ # emerge -1vUD @world -pv

!!! Your current profile is deprecated and not supported anymore.
!!! Use eselect profile to update your profile.
!!! Please upgrade to the following profile if possible:

default/linux/amd64/23.0/split-usr/desktop/plasma

To upgrade do the following steps:

A profile upgrade to version 23.0 is available for your architecture.
The new 23.0 profiles enable some toolchain hardening features and
performance enhancements by default, and standardize settings.
You can find the list of changes on the wiki tracking page [1].

Upgrade instructions

Note 1: If you have manually changed your CHOST to a value different from
what the stages and profiles set, you may have to do that in the future too.
In that case you should know what you are doing, hopefully; please read the
instructions with a critical eye then.

Note 2: In case you are already familiar with binary packages, you should be
able to add "--getbinpkg" to the emerge calls to speed things up.
The use of binary packages is completely optional though, and also not
as much tested as the source-based upgrade path yet.

1. Ensure your system backups are up to date. Please also update
your system fully and depclean before proceeding.
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.

2. If you are still using one of the long-deprecated amd64 17.0 profiles
(other than x32 or musl), then first complete the migration to the
corresponding 17.1 profile. Instructions can be found at [3].

3. If you are currently using systemd in a split-usr configuration, then first
complete the migration to the corresponding merged-usr profile of the
same profile version. Details on how to do this can be found in the news
item [4].
If you are currently using openrc, migrate to 23.0 first, keeping your disk
layout. If you want to move from split-usr to merged-usr, do that afterwards.

4. Run "emerge --info" and note down the value of the CHOST variable.

5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
remove it. Also delete all lines defining CHOST_... variables.

6. Select the 23.0 profile corresponding to your current profile, either using
"eselect profile" or by manually setting the profile symlink.
Note that old profiles are by default split-usr and the 23.0 profiles by
default merged-usr. Do NOT change directory scheme now, since this will
mess up your system!
Instead, make sure that the new profile has the same property: for example,
OLD default/linux/amd64/17.1
==> NEW default/linux/amd64/23.0/split-usr
(added "split-usr")
OLD default/linux/amd64/17.1/systemd/merged-usr
==> NEW default/linux/amd64/23.0/systemd
(removed "merged-usr")
A detailed table of the upgrade paths can be found at [5]. Please consult it.
In some cases (hppa, x86) the table will tell you to pick between two choices.
What you need should be obvious from your *old* CHOST value (from step 4).

7. Delete the contents of your binary package cache at ${PKGDIR}
rm -r /var/cache/binpkgs/*

8. In the file or directory /etc/portage/binrepos.conf (if existing), update
the URI in all configuration such that they point to 23.0 profile binhost
directories. The exact paths can be found in the table at [5], too.

9. Rebuild or reinstall from binary (if available) the following packages in
this order, with the same version as already active:
emerge --ask --oneshot sys-devel/binutils
(you may have to run binutils-config and re-select your binutils now)
emerge --ask --oneshot sys-devel/gcc
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
that; instead, abort and try again with --nodeps added to the command line.)
(you may have to run gcc-config and re-select your gcc now)
and the C library, i.e. for glibc-based systems
emerge --ask --oneshot sys-libs/glibc
or for musl-based systems
emerge --ask --oneshot sys-libs/musl

10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.

If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,

11. Recheck with binutils-config and gcc-config that valid installed versions
of binutils and gcc are selected.

12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
refer to the *OLD* CHOST value, and remove them.
Examples how to do this can be found in the similar procedure at [6].

13. Run env-update && source /etc/profile

14. Re-emerge libtool:
emerge --ask --oneshot libtool

15. Just for safety, delete the contents of your binary package cache at
${PKGDIR} again:
rm -r /var/cache/binpkgs/*

16. Rebuild world:
emerge --ask --emptytree @world

[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work



These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 68.46 s (backtrack: 1/20).


Total: 0 packages, Size of downloads: 0 KiB

WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:

x11-misc/sddm:0

(x11-misc/sddm-0.21.0_p20240302:0/0::gentoo, ebuild scheduled for merge) USE="X elogind -systemd -test" ABI_X86="(64)" conflicts with
<x11-misc/sddm-0.21.0_p20240302[elogind] required by (kde-plasma/plasma-meta-5.27.11-r1:5/5::gentoo, installed) USE="bluetooth browser-integration crash-handler crypt cups desktop-portal display-manager elogind gtk handbook kwallet legacy-systray networkmanager pulseaudio sddm smart wallpapers -accessibility -colord -discover (-firewall) -flatpak -grub -plymouth -sdk -systemd -thunderbolt" ABI_X86="(64)"
^ ^^^^^^^^^^^^^^^^


* IMPORTANT: 4 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.

gentoo-audio ~ #
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.40-r5, gcc-14
kernel-6.11.3 USE=experimental python3_12.7-final-0

[lekto]

I really don't know why two important changes were scheduled for the same week (profile deprecation and changing the Python default). I have a machine where I didn't update the profile because there were some packages that I couldn't update, and the first point in the news said to have updated the system before changing the profile. When I saw a message about the deprecation of the profile, I decided to wait, fix everything, and update the profile during the weekend. While fixing stuff, without notice, I synced the tree, and portage wanted to change Python USE flags in some packages for some reason, but I couldn't because I have packages that don't have Python 3.12 single target. Because of this, I unexpectedly got hundreds of lines of errors instead of tens, and it took me too long to realize that this is not my fault. I set the Python target in make.conf and finished updating the system. After that, I decided to update the Python before the profile, and it was successful. After I finished with the Python, I started to update the profile. Right now, I'm doing --emptytree, and nothing has broken so far. Meanwhile, QT wanted to be updated, which is always fun when some parts of it doesn't want to be updated because of long errors that I can't grasp.


Packages that don't have Python 3.12 single target in my case are: catalyst, kicad, guake, apparmor-utils, libapparmor.

[asturm]

You are the master of your system. I haven't done the profile switch myself yet as I need to work on more important things like KDE Plasma/Gear/Frameworks packaging, which is time consuming, and time is very limited. No one is forcing my (or your) hand. The python-3.12 switch was more important as I had to make sure all my packages supported it if possible, so I made that switch much earlier than scheduled in the news. Incidentally, your mentioned Qt5(?) update was part of that.

[lekto]