diff options
Diffstat (limited to 'profiles')
503 files changed, 24579 insertions, 3075 deletions
diff --git a/profiles/Manifest.gz b/profiles/Manifest.gz Binary files differindex f6914c268c32..3fa01bd5cc08 100644 --- a/profiles/Manifest.gz +++ b/profiles/Manifest.gz diff --git a/profiles/arch.list b/profiles/arch.list index 7bb08e3b8787..51ee66667c4b 100644 --- a/profiles/arch.list +++ b/profiles/arch.list @@ -3,7 +3,6 @@ amd64 arm arm64 hppa -ia64 loong m68k mips diff --git a/profiles/arch/alpha/package.use.mask b/profiles/arch/alpha/package.use.mask index 8789d3aaa07c..a9a88e0bb322 100644 --- a/profiles/arch/alpha/package.use.mask +++ b/profiles/arch/alpha/package.use.mask @@ -1,6 +1,42 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James <sam@gentoo.org> (2024-08-23) +# dev-util/bpftool and/or sys-devel/bpf-toolchain not keyworded here +sys-apps/systemd bpf + +# Hans de Graaff <graaff@gentoo.org> (2024-08-16) +# Requires large parts of dev-ruby/rails to be keyworded +dev-ruby/minitest-hooks test + +# Matt Jolly <kangie@gentoo.org> (2024-08-14) +# QUIC dependencies are not keyworded +net-misc/curl http3 quic curl_quic_openssl curl_quic_ngtcp2 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-10) +# Needs dev-libs/openspecfun which is not yet keyworded +sci-visualization/gnuplot amos + +# Leonardo Hernández Hernández <leohdz172@proton.me> (2024-07-07) +# media-libs/quirc and media-sound/liblc3 are not keyworded here +media-video/ffmpeg quirc liblc3 + +# matoro <matoro_gentoo@matoro.tk> (2024-07-03) +# Requires dev-util/shelltestrunner +app-arch/mt-st test + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-07-04) +# kde-frameworks/kservice not keyworded here +x11-misc/xdg-utils plasma + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-07-03) +# dev-python/redis lacks keywords here +mail-filter/pyzor redis test + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-29) +# media-libs/libplacebo is not keyworded +media-video/ffmpeg libplacebo + # Michał Górny <mgorny@gentoo.org> (2024-05-08) # Requires sys-devel/{clang,llvm}:16. dev-lang/python jit @@ -51,6 +87,7 @@ app-alternatives/ninja samurai # indicate a passing test suite, you must check the logs. # https://buildd.debian.org/status/logs.php?pkg=weston&arch=alpha gui-libs/gtk wayland +dev-libs/libportal wayland # matoro <matoro_gentoo@matoro.tk> (2023-06-18) # sci-physics/bullet not keyworded here (#908240) @@ -209,7 +246,6 @@ sci-libs/umfpack cholmod media-libs/openal sndio media-video/ffmpeg sndio media-sound/moc sndio -media-sound/mpd sndio media-libs/libsdl2 sndio media-libs/libao sndio @@ -238,7 +274,7 @@ media-sound/fluidsynth lash # Arfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com> (2020-10-14) # app-i18n/fcitx:4 not keyworded. -media-libs/libsdl2 fcitx4 +media-libs/libsdl2 fcitx # Sergei Trofimovich <slyfox@gentoo.org> (2020-09-18) # media-libs/libilbc is not ported to alpha @@ -250,11 +286,10 @@ mail-filter/pyzor mysql # Matt Turner <mattst88@gentoo.org> (2020-08-11) # No drivers on this architecture support Vulkan -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa video_cards_zink vulkan vulkan-overlay zink # Sergei Trofimovich <slyfox@gentoo.org> (2020-07-18) # net-libs/webkit-gtk has no alpha keywords -app-editors/emacs xwidgets gnome-extra/evolution-data-server oauth-gtk3 oauth-gtk4 # needs gnome-extra/sushi, depends on net-libs/webkit-gtk gnome-base/nautilus previewer @@ -302,7 +337,6 @@ media-video/ffmpeg dav1d libaribb24 libtesseract # Andrey Utkin <andrey_utkin@gentoo.org> (2020-03-11) # USE=bpf depends on sys-devel/clang which is not keyworded on alpha. media-libs/libv4l bpf -media-tv/v4l-utils bpf # Patrick McLean <chutzpah@gentoo.org> (2020-02-15) # Mask until dev-libs/libfido2 is keyworded @@ -335,10 +369,6 @@ dev-db/percona-server cjk app-admin/sudo sssd sys-auth/pambase sssd -# Andreas Sturmlechner <asturm@gentoo.org> (2018-09-30) -# Optional dependency blocking security cleanup, bug #627316 -media-sound/mpd wildmidi - # Thomas Deutschmann <whissi@gentoo.org> (2018-06-06) # Needs sys-apps/fakechroot which isn't keyworded app-arch/rpm test diff --git a/profiles/arch/amd64/no-multilib/package.mask b/profiles/arch/amd64/no-multilib/package.mask index 45d113b969a2..5778ea9dddaf 100644 --- a/profiles/arch/amd64/no-multilib/package.mask +++ b/profiles/arch/amd64/no-multilib/package.mask @@ -5,10 +5,6 @@ # This code assumes 32-bit longs and must therefore be built as a 32-bit binary. sys-fs/atari-fdisk -# David Seifert <soap@gentoo.org> (2018-01-03) -# Requires 32-bit multilib compatibility -sys-block/megamgr - # James Le Cuirot <chewi@gentoo.org> (2016-08-13) # Steam requires amd64 multilib. These are steam-overlay packages. dev-util/adobe-air-runtime @@ -27,7 +23,6 @@ app-emulation/crossover-bin app-emulation/q4wine dev-embedded/libftd2xx dev-embedded/openocd -dev-util/android-ndk dev-util/android-sdk-update-manager dev-util/biew games-action/badland @@ -83,10 +78,8 @@ games-rpg/eschalon-book-1-demo games-rpg/wasteland2 games-server/etqw-ded games-strategy/darwinia -games-strategy/darwinia-demo games-strategy/dominions2 games-strategy/knights-demo -games-strategy/majesty-demo games-strategy/spaz media-sound/aucdtect media-video/binkplayer diff --git a/profiles/arch/amd64/package.use b/profiles/arch/amd64/package.use index 40a242b365d5..273406b0e81e 100644 --- a/profiles/arch/amd64/package.use +++ b/profiles/arch/amd64/package.use @@ -1,6 +1,12 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Michał Górny <mgorny@gentoo.org> (2024-09-04) +# Build with debugging support by default to facilitate dev-debug/dtrace +# and sys-apps/systemd[bpf]. +>=sys-kernel/gentoo-kernel-6.6.53 debug +>=sys-kernel/vanilla-kernel-6.6.53 debug + # James Le Cuirot <chewi@gentoo.org> (2022-06-25) # Realign the stack in the 32-bit build for compatibility with older binaries by # default. This is not the default on x86 because it has a performance cost. diff --git a/profiles/arch/amd64/package.use.force b/profiles/arch/amd64/package.use.force index 5c9f06cdb0c4..85659560a1e0 100644 --- a/profiles/arch/amd64/package.use.force +++ b/profiles/arch/amd64/package.use.force @@ -1,6 +1,11 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# James Le Cuirot <chewi@gentoo.org> (2024-07-02) +# Needed to build gcc. Force here rather than using BDEPEND to simplify +# cross-compile scenarios. +sys-devel/binutils cet + # Michał Górny <mgorny@gentoo.org> (2023-10-06) # Require ABIs matching MULTILIB_ABIS in gcc dependencies -- otherwise # sys-devel/gcc[multilib] (which is forced) will fail late in build. diff --git a/profiles/arch/amd64/package.use.mask b/profiles/arch/amd64/package.use.mask index fd3bee6f4be7..8140309fc8e9 100644 --- a/profiles/arch/amd64/package.use.mask +++ b/profiles/arch/amd64/package.use.mask @@ -17,6 +17,26 @@ #--- END OF EXAMPLES --- +# Patrick McLean <chutzpah@gentoo.org> (2024-09-23) +# Only supported on x86/amd64 (bug #940014). +net-misc/lldpd -seccomp + +# orbea <orbea@riseup.net> (2024-07-19) +# Unmask the dynarec flag which has amd64 asm. +games-emulation/rmg -dynarec + +# Zen <dev@pyl.onl> (2024-07-01) +# Unmask the ugrd flag for installkernel. It is keyworded here +sys-kernel/installkernel -ugrd + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-23) +# Pulls in kde-apps/kgpg which is keyworded here +>=kde-apps/kdeutils-meta-24.05.1 -gpg + +# Jared Allard <jared@rgst.io> (2024-06-21) +# uasm and jwasm include amd64-specific ASM +app-arch/7zip -uasm -jwasm + # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-04-25) # ROCm and Level-Zero are amd64-only at the moment sys-apps/hwloc -rocm -l0 @@ -54,10 +74,6 @@ app-admin/syslog-ng -mqtt # Refind is only available on a subset of arches sys-kernel/installkernel -refind -# Ionen Wolkens <ionen@gentoo.org> (2024-01-27) -# dev-python/PyQt6 and dev-python/pyside6 are keyworded here -dev-python/QtPy -pyqt6 -pyside6 - # Michal Privoznik <michal.privoznik@gmail.com> (2024-01-21) # virtiofsd is available here app-emulation/libvirt -virtiofsd @@ -76,13 +92,8 @@ sys-kernel/gentoo-kernel -generic-uki sys-kernel/gentoo-kernel-bin -generic-uki # Ionen Wolkens <ionen@gentoo.org> (2023-12-02) -# dev-qt/qtwebengine:6 is keyworded here. -dev-python/PyQt6 -pdfium - -# Leonardo Hernández Hernández <leohdz172@proton.me> (2023-11-25) -# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff) -# are only available for amd64, arm64 and riscv ->=gui-libs/wlroots-0.17.0 -drm -liftoff +# dev-qt/qtwebengine:6 and dev-qt/qtremoteobjects:6 are keyworded here. +dev-python/PyQt6 -pdfium -remoteobjects # Jimi Huotari <chiitoo@gentoo.org> (2023-11-22) # Unmask on amd64. @@ -114,10 +125,6 @@ dev-qt/qtbase -renderdoc media-video/pipewire -roc # Matt Jolly <kangie@gentoo.org> (2023-08-10) -# 'ssl' USE required for curl's nghttp3/quic support -net-libs/ngtcp2 -ssl - -# Matt Jolly <kangie@gentoo.org> (2023-08-10) # nghttp3 has been tested to work on amd64 net-misc/curl -nghttp3 @@ -135,6 +142,7 @@ www-servers/apache -apache2_modules_tls # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-04-22) # snap only works on amd64 +gnome-extra/gnome-software -snap kde-plasma/discover -snap # Sam James <sam@gentoo.org> (2023-04-17) @@ -146,10 +154,6 @@ dev-lang/ruby -jit # pytables is available here. dev-python/tables -cpudetection -# Craig Andrews <candrews@gentoo.org> (2023-03-09) -# media-libs/libplacebo is keyworded here -media-video/ffmpeg -libplacebo - # Yiyang Wu <xgreenlandforwyy@gmail.com> (2023-01-27) # AMDGPU enablement depends on dev-libs/rocr-runtime, ~amd64 only # See also: https://bugs.gentoo.org/891499 @@ -249,7 +253,7 @@ sys-libs/compiler-rt-sanitizers -asan -dfsan -lsan -msan -hwasan -tsan sys-libs/compiler-rt-sanitizers -ubsan -safestack -cfi -scudo sys-libs/compiler-rt-sanitizers -gwp-asan sys-libs/compiler-rt-sanitizers -libfuzzer -memprof -orc -profile -xray -sys-libs/compiler-rt-sanitizers -ctx-profile +sys-libs/compiler-rt-sanitizers -ctx-profile -nsan -rtsan # Sam James <sam@gentoo.org> (2020-10-24) # asm redc is only available on amd64, @@ -329,10 +333,6 @@ dev-java/openjdk:11 -javafx # build on amd64. >=dev-lang/spidermonkey-60 -jit -# Andreas Sturmlechner <asturm@gentoo.org> (2019-05-09) -# media-libs/libplacebo is keyworded on amd64 -media-video/vlc -libplacebo - # Denis Lisov <dennis.lissov@gmail.com> (2019-05-09) # Overlay can only be built on amd64 and x86 x11-apps/igt-gpu-tools -overlay diff --git a/profiles/arch/amd64/package.use.stable.mask b/profiles/arch/amd64/package.use.stable.mask index 5be319fb3993..2dd055c2fb8e 100644 --- a/profiles/arch/amd64/package.use.stable.mask +++ b/profiles/arch/amd64/package.use.stable.mask @@ -17,14 +17,22 @@ #--- END OF EXAMPLES --- +# Ionen Wolkens <ionen@gentoo.org> (2024-09-27) +# dev-qt/qtremoteobjects:6 has not been stabilized yet. +dev-python/PyQt6 remoteobjects + +# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-07-24) +# No stable versions of ROCm at the moment +sys-apps/hwloc rocm + +# Zen <dev@pyl.onl> (2024-07-01) +# UGRD support is still experimental, no stable keywords for now +sys-kernel/installkernel ugrd + # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-17) # Experimental, virt-firmware is keyworded only unstable sys-kernel/installkernel efistub -# Ionen Wolkens <ionen@gentoo.org> (2024-01-27) -# dev-python/pyside6 is not stable here yet -dev-python/QtPy pyside6 - # Ionen Wolkens <ionen@gentoo.org> (2024-01-16) # cuda (and thus cudnn) are not available in stable media-libs/opencv cudnn @@ -42,10 +50,6 @@ sys-kernel/gentoo-kernel-bin generic-uki # librttopo has not been stabalized on this arch yet dev-db/spatialite rttopo -# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-08-21) -# Mask testing on stable until we have stable qt6 -dev-python/pytest-qt test - # Matt Jolly <kangie@gentoo.org> (2023-08-10) # net-libs/ngtcp2 is not marked stable net-misc/curl nghttp3 @@ -76,10 +80,6 @@ media-video/ffmpeg qsv # needs stabilizing media-video/ffmpeg vmaf -# Adel Kara Slimane <adel.ks@zegrapher.com> (2022-02-17) -# needs stabilizing -media-video/ffmpeg amf - # Joonas Niilola <juippis@gentoo.org> (2021-08-13) # dev-libs/efl is stabilized on amd64. app-crypt/pinentry -efl diff --git a/profiles/arch/amd64/use.mask b/profiles/arch/amd64/use.mask index 8049967550c6..445c840781e2 100644 --- a/profiles/arch/amd64/use.mask +++ b/profiles/arch/amd64/use.mask @@ -141,6 +141,7 @@ -video_cards_i965 -video_cards_intel -video_cards_nvidia +-video_cards_nvk -video_cards_siliconmotion -video_cards_vesa -video_cards_via diff --git a/profiles/arch/amd64/use.stable.mask b/profiles/arch/amd64/use.stable.mask index c7159b879206..237e247f299f 100644 --- a/profiles/arch/amd64/use.stable.mask +++ b/profiles/arch/amd64/use.stable.mask @@ -8,10 +8,6 @@ # ROCm/HIP is not suitable for stabilization. hip -# Jimi Huotari <chiitoo@gentoo.org> (2023-03-03) -# Mask until stable. -pyside6 - # Andreas Sturmlechner <asturm@gentoo.org> (2020-06-06) # sci-libs/mkl is not stable, needs online registration to even run pkg_setup mkl diff --git a/profiles/arch/amd64/x32/package.mask b/profiles/arch/amd64/x32/package.mask index 68f213cb7db1..d34202932280 100644 --- a/profiles/arch/amd64/x32/package.mask +++ b/profiles/arch/amd64/x32/package.mask @@ -1,6 +1,11 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Ben Kohler <bkohler@gentoo.org> (2024-05-27) +# Requires libpcre2[jit] which is now masked on x32 +mail-filter/rspamd +net-analyzer/ossec-hids + # James Le Cuirot <chewi@gentoo.org> (2024-02-17) # Requires net-libs/nodejs which is unavailable on amd64/x32. net-misc/sunshine @@ -33,6 +38,7 @@ sci-geosciences/viking # Jupyterlab and friends require net-libs/nodejs dev-python/jupyterlab dev-python/jupyterlab-lsp +dev-python/jupyterlab-widgets dev-python/jupyter-server-proxy sci-misc/jupyterlab-desktop-bin dev-python/plotly @@ -86,6 +92,7 @@ dev-python/spyder-notebook dev-util/kdevelop dev-util/kdevelop-php dev-util/kdevelop-python +kde-frameworks/purpose-kaccounts-services kde-apps/akonadi-calendar kde-apps/akonadi-import-wizard kde-apps/akonadiconsole @@ -96,6 +103,7 @@ kde-apps/cantor kde-apps/eventviews kde-apps/grantlee-editor kde-apps/incidenceeditor +kde-apps/kaccounts-integration:6 kde-apps/kaccounts-providers kde-apps/kaddressbook kde-apps/kalarm @@ -121,19 +129,18 @@ kde-apps/parley kde-apps/pim-data-exporter kde-apps/pim-sieve-editor kde-misc/kio-gdrive +kde-misc/kio-gdrive-common kde-misc/tellico kde-misc/zanshin media-gfx/digikam media-gfx/luminance-hdr >=media-gfx/skanpage-24.04.90 ->=media-sound/audex-24.04.90 media-sound/frescobaldi media-sound/teamspeak-client:3 media-video/vidify media-video/vidify-audiosync net-analyzer/nmapsi >=net-im/neochat-24.02.0 -=net-im/tokodon-24.02* net-im/whatsie net-libs/signon-ui sci-geosciences/qmapshack diff --git a/profiles/arch/amd64/x32/package.use.mask b/profiles/arch/amd64/x32/package.use.mask index f61f44b6b418..a5e47f6be8d8 100644 --- a/profiles/arch/amd64/x32/package.use.mask +++ b/profiles/arch/amd64/x32/package.use.mask @@ -1,6 +1,21 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner <asturm@gentoo.org> (2024-07-01) +# USE="kf6compat,kaccounts" depends on kde-frameworks/purpose:6[webengine] +# which is package.use.mask'ed on these arches. We cannot mask the +# combination specifically but in reality kaccounts is useless without +# additional dev-qt/qtwebengine revdeps. +kde-frameworks/purpose:5 kaccounts + +# Ben Kohler <bkohler@gentoo.org> (2024-05-27) +# Runtime issues (bug #925115) and build issues (bug #931092) +dev-libs/libpcre2 jit +dev-lang/php jit +mail-filter/rspamd jit +net-proxy/haproxy pcre-jit +www-servers/varnish jit + # Andreas Sturmlechner <asturm@gentoo.org> (2024-03-24) # Requires unkeyworded dev-qt/qtwebengine net-p2p/ktorrent rss @@ -16,7 +31,7 @@ dev-python/iminuit test dev-python/nbdime test dev-python/nbclient test dev-python/nbconvert test -dev-python/qiskit-terra visualization +dev-python/qiskit visualization sci-mathematics/cadabra jupyter sci-mathematics/yacas jupyter sci-physics/hepmc root diff --git a/profiles/arch/arm/make.defaults b/profiles/arch/arm/make.defaults index 49365fcaee47..72f8fa05cf8e 100644 --- a/profiles/arch/arm/make.defaults +++ b/profiles/arch/arm/make.defaults @@ -25,7 +25,3 @@ VIDEO_CARDS="exynos fbdev omap" # Michał Górny <mgorny@gentoo.org> (2017-03-14) # Unhide the ARM-specific USE_EXPANDs. USE_EXPAND_HIDDEN="-CPU_FLAGS_ARM" - -# Hans de Graaff <graaff@gentoo.org> (2024-05-20) -# Allow ruby32 stabling: https://bugs.gentoo.org/932285 -RUBY_TARGETS="ruby31 -ruby32" diff --git a/profiles/arch/arm/package.use.mask b/profiles/arch/arm/package.use.mask index 93d1793bbe6d..184bd8baf26c 100644 --- a/profiles/arch/arm/package.use.mask +++ b/profiles/arch/arm/package.use.mask @@ -1,6 +1,45 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-07) +# kde-plasma/plasma-workspace:6 is not keyworded +sys-auth/polkit kde +virtual/notification-daemon kde + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-07-31) +# KF6 and media-libs/phonon will drop arm keyword +app-office/texstudio video + +# Michał Górny <mgorny@gentoo.org> (2024-07-24) +# Full testing requires www-client/firefox. +dev-python/selenium test-rust + +# orbea <orbea@riseup.net> (2024-07-19) +# Unmask the dynarec flag which has arm asm. +games-emulation/rmg -dynarec + +# matoro <matoro_gentoo@matoro.tk> (2024-07-14) +# Abandoned upstream, does not take bug reports, unsupported in Gentoo. +# Only remaining use is as a requirement for dev-lang/go on arm{,64}. +# See #934149, #934151, #936022, #936021 +sys-devel/binutils -gold + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-07-01) +# USE="kf6compat,kaccounts" depends on kde-frameworks/purpose:6[webengine] +# which is package.use.mask'ed on these arches. We cannot mask the +# combination specifically but in reality kaccounts is useless without +# additional dev-qt/qtwebengine revdeps. +kde-frameworks/purpose:5 kaccounts + +# Sam James <sam@gentoo.org> (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +app-crypt/pinentry qt6 +app-office/libreoffice qt6 + +# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-06-01) +# qtnetworkauth not yet keyworded here +dev-python/pyside6 network-auth + # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-21) # virt-firmware is keyworded here sys-kernel/installkernel -efistub @@ -74,11 +113,7 @@ dev-lang/idris2 test-full dev-python/cloudscraper test dev-python/QtPy test games-util/lgogdownloader gui -kde-apps/kde-apps-meta pim -kde-apps/kdenetwork-meta bittorrent -kde-apps/kleopatra pim -kde-apps/umbrello php -kde-misc/kio-gdrive share +kde-plasma/plasma-nm openconnect net-irc/quassel urlpreview net-misc/fatrat bittorrent net-misc/seafile-client shibboleth @@ -114,10 +149,6 @@ app-text/enchant nuspell # Untested useflag on other arches, needs keywording media-video/ffmpeg vmaf -# Andreas Sturmlechner <asturm@gentoo.org> (2022-03-13) -# Not yet keyworded. Bug #835037 -kde-frameworks/kfilemetadata mobi - # Sam James <sam@gentoo.org> (2022-03-10) # Boost has support for ARM32 # https://www.boost.org/doc/libs/1_78_0/libs/context/doc/html/context/architectures.html @@ -194,7 +225,7 @@ net-wireless/gnuradio ctrlport # Arfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com> (2020-10-14) # app-i18n/fcitx:4 not keyworded. -media-libs/libsdl2 fcitx4 +media-libs/libsdl2 fcitx # Adam Feldman <NP-Hardass@gentoo.org> (2020-09-05) # dev-util/dogtail is not keyworded for arm @@ -259,10 +290,6 @@ dev-ruby/capybara test # pre-built, no ARM support net-wireless/gr-osmosdr sdrplay -# Andreas Sturmlechner <asturm@gentoo.org> (2018-06-03) -# net-wireless/soapysdr not keyworded -net-wireless/gr-osmosdr soapy - # Markus Meier <maekke@gentoo.org> (2018-05-30) # unkeyworded deps for bug #621434 net-analyzer/zmap mongo @@ -279,23 +306,11 @@ net-libs/gnutls test-full # Moved from use.mask since they are flags local to one package. media-tv/tvheadend hdhomerun -# Patrice Clement <monsieurp@gentoo.org> (2017-09-24) -# Unmask Raspberry Pi support on arm. -media-video/mpv -raspberry-pi - # James Le Cuirot <chewi@gentoo.org> (2017-09-20) # media-sound/mac's executable segfaults when compressing all but the # smallest wav files. media-sound/xmms2 mac -# Michał Górny <mgorny@gentoo.org> (2017-08-10) -# Requires USE=ipmi which is masked in this profile. -sys-power/nut ups_drivers_nut-ipmipsu - -# Michał Górny <mgorny@gentoo.org> (2017-08-08) -# Requires USE=opencl that is masked in this profile. -net-misc/bfgminer adl lm-sensors - # Patrice Clement <monsieurp@gentoo.org> (2017-04-09) # Enable MQTT support on supported architectures app-metrics/collectd -collectd_plugins_mqtt @@ -368,7 +383,6 @@ net-print/hplip -scanner kde # MMAL is available on the Raspberry Pi (armv6 & armv7 so far) media-video/ffmpeg -mmal media-video/ffmpeg-chromium -mmal -media-video/mpv -mmal # Alexis Ballier <aballier@gentoo.org> (2015-04-02) # Needs ilmbase (openexr), which does not build and is masked on arm. diff --git a/profiles/arch/arm/package.use.stable.mask b/profiles/arch/arm/package.use.stable.mask index 674e85444f0a..31ac62057c09 100644 --- a/profiles/arch/arm/package.use.stable.mask +++ b/profiles/arch/arm/package.use.stable.mask @@ -1,6 +1,14 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner <asturm@gentoo.org> (2024-07-23) +# kde-frameworks/kservice, dev-qt/qtpaths not stable here +x11-misc/xdg-utils plasma + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-29) +# media-libs/libplacebo is not stable here +media-video/ffmpeg libplacebo + # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-21) # Experimental, virt-firmware is keyworded only unstable sys-kernel/installkernel efistub @@ -52,11 +60,6 @@ dev-python/ipython nbconvert # dev-libs/criterion is not marked stable yet app-admin/syslog-ng test -# Sam James <sam@gentoo.org> (2022-01-15) -# Requires dev-util/pahole which is not yet marked stable on arm. -sys-kernel/gentoo-kernel debug -sys-kernel/vanilla-kernel debug - # Sam James <sam@gentoo.org> (2021-10-25) # Various dependencies not yet stable on arm # bug #816981 @@ -98,7 +101,6 @@ sci-mathematics/z3 java # Andreas Sturmlechner <asturm@gentoo.org> (2019-02-10) # Needs kde-frameworks/{kwallet,ki18n,kconfig} stable dev-vcs/subversion kwallet -net-libs/libproxy kde # Andreas Sturmlechner <asturm@gentoo.org> (2019-02-10) # Needs kde-plasma/{polkit-kde-agent,plasma-workspace} stable @@ -171,10 +173,6 @@ dev-db/mariadb jdbc # RPI support on arm dev-libs/libcec -raspberry-pi -# Ilya Tumaykin <itumaykin+gentoo@gmail.com> (2016-04-13) -# Requires special hardware to test and stabilize properly. -media-video/mpv raspberry-pi - # Brian Evans <grknight@gentoo.org> (2016-01-08) # net-misc/libteam is not yet stable on arm net-misc/networkmanager teamd diff --git a/profiles/arch/arm/use.mask b/profiles/arch/arm/use.mask index f5ae9cb0482a..53b35994e0a5 100644 --- a/profiles/arch/arm/use.mask +++ b/profiles/arch/arm/use.mask @@ -1,12 +1,17 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # Unmask the flag which corresponds to ARCH. -arm +# Sam James <sam@gentoo.org> (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +kf6compat + # Andreas Sturmlechner <asturm@gentoo.org> (2023-02-06) # Successful build of dev-qt/qtwebengine depends on 64-bit host # Bug #893234 +pdfium webengine # matoro <matoro_gentoo@matoro.tk> (2022-09-29) diff --git a/profiles/arch/arm/use.stable.mask b/profiles/arch/arm/use.stable.mask index 496c16486c01..dceaf51d1fc3 100644 --- a/profiles/arch/arm/use.stable.mask +++ b/profiles/arch/arm/use.stable.mask @@ -4,14 +4,6 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in use.mask -# Hans de Graaff <graaff@gentoo.org> (2024-05-20) -# Allow ruby32 stabling: https://bugs.gentoo.org/932285 -ruby_targets_ruby32 - -# Ionen Wolkens <ionen@gentoo.org> (2024-01-27) -# Qt6 is not stable here yet -qt6 - # Sam James <sam@gentoo.org> (2022-01-16) # net-libs/gnome-online-accounts is not marked stable on arm yet gnome-online-accounts diff --git a/profiles/arch/arm64/package.use b/profiles/arch/arm64/package.use index 3d30a34a0dba..f1ba7d873ad1 100644 --- a/profiles/arch/arm64/package.use +++ b/profiles/arch/arm64/package.use @@ -1,6 +1,12 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Michał Górny <mgorny@gentoo.org> (2024-09-04) +# Build with debugging support by default to facilitate dev-debug/dtrace +# and sys-apps/systemd[bpf]. +>=sys-kernel/gentoo-kernel-6.6.53 debug +>=sys-kernel/vanilla-kernel-6.6.53 debug + # James Le Cuirot <chewi@gentoo.org> (2023-12-16) # Apply additional FFmpeg patches for efficient playback on some SoCs. media-tv/kodi soc diff --git a/profiles/arch/arm64/package.use.mask b/profiles/arch/arm64/package.use.mask index 36a23c24ef07..a55d1801907f 100644 --- a/profiles/arch/arm64/package.use.mask +++ b/profiles/arch/arm64/package.use.mask @@ -1,6 +1,24 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# orbea <orbea@riseup.net> (2024-07-19) +# Unmask the dynarec flag which has arm64 asm. +games-emulation/rmg -dynarec + +# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-07-16) +# Unmask the ugrd flag for installkernel. It is keyworded here +sys-kernel/installkernel -ugrd + +# matoro <matoro_gentoo@matoro.tk> (2024-07-14) +# Abandoned upstream, does not take bug reports, unsupported in Gentoo. +# Only remaining use is as a requirement for dev-lang/go on arm{,64}. +# See #934149, #934151, #936022, #936021 +sys-devel/binutils -gold + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-23) +# Pulls in kde-apps/kgpg which is keyworded here +>=kde-apps/kdeutils-meta-24.05.1 -gpg + # Ionen Wolkens <ionen@gentoo.org> (2024-05-19) # jit is supported here >=dev-qt/qtdeclarative-6 -jit @@ -21,11 +39,6 @@ media-libs/openpgl -cpu_flags_arm_neon # virt-firmware is keyworded here sys-kernel/installkernel -efistub -# Mart Raudsepp <leio@gentoo.org> (2024-03-03) -# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff) -# are only available for amd64, arm64 and riscv ->=gui-libs/wlroots-0.17.0 -drm -liftoff - # Joonas Niilola <juippis@gentoo.org> (2024-02-16) # Test dependencies not keyworded on this arch. www-servers/nginx test @@ -42,10 +55,6 @@ www-servers/nginx test # Supports 64-bit NEON media-libs/zita-resampler -cpu_flags_arm_neon -# Ionen Wolkens <ionen@gentoo.org> (2024-01-27) -# dev-python/PyQt6 is keyworded here -dev-python/QtPy -pyqt6 - # Michal Privoznik <michal.privoznik@gmail.com> (2024-01-18) # No sys-block/nbdkit on arm, yet app-emulation/libvirt nbd @@ -82,6 +91,7 @@ dev-libs/botan -cpu_flags_arm_neon # Patrick McLean <chutzpah@gentoo.org> (2023-10-03) # sys-apps/s6-linux-init has not been tested on this arch sys-apps/openrc s6 +sys-apps/openrc-navi s6 # Jon Janzen <jon@jonjanzen.com> (2023-09-11) # librttopo has not been tested on this arch @@ -223,7 +233,7 @@ app-text/enchant voikko sys-libs/compiler-rt-sanitizers -asan -dfsan -lsan -msan -hwasan -tsan sys-libs/compiler-rt-sanitizers -ubsan -safestack -cfi -scudo sys-libs/compiler-rt-sanitizers -gwp-asan -shadowcallstack -sys-libs/compiler-rt-sanitizers -libfuzzer -profile -xray +sys-libs/compiler-rt-sanitizers -libfuzzer -profile -xray -rtsan >=sys-libs/compiler-rt-sanitizers-16 -orc # Roy Bamford <neddyseagoon@gentoo.org> (2020-12-07) @@ -267,11 +277,6 @@ media-video/ffmpeg -rav1e # Mask io-uring & zbc pending keywording sys-block/fio -io-uring -# Michał Górny <mgorny@gentoo.org> (2020-06-19) -# Requires dev-util/pahole. -sys-kernel/gentoo-kernel debug -sys-kernel/vanilla-kernel debug - # Sam James <sam@gentoo.org> (2020-06-11) # PGO works on arm64 >=www-client/firefox-68.9.0 -pgo diff --git a/profiles/arch/arm64/package.use.stable.mask b/profiles/arch/arm64/package.use.stable.mask index 459cf2219642..d43977feeedb 100644 --- a/profiles/arch/arm64/package.use.stable.mask +++ b/profiles/arch/arm64/package.use.stable.mask @@ -1,17 +1,25 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-07-16) +# UGRD support is still experimental, no stable keywords for now +sys-kernel/installkernel ugrd + +# Eray Aslan <eras@gentoo.org> (2024-06-17) +# mongodb needed for tests which is not stable keyworded for arm64 +dev-libs/mongo-c-driver test + +# Sam Jamrs <sam@gentoo.org> (2024-06-07) +# dev-libs/capstone hasn't been stabilized yet +app-emulation/qemu capstone + # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-21) # Experimental, virt-firmware is keyworded only unstable sys-kernel/installkernel efistub -# Mart Raudsepp <leio@gentoo.org> (2024-03-03) -# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff) -# are not stable yet on arm64 ->=gui-libs/wlroots-0.17.0 drm liftoff - # Ionen Wolkens <ionen@gentoo.org> (2024-01-27) -# dev-python/PyQt6 and dev-python/pyside6 are not stable here yet +# dev-python/PyQt6-WebEngine is not stable here yet, bug #939558 +# dev-python/pyside6 is not stable here yet dev-python/QtPy pyqt6 pyside6 # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-12-18) @@ -87,7 +95,7 @@ media-gfx/enblend doc # Arfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com> (2020-10-14) # app-i18n/fcitx:4 not stable. -media-libs/libsdl2 fcitx4 +media-libs/libsdl2 fcitx # Sam James <sam@gentoo.org> (2020-10-06) # Not yet stable on arm64. diff --git a/profiles/arch/arm64/use.mask b/profiles/arch/arm64/use.mask index 2b5aca1f59d3..964b358c1de6 100644 --- a/profiles/arch/arm64/use.mask +++ b/profiles/arch/arm64/use.mask @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # Unmask the flag which corresponds to ARCH. diff --git a/profiles/arch/base/make.defaults b/profiles/arch/base/make.defaults index bb227e4ece2a..19d64396e468 100644 --- a/profiles/arch/base/make.defaults +++ b/profiles/arch/base/make.defaults @@ -3,6 +3,6 @@ USE_EXPAND_UNPREFIXED="ARCH" USE_EXPAND_IMPLICIT="ARCH" -USE_EXPAND_VALUES_ARCH="alpha amd64 amd64-linux arm arm64 arm64-macos hppa ia64 loong m68k mips ppc ppc64 ppc64-linux ppc-macos riscv s390 sparc x64-macos x64-solaris x86 x86-linux" +USE_EXPAND_VALUES_ARCH="alpha amd64 amd64-linux arm arm64 arm64-macos hppa loong m68k mips ppc ppc64 ppc64-linux ppc-macos riscv s390 sparc x64-macos x64-solaris x86 x86-linux" PROFILE_ONLY_VARIABLES="${PROFILE_ONLY_VARIABLES} ARCH USE_EXPAND_VALUES_ARCH" diff --git a/profiles/arch/base/package.use.mask b/profiles/arch/base/package.use.mask index 9298664bc709..f1851b42d61a 100644 --- a/profiles/arch/base/package.use.mask +++ b/profiles/arch/base/package.use.mask @@ -1,6 +1,32 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Paul Zander <negril.nx+gentoo@gmail.com> (2024-08-12) +# Builds a amd vendored opencl runtime that causes collisions. +# Hardly useful outside of maintainer testing. #934963, #936317 +dev-util/hip opencl + +# matoro <matoro_gentoo@matoro.tk> (2024-07-14) +# Abandoned upstream, does not take bug reports, unsupported in Gentoo. +# Only remaining use is as a requirement for dev-lang/go on arm{,64}. +# See #934149, #934151, #936022, #936021 +sys-devel/binutils default-gold gold +sys-devel/binutils-hppa64 default-gold gold + +# Zen <dev@pyl.onl> (2024-07-01) +# UGRD is not keyworded everywhere yet +sys-kernel/installkernel ugrd + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-23) +# Pulls in kde-apps/kgpg which requires kde-apps/akonadi, which is as +# part of the KDE PIM stack (big, requiring QtWebengine) only keyworded +# on amd64 and arm64. +>=kde-apps/kdeutils-meta-24.05.1 gpg + +# Jared Allard <jared@rgst.io> (2024-06-21) +# uasm and jwasm include amd64-specific ASM +app-arch/7zip uasm jwasm + # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-04-25) # ROCm and Level-Zero are amd64-only at the moment sys-apps/hwloc rocm l0 @@ -34,10 +60,6 @@ app-admin/syslog-ng mqtt # Refind is only available on a subset of arches sys-kernel/installkernel refind -# Ionen Wolkens <ionen@gentoo.org> (2024-01-27) -# dev-python/PyQt6 and dev-python/pyside6 have very few keywords -dev-python/QtPy pyqt6 pyside6 - # Michal Privoznik <michal.privoznik@gmail.com> (2024-01-21) # virtiofsd is only available on some arches app-emulation/libvirt virtiofsd @@ -56,13 +78,8 @@ sys-kernel/gentoo-kernel generic-uki sys-kernel/gentoo-kernel-bin generic-uki # Ionen Wolkens <ionen@gentoo.org> (2023-12-02) -# Needs dev-qt/qtwebengine:6 which has very few keywords. -dev-python/PyQt6 pdfium - -# Leonardo Hernández Hernández <leohdz172@proton.me> (2023-11-25) -# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff) -# are only available for amd64, arm64 and riscv ->=gui-libs/wlroots-0.17.0 drm liftoff +# dev-qt/qtwebengine:6 and dev-qt/qtremoteobjects:6 have few keywords. +dev-python/PyQt6 pdfium remoteobjects # Jimi Huotari <chiitoo@gentoo.org> (2023-11-22) # media-libs/libvpl is only keyworded for amd64 at this time. @@ -107,6 +124,7 @@ www-servers/apache apache2_modules_tls # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-04-22) # snap only works on amd64 +gnome-extra/gnome-software snap kde-plasma/discover snap # Sam James <sam@gentoo.org> (2023-04-03) @@ -114,10 +132,6 @@ kde-plasma/discover snap # See bug #894078. dev-python/tables cpudetection -# Andreas Sturmlechner <asturm@gentoo.org> (2023-03-09) -# media-libs/libplacebo is not keyworded anywhere except amd64/ppc64/x86 yet -media-video/ffmpeg libplacebo - # Michał Górny <mgorny@gentoo.org> (2023-01-24) # libomptarget is only supported on 64-bit architectures. >=sys-libs/libomp-16.0.0_pre20230124 offload @@ -234,7 +248,7 @@ sys-libs/compiler-rt-sanitizers asan dfsan lsan msan hwasan tsan sys-libs/compiler-rt-sanitizers ubsan safestack cfi scudo sys-libs/compiler-rt-sanitizers shadowcallstack gwp-asan sys-libs/compiler-rt-sanitizers libfuzzer memprof orc profile xray -sys-libs/compiler-rt-sanitizers ctx-profile +sys-libs/compiler-rt-sanitizers ctx-profile nsan rtsan # Sam James <sam@gentoo.org> (2020-10-24) # asm redc is only available on amd64, @@ -308,10 +322,6 @@ dev-java/openjdk:11 javafx # dev-lang/spidermonkey:60[jit] fails to build on most platforms >=dev-lang/spidermonkey-60 jit -# Andreas Sturmlechner <asturm@gentoo.org> (2019-05-09) -# media-libs/libplacebo is not keyworded anywhere except amd64/ppc64/x86 yet -media-video/vlc libplacebo - # Denis Lisov <dennis.lissov@gmail.com> (2019-05-09) # Overlay can only be built on amd64 and x86 x11-apps/igt-gpu-tools overlay @@ -388,19 +398,12 @@ dev-db/mariadb jdbc # This flag only has meaning on amd64 sys-boot/grub:2 grub_platforms_xen-32 -# Ian Delaney <idella4@gentoo.org> (2016-04-06) -# on behalf of Ilya Tumaykin <itumaykin+gentoo@gmail.com> -# Raspberry Pi support is only available on arm. -# Mask raspberry-pi USE globally, unmask on arm. -media-video/mpv raspberry-pi - # Alexis Ballier <aballier@gentoo.org> (2015-11-14) # MMAL is only available on the Raspberry Pi: # Mask it globally, unmask it on arm. media-video/motion mmal media-video/ffmpeg mmal media-video/ffmpeg-chromium mmal -media-video/mpv mmal # Brian Evans <grknight@gentoo.org> (2015-09-14) # Mask new USE flags for mariadb which all arches do not yet have dependencies diff --git a/profiles/arch/base/use.mask b/profiles/arch/base/use.mask index d1cd9910ec4a..a9616ebb2587 100644 --- a/profiles/arch/base/use.mask +++ b/profiles/arch/base/use.mask @@ -17,10 +17,6 @@ jasper # sci-libs/atlas is only supported on specific architectures atlas -# Michał Górny <mgorny@gentoo.org> (2024-02-05) -# LLVM slots without keywords. -llvm_slot_19 - # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-07-11) # Mask secureboot flag on arches where sbsigntools is not keyworded secureboot @@ -160,6 +156,7 @@ video_cards_i915 video_cards_i965 video_cards_intel video_cards_nvidia +video_cards_nvk video_cards_vesa video_cards_via video_cards_vmware @@ -248,7 +245,6 @@ amd64 arm arm64 hppa -ia64 loong m68k mips diff --git a/profiles/arch/hppa/make.defaults b/profiles/arch/hppa/make.defaults index a279a075b229..b8faae33585f 100644 --- a/profiles/arch/hppa/make.defaults +++ b/profiles/arch/hppa/make.defaults @@ -22,7 +22,3 @@ CHOST_hppa="${CHOST}" # Donnie Berkholz <dberkholz@gentoo.org> (2006-08-18) # Defaults for video drivers VIDEO_CARDS="fbdev" - -# Hans de Graaff <graaff@gentoo.org> (2024-05-20) -# Allow ruby32 stabling: https://bugs.gentoo.org/932285 -RUBY_TARGETS="ruby31 -ruby32" diff --git a/profiles/arch/hppa/package.use.mask b/profiles/arch/hppa/package.use.mask index 1350b08d459d..dc92c7939f40 100644 --- a/profiles/arch/hppa/package.use.mask +++ b/profiles/arch/hppa/package.use.mask @@ -4,6 +4,22 @@ # NOTE: When masking a USE flag due to missing keywords, please file a keyword # request bug for the hppa arch. +# Sam James <sam@gentoo.org> (2024-08-23) +# dev-util/bpftool and/or sys-devel/bpf-toolchain not keyworded here +sys-apps/systemd bpf + +# Ulrich Müller <ulm@gentoo.org> (2024-08-03) +# Needs dev-libs/openspecfun which is not yet keyworded +sci-visualization/gnuplot amos + +# Leonardo Hernández Hernández <leohdz172@proton.me> (2024-07-07) +# media-libs/quirc and media-sound/liblc3 are not keyworded here +media-video/ffmpeg quirc liblc3 + +# Sam James <sam@gentoo.org> (2024-07-03) +# kde-frameworks/kservice not keyworded here +x11-misc/xdg-utils plasma + # Holger Hoffstätte <holger@applied-asynchrony.com> (2024-05-19) # media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 media-gfx/graphicsmagick jpeg2k @@ -57,15 +73,12 @@ dev-qt/qtgui vulkan # Patrick McLean <chutzpah@gentoo.org> (2023-10-03) # sys-apps/s6-linux-init has not been tested on this arch sys-apps/openrc s6 +sys-apps/openrc-navi s6 # Sam James <sam@gentoo.org> (2023-09-24) # Qt not keyworded here. app-text/doxygen gui -# Sam James <sam@gentoo.org> (2023-09-22) -# Qt 6 not keyworded here. -dev-build/cmake gui - # Sam James <sam@gentoo.org> (2023-09-18) # x11-libs/gtksourceview:4 not keyworded here media-gfx/inkscape sourceview @@ -250,7 +263,7 @@ dev-libs/efl avif lua_single_target_luajit physics # Matt Turner <mattst88@gentoo.org> (2020-08-11) # No drivers on this architecture support Vulkan -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa video_cards_zink vulkan vulkan-overlay zink # Robin H. Johnson <robbat2@gentoo.org> (2020-07-02) # Mask io-uring & zbc pending keywording diff --git a/profiles/arch/hppa/package.use.stable.mask b/profiles/arch/hppa/package.use.stable.mask index c12bd0c48c58..14afbb12801f 100644 --- a/profiles/arch/hppa/package.use.stable.mask +++ b/profiles/arch/hppa/package.use.stable.mask @@ -17,6 +17,18 @@ #--- END OF EXAMPLES --- +# Sam James <sam@gentoo.org> (2024-07-31) +# Qt 6 not stable here. +dev-build/cmake gui + +# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-07-25) +# Moved to stable.mask, issue is fixed in unstable v40 +# Sam James <sam@gentoo.org> (2024-06-19) +# The systemd implementation of installkernel doesn't currently support +# updating the 'initramfs.img' and 'vmlinuz' symlinks that palo needs, +# and palo is the only bootloader for HPPA. +sys-kernel/installkernel systemd + # Eli Schwartz <eschwartz93@gmail.com> (2024-02-05) # Mask pdf support so net-print/cups-filters stabilisation # can go ahead (bug 627392) @@ -185,7 +197,7 @@ x11-base/xorg-server xorg # Arfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com> (2020-10-14) # app-i18n/fcitx:4 not stable. -media-libs/libsdl2 fcitx4 +media-libs/libsdl2 fcitx # Rolf Eike Beer <eike@sf-mail.de> (2020-06-10) # not stable dev-vcs/mercurial because of broken dependencies: bug #727390 diff --git a/profiles/arch/hppa/use.mask b/profiles/arch/hppa/use.mask index 429687a52b99..e988802889da 100644 --- a/profiles/arch/hppa/use.mask +++ b/profiles/arch/hppa/use.mask @@ -66,10 +66,6 @@ plymouth # sys-fs/dmraid has not been tested on HPPA dmraid -# Jeroen Roovers <jer@gentoo.org> (2016-01-31) -# USE=xwidgets requires net-libs/webkit-gtk -xwidgets - # Jeroen Roovers <jer@gentoo.org> (2015-10-16) # HPPA has no NUMA support in the kernel numa diff --git a/profiles/arch/hppa/use.stable.mask b/profiles/arch/hppa/use.stable.mask index cbac15e9d089..3d3e6d11f69b 100644 --- a/profiles/arch/hppa/use.stable.mask +++ b/profiles/arch/hppa/use.stable.mask @@ -4,9 +4,9 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in use.mask -# Hans de Graaff <graaff@gentoo.org> (2024-05-20) -# Allow ruby32 stabling: https://bugs.gentoo.org/932285 -ruby_targets_ruby32 +# matoro <matoro_gentoo@matoro.tk> (2024-07-16) +# dev-lang/ruby now unstabled on hppa +ruby # Ionen Wolkens <ionen@gentoo.org> (2024-01-27) # Qt6 is not stable here yet diff --git a/profiles/arch/ia64/make.defaults b/profiles/arch/ia64/make.defaults deleted file mode 100644 index 0e0ebaa64120..000000000000 --- a/profiles/arch/ia64/make.defaults +++ /dev/null @@ -1,31 +0,0 @@ -# Copyright 1999-2022 Gentoo Authors -# Distributed under the terms of the GNU General Public License v2 - -ARCH="ia64" -ACCEPT_KEYWORDS="ia64 ~ia64" - -CHOST="ia64-unknown-linux-gnu" -CFLAGS="-O2 -pipe" -CXXFLAGS="${CFLAGS}" -FFLAGS="${CFLAGS}" -FCFLAGS="${CFLAGS}" - -# Sergei Trofimovich <slyfox@gentoo.org> (2017-06-03) -# Enable USE=libtirpc by default, to ease dependency resolution during -# the stabilization of glibc-2.26. Bug 657148 -USE="libtirpc" - -# Michał Górny <mgorny@gentoo.org> (2014-07-01) -# Set ABI & DEFAULT_ABI consistently with ${ARCH}, to make ebuild -# checks simpler. -ABI="ia64" -DEFAULT_ABI="ia64" -MULTILIB_ABIS="ia64" -LIBDIR_ia64="lib" -CHOST_ia64="${CHOST}" - -# Donnie Berkholz <dberkholz@gentoo.org> (2006-08-18) -# Defaults for video drivers -#VIDEO_CARDS="fbdev mga r128 radeon" -INPUT_DEVICES="void" -VIDEO_CARDS="dummy" diff --git a/profiles/arch/ia64/package.mask b/profiles/arch/ia64/package.mask deleted file mode 100644 index a9dc726d7b2d..000000000000 --- a/profiles/arch/ia64/package.mask +++ /dev/null @@ -1,10 +0,0 @@ -# Copyright 2019-2024 Gentoo Authors -# Distributed under the terms of the GNU General Public License v2 - -# Sam James <sam@gentoo.org> (2024-01-09) -# glibc-2.39 dropped support for ia64. ->=sys-libs/glibc-2.39 - -# Sergei Trofimovich <slyfox@gentoo.org> (2020-05-02) -# greenlet needs arch-specific stack switching code. There is no ia64 port. -dev-python/greenlet diff --git a/profiles/arch/ia64/package.use.force b/profiles/arch/ia64/package.use.force deleted file mode 100644 index 618de622be91..000000000000 --- a/profiles/arch/ia64/package.use.force +++ /dev/null @@ -1,11 +0,0 @@ -# Copyright 1999-2022 Gentoo Authors -# Distributed under the terms of the GNU General Public License v2 - -# Sam James <sam@gentoo.org> (2022-02-19) -# New enough SpiderMonkey not keyworded here, bug #753221 -sys-auth/polkit duktape - -# Raúl Porcel <armin76@gentoo.org> (2007-10-21) -# It segfaults without debug use-flags -# Remove when http://bugs.php.net/bug.php?id=42893 is fixed -dev-lang/php debug diff --git a/profiles/arch/ia64/package.use.mask b/profiles/arch/ia64/package.use.mask deleted file mode 100644 index c51e084cdf1c..000000000000 --- a/profiles/arch/ia64/package.use.mask +++ /dev/null @@ -1,559 +0,0 @@ -# Copyright 1999-2024 Gentoo Authors -# Distributed under the terms of the GNU General Public License v2 - -# Sam James <sam@gentoo.org> (2024-05-19) -# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 -media-gfx/graphicsmagick jpeg2k - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-13) -# Requires dev-util/shelltestrunner -app-arch/mt-st test - -# Michał Górny <mgorny@gentoo.org> (2024-05-08) -# Requires sys-devel/{clang,llvm}:16. -dev-lang/python jit - -# Robin H. Johnson <robbat2@gentoo.org) (2024-03-13) -# sys-cluster/corosync not yet keyworded, niche use case for mdadm -sys-fs/mdadm corosync - -# Eray Aslan <eras@gentoo.org> (2024-03-08) -# mongodb dependencies are not keyworded -mail-mta/postfix mongodb - -# matoro <matoro_gentoo@matoro.tk> (2024-02-29) -# Observed crashes in git-remote-https due to this -net-misc/curl adns - -# Eray Aslan <eras@gentoo.org> (2024-02-13) -# tests require dev-db/mongodb which is not keyworded -dev-libs/mongo-c-driver test - -# Leonardo Hernández Hernández <leohdz172@proton.me> (2024-01-15) -# net-libs/grpc not keyworded here -app-admin/syslog-ng grpc - -# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-01-13) -# Unmask only where grub is keyworded -sys-kernel/installkernel -grub - -# Sam James <sam@gentoo.org> (2024-01-02) -# dev-libs/capstone not keyworded here -dev-lang/php capstone - -# David Seifert <soap@gentoo.org> (2023-12-30) -# sys-auth/sssd not keyworded here anymore -app-admin/sudo sssd -sys-auth/pambase sssd - -# Mart Raudsepp <leio@gentoo.org> (2023-12-25) -# sys-apps/xdg-desktop-portal not keyworded here yet -x11-base/xwayland libei - -# James Le Cuirot (2023-12-12) -# USE=bpf depends on sys-devel/clang which is not keyworded on ia64 -media-libs/libv4l bpf - -# Leonardo Hernández Hernández <leohdz172@proton.me> (2023-11-15) -# Vulkan is not available here -media-video/ffmpeg glslang shaderc vulkan - -# Violet Purcell <vimproved@inventati.org> (2023-10-12) -# dev-build/samurai is not keyworded here. -app-alternatives/ninja samurai - -# Patrick McLean <chutzpah@gentoo.org> (2023-10-03) -# sys-apps/s6-linux-init has not been tested on this arch -sys-apps/openrc s6 - -# Sam James <sam@gentoo.org> (2023-09-24) -# Qt not keyworded here. -app-text/doxygen gui - -# Sam James <sam@gentoo.org> (2023-09-22) -# Qt 6 not keyworded here. -dev-build/cmake gui - -# Jon Janzen <jon@jonjanzen.com> (2023-09-11) -# librttopo has not been tested on this arch -dev-db/spatialite rttopo - -# Sam James <sam@gentoo.org> (2023-06-18) -# Qt 5 not keyworded here -app-text/ansifilter gui -app-text/highlight gui - -# Matt Turner <mattst88@gentoo.org> (2023-05-30) -# sys-apps/dbus-broker is not keyworded -app-accessibility/at-spi2-core dbus-broker - -# Sam James <sam@gentoo.org> (2023-04-17) -# net-misc/pps-tools is not keyworded here -net-misc/chrony pps - -# Sam James <sam@gentoo.org> (2023-05-01) -# media-libs/libjxl is not keyworded -# bug https://bugs.gentoo.org/853628 -media-gfx/gimp jpegxl -media-gfx/graphicsmagick jpegxl -media-gfx/imagemagick jpegxl -media-libs/imlib2 jpegxl - -# Sam James <sam@gentoo.org> (2023-04-14) -# dev-python/sympy not keyworded here yet -dev-python/nbval test - -# Michał Górny <mgorny@gentoo.org> (2023-03-14) -# Requires virtual/pandoc. -dev-python/nbclassic doc -dev-python/nbval doc - -# Sam James <sam@gentoo.org> (2022-12-26) -# Unkeyworded dependencies -dev-util/diffoscope opendocument pascal pdf R - -# matoro <matoro_gentoo@matoro.tk> (2022-09-30) -# No ruby on ia64 for dev-ruby/asciidoctor -net-misc/chrony html - -# Arthur Zamarin <arthurzam@gentoo.org> (2022-08-15) -# deps not keyworded -dev-util/pkgcheck emacs - -# Matt Turner <mattst88@gentoo.org> (2022-06-25) -# net-libs/libqrtr-glib not keyworded -net-misc/modemmanager qrtr - -# Nickolas Raymond Kaczynski <nrk@disroot.org> (2022-04-24) -# Dependencies are missing keywords -media-libs/imlib2 svg - -# Matt Turner <mattst88@gentoo.org> (2022-04-18) -# app-text/nuspell is not keyworded -app-text/enchant nuspell - -# Matt Turner <mattst88@gentoo.org> (2022-04-16) -# net-misc/freerdp is not keyworded -dev-libs/weston rdp - -# Lars Wendler <polynomial-c@gentoo.org> (2022-04-01) -# gnome-base/librsvg missing keywords -media-libs/freetype svg - -# Adel Kara Slimane <adel.ks@zegrapher.com> (2022-03-14) -# Untested useflag on other arches, needs keywording -media-video/ffmpeg vmaf - -# Sam James <sam@gentoo.org> (2022-03-06) -# Unkeyworded dependencies -net-mail/cyrus-imapd http - -# Sam James <sam@gentoo.org> (2022-01-29) -# app-text/ronn-ng not keyworded here, bug #801103 -app-accessibility/espeak-ng man - -# Sam James <sam@gentoo.org> (2021-11-05) -# Avoid keywording unnecessary depenencies for now, bug #804115 -dev-python/scipy fortran - -# Sam James <sam@gentoo.org> (2021-11-05) -# Test suite is very fragile and doesn't even run on amd64. -# No real point in running it here right now, bug #804115. -dev-cpp/eigen test - -# Sam James <sam@gentoo.org> (2021-10-24) -# Avoid Pipewire for now because of new wireplumber dependency which lacks -# keywords. Doubt anybody is using PW here anyway right now. -# bug #807616 -media-libs/libsdl2 pipewire - -# Sam James <sam@gentoo.org> (2021-09-14) -# JACK2 isn't keyworded here -# bug #807616 -media-video/pipewire jack-client - -# Sam James <sam@gentoo.org> (2021-09-12) -# dev-ruby/asciidoctor isn't keyworded here -dev-util/ccache doc - -# David Seifert <soap@gentoo.org> (2021-09-04) -# dev-lang/go not keyworded here -sys-libs/libcap tools - -# Marek Szuba <marecki@gentoo.org> (2021-08-17) -# net-wireless/rtl-sdr not keyworded here -sys-apps/rng-tools rtlsdr - -# Michał Górny <mgorny@gentoo.org> (2021-07-25) -# PyQt5 and wxpython are not keyworded. -dev-python/matplotlib wxwidgets - -# Matt Turner <mattst88@gentoo.org> (2021-07-23) -# gui-libs/gtk is not keyworded -net-libs/gssdp gtk - -# Matt Turner <mattst88@gentoo.org> (2021-06-10) -# dev-python/django is not keyworded here -dev-python/diskcache test - -# Miroslav Šulc <fordfrog@gentoo.org> (2021-03-13) -# virtual/jdk isn't keyworded here -media-libs/rubberband jni - -# Sam James <sam@gentoo.org> (2021-03-11) -# media-libs/libavif isn't keyworded here -media-libs/gd avif -www-client/links avif -dev-lang/php avif - -# Akinori Hattori <hattya@gentoo.org> (2021-03-03) -# dev-lang/ruby is not keyworded ->=dev-libs/libutf8proc-2.6.0 test - -# Sam James <sam@gentoo.org> (2021-02-26) -# dev-libs/efl not keyworded here -# and is a desktop application mainly -# bug #773178 -app-crypt/pinentry efl - -# Joonas Niilola <juippis@gentoo.org> (2021-01-15) -# Dependency not keyworded on this arch. -app-text/enchant voikko - -# Arfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com> (2020-10-14) -# app-i18n/fcitx:4 not keyworded. -media-libs/libsdl2 fcitx4 - -# Sergei Trofimovich <slyfox@gentoo.org> (2020-09-18) -# media-libs/libilbc is not ported to ia64 -# nor is Qt -net-analyzer/wireshark gui ilbc - -# Matt Turner <mattst88@gentoo.org> (2020-08-11) -# No drivers on this architecture support Vulkan -media-libs/mesa vulkan vulkan-overlay zink - -# Michał Górny <mgorny@gentoo.org> (2020-06-14) -# Requires dev-python/networkx. -app-portage/nattka depgraph-order - -# Mikle Kolyada <zlogene@gentoo.org> (2020-06-08) -# clisp is keyworded on ia64 -app-text/texlive-core -xindy - -# Michał Górny <mgorny@gentoo.org> (2020-06-02) -# Avoid unkeyworded deps, we really need a minimal install -# for imagemagick. -media-gfx/inkscape cdr visio - -# James Le Cuirot <chewi@gentoo.org> (2020-04-23) -# Requires media-libs/mesa[llvm], which is masked. -dev-python/pyopengl test - -# Mikle Kolyada <zlogene@gentoo.org> (2020-04-20) -# dev-lang/ruby is not keyworded (a dep) -app-text/texlive context l10n_ja - -# Sergei Trofimovich <slyfox@gentoo.org> (2020-04-12) -# ruby-2.7 dropped ia64 support, mask dependencies requiring ruby. -# These pull in: -# - direct ruby dependency: -app-admin/augeas test -sys-block/thin-provisioning-tools test -# - Ruby-based test suite, with additional dependencies -app-text/htmltidy test -# - texlive japan modules: ruby runtime scripts -app-text/texlive l10n_ja context -# - net-libs/webkit-gtk: ruby build system -app-editors/emacs xwidgets -dev-util/geany-plugins markdown -gnome-extra/evolution-data-server oauth-gtk3 oauth-gtk4 -# - gnome-extra/sushi: depends on webkit-gtk -gnome-base/nautilus previewer -# - net-libs/gnome-online-accounts: depends on webkit-gtk -gnome-base/gvfs google -# app-text/libgepub depends on webkit-gtk. -xfce-base/tumbler epub - -# Thomas Deutschmann <whissi@gentoo.org> (2020-03-15) -# Mask USE=libtesseract, app-text/tesseract is not keyworded -# Mask USE=dav1d, media-libs/dav1d is not keyworded -# Mask USE=libaribb24, media-libs/aribb24 is not keyworded -media-video/ffmpeg dav1d libaribb24 libtesseract - -# Mart Raudsepp <leio@gentoo.org> (2020-03-01) -# Mask until app-text/gspell is keyworded -mail-client/evolution spell - -# Patrick McLean <chutzpah@gentoo.org> (2020-02-15) -# Mask until dev-libs/libfido2 is keyworded -net-misc/openssh security-key - -# Joonas Niilola <juippis@gentoo.org> (2020-02-08) -# Dependency not keyworded on this arch. -dev-libs/dbus-c++ ecore - -# David Seifert <soap@gentoo.org> (2020-01-26) -# media-libs/libkate is not keyworded on ia64 anymore -media-sound/vorbis-tools kate - -# Tomáš Mózes <hydrapolic@gmail.com> (2019-12-19) -# dev-libs/criterion is not keyworded yet -app-admin/syslog-ng test - -# Sergei Trofimovich <slyfox@gentoo.org> (2019-12-07) -# app-emulation/xen-tools is not keyworded on ia64. -sys-boot/grub grub_platforms_xen grub_platforms_xen-32 grub_platforms_xen-pvh - -# Mart Raudsepp <leio@gentoo.org> (2019-08-18) -# media-video/pipewire is not keyworded yet -x11-wm/mutter screencast - -# Matt Turner <mattst88@gentoo.org> (2019-08-08) -# Tomáš Mózes <hydrapolic@gmail.com> (2019-07-24) -# Unkeyworded dependency -app-admin/syslog-ng kafka - -# Sergei Trofimovich <slyfox@gentoo.org> (2019-05-21) -# No ia64 arch support for jit. Version 17 USE=debug -# required USE=jit. -dev-lang/spidermonkey jit - -# Mart Raudsepp <leio@gentoo.org> (2019-03-17) -# Unkeyworded media-libs/opencv dependency, bug #680656 -media-gfx/shotwell opencv - -# Sergei Trofimovich <slyfox@gentoo.org> (2018-10-13) -# USE=debug needs support for target-specific _FPU_MASK_IM. ia64 -# does not define those. -media-sound/lame debug - -# Thomas Deutschmann <whissi@gentoo.org> (2018-06-06) -# Needs sys-apps/fakechroot which isn't keyworded -app-arch/rpm test - -# Michał Górny <mgorny@gentoo.org> (2018-04-15) -# Unkeyworded dep masks moved from default/linux/ia64 tree. -mail-mta/exim redis - -# Sergei Trofimovich <slyfox@gentoo.org> (2018-03-18) -# Many unkeyworded rails deps, bug #650642 -net-analyzer/wireshark doc - -# Mart Raudsepp <leio@gentoo.org> (2018-01-08) -# mail-client/evolution[ytnef] requires net-mail/ytnef which is not keyworded -mail-client/evolution ytnef - -# Sergei Trofimovich <slyfox@gentoo.org> (2017-12-25) -# net-firewall/nftables[doc] requires dblatex which is not keyworded -net-firewall/nftables doc - -# Michał Górny <mgorny@gentoo.org> (2017-08-10) -# Both USE=fluidsynth and USE=timidity are masked in this profile. -media-libs/sdl-mixer midi - -# Michał Górny <mgorny@gentoo.org> (2017-08-08) -# Requires USE=seccomp that is masked in this profile. -net-libs/gnutls test-full - -# Michał Górny <mgorny@gentoo.org> (2017-08-07) -# Requires USE=dvd that is masked in this profile. -media-video/mplayer dvdnav - -# Michał Górny <mgorny@gentoo.org> (2017-08-07) -# Requires USE=v4l that is masked in this profile. -media-video/ffmpeg libv4l - -# Sergei Trofimovich <slyfox@gentoo.org> (2017-07-20) -# pulls in unkeyworded lapack -sci-libs/gdal armadillo - -# Sergei Trofimovich <slyfox@gentoo.org> (2017-06-17) -# Pulls in dev-db/redis which is not keyworded on ia64. -mail-filter/pyzor test - -# Sergei Trofimovich <slyfox@gentoo.org> (2017-06-10) -# media-libs/libilbc has not been ported to ia64, bug #610546 -media-video/ffmpeg libilbc - -# Sergei Trofimovich <slyfox@gentoo.org> (2017-06-06) -# Mask USE=rados for net-analyzer/rrdtool since sys-cluster/ceph is not -# keyworded (bug #549516) -net-analyzer/rrdtool rados - -# Jason Zaman <perfinion@gentoo.org> (2017-05-09) -# x11-libs/libXpresent is not keyworded on ia64 -xfce-base/xfwm4 xpresent - -# Pacho Ramos <pacho@gentoo.org> (2017-01-02) -# Don't keyword redis -dev-libs/hiredis test - -# Lars Wendler <polynomial-c@gentoo.org> (2016-11-17) -# jit not supported on ia64 (bug #600052). -dev-libs/libpcre2 jit - -# Christian Ruppert <idl0r@gentoo.org> (2016-10-14) -# dnstap USE masked due to missing keywords -net-dns/bind dnstap - -# Gilles Dartiguelongue <eva@gentoo.org> (2016-09-11) -# networkmanager USE masked due to missing keywords -gnome-extra/nm-applet teamd - -# Gilles Dartiguelongue <eva@gentoo.org> (2016-09-11) -# Opt-out of ofono support until there is a user request, -# see also pulseaudio/connman -net-misc/networkmanager ofono - -# Thomas Deutschmann <whissi@gentoo.org> (2016-08-26) -# Enable numa support on supported architectures -dev-db/mysql -numa -dev-db/percona-server -numa - -# Gilles Dartiguelongue <eva@gentoo.org> (2016-08-23) -# Missing keywords on media-libs/grilo - bug #521972 -media-sound/rhythmbox upnp-av - -# Alexandre Rostovtsev <tetromino@gentoo.org> (2016-06-28) -# Missing keywords on app-text/gspell - bug #587368 ->=app-text/evince-3.30 spell - -# Pacho Ramos <pacho@gentoo.org> (2016-01-31) -# Missing keywords, bug #560382 -media-video/ffmpeg snappy - -# Justin Lecher <jlec@gentoo.org> (2015-11-18) -# requires dev-python/restkit which requires -# dev-python/socketpool which requires dev-python/gevent which requires -# dev-python/greenlet which has not been ported -dev-python/wsgiproxy2 test -dev-python/pyquery test - -# Pacho Ramos <pacho@gentoo.org> (2015-11-15) -# Missing keywords ->=media-plugins/grilo-plugins-0.2.16 upnp-av - -# Davide Pesavento <pesa@gentoo.org> (2015-10-26) -# Tests require non-keyworded qt5 -dev-qt/qtchooser test - -# Brian Evans <grknight@gentoo.org> (2015-09-14) -# Mask new USE flags for mariadb which all arches do not yet have dependencies ->=dev-db/mariadb-10.1.0 innodb-snappy - -# Alexandre Rostovtsev <tetromino@gentoo.org> (2015-09-10) -# Requires wifi USE flag, which is masked for this arch -net-misc/networkmanager wext - -# Pacho Ramos <pacho@gentoo.org> (2015-09-06) -# Missing keywords -media-sound/pulseaudio ofono-headset -media-sound/pulseaudio-daemon ofono-headset - -# Pacho Ramos <pacho@gentoo.org> (2015-06-13) -# Missing keywords, bug #513108 -net-misc/spice-gtk smartcard webdav - -# Gilles Dartiguelongue <eva@gentoo.org> (2015-06-09) -# dev-lang/luajit lacks ia64 keyword, bug #551540 -dev-libs/libpeas lua - -# Alexis Ballier <aballier@gentoo.org> (2015-02-11) -# Missing ffmpeg deps, bug #510340 -media-video/ffmpeg gme ssh - -# Pacho Ramos <pacho@gentoo.org> (2014-01-10) -# Missing keywords -net-misc/networkmanager teamd - -# Christoph Junghans <junghans@gentoo.org> (2014-07-21) -# Missing keywords on sci-libs/libcerf (bug 517726) -sci-visualization/gnuplot libcerf - -# Pacho Ramos <pacho@gentoo.org> (2014-04-12) -# Missing keywords, bug #507490 -net-misc/modemmanager mbim - -# Mike Frysinger <vapier@gentoo.org> (2014-03-15) -# Various deps not ported to ia64. -dev-python/ipython nbconvert notebook - -# Pacho Ramos <pacho@gentoo.org> (2014-02-23) -# Needed dependencies cannot be installed on ia64, bug #498638 -dev-util/dbus-test-runner test - -# Pacho Ramos <pacho@gentoo.org> (2014-02-22) -# Missing keywords, bug #495250 ->=gnome-base/gnome-extra-apps-3.10 tracker - -# Pacho Ramos <pacho@gentoo.org> (2014-01-19) -# Missing keywords, bug #478254 -gnome-base/gnome classic extras - -# Pacho Ramos <pacho@gentoo.org> (2013-12-02) -# Missing keywords, bug #493156 -media-libs/libgphoto2 serial - -# Pacho Ramos <pacho@gentoo.org> (2013-07-20) -# Keywords pending, bug #476710 ->=gnome-base/gnome-extra-apps-3.8 games - -# Julian Ospald <hasufell@gentoo.org> (2013-03-31) -# depends on mono/monodevelop ->=net-irc/hexchat-2.9.4-r1 theme-manager - -# Alexandre Rostovtsev <tetromino@gentoo.org> (2013-01-31) -# remove mask when net-libs/libqmi is keyworded here -net-misc/modemmanager qmi - -# Alexandre Rostovtsev <tetromino@gentoo.org> (2013-01-22) -# remove mask if/when media-gfx/argyllcms is keywored here. -x11-misc/colord argyllcms extra-print-profiles - -# Agostino Sarubbo <ago@gentoo.org> (2012-12-18) -# kde is not stable, then no needs phonon backends -media-libs/phonon gstreamer vlc - -# Raúl Porcel <armin76@gentoo.org> (2012-05-28) -# Needs x11-misc/lightdm(which also requires some other deps) -x11-misc/xscreensaver new-login - -# Alexey Shvetsov <alexxy@gentoo.org> (2011-12-17) -# Mask use numa for openmpi -sys-cluster/openmpi openmpi_fabrics_knem openmpi_fabrics_ofed openmpi_ofed_features_rdmacm openmpi_ofed_features_control-hdr-padding openmpi_ofed_features_udcm openmpi_ofed_features_dynamic-sl - -# Raúl Porcel <armin76@gentoo.org> (2011-11-05) -# jit not supported on ia64 -dev-libs/libpcre jit - -# Tomáš Chvátal <scarabeus@gentoo.org> (2011-04-04) -# Needs sci-libs/umfpack keyworded. Bug #361947. -media-libs/gegl umfpack - -# Sebastian Pipping <sping@gentoo.org> (2011-02-22) -# No media-sound/lilypond here, yet (bug #356069) -app-text/asciidoc test - -# Diego Elio Pettenò <flameeyes@gentoo.org> (2010-12-17) -# needs sys-libs/libcap-ng that is masked right now -sys-apps/smartmontools caps - -# Raúl Porcel <armin76@gentoo.org> (2010-06-26) -# custom-optimization doesn't work on ia64 -www-client/seamonkey custom-optimization - -# Raúl Porcel <armin76@gentoo.org> -# Keep deps minimal -x11-wm/fvwm lock - -# Raúl Porcel <armin76@gentoo.org> (2008-07-07) -# Make clisp deps minimal -dev-lisp/clisp hyperspec svm - -# missing keywords -media-plugins/gst-plugins-meta dts dv lame libvisual modplug jack taglib vcd wavpack - -# Marius Brehler <marfbre@linux.sungazer.de> (2015-08-13) -# missing keyword ->=sci-misc/boinc-7.4.42-r1 X diff --git a/profiles/arch/ia64/parent b/profiles/arch/ia64/parent deleted file mode 100644 index e234bf836e61..000000000000 --- a/profiles/arch/ia64/parent +++ /dev/null @@ -1,2 +0,0 @@ -../base -../../features/wd40 diff --git a/profiles/arch/ia64/use.force b/profiles/arch/ia64/use.force deleted file mode 100644 index 1dfcca5c0949..000000000000 --- a/profiles/arch/ia64/use.force +++ /dev/null @@ -1,2 +0,0 @@ -# Force the flag which corresponds to ARCH. -ia64 diff --git a/profiles/arch/ia64/use.mask b/profiles/arch/ia64/use.mask deleted file mode 100644 index 0b0b6ab04b62..000000000000 --- a/profiles/arch/ia64/use.mask +++ /dev/null @@ -1,211 +0,0 @@ -# Copyright 1999-2024 Gentoo Authors -# Distributed under the terms of the GNU General Public License v2 - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-02-20) -openexr - -# Unmask the flag which corresponds to ARCH. --ia64 - -# matoro <matoro_gentoo@matoro.tk> (2023-06-17) -# media-libs/libheif is not keyworded here -heif - -# Sam James <sam@gentoo.org> (2022-07-21) -# Untested. -ieee1394 - -# Matt Turner <mattst88@gentoo.org> (2022-02-21) -# app-crypt/tpm2-tss is not keyworded here -tpm - -# James Le Cuirot <chewi@gentoo.org> (2021-08-10) -# media-video/pipewire is not keyworded. Bug #807616. -pipewire - -# Arfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com> (2021-04-01) -# sys-libs/llvm-libunwind not supported on IA64. -llvm-libunwind - -# Matt Turner <mattst88@gentoo.org> (2020-07-01) -# Unlikely. -vulkan - -# James Le Cuirot <chewi@gentoo.org> (2020-05-10) -# media-libs/allegro is not keyworded. -allegro - -# Sergei Trofimovich <slyfox@gentoo.org> (2020-04-12) -# ruby-2.7 dropped ia64 support, mask ruby in Gentoo. -ruby -# - net-libs/gnome-online-accounts: depend on net-libs/webkit-gtk -gnome-online-accounts - -# Sergei Trofimovich <slyfox@gentoo.org> (2017-06-17) -# There is no luajit support on ia64. Bug #554376 -lua_single_target_luajit -lua_targets_luajit -luajittex - -# No hardware to test by the team -3dfx -bluetooth -bluray -dvb -dvd -gphoto2 -gps -ios -ipod -lirc -pcmcia -pda -scanner -sms -v4l -wifi - -# Hardware not available on ia64 -apm -battery -lm-sensors - -# Stuff that doesn't work on ia64, or not tested -afs -djbfft -jack -lqr -capi -lensfun -kde -kwallet -metalink -upnp -fdk -valgrind -mongodb -pgm -scim - -# Stuff we don't want -antlr -lasi -mpi -octave -timidity -semantic-desktop -fits -libburn -topal -flite -sctp -bs2b -tokyocabinet -ots -vaapi -librtmp -rtmp -vpx -frei0r -lpsol -ladspa -devil -gts -clang -redis - -# Stuff that doesn't compile on ia64 -diet -emf -mono -xemacs - -# Other - -# Raúl Porcel <armin76@gentoo.org> (2014-08-20) -# Upstream drops support on ia64 from 4.0 onwards, bug #430352 -ocamlopt - - -# Raúl Porcel <armin76@gentoo.org> (2011-04-23) -# Needs to be tested -video_cards_nouveau - -# Samuli Suominen <ssuominen@gentoo.org> (2009-12-02) -# This will need media-sound/musepack-tools -musepack - -# Raúl Porcel <armin76@gentoo.org> (2009-03-20) -# Current webkit segfaults -webkit - -# Ben de Groot <yngwin@gentoo.org> (2009-02-11) -# Both dev-qt/qtphonon and media-sound/phonon are unkeyworded -phonon - -# see email to gentoo-dev with subject "use.mask and PHP5's crazy IUSE" -# Dated Sat, 31 Jul 2004 14:49:28 -0700, from robbat2@gentoo.org -# all of these are binary-only, and not presently available on this -# architecture. -qdbm - -# James Le Cuirot <chewi@gentoo.org> (2015-07-11) -# We don't support java on ia64. -java -pdfannotextractor - -# Matt Turner <mattst88@gentoo.org> -# llvm is not keyworded -video_cards_amdgpu -video_cards_radeonsi - -# Diego Pettenò <flameeyes@gentoo.org> (2006-12-06) -# Mask ALSA drivers for ISA cards -alsa_cards_msnd-pinnacle -alsa_cards_sb16 -alsa_cards_sbawe -alsa_cards_sscape -alsa_cards_wavefront - -# Diego Elio Pettenò <flameeyes@gentoo.org> (2012-08-21) -# IPMI is only implemented for x86, amd64 and ia64 --ipmi - -# Michael Sterrett <mr_bones_@gentoo.org> (2012-08-24) -# media-sound/fluidsynth isn't keyworded -fluidsynth - -# Alexandre Rostovtsev <tetromino@gentoo.org> (2012-12-31) -# net-misc/connman is not keyworded, bug 348308 -connman - -# Alexandre Rostovtsev <tetromino@gentoo.org> (2012-12-31) -# media-libs/xine-lib is not keyworded -xine - -template-haskell - -# toolkit for nvidia binary drivers -cg - -# Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org> (2013-08-22) -# virtual/opencl is not keyworded -opencl - -# Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org> (2013-11-10) -# sys-devel/llvm s not keyworded, bug #320221 -llvm - -# sys-libs/libseccomp has not been ported to this arch yet #524148 -seccomp - -# need to test sys-cluster/glusterfs #519618 -glusterfs - -# need to test ceph and friends #519618 -rbd - -# Ben de Groot <yngwin@gentoo.org> (2015-02-01) -# please remove when keyworded -qt5 -qt6 diff --git a/profiles/arch/loong/package.use.mask b/profiles/arch/loong/package.use.mask index efb2472587f7..0438cea893d3 100644 --- a/profiles/arch/loong/package.use.mask +++ b/profiles/arch/loong/package.use.mask @@ -1,16 +1,85 @@ # Copyright 2022-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# WANG Xuerui <xen0n@gentoo.org> (2024-09-27) +# media-libs/libilbc needs porting +media-video/ffmpeg libilbc +net-analyzer/wireshark ilbc +net-libs/pjproject ilbc +net-misc/asterisk ilbc +net-voip/yate ilbc + +# Paul Zander <negril.nx+gentoo@gmail.com> (2024-09-14) +# needs re-keywording and clean-up of media-libs/opencollada +media-libs/assimp collada + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-13) +# dev-python/pyside6 isn't keyworded here +dev-python/QtPy pyside6 + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-07) +# kde-plasma/plasma-workspace:6 is not keyworded +virtual/notification-daemon kde + +# Sam James <sam@gentoo.org> (2024-08-31) +# dnstap USE masked due to missing keywords +net-dns/bind dnstap + +# Sam James <sam@gentoo.org> (2024-08-23) +# dev-util/bpftool and/or sys-devel/bpf-toolchain not keyworded here +sys-apps/systemd bpf + +# WANG Xuerui <xen0n@gentoo.org> (2024-08-22) +# dev-lang/spidermonkey gained JIT support for loong since version 107, +# but the nearest packaged version is 115. +>=dev-lang/spidermonkey-115 -jit + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-08-19) +# kde-apps/kdesdk-thumbnailers is not yet keyworded +kde-apps/thumbnailers gettext + +# Hans de Graaff <graaff@gentoo.org> (2024-08-18) +# Requires large parts of dev-ruby/rails to be keyworded +dev-ruby/minitest-hooks test + +# Matt Jolly <kangie@gentoo.org> (2024-08-14) +# QUIC dependencies are not keyworded +net-misc/curl http3 quic curl_quic_openssl curl_quic_ngtcp2 + +# Ulrich Müller <ulm@gentoo.org> (2024-08-03) +# Needs dev-libs/openspecfun which is not yet keyworded +sci-visualization/gnuplot amos + +# Michał Górny <mgorny@gentoo.org> (2024-07-24) +# Full testing requires www-client/firefox. +dev-python/selenium test-rust + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-07-01) +# USE="kf6compat,kaccounts" depends on kde-frameworks/purpose:6[webengine] +# which is package.use.mask'ed on these arches. We cannot mask the +# combination specifically but in reality kaccounts is useless without +# additional dev-qt/qtwebengine revdeps. +kde-frameworks/purpose:5 kaccounts + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-15) +# Requires unkeyworded dev-qt/qtwebengine (and revdeps) +kde-plasma/plasma-nm openconnect + +# Sam James <sam@gentoo.org> (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +app-crypt/pinentry qt6 +app-office/libreoffice qt6 + +# WANG Xuerui <xen0n@gentoo.org> (2024-06-03) +# Requires arch-specific code in python (relocs handling), in addition to +# sys-devel/{clang,llvm}. +dev-lang/python jit + # WANG Xuerui <xen0n@gentoo.org> (2024-05-16) # dev-ruby/asciidoctor has some really heavy deps, and is not keyworded on # loong yet. net-misc/chrony html -# WANG Xuerui <xen0n@gentoo.org> (2024-04-04) -# dev-qt/qtwebengine is not available on loong (no upstream Chromium support, -# patchset not integrated yet) ->=kde-apps/kdecore-meta-24 handbook - # Sam James <sam@gentoo.org> (2024-03-27) # No rust-bin available for profiler <virtual/rust-1.73.0 profiler @@ -58,6 +127,7 @@ dev-db/postgresql llvm # Patrick McLean <chutzpah@gentoo.org> (2023-10-03) # sys-apps/s6-linux-init has not been tested on this arch sys-apps/openrc s6 +sys-apps/openrc-navi s6 # WANG Xuerui <xen0n@gentoo.org> (2023-09-29) # no luajit for now @@ -85,13 +155,13 @@ dev-python/requests-cache test # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-08-30) # Avoid having to keyword more Qt deps dev-python/pyside2 3d datavis location scxml +dev-python/pyside6 3d location scxml # WANG Xuerui <xen0n@gentoo.org> (2023-07-26) # no llvm:15 or lld:16 on loong app-office/libreoffice clang <dev-db/postgresql-16 llvm <dev-lang/rust-1.73.0 wasm -dev-lang/spidermonkey clang lto # Ionen Wolkens <ionen@gentoo.org> (2023-07-26) # MPV currently[1] has no plans to support >=lua5-3 making luajit @@ -123,6 +193,7 @@ dev-util/perf python # # See https://github.com/openssl/openssl/issues/21340 >=dev-libs/openssl-3.1 asm +>=dev-libs/openssl-3.2 -asm # WANG Xuerui <xen0n@gentoo.org> (2023-06-03) # sys-cluster/knem not keyworded yet @@ -147,11 +218,6 @@ sys-kernel/installkernel -systemd-boot -ukify -uki # dev-python/pyopengl fails tests dev-python/sympy opengl -# WANG Xuerui <xen0n@gentoo.org> (2023-04-16) -# dev-python/aesara doesn't work on loong yet (due to hardcoding -m64 in its -# cc invocations) -dev-python/sympy aesara - # WANG Xuerui <xen0n@gentoo.org> (2022-12-06) # dev-cpp/glog fails tests, needs checking media-libs/opencv glog contribsfm @@ -200,7 +266,7 @@ app-cdr/brasero tracker # time being dev-cpp/libcmis man media-libs/opencv tesseract -media-video/ffmpeg libilbc libtesseract +media-video/ffmpeg libtesseract # WANG Xuerui <xen0n@gentoo.org> (2022-12-05) # sys-auth/sssd isn't keyworded here yet @@ -264,6 +330,7 @@ media-plugins/gst-plugins-meta libvisual >=sys-libs/compiler-rt-sanitizers-17.0.0_pre20230705 -dfsan >=sys-libs/compiler-rt-sanitizers-17.0.0_pre20230717 -profile -xray >sys-libs/compiler-rt-sanitizers-17.0.0_pre20230717 -libfuzzer +>=sys-libs/compiler-rt-sanitizers-19 -cfi # WANG Xuerui <xen0n@gentoo.org> (2022-07-08) # virtual/{jdk,jre} is not available on loong yet. diff --git a/profiles/arch/loong/use.mask b/profiles/arch/loong/use.mask index e0e50583c2ab..697686ae9aed 100644 --- a/profiles/arch/loong/use.mask +++ b/profiles/arch/loong/use.mask @@ -1,6 +1,10 @@ # Copyright 2022-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James <sam@gentoo.org> (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +kf6compat + # Michał Górny <mgorny@gentoo.org> (2024-02-05) # LLVM slots without keywords. llvm_slot_15 @@ -39,6 +43,7 @@ nas # WANG Xuerui <xen0n@gentoo.org> (2022-11-01) # qtwebengine isn't available on loong yet +pdfium webengine # Unmask the flag which corresponds to ARCH. diff --git a/profiles/arch/m68k/package.mask b/profiles/arch/m68k/package.mask new file mode 100644 index 000000000000..c9a806f67556 --- /dev/null +++ b/profiles/arch/m68k/package.mask @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Andreas K. Hüttel <dilfridge@gentoo.org> +# Requires 32bit alignment, so we mask it for the moment +dev-lang/python:3.13 diff --git a/profiles/arch/m68k/package.use.mask b/profiles/arch/m68k/package.use.mask index 5dcd046b960f..5351d18a96b0 100644 --- a/profiles/arch/m68k/package.use.mask +++ b/profiles/arch/m68k/package.use.mask @@ -1,6 +1,11 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# James Le Cuirot <chewi@gentoo.org> (2024-07-13) +# These tests pass, but the net-misc/memcached tests do not, so we should not +# keyword memcached-related packages such as dev-python/pylibmc. +dev-python/pytest-services test + # Michał Górny <mgorny@gentoo.org> (2024-05-08) # Requires sys-devel/{clang,llvm}:16. dev-lang/python jit diff --git a/profiles/arch/m68k/use.mask b/profiles/arch/m68k/use.mask index 25d4d1977e96..120f9403a7de 100644 --- a/profiles/arch/m68k/use.mask +++ b/profiles/arch/m68k/use.mask @@ -157,3 +157,7 @@ slang tcl tk xemacs + +# Andreas K. Hüttel <dilfridge@gentoo.org> +# Requires 32bit alignment, so we mask it for the moment +python_targets_python3_13 diff --git a/profiles/arch/mips/mips64/multilib/package.mask b/profiles/arch/mips/mips64/multilib/package.mask new file mode 100644 index 000000000000..aff67b6b78b8 --- /dev/null +++ b/profiles/arch/mips/mips64/multilib/package.mask @@ -0,0 +1,5 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Has broken dependency specs for multilib... +sys-boot/arcload diff --git a/profiles/arch/mips/mipsel/mips64el/multilib/package.mask b/profiles/arch/mips/mipsel/mips64el/multilib/package.mask new file mode 100644 index 000000000000..aff67b6b78b8 --- /dev/null +++ b/profiles/arch/mips/mipsel/mips64el/multilib/package.mask @@ -0,0 +1,5 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Has broken dependency specs for multilib... +sys-boot/arcload diff --git a/profiles/arch/mips/mipsel/o32/package.mask b/profiles/arch/mips/mipsel/o32/package.mask index 02c903e795a5..3eba8c7538c5 100644 --- a/profiles/arch/mips/mipsel/o32/package.mask +++ b/profiles/arch/mips/mipsel/o32/package.mask @@ -1,6 +1,10 @@ # Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas K. Hüttel <dilfridge@gentoo.org> (2024-09-10) +# Mask on o32 until we've fixed kgcc64 +sys-boot/arcload + # Joshua Kinard <kumba@gentoo.org> (2024-02-27) # app-arch/lrzip-next does not support 32-bit arches (#925548) app-arch/lrzip-next diff --git a/profiles/arch/mips/o32/package.mask b/profiles/arch/mips/o32/package.mask index 02c903e795a5..3eba8c7538c5 100644 --- a/profiles/arch/mips/o32/package.mask +++ b/profiles/arch/mips/o32/package.mask @@ -1,6 +1,10 @@ # Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas K. Hüttel <dilfridge@gentoo.org> (2024-09-10) +# Mask on o32 until we've fixed kgcc64 +sys-boot/arcload + # Joshua Kinard <kumba@gentoo.org> (2024-02-27) # app-arch/lrzip-next does not support 32-bit arches (#925548) app-arch/lrzip-next diff --git a/profiles/arch/mips/package.mask b/profiles/arch/mips/package.mask index ddd3628b28a4..f96d719f45e3 100644 --- a/profiles/arch/mips/package.mask +++ b/profiles/arch/mips/package.mask @@ -1,6 +1,13 @@ -# Copyright 2006-2023 Gentoo Authors +# Copyright 2006-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Arthur Zamarin <arthurzam@gentoo.org> (2024-09-08) +# requires <llvm-18 +dev-lang/spidermonkey:102 +=sys-auth/polkit-123 +=dev-lang/rust-1.71.1 +=virtual/rust-1.71.1-r2 + # matoro <matoro_gentoo@matoro.tk> (2023-12-15) # Broken on BE and no way to test on LE, mask for now # https://github.com/libjxl/libjxl/issues/2433 @@ -21,5 +28,4 @@ media-libs/libaom gui-libs/gtk:4 # Mask pam_ldap and nss_ldap - openldap dep missing. -sys-auth/pam_ldap sys-auth/nss_ldap diff --git a/profiles/arch/mips/package.use.mask b/profiles/arch/mips/package.use.mask index a9717ab8aad9..d7cac0a393f7 100644 --- a/profiles/arch/mips/package.use.mask +++ b/profiles/arch/mips/package.use.mask @@ -1,6 +1,112 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Arthur Zamarin <arthurzam@gentoo.org> (2024-09-08) +# Packages needing dev-python/selenium. +dev-python/aiohttp-cors test +dev-python/django test + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-09-08) +# requires <llvm-18 +dev-db/postgresql llvm_slot_15 llvm_slot_16 llvm_slot_17 +media-libs/mesa llvm_slot_15 llvm_slot_16 llvm_slot_17 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-09-08) +# needs libgdata[gnome-online-accounts], depends on net-libs/webkit-gtk +gnome-base/gvfs google test + +# Michał Górny <mgorny@gentoo.org> (2024-09-08) +# libcxx is broken on mips, https://bugs.gentoo.org/939297#c2 +sys-devel/clang-common default-libcxx +sys-devel/clang-runtime libcxx + +# Hans de Graaff <graaff@gentoo.org> (2024-09-08) +# Requires large parts of dev-ruby/rails to be keyworded +dev-ruby/minitest-hooks test + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-09-07) +# gui-libs/gtk:4 is not keyworded here +app-crypt/gcr:4 gtk +>=app-crypt/pinentry-1.3.0 gtk + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-09-06) +# media-libs/vidstab is not keyworded +media-video/ffmpeg vidstab + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-09-06) +# media-video/rav1e isn't keyworded here +media-libs/libavif rav1e + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-26) +# dev-util/bpftool and/or sys-devel/bpf-toolchain not keyworded here +sys-apps/systemd bpf +media-libs/libv4l bpf + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-26) +# dev-ruby/thor not keyworded here +app-text/htmltidy test + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-25) +# simplify the dep tree +app-admin/syslog-ng amqp grpc kafka mongodb smtp test +app-crypt/pinentry efl +app-text/doxygen gui +dev-build/cmake gui +dev-db/mysql cjk +dev-db/percona-server cjk +dev-libs/libisoburn frontend-optional +dev-python/uvicorn test-rust +dev-util/glade gjs +dev-util/pkgcheck emacs +dev-util/ragel doc +dev-vcs/git doc subversion +mail-mta/postfix mongodb +media-sound/liblc3 test +net-misc/rsync rrsync +net-firewall/nftables doc +dev-util/ccache doc + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-25) +# Some optional emacs dependencies are not keyworded. +app-editors/emacs gui mailutils + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-25) +# net-libs/webkit-gtk has no mips keywords +dev-util/glade webkit + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-25) +# alternatives not available on mips +app-alternatives/awk nawk +app-alternatives/bc gh +app-alternatives/lex reflex + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-07-05) +# Avoid unkeyworded media-gfx/libimagequant +dev-python/pillow imagequant + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-07-04) +# kde-frameworks/kservice not keyworded here +x11-misc/xdg-utils plasma + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-07-01) +# simplify the dep tree +dev-python/click doc +dev-python/cython doc +dev-python/flake8 doc +dev-python/flask doc +dev-python/flit doc +dev-python/greenlet doc +dev-python/outcome doc +dev-python/pytest-cov doc +dev-python/pytest-trio doc +dev-python/stevedore doc +dev-python/sphinx-autodoc-typehints test +dev-util/maturin doc + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-29) +# media-libs/libplacebo is not keyworded +media-video/ffmpeg libplacebo + # Michał Górny <mgorny@gentoo.org> (2024-05-08) # Requires sys-devel/{clang,llvm}:16. dev-lang/python jit @@ -55,7 +161,7 @@ net-analyzer/rrdtool rados # matoro <matoro_gentoo@matoro.tk> (2023-11-22) # Qt 5 is not keyworded here -app-admin/setools X +app-admin/setools X test # matoro <matoro_gentoo@matoro.tk> (2023-11-22) # Qt 5 is not keyworded here @@ -82,7 +188,7 @@ app-alternatives/ninja samurai # matoro <matoro_gentoo@matoro.tk> (2023-06-18) # app-i18n/fcitx:4 not keyworded here -media-libs/libsdl2 fcitx4 +media-libs/libsdl2 fcitx # Sam James <sam@gentoo.org> (2023-06-18) # Qt 5 not keyworded here @@ -143,14 +249,6 @@ dev-libs/libgudev test # dev-python/django is not keyworded here dev-python/diskcache test -# Joshua Kinard <kumba@gentoo.org> (2021-05-20) -# mask USE 'test' on MIPS for setuptools and jaraco-path due to -# the very deep dependency chain that is enabled. Will unmask -# on a future date. -# Bug #774216 -dev-python/jaraco-path test -dev-python/setuptools test - # Sam James <sam@gentoo.org> (2021-02-06) # media-sound/sndio is not yet keyworded here # bug #769098, bug #769122 @@ -169,7 +267,7 @@ app-text/enchant voikko # Matt Turner <mattst88@gentoo.org> (2020-08-11) # No drivers on this architecture support Vulkan -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa vulkan vulkan-overlay zink video_cards_zink # Michał Górny <mgorny@gentoo.org> (2018-01-23) # USE=collab requires unkeyworded net-libs/loudmouth & dev-cpp/asio. @@ -191,10 +289,6 @@ media-libs/sdl-mixer midi # Moved from use.mask since they are flags local to one package. sys-kernel/mips-sources -ip27 -ip28 -ip30 -# Michał Górny <mgorny@gentoo.org> (2017-08-08) -# Requires USE=opencl that is masked in this profile. -net-misc/bfgminer adl lm-sensors - # Mart Raudsepp <leio@gentoo.org> (2017-05-27) # app-pda/libimobiledevice, app-pda/libplist and co not tested sys-power/upower ios diff --git a/profiles/arch/mips/use.mask b/profiles/arch/mips/use.mask index a92babc25175..da6c9e7c86fe 100644 --- a/profiles/arch/mips/use.mask +++ b/profiles/arch/mips/use.mask @@ -1,6 +1,14 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-26) +# media-libs/libheif is not keyworded here +heif + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-26) +# media-libs/libjxl is not keyworded here +jpegxl + # Unmask the flag which corresponds to ARCH. -mips @@ -81,7 +89,6 @@ cblas-external # Samuli Suominen <ssuominen@gentoo.org> # Media cannot be tested for MIPS at the moment. -# media-libs/libmpeg3 # media-libs/portaudio # dev-libs/libcdio # media-libs/musicbrainz diff --git a/profiles/arch/powerpc/package.mask b/profiles/arch/powerpc/package.mask index 09ee3b610ae3..9c9ec8296565 100644 --- a/profiles/arch/powerpc/package.mask +++ b/profiles/arch/powerpc/package.mask @@ -1,6 +1,17 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# matoro <matoro_gentoo@matoro.tk> (2024-07-09) +# Known to crash on boot for at least ppc64le w/ 64k kernel, +# possibly other powerpc arches. Masking out of caution. +# https://lore.kernel.org/stable/20240705203413.wbv2nw3747vjeibk@altlinux.org/ +=sys-kernel/gentoo-kernel-6.6.37 +=sys-kernel/gentoo-kernel-bin-6.6.37 +=sys-kernel/gentoo-sources-6.6.37 +=sys-kernel/vanilla-kernel-6.6.37 +=sys-kernel/vanilla-sources-6.6.37 +=virtual/dist-kernel-6.6.37 + # Georgy Yakovlev <gyakovlev@gentoo.org> (2020-09-22) # criu does not work on ppc64be and ppc32 sys-process/criu diff --git a/profiles/arch/powerpc/package.use.mask b/profiles/arch/powerpc/package.use.mask index 8ae2a829a2fd..c2e463edbe03 100644 --- a/profiles/arch/powerpc/package.use.mask +++ b/profiles/arch/powerpc/package.use.mask @@ -1,6 +1,14 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner <asturm@gentoo.org> (2024-08-19) +# kde-apps/kdesdk-thumbnailers is not yet keyworded +kde-apps/thumbnailers gettext + +# Thomas Bettler <thomas.bettler@gmail.com> (2024-06-10) +# requires dev-libs/apache-arrow which is net yet keyworded +sci-libs/gdal parquet + # Arthur Zamarin <arthurzam@gentoo.org> (2024-05-13) # Requires dev-util/shelltestrunner app-arch/mt-st test @@ -17,6 +25,7 @@ media-video/mpv -lua_single_target_lua5-1 lua_single_target_luajit # Andreas Sturmlechner <asturm@gentoo.org> (2024-03-24) # Requires unkeyworded dev-qt/qtwebengine (and revdeps) kde-apps/kleopatra pim +kde-plasma/plasma-nm openconnect net-irc/quassel urlpreview net-p2p/ktorrent rss @@ -62,6 +71,7 @@ media-libs/libaom cpu_flags_ppc_vsx # Patrick McLean <chutzpah@gentoo.org> (2023-10-03) # sys-apps/s6-linux-init has not been tested on this arch sys-apps/openrc s6 +sys-apps/openrc-navi s6 # Georgy Yakovlev <gyakovlev@gentoo.org> (2023-09-21) # dtrace/systemtap not availabie on ppc platform for jdk @@ -76,6 +86,7 @@ dev-db/spatialite rttopo # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-08-30) # Avoid keywordming more Qt stuff dev-python/pyside2 3d datavis scxml +dev-python/pyside6 3d scxml # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-03-07) # nbval/nbclassic docs require pandoc which is not keyworded here yet @@ -104,9 +115,9 @@ app-admin/conky doc media-sound/snd notcurses # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2022-09-23) -# Only PyQt5 is keyworded on pcc64 at the moment. +# pyside2 is not keyworded on powerpc at the moment. # Mask the other Qt4Python implementations -dev-python/QtPy pyside2 pyqt6 pyside6 +dev-python/QtPy pyside2 pyside6 # Matt Turner <mattst88@gentoo.org> (2022-04-18) # app-text/nuspell is not keyworded @@ -182,10 +193,6 @@ www-client/chromium widevine # requires media-libs/sdl2-image, which is not yet keyworded app-emulation/qemu sdl-image -# Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-25) -# requires fwupd, which is not yet keyworded -kde-plasma/discover firmware - # Rick Farina <zerochaos@gentoo.org> (2020-01-03) # ubertooth needs net-libs/libbtbb and net-wireless/ubertooth which aren't keyworded net-wireless/kismet ubertooth @@ -270,14 +277,6 @@ app-i18n/fcitx-libpinyin dictionary-manager # Requires java app-forensics/sleuthkit java -# Michał Górny <mgorny@gentoo.org> (2017-08-10) -# Requires USE=ipmi which is masked in this profile. -sys-power/nut ups_drivers_nut-ipmipsu - -# Michał Górny <mgorny@gentoo.org> (2017-08-08) -# Requires USE=opencl that is masked in this profile. -net-misc/bfgminer adl lm-sensors - # Michał Górny <mgorny@gentoo.org> (2017-03-24) # libcxx fails to compile on ppc*, #595744. sys-devel/clang-common default-libcxx @@ -296,7 +295,6 @@ dev-db/percona-server -numa # Requires unkeyworded dependencies dev-vcs/subversion kwallet net-irc/quassel kde -net-libs/libproxy kde sys-auth/polkit kde sys-block/gparted kde virtual/notification-daemon kde diff --git a/profiles/arch/powerpc/package.use.stable.mask b/profiles/arch/powerpc/package.use.stable.mask index b7d60aceea32..5d6791cd8cd2 100644 --- a/profiles/arch/powerpc/package.use.stable.mask +++ b/profiles/arch/powerpc/package.use.stable.mask @@ -17,6 +17,11 @@ #--- END OF EXAMPLES --- +# Joonas Niilola <juippis@gentoo.org> (2024-05-28) +# Depchain-destabilization on ppc (libsecret[test-rust] -> gjs -> spidermonkey) +app-crypt/libsecret test-rust +dev-util/glade gjs + # Mart Raudsepp <leio@gentoo.org> (2023-12-25) # Libei not stable here yet x11-base/xwayland libei @@ -40,7 +45,7 @@ media-sound/jack2 ieee1394 # Sam James <sam@gentoo.org> (2020-07-30) # vulkan-loader and glslang are not yet stable on ppc -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa video_cards_zink vulkan vulkan-overlay zink # Sergei Trofimovich <slyfox@gentoo.org> (2019-12-12) # Needs stable net-libs/webkit-gtk, bug #684702 diff --git a/profiles/arch/powerpc/ppc32/package.use.mask b/profiles/arch/powerpc/ppc32/package.use.mask index 8b5f9711f300..bf02a9359c47 100644 --- a/profiles/arch/powerpc/ppc32/package.use.mask +++ b/profiles/arch/powerpc/ppc32/package.use.mask @@ -1,6 +1,29 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-04) +# KF6 and media-libs/phonon have dropped ppc keyword +app-office/texstudio video +net-irc/kvirc phonon + +# Matt Jolly <kangie@gentoo.org> (2024-08-14) +# QUIC dependencies are not keyworded +net-misc/curl http3 quic curl_quic_openssl curl_quic_ngtcp2 + +# Michał Górny <mgorny@gentoo.org> (2024-07-24) +# Full testing requires www-client/firefox. +dev-python/selenium test-rust + +# Sam James <sam@gentoo.org> (2024-07-03) +# kde-frameworks/kservice not keyworded here +x11-misc/xdg-utils plasma + +# Ionen Wolkens <ionen@gentoo.org> (2024-07-02) +# Needs dev-qt/qtquick3d:6 which itself needs media-libs/assimp that +# is no longer keyworded here and currently fails tests (bug #935313). +dev-python/PyQt6 quick3d +dev-qt/qtmultimedia:6 qml + # Sam James <sam@gentoo.org> (2024-05-19) # media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 media-gfx/graphicsmagick jpeg2k @@ -13,10 +36,6 @@ sys-devel/clang-runtime openmp # Fails tests, potential false negatives #911402 app-antivirus/clamav system-mspack -# Sam James <sam@gentoo.org> (2024-01-17) -# The generated code is too large and it takes ages to build, bug #922249. -dev-python/mypy native-extensions - # Marek Szuba <marecki@gentoo.org> (2024-04-24) # Sam James <sam@gentoo.org> (2024-01-05) # sys-apps/keyutils not stable here, because of test failures. bug #636252 @@ -25,7 +44,6 @@ app-crypt/mit-krb5 keyutils app-emulation/qemu keyutils net-fs/cifs-utils ads creds pam net-fs/samba ads -sys-auth/sssd keyutils >=sys-libs/libblockdev-3.0.0 cryptsetup sys-libs/libnvme keyutils @@ -40,10 +58,6 @@ dev-python/nbconvert test dev-perl/DBD-mysql mysql # Sam James <sam@gentoo.org> (2023-09-22) -# Qt 6 not keyworded here. -dev-build/cmake gui - -# Sam James <sam@gentoo.org> (2023-09-22) # sys-apps/flatpak is not keyworded here sys-apps/xdg-desktop-portal flatpak @@ -190,7 +204,6 @@ dev-python/pyopengl test # Andrey Utkin <andrey_utkin@gentoo.org> (2020-03-11) # USE=bpf depends on sys-devel/clang which is not keyworded on ppc. media-libs/libv4l bpf -media-tv/v4l-utils bpf # Matthew Thode <prometheanfire@gentoo.org> (2020-02-17) # Mask until net-analyzer/icinga2 is keyworded diff --git a/profiles/arch/powerpc/ppc64/32ul/make.defaults b/profiles/arch/powerpc/ppc64/32ul/make.defaults deleted file mode 100644 index 116e08896a17..000000000000 --- a/profiles/arch/powerpc/ppc64/32ul/make.defaults +++ /dev/null @@ -1,16 +0,0 @@ -# Copyright 1999-2014 Gentoo Foundation -# Distributed under the terms of the GNU General Public License v2 - -# All extra USE/etc should be specified in sub-profiles. -# DO NOT POLLUTE USE ON THIS PROFILE. - -ARCH="ppc" -CHOST="powerpc-unknown-linux-gnu" -ABI="ppc" -MULTILIB_ABIS="ppc" -DEFAULT_ABI="ppc" -ACCEPT_KEYWORDS="${ARCH} -ppc64" - -# Michał Górny <mgorny@gentoo.org> (2014-06-27) -# Make the ABI flag implicit for compatibility with native ebuilds. -IUSE_IMPLICIT="abi_ppc_32 -abi_ppc_64" diff --git a/profiles/arch/powerpc/ppc64/32ul/package.mask b/profiles/arch/powerpc/ppc64/32ul/package.mask deleted file mode 100644 index 48fd10c7bac9..000000000000 --- a/profiles/arch/powerpc/ppc64/32ul/package.mask +++ /dev/null @@ -1,7 +0,0 @@ -# Copyright 1999-2022 Gentoo Authors -# Distributed under the terms of the GNU General Public License v2 - -# Sam James <sam@gentoo.org> (2022-01-18) -# No bootstrap binary available on big endian PPC64 right now -# But there is one for PPC (big endian). --dev-lisp/sbcl diff --git a/profiles/arch/powerpc/ppc64/32ul/package.use.mask b/profiles/arch/powerpc/ppc64/32ul/package.use.mask deleted file mode 100644 index 5e473bff5ffa..000000000000 --- a/profiles/arch/powerpc/ppc64/32ul/package.use.mask +++ /dev/null @@ -1,18 +0,0 @@ -# Copyright 1999-2023 Gentoo Authors -# Distributed under the terms of the GNU General Public License v2 - -# Lars Wendler <polynomial-c@gentoo.org> (2022-04-22) -# gnome-base/librsvg missing keywords -media-libs/freetype svg - -# Andreas Sturmlechner <asturm@gentoo.org> (2021-01-19) -# dev-java/openjdk:11 is not keyworded ->=app-office/libreoffice-7 java - -# Robin H. Johnson <robbat2@gentoo.org> (2019-12-06) -# PPS should work on all arches, but only keyworded on some arches ->=net-misc/ntp-4.2.6_p3-r1 -parse-clocks - -# Andreas Sturmlechner <asturm@gentoo.org> (2019-02-16) -# app-text/libwpd and app-text/libwpg are not keyworded -media-gfx/inkscape cdr visio wpg diff --git a/profiles/arch/powerpc/ppc64/32ul/packages b/profiles/arch/powerpc/ppc64/32ul/packages deleted file mode 100644 index 66d529b24633..000000000000 --- a/profiles/arch/powerpc/ppc64/32ul/packages +++ /dev/null @@ -1,5 +0,0 @@ -# Copyright 2012-2012 Gentoo Foundation. -# Distributed under the terms of the GNU General Public License v2 - -# This is no longer needed for ppc64-32ul builds --*sys-devel/kgcc64 diff --git a/profiles/arch/powerpc/ppc64/32ul/parent b/profiles/arch/powerpc/ppc64/32ul/parent deleted file mode 100644 index 0cd1f96e3181..000000000000 --- a/profiles/arch/powerpc/ppc64/32ul/parent +++ /dev/null @@ -1,3 +0,0 @@ -../../../../features/multilib -.. -../../ppc32 diff --git a/profiles/arch/powerpc/ppc64/32ul/use.force b/profiles/arch/powerpc/ppc64/32ul/use.force deleted file mode 100644 index c74bf3460241..000000000000 --- a/profiles/arch/powerpc/ppc64/32ul/use.force +++ /dev/null @@ -1,5 +0,0 @@ -# Force the flag which corresponds to ARCH. -ppc - -# Unforce the flag which corresponds to the 64-bit ARCH. --ppc64 diff --git a/profiles/arch/powerpc/ppc64/32ul/use.mask b/profiles/arch/powerpc/ppc64/32ul/use.mask deleted file mode 100644 index 7d18300e0fbc..000000000000 --- a/profiles/arch/powerpc/ppc64/32ul/use.mask +++ /dev/null @@ -1,12 +0,0 @@ -# Unmask the flag which corresponds to ARCH. --ppc - -# Mask the flag which corresponds to the 64-bit ARCH. -ppc64 - -# We mask this since we're not really a multilib profile -multilib - -# matoro <matoro_gentoo@matoro.tk> (2023-06-17) -# media-libs/libheif is not keyworded here -heif diff --git a/profiles/arch/powerpc/ppc64/64le/package.mask b/profiles/arch/powerpc/ppc64/64le/package.mask index b186047f223f..aa4f7d7393b0 100644 --- a/profiles/arch/powerpc/ppc64/64le/package.mask +++ b/profiles/arch/powerpc/ppc64/64le/package.mask @@ -1,6 +1,14 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# WARNING: UnmatchedProfilePackageUnmask has a bug with false positives here +# https://github.com/pkgcore/pkgcheck/issues/685 + +# matoro <matoro_gentoo@matoro.tk> (2024-06-10) +# Unmask for ppc64le, #892183 +-dev-python/sympy +-dev-python/symengine + # Michał Górny <mgorny@gentoo.org> (2024-04-24) # Unmask ppc64le binpkg. -dev-python/pypy-exe-bin @@ -9,10 +17,6 @@ # https://bugs.gentoo.org/925111 -app-containers/podman -# Jimi Huotari <chiitoo@gentoo.org> (2023-01-11) -# Requires media-libs/libva since 29.0.0, which is unmasked here. -->=media-video/obs-studio-29.0.0 - # Sam James <sam@gentoo.org> (2022-01-18) # No bootstrap binary available on big endian PPC64 right now, but there is # one for ppc64le. @@ -68,16 +72,6 @@ -sys-kernel/vanilla-kernel -virtual/dist-kernel -# Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-25) -# libva unmasked on little-endian profile --net-im/telegram-desktop - -# Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-21) -# works fine on little-endian --media-libs/libva --media-video/libva-utils --media-plugins/gst-plugins-vaapi - # Georgy Yakovlev <gyakovlev@gentoo.org> (2019-08-14) # works fine on little-endian -x11-drivers/xf86-video-amdgpu diff --git a/profiles/arch/powerpc/ppc64/64le/package.use.mask b/profiles/arch/powerpc/ppc64/64le/package.use.mask index 6451c29aa1cf..db2c738617c6 100644 --- a/profiles/arch/powerpc/ppc64/64le/package.use.mask +++ b/profiles/arch/powerpc/ppc64/64le/package.use.mask @@ -1,18 +1,10 @@ # Copyright 2019-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -# James Le Cuirot <chewi@gentoo.org> (2024-04-26) -# Temporary mask while we get dev-libs/weston keywords in order. -gui-libs/gtk test - # Marek Szuba <marecki@gentoo.org> (2023-12-05) # Needs USE=video_cards_amdgpu, which IS available on ppc64le. >=sys-apps/fwupd-1.9.10 -amdgpu -# Craig Andrews <candrews@gentoo.org> (2023-03-09) -# media-libs/libplacebo is keyworded here -media-video/ffmpeg -libplacebo - # Joonas Niilola <juippis@gentoo.org> (2022-11-10) # Doesn't work on ppc64, #871921 sci-mathematics/gmp-ecm custom-tune diff --git a/profiles/arch/powerpc/ppc64/64ul/package.mask b/profiles/arch/powerpc/ppc64/64ul/package.mask index 7cd1ff04a69d..0686d825e2a1 100644 --- a/profiles/arch/powerpc/ppc64/64ul/package.mask +++ b/profiles/arch/powerpc/ppc64/64ul/package.mask @@ -1,10 +1,20 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# matoro <matoro_gentoo@matoro.tk> (2024-06-10) +# Requires ieee-long-double, i.e. ppc64le with 23.0 +# profiles and up, #892183 +dev-python/sympy +dev-python/symengine + # Rahil Bhimjiani <me@rahil.rocks> (2024-03-20) # https://bugs.gentoo.org/925111 app-containers/podman +# Jimi Huotari <chiitoo@gentoo.org> (2023-01-11) +# Requires media-libs/libva since 29.0.0, which is masked here. +>=media-video/obs-studio-29.0.0 + # Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-25) # Not all dependencies keyworded net-im/telegram-desktop diff --git a/profiles/arch/powerpc/ppc64/64ul/package.use.mask b/profiles/arch/powerpc/ppc64/64ul/package.use.mask index 785e4d8dc70e..02d3e897d489 100644 --- a/profiles/arch/powerpc/ppc64/64ul/package.use.mask +++ b/profiles/arch/powerpc/ppc64/64ul/package.use.mask @@ -1,6 +1,11 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Joonas Niilola <juippis@gentoo.org> (2023-08-24) +# media-video/libva-utils is masked on ppc64, so hwaccel on Firefox +# wouldn't work. +www-client/firefox hwaccel + # Georgy Yakovlev (2022-02-16) # dev-python/networkx is keyworded here app-portage/nattka -depgraph-order diff --git a/profiles/arch/powerpc/ppc64/package.mask b/profiles/arch/powerpc/ppc64/package.mask index 694da7e1f320..9b330b7b8468 100644 --- a/profiles/arch/powerpc/ppc64/package.mask +++ b/profiles/arch/powerpc/ppc64/package.mask @@ -1,10 +1,6 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -# Jimi Huotari <chiitoo@gentoo.org> (2023-01-11) -# Requires media-libs/libva since 29.0.0. ->=media-video/obs-studio-29.0.0 - # Michał Górny <mgorny@gentoo.org> (2022-08-25) # Only ppc64le binpkg is provided. dev-python/pypy-exe-bin @@ -61,12 +57,6 @@ sys-kernel/gentoo-kernel-bin sys-kernel/vanilla-kernel virtual/dist-kernel -# Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-21) -# buggy on big-endian -media-libs/libva -media-video/libva-utils -media-plugins/gst-plugins-vaapi - # Georgy Yakovlev <gyakovlev@gentoo.org> (2019-08-14) # buggy on big-endian x11-drivers/xf86-video-amdgpu diff --git a/profiles/arch/powerpc/ppc64/package.use.mask b/profiles/arch/powerpc/ppc64/package.use.mask index 8a74df107f70..1818fc6de33f 100644 --- a/profiles/arch/powerpc/ppc64/package.use.mask +++ b/profiles/arch/powerpc/ppc64/package.use.mask @@ -1,14 +1,25 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Matt Jolly <kangie@gentoo.org> (2024-08-14) +# QUIC dependencies are not keyworded +net-misc/curl http3 quic curl_quic_openssl curl_quic_ngtcp2 + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-08-09) +# KDE PIM 6 is not being keyworded here +kde-apps/libkgapi:5 kf6compat + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-07-01) +# USE="kf6compat,kaccounts" depends on kde-frameworks/purpose:6[webengine] +# which is package.use.mask'ed on these arches. We cannot mask the +# combination specifically but in reality kaccounts is useless without +# additional dev-qt/qtwebengine revdeps. +kde-frameworks/purpose:5 kaccounts + # Sam James <sam@gentoo.org> (2024-05-19) # media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 media-gfx/graphicsmagick jpeg2k -# José de Paula R. N. Assis <espinafre@gmail.com> (2024-03-25) -# No PyQt6 (which is needed by USE=qt6 for qscintilla-python) on ppc64. ->=dev-python/qscintilla-python-2.14.1-r1 qt6 - # Sam James <sam@gentoo.org> (2024-03-23) # dev-qt/qtwebengine not available here dev-python/QtPy webengine test @@ -21,15 +32,6 @@ app-emulation/libvirt -virtiofsd # media-libs/shaderc is keyworded here. media-libs/libplacebo -shaderc -# Sam James <sam@gentoo.org> (2023-09-22) -# Qt 6 not keyworded here. -dev-build/cmake gui - -# Joonas Niilola <juippis@gentoo.org> (2023-08-24) -# media-video/libva-utils is masked on ppc64, so hwaccel on Firefox -# wouldn't work. -www-client/firefox hwaccel - # Alexey Sokolov <alexey+gentoo@asokolov.org> (2023-08-14) # OpenMW is only playtested with LuaJIT, and in fact unit tests fail with Lua-5. # Therefore apply mask/force to override the profile's defaults, and invert on @@ -59,10 +61,6 @@ sci-libs/symengine tcmalloc # https://github.com/rustsec/rustsec/issues/707 dev-util/cargo-audit fix -# Andreas Sturmlechner <asturm@gentoo.org> (2022-07-17) -# dev-python/pyside2 is not keyworded -www-client/falkon python - # Jimi Huotari <chiitoo@gentoo.org> (2022-05-08) # Not keyworded here yet. lxqt-base/lxqt-meta desktop-portal @@ -72,10 +70,6 @@ lxqt-base/lxqt-meta desktop-portal # impl there anyway. Please keep this in sync with use.stable.mask. dev-lang/python-exec -python_targets_pypy3 -# Georgy Yakovlev <gyakovlev@gentoo.org> (2021-11-12) -# telepathy stack is not keyworded -dev-util/kdevelop reviewboard - # Sam James <sam@gentoo.org> (2021-10-17) # Go doesn't support pie on ppc64, bug #818529 net-dns/dnscrypt-proxy pie @@ -113,6 +107,7 @@ dev-util/diffoscope haskell sys-libs/compiler-rt-sanitizers -asan -lsan -msan -tsan sys-libs/compiler-rt-sanitizers -ubsan -scudo sys-libs/compiler-rt-sanitizers -profile +>=sys-libs/compiler-rt-sanitizers-19 -orc # Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-25) # fwupd keyworded now on ppc64 @@ -140,10 +135,6 @@ x11-themes/arc-theme cinnamon # Bug #728558 media-video/ffmpeg -rav1e -# Andreas Sturmlechner <asturm@gentoo.org> (2020-07-02) -# media-libs/libplacebo is keyworded -media-video/vlc -libplacebo - # Georgy Yakovlev <gyakovlev@gentoo.org> (2020-06-07) # works on ppc64 app-emulation/qemu -spice -usbredir diff --git a/profiles/arch/powerpc/ppc64/package.use.stable.mask b/profiles/arch/powerpc/ppc64/package.use.stable.mask index dbbd4dfe6178..f33f0f16b0b6 100644 --- a/profiles/arch/powerpc/ppc64/package.use.stable.mask +++ b/profiles/arch/powerpc/ppc64/package.use.stable.mask @@ -17,6 +17,10 @@ #--- END OF EXAMPLES --- +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-12) +# dev-python/pyside6 is not stable here +dev-python/QtPy pyside6 + # Sam James <sam@gentoo.org> (2024-04-30) # sys-block/nbdkit is not yet marked stable here app-emulation/libvirt nbd diff --git a/profiles/arch/powerpc/ppc64/use.mask b/profiles/arch/powerpc/ppc64/use.mask index 34a2f70e2b10..df505e9a7a73 100644 --- a/profiles/arch/powerpc/ppc64/use.mask +++ b/profiles/arch/powerpc/ppc64/use.mask @@ -1,4 +1,4 @@ -# Copyright 2008-2023 Gentoo Authors +# Copyright 2008-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 ### THIS FILE IS ONLY FOR PACKAGES MASKED ON BOTH 64-BIT AND 32-BIT USERLAND!!! diff --git a/profiles/arch/powerpc/use.mask b/profiles/arch/powerpc/use.mask index df5495374f7f..7a1c27c1b517 100644 --- a/profiles/arch/powerpc/use.mask +++ b/profiles/arch/powerpc/use.mask @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # PPC Specific use flags @@ -18,6 +18,7 @@ mono # Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-25) # Requires qtwebengine, which is not ported to any of powerpc arches yet +pdfium webengine # Matt Turner <mattst88@gentoo.org> (2018-09-18) diff --git a/profiles/arch/powerpc/use.stable.mask b/profiles/arch/powerpc/use.stable.mask index 26c5e7756991..cf5a25e06e1d 100644 --- a/profiles/arch/powerpc/use.stable.mask +++ b/profiles/arch/powerpc/use.stable.mask @@ -1,13 +1,9 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in use.mask -# Ionen Wolkens <ionen@gentoo.org> (2024-01-27) -# Qt6 is not stable here yet -qt6 - # Matt Turner <mattst88@gentoo.org> (2018-04-25) # Dropped stable keywords octave diff --git a/profiles/arch/ppc/package.use.mask b/profiles/arch/ppc/package.use.mask index 5d71faf85142..8c3b12715f9b 100644 --- a/profiles/arch/ppc/package.use.mask +++ b/profiles/arch/ppc/package.use.mask @@ -1,6 +1,10 @@ # Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Eli Schwartz <eschwartz93@gmail.com> (2024-06-05) +# tests require pytest-qt which is not keyworded +app-portage/elogviewer test + # Eray Aslan <eras@gentoo.org> (2024-03-08) # mongodb dependencies are not keyworded mail-mta/postfix mongodb diff --git a/profiles/arch/riscv/package.use.mask b/profiles/arch/riscv/package.use.mask index 4ff7748d732a..40d756b4ac58 100644 --- a/profiles/arch/riscv/package.use.mask +++ b/profiles/arch/riscv/package.use.mask @@ -1,6 +1,37 @@ # Copyright 2019-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Paul Zander <negril.nx+gentoo@gmail.com> (2024-09-08) +# needs re-keywording and clean-up of media-libs/opencollada +media-libs/assimp collada + +# Michael Orlitzky <mjo@gentoo.org> (2024-09-01) +# Mask the optional plotting backend sci-libs/vtk because it's a beast +# and I don't want to deal with it right now. +sci-mathematics/maxima vtk + +# Michael Orlitzky <mjo@gentoo.org> (2024-08-26) +# There's an unexplained test failure in sci-libs/qd that I've emailed +# the authors about. Until we know what's up with that, USE=qd should +# remain masked for consumers. +sci-libs/fplll qd +sci-mathematics/lcalc double-double quad-double + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-07-06) +# KDE PIM is not keyworded here +kde-apps/libkgapi:5 kf6compat + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-07-01) +# USE="kf6compat,kaccounts" depends on kde-frameworks/purpose:6[webengine] +# which is package.use.mask'ed on these arches. We cannot mask the +# combination specifically but in reality kaccounts is useless without +# additional dev-qt/qtwebengine revdeps. +kde-frameworks/purpose:5 kaccounts + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-15) +# Requires unkeyworded dev-qt/qtwebengine (and revdeps) +kde-plasma/plasma-nm openconnect + # Sam James <sam@gentoo.org> (2024-05-19) # media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 media-gfx/graphicsmagick jpeg2k @@ -21,11 +52,6 @@ app-emulation/libvirt nbd # Unmask only where grub is keyworded sys-kernel/installkernel -grub -# Leonardo Hernández Hernández <leohdz172@proton.me> (2023-11-22) -# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff) -# are only available for amd64, arm64 and riscv ->=gui-libs/wlroots-0.17.0 -drm -liftoff - # Ionen Wolkens <ionen@gentoo.org> (2023-10-09) # media-libs/shaderc is keyworded here. media-libs/libplacebo -shaderc @@ -33,6 +59,7 @@ media-libs/libplacebo -shaderc # Patrick McLean <chutzpah@gentoo.org> (2023-10-03) # sys-apps/s6-linux-init has not been tested on this arch sys-apps/openrc s6 +sys-apps/openrc-navi s6 # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-08-30) # Avoid keywording more Qt stuff @@ -61,8 +88,10 @@ sys-kernel/installkernel -systemd-boot -ukify -uki sys-block/tgt rbd # jinqiang zhang <peeweep@0x0.ee> (2023-03-27) -# Sanitizers supported on this architecture. +# Sanitizers supported on riscv64. sys-libs/compiler-rt-sanitizers -asan -lsan +>=sys-libs/compiler-rt-sanitizers-19 -libfuzzer -hwasan -profile -tsan +>=sys-libs/compiler-rt-sanitizers-19 -ubsan -scudo # Yixun Lan <dlan@gentoo.org> (2023-02-16) # USE=java depend on virtual/jdk:1.8 which is not support on RISC-V @@ -220,7 +249,6 @@ dev-libs/mongo-c-driver test # LuaJIT does not support riscv app-text/texlive-core luajittex dev-texlive/texlive-basic luajittex -dev-texlive/texlive-context luajittex media-gfx/gimp lua www-servers/nginx nginx_modules_http_lua diff --git a/profiles/arch/ia64/eapi b/profiles/arch/riscv/rv32imac/eapi index 7ed6ff82de6b..7ed6ff82de6b 100644 --- a/profiles/arch/ia64/eapi +++ b/profiles/arch/riscv/rv32imac/eapi diff --git a/profiles/arch/riscv/rv32imac/ilp32/parent b/profiles/arch/riscv/rv32imac/ilp32/parent new file mode 100644 index 000000000000..f3229c5b9876 --- /dev/null +++ b/profiles/arch/riscv/rv32imac/ilp32/parent @@ -0,0 +1 @@ +.. diff --git a/profiles/arch/riscv/rv32imac/ilp32d/parent b/profiles/arch/riscv/rv32imac/ilp32d/parent new file mode 100644 index 000000000000..f3229c5b9876 --- /dev/null +++ b/profiles/arch/riscv/rv32imac/ilp32d/parent @@ -0,0 +1 @@ +.. diff --git a/profiles/arch/riscv/rv32imac/parent b/profiles/arch/riscv/rv32imac/parent new file mode 100644 index 000000000000..6c33bf12d0d1 --- /dev/null +++ b/profiles/arch/riscv/rv32imac/parent @@ -0,0 +1 @@ +../../../features/wd40 diff --git a/profiles/arch/riscv/use.mask b/profiles/arch/riscv/use.mask index 4eb16fdf74f2..3c3913716246 100644 --- a/profiles/arch/riscv/use.mask +++ b/profiles/arch/riscv/use.mask @@ -4,6 +4,13 @@ # Unmask the flag which corresponds to ARCH. -riscv +# Michael Orlitzky <mjo@gentoo.org> (2024-09-01) +# These lisp implementations have ~riscv keywords. +# This counteracts the mask in arch/base/use.mask. +-clisp +-ecl +-gcl + # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-07-11) # Unmask secureboot flag on arches where sbsigntools is keyworded -secureboot @@ -22,6 +29,7 @@ # Yongxiang Liang <tanekliang@gmail.com> (2024-01-16) # Requires qtwebengine, which is not ported to riscv +pdfium webengine # Marek Szuba <marecki@gentoo.org> (2021-08-14) diff --git a/profiles/arch/s390/package.use.mask b/profiles/arch/s390/package.use.mask index 3f1e43fa394d..ae7ab5ecfa16 100644 --- a/profiles/arch/s390/package.use.mask +++ b/profiles/arch/s390/package.use.mask @@ -1,6 +1,26 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Hans de Graaff <graaff@gentoo.org> (2024-09-01) +# Requires large parts of dev-ruby/rails to be keyworded +dev-ruby/minitest-hooks test + +# Sam James <sam@gentoo.org> (2024-08-23) +# dev-util/bpftool and/or sys-devel/bpf-toolchain not keyworded here +sys-apps/systemd bpf + +# Matt Jolly <kangie@gentoo.org> (2024-08-14) +# QUIC dependencies are not keyworded +net-misc/curl http3 quic curl_quic_openssl curl_quic_ngtcp2 + +# Michał Górny <mgorny@gentoo.org> (2024-07-24) +# Full testing requires www-client/firefox. +dev-python/selenium test-rust + +# Sam James <sam@gentoo.org> (2024-07-03) +# kde-frameworks/kservice not keyworded here +x11-misc/xdg-utils plasma + # Michał Górny <mgorny@gentoo.org> (2024-05-08) # Requires sys-devel/{clang,llvm}:16. dev-lang/python jit @@ -62,6 +82,7 @@ app-alternatives/ninja samurai # Patrick McLean <chutzpah@gentoo.org> (2023-10-03) # sys-apps/s6-linux-init has not been tested on this arch sys-apps/openrc s6 +sys-apps/openrc-navi s6 # Sam James <sam@gentoo.org> (2023-09-24) # Qt not keyworded here. @@ -206,7 +227,7 @@ dev-python/diskcache test # Matt Turner <mattst88@gentoo.org> (2020-08-11) # No drivers on this architecture support Vulkan -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa video_cards_zink vulkan vulkan-overlay zink # Hans de Graaff <graaff@gentoo.org> (2019-04-08) # Obsolete ruby version, no newer versions keyworded or stable. diff --git a/profiles/arch/s390/s390x/package.use.mask b/profiles/arch/s390/s390x/package.use.mask index 2db48ad88c12..56e0148ca364 100644 --- a/profiles/arch/s390/s390x/package.use.mask +++ b/profiles/arch/s390/s390x/package.use.mask @@ -1,6 +1,10 @@ # Copyright 1999-2022 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas K. Hüttel <dilfridge@gentoo.org> (2024-07-27) +# Once again, assembler is broken (too high baseline) +=dev-libs/openssl-3.3* asm + # Michał Górny <mgorny@gentoo.org> (2022-06-18) # media-libs/librsvg not keyworded yet. media-libs/freetype svg diff --git a/profiles/arch/sparc/make.defaults b/profiles/arch/sparc/make.defaults index cf143847e97a..ad4a52329c2f 100644 --- a/profiles/arch/sparc/make.defaults +++ b/profiles/arch/sparc/make.defaults @@ -42,7 +42,3 @@ VIDEO_CARDS="fbdev mga r128 radeon" # Enable USE=libtirpc by default, to ease dependency resolution during # the stabilization of glibc-2.26. Bug 657148 USE="libtirpc" - -# Hans de Graaff <graaff@gentoo.org> (2024-05-20) -# Allow ruby32 stabling: https://bugs.gentoo.org/932285 -RUBY_TARGETS="ruby31 -ruby32" diff --git a/profiles/arch/sparc/package.mask b/profiles/arch/sparc/package.mask index 538d5c80fc20..dcbae565c287 100644 --- a/profiles/arch/sparc/package.mask +++ b/profiles/arch/sparc/package.mask @@ -1,6 +1,13 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# matoro <matoro_gentoo@matoro.tk> (2024-06-11) +# Extensive use of unaligned access, no plans to fix, #636552 +# https://github.com/memcached/memcached/issues/902 +net-misc/memcached +dev-libs/libmemcached +dev-python/pylibmc + # matoro <matoro_gentoo@matoro.tk> (2023-03-07) # Fails tests disastrously. Present evidence of passing test suite # before removing, please. diff --git a/profiles/arch/sparc/package.use.mask b/profiles/arch/sparc/package.use.mask index a27c74642a24..55d49431d68f 100644 --- a/profiles/arch/sparc/package.use.mask +++ b/profiles/arch/sparc/package.use.mask @@ -1,6 +1,42 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James <sam@gentoo.org> (2024-08-23) +# dev-util/bpftool and/or sys-devel/bpf-toolchain not keyworded here +sys-apps/systemd bpf + +# Ulrich Müller <ulm@gentoo.org> (2024-08-03) +# Needs dev-libs/openspecfun which is not yet keyworded +sci-visualization/gnuplot amos + +# Joonas Niilola <juippis@gentoo.org> (2024-07-29) +# Dependency not keyworded on sparc. +dev-libs/re2 benchmark + +# Michał Górny <mgorny@gentoo.org> (2024-07-24) +# Full testing requires www-client/firefox. +dev-python/selenium test-rust + +# Sam James <sam@gentoo.org> (2024-07-03) +# kde-frameworks/kservice not keyworded here +x11-misc/xdg-utils plasma + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-29) +# media-libs/libplacebo is not keyworded here +media-video/ffmpeg libplacebo + +# Sam James <sam@gentoo.org> (2024-06-23) +# app-crypt/gcr:4[gtk] is not available here +app-crypt/pinentry gtk + +# matoro <matoro_gentoo@matoro.tk> (2024-06-11) +# net-misc/memcached casualties, #636552 +# https://github.com/memcached/memcached/issues/902 +dev-python/pylibmc test +dev-python/pytest-services test +net-ftp/proftpd memcache +dev-ruby/dalli test + # Sam James <sam@gentoo.org> (2024-05-19) # media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 media-gfx/graphicsmagick jpeg2k @@ -48,7 +84,6 @@ app-crypt/mit-krb5 keyutils app-emulation/qemu keyutils net-fs/samba ads net-fs/cifs-utils ads creds pam -sys-auth/sssd keyutils >=sys-libs/libblockdev-3.0.0 cryptsetup sys-libs/libnvme keyutils @@ -91,10 +126,7 @@ dev-qt/qtgui vulkan # Patrick McLean <chutzpah@gentoo.org> (2023-10-03) # sys-apps/s6-linux-init has not been tested on this arch sys-apps/openrc s6 - -# Sam James <sam@gentoo.org> (2023-09-22) -# Qt 6 not keyworded here. -dev-build/cmake gui +sys-apps/openrc-navi s6 # Sam James <sam@gentoo.org> (2023-07-21) # Requires app-emulation/qemu. @@ -303,11 +335,11 @@ xfce-base/tumbler epub # Arfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com> (2020-10-14) # app-i18n/fcitx:4 not keyworded. -media-libs/libsdl2 fcitx4 +media-libs/libsdl2 fcitx # Matt Turner <mattst88@gentoo.org> (2020-08-11) # No drivers on this architecture support Vulkan -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa video_cards_zink vulkan vulkan-overlay zink # Robin H. Johnson <robbat2@gentoo.org> (2020-07-02) # Mask io-uring & zbc pending keywording @@ -355,7 +387,6 @@ app-misc/tracker-miners test dev-ruby/rack-cache test dev-ruby/activemodel test dev-ruby/activerecord test -dev-ruby/activesupport test dev-ruby/globalid test # Rolf Eike Beer <eike@sf-mail.de> (2020-04-18) @@ -377,7 +408,6 @@ x11-libs/qwt designer # Rolf Eike Beer <eike@sf-mail.de> (2020-04-15) # USE=bpf depends on sys-devel/clang which is not keyworded on sparc media-libs/libv4l bpf -media-tv/v4l-utils bpf # Rolf Eike Beer <eike@sf-mail.de> (2020-04-14) # dev-lang/luajit is not keyworded on sparc @@ -592,10 +622,6 @@ dev-haskell/haskell-src-exts test # Missing keywords, bug #524352 >=app-accessibility/orca-3.12.3 braille -# Christoph Junghans <junghans@gentoo.org> (2014-07-21) -# Missing keywords on sci-libs/libcerf (bug 517726) -sci-visualization/gnuplot libcerf - # Pacho Ramos <pacho@gentoo.org> (2014-04-12) # Missing keywords, bug #507490 net-misc/modemmanager mbim diff --git a/profiles/arch/sparc/package.use.stable.mask b/profiles/arch/sparc/package.use.stable.mask index 5451339c6b85..5bec10bead0e 100644 --- a/profiles/arch/sparc/package.use.stable.mask +++ b/profiles/arch/sparc/package.use.stable.mask @@ -1,13 +1,16 @@ # Copyright 2019-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James <sam@gentoo.org> (2024-07-31) +# Qt 6 not stable here. +dev-build/cmake gui + # Eli Schwartz <eschwartz93@gmail.com> (2024-02-05) # app-text/mupdf is not stable. bug #923811 net-print/cups-filters pdf net-print/libcupsfilters pdf net-print/cups-meta pdf - # Sam James <sam@gentoo.org> (2023-12-30) # Qt not marked stable here. app-text/doxygen gui @@ -119,7 +122,3 @@ dev-libs/libzip mbedtls net-libs/libssh mbedtls net-libs/libssh2 mbedtls net-vpn/openvpn mbedtls - -# Sergei Trofimovich <slyfox@gentoo.org> (2020-04-04) -# Needs stable net-libs/webkit-gtk, bug #712260 -app-editors/emacs xwidgets diff --git a/profiles/arch/sparc/use.mask b/profiles/arch/sparc/use.mask index 6bad40b9cccd..c3222cbf6f28 100644 --- a/profiles/arch/sparc/use.mask +++ b/profiles/arch/sparc/use.mask @@ -4,6 +4,11 @@ # Unmask the flag which corresponds to ARCH. -sparc +# matoro <matoro_gentoo@matoro.tk> (2024-06-11) +# Extensive use of unaligned access, no plans to fix, #636552 +# https://github.com/memcached/memcached/issues/902 +memcached + # Ionen Wolkens <ionen@gentoo.org> (2024-01-27) # Needs bug #918896 for missing Qt6 keywords qt6 diff --git a/profiles/arch/sparc/use.stable.mask b/profiles/arch/sparc/use.stable.mask index 865b799bc738..79cf2319f1fd 100644 --- a/profiles/arch/sparc/use.stable.mask +++ b/profiles/arch/sparc/use.stable.mask @@ -4,10 +4,6 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in use.mask -# Hans de Graaff <graaff@gentoo.org> (2024-05-20) -# Allow ruby32 stabling: https://bugs.gentoo.org/932285 -ruby_targets_ruby32 - # Sam James <sam@gentoo.org> (2024-03-07) # dev-lang/php:8.2 is not marked stable here yet (bug #920701) php_targets_php8-2 diff --git a/profiles/arch/x86/i486/parent b/profiles/arch/x86/i486/parent new file mode 100644 index 000000000000..6c33bf12d0d1 --- /dev/null +++ b/profiles/arch/x86/i486/parent @@ -0,0 +1 @@ +../../../features/wd40 diff --git a/profiles/arch/x86/package.mask b/profiles/arch/x86/package.mask index 19f6423ba197..ec1bcf600753 100644 --- a/profiles/arch/x86/package.mask +++ b/profiles/arch/x86/package.mask @@ -28,9 +28,6 @@ dev-python/spyder-unittest dev-python/spyder-line-profiler dev-python/spyder-vim dev-python/spyder-notebook -dev-util/kdevelop:5 -dev-util/kdevelop-php:5 -dev-util/kdevelop-python:5 kde-apps/akonadi-calendar:5 kde-apps/akonadi-import-wizard:5 kde-apps/akonadiconsole:5 @@ -44,7 +41,6 @@ kde-apps/incidenceeditor:5 kde-apps/kaccounts-providers:5 kde-apps/kaddressbook:5 kde-apps/kalarm:5 -kde-apps/kalgebra:5 kde-apps/kdepim-addons:5 kde-apps/kdepim-meta kde-apps/kdepim-runtime:5 @@ -61,21 +57,16 @@ kde-apps/libksieve:5 kde-apps/mailcommon:5 kde-apps/messagelib:5 kde-apps/mbox-importer:5 -kde-apps/parley:5 kde-apps/pim-data-exporter:5 kde-apps/pim-sieve-editor:5 kde-misc/kio-gdrive kde-misc/tellico:5 kde-misc/zanshin:5 -media-gfx/digikam:5 media-gfx/luminance-hdr media-sound/frescobaldi media-sound/teamspeak-client:3 net-analyzer/nmapsi net-libs/signon-ui sci-geosciences/qmapshack ->=sci-geosciences/gpsbabel-1.8.0 -sci-mathematics/rkward:5 -sci-visualization/labplot:5 www-client/falkon www-client/otter diff --git a/profiles/arch/x86/package.use b/profiles/arch/x86/package.use index 9770883187a6..9a904c7bc993 100644 --- a/profiles/arch/x86/package.use +++ b/profiles/arch/x86/package.use @@ -1,6 +1,11 @@ # Copyright 1999-2019 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Ben Kohler <bkohler@gentoo.org> (2024-06-12) +# Disable thin volume support by default since it reuqires sse2 which most +# x86 cpus will lack +sys-fs/lvm2 -thin + # Ben Kohler <bkohler@gentoo.org> (2022-06-07) # Enable BIOS target by default sys-apps/memtest86+ bios32 diff --git a/profiles/arch/x86/package.use.mask b/profiles/arch/x86/package.use.mask index ffa478160365..c8fd4375ed58 100644 --- a/profiles/arch/x86/package.use.mask +++ b/profiles/arch/x86/package.use.mask @@ -1,22 +1,44 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -# José de Paula R. N. Assis <espinafre@gmail.com> (2024-03-25) -# No PyQt6 (which is needed by USE=qt6 for qscintilla-python) on x86. ->=dev-python/qscintilla-python-2.14.1-r1 qt6 - -# Andreas Sturmlechner <asturm@gentoo.org> (2024-03-24) -# Requires unkeyworded dev-qt/qtwebengine -net-p2p/ktorrent rss +# Patrick McLean <chutzpah@gentoo.org> (2024-09-23) +# Only supported on x86/amd64 (bug #940014). +net-misc/lldpd -seccomp + +# orbea <orbea@riseup.net> (2024-07-19) +# Unmask the dynarec flag which has x86 asm. +games-emulation/rmg -dynarec + +# Matt Turner <mattst88@gentoo.org> (2024-07-17) +# We only want to support spirv-llvm-translator >= 17 on x86, which is a +# dependency of mesa. +>=media-libs/mesa-24.1 llvm_slot_15 llvm_slot_16 +>=dev-util/intel_clc-24.1 llvm_slot_15 llvm_slot_16 + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-07-12) +# KDE PIM 6 is not being keyworded here +kde-apps/libkgapi:5 kf6compat + +# Michael Orlitzky <mjo@gentoo.org> (2024-07-09) +# The opcache extension fails to build on hardened x86, but only +# if the JIT is enabled. Bug 930145. +dev-lang/php opcache-jit + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-07-04) +# app-office/lyx is unavailable on x86 +dev-tex/abntex lyx + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-07-01) +# USE="kf6compat,kaccounts" depends on kde-frameworks/purpose:6[webengine] +# which is package.use.mask'ed on these arches. We cannot mask the +# combination specifically but in reality kaccounts is useless without +# additional dev-qt/qtwebengine revdeps. +kde-frameworks/purpose:5 kaccounts # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-21) # virt-firmware is keyworded here sys-kernel/installkernel -efistub -# Guilherme Amadio <amadio@gentoo.org> (2024-03-09) -# Qt6 not keyworded on x86 -sci-physics/root qt6 - # Sam James <sam@gentoo.org> (2024-03-04) # Miscompiles rust and fails to bootstrap (bug #923278) >=dev-lang/rust-1.74.1 lto @@ -86,10 +108,6 @@ net-libs/pjproject webrtc # Needs x11-drivers/nvidia-drivers which is no longer available here. media-tv/mythtv nvdec -# Craig Andrews <candrews@gentoo.org> (2023-03-09) -# media-libs/libplacebo is keyworded here -media-video/ffmpeg -libplacebo - # Andreas Sturmlechner <asturm@gentoo.org> (2023-02-06) # Successful build of dev-qt/qtwebengine depends on 64-bit host # Bug #893234 @@ -103,11 +121,13 @@ kde-apps/kdenetwork-meta bittorrent kde-apps/kleopatra pim kde-apps/umbrello php kde-misc/kio-gdrive share +kde-plasma/plasma-nm openconnect net-irc/quassel urlpreview net-misc/fatrat bittorrent net-misc/seafile-client shibboleth +net-p2p/ktorrent rss sci-mathematics/yacas gui -sci-physics/root qt5 +sci-physics/root qt5 qt6 # Ionen Wolkens <ionen@gentoo.org> (2022-11-07) # Vulkan is usable here. diff --git a/profiles/arch/x86/package.use.stable.mask b/profiles/arch/x86/package.use.stable.mask index 7a39da3cbf11..334ee2d10a69 100644 --- a/profiles/arch/x86/package.use.stable.mask +++ b/profiles/arch/x86/package.use.stable.mask @@ -17,14 +17,27 @@ #--- END OF EXAMPLES --- +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-20) +# dev-python/pyside6 is not stable here. +dev-python/QtPy pyside6 + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-02) +# kde-plasma/plasma-workspace is not stable here. +sys-auth/polkit kde +virtual/notification-daemon kde + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-08-30) +# KF6 is not stable here. +>=app-crypt/pinentry-1.3.0 wayland + +# Matt Turner <mattst88@gentoo.org> (2024-07-14) +# spirv-llvm-translator < 17 is not stable on x86. +<dev-libs/libclc-17 spirv + # Sam James <sam@gentoo.org> (2024-04-30) # sys-block/nbdkit is not yet marked stable here app-emulation/libvirt nbd -# Matt Turner <mattst88@gentoo.org> (2024-04-25) -# spirv-llvm-translator is not stable on x86. -dev-libs/libclc spirv - # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-21) # Experimental, virt-firmware is keyworded only unstable sys-kernel/installkernel efistub diff --git a/profiles/arch/x86/use.mask b/profiles/arch/x86/use.mask index 38dc83097d4f..2157622d2e3c 100644 --- a/profiles/arch/x86/use.mask +++ b/profiles/arch/x86/use.mask @@ -31,6 +31,7 @@ color-management # Andreas Sturmlechner <asturm@gentoo.org> (2023-02-06) # Successful build of dev-qt/qtwebengine depends on 64-bit host # Bug #893234 +pdfium webengine # matoro <matoro_gentoo@matoro.tk> (2022-09-29) diff --git a/profiles/arch/x86/use.stable.mask b/profiles/arch/x86/use.stable.mask index 6f373ce425c2..90b1e4500f31 100644 --- a/profiles/arch/x86/use.stable.mask +++ b/profiles/arch/x86/use.stable.mask @@ -12,10 +12,6 @@ atlas # media-libs/jasper is not stable jasper -# Ionen Wolkens <ionen@gentoo.org> (2024-01-27) -# Qt6 is not stable here yet -qt6 - # Sam James <sam@gentoo.org> (2020-11-10) # media-gfx/openvdb is not stable on x86 # ... and has failing tests right now anyway diff --git a/profiles/arches.desc b/profiles/arches.desc index 965e36c6c0c1..8de7897c19ea 100644 --- a/profiles/arches.desc +++ b/profiles/arches.desc @@ -16,7 +16,6 @@ amd64 stable arm stable arm64 stable hppa stable -ia64 testing loong testing m68k testing mips testing diff --git a/profiles/base/make.defaults b/profiles/base/make.defaults index 7d731fd07cf1..515c1745fc52 100644 --- a/profiles/base/make.defaults +++ b/profiles/base/make.defaults @@ -12,7 +12,7 @@ USE_EXPAND_VALUES_KERNEL="Darwin linux SunOS" # Env vars to expand into USE vars. Modifying this requires prior # discussion on gentoo-dev@lists.gentoo.org. -USE_EXPAND="ABI_MIPS ABI_S390 ABI_X86 ADA_TARGET ALSA_CARDS AMDGPU_TARGETS APACHE2_MODULES APACHE2_MPMS CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_ARM CPU_FLAGS_PPC CPU_FLAGS_X86 CURL_SSL ELIBC FFTOOLS GPSD_PROTOCOLS GRUB_PLATFORMS INPUT_DEVICES KERNEL L10N LCD_DEVICES LIBREOFFICE_EXTENSIONS LLVM_SLOT LLVM_TARGETS LUA_SINGLE_TARGET LUA_TARGETS MONKEYD_PLUGINS NGINX_MODULES_HTTP NGINX_MODULES_MAIL NGINX_MODULES_STREAM OFFICE_IMPLEMENTATION OPENMPI_FABRICS OPENMPI_OFED_FEATURES OPENMPI_RM PERL_FEATURES PHP_TARGETS POSTGRES_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS RUBY_TARGETS SANE_BACKENDS UWSGI_PLUGINS VIDEO_CARDS VOICEMAIL_STORAGE XTABLES_ADDONS" +USE_EXPAND="ABI_MIPS ABI_S390 ABI_X86 ADA_TARGET ALSA_CARDS AMDGPU_TARGETS APACHE2_MODULES APACHE2_MPMS CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_ARM CPU_FLAGS_PPC CPU_FLAGS_X86 CURL_SSL CURL_QUIC ELIBC FFTOOLS GPSD_PROTOCOLS GRUB_PLATFORMS GUILE_SINGLE_TARGET GUILE_TARGETS INPUT_DEVICES KERNEL L10N LCD_DEVICES LIBREOFFICE_EXTENSIONS LLVM_SLOT LLVM_TARGETS LUA_SINGLE_TARGET LUA_TARGETS NGINX_MODULES_HTTP NGINX_MODULES_MAIL NGINX_MODULES_STREAM OFFICE_IMPLEMENTATION OPENMPI_FABRICS OPENMPI_OFED_FEATURES OPENMPI_RM PERL_FEATURES PHP_TARGETS POSTGRES_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS RUBY_TARGETS SANE_BACKENDS UWSGI_PLUGINS VIDEO_CARDS VOICEMAIL_STORAGE XTABLES_ADDONS" # USE_EXPAND variables whose contents are not shown in package manager # output. Changes need discussion on gentoo-dev. @@ -123,12 +123,13 @@ PYTHONDONTWRITEBYTECODE="1" # This MUST be kept in sync with the PYTHON_TARGETS below # Mike Gilbert <floppym@gentoo.org> (2018-05-23) # sys-apps/baselayout-2.5 needs split-usr enabled. -BOOTSTRAP_USE="unicode internal-glib pkg-config split-usr xml python_targets_python3_11 python_single_target_python3_11" +# dev-lang/python:3.13 and later needs gil enabled +BOOTSTRAP_USE="unicode pkg-config split-usr xml python_targets_python3_12 python_single_target_python3_12 gil" # Mike Gilbert <floppym@gentoo.org> (2012-05-15) # Default target(s) for python-r1.eclass -PYTHON_TARGETS="python3_11" -PYTHON_SINGLE_TARGET="python3_11" +PYTHON_TARGETS="python3_12" +PYTHON_SINGLE_TARGET="python3_12" # Michał Górny <mgorny@gentoo.org> (2013-08-10) # Moved from portage's make.globals. @@ -149,7 +150,7 @@ TWISTED_DISABLE_WRITING_OF_PLUGIN_CACHE="1" # Aaron W. Swenson <titanofold@gentoo.org> (2017-07-09) # Default target(s) for postgres{,-multi}.eclass -POSTGRES_TARGETS="postgres15" +POSTGRES_TARGETS="postgres16" # Michael Orlitzky <mjo@gentoo.org> (2017-11-17) # @@ -164,7 +165,7 @@ POSTGRES_TARGETS="postgres15" # Moreover, it should only contain targets that have a stable version # of PHP, to avoid pulling in an unstable PHP on stable systems. # -PHP_TARGETS="php8-1" +PHP_TARGETS="php8-2" # Alfredo Tupone <tupone@gentoo.org> (2024-03-15) # @@ -181,3 +182,9 @@ LUA_TARGETS="lua5-1" # we care about should match these anyway. See https://wiki.gentoo.org/wiki/Modern_C_porting. ac_cv_c_undeclared_builtin_options="none needed" gl_cv_compiler_check_decl_option="-Werror=implicit-function-declaration" + +# Arsen Arsenović <arsen@gentoo.org> (2024-08-04) +# Default target values for the Guile ecosystem (see also: +# guile{,-single}.eclass) +GUILE_TARGETS="3-0" +GUILE_SINGLE_TARGET="3-0" diff --git a/profiles/base/package.mask b/profiles/base/package.mask index cbe031846f35..f7f6c9a921d0 100644 --- a/profiles/base/package.mask +++ b/profiles/base/package.mask @@ -1,6 +1,11 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# matoro <matoro_gentoo@matoro.tk> (2024-08-18) +# Pre-rust versions of librsvg. Has vulnerabilities, so masked by +# default and only unmasked on wd40. +<gnome-base/librsvg-2.41 + # Mike Gilbert <floppym@gentoo.org> (2023-06-15) # Conflicts with glibc. sys-apps/musl-locales diff --git a/profiles/base/package.use b/profiles/base/package.use index cf646b56fb24..6a55f366e30f 100644 --- a/profiles/base/package.use +++ b/profiles/base/package.use @@ -1,6 +1,14 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Michał Górny <mgorny@gentoo.org> (2024-09-15) +# Each flag is used by exactly one version, so let's default-enable +# them all to make tattoo not fail on almost everything. +dev-python/python-tests:3.10 python_targets_python3_10 +dev-python/python-tests:3.11 python_targets_python3_11 +dev-python/python-tests:3.12 python_targets_python3_12 +dev-python/python-tests:3.13 python_targets_python3_13 + # Arthur Zamarin <arthurzam@gentoo.org> (2024-03-23) # Used by pkgcheck, so let's make it easier for all developers to install it >=dev-libs/tree-sitter-bash-0.21.0 python diff --git a/profiles/base/package.use.force b/profiles/base/package.use.force index f4cd5a5e7e69..fe7d666017ea 100644 --- a/profiles/base/package.use.force +++ b/profiles/base/package.use.force @@ -1,6 +1,28 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James <sam@gentoo.org> (2024-09-30) +# gnat-gpl only exists for (bootstrapping) Ada. Until bug #940471 is handled, +# force Ada on. Once it is split/moved/gutted, this won't be necessary +# as it'll always build Ada. +dev-lang/gnat-gpl ada + +# Michał Górny <mgorny@gentoo.org> (2024-06-29) +# Disabling GIL (enabling freethreading) is experimental and prone +# to break packages. Should you choose to test it, please do not file +# Gentoo bugs and report any issues you hit upstream. +dev-lang/python gil + +# Sam James <sam@gentoo.org> (2024-06-03) +# Poor rendering performance otherwise (bug #931215). +kde-plasma/kwin caps + +# James Le Cuirot <chewi@gentoo.org> (2024-06-02) +# Requires FFmpeg 7.0, which we don't have yet, so force Chromium fork. +>=dev-libs/nwjs-0.88.0 ffmpeg-chromium +>=www-client/vivaldi-6.8.3371.4 ffmpeg-chromium +>=www-client/vivaldi-snapshot-6.8.3371.4 ffmpeg-chromium + # Ionen Wolkens <ionen@gentoo.org> (2024-04-10) # Flipping the zstd USE state is unsafe and can break *tons* of Qt revdeps # including many KDE packages and Qt itself without rebuilds due to losing @@ -174,10 +196,6 @@ net-misc/wget ssl # is maintained for experts only. sys-libs/libcxx libcxxabi -# Matt Turner <mattst88@gentoo.org> (2019-09-01) -# <dev-scheme/guile-2 is package.mask'd, so force USE=guile2 -media-sound/lilypond guile2 - # Sergei Trofimovich <slyfox@gentoo.org> (2019-08-17) # USE=-cxx us a sure way to break native install as modern gcc # requires C++ to bootstrap. But in rare cases it's useful @@ -218,7 +236,6 @@ sys-firmware/seabios binary net-analyzer/snort libtirpc net-fs/autofs libtirpc net-misc/netkit-bootparamd libtirpc -sci-astronomy/esomidas libtirpc sys-cluster/glusterfs libtirpc # Maciej Mrozowski <reavertm@gentoo.org> (2016-09-01) diff --git a/profiles/base/package.use.mask b/profiles/base/package.use.mask index aaf0abe073b1..1066cfb7f764 100644 --- a/profiles/base/package.use.mask +++ b/profiles/base/package.use.mask @@ -3,12 +3,74 @@ # New entries go on top. +# Volkmar W. Pogatzki <gentoo@pogatzki.net> (2024-09-21) +# openjfx for OpenJDK 23 is not yet available. +dev-java/openjdk:23 javafx + # This file is only for generic masks. For arch-specific masks (i.e. # mask everywhere, unmask on arch/*) use arch/base. -# Michał Górny <mgorny@gentoo.org> (2024-05-18) -# dev-python/aesara is being removed. -dev-python/sympy aesara +# Sam James <sam@gentoo.org> (2024-09-30) +# gnat-gpl is purely for bootstrapping Ada and it's based on an old +# version of GCC. Avoid risks of miscompilations. +dev-lang/gnat-gpl pgo lto + +# Patrick McLean <chutzpah@gentoo.org> (2024-09-23) +# Only supported on x86/amd64 (bug #940014). +net-misc/lldpd seccomp + +# Volkmar W. Pogatzki <gentoo@pogatzki.net> (2024-09-12) +# No suitable version of dev-libs/protobuf available. +=dev-java/protobuf-java-4.28.1 system-protoc + +# Sam James <sam@gentoo.org> (2024-09-07) +# yacc[reference] exists more for curiosity than anything else, it's +# not for real use on systems. +app-alternatives/yacc reference + +# Sam James <sam@gentoo.org> (2024-09-03) +# Causes crashes with e.g. dlz+samba (bug #938955) +net-dns/bind jemalloc + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-02) +# kde-plasma/print-manager:5 and kde-apps/khelpcenter:5 cleanup +kde-plasma/plasma-meta:5 cups handbook + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-02) +# Prepare kde-apps/kaccounts-integration:5 cleanup +kde-plasma/plasma-desktop:5 kaccounts +kde-plasma/plasma-welcome:5 kaccounts + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-01) +# Prepare for dev-util/kdevelop:5 removal +kde-apps/umbrello:5 php + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-08-31) +# Prepare for KDE PIM 5 removal and avoid conflicts w/ KDE PIM 6 +app-office/kmymoney:5 addressbook +app-office/kraft:5 pim + +# orbea <orbea@riseup.net> (2024-07-19) +# The dynarec is only supported upstream for amd64, arm, arm64 and x86. +games-emulation/rmg dynarec + +# Maciej Mrozowski <reavertm@gentoo.org> (2024-07-14) +# Fails with newer ffmpeg, bug #831486 +# Not needed by reverse deps as of 2024-07-14. Re-enable when +# https://github.com/openscenegraph/OpenSceneGraph/pull/1281 or +# similar effort is upstreamed +dev-games/openscenegraph ffmpeg + +# Michał Górny <mgorny@gentoo.org> (2024-06-29) +# JIT is experimental and prone to break packages. Should you choose +# to use it, please do not file Gentoo bugs and report any issues you +# hit upstream. +dev-lang/python jit + +# Sam James <sam@gentoo.org> (2024-06-24) +# Breaks installed gems in hard-to-debug ways. +# bug #887223, bug #891367, bug #903891, bug #917139 +dev-lang/ruby static-libs # Sam James <sam@gentoo.org> (2024-05-09) # Experimental option upstream which seems undertested and underdocumented. @@ -18,7 +80,7 @@ net-misc/openssh xmss # Matt Turner <mattst88@gentoo.org> (2024-05-08) # Brand new, introduces lots of new aspects to the build. # Masked for further testing. -media-libs/mesa video_cards_nvk +<media-libs/mesa-24.2 video_cards_nvk # Michał Górny <mgorny@gentoo.org> (2024-04-27) # dev-python/uv is nowhere near ready to be stabilized. @@ -33,31 +95,10 @@ app-admin/testdisk ewf # Wayland client is broken/deprecated by upstream. Bug 930197. >=net-misc/freerdp-3 wayland -# Andreas Sturmlechner <asturm@gentoo.org> (2024-04-06) -# Depends on last-rited kde-apps/ktp-accounts-kcm -dev-util/kdevelop reviewboard - # Michał Górny <mgorny@gentoo.org> (2024-03-26) # sys-auth/pam_ssh is being last rited, bug #892031. sys-auth/pambase pam_ssh -# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-22) -# Building with qt6 requires (masked) kde-frameworks:6 -app-admin/calamares qt6 - -# Viorel Munteanu <ceamac@gentoo.org> (2024-03-19) -# The live version needs a new BDEPEND for doc -=app-emulation/virtualbox-9999 doc - -# Sam James <sam@gentoo.org> (2024-03-18) -# Needs masked KF6 for Wayland at least. -app-crypt/pinentry qt6 - -# Michał Górny <mgorny@gentoo.org> (2024-03-17) -# Suffers from unaligned accesses, upstream's working on it. -# https://github.com/psycopg/psycopg/issues/734 -<=dev-python/psycopg-3.1.18 native-extensions - # Guilherme Amadio <amadio@gentoo.org> (2024-03-09) # Requires manually installing dependencies, see bug #791802 # Please use MYCMAKEARGS instead. @@ -200,7 +241,7 @@ app-admin/ansible-molecule doc # William Hubbs <williamh@gentoo.org> (2023-06-30) # multiple repeated issues: Bug: #909394 # Joonas Niilola <juippis@gentoo.org> (2024-04-22) -# Can break reverse dependencies (Chromium, Firefox), debugging not always +# Can break reverse dependencies (Chromium, Firefox), debugging not always # obvious. net-libs/nodejs lto @@ -213,11 +254,6 @@ dev-libs/openssl sslv2 sslv3 # Needs <dev-libs/openssl-3 which is EOL beyond September 2023. net-misc/curl sslv3 -# Volkmar W. Pogatzki <gentoo@pogatzki.net> (2023-05-04) -# No suitable version of dev-libs/protobuf available. ->=dev-java/protobuf-java-3.24.2 system-protoc -=dev-java/protobuf-java-3.23.0 system-protoc - # Joonas Niilola <juippis@gentoo.org> (2023-06-06) # Runtime not tested, may require more configuration in the ebuild. # Bug: #906509. @@ -273,10 +309,6 @@ sci-libs/vtk debug # See also: https://bugs.gentoo.org/891499 sys-libs/libomp llvm_targets_AMDGPU -# Sam James <sam@gentoo.org> (2023-01-21) -# Fails to compile: https://github.com/libffi/libffi/issues/760 -<dev-libs/libffi-3.4.4-r4 exec-static-trampoline - # Joonas Niilola <juippis@gentoo.org> (2023-01-08) # Doesn't compile currently, bug #853094. >=net-dialup/freeradius-3.2.0 oracle @@ -294,10 +326,6 @@ app-misc/pax-utils seccomp # Broken when trying to use sys-libs/binutils-libs header, bug #879067 >=x11-libs/cairo-1.17.6 debug -# Joonas Niilola <juippis@gentoo.org> (2022-11-25) -# x11-wm/stumpwm-22.05_p20220818[doc] is totally broken. Bug #882935 -x11-wm/stumpwm doc - # Bernd Waibel <waebbl-gentoo@posteo.net> (2022-11-25) # USE=tbb is broken in 7.7.0 # https://tracker.dev.opencascade.org/view.php?id=33152 @@ -575,13 +603,9 @@ dev-php/fedora-autoloader test dev-php/json-schema test dev-php/jsonlint test dev-php/recaptcha test -dev-php/symfony-config test -dev-php/symfony-dependency-injection test -dev-php/symfony-event-dispatcher test dev-php/symfony-filesystem test dev-php/symfony-finder test dev-php/symfony-process test -dev-php/symfony-yaml test dev-php/theseer-Autoload test dev-php/twig test @@ -649,10 +673,6 @@ dev-python/autobahn xbr # Dependency pam_wrapper missing for tests, and RESTRICT=test is already set net-fs/samba test -# Mike Gilbert <floppym@gentoo.org> (2020-04-23) -# Tests are very sensitive to the host environment. -dev-build/meson test - # Alfredo Tupone <tupone@gentoo.org> (2020-04-04) # Ada support is not yet ready for sys-devel/gcc sys-devel/gcc ada @@ -691,7 +711,7 @@ dev-python/statsmodels doc # Craig Andrews <candrews@gentoo.org> (2019-09-12) # OpenSSL (as of version 1.1.1) doesn't have APIs for QUIC support # see https://github.com/openssl/openssl/pull/8797 -net-libs/ngtcp2 ssl +net-libs/ngtcp2 openssl net-misc/curl nghttp3 # Thomas Deutschmann <whissi@gentoo.org> (2019-09-02) @@ -807,7 +827,6 @@ app-emulation/libvirt openvz # need or even advantage to set custom compiler flags at all. # Example: bug #619628 sys-boot/gnu-efi custom-cflags -sys-boot/refind custom-cflags # Andreas K. Hüttel <dilfridge@gentoo.org> (2017-05-29) # Does not build diff --git a/profiles/base/package.use.stable.mask b/profiles/base/package.use.stable.mask index fd8790053fa9..abb59cb7f4e6 100644 --- a/profiles/base/package.use.stable.mask +++ b/profiles/base/package.use.stable.mask @@ -4,24 +4,22 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in package.use.mask -# Ionen Wolkens <ionen@gentoo.org> (2024-05-07) -# ffmpeg[soc] is not stable yet -media-video/mpv soc - -# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-04-14) -# Qt6 dependencies are not yet available in stable. Moreover, -# Qt6 support in freecad is not completely finished. -media-gfx/freecad qt6 +# Andreas Sturmlechner <asturm@gentoo.org> (2024-08-29) +# Pin down kf6compat mask to currently stable versions. +<kde-apps/kio-extras-24.02.2-r2 kf6compat +<kde-apps/libkgapi-23.08.5-r2 kf6compat +<kde-frameworks/baloo-5.116.0-r1 kf6compat +<kde-frameworks/kglobalaccel-5.116.0-r1 kf6compat +<kde-frameworks/kguiaddons-5.116.0-r1 kf6compat +<kde-frameworks/kuserfeedback-1.3.0-r4 kf6compat +<kde-frameworks/kwallet-5.116.0-r1 kf6compat +<kde-plasma/libplasma-5.116.0-r1 kf6compat # Joonas Niilola <juippis@gentoo.org> (2023-07-14) # Calendar is broken with some languages on 115.0 release with <icu-75. # Bug #910229, #920713 >=mail-client/thunderbird-115.0 system-icu -# Sam James <sam@gentoo.org> (2023-10-23) -# Requires llvm-17. ->=www-client/chromium-118 libcxx lto pgo - # Michał Górny <mgorny@gentoo.org> (2023-06-11) # xfce-base/libxfce4windowing is not ready to go stable (4.19 branch). xfce-extra/xfce4-pulseaudio-plugin libxfce4windowing @@ -177,10 +175,6 @@ sys-auth/pambase sssd # Needs dev-ruby/asciidoctor which has a lot of unstable deps net-analyzer/wireshark doc -# Matthias Maier <tamiko@gentoo.org> (2018-03-18) -# dev-libs/capstone hasn't been stabilized yet -app-emulation/qemu capstone - # Kent Fredric <kentnl@gentoo.org> (2018-03-03) # Not an officially supported configuration, as it causes unpredictable # fragility and/or dependency headaches due to the very narrow interop window diff --git a/profiles/base/use.mask b/profiles/base/use.mask index 392c76f40109..3db1ca5d5430 100644 --- a/profiles/base/use.mask +++ b/profiles/base/use.mask @@ -13,10 +13,6 @@ perl_features_debug # Telepathy is dead and packages masked for removal. telepathy -# Andreas Sturmlechner <asturm@gentoo.org> (2023-12-15) -# KF6 is not in ::gentoo yet. Move to stable.use.mask on KF6 intro. -kf6compat - # Hans de Graaff <graaff@gentoo.org> (2023-08-19) # Ruby 3.0 is not compatible with OpenSSL 3. Please upgrade to a newer # Ruby version. diff --git a/profiles/base/use.stable.mask b/profiles/base/use.stable.mask index ee3bba441b93..9167592b9e10 100644 --- a/profiles/base/use.stable.mask +++ b/profiles/base/use.stable.mask @@ -4,6 +4,14 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in use.mask +# Patrick Lauer <patrick@gentoo.org> (2024-09-26) +# Postgresql 17 isn't stable yet +postgres_targets_postgres17 + +# Sam James <sam@gentoo.org> (2024-09-18) +# LLVM slots without stable keywords. +llvm_slot_19 + # Michał Górny <mgorny@gentoo.org> (2024-05-08) # Python implementations without stable keywords. python_targets_python3_13 @@ -11,10 +19,6 @@ python_single_target_python3_13 python_targets_pypy3 python_single_target_pypy3 -# Michał Górny <mgorny@gentoo.org> (2024-04-04) -# LLVM slots without stablekeywords. -llvm_slot_18 - # Hans de Graaff <graaff@gentoo.org> (2023-12-25) # Currently in testing and not ready to go stable yet. ruby_targets_ruby33 diff --git a/profiles/default/linux/alpha/17.0/deprecated b/profiles/default/linux/alpha/17.0/deprecated new file mode 100644 index 000000000000..3cee56363026 --- /dev/null +++ b/profiles/default/linux/alpha/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/split-usr + +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 diff --git a/profiles/default/linux/alpha/17.0/desktop/deprecated b/profiles/default/linux/alpha/17.0/desktop/deprecated new file mode 100644 index 000000000000..5250cf03f640 --- /dev/null +++ b/profiles/default/linux/alpha/17.0/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/split-usr/desktop + +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 diff --git a/profiles/default/linux/alpha/17.0/desktop/gnome/deprecated b/profiles/default/linux/alpha/17.0/desktop/gnome/deprecated new file mode 100644 index 000000000000..9a079e68bef3 --- /dev/null +++ b/profiles/default/linux/alpha/17.0/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/split-usr/desktop/gnome + +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 diff --git a/profiles/default/linux/alpha/17.0/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/alpha/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..eca25d7adc43 --- /dev/null +++ b/profiles/default/linux/alpha/17.0/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/desktop/gnome/systemd + +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 diff --git a/profiles/default/linux/alpha/17.0/developer/deprecated b/profiles/default/linux/alpha/17.0/developer/deprecated new file mode 100644 index 000000000000..3cee56363026 --- /dev/null +++ b/profiles/default/linux/alpha/17.0/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/split-usr + +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 diff --git a/profiles/default/linux/alpha/17.0/systemd/merged-usr/deprecated b/profiles/default/linux/alpha/17.0/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..217bbccd2dac --- /dev/null +++ b/profiles/default/linux/alpha/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/systemd + +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 diff --git a/profiles/default/linux/amd64/17.0/musl/clang/deprecated b/profiles/default/linux/amd64/17.0/musl/clang/deprecated new file mode 100644 index 000000000000..f4c5ed652f3e --- /dev/null +++ b/profiles/default/linux/amd64/17.0/musl/clang/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/musl/llvm + +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 diff --git a/profiles/default/linux/amd64/17.0/musl/deprecated b/profiles/default/linux/amd64/17.0/musl/deprecated new file mode 100644 index 000000000000..fb300c26f9ab --- /dev/null +++ b/profiles/default/linux/amd64/17.0/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/musl + +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 diff --git a/profiles/default/linux/amd64/17.0/musl/hardened/deprecated b/profiles/default/linux/amd64/17.0/musl/hardened/deprecated new file mode 100644 index 000000000000..20c9fedaf0a9 --- /dev/null +++ b/profiles/default/linux/amd64/17.0/musl/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/musl/hardened + +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 diff --git a/profiles/default/linux/amd64/17.0/musl/hardened/selinux/deprecated b/profiles/default/linux/amd64/17.0/musl/hardened/selinux/deprecated new file mode 100644 index 000000000000..d11cd2c3257f --- /dev/null +++ b/profiles/default/linux/amd64/17.0/musl/hardened/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/musl/hardened/selinux + +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 diff --git a/profiles/default/linux/amd64/17.0/x32/deprecated b/profiles/default/linux/amd64/17.0/x32/deprecated new file mode 100644 index 000000000000..69d1807d0750 --- /dev/null +++ b/profiles/default/linux/amd64/17.0/x32/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/x32 + +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 diff --git a/profiles/default/linux/amd64/17.0/x32/systemd/merged-usr/deprecated b/profiles/default/linux/amd64/17.0/x32/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..1b330827394f --- /dev/null +++ b/profiles/default/linux/amd64/17.0/x32/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/x32/systemd + +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 diff --git a/profiles/default/linux/amd64/17.1/clang/deprecated b/profiles/default/linux/amd64/17.1/clang/deprecated new file mode 100644 index 000000000000..1087d3e33977 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/clang/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/llvm + +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 diff --git a/profiles/default/linux/amd64/17.1/deprecated b/profiles/default/linux/amd64/17.1/deprecated new file mode 100644 index 000000000000..1dfba2cdb1f0 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr + +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 diff --git a/profiles/default/linux/amd64/17.1/desktop/deprecated b/profiles/default/linux/amd64/17.1/desktop/deprecated new file mode 100644 index 000000000000..04b8c3bd66fd --- /dev/null +++ b/profiles/default/linux/amd64/17.1/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/desktop + +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 diff --git a/profiles/default/linux/amd64/17.1/desktop/gnome/deprecated b/profiles/default/linux/amd64/17.1/desktop/gnome/deprecated new file mode 100644 index 000000000000..2b8cce7ee0eb --- /dev/null +++ b/profiles/default/linux/amd64/17.1/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/desktop/gnome + +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 diff --git a/profiles/default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..bb2fc8dfd7fa --- /dev/null +++ b/profiles/default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/desktop/gnome/systemd + +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 diff --git a/profiles/default/linux/amd64/17.1/desktop/plasma/deprecated b/profiles/default/linux/amd64/17.1/desktop/plasma/deprecated new file mode 100644 index 000000000000..e0f4c8a25372 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/desktop/plasma + +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 diff --git a/profiles/default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr/deprecated b/profiles/default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..1a027e1ea361 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/desktop/plasma/systemd + +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 diff --git a/profiles/default/linux/amd64/17.1/desktop/systemd/merged-usr/deprecated b/profiles/default/linux/amd64/17.1/desktop/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..f8443e5de5a9 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/desktop/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/desktop/systemd + +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 diff --git a/profiles/default/linux/amd64/17.1/developer/deprecated b/profiles/default/linux/amd64/17.1/developer/deprecated new file mode 100644 index 000000000000..1dfba2cdb1f0 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr + +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 diff --git a/profiles/default/linux/amd64/17.1/hardened/deprecated b/profiles/default/linux/amd64/17.1/hardened/deprecated new file mode 100644 index 000000000000..f1d39a57a31e --- /dev/null +++ b/profiles/default/linux/amd64/17.1/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/hardened + +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 diff --git a/profiles/default/linux/amd64/17.1/hardened/selinux/deprecated b/profiles/default/linux/amd64/17.1/hardened/selinux/deprecated new file mode 100644 index 000000000000..3996638f2a19 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/hardened/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/hardened/selinux + +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 diff --git a/profiles/default/linux/amd64/17.1/no-multilib/deprecated b/profiles/default/linux/amd64/17.1/no-multilib/deprecated new file mode 100644 index 000000000000..33a1cf4ea272 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/no-multilib/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/no-multilib + +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 diff --git a/profiles/default/linux/amd64/17.1/no-multilib/hardened/deprecated b/profiles/default/linux/amd64/17.1/no-multilib/hardened/deprecated new file mode 100644 index 000000000000..7f6226b8021b --- /dev/null +++ b/profiles/default/linux/amd64/17.1/no-multilib/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/no-multilib/hardened + +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 diff --git a/profiles/default/linux/amd64/17.1/no-multilib/hardened/selinux/deprecated b/profiles/default/linux/amd64/17.1/no-multilib/hardened/selinux/deprecated new file mode 100644 index 000000000000..55b586baed3c --- /dev/null +++ b/profiles/default/linux/amd64/17.1/no-multilib/hardened/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux + +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 diff --git a/profiles/default/linux/amd64/17.1/no-multilib/systemd/merged-usr/deprecated b/profiles/default/linux/amd64/17.1/no-multilib/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..5dffabddd095 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/no-multilib/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/no-multilib/systemd + +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 diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/deprecated b/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/deprecated index 36bae5bdb267..0a7d7473d192 100644 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/deprecated +++ b/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/deprecated @@ -1,4 +1,4 @@ -default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr +default/linux/amd64/17.1/no-multilib/systemd/selinux/merged-usr As warned about previously in a news item, systemd-255 has dropped support for split-usr systems. All Gentoo systems running systemd will diff --git a/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/merged-usr/deprecated b/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/merged-usr/deprecated new file mode 100644 index 000000000000..ca932ac65f68 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd + +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 diff --git a/profiles/default/linux/amd64/17.1/selinux/deprecated b/profiles/default/linux/amd64/17.1/selinux/deprecated new file mode 100644 index 000000000000..3996638f2a19 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/hardened/selinux + +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 diff --git a/profiles/default/linux/ia64/17.0/systemd/deprecated b/profiles/default/linux/amd64/17.1/systemd/clang/deprecated index 37010bfe7dbf..e5a3dd1d758e 100644 --- a/profiles/default/linux/ia64/17.0/systemd/deprecated +++ b/profiles/default/linux/amd64/17.1/systemd/clang/deprecated @@ -1,4 +1,4 @@ -default/linux/ia64/17.0/systemd/merged-usr +default/linux/amd64/17.1/systemd/clang/merged-usr As warned about previously in a news item, systemd-255 has dropped support for split-usr systems. All Gentoo systems running systemd will diff --git a/profiles/default/linux/amd64/17.1/systemd/clang/merged-usr/deprecated b/profiles/default/linux/amd64/17.1/systemd/clang/merged-usr/deprecated new file mode 100644 index 000000000000..aa61cab28ddc --- /dev/null +++ b/profiles/default/linux/amd64/17.1/systemd/clang/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/llvm/systemd + +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 diff --git a/profiles/default/linux/amd64/17.1/systemd/merged-usr/deprecated b/profiles/default/linux/amd64/17.1/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..0da73aecf99a --- /dev/null +++ b/profiles/default/linux/amd64/17.1/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/systemd + +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 diff --git a/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/deprecated b/profiles/default/linux/amd64/17.1/systemd/selinux/deprecated index e91b42445e45..736342a22121 100644 --- a/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/deprecated +++ b/profiles/default/linux/amd64/17.1/systemd/selinux/deprecated @@ -1,4 +1,4 @@ -default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr +default/linux/amd64/17.1/systemd/selinux/merged-usr As warned about previously in a news item, systemd-255 has dropped support for split-usr systems. All Gentoo systems running systemd will diff --git a/profiles/default/linux/amd64/17.1/systemd/selinux/merged-usr/deprecated b/profiles/default/linux/amd64/17.1/systemd/selinux/merged-usr/deprecated new file mode 100644 index 000000000000..e0853bb8ea72 --- /dev/null +++ b/profiles/default/linux/amd64/17.1/systemd/selinux/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/hardened/selinux/systemd + +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 diff --git a/profiles/default/linux/arm/17.0/armv4/deprecated b/profiles/default/linux/arm/17.0/armv4/deprecated new file mode 100644 index 000000000000..45b5c52341c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv4/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4 + +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 diff --git a/profiles/default/linux/arm/17.0/armv4/desktop/deprecated b/profiles/default/linux/arm/17.0/armv4/desktop/deprecated new file mode 100644 index 000000000000..45b5c52341c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv4/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4 + +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 diff --git a/profiles/default/linux/arm/17.0/armv4/desktop/gnome/deprecated b/profiles/default/linux/arm/17.0/armv4/desktop/gnome/deprecated new file mode 100644 index 000000000000..45b5c52341c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv4/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4 + +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 diff --git a/profiles/default/linux/arm/17.0/armv4/desktop/plasma/deprecated b/profiles/default/linux/arm/17.0/armv4/desktop/plasma/deprecated new file mode 100644 index 000000000000..45b5c52341c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv4/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4 + +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 diff --git a/profiles/default/linux/arm/17.0/armv4/developer/deprecated b/profiles/default/linux/arm/17.0/armv4/developer/deprecated new file mode 100644 index 000000000000..45b5c52341c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv4/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4 + +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 diff --git a/profiles/default/linux/arm/17.0/armv4t/deprecated b/profiles/default/linux/arm/17.0/armv4t/deprecated new file mode 100644 index 000000000000..97e893728d18 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv4t/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4t + +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 diff --git a/profiles/default/linux/arm/17.0/armv4t/desktop/deprecated b/profiles/default/linux/arm/17.0/armv4t/desktop/deprecated new file mode 100644 index 000000000000..97e893728d18 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv4t/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4t + +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 diff --git a/profiles/default/linux/arm/17.0/armv4t/desktop/gnome/deprecated b/profiles/default/linux/arm/17.0/armv4t/desktop/gnome/deprecated new file mode 100644 index 000000000000..97e893728d18 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv4t/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4t + +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 diff --git a/profiles/default/linux/arm/17.0/armv4t/desktop/plasma/deprecated b/profiles/default/linux/arm/17.0/armv4t/desktop/plasma/deprecated new file mode 100644 index 000000000000..97e893728d18 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv4t/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4t + +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 diff --git a/profiles/default/linux/arm/17.0/armv4t/developer/deprecated b/profiles/default/linux/arm/17.0/armv4t/developer/deprecated new file mode 100644 index 000000000000..97e893728d18 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv4t/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4t + +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 diff --git a/profiles/default/linux/arm/17.0/armv4t/systemd/merged-usr/deprecated b/profiles/default/linux/arm/17.0/armv4t/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..39e9ddab5c5d --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv4t/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/armv4t/systemd + +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 diff --git a/profiles/default/linux/arm/17.0/armv5te/deprecated b/profiles/default/linux/arm/17.0/armv5te/deprecated new file mode 100644 index 000000000000..021c24a339ac --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv5te/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv5te + +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 diff --git a/profiles/default/linux/arm/17.0/armv5te/desktop/deprecated b/profiles/default/linux/arm/17.0/armv5te/desktop/deprecated new file mode 100644 index 000000000000..021c24a339ac --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv5te/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv5te + +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 diff --git a/profiles/default/linux/arm/17.0/armv5te/desktop/gnome/deprecated b/profiles/default/linux/arm/17.0/armv5te/desktop/gnome/deprecated new file mode 100644 index 000000000000..021c24a339ac --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv5te/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv5te + +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 diff --git a/profiles/default/linux/arm/17.0/armv5te/desktop/plasma/deprecated b/profiles/default/linux/arm/17.0/armv5te/desktop/plasma/deprecated new file mode 100644 index 000000000000..021c24a339ac --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv5te/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv5te + +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 diff --git a/profiles/default/linux/arm/17.0/armv5te/developer/deprecated b/profiles/default/linux/arm/17.0/armv5te/developer/deprecated new file mode 100644 index 000000000000..021c24a339ac --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv5te/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv5te + +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 diff --git a/profiles/default/linux/arm/17.0/armv5te/systemd/merged-usr/deprecated b/profiles/default/linux/arm/17.0/armv5te/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..7721e0101edb --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv5te/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/armv5te/systemd + +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 diff --git a/profiles/default/linux/arm/17.0/armv6j/deprecated b/profiles/default/linux/arm/17.0/armv6j/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv6j/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv6j/desktop/deprecated b/profiles/default/linux/arm/17.0/armv6j/desktop/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv6j/desktop/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv6j/desktop/gnome/deprecated b/profiles/default/linux/arm/17.0/armv6j/desktop/gnome/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv6j/desktop/gnome/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv6j/desktop/plasma/deprecated b/profiles/default/linux/arm/17.0/armv6j/desktop/plasma/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv6j/desktop/plasma/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv6j/developer/deprecated b/profiles/default/linux/arm/17.0/armv6j/developer/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv6j/developer/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv6j/hardened/deprecated b/profiles/default/linux/arm/17.0/armv6j/hardened/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv6j/hardened/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv6j/hardened/selinux/deprecated b/profiles/default/linux/arm/17.0/armv6j/hardened/selinux/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv6j/hardened/selinux/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv6j/selinux/deprecated b/profiles/default/linux/arm/17.0/armv6j/selinux/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv6j/selinux/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv6j/systemd/merged-usr/deprecated b/profiles/default/linux/arm/17.0/armv6j/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv6j/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv7a/deprecated b/profiles/default/linux/arm/17.0/armv7a/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv7a/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv7a/desktop/deprecated b/profiles/default/linux/arm/17.0/armv7a/desktop/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv7a/desktop/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/deprecated b/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/deprecated b/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/systemd/merged-usr/deprecated b/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv7a/developer/deprecated b/profiles/default/linux/arm/17.0/armv7a/developer/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv7a/developer/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv7a/hardened/deprecated b/profiles/default/linux/arm/17.0/armv7a/hardened/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv7a/hardened/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv7a/hardened/selinux/deprecated b/profiles/default/linux/arm/17.0/armv7a/hardened/selinux/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv7a/hardened/selinux/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/armv7a/systemd/merged-usr/deprecated b/profiles/default/linux/arm/17.0/armv7a/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/armv7a/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/arm/17.0/deprecated b/profiles/default/linux/arm/17.0/deprecated new file mode 100644 index 000000000000..ebd06e20749f --- /dev/null +++ b/profiles/default/linux/arm/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr + +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 diff --git a/profiles/default/linux/arm/17.0/desktop/deprecated b/profiles/default/linux/arm/17.0/desktop/deprecated new file mode 100644 index 000000000000..b65e6c8df8d5 --- /dev/null +++ b/profiles/default/linux/arm/17.0/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/desktop + +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 diff --git a/profiles/default/linux/arm/17.0/desktop/gnome/deprecated b/profiles/default/linux/arm/17.0/desktop/gnome/deprecated new file mode 100644 index 000000000000..51ad785cb389 --- /dev/null +++ b/profiles/default/linux/arm/17.0/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/desktop/gnome + +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 diff --git a/profiles/default/linux/arm/17.0/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/arm/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..e79024de0325 --- /dev/null +++ b/profiles/default/linux/arm/17.0/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/desktop/gnome/systemd + +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 diff --git a/profiles/default/linux/arm/17.0/desktop/plasma/deprecated b/profiles/default/linux/arm/17.0/desktop/plasma/deprecated new file mode 100644 index 000000000000..4e44c2757acc --- /dev/null +++ b/profiles/default/linux/arm/17.0/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/desktop/plasma + +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 diff --git a/profiles/default/linux/arm/17.0/desktop/plasma/systemd/merged-usr/deprecated b/profiles/default/linux/arm/17.0/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..df5a51661dd0 --- /dev/null +++ b/profiles/default/linux/arm/17.0/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/desktop/plasma/systemd + +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 diff --git a/profiles/default/linux/arm/17.0/developer/deprecated b/profiles/default/linux/arm/17.0/developer/deprecated new file mode 100644 index 000000000000..ebd06e20749f --- /dev/null +++ b/profiles/default/linux/arm/17.0/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr + +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 diff --git a/profiles/default/linux/arm/17.0/musl/armv6j/deprecated b/profiles/default/linux/arm/17.0/musl/armv6j/deprecated new file mode 100644 index 000000000000..5d36c73cd850 --- /dev/null +++ b/profiles/default/linux/arm/17.0/musl/armv6j/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv6j_hf/musl + +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 diff --git a/profiles/default/linux/arm/17.0/musl/armv6j/hardened/deprecated b/profiles/default/linux/arm/17.0/musl/armv6j/hardened/deprecated new file mode 100644 index 000000000000..de12cbfb2272 --- /dev/null +++ b/profiles/default/linux/arm/17.0/musl/armv6j/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv6j_hf/musl/hardened + +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 diff --git a/profiles/default/linux/arm/17.0/musl/armv6j/hardened/selinux/deprecated b/profiles/default/linux/arm/17.0/musl/armv6j/hardened/selinux/deprecated new file mode 100644 index 000000000000..32c22267e806 --- /dev/null +++ b/profiles/default/linux/arm/17.0/musl/armv6j/hardened/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv6j_hf/musl/hardened/selinux + +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 diff --git a/profiles/default/linux/arm/17.0/musl/armv7a/deprecated b/profiles/default/linux/arm/17.0/musl/armv7a/deprecated new file mode 100644 index 000000000000..6fc6daceb3ca --- /dev/null +++ b/profiles/default/linux/arm/17.0/musl/armv7a/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv7a_hf/musl + +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 diff --git a/profiles/default/linux/arm/17.0/musl/armv7a/hardened/deprecated b/profiles/default/linux/arm/17.0/musl/armv7a/hardened/deprecated new file mode 100644 index 000000000000..b06f94740d02 --- /dev/null +++ b/profiles/default/linux/arm/17.0/musl/armv7a/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv7a_hf/musl/hardened + +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 diff --git a/profiles/default/linux/arm/17.0/musl/armv7a/hardened/selinux/deprecated b/profiles/default/linux/arm/17.0/musl/armv7a/hardened/selinux/deprecated new file mode 100644 index 000000000000..05defdaa7231 --- /dev/null +++ b/profiles/default/linux/arm/17.0/musl/armv7a/hardened/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv7a_hf/musl/hardened/selinux + +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 diff --git a/profiles/default/linux/arm/17.0/musl/parent b/profiles/default/linux/arm/17.0/musl/parent index 468c1fa0a937..a5858d7a3c50 100644 --- a/profiles/default/linux/arm/17.0/musl/parent +++ b/profiles/default/linux/arm/17.0/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../arch/arm ../../../../../features/musl +../../../../../features/wd40 diff --git a/profiles/default/linux/arm/23.0/armv6j_hf/musl/package.use.stable.mask b/profiles/default/linux/arm/23.0/armv6j_hf/musl/package.use.mask index c021f45d8508..c021f45d8508 100644 --- a/profiles/default/linux/arm/23.0/armv6j_hf/musl/package.use.stable.mask +++ b/profiles/default/linux/arm/23.0/armv6j_hf/musl/package.use.mask diff --git a/profiles/default/linux/arm/23.0/armv6j_hf/musl/parent b/profiles/default/linux/arm/23.0/armv6j_hf/musl/parent index 5bbe8700f1a6..bd0ef6ecac62 100644 --- a/profiles/default/linux/arm/23.0/armv6j_hf/musl/parent +++ b/profiles/default/linux/arm/23.0/armv6j_hf/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../../features/musl +../../../../../../features/wd40 diff --git a/profiles/default/linux/arm/23.0/armv7a_hf/musl/package.use.stable.mask b/profiles/default/linux/arm/23.0/armv7a_hf/musl/package.use.mask index c021f45d8508..c021f45d8508 100644 --- a/profiles/default/linux/arm/23.0/armv7a_hf/musl/package.use.stable.mask +++ b/profiles/default/linux/arm/23.0/armv7a_hf/musl/package.use.mask diff --git a/profiles/default/linux/arm/23.0/armv7a_hf/musl/parent b/profiles/default/linux/arm/23.0/armv7a_hf/musl/parent index 5bbe8700f1a6..bd0ef6ecac62 100644 --- a/profiles/default/linux/arm/23.0/armv7a_hf/musl/parent +++ b/profiles/default/linux/arm/23.0/armv7a_hf/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../../features/musl +../../../../../../features/wd40 diff --git a/profiles/default/linux/arm/23.0/musl/package.use.stable.mask b/profiles/default/linux/arm/23.0/musl/package.use.stable.mask index c021f45d8508..785b52ceb864 100644 --- a/profiles/default/linux/arm/23.0/musl/package.use.stable.mask +++ b/profiles/default/linux/arm/23.0/musl/package.use.stable.mask @@ -1,6 +1,11 @@ # Copyright 2024 Gentoo Authors # Distributed under the terms of the GNU General Public License, v2 +# Sam James <sam@gentoo.org> (2024-06-16) +# Avoid pulling in sys-libs/compiler-rt-sanitizers which fails to build +# See bug #928936. +sys-devel/clang-runtime sanitize + # Andreas K. Hüttel <dilfridge@gentoo.org> (2024-03-20) # Does not compile with musl-1.2.4 sys-devel/gcc sanitize diff --git a/profiles/default/linux/arm/23.0/musl/parent b/profiles/default/linux/arm/23.0/musl/parent index 468c1fa0a937..a5858d7a3c50 100644 --- a/profiles/default/linux/arm/23.0/musl/parent +++ b/profiles/default/linux/arm/23.0/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../arch/arm ../../../../../features/musl +../../../../../features/wd40 diff --git a/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/package.use.stable.mask b/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/package.use.mask index c021f45d8508..c021f45d8508 100644 --- a/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/package.use.stable.mask +++ b/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/package.use.mask diff --git a/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/parent b/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/parent index b488e1ca01b8..a3de2bcf95f7 100644 --- a/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/parent +++ b/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../../../features/musl +../../../../../../../features/wd40 diff --git a/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/package.use.stable.mask b/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/package.use.mask index c021f45d8508..c021f45d8508 100644 --- a/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/package.use.stable.mask +++ b/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/package.use.mask diff --git a/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/parent b/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/parent index b488e1ca01b8..a3de2bcf95f7 100644 --- a/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/parent +++ b/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../../../features/musl +../../../../../../../features/wd40 diff --git a/profiles/default/linux/arm/23.0/split-usr/musl/parent b/profiles/default/linux/arm/23.0/split-usr/musl/parent index 5bbe8700f1a6..bd0ef6ecac62 100644 --- a/profiles/default/linux/arm/23.0/split-usr/musl/parent +++ b/profiles/default/linux/arm/23.0/split-usr/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../../features/musl +../../../../../../features/wd40 diff --git a/profiles/default/linux/arm64/17.0/big-endian/deprecated b/profiles/default/linux/arm64/17.0/big-endian/deprecated new file mode 100644 index 000000000000..680df0d1ab93 --- /dev/null +++ b/profiles/default/linux/arm64/17.0/big-endian/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/big-endian + +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 diff --git a/profiles/default/linux/arm64/17.0/big-endian/systemd/merged-usr/deprecated b/profiles/default/linux/arm64/17.0/big-endian/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..c59e6961886c --- /dev/null +++ b/profiles/default/linux/arm64/17.0/big-endian/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/big-endian/systemd + +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 diff --git a/profiles/default/linux/arm64/17.0/deprecated b/profiles/default/linux/arm64/17.0/deprecated new file mode 100644 index 000000000000..486ba33d3d4b --- /dev/null +++ b/profiles/default/linux/arm64/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr + +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 diff --git a/profiles/default/linux/arm64/17.0/desktop/deprecated b/profiles/default/linux/arm64/17.0/desktop/deprecated new file mode 100644 index 000000000000..717b8575347c --- /dev/null +++ b/profiles/default/linux/arm64/17.0/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/desktop + +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 diff --git a/profiles/default/linux/arm64/17.0/desktop/gnome/deprecated b/profiles/default/linux/arm64/17.0/desktop/gnome/deprecated new file mode 100644 index 000000000000..a97368ac1d79 --- /dev/null +++ b/profiles/default/linux/arm64/17.0/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/desktop/gnome + +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 diff --git a/profiles/default/linux/arm64/17.0/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/arm64/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..668387f6a691 --- /dev/null +++ b/profiles/default/linux/arm64/17.0/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/desktop/gnome/systemd + +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 diff --git a/profiles/default/linux/arm64/17.0/desktop/plasma/deprecated b/profiles/default/linux/arm64/17.0/desktop/plasma/deprecated new file mode 100644 index 000000000000..ebb83e5535f5 --- /dev/null +++ b/profiles/default/linux/arm64/17.0/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/desktop/plasma + +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 diff --git a/profiles/default/linux/arm64/17.0/desktop/plasma/systemd/merged-usr/deprecated b/profiles/default/linux/arm64/17.0/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..ccd2417ba85c --- /dev/null +++ b/profiles/default/linux/arm64/17.0/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/desktop/plasma/systemd + +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 diff --git a/profiles/default/linux/arm64/17.0/desktop/systemd/merged-usr/deprecated b/profiles/default/linux/arm64/17.0/desktop/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..7b6310b03feb --- /dev/null +++ b/profiles/default/linux/arm64/17.0/desktop/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/desktop/systemd + +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 diff --git a/profiles/default/linux/arm64/17.0/developer/deprecated b/profiles/default/linux/arm64/17.0/developer/deprecated new file mode 100644 index 000000000000..486ba33d3d4b --- /dev/null +++ b/profiles/default/linux/arm64/17.0/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr + +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 diff --git a/profiles/default/linux/arm64/17.0/hardened/deprecated b/profiles/default/linux/arm64/17.0/hardened/deprecated new file mode 100644 index 000000000000..ae8d32507a5a --- /dev/null +++ b/profiles/default/linux/arm64/17.0/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/hardened + +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 diff --git a/profiles/default/linux/arm64/17.0/hardened/selinux/deprecated b/profiles/default/linux/arm64/17.0/hardened/selinux/deprecated new file mode 100644 index 000000000000..04377eb07d4c --- /dev/null +++ b/profiles/default/linux/arm64/17.0/hardened/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/hardened/selinux + +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 diff --git a/profiles/default/linux/arm64/17.0/llvm/deprecated b/profiles/default/linux/arm64/17.0/llvm/deprecated new file mode 100644 index 000000000000..50d9447edffb --- /dev/null +++ b/profiles/default/linux/arm64/17.0/llvm/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/llvm + +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 diff --git a/profiles/default/linux/arm64/17.0/musl/deprecated b/profiles/default/linux/arm64/17.0/musl/deprecated new file mode 100644 index 000000000000..96ea042000bf --- /dev/null +++ b/profiles/default/linux/arm64/17.0/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/musl + +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 diff --git a/profiles/default/linux/arm64/17.0/musl/hardened/deprecated b/profiles/default/linux/arm64/17.0/musl/hardened/deprecated new file mode 100644 index 000000000000..7a1a18659361 --- /dev/null +++ b/profiles/default/linux/arm64/17.0/musl/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/musl/hardened + +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 diff --git a/profiles/default/linux/arm64/17.0/musl/hardened/selinux/deprecated b/profiles/default/linux/arm64/17.0/musl/hardened/selinux/deprecated new file mode 100644 index 000000000000..da1bf7ef3770 --- /dev/null +++ b/profiles/default/linux/arm64/17.0/musl/hardened/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/musl/hardened/selinux + +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 diff --git a/profiles/default/linux/arm64/17.0/musl/llvm/deprecated b/profiles/default/linux/arm64/17.0/musl/llvm/deprecated new file mode 100644 index 000000000000..8e6ae643caf1 --- /dev/null +++ b/profiles/default/linux/arm64/17.0/musl/llvm/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/musl/llvm + +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 diff --git a/profiles/default/linux/arm64/17.0/systemd/llvm/merged-usr/deprecated b/profiles/default/linux/arm64/17.0/systemd/llvm/merged-usr/deprecated new file mode 100644 index 000000000000..a344c6d61e5b --- /dev/null +++ b/profiles/default/linux/arm64/17.0/systemd/llvm/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/llvm/systemd + +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 diff --git a/profiles/default/linux/arm64/17.0/systemd/merged-usr/deprecated b/profiles/default/linux/arm64/17.0/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..d639e20f1867 --- /dev/null +++ b/profiles/default/linux/arm64/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/systemd + +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 diff --git a/profiles/default/linux/arm64/17.0/systemd/selinux/merged-usr/deprecated b/profiles/default/linux/arm64/17.0/systemd/selinux/merged-usr/deprecated new file mode 100644 index 000000000000..826f54d8a36a --- /dev/null +++ b/profiles/default/linux/arm64/17.0/systemd/selinux/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/hardened/selinux/systemd + +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 diff --git a/profiles/default/linux/hppa/17.0/deprecated b/profiles/default/linux/hppa/17.0/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/hppa/17.0/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/hppa/17.0/desktop/deprecated b/profiles/default/linux/hppa/17.0/desktop/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/hppa/17.0/desktop/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/hppa/17.0/developer/deprecated b/profiles/default/linux/hppa/17.0/developer/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/hppa/17.0/developer/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/hppa/17.0/systemd/merged-usr/deprecated b/profiles/default/linux/hppa/17.0/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/hppa/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/ia64/17.0/desktop/gnome/parent b/profiles/default/linux/ia64/17.0/desktop/gnome/parent deleted file mode 100644 index 6589a0e01478..000000000000 --- a/profiles/default/linux/ia64/17.0/desktop/gnome/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../targets/desktop/gnome diff --git a/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr/parent b/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr/parent deleted file mode 100644 index 1b7f7eef0a7e..000000000000 --- a/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../../../features/merged-usr diff --git a/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/parent b/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/parent deleted file mode 100644 index f5c1ae438de4..000000000000 --- a/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../../targets/desktop/gnome/systemd diff --git a/profiles/default/linux/ia64/17.0/desktop/parent b/profiles/default/linux/ia64/17.0/desktop/parent deleted file mode 100644 index ad6c5e126fbb..000000000000 --- a/profiles/default/linux/ia64/17.0/desktop/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../targets/desktop diff --git a/profiles/default/linux/ia64/17.0/developer/parent b/profiles/default/linux/ia64/17.0/developer/parent deleted file mode 100644 index 4c893748ce71..000000000000 --- a/profiles/default/linux/ia64/17.0/developer/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../targets/developer diff --git a/profiles/default/linux/ia64/17.0/parent b/profiles/default/linux/ia64/17.0/parent deleted file mode 100644 index 4ce24f0217a8..000000000000 --- a/profiles/default/linux/ia64/17.0/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../releases/17.0 diff --git a/profiles/default/linux/ia64/17.0/systemd/merged-usr/eapi b/profiles/default/linux/ia64/17.0/systemd/merged-usr/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/ia64/17.0/systemd/merged-usr/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/ia64/17.0/systemd/merged-usr/parent b/profiles/default/linux/ia64/17.0/systemd/merged-usr/parent deleted file mode 100644 index c407ca65bdc2..000000000000 --- a/profiles/default/linux/ia64/17.0/systemd/merged-usr/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../features/merged-usr diff --git a/profiles/default/linux/ia64/17.0/systemd/parent b/profiles/default/linux/ia64/17.0/systemd/parent deleted file mode 100644 index ced72403bde9..000000000000 --- a/profiles/default/linux/ia64/17.0/systemd/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../targets/systemd diff --git a/profiles/default/linux/ia64/23.0/desktop/eapi b/profiles/default/linux/ia64/23.0/desktop/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/ia64/23.0/desktop/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/ia64/23.0/desktop/gnome/eapi b/profiles/default/linux/ia64/23.0/desktop/gnome/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/ia64/23.0/desktop/gnome/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/ia64/23.0/desktop/gnome/parent b/profiles/default/linux/ia64/23.0/desktop/gnome/parent deleted file mode 100644 index 6589a0e01478..000000000000 --- a/profiles/default/linux/ia64/23.0/desktop/gnome/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../targets/desktop/gnome diff --git a/profiles/default/linux/ia64/23.0/desktop/gnome/systemd/eapi b/profiles/default/linux/ia64/23.0/desktop/gnome/systemd/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/ia64/23.0/desktop/gnome/systemd/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/ia64/23.0/desktop/gnome/systemd/parent b/profiles/default/linux/ia64/23.0/desktop/gnome/systemd/parent deleted file mode 100644 index f5c1ae438de4..000000000000 --- a/profiles/default/linux/ia64/23.0/desktop/gnome/systemd/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../../targets/desktop/gnome/systemd diff --git a/profiles/default/linux/ia64/23.0/desktop/parent b/profiles/default/linux/ia64/23.0/desktop/parent deleted file mode 100644 index ad6c5e126fbb..000000000000 --- a/profiles/default/linux/ia64/23.0/desktop/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../targets/desktop diff --git a/profiles/default/linux/ia64/23.0/eapi b/profiles/default/linux/ia64/23.0/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/ia64/23.0/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/ia64/23.0/parent b/profiles/default/linux/ia64/23.0/parent deleted file mode 100644 index 50be433109ef..000000000000 --- a/profiles/default/linux/ia64/23.0/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../releases/23.0 diff --git a/profiles/default/linux/ia64/23.0/split-usr/desktop/eapi b/profiles/default/linux/ia64/23.0/split-usr/desktop/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/ia64/23.0/split-usr/desktop/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/ia64/23.0/split-usr/desktop/gnome/eapi b/profiles/default/linux/ia64/23.0/split-usr/desktop/gnome/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/ia64/23.0/split-usr/desktop/gnome/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/ia64/23.0/split-usr/desktop/gnome/parent b/profiles/default/linux/ia64/23.0/split-usr/desktop/gnome/parent deleted file mode 100644 index 9e06c4505a75..000000000000 --- a/profiles/default/linux/ia64/23.0/split-usr/desktop/gnome/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../../targets/desktop/gnome diff --git a/profiles/default/linux/ia64/23.0/split-usr/desktop/parent b/profiles/default/linux/ia64/23.0/split-usr/desktop/parent deleted file mode 100644 index db8ce088c69a..000000000000 --- a/profiles/default/linux/ia64/23.0/split-usr/desktop/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../targets/desktop diff --git a/profiles/default/linux/ia64/23.0/split-usr/eapi b/profiles/default/linux/ia64/23.0/split-usr/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/ia64/23.0/split-usr/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/ia64/23.0/split-usr/parent b/profiles/default/linux/ia64/23.0/split-usr/parent deleted file mode 100644 index 598ca888c8c2..000000000000 --- a/profiles/default/linux/ia64/23.0/split-usr/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../features/split-usr diff --git a/profiles/default/linux/ia64/23.0/systemd/eapi b/profiles/default/linux/ia64/23.0/systemd/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/ia64/23.0/systemd/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/ia64/23.0/systemd/parent b/profiles/default/linux/ia64/23.0/systemd/parent deleted file mode 100644 index ced72403bde9..000000000000 --- a/profiles/default/linux/ia64/23.0/systemd/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../targets/systemd diff --git a/profiles/default/linux/ia64/eapi b/profiles/default/linux/ia64/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/ia64/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/ia64/parent b/profiles/default/linux/ia64/parent deleted file mode 100644 index 10d6c4b38690..000000000000 --- a/profiles/default/linux/ia64/parent +++ /dev/null @@ -1,3 +0,0 @@ -../../../base -.. -../../../arch/ia64 diff --git a/profiles/default/linux/loong/22.0/la64v100/lp64d/deprecated b/profiles/default/linux/loong/22.0/la64v100/lp64d/deprecated new file mode 100644 index 000000000000..e014056c3146 --- /dev/null +++ b/profiles/default/linux/loong/22.0/la64v100/lp64d/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/split-usr/lp64d + +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 diff --git a/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/deprecated b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/deprecated new file mode 100644 index 000000000000..7dad124056fc --- /dev/null +++ b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/split-usr/lp64d/desktop + +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 diff --git a/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/deprecated b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/deprecated new file mode 100644 index 000000000000..4f70ec5b094c --- /dev/null +++ b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/split-usr/lp64d/desktop/gnome + +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 diff --git a/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..2739d57076a1 --- /dev/null +++ b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/lp64d/desktop/gnome/systemd + +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 diff --git a/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/deprecated b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/deprecated new file mode 100644 index 000000000000..fba6aacd507d --- /dev/null +++ b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/split-usr/lp64d/desktop/plasma + +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 diff --git a/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/systemd/merged-usr/deprecated b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..dd2de41c7c1b --- /dev/null +++ b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/lp64d/desktop/plasma/systemd + +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 diff --git a/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/systemd/merged-usr/deprecated b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..a6a9180fadca --- /dev/null +++ b/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/lp64d/desktop/systemd + +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 diff --git a/profiles/default/linux/loong/22.0/la64v100/lp64d/developer/deprecated b/profiles/default/linux/loong/22.0/la64v100/lp64d/developer/deprecated new file mode 100644 index 000000000000..e014056c3146 --- /dev/null +++ b/profiles/default/linux/loong/22.0/la64v100/lp64d/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/split-usr/lp64d + +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 diff --git a/profiles/default/linux/loong/22.0/la64v100/lp64d/systemd/merged-usr/deprecated b/profiles/default/linux/loong/22.0/la64v100/lp64d/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..3967f72298be --- /dev/null +++ b/profiles/default/linux/loong/22.0/la64v100/lp64d/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/lp64d/systemd + +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 diff --git a/profiles/default/linux/m68k/17.0/deprecated b/profiles/default/linux/m68k/17.0/deprecated new file mode 100644 index 000000000000..5b3bb8039bb2 --- /dev/null +++ b/profiles/default/linux/m68k/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/m68k/23.0/split-usr + +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 diff --git a/profiles/default/linux/m68k/17.0/musl/deprecated b/profiles/default/linux/m68k/17.0/musl/deprecated new file mode 100644 index 000000000000..d9c8615f02bd --- /dev/null +++ b/profiles/default/linux/m68k/17.0/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/m68k/23.0/split-usr/musl + +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 diff --git a/profiles/default/linux/m68k/17.0/musl/parent b/profiles/default/linux/m68k/17.0/musl/parent index 58651906cb67..9ef7663a23b6 100644 --- a/profiles/default/linux/m68k/17.0/musl/parent +++ b/profiles/default/linux/m68k/17.0/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../features/musl +../../../../../features/wd40 diff --git a/profiles/default/linux/m68k/17.0/systemd/merged-usr/deprecated b/profiles/default/linux/m68k/17.0/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..d5519859465c --- /dev/null +++ b/profiles/default/linux/m68k/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/m68k/23.0/systemd + +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 diff --git a/profiles/default/linux/m68k/23.0/musl/parent b/profiles/default/linux/m68k/23.0/musl/parent index 58651906cb67..9ef7663a23b6 100644 --- a/profiles/default/linux/m68k/23.0/musl/parent +++ b/profiles/default/linux/m68k/23.0/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../features/musl +../../../../../features/wd40 diff --git a/profiles/default/linux/m68k/23.0/split-usr/musl/parent b/profiles/default/linux/m68k/23.0/split-usr/musl/parent index 5bbe8700f1a6..bd0ef6ecac62 100644 --- a/profiles/default/linux/m68k/23.0/split-usr/musl/parent +++ b/profiles/default/linux/m68k/23.0/split-usr/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../../features/musl +../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/17.0/mipsel/multilib/n32/deprecated b/profiles/default/linux/mips/17.0/mipsel/multilib/n32/deprecated new file mode 100644 index 000000000000..a88072d79600 --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/multilib/n32/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/split-usr/mipsel/multilib/n32 + +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 diff --git a/profiles/default/linux/mips/17.0/mipsel/multilib/n32/systemd/merged-usr/deprecated b/profiles/default/linux/mips/17.0/mipsel/multilib/n32/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..91dd79c36c49 --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/multilib/n32/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/mipsel/multilib/n32/systemd + +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 diff --git a/profiles/default/linux/mips/17.0/mipsel/multilib/n64/deprecated b/profiles/default/linux/mips/17.0/mipsel/multilib/n64/deprecated new file mode 100644 index 000000000000..d30a7d94ed9e --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/multilib/n64/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/split-usr/mipsel/multilib/n64 + +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 diff --git a/profiles/default/linux/mips/17.0/mipsel/multilib/n64/systemd/merged-usr/deprecated b/profiles/default/linux/mips/17.0/mipsel/multilib/n64/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..546f2481518e --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/multilib/n64/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/mipsel/multilib/n64/systemd + +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 diff --git a/profiles/default/linux/mips/17.0/mipsel/multilib/o32/deprecated b/profiles/default/linux/mips/17.0/mipsel/multilib/o32/deprecated new file mode 100644 index 000000000000..0b4da443b64e --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/multilib/o32/deprecated @@ -0,0 +1 @@ +default/linux/mips/17.0/mipsel/o32 diff --git a/profiles/default/linux/mips/17.0/mipsel/n32/deprecated b/profiles/default/linux/mips/17.0/mipsel/n32/deprecated new file mode 100644 index 000000000000..e8ef1fd920dd --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/n32/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/split-usr/mipsel/n32 + +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 diff --git a/profiles/default/linux/mips/17.0/mipsel/n32/systemd/merged-usr/deprecated b/profiles/default/linux/mips/17.0/mipsel/n32/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..d98cd50d4944 --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/n32/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/mipsel/n32/systemd + +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 diff --git a/profiles/default/linux/mips/17.0/mipsel/n64/deprecated b/profiles/default/linux/mips/17.0/mipsel/n64/deprecated new file mode 100644 index 000000000000..d27ee875a2ba --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/n64/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/split-usr/mipsel/n64 + +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 diff --git a/profiles/default/linux/mips/17.0/mipsel/n64/musl/deprecated b/profiles/default/linux/mips/17.0/mipsel/n64/musl/deprecated new file mode 100644 index 000000000000..085b11b8d942 --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/n64/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/split-usr/mipsel/n64/musl + +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 diff --git a/profiles/default/linux/mips/17.0/mipsel/n64/musl/parent b/profiles/default/linux/mips/17.0/mipsel/n64/musl/parent index a3de2bcf95f7..7b9610fe3971 100644 --- a/profiles/default/linux/mips/17.0/mipsel/n64/musl/parent +++ b/profiles/default/linux/mips/17.0/mipsel/n64/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../../features/musl ../../../../../../../features/wd40 +../../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/17.0/mipsel/n64/systemd/merged-usr/deprecated b/profiles/default/linux/mips/17.0/mipsel/n64/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..0f1d3637239e --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/n64/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/mipsel/n64/systemd + +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 diff --git a/profiles/default/linux/mips/17.0/mipsel/o32/deprecated b/profiles/default/linux/mips/17.0/mipsel/o32/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/o32/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/mips/17.0/mipsel/o32/musl/deprecated b/profiles/default/linux/mips/17.0/mipsel/o32/musl/deprecated new file mode 100644 index 000000000000..970442e531a0 --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/o32/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/split-usr/mipsel/o32/musl + +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 diff --git a/profiles/default/linux/mips/17.0/mipsel/o32/musl/parent b/profiles/default/linux/mips/17.0/mipsel/o32/musl/parent index a3de2bcf95f7..7b9610fe3971 100644 --- a/profiles/default/linux/mips/17.0/mipsel/o32/musl/parent +++ b/profiles/default/linux/mips/17.0/mipsel/o32/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../../features/musl ../../../../../../../features/wd40 +../../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/17.0/mipsel/o32/systemd/merged-usr/deprecated b/profiles/default/linux/mips/17.0/mipsel/o32/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/mips/17.0/mipsel/o32/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/mips/17.0/multilib/n32/deprecated b/profiles/default/linux/mips/17.0/multilib/n32/deprecated new file mode 100644 index 000000000000..a4a9ed800704 --- /dev/null +++ b/profiles/default/linux/mips/17.0/multilib/n32/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/split-usr/multilib/n32 + +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 diff --git a/profiles/default/linux/mips/17.0/multilib/n32/systemd/merged-usr/deprecated b/profiles/default/linux/mips/17.0/multilib/n32/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..372276d3f1aa --- /dev/null +++ b/profiles/default/linux/mips/17.0/multilib/n32/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/multilib/n32/systemd + +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 diff --git a/profiles/default/linux/mips/17.0/multilib/n64/deprecated b/profiles/default/linux/mips/17.0/multilib/n64/deprecated new file mode 100644 index 000000000000..a086d5b8f3f3 --- /dev/null +++ b/profiles/default/linux/mips/17.0/multilib/n64/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/split-usr/multilib/n64 + +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 diff --git a/profiles/default/linux/mips/17.0/multilib/o32/deprecated b/profiles/default/linux/mips/17.0/multilib/o32/deprecated new file mode 100644 index 000000000000..98ce3606a057 --- /dev/null +++ b/profiles/default/linux/mips/17.0/multilib/o32/deprecated @@ -0,0 +1 @@ +default/linux/mips/17.0/o32 diff --git a/profiles/default/linux/mips/17.0/n32/deprecated b/profiles/default/linux/mips/17.0/n32/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/mips/17.0/n32/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/mips/17.0/n32/systemd/merged-usr/deprecated b/profiles/default/linux/mips/17.0/n32/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/mips/17.0/n32/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/mips/17.0/n64/deprecated b/profiles/default/linux/mips/17.0/n64/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/mips/17.0/n64/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/mips/17.0/n64/musl/deprecated b/profiles/default/linux/mips/17.0/n64/musl/deprecated new file mode 100644 index 000000000000..4f0f9630cede --- /dev/null +++ b/profiles/default/linux/mips/17.0/n64/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/split-usr/n64/musl + +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 diff --git a/profiles/default/linux/mips/17.0/n64/musl/parent b/profiles/default/linux/mips/17.0/n64/musl/parent index bd0ef6ecac62..25049c8047e4 100644 --- a/profiles/default/linux/mips/17.0/n64/musl/parent +++ b/profiles/default/linux/mips/17.0/n64/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../features/musl ../../../../../../features/wd40 +../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/17.0/n64/systemd/merged-usr/deprecated b/profiles/default/linux/mips/17.0/n64/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/mips/17.0/n64/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/mips/17.0/o32/deprecated b/profiles/default/linux/mips/17.0/o32/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/mips/17.0/o32/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/mips/17.0/o32/musl/deprecated b/profiles/default/linux/mips/17.0/o32/musl/deprecated new file mode 100644 index 000000000000..0eadddb9a36b --- /dev/null +++ b/profiles/default/linux/mips/17.0/o32/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/mips/23.0/split-usr/o32/musl + +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 diff --git a/profiles/default/linux/mips/17.0/o32/musl/parent b/profiles/default/linux/mips/17.0/o32/musl/parent index bd0ef6ecac62..25049c8047e4 100644 --- a/profiles/default/linux/mips/17.0/o32/musl/parent +++ b/profiles/default/linux/mips/17.0/o32/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../features/musl ../../../../../../features/wd40 +../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/17.0/o32/systemd/merged-usr/deprecated b/profiles/default/linux/mips/17.0/o32/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/mips/17.0/o32/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/mips/23.0/mipsel/n64/musl/parent b/profiles/default/linux/mips/23.0/mipsel/n64/musl/parent index a3de2bcf95f7..7b9610fe3971 100644 --- a/profiles/default/linux/mips/23.0/mipsel/n64/musl/parent +++ b/profiles/default/linux/mips/23.0/mipsel/n64/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../../features/musl ../../../../../../../features/wd40 +../../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/23.0/mipsel/o32/musl/parent b/profiles/default/linux/mips/23.0/mipsel/o32/musl/parent index a3de2bcf95f7..7b9610fe3971 100644 --- a/profiles/default/linux/mips/23.0/mipsel/o32/musl/parent +++ b/profiles/default/linux/mips/23.0/mipsel/o32/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../../features/musl ../../../../../../../features/wd40 +../../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/23.0/mipsel/o32_sf/musl/parent b/profiles/default/linux/mips/23.0/mipsel/o32_sf/musl/parent index a3de2bcf95f7..7b9610fe3971 100644 --- a/profiles/default/linux/mips/23.0/mipsel/o32_sf/musl/parent +++ b/profiles/default/linux/mips/23.0/mipsel/o32_sf/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../../features/musl ../../../../../../../features/wd40 +../../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/23.0/n64/musl/parent b/profiles/default/linux/mips/23.0/n64/musl/parent index bd0ef6ecac62..25049c8047e4 100644 --- a/profiles/default/linux/mips/23.0/n64/musl/parent +++ b/profiles/default/linux/mips/23.0/n64/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../features/musl ../../../../../../features/wd40 +../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/23.0/o32/musl/parent b/profiles/default/linux/mips/23.0/o32/musl/parent index bd0ef6ecac62..25049c8047e4 100644 --- a/profiles/default/linux/mips/23.0/o32/musl/parent +++ b/profiles/default/linux/mips/23.0/o32/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../features/musl ../../../../../../features/wd40 +../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/23.0/o32_sf/musl/parent b/profiles/default/linux/mips/23.0/o32_sf/musl/parent index bd0ef6ecac62..25049c8047e4 100644 --- a/profiles/default/linux/mips/23.0/o32_sf/musl/parent +++ b/profiles/default/linux/mips/23.0/o32_sf/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../features/musl ../../../../../../features/wd40 +../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/23.0/split-usr/mipsel/n64/musl/parent b/profiles/default/linux/mips/23.0/split-usr/mipsel/n64/musl/parent index 43b77c652c58..83d58b1b76c5 100644 --- a/profiles/default/linux/mips/23.0/split-usr/mipsel/n64/musl/parent +++ b/profiles/default/linux/mips/23.0/split-usr/mipsel/n64/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../../../features/musl ../../../../../../../../features/wd40 +../../../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/23.0/split-usr/mipsel/o32/musl/parent b/profiles/default/linux/mips/23.0/split-usr/mipsel/o32/musl/parent index 43b77c652c58..83d58b1b76c5 100644 --- a/profiles/default/linux/mips/23.0/split-usr/mipsel/o32/musl/parent +++ b/profiles/default/linux/mips/23.0/split-usr/mipsel/o32/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../../../features/musl ../../../../../../../../features/wd40 +../../../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/23.0/split-usr/mipsel/o32_sf/musl/parent b/profiles/default/linux/mips/23.0/split-usr/mipsel/o32_sf/musl/parent index 43b77c652c58..83d58b1b76c5 100644 --- a/profiles/default/linux/mips/23.0/split-usr/mipsel/o32_sf/musl/parent +++ b/profiles/default/linux/mips/23.0/split-usr/mipsel/o32_sf/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../../../features/musl ../../../../../../../../features/wd40 +../../../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/23.0/split-usr/n64/musl/parent b/profiles/default/linux/mips/23.0/split-usr/n64/musl/parent index a3de2bcf95f7..7b9610fe3971 100644 --- a/profiles/default/linux/mips/23.0/split-usr/n64/musl/parent +++ b/profiles/default/linux/mips/23.0/split-usr/n64/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../../features/musl ../../../../../../../features/wd40 +../../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/23.0/split-usr/o32/musl/parent b/profiles/default/linux/mips/23.0/split-usr/o32/musl/parent index a3de2bcf95f7..7b9610fe3971 100644 --- a/profiles/default/linux/mips/23.0/split-usr/o32/musl/parent +++ b/profiles/default/linux/mips/23.0/split-usr/o32/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../../features/musl ../../../../../../../features/wd40 +../../../../../../../features/wd40 diff --git a/profiles/default/linux/mips/23.0/split-usr/o32_sf/musl/parent b/profiles/default/linux/mips/23.0/split-usr/o32_sf/musl/parent index a3de2bcf95f7..7b9610fe3971 100644 --- a/profiles/default/linux/mips/23.0/split-usr/o32_sf/musl/parent +++ b/profiles/default/linux/mips/23.0/split-usr/o32_sf/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../../features/musl ../../../../../../../features/wd40 +../../../../../../../features/wd40 diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/parent deleted file mode 100644 index d5a56a13f692..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../../../targets/desktop/gnome diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/parent deleted file mode 100644 index 05b6f4918b26..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../../../../../features/merged-usr diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/parent deleted file mode 100644 index 288aeccdce82..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../../../../targets/desktop/gnome/systemd diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/parent deleted file mode 100644 index fae96e8d36b2..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../../targets/desktop diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/parent deleted file mode 100644 index 4bb06e409236..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../../targets/developer diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/eapi deleted file mode 100644 index 7ed6ff82de6b..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/eapi +++ /dev/null @@ -1 +0,0 @@ -5 diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/parent deleted file mode 100644 index 898d55cbcebd..000000000000 --- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/parent +++ /dev/null @@ -1,2 +0,0 @@ -.. -../../../../../../arch/powerpc/ppc64/32ul diff --git a/profiles/default/linux/ppc/17.0/deprecated b/profiles/default/linux/ppc/17.0/deprecated new file mode 100644 index 000000000000..4b91a95b3766 --- /dev/null +++ b/profiles/default/linux/ppc/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc/23.0/split-usr + +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 diff --git a/profiles/default/linux/ppc/17.0/desktop/deprecated b/profiles/default/linux/ppc/17.0/desktop/deprecated new file mode 100644 index 000000000000..0159d2926b31 --- /dev/null +++ b/profiles/default/linux/ppc/17.0/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc/23.0/split-usr/desktop + +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 diff --git a/profiles/default/linux/ppc/17.0/desktop/gnome/deprecated b/profiles/default/linux/ppc/17.0/desktop/gnome/deprecated new file mode 100644 index 000000000000..0c3059bbec6b --- /dev/null +++ b/profiles/default/linux/ppc/17.0/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc/23.0/split-usr/desktop/gnome + +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 diff --git a/profiles/default/linux/ppc/17.0/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/ppc/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..4c39f7d0e8e4 --- /dev/null +++ b/profiles/default/linux/ppc/17.0/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc/23.0/desktop/gnome/systemd + +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 diff --git a/profiles/default/linux/ppc/17.0/developer/deprecated b/profiles/default/linux/ppc/17.0/developer/deprecated new file mode 100644 index 000000000000..4b91a95b3766 --- /dev/null +++ b/profiles/default/linux/ppc/17.0/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc/23.0/split-usr + +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 diff --git a/profiles/default/linux/ppc/17.0/musl/deprecated b/profiles/default/linux/ppc/17.0/musl/deprecated new file mode 100644 index 000000000000..e719c6300283 --- /dev/null +++ b/profiles/default/linux/ppc/17.0/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc/23.0/split-usr/musl + +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 diff --git a/profiles/default/linux/ppc/17.0/musl/hardened/deprecated b/profiles/default/linux/ppc/17.0/musl/hardened/deprecated new file mode 100644 index 000000000000..4f477a5098aa --- /dev/null +++ b/profiles/default/linux/ppc/17.0/musl/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc/23.0/split-usr/musl/hardened + +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 diff --git a/profiles/default/linux/ppc/17.0/musl/parent b/profiles/default/linux/ppc/17.0/musl/parent index 9ef7663a23b6..65eaf9bd2624 100644 --- a/profiles/default/linux/ppc/17.0/musl/parent +++ b/profiles/default/linux/ppc/17.0/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../features/musl ../../../../../features/wd40 +../../../../../features/wd40 diff --git a/profiles/default/linux/ppc/17.0/systemd/merged-usr/deprecated b/profiles/default/linux/ppc/17.0/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..030e189b867f --- /dev/null +++ b/profiles/default/linux/ppc/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc/23.0/systemd + +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 diff --git a/profiles/default/linux/ppc/23.0/musl/package.use.mask b/profiles/default/linux/ppc/23.0/musl/package.use.mask index 80fbaf3654a7..c7d54156ade0 100644 --- a/profiles/default/linux/ppc/23.0/musl/package.use.mask +++ b/profiles/default/linux/ppc/23.0/musl/package.use.mask @@ -1,6 +1,11 @@ -# Copyright 2023 Gentoo Authors +# Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James <sam@gentoo.org> (2024-06-16) +# Avoid pulling in sys-libs/compiler-rt-sanitizers which fails to build +# See bug #928936. +sys-devel/clang-runtime sanitize + # Sam James <sam@gentoo.org> (2023-01-29) # Fails to build on combination of ppc* + musl because of mcontext. # libsanitizer needs adapting, bug #892079. diff --git a/profiles/default/linux/ppc/23.0/musl/parent b/profiles/default/linux/ppc/23.0/musl/parent index 9ef7663a23b6..65eaf9bd2624 100644 --- a/profiles/default/linux/ppc/23.0/musl/parent +++ b/profiles/default/linux/ppc/23.0/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../features/musl ../../../../../features/wd40 +../../../../../features/wd40 diff --git a/profiles/default/linux/ppc/23.0/split-usr/musl/parent b/profiles/default/linux/ppc/23.0/split-usr/musl/parent index bd0ef6ecac62..25049c8047e4 100644 --- a/profiles/default/linux/ppc/23.0/split-usr/musl/parent +++ b/profiles/default/linux/ppc/23.0/split-usr/musl/parent @@ -1,3 +1,4 @@ .. ../../../../../../features/musl ../../../../../../features/wd40 +../../../../../../features/wd40 diff --git a/profiles/default/linux/ppc/package.use.mask b/profiles/default/linux/ppc/package.use.mask index 631cbe4ff0cb..eff2ddb9a45c 100644 --- a/profiles/default/linux/ppc/package.use.mask +++ b/profiles/default/linux/ppc/package.use.mask @@ -1,6 +1,10 @@ -# Copyright 1999-2020 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Mattéo Rossillol‑‑Laruelle <beatussum@protonmail.com> (2024-08-06) +# Requires sys-libs/libcxx. +dev-cpp/benchmark libcxx + # Mike Frysinger <vapier@gentoo.org> (2014-10-21) # This target supports ASAN/etc... #504200. sys-devel/gcc -sanitize diff --git a/profiles/default/linux/ppc64/17.0/deprecated b/profiles/default/linux/ppc64/17.0/deprecated new file mode 100644 index 000000000000..d41b17886ec4 --- /dev/null +++ b/profiles/default/linux/ppc64/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64/23.0/split-usr + +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 diff --git a/profiles/default/linux/ppc64/17.0/desktop/deprecated b/profiles/default/linux/ppc64/17.0/desktop/deprecated new file mode 100644 index 000000000000..d76d864e182e --- /dev/null +++ b/profiles/default/linux/ppc64/17.0/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64/23.0/split-usr/desktop + +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 diff --git a/profiles/default/linux/ppc64/17.0/desktop/gnome/deprecated b/profiles/default/linux/ppc64/17.0/desktop/gnome/deprecated new file mode 100644 index 000000000000..5140905bc84b --- /dev/null +++ b/profiles/default/linux/ppc64/17.0/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64/23.0/split-usr/desktop/gnome + +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 diff --git a/profiles/default/linux/ppc64/17.0/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/ppc64/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..8dd6e72c370d --- /dev/null +++ b/profiles/default/linux/ppc64/17.0/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64/23.0/desktop/gnome/systemd + +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 diff --git a/profiles/default/linux/ppc64/17.0/developer/deprecated b/profiles/default/linux/ppc64/17.0/developer/deprecated new file mode 100644 index 000000000000..d41b17886ec4 --- /dev/null +++ b/profiles/default/linux/ppc64/17.0/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64/23.0/split-usr + +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 diff --git a/profiles/default/linux/ppc64/17.0/musl/deprecated b/profiles/default/linux/ppc64/17.0/musl/deprecated new file mode 100644 index 000000000000..7b217795bc28 --- /dev/null +++ b/profiles/default/linux/ppc64/17.0/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64/23.0/split-usr/musl + +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 diff --git a/profiles/default/linux/ppc64/17.0/musl/hardened/deprecated b/profiles/default/linux/ppc64/17.0/musl/hardened/deprecated new file mode 100644 index 000000000000..254125d4eb92 --- /dev/null +++ b/profiles/default/linux/ppc64/17.0/musl/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64/23.0/split-usr/musl/hardened + +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 diff --git a/profiles/default/linux/ppc64/17.0/musl/parent b/profiles/default/linux/ppc64/17.0/musl/parent index 58651906cb67..9ef7663a23b6 100644 --- a/profiles/default/linux/ppc64/17.0/musl/parent +++ b/profiles/default/linux/ppc64/17.0/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../features/musl +../../../../../features/wd40 diff --git a/profiles/default/linux/ppc64/17.0/package.mask b/profiles/default/linux/ppc64/17.0/package.mask new file mode 100644 index 000000000000..f59665ea744c --- /dev/null +++ b/profiles/default/linux/ppc64/17.0/package.mask @@ -0,0 +1,7 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# matoro <matoro_gentoo@matoro.tk> +# Requires USE=ieee-long-double, so mask on 17.0, #892183 +dev-python/sympy +dev-python/symengine diff --git a/profiles/default/linux/ppc64/17.0/systemd/merged-usr/deprecated b/profiles/default/linux/ppc64/17.0/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..dfa8e211fd84 --- /dev/null +++ b/profiles/default/linux/ppc64/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64/23.0/systemd + +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 diff --git a/profiles/default/linux/ppc64/23.0/musl/package.mask b/profiles/default/linux/ppc64/23.0/musl/package.mask new file mode 100644 index 000000000000..ab6e39a666f1 --- /dev/null +++ b/profiles/default/linux/ppc64/23.0/musl/package.mask @@ -0,0 +1,7 @@ +# Copyright 2024 Gentoo Authors. +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-15) +# rust-bin is available on ppc64 musl starting from 1.80.1 +-dev-lang/rust-bin +<dev-lang/rust-bin-1.80.1 diff --git a/profiles/default/linux/ppc64/23.0/musl/package.use.force b/profiles/default/linux/ppc64/23.0/musl/package.use.force new file mode 100644 index 000000000000..fd3ef27d892d --- /dev/null +++ b/profiles/default/linux/ppc64/23.0/musl/package.use.force @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-16) +# We build our riscv musl binaries ourselves, #936643 +dev-lang/rust system-bootstrap diff --git a/profiles/default/linux/ppc64/23.0/split-usr/musl/package.mask b/profiles/default/linux/ppc64/23.0/split-usr/musl/package.mask new file mode 100644 index 000000000000..ab6e39a666f1 --- /dev/null +++ b/profiles/default/linux/ppc64/23.0/split-usr/musl/package.mask @@ -0,0 +1,7 @@ +# Copyright 2024 Gentoo Authors. +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-15) +# rust-bin is available on ppc64 musl starting from 1.80.1 +-dev-lang/rust-bin +<dev-lang/rust-bin-1.80.1 diff --git a/profiles/default/linux/ppc64/23.0/split-usr/musl/package.use.force b/profiles/default/linux/ppc64/23.0/split-usr/musl/package.use.force new file mode 100644 index 000000000000..fd3ef27d892d --- /dev/null +++ b/profiles/default/linux/ppc64/23.0/split-usr/musl/package.use.force @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-16) +# We build our riscv musl binaries ourselves, #936643 +dev-lang/rust system-bootstrap diff --git a/profiles/default/linux/ppc64/package.use.mask b/profiles/default/linux/ppc64/package.use.mask index 631cbe4ff0cb..eff2ddb9a45c 100644 --- a/profiles/default/linux/ppc64/package.use.mask +++ b/profiles/default/linux/ppc64/package.use.mask @@ -1,6 +1,10 @@ -# Copyright 1999-2020 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Mattéo Rossillol‑‑Laruelle <beatussum@protonmail.com> (2024-08-06) +# Requires sys-libs/libcxx. +dev-cpp/benchmark libcxx + # Mike Frysinger <vapier@gentoo.org> (2014-10-21) # This target supports ASAN/etc... #504200. sys-devel/gcc -sanitize diff --git a/profiles/default/linux/ppc64le/17.0/deprecated b/profiles/default/linux/ppc64le/17.0/deprecated new file mode 100644 index 000000000000..ee7320f6f7c6 --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/split-usr + +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 diff --git a/profiles/default/linux/ppc64le/17.0/desktop/deprecated b/profiles/default/linux/ppc64le/17.0/desktop/deprecated new file mode 100644 index 000000000000..a4ec403f1ad0 --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/split-usr/desktop + +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 diff --git a/profiles/default/linux/ppc64le/17.0/desktop/gnome/deprecated b/profiles/default/linux/ppc64le/17.0/desktop/gnome/deprecated new file mode 100644 index 000000000000..32232b7ffd72 --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/split-usr/desktop/gnome + +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 diff --git a/profiles/default/linux/ppc64le/17.0/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/ppc64le/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..1b0374bba685 --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/desktop/gnome/systemd + +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 diff --git a/profiles/default/linux/ppc64le/17.0/desktop/plasma/deprecated b/profiles/default/linux/ppc64le/17.0/desktop/plasma/deprecated new file mode 100644 index 000000000000..7d25eb99fd37 --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/split-usr/desktop/plasma + +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 diff --git a/profiles/default/linux/ppc64le/17.0/desktop/plasma/systemd/merged-usr/deprecated b/profiles/default/linux/ppc64le/17.0/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..225eb9579cba --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/desktop/plasma/systemd + +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 diff --git a/profiles/default/linux/ppc64le/17.0/desktop/systemd/merged-usr/deprecated b/profiles/default/linux/ppc64le/17.0/desktop/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..31f5006e0ca7 --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/desktop/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/desktop/systemd + +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 diff --git a/profiles/default/linux/ppc64le/17.0/developer/deprecated b/profiles/default/linux/ppc64le/17.0/developer/deprecated new file mode 100644 index 000000000000..ee7320f6f7c6 --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/split-usr + +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 diff --git a/profiles/default/linux/ppc64le/17.0/ieee-long-double/deprecated b/profiles/default/linux/ppc64le/17.0/ieee-long-double/deprecated new file mode 100644 index 000000000000..ee7320f6f7c6 --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/ieee-long-double/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/split-usr + +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 diff --git a/profiles/default/linux/ppc64le/17.0/musl/deprecated b/profiles/default/linux/ppc64le/17.0/musl/deprecated new file mode 100644 index 000000000000..f439ee75b0df --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/split-usr/musl + +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 diff --git a/profiles/default/linux/ppc64le/17.0/musl/hardened/deprecated b/profiles/default/linux/ppc64le/17.0/musl/hardened/deprecated new file mode 100644 index 000000000000..41718e4bc2b7 --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/musl/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/split-usr/musl/hardened + +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 diff --git a/profiles/default/linux/ppc64le/17.0/musl/parent b/profiles/default/linux/ppc64le/17.0/musl/parent index 58651906cb67..9ef7663a23b6 100644 --- a/profiles/default/linux/ppc64le/17.0/musl/parent +++ b/profiles/default/linux/ppc64le/17.0/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../features/musl +../../../../../features/wd40 diff --git a/profiles/default/linux/ppc64le/17.0/systemd/merged-usr/deprecated b/profiles/default/linux/ppc64le/17.0/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..e4eebc79b279 --- /dev/null +++ b/profiles/default/linux/ppc64le/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc64le/23.0/systemd + +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 diff --git a/profiles/default/linux/ppc64le/23.0/musl/package.mask b/profiles/default/linux/ppc64le/23.0/musl/package.mask new file mode 100644 index 000000000000..ab6e39a666f1 --- /dev/null +++ b/profiles/default/linux/ppc64le/23.0/musl/package.mask @@ -0,0 +1,7 @@ +# Copyright 2024 Gentoo Authors. +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-15) +# rust-bin is available on ppc64 musl starting from 1.80.1 +-dev-lang/rust-bin +<dev-lang/rust-bin-1.80.1 diff --git a/profiles/default/linux/ppc64le/23.0/musl/package.use.force b/profiles/default/linux/ppc64le/23.0/musl/package.use.force new file mode 100644 index 000000000000..fd3ef27d892d --- /dev/null +++ b/profiles/default/linux/ppc64le/23.0/musl/package.use.force @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-16) +# We build our riscv musl binaries ourselves, #936643 +dev-lang/rust system-bootstrap diff --git a/profiles/default/linux/ppc64le/23.0/split-usr/musl/package.mask b/profiles/default/linux/ppc64le/23.0/split-usr/musl/package.mask new file mode 100644 index 000000000000..ab6e39a666f1 --- /dev/null +++ b/profiles/default/linux/ppc64le/23.0/split-usr/musl/package.mask @@ -0,0 +1,7 @@ +# Copyright 2024 Gentoo Authors. +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-15) +# rust-bin is available on ppc64 musl starting from 1.80.1 +-dev-lang/rust-bin +<dev-lang/rust-bin-1.80.1 diff --git a/profiles/default/linux/ppc64le/23.0/split-usr/musl/package.use.force b/profiles/default/linux/ppc64le/23.0/split-usr/musl/package.use.force new file mode 100644 index 000000000000..fd3ef27d892d --- /dev/null +++ b/profiles/default/linux/ppc64le/23.0/split-usr/musl/package.use.force @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-08-16) +# We build our riscv musl binaries ourselves, #936643 +dev-lang/rust system-bootstrap diff --git a/profiles/default/linux/ppc64le/package.use.mask b/profiles/default/linux/ppc64le/package.use.mask index 631cbe4ff0cb..eff2ddb9a45c 100644 --- a/profiles/default/linux/ppc64le/package.use.mask +++ b/profiles/default/linux/ppc64le/package.use.mask @@ -1,6 +1,10 @@ -# Copyright 1999-2020 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Mattéo Rossillol‑‑Laruelle <beatussum@protonmail.com> (2024-08-06) +# Requires sys-libs/libcxx. +dev-cpp/benchmark libcxx + # Mike Frysinger <vapier@gentoo.org> (2014-10-21) # This target supports ASAN/etc... #504200. sys-devel/gcc -sanitize diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64/deprecated new file mode 100644 index 000000000000..e49def3f4967 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/split-usr/lp64 + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/deprecated new file mode 100644 index 000000000000..6c2be8c5f679 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/split-usr/lp64/desktop + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/deprecated new file mode 100644 index 000000000000..fb525dece1c2 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/split-usr/lp64/desktop/gnome + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..b9f28caee6ad --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/lp64/desktop/gnome/systemd + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/deprecated new file mode 100644 index 000000000000..8d8c0756f87d --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/split-usr/lp64/desktop/plasma + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/systemd/merged-usr/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..beb2580f569e --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/lp64/desktop/plasma/systemd + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/systemd/merged-usr/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..338c8842c0f0 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/lp64/desktop/systemd + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64/musl/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64/musl/deprecated new file mode 100644 index 000000000000..892b778d212c --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/split-usr/lp64/musl + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64/musl/package.use.force b/profiles/default/linux/riscv/20.0/rv64gc/lp64/musl/package.use.force new file mode 100644 index 000000000000..1205c8086524 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64/musl/package.use.force @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# matoro <matoro_gentoo@matoro.tk> +# We build our riscv musl binaries ourselves, #936643 +dev-lang/rust system-bootstrap diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64/systemd/merged-usr/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..b7fc6f92311e --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/lp64/systemd + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64d/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/deprecated new file mode 100644 index 000000000000..540d5a7a8b20 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/split-usr/lp64d + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/deprecated new file mode 100644 index 000000000000..5e2131dd0c9b --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/split-usr/lp64d/desktop + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/deprecated new file mode 100644 index 000000000000..2364215f9525 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/split-usr/lp64d/desktop/gnome + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..bb4966dda923 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/lp64d/desktop/gnome/systemd + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/deprecated new file mode 100644 index 000000000000..41bf9a8a889c --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/split-usr/lp64d/desktop/plasma + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/systemd/merged-usr/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..a6e661c9749b --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/lp64d/desktop/plasma/systemd + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/systemd/merged-usr/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..b551ec79fb17 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/lp64d/desktop/systemd + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64d/musl/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/musl/deprecated new file mode 100644 index 000000000000..d7c4a35e16c3 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/musl/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/split-usr/lp64d/musl + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64d/musl/package.use.force b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/musl/package.use.force new file mode 100644 index 000000000000..1205c8086524 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/musl/package.use.force @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# matoro <matoro_gentoo@matoro.tk> +# We build our riscv musl binaries ourselves, #936643 +dev-lang/rust system-bootstrap diff --git a/profiles/default/linux/riscv/20.0/rv64gc/lp64d/systemd/merged-usr/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..cb41936251b2 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/lp64d/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/lp64d/systemd + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/multilib/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/multilib/deprecated new file mode 100644 index 000000000000..a4771c0b41b7 --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/multilib/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/split-usr/multilib + +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 diff --git a/profiles/default/linux/riscv/20.0/rv64gc/multilib/systemd/merged-usr/deprecated b/profiles/default/linux/riscv/20.0/rv64gc/multilib/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..80d5cdfc4ead --- /dev/null +++ b/profiles/default/linux/riscv/20.0/rv64gc/multilib/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/riscv/23.0/rv64/multilib/systemd + +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 diff --git a/profiles/default/linux/riscv/23.0/rv64/lp64/musl/package.use.force b/profiles/default/linux/riscv/23.0/rv64/lp64/musl/package.use.force new file mode 100644 index 000000000000..1205c8086524 --- /dev/null +++ b/profiles/default/linux/riscv/23.0/rv64/lp64/musl/package.use.force @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# matoro <matoro_gentoo@matoro.tk> +# We build our riscv musl binaries ourselves, #936643 +dev-lang/rust system-bootstrap diff --git a/profiles/default/linux/riscv/23.0/rv64/lp64d/musl/package.mask b/profiles/default/linux/riscv/23.0/rv64/lp64d/musl/package.mask new file mode 100644 index 000000000000..36b75d044c99 --- /dev/null +++ b/profiles/default/linux/riscv/23.0/rv64/lp64d/musl/package.mask @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors. +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-06-12) +# rust-bin is available on riscv musl +-dev-lang/rust-bin diff --git a/profiles/default/linux/riscv/23.0/rv64/lp64d/musl/package.use.force b/profiles/default/linux/riscv/23.0/rv64/lp64d/musl/package.use.force new file mode 100644 index 000000000000..1205c8086524 --- /dev/null +++ b/profiles/default/linux/riscv/23.0/rv64/lp64d/musl/package.use.force @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# matoro <matoro_gentoo@matoro.tk> +# We build our riscv musl binaries ourselves, #936643 +dev-lang/rust system-bootstrap diff --git a/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64/musl/package.use.force b/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64/musl/package.use.force new file mode 100644 index 000000000000..1205c8086524 --- /dev/null +++ b/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64/musl/package.use.force @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# matoro <matoro_gentoo@matoro.tk> +# We build our riscv musl binaries ourselves, #936643 +dev-lang/rust system-bootstrap diff --git a/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64d/musl/package.mask b/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64d/musl/package.mask new file mode 100644 index 000000000000..36b75d044c99 --- /dev/null +++ b/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64d/musl/package.mask @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors. +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-06-12) +# rust-bin is available on riscv musl +-dev-lang/rust-bin diff --git a/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64d/musl/package.use.force b/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64d/musl/package.use.force new file mode 100644 index 000000000000..1205c8086524 --- /dev/null +++ b/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64d/musl/package.use.force @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# matoro <matoro_gentoo@matoro.tk> +# We build our riscv musl binaries ourselves, #936643 +dev-lang/rust system-bootstrap diff --git a/profiles/default/linux/s390/17.0/deprecated b/profiles/default/linux/s390/17.0/deprecated new file mode 100644 index 000000000000..61ac072431c1 --- /dev/null +++ b/profiles/default/linux/s390/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/s390/23.0/split-usr + +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 diff --git a/profiles/default/linux/s390/17.0/s390x/deprecated b/profiles/default/linux/s390/17.0/s390x/deprecated new file mode 100644 index 000000000000..c11e580933f3 --- /dev/null +++ b/profiles/default/linux/s390/17.0/s390x/deprecated @@ -0,0 +1,104 @@ +default/linux/s390/23.0/split-usr/s390x + +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 diff --git a/profiles/default/linux/s390/17.0/s390x/systemd/merged-usr/deprecated b/profiles/default/linux/s390/17.0/s390x/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..c0dbaaa46ccf --- /dev/null +++ b/profiles/default/linux/s390/17.0/s390x/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/s390/23.0/s390x/systemd + +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 diff --git a/profiles/default/linux/s390/17.0/systemd/merged-usr/deprecated b/profiles/default/linux/s390/17.0/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..7f3fc08d2879 --- /dev/null +++ b/profiles/default/linux/s390/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/s390/23.0/systemd + +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 diff --git a/profiles/default/linux/sparc/17.0/64ul/deprecated b/profiles/default/linux/sparc/17.0/64ul/deprecated new file mode 100644 index 000000000000..74bb6bf3aef0 --- /dev/null +++ b/profiles/default/linux/sparc/17.0/64ul/deprecated @@ -0,0 +1,104 @@ +default/linux/sparc/23.0/split-usr/64ul + +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 diff --git a/profiles/default/linux/sparc/17.0/64ul/desktop/deprecated b/profiles/default/linux/sparc/17.0/64ul/desktop/deprecated new file mode 100644 index 000000000000..18cc090c46ed --- /dev/null +++ b/profiles/default/linux/sparc/17.0/64ul/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/sparc/23.0/split-usr/64ul/desktop + +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 diff --git a/profiles/default/linux/sparc/17.0/64ul/developer/deprecated b/profiles/default/linux/sparc/17.0/64ul/developer/deprecated new file mode 100644 index 000000000000..74bb6bf3aef0 --- /dev/null +++ b/profiles/default/linux/sparc/17.0/64ul/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/sparc/23.0/split-usr/64ul + +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 diff --git a/profiles/default/linux/sparc/17.0/64ul/systemd/merged-usr/deprecated b/profiles/default/linux/sparc/17.0/64ul/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..a1b8be4d89d4 --- /dev/null +++ b/profiles/default/linux/sparc/17.0/64ul/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/sparc/23.0/64ul/systemd + +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 diff --git a/profiles/default/linux/sparc/17.0/deprecated b/profiles/default/linux/sparc/17.0/deprecated new file mode 100644 index 000000000000..60588d75d06b --- /dev/null +++ b/profiles/default/linux/sparc/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/sparc/23.0/split-usr + +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 diff --git a/profiles/default/linux/sparc/17.0/desktop/deprecated b/profiles/default/linux/sparc/17.0/desktop/deprecated new file mode 100644 index 000000000000..954e06165107 --- /dev/null +++ b/profiles/default/linux/sparc/17.0/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/sparc/23.0/split-usr/desktop + +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 diff --git a/profiles/default/linux/sparc/17.0/developer/deprecated b/profiles/default/linux/sparc/17.0/developer/deprecated new file mode 100644 index 000000000000..60588d75d06b --- /dev/null +++ b/profiles/default/linux/sparc/17.0/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/sparc/23.0/split-usr + +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 diff --git a/profiles/default/linux/sparc/17.0/systemd/merged-usr/deprecated b/profiles/default/linux/sparc/17.0/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..f43dfd7a92d6 --- /dev/null +++ b/profiles/default/linux/sparc/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/sparc/23.0/systemd + +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 diff --git a/profiles/default/linux/x86/17.0/deprecated b/profiles/default/linux/x86/17.0/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/desktop/deprecated b/profiles/default/linux/x86/17.0/desktop/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/desktop/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/desktop/gnome/deprecated b/profiles/default/linux/x86/17.0/desktop/gnome/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/desktop/gnome/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/x86/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/desktop/plasma/deprecated b/profiles/default/linux/x86/17.0/desktop/plasma/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/desktop/plasma/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/desktop/plasma/systemd/merged-usr/deprecated b/profiles/default/linux/x86/17.0/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/developer/deprecated b/profiles/default/linux/x86/17.0/developer/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/developer/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/hardened/deprecated b/profiles/default/linux/x86/17.0/hardened/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/hardened/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/hardened/selinux/deprecated b/profiles/default/linux/x86/17.0/hardened/selinux/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/hardened/selinux/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/musl/deprecated b/profiles/default/linux/x86/17.0/musl/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/musl/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/musl/parent b/profiles/default/linux/x86/17.0/musl/parent index 58651906cb67..9ef7663a23b6 100644 --- a/profiles/default/linux/x86/17.0/musl/parent +++ b/profiles/default/linux/x86/17.0/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../features/musl +../../../../../features/wd40 diff --git a/profiles/default/linux/x86/17.0/musl/selinux/deprecated b/profiles/default/linux/x86/17.0/musl/selinux/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/musl/selinux/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/selinux/deprecated b/profiles/default/linux/x86/17.0/selinux/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/selinux/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/17.0/systemd/merged-usr/deprecated b/profiles/default/linux/x86/17.0/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..063fe9af04c0 --- /dev/null +++ b/profiles/default/linux/x86/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +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 diff --git a/profiles/default/linux/x86/23.0/i486/musl/package.use.mask b/profiles/default/linux/x86/23.0/i486/musl/package.use.mask index b794980bdad7..0f0f54b0e2d2 100644 --- a/profiles/default/linux/x86/23.0/i486/musl/package.use.mask +++ b/profiles/default/linux/x86/23.0/i486/musl/package.use.mask @@ -1,6 +1,15 @@ -# Copyright 1999-2020 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License, v2 +# Sam James <sam@gentoo.org> (2024-06-16) +# Avoid pulling in sys-libs/compiler-rt-sanitizers which fails to build +# See bug #928936. +sys-devel/clang-runtime sanitize + +# Ian Jordan <immoloism@gmail.com> (2024-05-20) +# Does not compile with musl-1.2.4+ +sys-devel/gcc sanitize + # Anthony G. Basile <blueness@gentoo.org> (2020-09-06) # The patch added for 5.39-r1 breaks on musl i686 # file-5.39-seccomp_sandbox.patch is okay diff --git a/profiles/default/linux/x86/23.0/i486/musl/package.use.stable.mask b/profiles/default/linux/x86/23.0/i486/musl/package.use.stable.mask deleted file mode 100644 index c021f45d8508..000000000000 --- a/profiles/default/linux/x86/23.0/i486/musl/package.use.stable.mask +++ /dev/null @@ -1,6 +0,0 @@ -# Copyright 2024 Gentoo Authors -# Distributed under the terms of the GNU General Public License, v2 - -# Andreas K. Hüttel <dilfridge@gentoo.org> (2024-03-20) -# Does not compile with musl-1.2.4 -sys-devel/gcc sanitize diff --git a/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.mask b/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.mask index b794980bdad7..d3fa26567c1d 100644 --- a/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.mask +++ b/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.mask @@ -1,6 +1,10 @@ -# Copyright 1999-2020 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License, v2 +# Ian Jordan <immoloism@gmail.com> (2024-05-20) +# Does not compile with musl-1.2.4+ +sys-devel/gcc sanitize + # Anthony G. Basile <blueness@gentoo.org> (2020-09-06) # The patch added for 5.39-r1 breaks on musl i686 # file-5.39-seccomp_sandbox.patch is okay diff --git a/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.stable.mask b/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.stable.mask deleted file mode 100644 index c021f45d8508..000000000000 --- a/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.stable.mask +++ /dev/null @@ -1,6 +0,0 @@ -# Copyright 2024 Gentoo Authors -# Distributed under the terms of the GNU General Public License, v2 - -# Andreas K. Hüttel <dilfridge@gentoo.org> (2024-03-20) -# Does not compile with musl-1.2.4 -sys-devel/gcc sanitize diff --git a/profiles/default/linux/x86/23.0/i686/musl/package.use.mask b/profiles/default/linux/x86/23.0/i686/musl/package.use.mask index b794980bdad7..0f0f54b0e2d2 100644 --- a/profiles/default/linux/x86/23.0/i686/musl/package.use.mask +++ b/profiles/default/linux/x86/23.0/i686/musl/package.use.mask @@ -1,6 +1,15 @@ -# Copyright 1999-2020 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License, v2 +# Sam James <sam@gentoo.org> (2024-06-16) +# Avoid pulling in sys-libs/compiler-rt-sanitizers which fails to build +# See bug #928936. +sys-devel/clang-runtime sanitize + +# Ian Jordan <immoloism@gmail.com> (2024-05-20) +# Does not compile with musl-1.2.4+ +sys-devel/gcc sanitize + # Anthony G. Basile <blueness@gentoo.org> (2020-09-06) # The patch added for 5.39-r1 breaks on musl i686 # file-5.39-seccomp_sandbox.patch is okay diff --git a/profiles/default/linux/x86/23.0/i686/musl/package.use.stable.mask b/profiles/default/linux/x86/23.0/i686/musl/package.use.stable.mask deleted file mode 100644 index c021f45d8508..000000000000 --- a/profiles/default/linux/x86/23.0/i686/musl/package.use.stable.mask +++ /dev/null @@ -1,6 +0,0 @@ -# Copyright 2024 Gentoo Authors -# Distributed under the terms of the GNU General Public License, v2 - -# Andreas K. Hüttel <dilfridge@gentoo.org> (2024-03-20) -# Does not compile with musl-1.2.4 -sys-devel/gcc sanitize diff --git a/profiles/default/linux/x86/23.0/i686/musl/parent b/profiles/default/linux/x86/23.0/i686/musl/parent index 5bbe8700f1a6..bd0ef6ecac62 100644 --- a/profiles/default/linux/x86/23.0/i686/musl/parent +++ b/profiles/default/linux/x86/23.0/i686/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../../features/musl +../../../../../../features/wd40 diff --git a/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.mask b/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.mask index b794980bdad7..d3fa26567c1d 100644 --- a/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.mask +++ b/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.mask @@ -1,6 +1,10 @@ -# Copyright 1999-2020 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License, v2 +# Ian Jordan <immoloism@gmail.com> (2024-05-20) +# Does not compile with musl-1.2.4+ +sys-devel/gcc sanitize + # Anthony G. Basile <blueness@gentoo.org> (2020-09-06) # The patch added for 5.39-r1 breaks on musl i686 # file-5.39-seccomp_sandbox.patch is okay diff --git a/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.stable.mask b/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.stable.mask deleted file mode 100644 index c021f45d8508..000000000000 --- a/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.stable.mask +++ /dev/null @@ -1,6 +0,0 @@ -# Copyright 2024 Gentoo Authors -# Distributed under the terms of the GNU General Public License, v2 - -# Andreas K. Hüttel <dilfridge@gentoo.org> (2024-03-20) -# Does not compile with musl-1.2.4 -sys-devel/gcc sanitize diff --git a/profiles/default/linux/x86/23.0/i686/split-usr/musl/parent b/profiles/default/linux/x86/23.0/i686/split-usr/musl/parent index b488e1ca01b8..a3de2bcf95f7 100644 --- a/profiles/default/linux/x86/23.0/i686/split-usr/musl/parent +++ b/profiles/default/linux/x86/23.0/i686/split-usr/musl/parent @@ -1,2 +1,3 @@ .. ../../../../../../../features/musl +../../../../../../../features/wd40 diff --git a/profiles/arch/powerpc/ppc64/32ul/eapi b/profiles/default/linux/x86/23.0/i686/time64/eapi index 7ed6ff82de6b..7ed6ff82de6b 100644 --- a/profiles/arch/powerpc/ppc64/32ul/eapi +++ b/profiles/default/linux/x86/23.0/i686/time64/eapi diff --git a/profiles/default/linux/x86/23.0/i686/time64/make.defaults b/profiles/default/linux/x86/23.0/i686/time64/make.defaults new file mode 100644 index 000000000000..983829cdc512 --- /dev/null +++ b/profiles/default/linux/x86/23.0/i686/time64/make.defaults @@ -0,0 +1,5 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +CHOST="i686-pc_t64-linux-gnu" +CHOST_x86="${CHOST}" diff --git a/profiles/default/linux/x86/23.0/i686/time64/package.accept_keywords b/profiles/default/linux/x86/23.0/i686/time64/package.accept_keywords new file mode 100644 index 000000000000..f065ec275cad --- /dev/null +++ b/profiles/default/linux/x86/23.0/i686/time64/package.accept_keywords @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# For better testing of time64, we use gcc-14 here already in an otherwise stable +# environment. +sys-devel/gcc:14 ~x86 diff --git a/profiles/default/linux/x86/23.0/i686/time64/parent b/profiles/default/linux/x86/23.0/i686/time64/parent new file mode 100644 index 000000000000..1072670e42f2 --- /dev/null +++ b/profiles/default/linux/x86/23.0/i686/time64/parent @@ -0,0 +1,2 @@ +.. +../../../../../../features/time64 diff --git a/profiles/default/linux/ia64/17.0/desktop/eapi b/profiles/default/linux/x86/23.0/i686/time64/systemd/eapi index 7ed6ff82de6b..7ed6ff82de6b 100644 --- a/profiles/default/linux/ia64/17.0/desktop/eapi +++ b/profiles/default/linux/x86/23.0/i686/time64/systemd/eapi diff --git a/profiles/default/linux/x86/23.0/i686/time64/systemd/parent b/profiles/default/linux/x86/23.0/i686/time64/systemd/parent new file mode 100644 index 000000000000..44f88d3e2df0 --- /dev/null +++ b/profiles/default/linux/x86/23.0/i686/time64/systemd/parent @@ -0,0 +1,2 @@ +.. +../../../../../../../targets/systemd diff --git a/profiles/desc/ada_target.desc b/profiles/desc/ada_target.desc index 005be2d73640..d9b797cfb661 100644 --- a/profiles/desc/ada_target.desc +++ b/profiles/desc/ada_target.desc @@ -1,6 +1,8 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 gnat_2021 - Compile with dev-lang/gnat-gpl-2021 gcc_12 - Compile with sys-devel/gcc:12 gcc_13 - Compile with sys-devel/gcc:13 +gcc_14 - Compile with sys-devel/gcc:14 +gcc_15 - Compile with sys-devel/gcc:15 diff --git a/profiles/desc/curl_quic.desc b/profiles/desc/curl_quic.desc new file mode 100644 index 000000000000..372bb9ce8f83 --- /dev/null +++ b/profiles/desc/curl_quic.desc @@ -0,0 +1,7 @@ +# Copyright 1999-2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# This file contains descriptions of CURL_QUIC USE_EXPAND flags for net-misc/curl + +openssl - Use OpenSSL +ngtcp2 - Use ngtcp2 diff --git a/profiles/desc/curl_ssl.desc b/profiles/desc/curl_ssl.desc index 9023283859e1..3ac2d3b60f2f 100644 --- a/profiles/desc/curl_ssl.desc +++ b/profiles/desc/curl_ssl.desc @@ -1,8 +1,7 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # This file contains descriptions of CURL_SSL USE_EXPAND flags for net-misc/curl -# spnego - Use SPNEGO fbopenssl - to be added gnutls - Use GnuTLS mbedtls - Use mbed TLS diff --git a/profiles/desc/gpsd_protocols.desc b/profiles/desc/gpsd_protocols.desc index c27e9b112a2b..31d9dbaf9162 100644 --- a/profiles/desc/gpsd_protocols.desc +++ b/profiles/desc/gpsd_protocols.desc @@ -1,4 +1,4 @@ -# Copyright 1999-2019 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # This file contains descriptions of possible protocols for gpsd package. @@ -17,14 +17,10 @@ gpsclock - GPSclock protocol support greis - Javad GREIS protocol support isync - Isync protocol support itrax - iTrax protocol support -mtk3301 - MTK-3301 protocol support navcom - Navcom protocol support -nmea0183 - NMEA protocol support nmea2000 - NMEA2000/CAN support -ntrip - NTRIP protocol support oceanserver - OceanServer protocol support oncore - OnCore protocol support -passthrough - Pass through JSON data rtcm104v2 - RTCM104V2 protocol support rtcm104v3 - RTCM104V3 protocol support sirf - SiRF protocol support diff --git a/profiles/desc/guile_single_target.desc b/profiles/desc/guile_single_target.desc new file mode 100644 index 000000000000..81322b2380d4 --- /dev/null +++ b/profiles/desc/guile_single_target.desc @@ -0,0 +1,8 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# This file contains descriptions of GUILE_SINGLE_TARGET USE_EXPAND flags. + +1-8 - Build only for GNU Guile 1.8. +2-2 - Build only for GNU Guile 2.2. +3-0 - Build only for GNU Guile 3.0. diff --git a/profiles/desc/guile_targets.desc b/profiles/desc/guile_targets.desc new file mode 100644 index 000000000000..a56ca35810b7 --- /dev/null +++ b/profiles/desc/guile_targets.desc @@ -0,0 +1,8 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# This file contains descriptions of GUILE_TARGETS USE_EXPAND flags. + +1-8 - Build with GNU Guile 1.8 +2-2 - Build with GNU Guile 2.2 +3-0 - Build with GNU Guile 3.0 diff --git a/profiles/desc/l10n.desc b/profiles/desc/l10n.desc index 8507b4ecd5b2..e37807f4a3e8 100644 --- a/profiles/desc/l10n.desc +++ b/profiles/desc/l10n.desc @@ -1,4 +1,4 @@ -# Copyright 2016-2022 Gentoo Authors +# Copyright 2016-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # This file contains descriptions of L10N USE_EXPAND flags. @@ -188,6 +188,7 @@ sd - Sindhi si - Sinhala sid - Sidamo sk - Slovak +skr - Saraiki sl - Slovenian sml - Central Sama sn - Shona diff --git a/profiles/desc/monkeyd_plugins.desc b/profiles/desc/monkeyd_plugins.desc deleted file mode 100644 index 49a82d1a8bb3..000000000000 --- a/profiles/desc/monkeyd_plugins.desc +++ /dev/null @@ -1,15 +0,0 @@ -# Copyright 1999-2013 Gentoo Foundation. -# Distributed under the terms of the GNU General Public License v2 - -# This file contains descriptions of MONKEYD_PLUGINS USE_EXPAND flags for www-servers/monkeyd. -# All plugins are included here except cgi and fastcgi which are global use flags. - -auth - Provide HTTP Basic Authentication. -cheetah - Provide a shell-like command line interface. -#cgi - Provide the traditional CGI interface - This is a global USE flag. -dirlisting - Show an HTML listing of the content of a directory. -#fastcgi - Provide FastCGI proxy support - This is a global USE flag. -liana - Build your own network layer through monkeyd. -logger - Log requests and common errors. -mandril - Restrict incoming connections based on the IP address or URI request. -tls - Provide TLS using mbed TLS (formerly known as PolarSSL) - Currently disabled. diff --git a/profiles/desc/postgres_targets.desc b/profiles/desc/postgres_targets.desc index d40f508181cc..7e18a89e66d0 100644 --- a/profiles/desc/postgres_targets.desc +++ b/profiles/desc/postgres_targets.desc @@ -8,3 +8,4 @@ postgres13 - Build against PostgreSQL 13 postgres14 - Build against PostgreSQL 14 postgres15 - Build against PostgreSQL 15 postgres16 - Build against PostgreSQL 16 +postgres17 - Build against PostgreSQL 17 diff --git a/profiles/desc/video_cards.desc b/profiles/desc/video_cards.desc index f03d0d11b5ea..e54f4b53d7bd 100644 --- a/profiles/desc/video_cards.desc +++ b/profiles/desc/video_cards.desc @@ -43,3 +43,4 @@ virgl - VIDEO_CARDS setting to build driver for virgil (virtual 3D GPU) virtualbox - VIDEO_CARDS setting to build driver for virtualbox emulation vivante - VIDEO_CARDS setting to build etnaviv driver for vivante video cards vmware - VIDEO_CARDS setting to build driver for vmware video cards +zink - VIDEO_CARDS setting to build Zink OpenGL-over-Vulkan Gallium driver diff --git a/profiles/embedded/make.defaults b/profiles/embedded/make.defaults index 96fbd36959f5..d2e418b98da3 100644 --- a/profiles/embedded/make.defaults +++ b/profiles/embedded/make.defaults @@ -22,14 +22,14 @@ LINGUAS="en" IUSE_IMPLICIT="prefix prefix-guest prefix-stack" USE_EXPAND_UNPREFIXED="ARCH" USE_EXPAND_IMPLICIT="ARCH ELIBC KERNEL" -USE_EXPAND_VALUES_ARCH="alpha amd64 amd64-linux arm arm64 hppa ia64 loong m68k mips ppc ppc64 ppc64-linux ppc-macos riscv s390 sparc x64-macos x64-solaris x86 x86-linux" +USE_EXPAND_VALUES_ARCH="alpha amd64 amd64-linux arm arm64 hppa loong m68k mips ppc ppc64 ppc64-linux ppc-macos riscv s390 sparc x64-macos x64-solaris x86 x86-linux" USE_EXPAND_VALUES_ELIBC="bionic Darwin glibc mingw musl SunOS" # Note that we keep Winnt here for cross, especially for cmake.eclass (bug #910605) USE_EXPAND_VALUES_KERNEL="Darwin linux SunOS Winnt" # Env vars to expand into USE vars. Modifying this requires prior # discussion on gentoo-dev@lists.gentoo.org. -USE_EXPAND="ABI_MIPS ABI_S390 ABI_X86 ADA_TARGET ALSA_CARDS APACHE2_MODULES APACHE2_MPMS CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_ARM CPU_FLAGS_PPC CPU_FLAGS_X86 CURL_SSL ELIBC FFTOOLS GPSD_PROTOCOLS GRUB_PLATFORMS INPUT_DEVICES KERNEL L10N LCD_DEVICES LIBREOFFICE_EXTENSIONS LLVM_SLOT LLVM_TARGETS LUA_SINGLE_TARGET LUA_TARGETS MONKEYD_PLUGINS NGINX_MODULES_HTTP NGINX_MODULES_MAIL NGINX_MODULES_STREAM OFFICE_IMPLEMENTATION OPENMPI_FABRICS OPENMPI_OFED_FEATURES OPENMPI_RM PHP_TARGETS POSTGRES_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS RUBY_TARGETS SANE_BACKENDS UWSGI_PLUGINS VIDEO_CARDS VOICEMAIL_STORAGE XTABLES_ADDONS" +USE_EXPAND="ABI_MIPS ABI_S390 ABI_X86 ADA_TARGET ALSA_CARDS APACHE2_MODULES APACHE2_MPMS CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_ARM CPU_FLAGS_PPC CPU_FLAGS_X86 CURL_SSL ELIBC FFTOOLS GPSD_PROTOCOLS GRUB_PLATFORMS INPUT_DEVICES KERNEL L10N LCD_DEVICES LIBREOFFICE_EXTENSIONS LLVM_SLOT LLVM_TARGETS LUA_SINGLE_TARGET LUA_TARGETS NGINX_MODULES_HTTP NGINX_MODULES_MAIL NGINX_MODULES_STREAM OFFICE_IMPLEMENTATION OPENMPI_FABRICS OPENMPI_OFED_FEATURES OPENMPI_RM PHP_TARGETS POSTGRES_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS RUBY_TARGETS SANE_BACKENDS UWSGI_PLUGINS VIDEO_CARDS VOICEMAIL_STORAGE XTABLES_ADDONS" # USE_EXPAND variables whose contents are not shown in package manager # output. Changes need discussion on gentoo-dev. diff --git a/profiles/features/big-endian/package.mask b/profiles/features/big-endian/package.mask index 407bf030c989..1e9525c6e837 100644 --- a/profiles/features/big-endian/package.mask +++ b/profiles/features/big-endian/package.mask @@ -1,6 +1,16 @@ # Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Michał Górny <mgorny@gentoo.org> (2024-06-07) +# dev-python/tables is broken on big endian platforms. Bug #922235. +dev-python/tables + +# Michał Górny <mgorny@gentoo.org> (2024-06-05) +# media-libs/exempi is seriously broken on big endian platforms. +# https://gitlab.freedesktop.org/libopenraw/exempi/-/merge_requests/8#note_2277243 +dev-python/python-xmp-toolkit +media-libs/exempi + # matoro <matoro_gentoo@matoro.tk> (2024-01-09) # Test failures on BE (#920353, #902191) net-misc/nextcloud-client @@ -43,6 +53,7 @@ kde-apps/knotes kde-apps/kdepim-meta kde-apps/kdepim-addons kde-apps/kaddressbook +kde-apps/kaccounts-integration:6 kde-apps/kaccounts-providers kde-apps/akonadiconsole kde-apps/akonadi-calendar diff --git a/profiles/features/big-endian/package.use.mask b/profiles/features/big-endian/package.use.mask index a83df9315ceb..bbde951452d2 100644 --- a/profiles/features/big-endian/package.use.mask +++ b/profiles/features/big-endian/package.use.mask @@ -1,6 +1,15 @@ -# Copyright 2023 Gentoo Authors +# Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Michał Górny <mgorny@gentoo.org> (2024-06-05) +# media-libs/exempi is seriously broken on big endian platforms. +# https://gitlab.freedesktop.org/libopenraw/exempi/-/merge_requests/8#note_2277243 +app-misc/tracker-miners xmp +games-fps/eduke32 xmp +gnome-extra/nemo xmp +media-gfx/eog xmp +media-libs/gexiv2 test + # matoro <matoro_gentoo@matoro.tk> (2023-11-16) # media-libs/libvpx casualties (#700902) media-video/ffmpeg vpx @@ -36,6 +45,7 @@ gui-libs/gtk wayland gnome-base/gnome-control-center wayland sys-apps/xdg-desktop-portal-gnome wayland net-libs/webkit-gtk:6 wayland +dev-libs/libportal wayland # matoro <matoro_gentoo@matoro.tk> (2023-04-10) # media-libs/libldac casualties (#80238) diff --git a/profiles/features/big-endian/use.mask b/profiles/features/big-endian/use.mask index 49de7dd81e15..792562b3f91a 100644 --- a/profiles/features/big-endian/use.mask +++ b/profiles/features/big-endian/use.mask @@ -1,4 +1,4 @@ -# Copyright 2023 Gentoo Authors +# Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # matoro <matoro_gentoo@matoro.tk> (2023-06-30) diff --git a/profiles/features/hardened/make.defaults b/profiles/features/hardened/make.defaults index 8843d9bdb2c8..431f75d3915d 100644 --- a/profiles/features/hardened/make.defaults +++ b/profiles/features/hardened/make.defaults @@ -12,7 +12,7 @@ USE="hardened pic xtpax -jit -orc" # This variable can be leveraged in ebuilds for pkg_postinst messages that # indicate said package is, say, configured in a way that defeats the purpose # of running hardened. -PROFILE_IS_HARDENED=1 +PROFILE_IS_HARDENED="1" # We set the default markings to none PAX_MARKINGS="none" diff --git a/profiles/features/llvm/make.defaults b/profiles/features/llvm/make.defaults index ce3401222615..f36599c1e300 100644 --- a/profiles/features/llvm/make.defaults +++ b/profiles/features/llvm/make.defaults @@ -31,7 +31,7 @@ ADDR2LINE="llvm-addr2line" # Rust needs this to build some crates (like uutils) # https://github.com/rust-lang/rust/blob/master/compiler/rustc_llvm/build.rs -LLVM_USE_LIBCXX=1 +LLVM_USE_LIBCXX="1" # https://github.com/rust-lang/cc-rs#c-support # https://github.com/rust-lang/cc-rs/blob/main/src/lib.rs CXXSTDLIB="c++" @@ -41,9 +41,6 @@ CXXSTDLIB="c++" # curl needed by cmake BOOTSTRAP_USE="${BOOTSTRAP_USE} ssl curl_ssl_openssl" -# Clang needs this -BOOTSTRAP_USE="${BOOTSTRAP_USE} python_single_target_python3_11" - # sys-devel/llvm BOOTSTRAP_USE="${BOOTSTRAP_USE} -binutils-plugin" diff --git a/profiles/features/llvm/package.accept_keywords b/profiles/features/llvm/package.accept_keywords deleted file mode 100644 index 231f53933017..000000000000 --- a/profiles/features/llvm/package.accept_keywords +++ /dev/null @@ -1,8 +0,0 @@ -# Copyright 2022 Gentoo Authors -# Distributed under the terms of the GNU General Public License v2 - -# this version contains the path fix for portage needed for stage1 builds -=sys-apps/portage-3.0.33 ~amd64 - -# this version contains the fix for CPP resetting -=sys-libs/glibc-2.35-r10 ~amd64 diff --git a/profiles/features/llvm/package.use.mask b/profiles/features/llvm/package.use.mask index 2b52ec272120..9559cea0d1f0 100644 --- a/profiles/features/llvm/package.use.mask +++ b/profiles/features/llvm/package.use.mask @@ -1,6 +1,11 @@ -# Copyright 2022-2023 Gentoo Authors +# Copyright 2022-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Jimi Huotari <chiitoo@gentoo.org> (2024-08-22) +# Fails to compile due to a pre-built binary. +# Gentoo bug: 922163 +media-video/obs-studio browser + # Sam James <sam@gentoo.org> (2023-07-22) # Doesn't call llvm-profdata so fails. sys-devel/binutils pgo @@ -8,6 +13,3 @@ sys-devel/binutils pgo # Sam James <sam@gentoo.org> (2022-09-15) # Works on pure LLVM systems: bug #870211. dev-lang/rust -llvm-libunwind - -# libquadmath is gcc-specific -dev-lang/perl quadmath diff --git a/profiles/features/musl/package.mask b/profiles/features/musl/package.mask index f54ff6cdaabc..880c3d73987f 100644 --- a/profiles/features/musl/package.mask +++ b/profiles/features/musl/package.mask @@ -1,6 +1,20 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James <sam@gentoo.org> (2024-09-30) +# Needs porting to musl (bug #940130) +=sys-auth/elogind-255.5 + +# Sam James <sam@gentoo.org> (2024-08-31) +# sys-devel/binutils[gprofng] is masked on musl +dev-debug/gprofng-gui + +# Sam James <sam@gentoo.org> (2024-08-21) +# systemtap needs porting to musl. Fails to compile in a few ways. +# See bug #925857. +dev-debug/systemtap +sys-apps/tuned + # Robert Förster <Dessa@gmake.de> (2024-05-06) # needs mongodb net-wireless/unifi @@ -28,10 +42,6 @@ app-emulation/protontricks # Mask until execinfo.h use can be properly patched, bug #853856 media-gfx/renderdoc -# Maciej Barć <xgqt@gentoo.org> (2024-03-23) -# Binary package, which is compiled against glibc -www-apps/jellyfin-bin - # Arthur Zamarin <arthurzam@gentoo.org> (2024-03-15) # Needs ada sci-electronics/ghdl @@ -76,53 +86,23 @@ games-strategy/seven-kingdoms # this time. (#925547) app-arch/lrzip-next -# Marek Szuba <marecki@gentoo.org> (2024-02-18) -# Binary-only packages linked against glibc -net-analyzer/nessus-agent-bin -net-analyzer/nessus-bin - -# Marc Schiffbauer <mschiff@gentoo.org> (2024-02-16) -# Binary package, which is compiled against glibc -app-editors/logseq-desktop-bin - # Christopher Fore <csfore@posteo.net> (2024-01-24) # >=sys-fs/bcachefs-tools-1.4.1 uses functions currently not in Musl # https://github.com/koverstreet/bcachefs-tools/issues/213 ->=sys-fs/bcachefs-tools-1.4.1 +# The above was fixed in musl 1.2.5, which bcachefs-tools 1.11.0 +# will now depend on. +# https://www.openwall.com/lists/musl/2024/03/01/2 +<sys-fs/bcachefs-tools-1.11.0 # Conrad Kostecki <conikost@gentoo.org> (2024-01-23) # Uses glibc function getsourcefilter(), # which are not available on musl. net-misc/mcproxy -# Giuseppe Foti <foti.giuseppe@gmail.com> (2024-01-22) -# Binary package, which is compiled against glibc -app-office/drawio-desktop-bin - -# Maciej Barć <xgqt@gentoo.org> (2024-01-06) -# Binary package, which is compiled against glibc -app-office/joplin-desktop - -# Maciej Barć <xgqt@gentoo.org> (2024-01-06) -# Binary package, which is compiled against glibc -dev-util/azuredatastudio - # Florian Schmaus <flow@gentoo.org> (2023-11-22) # Requires systemd which is not supported on musl. sys-power/sandmann-bin -# Maciej Barć <xgqt@gentoo.org> (2023-09-16) -# Binary package, which is compiled against glibc -dev-lang/dafny-bin - -# Maciej Barć <xgqt@gentoo.org> (2023-09-16) -# Binary package, which is compiled against glibc -app-shells/pwsh-bin - -# Maciej Barć <xgqt@gentoo.org> (2023-07-01) -# Binary package, which is compiled against glibc -games-util/heroic-bin - # Brahmajit Das <brahmajit.xyz@gmail.com> (2023-06-15) # The package uses innetgr which is not available in musl, bug 898556 # The package is only for long-obsolete polkit policies anyway. @@ -136,14 +116,6 @@ sys-auth/polkit-pkla-compat # Mask until execinfo.h use can be properly patched, bug #877721 and #903689. dev-scheme/guile-ssh -# Conrad Kostecki <conikost@gentoo.org> (2023-03-01) -# Binary package, which is compiled against glibc -sys-block/arcconf - -# Conrad Kostecki <conikost@gentoo.org> (2023-03-01) -# Binary package, which is compiled against glibc -sys-apps/smcipmitool - # Alfredo Tupone <tupone@gentoo.org> (2023-02-27) # Uses dev-util/nvidia-cuda-sdk dev-libs/cutlass @@ -170,7 +142,6 @@ net-analyzer/openvas-scanner net-analyzer/ospd-openvas net-misc/grive net-print/pnm2ppa -net-wireless/neard sys-apps/noexec # Giuseppe Foti <foti.giuseppe@gmail.com> (2023-05-19) @@ -178,6 +149,7 @@ sys-apps/noexec dev-db/pg-gvm net-analyzer/notus-scanner net-analyzer/greenbone-feed-sync +net-analyzer/boreas # Petr Vaněk <arkamar@atlas.cz> (2022-09-23) # Musl does not implement rresvport function, bugs #713810 and #713376. @@ -231,19 +203,26 @@ app-admin/awscli-bin app-admin/bitwarden-desktop-bin app-admin/puppet-agent app-admin/puppetserver +app-admin/winbox app-arch/rar app-backup/tsm app-benchmarks/geekbench app-benchmarks/geekbench-ml app-crypt/rainbowcrack app-crypt/yubioath-flutter-bin +app-editors/logseq-desktop-bin app-editors/sublime-text app-editors/vscode app-editors/vscodium app-emulation/crossover-bin +app-emulation/genymotion-bin app-misc/kryoflux-dtc +app-office/drawio-desktop-bin +app-office/joplin-desktop app-office/libreoffice-bin app-office/libreoffice-bin-debug +app-office/onlyoffice-bin +app-shells/pwsh-bin app-text/master-pdf-editor app-text/zotero-bin dev-db/ocp @@ -252,11 +231,13 @@ dev-db/sqlcl-bin dev-games/ps2-packer dev-java/openjdk-bin dev-java/openjdk-jre-bin +dev-lang/dafny-bin dev-libs/luise dev-libs/nwjs dev-perl/Lab-Zhinst dev-php/PEAR-MDB2_Driver_oci8 dev-python/pyzotero +dev-util/azuredatastudio dev-util/idea-community games-action/a-story-about-my-uncle games-action/badland @@ -307,14 +288,14 @@ games-server/steamcmd games-server/ut2004-ded games-simulation/slime-rancher games-strategy/darwinia -games-strategy/darwinia-demo games-strategy/knights-demo -games-strategy/majesty-demo +games-util/heroic-bin gnome-extra/nautilus-dropbox kde-apps/dolphin-plugins-dropbox mail-client/thunderbird-bin mate-extra/caja-dropbox media-gfx/brscan4 +media-gfx/evoluspencil media-libs/amdgpu-pro-vulkan media-sound/baudline media-sound/teamspeak-server @@ -323,6 +304,8 @@ media-video/amdgpu-pro-amf media-video/dvbackup media-video/makemkv media-video/popcorntime-bin +net-analyzer/nessus-agent-bin +net-analyzer/nessus-bin net-im/discord net-im/element-desktop-bin net-im/gitter-bin @@ -343,6 +326,7 @@ net-nntp/sabnzbd net-p2p/resilio-sync net-print/cnijfilter2 net-print/hplip-plugin +net-vpn/microsoft-azurevpnclient sci-chemistry/cara-bin sci-electronics/eagle sci-electronics/labone @@ -352,16 +336,15 @@ sci-misc/jupyterlab-desktop-bin sci-misc/netlogo-bin sys-apps/intune-portal sys-apps/ipmicfg +sys-apps/smcipmitool sys-apps/tas +sys-block/arcconf sys-block/hpssacli sys-block/megacli www-apps/chromedriver-bin www-apps/grafana-bin -www-apps/jellyfin +www-apps/jellyfin-bin www-apps/kibana-bin -www-apps/prowlarr -www-apps/radarr -www-apps/readarr www-client/firefox-bin www-client/google-chrome www-client/google-chrome-beta diff --git a/profiles/features/musl/package.use.force b/profiles/features/musl/package.use.force index 78001ea4cdfe..5dc756fc6d32 100644 --- a/profiles/features/musl/package.use.force +++ b/profiles/features/musl/package.use.force @@ -1,6 +1,11 @@ # Copyright 1999-2024 Gentoo Authors. # Distributed under the terms of the GNU General Public License v2 +# Sam James <sam@gentoo.org> (2024-06-03) +# Poor rendering performance otherwise (bug #931215) but it doesn't +# work on musl. +kde-plasma/kwin -caps + # Violet Purcell <vimproved@inventati.org> (2023-04-25) # SBCL Upstream does not provide musl binaries for bootstrap, use CLisp. dev-lisp/sbcl system-bootstrap diff --git a/profiles/features/musl/package.use.mask b/profiles/features/musl/package.use.mask index 67ed6fe94f32..1bae192c2abe 100644 --- a/profiles/features/musl/package.use.mask +++ b/profiles/features/musl/package.use.mask @@ -1,6 +1,34 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Ian Jordan <immoloism@gmail.com> (2024-08-22) +# Browser uses a prebuilt binary built against glibc (bug #934005) +media-video/obs-studio browser + +# Sam James <sam@gentoo.org> (2024-08-21) +# dev-debug/systemtap doesn't work on musl +app-emulation/libvirt dtrace +gui-libs/neatvnc tracing +gui-apps/wayvnc tracing + +# Mattéo Rossillol‑‑Laruelle <beatussum@protonmail.com> (2024-08-06) +# Requires sys-libs/libcxx. +dev-cpp/benchmark libcxx + +# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-07-25) +# Requires systemd-detect-virt +app-emulation/virt-firmware test + +# Sam James <sam@gentoo.org> (2024-06-03) +# Poor rendering performance otherwise (bug #931215) but it doesn't +# work on musl. +kde-plasma/kwin caps + +# Violet Purcell <vimproved@inventati.org> (2024-05-15) +# Python does not support JIT on musl, see +# https://peps.python.org/pep-0744/#support. +dev-lang/python jit + # Robert Förster <Dessa@gmake.de> (2024-05-06) # dev-db/mongodb is masked on musl dev-libs/mongo-c-driver test @@ -44,6 +72,11 @@ sys-devel/gcc cet sys-libs/binutils-libs cet sys-libs/glibc cet +# Andreas K. Hüttel <dilfridge@gentoo.org> (2024-03-05) +# gprofng is still somewhat messed up with musl-1.2.4, does not build +# bug 912284 +sys-devel/binutils gprofng + # Violet Purcell <vimproved@inventati.org> (2024-01-25) # f16c support in gtk4 requires the ifunc attribute, which # is not available on musl. There is a configure check for @@ -128,6 +161,7 @@ www-client/qutebrowser widevine net-analyzer/wireshark sdjournal sys-apps/ipmitool openbmc sys-auth/pambase homed +dev-qt/qtbase journald # Petr Vaněk <arkamar@atlas.cz> (2022-03-15) # musl package does not currently provide gencat binary, which is needed for @@ -150,6 +184,7 @@ net-misc/iputils rarpd # Sam James <sam@gentoo.org> (2021-11-20) # Pulls in po4a which doesn't seem to work on musl (wants /usr/bin/locale) app-arch/dpkg nls +app-crypt/loop-aes-losetup nls app-emulation/guestfs-tools doc app-emulation/libguestfs doc app-text/bibletime doc diff --git a/profiles/features/musl/package.use.stable.mask b/profiles/features/musl/package.use.stable.mask index 0a42768ac43b..a903356e7e0b 100644 --- a/profiles/features/musl/package.use.stable.mask +++ b/profiles/features/musl/package.use.stable.mask @@ -1,16 +1,10 @@ -# Copyright 2022 Gentoo Authors +# Copyright 2022-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # Andreas K. Hüttel <dilfridge@gentoo.org> (2024-03-07) # This doesn't work yet with musl-1.2.4, bug 906603 sys-libs/compiler-rt-sanitizers msan -# Andreas K. Hüttel <dilfridge@gentoo.org> (2024-03-05) -# gprofng is still somewhat messed up with musl-1.2.4, does not build -# let's hope this is fixed with the next release -# bug 912284 -<sys-devel/binutils-2.43 gprofng - # Sam James <sam@gentoo.org> (2022-10-04) # libxcrypt migration isn't yet stable on musl. sys-auth/pambase yescrypt diff --git a/profiles/features/musl/use.mask b/profiles/features/musl/use.mask index 8188a9fef818..36a3df9cb46b 100644 --- a/profiles/features/musl/use.mask +++ b/profiles/features/musl/use.mask @@ -1,10 +1,14 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # Select the correct ELIBC -elibc_musl elibc_glibc +# Sam James <sam@gentoo.org> (2024-08-21) +# dev-debug/systemtap doesn't work on musl +systemtap + # Sam James <sam@gentoo.org> (2022-10-04) # Mask USE flags which pull in a binary package linked against glibc (rolling # mask, use for all such packages) diff --git a/profiles/features/prefix/standalone/kernel-2.6.16+/make.defaults b/profiles/features/prefix/standalone/kernel-2.6.16+/make.defaults index 4f6092226447..b98ce4ffc95f 100644 --- a/profiles/features/prefix/standalone/kernel-2.6.16+/make.defaults +++ b/profiles/features/prefix/standalone/kernel-2.6.16+/make.defaults @@ -13,10 +13,10 @@ # utimensat is missing or not reliable until linux-2.6.32. # needed by python-3. # lutimes requires utimensat -ac_cv_func_utimensat=no -ac_cv_func_lutimes=no +ac_cv_func_utimensat="no" +ac_cv_func_lutimes="no" # pipe2 and dup3 requires >=linux-2.6.27. Needed by python-3. -ac_cv_func_pipe2=no -ac_cv_func_dup3=no +ac_cv_func_pipe2="no" +ac_cv_func_dup3="no" # epoll_create1 requires >=linux-2.6.27. -ac_cv_func_epoll_create1=no +ac_cv_func_epoll_create1="no" diff --git a/profiles/features/prefix/standalone/kernel-2.6.16+/package.use.mask b/profiles/features/prefix/standalone/kernel-2.6.16+/package.use.mask index b838f9fa82cc..266afd1a1eee 100644 --- a/profiles/features/prefix/standalone/kernel-2.6.16+/package.use.mask +++ b/profiles/features/prefix/standalone/kernel-2.6.16+/package.use.mask @@ -1,4 +1,4 @@ -# Copyright 1999-2022 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # Benda Xu <heroxbd@gentoo.org> (2019-10-14) @@ -6,7 +6,6 @@ # without checking. That results on build time failure, because we have # stripped away F_DUPFD_CLOEXEC from glibc for this profile. media-libs/mesa gles2 llvm -media-libs/libepoxy egl # Benda Xu <heroxbd@gentoo.org> (2018-02-21) # We are on an old kernel that only glibc-2.19 is supported. That glibc does diff --git a/profiles/features/prefix/standalone/kernel-2.6.32+/make.defaults b/profiles/features/prefix/standalone/kernel-2.6.32+/make.defaults index 056f07700a5d..33e139f1ded2 100644 --- a/profiles/features/prefix/standalone/kernel-2.6.32+/make.defaults +++ b/profiles/features/prefix/standalone/kernel-2.6.32+/make.defaults @@ -1,4 +1,4 @@ # This profile is supporting >=linux-2.6.32[a] and <linux-3.2[b]. # only available in glibc-2.26. -ac_cv_func_reallocarray=no +ac_cv_func_reallocarray="no" diff --git a/profiles/features/prefix/standalone/make.defaults b/profiles/features/prefix/standalone/make.defaults index 09b32b13eaaa..a5acafc188fa 100644 --- a/profiles/features/prefix/standalone/make.defaults +++ b/profiles/features/prefix/standalone/make.defaults @@ -4,6 +4,6 @@ # remove when python-3.4 goes end-of-life on 2019-03-16, # and when python-2.7 goes end-of-life on 2020-01-01. # https://docs.python.org/devguide/#status-of-python-branches -ac_cv_func_getentropy=no +ac_cv_func_getentropy="no" # Reconsider the stability of Prefix in 2019. ACCEPT_KEYWORDS="~${ARCH}" diff --git a/profiles/features/split-usr/make.defaults b/profiles/features/split-usr/make.defaults index 9d42deee4999..3f95c0a0e32a 100644 --- a/profiles/features/split-usr/make.defaults +++ b/profiles/features/split-usr/make.defaults @@ -1,2 +1,2 @@ # Set an environment variable so we can easily test for the profile type -PROFILE_23_USRTYPE=split-usr +PROFILE_23_USRTYPE="split-usr" diff --git a/profiles/features/time64/make.defaults b/profiles/features/time64/make.defaults index 993dd21b6104..0edc40fa682e 100644 --- a/profiles/features/time64/make.defaults +++ b/profiles/features/time64/make.defaults @@ -1,3 +1,15 @@ # Copyright 2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Many profiles and stages override CFLAGS etc, and need then to eat their +# own dogfood. For those who don't... +__COMMON_FLAGS_TIME64="-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64" + +CFLAGS="${CFLAGS} ${__COMMON_FLAGS_TIME64} -Werror=implicit-function-declaration -Werror=implicit-int -Werror=incompatible-pointer-types -Werror=return-type -Werror=int-conversion" +CXXFLAGS="${CXXFLAGS} ${__COMMON_FLAGS_TIME64}" +FCFLAGS="${FCFLAGS} ${__COMMON_FLAGS_TIME64}" +FFLAGS="${FFLAGS} ${__COMMON_FLAGS_TIME64}" + +# We need to switch this explicitly on since it's explicitly disabled +# in profiles otherwise. +enable_year2038="yes" diff --git a/profiles/features/wd40/package.mask b/profiles/features/wd40/package.mask index 1179bb3a0abc..4a9c862847d3 100644 --- a/profiles/features/wd40/package.mask +++ b/profiles/features/wd40/package.mask @@ -1,6 +1,172 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Michał Górny <mgorny@gentoo.org> (2024-09-23) +# Requires dev-python/nh3. +dev-python/textile + +# matoro <matoro_gentoo@matoro.tk> (2024-08-10), #936643 +# Unmask old pre-rust librsvg. This has vulnerabilities, +# so it is masked by default and only unmasked on wd40 +-<gnome-base/librsvg-2.41 + +# matoro <matoro_gentoo@matoro.tk> (2024-07-27) +# Additional entries exposed by correcting musl, #936643 +x11-terms/alacritty +www-client/firefox +www-misc/buku +www-client/seamonkey +www-misc/urlwatch +www-client/tangram +www-apps/nextcloud-notify_push +sys-process/below +sys-process/bottom +sys-cluster/ceph +sys-block/dust +sys-apps/zram-generator +sys-apps/ripgrep +sys-apps/eza +sys-apps/lsd +sys-apps/fd +net-wireless/urh +net-proxy/mitmproxy +net-wireless/gr-ieee802154 +net-wireless/gr-rds +net-wireless/gr-scopy +net-wireless/gqrx-scanner +net-misc/electrum +net-misc/gns3-server +net-misc/geckodriver +net-im/synapse +net-irc/limnoria +net-irc/limnoria-plugins-progval +net-irc/limnoria-plugins-jlu5 +net-irc/limnoria-plugins-chantracker +net-analyzer/nagstamon +net-analyzer/python-gvm +net-analyzer/suricata +net-analyzer/gvm-tools +net-analyzer/gr-fosphor +net-analyzer/gvm +net-analyzer/snmpclitools +media-sound/beets +media-sound/gnome-sound-recorder +media-gfx/oxipng +media-gfx/curtail +mail-client/thunderbird +gui-libs/greetd +gnome-extra/gnome-shell-extensions +gui-apps/tuigreet +gnome-base/gnome-extra-apps +gui-apps/gtkgreet +gnome-extra/pch-session +gnome-extra/gnome-weather +gnome-extra/gnome-shell-frippery +gnome-extra/gnome-characters +gnome-extra/cjs +gnome-extra/cinnamon +gnome-extra/gnome-shell-extension-dash-to-panel +gnome-extra/gnome-shell-extension-weather-in-the-clock +gnome-extra/gnome-shell-extension-bluetooth-quick-connect +gnome-extra/gnome-shell-extension-gsconnect +gnome-extra/gnome-shell-extension-desktop-icons-ng +gnome-extra/gnome-shell-extension-appindicator +gnome-extra/gnome-shell-extension-control-blur-effect-on-lock-screen +gnome-extra/gnome-shell-extension-bing-wallpaper +gnome-extra/gnome-shell-extension-applications-overview-tooltip +gnome-extra/gnome-shell-extension-alphabetical-grid +gnome-extra/gnome-shell-extension-pop-shell +gnome-base/gnome +games-strategy/ja2-stracciatella +games-strategy/0ad +games-rpg/rpg-cli +games-board/gnome-chess +dev-util/pwntools +dev-util/rustup +dev-util/sccache +dev-util/bindgen +dev-util/cargo-license +dev-util/cargo-ebuild +dev-util/cargo-audit +dev-util/bingrep +dev-python/trimesh +dev-python/vpython +dev-python/treq +dev-python/twython +dev-python/txtorcon +dev-python/txredisapi +dev-python/sqlglot +dev-python/spake2 +dev-python/requests-ntlm +dev-python/python3-discogs-client +dev-python/python-axolotl +net-im/yowsup +dev-python/pyghmi +dev-python/omemo-dr +net-im/transwhat +dev-python/noiseprotocol +dev-python/mitmproxy_wireguard +dev-python/magic-wormhole +dev-python/magic-wormhole-transit-relay +dev-python/magic-wormhole-mailbox-server +dev-python/jwcrypto +dev-python/websockify +dev-python/jupyter +dev-python/jupyter-server-proxy +dev-python/jupyter-kernel-test +dev-python/jellyfish +www-apps/novnc +dev-python/jsonmerge +dev-python/jinja2_pluralize +dev-python/fido2 +dev-python/github3-py +dev-python/google-auth-oauthlib +dev-python/elasticsearch +dev-python/dns-lexicon +dev-python/dissononce +dev-python/consonance +dev-python/PyGithub +dev-python/adblock +dev-python/pysnmp +dev-python/pysnmp-mibs +dev-python/pysmi +dev-python/pysnmpcrypto +dev-java/icedtea-web +dev-debug/pwndbg +dev-db/mycli +sci-mathematics/mathlib-tools +dev-python/keep +dev-db/pgcli +dev-db/mysql-workbench +>=app-text/pelican-4.9.0 +dev-util/howdoi +app-text/pdfminer +app-text/restview +app-text/fblog +app-shells/nushell +app-misc/rpick +app-misc/skim +app-i18n/yaskkserv2 +app-emulation/cloud-init +app-forensics/yara-x +app-eselect/eselect-gnome-shell-extensions +app-emacs/rg +app-emacs/emacs-ipython-notebook +app-crypt/yubikey-manager +app-crypt/yubikey-manager-qt +app-crypt/sequoia-sq +app-crypt/sequoia-sqv +app-crypt/certbot-apache +app-crypt/nitrocli +app-crypt/certbot-dns-nsone +app-crypt/certbot-dns-dnsimple +app-containers/netavark +app-containers/aardvark-dns +app-backup/duplicity +app-backup/backintime +app-benchmarks/hyperfine +app-backup/duply + # Agostino Sarubbo <ago@gentoo.org> (2024-04-10) # Requires rust on armv4/armv4t/arm5te dev-util/bugbite-cli @@ -23,6 +189,7 @@ net-wireless/gnuradio net-wireless/gqrx net-wireless/gr-iqbal net-wireless/gr-osmosdr +app-emulation/diskimage-builder # Various packages requiring Rust. app-admin/ansible @@ -68,6 +235,7 @@ dev-python/jupyter-lsp dev-python/jupyter-server dev-python/jupyter-server-mathjax dev-python/jupyter-server-terminals +dev-python/jupyterlab-widgets dev-python/jupyterlab-server dev-python/jupyterlab dev-python/keyring @@ -150,6 +318,7 @@ dev-util/tree-sitter-cli dev-vcs/breezy >=dev-vcs/stgit-2 >=games-board/gnome-mahjongg-3.40.0 +>=games-puzzle/swell-foop-46 gnome-base/gdm >=gnome-base/gnome-core-apps-3.36.5 >=gnome-base/gnome-core-libs-3.36.5 @@ -157,6 +326,7 @@ gnome-base/gdm >=gnome-base/gnome-shell-3.38 >=gnome-base/librsvg-2.41 gnome-extra/gnome-browser-connector +>=gnome-extra/gnome-system-monitor-46 gnome-extra/gnome-tweaks gnome-extra/sushi >=media-gfx/libimagequant-4 @@ -174,7 +344,9 @@ net-p2p/deluge sci-geosciences/gnome-maps >=sys-apps/bat-0.18.1 >=sys-block/thin-provisioning-tools-1.0.6 +>=sys-process/glances-4.1.2.1 sys-fs/bcachefs-tools virtual/rust www-apps/radicale >=x11-themes/adwaita-icon-theme-3.36 +x11-themes/adwaita-icon-theme-legacy diff --git a/profiles/features/wd40/package.use.mask b/profiles/features/wd40/package.use.mask index 4d70f8b95974..888aadab1d16 100644 --- a/profiles/features/wd40/package.use.mask +++ b/profiles/features/wd40/package.use.mask @@ -1,6 +1,45 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Petr Vaněk <arkamar@gentoo.org> (2024-09-01) +# Requires dev-python/cryptography +app-crypt/osslsigncode test + +# matoro <matoro_gentoo@matoro.tk> (2024-07-27) +# Additional entries exposed by correcting musl, #936643 +x11-wm/xpra crypt oauth +>=x11-wm/xpra-6.0.1-r1 test +x11-misc/gpaste introspection gnome +www-servers/servefile ssl +sys-block/tgt rbd +sci-physics/root jupyter +sci-libs/branca doc test +net-vpn/eduvpn-client doc +net-misc/httpie test +net-dns/dnsdist doh3 quic +net-analyzer/linkchecker test +x11-themes/arc-theme cinnamon +dev-python/xdoctest test +dev-python/stripe test +dev-python/respx test +dev-python/python-swiftclient test +dev-python/pypdf test +dev-python/oct2py test +dev-python/octave-kernel test +dev-python/markups test +dev-python/keyrings-alt test +sci-mathematics/cadabra jupyter +sci-mathematics/yacas jupyter +dev-python/metakernel test +dev-python/elastic-transport test +dev-python/genson test +dev-python/construct test +dev-db/barman test +app-emulation/libvirt rbd virtiofsd +app-misc/gramps test +app-forensics/volatility3 jsonschema +app-emulation/libguestfs test + # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-19) # Requires dev-python/cryptography sys-kernel/installkernel efistub @@ -87,6 +126,7 @@ dev-libs/tree-sitter-c-sharp test dev-libs/tree-sitter-cpp test dev-libs/tree-sitter-css test dev-libs/tree-sitter-embedded-template test +dev-libs/tree-sitter-gleam test dev-libs/tree-sitter-go test dev-libs/tree-sitter-haskell test dev-libs/tree-sitter-html test @@ -95,15 +135,22 @@ dev-libs/tree-sitter-javascript test dev-libs/tree-sitter-jsdoc test dev-libs/tree-sitter-json test dev-libs/tree-sitter-julia test +dev-libs/tree-sitter-lua test +dev-libs/tree-sitter-markdown test +dev-libs/tree-sitter-markdown-inline test dev-libs/tree-sitter-ocaml test dev-libs/tree-sitter-php test dev-libs/tree-sitter-python test dev-libs/tree-sitter-ql test +dev-libs/tree-sitter-query test dev-libs/tree-sitter-ruby test dev-libs/tree-sitter-rust test dev-libs/tree-sitter-scala test dev-libs/tree-sitter-tsq test +dev-libs/tree-sitter-tsx test dev-libs/tree-sitter-typescript test +dev-libs/tree-sitter-vim test +dev-libs/tree-sitter-vimdoc test # Sam James <sam@gentoo.org> (2022-11-19) # GNOME packages pulling in e.g. gjs which then needs Rust. @@ -119,7 +166,6 @@ net-vpn/networkmanager-vpnc gtk # Michał Górny <mgorny@gentoo.org> (2022-07-29) # More packages requiring dev-python/cryptography or its revdeps. app-admin/salt keyring neutron -dev-python/dask test dev-python/docker test dev-python/google-api-python-client test dev-python/httpx-socks test @@ -155,6 +201,7 @@ dev-python/anyio test dev-python/httpcore test dev-python/httpx test dev-python/aiohttp-socks test +dev-python/truststore test # WANG Xuerui <xen0n@gentoo.org> (2022-05-13) # dev-lang/rust is not available on ${arch} yet. @@ -188,7 +235,9 @@ dev-vcs/mercurial rust # Joonas Niilola <juippis@gentoo.org> (2020-10-02) # Sam James <sam@gentoo.org> (2021-03-11) +# Michael Orlitzky <mjo@gentoo.org> (2024-07-09) # Dependency only keyworded on specific ${arch} profiles. +>=dev-lang/php-8.3.9 avif dev-libs/efl avif kde-frameworks/kimageformats avif media-libs/gd avif diff --git a/profiles/features/wd40/use.mask b/profiles/features/wd40/use.mask index a265b328acb2..cd95248c0a62 100644 --- a/profiles/features/wd40/use.mask +++ b/profiles/features/wd40/use.mask @@ -1,6 +1,10 @@ -# Copyright 1999-2022 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# matoro <matoro_gentoo@matoro.tk> (2024-07-27) +# media-video/rav1e requires Rust. +rav1e + rust # Michał Górny <mgorny@gentoo.org> (2022-10-09) diff --git a/profiles/license_groups b/profiles/license_groups index 4922fdefd324..364b7e8b49bd 100644 --- a/profiles/license_groups +++ b/profiles/license_groups @@ -15,7 +15,7 @@ # https://www.gnu.org/licenses/license-list.html # GPL or LGPL with various exceptions are also included here, because # they are more permissive than the licenses they are based on. -GPL-COMPATIBLE AGPL-3 AGPL-3+ Apache-2.0 Apache-2.0-with-LLVM-exceptions Artistic-2 Boost-1.0 BSD BSD-2 CC0-1.0 CeCILL-2 Clarified-Artistic Clear-BSD ECL-2.0 FSFAP FTL gcc-runtime-library-exception-3.1 GPL-1 GPL-1+ GPL-2 GPL-2+ GPL-2+-with-openssl-exception GPL-2+-with-eCos-exception-2 GPL-2-with-classpath-exception GPL-2-with-exceptions GPL-2-with-font-exception GPL-2-with-linking-exception GPL-2-with-MySQL-FLOSS-exception GPL-2+-with-Pyinstaller-Bootloader-exception GPL-3 GPL-3+ GPL-3+-with-autoconf-exception GPL-3+-with-font-exception GPL-3-with-font-exception GPL-3-with-openssl-exception HPND IJG ISC LGPL-2 LGPL-2+ LGPL-2-with-linking-exception LGPL-2.1 LGPL-2.1+ LGPL-2.1-with-linking-exception LGPL-3 LGPL-3+ LGPL-3-with-linking-exception libgcc libstdc++ metapackage MIT MPL-2.0 Nokia-Qt-LGPL-Exception-1.1 OPENLDAP PSF-2 PSF-2.4 public-domain PYTHON qwt Ruby Ruby-BSD SGI-B-2.0 Sleepycat tanuki-community Transmission-OpenSSL-exception Unicode-DFS-2016 Unlicense UoI-NCSA UPL-1.0 UPX-exception vim W3C WTFPL-2 wxWinLL-3.1 ZLIB ZPL +GPL-COMPATIBLE AGPL-3 AGPL-3+ Apache-2.0 Apache-2.0-with-LLVM-exceptions Artistic-2 Boost-1.0 BSD BSD-2 CC0-1.0 CeCILL-2 Clarified-Artistic Clear-BSD ECL-2.0 FSFAP FTL gcc-runtime-library-exception-3.1 GPL-1 GPL-1+ GPL-2 GPL-2+ GPL-2+-with-openssl-exception GPL-2+-with-eCos-exception-2 GPL-2-with-classpath-exception GPL-2-with-font-exception GPL-2-with-linking-exception GPL-2-with-MySQL-FLOSS-exception GPL-2+-with-Pyinstaller-Bootloader-exception GPL-3 GPL-3+ GPL-3+-with-autoconf-exception GPL-3+-with-font-exception GPL-3+-with-openssl-exception GPL-3-with-font-exception GPL-3-with-openssl-exception HPND IJG ISC LGPL-2 LGPL-2+ LGPL-2-with-linking-exception LGPL-2.1 LGPL-2.1+ LGPL-2.1-with-linking-exception LGPL-3 LGPL-3+ LGPL-3-with-linking-exception libgcc libstdc++ metapackage MIT MPL-2.0 Nokia-Qt-LGPL-Exception-1.1 OPENLDAP PSF-2 PSF-2.4 public-domain PYTHON qwt Ruby Ruby-BSD SGI-B-2.0 Sleepycat tanuki-community Transmission-OpenSSL-exception Unicode-DFS-2016 Unlicense UoI-NCSA UPL-1.0 UPX-exception vim W3C WTFPL-2 wxWinLL-3.1 ZLIB ZPL # Free software licenses approved by the FSF FSF-APPROVED @GPL-COMPATIBLE AFL-2.1 AFL-3.0 Apache-1.0 Apache-1.1 APSL-2 BSD-4 CDDL CeCILL-B CeCILL-C CNRI CPAL-1.0 CPL-1.0 EPL-1.0 EPL-2.0 EUPL-1.1 EUPL-1.2 FraunhoferFDK gnuplot IBM LPL-1.02 LPPL-1.2 LPPL-1.3a MPL-1.0 MPL-1.1 Ms-PL Ms-RL NPL-1.1 openssl OSL-1.1 OSL-2.0 OSL-2.1 PHP-3.01 QPL-1.0 Zend-2.0 @@ -25,7 +25,7 @@ FSF-APPROVED @GPL-COMPATIBLE AFL-2.1 AFL-3.0 Apache-1.0 Apache-1.1 APSL-2 BSD-4 # Note that the FSF lists these as nonfree: Artistic NOSA Watcom-1.0 # We exclude NOSA and Watcom-1.0, but we keep Artistic because Debian # considers it DFSG-free. -OSI-APPROVED-FREE 0BSD AFL-3.0 AGPL-3 AGPL-3+ Apache-1.1 Apache-2.0 APL-1.0 APSL-2 Artistic Artistic-2 Boost-1.0 BSD BSD-2 CDDL CNRI CPAL-1.0 CPL-1.0 ECL-2.0 EPL-1.0 EPL-2.0 EUPL-1.1 EUPL-1.2 GPL-1 GPL-1+ GPL-2 GPL-2+ GPL-3 GPL-3+ HPND IBM IPAfont ISC LGPL-2 LGPL-2+ LGPL-2.1 LGPL-2.1+ LGPL-3 LGPL-3+ LPL-1.02 LPPL-1.3c MirOS MIT MIT-0 MPL-1.0 MPL-1.1 MPL-2.0 Ms-PL Ms-RL nethack OFL-1.1 OSL-2.1 PHP-3 PHP-3.01 POSTGRESQL PSF-2 QPL-1.0 Sleepycat Unicode-3.0 Unicode-DFS-2016 Unlicense UPL-1.0 UoI-NCSA W3C wxWinLL-3 ZLIB ZPL +OSI-APPROVED-FREE 0BSD AFL-3.0 AGPL-3 AGPL-3+ Apache-1.1 Apache-2.0 APL-1.0 APSL-2 Artistic Artistic-2 BlueOak-1.0.0 Boost-1.0 BSD BSD-2 CDDL CNRI CPAL-1.0 CPL-1.0 ECL-2.0 EPL-1.0 EPL-2.0 EUPL-1.1 EUPL-1.2 GPL-1 GPL-1+ GPL-2 GPL-2+ GPL-3 GPL-3+ HPND IBM IPAfont ISC LBNLBSD LGPL-2 LGPL-2+ LGPL-2.1 LGPL-2.1+ LGPL-3 LGPL-3+ LPL-1.02 LPPL-1.3c MirOS MIT MIT-0 MPL-1.0 MPL-1.1 MPL-2.0 Ms-PL Ms-RL nethack OFL-1.1 OSL-2.1 PHP-3 PHP-3.01 POSTGRESQL PSF-2 QPL-1.0 Sleepycat Unicode-3.0 Unicode-DFS-2016 Unlicense UPL-1.0 UoI-NCSA W3C wxWinLL-3 ZLIB ZPL # Misc licenses that are probably free software, i.e. follow the # Free Software Definition at https://www.gnu.org/philosophy/free-sw.html @@ -43,7 +43,7 @@ FREE-SOFTWARE @FSF-APPROVED @OSI-APPROVED-FREE @MISC-FREE # FSF-approved licenses for "free documentation" and "works of # practical use besides software and documentation" (including fonts) -FSF-APPROVED-OTHER Arphic CC-BY-2.0 CC-BY-2.5 CC-BY-3.0 CC-BY-4.0 CC-BY-SA-2.0 CC-BY-SA-2.5 CC-BY-SA-3.0 CC-BY-SA-4.0 FDL-1.1 FDL-1.1+ FDL-1.2 FDL-1.2+ FDL-1.3 FDL-1.3+ Free-Art-1.2 Free-Art-1.3 GPL-1 GPL-1+ GPL-2 GPL-2+ GPL-3 GPL-3+ IPAfont OFL OFL-1.0 OFL-1.1 OPL +FSF-APPROVED-OTHER Arphic CC-BY-2.0 CC-BY-2.5 CC-BY-3.0 CC-BY-4.0 CC-BY-SA-2.0 CC-BY-SA-2.5 CC-BY-SA-3.0 CC-BY-SA-4.0 FDL-1.1 FDL-1.1+ FDL-1.2 FDL-1.2+ FDL-1.3 FDL-1.3+ Free-Art-1.2 Free-Art-1.3 GPL-1 GPL-1+ GPL-2 GPL-2+ GPL-3 GPL-3+ IPAfont OFL-1.0 OFL-1.1 OPL # Misc licenses for free documents and other works (including fonts) # that follow the definition at https://freedomdefined.org/ but are NOT @@ -81,10 +81,10 @@ OSI-APPROVED @OSI-APPROVED-FREE @OSI-APPROVED-NONFREE # License agreements that try to take away your rights. These are more # restrictive than "all-rights-reserved" or require explicit approval. -EULA 2dboy-EULA AMD-GPU-PRO-EULA android AnyDesk-TOS Aseprite-EULA baudline bestcrypt CAPYBARA-EULA Coherent-Graphics Dell-EULA ETQW f.lux FAH-EULA-2014 Flightradar24 Gameplay-Group-EULA geekbench genymotion GIMPS GOG-EULA google-chrome Intel-SDP Introversion JoyPixels LOKI-EULA MakeMKV-EULA Microsemi microsoft-edge Microsoft-vscode Mojang MTA-0.5 NVIDIA-CUDA NVIDIA-SDK Ookla OPERA-2018 PAPERS-PLEASE PassMark-EULA PICO-8 Primate-Plunge PUEL-11 Q3AEULA-20000111 QUAKE4 RAR sfpg SPS Steam supermicro Synology teamspeak3 teamspeak5 TeamViewer THINKTANKS TIK ubiquiti ut2003 ut2003-demo Vivaldi worklog-assistant WPS-EULA zi-labone +EULA 2dboy-EULA AMD-GPU-PRO-EULA android AnyDesk-TOS Aseprite-EULA baudline bestcrypt CAPYBARA-EULA Coherent-Graphics Dell-EULA ETQW f.lux FAH-EULA-2014 Flightradar24 Gameplay-Group-EULA geekbench genymotion GIMPS GOG-EULA google-chrome Intel-SDP Introversion JoyPixels LOKI-EULA MakeMKV-EULA Microsemi microsoft-azurevpnclient microsoft-edge Microsoft-vscode MikroTik Mojang MTA-0.5 NVIDIA-CUDA NVIDIA-SDK Ookla OPERA-2018 PAPERS-PLEASE PassMark-EULA PICO-8 Primate-Plunge PUEL-11 PUEL-12 Q3AEULA-20000111 QUAKE4 RAR sfpg SPS Steam supermicro Synology teamspeak3 teamspeak5 TeamViewer THINKTANKS TIK ubiquiti ut2003 ut2003-demo Vivaldi worklog-assistant WPS-EULA zi-labone # Deprecated license labels, used by repoman and pkgcheck -DEPRECATED OFL +#DEPRECATED (currently none) # Local Variables: # mode: conf-space diff --git a/profiles/package.deprecated b/profiles/package.deprecated index ef557ec07d2b..49933e11aad2 100644 --- a/profiles/package.deprecated +++ b/profiles/package.deprecated @@ -17,11 +17,16 @@ #--- END OF EXAMPLES --- -# Volkmar W. Pogatzki <gentoo@pogatzki.net> (2024-03-10) -# ant-core should no longer be ussed as of version 1.10.14 or higher. -# It is now completely integrated in dev-java/ant and will be removed after a -# grace period. -dev-java/ant-core +# Michał Górny <mgorny@gentoo.org> (2024-07-23) +# Abandoned and broken with pytest-8. Superseded +# by dev-python/pytest-lazy-fixtures (plural), which requires small +# changes in code. +dev-python/pytest-lazy-fixture + +# Michał Górny <mgorny@gentoo.org> (2024-06-15) +# Stop-gap compatibility package. Upstreams really need to move away +# from the removed cgi module rather than rely on this. +dev-python/legacy-cgi # Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-09) # Unmaintained upstream. Does not build with llvm-16 and up, nor with @@ -53,15 +58,6 @@ net-p2p/bitcoind # Bug 915779 dev-qt/qtscript:5 -# Michał Górny <mgorny@gentoo.org> (2023-06-18) -# Superseded by dev-python/pdm-backend. The migration guide is at: -# https://pdm-backend.fming.dev/migration/ -dev-python/pdm-pep517 - -# Sam James <sam@gentoo.org> (2023-06-18) -# Merged into dev-perl/Type-Tiny. Please depend on that instead. -dev-perl/Type-Tie - # Andreas Sturmlechner <asturm@gentoo.org> (2023-06-10) # Obsolete transitional meta package. Switch to media-libs/libpulse # which ensures a sound server is installed via PDEPEND. diff --git a/profiles/package.mask b/profiles/package.mask index 2a4c9000e858..fc42b92df2ad 100644 --- a/profiles/package.mask +++ b/profiles/package.mask @@ -33,342 +33,324 @@ #--- END OF EXAMPLES --- -# Andreas Sturmlechner <asturm@gentoo.org> (2024-05-20) -# Short-lived side-by-side release, now unnecessary as it moved back to -# kde-apps/kio-extras:5. Removal on 2024-06-04. -kde-apps/kio-extras-kf5 - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-18) -# EAPI=6, no reverse dependencies, dead homepage, has issues -# with modern C, maintainer needed. -# Removal on 2024-06-17. Bugs #932168, #906348, #895028, #870640. -dev-lang/srf - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-18) -# EAPI6. Fails to compile with go versions in tree. Upstream is archived. -# Uses deprecated go eclasses. Maintainer needed, no rev deps. -# Removal on 2024-06-17. Bugs #932166, #844604, #679832. -app-emulation/hyperd - -# Michał Górny <mgorny@gentoo.org> (2024-05-18) -# Another abandoned project in the middle of a line of forks. -# Broken with Python 3.12, with pytest 8 and with numpy 2. Last -# upstream activity in September 2023, but bugs remained unanswered -# before that. -# Removal on 2024-06-17. Bug #929433. -dev-python/aesara - -# Michał Górny <mgorny@gentoo.org> (2024-05-18) -# Superseded by dev-python/pdm-backend. No revdeps left. -# Removal on 2024-06-17. Bug #932160. -dev-python/pdm-pep517 - -# Michał Górny <mgorny@gentoo.org> (2024-05-17) -# Superseded by dev-python/pathable. No revdeps. -# Removal on 2024-06-16. Bug #932103. -dev-python/dictpath - -# Michał Górny <mgorny@gentoo.org> (2024-05-17) -# Unmaintained. Last activity in 2020. Redundant to stdlib. -# No revdeps. -# Removal on 2024-06-16. Bug #932096. -dev-python/cached-property - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-17) -# EAPI=6, no maintainer, fails to compile. -# Removal on 2024-06-16. Bugs #932097, #542244, #742965. -x11-plugins/pidgintex - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-17) -# EAPI=6, no maintainer, fails to compile. -# Removal on 2024-06-16. Bugs #932095, #768072, #777747. -app-forensics/air - -# Sam James <sam@gentoo.org> (2024-05-17) -# Needs adaptation to new build system (bug #932092). -=net-libs/libupnpp-0.26.4 - -# Michał Górny <mgorny@gentoo.org> (2024-05-17) -# A Python < 3.3 backport of shutil.which(). No revdeps left. -# Removal on 2024-06-16. Bug #932088. -dev-python/whichcraft - -# Eli Schwartz <eschwartz93@gmail.com> (2024-05-17) -# Last updated in 2007, has no reverse dependencies, is unmaintained upstream -# (in 2010 a version 4 alpha was released using cmake, the project has seen no -# other activity upstream). Fails to build with dash, lto. -# Bug #862669, #890423. -# Removal on 2024-06-16. -sci-libs/beagle - -# Andreas Sturmlechner <asturm@gentoo.org> (2024-05-14) -# Breaks build of revdeps. Bugs #931916, #931917 -~app-text/poppler-24.05.0 - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-13) -# EAPI=6, fails to compile, archived upstream, uses deprecated go eclasses. -# Removal: 2024-06-12. Bugs #931879, #734186. -app-emulation/docker-machine-kvm - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-13) -# EAPI=6, fails to compile, dead upstream, maintainer-needed. -# Removal: 2024-06-12. Bugs #931874, #878771. -media-gfx/raw-thumbnailer - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-13) -# EAPI=6, fails to compile, library with no reverse dependencies. -# Removal: 2024-06-12. Bug #931861. -sci-libs/cifparse-obj - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-13) -# EAPI=6, fails to compile, no reverse dependencies. -# Removal: 2024-06-12. Bugs #931860, #891895. -sci-libs/libghemical - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-11) -# EAPI=6, uses deprecated go eclass, archived upstream. Update to -# usage of go-module.eclass isn't simple. -# Removal: 2024-06-10. Bugs #931745, #844598. -app-emulation/docker-machine - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-11) -# EAPI=6, library only without any reverse dependencies, uses -# deprecated go eclasses. -# Removal: 2024-06-10. Bug #931725. -dev-go/fuzzy -dev-go/go-bindata-assetfs -dev-go/godebug-pretty -dev-go/sanitized-anchor-name - -# Eli Schwartz <eschwartz93@gmail.com> (2024-05-08) -# Fails to configure with GCC 14, fails to install with older -# gcc, unmaintained, upstream website vanished. -# Bug #731180, #861461, #888577, #889930. -# Removal on 2024-06-08. -net-irc/ninja - -# Sam James <sam@gentoo.org> (2024-05-06) -# Long-deprecated upstream, replaced by (unpackaged) Twitter::API. -# Twitter's API has changed at least once since the last release of Net::Twitter. -# Removal on 2024-06-05. Bug #931295. -dev-perl/Net-Twitter - -# Sam James <sam@gentoo.org> (2024-05-06) -# Incompatible with latest last.fm APIs, hence useless. -# Removal on 2024-06-05. Bug #928115. -media-libs/lastfmlib - -# Michał Górny <mgorny@gentoo.org> (2024-05-05) -# A library last bumped in 2010. Homepage gone. No revdeps. -# Removal on 2024-06-04. Bug #909527. -dev-games/poker-eval - -# Michał Górny <mgorny@gentoo.org> (2024-05-05) -# A library last bumped in 2004. Homepage gone. Carries patches -# and hacks already. No reverse dependencies. -# Removal on 2024-06-04. Bug #909581. -dev-games/hawknl - -# Michał Górny <mgorny@gentoo.org> (2024-05-05) -# An unmaintained fork of an unmaintained DNS server. All successive -# homepages are gone. Last commit in 2014. Already carries a lot -# of patches and hacks. -# Removal on 2024-06-04. Bug #928942. -net-dns/mydns - -# Michał Górny <mgorny@gentoo.org> (2024-05-04) -# A really bad quality package with a never-ending stream of unclear -# test failures, and blocked keywording and stabilization bugs. -# The bump to the most recent release is blocked by a ton of test -# regressions. No reverse dependencies left. -# Removal on 2024-06-03. Bug #931151. -dev-python/dask -dev-python/dask-expr - -# Andreas K. Hüttel <dilfridge@gentoo.org> (2024-05-01) -# Outdated package, now part of dev-perl/Type-Tiny. Removal in 30 days. -dev-perl/Type-Tie - -# Michał Górny <mgorny@gentoo.org> (2024-05-01) -# Effectively unmaintained. EAPI 6. Keyworded for PowerPC only. -# Might not work anymore (when I run it, it hangs input to X11 entirely). -# Removal on 2024-05-31. Bug #930195. -sys-apps/mouseemu - -# Michał Górny <mgorny@gentoo.org> (2024-05-01) -# Unmaintained in Gentoo. Multiple releases behind upstream. No tests. -# No Python 3.12. No (unconditional) reverse dependencies. -# Removal on 2024-05-31. Bug #904945. -dev-python/grpcio -dev-python/grpcio-testing -dev-python/grpcio-tools - -# Jason Zaman <perfinion@gentoo.org> (2024-04-28) -# TensorFlow was removed from the tree in feb, Keras applications and -# preprocessing no longer have any revdeps in the tree. For ML, the -# recommendation is to install from pip in a venv. -# Removal in 30 days. Bug #930830 -sci-libs/keras-applications -sci-libs/keras-preprocessing +# Sebastian Pipping <sping@gentoo.org> (2024-10-03) +# Masked for removal in 30 days. Last release in 2021, +# last commit two years ago, has open bugs, .. (bug #940725). +# Also removing its two dependencies that have no other +# reverse dependencies in Gentoo or known use outside of Lurch. +net-libs/libaxc +net-libs/libomemo +x11-plugins/lurch + +# Sam James <sam@gentoo.org> (2024-09-30) +# GCC 10 and older no longer receive upstream support or fixes for +# bugs. Please switch to a newer GCC version using gcc-config. +# The lowest supported version of GCC is GCC 11. +<sys-devel/gcc-11 +<sys-devel/kgcc64-11 + +# Michał Górny <mgorny@gentoo.org> (2024-09-29) +# This package has not been updated since Python 3.11.2. It bundles +# part of Python stdlib that's most likely vulnerable by now, as well +# as some third-party packages. And it really needs a dedicated +# maintainer. +# Removal on 2024-10-29. Bug #910612. +dev-python/brython + +# Volkmar W. Pogatzki <gentoo@pogatzki.net> (2024-09-28) +# Nothing depends on it. Removal on 2024-10-28. +dev-java/ant-core + +# Michał Górny <mgorny@gentoo.org> (2024-09-25) +# Fails on deprecated config options from eclass, except that if we +# update them, then all existing packages break. +# https://github.com/scikit-build/scikit-build-core/issues/912 +=dev-python/rapidfuzz-3.10.0 + +# Eli Schwartz <eschwartz@gentoo.org> (2024-09-22) +# Unmaintained, abandoned upstream, does not compile with GCC 14. +# Removal on 2024-10-22. Bug #874732. +dev-util/biew + +# Robin H. Johnson <robbat2@gentoo.org> (2024-09-22) +# Upstream testing release; fails some tests as well here +# Beware that if you upgrade to it, you may need to reset your keyrings. +>=app-crypt/gnupg-2.5 + +# Michał Górny <mgorny@gentoo.org> (2024-09-21) +# Discontinued upstream. Since 7.3.17, only 2.7 and 3.10 are released. +# Vulnerable. +# Removal on 2024-10-21. Bug #939951. +dev-python/pypy3_9 +dev-python/pypy3_9-exe +dev-python/pypy3_9-exe-bin + +# Michał Górny <mgorny@gentoo.org> (2024-09-21) +# Unmaintained. Broken with >=dev-python/pytest-8. +# Replaced by dev-python/pytest-lazy-fixtures. No revdeps left. +# Removal on 2024-10-21. Bug #939420. +dev-python/pytest-lazy-fixture + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-20) +# No more revdeps after app-accessibility/kontrast:5 cleanup. +# Removal on 2024-10-20. +dev-db/futuresql5 + +# Eli Schwartz <eschwartz@gentoo.org> (2024-09-19) +# Breaks parallel builds with fatal compiler errors. +# Bug #939798, #939875. +=dev-python/ensurepip-setuptools-75.1.0 +=dev-python/setuptools-75.1.0 + +# Hans de Graaff <graaff@gentoo.org> (2024-09-14) +# Obsolete slots that were used for older cucumber version but that no +# longer have reverse dependencies. Removal on 2024-10-14. +dev-util/cucumber-compatibility-kit:10 +dev-util/cucumber-core:12 +dev-util/cucumber-gherkin:22 + +# Hans de Graaff <graaff@gentoo.org> (2024-09-14) +# Old slots that are not compatible with ruby32. Use the newer slots +# instead. Removal on 2024-10-14. +dev-ruby/hiera-eyaml:3 +dev-util/aruba:0 + +# Arthur Zamarin <arthurzam@gentoo.org> (2024-09-10) +# ia64 only package. Since we drop ia64, we can remove this package. +# Removal on 2024-10-10. Bug #939298. +sys-apps/salinfo + +# Ulrich Müller <ulm@gentoo.org> (2024-09-12) +# Pretest versions, masked for testing. +<app-editors/emacs-30.0.9999:30-vcs + +# Eli Schwartz <eschwartz@gentoo.org> (2024-09-09) +# Upstream has dropped this package since MATE 1.28. +# Removal on 2024-10-09. Bug #932568. +mate-extra/mate-netbook + +# Eli Schwartz <eschwartz@gentoo.org> (2024-09-09) +# Fails to build with modern C. Unmaintained for 20 years. +# Removal on 2024-10-09. Bug #877105, #927389. +sci-chemistry/mopac7 + +# Sam James <sam@gentoo.org> (2024-09-10) +# Breaks libstdc++ with a casing issue: https://gcc.gnu.org/PR116657 +=sys-libs/timezone-data-2024b + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-09) +# No revdeps for years, KF5-based. Removal on 2024-10-09. +net-libs/libmediawiki + +# Alfredo Tupone <tupone@gentoo.org> (2024-06-09) +# These packages are no more needed. Use dev-ml/dune-private-libs +# that include these +# remove on 2024-10-08. Bug #939339 +dev-ml/stdune +dev-ml/ordering +dev-ml/dyn + +# Michał Górny <mgorny@gentoo.org> (2024-09-08) +# Does not build anymore. No upstream activity since 2021. +# Removal on 2024-10-08. Bug #932532. +sci-physics/qmeq + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-07) +# These packages are EOL in Plasma 6. +# Removal on 2024-10-07. +<kde-plasma/khotkeys-5.27.50:5 +<kde-plasma/libkworkspace-5.27.50:5 +<kde-plasma/xembed-sni-proxy-5.27.50:5 + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-04) +# Unmaintained upstream, latest media-libs/phonon release incompatible. +# Removal on 2024-10-04. +media-libs/phonon-gstreamer + +# Andreas Sturmlechner <asturm@gentoo.org> (2024-09-04) +# KF5 Porting aids (from KDElibs4). No more, or PMASKED revdeps. +# Removal on 2024-10-04. Bug #755956 +kde-frameworks/khtml +kde-frameworks/kjs +kde-frameworks/kross + +# Fabian Groffen <grobian@gentoo.org> (2024-09-02) +# exim_tinydb utility crashes due to invalid free() (used in startup script) +=mail-mta/exim-4.98 + +# Florian Schmaus <flow@gentoo.org> (2024-08-23) +# Has a serious bug that causes synced directories to end up world read- +# and writeable. See https://github.com/nextcloud/desktop/issues/6863 +>=net-misc/nextcloud-client-3.13.1 + +# Ionen Wolkens <ionen@gentoo.org> (2024-08-11) +# >=1.1.14 enables usage of explicit sync (with >=nvidia-drivers-560 +# and compositors that supports like kwin-6), which currently seems +# to be causing too many problems ranging from application crashes +# and potential VRAM leaking (even with the fixes in 1.1.15) and may +# be better left masked for the time being. It can hwoever solve +# flicking/stutter issues on some setups so users may want to unmask +# if heavily affected (bug #937773). +>=gui-libs/egl-wayland-1.1.14 + +# Pacho Ramos <pacho@gentoo.org> (2024-08-09) +# Mask until we find out a way to deal better with the upstream +# introduced circular dep, bug #937616 +>=dev-libs/glib-2.80 +>=dev-util/glib-utils-2.80 +>=dev-util/gdbus-codegen-2.80 +>=gnome-base/gnome-shell-46 +>=gnome-extra/gnome-shell-extensions-46 +>=gnome-base/nautilus-46 +>=dev-libs/gobject-introspection-1.80 +>=dev-libs/gobject-introspection-common-1.80 +>=x11-terms/ptyxis-46 + +# Eli Schwartz <eschwartz@gentoo.org> (2024-07-29) +# Bad version can result in failing builds. Please upgrade to 72.1.0. +=dev-python/ensurepip-setuptools-72.0.0 +=dev-python/setuptools-72.0.0 + +# Alfred Wingate <parona@protonmail.com> (2024-07-24) +# Includes change that breaks firewalld notably. +# +# https://git.netfilter.org/nftables/commit/?id=93560d0117639c8685fc287128ab06dec9950fbd +# https://github.com/firewalld/firewalld/issues/1366 +# https://lore.kernel.org/netfilter-devel/Zp7FqL_YK3p_dQ8B@egarver-mac/ +=net-firewall/nftables-1.1.0 + +# Leonardo Hernández Hernández <leohdz172@proton.me> (2024-07-07) +# New major ffmpeg version. Tracker bug #928905. +>=media-video/ffmpeg-7.0 + +# Joonas Niilola <juippis@gentoo.org> (2024-07-04) +# libxml2-2.13.1 removed "deprecated" symbols that other (older) +# packages depend upon. It can be mitigated with a --with-legacy +# configure option, but it's still not a perfect fix. Bug #935452 +# to track and work on tree-wide support. Masking the exact version +# so we can revbump the package with a fix. +=dev-libs/libxml2-2.13.1 +=dev-libs/libxslt-1.1.41 + +# Sam James <sam@gentoo.org> (2024-06-25) +# Subvolume printing is broken: https://github.com/kdave/btrfs-progs/issues/829 +=sys-fs/btrfs-progs-6.9.1 + +# Sam James <sam@gentoo.org> (2024-06-25) +# The symbol versioning "fix" breaks anything built with 3.0.0. +=dev-libs/libassuan-3.0.1 + +# Cédric Krier <cedk@gentoo.org> (2023-06-15) +# critical regression with potential data loss: +# https://lists.mercurial-scm.org/pipermail/mercurial-devel/2024-June/297954.html +# Bug #934138 +~dev-vcs/mercurial-6.7 +~dev-vcs/mercurial-6.7.1 +~dev-vcs/mercurial-6.7.2 +~dev-vcs/mercurial-6.7.3 + +# Alfredo Tupone <tupone@gentoo.org> (2024-06-09) +# Not ready for testing +>=dev-lang/ocaml-5 +dev-ml/sexplib0:0/0.17 +dev-ml/ocaml_intrinsics:0/0.17 +dev-ml/ocaml_intrinsics_kernel:0/0.17 +dev-ml/base:0/0.17 +dev-ml/fieldslib:0/0.17 +dev-ml/stdio:0/0.17 +>=dev-ml/ocaml-compiler-libs-0.17 +>=dev-ml/ppxlib-0.32.1 +dev-ml/ppx_cold:0/0.17 +dev-ml/ppxlib_jane +dev-ml/ppx_compare:0/0.17 +dev-ml/ppx_enumerate:0/0.17 +dev-ml/ppx_globalize:0/0.17 +dev-ml/ppx_sexp_conv:0/0.17 +dev-ml/ppx_hash:0/0.17 +dev-ml/ppx_base:0/0.17 +dev-ml/ppx_fields_conv:0/0.17 +dev-ml/ppx_fixed_literal:0/0.17 +dev-ml/ppx_here:0/0.17 +dev-ml/ppx_let:0/0.17 +dev-ml/ppx_sexp_message:0/0.17 +dev-ml/ppx_sexp_value:0/0.17 +dev-ml/ppx_assert:0/0.17 +dev-ml/jane-street-headers:0/0.17 +dev-ml/ppx_optcomp:0/0.17 +dev-ml/jst-config:0/0.17 +dev-ml/time_now:0/0.17 +dev-ml/ppx_inline_test:0/0.17 +dev-ml/ppx_bench:0/0.17 +dev-ml/splittable_random:0/0.17 +dev-ml/base_quickcheck:0/0.17 +dev-ml/ppx_stable:0/0.17 +dev-ml/ppx_string:0/0.17 +dev-ml/ppx_expect:0/0.17 +dev-ml/parsexp:0/0.17 +dev-ml/sexplib:0/0.17 +dev-ml/variantslib:0/0.17 +dev-ml/ppx_variants_conv:0/0.17 +dev-ml/ppx_log:0/0.17 +dev-ml/ppx_ignore_instrumentation:0/0.17 +dev-ml/typerep:0/0.17 +dev-ml/ppx_typerep_conv:0/0.17 +dev-ml/ppx_tydi:0/0.17 +dev-ml/capitalization:0/0.17 +dev-ml/ppx_string_conv:0/0.17 +dev-ml/ppx_stable_witness:0/0.17 +dev-ml/ppx_pipebang:0/0.17 +dev-ml/ppx_optional:0/0.17 +dev-ml/ppx_module_timer:0/0.17 +dev-ml/ppx_disable_unused_warnings:0/0.17 +dev-ml/ppx_custom_printf:0/0.17 +dev-ml/bin_prot:0/0.17 +dev-ml/ppx_bin_prot:0/0.17 +dev-ml/ppx_jane:0/0.17 +dev-ml/gel:0/0.17 +dev-ml/ppx_diff:0/0.17 +dev-ml/int_repr:0/0.17 +dev-ml/base_bigstring:0/0.17 +dev-ml/core:0/0.17 +dev-ml/uopt:0/0.17 +dev-ml/core_kernel:0/0.17 +dev-ml/timezone:0/0.17 +dev-ml/sexp_pretty:0/0.17 +dev-ml/expect_test_helpers_core:0/0.17 +dev-ml/core_unix:0/0.17 +dev-ml/async_kernel:0/0.17 +dev-ml/async_unix:0/0.17 +dev-ml/protocol_version_header:0/0.17 +dev-ml/async_rpc_kernel:0/0.17 +dev-ml/async_log:0/0.17 +dev-ml/textutils:0/0.17 +dev-ml/async:0/0.17 +>=dev-ml/labltk-8.06.14 +dev-ml/patience_diff:0/0.17 +>=dev-ml/ppx_deriving-6.0.2 +dev-ml/ppx_js_style:0/0.17 + +# Michał Górny <mgorny@gentoo.org> (2024-06-08) +# Prereleases of Xfce 4.20. Masking upon popular request, due to +# a large number of regressions in every new release. +>=dev-build/xfce4-dev-tools-4.19 +>=xfce-base/exo-4.19 +>=xfce-base/garcon-4.19 +>=xfce-base/libxfce4ui-4.19 +>=xfce-base/libxfce4util-4.19 +>=xfce-base/thunar-4.19 +>=xfce-base/tumbler-4.19 +>=xfce-base/xfce4-appfinder-4.19 +>=xfce-base/xfce4-panel-4.19 +>=xfce-base/xfce4-power-manager-4.19 +>=xfce-base/xfce4-session-4.19 +>=xfce-base/xfce4-settings-4.19 +>=xfce-base/xfconf-4.19 +>=xfce-base/xfdesktop-4.19 # Sam James <sam@gentoo.org> (2024-04-28) # Masked for testing. Tracker bug: bug #930805. >=sys-libs/ncurses-6.5 -# Jason Zaman <perfinion@gentoo.org> (2024-04-27) -# Sandboxfs was only experimental in Bazel. It was fully removed in Bazel-7 -# Bazel was removed from gentoo in Feb. -# Removal in 30 days. Bug #930790 -sys-fs/sandboxfs - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-04-27) -# EAPI=6 package, has issues with implicit function declarations, has -# issues with incompatible types and more. The only reverse dependency -# is virtual/skkserv, which has other better candidates. -# Removal on 2024-05-27, bug #930781 -app-i18n/skkserv - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-04-26) -# Broken and reported as such upstream. EAPI=6. -# Removal: 2024-05-26. Bug #912842. -net-misc/ttytter - -# Maciej Barć <xgqt@gentoo.org> (2024-04-25) -# Mask "app-emacs/windows" and reverse dependencies. -# Very old package failing to compile with modern GNU Emacs. -# Additionally all 3 packages do not have any definitive repository nor VCS. -# Open bugs: #930655 -# Removal on 2024-05-25. -app-emacs/basic-toolkit -app-emacs/buffer-extension -app-emacs/windows - -# Matt Turner <mattst88@gentoo.org> (2024-04-25) -# Masked for testing -=dev-util/intel_clc-24.1* -=media-libs/mesa-24.1* - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# No py3.12, no tests, no maintainer. Also no revdeps. -# Removal on 2024-05-23. Bug #929513. -dev-python/sphinxcontrib-newsfeed - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Integrated into >=dev-python/pytest-5.0. No revdeps. -# Removal on 2024-05-23. Bug #929496. -dev-python/pytest-faulthandler - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Broken with py3.12. Last commit upstream in 2021. No revdeps. -# Removal on 2024-05-23. Bug #929484. -dev-python/pyannotate - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# No py3.12, broken. Upstream literally tells people to use a fork -# "for the time being". No revdeps. -# Removal on 2024-05-23. Bug #929461. -dev-python/kafka-python - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Unmaintained. No py3.12, failing tests. Last upstream activity -# in 2020, triggered by our previous last rites. No revdeps. -# Removal on 2024-05-23. Bug #929445. -dev-python/cgroup-utils - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Unmaintained Sphinx theme. Last commit in 2021. No revdeps. -# Removal on 2024-05-23. Bug #929458. -dev-python/guzzle_sphinx_theme - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Unmaintained in Gentoo. Lacking tests, py3.12 support, outdated. -# No revdeps. The alternatives are dev-python/{llfuse,pyfuse3}. -# Removal on 2024-05-23. Bug #929453. -dev-python/fuse-python - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Unmaintained. Last release in 2003. Carries a ton of patches. -# Removal on 2024-05-23. Bug #928731. -net-analyzer/tcpstat - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Added in 2005 and not updated since. Homepage and source mirrors -# are gone. Needs patches to even build. -# Removal on 2024-05-23. Bug #928594. -media-video/vstrip - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Obsolete Pidgin plugin. Last supported in 2008, removed from plugin -# list in 2019. -# Removal on 2024-05-23. Bug #928578. -net-im/librvp - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Unmaintained GTK+2 application. Last update in 2005. -# Alternatives include media-sound/fmit and media-sound/lingot. -# Removal on 2024-05-23. Bug #928512. -media-sound/pitchtune - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Ancient. Homepage gone. There are many alternative network testing -# tools, such as net-misc/iperf. -# Removal on 2024-05-23. Bug #928133. -net-analyzer/gensink - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# An old, unmaintained theme. The last revdep stopped using it. -# Removal on 2024-05-23. Bug #927764. -dev-python/sphinx-py3doc-enhanced-theme - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Unmaintained in Gentoo and seriously outdated. EAPI 6. No revdeps. -# There seem to be an up-to-date ebuilds in ::mva. -# Removal on 2024-05-23. Bug #928070. -dev-util/android-ndk - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Unmaintained in Gentoo and seriously outdated. Its only reverse -# dependency is app-admin/testdisk, and the current TestDisk versions -# do not build against this version anyway -# Removal on 2024-05-23. Bug #927076. -app-forensics/libewf - -# Michał Górny <mgorny@gentoo.org> (2024-04-23) -# Superseded by dev-python/tinycss2. No revdeps. -# Removal on 2024-05-23. Bug #930503. -dev-python/tinycss - -# Matthew Smith <matthew@gentoo.org> (2024-04-23) -# Security issues (Bug #920682). -# See the following link for breaking changes: -# https://www.erlang.org/patches/otp-26.2#incompatibilities -# Removal on 2024-05-23 -<dev-lang/elixir-1.14.5-r2 -=dev-lang/elixir-1.15.6 -<dev-lang/erlang-26.2.1 - -# Matthew Smith <matthew@gentoo.org> (2024-04-23) -# Security issues (Bug #918527) and blocking cleanup of vulnerable -# dev-lang/erlang versions. Please upgrade. -# https://www.rabbitmq.com/docs/upgrade -# Removal on 2024-05-23 -<net-misc/rabbitmq-server-3.13.1 - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-04-20) -# EAPI6 package, with no reverse dependencies. Not really maintained -# since gentoo's transition to git. Distfile is fetch and mirror -# restricted, and based on comment in ebuild, the source isn't stable -# and we can lose the only source for distfile. -# Removal on 2024-05-20, bug #930346. -sys-block/megamgr - -# Arthur Zamarin <arthurzam@gentoo.org> (2024-04-19) -# EAPI=6, library only without any reverse dependencies, uses -# deprecated go eclasses, maintainer-needed. -# Removal on 2024-05-19, bug #930249 -dev-go/qr -dev-go/twofactor - # Michał Górny <mgorny@gentoo.org> (2024-04-11) # Contains a bug that could render the kernel fail to boot. # https://lore.kernel.org/oe-lkp/202403221630.2692c998-oliver.sang@intel.com/ @@ -402,457 +384,6 @@ sec-keys/openpgp-keys-jiatan # Mask experimental software =mail-mta/postfix-3.10* -# Andreas Sturmlechner <asturm@gentoo.org> (2024-05-20) -# KDE Plasma 6.0.4, Gear 24.05 RC1 and Frameworks 6.2.0 mask -# -# Don't do anything unless you're intentionally moving to Plasma 6, which is -# masked still for a reason. If you get this message just from conflicts where -# you're not trying to do that, please cleanup stale entries in /etc/portage -# and your world file. -# -# Plasma 6 replaces 5. For conflict resolution between KF5- and KF6-packages: -# - put '-kf6compat' into /etc/portage/profile/use.mask -# - enable USE=kf6compat globally -# - if you have the following packages installed, put the following into -# /etc/portage/package.use in order to avoid conflicts: -# dev-util/kdevelop:5 -gdbui -plasma -# If you encounter ... -# - build-time/packaging bugs: -# - file a bug after making sure none exists yet for your issue -# - runtime bugs: https://community.kde.org/Plasma/Plasma_6#How_to_use/test_it -# - work with upstream and help test patches using /etc/portage/patches -~kde-frameworks/frameworkintegration-6.2.0 -~kde-frameworks/attica-6.2.0 -~kde-frameworks/bluez-qt-6.2.0 -~kde-frameworks/breeze-icons-6.2.0 -~kde-frameworks/extra-cmake-modules-6.2.0 -~kde-frameworks/karchive-6.2.0 -~kde-frameworks/kcalendarcore-6.2.0 -~kde-frameworks/kcodecs-6.2.0 -~kde-frameworks/kconfig-6.2.0 -~kde-frameworks/kcoreaddons-6.2.0 -~kde-frameworks/kdbusaddons-6.2.0 -~kde-frameworks/kdnssd-6.2.0 -~kde-frameworks/kguiaddons-6.2.0 -~kde-frameworks/kholidays-6.2.0 -~kde-frameworks/ki18n-6.2.0 -~kde-frameworks/kidletime-6.2.0 -~kde-frameworks/kirigami-6.2.1 -~kde-frameworks/kitemmodels-6.2.0 -~kde-frameworks/kitemviews-6.2.0 -~kde-frameworks/kplotting-6.2.0 -~kde-frameworks/kquickcharts-6.2.0 -~kde-frameworks/ktexttemplate-6.2.0 -~kde-frameworks/kuserfeedback-6.2.0 -~kde-frameworks/kwidgetsaddons-6.2.0 -~kde-frameworks/kwindowsystem-6.2.0 -~kde-frameworks/modemmanager-qt-6.2.0 -~kde-frameworks/networkmanager-qt-6.2.0 -~kde-frameworks/prison-6.2.0 -~kde-frameworks/solid-6.2.0 -~kde-frameworks/sonnet-6.2.0 -~kde-frameworks/syntax-highlighting-6.2.0 -~kde-frameworks/threadweaver-6.2.0 -~kde-frameworks/kauth-6.2.0 -~kde-frameworks/kcolorscheme-6.2.0 -~kde-frameworks/kcompletion-6.2.0 -~kde-frameworks/kcontacts-6.2.0 -~kde-frameworks/kcrash-6.2.0 -~kde-frameworks/kdoctools-6.2.0 -~kde-frameworks/kfilemetadata-6.2.0 -~kde-frameworks/kimageformats-6.2.0 -~kde-frameworks/kjobwidgets-6.2.0 -~kde-frameworks/knotifications-6.2.0 -~kde-frameworks/kpackage-6.2.0 -~kde-frameworks/kpty-6.2.0 -~kde-frameworks/kstatusnotifieritem-6.2.0 -~kde-frameworks/ksvg-6.2.0 -~kde-frameworks/kunitconversion-6.2.0 -~kde-frameworks/syndication-6.2.0 -~kde-frameworks/baloo-6.2.0 -~kde-frameworks/kbookmarks-6.2.0 -~kde-frameworks/kcmutils-6.2.0 -~kde-frameworks/kconfigwidgets-6.2.0 -~kde-frameworks/kdav-6.2.0 -~kde-frameworks/kdeclarative-6.2.0 -~kde-frameworks/kded-6.2.0 -~kde-frameworks/kdesu-6.2.0 -~kde-frameworks/kglobalaccel-6.2.0 -~kde-frameworks/kiconthemes-6.2.0 -~kde-frameworks/kio-6.2.0 -~kde-frameworks/knewstuff-6.2.0 -~kde-frameworks/knotifyconfig-6.2.0 -~kde-frameworks/kparts-6.2.0 -~kde-frameworks/kpeople-6.2.0 -~kde-frameworks/krunner-6.2.0 -~kde-frameworks/kservice-6.2.0 -~kde-frameworks/ktexteditor-6.2.0 -~kde-frameworks/ktextwidgets-6.2.0 -~kde-frameworks/kwallet-6.2.0 -~kde-frameworks/kxmlgui-6.2.0 -~kde-frameworks/purpose-6.2.0 -~kde-frameworks/qqc2-desktop-style-6.2.0 -~kde-plasma/bluedevil-6.0.4 -~kde-plasma/breeze-6.0.4 -~kde-plasma/breeze-grub-6.0.4 -~kde-plasma/breeze-gtk-6.0.4.1 -~kde-plasma/breeze-plymouth-6.0.4.1 -~kde-plasma/discover-6.0.4 -~kde-plasma/drkonqi-6.0.4 -~kde-plasma/flatpak-kcm-6.0.4 -~kde-plasma/kactivitymanagerd-6.0.4 -~kde-plasma/kde-cli-tools-6.0.4 -~kde-plasma/kde-gtk-config-6.0.4 -~kde-plasma/kdecoration-6.0.4 -~kde-plasma/kdeplasma-addons-6.0.4 -~kde-plasma/kgamma-6.0.4 -~kde-plasma/kglobalacceld-6.0.4 -~kde-plasma/kinfocenter-6.0.4 -~kde-plasma/kmenuedit-6.0.4 -~kde-plasma/kpipewire-6.0.4 -~kde-plasma/kscreen-6.0.4 -~kde-plasma/kscreenlocker-6.0.4 -~kde-plasma/ksshaskpass-6.0.4 -~kde-plasma/ksystemstats-6.0.4 -~kde-plasma/kwallet-pam-6.0.4 -~kde-plasma/kwayland-6.0.4 -~kde-plasma/kwayland-integration-6.0.4 -~kde-plasma/kwin-6.0.4.1 -~kde-plasma/kwrited-6.0.4 -~kde-plasma/layer-shell-qt-6.0.4 -~kde-plasma/libkscreen-6.0.4 -~kde-plasma/libksysguard-6.0.4 -~kde-plasma/libplasma-6.0.4 -~kde-plasma/milou-6.0.4 -~kde-plasma/ocean-sound-theme-6.0.4 -~kde-plasma/oxygen-6.0.4 -~kde-plasma/oxygen-sounds-6.0.4 -~kde-plasma/plasma-activities-6.0.4 -~kde-plasma/plasma-activities-stats-6.0.4 -~kde-plasma/plasma-browser-integration-6.0.4 -~kde-plasma/plasma-desktop-6.0.4 -~kde-plasma/plasma-disks-6.0.4 -~kde-plasma/plasma-firewall-6.0.4 -~kde-plasma/plasma-integration-6.0.4 -~kde-plasma/plasma-meta-6.0.4 -~kde-plasma/plasma-nm-6.0.4 -~kde-plasma/plasma-pa-6.0.4 -~kde-plasma/plasma-sdk-6.0.4 -~kde-plasma/plasma-systemmonitor-6.0.4 -~kde-plasma/plasma-thunderbolt-6.0.4 -~kde-plasma/plasma-vault-6.0.4 -~kde-plasma/plasma-welcome-6.0.4 -~kde-plasma/plasma-workspace-6.0.4 -~kde-plasma/plasma-workspace-wallpapers-6.0.4 -~kde-plasma/plasma5support-6.0.4 -~kde-plasma/plymouth-kcm-6.0.4 -~kde-plasma/polkit-kde-agent-6.0.4 -~kde-plasma/powerdevil-6.0.4 -~kde-plasma/print-manager-6.0.4 -~kde-plasma/qqc2-breeze-style-6.0.4 -~kde-plasma/sddm-kcm-6.0.4 -~kde-plasma/systemsettings-6.0.4 -~kde-plasma/wacomtablet-6.0.4 -~kde-plasma/xdg-desktop-portal-kde-6.0.4 -~kde-apps/kdialog-24.04.90 -~kde-apps/keditbookmarks-24.04.90 -~kde-apps/kfind-24.04.90 -~kde-apps/konqueror-24.04.90 -~www-client/falkon-24.04.90 -~kde-apps/baloo-widgets-24.04.90 -~kde-apps/dolphin-24.04.90 -~kde-apps/kate-24.04.90 -~kde-apps/kate-addons-24.04.90 -~kde-apps/kate-lib-24.04.90 -~kde-apps/kde-apps-meta-24.04.90 -~kde-apps/kdecore-meta-24.04.90 -~kde-apps/khelpcenter-24.04.90 -~kde-apps/konsole-24.04.90 -~kde-apps/kwrite-24.04.90 -~app-accessibility/kontrast-24.04.90 -~kde-apps/kdeaccessibility-meta-24.04.90 -~kde-apps/kmag-24.04.90 -~kde-apps/kmousetool-24.04.90 -~kde-apps/kmouth-24.04.90 -~kde-apps/kdeadmin-meta-24.04.90 -~kde-apps/kcron-24.04.90 -~kde-apps/ksystemlog-24.04.90 -~kde-apps/analitza-24.04.90 -~kde-apps/artikulate-24.04.90 -~kde-apps/blinken-24.04.90 -~kde-apps/cantor-24.04.90 -~kde-apps/kalgebra-24.04.90 -~kde-apps/kalzium-24.04.90 -~kde-apps/kanagram-24.04.90 -~kde-apps/kbruch-24.04.90 -~kde-apps/kdeedu-data-24.04.90 -~kde-apps/kdeedu-meta-24.04.90 -~kde-apps/kgeography-24.04.90 -~kde-apps/khangman-24.04.90 -~kde-apps/kig-24.04.90 -~kde-apps/kiten-24.04.90 -~kde-apps/klettres-24.04.90 -~kde-apps/kmplot-24.04.90 -~kde-apps/kqtquickcharts-24.04.90 -~kde-apps/ktouch-24.04.90 -~kde-apps/kturtle-24.04.90 -~kde-apps/kwordquiz-24.04.90 -~kde-apps/libkeduvocdocument-24.04.90 -~kde-apps/marble-24.04.90 -~kde-apps/minuet-24.04.90 -~kde-apps/parley-24.04.90 -~kde-apps/rocs-24.04.90 -~kde-apps/step-24.04.90 -~games-puzzle/skladnik-24.04.90 -~kde-apps/bomber-24.04.90 -~kde-apps/bovo-24.04.90 -~kde-apps/granatier-24.04.90 -~kde-apps/kajongg-24.04.90 -~kde-apps/kapman-24.04.90 -~kde-apps/katomic-24.04.90 -~kde-apps/kblackbox-24.04.90 -~kde-apps/kblocks-24.04.90 -~kde-apps/kbounce-24.04.90 -~kde-apps/kbreakout-24.04.90 -~kde-apps/kdegames-meta-24.04.90 -~kde-apps/kdiamond-24.04.90 -~kde-apps/kfourinline-24.04.90 -~kde-apps/kgoldrunner-24.04.90 -~kde-apps/kigo-24.04.90 -~kde-apps/killbots-24.04.90 -~kde-apps/kiriki-24.04.90 -~kde-apps/kjumpingcube-24.04.90 -~kde-apps/klickety-24.04.90 -~kde-apps/klines-24.04.90 -~kde-apps/kmahjongg-24.04.90 -~kde-apps/kmines-24.04.90 -~kde-apps/knavalbattle-24.04.90 -~kde-apps/knetwalk-24.04.90 -~kde-apps/knights-24.04.90 -~kde-apps/kolf-24.04.90 -~kde-apps/kollision-24.04.90 -~kde-apps/konquest-24.04.90 -~kde-apps/kpat-24.04.90 -~kde-apps/kreversi-24.04.90 -~kde-apps/kshisen-24.04.90 -~kde-apps/ksirk-24.04.90 -~kde-apps/ksnakeduel-24.04.90 -~kde-apps/kspaceduel-24.04.90 -~kde-apps/ksquares-24.04.90 -~kde-apps/ksudoku-24.04.90 -~kde-apps/ktuberling-24.04.90 -~kde-apps/kubrick-24.04.90 -~kde-apps/libkdegames-24.04.90 -~kde-apps/libkmahjongg-24.04.90 -~kde-apps/lskat-24.04.90 -~kde-apps/palapeli-24.04.90 -~kde-apps/picmi-24.04.90 -~kde-apps/gwenview-24.04.90 -~kde-apps/kamera-24.04.90 -~kde-apps/kcolorchooser-24.04.90 -~kde-apps/kdegraphics-meta-24.04.90 -~kde-apps/kdegraphics-mobipocket-24.04.90 -~kde-apps/kolourpaint-24.04.90 -~kde-apps/kruler-24.04.90 -~kde-apps/libkdcraw-24.04.90 -~kde-apps/libkexiv2-24.04.90 -~kde-apps/libksane-24.04.90 -~kde-apps/okular-24.04.90 -~kde-apps/spectacle-24.04.90 -~kde-apps/svgpart-24.04.90 -~kde-apps/thumbnailers-24.04.90 -~kde-misc/colord-kde-24.04.90 -~kde-misc/skanlite-24.04.90 -~media-gfx/skanpage-24.04.90 -~media-libs/ksanecore-24.04.90 -~kde-apps/audiocd-kio-24.04.90 -~kde-apps/dragon-24.04.90 -~kde-apps/ffmpegthumbs-24.04.90 -~kde-apps/juk-24.04.90 -~kde-apps/k3b-24.04.90 -~kde-apps/kamoso-24.04.90 -~kde-apps/kdemultimedia-meta-24.04.90 -~kde-apps/kdenlive-24.04.90 -~kde-apps/kmix-24.04.90 -~kde-apps/kwave-24.04.90 -~kde-apps/libkcddb-24.04.90 -~kde-apps/libkcompactdisc-24.04.90 -~media-sound/audex-24.04.90 -~media-sound/elisa-24.04.90 -~media-sound/kasts-24.04.90 -~media-sound/krecorder-24.04.90 -~kde-apps/dolphin-plugins-dropbox-24.04.90 -~kde-apps/kaccounts-integration-24.04.90 -~kde-apps/kaccounts-providers-24.04.90 -~kde-apps/kdenetwork-meta-24.04.90 -~kde-apps/kdenetwork-filesharing-24.04.90 -~kde-apps/kget-24.04.90 -~kde-apps/kio-extras-24.04.90 -~kde-apps/krdc-24.04.90 -~kde-apps/krfb-24.04.90 -~kde-apps/signon-kwallet-extension-24.04.90 -~kde-misc/kdeconnect-24.04.90 -~kde-misc/kio-gdrive-24.04.90 -~net-im/neochat-24.04.90 -~net-im/tokodon-24.04.90 -~net-irc/konversation-24.04.90 -~net-libs/libktorrent-24.04.90 -~net-misc/kio-zeroconf-24.04.90 -~net-news/alligator-24.04.90 -~net-p2p/ktorrent-24.04.90 -~app-office/merkuro-24.04.90 -~dev-libs/kopeninghours-24.04.90 -~dev-libs/kosmindoormap-24.04.90 -~dev-libs/kpublictransport-24.04.90 -~kde-apps/akonadi-24.04.90 -~kde-apps/akonadi-calendar-24.04.90 -~kde-apps/akonadi-contacts-24.04.90 -~kde-apps/akonadi-import-wizard-24.04.90 -~kde-apps/akonadi-mime-24.04.90 -~kde-apps/akonadi-notes-24.04.90 -~kde-apps/akonadi-search-24.04.90 -~kde-apps/akonadiconsole-24.04.90 -~kde-apps/akregator-24.04.90 -~kde-apps/calendarjanitor-24.04.90 -~kde-apps/calendarsupport-24.04.90 -~kde-apps/eventviews-24.04.90 -~kde-apps/grantlee-editor-24.04.90 -~kde-apps/grantleetheme-24.04.90 -~kde-apps/incidenceeditor-24.04.90 -~kde-apps/kaddressbook-24.04.90 -~kde-apps/kalarm-24.04.90 -~kde-apps/kcalutils-24.04.90 -~kde-apps/kdepim-addons-24.04.90 -~kde-apps/kdepim-meta-24.04.90 -~kde-apps/kdepim-runtime-24.04.90 -~kde-apps/kidentitymanagement-24.04.90 -~kde-apps/kimap-24.04.90 -~kde-apps/kitinerary-24.04.90 -~kde-apps/kldap-24.04.90 -~kde-apps/kleopatra-24.04.90 -~kde-apps/kmail-24.04.90 -~kde-apps/kmail-account-wizard-24.04.90 -~kde-apps/kmailtransport-24.04.90 -~kde-apps/kmbox-24.04.90 -~kde-apps/kmime-24.04.90 -~kde-apps/knotes-24.04.90 -~kde-apps/konsolekalendar-24.04.90 -~kde-apps/kontact-24.04.90 -~kde-apps/kontactinterface-24.04.90 -~kde-apps/korganizer-24.04.90 -~kde-apps/kpimtextedit-24.04.90 -~kde-apps/kpkpass-24.04.90 -~kde-apps/ksmtp-24.04.90 -~kde-apps/libgravatar-24.04.90 -~kde-apps/libkdepim-24.04.90 -~kde-apps/libkgapi-24.04.90 -~kde-apps/libkleo-24.04.90 -~kde-apps/libksieve-24.04.90 -~kde-apps/libktnef-24.04.90 -~kde-apps/mailcommon-24.04.90 -~kde-apps/mailimporter-24.04.90 -~kde-apps/mbox-importer-24.04.90 -~kde-apps/messagelib-24.04.90 -~kde-apps/mimetreeparser-24.04.90 -~kde-apps/pim-data-exporter-24.04.90 -~kde-apps/pim-sieve-editor-24.04.90 -~kde-apps/pimcommon-24.04.90 -~kde-misc/zanshin-24.04.90 -~dev-util/kdevelop-24.04.90 -~dev-util/kdevelop-php-24.04.90 -~dev-util/kdevelop-python-24.04.90 -~dev-util/kio-perldoc-24.04.90 -~kde-apps/cervisia-24.04.90 -~kde-apps/dolphin-plugins-git-24.04.90 -~kde-apps/dolphin-plugins-mercurial-24.04.90 -~kde-apps/dolphin-plugins-subversion-24.04.90 -~kde-apps/kapptemplate-24.04.90 -~kde-apps/kcachegrind-24.04.90 -~kde-apps/kde-dev-scripts-24.04.90 -~kde-apps/kde-dev-utils-24.04.90 -~kde-apps/kdesdk-meta-24.04.90 -~kde-apps/kdesdk-thumbnailers-24.04.90 -~kde-apps/kompare-24.04.90 -~kde-apps/libkomparediff2-24.04.90 -~kde-apps/lokalize-24.04.90 -~kde-apps/poxml-24.04.90 -~kde-apps/umbrello-24.04.90 -~app-cdr/dolphin-plugins-mountiso-24.04.90 -~app-cdr/isoimagewriter-24.04.90 -~app-crypt/keysmith-24.04.90 -~app-editors/ghostwriter-24.04.90 -~kde-apps/ark-24.04.90 -~kde-apps/filelight-24.04.90 -~kde-apps/kbackup-24.04.90 -~kde-apps/kcalc-24.04.90 -~kde-apps/kcharselect-24.04.90 -~kde-apps/kdebugsettings-24.04.90 -~kde-apps/kdeutils-meta-24.04.90 -~kde-apps/kdf-24.04.90 -~kde-apps/kgpg-24.04.90 -~kde-apps/kimagemapeditor-24.04.90 -~kde-apps/kteatime-24.04.90 -~kde-apps/ktimer-24.04.90 -~kde-apps/kwalletmanager-24.04.90 -~kde-apps/sweeper-24.04.90 -~kde-apps/yakuake-24.04.90 -~kde-misc/kclock-24.04.90 -~kde-misc/kweather-24.04.90 -~kde-misc/markdownpart-24.04.90 -~sys-block/partitionmanager-24.04.90 -~sys-libs/kpmcore-24.04.90 -=kde-misc/kio-gdrive-23.08.5-r1 -=kde-plasma/print-manager-23.08.5-r100 -~kde-misc/kio-fuse-5.1.0 -~kde-misc/plasma-pass-1.2.2 -~app-editors/kile-2.9.94 -~dev-db/futuresql-0.1.1 -~dev-libs/appstream-1.0.3 -~dev-libs/kdiagram-3.0.1 -~dev-libs/kirigami-addons-1.2.1 -~dev-libs/ktextaddons-1.5.4 -~dev-libs/kweathercore-0.8.0 -~dev-util/massif-visualizer-0.8.0 -~games-puzzle/skladnik-0.5.2 -~gui-apps/xwaylandvideobridge-0.4.0 -~kde-frameworks/oxygen-icons-6.0.0 -~media-gfx/kgraphviewer-2.5.0 -=media-libs/kquickimageeditor-0.3.0-r100 -~media-libs/libqaccessibilityclient-0.6.0 -~media-libs/mpvqt-1.0.0 -~media-libs/phonon-4.12.0 -~media-libs/phonon-vlc-0.12.0 -~media-libs/pulseaudio-qt-1.4.0 -~net-libs/kdsoap-2.2.0 -~net-libs/kdsoap-ws-discovery-client-0.4.0 -~net-libs/signon-ui-0.15_p20231016 -~net-libs/accounts-qt-1.17 -~net-libs/accounts-qml-0.7_p20231028 -~net-libs/signon-oauth2-0.25_p20210102 -=net-libs/signond-8.61-r100 -=net-misc/smb4k-3.2.5-r2 -~sys-auth/polkit-qt-0.200.0 - -# Sam James <sam@gentoo.org> (2024-02-18) -# Lots of changes, including a port to a new build system. Needs lots of testing. -=sys-apps/gentoo-functions-1* - -# Ulrich Müller <ulm@gentoo.org> (2024-02-08) -# Masked for testing. -# Test failure in watchpoints.dem, undefined function FresnelC. -~sci-visualization/gnuplot-6.0.0 - -# Patrick Lauer <patrick@gentoo.org> (2023-12-23) -# ROCm-6 builds but has runtime issues for me ->=dev-libs/roct-thunk-interface-6.0.0 ->=dev-libs/rocr-runtime-6.0.0 ->=dev-libs/rocm-comgr-6.0.0 ->=dev-libs/rocm-device-libs-6.0.0 ->=dev-libs/rocm-opencl-runtime-6.0.0 ->=dev-util/hipcc-6.0.0 ->=dev-util/hip-6.0.0 ->=dev-util/rocminfo-6.0.0 - # Sam James <sam@gentoo.org> (2023-12-14) # Gentoo's kernel maintainers have decided to discontinue gentoo-sources and # gentoo-kernel for old kernel LTS branches because of the resources to require @@ -871,50 +402,6 @@ sec-keys/openpgp-keys-jiatan <sys-kernel/gentoo-kernel-5.10 <virtual/dist-kernel-5.10 -# Sam James <sam@gentoo.org> (2023-12-09) -# ext4 corruption bug: https://lore.kernel.org/stable/20231205122122.dfhhoaswsfscuhc3@quack3/ (bug #919675) -# Please update immediately to the latest versions in each series. -=sys-kernel/gentoo-sources-6.1.64 -=sys-kernel/gentoo-sources-6.1.64-r1 -=sys-kernel/gentoo-sources-6.1.65 -=sys-kernel/gentoo-kernel-6.1.64 -=sys-kernel/gentoo-kernel-6.1.64-r1 -=sys-kernel/gentoo-kernel-6.1.65 -=sys-kernel/vanilla-sources-6.1.64 -=sys-kernel/vanilla-sources-6.1.65 -=sys-kernel/vanilla-kernel-6.1.64 -=sys-kernel/vanilla-kernel-6.1.65 - -# Sam James <sam@gentoo.org> (2023-11-22) -# Further bugs with CoW via copy_file_range (bug #917224, https://github.com/openzfs/zfs/issues/15526). -# The issue is very similar to bug #815469. -# ZFS 2.2.1 has a workaround but if you haven't already upgraded your pool to -# use the new block cloning feature, consider using <zfs-2.2 for now. -=sys-fs/zfs-2.2.0 -=sys-fs/zfs-kmod-2.2.0 - -# Sam James <sam@gentoo.org> (2023-11-19) -# GCC 10 and older no longer receive upstream support or fixes for -# bugs. Please switch to a newer GCC version using gcc-config. -# The lowest supported version of GCC is GCC 11. -<sys-devel/gcc-11 -<sys-devel/kgcc64-11 - -# Sam James <sam@gentoo.org> (2023-11-05) -# Mask broken versions: -# - sys-fs/btrfs-progs-6.6(-r0) was respun upstream. -# - sys-fs/btrfs-progs-6.6-r1 had the fixed tarball, but contained an upstream -# bug in the ioctl numbers. -# Please use sys-fs/btrfs-progs-6.6-r2 or, better, sys-fs/btrfs-progs-6.6.1 -# (identical in functional contents). -=sys-fs/btrfs-progs-6.6 -=sys-fs/btrfs-progs-6.6-r1 -=sys-fs/btrfs-progs-6.6-r2 - -# Sam James <sam@gentoo.org> (2023-10-06) -# Breaks building scipy: https://github.com/cython/cython/issues/5748 -=dev-python/cython-3.0.3 - # Sam James <sam@gentoo.org> (2023-09-09) # OpenSSL 1.1.x is EOL on 2023-09-11. Please upgrade immediately to >= OpenSSL 3. # https://www.openssl.org/blog/blog/2023/03/28/1.1.1-EOL/ @@ -931,10 +418,6 @@ sec-keys/openpgp-keys-jiatan # may or may not lead to useful results. <dev-util/catalyst-4 -# Matt Turner <mattst88@gentoo.org> (2023-07-06) -# GNOME 45 mask ->=gnome-extra/gnome-logs-45_alpha - # Michał Górny <mgorny@gentoo.org> (2023-06-21) # suitesparseconfig-7.0.0 fails to build with multilib enabled # because of dependencies that cannot be satisfied. All the other @@ -955,7 +438,8 @@ sec-keys/openpgp-keys-jiatan # Sam James <sam@gentoo.org> (2023-05-10) # Lots of package breakage as usual for new versions. Masked until most/all # reverse dependencies are fixed. Tracker bug is bug #906077. -=dev-libs/libfmt-10* +>=dev-libs/libfmt-10 +>=games-emulation/dolphin-2407 # Ionen Wolkens <ionen@gentoo.org> (2023-03-30) # NVIDIA dropped support for the 390.xx branch in December 2022[1]. @@ -983,11 +467,6 @@ x11-drivers/nvidia-drivers:0/390 # Breaks too many revdeps for now =app-text/discount-3* -# John Helmert III <ajak@gentoo.org> (2022-10-16) -# <OpenSSL-1.1.1 are EOL and contain known vulnerabilities. Users should -# migrate to a newer branch. -<dev-libs/openssl-1.1.1 - # Joonas Niilola <juippis@gentoo.org> (2022-04-29) # Apparently the "b" in version means "beta". 3.24 is available, we # should update to that. #841437 @@ -998,11 +477,6 @@ x11-drivers/nvidia-drivers:0/390 # This is likely to cause issues in tests; Unmask if using for other purposes >=dev-php/PHP_Timer-5.0 -# Volkmar W. Pogatzki <gentoo@pogatzki.net> (2021-11-23) -# Does not support updated dev-java/pdfbox-2.0.24, Bug #803488 -# Blocks (CVE-2018-11797, CVE-2021-{27807,27906,31811,31812}) -dev-tex/pdfannotextractor - # Ionen Wolkens <ionen@gentoo.org> (2021-10-09) # Vulkan beta driver branch aimed at Vulkan developers for testing # new features. Beside vulkan, it is typically behind the main branch @@ -1044,20 +518,6 @@ dev-build/automake:1.11 media-plugins/kodi-game-libretro-nestopia media-plugins/kodi-game-libretro-dosbox -# Sam James <sam@gentoo.org> (2020-10-05) -# Masked for testing. New major versions of Guile -# often break reverse dependencies. -# Guile in Gentoo is not slotted, so let's be cautious. -# bug #705554, bug #689408. ->=dev-scheme/guile-3.0.4 - -# Matt Turner <mattst88@gentoo.org> (2019-09-01) -# TeXmacs is the only remaining package in tree that requires guile-1.8, which -# is unsupported upstream. A TeXmacs port to Guile-2 has been in progress for a -# few years. Bug #436400 -app-office/texmacs -<dev-scheme/guile-2 - # Andreas Sturmlechner <asturm@gentoo.org> (2018-10-07) # Masked for more testing especially of reverse-deps. # ogre 1.11/1.12 breakage: bug #834468 diff --git a/profiles/default/linux/ia64/17.0/desktop/gnome/eapi b/profiles/prefix/darwin/macos/15.0/arm64/clang/eapi index 7ed6ff82de6b..7ed6ff82de6b 100644 --- a/profiles/default/linux/ia64/17.0/desktop/gnome/eapi +++ b/profiles/prefix/darwin/macos/15.0/arm64/clang/eapi diff --git a/profiles/prefix/darwin/macos/15.0/arm64/clang/parent b/profiles/prefix/darwin/macos/15.0/arm64/clang/parent new file mode 100644 index 000000000000..855aaf175968 --- /dev/null +++ b/profiles/prefix/darwin/macos/15.0/arm64/clang/parent @@ -0,0 +1,2 @@ +.. +../../../features/clang-lld diff --git a/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/eapi b/profiles/prefix/darwin/macos/15.0/arm64/eapi index 7ed6ff82de6b..7ed6ff82de6b 100644 --- a/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/eapi +++ b/profiles/prefix/darwin/macos/15.0/arm64/eapi diff --git a/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr/eapi b/profiles/prefix/darwin/macos/15.0/arm64/gcc/eapi index 7ed6ff82de6b..7ed6ff82de6b 100644 --- a/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr/eapi +++ b/profiles/prefix/darwin/macos/15.0/arm64/gcc/eapi diff --git a/profiles/prefix/darwin/macos/15.0/arm64/gcc/parent b/profiles/prefix/darwin/macos/15.0/arm64/gcc/parent new file mode 100644 index 000000000000..5ebbfd24d627 --- /dev/null +++ b/profiles/prefix/darwin/macos/15.0/arm64/gcc/parent @@ -0,0 +1,2 @@ +.. +../../../features/fsf-gcc-nold diff --git a/profiles/prefix/darwin/macos/15.0/arm64/make.defaults b/profiles/prefix/darwin/macos/15.0/arm64/make.defaults new file mode 100644 index 000000000000..d998178e0188 --- /dev/null +++ b/profiles/prefix/darwin/macos/15.0/arm64/make.defaults @@ -0,0 +1,5 @@ +# Copyright 1999-2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +CHOST="arm64-apple-darwin24" +CHOST_arm64="${CHOST}" diff --git a/profiles/prefix/darwin/macos/15.0/arm64/parent b/profiles/prefix/darwin/macos/15.0/arm64/parent new file mode 100644 index 000000000000..a75c3ad0a555 --- /dev/null +++ b/profiles/prefix/darwin/macos/15.0/arm64/parent @@ -0,0 +1,2 @@ +.. +../../arch/arm64 diff --git a/profiles/default/linux/ia64/17.0/developer/eapi b/profiles/prefix/darwin/macos/15.0/eapi index 7ed6ff82de6b..7ed6ff82de6b 100644 --- a/profiles/default/linux/ia64/17.0/developer/eapi +++ b/profiles/prefix/darwin/macos/15.0/eapi diff --git a/profiles/prefix/darwin/macos/15.0/make.defaults b/profiles/prefix/darwin/macos/15.0/make.defaults new file mode 100644 index 000000000000..5ea2db2a3f07 --- /dev/null +++ b/profiles/prefix/darwin/macos/15.0/make.defaults @@ -0,0 +1,4 @@ +# Copyright 1999-2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +MACOSX_DEPLOYMENT_TARGET="15.0" diff --git a/profiles/prefix/darwin/macos/15.0/package.use.mask b/profiles/prefix/darwin/macos/15.0/package.use.mask new file mode 100644 index 000000000000..0d222cee3b56 --- /dev/null +++ b/profiles/prefix/darwin/macos/15.0/package.use.mask @@ -0,0 +1,7 @@ +# Copyright 1999-2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Fabian Groffen <grobian@gentoo.org> (2011-04-10) +# as long as util-linux installs uuid.h which breaks the system headers +# (hence we don't) we can't do uuid support here +x11-libs/libSM -uuid diff --git a/profiles/prefix/darwin/macos/15.0/parent b/profiles/prefix/darwin/macos/15.0/parent new file mode 100644 index 000000000000..f3229c5b9876 --- /dev/null +++ b/profiles/prefix/darwin/macos/15.0/parent @@ -0,0 +1 @@ +.. diff --git a/profiles/prefix/darwin/macos/15.0/profile.bashrc b/profiles/prefix/darwin/macos/15.0/profile.bashrc new file mode 100644 index 000000000000..933758acd5d9 --- /dev/null +++ b/profiles/prefix/darwin/macos/15.0/profile.bashrc @@ -0,0 +1,4 @@ +# Copyright 1999-2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +export MACOSX_DEPLOYMENT_TARGET=15.0 diff --git a/profiles/default/linux/ia64/17.0/eapi b/profiles/prefix/darwin/macos/15.0/x64/eapi index 7ed6ff82de6b..7ed6ff82de6b 100644 --- a/profiles/default/linux/ia64/17.0/eapi +++ b/profiles/prefix/darwin/macos/15.0/x64/eapi diff --git a/profiles/default/linux/ia64/17.0/systemd/eapi b/profiles/prefix/darwin/macos/15.0/x64/gcc/eapi index 7ed6ff82de6b..7ed6ff82de6b 100644 --- a/profiles/default/linux/ia64/17.0/systemd/eapi +++ b/profiles/prefix/darwin/macos/15.0/x64/gcc/eapi diff --git a/profiles/prefix/darwin/macos/15.0/x64/gcc/parent b/profiles/prefix/darwin/macos/15.0/x64/gcc/parent new file mode 100644 index 000000000000..fceecddb55c7 --- /dev/null +++ b/profiles/prefix/darwin/macos/15.0/x64/gcc/parent @@ -0,0 +1,2 @@ +.. +../../../features/fsf-gcc-ld64 diff --git a/profiles/prefix/darwin/macos/15.0/x64/make.defaults b/profiles/prefix/darwin/macos/15.0/x64/make.defaults new file mode 100644 index 000000000000..ec3bbe571aeb --- /dev/null +++ b/profiles/prefix/darwin/macos/15.0/x64/make.defaults @@ -0,0 +1,5 @@ +# Copyright 1999-2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +CHOST="x86_64-apple-darwin24" +CHOST_amd64="${CHOST}" diff --git a/profiles/prefix/darwin/macos/15.0/x64/parent b/profiles/prefix/darwin/macos/15.0/x64/parent new file mode 100644 index 000000000000..269f6f48bb15 --- /dev/null +++ b/profiles/prefix/darwin/macos/15.0/x64/parent @@ -0,0 +1,2 @@ +.. +../../arch/x64 diff --git a/profiles/prefix/darwin/macos/package.mask b/profiles/prefix/darwin/macos/package.mask index 929018114296..709360d865d4 100644 --- a/profiles/prefix/darwin/macos/package.mask +++ b/profiles/prefix/darwin/macos/package.mask @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # Benda Xu <heroxbd@gentoo.org> (2023-08-20) diff --git a/profiles/prefix/darwin/macos/package.use.mask b/profiles/prefix/darwin/macos/package.use.mask index 752f5b30f15f..b388ebc3beb3 100644 --- a/profiles/prefix/darwin/macos/package.use.mask +++ b/profiles/prefix/darwin/macos/package.use.mask @@ -1,6 +1,10 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Fabian Groffen <grobian@gentoo.org> (2024-07-19) +# misdetects and results in a broken (trapping) library e.g. breaks gpg +dev-libs/libgcrypt asm + # Fabian Groffen <grobian@gentoo.org> (2024-03-08) # -z,now is not something Darwin linkers understand sys-devel/gcc default-znow diff --git a/profiles/prefix/package.mask b/profiles/prefix/package.mask index 321dccb561cb..4cc8f353b920 100644 --- a/profiles/prefix/package.mask +++ b/profiles/prefix/package.mask @@ -1,4 +1,4 @@ -# Copyright 1999-2022 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # # When you add an entry to the top of this file, add your name, the date, and diff --git a/profiles/prefix/sunos/solaris/package.mask b/profiles/prefix/sunos/solaris/package.mask index 1971a00902cf..d9757c8bbe3d 100644 --- a/profiles/prefix/sunos/solaris/package.mask +++ b/profiles/prefix/sunos/solaris/package.mask @@ -1,12 +1,6 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -# Fabian Groffen <grobian@gentoo.org> (2024-05-19) -# Fails to compile due to undefined INT_MAX -# https://github.com/libarchive/libarchive/issues/2162 -# https://github.com/libarchive/libarchive/commit/6ff1cd1e487ddf545337b88da3f1f5ca69a2f958 -=app-arch/libarchive-3.7.4 - # Fabian Groffen <grobian@gentoo.org> (2023-06-23) # Fails to link due to missing libintl, already fixed upstream: # https://git.savannah.gnu.org/cgit/tar.git/commit/?id=8632df398b2f548465ebe68b8f494c0d6f8d913d diff --git a/profiles/prefix/sunos/solaris/package.use.mask b/profiles/prefix/sunos/solaris/package.use.mask index 740b644ecf23..ab2b27c9ac44 100644 --- a/profiles/prefix/sunos/solaris/package.use.mask +++ b/profiles/prefix/sunos/solaris/package.use.mask @@ -1,6 +1,14 @@ -# Copyright 1999-2022 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Fabian Groffen <grobian@gentoo.org> (2024-08-20) +# quic code fails to compile, seems Linux minded +net-misc/curl http3 quic curl_quic_openssl + +# Fabian Groffen <grobian@gentoo.org> (2024-07-21) +# Python integration breaks over C++ standards conflict(s) that Python +# headers try to change +dev-debug/gdb python # Fabian Groffen <grobian@gentoo.org> (2022-12-27) # Solaris must keep system libelf, else things break down diff --git a/profiles/profiles.desc b/profiles/profiles.desc index 3a9f5b22b107..445189fc42ef 100644 --- a/profiles/profiles.desc +++ b/profiles/profiles.desc @@ -17,33 +17,33 @@ alpha default/linux/alpha/17.0/desktop exp alpha default/linux/alpha/17.0/desktop/gnome exp alpha default/linux/alpha/17.0/desktop/gnome/systemd/merged-usr exp alpha default/linux/alpha/17.0/developer exp -alpha default/linux/alpha/23.0 exp -alpha default/linux/alpha/23.0/systemd exp -alpha default/linux/alpha/23.0/desktop exp -alpha default/linux/alpha/23.0/desktop/gnome exp -alpha default/linux/alpha/23.0/desktop/gnome/systemd exp -alpha default/linux/alpha/23.0/split-usr exp -alpha default/linux/alpha/23.0/split-usr/desktop exp -alpha default/linux/alpha/23.0/split-usr/desktop/gnome exp +alpha default/linux/alpha/23.0 stable +alpha default/linux/alpha/23.0/systemd stable +alpha default/linux/alpha/23.0/desktop stable +alpha default/linux/alpha/23.0/desktop/gnome stable +alpha default/linux/alpha/23.0/desktop/gnome/systemd stable +alpha default/linux/alpha/23.0/split-usr stable +alpha default/linux/alpha/23.0/split-usr/desktop stable +alpha default/linux/alpha/23.0/split-usr/desktop/gnome stable # AMD64 Profiles # @MAINTAINER: amd64@gentoo.org amd64 default/linux/amd64/17.1 stable -amd64 default/linux/amd64/17.1/selinux stable -amd64 default/linux/amd64/17.1/hardened stable -amd64 default/linux/amd64/17.1/hardened/selinux stable -amd64 default/linux/amd64/17.1/desktop stable -amd64 default/linux/amd64/17.1/desktop/gnome stable -amd64 default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr stable -amd64 default/linux/amd64/17.1/desktop/plasma stable -amd64 default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr stable -amd64 default/linux/amd64/17.1/desktop/systemd/merged-usr stable +amd64 default/linux/amd64/17.1/selinux exp +amd64 default/linux/amd64/17.1/hardened exp +amd64 default/linux/amd64/17.1/hardened/selinux exp +amd64 default/linux/amd64/17.1/desktop exp +amd64 default/linux/amd64/17.1/desktop/gnome exp +amd64 default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr exp +amd64 default/linux/amd64/17.1/desktop/plasma exp +amd64 default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr exp +amd64 default/linux/amd64/17.1/desktop/systemd/merged-usr exp amd64 default/linux/amd64/17.1/developer exp -amd64 default/linux/amd64/17.1/no-multilib stable -amd64 default/linux/amd64/17.1/no-multilib/hardened stable -amd64 default/linux/amd64/17.1/no-multilib/hardened/selinux stable -amd64 default/linux/amd64/17.1/no-multilib/systemd/merged-usr dev +amd64 default/linux/amd64/17.1/no-multilib exp +amd64 default/linux/amd64/17.1/no-multilib/hardened exp +amd64 default/linux/amd64/17.1/no-multilib/hardened/selinux exp +amd64 default/linux/amd64/17.1/no-multilib/systemd/merged-usr exp amd64 default/linux/amd64/17.1/no-multilib/systemd/selinux/merged-usr exp amd64 default/linux/amd64/17.1/systemd/merged-usr stable amd64 default/linux/amd64/17.1/systemd/selinux/merged-usr exp @@ -92,7 +92,7 @@ amd64 default/linux/amd64/23.0/split-usr/hardened/selinux stable # AMD64 Profiles # @MAINTAINER: amd64@gentoo.org -amd64 default/linux/amd64/17.0/x32 dev +amd64 default/linux/amd64/17.0/x32 exp amd64 default/linux/amd64/17.0/x32/systemd/merged-usr exp amd64 default/linux/amd64/23.0/x32 dev amd64 default/linux/amd64/23.0/x32/systemd exp @@ -101,49 +101,49 @@ amd64 default/linux/amd64/23.0/split-usr/x32 exp # ARM Profiles # @MAINTAINER: arm@gentoo.org -arm default/linux/arm/17.0 stable -arm default/linux/arm/17.0/desktop dev -arm default/linux/arm/17.0/desktop/gnome dev -arm default/linux/arm/17.0/desktop/gnome/systemd/merged-usr dev -arm default/linux/arm/17.0/desktop/plasma dev -arm default/linux/arm/17.0/desktop/plasma/systemd/merged-usr dev +arm default/linux/arm/17.0 exp +arm default/linux/arm/17.0/desktop exp +arm default/linux/arm/17.0/desktop/gnome exp +arm default/linux/arm/17.0/desktop/gnome/systemd/merged-usr exp +arm default/linux/arm/17.0/desktop/plasma exp +arm default/linux/arm/17.0/desktop/plasma/systemd/merged-usr exp arm default/linux/arm/17.0/developer exp -arm default/linux/arm/17.0/armv4 dev -arm default/linux/arm/17.0/armv4/desktop dev -arm default/linux/arm/17.0/armv4/desktop/gnome dev -arm default/linux/arm/17.0/armv4/desktop/plasma dev +arm default/linux/arm/17.0/armv4 exp +arm default/linux/arm/17.0/armv4/desktop exp +arm default/linux/arm/17.0/armv4/desktop/gnome exp +arm default/linux/arm/17.0/armv4/desktop/plasma exp arm default/linux/arm/17.0/armv4/developer exp -arm default/linux/arm/17.0/armv4t dev -arm default/linux/arm/17.0/armv4t/desktop dev -arm default/linux/arm/17.0/armv4t/desktop/gnome dev -arm default/linux/arm/17.0/armv4t/desktop/plasma dev +arm default/linux/arm/17.0/armv4t exp +arm default/linux/arm/17.0/armv4t/desktop exp +arm default/linux/arm/17.0/armv4t/desktop/gnome exp +arm default/linux/arm/17.0/armv4t/desktop/plasma exp arm default/linux/arm/17.0/armv4t/developer exp -arm default/linux/arm/17.0/armv4t/systemd/merged-usr dev -arm default/linux/arm/17.0/armv5te dev -arm default/linux/arm/17.0/armv5te/desktop dev -arm default/linux/arm/17.0/armv5te/desktop/gnome dev -arm default/linux/arm/17.0/armv5te/desktop/plasma dev +arm default/linux/arm/17.0/armv4t/systemd/merged-usr exp +arm default/linux/arm/17.0/armv5te exp +arm default/linux/arm/17.0/armv5te/desktop exp +arm default/linux/arm/17.0/armv5te/desktop/gnome exp +arm default/linux/arm/17.0/armv5te/desktop/plasma exp arm default/linux/arm/17.0/armv5te/developer exp -arm default/linux/arm/17.0/armv5te/systemd/merged-usr dev -arm default/linux/arm/17.0/armv6j stable +arm default/linux/arm/17.0/armv5te/systemd/merged-usr exp +arm default/linux/arm/17.0/armv6j exp arm default/linux/arm/17.0/armv6j/hardened exp arm default/linux/arm/17.0/armv6j/hardened/selinux exp -arm default/linux/arm/17.0/armv6j/desktop dev -arm default/linux/arm/17.0/armv6j/desktop/gnome dev -arm default/linux/arm/17.0/armv6j/desktop/plasma dev +arm default/linux/arm/17.0/armv6j/desktop exp +arm default/linux/arm/17.0/armv6j/desktop/gnome exp +arm default/linux/arm/17.0/armv6j/desktop/plasma exp arm default/linux/arm/17.0/armv6j/developer exp arm default/linux/arm/17.0/armv6j/selinux exp -arm default/linux/arm/17.0/armv6j/systemd/merged-usr dev -arm default/linux/arm/17.0/armv7a stable +arm default/linux/arm/17.0/armv6j/systemd/merged-usr exp +arm default/linux/arm/17.0/armv7a exp arm default/linux/arm/17.0/armv7a/hardened exp -arm default/linux/arm/17.0/armv7a/hardened/selinux dev -arm default/linux/arm/17.0/armv7a/desktop dev -arm default/linux/arm/17.0/armv7a/desktop/gnome dev -arm default/linux/arm/17.0/armv7a/desktop/gnome/systemd/merged-usr dev -arm default/linux/arm/17.0/armv7a/desktop/plasma dev -arm default/linux/arm/17.0/armv7a/desktop/plasma/systemd/merged-usr dev +arm default/linux/arm/17.0/armv7a/hardened/selinux exp +arm default/linux/arm/17.0/armv7a/desktop exp +arm default/linux/arm/17.0/armv7a/desktop/gnome exp +arm default/linux/arm/17.0/armv7a/desktop/gnome/systemd/merged-usr exp +arm default/linux/arm/17.0/armv7a/desktop/plasma exp +arm default/linux/arm/17.0/armv7a/desktop/plasma/systemd/merged-usr exp arm default/linux/arm/17.0/armv7a/developer exp -arm default/linux/arm/17.0/armv7a/systemd/merged-usr dev +arm default/linux/arm/17.0/armv7a/systemd/merged-usr exp arm default/linux/arm/23.0 stable arm default/linux/arm/23.0/desktop dev arm default/linux/arm/23.0/desktop/gnome dev @@ -210,17 +210,17 @@ arm default/linux/arm/23.0/split-usr/armv7a_hf/desktop/plasma dev # ARM64 Profiles # @MAINTAINER: arm64@gentoo.org -arm64 default/linux/arm64/17.0 stable +arm64 default/linux/arm64/17.0 exp arm64 default/linux/arm64/17.0/hardened exp -arm64 default/linux/arm64/17.0/hardened/selinux dev -arm64 default/linux/arm64/17.0/desktop stable -arm64 default/linux/arm64/17.0/desktop/gnome stable -arm64 default/linux/arm64/17.0/desktop/gnome/systemd/merged-usr stable -arm64 default/linux/arm64/17.0/desktop/plasma stable -arm64 default/linux/arm64/17.0/desktop/plasma/systemd/merged-usr stable -arm64 default/linux/arm64/17.0/desktop/systemd/merged-usr stable +arm64 default/linux/arm64/17.0/hardened/selinux exp +arm64 default/linux/arm64/17.0/desktop exp +arm64 default/linux/arm64/17.0/desktop/gnome exp +arm64 default/linux/arm64/17.0/desktop/gnome/systemd/merged-usr exp +arm64 default/linux/arm64/17.0/desktop/plasma exp +arm64 default/linux/arm64/17.0/desktop/plasma/systemd/merged-usr exp +arm64 default/linux/arm64/17.0/desktop/systemd/merged-usr exp arm64 default/linux/arm64/17.0/developer exp -arm64 default/linux/arm64/17.0/systemd/merged-usr stable +arm64 default/linux/arm64/17.0/systemd/merged-usr exp arm64 default/linux/arm64/17.0/systemd/selinux/merged-usr exp arm64 default/linux/arm64/17.0/llvm exp arm64 default/linux/arm64/17.0/systemd/llvm/merged-usr exp @@ -259,9 +259,9 @@ arm64 default/linux/arm64/23.0/split-usr/big-endian exp # HPPA Profiles # @MAINTAINER: hppa@gentoo.org -hppa default/linux/hppa/17.0 stable +hppa default/linux/hppa/17.0 exp hppa default/linux/hppa/17.0/systemd/merged-usr exp -hppa default/linux/hppa/17.0/desktop stable +hppa default/linux/hppa/17.0/desktop exp hppa default/linux/hppa/17.0/developer exp hppa default/linux/hppa/23.0/hppa1.1 stable hppa default/linux/hppa/23.0/hppa1.1/systemd stable @@ -277,39 +277,21 @@ hppa default/linux/hppa/23.0/hppa2.0/split-usr stable hppa default/linux/hppa/23.0/hppa2.0/split-usr/desktop exp -# IA64 Profiles -# @MAINTAINER: ia64@gentoo.org -ia64 default/linux/ia64/17.0 stable -ia64 default/linux/ia64/17.0/desktop stable -ia64 default/linux/ia64/17.0/desktop/gnome stable -ia64 default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr stable -ia64 default/linux/ia64/17.0/developer exp -ia64 default/linux/ia64/17.0/systemd/merged-usr exp -ia64 default/linux/ia64/23.0 stable -ia64 default/linux/ia64/23.0/desktop stable -ia64 default/linux/ia64/23.0/desktop/gnome stable -ia64 default/linux/ia64/23.0/desktop/gnome/systemd stable -ia64 default/linux/ia64/23.0/systemd stable -ia64 default/linux/ia64/23.0/split-usr stable -ia64 default/linux/ia64/23.0/split-usr/desktop exp -ia64 default/linux/ia64/23.0/split-usr/desktop/gnome exp - - # LoongArch Profiles # @MAINTAINER: loong@gentoo.org -loong default/linux/loong/22.0/la64v100/lp64d stable -loong default/linux/loong/22.0/la64v100/lp64d/desktop stable -loong default/linux/loong/22.0/la64v100/lp64d/desktop/gnome dev -loong default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/systemd dev -loong default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/systemd/merged-usr dev -loong default/linux/loong/22.0/la64v100/lp64d/desktop/plasma stable -loong default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/systemd stable -loong default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/systemd/merged-usr stable -loong default/linux/loong/22.0/la64v100/lp64d/desktop/systemd stable -loong default/linux/loong/22.0/la64v100/lp64d/desktop/systemd/merged-usr stable +loong default/linux/loong/22.0/la64v100/lp64d exp +loong default/linux/loong/22.0/la64v100/lp64d/desktop exp +loong default/linux/loong/22.0/la64v100/lp64d/desktop/gnome exp +loong default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/systemd exp +loong default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/systemd/merged-usr exp +loong default/linux/loong/22.0/la64v100/lp64d/desktop/plasma exp +loong default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/systemd exp +loong default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/systemd/merged-usr exp +loong default/linux/loong/22.0/la64v100/lp64d/desktop/systemd exp +loong default/linux/loong/22.0/la64v100/lp64d/desktop/systemd/merged-usr exp loong default/linux/loong/22.0/la64v100/lp64d/developer exp -loong default/linux/loong/22.0/la64v100/lp64d/systemd stable -loong default/linux/loong/22.0/la64v100/lp64d/systemd/merged-usr stable +loong default/linux/loong/22.0/la64v100/lp64d/systemd exp +loong default/linux/loong/22.0/la64v100/lp64d/systemd/merged-usr exp loong default/linux/loong/23.0/la64v100/lp64d stable loong default/linux/loong/23.0/la64v100/lp64d/llvm dev loong default/linux/loong/23.0/la64v100/lp64d/llvm/systemd dev @@ -358,60 +340,51 @@ mips default/linux/mips/17.0/mipsel/multilib/n32 exp mips default/linux/mips/17.0/mipsel/multilib/n32/systemd/merged-usr exp mips default/linux/mips/17.0/mipsel/multilib/n64 exp mips default/linux/mips/17.0/mipsel/multilib/n64/systemd/merged-usr exp -mips default/linux/mips/23.0/mipsel/o32_sf exp -mips default/linux/mips/23.0/mipsel/o32_sf/systemd exp -mips default/linux/mips/23.0/mipsel/o32 exp -mips default/linux/mips/23.0/mipsel/o32/systemd exp -mips default/linux/mips/23.0/mipsel/n32 exp -mips default/linux/mips/23.0/mipsel/n32/systemd exp -mips default/linux/mips/23.0/mipsel/n64 exp -mips default/linux/mips/23.0/mipsel/n64/systemd exp -mips default/linux/mips/23.0/mipsel/multilib/n32 exp -mips default/linux/mips/23.0/mipsel/multilib/n32/systemd exp -mips default/linux/mips/23.0/mipsel/multilib/n64 exp -mips default/linux/mips/23.0/mipsel/multilib/n64/systemd exp -mips default/linux/mips/23.0/o32_sf exp -mips default/linux/mips/23.0/o32_sf/systemd exp -mips default/linux/mips/23.0/o32 exp -mips default/linux/mips/23.0/o32/systemd exp -mips default/linux/mips/23.0/n32 exp -mips default/linux/mips/23.0/n32/systemd exp -mips default/linux/mips/23.0/n64 exp -mips default/linux/mips/23.0/n64/systemd exp -mips default/linux/mips/23.0/multilib/n32 exp -mips default/linux/mips/23.0/multilib/n32/systemd exp -mips default/linux/mips/23.0/multilib/n64 exp -mips default/linux/mips/23.0/multilib/n64/systemd exp -mips default/linux/mips/23.0/split-usr/mipsel/o32_sf exp -mips default/linux/mips/23.0/split-usr/mipsel/o32 exp -mips default/linux/mips/23.0/split-usr/mipsel/n32 exp -mips default/linux/mips/23.0/split-usr/mipsel/n64 exp -mips default/linux/mips/23.0/split-usr/mipsel/multilib/n32 exp -mips default/linux/mips/23.0/split-usr/mipsel/multilib/n64 exp -mips default/linux/mips/23.0/split-usr/o32_sf exp -mips default/linux/mips/23.0/split-usr/o32 exp -mips default/linux/mips/23.0/split-usr/n32 exp -mips default/linux/mips/23.0/split-usr/n64 exp -mips default/linux/mips/23.0/split-usr/multilib/n32 exp -mips default/linux/mips/23.0/split-usr/multilib/n64 exp - - -# Deprecated PPC64 Profiles -# @MAINTAINER: ppc64@gentoo.org -ppc default/linux/powerpc/ppc64/17.0/32bit-userland exp -ppc default/linux/powerpc/ppc64/17.0/32bit-userland/desktop exp -ppc default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome exp -ppc default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd exp -ppc default/linux/powerpc/ppc64/17.0/32bit-userland/developer exp +mips default/linux/mips/23.0/mipsel/o32_sf stable +mips default/linux/mips/23.0/mipsel/o32_sf/systemd stable +mips default/linux/mips/23.0/mipsel/o32 stable +mips default/linux/mips/23.0/mipsel/o32/systemd stable +mips default/linux/mips/23.0/mipsel/n32 stable +mips default/linux/mips/23.0/mipsel/n32/systemd stable +mips default/linux/mips/23.0/mipsel/n64 stable +mips default/linux/mips/23.0/mipsel/n64/systemd stable +mips default/linux/mips/23.0/mipsel/multilib/n32 dev +mips default/linux/mips/23.0/mipsel/multilib/n32/systemd dev +mips default/linux/mips/23.0/mipsel/multilib/n64 dev +mips default/linux/mips/23.0/mipsel/multilib/n64/systemd dev +mips default/linux/mips/23.0/o32_sf stable +mips default/linux/mips/23.0/o32_sf/systemd stable +mips default/linux/mips/23.0/o32 stable +mips default/linux/mips/23.0/o32/systemd stable +mips default/linux/mips/23.0/n32 stable +mips default/linux/mips/23.0/n32/systemd stable +mips default/linux/mips/23.0/n64 stable +mips default/linux/mips/23.0/n64/systemd stable +mips default/linux/mips/23.0/multilib/n32 dev +mips default/linux/mips/23.0/multilib/n32/systemd dev +mips default/linux/mips/23.0/multilib/n64 dev +mips default/linux/mips/23.0/multilib/n64/systemd dev +mips default/linux/mips/23.0/split-usr/mipsel/o32_sf dev +mips default/linux/mips/23.0/split-usr/mipsel/o32 dev +mips default/linux/mips/23.0/split-usr/mipsel/n32 dev +mips default/linux/mips/23.0/split-usr/mipsel/n64 stable +mips default/linux/mips/23.0/split-usr/mipsel/multilib/n32 dev +mips default/linux/mips/23.0/split-usr/mipsel/multilib/n64 dev +mips default/linux/mips/23.0/split-usr/o32_sf dev +mips default/linux/mips/23.0/split-usr/o32 dev +mips default/linux/mips/23.0/split-usr/n32 dev +mips default/linux/mips/23.0/split-usr/n64 stable +mips default/linux/mips/23.0/split-usr/multilib/n32 dev +mips default/linux/mips/23.0/split-usr/multilib/n64 dev # PPC profiles # @MAINTAINER: gyakovlev@gentoo.org, ppc@gentoo.org, musl@gentoo.org -ppc default/linux/ppc/17.0 stable -ppc default/linux/ppc/17.0/desktop stable -ppc default/linux/ppc/17.0/desktop/gnome stable -ppc default/linux/ppc/17.0/desktop/gnome/systemd/merged-usr stable -ppc default/linux/ppc/17.0/systemd/merged-usr stable +ppc default/linux/ppc/17.0 exp +ppc default/linux/ppc/17.0/desktop exp +ppc default/linux/ppc/17.0/desktop/gnome exp +ppc default/linux/ppc/17.0/desktop/gnome/systemd/merged-usr exp +ppc default/linux/ppc/17.0/systemd/merged-usr exp ppc default/linux/ppc/17.0/developer exp ppc default/linux/ppc/23.0 stable ppc default/linux/ppc/23.0/desktop stable @@ -425,11 +398,11 @@ ppc default/linux/ppc/23.0/split-usr/desktop/gnome stable # PPC64 profiles # @MAINTAINER: gyakovlev@gentoo.org, ppc64@gentoo.org, musl@gentoo.org -ppc64 default/linux/ppc64/17.0 stable -ppc64 default/linux/ppc64/17.0/desktop stable -ppc64 default/linux/ppc64/17.0/desktop/gnome stable -ppc64 default/linux/ppc64/17.0/desktop/gnome/systemd/merged-usr stable -ppc64 default/linux/ppc64/17.0/systemd/merged-usr stable +ppc64 default/linux/ppc64/17.0 exp +ppc64 default/linux/ppc64/17.0/desktop exp +ppc64 default/linux/ppc64/17.0/desktop/gnome exp +ppc64 default/linux/ppc64/17.0/desktop/gnome/systemd/merged-usr exp +ppc64 default/linux/ppc64/17.0/systemd/merged-usr exp ppc64 default/linux/ppc64/17.0/developer exp ppc64 default/linux/ppc64/23.0 stable ppc64 default/linux/ppc64/23.0/desktop stable @@ -443,14 +416,14 @@ ppc64 default/linux/ppc64/23.0/split-usr/desktop/gnome stable # PPC64LE profiles # @MAINTAINER: gyakovlev@gentoo.org, ppc64@gentoo.org, musl@gentoo.org -ppc64 default/linux/ppc64le/17.0 stable -ppc64 default/linux/ppc64le/17.0/desktop stable -ppc64 default/linux/ppc64le/17.0/desktop/gnome stable -ppc64 default/linux/ppc64le/17.0/desktop/gnome/systemd/merged-usr stable -ppc64 default/linux/ppc64le/17.0/desktop/plasma stable -ppc64 default/linux/ppc64le/17.0/desktop/plasma/systemd/merged-usr stable -ppc64 default/linux/ppc64le/17.0/desktop/systemd/merged-usr stable -ppc64 default/linux/ppc64le/17.0/systemd/merged-usr stable +ppc64 default/linux/ppc64le/17.0 exp +ppc64 default/linux/ppc64le/17.0/desktop exp +ppc64 default/linux/ppc64le/17.0/desktop/gnome exp +ppc64 default/linux/ppc64le/17.0/desktop/gnome/systemd/merged-usr exp +ppc64 default/linux/ppc64le/17.0/desktop/plasma exp +ppc64 default/linux/ppc64le/17.0/desktop/plasma/systemd/merged-usr exp +ppc64 default/linux/ppc64le/17.0/desktop/systemd/merged-usr exp +ppc64 default/linux/ppc64le/17.0/systemd/merged-usr exp ppc64 default/linux/ppc64le/17.0/developer exp ppc64 default/linux/ppc64le/17.0/ieee-long-double exp ppc64 default/linux/ppc64le/23.0 stable @@ -469,30 +442,30 @@ ppc64 default/linux/ppc64le/23.0/split-usr/desktop/plasma stable # RISC-V Profiles # @MAINTAINER: riscv@gentoo.org -riscv default/linux/riscv/20.0/rv64gc/lp64d stable -riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop dev -riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome dev -riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/systemd dev -riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/systemd/merged-usr dev -riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma dev -riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/systemd dev -riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/systemd/merged-usr dev -riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/systemd dev -riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/systemd/merged-usr dev -riscv default/linux/riscv/20.0/rv64gc/lp64d/systemd stable -riscv default/linux/riscv/20.0/rv64gc/lp64d/systemd/merged-usr stable -riscv default/linux/riscv/20.0/rv64gc/lp64 stable -riscv default/linux/riscv/20.0/rv64gc/lp64/desktop dev -riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome dev -riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/systemd dev -riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/systemd/merged-usr dev -riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma dev -riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/systemd dev -riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/systemd/merged-usr dev -riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/systemd dev -riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/systemd/merged-usr dev -riscv default/linux/riscv/20.0/rv64gc/lp64/systemd stable -riscv default/linux/riscv/20.0/rv64gc/lp64/systemd/merged-usr stable +riscv default/linux/riscv/20.0/rv64gc/lp64d exp +riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop exp +riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome exp +riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/systemd exp +riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/systemd/merged-usr exp +riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma exp +riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/systemd exp +riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/systemd/merged-usr exp +riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/systemd exp +riscv default/linux/riscv/20.0/rv64gc/lp64d/desktop/systemd/merged-usr exp +riscv default/linux/riscv/20.0/rv64gc/lp64d/systemd exp +riscv default/linux/riscv/20.0/rv64gc/lp64d/systemd/merged-usr exp +riscv default/linux/riscv/20.0/rv64gc/lp64 exp +riscv default/linux/riscv/20.0/rv64gc/lp64/desktop exp +riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome exp +riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/systemd exp +riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/systemd/merged-usr exp +riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma exp +riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/systemd exp +riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/systemd/merged-usr exp +riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/systemd exp +riscv default/linux/riscv/20.0/rv64gc/lp64/desktop/systemd/merged-usr exp +riscv default/linux/riscv/20.0/rv64gc/lp64/systemd exp +riscv default/linux/riscv/20.0/rv64gc/lp64/systemd/merged-usr exp riscv default/linux/riscv/20.0/rv64gc/multilib exp riscv default/linux/riscv/20.0/rv64gc/multilib/systemd exp riscv default/linux/riscv/20.0/rv64gc/multilib/systemd/merged-usr exp @@ -533,9 +506,9 @@ riscv default/linux/riscv/23.0/rv32/split-usr/ilp32 exp # S390 Profiles # @MAINTAINER: s390@gentoo.org -s390 default/linux/s390/17.0 stable -s390 default/linux/s390/17.0/s390x stable -s390 default/linux/s390/17.0/systemd/merged-usr stable +s390 default/linux/s390/17.0 exp +s390 default/linux/s390/17.0/s390x exp +s390 default/linux/s390/17.0/systemd/merged-usr exp s390 default/linux/s390/17.0/s390x/systemd/merged-usr exp s390 default/linux/s390/23.0 stable s390 default/linux/s390/23.0/systemd dev @@ -547,14 +520,14 @@ s390 default/linux/s390/23.0/s390x/systemd stable # SPARC Profiles # @MAINTAINER: sparc@gentoo.org -sparc default/linux/sparc/17.0 stable -sparc default/linux/sparc/17.0/desktop stable +sparc default/linux/sparc/17.0 exp +sparc default/linux/sparc/17.0/desktop exp sparc default/linux/sparc/17.0/developer exp -sparc default/linux/sparc/17.0/systemd/merged-usr stable -sparc default/linux/sparc/17.0/64ul stable -sparc default/linux/sparc/17.0/64ul/desktop stable +sparc default/linux/sparc/17.0/systemd/merged-usr exp +sparc default/linux/sparc/17.0/64ul exp +sparc default/linux/sparc/17.0/64ul/desktop exp sparc default/linux/sparc/17.0/64ul/developer exp -sparc default/linux/sparc/17.0/64ul/systemd/merged-usr stable +sparc default/linux/sparc/17.0/64ul/systemd/merged-usr exp sparc default/linux/sparc/23.0 stable sparc default/linux/sparc/23.0/desktop dev sparc default/linux/sparc/23.0/systemd dev @@ -570,16 +543,16 @@ sparc default/linux/sparc/23.0/split-usr/64ul/desktop stable # x86 Profiles # @MAINTAINER: x86@gentoo.org x86 default/linux/x86/17.0 stable -x86 default/linux/x86/17.0/selinux stable -x86 default/linux/x86/17.0/hardened stable -x86 default/linux/x86/17.0/hardened/selinux stable -x86 default/linux/x86/17.0/desktop stable -x86 default/linux/x86/17.0/desktop/gnome stable -x86 default/linux/x86/17.0/desktop/gnome/systemd/merged-usr stable -x86 default/linux/x86/17.0/desktop/plasma stable -x86 default/linux/x86/17.0/desktop/plasma/systemd/merged-usr stable +x86 default/linux/x86/17.0/selinux exp +x86 default/linux/x86/17.0/hardened exp +x86 default/linux/x86/17.0/hardened/selinux exp +x86 default/linux/x86/17.0/desktop exp +x86 default/linux/x86/17.0/desktop/gnome exp +x86 default/linux/x86/17.0/desktop/gnome/systemd/merged-usr exp +x86 default/linux/x86/17.0/desktop/plasma exp +x86 default/linux/x86/17.0/desktop/plasma/systemd/merged-usr exp x86 default/linux/x86/17.0/developer exp -x86 default/linux/x86/17.0/systemd/merged-usr stable +x86 default/linux/x86/17.0/systemd/merged-usr exp x86 default/linux/x86/23.0/i686 stable x86 default/linux/x86/23.0/i686/systemd stable x86 default/linux/x86/23.0/i686/hardened stable @@ -614,7 +587,7 @@ x86 default/linux/x86/23.0/i486/split-usr/hardened/selinux dev # musl profiles # @MAINTAINER: musl@gentoo.org -amd64 default/linux/amd64/17.0/musl dev +amd64 default/linux/amd64/17.0/musl exp amd64 default/linux/amd64/17.0/musl/clang exp amd64 default/linux/amd64/17.0/musl/hardened exp amd64 default/linux/amd64/17.0/musl/hardened/selinux exp @@ -626,10 +599,10 @@ amd64 default/linux/amd64/23.0/split-usr/musl dev amd64 default/linux/amd64/23.0/split-usr/musl/llvm exp amd64 default/linux/amd64/23.0/split-usr/musl/hardened exp amd64 default/linux/amd64/23.0/split-usr/musl/hardened/selinux exp -arm default/linux/arm/17.0/musl/armv6j dev +arm default/linux/arm/17.0/musl/armv6j exp arm default/linux/arm/17.0/musl/armv6j/hardened exp arm default/linux/arm/17.0/musl/armv6j/hardened/selinux exp -arm default/linux/arm/17.0/musl/armv7a dev +arm default/linux/arm/17.0/musl/armv7a exp arm default/linux/arm/17.0/musl/armv7a/hardened exp arm default/linux/arm/17.0/musl/armv7a/hardened/selinux exp arm default/linux/arm/23.0/armv6j_hf/musl dev @@ -644,7 +617,7 @@ arm default/linux/arm/23.0/split-usr/armv6j_hf/musl/hardened/selinux exp arm default/linux/arm/23.0/split-usr/armv7a_hf/musl dev arm default/linux/arm/23.0/split-usr/armv7a_hf/musl/hardened exp arm default/linux/arm/23.0/split-usr/armv7a_hf/musl/hardened/selinux exp -arm64 default/linux/arm64/17.0/musl dev +arm64 default/linux/arm64/17.0/musl exp arm64 default/linux/arm64/17.0/musl/llvm exp arm64 default/linux/arm64/17.0/musl/hardened exp arm64 default/linux/arm64/17.0/musl/hardened/selinux exp @@ -663,34 +636,34 @@ mips default/linux/mips/17.0/o32/musl exp mips default/linux/mips/17.0/n64/musl exp mips default/linux/mips/17.0/mipsel/o32/musl exp mips default/linux/mips/17.0/mipsel/n64/musl exp -mips default/linux/mips/23.0/mipsel/o32/musl exp +mips default/linux/mips/23.0/mipsel/o32/musl dev mips default/linux/mips/23.0/mipsel/n64/musl exp -mips default/linux/mips/23.0/o32/musl exp +mips default/linux/mips/23.0/o32/musl dev mips default/linux/mips/23.0/n64/musl exp mips default/linux/mips/23.0/split-usr/mipsel/o32/musl exp mips default/linux/mips/23.0/split-usr/mipsel/n64/musl exp mips default/linux/mips/23.0/split-usr/o32/musl exp mips default/linux/mips/23.0/split-usr/n64/musl exp -ppc default/linux/ppc/17.0/musl dev +ppc default/linux/ppc/17.0/musl exp ppc default/linux/ppc/17.0/musl/hardened exp ppc default/linux/ppc/23.0/musl dev ppc default/linux/ppc/23.0/musl/hardened exp ppc default/linux/ppc/23.0/split-usr/musl dev ppc default/linux/ppc/23.0/split-usr/musl/hardened exp -ppc64 default/linux/ppc64/17.0/musl dev +ppc64 default/linux/ppc64/17.0/musl exp ppc64 default/linux/ppc64/17.0/musl/hardened exp ppc64 default/linux/ppc64/23.0/musl dev ppc64 default/linux/ppc64/23.0/musl/hardened exp ppc64 default/linux/ppc64/23.0/split-usr/musl dev ppc64 default/linux/ppc64/23.0/split-usr/musl/hardened exp -ppc64 default/linux/ppc64le/17.0/musl dev +ppc64 default/linux/ppc64le/17.0/musl exp ppc64 default/linux/ppc64le/17.0/musl/hardened exp ppc64 default/linux/ppc64le/23.0/musl dev ppc64 default/linux/ppc64le/23.0/musl/hardened exp ppc64 default/linux/ppc64le/23.0/split-usr/musl dev ppc64 default/linux/ppc64le/23.0/split-usr/musl/hardened exp -riscv default/linux/riscv/20.0/rv64gc/lp64d/musl dev -riscv default/linux/riscv/20.0/rv64gc/lp64/musl dev +riscv default/linux/riscv/20.0/rv64gc/lp64d/musl exp +riscv default/linux/riscv/20.0/rv64gc/lp64/musl exp riscv default/linux/riscv/23.0/rv64/lp64d/musl dev riscv default/linux/riscv/23.0/rv64/lp64/musl dev riscv default/linux/riscv/23.0/rv64/split-usr/lp64d/musl dev @@ -699,7 +672,7 @@ riscv default/linux/riscv/23.0/rv32/ilp32d/musl exp riscv default/linux/riscv/23.0/rv32/ilp32/musl exp riscv default/linux/riscv/23.0/rv32/split-usr/ilp32d/musl exp riscv default/linux/riscv/23.0/rv32/split-usr/ilp32/musl exp -x86 default/linux/x86/17.0/musl dev +x86 default/linux/x86/17.0/musl exp x86 default/linux/x86/17.0/musl/selinux exp x86 default/linux/x86/23.0/i686/musl dev x86 default/linux/x86/23.0/i686/musl/selinux exp @@ -752,12 +725,14 @@ x64-macos prefix/darwin/macos/12.0/x64 exp x64-macos prefix/darwin/macos/12.0/x64/gcc exp x64-macos prefix/darwin/macos/13.0/x64/gcc exp x64-macos prefix/darwin/macos/14.0/x64/gcc exp +x64-macos prefix/darwin/macos/15.0/x64/gcc exp arm64-macos prefix/darwin/macos/11.0/arm64 exp arm64-macos prefix/darwin/macos/11.0/arm64/gcc exp arm64-macos prefix/darwin/macos/12.0/arm64 exp arm64-macos prefix/darwin/macos/12.0/arm64/gcc exp arm64-macos prefix/darwin/macos/13.0/arm64/gcc exp arm64-macos prefix/darwin/macos/14.0/arm64/gcc exp +arm64-macos prefix/darwin/macos/15.0/arm64/gcc exp # Solaris Profiles x64-solaris prefix/sunos/solaris/5.11/x64 exp diff --git a/profiles/targets/desktop/gnome/make.defaults b/profiles/targets/desktop/gnome/make.defaults index 3f9e6955f3b8..2dc85fe967ca 100644 --- a/profiles/targets/desktop/gnome/make.defaults +++ b/profiles/targets/desktop/gnome/make.defaults @@ -1,4 +1,4 @@ # Copyright 1999-2023 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -USE="colord eds evo gnome gnome-keyring gnome-online-accounts gnome-shell gstreamer introspection keyring nautilus networkmanager pulseaudio sysprof tracker wayland" +USE="colord eds evo gnome gnome-keyring gnome-online-accounts gnome-shell gstreamer introspection keyring nautilus networkmanager pulseaudio sysprof tracker" diff --git a/profiles/targets/desktop/gnome/package.use b/profiles/targets/desktop/gnome/package.use index 3914d0992c9e..a60190ee8b3e 100644 --- a/profiles/targets/desktop/gnome/package.use +++ b/profiles/targets/desktop/gnome/package.use @@ -1,15 +1,6 @@ # Copyright 1999-2023 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -# Alfred Wingate <parona@protonmail.com> (2023-12-25) -# Prefer wayland over X with REQUIRED_USE: ^^ ( gbm wayland X ) ->=media-tv/kodi-20.2 wayland -X - -# Mart Raudsepp <leio@gentoo.org> (2023-10-01) -# x11-wm/mutter[wayland] requires xwayland[libei] for emulated input portal -# for e.g. remote desktop remote input support -x11-base/xwayland libei - # Mart Raudsepp <leio@gentoo.org> (2022-01-05) # gnome-boxes requires spice-gtk[vala] net-misc/spice-gtk vala @@ -32,15 +23,6 @@ dev-libs/efl sound # Needed by gnome-photos media-libs/gegl raw -# Needed by a global USE=wayland right now; some REQUIRED_USE may be outdated and need review ->=media-libs/cogl-1.18.2-r1 gles2 ->=media-libs/clutter-1.20 egl -media-libs/cogl kms -media-libs/libsdl2 gles2 - -# Needed by mutter defaults and USE=wayland, bug #547300 ->=media-libs/mesa-10.3 gles2 - # For eautoreconf in =app-crypt/seahorse-3.10.2-r1 app-crypt/gcr vala diff --git a/profiles/targets/desktop/make.defaults b/profiles/targets/desktop/make.defaults index caccdbdd22a3..3e4f9fd3998b 100644 --- a/profiles/targets/desktop/make.defaults +++ b/profiles/targets/desktop/make.defaults @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -USE="a52 aac acpi alsa bluetooth branding cairo cdda cdr cups dbus dri dts dvd dvdr elogind encode exif flac gif gpm gtk gui icu jpeg lcms libnotify mad mng mp3 mp4 mpeg ogg opengl pango pdf png policykit ppds qt5 sdl sound spell startup-notification svg tiff truetype vorbis udev udisks unicode upower usb vulkan wxwidgets X xcb xft x264 xml xv xvid" +USE="a52 aac acpi alsa bluetooth branding cairo cdda cdr cups dbus dri dts dvd dvdr elogind encode exif flac gif gpm gtk gui icu jpeg kf6compat lcms libnotify mad mng mp3 mp4 mpeg ogg opengl pango pdf png policykit ppds qml qt6 qt5 sdl sound spell startup-notification svg tiff truetype vorbis udev udisks unicode upower usb vulkan wayland wxwidgets X xcb xft x264 xml xv xvid" diff --git a/profiles/targets/desktop/package.use b/profiles/targets/desktop/package.use index 0822e94248e9..bf9f420beb1e 100644 --- a/profiles/targets/desktop/package.use +++ b/profiles/targets/desktop/package.use @@ -1,14 +1,15 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner <asturm@gentoo.org> (2024-08-30) +# Resolve conflicting REQUIRED_USE defaults (qt5 vs. qt6) +media-libs/simage -qt5 +net-p2p/transmission -qt5 + # Andreas Sturmlechner <asturm@gentoo.org> (2024-03-07) # Required by kde-frameworks/kio:6 dev-qt/qtbase libproxy -# Alfred Wingate <parona@protonmail.com> (2023-12-25) -# Prefer X over gbm with REQUIRED_USE: ^^ ( gbm wayland X ) ->=media-tv/kodi-20.2 X -gbm - # Andreas Sturmlechner <asturm@gentoo.org> (2023-11-12) # NSS: Required by kde-apps/okular[pdf] # Boost: app-text/poppler[qt5] recommended w/ Boost (bug #795888) @@ -19,6 +20,11 @@ app-text/poppler nss boost # accessibility required by kde-plasma/kwin:5 dev-qt/qtgui:5 accessibility egl libinput +# Mart Raudsepp <leio@gentoo.org> (2023-10-01) +# kde-plasma/kwin and x11-wm/mutter[wayland] require xwayland[libei] for +# emulated input portal for e.g. remote desktop remote input support +x11-base/xwayland libei + # Sam James <sam@gentoo.org> (2023-09-22) # Most people aren't going to use CMake's GUI. USE=gui is enabled by default # on desktop profiles and CMake is unavoidable, it feels a shame to drag in @@ -30,6 +36,13 @@ dev-build/cmake -gui -qt6 # Required by dev-python/PyQt5[multimedia] dev-qt/qtmultimedia:5 widgets +# Andreas Sturmlechner <asturm@gentoo.org> (2023-05-21) +# Needed by a global USE=wayland right now (REQUIRED_USE conflicts) +media-libs/clutter egl +media-libs/cogl gles2 +media-libs/libsdl2 gles2 +<media-libs/mesa-24.1 gles2 + # Alexey Sokolov <alexey+gentoo@asokolov.org> (2022-12-27) # On desktops it's common to use browser to browse internet, which these # days is full of emojis, which wouldn't render properly without the fonts. diff --git a/profiles/targets/desktop/package.use.force b/profiles/targets/desktop/package.use.force index 77925d886d5a..a95659f9f08d 100644 --- a/profiles/targets/desktop/package.use.force +++ b/profiles/targets/desktop/package.use.force @@ -3,9 +3,10 @@ # Andreas Sturmlechner <asturm@gentoo.org> (2024-03-10) # Ensure that KF5- and Qt5-based applications, of which there are still -# many (even as part of KDE Gear 24.02), will not exhibit bugs and look -# out of place in Plasma 6 sessions. -=kde-plasma/plasma-meta-6.0*:6 qt5 +# many (even as part of KDE Gear 24.05), will not exhibit bugs and look +# out of place in Plasma 6 sessions. Do *not* file upstream bugs for Qt5- +# based packages if unsetting this. +<kde-plasma/plasma-meta-6.1.80:6 qt5 # Alexandre Rostovtsev <tetromino@gentoo.org> (2014-06-03) # Ensure shared-mime-info is pulled in by glib, otherwise GNOME, XFCE, and diff --git a/profiles/targets/desktop/plasma/make.defaults b/profiles/targets/desktop/plasma/make.defaults index 62e625bbfdcb..952f3e112e02 100644 --- a/profiles/targets/desktop/plasma/make.defaults +++ b/profiles/targets/desktop/plasma/make.defaults @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -USE="activities declarative dri kde kwallet networkmanager pipewire plasma policykit pulseaudio qml screencast semantic-desktop wayland widgets" +USE="activities declarative dri kde kwallet networkmanager pipewire plasma policykit pulseaudio screencast semantic-desktop widgets" diff --git a/profiles/targets/desktop/plasma/package.use b/profiles/targets/desktop/plasma/package.use index 60ec3645b00c..f72f96ede24e 100644 --- a/profiles/targets/desktop/plasma/package.use +++ b/profiles/targets/desktop/plasma/package.use @@ -1,10 +1,6 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -# Alfred Wingate <parona@protonmail.com> (2023-12-25) -# Prefer wayland over X with REQUIRED_USE: ^^ ( gbm wayland X ) ->=media-tv/kodi-20.2 wayland -X - # Marek Szuba <marecki@gentoo.org> (2023-11-12) # FUSE cannot be built with multiple audio drivers, and desktop/gnome # profiles set both USE=pulseaudio (directly) and USE=alsa (inherited @@ -20,18 +16,12 @@ dev-libs/libjcat gpg pkcs7 # qtwebchannel package is fairly small, and python bindings are # required by some popular desktop packages such as calibre, # qutebrowser, and freecad (or indirectly through PyQt*WebEngine). -dev-python/PyQt5 webchannel dev-python/PyQt6 webchannel -dev-python/pyside2 designer location positioning quick -dev-python/pyside2 printsupport webchannel dev-python/pyside6 webchannel # Required by sys-apps/flatpak, a dependency of kde-plasma/discover dev-util/ostree curl -# Required by <net-im/neochat-23.08.50 -dev-qt/qtmultimedia:5 gstreamer - # Required by app-editors/okteta:5 dev-qt/qtscript:5 scripttools @@ -41,18 +31,12 @@ dev-qt/qtsql:5 mysql # Enable by default, requires kde-frameworks/kwayland kde-apps/yakuake absolute-position -# Required by kde-frameworks/kapidox -media-gfx/graphviz python +# Required by kde-plasma/plasma-workspace, in ksmserver +kde-plasma/kde-cli-tools kdesu # Required by media-gfx/graphviz which is required by kde-apps/kcachegrind media-libs/gd fontconfig -# Needed by a global USE=wayland right now -media-libs/libsdl2 gles2 - -# Required by kde-plasma/kwin -media-libs/mesa wayland - # Required by kde-apps/kdenlive media-libs/mlt ffmpeg frei0r rubberband @@ -67,9 +51,7 @@ net-firewall/nftables json python xtables sys-libs/zlib minizip # Keep existing defaults after dropping IUSE=phonon from make.defaults -<app-office/calligra-3.3 phonon kde-apps/kio-extras phonon -kde-apps/kio-extras-kf5 phonon kde-apps/marble phonon # Required by kde-plasma/plasma-meta @@ -77,7 +59,3 @@ kde-plasma/kwin lock # plasma profile never enabled pulseaudio. We're skipping to pipewire. media-video/pipewire sound-server - -# Expected to be available by default in Plasma -kde-frameworks/purpose kaccounts -kde-plasma/plasma-desktop kaccounts diff --git a/profiles/thirdpartymirrors b/profiles/thirdpartymirrors index dadd208df8ec..bb5398896976 100644 --- a/profiles/thirdpartymirrors +++ b/profiles/thirdpartymirrors @@ -6,17 +6,17 @@ gcc https://gcc.gnu.org/pub/gcc/ http://mirrors.concertpass.com/gcc/ https://mi gimp https://ftp.fau.de/gimp/gimp/ ftp://ftp.fau.de/gimp/gimp/ https://artfiles.org/gimp.org/pub/gimp/ https://www.mirrorservice.org/sites/ftp.gimp.org/pub/gimp/ ftp://ftp.mirrorservice.org/sites/ftp.gimp.org/pub/gimp/ gnome https://download.gnome.org/ gnu https://ftp.gnu.org/gnu/ https://artfiles.org/gnu.org/ https://www.mirrorservice.org/sites/ftp.gnu.org/gnu/ -gnupg https://www.mirrorservice.org/sites/ftp.gnupg.org/gcrypt/ https://ftp.heanet.ie/mirrors/ftp.gnupg.org/gcrypt/ https://mirrors.dotsrc.org/gcrypt/ https://gnupg.org/ftp/gcrypt/ ftp://ftp.gnupg.org/gcrypt/ +gnupg https://www.mirrorservice.org/sites/ftp.gnupg.org/gcrypt/ https://mirrors.dotsrc.org/gcrypt/ https://gnupg.org/ftp/gcrypt/ ftp://ftp.gnupg.org/gcrypt/ goproxy https://proxy.golang.org/ https://goproxy.io/ idsoftware ftp://ftp.fu-berlin.de/pc/games/idgames/idstuff ftp://ftp.gamers.org/pub/idgames/idstuff imagemagick https://imagemagick.org/archive/releases/ https://mirror.checkdomain.de/imagemagick/releases/ https://ftp.acc.umu.se/mirror/imagemagick.org/ftp/releases/ ftp://ftp.fifi.org/pub/ImageMagick/releases/ kde https://download.kde.org https://mirror.csclub.uwaterloo.ca/kde ftp://mirrors.dotsrc.org/kde http://kde.mirror.anlx.net lokigames http://updates.lokigames.com -mariadb https://archive.mariadb.org/ http://ftp.bme.hu/pub/mirrors/mariadb/ https://ftp.heanet.ie/mirrors/mariadb/ https://ftp.nluug.nl/db/mariadb/ https://mirrors.up.pt/pub/mariadb/ https://rsync.osuosl.org/pub/mariadb/ https://mirror.netcologne.de/mariadb/ +mariadb https://archive.mariadb.org/ http://ftp.bme.hu/pub/mirrors/mariadb/ https://ftp.nluug.nl/db/mariadb/ https://mirrors.up.pt/pub/mariadb/ https://rsync.osuosl.org/pub/mariadb/ https://mirror.netcologne.de/mariadb/ mplayer https://www1.mplayerhq.hu/MPlayer http://www2.mplayerhq.hu/MPlayer http://www7.mplayerhq.hu/MPlayer http://www8.mplayerhq.hu/MPlayer ftp://ftp1.mplayerhq.hu/MPlayer/ ftp://ftp6.mplayerhq.hu/MPlayer/ ftp://ftp7.mplayerhq.hu/MPlayer/ ftp://ftp8.mplayerhq.hu/MPlayer/ nongnu https://download.savannah.nongnu.org/releases/ https://ftp.cc.uoc.gr/mirrors/nongnu.org/ http://ftp.twaren.net/Unix/NonGNU/ https://mirror.csclub.uwaterloo.ca/nongnu/ ftp://mirror.csclub.uwaterloo.ca/nongnu/ https://mirrors.fe.up.pt/pub/nongnu/ ftp://mirrors.fe.up.pt/pub/nongnu/ https://nongnu.askapache.com/ https://nongnu.uib.no/ ftp://nongnu.uib.no/pub/nongnu/ http://savannah.c3sl.ufpr.br/ ftp://ftp.twaren.net/Unix/NonGNU/ openbsd https://cdn.openbsd.org/pub/OpenBSD https://fastly.cdn.openbsd.org/pub/OpenBSD -openssl https://www.openssl.org/ https://artfiles.org/openssl.org/ https://www.mirrorservice.org/sites/ftp.openssl.org/ ftp://ftp.openssl.org +openssl https://www.openssl.org/ https://artfiles.org/openssl.org/ https://www.mirrorservice.org/sites/ftp.openssl.org/ sourceforge.jp http://iij.dl.sourceforge.jp https://osdn.dl.sourceforge.jp https://jaist.dl.sourceforge.jp ubuntu http://mirror.internode.on.net/pub/ubuntu/ubuntu/ http://ubuntu.uni-klu.ac.at/ubuntu/ http://mirror.dhakacom.com/ubuntu-archive/ http://ubuntu.c3sl.ufpr.br/ubuntu/ http://hr.archive.ubuntu.com/ubuntu/ http://cz.archive.ubuntu.com/ubuntu/ https://mirror.dkm.cz/ubuntu http://ftp.cvut.cz/ubuntu/ http://ftp.stw-bonn.de/ubuntu/ https://ftp-stud.hs-esslingen.de/ubuntu/ https://mirror.netcologne.de/ubuntu/ https://mirror.unej.ac.id/ubuntu/ http://kr.archive.ubuntu.com/ubuntu/ https://mirror.nforce.com/pub/linux/ubuntu/ http://nl3.archive.ubuntu.com/ubuntu/ https://mirror.timeweb.ru/ubuntu/ http://ubuntu.mirror.su.se/ubuntu/ https://ubuntu.volia.net/ubuntu-archive/ https://mirror.pnl.gov/ubuntu/ https://mirrors.namecheap.com/ubuntu/ vdr-developerorg http://projects.vdr-developer.org/attachments/download diff --git a/profiles/updates/1Q-2024 b/profiles/updates/1Q-2024 index 8076671c9fdb..05eb97ac02e0 100644 --- a/profiles/updates/1Q-2024 +++ b/profiles/updates/1Q-2024 @@ -7,7 +7,6 @@ move app-doc/psmark app-text/psmark move app-doc/xmltoman app-text/xmltoman move app-doc/zeal app-text/zeal move sys-devel/gdb dev-debug/gdb -move sys-devel/gdb-apple dev-debug/gdb-apple move dev-util/lldb dev-debug/lldb move dev-util/cgdb dev-debug/cgdb move dev-util/ninja dev-build/ninja @@ -47,7 +46,6 @@ move dev-util/scons dev-build/scons move sys-devel/qconf dev-build/qconf move dev-util/b2 dev-build/b2 move dev-util/kbuild dev-build/kbuild -move dev-util/ald dev-debug/ald move dev-util/ddd dev-debug/ddd move dev-util/edb-debugger dev-debug/edb-debugger move dev-util/kdbg dev-debug/kdbg diff --git a/profiles/updates/2Q-2024 b/profiles/updates/2Q-2024 index 2676c36b6d95..ecf22219d7a5 100644 --- a/profiles/updates/2Q-2024 +++ b/profiles/updates/2Q-2024 @@ -5,3 +5,9 @@ slotmove dev-java/icu4j 70 0 move dev-python/django_polymorphic dev-python/django-polymorphic move dev-python/octave_kernel dev-python/octave-kernel slotmove kde-apps/kdeedu-data 5 0 +move dev-perl/Term-Table perl-core/Term-Table +move dev-perl/Test2-Suite perl-core/Test2-Suite +move dev-python/et_xmlfile dev-python/et-xmlfile +move dev-python/qiskit-terra dev-python/qiskit +move dev-python/jupyterlab_widgets dev-python/jupyterlab-widgets +move dev-python/pyyaml_env_tag dev-python/pyyaml-env-tag diff --git a/profiles/updates/3Q-2020 b/profiles/updates/3Q-2020 index 3f451f53e7f7..3e54e401cfa6 100644 --- a/profiles/updates/3Q-2020 +++ b/profiles/updates/3Q-2020 @@ -10,5 +10,5 @@ slotmove <media-sound/teamspeak-client-5 0 3 slotmove dev-haskell/network 3 0 move sci-libs/scipy dev-python/scipy move dev-perl/frontier-rpc dev-perl/Frontier-RPC -move sci-libs/Rtree sci-libs/rtree +move sci-libs/Rtree dev-python/rtree move sci-libs/Shapely dev-python/shapely diff --git a/profiles/updates/3Q-2023 b/profiles/updates/3Q-2023 index 35c455f3127e..0edbbf5276cb 100644 --- a/profiles/updates/3Q-2023 +++ b/profiles/updates/3Q-2023 @@ -11,7 +11,6 @@ move dev-python/nest_asyncio dev-python/nest-asyncio move dev-python/libcloud dev-python/apache-libcloud move dev-python/uri_template dev-python/uri-template move dev-python/pykerberos dev-python/kerberos -move dev-python/rapidfuzz_capi dev-python/rapidfuzz-capi move dev-python/line_profiler dev-python/line-profiler move dev-libs/paho-mqtt-c net-libs/paho-mqtt-c move dev-lisp/ecls dev-lisp/ecl diff --git a/profiles/updates/3Q-2024 b/profiles/updates/3Q-2024 new file mode 100644 index 000000000000..ade5eb7db7ba --- /dev/null +++ b/profiles/updates/3Q-2024 @@ -0,0 +1,11 @@ +move sci-libs/rtree dev-python/rtree +move dev-python/mapbox_earcut dev-python/mapbox-earcut +move dev-qt/kdsingleapplication dev-libs/kdsingleapplication +slotmove dev-util/kdevelop-pg-qt 5 0 +move dev-python/parse_type dev-python/parse-type +slotmove app-admin/calamares 5 0 +slotmove x11-misc/kronometer 5 0 +slotmove app-dicts/dikt 5 0 +slotmove app-cdr/kcdemu 5 0 +move sys-apps/azure-nvme-utils sys-apps/azure-vm-utils +move dev-python/sphinx-aiohttp-theme dev-python/aiohttp-theme diff --git a/profiles/use.local.desc b/profiles/use.local.desc index 8f89b2e931c4..0b57adadf1d7 100644 --- a/profiles/use.local.desc +++ b/profiles/use.local.desc @@ -42,6 +42,7 @@ app-admin/clsync:socket-library - Build the control and monitoring socket librar app-admin/conky:apcupsd - Enable support for sys-power/apcupsd app-admin/conky:bundled-toluapp - Enable support for bundled toluapp. This only makes sense in combination with the lua-* flags app-admin/conky:cmus - Enable monitoring of music played by media-sound/cmus +app-admin/conky:colour-name-map - Include mappings of colour name app-admin/conky:extras - Enable syntax highlighting for app-editors/nanoand app-editors/vim app-admin/conky:ical - Enable support for events from iCalendar (RFC 5545) files using dev-libs/libical app-admin/conky:intel-backlight - Enable support for Intel backlight @@ -53,11 +54,13 @@ app-admin/conky:lua-imlib - Enable if you want Lua Imlib2 bindings app-admin/conky:lua-rsvg - Enable if you want Lua RSVG bindings app-admin/conky:math - Enable support for glibc's libm math library app-admin/conky:moc - Enable monitoring of music played by media-sound/moc +app-admin/conky:mouse-events - Enable support for mouse events" app-admin/conky:mpd - Enable monitoring of music controlled by media-sound/mpd app-admin/conky:nvidia - Enable reading of nvidia card temperature sensors via x11-drivers/nvidia-drivers app-admin/conky:portmon - Enable support for tcp (ip4) port monitoring app-admin/conky:thinkpad - Enable support for IBM/Lenovo notebooks app-admin/conky:webserver - Enable support to act as a webserver serving conkys output using net-libs/libmicrohttpd +app-admin/conky:xinput - Enable support for Xinput 2 (slow) app-admin/conky:xmms2 - Enable monitoring of music played by media-sound/xmms2 app-admin/conserver:freeipmi - Compile in FreeIPMI support via sys-libs/freeipmi app-admin/diradm:automount - Support for automount data in LDAP @@ -247,11 +250,10 @@ app-arch/libarchive:blake2 - Enable Blake2 hash support via app-crypt/libb2. app-arch/libarchive:bzip2 - Allow accessing bzip2-compressed archives through libbz2 (which comes with app-arch/bzip2). This only affects libarchive's native support: bsdtar will keep using bunzip2 as a filter if that's not built-in. app-arch/libarchive:e2fsprogs - Use file flags from sys-fs/e2fsprogs headers instead of virtual/os-headers headers app-arch/libarchive:nettle - Use dev-libs/nettle as crypto backend -app-arch/libdeflate:gzip - Support the gzip format app-arch/libdeflate:test - Build the test programs (requires sys-libs/zlib) app-arch/libdeflate:utils - Build the libdeflate-gzip program -app-arch/libdeflate:zlib - Support the zlib format -app-arch/lrzip-next:year2038 - Enables support for timestamps after the year 2038 +app-arch/lrzip-next:largefile - Enables support for large files +app-arch/lrzip-next:year2038 - Enables support for 64-bit 'time_t' (sets D_TIME_BITS=64; glibc only) app-arch/p7zip:natspec - Use dev-libs/libnatspec to correctly decode non-ascii file names archived in Windows. app-arch/p7zip:rar - Enable support for non-free rar decoder app-arch/rar:all-sfx - Install all SFX (Self-Extracting) files rather than just the native format (allows creation of Windows EXEs on Linux ELF systems) @@ -330,8 +332,8 @@ app-containers/crun:bpf - Enable in Kernel, eBPF (enhanced Berkley Packet Filter app-containers/crun:criu - Enable CRIU based checkpoint/restore support app-containers/docker:btrfs - Enables dependencies for the "btrfs" graph driver, including necessary kernel flags. app-containers/docker:container-init - Makes the a staticly-linked init system tini available inside a container. -app-containers/docker:device-mapper - Enables dependencies for the "devicemapper" graph driver, including necessary kernel flags. app-containers/docker:overlay - Enables dependencies for the "overlay" graph driver, including necessary kernel flags. +app-containers/docker:overlay2 - Enables dependencies for the "overlay2" graph driver, including necessary kernel flags. app-containers/docker-credential-helpers:pass - Build pass helper for the pass utility. app-containers/incus:fuidshift - Install the fuidshift binary - currently conflicts with app-containers/lxd app-containers/lxc:io-uring - Enable io_uring support, and use io_uring instead of epoll @@ -450,7 +452,6 @@ app-editors/emacs:threads - Add elisp threading support app-editors/emacs:toolkit-scroll-bars - Use the selected toolkit's scrollbars in preference to Emacs' own scrollbars app-editors/emacs:tree-sitter - Support the dev-libs/tree-sitter parsing library app-editors/emacs:wide-int - Prefer wide Emacs integers (typically 62-bit). This option has an effect only on architectures where "long" and "long long" types have different size. -app-editors/emacs:xwidgets - Enable use of GTK widgets in Emacs buffers (requires GTK3) app-editors/fe:sendmail - Send mail after editor abend app-editors/featherpad:X - Link application against X11 libraries which adds support for virtual desktop awareness and tab DND app-editors/gedit-plugins:charmap - Insert special characters just by clicking on them @@ -473,15 +474,8 @@ app-editors/nano:magic - Add magic file support (sys-apps/file) to automatically app-editors/nano:minimal - Disable all fancy features, including ones that otherwise have a dedicated USE flag (such as spelling). app-editors/neovim:nvimpager - Install nvimpager symlink to less.sh macro app-editors/okteta:designer - Build plugins for dev-qt/designer -app-editors/pluma-plugins:bracketcompletion - Auto complete bracket pairs -app-editors/pluma-plugins:codecomment - Comment code blocks -app-editors/pluma-plugins:smartspaces - Insert smart spaces -app-editors/pluma-plugins:synctex - Enable synctex support for pdflatex -app-editors/pluma-plugins:terminal - Embed a terminal in the bottom pane app-editors/qhexedit2:gui - Install Qt5 hex editor app-editors/tea:aspell - Enable spellchecking using app-text/aspell -app-editors/tea:hunspell - Enable spellchecking using app-text/hunspell -app-editors/tea:qml - Enable support for plugins using QML app-editors/vim:X - Link console vim against X11 libraries to enable title and clipboard features in xterm app-editors/vim:crypt - Use dev-libs/libsodium for crypto support app-editors/vim:cscope - Enable cscope interface @@ -521,7 +515,6 @@ app-emacs/sly:xref - Install xref.lisp cross-referencing tool app-emacs/vm:bbdb - Include support for app-emacs/bbdb app-emacs/wanderlust:bbdb - Include support for app-emacs/bbdb app-emacs/wikipedia-mode:outline-magic - Enable support for outline-mode extensions (app-emacs/outline-magic) -app-emulation/86Box:dinput - Enable legacy Dinput mode instead of Xinput for older controllers. app-emulation/86Box:experimental - Enable hardware from devbranch, which may be unstable or unusable. app-emulation/86Box:fluidsynth - Enable MIDI support through media-sound/fluidsynth. app-emulation/86Box:munt - Enable MIDI MT-32 support through media-libs/munt-mt32emu. @@ -544,6 +537,7 @@ app-emulation/dosemu:fluidsynth - use media-sound/fluidsynth for MIDI emulation app-emulation/dxvk:crossdev-mingw - Use sys-devel/crossdev for the toolchain rather than dev-util/mingw64-toolchain (requires manual setting up) app-emulation/dxvk:d3d10 - Enable support for DirectX 10 (d3d10.dll) app-emulation/dxvk:d3d11 - Enable support for DirectX 11 (d3d11.dll) +app-emulation/dxvk:d3d8 - Enable support for DirectX 8 (d3d8.dll) app-emulation/dxvk:d3d9 - Enable support for DirectX 9 (d3d9.dll) app-emulation/dxvk:dxgi - Enable support for the DirectX Graphics Infrastructure (dxgi.dll) app-emulation/faudio:dumpvoices - FAudio dumps buffer data to individual files with RIFF/XWMA headers, usable with players like ffplay/testxwma. @@ -560,8 +554,6 @@ app-emulation/fuse-utils:gcrypt - Use dev-libs/libgcrypt for low-level crypto of app-emulation/grub-xen-host:pvh - Build an additional grub bin for pvh. app-emulation/hercules-sdl:object-rexx - Enable REXX support via Open Object Rexx (dev-lang/oorexx) app-emulation/hercules-sdl:regina-rexx - Enable REXX support via Regina Rexx (dev-lang/regina-rexx) -app-emulation/hyperd:libvirt - Enable support for KVM via libvirt -app-emulation/hyperd:xen - Enable support for the Xen Hypervisor app-emulation/libcacard:passthrough - Enable smartcard passthrough support via sys-apps/pcsc-lite app-emulation/libguestfs:erlang - Build Erlang bindings app-emulation/libguestfs:fuse - Enable image mount support via sys-fs/fuse @@ -644,7 +636,7 @@ app-emulation/qemu:spice - Enable Spice protocol support via app-emulation/spice app-emulation/qemu:ssh - Enable SSH based block device support via net-libs/libssh2 app-emulation/qemu:static - Build the User and Software MMU (system) targets as well as tools as static binaries app-emulation/qemu:static-user - Build the User targets as static binaries -app-emulation/qemu:systemtap - Enable SystemTAP/DTrace tracing +app-emulation/qemu:systemtap - Enable SystemTap/DTrace tracing app-emulation/qemu:usb - Enable USB passthrough via dev-libs/libusb app-emulation/qemu:usbredir - Use sys-apps/usbredir to redirect USB devices to another machine over TCP app-emulation/qemu:vde - Enable VDE-based networking @@ -653,6 +645,7 @@ app-emulation/qemu:virgl - Enable experimental Virgil 3d (virtual software GPU) app-emulation/qemu:virtfs - Enable VirtFS via virtio-9p-pci / fsdev. See https://wiki.qemu.org/Documentation/9psetup app-emulation/qemu:vte - Enable terminal support (x11-libs/vte) in the GTK+ interface app-emulation/qemu:xattr - Add support for getting and setting POSIX extended attributes, through sys-apps/attr. Requisite for the virtfs backend. +app-emulation/qemu:xdp - Enable support for XDP through net-libs/xdp-tools app-emulation/qemu:xen - Enables support for Xen backends app-emulation/ski:debug - enable extra binary emulation debugging via sys-libs/binutils-libs app-emulation/spice:smartcard - Enable smartcard remoting using app-emulation/libcacard @@ -669,25 +662,28 @@ app-emulation/virt-viewer:spice - Support connecting to SPICE-enabled virtual ma app-emulation/virt-viewer:vnc - Support connecting to VNC-enabled virtual machines. app-emulation/virt-viewer:vte - Enable terminal support (x11-libs/vte) in the GTK+ interface app-emulation/virt-what:dmi - Use sys-apps/dmidecode to read firmware data -app-emulation/virtualbox:dtrace - Install dtrace Extension Pack -app-emulation/virtualbox:headless - Build without any graphic frontend +app-emulation/virtualbox:dtrace - Install dtrace Extension Pack. +app-emulation/virtualbox:headless - Build without any graphic frontend. app-emulation/virtualbox:lvm - Build VBoxVolInfo that needs devicemapper from sys-fs/lvm2. app-emulation/virtualbox:pax-kernel - Apply patch needed for pax enabled kernels. -app-emulation/virtualbox:sdk - Enable building of SDK +app-emulation/virtualbox:sdk - Enable building of SDK. app-emulation/virtualbox:udev - Controls installation of special USB udev rules. -app-emulation/virtualbox:vboxwebsrv - Build and install the VirtualBox webservice -app-emulation/virtualbox:vde - Support for VDE networking via net-misc/vde +app-emulation/virtualbox:vboxwebsrv - Build and install the VirtualBox webservice. +app-emulation/virtualbox:vde - Support for VDE networking via net-misc/vde. +app-emulation/virtualbox:vmmraw - Enable 32-bit support on a 64-bit kernel. app-emulation/virtualbox-kvm:dtrace - Install dtrace Extension Pack +app-emulation/virtualbox-kvm:hardened - Enable hardening and install binaries SUID app-emulation/virtualbox-kvm:lvm - Build VBoxVolInfo that needs devicemapper from sys-fs/lvm2. app-emulation/virtualbox-kvm:sdk - Enable building of SDK app-emulation/virtualbox-kvm:udev - Controls installation of special USB udev rules. app-emulation/virtualbox-kvm:vboxwebsrv - Build and install the VirtualBox webservice app-emulation/virtualbox-kvm:vde - Support for VDE networking via net-misc/vde +app-emulation/virtualbox-kvm:vmmraw - Enable 32-bit support on a 64-bit kernel. app-emulation/vkd3d:spirv-tools - Enable SPIRV shader debugging support using dev-util/spirv-tools app-emulation/vkd3d-proton:crossdev-mingw - Use sys-devel/crossdev for the toolchain rather than dev-util/mingw64-toolchain (requires manual setting up) app-emulation/vkd3d-proton:extras - Install extra tools and demos in /usr/lib/vkd3d-proton app-emulation/wine-gecko:shared - Install pre-unpacked files which do not need to be copied into the Wine prefix -app-emulation/wine-mono:shared - Install pre-unpacked files which do not need to be copied into the Wine prefix +app-emulation/wine-mono:shared - Install pre-unpacked files which do not need to be copied into the Wine prefix (note that this requires the default top-level Z: drive to be kept for out-of-prefix files to be readable) app-emulation/wine-proton:crossdev-mingw - Use sys-devel/crossdev for the toolchain rather than dev-util/mingw64-toolchain (requires manual setting up) app-emulation/wine-proton:gecko - Enable mshtml support using app-emulation/wine-gecko app-emulation/wine-proton:mono - Enable .NET support using app-emulation/wine-mono @@ -751,9 +747,6 @@ app-forensics/aide:curl - Use curl for http,https and ftp backends app-forensics/aide:e2fs - Enable support for checking file attributes on ext2/ext3/ext4 filesystems app-forensics/chkrootkit:cron - Install cron script for weekly rootkit scans app-forensics/honggfuzz:clang - Enable clang support (pull sys-libs/blocksruntime dependency). -app-forensics/libewf:bfio - Enables libbfio for chaining file in file handling -app-forensics/libewf:fuse - Enable fuse support for ewfmount -app-forensics/libewf:uuid - Enable UUID support in the ewftools app-forensics/lynis:cron - Install /etc/cron.* files app-forensics/sleuthkit:aff - Enable extra aff formats app-forensics/sleuthkit:ewf - Enable libewf support @@ -801,9 +794,8 @@ app-i18n/fcitx-lua:dlopen - Use dlopen to load lua library app-i18n/fcitx-qt:onlyplugin - Build only plugin app-i18n/fcitx-qt:qt6 - Build support for QT6 app-i18n/fcitx-qt:staticplugin - Build plugin as static -app-i18n/fcitx-rime:configuration_tool - Install configuration tool +app-i18n/fcitx-rime:configuration-tool - Install configuration tool app-i18n/fcitx-unikey:macro-editor - Install macro editor -app-i18n/freewnn:uum - Build uum app-i18n/ibus:emoji - Enable support for Emoji app-i18n/ibus:gtk2 - Enable the GTK-2 input method module app-i18n/ibus:gtk3 - Enable the GTK-3 input method module @@ -876,7 +868,7 @@ app-misc/ebusd:mqtt - Enable support for connecting to MQTT. app-misc/fastfetch:chafa - Enables text/graphics renderer with media-gfx/chafa app-misc/fastfetch:ddcutil - Use app-misc/ddcutil to query monitor settings app-misc/fastfetch:drm - Enables support for X.org's x11-libs/libdrm -app-misc/fastfetch:nvidia-gpu - Enables extra support for NVIDIA GPU +app-misc/fastfetch:elf - Use libelf to extract strings from binaries app-misc/fastfetch:osmesa - Enables offscreen rendering support from media-libs/mesa app-misc/fastfetch:vulkan - Enables reading GPU via media-libs/vulkan-loader app-misc/fastfetch:xfce - Enables support for XFCE config @@ -905,7 +897,6 @@ app-misc/lcd4linux:button-exec - Enable the Button plugin, to execute something app-misc/lcd4linux:cpuinfo - Enable the cpuinfo plugin. app-misc/lcd4linux:dbus - Enable the dbus plugin. app-misc/lcd4linux:diskstats - Enable the diskstats plugin. -app-misc/lcd4linux:dmalloc - Enable dmalloc for debugging. app-misc/lcd4linux:dvb - Enable support for the DVB plugin. app-misc/lcd4linux:event - Enable the event plugin. app-misc/lcd4linux:exec - Enable the exec plugin, to read output from external programs. @@ -987,8 +978,6 @@ app-misc/rlwrap:debug - Enable debug app-misc/screen:multiuser - Enable multiuser support (by setting correct permissions) app-misc/screen:nethack - Express error messages in nethack style app-misc/screenfetch:X - Use the media-gfx/scrot package to take screenshots -app-misc/skim:tmux - Install sk-tmux script to run skim in a tmux pane -app-misc/skim:vim - Install vim plugin for skim app-misc/sphinx:id64 - use 64-bit document and word IDs app-misc/sphinx:mariadb - Add mariadb database support app-misc/sphinx:stemmer - Enable language stemming support @@ -1005,11 +994,12 @@ app-misc/tracker-miners:xps - Add support for XPS file format through app-text/l app-misc/unfoo:minimal - Do not install all support archive binaries app-misc/vcontrold:vclient - Build the vclient helper program to talk to vcontrold app-misc/vcontrold:vsim - Build the vsim helper program (simulates the heating's answers, for development and debugging) -app-misc/vifm:developer - Enable features of interest to developers app-misc/vifm:extended-keys - Support for extended keys (arrows, home etc) app-misc/vifm:gtk - Use gtk+ to determine mimetypes app-misc/vifm:vim - Install the vifm vim plugin and vim-compatible documentation app-misc/worker:avfs - Enable support for sys-fs/avfs +app-misc/yq:yq-symlink - Create a yq symlink to yq-python. +app-misc/yq-go:yq-symlink - Create a yq symlink to yq-go. app-mobilephone/gammu:curl - Enables curl support app-mobilephone/gammu:irda - Enables infrared support app-mobilephone/gammu:mysql - Use mysql for data storage @@ -1033,14 +1023,12 @@ app-office/abiword:redland - Enables support redland and raptor libs. app-office/abiword:thesaurus - Enable thesaurus support app-office/abiword:wordperfect - Enable wordperfect file support via app-text/libwpd app-office/calcurse:caldav - Support CalDAV -app-office/calligra:activities - Enable kactivities support app-office/calligra:charts - Build chartshape plugin for creating business charts with dev-libs/kdiagram -app-office/calligra:gemini - Enable tablet and 2:1 devices support app-office/calligra:import-filter - Enable support for various import filter file formats like WordPerfect, Visio and Apple Keynote app-office/calligra:lcms - Build colorengine plugins using media-libs/lcms app-office/calligra:okular - Enable bindings for kde-apps/okular app-office/calligra:phonon - Build stage/eventplugins and videoshape plugin using media-libs/phonon -app-office/calligra:spacenav - Enable support for the 3Dconnexion spacenav input device via dev-libs/libspnav +app-office/calligra:webengine - Enable Braindump support using dev-qt/qtwebengine app-office/calligraplan:activities - Enable kactivities support app-office/calligraplan:holidays - Enable kde-frameworks/kholidays integration app-office/calligraplan:kwallet - Enable access to encrypted OpenDocument files with kde-frameworks/kwallet storage @@ -1116,6 +1104,7 @@ app-portage/portage-utils:qmanifest - Build qmanifest applet, this adds addition app-portage/portage-utils:qtegrity - Build qtegrity applet, this adds additional dependencies for OpenSSL app-portage/tatt:templates - Install template scripts to be used with tatt app-shells/atuin:client - Enable the autin client +app-shells/atuin:daemon - Enable the autin background daemon on the client app-shells/atuin:server - Enable the autin server app-shells/atuin:sync - Enable the server-sync feature in the autin client app-shells/autojump:ipython - Add support for dev-python/ipython @@ -1126,8 +1115,7 @@ app-shells/bash:pgo - Optimize the build using Profile Guided Optimization (PGO) app-shells/bash:plugins - Add support for loading builtins at runtime via 'enable' app-shells/bash-completion:eselect - Support blacklisting of completions via 'eselect bashcomp'. This enables custom Gentoo patching of upstream completion loader. app-shells/mksh:lksh - variant that uses POSIX-compliant arithmetics with the host “long” data type and is automatically in POSIX mode when called as /bin/sh -app-shells/nushell:dataframe - Dataframe feature for nushell -app-shells/nushell:extra - Enable less stable or less common commands +app-shells/nushell:plugins - Build official plugins app-shells/pdsh:rsh - This allows the use of rsh (remote shell) and rcp (remote copy) for authoring websites. sftp is a much more secure protocol and is preferred. app-shells/shish:diet - Use dev-libs/dietlibc app-text/atril:caja - Enable property page extension in mate-base/caja @@ -1213,7 +1201,7 @@ app-text/mathtex:png - Generate png images by default instead of gif app-text/msort:heap - Use heap instead of alloca() app-text/msort:icu - Use dev-libs/icu instead of dev-libs/libutf8proc. app-text/msort:libuninum - Use dev-libs/libuninum for conversion. -app-text/mupdf:drm - Enable support for Digital rights management (DRM) +app-text/mupdf:archive - Enable support for CBR and other archive formats using libarchive app-text/pandoc:embed-data-files - Embed data files in binary for relocatable executable. app-text/pandoc:trypandoc - Build trypandoc cgi executable. app-text/pandoc-bin:pandoc-symlink - Install pandoc symlink that points to pandoc-bin @@ -1221,6 +1209,7 @@ app-text/pandoc-cli:lua - Support custom modifications and conversions with the app-text/pandoc-cli:nightly - Add '-nightly-COMPILEDATE' to the output of '--version'. app-text/pandoc-cli:server - Include support for running pandoc as an HTTP server. app-text/pdfgrep:unac - Removing accents and ligatures before search +app-text/pdfjam:extra - Install unsupported wrapper scripts, for example pdf90, pdfnup, pdfjoin app-text/pdfpc:gstreamer - Compile support for movie playback (media-libs/gstreamer) app-text/pdfpc:soup - Compile support for REST server (net-libs/libsoup) app-text/pdfpc:webkit - Enable viewing Markdown notes (net-libs/webkit-gtk) @@ -1236,6 +1225,7 @@ app-text/qpdfview:synctex - Add support for searching TeX sources app-text/robodoc:examples - Installs usage examples in /usr/share for Perl app-text/sdcv:darkterm - Improve readability of color output on terminals with dark background. app-text/sigil:plugins - Installed needed Python packages for using Sigil plugins +app-text/sigil:system-mathjax - Use the system-wide dev-libs/mathjax instead of bundled app-text/sword:clucene - Use dev-cpp/clucene for lucene search support app-text/tessdata_best:osd - Enable support orientation and script detection. app-text/tessdata_fast:osd - Enable support orientation and script detection. @@ -1249,7 +1239,7 @@ app-text/texlive:extra - Add support for extra TeXLive packages app-text/texlive:games - Add typesetting support for games (chess, etc.) (dev-texlive/texlive-games) app-text/texlive:graphics - Add support for several graphics packages (pgf, tikz,...) app-text/texlive:humanities - Add LaTeX support for the humanities (dev-texlive/texlive-humanities) -app-text/texlive:luatex - Add extra support for luatex +app-text/texlive:luatex - Install TeX Live packages that require luatex app-text/texlive:metapost - Add support for metapost: A tool for creating graphics in scalable PostScript app-text/texlive:music - Add support for music typesetting (dev-texlive/texlive-music) app-text/texlive:pdfannotextractor - Add dev-tex/pdfannotextractor support, for extracting annotations from PDF files @@ -1285,7 +1275,7 @@ app-text/wv:tools - Install optional utilities considered deprecated in favor of app-text/xmlto:text - Support conversion from XML to plain text app-text/xpdf:cmyk - Include support for CMYK rasterization app-text/xpdf:i18n - Enable support non-UTF8 national charsets -app-text/xpdf:icons - Generate desktop PNG icons using media-gfx/inkscape +app-text/xpdf:icons - Generate desktop PNG icons using rsvg-convert from gnome-base/librsvg app-text/xpdf:libpaper - Use app-text/libpaper to get paper preferences app-text/xpdf:metric - Use A4 instead of US Letter paper size by default for PostScript output. This option has effect only if libpaper USE flag is disabled app-text/xpdf:opi - Include support for OPI (Open Prepress Interface) comments @@ -1293,6 +1283,7 @@ app-text/xpdf:textselect - Allow text selection app-text/xpdf:utils - Install command-line PDF converters and various utilities app-text/zathura:synctex - Use libsynctex to get latex codeline from pdf app-text/zathura-meta:cb - Install plug-in for ComicBook support +app-text/zeal:X - Enable global shortcut support on X11 app-vim/gentoo-syntax:ignore-glep31 - Remove GLEP 31 (UTF-8 file encodings) settings app-xemacs/xemacs-packages-all:mule - Add multi-language support to XEmacs dev-ada/AdaSAT:shared - Build shared library @@ -1336,6 +1327,10 @@ dev-build/bazelisk:bazel-symlink - Install bazel symlink that points to bazelisk dev-build/cmake:dap - Build debugger for CMake with Debug Adapter Protocol support via dev-cpp/cppdap dev-build/muon:archive - Enable extracting wraps using app-arch/libarchive. dev-build/muon:libpkgconf - Enable looking up packages via dev-util/pkgconf. +dev-cpp/benchmark:exceptions - Enable the use of exceptions in the benchmark library +dev-cpp/benchmark:libcxx - Use sys-libs/libcxx instead of libstdc++ as the default stdlib +dev-cpp/benchmark:libpfm - Enable dev-libs/libpfm support +dev-cpp/benchmark:tools - Install some additional Python tools dev-cpp/eigen:adolc - Add test support for Adolc (sci-libs/adolc) dev-cpp/eigen:benchmark - Build benchmark suite dev-cpp/eigen:boost - Add test support for Boost.Multiprecision (dev-libs/boost) @@ -1447,6 +1442,8 @@ dev-db/timescaledb:proprietary-extensions - Enable proprietary features/extensio dev-db/unixODBC:minimal - Disable bundled drivers and extra libraries (most users don't need these) dev-db/unixODBC:odbcmanual - Administrator, Internal Structure, Programmer and User documentation dev-debug/bpftrace:fuzzing - Build bpftrace for fuzzing +dev-debug/bpftrace:lldb - Parse debug info usingdev-debug/lldb +dev-debug/dtrace:test-install - Install the testsuite for manual use. It is not suitable for automatic execution within the ebuild because it requires root privlieges. dev-debug/gdb:cet - Enable Intel Control-flow Enforcement Technology. dev-debug/gdb:debuginfod - Enable debuginfod support via dev-libs/elfutils libdebuginfod dev-debug/gdb:lzma - Support lzma compression in ELF debug info @@ -1464,6 +1461,8 @@ dev-debug/strace:aio - Enable dev-libs/libaio support for tracing Asynchronous I dev-debug/strace:elfutils - Enable stack backtraces (-k flag) via dev-libs/elfutils dev-debug/strace:unwind - Enable stack backtraces (-k flag) via sys-libs/libunwind dev-debug/sysdig:modules - Build kernel modules needed for tracing local events. Disable this only if you intend to use sysdig purely to work with dumpfiles. +dev-debug/systemtap:debuginfod - Enable debuginfod support via dev-libs/elfutils libdebuginfod +dev-debug/systemtap:dtrace-symlink - Provide /usr/bin/dtrace symlink pointing to /usr/bin/stap-dtrace. This prevents coinstallation with dev-debug/dtrace. dev-debug/systemtap:libvirt - Support probing of libvirt domains. dev-embedded/avrdude:ftdi - Enable support for USB FTDI chips via dev-embedded/libftdi dev-embedded/libftdi:tools - build ftdi_eeprom helper tool @@ -1513,12 +1512,9 @@ dev-embedded/sdcc:z80n - Add support for Zilog Z80N dev-embedded/u-boot-tools:envtools - Build only the target-side environment tools dev-embedded/urjtag:ftd2xx - Enable support for USB FTDI chips via dev-embedded/libftd2xx dev-embedded/urjtag:ftdi - Enable support for USB FTDI chips via dev-embedded/libftdi -dev-games/godot:bullet - Enable the sci-physics/bullet module dev-games/godot:deprecated - Enable support for deprecated features dev-games/godot:raycast - Enable the raycast Editor module using media-libs/embree -dev-games/godot:runner - Build an additional binary optimized for running games (only relevant with USE=tools) dev-games/godot:tools - Enable the Godot Editor for game development -dev-games/godot:webm - Enable the WebM module dev-games/guichan:allegro - Build the Allegro frontend dev-games/mygui:l10n_ru - Install some additional russian docs if 'doc' useflag enabled dev-games/mygui:ogre - Use the ogre render subsystem. (cannot combine with opengl) @@ -1577,6 +1573,7 @@ dev-games/physfs:wad - Enable Doom WAD archive support dev-games/simgear:dns - Enable DNS resolver via net-libs/udns dev-games/simgear:gdal - Enable alternative terrain engine based on pagedLOD via sci-libs/gdal dev-games/simgear:subversion - Enable terrasync scenery downloader +dev-games/tiled:minimal - Exclude optional plugins and development headers dev-gap/grape:bliss - Use sci-libs/bliss instead of sci-mathematics/nauty as the backend. dev-haskell/abstract-deque:usecas - Enable the reference implementation to use hardware compare-and-swap. dev-haskell/aeson:cffi - Controls whether to include c-ffi bits or pure haskell. Default to False for security. @@ -1738,9 +1735,11 @@ dev-java/commons-logging:log4j - Add optional support for log4j dev-java/dom4j:jaxen - Includes org.jaxen.dom4j package dev-java/emma:launcher - Install /usr/bin/emma. Collides with sci-biology/emboss. dev-java/java-config:compat - Install bin/java-config-2 symlink pointing to java-config +dev-java/javacup:ant-task - Build and register the ant-task dev-java/jaxen:dom4j - Includes org.jaxen.dom4j package dev-java/jaxen:jdom - Includes org.jaxen.jdom package dev-java/jaxen:xom - Includes org.jaxen.xom package +dev-java/jflex:ant-task - Build and register the ant-task dev-java/junit:migration-support - Include the junit-jupiter-migrationsupport module, which helps with migration from JUnit 4 to JUnit Jupiter dev-java/junit:suite - Include the JUnit Platform Suite Engine, which adds test suite support dev-java/junit:vintage - Include JUnit Vintage, which allows JUnit 5 to run JUnit 3 and JUnit 4 tests @@ -1749,7 +1748,7 @@ dev-java/openjdk:javafx - Import OpenJFX modules at build time, via dev-java/ope dev-java/openjdk:jbootstrap - Build OpenJDK twice, the second time using the result of the first dev-java/openjdk:source - Install JVM sources dev-java/openjdk:system-bootstrap - Bootstrap using installed openjdk -dev-java/openjdk:systemtap - Enable SystemTAP/DTrace tracing +dev-java/openjdk:systemtap - Enable SystemTap/DTrace tracing dev-java/openjdk-bin:headless-awt - Don't install the X backend for AWT, needed by some GUIs (used to be X flag) dev-java/openjdk-bin:source - Install JVM sources dev-java/openjdk-jre-bin:headless-awt - Don't install the X backend for AWT, needed by some GUIs (used to be X flag) @@ -1757,8 +1756,11 @@ dev-java/openjfx:media - Compile media module, based on gstreamer-minimal (does dev-java/openjfx:source - Install JavaFX sources dev-java/pdfbox:tools - Build and install pdfbox-tools dev-java/protobuf-java:system-protoc - Use protoc provided by dev-libs/protobuf +dev-java/qdox:ant-task - Build the ant-task dev-java/rxtx:lfd - Installs and uses LockFileServer daemon (lfd) +dev-java/saxon:ant-task - BUILD and register the ant-task dev-java/sbt:binary - Install from (Gentoo-compiled) binary instead of building from sources. Set this when you run out of memory during build. +dev-lang/R:libdeflate - Use app-arch/libdeflate rather than sys-libs/zlib for lazy-loaded R objects. dev-lang/algol68g:mpfr - Add support for multiprecision floating point rouding dev-lang/ammonite-repl-bin:scala2-13 - Install Ammonite for Scala 2.13 dev-lang/ammonite-repl-bin:scala3-0 - Install Ammonite for Scala 3.0 @@ -1784,7 +1786,6 @@ dev-lang/ghc:llvm - Pull in dependencies for the sys-devel/llvm codegen backend. dev-lang/ghc:numa - Enable NUMA thread balancing policy using sys-process/numactl. dev-lang/ghc:unregisterised - Create an unregisterised build in which only the C codegen backend will be available. dev-lang/gnat-gpl:ada - Build the ADA language (GNAT) frontend -dev-lang/gnat-gpl:bootstrap - Used to bootstrap gnat-gpl dev-lang/gnat-gpl:cet - Enable support for Intel Control Flow Enforcement Technology (CET) dev-lang/gnat-gpl:d - Enable support for the D programming language dev-lang/gnat-gpl:default-stack-clash-protection - Build packages with stack clash protection on by default @@ -1801,6 +1802,7 @@ dev-lang/gnat-gpl:pgo - Build GCC using Profile Guided Optimization (PGO) dev-lang/gnat-gpl:rust - Build support for the Rust language, installs gccrs. dev-lang/gnat-gpl:sanitize - Build support for various sanitizer functions (ASAN/TSAN/etc...) dev-lang/gnat-gpl:ssp - Build packages with stack smashing protector on by default +dev-lang/gnat-gpl:system-bootstrap - Bootstrap using installed Ada compiler dev-lang/gnat-gpl:systemtap - enable systemtap static probe points dev-lang/gnat-gpl:vtv - Build support for virtual table verification (a C++ hardening feature) dev-lang/gnucobol:json - Enable support for JSON template formatting via dev-libs/json-c @@ -1821,7 +1823,6 @@ dev-lang/logtalk:fop - Support for generating pdf documentation using fop dev-lang/logtalk:xslt - Support for generating html documentation using xslt dev-lang/lua:deprecated - make deprecated data structures/routines available dev-lang/luajit:lua52compat - Enable some upwards-compatible features from Lua 5.2 that are unlikely to break existing code. -dev-lang/mercury:erlang - Support Mercury Erlang grade dev-lang/mercury:trail - Support Mercury trail grades dev-lang/mercury-extras:tommath - Enable support for tommath library dev-lang/mlton:binary - install a binary version @@ -1836,14 +1837,11 @@ dev-lang/moarvm:ubsan - Enable clang's Undefined Behavior Sanitizer functionalit dev-lang/mono:pax-kernel - Enable if the user plans to run the package under a pax enabled hardened kernel dev-lang/mono:xen - Make mono generate code that is considerably faster on xen VMs but slightly slower on for normal systems. dev-lang/neko:apache - Build Apache modules -dev-lang/nim:experimental - Apply experimental patches dev-lang/nim:test-js - Enable tests that require Node.js dev-lang/nqp:clang - Toggle usage of the clang compiler in conjunction with MoarVM dev-lang/nqp:moar - Build the MoarVM backend (experimental/broken) dev-lang/ocaml:flambda - Enables the Flambda optimizer: A new intermediate representation (introduced in ocaml 4.03) in the depths of the compiler designed to allow for better inlining. dev-lang/ocaml:spacetime - Enables the Spacetime memory profiler. See https://caml.inria.fr/pub/docs/manual-ocaml/spacetime.html for more information. -dev-lang/perl:ithreads - Enable Perl threads, has some compatibility problems -dev-lang/perl:quadmath - Enable 128bit floating point arithmetic via libquadmath dev-lang/php:apparmor - Support FPM application confinement through sys-libs/libapparmor dev-lang/php:argon2 - Enable password hashing algorithm from app-crypt/argon2 dev-lang/php:bcmath - Enable the BCMath Arbitrary Precision Mathematics extension @@ -1866,6 +1864,7 @@ dev-lang/php:jit - Enable PCRE JIT support dev-lang/php:ldap-sasl - Add SASL support for the PHP LDAP extension using dev-libs/cyrus-sasl dev-lang/php:lmdb - Enable support for dev-db/lmdb db backend dev-lang/php:opcache - Enables built-in opcode cache, replacing pecl-apc et al. +dev-lang/php:opcache-jit - Enable Just In Time (JIT) compilation within the opcache extension dev-lang/php:pcntl - Enable the Process Control extension dev-lang/php:pdo - Enable the PHP Data Objects extension dev-lang/php:phar - Enables the phar extension to provide phar archive support @@ -1894,7 +1893,7 @@ dev-lang/qu-prolog:pedro - Pedro subscription/notification communications system dev-lang/rakudo:clang - Use Clang to compile the MoarVM backend dev-lang/rakudo:moar - Use the MoarVM as backend dev-lang/ruby:rdoc - Install dev-ruby/rdoc after installing Ruby. -dev-lang/ruby:systemtap - Enable SystemTAP/DTrace tracing +dev-lang/ruby:systemtap - Enable SystemTap/DTrace tracing dev-lang/rust:clippy - Install clippy, Rust code linter dev-lang/rust:dist - Install dist tarballs (used for bootstrapping) dev-lang/rust:miri - Install miri, an interpreter for Rust's mid-level intermediate representation (requires USE=nightly, sometimes is broken) @@ -1912,7 +1911,6 @@ dev-lang/rust-bin:profiler - Build the profiler runtime and rust-demangler tool dev-lang/rust-bin:rust-analyzer - Install rust-analyzer, A Rust compiler front-end for IDEs (language server) dev-lang/rust-bin:rust-src - Install rust-src, needed by developer tools and for build-std (cross) dev-lang/rust-bin:rustfmt - Install rustfmt, Rust code formatter -dev-lang/scala:binary - Install from (Gentoo-compiled) binary instead of building from sources. Set this when you run out of memory during build. dev-lang/souffle:ffi - Support c++ functors with arbitrary number of arguments dev-lang/souffle:swig - Enable SWIG usage, needed for Java and Python bindings dev-lang/spidermonkey:clang - Use Clang compiler instead of GCC @@ -2004,6 +2002,7 @@ dev-libs/gf2x:fft - Build an FFT API for multiplication of 2 polynomials over GF dev-libs/gjs:sysprof - Enable profiling data capture support using dev-util/sysprof-capture dev-libs/glib:dbus - Enable dependencies required by glib libraries using dbus service to manage settings saving dev-libs/glib:elf - Enable support for listing and extracting from ELF resource files with gresource tool +dev-libs/glib:introspection - Enable generating introspection data (requires dev-libs/gobject-introspection ) dev-libs/glib:mime - Pull in shared MIME database that many glib-based applications require at runtime to detect or open files. Warning: do not disable this flag unless installing on a headless server. dev-libs/glib:sysprof - Enable profiling data capture support using dev-util/sysprof-capture dev-libs/glib:systemtap - Build support for profiling and tracing using dev-debug/systemtap @@ -2023,7 +2022,6 @@ dev-libs/jemalloc:prof - Enable allocation profiling dev-libs/jemalloc:stats - Enable statistics calculation/reporting dev-libs/jemalloc:xmalloc - Add support for xmalloc (abort-on-out-of-memory) dev-libs/json-glib:nls - Enable native language support (translations) -dev-libs/kosmindoormap:openinghours - Enable support for highlighting currently open amenities/shops/etc. dev-libs/kreport:marble - Enable displaying of maps using kde-apps/marble dev-libs/kreport:scripting - Support Qml scripting using dev-qt/qtdeclarative dev-libs/ktextaddons:designer - Build plugins for dev-qt/designer @@ -2155,6 +2153,7 @@ dev-libs/modsecurity:lmdb - Add LMDB backend support dev-libs/modsecurity:pcre2 - Use dev-libs/libpcre2 as regex implementation dev-libs/ncnn:tools - Enable installation of various tools in addition to the library dev-libs/nss:cacert - Include root/class3 certs from CAcert (https://www.cacert.org/) +dev-libs/nss:test-full - Run all available tests, instead of the standard set only dev-libs/nss:utils - Compile and install all extra binaries, such as certutil, modutil and few more dev-libs/nwjs:ffmpeg-chromium - Use Chromium FFmpeg fork (media-video/ffmpeg-chromium) rather than mainline FFmpeg (media-video/ffmpeg) dev-libs/oneDNN:cblas - Use virtual/cblas for sgemm routines @@ -2175,6 +2174,7 @@ dev-libs/opensc:secure-messaging - Enable secure messaging dev-libs/openssl:bindist - Disable/Restrict EC algorithms (as they seem to be patented) -- note: changes the ABI dev-libs/openssl:fips - Enable FIPS provider dev-libs/openssl:ktls - Enable support for Kernel implementation of TLS (kTLS) +dev-libs/openssl:quic - Enable support for QUIC (RFC 9000); a UDP-based protocol intended to replace TCP dev-libs/openssl:rfc3779 - Enable support for RFC 3779 (X.509 Extensions for IP Addresses and AS Identifiers) dev-libs/openssl:sslv2 - Support for the old/insecure SSLv2 protocol -- note: not required for TLS/https dev-libs/openssl:sslv3 - Support for the old/insecure SSLv3 protocol -- note: not required for TLS/https @@ -2214,6 +2214,11 @@ dev-libs/poco:util - Several utility classes (like logger, timer, config file pa dev-libs/poco:zip - Add support for the zip & gz archive formats dev-libs/ppl:cdd - Build the ppl_lcdd program for vertex/facet enumeration accepting the same input format as the programs shipped with sci-libs/cddlib and sci-libs/lrslib dev-libs/ppl:lpsol - Build the ppl_lpsol linear program solver that uses sci-mathematics/glpk for its input routines +dev-libs/protobuf:conformance - Build conformance tests +dev-libs/protobuf:libprotoc - Build libprotoc +dev-libs/protobuf:libupb - Build libupb +dev-libs/protobuf:protobuf - Build protobuf libraries and protoc compiler +dev-libs/protobuf:protoc - Build libprotoc and protoc compiler dev-libs/qcoro:network - Build dev-qt/qtbase network support dev-libs/qcoro:qml - Enable QML/QtQuick support via dev-qt/qtdeclarative dev-libs/qcoro:websockets - Build dev-qt/qtwebsockets support @@ -2225,6 +2230,8 @@ dev-libs/qhotkey:qt6 - Use Qt6 dependencies dev-libs/quazip:qt5 - Build with Qt5 support dev-libs/quazip:qt6 - Build with Qt6 support dev-libs/raft:zfs - ZFS support +dev-libs/re2:benchmark - Build a benchmark binary, install it as re2-bench +dev-libs/re2:test-full - Run additional, quite slow tests dev-libs/rocksdb:numa - Enable NUMA support dev-libs/rocksdb:tbb - Enable support for dev-cpp/tbb dev-libs/sentry-native:breakpad - Use dev-util/breakpad as the crash handler @@ -2264,8 +2271,6 @@ dev-libs/weston:resize-optimization - Increase performance, allocate more RAM. R dev-libs/weston:screen-sharing - Enable screen-sharing through RDP dev-libs/weston:wayland-compositor - Enable Wayland compositor support dev-libs/weston:xwayland - Enable ability support native X11 applications -dev-libs/xapian:inmemory - Enabled inmemory backend db support -dev-libs/xapian:remote - Enabled remote backend db support dev-libs/xerces-c:iconv - Use iconv (virtual/libiconv) as message loader and transcoder (in general it would be possible to use iconv only as message loader and something else like icu or the native method as transcoder and vice-versa, but this is a less common case and hard to handle) dev-libs/xerces-c:threads - Enable threading support through pthread (or other libraries on AIX, IRIX, HPUX, Solars). Highly recommended dev-libs/xmlrpc-c:abyss - Build the Abyss mini web-server. @@ -2280,8 +2285,8 @@ dev-libs/yaz:ziffy - Install ziffy, a promiscuous Z39.50 APDU sniffer dev-lisp/clisp:hyperspec - Use local hyperspec instead of online version dev-lisp/clisp:svm - Build CLISP with support for the Support Vector Machine module dev-lisp/clx:doc - Builds documentation -dev-lisp/cmucl:X - Build CLX, CLM, or Hemlock dev-lisp/cmucl:doc - Installs package documentation +dev-lisp/cmucl:gui - Build CLX, CLM, or Hemlock dev-lisp/cmucl:source - Include source code for CMUCL in installation dev-lisp/ecl:gengc - Use generational garbage collection (experimental) dev-lisp/ecl:precisegc - Use type information during garbage collection (experimental) @@ -2359,11 +2364,6 @@ dev-perl/Text-CSV:xs - Install dev-perl/Text-CSV_XS for accelerated decoding dev-perl/WWW-Form-UrlEncoded:xs - Install C-Based dependieces for faster performance dev-perl/perl-headers:debug - Add source locations in generated .ph files to assist with debugging when errors occur dev-perl/perl-headers:sizeof-warning - Include logic to warn when a .ph file tries to use a sizeof() that is unknown -dev-php/PEAR-HTTP_Request2:curl - Force dev-lang/php to be compiled with curl extension -dev-php/PEAR-HTTP_Request2:fileinfo - Force dev-lang/php to be compiled with fileinfo extension -dev-php/PEAR-HTTP_Request2:ssl - Force dev-lang/php to be compiled with ssl extension -dev-php/PEAR-HTTP_Request2:zlib - Force dev-lang/php to be compiled with zlib extension -dev-php/PEAR-PHP_Beautifier:cli - Require dev-lang/php to be built with the "cli" SAPI and install the php_beautifier script. dev-php/maxmind-db-reader:extension - Build the C extension that uses dev-libs/libmaxminddb dev-php/pecl-apcu:lock-pthreadmutex - Enable pthread mutex locking dev-php/pecl-apcu:lock-pthreadrw - Enable pthread read/write locking @@ -2412,6 +2412,7 @@ dev-python/PyQt6:printsupport - Build bindings for the QtPrintSupport module dev-python/PyQt6:qml - Build bindings for the QtQml module and enable the qml plugin dev-python/PyQt6:quick - Build bindings for the QtQuick module dev-python/PyQt6:quick3d - Build bindings for the QtQuick3D module +dev-python/PyQt6:remoteobjects - Build bindings for the QtRemoteObjects module dev-python/PyQt6:sensors - Build bindings for the QtSensors module dev-python/PyQt6:serialport - Build bindings for the QtSerialPort module dev-python/PyQt6:spatialaudio - Build bindings for the QtSpatialAudio module @@ -2481,6 +2482,7 @@ dev-python/mkdocs-material:social - Install the dependencies of the "social" plu dev-python/msgpack:native-extensions - Compiles native "C" extensions (speedups, instead of using python fallback code). dev-python/multidict:native-extensions - Compile native C extensions (speedups, instead of using Python fallback code). dev-python/mypy:native-extensions - Compiles native C extensions (speedups, instead of using Python fallback code). +dev-python/netcdf4:blosc - Allow using blosc compression via dev-libs/c-blosc dev-python/pandas:full-support - Pull all packages to give pandas full support dev-python/paramiko:server - Enable server feature dev-python/peewee:native-extensions - Compiles native C extension for more complete SQLite3 support. @@ -2491,14 +2493,14 @@ dev-python/pyarrow:parquet - Enables read/write parquet data format dev-python/pyglet:image - Enable support for image formats other than PNG and BMP dev-python/pymongo:native-extensions - Compiles native C extensions dev-python/pymongo:test-full - Run test suite in full, including tests that run a local database instance. -dev-python/pyocr:cuneiform - Enable support for the app-text/cuneiform OCR engine -dev-python/pyocr:tesseract - Enable support for the app-text/tesseract OCR engine dev-python/pyopengl_accelerate:numpy - Building NumPy native format handlers. dev-python/pypax:ptpax - Enable PT_PAX_FLAGS support. dev-python/pypax:xtpax - Enable XATTR_PAX_FLAGS support. dev-python/pypy:full-stdlib - Install complete stdlib as necessary to use PyPy for general purpose programs. By default, only a limited subset that is used when building PyPy3 executables is installed. Note that PyPy2.7's stdlib contains multiple known vulnerabilities. dev-python/pypy-exe:low-memory - Build using PyPy with the engine configured towards low memory footprint. This makes it possible to build PyPy using ~3.5G of RAM on amd64 and ~half of that on x86, at the cost of lengthened build time. +dev-python/pypy3:test-install - Install the test suite packages, that are required to run tests in a few reverse dependencies. dev-python/pypy3_10:ensurepip - Install the ensurepip module that uses bundled wheels to bootstrap pip and setuptools (if disabled, it will be only possible to use venv `--without-pip`) +dev-python/pypy3_10:test-install - Install the test suite packages, that are required to run tests in a few reverse dependencies. dev-python/pypy3_10-exe:low-memory - Build using PyPy with the engine configured towards low memory footprint. This makes it possible to build PyPy using ~3.5G of RAM on amd64 and ~half of that on x86, at the cost of lengthened build time. dev-python/pypy3_9:ensurepip - Install the ensurepip module that uses bundled wheels to bootstrap pip and setuptools (if disabled, it will be only possible to use venv `--without-pip`) dev-python/pypy3_9-exe:low-memory - Build using PyPy with the engine configured towards low memory footprint. This makes it possible to build PyPy using ~3.5G of RAM on amd64 and ~half of that on x86, at the cost of lengthened build time. @@ -2569,7 +2571,7 @@ dev-python/python-mpd2:twisted - Enable twisted support dev-python/python-stdnum:vies - Enable VIES dev-python/pyudev:qt5 - Install PyQt5 bindings dev-python/pyzmq:drafts - Enable draft API support -dev-python/qiskit-terra:visualization - Enable visualization modules +dev-python/qiskit:visualization - Enable visualization modules dev-python/rarfile:compressed - Enables the module to support compressed v3 archives by calling the app-arch/unrar. dev-python/reedsolo:native-extensions - Compile native C extensions. dev-python/rfc3986:idna - enable support for the IDNA specification (RFC 5891) @@ -2584,7 +2586,6 @@ dev-python/shiboken6:vulkan - Generate "QSurface::VulkanSurface" bindings dev-python/simplejson:native-extensions - Compiles native "C" extensions (speedups, instead of using Python fallback code). dev-python/stripe:telemetry - Enable sending "telemetry to Stripe regarding request latency and feature usage" by default. Upstream enables it by default in their PyPI distribution; it can also be explicitly controlled via stripe.enable_telemetry variable (boolean). dev-python/subprocess-tee:test-full - Enable full test mode. Pulls in many additional dependencies, and requires having been emerged without this flag first in order to avoid a circular dependency. -dev-python/sympy:aesara - Add support for dev-python/aesara dev-python/sympy:imaging - Add support for dev-python/pillow dev-python/sympy:ipython - Add support for dev-python/ipython dev-python/sympy:mathml - Add support for mathml @@ -2612,7 +2613,7 @@ dev-qt/qt-creator:help - Enable the integrated dev-qt/qt-docs viewer (also neede dev-qt/qt-creator:plugin-dev - Install the 'Devel' component needed to build external Qt Creator plugins dev-qt/qt-creator:qmldesigner - Build QmlDesigner and related plugins (Insight, StudioWelcome) dev-qt/qt-creator:serialterminal - Build the serial terminal plugin -dev-qt/qt-creator:tracing - Build plugins requiring tracing capabilities (CtfVisualizer, PerfProfiler, QmlProfiler) +dev-qt/qt-creator:tracing - Build plugins for tracing requiring extra dependencies (AppStatisticsMonitor, CtfVisualizer, PerfProfiler, QmlProfiler) dev-qt/qt-creator:webengine - Use dev-qt/qtwebengine with the help USE rather than bundled litehtml dev-qt/qt-docs:3d - Install documentation for dev-qt/qt3d dev-qt/qt-docs:activeqt - Install documentation for ActiveQt (unpackaged, Windows-only) @@ -2681,15 +2682,18 @@ dev-qt/qtbase:evdev - Enable support for input devices via evdev dev-qt/qtbase:gssapi - Enable support for GSSAPI (virtual/krb5) dev-qt/qtbase:gtk - Build the GTK platform theme plugin dev-qt/qtbase:gui - Build Qt6Gui module +dev-qt/qtbase:journald - Log messages using sys-apps/systemd's journald rather than output to stderr (override with the QT_FORCE_STDERR_LOGGING=1 env var) dev-qt/qtbase:libinput - Enable support for input devices via dev-libs/libinput dev-qt/qtbase:libproxy - Use net-libs/libproxy for automatic HTTP/SOCKS proxy configuration dev-qt/qtbase:network - Build Qt6Network module dev-qt/qtbase:renderdoc - Enable support for capturing graphic's API calls using media-gfx/renderdoc dev-qt/qtbase:sql - Build Qt6Sql module +dev-qt/qtbase:syslog - Log messages using syslog rather than output to stderr (override with the QT_FORCE_STDERR_LOGGING=1 env var) dev-qt/qtbase:tslib - Enable support for touchscreen devices via x11-libs/tslib dev-qt/qtbase:widgets - Build Qt6Widgets module dev-qt/qtbluetooth:qml - Build QML/QtQuick bindings and imports dev-qt/qtcharts:qml - Build QML/QtQuick bindings and imports +dev-qt/qtconnectivity:neard - Use net-wireless/neard to access NFC devices dev-qt/qtconnectivity:nfc - Enable support for the Near Field Communication protocol dev-qt/qtcore:old-kernel - Disable syscalls not available on Linux kernels older than 4.11 dev-qt/qtdatavis3d:qml - Build QML/QtQuick bindings and imports @@ -2724,6 +2728,7 @@ dev-qt/qtpositioning:nmea - Build plugin for parsing NMEA (National Marine Elect dev-qt/qtpositioning:qml - Build QML bindings dev-qt/qtquickcontrols:widgets - Enable QtWidgets support dev-qt/qtquickcontrols2:widgets - Enable QtWidgets support +dev-qt/qtremoteobjects:qml - Build QML/QtQuick bindings and imports dev-qt/qtscript:scripttools - Build the QtScriptTools module (requires QtWidgets) dev-qt/qtscxml:qml - Build QML/QtQuick bindings and imports dev-qt/qtsensors:qml - Build QML bindings @@ -2739,12 +2744,14 @@ dev-qt/qttools:pixeltool - Build Qt Pixeltool dev-qt/qttools:qdbus - Build the Qt D-Bus Interface (D-Bus Viewer requires USE=widgets) dev-qt/qttools:qdoc - Build Qt Documentation Generator dev-qt/qttools:qml - Build QML/QtQuick bindings and imports +dev-qt/qttools:qmlls - Build the QtHelp plugin for the QML language server dev-qt/qttools:qtattributionsscanner - Build Qt Source Code Attribution Scanner dev-qt/qttools:qtdiag - Build Qt Diag dev-qt/qttools:qtplugininfo - Build Qt Plugin Info dev-qt/qttools:widgets - Enable QtWidgets support dev-qt/qtvirtualkeyboard:handwriting - Adds handwriting recognition integration support dev-qt/qtwayland:compositor - Enable support for the wayland compositor / server APIs +dev-qt/qtwayland:gnome - Build the GNOME-like decoration plugin (loaded by default with GNOME) dev-qt/qtwayland:qml - Build QML/QtQuick bindings and imports dev-qt/qtwayland:vulkan - Enable support for Vulkan-based server buffer integration dev-qt/qtwebchannel:qml - Build QML/QtQuick bindings and imports @@ -2776,6 +2783,7 @@ dev-ruby/faraday_middleware:oauth - Include FaradayMiddleware::OAuth dev-ruby/faraday_middleware:parsexml - Include FaradayMiddleware::ParseXml dev-ruby/faraday_middleware:rashify - Include FaradayMiddleware::Rashify dev-ruby/io-event:io-uring - Enable io_uring support, and use io_uring instead of epoll +dev-ruby/jwt:eddsa - Support EdDSA algorithm using dev-ruby/rbnacl dev-ruby/maruku:highlight - Enable source code highlighting via dev-ruby/syntax dev-ruby/mysql2:mariadb - Use mariadb bindings dev-ruby/net-ssh:chacha20 - Use dev-ruby/rbnacl for chacha20-poly1305@openssh.com support @@ -2829,12 +2837,11 @@ dev-tex/abntex:lyx - Install with app-office/lyx layout dev-tex/biblatex:biber - Install the unicode compatible backend processor dev-tex/pythontex:highlighting - Syntax highlighting using dev-python/pygments dev-texlive/texlive-basic:luajittex - Add support for LuaJitTeX: LuaTeX based on LuaJIT which is usually faster. -dev-texlive/texlive-context:luajittex - Add support for LuaJitTeX: LuaTeX based on LuaJIT which is usually faster. dev-util/Tensile:client - Build and install tensile_client executable to run benchmarks and tune GPU GEMM dev-util/babeltrace:elfutils - Build the dev-util/lttng-ust debug information filter component class dev-util/babeltrace:plugins - Build support for Babeltrace 2 Python plugins dev-util/bpftool:caps - Use sys-libs/libcap to enable unprivileged run support -dev-util/bpftool:llvm - Use sys-devel/llvm +dev-util/bpftool:llvm - Use sys-devel/llvm instead of libbfd (sys-libs/binutils-libs) for JIT disassembly dev-util/breakpad:tools - Build tools dev-util/buildbot:docker - Add support for worker docker command steps dev-util/buildbot:irc - Add support for status delivery through an ircbot. @@ -2914,13 +2921,16 @@ dev-util/google-perftools:pagesize-32k - Use 32K page size for tcmalloc. Larger dev-util/google-perftools:pagesize-64k - Use 64K page size for tcmalloc. Larger size makes tcmalloc faster, at the cost of using more space (due to internal fragmentation) dev-util/heaptrack:gui - Install Qt5-based analyzer tool dev-util/hfstospell:clang - Use different logic in ebuild when clang is used +dev-util/hip:hip - Build HIP runtime +dev-util/hip:opencl - Build OpenCL runtime +dev-util/hip:video_cards_amdgpu - Build for AMD platform +dev-util/hip:video_cards_nvidia - Build for Nvidia platform dev-util/intel-graphics-compiler:vc - Enable VectorCompiler for a better performance. dev-util/intel-graphics-system-controller:cli - Build CLI tools for flashing manually a firmware upgrade. -dev-util/kcov:binutils - Use sys-libs/binutils-libs for --verify support +dev-util/kcov:binutils - Use sys-libs/binutils-libs for `--verify` support dev-util/kdevelop:gdbui - Enable GUI for attaching GDB to a running process -dev-util/kdevelop:hex - Enable hex editor plugin via app-editors/okteta dev-util/kdevelop:qmake - Enable support for QMake build system -dev-util/kdevelop:reviewboard - Enable reviewboard support +dev-util/kdevelop:share - Enable support for patch sharing using kde-frameworks/purpose dev-util/kernelshark:custom-optimization - Build with user-specified compiler optimizations (-Os, -O0, -O1, -O2, -O3) from CFLAGS dev-util/kup:gitolite - Enable support for dev-vcs/gitolite in kup-server dev-util/libabigail:btf - Handle reading kernel debug files in BTF format via dev-libs/libbpf @@ -2950,6 +2960,7 @@ dev-util/ostree:sodium - Use libsodium for ed25519 dev-util/ostree:soup - Use libsoup for networking dev-util/perf:babeltrace - Enable dev-util/babeltrace support dev-util/perf:bpf - Enable support for eBPF features with dev-libs/libbpf +dev-util/perf:capstone - Use dev-libs/capstone for disassembly support dev-util/perf:clang - Enable builtin clang and LLVM support dev-util/perf:doc - Build documentation and man pages. With this USE flag disabled, the --help parameter for perf and its sub-tools will not be available. This is optional because it depends on a few documentation handling tools that are not always welcome on user systems. dev-util/perf:libpfm - Enable dev-libs/libpfm support @@ -2980,8 +2991,8 @@ dev-util/schroot:lvm - Enable support for chroots using LVM snapshots dev-util/schroot:zfs - Enable support for chroots using ZFS shapshots/clones dev-util/sdl-jstest:sdl - Enable media-libs/libsdl2 based input test dev-util/sdl-jstest:sdl1 - Enable media-libs/libsdl based input test +dev-util/selenium-manager:telemetry - Disable sending telemetry by default (avoid-stats config option). dev-util/sysprof:unwind - Use sys-libs/libunwind to unwind the stack -dev-util/trace-cmd:udis86 - Enable support for dev-libs/udis86 disassembler library dev-util/uftrace:capstone - Use capstone to provide dynamic tracing without recompilation dev-util/vulkan-tools:cube - Build the cube/cubepp demos dev-util/watchman:python - Install pywatchman bindings and the watchman-{wait,make} utils @@ -3060,14 +3071,15 @@ games-action/trine:launcher - Install GTK+ launcher games-action/trine-enchanted-edition:launcher - Install GTK+ launcher games-action/trine2:launcher - Install GTK+ launcher games-arcade/bomns:editor - enables building the level editor -games-arcade/burgerspace:network - Enable client-server support games-arcade/commandergenius:downloader - Allows some Keen games to be downloaded from the menu +games-arcade/jazz2:sdl - Prefer SDL2 over GLFW backend games-arcade/jazz2:server - Build the multiplayer game server games-arcade/jazz2-data:cc - Install The Christmas Chronicles additional data games-arcade/jazz2-data:demo - Use the free demo data instead of the full retail game data games-arcade/lbreakout2:themes - Install additional themes games-arcade/moleinvasion:music - Download and install the music files games-arcade/oshu:osu-skin - Include more complete osu-skin (other is minimal) +games-arcade/osu-lazer:pipewire - Use pipewire to enable sound output games-arcade/performous:midi - Enable MIDI I/O support games-arcade/performous:songs - Install a few demo songs games-arcade/performous:webcam - Enable Webcam support @@ -3100,6 +3112,7 @@ games-emulation/desmume:openal - Use media-libs/openal for microphone input games-emulation/desmume:wifi - Enable support for Wi-Fi (experimental and discouraged) games-emulation/dolphin:discord-presence - Enables Discord Rich Presence, show the current game on Discord games-emulation/dolphin:evdev - Enable evdev input support +games-emulation/dolphin:llvm - Enables LLVM support, for disassembly games-emulation/dolphin:log - Increase logging output games-emulation/dolphin:mgba - Enables GBA controllers emulation using libmgba. games-emulation/dosbox:core-inline - Enable memory-increasing inlines for better performance but requiring more build time @@ -3146,6 +3159,7 @@ games-emulation/mupen64plus:ui-m64py - Enable PyQt5 UI using games-emulation/m64 games-emulation/mupen64plus:video-glide64mk2 - Enable Glide64mk2 video plugin. games-emulation/mupen64plus:video-rice - Enable Rice video plugin. games-emulation/mupen64plus-core:debugger - Build the debugger +games-emulation/mupen64plus-core:netplay - Enable netplay functionality games-emulation/mupen64plus-core:new-dynarec - Enable new experimental dynamic recompiler implementation (only for x86 and arm) games-emulation/mupen64plus-core:opencv - Support video capture via media-libs/opencv games-emulation/mupen64plus-core:osd - Overlay emulator messages using on-screen-display @@ -3153,6 +3167,10 @@ games-emulation/mupen64plus-video-glide64mk2:hires - Support hi-resolution textu games-emulation/pcsx2:clang - Use Clang compiler to build (the only compiler that is currently supported by upstream on Linux, do not report bugs if force-disabled) games-emulation/pcsx2:sndio - Enable support for the media-sound/sndio backend games-emulation/ppsspp:discord - Enable interfacing with a locally running Discord desktop client +games-emulation/rmg:angrylion-plugin - Enable the mupen64plus-video-angrylion-plus XMAME licensed plugin +games-emulation/rmg:discord - Enable Discord RPC support +games-emulation/rmg:dynarec - Enable the new dynarec for the mupen64plus-core plugin +games-emulation/rmg:rust-plugin - Enable the mupen64plus-input-gca rust plugin games-emulation/snes9x:libretro - Build libretro port games-emulation/snes9x:netplay - Enable playing ROMs over the network (not recommended) games-emulation/vbam:link - Enable GBA linking functionality @@ -3354,6 +3372,7 @@ games-strategy/wesnoth:server - Enable compilation of server games-util/gslist:web - Enable the web interface games-util/heroic-bin:gamescope - Run Heroic Launcher inside gamescope games-util/lgogdownloader:gui - Enable GUI login support for passing reCAPTCHA +games-util/sc-controller:trayicon - Enable system tray icon games-util/slade:fluidsynth - Enable MIDI software synthesis using media-sound/fluidsynth games-util/wit:fuse - Enable image mount support via fuse gnome-base/gdm:bluetooth-sound - Allow loading of bluetooth sound modules. This may be necessary for accessibility screen readers, but may cause bluetooth sound issues for users logging in. @@ -3393,8 +3412,7 @@ gnome-base/nautilus:cloudproviders - Enable the cloudproviders support gnome-base/nautilus:gstreamer - Enable the Audio/Video file properties page gnome-base/nautilus:previewer - Use gnome-extra/sushi to preview files from the file mananger gnome-base/nautilus:sendto - Enable the nautilus-sendto extension to send files to various locations/devices -gnome-extra/cinnamon:desktop-portal - Enable sys-apps/xdg-desktop-portal backend implementation for Cinnamon -gnome-extra/cinnamon-control-center:gnome-online-accounts - Enable configuration panel for net-libs/gnome-online-accounts accounts +gnome-extra/cinnamon:internal-polkit - Use Cinnamon's internal polkit agent instead of gnome-extra/polkit-gnome. This does not currently support multi-user fast switching. gnome-extra/cinnamon-control-center:modemmanager - Enable support for mobile broadband devices using net-misc/modemmanager gnome-extra/cjs:sysprof - Enable profiling data capture support using dev-util/sysprof-capture gnome-extra/eiciel:nautilus - Build gnome-base/nautilus extension @@ -3411,6 +3429,7 @@ gnome-extra/gnome-network-displays:firewalld - Install firewalld zones gnome-extra/gnome-shell-extension-gsconnect:nautilus - Install Nautilus extension for sending files via GSConnect gnome-extra/gnome-software:firmware - Enable firmware update support through sys-apps/fwupd gnome-extra/gnome-software:flatpak - Enable support for flatpak applications using sys-apps/flatpak +gnome-extra/gnome-software:snap - Enable support for snap packages using app-containers/snapd gnome-extra/gnome-software:sysprof - Enable profiling data capture support using dev-util/sysprof-capture gnome-extra/gnome-system-monitor:systemd - Display sys-apps/systemd metadata, e.g. unit names, for running processes gnome-extra/libgda:canvas - Enable support for x11-libs/goocanvas @@ -3447,16 +3466,16 @@ gui-apps/waybar:mpd - Enable support for the Music Player Daemon gui-apps/waybar:mpris - Enable support for mpris gui-apps/waybar:network - Enable libnl support for network related features gui-apps/waybar:pipewire - Enable support for pipewire -gui-apps/waybar:popups - Enable popup support with gtk-layer-shell gui-apps/waybar:pulseaudio - Enable support for volume control via PulseAudio gui-apps/waybar:sndio - Enable support for volume control via sndio gui-apps/waybar:tray - Enable support for tray gui-apps/waybar:wifi - Enable support for wifi/rfkill gui-apps/waypipe:dmabuf - Use DMABUFs for data exchange and hardware decoding gui-apps/waypipe:ffmpeg - Link with ffmpeg to allow buffer displays using video streams -gui-apps/waypipe:systemtap - Enable SystemTAP/DTrace tracing +gui-apps/waypipe:systemtap - Enable SystemTap/DTrace tracing gui-apps/wayvnc:gbm - enable GPU-side screencopy (experimental) gui-apps/wayvnc:tracing - Trace kernel and memory calls +gui-apps/wf-recorder:pipewire - Enable support for audio capture via media-video/pipewire. gui-apps/wf-recorder:pulseaudio - Enable support for audio capture via PulseAudio gui-libs/gtk:broadway - Enable the GDK Broadway backend. gui-libs/gtk:cloudproviders - Enable GtkPlacesSidebar to access cloud services @@ -3481,13 +3500,12 @@ gui-libs/wlroots:drm - Enable Direct Rendering Management gui-libs/wlroots:libinput - Enable support for input devices via dev-libs/libinput gui-libs/wlroots:liftoff - Enable support for libliftoff KMS plane backend gui-libs/wlroots:session - Enable session support (is required for DRM and libinput) -gui-libs/wlroots:tinywl - Install the minimal wayland client, tinywl gui-libs/wlroots:x11-backend - Enable support for handling input/output devices through x11-libs/libxcb gui-libs/wlroots:xcb-errors - Better error reporting when using xwayland gui-libs/xdg-desktop-portal-wlr:elogind - Enable support for rootless session via elogind +gui-wm/gamescope:libei - Enable emulated input using dev-libs/libei gui-wm/gamescope:pipewire - Enable screen capture via PipeWire gui-wm/gamescope:wsi-layer - Enable the WSI layer (required for HDR) -gui-wm/hikari:X - Enable support for X11 applications (XWayland) gui-wm/hyprland:legacy-renderer - Enable legacy renderer gui-wm/sway:X - Enable support for X11 applications (XWayland) gui-wm/sway:swaybar - Install 'swaybar': sway's status bar component @@ -3495,17 +3513,13 @@ gui-wm/sway:swaynag - Install 'swaynag': shows a message with buttons gui-wm/sway:tray - Enable support for StatusNotifierItem tray specification gui-wm/sway:wallpapers - Install sway's default wallpaper image gui-wm/wayfire:X - Enable support for X11 applications (XWayland). -gui-wm/wayfire:gles - use libglvnd to do animations more efficiently gui-wm/wayfire:gles3 - Enable OpenGL ES 3.x Features. -gui-wm/wayfire:system-wfconfig - Use the system-wide gui-libs/wf-config instead of building as a submodule. It will block system-wide gui-libs/wf-config from being installed. -gui-wm/wayfire:system-wlroots - Use the system-wide gui-libs/wlroots instead of building as a submodule. It will block system-wide gui-libs/wlroots from being installed. kde-apps/akonadi:designer - Install plugin for dev-qt/designer -kde-apps/akonadi:kaccounts - Enable support for system-wide defined KAccounts kde-apps/akonadi:tools - Install tools for developers and testing +kde-apps/akonadi:webengine - Enable support for system-wide defined KAccounts kde-apps/analitza:eigen - Enable dev-cpp/eigen mathematical templates support kde-apps/ark:zip - Enable ZIP archive support via dev-libs/libzip kde-apps/cantor:R - Enable dev-lang/R backend support -kde-apps/cantor:analitza - Enable kde-apps/analitza backend support kde-apps/cantor:julia - Enable dev-lang/julia backend support kde-apps/cantor:qalculate - Enable sci-libs/libqalculate backend support kde-apps/dolphin:activities - Track which folders are frequently accessed on a Plasma desktop @@ -3514,7 +3528,6 @@ kde-apps/gwenview:fits - Enable support for NASA's sci-libs/cfitsio library kde-apps/gwenview:mpris - Enable support for MPRIS2 interface, requiring dev-qt/qtdbus as dependency. kde-apps/gwenview:share - Enable support for a share menu using kde-frameworks/purpose kde-apps/k3b:webengine - Use dev-qt/qtwebengine for fancy k3bdiskinfoview -kde-apps/kaccounts-providers:webengine - Enable Nextcloud KAccounts plugin using dev-qt/qtwebengine kde-apps/kalarm:pim - Enable birthday import, email functions etc. using kde-apps/akonadi kde-apps/kalzium:editor - Enable the embedded molecule editor/viewer kde-apps/kalzium:solver - Enable the equation solver @@ -3523,7 +3536,6 @@ kde-apps/kate-addons:lspclient - Enable LSP (Language Server Protocol) client pl kde-apps/kate-addons:projects - Enable Project plugin for executing queries on SQL DBs kde-apps/kate-addons:snippets - Enable Snippets Tool View plugin to manage or download code snippets kde-apps/kate-addons:sql - Enable SQL plugin for executing queries on SQL DBs -kde-apps/kate-lib:activities - Enable Plasma Activities support via kde-plasma/plasma-activities kde-apps/kde-apps-meta:accessibility - Pull in kde-apps/kdeaccessibility-meta packages kde-apps/kde-apps-meta:admin - Pull in kde-apps/kdeadmin-meta packages kde-apps/kde-apps-meta:education - Pull in kde-apps/kdeedu-meta packages @@ -3536,7 +3548,6 @@ kde-apps/kde-apps-meta:sdk - Pull in developer-specific meta-packages kde-apps/kde-apps-meta:utils - Pull in kde-apps/kdeutils-meta packages kde-apps/kdeadmin-meta:cron - Installs KDE application for virtual/cron configuration kde-apps/kdecore-meta:share - Install kde-frameworks/purpose for share file context menu actions in kde-apps/dolphin -kde-apps/kdecore-meta:thumbnail - Install kde-apps/ffmpegthumbs and kde-apps/thumbnailers for thumbnail generation in kde-apps/dolphin kde-apps/kdecore-meta:webengine - Enable www-client/falkon which depends on dev-qt/qtwebengine kde-apps/kdeedu-meta:webengine - Enable packages requiring dev-qt/qtwebengine kde-apps/kdegraphics-meta:color-management - Enable color management via media-libs/opencolorio @@ -3577,50 +3588,16 @@ kde-apps/kio-extras:nfs - Enable NFS support using net-libs/libtirpc kde-apps/kio-extras:phonon - Enable file audio preview plugin using media-libs/phonon kde-apps/kio-extras:sftp - Enable SFTP protocol support using net-libs/libssh kde-apps/kio-extras:taglib - Enable audio thumbnails via media-libs/taglib -kde-apps/kio-extras-kf5:X - Enable support for XCursor thumbnails via x11-libs/libX11 -kde-apps/kio-extras-kf5:activities - Enable activities KIO worker and fileitem plugin -kde-apps/kio-extras-kf5:ios - Enable AFC (Apple File Conduit) KIO worker for iOS devices support -kde-apps/kio-extras-kf5:kf6compat - Disable components colliding with KF6, depend on KF6 components instead -kde-apps/kio-extras-kf5:man - Enable manpages KIO worker -kde-apps/kio-extras-kf5:nfs - Enable NFS support using net-libs/libtirpc -kde-apps/kio-extras-kf5:phonon - Enable file audio preview plugin using media-libs/phonon -kde-apps/kio-extras-kf5:sftp - Enable SFTP protocol support using net-libs/libssh -kde-apps/kio-extras-kf5:taglib - Enable audio thumbnails via media-libs/taglib kde-apps/kleopatra:pim - Enable WKS publishing support using kde-apps/kmail kde-apps/kmag:keyboardfocus - Enable keyboard focus tracking kde-apps/konqueror:activities - Enable kactivities support -kde-apps/kopete:addbookmarks - Automatically add incoming urls to bookmarks. -kde-apps/kopete:autoreplace - Automatically replace selected text -kde-apps/kopete:contactnotes - Enables writing personal notes for contacts. -kde-apps/kopete:gadu - Enable the Gadu protocol handler. -kde-apps/kopete:groupwise - Enable the Groupwise protocol handler. -kde-apps/kopete:highlight - Allows you to specify highlights on specific events. -kde-apps/kopete:history - Enables saving chat history. -kde-apps/kopete:latex - Embed latex formatted text into messages. -kde-apps/kopete:meanwhile - Enable the Sametime protocol handler. -kde-apps/kopete:nowlistening - Shows song you currently listen to in your status/etc. Bindings for many players. -kde-apps/kopete:otr - Allows crypting your chat (drugs and talking nonsense are considered as good alternatives ;]). -kde-apps/kopete:pipes - Send messages to external pipe. -kde-apps/kopete:privacy - Filter for incoming messages -kde-apps/kopete:statistics - Everybody loves statistic graphs, especially cake ones. ;] -kde-apps/kopete:testbed - Enable the testbed protocol. -kde-apps/kopete:texteffect - Various fancy text effects for your messages (don't ever consider writing us with this enabled ;]). -kde-apps/kopete:translator - Translate incoming and outgoing messages. -kde-apps/kopete:urlpicpreview - Enables in conversation pictures preview. -kde-apps/kopete:webpresence - Show your status and some more information on web. -kde-apps/kopete:winpopup - Enable pop-up messages sending on windows. (same as good old "net send" messages ;]) -kde-apps/kopete:zeroconf - Enable Link-Local Messaging via the bonjour protocol. -kde-apps/kpimtextedit:designer - Build plugins for dev-qt/designer kde-apps/krdc:activities - Enable Plasma Activities support via kde-plasma/plasma-activities kde-apps/ksystemlog:kdesu - Run as root using kdesu from kde-plasma/kde-cli-tools kde-apps/ktouch:X - Enable support for X11 Keyboard Layout Detection kde-apps/kwave:qtmedia - Enable playback via Qt5Multimedia -kde-apps/libkcddb:kf6compat - Disable components colliding with KF6, depend on KF6 components instead -kde-apps/libkcompactdisc:kf6compat - Disable components colliding with KF6, depend on KF6 components instead kde-apps/libkdepim:designer - Build plugins for dev-qt/designer kde-apps/libkgapi:kf6compat - Disable components colliding with KF6, depend on KF6 components instead kde-apps/libkleo:fancyviewer - Use kde-apps/kpimtextedit for an improved audit log viewer -kde-apps/libksane:kf6compat - Disable components colliding with KF6, depend on KF6 components instead kde-apps/libksane:kwallet - Enable encrypted storage of passwords with kde-frameworks/kwallet kde-apps/mailcommon:designer - Build plugins for dev-qt/designer kde-apps/marble:aprs - Enable support for APRS data sources @@ -3632,18 +3609,19 @@ kde-apps/marble:shapefile - Enable support for ESRI shapefiles kde-apps/marble:webengine - Use dev-qt/qtwebengine for embedded web browser kde-apps/okular:crypt - Enable support for password-encrypted documents via kde-frameworks/kwallet kde-apps/okular:epub - Enable E-Book support via app-text/ebook-tools -kde-apps/okular:image-backend - Enable image viewing support kde-apps/okular:markdown - Enable Markdown support via app-text/discount kde-apps/okular:mobi - Enable mobipocket support via kde-apps/kdegraphics-mobipocket kde-apps/okular:phonon - Enable sound support via media-libs/phonon -kde-apps/okular:plucker - Enable Plucker E-Book for Palm OS devices support kde-apps/okular:qml - Install Okular Qml components kde-apps/okular:share - Enable support for a share menu using kde-frameworks/purpose kde-apps/parley:webengine - Build browser integration for the editor, requires dev-qt/qtwebengine kde-apps/pimcommon:designer - Build plugins for dev-qt/designer kde-apps/spectacle:share - Enable support for a share menu using kde-frameworks/purpose kde-apps/step:qalculate - Enable the libqalculate library for unit conversion +kde-apps/thumbnailers:blender - Enable blender thumbnail generation using kde-frameworks/karchive +kde-apps/thumbnailers:gettext - Enable PO file thumbnail generation using kde-apps/kdesdk-thumbnailers kde-apps/thumbnailers:mobi - Enable mobipocket thumbnail generation using kde-apps/kdegraphics-mobipocket +kde-apps/thumbnailers:video - Enable video thumbnail generation using kde-apps/ffmpegthumbs kde-apps/umbrello:php - Enable PHP import support using dev-util/kdevelop and dev-util/kdevelop-pg-qt kde-apps/yakuake:absolute-position - Use kde-plasma/kwayland for absolute window positioning in KWin kde-frameworks/baloo:kf6compat - Disable components colliding with KF6, depend on KF6 components instead @@ -3658,7 +3636,6 @@ kde-frameworks/kiconthemes:designer - Build plugins for dev-qt/designer kde-frameworks/kimageformats:eps - Support the EPS graphics file format kde-frameworks/kinit:caps - Capabilities support for improved security and better OOM handling kde-frameworks/kio:designer - Build plugins for dev-qt/designer -kde-frameworks/kio:kf6compat - Disable components colliding with KF6, depend on KF6 components instead kde-frameworks/kio:kwallet - Enable permanent storage of passwords for kpasswdserver with kde-frameworks/kwallet kde-frameworks/kitemmodels:qml - Enable QML support via dev-qt/qtdeclarative kde-frameworks/kitemviews:designer - Build plugins for dev-qt/designer @@ -3672,7 +3649,6 @@ kde-frameworks/kplotting:designer - Build plugins for dev-qt/designer kde-frameworks/krunner:activities - Enable search runner for KDE Activities history kde-frameworks/ktexteditor:editorconfig - Enable support for EditorConfig configuration files kde-frameworks/ktextwidgets:designer - Build plugins for dev-qt/designer -kde-frameworks/kuserfeedback:kf6compat - Disable components colliding with KF6, depend on KF6 components instead kde-frameworks/kwallet:gpg - Support wallets with GnuPG encryption in addition to the default blowfish-encrypted file kde-frameworks/kwallet:kf6compat - Disable components colliding with KF6, depend on KF6 components instead kde-frameworks/kwidgetsaddons:designer - Build plugins for dev-qt/designer @@ -3680,7 +3656,7 @@ kde-frameworks/kxmlgui:designer - Build plugins for dev-qt/designer kde-frameworks/networkmanager-qt:teamd - Enable Teamd control support kde-frameworks/prison:qml - Enable QML/QtQuick support via dev-qt/qtdeclarative kde-frameworks/purpose:kaccounts - Enable support for system-wide defined KAccounts -kde-frameworks/purpose:kf6compat - Disable components colliding with KF6, depend on KF6 components instead +kde-frameworks/purpose:webengine - Enable support for system-wide defined KAccounts kde-frameworks/sonnet:aspell - Enable the app-text/aspell spell-checking backend kde-frameworks/sonnet:designer - Build plugins for dev-qt/designer kde-frameworks/sonnet:hunspell - Enable the app-text/hunspell spell-checking backend @@ -3690,6 +3666,7 @@ kde-misc/kdeconnect:pulseaudio - Enable system volume control plugin using media kde-misc/kdeconnect:telephony - Enable telephony plugin using kde-frameworks/modemmanager-qt kde-misc/kio-gdrive:kf6compat - Disable components colliding with KF6, depend on KF6 components instead kde-misc/kio-gdrive:share - Enable support for a share menu using kde-frameworks/purpose +kde-misc/krename:office - Enable support for file naming based on ODF metadata kde-misc/tellico:bibtex - Add support for bibtex importing using btparse from dev-perl/Text-BibTeX kde-misc/tellico:discid - Add support for reading disc IDs from audio CDs kde-misc/tellico:yaz - Add support for searching Z39.50 databases @@ -3700,28 +3677,23 @@ kde-plasma/discover:webengine - Enable webflow support using dev-qt/qtwebview an kde-plasma/drkonqi:systemd - Enable Coredumpd integration kde-plasma/kde-cli-tools:kdesu - Build graphical frontend for kde-frameworks/kdesu kde-plasma/kdeplasma-addons:alternate-calendar - Support alternate calendar systems (currently Chinese or Indian) via dev-libs/icu -kde-plasma/kdeplasma-addons:networkmanager - Disable wallpaper update when using metered connections kde-plasma/kdeplasma-addons:share - Enable applet for quickly sharing data to a variety of sources kde-plasma/kdeplasma-addons:webengine - Enable dictionary and web browser applets using dev-qt/qtwebengine kde-plasma/kinfocenter:usb - Show USB device information kde-plasma/ksystemstats:networkmanager - Enable improved backend for Network statistics using kde-frameworks/networkmanager-qt kde-plasma/kwin:lock - Enable screen locking via kde-plasma/kscreenlocker -kde-plasma/kwin:multimedia - Enable effect video button in desktop effects KCM kde-plasma/kwin:screencast - Enable screencast portal using media-video/pipewire kde-plasma/kwin:shortcuts - Enable global shortcuts support via kde-plasma/kglobalacceld -kde-plasma/libksysguard:designer - Build plugins for dev-qt/designer -kde-plasma/libksysguard:webengine - Enable display of detailed memory information using dev-qt/qtwebengine. kde-plasma/libplasma:kf6compat - Disable components colliding with KF6, depend on KF6 components instead kde-plasma/plasma-desktop:ibus - Use ibus input method via app-i18n/ibus -kde-plasma/plasma-desktop:kaccounts - Build the OpenDesktop integration plugin kde-plasma/plasma-desktop:scim - Enable applets that use app-i18n/scim +kde-plasma/plasma-desktop:webengine - Build the OpenDesktop integration plugin kde-plasma/plasma-firewall:firewalld - Build net-firewall/firewalld backend kde-plasma/plasma-firewall:ufw - Build net-firewall/ufw backend kde-plasma/plasma-meta:browser-integration - Enable integration with Chrome/Firefox with browser extensions kde-plasma/plasma-meta:colord - Enable kde-plasma/kwin color management via x11-misc/colord kde-plasma/plasma-meta:crash-handler - Pull in kde-plasma/drkonqi for assisted upstream crash reports kde-plasma/plasma-meta:crypt - Pull in kde-plasma/plasma-vault for encrypted vaults integration -kde-plasma/plasma-meta:desktop-portal - Enable sys-apps/xdg-desktop-portal backend implementation for Plasma kde-plasma/plasma-meta:discover - Pull in resources management GUI; a centralised GHNS alternative and optional sys-apps/fwupd frontend kde-plasma/plasma-meta:display-manager - Pull in a graphical display manager kde-plasma/plasma-meta:firewall - Pull in kde-plasma/plasma-firewall for system firewall administration @@ -3729,7 +3701,6 @@ kde-plasma/plasma-meta:flatpak - Pull in kde-plasma/flatpak-kcm for flatpak perm kde-plasma/plasma-meta:grub - Pull in Breeze theme for sys-boot/grub kde-plasma/plasma-meta:gtk - Enable Breeze widget style and system settings module for GTK+ kde-plasma/plasma-meta:kwallet - Enable support for KWallet auto-unlocking via kde-plasma/kwallet-pam -kde-plasma/plasma-meta:legacy-systray - Add support for legacy applications using kde-plasma/xembed-sni-proxy kde-plasma/plasma-meta:oxygen-theme - Pull in Oxygen icons, sound theme and visual style for KDE Plasma kde-plasma/plasma-meta:plymouth - Pull in Breeze theme for sys-boot/plymouth kde-plasma/plasma-meta:pulseaudio - Install Plasma applet for PulseAudio volume management @@ -3745,8 +3716,6 @@ kde-plasma/plasma-meta:webengine - Use kde-apps/khelpcenter to access the locall kde-plasma/plasma-meta:xwayland - Enable Wayland windows screensharing to XWayland applications via gui-apps/xwaylandvideobridge kde-plasma/plasma-nm:openconnect - Build support for the OpenConnect VPN client kde-plasma/plasma-nm:teamd - Enable Teamd control support -kde-plasma/plasma-welcome:discover - Pull in resources management GUI; a centralised GHNS alternative and optional sys-apps/fwupd frontend -kde-plasma/plasma-welcome:kaccounts - Build the OpenDesktop integration plugin kde-plasma/plasma-workspace:appstream - Enable AppStream software metadata support kde-plasma/plasma-workspace:geolocation - Enables dataengine providing location information kde-plasma/plasma-workspace:policykit - Enable locale generation and Users KCM using sys-auth/polkit and sys-apps/accountsservice @@ -3755,7 +3724,6 @@ kde-plasma/plasma-workspace:telemetry - Enable User Feedback control module for kde-plasma/plasma-workspace:wallpaper-metadata - Show metadata for image wallpaper plugin using kde-apps/libkexiv2 kde-plasma/powerdevil:brightness-control - Enable screen brightness control using app-misc/ddcutil kde-plasma/powerdevil:caps - Capabilities support for scheduled wakeup which can wake from suspend (CAP_WAKE_ALARM) -kde-plasma/powerdevil:wireless - Enable wireless energy saving actions via kde-frameworks/bluez-qt and kde-frameworks/networkmanager-qt lxqt-base/liblxqt:backlight - Enable backlight control features. lxqt-base/lxqt-config:monitor - Build monitor settings tool lxqt-base/lxqt-config:touchpad - Build touchpad settings tool @@ -3764,9 +3732,9 @@ lxqt-base/lxqt-meta:admin - Install lxqt-base/lxqt-admin lxqt-base/lxqt-meta:archiver - Install app-arch/lxqt-archiver lxqt-base/lxqt-meta:desktop-portal - Enable the LXQt sys-apps/xdg-desktop-portal backend implementation lxqt-base/lxqt-meta:display-manager - Install a graphical display manager -lxqt-base/lxqt-meta:filemanager - Install x11-misc/pcmanfm-qtfile manager -lxqt-base/lxqt-meta:lximage - Install media-gfx/lximage-qtimage viewer -lxqt-base/lxqt-meta:minimal - Do not install x11-wm/openboxwindow manager +lxqt-base/lxqt-meta:filemanager - Install x11-misc/pcmanfm-qt file manager +lxqt-base/lxqt-meta:lximage - Install media-gfx/lximage-qt image viewer +lxqt-base/lxqt-meta:minimal - Do not install x11-wm/openbox window manager lxqt-base/lxqt-meta:nls - Install dev-qt/qttranslations to better support different locales lxqt-base/lxqt-meta:powermanagement - Install lxqt-base/lxqt-powermanagement package lxqt-base/lxqt-meta:processviewer - Install x11-misc/qps package @@ -3776,6 +3744,7 @@ lxqt-base/lxqt-meta:ssh-askpass - Install lxqt-base/lxqt-openssh-askpass user pa lxqt-base/lxqt-meta:sudo - Install lxqt-base/lxqt-sudo lxqt-base/lxqt-meta:terminal - Install x11-terms/qterminal package lxqt-base/lxqt-meta:trash - Install gnome-base/gvfs to enable 'trash' functionality in x11-misc/pcmanfm-qt +lxqt-base/lxqt-meta:window-manager - Install kde-plasma/kwin window manager lxqt-base/lxqt-panel:colorpicker - Build colorpicker plugin lxqt-base/lxqt-panel:cpuload - Build cpuload plugin lxqt-base/lxqt-panel:desktopswitch - Build desktopswitch plugin @@ -3804,7 +3773,6 @@ mail-client/balsa:rubrica - Adds support for rubrica addressbook mail-client/balsa:systray - Enable System Tray Icon support mail-client/claws-mail:archive - Enable archiving plugin mail-client/claws-mail:bogofilter - Build mail-filter/bogofilter plugin -mail-client/claws-mail:gdata - Enable plugin for access to Google data providers mail-client/claws-mail:libcanberra - Enable sound notification in connection with USE=notification mail-client/claws-mail:libnotify - Enable notification on the desktop in connection with USE=notification mail-client/claws-mail:litehtml - Enable dev-libs/gumbo html viewer plugin @@ -3867,6 +3835,7 @@ mail-client/thunderbird:libproxy - Enable libproxy support mail-client/thunderbird:openh264 - Use media-libs/openh264 for H.264 support instead of downloading binary blob from Mozilla at runtime mail-client/thunderbird:pgo - Add support for profile-guided optimization using gcc-4.5, for faster binaries. This option will double the compile time. mail-client/thunderbird:pulseaudio - Add sound server support via media-libs/libpulse (may be PulseAudio or Pipewire, or apulse if installed) +mail-client/thunderbird:rust-extensions - Compile and install experimental rust extensions, that may become part of Thunderbird some day. mail-client/thunderbird:sndio - Enable support for the media-sound/sndio backend mail-client/thunderbird:system-av1 - Use the system-wide media-libs/dav1d and media-libs/libaom library instead of bundled. mail-client/thunderbird:system-harfbuzz - Use the system-wide media-libs/harfbuzz and media-gfx/graphite2 instead of bundled. @@ -4089,9 +4058,9 @@ media-gfx/darktable:tools - Install tools for generating base curves and noise p media-gfx/digikam:addressbook - Enable akonadi contact integration media-gfx/digikam:imagemagick - Enable support for additional image formats such as XCF, FITS, HEIC etc. media-gfx/digikam:lensfun - Enable support for media-libs/lensfun -media-gfx/digikam:mediaplayer - Enable integrated video player media-gfx/digikam:panorama - Build the panorama plugin which requires media-gfx/hugin media-gfx/digikam:semantic-desktop - Enable kde-frameworks/kfilemetadata support +media-gfx/digikam:video - Enable integrated video player media-gfx/eog-plugins:map - Enable world map display using media-libs/libchamplain media-gfx/eom:imagemagick - Use media-gfx/imagemagick as an external backend for the thumbnailer media-gfx/exact-image:swig - Adds Swig support dev-lang/swig @@ -4100,6 +4069,7 @@ media-gfx/exiv2:webready - Support reading metadata over the internet media-gfx/fbida:X - Install the Motif based image viewer "ida" media-gfx/fbida:fbcon - Install the framebuffer image viewer "fbi" media-gfx/fbida:ghostscript - Install the framebuffer ghostscript viewer "fbgs" +media-gfx/fig2dev:ghostscript - Require app-text/ghostscript-gpl to export PDF an bitmap formats media-gfx/fontforge:truetype-debugger - Enable truetype debugger in fontforge media-gfx/fontforge:woff2 - Enable support for WOFF2 format media-gfx/fotowall:webcam - Enable webcam support @@ -4121,16 +4091,19 @@ media-gfx/freecad:points - Build the points module and workbench for working wit media-gfx/freecad:raytracing - Build the raytracing module and workbench for raytracing and rendering media-gfx/freecad:robot - Build the robot module and workbench for studying robot movements media-gfx/freecad:show - Build the show module, a helper module for visibility automation +media-gfx/freecad:smesh - Build the Salome SMESH module media-gfx/freecad:surface - Build the surface module and workbench media-gfx/freecad:techdraw - Build the techdraw module and workbench, a more advanced and feature-rich successor of the drawing workbench media-gfx/freecad:tux - Build the Tux module media-gfx/geeqie:ffmpegthumbnailer - Enable video thumbnail support with media-video/ffmpegthumbnailer media-gfx/geeqie:map - Enable items GPS map display +media-gfx/gimp:fits - Enable support for loading/exporting FITS images media-gfx/gimp:vector-icons - Enable support for vector icons (experimental) media-gfx/graphicsmagick:dynamic-loading - Compile graphicsmagick with dynamically loadable modules media-gfx/graphicsmagick:fpx - Enable FlashPix support with media-libs/libfpx media-gfx/graphicsmagick:q16 - Set storage quantum size to 16 (~2*memory) media-gfx/graphicsmagick:q32 - Set storage quantum size to 32 (~5*memory) +media-gfx/graphicsmagick:zip - Build with dev-libs/libzip to support the OpenRaster (ORA) format. media-gfx/graphviz:X - Builds unflatten, vimdot, builds plugin -Txlib, and enables support for x11 in various other modules (needs cairo) media-gfx/graphviz:devil - Enables DevIL output plugin -Tdevil media-gfx/graphviz:gtk2 - Enables gtk+ output plugin -Tgtk (needs cairo) @@ -4159,8 +4132,10 @@ media-gfx/kphotoalbum:phonon - Enable media-libs/phonon video backend (known to media-gfx/kphotoalbum:share - Enable support for a share menu using kde-frameworks/purpose media-gfx/kphotoalbum:vlc - Enable media-video/vlc video backend (recommended for X11) media-gfx/krita:color-management - Enable color management via media-libs/opencolorio +media-gfx/krita:media - Enable sound support for animations via media-libs/mlt media-gfx/krita:mypaint-brush-engine - Enable MyPaint brush engine support media-libs/libmypaint media-gfx/krita:qtmedia - Enable sound support for animations via dev-qt/qtmultimedia +media-gfx/krita:xsimd - Enable usage of SIMD instructions via dev-cpp/xsimd media-gfx/librecad:tools - Build additional tool programs: tff2lff media-gfx/luminance-hdr:fits - Enable support for the FITS format media-gfx/mandelbulber:opencl - Enable GPU rendering support using OpenCL @@ -4194,6 +4169,7 @@ media-gfx/openvdb:utils - Build utility binaries media-gfx/photoqt:devil - Support additional image formats using media-libs/devil media-gfx/photoqt:freeimage - Support additional image formats using media-libs/freeimage media-gfx/photoqt:mpv - Support for video files using media-video/mpv +media-gfx/plantuml:ant-task - Provides classes used to manage PlantUML Ant task media-gfx/potrace:metric - default to a4 paper size and metric measurement media-gfx/povray:io-restrictions - POV-Ray's mechanism for control of I/O operations media-gfx/pqiv:archive - Enable support for images in archives and cbX comic book files @@ -4220,6 +4196,7 @@ media-libs/allegro:vga - Enables the VGA graphics driver media-libs/alsa-lib:alisp - Enable support for ALISP (ALSA LISP) interpreter for advanced features. media-libs/alure:dumb - Enable media-libs/dumb module library support media-libs/alure:fluidsynth - Enables Fluidsynth MIDI software synthesis +media-libs/assimp:collada - Add support for Collada interchange format through media-libs/opencollada media-libs/assimp:samples - Build viewer library media-libs/aubio:double-precision - Compile in double precision mode. media-libs/avidemux-core:system-ffmpeg - Use the ffmpeg provided by the system. @@ -4296,7 +4273,6 @@ media-libs/imlib2:text - Build text (TrueType font) functions media-libs/imlib2:zlib - Zlib loader support media-libs/intel-mediasdk:tools - Build analyse and inspect tools media-libs/jasper:heif - Enable experimental support for HEIF/HEIC, unsupported by upstream -media-libs/ksanecore:kf6compat - Disable components colliding with KF6, depend on KF6 components instead media-libs/leptonica:utils - Install command-line utilities media-libs/lib3mf:system-act - Use system-provided dev-go/act as code generator instead of package provided binaries. This flag will be removed after some time used for testing! media-libs/libafterimage:shaping - Use MIT shaped X windows extention. @@ -4333,8 +4309,10 @@ media-libs/libheif:aom - Use media-libs/libaom for AVIF encoding/decoding media-libs/libheif:gdk-pixbuf - Enable x11-libs/gdk-pixbuf plugin media-libs/libheif:go - Enable building dev-lang/go code/examples media-libs/libheif:rav1e - Use media-video/rav1e for AVIF encoding +media-libs/libheif:svt-av1 - Use media-libs/svt-av1 for SVT-AV1 encoding media-libs/libheif:x265 - Use media-libs/x265 for HEIF encoding -media-libs/libjxl:gdk-pixbuf - Build a gdk-pixbuf loader +media-libs/libjxl:gdk-pixbuf - Build a gdk-pixbuf loader. +media-libs/libjxl:jpeg - Enable full support for JPEG images. When disabled, only lossless conversion between JPEG and JPEG-XL is supported. media-libs/liblastfm:fingerprint - Build the lastfm-fingerprint library media-libs/libmp4v2:utils - Install command-line utilities media-libs/libmypaint:gegl - Add support for media-libs/gegl @@ -4356,7 +4334,7 @@ media-libs/libsdl:joystick - Control joystick support (disable at your own risk) media-libs/libsdl:sound - Control audio support (disable at your own risk) media-libs/libsdl:tslib - Build with tslib support for touchscreen devices media-libs/libsdl:video - Control video support (disable at your own risk) -media-libs/libsdl2:fcitx4 - Enable support for app-i18n/fcitx 4 +media-libs/libsdl2:fcitx - Enable support for app-i18n/fcitx media-libs/libsdl2:gles1 - include OpenGL ES 1.0 support media-libs/libsdl2:haptic - Enable the haptic (force feedback) subsystem media-libs/libsdl2:ibus - Enable support for app-i18n/ibus @@ -4376,9 +4354,6 @@ media-libs/libva-intel-driver:hybrid - Enable support for hybrid vaapi hardware media-libs/libva-intel-media-driver:redistributable - Install redistributable media kernel binaries (no source code) files (primarily needed for video encoding support) media-libs/libvisio:tools - Build conversion tools media-libs/libvmaf:embed-models - Compile default vmaf models into the library (needs app-editors/vim-core) -media-libs/libvpl:drm - Build with DRM support -media-libs/libvpl:experimental - Build dispatcher with experimental APIs -media-libs/libvpl:tools - Build decode/encode/analyse/inspect tools media-libs/libvpl-tools:drm - Build with DRM support media-libs/libvpx:highbitdepth - Enable 10 and 12 bit support for VP9. media-libs/libvpx:postproc - Enable additional post processing filters @@ -4391,7 +4366,6 @@ media-libs/lv2:plugins - Enables examples plugins. media-libs/lvtk:gtk2 - Enable x11-libs/gtk+:2 based GUI support media-libs/lvtk:tools - Compile and install ttl2c tool media-libs/mesa:d3d9 - Enable Direct 3D9 API through Nine state tracker. Can be used together with patched wine. -media-libs/mesa:gles1 - Enable GLESv1 support. media-libs/mesa:llvm - Enable LLVM backend for Gallium3D. media-libs/mesa:lm-sensors - Enable Gallium HUD lm-sensors support. media-libs/mesa:opencl - Enable the Rusticl Gallium OpenCL state tracker. @@ -4401,7 +4375,6 @@ media-libs/mesa:vdpau - Enable the VDPAU acceleration interface for the Gallium3 media-libs/mesa:vulkan-overlay - Build vulkan-overlay-layer which displays Frames Per Second and other statistics media-libs/mesa:wayland - Enable support for dev-libs/wayland media-libs/mesa:xa - Enable the XA (X Acceleration) API for Gallium3D. -media-libs/mesa:zink - Enable the Zink OpenGL-over-Vulkan Gallium driver media-libs/mesa-amber:gles1 - Enable GLESv1 support. media-libs/mesa-amber:wayland - Enable support for dev-libs/wayland media-libs/mlt:frei0r - Build the module for media-plugins/frei0r-plugins @@ -4417,7 +4390,6 @@ media-libs/noise-suppression-for-voice:vst3 - Enable the VST3 plugin media-libs/oidn:apps - Build the standalone denoise, self test, and benchmark binaries. media-libs/oidn:hip - Build OIDN with AMD HIP support. media-libs/oidn:openimageio - Enable OpenImageIO Support -media-libs/oneVPL-cpu:experimental - Enable experimental API media-libs/oneVPL-cpu:openh264 - Use media-libs/openh264 instead of media-libs/x264 media-libs/openal:pipewire - Enable support for the media-video/pipewire audio backend media-libs/openal:sndio - Enable support for the media-sound/sndio backend @@ -4460,16 +4432,18 @@ media-libs/openimageio:gui - Build iv (with Qt5) media-libs/openimageio:opencv - Enable OpenCV support via media-libs/opencv media-libs/openimageio:openvdb - Enable OpenVDB support via media-gfx/openvdb media-libs/openimageio:ptex - Enable Ptex texture mapping system file support via media-libs/ptex -media-libs/openimageio:qt5 - Build iv with Qt5 media-libs/openimageio:qt6 - Build iv with Qt6 media-libs/openimageio:tools - Build the command-line tools media-libs/opensubdiv:glew - Enable support for OpenGL Extension Wrangler Library (media-libs/glew) -media-libs/opensubdiv:glfw - Enable support for OpenGL FrameWork (media-libs/glfw) +media-libs/opensubdiv:glfw - Build all example files that uses (media-libs/glfw) media-libs/opensubdiv:ptex - Adds support for faster per-face texture mapping through media-libs/ptex media-libs/opensubdiv:python - Use dev-lang/python to process source and documentation source files media-libs/opensubdiv:tbb - Enable multithreading with the Intel Threads Building Blocks through dev-cpp/tbb media-libs/opensubdiv:tutorials - Install the tutorials media-libs/opus:custom-modes - Enable non-Opus modes, e.g. 44.1 kHz and 2^n frames +media-libs/opus:deep-plc - Enable Deep Packet Loss Concealment (PLC) +media-libs/opus:dred - Enable Deep REDundancy (DRED) +media-libs/opus:osce - Enable Opus Speech Coding Enhancement (OSCE) media-libs/opusfile:fixed-point - Enable fixed-point arithmetic operations media-libs/opusfile:float - Enable floating point arithmetic operations media-libs/opusfile:http - Enable http connections @@ -4480,7 +4454,6 @@ media-libs/osl:optix - Add support for NVIDIA's OptiX Raytracing Engine media-libs/osl:partio - Use media-libs/partio media-libs/osl:qt6 - Build the osltoy binary (with Qt6) media-libs/phonon:designer - Install plugin for dev-qt/designer -media-libs/phonon:vlc - Install VLC Phonon backend media-libs/phonon-gstreamer:network - Enable network streaming support via libsoup media-libs/portmidi:test-programs - Install various example programs media-libs/quarter:designer - Install plugin for dev-qt/designer @@ -4536,7 +4509,6 @@ media-libs/x264:pic - disable optimized assembly code that is not PIC friendly media-libs/x265:10bit - Add support for producing 10bits HEVC. media-libs/x265:12bit - Add support for producing 12bits HEVC. media-libs/x265:numa - Build with support for NUMA nodes. -media-libs/x265:pic - Disable optimized assembly code that is not PIC friendly media-libs/xine-lib:bluray - Enable playback of Blu-ray filesystems using media-libs/libbluray media-libs/xine-lib:dav1d - Enable support for media-libs/dav1d AV1 decoder media-libs/xine-lib:dxr3 - Enable support for DXR3 mpeg acceleration cards. @@ -4613,7 +4585,10 @@ media-radio/ax25-tools:X - Enable some X based configuration tools. media-radio/chirp:radioreference - pull in optional deps for query of radioreference media-radio/direwolf:hamlib - Enables support by the Hamlib amateur radio rig control library media-radio/fldigi:hamlib - Enables support by the Hamlib amateur radio rig control library to get/set frequency and mode of the ham radio in use +media-radio/svxlink:qt5 - Build and install qtel application +media-radio/svxlink:rtlsdr - Add support for rtlsdr hardware media-radio/tucnak:hamlib - Enables support by the Hamlib amateur radio rig control library to get/set frequency and mode of the ham radio +media-radio/tucnak:rtlsdr - Add support for rtlsdr hardware media-radio/unixcw:ncurses - Enables building the curses based morse code tutor program 'cwcp'. media-radio/xastir:geotiff - Install geotiff support. Allows using USGS DRG topo maps or other types of geotiff mapes/images media-sound/abcde:aiff - Enable support for Audio Interchange File Format (AIFF) output encoding @@ -4656,6 +4631,7 @@ media-sound/audiotools:twolame - Enable twolame support (MPEG Audio Layer 2 enco media-sound/bluez-alsa:aptx - aptX (HD) over Bluetooth (many Android compatible headphones) media-sound/bluez-alsa:hcitop - Enable top-like monitoring tool for HCI media-sound/bluez-alsa:ldac - Enable support for AOSP media-libs/libldac dispatcher +media-sound/bluez-alsa:liblc3 - Enable LC3 support media-sound/bluez-alsa:mpg123 - Enable support for MPEG audio playback via media-sound/mpg123 media-sound/bluez-alsa:ofono - Enable ofono elephony support media-sound/cadence:a2jmidid - Enables support for legacy ALSA sequencer applications in JACK MIDI system @@ -4714,7 +4690,6 @@ media-sound/easyeffects:calf - Enable use of media-plugins/calf for adding vario media-sound/easyeffects:doc - Install packages needed to display built-in user documentation media-sound/easyeffects:mda-lv2 - Enable use of media-plugins/mda-lv2 for the loudness FX media-sound/easyeffects:zamaudio - Enable use of media-plugins/zam-plugins for the maximizer FX -media-sound/easytag:nautilus - Build gnome-base/nautilus extension media-sound/ecasound:lv2 - Add support for Ladspa V2 media-sound/ecasound:oil - Use dev-libs/liboil for inner loop optimizations media-sound/elisa:mpris - Enable MPRIS support @@ -4727,8 +4702,6 @@ media-sound/gimmix:lyrics - Enable lyric fetching media-sound/guitarix:lv2 - Build lv2 plugins media-sound/guitarix:nsm - Build NSM (Non Session Manager) support media-sound/guitarix:standalone - Build standalone application -media-sound/herrie:http - Enable http streaming -media-sound/herrie:xspf - Enable support for reading and saving XSPF playlists media-sound/hydrogen:archive - Use libarchive instead of libtar media-sound/hydrogen:portmidi - Add portmidi support media-sound/jack-audio-connection-kit:pam - Add basic realtime configuration via sys-auth/realtime-base @@ -4746,7 +4719,6 @@ media-sound/klick:rubberband - Enable rubberband support media-sound/lame:frontend - Build and install the 'lame' executable frontend to lame libraries. media-sound/lame:mp3rtp - Build the mp3-to-RTP streaming utility. **UNSUPPORTED** media-sound/liblc3:tools - Enable extra tools -media-sound/lilypond:guile2 - Enable experimental support for Guile 2 media-sound/linux-show-player:midi - Allow cues to send, or trigger on, MIDI messages media-sound/linux-show-player:timecode - Support the sending of time code of running audio files over ArtNet, for instance to trigger cues in lighting-control software on lighting desks media-sound/linuxsampler:lv2 - Add support for Ladspa V2 @@ -4778,6 +4750,7 @@ media-sound/mpd:fluidsynth - Enables Fluidsynth MIDI software synthesis (discour media-sound/mpd:gme - Enables support for media-libs/game-music-emu for playing various video game music formats. media-sound/mpd:id3tag - Support for ID3 tags media-sound/mpd:inotify - Use the Linux kernel inotify subsystem to notice changes to mpd music library +media-sound/mpd:io-uring - Enable support for io_uring media-sound/mpd:lame - Support for MP3 streaming via Icecast2 media-sound/mpd:libmpdclient - Enable support for remote mpd databases media-sound/mpd:libsoxr - Enable the libsoxr resampler @@ -4797,10 +4770,10 @@ media-sound/mpd:systemd - Enable support for systemd socket activation media-sound/mpd:twolame - Support twolame MPEG-2 encoding media-sound/mpd:webdav - Enable using music from a WebDAV share media-sound/mpd:wildmidi - Enable MIDI support via wildmidi +media-sound/mpd:yajl - Enable JSON parsing via dev-libs/yajl media-sound/mpfc:wav - Enable wav audio codec support media-sound/mpg123:int-quality - Use rounding instead of fast truncation for integer output, where possible media-sound/mpg123-base:int-quality - Use rounding instead of fast truncation for integer output, where possible -media-sound/musescore:jumbo-build - Combine source files to speed up build process, requires more memory media-sound/musescore:omr - Enable PDF import (OMR - optical music recognition) media-sound/musescore:osc - Enable OSC remote control protocol media-sound/musescore:portmidi - Enable support for building against media-libs/portmidi @@ -4826,6 +4799,7 @@ media-sound/ncspot:cover - Support displaying the album cover media-sound/ncspot:mpris - Allow ncspot to be controlled via MPRIS API media-sound/ncspot:ncurses - Use cursive/ncurses-backend instead of crossterm or pancurses media-sound/ncspot:notify - Show what's playing via a notification +media-sound/owntone:chromecast - build and install Chromecast support media-sound/patchage:jack-dbus - Use Jack via D-Bus instead of libjack media-sound/picard:discid - Enable reading the ID of the inserted CD media-sound/picard:fingerprints - Enable calculation and lookup of AcoustID fingerprints @@ -4885,7 +4859,6 @@ media-sound/qmmp:soxr - Use the SoX resampling library media-sound/qmmp:stereo - Enable stereo effect media-sound/qmmp:tray - Build tray icon media-sound/qmmp:xmp - Enable module files renderer (modplug replacement) -media-sound/qpwgraph:trayicon - Build support for tray icon media-sound/qsampler:libgig - Enable libgig support for loading Gigasampler files and DLS (Downloadable Sounds) Level 1/2 files media-sound/qtractor:aubio - Enable media-libs/aubio support media-sound/qtractor:dssi - Enable support for DSSI Soft Synth Interface @@ -4913,7 +4886,7 @@ media-sound/spotify:local-playback - Allows playing local files with the Spotify media-sound/spotify:pax-kernel - Triggers a paxmarking of the main Spotify binary media-sound/spotify:pulseaudio - Controls the dependency on pulseaudio or apulse media-sound/strawberry:moodbar - Enable moodbar support -media-sound/strawberry:soup - Enable soup support +media-sound/strawberry:soup - Allow streaming with media-plugins/gst-plugins-soup media-sound/strawberry:vlc - Enable media-video/vlc backend media-sound/supercollider:ableton-link - Enable support for Ableton Link media-sound/supercollider:emacs - Enable the SCEL user interface @@ -4957,7 +4930,6 @@ media-tv/kodi:bluetooth - Enable JSON-RPC over BT for remote control connected v media-tv/kodi:bluray - Enable playback of Blu-ray filesystems media-tv/kodi:caps - Use sys-libs/libcap to bind to privileged ports as non-root media-tv/kodi:cec - Enable support for HDMI-CEC devices via libcec -media-tv/kodi:dav1d - Enables AV1 decoding via media-libs/dav1d media-tv/kodi:eventclients - Install full set of Kodi python evenclients and evenclients examples media-tv/kodi:gbm - Use the Graphics Buffer Manager for EGL on KMS. media-tv/kodi:gles - Use simplified OpenGLES instead of full-scale OpenGL @@ -4968,13 +4940,10 @@ media-tv/kodi:mysql - Enable support store of media library metadata on local or media-tv/kodi:nfs - Enable NFS client support media-tv/kodi:optical - Enable Audio CD playback, optical disks detection and reading (CD-ROM, Video CD, and others), and ISO optical disk images direct reading. DVD disks may require additional 'udf' flag. media-tv/kodi:pipewire - Enable pipewire support -media-tv/kodi:power-control - Enable control of shutdown, reboot, suspend, and hibernate -media-tv/kodi:raspberry-pi - Enable support for the Raspberry Pi media-tv/kodi:soc - Use additional media-video/ffmpeg patches for efficient playback on some SoCs (e.g. ARM, RISC-V) media-tv/kodi:system-ffmpeg - Use system ffmpeg instead of the bundled one media-tv/kodi:udev - Use udev rules to handle devices' permissions and hotplug support. Unless you know what you're doing do not disable this flag on Linux kernels. This is provided as an option for completeness. media-tv/kodi:udf - Enable UDF support. Required for playing blurays. -media-tv/kodi:upower - Use sys-power/upower to get battery level and active power source media-tv/kodi:webserver - Enable internal webserver media-tv/kodi:xslt - Enable metadata XSLT scrapers support with dev-libs/libxslt media-tv/linuxtv-dvb-apps:alevt - Build videotext decoder @@ -4998,12 +4967,8 @@ media-tv/mythtv:vpx - Enable VP8/VP9 support for media-libs/libvpx media-tv/mythtv:wrapper - Use Ubuntu mythtfrontend wrapper media-tv/mythtv:x265 - Enable h265 encoding using x265 media-tv/mythtv:xmltv - Support media-tv/xmltv TV listing - not used by Schedules Direct] -media-tv/tvheadend:capmt - Enable support for capmt (dvbapi) protocol -media-tv/tvheadend:constcw - Enable support for the constcw protocol -media-tv/tvheadend:cwc - Enable support for the cwc (newcamd) protocol media-tv/tvheadend:ddci - Enable support for DDCI hardware media-tv/tvheadend:dvbcsa - Enable decryption of the DVB Common Scrambling Algorithm -media-tv/tvheadend:dvben50221 - Enable support for hardware CAM media-tv/tvheadend:hdhomerun - Enable support for the HDHomeRun device media-tv/tvheadend:imagecache - Enable support for image caching media-tv/tvheadend:iptv - Enable support for Internet Protocol TV @@ -5014,7 +4979,6 @@ media-tv/tvheadend:vpx - Enable transcoding with the VP8/VP9 video codecs media-tv/tvheadend:x264 - Enable transcoding with the H.264 video codec media-tv/tvheadend:x265 - Enable transcoding with the HEVC video codec media-tv/tvheadend:xmltv - Use media-tv/xmltv -media-tv/v4l-utils:bpf - Enables support for IR BPF decoders. media-tv/xmltv:ar - Argentina tv listing grabber media-tv/xmltv:ch-search - Grabber for Switzerland media-tv/xmltv:eu-epgdata - include fanart URLs for some European countries. @@ -5038,6 +5002,8 @@ media-tv/xmltv:uk-tvguide - UK and Ireland tv listing grabber using TV Guide web media-tv/xmltv:zz-sdjson - Grabber for schedulesDirect.org SD-JSON service (many countries) media-tv/xmltv:zz-sdjson-sqlite - Grabber for schedulesDirect.org SD-JSON service (sqlite DB) media-video/aegisub:uchardet - Enable charset discovery via app-i18n/uchardet +media-video/amdgpu-pro-amf:pro - Pull media-libs/mesa as dependency +media-video/amdgpu-pro-amf:radv - Pull media-libs/amdgpu-pro-vulkan as dependency media-video/aravis:fast-heartbeat - Enable faster heartbeat rate. media-video/aravis:gstreamer - Build the GStreamer plugin. media-video/aravis:packet-socket - Enable packet socket support. @@ -5074,7 +5040,10 @@ media-video/ffmpeg:lcms - Enable ICC profile support via media-libs/lcms. media-video/ffmpeg:libaom - Enables media-libs/libaom based AV1 codec support. media-video/ffmpeg:libaribb24 - Enables ARIB text and caption decoding via media-libs/aribb24. media-video/ffmpeg:libdrm - Enables x11-libs/libdrm support for better screen grabbing and hardware accelerated codecs. +media-video/ffmpeg:libdvdnav - Uses media-libs/libdvdnav to enable DVD demuxing +media-video/ffmpeg:libdvdread - Uses media-libs/libdvdread to enable DVD demuxing media-video/ffmpeg:libilbc - Enables iLBC de/encoding via media-libs/libilbc. +media-video/ffmpeg:liblc3 - Enables LC3 de/encoding via media-sound/liblc3. media-video/ffmpeg:libplacebo - Adds flexible GPU-accelerated processing filter based on media-libs/libplacebo. media-video/ffmpeg:librtmp - Enables Real Time Messaging Protocol using librtmp (media-video/rtmpdump) in addition to FFmpeg's native implementation. media-video/ffmpeg:libsoxr - Enables audio resampling through media-libs/soxr. @@ -5091,7 +5060,9 @@ media-video/ffmpeg:openh264 - Enables H.264 encoding suppoprt via media-libs/ope media-video/ffmpeg:openssl - Enables dev-libs/openssl support. Adds support for encrypted network protocols (TLS/HTTPS). media-video/ffmpeg:pic - Force shared libraries to be built as PIC (this is slower) media-video/ffmpeg:postproc - Build and install libpostproc. +media-video/ffmpeg:qrcode - Enables QR encode generation via media-gfx/qrencode media-video/ffmpeg:qsv - Enable Intel Quick Sync Video via media-libs/intel-mediasdk (ffmpeg versions older than, and including, 5.1) or media-libs/libvpl (ffmpeg version newer than 5.1). +media-video/ffmpeg:quirc - Enables QR decoding via media-libs/quirc media-video/ffmpeg:rav1e - Enables AV1 encoding support via media-video/rav1e. media-video/ffmpeg:rubberband - Adds time-stretching and pitch-shifting audio filter based on media-libs/rubberband. media-video/ffmpeg:shaderc - Use media-libs/shaderc to compile GLSL @@ -5112,7 +5083,6 @@ media-video/ffmpeg:zimg - Enables media-libs/zimg based scale filter. media-video/ffmpeg:zvbi - Enables media-libs/zvbi based teletext decoder. media-video/ffmpeg-chromium:cpudetection - Enables runtime CPU detection (useful for bindist, compatibility on other CPUs) media-video/ffmpeg-chromium:gpl - Build GPL code. Should be enabled unless you require LGPL binaries. -media-video/ffmpeg-chromium:mmal - Enables Multi-Media Abstraction Layer (MMAL) decoding support: Available e.g. on the Raspberry Pi. media-video/guvcview:qt5 - Build with Qt5 interface instead Gtk+ media-video/handbrake:fdk - Support for encoding AAC using media-libs/fdk-aac. media-video/handbrake:gstreamer - Support for the streaming media framework from media-libs/gstreamer. @@ -5183,10 +5153,8 @@ media-video/mpv:drm - Enable Kernel Mode Setting / Direct Rendering Manager base media-video/mpv:gamepad - Enable gamepad input support media-video/mpv:libmpv - Enable the shared library and headers (used by frontends / plugins) media-video/mpv:lua - Enable Lua scripting, OSC (On Screen Controller) GUI, and net-misc/yt-dlp support -media-video/mpv:mmal - Enable Multi-Media Abstraction Layer (MMAL) decoding support: Available e.g. on the Raspberry Pi media-video/mpv:opengl - Enable support for OpenGL-based video backends (Note: deprecated for X11, USE=egl provides the newer support for -gpu-api=opengl) media-video/mpv:pipewire - Enable sound support via native PipeWire backend -media-video/mpv:raspberry-pi - Enable support for the Raspberry Pi media-video/mpv:rubberband - Enable high quality pitch correction via media-libs/rubberband media-video/mpv:sdl - Enable media-libs/libsdl2 based video and audio outputs (Note: these outputs exist for compatibility reasons only, avoid if possible) media-video/mpv:sixel - Enable support for the sixel video backend using media-libs/libsixel @@ -5203,8 +5171,9 @@ media-video/obs-studio:mpegts - Enable native SRT/RIST mpegts output. media-video/obs-studio:pipewire - Build with PipeWire support. media-video/obs-studio:python - Build with scripting support for Python 3. media-video/obs-studio:qsv - Build with Intel Quick Sync Video support. +media-video/obs-studio:sndio - Build with sndio support. media-video/obs-studio:speex - Build with Speex noise suppression filter support. -media-video/obs-studio:ssl - Build with TLS/SSL support for RTMPS connections. +media-video/obs-studio:test-input - Build and install input sources used for testing. media-video/obs-studio:vlc - Build with VLC media source support. media-video/obs-studio:websocket - Build with WebSocket API support. media-video/peek:keybinder - Enable support for global hotkeys using dev-libs/keybinder @@ -5330,14 +5299,6 @@ net-analyzer/barnyard2:sguil - Enable sguil (The Analyst Console for Network Sec net-analyzer/bwm-ng:csv - Enable csv output net-analyzer/bwm-ng:html - Enable html output net-analyzer/cacti:doc - install html documentation -net-analyzer/check_mk_agent:apache_status - Install check_mk-agent apache-status plugin. -net-analyzer/check_mk_agent:inventory - Install check_mk-agent linux inventory plugin. -net-analyzer/check_mk_agent:logwatch - Install check_mk-agent logwatch plugin. -net-analyzer/check_mk_agent:mysql - Install check_mk-agent mysql plugin. -net-analyzer/check_mk_agent:nfsexports - Install check_mk-agent nfsexports plugin. -net-analyzer/check_mk_agent:postgres - Install check_mk-agent postgres plugin. -net-analyzer/check_mk_agent:smart - Install check_mk-agent S.M.A.R.T plugin. -net-analyzer/check_mk_agent:zypper - Install check_mk-agent zypper plugin. net-analyzer/echoping:http - enable support for http protocol. net-analyzer/echoping:icp - enable support for ICP (used to monitor proxies). net-analyzer/echoping:priority - enable socket priority support. @@ -5370,6 +5331,7 @@ net-analyzer/linkchecker:sqlite - Mozilla Bookmark parsing net-analyzer/monitoring-plugins:dns - Install net-dns/bind-tools required for monitoring DNS servers. Disabling the flag does not remove any plugins. net-analyzer/monitoring-plugins:fping - Install net-analyzer/fping required for fancy ping monitoring. Disabling the flag does not remove any plugins. net-analyzer/monitoring-plugins:game - Install games-util/qstat required for monitoring FPS servers. Disabling the flag does not remove any plugins. +net-analyzer/monitoring-plugins:ipv6 - Enable ipv6 checks. net-analyzer/monitoring-plugins:snmp - Install dev-perl/Net-SNMP and net-analyzer/net-snmp required for monitoring SNMP values. Disabling the flag does not remove any plugins. net-analyzer/monitoring-plugins:ssh - Install net-misc/openssh required for monitoring SSH servers. Disabling the flag does not remove any plugins. net-analyzer/mtr:ipinfo - Disable support for IP address lookups @@ -5581,11 +5543,6 @@ net-dialup/freeradius-client:scp - Add service type hints derived from username net-dialup/freeradius-client:shadow - Enable shadow password support net-dialup/mgetty:fax - Enables fax support net-dialup/mgetty:fidonet - Enables FidoNet support -net-dialup/openl2tp:client - Enable l2tp client. -net-dialup/openl2tp:dmalloc - Enable debugging using dev-libs/dmalloc. -net-dialup/openl2tp:rpc - Enable RPC control management. This flag is required for l2tpconfig to be built and used. -net-dialup/openl2tp:server - Enable l2tp server. -net-dialup/openl2tp:stats - Enable status files. Note: when they are used, this hampers performance of the daemon. net-dialup/ppp:activefilter - Enables active filter support net-dialup/ppp:dhcp - Installs PPP DHCP client plugin for IP address allocation by a DHCP server (see http://www.netservers.co.uk/gpl/) net-dialup/ppp:eap-tls - Enables support for Extensible Authentication Protocol and Transport Level Security (see http://www.nikhef.nl/~janjust/ppp/index.html) @@ -5600,6 +5557,7 @@ net-dns/avahi:mdnsresponder-compat - Enable compat libraries for mDNSResponder net-dns/bind:dlz - Enables dynamic loaded zones, 3rd party extension net-dns/bind:dnsrps - Enable the DNS Response Policy Service (DNSRPS) API, a mechanism to allow an external response policy provider net-dns/bind:dnstap - Enables dnstap packet logging +net-dns/bind:doh - Enables dns-over-https net-dns/bind:fixed-rrset - Enables fixed rrset-order option net-dns/bind:geoip2 - Enable GeoIP2 API from MaxMind net-dns/bind:gssapi - Enable gssapi support @@ -5668,16 +5626,24 @@ net-dns/knot:xdp - Enable eXpress Data Path net-dns/knot-resolver:dnstap - Build dnstap binary logging module net-dns/knot-resolver:kresc - Build (experimental) command-line client net-dns/knot-resolver:nghttp2 - DNS-over-HTTPS support -net-dns/mydns:alias - Enable David Phillips aliasing -net-dns/mydns:status - Enable the STATUS opcode to check server status -net-dns/nsd:bind8-stats - Enables BIND8 like NSTATS and XSTATS +net-dns/nsd:bind8-stats - Enables BIND8 like NSTATS and XSTATS and statistics in nsd-control +net-dns/nsd:default-znow - Enable full relocation binding at load-time (RELRO NOW, to protect GOT and .dtor areas) net-dns/nsd:dnstap - Enable the structured binary log format +net-dns/nsd:ipv6 - Enable IPv6 support +net-dns/nsd:largefile - Enables support for large files net-dns/nsd:libevent - Use libevent or libev, useful when zone count is high +net-dns/nsd:memclean - Cleanup memory (at exit) for eg. valgrind, memcheck net-dns/nsd:minimal-responses - If minimal responses are disabled, responses are more likely to get truncated, resulting in TCP fallback -net-dns/nsd:munin - Install a plugin for net-analyzer/munin to graph statistical data from nsd. +net-dns/nsd:mmap - Use mmap(2) instead of malloc(3); currently experimental +net-dns/nsd:munin - Install a plugin for net-analyzer/munin to graph statistical data from nsd net-dns/nsd:nsec3 - Enable NSEC3 support +net-dns/nsd:packed - Enable packed structure alignment; uses less memory but has unaligned reads +net-dns/nsd:radix-tree - Use a radix tree for main lookups instead of a red-black tree net-dns/nsd:ratelimit - Enables ratelimiting, based on query name, type and source -net-dns/nsd:root-server - Configure NSD as a root server +net-dns/nsd:recvmmsg - Enable recvmmsg and sendmmsg compilation, faster but some kernel versions may have implementation problems for IPv6 +net-dns/nsd:simdzone - Leverage SIMD instructions in modern CPUs to improve throughput +net-dns/nsd:tfo - Enable TCP Fast Open +net-dns/nsd:year2038 - Enables support for 64-bit 'time_t' (sets D_TIME_BITS=64; glibc only) net-dns/opendnssec:external-hsm - Enables support for storing DNSSEC keys through an arbitrary non-portage PKCS#11 interface, specified through an environment variable net-dns/opendnssec:opensc - Enables support for storing DNSSEC keys through a dev-libs/opensc PKCS#11 interface net-dns/opendnssec:signer - Enables signing capabilities for OpenDNSSEC @@ -5908,12 +5874,14 @@ net-im/spectrum2:twitter - Enables the Twitter backend. net-im/spectrum2:whatsapp - Enables the WhatsApp backend, based on net-im/transwhat. net-im/telegram-desktop:enchant - Use the app-text/enchant spell-checking backend instead of app-text/hunspell net-im/telegram-desktop:fonts - Use builtin patched copy of open-sans fonts (overrides fontconfig) +net-im/telegram-desktop:libdispatch - Use dev-libs/libdispatch to speed up concurrent code execution net-im/telegram-desktop:qt6 - Build with Qt6 support net-im/telegram-desktop:qt6-imageformats - Add support for HEIF, AVIF and JpegXL by bundling kde-frameworks/kimageformats net-im/tkabber:plugins - Enables installation the extra plugins net-im/tokodon:mpv - Use media-libs/mpvqt instead of dev-qt/qtmultimedia for video playback (default) net-im/tokodon:webengine - Use dev-qt/qtwebengine for built-in authentication page (default is external browser) net-im/toxic:audio-notify - Enables native sound notifications +net-im/toxic:experimental - Use experimental features in net-libs/tox net-im/toxic:games - Enables some small mini-games net-im/toxic:llvm - Enables support for LLVM Address Sanitizer net-im/toxic:notification - Enables desktop notifications with libnotify, with sound support. @@ -5922,6 +5890,7 @@ net-im/toxic:sound - Enables audio calling net-im/toxic:video - Enables video calling net-im/zoom:bundled-qt - Use bundled Qt and icu instead of system-wide libs net-im/zoom:opencl - Use OpenCL for virtual background support (virtual/opencl) +net-im/zoom:zoom-symlink - Install a zoom symlink in /usr/bin net-irc/anope:ldap - Build LDAP modules for e.g. opertypes net-irc/anope:sql - Build modules which require SQL net-irc/anope:ssl - Provide SSL services using OpenSSL @@ -5939,6 +5908,7 @@ net-irc/hexchat:theme-manager - Build the theme manager (mono) net-irc/inspircd:argon2 - Enable Argon2 hashes in modules net-irc/inspircd:gnutls - Enable TLS support net-irc/inspircd:ldap - Enable LDAP support +net-irc/inspircd:log-json - Enable logging via JSON net-irc/inspircd:maxminddb - Add support for geolocation using libMaxMindDB net-irc/inspircd:mbedtls - Add support for TLS using the mbedTLS library net-irc/inspircd:mysql - Enable MySQL database backend @@ -6034,7 +6004,9 @@ net-libs/davix:tools - Install additional tools net-libs/freaklabs-chibiarduino:promisc - Enable promisc in the config file for packet sniffing net-libs/glib-networking:gnome - Extract HTTP/HTTPS/SOCKS proxy configuration stored using GSettings net-libs/glib-networking:libproxy - Use net-libs/libproxy for getting the HTTP/HTTPS/SOCKS proxy configuration +net-libs/gloox:xhtmlim - expose internal NodeList for optional XHTML-IM rendering without external parser net-libs/gnome-online-accounts:gnome - Use gnome-base/gnome-control-center to set GNOME online accounts preferences +net-libs/gnome-online-accounts:ms365 - Enable Microsoft 365 provider net-libs/gnutls:dane - Build libgnutls-dane, implementing DNS-based Authentication of Named Entities. Requires net-dns/unbound net-libs/gnutls:openssl - Build openssl compatibility libraries net-libs/gnutls:pkcs11 - Add support for PKCS#11 through app-crypt/p11-kit @@ -6042,7 +6014,7 @@ net-libs/gnutls:sslv2 - Support for the old/insecure SSLv2 protocol net-libs/gnutls:sslv3 - Support for the old/insecure SSLv3 protocol net-libs/gnutls:test-full - Enable full test mode net-libs/gnutls:tls-heartbeat - Enable the Heartbeat Extension in TLS and DTLS -net-libs/gnutls:tools - Build extra tools +net-libs/gnutls:tools - Build cli tools such as gnutls-cli, certtool and oscptool net-libs/gssdp:man - Generate man page for tools net-libs/libetpan:liblockfile - Enable support for liblockfile library net-libs/libetpan:lmdb - Use dev-db/lmdb as cache DB @@ -6057,9 +6029,7 @@ net-libs/libmicrohttpd:thread-names - Assign thread names to internal threads, u net-libs/libnids:glib - Use dev-libs/glib for multiprocessing support net-libs/libnids:libnet - Include code requiring net-libs/libnet net-libs/libnma:pkcs11 - Enable PKCS#11 support in certificate chooser via app-crypt/gcr -net-libs/liboauth:bindist - Alias for the nss USE flag, since there are license compliancy trouble when using OpenSSL. net-libs/liboauth:curl - If enabled, net-misc/curl is used thorugh the libcurl library; if it's not, the curl command is used instead. Some features are only available when using the library, but using it as library requires matching SSL implementations. -net-libs/liboauth:nss - Use Mozilla NSS (dev-libs/nss) as hash library; if this is disabled, dev-libs/openssl is used instead. net-libs/liboping:filecaps - Allow non-root users to use [n]oping utility. net-libs/liboping:ncurses - Build ncurses-based version of oping utility (requires sys-libs/ncurses) net-libs/libpcap:netlink - Use dev-libs/libnl to put wireless interfaces in monitor mode. @@ -6069,7 +6039,6 @@ net-libs/libpcap:yydebug - Enable parser debugging code net-libs/libprotoident:tools - Build and install command-line tools net-libs/libproxy:duktape - Use dev-lang/duktape for PAC parsing net-libs/libproxy:gnome - Enable support for reading proxy settings from GNOME -net-libs/libproxy:kde - Enable support for reading proxy settings from KDE net-libs/libqmi:mbim - Support QMI over Mobile Broadband Interface Model (MBIM) net-libs/libqmi:qrtr - Support QMI over IPC Router bus (QRTR) net-libs/libsoup:gssapi - Enable GSSAPI support @@ -6101,6 +6070,7 @@ net-libs/libwebsockets:client - The client part of the library and libwebsockets net-libs/libwebsockets:extensions - Compile with extensions (permessage-deflate) net-libs/libwebsockets:generic-sessions - With the Generic Sessions plugin net-libs/libwebsockets:http-proxy - Support for rewriting HTTP proxying +net-libs/libwebsockets:ipv6 - Compile without support for ipv6 net-libs/libwebsockets:lejp - With the Lightweight JSON Parser net-libs/libwebsockets:libev - Support event loops via dev-libs/libev net-libs/libwebsockets:libevent - Support event loops via dev-libs/libevent @@ -6127,7 +6097,7 @@ net-libs/nodejs:pax-kernel - Enable building under a PaX enabled kernel net-libs/nodejs:snapshot - Enable snapshot creation for faster startup net-libs/nodejs:system-icu - Use system dev-libs/icu instead of the bundled version net-libs/nodejs:system-ssl - Use system OpenSSL instead of the bundled one -net-libs/nodejs:systemtap - Enable SystemTAP/DTrace tracing +net-libs/nodejs:systemtap - Enable SystemTap/DTrace tracing net-libs/ntirpc:gssapi - Include support for RPCSEC GSS net-libs/ntirpc:rdma - Include support for RDMA RPC net-libs/paho-mqtt-c:high-performance - The debugging aids internal tracing and heap tracking are not included @@ -6154,6 +6124,7 @@ net-libs/shairplay:playfair - Add support for handling fairplay handshake (used net-libs/tox:av - Adds support for audio and video. net-libs/tox:daemon - Enable the DHT Bootstrap Daemon. net-libs/tox:dht-node - Enables DHT Bootstrap Node. +net-libs/tox:experimental - Enables the experimental api net-libs/tox:key-utils - Builds utilities to create custom keys and profiles net-libs/tox:log-debug - Log level: 4 net-libs/tox:log-error - Log level: 1 @@ -6177,7 +6148,6 @@ net-libs/xrootd:server - Install xrootd server and related plug-ins net-libs/xrootd:xrdec - Enable erasure coding support (XrdEc plugin) with dev-libs/isa-l net-libs/zeromq:drafts - Build draft API, which may change at any time without any notice, and is therefore not recommended for normal use. net-libs/zeromq:libbsd - Use strlcpy() from dev-libs/libbsd instead of internal implementation. -net-libs/zeromq:pgm - Build PGM (Pragmatic General Multicast)extention, a protocol for reliable multicast transport of data over IP networks. net-libs/zeromq:sodium - Use dev-libs/libsodium for cryptography net-mail/courier-imap:trashquota - include deleted messages, and the Trash folder, in the estimated quota usage for maildirs net-mail/cyrus-imapd:backup - Enable backup service support @@ -6238,7 +6208,6 @@ net-misc/aria2:ssh - Enable SFTP support. net-misc/asterisk:blocks - Utlize -fblocks (only supported by, and required when using, clang/LLVM) net-misc/asterisk:cluster - Enable high-availability support through the Corosync Cluster Engine net-misc/asterisk:codec2 - Enable Codec2 support in asterisk -net-misc/asterisk:dahdi - Support Digium compatible hardware (formerly known as Zaptel) net-misc/asterisk:deprecated - Enable deprecated features (eg, app_macro) net-misc/asterisk:gtalk - Enable support for Google Talk services net-misc/asterisk:http - Enable embedded web server @@ -6275,48 +6244,6 @@ net-misc/asterisk-moh-opsound:siren7 - Install the sounds files for the siren7 c net-misc/asterisk-moh-opsound:sln16 - Install the sounds files for the sln16 codec. net-misc/asterisk-moh-opsound:ulaw - Install the sounds files for the ulaw codec. net-misc/asterisk-moh-opsound:wav - Install the sounds files for the wav codec. -net-misc/bfgminer:adl - Enable support for controlling fans and overclocking on AMD cards with AMD Display Library -net-misc/bfgminer:alchemist - Enable support for mining with AlcheMist -net-misc/bfgminer:avalon - Enable support for mining with Avalon 1 ASIC modules -net-misc/bfgminer:avalonmm - Enable support for mining with Avalon 2/3 ASIC modules -net-misc/bfgminer:bfsb - Enable support for mining on BFSB host Raspberry Pi -net-misc/bfgminer:bfx - Enable support for mining with BFx2 USB sticks -net-misc/bfgminer:bifury - Enable support for mining with Bi*fury USB sticks -net-misc/bfgminer:bigpic - Enable support for mining with Big Picture Mining USB sticks (Red/BlueFury, BF1, etc) -net-misc/bfgminer:bitforce - Enable support for mining with ButterFly Labs BitFORCE ASICs and/or FPGAs -net-misc/bfgminer:bitfury - Enable support for mining with 55nm Bitfury-based devices -net-misc/bfgminer:bitmain - Enable support for mining with Bitmain Antminer S* series -net-misc/bfgminer:cointerra - Enable support for mining with CoinTerra TerraMiner. -net-misc/bfgminer:cpumining - Enable support for mining with CPUs -net-misc/bfgminer:drillbit - Enable support for mining with Drillbit boards -net-misc/bfgminer:dualminer - Enable support for mining with DualMiner USB sticks -net-misc/bfgminer:gridseed - Enable support for mining with 5-chip GridSeed orbs -net-misc/bfgminer:hashbuster - Enable support for mining with HashBuster nano boards -net-misc/bfgminer:hashbuster2 - Enable support for mining with HashBuster micro boards -net-misc/bfgminer:hashfast - Enable support for mining with HashFast devices -net-misc/bfgminer:icarus - Enable support for mining with Icarus-compatible devices (including Block Erupter Sapphire ASICs) -net-misc/bfgminer:jingtian - Enable support for mining on JingTian boards via SPI/GPIO -net-misc/bfgminer:keccak - Enable support for mining with Keccak miners -net-misc/bfgminer:klondike - Enable support for mining with Klondike USB miners -net-misc/bfgminer:libusb - Use libusb -net-misc/bfgminer:littlefury - Enable support for mining with LittleFury USB sticks -net-misc/bfgminer:metabank - Enable support for mining on Metabank host Raspberry Pi -net-misc/bfgminer:minion - Enable support for mining on minion chips via SPI (BlackArrow Prospero) -net-misc/bfgminer:modminer - Enable support for mining with ModMiner FPGAs -net-misc/bfgminer:nanofury - Enable support for mining with NanoFury USB sticks -net-misc/bfgminer:opencl - Enable support for mining with OpenCL-capable devices (GPUs) -net-misc/bfgminer:proxy - Enable support for virtual proxy device -net-misc/bfgminer:proxy_getwork - Enable proxy support for getwork protocol (often used with Block Erupter Blades) -net-misc/bfgminer:proxy_stratum - Enable proxy support for stratum protocol -net-misc/bfgminer:rockminer - Enable support for mining with RockMiner devices -net-misc/bfgminer:screen - Provide start-bfgminer.sh script to launch BFGMiner in app-misc/screen -net-misc/bfgminer:scrypt - Enable support for scrypt mining algorithm -net-misc/bfgminer:sha256d - Enable support for SHA256d mining algorithm -net-misc/bfgminer:twinfury - Enable support for mining with Twinfury USB sticks -net-misc/bfgminer:udev-broad-rules - Enable broader udev rules that may match non-mining devices -net-misc/bfgminer:x6500 - Enable support for mining with X6500 FPGAs -net-misc/bfgminer:zeusminer - Enable support for mining with ZeusMiner units -net-misc/bfgminer:ztex - Enable support for mining with Ztex FPGAs net-misc/bird:client - Build the ncurses/readline full featured CLI net-misc/bird:libssh - Enables net-libs/libssh binding, mendatory for RPKI support net-misc/casync:fuse - Enable fuse support @@ -6377,13 +6304,15 @@ net-misc/curl:ftp - Enable FTP support net-misc/curl:gnutls - Enable gnutls ssl backend net-misc/curl:gopher - Enable Gopher protocol support net-misc/curl:hsts - Enable HTTP Strict Transport Security +net-misc/curl:http3 - Enable HTTP/3 support net-misc/curl:imap - Enable Internet Message Access Protocol support net-misc/curl:mbedtls - Enable mbedtls ssl backend -net-misc/curl:nghttp3 - Enable HTTP/3.0 support using net-libs/nghttp3 and net-libs/ngtcp2 +net-misc/curl:nghttp3 - Enable HTTP/3 support using net-libs/nghttp3 net-misc/curl:openssl - Enable openssl ssl backend net-misc/curl:pop3 - Enable Post Office Protocol 3 support net-misc/curl:progress-meter - Enable the progress meter net-misc/curl:psl - Enable Public Suffix List (PSL) support. See https://daniel.haxx.se/blog/2024/01/10/psl-in-curl/. +net-misc/curl:quic - Enable support for QUIC (RFC 9000); a UDP-based protocol intended to replace TCP net-misc/curl:rtmp - Enable RTMP Streaming Media support net-misc/curl:rustls - Enable Rustls ssl backend net-misc/curl:smtp - Enable Simple Mail Transfer Protocol support @@ -6491,7 +6420,6 @@ net-misc/kafkacat:json - Enable json support net-misc/kea:openssl - Use dev-libs/openssl instead of dev-libs/botan net-misc/kea:samples - Install sample configuration files net-misc/kea:shell - Install kea-shell text management client for Control Agent -net-misc/kio-zeroconf:kf6compat - Disable components colliding with KF6, depend on KF6 components instead net-misc/knock:server - Installs the knockd server daemon. net-misc/libteam:zmq - Build witch net-libs/zeromq support net-misc/lldpd:cdp - Enable Cisco Discovery Protocol @@ -6522,6 +6450,7 @@ net-misc/moonlight:embedded - Optimize UI for fullscreen non-desktop usage net-misc/moonlight:glslow - Prefer direct KMS/DRM rendering over EGL/GLES rendering for better performance on some weaker GPUs net-misc/moonlight:libdrm - Enable video rendering via x11-libs/libdrm net-misc/moonlight:soundio - Enable sound output via media-libs/libsoundio instead of media-libs/libsdl2 +net-misc/moonlight:vkslow - Prefer hardware YUV-RGB conversion and scaling over Vulkan for better performance on some weaker GPUs net-misc/mosh:client - Build network client net-misc/mosh:examples - Include example scripts net-misc/mosh:mosh-hardening - Enable compiler and linker options to frustrate memory corruption exploits @@ -6529,7 +6458,6 @@ net-misc/mosh:nettle - Use dev-libs/nettle for some cryptographic functions inst net-misc/mosh:server - Build network server net-misc/mosh:ufw - Install net-firewall/ufw rule set net-misc/mosh:utempter - Include libutempter support -net-misc/mrouted:rsrr - Enable Routing Support for Resource Reservations, for RSVP net-misc/mulk:checksum - Enable checksum verification for Metalink from dev-libs/openssl net-misc/mulk:metalink - Enable support for media-libs/libmetalink net-misc/netifrc:dhcp - Allow interfaces to configure via DHCP @@ -6559,12 +6487,22 @@ net-misc/nextcloud-client:webengine - Enable old Flow1 login using dev-qt/qtwebe net-misc/ntp:openntpd - Allow ntp to be installed alongside openntpd net-misc/ntp:parse-clocks - Add support for PARSE clocks net-misc/ntp:samba - Provide support for Samba's signing daemon (needed for Active Directory domain controllers) +net-misc/ntpsec:arbiter - Arbiter 1088A/B GPS driver net-misc/ntpsec:early - Drop root privileges early net-misc/ntpsec:gdb - Enable debugging with gdb +net-misc/ntpsec:generic - Enable support for generic time radios and GPSDOs +net-misc/ntpsec:gpsd - Enable gpsd daemon support net-misc/ntpsec:heat - Install contrib heat generating scripts +net-misc/ntpsec:hpgps - Hewlett Packard GPS driver +net-misc/ntpsec:jjy - JJY driver net-misc/ntpsec:libbsd - Use libbsd instead of internal funcs +net-misc/ntpsec:local - Support for undisciplined local clock (not recommended) +net-misc/ntpsec:modem - NIST/USNO/PTB Modem Time Services net-misc/ntpsec:nist - Set local clock deps +net-misc/ntpsec:nmea - NMEA GPS driver net-misc/ntpsec:ntpviz - Make visualizations of offsets, jiffies, etc. +net-misc/ntpsec:oncore - Oncore driver +net-misc/ntpsec:pps - PPS cesium clock driver net-misc/ntpsec:rclock_arbiter - Arbiter 1088A/B GPS driver net-misc/ntpsec:rclock_generic - Enable support for generic time radios and GPSDOs net-misc/ntpsec:rclock_gpsd - Enable gpsd daemon support @@ -6580,7 +6518,12 @@ net-misc/ntpsec:rclock_spectracom - Spectracom driver net-misc/ntpsec:rclock_trimble - Trimble driver net-misc/ntpsec:rclock_truetime - Trutime driver (deprecated) net-misc/ntpsec:rclock_zyfer - Zyfer driver +net-misc/ntpsec:shm - Obtain refclock info from shared memory-segment net-misc/ntpsec:smear - Specify the interval over which a leap second is applied (experimental) +net-misc/ntpsec:spectracom - Spectracom driver +net-misc/ntpsec:trimble - Trimble driver +net-misc/ntpsec:truetime - Trutime driver (deprecated) +net-misc/ntpsec:zyfer - Zyfer driver net-misc/ofono:atmodem - ETSI AT modem support. net-misc/ofono:bluetooth - Enable Bluetooth modem support using net-wireless/bluez. net-misc/ofono:cdmamodem - Enable CDMA modem support. @@ -6758,19 +6701,20 @@ net-p2p/bitcoin-core:qrcode - Enable generation of QR Codes for receiving paymen net-p2p/bitcoin-core:sqlite - Support descriptor wallets in SQLite format net-p2p/bitcoin-core:system-leveldb - Link with virtual/bitcoin-leveldb rather than embedding an internal copy net-p2p/bitcoin-core:system-libsecp256k1 - Link with dev-libs/libsecp256k1 rather than embedding an internal copy -net-p2p/bitcoin-core:systemtap - Enable SystemTAP/DTrace tracing +net-p2p/bitcoin-core:systemtap - Enable SystemTap/DTrace tracing +net-p2p/bitcoin-core:test-full - Run tests that take a long time net-p2p/bitcoin-core:upnp - Enable Universal Plug and Play net-p2p/bitcoin-core:zeromq - Report blocks and transactions via zeromq net-p2p/bitcoin-qt:external-signer - Include support for external wallet signer programs net-p2p/bitcoin-qt:nat-pmp - Enable NAT-PMP port forwarding net-p2p/bitcoin-qt:qrcode - Enable generation of QR Codes for receiving payments -net-p2p/bitcoin-qt:systemtap - Enable SystemTAP/DTrace tracing +net-p2p/bitcoin-qt:systemtap - Enable SystemTap/DTrace tracing net-p2p/bitcoin-qt:upnp - Enable Universal Plug and Play net-p2p/bitcoin-qt:wallet - Enable wallet support net-p2p/bitcoin-qt:zeromq - Report blocks and transactions via zeromq net-p2p/bitcoind:external-signer - Include support for external wallet signer programs net-p2p/bitcoind:nat-pmp - Enable NAT-PMP port forwarding -net-p2p/bitcoind:systemtap - Enable SystemTAP/DTrace tracing +net-p2p/bitcoind:systemtap - Enable SystemTap/DTrace tracing net-p2p/bitcoind:upnp - Enable Universal Plug and Play net-p2p/bitcoind:wallet - Enable wallet support net-p2p/bitcoind:zeromq - Report blocks and transactions via zeromq @@ -6780,7 +6724,6 @@ net-p2p/deluge:webinterface - Install dependencies needed for the web interface net-p2p/eiskaltdcpp:cli - Enable sample cli based on readline net-p2p/eiskaltdcpp:daemon - Enable eiskaltdcpp-daemon net-p2p/eiskaltdcpp:dht - Enable DHT (distributed hash table) support for libeiskaltdcpp -net-p2p/eiskaltdcpp:gold - Use gold.ld instead of ld net-p2p/eiskaltdcpp:libcanberra - Enable sound notifications support over libcanberra in EiskaltDC++ Gtk net-p2p/eiskaltdcpp:minimal - Don't install headers net-p2p/fms:frost - Add support for frost boards @@ -6810,12 +6753,12 @@ net-p2p/retroshare:cli - Enables terminal login support for retroshare-service net-p2p/retroshare:jsonapi - Enables the new RetroShare JSON API net-p2p/retroshare:libupnp - Enables UPnP port forwarding via net-libs/libupnp net-p2p/retroshare:miniupnp - Enables UPnP port forwarding via net-libs/miniupnpc +net-p2p/retroshare:plugins - Enables plugin support net-p2p/retroshare:service - Enables the new RetroShare service net-p2p/retroshare:sqlcipher - Enables GXS database encryption via SQLCipher net-p2p/syncthing:tools - Install stdiscosrv, strelaysrv and other tools to /usr/libexec/syncthing/. net-p2p/transmission:cli - Build command-line client net-p2p/transmission:debug - Enable assertions -net-p2p/transmission:lightweight - Optimize transmission for low-resource systems (smaller cache size, prefer unencrypted peer connections, etc.) net-p2p/transmission:mbedtls - Use mbed TLS instead of OpenSSL net-p2p/transmission-remote-gtk:libproxy - Use net-libs/libproxy for getting the HTTP/HTTPS/SOCKS proxy configuration. net-print/cups:openssl - Use dev-libs/openssl instead of net-libs/gnutls for TLS support @@ -6891,6 +6834,9 @@ net-proxy/tinyproxy:transparent-proxy - Enable transparent proxying net-proxy/tinyproxy:upstream-proxy - Enable upstream proxying net-proxy/tinyproxy:xtinyproxy-header - Include the X-Tinyproxy header net-proxy/trojan:mysql - build with MySQL support +net-proxy/trojan:nat - Build with NAT support +net-proxy/trojan:reuseport - Build with SO_REUSEPORT support +net-proxy/trojan:tcpfastopen - Force build with TCP Fast Open support net-proxy/tsocks:dns - Force DNS queries to use SOCKS server via tcp net-proxy/tsocks:envconf - Allow TSOCKS_CONF_FILE to specify configuration file net-proxy/tsocks:server-lookups - Allow hostname resolution _for_ SOCKS servers @@ -6898,7 +6844,6 @@ net-proxy/tsocks:tordns - Apply tordns patch which allows transparent TORificati net-voip/mumble:g15 - Enable support for the Logitech G15 LCD (and compatible devices). net-voip/mumble:pipewire - Enable pipewire support for audio output. net-voip/mumble:rnnoise - Enable alternative noise suppression option based on RNNoise. -net-voip/murmur:grpc - Use net-libs/grpc to enable remote control capabilities. net-voip/murmur:ice - Use dev-libs/Ice to enable remote control capabilities. net-voip/umurmur:mbedtls - Use net-libs/mbedtls as TLS provider net-voip/umurmur:shm - Enable shared memory support @@ -6921,7 +6866,6 @@ net-vpn/eduvpn-common:openvpn - enable support for OpenVPN net-vpn/eduvpn-common:wireguard - enable support for WireGuard net-vpn/frp:client - Build and install frp client (frpc) net-vpn/frp:server - Build and install frp server (frps) -net-vpn/i2pd:i2p-hardening - Compile with hardening on vanilla compilers/linkers net-vpn/libreswan:dnssec - Use DNSSEC resolver (requires net-dns/unbound) net-vpn/libreswan:ikev1 - Enable the IKEv1 protocol net-vpn/networkmanager-sstp:gtk4 - Use gui-libs/gtk for GUI support. @@ -7110,11 +7054,8 @@ net-wireless/wpa_supplicant:wep - Add support for Wired Equivalent Privacy (depr net-wireless/wpa_supplicant:wimax - Add support for Wimax EAP-PEER authentication algorithm net-wireless/wpa_supplicant:wps - Add support for Wi-Fi Protected Setup sci-astronomy/cpl:gasgano - Enable support for sci-astronomy/gasgano file organizer -sci-astronomy/esomidas:libtirpc - Build against net-libs/libtirpc for RPC support sci-astronomy/kstars:password - Store passwords securely via dev-libs/qtkeychain sci-astronomy/kstars:wcs - Enable support for World Coordinate System library using wcslib -sci-astronomy/predict:xforms - Add a "map" client which uses the x11-libs/xforms library for its GUI -sci-astronomy/predict:xplanet - Project predict data onto world maps generated by x11-misc/xplanet / x11-misc/xearth sci-astronomy/psfex:plplot - Build with sci-libs/plplot to allow diagnostic plots during processing sci-astronomy/scamp:plplot - Build with sci-libs/plplot to allow diagnostic plots during processing sci-astronomy/sextractor:modelfit - Enable profile model fitting, needs sci-libs/atlas and sci-libs/fftw @@ -7185,8 +7126,6 @@ sci-chemistry/vmd:tachyon - Add support for tachyon raytracer for HQ images sci-chemistry/votca:gromacs - Add support for gromacs file formats through sci-chemistry/gromacs sci-electronics/gerbv:unit-mm - Set default unit for coordinates in status bar to mm sci-electronics/ghdl:llvm - Build LLVM code generator -sci-electronics/gspiceui:schematics - Use sci-electronics/geda for schematics editing -sci-electronics/gspiceui:waveform - Use sci-electronics/gwave for waveform display sci-electronics/gtkwave:fasttree - Enables experimental Fast SST Tree widget code. sci-electronics/gtkwave:fatlines - Renders lines as double width in gtkwave. sci-electronics/gtkwave:judy - Enables Judy array support. @@ -7220,6 +7159,7 @@ sci-geosciences/gpsd:sockets - export gpsd over unix sockets sci-geosciences/grass:geos - Use sci-libs/geos for v.buffer and adds extended options to the v.select module sci-geosciences/grass:las - Include support for LAS and LAZ encoded LiDAR files through sci-geosciences/liblas sci-geosciences/grass:pdal - Enable support for PDAL for point clouds via sci-libs/pdal +sci-geosciences/grass:svm - Enable support for the Support Vector Machine library sci-libs/libsvm sci-geosciences/gshhs:data - Add earth data with sci-geosciences/gshhs-data sci-geosciences/liblas:gdal - Add support for the sci-libs/gdal geospatial raster library sci-geosciences/mapserver:apache - Enable mapserver to run under apache @@ -7245,6 +7185,7 @@ sci-geosciences/qgis:pdal - Enable support for PDAL for point clouds via sci-lib sci-geosciences/qgis:polar - Enable support for the polar coordinate system via x11-libs/qwtpolar sci-geosciences/qgis:qml - Enable support Qml-based plugins using dev-qt/qtdeclarative sci-geosciences/qgis:serial - Enable support for serial GPS using dev-qt/qtserialport +sci-geosciences/qgis:webengine - Enable webengine support using dev-qt/qtwebengine sci-geosciences/viking:geoclue - Use app-misc/geoclue to determine current location sci-geosciences/viking:libexif - Use media-libs/libexif for EXIF support sci-geosciences/viking:oauth - Enable OAuth authentication for OSM @@ -7288,7 +7229,6 @@ sci-libs/caffe2:opencv - Add support for image processing operators sci-libs/caffe2:openmp - Use OpenMP for parallel code sci-libs/caffe2:qnnpack - Use QNNPACK sci-libs/caffe2:rocm - Enable ROCm gpu computing support -sci-libs/caffe2:tensorpipe - Use tensorpipe sci-libs/caffe2:xnnpack - Use XNNPACK sci-libs/cantera:hdf5 - Add HDF5 container files support sci-libs/cantera:python - Install Python bindings and conversion tools from Chemkin to Cantera format @@ -7357,6 +7297,7 @@ sci-libs/gdal:fits - Enable support for NASA's sci-libs/cfitsio library sci-libs/gdal:geos - Add support for geometry engine (sci-libs/geos) sci-libs/gdal:gml - Enable support for dev-libs/xerces-c C++ API sci-libs/gdal:ogdi - Enable support for the open geographic datastore interface (sci-libs/ogdi) +sci-libs/gdal:parquet - Enables read/write parquet data format (dev-libs/apache-arrow) sci-libs/gdal:spatialite - Enable Spatial DBMS over sqlite dev-db/spatialite sci-libs/gdal:xls - Add the dev-libs/freexl library for xls import support sci-libs/ginkgo:cuda - Add support for cuda assimp (dev-util/nvidia-cuda-toolkit) @@ -7381,6 +7322,7 @@ sci-libs/gsl:deprecated - Enable deprecated functions sci-libs/hdf5:hl - Enable high level API (https://support.hdfgroup.org/HDF5/doc/HL/index.html) sci-libs/hdf5:unsupported - Enable unsupported combinations of configuration options sci-libs/hipCUB:benchmark - Build and install benchmark binaries. +sci-libs/hipSOLVER:sparse - Build hipSOLVER with sparse functionality (sci-libs/cholmod) sci-libs/hypre:int64 - Build the 64 bits integer library sci-libs/indilib:rtlsdr - Enable support for devices supported by net-wireless/rtl-sdr sci-libs/indilib:websocket - Enable support for WebSocket protocol @@ -7397,8 +7339,6 @@ sci-libs/libccd:double-precision - More precise calculations at the expense of s sci-libs/libgeodecomp:hpx - Enables HPX backend sci-libs/libgeodecomp:opencv - Enables OpenCV related code sci-libs/libgeodecomp:silo - Enables SILO related code -sci-libs/libghemical:mopac7 - Use sci-chemistry/mopac7 for semi-empirical calculations -sci-libs/libghemical:mpqc - Use sci-chemistry/mpqc for quantum-mechanical calculations sci-libs/liborigin:tools - Install opj2dat command line util sci-libs/libqalculate:hardened - Disable unsafe functions like 'command' and variables like 'uptime'. sci-libs/libsc:romio - Build with support for the ROMIO MPI-IO component @@ -7422,8 +7362,6 @@ sci-libs/netcdf:blosc - Allow using blosc compression via dev-libs/c-blosc sci-libs/netcdf:dap - Support for remote data access with the built-in OPeNDAP client sci-libs/netcdf:hdf - Build with HDF4 read capability(sci-libs/hdf, sci-libs/hdf5 and sys-libs/zlib required). sci-libs/nlopt:octave - Add plugin for sci-mathematics/octave -sci-libs/o2scl:armadillo - Build matrix manipulation with sci-libs/armadillo -sci-libs/o2scl:eigen - Build matrix manipulation with dev-cpp/eigen sci-libs/octomap:dynamicEDT3D - Build and install dynamicEDT3D library: A library for incrementally updatable Euclidean distance transforms in 3D. sci-libs/onnx:disableStaticReg - Disable Static Registration sci-libs/openblas:dynamic - Build dynamic architecture detection at run time (for multi targets) @@ -7461,7 +7399,7 @@ sci-libs/plplot:qhull - Add bindings for media-libs/qhull sci-libs/plplot:shapefile - Enable support for ESRI shapefiles sci-libs/rocBLAS:benchmark - Build and install rocblas-bench. sci-libs/rocBLAS:test - Perform rocblas-test to compare the result between rocBLAS and system BLAS. -sci-libs/rocFFT:benchmark - Build and install [dyna-]rocfft-rider. +sci-libs/rocFFT:benchmark - Build and install rocfft benchmark tools. sci-libs/rocFFT:perfscripts - Install rocfft-perf performance visualization suite. sci-libs/rocPRIM:benchmark - Build and install benchmark programs. sci-libs/rocRAND:benchmark - Build and install benchmark programs. @@ -7565,7 +7503,6 @@ sci-mathematics/giac:glpk - Enable the use of sci-mathematics/glpk sci-mathematics/gmp-ecm:custom-tune - Improve performance of some operations by selecting machine-specific defaults sci-mathematics/gretl:R - Enable support for dev-lang/R sci-mathematics/gretl:extras - Build and install add-ons bundled with gretl -sci-mathematics/gsl-shell:fox - Build a x11-libs/fox GUI sci-mathematics/lcalc:double - Use double precision (the upstream default) sci-mathematics/lcalc:double-double - Use sci-libs/qdfor double-double precision sci-mathematics/lcalc:pari - Use sci-mathematics/pari for elliptic curve L-functions @@ -7589,9 +7526,11 @@ sci-mathematics/octave:glpk - Add support for sci-mathematics/glpk for linear pr sci-mathematics/octave:gnuplot - Use sci-visualization/gnuplot to render plots if OpenGL is unavailable sci-mathematics/octave:imagemagick - Use media-gfx/graphicsmagick to read and write images sci-mathematics/octave:json - Allow using jsonencode and jsondecode commands via dev-libs/rapidjson +sci-mathematics/octave:klu - Add support for KLU (sci-libs/klu) sci-mathematics/octave:qhull - Add support for media-libs/qhull, to allow `delaunay', `convhull', and related functions sci-mathematics/octave:qrupdate - Add support for sci-libs/qrupdatefor QR and Cholesky update functions sci-mathematics/octave:sparse - Add enhanced support for sparse matrix algebra with SuiteSparse +sci-mathematics/octave:spqr - Add support for SPQR (sci-libs/spqr) sci-mathematics/octave:sundials - Enable the ode15i and ode15s ODE solvers using sci-libs/sundials sci-mathematics/pari:data - Add additional data (elldata, galdata, seadata, nftables) sci-mathematics/petsc:afterimage - Use Afterstep image library (media-libs/libafterimage) @@ -7677,6 +7616,7 @@ sci-physics/pythia:lhapdf - Support the use of external PDF sets via sci-physics sci-physics/pythia:root - Use sci-physics/root trees and histograms (in examples only) sci-physics/rivet:hepmc2 - Build with HepMC2 sci-physics/rivet:hepmc3 - Build with HepMC3 +sci-physics/rivet:highfive - Build with hdf5 and highfive sci-physics/rivet:zlib - Build with zlib sci-physics/root:R - Enable support for dev-lang/R sci-physics/root:asimage - Enable support for media-libs/libafterimage @@ -7709,24 +7649,31 @@ sci-physics/vgm:geant4 - Enable interaction with Geant4(sci-physics/geant:4) sci-physics/vgm:root - Enable interaction with ROOT (sci-physics/root) sci-physics/yoda:root - Adds support for sci-physics/root sci-visualization/fityk:nlopt - Enable optimization with sci-libs/nlopt +sci-visualization/gnuplot:amos - Enable Amos routines for complex Airy and Bessel functions (dev-libs/openspecfun) sci-visualization/gnuplot:bitmap - Enable dot-matrix printers and pbm terminal sci-visualization/gnuplot:gd - Add support for media-libs/gd. Needed for GIF, JPEG, and PNG image output. +sci-visualization/gnuplot:gpic - Include support for gpic terminal sci-visualization/gnuplot:libcerf - Enable special functions from sci-libs/libcerf -sci-visualization/gnuplot:regis - Enable ReGIS terminal +sci-visualization/gnuplot:metafont - Include support for metafont terminal +sci-visualization/gnuplot:metapost - Include support for metapost terminal +sci-visualization/gnuplot:regis - Include support for ReGIS terminal +sci-visualization/gnuplot:tgif - Include support for tgif terminal sci-visualization/gr:agg - Enable the libagg anti-grain rendering engine sci-visualization/gwyddion:fits - Enable FITS image import via sci-libs/cfitsio sci-visualization/gwyddion:jansson - Enable JSON data manipulation via dev-libs/jansson sci-visualization/gwyddion:sourceview - Enable support for x11-libs/gtksourceview sci-visualization/gwyddion:unique - Enable remote control backend via dev-libs/libunique -sci-visualization/labplot:cantor - Enable support for different open-source computer algebra systems via kde-apps/cantor -sci-visualization/labplot:excel - Enable support for importing/exporting Microsoft Excel files (.xlsx) via dev-libs/qxlsx +sci-visualization/labplot:eigen - Enable support for fast baseline removal via dev-cpp/eigen sci-visualization/labplot:fits - Enable support for NASA's sci-libs/cfitsio library sci-visualization/labplot:libcerf - Enable special functions from sci-libs/libcerf sci-visualization/labplot:markdown - Enable Markdown support via app-text/discount sci-visualization/labplot:matio - Enable support for matio (sci-libs/matio) +sci-visualization/labplot:ods - Enable support for importing/exporting OpenDocument spreadsheets (.ods) via dev-libs/liborcus sci-visualization/labplot:origin - Enable support for reading OriginLab OPJ project files through sci-libs/liborigin sci-visualization/labplot:root - Enable support for CERN's ROOT file type sci-visualization/labplot:serial - Enable support for RS232 serial ports using dev-qt/qtserialport +sci-visualization/labplot:share - Enable support for a share menu using kde-frameworks/purpose +sci-visualization/labplot:xlsx - Enable support for importing/exporting Microsoft Excel files (.xlsx) via dev-libs/qxlsx sci-visualization/paraview:boost - Enable the usage of dev-libs/boost sci-visualization/paraview:cg - Add support for nvidia's cg shaders sci-visualization/paraview:nvcontrol - Add NVCONTROL support for OpenGL options @@ -7741,7 +7688,6 @@ sec-policy/selinux-base:unknown-perms - Default allow unknown classes in kernels sec-policy/selinux-base-policy:unconfined - Enable support for the unconfined SELinux policy module sys-apps/accountsservice:elogind - Use sys-auth/elogind for session tracking sys-apps/accountsservice:systemd - Use sys-apps/systemd for session tracking -sys-apps/azure-nvme-utils:lun-fallback - Enable fallback LUN calculation via NSID sys-apps/bfs:io-uring - Use sys-libs/liburing for faster async I/O sys-apps/busybox:make-symlinks - Create all the appropriate symlinks in /bin and /sbin. sys-apps/busybox:math - Enable math support in gawk (requires libm) @@ -7898,6 +7844,7 @@ sys-apps/net-tools:hostname - build the hostname and dnsdomainname tools sys-apps/net-tools:plipconfig - build the plipconfig tool (for working with old PLIP hardware) sys-apps/net-tools:slattach - build the slattach tool (for working with old serial ports) sys-apps/nvme-cli:json - Support JSON output via dev-libs/json-c +sys-apps/nvme-cli:pdc - Set default Persistent Discovery Controllers behavior sys-apps/openrazer:client - Build the OpenRazer daemon client sys-apps/openrazer:daemon - Build the OpenRazer daemon service sys-apps/openrc:bash - enable the use of bash in service scripts (experimental) @@ -7906,6 +7853,12 @@ sys-apps/openrc:newnet - enable the new network stack (experimental) sys-apps/openrc:s6 - install s6-linux-init sys-apps/openrc:sysv-utils - Install sysvinit compatibility scripts for halt, init, poweroff, reboot and shutdown sys-apps/openrc:sysvinit - control the dependency on sysvinit (experimental) +sys-apps/openrc-navi:bash - enable the use of bash in service scripts (experimental) +sys-apps/openrc-navi:netifrc - enable Gentoo's network stack (net.* scripts) +sys-apps/openrc-navi:newnet - enable the new network stack (experimental) +sys-apps/openrc-navi:s6 - install s6-linux-init +sys-apps/openrc-navi:sysv-utils - Install sysvinit compatibility scripts for halt, init, poweroff, reboot and shutdown +sys-apps/openrc-navi:sysvinit - control the dependency on sysvinit (experimental) sys-apps/pciutils:dns - Enable support for querying the central database of PCI IDs using DNS sys-apps/pciutils:kmod - Enable sys-apps/kmod support for the -k switch in lspci command sys-apps/pciutils:zlib - Support compressed pci.ids database @@ -7940,7 +7893,6 @@ sys-apps/s390-tools:zlib - build the zgetdump and dump2tar utilities sys-apps/s6:execline - enable support for dev-lang/execline sys-apps/s6-linux-init:sysv-utils - Install sysvinit compatibility symlinks for telinit, halt, poweroff, reboot, and shutdown sys-apps/sandbox:nnp - Enable NO_NEW_PRIVS which blocks set*id programs from gaining privileges (e.g. sudo) -sys-apps/shadow:bcrypt - build the bcrypt password encryption algorithm sys-apps/shadow:su - build the su program sys-apps/smartmontools:caps - Build against sys-libs/libcap-ng to allow smartd to drop its privileges. sys-apps/smartmontools:daemon - Install the monitoring daemon (smartd) and associated scripts. @@ -7950,6 +7902,7 @@ sys-apps/superdiag:iso - Install an iso image, which can be used with sys-apps/s sys-apps/superdiag:usb - Install all files, which are needed for an installation on an usb thumb drive. sys-apps/systemd:audit - Enable support for sys-process/audit sys-apps/systemd:boot - Enable EFI boot manager and stub loader +sys-apps/systemd:bpf - Enable BPF support for sandboxing and firewalling. sys-apps/systemd:cgroup-hybrid - Default to hybrid (legacy) cgroup hierarchy instead of unified (modern). sys-apps/systemd:cryptsetup - Enable cryptsetup tools (includes unit generator for crypttab) sys-apps/systemd:curl - Enable support for uploading journals @@ -8003,7 +7956,7 @@ sys-apps/watchdog:nfs - enable support for checking nfs mounts sys-apps/xdg-desktop-portal:flatpak - Enable sys-apps/flatpak integration sys-apps/xdg-desktop-portal:seccomp - Use sys-apps/bubblewrap (which requires seccomp) to sandbox some functionality like icon handling sys-apps/xinetd:rpc - support RPC services -sys-auth/elogind:cgroup-hybrid - Use hybrid cgroup hierarchy (OpenRC's default) instead of unified. +sys-auth/elogind:cgroup-hybrid - Use hybrid cgroup hierarchy instead of unified (OpenRC's default). sys-auth/munge:gcrypt - Use libgcrypt instead of openssl sys-auth/nss-pam-ldapd:pynslcd - Install the python implementation along with the standard implementation sys-auth/nss-pam-ldapd:utils - Install the command-line utilities @@ -8034,13 +7987,12 @@ sys-auth/seatd:builtin - Enable embedded server in libseat sys-auth/seatd:server - Enable standalone seatd server, replacement to (e)logind sys-auth/ssh-ldap-pubkey:schema - Install a copy of the LPK schema, only needed on LDAP servers. sys-auth/sssd:acl - Build and use the cifsidmap plugin -sys-auth/sssd:keyutils - Controls whether the kernel keyring should be used via sys-apps/keyutils sys-auth/sssd:netlink - Add support for netlink protocol via dev-libs/libnl sys-auth/sssd:nfsv4 - Add support for the nfsv4 idmapd plugin provided by net-fs/nfs-utils sys-auth/sssd:samba - Add Privileged Attribute Certificate Support for Kerberos sys-auth/sssd:subid - Support subordinate uid and gid ranges in FreeIPA sys-auth/sssd:sudo - Build helper to let app-admin/sudo use sssd provided information -sys-auth/sssd:systemtap - Enable SystemTAP/DTrace tracing +sys-auth/sssd:systemtap - Enable SystemTap/DTrace tracing sys-block/f3:extra - Build the additional f3probe, f3brew and f3fix utility (requires sys-block/parted and virtual/udev) sys-block/fio:aio - Enable AIO ioengine sys-block/fio:curl - Enable HTTP engine for S3 and WebDav support support via net-misc/curl @@ -8079,7 +8031,7 @@ sys-block/sas3flash:uefi - Install UEFI variant as well sys-block/sas3ircu:uefi - Install EFI variant as well sys-block/tgt:rbd - Add support for ceph block devices sys-block/thin-provisioning-tools:io-uring - Enable experimental support for io-uring. -sys-boot/grub:device-mapper - Enable support for device-mapper from sys-fs/lvm2 +sys-boot/grub:device-mapper - Enable support for devmapper. Required for LUKS or LVM volume detection. sys-boot/grub:efiemu - Build and install the efiemu runtimes sys-boot/grub:fonts - Build and install fonts for the gfxterm module sys-boot/grub:libzfs - Enable support for sys-fs/zfs @@ -8215,6 +8167,7 @@ sys-devel/binutils-hppa64:gprofng - Enable the next-generation gprofng profiler sys-devel/binutils-hppa64:multitarget - Adds support to binutils for cross compiling (does not work with gas) sys-devel/binutils-hppa64:pgo - Build binutils with Profile Guided Optimization (PGO) and LTO sys-devel/binutils-hppa64:plugins - Enable plugin support in tools +sys-devel/bpf-toolchain:bin-symlinks - Symlink executables to usr/bin to be in default PATH (conflicts with crossdev bpf, and crossdev is preferable for a fully featured toolchain) sys-devel/clang:extra - Build extra tools (clangd, clang-tidy and a few more) sys-devel/clang:ieee-long-double - Use accelerated 128-bit IEEE long double ABI (ppc64le only) sys-devel/clang:static-analyzer - Install the Clang static analyzer @@ -8311,6 +8264,7 @@ sys-fs/android-file-transfer-linux:zune - Enable support for Microsoft Zune sys-fs/avfs:webdav - Allow mounting WebDAV shares via net-libs/neon sys-fs/bcachefs-tools:fuse - Enable bcachefs FUSE support (experimental!) sys-fs/btrfs-progs:convert - Build ext2 conversion utility (btrfs-convert) +sys-fs/btrfs-progs:experimental - Enable unstable and experimental features and install btrfs-corrupt-block, as needed by xfstests sys-fs/btrfs-progs:reiserfs - Enable reiserfs support in btrfs-convert tool. sys-fs/btrfs-progs:static - Build static binaries in addition to the dynamic ones sys-fs/btrfsmaintenance:systemd - Enable systemd services and timers instead of cron timers @@ -8335,6 +8289,7 @@ sys-fs/dmraid:intel-led - Enable Intel LED support sys-fs/dmraid:led - Enable LED support sys-fs/dmraid:mini - Create a minimal binary suitable for early boot environments sys-fs/dosfstools:compat - Install symlinks for legacy names of the tools +sys-fs/e2fsprogs:archive - Add support for mke2fs to read a tarball as input. This allows not needing privileges. Needs app-arch/libarchive. sys-fs/e2fsprogs:cron - Install e2scrub_all cron script sys-fs/e2fsprogs:fuse - Build fuse2fs, a FUSE file system client for ext2/ext3/ext4 file systems sys-fs/e2fsprogs:tools - Build extfs tools (mke2fs, e2fsck, tune2fs, etc.) @@ -8343,6 +8298,7 @@ sys-fs/ecryptfs-utils:openssl - Enable dev-libs/openssl key module sys-fs/ecryptfs-utils:pkcs11 - Enable PKCS#11 (Smartcards) key module sys-fs/ecryptfs-utils:tpm - Enable support for Trusted Platform Module (TPM) using app-crypt/trousers sys-fs/erofs-utils:fuse - Builds erofsfuse (requires sys-fs/fuse). +sys-fs/erofs-utils:libdeflate - Use app-arch/libdeflate rather than sys-libs/zlib for handling deflate compression. sys-fs/erofs-utils:uuid - Enables UUID support via sys-apps/util-linux. sys-fs/ext4magic:expert-mode - Builds ext4magic with expert mode. Highly useful in recovering data from a corrupted filesystem sys-fs/ext4magic:file-attr - Enable the recovery of file attributes (append, immutable, nodump etc) @@ -8354,6 +8310,7 @@ sys-fs/lvm2:lvm - Build all of LVM2 including daemons and tools like lvchange, n sys-fs/lvm2:sanlock - Enable lvmlockd with support for sanlock sys-fs/lvm2:thin - Support for thin volumes sys-fs/mdadm:corosync - Support for corosync cluster engine +sys-fs/mtd-utils:ubifs - Build UBIFS tools sys-fs/mtpfs:mad - Enable handling of MP3's metadata sys-fs/ntfs3g:fuse - Enable ntfs-3g FUSE driver sys-fs/ntfs3g:mount-ntfs - Install mount.ntfs symlink @@ -8380,18 +8337,20 @@ sys-fs/zfs-kmod:rootfs - Pull dependencies and check kernel options required for sys-kernel/asahi-sources:rust - Pull in the Rust For Linux dependencies sys-kernel/asahi-sources:symlink - Automatically symlink the kernel sources to /usr/src/linux sys-kernel/genkernel:firmware - Prefer system firmware sys-kernel/linux-firmware over local copy. +sys-kernel/gentoo-kernel:experimental - Apply experimental patches; for more information, see "https://wiki.gentoo.org/wiki/Project:Kernel/Experimental". sys-kernel/gentoo-kernel:generic-uki - Build and install a generic initramfs and Unified Kernel Image, this is intended for building binpkgs with a pre-generated UKI included (EXPERIMENTAL). sys-kernel/gentoo-kernel:hardened - Use selection of hardening options recommended by Kernel Self Protection Project sys-kernel/gentoo-kernel:initramfs - Build initramfs along with the kernel. sys-kernel/gentoo-kernel-bin:generic-uki - Install a prebuilt generic initramfs and Unified Kernel Image (EXPERIMENTAL). sys-kernel/gentoo-kernel-bin:initramfs - Build initramfs along with the kernel. sys-kernel/gentoo-sources:experimental - Apply experimental patches; for more information, see "https://wiki.gentoo.org/wiki/Project:Kernel/Experimental". -sys-kernel/installkernel:dracut - Generate an initrd or UKI on each kernel installation +sys-kernel/installkernel:dracut - Generate an initramfs or UKI on each kernel installation sys-kernel/installkernel:efistub - EXPERIMENTAL: Update UEFI configuration on each kernel installation sys-kernel/installkernel:grub - Re-generate grub.cfg on each kernel installation, used grub.cfg is overridable with GRUB_CFG env var sys-kernel/installkernel:refind - Install a Gentoo icon for rEFInd alongside the (unified) kernel image, used icon is overridable with REFIND_ICON env var sys-kernel/installkernel:systemd - Use systemd's kernel-install to install kernels, overridable with SYSTEMD_KERNEL_INSTALL env var sys-kernel/installkernel:systemd-boot - Use systemd-boot's native layout by default +sys-kernel/installkernel:ugrd - Generate an initramfs using UGRD on each kernel installation sys-kernel/installkernel:uki - Install UKIs to ESP/EFI/Linux for EFI stub booting and/or bootloaders with support for auto-discovering UKIs sys-kernel/installkernel:ukify - Build an UKI with systemd's ukify on each kernel installation sys-kernel/kpatch:contrib - Enable contrib kpatch services files. @@ -8426,8 +8385,10 @@ sys-libs/compiler-rt-sanitizers:libfuzzer - Build fuzzing runtime. sys-libs/compiler-rt-sanitizers:lsan - Build Leak Sanitizer runtime. sys-libs/compiler-rt-sanitizers:memprof - Build memory profiler runtime. sys-libs/compiler-rt-sanitizers:msan - Build Memory Sanitizer runtime. +sys-libs/compiler-rt-sanitizers:nsan - Build Numerical Sanitizer runtime. sys-libs/compiler-rt-sanitizers:orc - Build ORC runtime. sys-libs/compiler-rt-sanitizers:profile - Build profiling runtime. +sys-libs/compiler-rt-sanitizers:rtsan - Build Realtime Sanitizer runtime. sys-libs/compiler-rt-sanitizers:safestack - Build SafeStack runtime. sys-libs/compiler-rt-sanitizers:scudo - Build Scudo Hardened Allocator. sys-libs/compiler-rt-sanitizers:shadowcallstack - Build ShadowCallStack. @@ -8517,57 +8478,6 @@ sys-power/nut:modbus - Includes all UPS drivers that use MODBUS. sys-power/nut:monitor - Add a QT5 gui monitor. sys-power/nut:serial - Includes all UPS drivers that use SERIAL. sys-power/nut:snmp - Includes all UPS drivers that use SNMP. -sys-power/nut:ups_drivers_al175 - Driver for Eltek UPS models with AL175 alarm module -sys-power/nut:ups_drivers_apcsmart - Driver for American Power Conversion Smart Protocol UPS equipment -sys-power/nut:ups_drivers_apcsmart-old - Driver for American Power Conversion Smart Protocol UPS equipment -sys-power/nut:ups_drivers_apcupsd-ups - Driver for apcupsd client access -sys-power/nut:ups_drivers_bcmxcp - Driver for UPSes supporting the serial BCM/XCP protocol -sys-power/nut:ups_drivers_bcmxcp_usb - Experimental driver for UPSes supporting the BCM/XCP protocol over USB -sys-power/nut:ups_drivers_belkin - Driver for Belkin serial UPS equipment -sys-power/nut:ups_drivers_belkinunv - Driver for Belkin "Universal UPS" and compatible -sys-power/nut:ups_drivers_bestfcom - Driver for Best Power Fortress/Ferrups -sys-power/nut:ups_drivers_bestfortress - Driver for old Best Fortress UPS equipment -sys-power/nut:ups_drivers_bestuferrups - Driver for Best Power Micro-Ferrups -sys-power/nut:ups_drivers_bestups - Driver for Best Power / SOLA (Phoenixtec protocol) UPS equipment -sys-power/nut:ups_drivers_blazer_ser - Driver for Megatec/Q1 protocol serial based UPS equipment -sys-power/nut:ups_drivers_blazer_usb - Driver for Megatec/Q1 protocol USB based UPS equipment -sys-power/nut:ups_drivers_clone - Fake driver to clone outlets for device grouping -sys-power/nut:ups_drivers_clone-outlet - Fake driver to clone outlets for device grouping -sys-power/nut:ups_drivers_dummy-ups - Driver for multi-purpose UPS emulation -sys-power/nut:ups_drivers_etapro - Driver for ETA UPS equipment -sys-power/nut:ups_drivers_everups - Driver for Ever UPS models -sys-power/nut:ups_drivers_gamatronic - Driver for Gamatronic UPS equipment -sys-power/nut:ups_drivers_genericups - Driver for contact-closure UPS equipment -sys-power/nut:ups_drivers_isbmex - Driver for ISBMEX UPS equipment -sys-power/nut:ups_drivers_ivtscd - driver for the IVT Solar Controller Device -sys-power/nut:ups_drivers_liebert - Driver for Liebert contact-closure UPS equipment -sys-power/nut:ups_drivers_liebert-esp2 - Driver for Liebert UPS, using the ESP-II serial protocol -sys-power/nut:ups_drivers_masterguard - Driver for Masterguard UPS equipment -sys-power/nut:ups_drivers_metasys - Driver for Meta System UPS equipment -sys-power/nut:ups_drivers_mge-shut - Driver for SHUT Protocol UPS equipment -sys-power/nut:ups_drivers_mge-utalk - Driver for MGE UPS SYSTEMS UTalk protocol equipment -sys-power/nut:ups_drivers_microdowell - Driver for Microdowell Enterprise UPS series -sys-power/nut:ups_drivers_netxml-ups - Driver for Eaton / MGE Network Management Card / Proxy (XML/HTTP Protocol) equipment -sys-power/nut:ups_drivers_nut-ipmipsu - Driver for IPMI Power Supply Units (PSU) -sys-power/nut:ups_drivers_nutdrv_qx - Driver for Q* protocol serial and USB based UPS equipment -sys-power/nut:ups_drivers_oldmge-shut - Driver for SHUT Protocol UPS equipment (older implementation) -sys-power/nut:ups_drivers_oneac - Driver for Oneac UPS equipment -sys-power/nut:ups_drivers_optiups - Driver for Opti-UPS (Viewsonic) UPS and Zinto D (ONLINE-USV) equipment -sys-power/nut:ups_drivers_powercom - UPS driver for serial Powercom/Trust/Advice UPS equipment -sys-power/nut:ups_drivers_powerpanel - Driver for PowerPanel Plus compatible UPS equipment -sys-power/nut:ups_drivers_rhino - Driver for Brazilian Microsol RHINO UPS equipment -sys-power/nut:ups_drivers_richcomm_usb - Driver UPS equipment using Richcomm dry-contact to USB solution -sys-power/nut:ups_drivers_riello_ser - Driver for Riello UPS Protocol UPS equipment -sys-power/nut:ups_drivers_riello_usb - Driver for Riello UPS Protocol UPS equipment via USB -sys-power/nut:ups_drivers_safenet - Driver for SafeNet compatible UPS equipment -sys-power/nut:ups_drivers_snmp-ups - Multi-MIB Driver for SNMP UPS equipment -sys-power/nut:ups_drivers_solis - Driver for Brazilian Microsol SOLIS UPS equipment -sys-power/nut:ups_drivers_tripplite - Driver for Tripp-Lite SmartPro UPS equipment -sys-power/nut:ups_drivers_tripplite_usb - Driver for older Tripp Lite USB UPSes (not PDC HID) -sys-power/nut:ups_drivers_tripplitesu - Driver for Tripp-Lite SmartOnline (SU) UPS equipment -sys-power/nut:ups_drivers_upscode2 - Driver for UPScode II compatible UPS equipment -sys-power/nut:ups_drivers_usbhid-ups - Driver for USB/HID UPS equipment -sys-power/nut:ups_drivers_victronups - Driver for IMV/Victron UPS unit Match, Match Lite, NetUps sys-power/nut:usb - Includes all UPS drivers that use USB. sys-power/nut:xml - Includes all UPS drivers that use XML. sys-power/nvclock:gtk - Install the GTK+ based graphical interface @@ -8643,6 +8553,7 @@ www-apps/cgit:highlight - Enable source code highlighting www-apps/cgit:lua - Enable support for Lua scripting www-apps/drupal:uploadprogress - Install dev-php/pecl-uploadprogress package www-apps/gitea:acct - User and group management via acct-*/git packages +www-apps/gitea:gogit - (EXPERIMENTAL) Use go-git variants of Git commands. www-apps/hugo:extended - Enable SASS/SCSS and WebP encoding support www-apps/icingaweb2:apache2-server - Adds support for the apache2-server www-apps/icingaweb2:fpm - Adds FPM support to php @@ -8660,7 +8571,9 @@ www-apps/roundup:pyjwt - Enable jwt tokens for login www-apps/roundup:tz - Enable full support of timezone www-apps/roundup:whoosh - Enable Whoosh full-text indexer www-apps/roundup:xapian - Enable Xapian full-text indexer +www-apps/rt:apache - Add www-servers/apache support www-apps/rt:lighttpd - Add www-servers/lighttpd support +www-apps/rt:nginx - Add www-servers/nginx support www-apps/tt-rss:daemon - Install additional init scripts for automated RSS updates www-apps/ttyd:mbedtls - Use mbedTLS replacement for OpenSSL www-apps/webdavcgi:rcs - Adds support for a revision controlled backend with RCS (dev-vcs/rcs) @@ -8674,8 +8587,6 @@ www-client/chromium:ffmpeg-chromium - (binpkg only) Use Chromium FFmpeg fork (me www-client/chromium:gtk4 - Build with GTK4 headers. www-client/chromium:hangouts - Enable support for Google Hangouts features such as screen sharing www-client/chromium:headless - Build Ozone only with headless backend, NOT RECOMMENDED for general use. -www-client/chromium:libcxx - Use bundled libc++ instead of libstdc++ for building. -www-client/chromium:lto - Build with Link Time Optimizations (via clang's ThinLTO) www-client/chromium:official - Enable Official build instead of Developer build. www-client/chromium:pax-kernel - Allow building on a PaX-enabled kernel www-client/chromium:pgo - Build with Profile Guided Optimizations (2-stage compilation) @@ -8686,6 +8597,9 @@ www-client/chromium:system-png - Use system media-libs/libpng instead of the bun www-client/chromium:system-toolchain - Use system toolchain instead of the bundled one (if possible) www-client/chromium:system-zstd - Use system app-arch/zstd instead of the bundled one. www-client/chromium:widevine - Unsupported closed-source DRM capability (required by Netflix VOD) +www-client/dillo:mbedtls - Build against the net-libs/mbedtls library for TLS support. +www-client/dillo:openssl - Build against the dev-libs/openssl library for TLS support. +www-client/dillo:xembed - Enable XEmbed protocol support www-client/elinks:bittorrent - Enable support for the BitTorrent protocol www-client/elinks:finger - Enable support for the finger protocol www-client/elinks:gopher - Enable support for the gopher protocol @@ -8696,6 +8610,7 @@ www-client/firefox:clang - Use Clang compiler instead of GCC www-client/firefox:eme-free - Disable EME (DRM plugin) capability at build time www-client/firefox:geckodriver - Enable WebDriver support www-client/firefox:gmp-autoupdate - Allow Gecko Media Plugins (binary blobs) to be automatically downloaded and kept up-to-date in user profiles +www-client/firefox:gnome-shell - Integrate with gnome-base/gnome-shell search www-client/firefox:hwaccel - Force-enable hardware-accelerated rendering (Mozilla bug 594876) www-client/firefox:jumbo-build - Enable unified build - combines source files to speed up build process, but requires more memory www-client/firefox:libproxy - Enable libproxy support @@ -8737,7 +8652,6 @@ www-client/opera-beta:proprietary-codecs - Enable codecs for patent-encumbered a www-client/opera-developer:ffmpeg-chromium - Use Chromium FFmpeg fork (media-video/ffmpeg-chromium) rather than mainline FFmpeg (media-video/ffmpeg) www-client/opera-developer:proprietary-codecs - Enable codecs for patent-encumbered audio and video formats. www-client/qutebrowser:adblock - Enable Brave's ABP-style adblocker library for improved adblocking -www-client/qutebrowser:qt6 - Use Qt6 that provides a newer Chromium version www-client/qutebrowser:widevine - Unsupported closed-source DRM capability (required by Netflix VOD) www-client/seamonkey:chatzilla - Build Mozilla's IRC client (default on) www-client/seamonkey:custom-optimization - Build with user-specified compiler optimizations (-Os, -O0, -O1, -O2, -O3) from CFLAGS (unsupported) @@ -8793,15 +8707,14 @@ www-servers/kore:json - Add support for JSONRPC www-servers/kore:openssl - Use the openssl TLS backend www-servers/lighttpd:brotli - Enable output compression via app-arch/brotli (recommended) www-servers/lighttpd:gnutls - Build module for TLS via net-libs/gnutls +www-servers/lighttpd:libdeflate - Enable output compression via app-arch/libdeflate www-servers/lighttpd:maxminddb - Add support for geolocation using dev-libs/libmaxminddb www-servers/lighttpd:mbedtls - Build module for TLS via net-libs/mbedtls -www-servers/lighttpd:nettle - Use dev-libs/nettle as crypto backend +www-servers/lighttpd:nettle - Use dev-libs/nettle as crypto library www-servers/lighttpd:nss - Build module for TLS via Mozilla's Network Security Services www-servers/lighttpd:webdav - Enable webdav properties www-servers/lighttpd:zlib - Enable output compression via gzip or deflate algorithms from sys-libs/zlib www-servers/lighttpd:zstd - Enable output compression via Zstandard (app-arch/zstd) algorithm -www-servers/monkeyd:debug - Enable lots of debugging info -www-servers/monkeyd:static-plugins - Build statically linked plugins www-servers/nginx:aio - Enables file AIO support www-servers/nginx:http - Enable HTTP core support www-servers/nginx:http-cache - Enable HTTP cache support @@ -8824,7 +8737,6 @@ www-servers/tomcat:extra-webapps - Build also the docs and examples webapp www-servers/uwsgi:embedded - Embed plugins instead of building them as real plugins. When disabling this USE flag make sure you specify all used plugins in your uWSGI configuration. Note: Language plugins will always be built as real plugins. www-servers/uwsgi:go - Build the gccgo plugin to run Go applications. www-servers/uwsgi:json - Support json as a configuration file format. -www-servers/uwsgi:python-asyncio - Use the EXPERIMENTAL asyncio (tulip) for python3.4 async request dispatching and as LoopEngine (see http://uwsgi-docs.readthedocs.org/en/latest/asyncio.html). www-servers/uwsgi:routing - Enable routing support www-servers/uwsgi:yajl - Use dev-libs/yajl instead of dev-libs/jansson for parsing JSON configuration files (if USe=json is set) www-servers/uwsgi:yaml - Support yaml as a configuration file format. @@ -8851,7 +8763,7 @@ x11-base/xorg-server:xvfb - Build the Xvfb server x11-base/xwayland:libei - Enable emulated input using dev-libs/libei x11-base/xwayland:unwind - Enable libunwind usage for backtraces x11-base/xwayland:xcsecurity - Build Security extension -x11-drivers/nvidia-drivers:kernel-open - Use the open source variant of drivers (Turing/Ampere+ GPUs only, aka GTX 1650+, experimental) +x11-drivers/nvidia-drivers:kernel-open - Use the open source variant of the drivers (Turing/Ampere+ GPUs only, aka GTX 1650+ -- recommended with >=560.xx drivers if usable) x11-drivers/nvidia-drivers:persistenced - Install the persistence daemon for keeping devices state when unused (e.g. for headless) x11-drivers/nvidia-drivers:powerd - Install the NVIDIA dynamic boost support daemon (only useful with specific laptops, ignore if unsure) x11-drivers/nvidia-drivers:static-libs - Install the XNVCtrl static library for accessing sensors and other features @@ -8923,6 +8835,7 @@ x11-misc/i3blocks:contrib - Install contrib modules x11-misc/i3status:filecaps - Linux capabilities library is required for i3status to be able to read net bandwidth x11-misc/j4-dmenu-desktop:dmenu - Use x11-misc/dmenu as default. Disable to use a different implementation. x11-misc/ktsuss:sudo - Use the sudo backend instead the su one +x11-misc/libinput-gestures:experimental - avoid producing zombie processes x11-misc/light-locker:dpms - Turn on the display on screensaver deactivation. x11-misc/light-locker:screensaver - Lock the screen on screensaver activation. x11-misc/lightdm:gtk - Pull in the gtk+ greeter @@ -9005,7 +8918,6 @@ x11-terms/aterm:background - Enable background image support via media-libs/liba x11-terms/aterm:xgetdefault - Enable resources via X instead of aterm small version x11-terms/gnome-terminal:gnome-shell - Integrate with gnome-base/gnome-shell search x11-terms/gnome-terminal:nautilus - Build gnome-base/nautilus extension -x11-terms/guake:utempter - Include utmp management support via sys-libs/libutempter x11-terms/mlterm:brltty - Enable support for app-accessibility/brltty x11-terms/mlterm:fcitx - Enable support for app-i18n/fcitx x11-terms/mlterm:harfbuzz - Enable support for OpenType Layout (media-libs/harfbuzz) @@ -9054,23 +8966,7 @@ x11-themes/gentoo-artwork:pixmaps - Install pixmaps x11-themes/gtk-engines-murrine:animation-rtl - Progressbar animation from right to left x11-themes/gtk-engines-murrine:themes - Pull in themes via x11-themes/murrine-themes x11-themes/kfaenza:additional - Install additional KFaenza icons. See third homepage for details -x11-themes/tela-icon-theme:black - Install black folder version -x11-themes/tela-icon-theme:blue - Install blue folder version -x11-themes/tela-icon-theme:brown - Install bworn folder version -x11-themes/tela-icon-theme:dracula - Install dracula folder version -x11-themes/tela-icon-theme:green - Install green folder version -x11-themes/tela-icon-theme:grey - Install grey folder version x11-themes/tela-icon-theme:hardlink - Hardlink duplicate icons to greatly reduce installation size -x11-themes/tela-icon-theme:kde - Install dynamic color version for KDE plasma (folder color follows the colorscheme) -x11-themes/tela-icon-theme:manjaro - Install manjaro folder version -x11-themes/tela-icon-theme:nord - Install nord folder version -x11-themes/tela-icon-theme:orange - Install orange folder version -x11-themes/tela-icon-theme:pink - Install pink folder version -x11-themes/tela-icon-theme:purple - Install purple folder version -x11-themes/tela-icon-theme:red - Install red older version -x11-themes/tela-icon-theme:standard - Install standard folder version -x11-themes/tela-icon-theme:ubuntu - Install ubuntu folder version -x11-themes/tela-icon-theme:yellow - Install yellow folder version x11-themes/vertex-theme:cinnamon - Install theme for gnome-extra/cinnamon x11-themes/vertex-theme:gnome-shell - Install theme for gnome-base/gnome-shell x11-themes/vertex-theme:mate - Install Metacity theme for mate-base/mate @@ -9139,10 +9035,14 @@ x11-wm/xmonad-contrib:xft - Use Xft to render text x11-wm/xpra:client - Build client-side code x11-wm/xpra:clipboard - Enable clipboard support x11-wm/xpra:csc - Enable csc softscaler support +x11-wm/xpra:gtk3 - Enable the GTK3 client x11-wm/xpra:html - Install the HTML5 client x11-wm/xpra:ibus - Use ibus input method via app-i18n/ibus +x11-wm/xpra:mdns - Enable Multicast DNS via dev-libs/mdns x11-wm/xpra:oauth - Enable OAuth2 authentication in the server +x11-wm/xpra:openh264 - Enable H.264 support using media-libs/openh264 x11-wm/xpra:pinentry - Use app-crypt/pinentry for password entry +x11-wm/xpra:qrcode - Enable generating QRCodes for server URL via media-gfx/qrencode x11-wm/xpra:server - Build server-side code x11-wm/xpra:trayicon - Enable system tray icon x11-wm/xpra:vpx - Enable vpx image format support |