profiles: remove powerpc/ppc64/17.0/32bit-userland/**

There were deprecated for ~2 years. There should be no need to use
this configuration today (on 64 bit hardware, use 64 bit userland)

Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
Closes: https://github.com/gentoo/gentoo/pull/37724
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>

18 files changed, 0 insertions, 571 deletions

diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/deprecated b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/deprecated
deleted file mode 100644
index 4b91a95b3766..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/deprecated
+++ /dev/null
@@ -1,104 +0,0 @@
-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
deleted file mode 100644
index 0159d2926b31..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/deprecated
+++ /dev/null
@@ -1,104 +0,0 @@
-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/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/eapi
deleted file mode 100644
index 7ed6ff82de6b..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/eapi
+++ /dev/null
@@ -1 +0,0 @@
-5
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/deprecated b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/deprecated
deleted file mode 100644
index 0c3059bbec6b..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/deprecated
+++ /dev/null
@@ -1,104 +0,0 @@
-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/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/eapi
deleted file mode 100644
index 7ed6ff82de6b..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/eapi
+++ /dev/null
@@ -1 +0,0 @@
-5
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/parent
deleted file mode 100644
index d5a56a13f692..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/parent
+++ /dev/null
@@ -1,2 +0,0 @@
-..
-../../../../../../../../targets/desktop/gnome
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/deprecated b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/deprecated
deleted file mode 100644
index 36bae5bdb267..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/deprecated
+++ /dev/null
@@ -1,33 +0,0 @@
-default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr
-
-As warned about previously in a news item, systemd-255 has dropped
-support for split-usr systems. All Gentoo systems running systemd will
-need to be migrated to merged-usr.
-
-Migrating to merged-usr will move all data from /bin, /sbin, and /lib
-into the /usr/bin and /usr/lib directories. The directories in / are
-replaced with symlinks.
-
-To facilitate this, a new set of sub-profiles has been created, and a
-script is available to perform the actual migration.
-
-To migrate a system to merged-usr, follow this procedure:
-
-1. Ensure your system backups are up to date. Please also update
-   your system fully and depclean before proceeding.
-
-2. Install sys-apps/merge-usr.
-
-3. Run "merge-usr --dryrun" as root to check for conflicts. These will
-   appear with the word ERROR at the start of the line.
-
-4. Resolve any conflicts. This may involve deleting duplicate files. If
-   in doubt, seek support in a Gentoo support channel.
-
-5. Run the merge-usr script from a root shell. Avoid running it via sudo
-   directly to avoid locking yourself out if an unexpected error occurs.
-
-6. Switch to a merged-usr profile.
-
-7. Run emerge with the --newuse or --changed-use option to rebuild
-   any packages that have a "split-usr" USE flag.
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/eapi
deleted file mode 100644
index 7ed6ff82de6b..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/eapi
+++ /dev/null
@@ -1 +0,0 @@
-5
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/deprecated b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/deprecated
deleted file mode 100644
index 78c077397232..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/deprecated
+++ /dev/null
@@ -1,104 +0,0 @@
-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/desktop/gnome/systemd/merged-usr/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/eapi
deleted file mode 100644
index 7ed6ff82de6b..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/eapi
+++ /dev/null
@@ -1 +0,0 @@
-5
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/parent
deleted file mode 100644
index 05b6f4918b26..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/parent
+++ /dev/null
@@ -1,2 +0,0 @@
-..
-../../../../../../../../../../features/merged-usr
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/parent
deleted file mode 100644
index 288aeccdce82..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/parent
+++ /dev/null
@@ -1,2 +0,0 @@
-..
-../../../../../../../../../targets/desktop/gnome/systemd
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/parent
deleted file mode 100644
index fae96e8d36b2..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/parent
+++ /dev/null
@@ -1,2 +0,0 @@
-..
-../../../../../../../targets/desktop
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/deprecated b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/deprecated
deleted file mode 100644
index 4b91a95b3766..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/deprecated
+++ /dev/null
@@ -1,104 +0,0 @@
-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/developer/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/eapi
deleted file mode 100644
index 7ed6ff82de6b..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/eapi
+++ /dev/null
@@ -1 +0,0 @@
-5
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/parent
deleted file mode 100644
index 4bb06e409236..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/parent
+++ /dev/null
@@ -1,2 +0,0 @@
-..
-../../../../../../../targets/developer
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/eapi b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/eapi
deleted file mode 100644
index 7ed6ff82de6b..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/eapi
+++ /dev/null
@@ -1 +0,0 @@
-5
diff --git a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/parent b/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/parent
deleted file mode 100644
index 898d55cbcebd..000000000000
--- a/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/parent
+++ /dev/null
@@ -1,2 +0,0 @@
-..
-../../../../../../arch/powerpc/ppc64/32ul