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!

Code: Select all

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


Action: sync for repo: gentoo, returned code = 0



!!! 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 91.62 s (backtrack: 8/20).

[ebuild     U  ] sys-libs/glibc-2.39-r7:2.2::gentoo [2.39-r6:2.2::gentoo] USE="multiarch (multilib) ssp stack-realign (static-libs) -audit -caps -cet -compile-locales (-custom-cflags) -doc -gd -hash-sysv-compat -headers-only -multilib-bootstrap -nscd -perl -profile (-selinux) -suid -systemd -systemtap -test (-vanilla)" 103 KiB
[ebuild     U  ] dev-libs/simdjson-3.9.3:0/22::gentoo [3.9.2:0/22::gentoo] USE="all-impls -test -tools" 2,582 KiB
[ebuild     U  ] dev-lang/rust-bin-1.78.0:stable::gentoo [1.77.1:stable::gentoo] USE="(-big-endian) -clippy -doc (-prefix) -profiler -rust-analyzer -rust-src -rustfmt -verify-sig" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" 160,118 KiB
[ebuild     U  ] virtual/rust-1.78.0:0/llvm-18::gentoo [1.77.1:0/llvm-17::gentoo] USE="-profiler -rustfmt" ABI_X86="(64) -32 (-x32)" 0 KiB
[ebuild     U  ] media-libs/libvpx-1.14.1:0/9::gentoo [1.14.0:0/9::gentoo] USE="highbitdepth postproc threads -doc -static-libs -test" ABI_X86="(64) -32 (-x32)" 5,483 KiB
[ebuild     U  ] media-libs/libaom-3.9.0:0/3::gentoo [3.8.1:0/3::gentoo] USE="examples (-big-endian) -debug -doc -test" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="avx avx2 mmx sse sse2 sse3 sse4_1 sse4_2 ssse3" 5,390 KiB
[ebuild     U  ] dev-perl/HTTP-Message-6.460.0::gentoo [6.450.0::gentoo] USE="-test" PERL_FEATURES="(-debug) -ithreads -quadmath" 94 KiB
[ebuild     U  ] x11-misc/xdg-utils-1.2.1-r2::gentoo [1.2.1-r1::gentoo] USE="X dbus -doc -gnome" 0 KiB
[ebuild     U  ] dev-build/meson-1.4.1::gentoo [1.4.0-r1::gentoo] USE="(-test) -verify-sig" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12" 2,515 KiB
[ebuild     U  ] dev-libs/libevdev-1.13.2::gentoo [1.13.1-r1::gentoo] USE="-doc -test" ABI_X86="(64) -32 (-x32)" 450 KiB
[ebuild  NS    ] sys-kernel/gentoo-sources-6.9.3:6.9.3::gentoo [6.8.8:6.8.8::gentoo, 6.8.9:6.8.9::gentoo, 6.9.0:6.9.0::gentoo, 6.9.1:6.9.1::gentoo, 6.9.2:6.9.2::gentoo] USE="experimental -build -symlink" 165 KiB
[ebuild     U  ] dev-util/wayland-scanner-1.23.0::gentoo [1.22.0::gentoo] 233 KiB
[ebuild     U  ] dev-libs/wayland-1.23.0::gentoo [1.22.0::gentoo] USE="-doc -test" ABI_X86="(64) -32 (-x32)" 0 KiB
[blocks b      ] <dev-libs/wayland-1.23.0 ("<dev-libs/wayland-1.23.0" is soft blocking dev-util/wayland-scanner-1.23.0)
[ebuild  r  U  ] dev-qt/qtcore-5.15.14:5/5.15.14::gentoo [5.15.13:5/5.15.13::gentoo] USE="icu -debug -old-kernel -test" 50,026 KiB
[ebuild     U  ] dev-qt/qtdbus-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="-debug -test" 0 KiB
[blocks b      ] <dev-qt/qtdbus-5.15.14:5 ("<dev-qt/qtdbus-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtnetwork-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="ssl -debug -gssapi -libproxy -sctp -test" 0 KiB
[blocks b      ] <dev-qt/qtnetwork-5.15.14:5 ("<dev-qt/qtnetwork-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtxml-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="-debug -test" 0 KiB
[blocks b      ] <dev-qt/qtxml-5.15.14:5 ("<dev-qt/qtxml-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtconcurrent-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="-debug -test" 0 KiB
[blocks b      ] <dev-qt/qtconcurrent-5.15.14:5 ("<dev-qt/qtconcurrent-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qttest-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="-debug -test" 0 KiB
[blocks b      ] <dev-qt/qttest-5.15.14:5 ("<dev-qt/qttest-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtwaylandscanner-5.15.14:5::gentoo [5.15.13:5::gentoo] USE="-debug -test" 548 KiB
[ebuild     U  ] dev-qt/qtsql-5.15.14:5/5.15.14::gentoo [5.15.13:5/5.15.13::gentoo] USE="mysql sqlite -debug -freetds -oci8 -odbc -postgres -test" 0 KiB
[blocks b      ] <dev-qt/qtsql-5.15.14:5 ("<dev-qt/qtsql-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qdbus-5.15.14::gentoo [5.15.13::gentoo] USE="-debug -test" 8,686 KiB
[ebuild   R    ] dev-python/sphinxcontrib-jquery-4.1::gentoo  USE="-test" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12 -python3_13%" 0 KiB
[ebuild     U  ] dev-qt/qtgui-5.15.14:5/5.15.14::gentoo [5.15.13:5/5.15.13::gentoo] USE="X accessibility dbus egl jpeg libinput png udev vulkan wayland -debug -eglfs -evdev -gles2-only -ibus -linuxfb -test -tslib -tuio -vnc" 0 KiB
[blocks b      ] <dev-qt/qtgui-5.15.14:5 ("<dev-qt/qtgui-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtwayland-5.15.14:5/5.15.14::gentoo [5.15.13:5/5.15.13::gentoo] USE="vulkan -compositor -debug -test" 47 KiB
[blocks b      ] <dev-qt/qtwayland-5.15.14:5 ("<dev-qt/qtwayland-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtwidgets-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="X dbus gtk png -debug -gles2-only -test" 0 KiB
[blocks b      ] <dev-qt/qtwidgets-5.15.14:5 ("<dev-qt/qtwidgets-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtx11extras-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="-debug -test" 135 KiB
[blocks b      ] <dev-qt/qtx11extras-5.15.14:5 ("<dev-qt/qtx11extras-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild  rR    ] kde-plasma/kwayland-5.116.0:5/5.116::gentoo  USE="-debug -doc -test" 0 KiB
[ebuild     U  ] app-text/poppler-24.05.0:0/137::gentoo [24.04.0:0/136::gentoo] USE="boost cairo cxx introspection jpeg jpeg2k lcms nss png qt5 tiff utils -cjk -curl -debug -doc -gpgme -qt6 -test -verify-sig" 1,865 KiB
[ebuild     U  ] dev-qt/qtimageformats-5.15.14:5::gentoo [5.15.13:5::gentoo] USE="mng -debug -test" 1,897 KiB
[blocks b      ] <dev-qt/qtimageformats-5.15.14:5 ("<dev-qt/qtimageformats-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtdeclarative-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="jit vulkan widgets -debug -gles2-only -localstorage -test" 21,116 KiB
[blocks b      ] <dev-qt/qtdeclarative-5.15.14:5 ("<dev-qt/qtdeclarative-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild  rR    ] kde-frameworks/kguiaddons-5.116.0:5/5.116::gentoo  USE="X dbus wayland -debug -doc (-kf6compat) -test" 0 KiB
[ebuild     U  ] dev-qt/qtsvg-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="-debug -test" 1,840 KiB
[blocks b      ] <dev-qt/qtsvg-5.15.14:5 ("<dev-qt/qtsvg-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtprintsupport-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="cups -debug -gles2-only -test" 0 KiB
[blocks b      ] <dev-qt/qtprintsupport-5.15.14:5 ("<dev-qt/qtprintsupport-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild  rR    ] kde-frameworks/kidletime-5.116.0:5/5.116::gentoo  USE="X wayland -debug -doc -xscreensaver" 0 KiB
[ebuild     U  ] dev-qt/qtscript-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="jit scripttools -debug -test" 2,595 KiB
[blocks b      ] <dev-qt/qtscript-5.15.14:5 ("<dev-qt/qtscript-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] net-print/libcupsfilters-2.0.0-r5::gentoo [2.0.0-r4::gentoo] USE="dbus exif jpeg pdf png poppler postscript tiff -test" 0 KiB
[ebuild     U  ] dev-qt/linguist-tools-5.15.14:5::gentoo [5.15.13:5::gentoo] USE="qml -debug -test" 0 KiB
[ebuild     U  ] dev-qt/qtgraphicaleffects-5.15.14:5::gentoo [5.15.13:5::gentoo] USE="-debug -test" 13,706 KiB
[blocks b      ] <dev-qt/qtgraphicaleffects-5.15.14:5 ("<dev-qt/qtgraphicaleffects-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtquickcontrols-5.15.14:5::gentoo [5.15.13:5::gentoo] USE="widgets -debug -test" 5,835 KiB
[blocks b      ] <dev-qt/qtquickcontrols-5.15.14:5 ("<dev-qt/qtquickcontrols-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild  rR    ] kde-plasma/layer-shell-qt-5.27.11:5::gentoo  USE="-debug" 0 KiB
[ebuild     U  ] dev-qt/designer-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="declarative -debug -test" 0 KiB
[blocks b      ] <dev-qt/designer-5.15.14:5 ("<dev-qt/designer-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtxmlpatterns-5.15.14:5::gentoo [5.15.13:5::gentoo] USE="qml -debug -test" 5,063 KiB
[blocks b      ] <dev-qt/qtxmlpatterns-5.15.14:5 ("<dev-qt/qtxmlpatterns-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtwebchannel-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="qml -debug -test" 205 KiB
[blocks b      ] <dev-qt/qtwebchannel-5.15.14:5 ("<dev-qt/qtwebchannel-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtsensors-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="qml -debug -test" 2,004 KiB
[blocks b      ] <dev-qt/qtsensors-5.15.14:5 ("<dev-qt/qtsensors-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtcharts-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="qml -debug -test" 4,147 KiB
[blocks b      ] <dev-qt/qtcharts-5.15.14:5 ("<dev-qt/qtcharts-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qtpositioning-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="geoclue qml -debug -test" 6,396 KiB
[blocks b      ] <dev-qt/qtpositioning-5.15.14:5 ("<dev-qt/qtpositioning-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild     U  ] dev-qt/qttranslations-5.15.14:5::gentoo [5.15.13:5::gentoo] USE="-debug -test" 1,589 KiB
[ebuild     U  ] dev-qt/qtquickcontrols2-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="widgets -debug -test" 8,099 KiB
[blocks b      ] <dev-qt/qtquickcontrols2-5.15.14:5 ("<dev-qt/qtquickcontrols2-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild  rR    ] x11-libs/libfm-qt-1.4.0:0/7::gentoo  0 KiB
[ebuild  rR    ] kde-plasma/kwayland-integration-5.27.11:5::gentoo  USE="-debug" 0 KiB
[ebuild  rR    ] kde-frameworks/kxmlgui-5.116.0:5/5.116::gentoo  USE="-debug -designer -doc -test" 0 KiB
[ebuild     U  ] dev-qt/qtmultimedia-5.15.14:5/5.15::gentoo [5.15.13:5/5.15::gentoo] USE="alsa gstreamer pulseaudio qml widgets -debug -gles2-only -openal -test" 3,754 KiB
[blocks b      ] <dev-qt/qtmultimedia-5.15.14:5 ("<dev-qt/qtmultimedia-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild  rR    ] kde-apps/okular-23.08.5:5::gentoo  USE="crypt handbook image-backend pdf plucker postscript qml tiff -debug -djvu -epub -markdown -mobi -phonon -share -speech -test" 0 KiB
[ebuild     U  ] dev-qt/qtwebengine-5.15.14_p20240510:5/5.15::gentoo [5.15.13_p20240510:5/5.15::gentoo] USE="alsa jumbo-build pulseaudio screencast system-icu widgets -bindist -debug -designer -geolocation -kerberos -test" 21 KiB
[blocks b      ] <dev-qt/qtwebengine-5.15.14:5 ("<dev-qt/qtwebengine-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14)
[ebuild  rR    ] kde-apps/gwenview-23.08.5:5::gentoo  USE="X activities handbook mpris semantic-desktop -debug -fits -raw -share -test" 0 KiB
[ebuild  rR    ] kde-plasma/plasma-integration-5.27.11:5::gentoo  USE="-debug" 0 KiB
[ebuild  rR    ] kde-plasma/kwin-5.27.11-r1:5::gentoo  USE="handbook lock plasma screencast -accessibility -caps -debug -gles2-only -multimedia -test" 0 KiB
[ebuild     U  ] kde-plasma/plasma-workspace-5.27.11.1:5::gentoo [5.27.11:5::gentoo] USE="calendar fontconfig handbook (policykit) screencast semantic-desktop wallpaper-metadata -appstream -debug -geolocation -gps -telemetry -test" 19,034 KiB

Total: 59 packages (46 upgrades, 1 in new slot, 12 reinstalls), Size of downloads: 335,724 KiB
Conflict: 27 blocks (all satisfied)

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)"
    ^              ^^^^^^^^^^^^^^^^         


The following packages are causing rebuilds:

  (dev-qt/qtcore-5.15.14:5/5.15.14::gentoo, ebuild scheduled for merge) causes rebuilds for:
    (dev-qt/qtnetwork-5.15.14:5/5.15::gentoo, ebuild scheduled for merge)
    (dev-qt/qtconcurrent-5.15.14:5/5.15::gentoo, ebuild scheduled for merge)
    (dev-qt/qtwayland-5.15.14:5/5.15.14::gentoo, ebuild scheduled for merge)
    (dev-qt/qtxml-5.15.14:5/5.15::gentoo, ebuild scheduled for merge)
    (dev-qt/qtgui-5.15.14:5/5.15.14::gentoo, ebuild scheduled for merge)
    (dev-qt/qtprintsupport-5.15.14:5/5.15::gentoo, ebuild scheduled for merge)
    (dev-qt/linguist-tools-5.15.14:5/5::gentoo, ebuild scheduled for merge)
    (dev-qt/qttest-5.15.14:5/5.15::gentoo, ebuild scheduled for merge)
    (dev-qt/designer-5.15.14:5/5.15::gentoo, ebuild scheduled for merge)
    (dev-qt/qtwaylandscanner-5.15.14:5/5::gentoo, ebuild scheduled for merge)
    (dev-qt/qtdbus-5.15.14:5/5.15::gentoo, ebuild scheduled for merge)
    (dev-qt/qtwidgets-5.15.14:5/5.15::gentoo, ebuild scheduled for merge)
    (kde-apps/okular-23.08.5:5/5::gentoo, ebuild scheduled for merge)
    (kde-frameworks/kxmlgui-5.116.0:5/5.116::gentoo, ebuild scheduled for merge)
    (dev-qt/qtsql-5.15.14:5/5.15.14::gentoo, ebuild scheduled for merge)
  (dev-qt/qtgui-5.15.14:5/5.15.14::gentoo, ebuild scheduled for merge) causes rebuilds for:
    (kde-frameworks/kidletime-5.116.0:5/5.116::gentoo, ebuild scheduled for merge)
    (kde-frameworks/kguiaddons-5.116.0:5/5.116::gentoo, ebuild scheduled for merge)
    (kde-plasma/kwayland-integration-5.27.11:5/5::gentoo, ebuild scheduled for merge)
    (kde-plasma/kwin-5.27.11-r1:5/5::gentoo, ebuild scheduled for merge)
    (kde-apps/gwenview-23.08.5:5/5::gentoo, ebuild scheduled for merge)
    (kde-plasma/plasma-integration-5.27.11:5/5::gentoo, ebuild scheduled for merge)
    (x11-libs/libfm-qt-1.4.0:0/7::gentoo, ebuild scheduled for merge)
    (kde-plasma/kwayland-5.116.0:5/5.116::gentoo, ebuild scheduled for merge)
  (dev-qt/qtwayland-5.15.14:5/5.15.14::gentoo, ebuild scheduled for merge) causes rebuilds for:
    (kde-plasma/layer-shell-qt-5.27.11:5/5::gentoo, ebuild scheduled for merge)
    (kde-plasma/kwayland-integration-5.27.11:5/5::gentoo, ebuild scheduled for merge)
    (kde-plasma/kwayland-5.116.0:5/5.116::gentoo, ebuild scheduled for merge)

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

gentoo-audio ~ # 

[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.

[NeddySeagoon]

wrc1944,

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

[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?

[NeddySeagoon]

wrc1944,

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

Do @world then the profile.

[asturm]

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

Exactly. There is no reason at all to preempt the maintainers.

[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?

[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]

Code: Select all

2024-05-09-python3-12
  Title                     Python 3.12 to become the default on 2024-06-01
  Author                    Michał Górny <mgorny@gentoo.org>
  Posted                    2024-05-09
  Revision                  1

We are planning to switch the default Python target of Gentoo systems
on 2024-06-01, from Python 3.11 to Python 3.12.  If you have not changed
the values of PYTHON_TARGETS or PYTHON_SINGLE_TARGET, the change will
have immediate effect on your system and the package manager will try
to switch automatically on the next upgrade following the change.

I too have used Gentoo for 20 years. Somehow, during that time, I came to the understanding that, usually, before making changes to a system one is to sync and complete updates and then make the changes.

Not sure where to find that in writing.

Is that wrong? Or just, frustratingly, conditional?

[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

Code: Select all

1. ... Please also update
   your system fully and depclean before proceeding.  ...

and,

Code: Select all

2024-05-09-python3-12
  Title                     Python 3.12 to become the default on 2024-06-01 

Yet,

Why do you think that is in any way related?

Hu, thanks for your reply. I wanted to be sure what I was missing. I have multiple installs that I am only able to update on about a 4 to 6 week cycle. I don't run a sync unless I have the time for an update. In 4 weeks those updates can include 300 or more packages, many of which, the currently installed version is no longer in the tree.

So, I will leave remaining of the opinion that it is conditional.

[wrc1944]

OK.

All 59 @world packages emerged fine Gurss I'll depcleand then see what an emerge -1vUD @world -pv reports.

[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:To ... transition
[2] https://wiki.gentoo.org/wiki/Project:To ... e_timeline
[3] https://www.gentoo.org/support/news-ite ... table.html
[4] https://www.gentoo.org/support/news-ite ... merge.html
[5] https://wiki.gentoo.org/wiki/Project:To ... date_table
[6] https://wiki.gentoo.org/wiki/Changing_t ... hings_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 ~ #

[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]

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.

Understandable. I hoped the new Ryzen 9000 series would come out before the deprecation of 17.1 profiles, so I could install a fresh system on the new machine and not deal with that mess. I was thinking about asking how long the old profiles would be supported, but I didn't, and it took me by surprise.

Incidentally, your mentioned Qt5(?) update was part of that.

According to https://github.com/gentoo/gentoo/commit ... -qt/qtcore, QT 5.15.14 was stabilized during the weekend. Because I unknowingly synced the tree I thought I did something wrong and tried to revert my last changes in /etc/portage to their last goodish state, which didn't get rid of errors. I thought I changed the wrong thing and tried again and again until I realized what happened. It was not obvious to me what was going on because instead of QT wanting to update, it was complaining about blocks, and Portage wanted to uninstall QT and then install it updated. Also, this caused lots of errors in emerge output, and lots of packages wanted to be rebuilt after the update of QT.