diff options
Diffstat (limited to 'profiles')
132 files changed, 12252 insertions, 160 deletions
diff --git a/profiles/Manifest.gz b/profiles/Manifest.gz Binary files differindex 57d541adc197..26900ba6d85a 100644 --- a/profiles/Manifest.gz +++ b/profiles/Manifest.gz diff --git a/profiles/arch/arm/package.use.mask b/profiles/arch/arm/package.use.mask index 93d1793bbe6d..4bb172204dc1 100644 --- a/profiles/arch/arm/package.use.mask +++ b/profiles/arch/arm/package.use.mask @@ -1,6 +1,10 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# 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 diff --git a/profiles/arch/arm/use.mask b/profiles/arch/arm/use.mask index f5ae9cb0482a..adc3b1cde78c 100644 --- a/profiles/arch/arm/use.mask +++ b/profiles/arch/arm/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. @@ -7,6 +7,7 @@ # 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/loong/package.use.mask b/profiles/arch/loong/package.use.mask index efb2472587f7..5f19febd74b7 100644 --- a/profiles/arch/loong/package.use.mask +++ b/profiles/arch/loong/package.use.mask @@ -85,6 +85,7 @@ 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 diff --git a/profiles/arch/loong/use.mask b/profiles/arch/loong/use.mask index e0e50583c2ab..833644072e72 100644 --- a/profiles/arch/loong/use.mask +++ b/profiles/arch/loong/use.mask @@ -39,6 +39,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/powerpc/package.use.mask b/profiles/arch/powerpc/package.use.mask index 8ae2a829a2fd..23c554b9ad3d 100644 --- a/profiles/arch/powerpc/package.use.mask +++ b/profiles/arch/powerpc/package.use.mask @@ -76,6 +76,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 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/riscv/use.mask b/profiles/arch/riscv/use.mask index 4eb16fdf74f2..00ac5effb49e 100644 --- a/profiles/arch/riscv/use.mask +++ b/profiles/arch/riscv/use.mask @@ -22,6 +22,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/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/base/make.defaults b/profiles/base/make.defaults index 7d731fd07cf1..9ba2acfb4042 100644 --- a/profiles/base/make.defaults +++ b/profiles/base/make.defaults @@ -123,12 +123,12 @@ 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" +BOOTSTRAP_USE="unicode internal-glib pkg-config split-usr xml python_targets_python3_12 python_single_target_python3_12" # 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. @@ -164,7 +164,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) # 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/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/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/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/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/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/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/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/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/powerpc/ppc64/17.0/32bit-userland/deprecated b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/deprecated new file mode 100644 index 000000000000..4b91a95b3766 --- /dev/null +++ b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/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/powerpc/ppc64/17.0/32bit-userland/desktop/deprecated b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/deprecated new file mode 100644 index 000000000000..0159d2926b31 --- /dev/null +++ b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/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/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/deprecated b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/deprecated new file mode 100644 index 000000000000..0c3059bbec6b --- /dev/null +++ b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/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/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 000000000000..78c077397232 --- /dev/null +++ b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/ppc/23.0/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/powerpc/ppc64/17.0/32bit-userland/developer/deprecated b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/deprecated new file mode 100644 index 000000000000..4b91a95b3766 --- /dev/null +++ b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/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/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/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/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/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/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/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/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/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/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/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/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/features/llvm/make.defaults b/profiles/features/llvm/make.defaults index ce3401222615..defd200ce9d1 100644 --- a/profiles/features/llvm/make.defaults +++ b/profiles/features/llvm/make.defaults @@ -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/package.mask b/profiles/package.mask index 91375ba1699a..3d52ca327496 100644 --- a/profiles/package.mask +++ b/profiles/package.mask @@ -33,6 +33,24 @@ #--- END OF EXAMPLES --- +# Mike Gilbert <floppym@gentoo.org> (2024-06-01) +# Abandoned upstream. No Gentoo maintainer since 2021. +# Plugin system seems quite broken (bug 887119). +# Removal on 2024-07-01. +sys-fs/reiser4progs +sys-libs/libaal + +# Hans de Graaff <graaff@gentoo.org> (2024-06-01) +# Old ruby31-only slots. Please use a newer slot of these +# packages. Masked for removal on 2024-07-01. +dev-ruby/elasticsearch:6.8.3 +dev-ruby/elasticsearch-api:6.8.3 +dev-ruby/elasticsearch-transport:6.8.3 +dev-ruby/mimemagic:0 +dev-ruby/puppet_forge:2 +dev-ruby/puppet_forge:4 +dev-ruby/rspec-rails:5 + # Arthur Zamarin <arthurzam@gentoo.org> (2024-05-31) # EAPI=6, maintainer-needed, incorrect LICENSE, fails to compile with # clang. @@ -45,9 +63,10 @@ net-mail/gnubiff app-emulation/phpvirtualbox # Sam James <sam@gentoo.org> (2024-05-29) -# OpenPGP key of malicious xz co-maintainer. This key is no longer used -# by any ebuilds in tree. Removal on 2024-06-29. -# Bug #928134. +# OpenPGP key of malicious upstream xz co-maintainer. This key is no longer +# used by any ebuilds in tree. Removal on 2024-06-29. This package was already +# masked a while ago but is now being removed. See the bug for details +# on the gap. Bug #928134 (GLSA-202403-04). sec-keys/openpgp-keys-jiatan # Sam James <sam@gentoo.org> (2024-05-28) @@ -790,10 +809,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 diff --git a/profiles/profiles.desc b/profiles/profiles.desc index 3a9f5b22b107..ac4aea804aeb 100644 --- a/profiles/profiles.desc +++ b/profiles/profiles.desc @@ -30,20 +30,20 @@ alpha default/linux/alpha/23.0/split-usr/desktop/gnome exp # 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 @@ -279,10 +279,10 @@ 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 exp +ia64 default/linux/ia64/17.0/desktop exp +ia64 default/linux/ia64/17.0/desktop/gnome exp +ia64 default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr exp 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 @@ -297,19 +297,19 @@ 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 @@ -407,11 +407,11 @@ ppc default/linux/powerpc/ppc64/17.0/32bit-userland/developer exp # 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 +425,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 +443,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 +469,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 +533,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 +547,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 +570,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 +614,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 +626,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 +644,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 @@ -671,26 +671,26 @@ 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 +699,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 diff --git a/profiles/use.local.desc b/profiles/use.local.desc index b6d8426f95e3..5e6dbb5b962b 100644 --- a/profiles/use.local.desc +++ b/profiles/use.local.desc @@ -8637,6 +8637,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 |