From d8f50c18cd4c626013a34b4f254f4295aca077d3 Mon Sep 17 00:00:00 2001 From: Flatcar Buildbot Date: Mon, 1 Jul 2024 07:17:45 +0000 Subject: [PATCH] profiles: Sync with Gentoo It's from Gentoo commit f328287a62cf11e026aa92c853557c8c8bafddf6. --- .../profiles/arch/alpha/package.use.mask | 19 +- .../profiles/arch/amd64/make.defaults | 2 +- .../arch/amd64/no-multilib/package.mask | 5 - .../profiles/arch/amd64/package.use.mask | 30 +- .../arch/amd64/package.use.stable.mask | 6 - .../profiles/arch/amd64/x32/package.mask | 12 +- .../profiles/arch/amd64/x32/package.use.mask | 12 +- .../arch/arm/23.0-armv7a_hf/package.mask | 4 - .../arch/arm/23.0-armv7a_sf/package.mask | 4 - .../profiles/arch/arm/armv7a/package.mask | 4 - .../profiles/arch/arm/make.defaults | 6 +- .../profiles/arch/arm/package.mask | 4 - .../profiles/arch/arm/package.use.mask | 36 +- .../profiles/arch/arm/package.use.stable.mask | 8 +- .../portage-stable/profiles/arch/arm/use.mask | 7 +- .../profiles/arch/arm/use.stable.mask | 6 +- .../profiles/arch/arm64/make.defaults | 2 +- .../profiles/arch/arm64/package.use.mask | 26 +- .../arch/arm64/package.use.stable.mask | 13 +- .../profiles/arch/arm64/use.mask | 22 +- .../profiles/arch/arm64/use.stable.mask | 8 + .../profiles/arch/base/package.use.mask | 39 +- .../profiles/arch/hppa/make.defaults | 6 +- .../profiles/arch/hppa/package.use.mask | 24 +- .../profiles/arch/hppa/use.stable.mask | 4 + .../profiles/arch/ia64/package.use.mask | 30 +- .../profiles/arch/loong/package.mask | 5 - .../profiles/arch/loong/package.use.mask | 29 +- .../profiles/arch/loong/use.mask | 5 + .../profiles/arch/m68k/package.mask | 6 + .../profiles/arch/m68k/package.use.mask | 4 + .../profiles/arch/m68k/use.mask | 4 + .../arch/mips/mips64/package.use.mask | 6 + .../profiles/arch/mips/package.use.mask | 41 +- .../profiles/arch/mips/use.mask | 5 - .../profiles/arch/powerpc/package.use.mask | 22 +- .../arch/powerpc/package.use.stable.mask | 7 +- .../profiles/arch/powerpc/ppc32/make.defaults | 2 +- .../arch/powerpc/ppc32/package.use.mask | 11 +- .../arch/powerpc/ppc32/use.stable.mask | 4 + .../arch/powerpc/ppc64/64le/package.mask | 26 +- .../arch/powerpc/ppc64/64le/package.use.mask | 4 - .../arch/powerpc/ppc64/64ul/package.mask | 10 + .../arch/powerpc/ppc64/64ul/package.use.mask | 7 +- .../profiles/arch/powerpc/ppc64/make.defaults | 2 +- .../profiles/arch/powerpc/ppc64/package.mask | 10 - .../arch/powerpc/ppc64/package.use.mask | 22 +- .../powerpc/ppc64/package.use.stable.mask | 10 +- .../profiles/arch/powerpc/ppc64/use.mask | 6 +- .../profiles/arch/powerpc/use.mask | 7 +- .../profiles/arch/powerpc/use.stable.mask | 6 +- .../profiles/arch/ppc/package.use.mask | 8 +- .../profiles/arch/riscv/package.use.mask | 19 +- .../profiles/arch/riscv/use.mask | 5 + .../profiles/arch/s390/package.use.mask | 6 +- .../profiles/arch/sparc/make.defaults | 6 +- .../profiles/arch/sparc/package.mask | 9 +- .../profiles/arch/sparc/package.use.mask | 37 +- .../arch/sparc/package.use.stable.mask | 1 - .../profiles/arch/sparc/use.mask | 6 +- .../profiles/arch/sparc/use.stable.mask | 4 + .../profiles/arch/x86/i486/package.use.mask | 8 + .../profiles/arch/x86/make.defaults | 2 +- .../profiles/arch/x86/package.mask | 4 - .../profiles/arch/x86/package.use | 5 + .../profiles/arch/x86/package.use.mask | 25 +- .../profiles/arch/x86/package.use.stable.mask | 8 + .../portage-stable/profiles/arch/x86/use.mask | 5 + .../profiles/arch/x86/use.stable.mask | 4 - .../profiles/base/make.defaults | 15 +- .../portage-stable/profiles/base/package.use | 7 + .../profiles/base/package.use.force | 21 +- .../profiles/base/package.use.mask | 62 +- .../profiles/base/package.use.stable.force | 4 - .../profiles/base/package.use.stable.mask | 10 +- .../portage-stable/profiles/base/use.mask | 9 +- .../profiles/base/use.stable.mask | 17 +- .../default/linux/alpha/17.0/deprecated | 104 ++ .../linux/alpha/17.0/desktop/deprecated | 104 ++ .../linux/alpha/17.0/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../linux/alpha/17.0/developer/deprecated | 104 ++ .../alpha/17.0/systemd/merged-usr/deprecated | 104 ++ .../linux/amd64/17.0/musl/clang/deprecated | 104 ++ .../default/linux/amd64/17.0/musl/deprecated | 104 ++ .../linux/amd64/17.0/musl/hardened/deprecated | 104 ++ .../17.0/musl/hardened/selinux/deprecated | 104 ++ .../default/linux/amd64/17.0/x32/deprecated | 104 ++ .../17.0/x32/systemd/merged-usr/deprecated | 104 ++ .../default/linux/amd64/17.1/clang/deprecated | 104 ++ .../default/linux/amd64/17.1/deprecated | 104 ++ .../linux/amd64/17.1/desktop/deprecated | 104 ++ .../linux/amd64/17.1/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../amd64/17.1/desktop/plasma/deprecated | 104 ++ .../plasma/systemd/merged-usr/deprecated | 104 ++ .../desktop/systemd/merged-usr/deprecated | 104 ++ .../linux/amd64/17.1/developer/deprecated | 104 ++ .../linux/amd64/17.1/hardened/deprecated | 104 ++ .../amd64/17.1/hardened/selinux/deprecated | 104 ++ .../linux/amd64/17.1/no-multilib/deprecated | 104 ++ .../17.1/no-multilib/hardened/deprecated | 104 ++ .../no-multilib/hardened/selinux/deprecated | 104 ++ .../no-multilib/systemd/merged-usr/deprecated | 104 ++ .../no-multilib/systemd/selinux/deprecated | 33 + .../systemd/selinux/merged-usr/deprecated | 104 ++ .../linux/amd64/17.1/selinux/deprecated | 104 ++ .../linux/amd64/17.1/systemd/clang/deprecated | 33 + .../17.1/systemd/clang/merged-usr/deprecated | 104 ++ .../amd64/17.1/systemd/merged-usr/deprecated | 104 ++ .../amd64/17.1/systemd/selinux/deprecated | 33 + .../systemd/selinux/merged-usr/deprecated | 104 ++ .../default/linux/arm/17.0/armv4/deprecated | 104 ++ .../linux/arm/17.0/armv4/desktop/deprecated | 104 ++ .../arm/17.0/armv4/desktop/gnome/deprecated | 104 ++ .../arm/17.0/armv4/desktop/plasma/deprecated | 104 ++ .../linux/arm/17.0/armv4/developer/deprecated | 104 ++ .../default/linux/arm/17.0/armv4t/deprecated | 104 ++ .../linux/arm/17.0/armv4t/desktop/deprecated | 104 ++ .../arm/17.0/armv4t/desktop/gnome/deprecated | 104 ++ .../arm/17.0/armv4t/desktop/plasma/deprecated | 104 ++ .../arm/17.0/armv4t/developer/deprecated | 104 ++ .../17.0/armv4t/systemd/merged-usr/deprecated | 104 ++ .../default/linux/arm/17.0/armv5te/deprecated | 104 ++ .../linux/arm/17.0/armv5te/desktop/deprecated | 104 ++ .../arm/17.0/armv5te/desktop/gnome/deprecated | 104 ++ .../17.0/armv5te/desktop/plasma/deprecated | 104 ++ .../arm/17.0/armv5te/developer/deprecated | 104 ++ .../armv5te/systemd/merged-usr/deprecated | 104 ++ .../default/linux/arm/17.0/armv6j/deprecated | 104 ++ .../linux/arm/17.0/armv6j/desktop/deprecated | 104 ++ .../arm/17.0/armv6j/desktop/gnome/deprecated | 104 ++ .../arm/17.0/armv6j/desktop/plasma/deprecated | 104 ++ .../arm/17.0/armv6j/developer/deprecated | 104 ++ .../linux/arm/17.0/armv6j/hardened/deprecated | 104 ++ .../17.0/armv6j/hardened/selinux/deprecated | 104 ++ .../linux/arm/17.0/armv6j/selinux/deprecated | 104 ++ .../17.0/armv6j/systemd/merged-usr/deprecated | 104 ++ .../default/linux/arm/17.0/armv7a/deprecated | 104 ++ .../linux/arm/17.0/armv7a/desktop/deprecated | 104 ++ .../arm/17.0/armv7a/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../arm/17.0/armv7a/desktop/plasma/deprecated | 104 ++ .../plasma/systemd/merged-usr/deprecated | 104 ++ .../arm/17.0/armv7a/developer/deprecated | 104 ++ .../linux/arm/17.0/armv7a/hardened/deprecated | 104 ++ .../17.0/armv7a/hardened/selinux/deprecated | 104 ++ .../17.0/armv7a/systemd/merged-usr/deprecated | 104 ++ .../default/linux/arm/17.0/deprecated | 104 ++ .../default/linux/arm/17.0/desktop/deprecated | 104 ++ .../linux/arm/17.0/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../linux/arm/17.0/desktop/plasma/deprecated | 104 ++ .../plasma/systemd/merged-usr/deprecated | 104 ++ .../linux/arm/17.0/developer/deprecated | 104 ++ .../linux/arm/17.0/musl/armv6j/deprecated | 104 ++ .../arm/17.0/musl/armv6j/hardened/deprecated | 104 ++ .../musl/armv6j/hardened/selinux/deprecated | 104 ++ .../linux/arm/17.0/musl/armv7a/deprecated | 104 ++ .../arm/17.0/musl/armv7a/hardened/deprecated | 104 ++ .../musl/armv7a/hardened/selinux/deprecated | 104 ++ ...ckage.use.stable.mask => package.use.mask} | 0 ...ckage.use.stable.mask => package.use.mask} | 0 .../arm/23.0/musl/package.use.stable.mask | 5 + ...ckage.use.stable.mask => package.use.mask} | 0 ...ckage.use.stable.mask => package.use.mask} | 0 .../linux/arm64/17.0/big-endian/deprecated | 104 ++ .../big-endian/systemd/merged-usr/deprecated | 104 ++ .../default/linux/arm64/17.0/deprecated | 104 ++ .../linux/arm64/17.0/desktop/deprecated | 104 ++ .../linux/arm64/17.0/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../arm64/17.0/desktop/plasma/deprecated | 104 ++ .../plasma/systemd/merged-usr/deprecated | 104 ++ .../desktop/systemd/merged-usr/deprecated | 104 ++ .../linux/arm64/17.0/developer/deprecated | 104 ++ .../linux/arm64/17.0/hardened/deprecated | 104 ++ .../arm64/17.0/hardened/selinux/deprecated | 104 ++ .../default/linux/arm64/17.0/llvm/deprecated | 104 ++ .../default/linux/arm64/17.0/musl/deprecated | 104 ++ .../linux/arm64/17.0/musl/hardened/deprecated | 104 ++ .../17.0/musl/hardened/selinux/deprecated | 104 ++ .../linux/arm64/17.0/musl/llvm/deprecated | 104 ++ .../17.0/systemd/llvm/merged-usr/deprecated | 104 ++ .../arm64/17.0/systemd/merged-usr/deprecated | 104 ++ .../systemd/selinux/merged-usr/deprecated | 104 ++ .../default/linux/hppa/17.0/deprecated | 104 ++ .../linux/hppa/17.0/desktop/deprecated | 104 ++ .../linux/hppa/17.0/developer/deprecated | 104 ++ .../hppa/17.0/systemd/merged-usr/deprecated | 104 ++ .../default/linux/ia64/17.0/deprecated | 104 ++ .../linux/ia64/17.0/desktop/deprecated | 104 ++ .../linux/ia64/17.0/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../linux/ia64/17.0/developer/deprecated | 104 ++ .../ia64/17.0/systemd/merged-usr/deprecated | 104 ++ .../loong/22.0/la64v100/lp64d/deprecated | 104 ++ .../22.0/la64v100/lp64d/desktop/deprecated | 104 ++ .../la64v100/lp64d/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../la64v100/lp64d/desktop/plasma/deprecated | 104 ++ .../plasma/systemd/merged-usr/deprecated | 104 ++ .../desktop/systemd/merged-usr/deprecated | 104 ++ .../22.0/la64v100/lp64d/developer/deprecated | 104 ++ .../lp64d/systemd/merged-usr/deprecated | 104 ++ .../default/linux/m68k/17.0/deprecated | 104 ++ .../default/linux/m68k/17.0/musl/deprecated | 104 ++ .../m68k/17.0/systemd/merged-usr/deprecated | 104 ++ .../mips/17.0/mipsel/multilib/n32/deprecated | 104 ++ .../n32/systemd/merged-usr/deprecated | 104 ++ .../mips/17.0/mipsel/multilib/n64/deprecated | 104 ++ .../n64/systemd/merged-usr/deprecated | 104 ++ .../mips/17.0/mipsel/multilib/o32/deprecated | 1 + .../linux/mips/17.0/mipsel/n32/deprecated | 104 ++ .../mipsel/n32/systemd/merged-usr/deprecated | 104 ++ .../linux/mips/17.0/mipsel/n64/deprecated | 104 ++ .../mips/17.0/mipsel/n64/musl/deprecated | 104 ++ .../mipsel/n64/systemd/merged-usr/deprecated | 104 ++ .../linux/mips/17.0/mipsel/o32/deprecated | 104 ++ .../mips/17.0/mipsel/o32/musl/deprecated | 104 ++ .../mipsel/o32/systemd/merged-usr/deprecated | 104 ++ .../linux/mips/17.0/multilib/n32/deprecated | 104 ++ .../n32/systemd/merged-usr/deprecated | 104 ++ .../linux/mips/17.0/multilib/n64/deprecated | 104 ++ .../linux/mips/17.0/multilib/o32/deprecated | 1 + .../default/linux/mips/17.0/n32/deprecated | 104 ++ .../17.0/n32/systemd/merged-usr/deprecated | 104 ++ .../default/linux/mips/17.0/n64/deprecated | 104 ++ .../linux/mips/17.0/n64/musl/deprecated | 104 ++ .../17.0/n64/systemd/merged-usr/deprecated | 104 ++ .../default/linux/mips/17.0/o32/deprecated | 104 ++ .../linux/mips/17.0/o32/musl/deprecated | 104 ++ .../17.0/o32/systemd/merged-usr/deprecated | 104 ++ .../default/linux/mips/17.0/package.use.mask | 6 + .../profiles/default/linux/mips/17.0/use.mask | 7 + .../ppc64/17.0/32bit-userland/deprecated | 104 ++ .../17.0/32bit-userland/desktop/deprecated | 104 ++ .../32bit-userland/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../17.0/32bit-userland/developer/deprecated | 104 ++ .../default/linux/ppc/17.0/deprecated | 104 ++ .../default/linux/ppc/17.0/desktop/deprecated | 104 ++ .../linux/ppc/17.0/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../linux/ppc/17.0/developer/deprecated | 104 ++ .../default/linux/ppc/17.0/musl/deprecated | 104 ++ .../linux/ppc/17.0/musl/hardened/deprecated | 104 ++ .../ppc/17.0/systemd/merged-usr/deprecated | 104 ++ .../linux/ppc/23.0/musl/package.use.mask | 7 +- .../default/linux/ppc64/17.0/deprecated | 104 ++ .../linux/ppc64/17.0/desktop/deprecated | 104 ++ .../linux/ppc64/17.0/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../linux/ppc64/17.0/developer/deprecated | 104 ++ .../default/linux/ppc64/17.0/musl/deprecated | 104 ++ .../linux/ppc64/17.0/musl/hardened/deprecated | 104 ++ .../default/linux/ppc64/17.0/package.mask | 7 + .../ppc64/17.0/systemd/merged-usr/deprecated | 104 ++ .../default/linux/ppc64le/17.0/deprecated | 104 ++ .../linux/ppc64le/17.0/desktop/deprecated | 104 ++ .../ppc64le/17.0/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../ppc64le/17.0/desktop/plasma/deprecated | 104 ++ .../plasma/systemd/merged-usr/deprecated | 104 ++ .../desktop/systemd/merged-usr/deprecated | 104 ++ .../linux/ppc64le/17.0/developer/deprecated | 104 ++ .../ppc64le/17.0/ieee-long-double/deprecated | 104 ++ .../linux/ppc64le/17.0/musl/deprecated | 104 ++ .../ppc64le/17.0/musl/hardened/deprecated | 104 ++ .../17.0/systemd/merged-usr/deprecated | 104 ++ .../linux/riscv/20.0/rv64gc/lp64/deprecated | 104 ++ .../riscv/20.0/rv64gc/lp64/desktop/deprecated | 104 ++ .../20.0/rv64gc/lp64/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../rv64gc/lp64/desktop/plasma/deprecated | 104 ++ .../plasma/systemd/merged-usr/deprecated | 104 ++ .../desktop/systemd/merged-usr/deprecated | 104 ++ .../riscv/20.0/rv64gc/lp64/musl/deprecated | 104 ++ .../rv64gc/lp64/systemd/merged-usr/deprecated | 104 ++ .../linux/riscv/20.0/rv64gc/lp64d/deprecated | 104 ++ .../20.0/rv64gc/lp64d/desktop/deprecated | 104 ++ .../rv64gc/lp64d/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../rv64gc/lp64d/desktop/plasma/deprecated | 104 ++ .../plasma/systemd/merged-usr/deprecated | 104 ++ .../desktop/systemd/merged-usr/deprecated | 104 ++ .../riscv/20.0/rv64gc/lp64d/musl/deprecated | 104 ++ .../lp64d/systemd/merged-usr/deprecated | 104 ++ .../riscv/20.0/rv64gc/multilib/deprecated | 104 ++ .../multilib/systemd/merged-usr/deprecated | 104 ++ .../riscv/23.0/rv64/lp64d/musl/package.mask | 6 + .../rv64/split-usr/lp64d/musl/package.mask | 6 + .../default/linux/s390/17.0/deprecated | 104 ++ .../default/linux/s390/17.0/s390x/deprecated | 104 ++ .../17.0/s390x/systemd/merged-usr/deprecated | 104 ++ .../s390/17.0/systemd/merged-usr/deprecated | 104 ++ .../default/linux/sparc/17.0/64ul/deprecated | 104 ++ .../linux/sparc/17.0/64ul/desktop/deprecated | 104 ++ .../sparc/17.0/64ul/developer/deprecated | 104 ++ .../17.0/64ul/systemd/merged-usr/deprecated | 104 ++ .../default/linux/sparc/17.0/deprecated | 104 ++ .../linux/sparc/17.0/desktop/deprecated | 104 ++ .../linux/sparc/17.0/developer/deprecated | 104 ++ .../sparc/17.0/systemd/merged-usr/deprecated | 104 ++ .../default/linux/x86/17.0/deprecated | 104 ++ .../default/linux/x86/17.0/desktop/deprecated | 104 ++ .../linux/x86/17.0/desktop/gnome/deprecated | 104 ++ .../gnome/systemd/merged-usr/deprecated | 104 ++ .../linux/x86/17.0/desktop/plasma/deprecated | 104 ++ .../plasma/systemd/merged-usr/deprecated | 104 ++ .../linux/x86/17.0/developer/deprecated | 104 ++ .../linux/x86/17.0/hardened/deprecated | 104 ++ .../x86/17.0/hardened/selinux/deprecated | 104 ++ .../default/linux/x86/17.0/musl/deprecated | 104 ++ .../linux/x86/17.0/musl/selinux/deprecated | 104 ++ .../default/linux/x86/17.0/selinux/deprecated | 104 ++ .../x86/17.0/systemd/merged-usr/deprecated | 104 ++ .../linux/x86/23.0/i486/musl/package.use.mask | 11 +- .../23.0/i486/musl/package.use.stable.mask | 6 - .../23.0/i486/split-usr/musl/package.use.mask | 6 +- .../split-usr/musl/package.use.stable.mask | 6 - .../linux/x86/23.0/i686/musl/package.use.mask | 11 +- .../23.0/i686/musl/package.use.stable.mask | 6 - .../23.0/i686/split-usr/musl/package.use.mask | 6 +- .../split-usr/musl/package.use.stable.mask | 6 - .../default/linux/x86/23.0/i686/time64/eapi | 1 + .../linux/x86/23.0/i686/time64/make.defaults | 5 + .../default/linux/x86/23.0/i686/time64/parent | 2 + .../linux/x86/23.0/i686/time64/systemd/eapi | 1 + .../linux/x86/23.0/i686/time64/systemd/parent | 2 + .../profiles/desc/amdgpu_targets.desc | 14 +- .../profiles/desc/curl_quic.desc | 7 + .../profiles/desc/curl_ssl.desc | 3 +- .../profiles/desc/gpsd_protocols.desc | 6 +- .../profiles/desc/nginx_modules_http.desc | 1 + .../profiles/desc/perl_features.desc | 9 + .../profiles/desc/python_single_target.desc | 3 +- .../profiles/desc/python_targets.desc | 3 +- .../profiles/desc/video_cards.desc | 4 +- .../profiles/features/big-endian/package.mask | 10 + .../features/big-endian/package.use.mask | 11 +- .../profiles/features/big-endian/use.mask | 2 +- .../profiles/features/llvm/make.defaults | 3 - .../profiles/features/llvm/package.use.mask | 5 +- .../profiles/features/llvm/use.mask | 6 + .../profiles/features/musl/package.mask | 23 +- .../profiles/features/musl/package.use.force | 5 + .../profiles/features/musl/package.use.mask | 30 + .../kernel-2.6.16+/package.use.mask | 3 +- .../profiles/features/time64/make.defaults | 12 + .../profiles/features/wd40/package.mask | 3 + .../profiles/features/wd40/package.use.mask | 10 +- .../portage-stable/profiles/license_groups | 8 +- .../profiles/package.deprecated | 14 +- .../portage-stable/profiles/package.mask | 1239 +++++++---------- .../profiles/prefix/darwin/macos/package.mask | 4 + .../prefix/sunos/solaris/package.mask | 6 + .../portage-stable/profiles/profiles.desc | 288 ++-- .../profiles/targets/desktop/make.defaults | 4 +- .../targets/desktop/package.use.force | 7 +- .../targets/desktop/plasma/package.use | 22 +- .../portage-stable/profiles/thirdpartymirrors | 1 - .../portage-stable/profiles/updates/2Q-2024 | 7 + .../portage-stable/profiles/use.desc | 1 + 364 files changed, 24869 insertions(+), 1322 deletions(-) create mode 100644 sdk_container/src/third_party/portage-stable/profiles/arch/m68k/package.mask create mode 100644 sdk_container/src/third_party/portage-stable/profiles/arch/mips/mips64/package.use.mask create mode 100644 sdk_container/src/third_party/portage-stable/profiles/arch/x86/i486/package.use.mask create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/clang/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/hardened/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/x32/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/x32/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/clang/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/hardened/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/hardened/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/clang/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/clang/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/selinux/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/hardened/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/hardened/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/plasma/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv6j/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv6j/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv6j/hardened/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv7a/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv7a/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv7a/hardened/selinux/deprecated rename sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/armv6j_hf/musl/{package.use.stable.mask => package.use.mask} (100%) rename sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/armv7a_hf/musl/{package.use.stable.mask => package.use.mask} (100%) rename sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/{package.use.stable.mask => package.use.mask} (100%) rename sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/{package.use.stable.mask => package.use.mask} (100%) create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/big-endian/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/big-endian/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/plasma/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/hardened/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/llvm/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/hardened/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/llvm/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/llvm/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/selinux/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/m68k/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/m68k/17.0/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/m68k/17.0/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n32/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n32/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n64/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n64/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/o32/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n32/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n32/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n64/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n64/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n64/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/o32/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/o32/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/o32/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/n32/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/n32/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/n64/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/o32/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n32/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n32/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n64/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n64/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n64/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/o32/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/o32/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/o32/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/package.use.mask create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/use.mask create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/musl/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/musl/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/package.mask create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/plasma/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/ieee-long-double/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/musl/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/multilib/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/multilib/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/23.0/rv64/lp64d/musl/package.mask create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64d/musl/package.mask create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/s390x/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/s390x/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/gnome/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/gnome/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/plasma/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/plasma/systemd/merged-usr/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/developer/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/hardened/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/hardened/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/musl/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/musl/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/selinux/deprecated create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/systemd/merged-usr/deprecated delete mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/musl/package.use.stable.mask delete mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.stable.mask delete mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/musl/package.use.stable.mask delete mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.stable.mask create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/eapi create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/make.defaults create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/parent create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/systemd/eapi create mode 100644 sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/systemd/parent create mode 100644 sdk_container/src/third_party/portage-stable/profiles/desc/curl_quic.desc create mode 100644 sdk_container/src/third_party/portage-stable/profiles/desc/perl_features.desc create mode 100644 sdk_container/src/third_party/portage-stable/profiles/features/llvm/use.mask diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/alpha/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/alpha/package.use.mask index a3a882bc12..7ac2cf5bbc 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/alpha/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/alpha/package.use.mask @@ -1,6 +1,14 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner (2024-06-29) +# media-libs/libplacebo is not keyworded +media-video/ffmpeg libplacebo + +# Michał Górny (2024-05-08) +# Requires sys-devel/{clang,llvm}:16. +dev-lang/python jit + # matoro (2024-02-29) # sys-apps/xdg-desktop-portal is not keyworded here, #925731 x11-base/xwayland libei @@ -205,7 +213,6 @@ sci-libs/umfpack cholmod media-libs/openal sndio media-video/ffmpeg sndio media-sound/moc sndio -media-sound/mpd sndio media-libs/libsdl2 sndio media-libs/libao sndio @@ -246,7 +253,7 @@ mail-filter/pyzor mysql # Matt Turner (2020-08-11) # No drivers on this architecture support Vulkan -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa video_cards_zink vulkan vulkan-overlay zink # Sergei Trofimovich (2020-07-18) # net-libs/webkit-gtk has no alpha keywords @@ -331,10 +338,6 @@ dev-db/percona-server cjk app-admin/sudo sssd sys-auth/pambase sssd -# Andreas Sturmlechner (2018-09-30) -# Optional dependency blocking security cleanup, bug #627316 -media-sound/mpd wildmidi - # Thomas Deutschmann (2018-06-06) # Needs sys-apps/fakechroot which isn't keyworded app-arch/rpm test @@ -499,10 +502,6 @@ media-video/ffmpeg x265 # Missing keywords, bug #493156 media-libs/libgphoto2 serial -# Pacho Ramos (2013-11-28) -# Missing keywords, bug #492820 -net-im/telepathy-connection-managers sipe - # Pacho Ramos (2013-11-13) # Missing keywords, bug #478254 >=gnome-base/gnome-3.8 classic diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/make.defaults index d6c8326720..9452882147 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/make.defaults +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/make.defaults @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 ARCH="amd64" diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/no-multilib/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/no-multilib/package.mask index 45d113b969..eb5dc6e238 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/no-multilib/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/no-multilib/package.mask @@ -5,10 +5,6 @@ # This code assumes 32-bit longs and must therefore be built as a 32-bit binary. sys-fs/atari-fdisk -# David Seifert (2018-01-03) -# Requires 32-bit multilib compatibility -sys-block/megamgr - # James Le Cuirot (2016-08-13) # Steam requires amd64 multilib. These are steam-overlay packages. dev-util/adobe-air-runtime @@ -27,7 +23,6 @@ app-emulation/crossover-bin app-emulation/q4wine dev-embedded/libftd2xx dev-embedded/openocd -dev-util/android-ndk dev-util/android-sdk-update-manager dev-util/biew games-action/badland diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/package.use.mask index 101301028d..19d1727908 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/package.use.mask @@ -17,9 +17,21 @@ #--- END OF EXAMPLES --- +# Andreas Sturmlechner (2024-06-23) +# Pulls in kde-apps/kgpg is keyworded here +>=kde-apps/kdeutils-meta-24.05.1 -gpg + +# Jared Allard (2024-06-21) +# uasm and jwasm include amd64-specific ASM +app-arch/7zip -uasm -jwasm + +# Andrew Ammerlaan (2024-04-25) +# ROCm and Level-Zero are amd64-only at the moment +sys-apps/hwloc -rocm -l0 + # Paul Zander (2024-04-20) # only keyworded for amd64 currently -media-gfx/blender -gnome +media-gfx/blender -gnome -oneapi -renderdoc -vulkan # Ionen Wolkens (2024-04-16) # dev-qt/qtlanguageserver:6 is keyworded here @@ -75,11 +87,6 @@ sys-kernel/gentoo-kernel-bin -generic-uki # dev-qt/qtwebengine:6 is keyworded here. dev-python/PyQt6 -pdfium -# Leonardo Hernández Hernández (2023-11-25) -# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff) -# are only available for amd64, arm64 and riscv ->=gui-libs/wlroots-0.17.0 -drm -liftoff - # Jimi Huotari (2023-11-22) # Unmask on amd64. media-video/obs-studio -qsv -websocket @@ -131,6 +138,7 @@ www-servers/apache -apache2_modules_tls # Andrew Ammerlaan (2023-04-22) # snap only works on amd64 +gnome-extra/gnome-software -snap kde-plasma/discover -snap # Sam James (2023-04-17) @@ -142,10 +150,6 @@ dev-lang/ruby -jit # pytables is available here. dev-python/tables -cpudetection -# Craig Andrews (2023-03-09) -# media-libs/libplacebo is keyworded here -media-video/ffmpeg -libplacebo - # Yiyang Wu (2023-01-27) # AMDGPU enablement depends on dev-libs/rocr-runtime, ~amd64 only # See also: https://bugs.gentoo.org/891499 @@ -168,7 +172,6 @@ net-misc/curl -rustls -curl_ssl_rustls # Quick Sync Video (through intel-mediasdk or libvpl) is # only keyworded on amd64 media-video/ffmpeg -qsv -media-libs/gst-plugins-bad -qsv # WANG Xuerui (2022-10-07) # sys-libs/libsmbios is available here. @@ -246,6 +249,7 @@ sys-libs/compiler-rt-sanitizers -asan -dfsan -lsan -msan -hwasan -tsan sys-libs/compiler-rt-sanitizers -ubsan -safestack -cfi -scudo sys-libs/compiler-rt-sanitizers -gwp-asan sys-libs/compiler-rt-sanitizers -libfuzzer -memprof -orc -profile -xray +sys-libs/compiler-rt-sanitizers -ctx-profile # Sam James (2020-10-24) # asm redc is only available on amd64, @@ -325,10 +329,6 @@ dev-java/openjdk:11 -javafx # build on amd64. >=dev-lang/spidermonkey-60 -jit -# Andreas Sturmlechner (2019-05-09) -# media-libs/libplacebo is keyworded on amd64 -media-video/vlc -libplacebo - # Denis Lisov (2019-05-09) # Overlay can only be built on amd64 and x86 x11-apps/igt-gpu-tools -overlay diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/package.use.stable.mask index 6309d1e2f7..5be319fb39 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/package.use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/package.use.stable.mask @@ -17,11 +17,6 @@ #--- END OF EXAMPLES --- -# Ionen Wolkens (2024-04-16) -# Temporary mask to give a little bit of time before stabilizing -# the just added dev-qt/qtlanguageserver-6.7.0 for amd64 -dev-qt/qtdeclarative:6 qmlls - # Andrew Ammerlaan (2024-03-17) # Experimental, virt-firmware is keyworded only unstable sys-kernel/installkernel efistub @@ -75,7 +70,6 @@ net-misc/curl rustls curl_ssl_rustls # Sam James (2022-12-07) # Needs unstable media-libs/libvpl -media-libs/gst-plugins-bad qsv media-video/ffmpeg qsv # Adel Kara Slimane (2022-03-14) diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/x32/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/x32/package.mask index 0f64711a55..864b43d5f5 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/x32/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/x32/package.mask @@ -1,6 +1,11 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Ben Kohler (2024-05-27) +# Requires libpcre2[jit] which is now masked on x32 +mail-filter/rspamd +net-analyzer/ossec-hids + # James Le Cuirot (2024-02-17) # Requires net-libs/nodejs which is unavailable on amd64/x32. net-misc/sunshine @@ -33,6 +38,7 @@ sci-geosciences/viking # Jupyterlab and friends require net-libs/nodejs dev-python/jupyterlab dev-python/jupyterlab-lsp +dev-python/jupyterlab-widgets dev-python/jupyter-server-proxy sci-misc/jupyterlab-desktop-bin dev-python/plotly @@ -113,8 +119,6 @@ kde-apps/konqueror kde-apps/konsolekalendar kde-apps/kontact kde-apps/korganizer -kde-apps/ktp-accounts-kcm -kde-apps/ktp-text-ui kde-apps/libksieve kde-apps/mailcommon kde-apps/messagelib @@ -122,20 +126,18 @@ kde-apps/mbox-importer kde-apps/parley kde-apps/pim-data-exporter kde-apps/pim-sieve-editor -kde-apps/plasma-telepathy-meta:5 kde-misc/kio-gdrive kde-misc/tellico kde-misc/zanshin media-gfx/digikam media-gfx/luminance-hdr +>=media-gfx/skanpage-24.04.90 media-sound/frescobaldi media-sound/teamspeak-client:3 -media-video/openshot media-video/vidify media-video/vidify-audiosync net-analyzer/nmapsi >=net-im/neochat-24.02.0 ->=net-im/tokodon-24.02.0 net-im/whatsie net-libs/signon-ui sci-geosciences/qmapshack diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/x32/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/x32/package.use.mask index b6cc1e0d85..79de1712fa 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/x32/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/amd64/x32/package.use.mask @@ -1,6 +1,14 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Ben Kohler (2024-05-27) +# Runtime issues (bug #925115) and build issues (bug #931092) +dev-libs/libpcre2 jit +dev-lang/php jit +mail-filter/rspamd jit +net-proxy/haproxy pcre-jit +www-servers/varnish jit + # Andreas Sturmlechner (2024-03-24) # Requires unkeyworded dev-qt/qtwebengine net-p2p/ktorrent rss @@ -16,7 +24,7 @@ dev-python/iminuit test dev-python/nbdime test dev-python/nbclient test dev-python/nbconvert test -dev-python/qiskit-terra visualization +dev-python/qiskit visualization sci-mathematics/cadabra jupyter sci-mathematics/yacas jupyter sci-physics/hepmc root @@ -85,6 +93,6 @@ www-apps/xpra-html5 minify dev-python/QtPy test # Davide Pesavento (2011-11-30) -# The QML (V4) and JSC JITs do not work on x32. +# The QML (V4) and JSC JITs do not work on x32 (bug #932192). dev-qt/qtdeclarative jit dev-qt/qtscript jit diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/23.0-armv7a_hf/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/23.0-armv7a_hf/package.mask index 30e86d72cc..6ce998c440 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/23.0-armv7a_hf/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/23.0-armv7a_hf/package.mask @@ -5,10 +5,6 @@ # Valgrind works on ARMv7 -dev-debug/valgrind -# James Le Cuirot (2015-05-24) -# This is built for armv7a so unmask against the wider arm mask. --dev-java/icedtea-bin - # Georgy Yakovlev (2019-06-22) # This is built for armv7a so unmask here. -dev-java/openjdk-bin:11 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/23.0-armv7a_sf/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/23.0-armv7a_sf/package.mask index 30e86d72cc..6ce998c440 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/23.0-armv7a_sf/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/23.0-armv7a_sf/package.mask @@ -5,10 +5,6 @@ # Valgrind works on ARMv7 -dev-debug/valgrind -# James Le Cuirot (2015-05-24) -# This is built for armv7a so unmask against the wider arm mask. --dev-java/icedtea-bin - # Georgy Yakovlev (2019-06-22) # This is built for armv7a so unmask here. -dev-java/openjdk-bin:11 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/armv7a/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/armv7a/package.mask index 30e86d72cc..6ce998c440 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/armv7a/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/armv7a/package.mask @@ -5,10 +5,6 @@ # Valgrind works on ARMv7 -dev-debug/valgrind -# James Le Cuirot (2015-05-24) -# This is built for armv7a so unmask against the wider arm mask. --dev-java/icedtea-bin - # Georgy Yakovlev (2019-06-22) # This is built for armv7a so unmask here. -dev-java/openjdk-bin:11 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/make.defaults index 4527d2144a..49365fcaee 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/make.defaults +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/make.defaults @@ -1,4 +1,4 @@ -# Copyright 2008-2023 Gentoo Authors +# Copyright 2008-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # Main ARM profile @@ -25,3 +25,7 @@ VIDEO_CARDS="exynos fbdev omap" # Michał Górny (2017-03-14) # Unhide the ARM-specific USE_EXPANDs. USE_EXPAND_HIDDEN="-CPU_FLAGS_ARM" + +# Hans de Graaff (2024-05-20) +# Allow ruby32 stabling: https://bugs.gentoo.org/932285 +RUBY_TARGETS="ruby31 -ruby32" diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.mask index 17e581e17f..84f43bbcff 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.mask @@ -10,10 +10,6 @@ # https://valgrind.org/info/platforms.html dev-debug/valgrind -# James Le Cuirot (2015-05-24) -# This is built for armv7a and will not work on earlier generations. -dev-java/icedtea-bin - # Georgy Yakovlev (2019-06-22) # This is built for armv7a and will not work on earlier generations. dev-java/openjdk-bin:11 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.use.mask index 1a7446c4fe..03ec1adc1a 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.use.mask @@ -1,6 +1,15 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +app-crypt/pinentry qt6 +app-office/libreoffice qt6 + +# Andrew Ammerlaan (2024-06-01) +# qtnetworkauth not yet keyworded here +dev-python/pyside6 network-auth + # Andrew Ammerlaan (2024-03-21) # virt-firmware is keyworded here sys-kernel/installkernel -efistub @@ -74,11 +83,7 @@ dev-lang/idris2 test-full dev-python/cloudscraper test dev-python/QtPy test games-util/lgogdownloader gui -kde-apps/kde-apps-meta pim -kde-apps/kdenetwork-meta bittorrent -kde-apps/kleopatra pim -kde-apps/umbrello php -kde-misc/kio-gdrive share +kde-plasma/plasma-nm openconnect net-irc/quassel urlpreview net-misc/fatrat bittorrent net-misc/seafile-client shibboleth @@ -114,10 +119,6 @@ app-text/enchant nuspell # Untested useflag on other arches, needs keywording media-video/ffmpeg vmaf -# Andreas Sturmlechner (2022-03-13) -# Not yet keyworded. Bug #835037 -kde-frameworks/kfilemetadata mobi - # Sam James (2022-03-10) # Boost has support for ARM32 # https://www.boost.org/doc/libs/1_78_0/libs/context/doc/html/context/architectures.html @@ -259,10 +260,6 @@ dev-ruby/capybara test # pre-built, no ARM support net-wireless/gr-osmosdr sdrplay -# Andreas Sturmlechner (2018-06-03) -# net-wireless/soapysdr not keyworded -net-wireless/gr-osmosdr soapy - # Markus Meier (2018-05-30) # unkeyworded deps for bug #621434 net-analyzer/zmap mongo @@ -279,19 +276,11 @@ net-libs/gnutls test-full # Moved from use.mask since they are flags local to one package. media-tv/tvheadend hdhomerun -# Patrice Clement (2017-09-24) -# Unmask Raspberry Pi support on arm. -media-video/mpv -raspberry-pi - # James Le Cuirot (2017-09-20) # media-sound/mac's executable segfaults when compressing all but the # smallest wav files. media-sound/xmms2 mac -# Michał Górny (2017-08-10) -# Requires USE=ipmi which is masked in this profile. -sys-power/nut ups_drivers_nut-ipmipsu - # Michał Górny (2017-08-08) # Requires USE=opencl that is masked in this profile. net-misc/bfgminer adl lm-sensors @@ -368,7 +357,6 @@ net-print/hplip -scanner kde # MMAL is available on the Raspberry Pi (armv6 & armv7 so far) media-video/ffmpeg -mmal media-video/ffmpeg-chromium -mmal -media-video/mpv -mmal # Alexis Ballier (2015-04-02) # Needs ilmbase (openexr), which does not build and is masked on arm. @@ -433,10 +421,6 @@ app-emulation/xen-tools doc # Unkeyworded deps, bug #488724 app-office/gnumeric libgda -# Pacho Ramos (2013-11-28) -# Missing keywords, bug #492820 -net-im/telepathy-connection-managers sipe - # Pacho Ramos (2013-10-31) # Missing keywords, bug #478254 gnome-base/gnome classic extras diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.use.stable.mask index 674e85444f..a6edf3ad99 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/package.use.stable.mask @@ -1,6 +1,10 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner (2024-06-29) +# media-libs/libplacebo is not stable here +media-video/ffmpeg libplacebo + # Andrew Ammerlaan (2024-03-21) # Experimental, virt-firmware is keyworded only unstable sys-kernel/installkernel efistub @@ -171,10 +175,6 @@ dev-db/mariadb jdbc # RPI support on arm dev-libs/libcec -raspberry-pi -# Ilya Tumaykin (2016-04-13) -# Requires special hardware to test and stabilize properly. -media-video/mpv raspberry-pi - # Brian Evans (2016-01-08) # net-misc/libteam is not yet stable on arm net-misc/networkmanager teamd diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/use.mask index f5ae9cb048..53b35994e0 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/use.mask @@ -1,12 +1,17 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # Unmask the flag which corresponds to ARCH. -arm +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +kf6compat + # Andreas Sturmlechner (2023-02-06) # Successful build of dev-qt/qtwebengine depends on 64-bit host # Bug #893234 +pdfium webengine # matoro (2022-09-29) diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/use.stable.mask index 77c107fbe7..067c0d6c42 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm/use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm/use.stable.mask @@ -4,9 +4,9 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in use.mask -# Ionen Wolkens (2024-01-27) -# Qt6 is not stable here yet -qt6 +# Hans de Graaff (2024-05-20) +# Allow ruby32 stabling: https://bugs.gentoo.org/932285 +ruby_targets_ruby32 # Sam James (2022-01-16) # net-libs/gnome-online-accounts is not marked stable on arm yet diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/make.defaults index fd42ca3f2c..55118834bc 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/make.defaults +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/make.defaults @@ -1,4 +1,4 @@ -# Copyright 2014-2023 Gentoo Authors +# Copyright 2014-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # Main ARM64 (AArch64/ARMv8) profile; endian independent. diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/package.use.mask index a95fa3ba22..d83b2e0051 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/package.use.mask @@ -1,6 +1,23 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner (2024-06-23) +# Pulls in kde-apps/kgpg is keyworded here +>=kde-apps/kdeutils-meta-24.05.1 -gpg + +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +app-crypt/pinentry qt6 +app-office/libreoffice qt6 + +# Ionen Wolkens (2024-05-19) +# jit is supported here +>=dev-qt/qtdeclarative-6 -jit + +# Matt Turner (2024-05-09) +# Unmask for keywording bug #931634 +x11-libs/libdrm -video_cards_vmware + # Paul Zander (2024-04-12) # Supports 64-bit NEON media-libs/opencv -cpu_flags_arm_neon @@ -13,11 +30,6 @@ media-libs/openpgl -cpu_flags_arm_neon # virt-firmware is keyworded here sys-kernel/installkernel -efistub -# Mart Raudsepp (2024-03-03) -# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff) -# are only available for amd64, arm64 and riscv ->=gui-libs/wlroots-0.17.0 -drm -liftoff - # Joonas Niilola (2024-02-16) # Test dependencies not keyworded on this arch. www-servers/nginx test @@ -470,10 +482,6 @@ app-text/evince dvi nautilus postscript xps # Unkeyworded deps, bug #488724 app-office/gnumeric libgda -# Pacho Ramos (2013-11-28) -# Missing keywords, bug #492820 -net-im/telepathy-connection-managers sipe - # Sergey Popov (2013-09-06) # sci-libs/hdf does not build properly on arm dev-perl/PDL hdf diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/package.use.stable.mask index 459cf22196..75d33815b7 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/package.use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/package.use.stable.mask @@ -1,15 +1,18 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Eray Aslan (2024-06-17) +# mongodb needed for tests which is not stable keyworded for arm64 +dev-libs/mongo-c-driver test + +# Sam Jamrs (2024-06-07) +# dev-libs/capstone hasn't been stabilized yet +app-emulation/qemu capstone + # Andrew Ammerlaan (2024-03-21) # Experimental, virt-firmware is keyworded only unstable sys-kernel/installkernel efistub -# Mart Raudsepp (2024-03-03) -# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff) -# are not stable yet on arm64 ->=gui-libs/wlroots-0.17.0 drm liftoff - # Ionen Wolkens (2024-01-27) # dev-python/PyQt6 and dev-python/pyside6 are not stable here yet dev-python/QtPy pyqt6 pyside6 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/use.mask index 4211f21cb5..7a6b867544 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/use.mask @@ -1,9 +1,13 @@ -# 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. -arm64 +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +kf6compat + # Paul Zander (2024-03-28) # dev-libs/optix works on arm64 -optix @@ -121,30 +125,26 @@ anthy snapcast # Unmask ARM-only video-cards +-video_cards_amdgpu +-video_cards_d3d12 -video_cards_exynos -video_cards_freedreno -video_cards_lima -video_cards_nouveau -video_cards_panfrost +-video_cards_radeon +-video_cards_radeonsi -video_cards_tegra -video_cards_v3d -video_cards_vc4 --video_cards_amdgpu --video_cards_radeon --video_cards_radeonsi - -# James Le Cuirot -# Unmask as Vivante is available for arm. -video_cards_vivante +-video_cards_vmware # Donnie Berkholz (2006-02-05) # Modular X: mask for architectures on which they aren't available video_cards_mga -video_cards_r128 - -# Matt Turner -# Mask more VIDEO_CARDs added with mesa-8.0 video_cards_r100 +video_cards_r128 video_cards_r200 video_cards_r300 video_cards_r600 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/use.stable.mask index fd6426126d..18cd219279 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/arm64/use.stable.mask @@ -4,6 +4,14 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in use.mask +# Matt Turner (2024-05-10) +# x11-drivers/xf86-video-vmware is not stable yet +video_cards_vmware + +# Matt Turner (2024-05-10) +# dev-util/directx-headers is not stable yet +video_cards_d3d12 + # Mart Raudsepp (2023-10-03) # dev-util/sysprof-capture and dev-util/sysprof are not stable yet sysprof diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/base/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/base/package.use.mask index d0a0ec7455..6dee4d2466 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/base/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/base/package.use.mask @@ -1,9 +1,23 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner (2024-06-23) +# Pulls in kde-apps/kgpg which requires kde-apps/akonadi, which is as +# part of the KDE PIM stack (big, requiring QtWebengine) only keyworded +# on amd64 and arm64. +>=kde-apps/kdeutils-meta-24.05.1 gpg + +# Jared Allard (2024-06-21) +# uasm and jwasm include amd64-specific ASM +app-arch/7zip uasm jwasm + +# Andrew Ammerlaan (2024-04-25) +# ROCm and Level-Zero are amd64-only at the moment +sys-apps/hwloc rocm l0 + # Paul Zander (2024-04-20) # only keyworded for amd64 currently -media-gfx/blender gnome +media-gfx/blender gnome oneapi renderdoc vulkan # Ionen Wolkens (2024-04-16) # dev-qt/qtlanguageserver:6 currently has very few keywords @@ -55,11 +69,6 @@ sys-kernel/gentoo-kernel-bin generic-uki # Needs dev-qt/qtwebengine:6 which has very few keywords. dev-python/PyQt6 pdfium -# Leonardo Hernández Hernández (2023-11-25) -# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff) -# are only available for amd64, arm64 and riscv ->=gui-libs/wlroots-0.17.0 drm liftoff - # Jimi Huotari (2023-11-22) # media-libs/libvpl is only keyworded for amd64 at this time. media-video/obs-studio qsv @@ -103,6 +112,7 @@ www-servers/apache apache2_modules_tls # Andrew Ammerlaan (2023-04-22) # snap only works on amd64 +gnome-extra/gnome-software snap kde-plasma/discover snap # Sam James (2023-04-03) @@ -110,10 +120,6 @@ kde-plasma/discover snap # See bug #894078. dev-python/tables cpudetection -# Andreas Sturmlechner (2023-03-09) -# media-libs/libplacebo is not keyworded anywhere except amd64/ppc64/x86 yet -media-video/ffmpeg libplacebo - # Michał Górny (2023-01-24) # libomptarget is only supported on 64-bit architectures. >=sys-libs/libomp-16.0.0_pre20230124 offload @@ -131,7 +137,6 @@ net-misc/curl rustls curl_ssl_rustls # Quick Sync Video (through intel-mediasdk or oneVPL) is # only keyworded on amd64 media-video/ffmpeg qsv -media-libs/gst-plugins-bad qsv # Georgy Yakovlev (2022-12-01) # Only supported on ppc64le. @@ -231,6 +236,7 @@ sys-libs/compiler-rt-sanitizers asan dfsan lsan msan hwasan tsan sys-libs/compiler-rt-sanitizers ubsan safestack cfi scudo sys-libs/compiler-rt-sanitizers shadowcallstack gwp-asan sys-libs/compiler-rt-sanitizers libfuzzer memprof orc profile xray +sys-libs/compiler-rt-sanitizers ctx-profile # Sam James (2020-10-24) # asm redc is only available on amd64, @@ -304,10 +310,6 @@ dev-java/openjdk:11 javafx # dev-lang/spidermonkey:60[jit] fails to build on most platforms >=dev-lang/spidermonkey-60 jit -# Andreas Sturmlechner (2019-05-09) -# media-libs/libplacebo is not keyworded anywhere except amd64/ppc64/x86 yet -media-video/vlc libplacebo - # Denis Lisov (2019-05-09) # Overlay can only be built on amd64 and x86 x11-apps/igt-gpu-tools overlay @@ -384,19 +386,12 @@ dev-db/mariadb jdbc # This flag only has meaning on amd64 sys-boot/grub:2 grub_platforms_xen-32 -# Ian Delaney (2016-04-06) -# on behalf of Ilya Tumaykin -# Raspberry Pi support is only available on arm. -# Mask raspberry-pi USE globally, unmask on arm. -media-video/mpv raspberry-pi - # Alexis Ballier (2015-11-14) # MMAL is only available on the Raspberry Pi: # Mask it globally, unmask it on arm. media-video/motion mmal media-video/ffmpeg mmal media-video/ffmpeg-chromium mmal -media-video/mpv mmal # Brian Evans (2015-09-14) # Mask new USE flags for mariadb which all arches do not yet have dependencies diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/make.defaults index 9d9c0c818b..a279a075b2 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/make.defaults +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/make.defaults @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 ARCH="hppa" @@ -22,3 +22,7 @@ CHOST_hppa="${CHOST}" # Donnie Berkholz (2006-08-18) # Defaults for video drivers VIDEO_CARDS="fbdev" + +# Hans de Graaff (2024-05-20) +# Allow ruby32 stabling: https://bugs.gentoo.org/932285 +RUBY_TARGETS="ruby31 -ruby32" diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/package.use.mask index 045ee43a97..54c9a841a6 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/package.use.mask @@ -4,6 +4,24 @@ # NOTE: When masking a USE flag due to missing keywords, please file a keyword # request bug for the hppa arch. +# Sam James (2024-06-19) +# The systemd implementation of installkernel doesn't currently support +# updating the 'initramfs.img' and 'vmlinuz' symlinks that palo needs, +# and palo is the only bootloader for HPPA. +sys-kernel/installkernel systemd + +# Holger Hoffstätte (2024-05-19) +# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 +media-gfx/graphicsmagick jpeg2k + +# Arthur Zamarin (2024-05-13) +# Requires dev-util/shelltestrunner +app-arch/mt-st test + +# Michał Górny (2024-05-08) +# Requires sys-devel/{clang,llvm}:16. +dev-lang/python jit + # Ionen Wolkens (2024-01-23) # Needs dev-qt/qtquick3d:6 which itself needs media-libs/assimp that # is not keyworded here and currently fails tests (bug #919896). @@ -58,10 +76,6 @@ dev-build/cmake gui # x11-libs/gtksourceview:4 not keyworded here media-gfx/inkscape sourceview -# Rich Freeman (2023-09-13) -# Tests require shellcheck which is not currently available on hppa -sys-process/systemd-cron test - # Matt Turner (2023-05-30) # sys-apps/dbus-broker is not keyworded app-accessibility/at-spi2-core dbus-broker @@ -242,7 +256,7 @@ dev-libs/efl avif lua_single_target_luajit physics # Matt Turner (2020-08-11) # No drivers on this architecture support Vulkan -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa video_cards_zink vulkan vulkan-overlay zink # Robin H. Johnson (2020-07-02) # Mask io-uring & zbc pending keywording diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/use.stable.mask index d9780b80ad..cbac15e9d0 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/hppa/use.stable.mask @@ -4,6 +4,10 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in use.mask +# Hans de Graaff (2024-05-20) +# Allow ruby32 stabling: https://bugs.gentoo.org/932285 +ruby_targets_ruby32 + # Ionen Wolkens (2024-01-27) # Qt6 is not stable here yet qt6 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/ia64/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/ia64/package.use.mask index 9f34c46e0b..5a441ff877 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/ia64/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/ia64/package.use.mask @@ -1,6 +1,26 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner (2024-06-29) +# media-libs/libplacebo is not keyworded +media-video/ffmpeg libplacebo + +# Thomas Bettler (2024-06-10) +# requires dev-libs/apache-arrow which is net yet keyworded +sci-libs/gdal parquet + +# Sam James (2024-05-19) +# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 +media-gfx/graphicsmagick jpeg2k + +# Arthur Zamarin (2024-05-13) +# Requires dev-util/shelltestrunner +app-arch/mt-st test + +# Michał Górny (2024-05-08) +# Requires sys-devel/{clang,llvm}:16. +dev-lang/python jit + # Robin H. Johnson (2023-09-13) -# Tests require shellcheck which is not currently available -sys-process/systemd-cron test - # Jon Janzen (2023-09-11) # librttopo has not been tested on this arch dev-db/spatialite rttopo @@ -223,7 +239,7 @@ net-analyzer/wireshark gui ilbc # Matt Turner (2020-08-11) # No drivers on this architecture support Vulkan -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa video_cards_zink vulkan vulkan-overlay zink # Michał Górny (2020-06-14) # Requires dev-python/networkx. @@ -487,10 +503,6 @@ gnome-base/gnome classic extras # Missing keywords, bug #493156 media-libs/libgphoto2 serial -# Pacho Ramos (2013-11-28) -# Missing keywords, bug #492820 -net-im/telepathy-connection-managers sipe - # Pacho Ramos (2013-07-20) # Keywords pending, bug #476710 >=gnome-base/gnome-extra-apps-3.8 games diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/loong/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/loong/package.mask index 398aed52ab..8e24d8cdb1 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/loong/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/loong/package.mask @@ -1,11 +1,6 @@ # Copyright 2022-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -# Ionen Wolkens (@024-03-07) -# This version fails to build here due to the used crates, and -# will wait for next bump rather than try to fix it (bug #926407) -~dev-util/maturin-1.5.0 - # WANG Xuerui (2023-09-10) # Has correctness issues on loong (failing test_encode_long_neg_conversion), # pending debug. diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/loong/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/loong/package.use.mask index b9f0e6aa37..64a71be316 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/loong/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/loong/package.use.mask @@ -1,11 +1,24 @@ # Copyright 2022-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -# WANG Xuerui (2024-04-04) -# dev-qt/qtwebengine is not available on loong (no upstream Chromium support, -# patchset not integrated yet) ->=kde-apps/kdecore-meta-24 handbook -kde-plasma/plasma-meta:6 handbook +# Andreas Sturmlechner (2024-06-15) +# Requires unkeyworded dev-qt/qtwebengine (and revdeps) +kde-plasma/plasma-nm openconnect + +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +app-crypt/pinentry qt6 +app-office/libreoffice qt6 + +# WANG Xuerui (2024-06-03) +# Requires arch-specific code in python (relocs handling), in addition to +# sys-devel/{clang,llvm}. +dev-lang/python jit + +# WANG Xuerui (2024-05-16) +# dev-ruby/asciidoctor has some really heavy deps, and is not keyworded on +# loong yet. +net-misc/chrony html # Sam James (2024-03-27) # No rust-bin available for profiler @@ -81,6 +94,7 @@ dev-python/requests-cache test # Andrew Ammerlaan (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 (2023-07-26) # no llvm:15 or lld:16 on loong @@ -143,11 +157,6 @@ sys-kernel/installkernel -systemd-boot -ukify -uki # dev-python/pyopengl fails tests dev-python/sympy opengl -# WANG Xuerui (2023-04-16) -# dev-python/aesara doesn't work on loong yet (due to hardcoding -m64 in its -# cc invocations) -dev-python/sympy aesara - # WANG Xuerui (2022-12-06) # dev-cpp/glog fails tests, needs checking media-libs/opencv glog contribsfm diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/loong/use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/loong/use.mask index e0e50583c2..697686ae9a 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/loong/use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/loong/use.mask @@ -1,6 +1,10 @@ # Copyright 2022-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +kf6compat + # Michał Górny (2024-02-05) # LLVM slots without keywords. llvm_slot_15 @@ -39,6 +43,7 @@ nas # WANG Xuerui (2022-11-01) # qtwebengine isn't available on loong yet +pdfium webengine # Unmask the flag which corresponds to ARCH. diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/m68k/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/m68k/package.mask new file mode 100644 index 0000000000..c9a806f675 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/m68k/package.mask @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Andreas K. Hüttel +# Requires 32bit alignment, so we mask it for the moment +dev-lang/python:3.13 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/m68k/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/m68k/package.use.mask index 9be2feccdf..5dcd046b96 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/m68k/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/m68k/package.use.mask @@ -1,6 +1,10 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Michał Górny (2024-05-08) +# Requires sys-devel/{clang,llvm}:16. +dev-lang/python jit + # James Le Cuirot (2023-12-12) # USE=bpf depends on sys-devel/clang which is not keyworded on m68k media-libs/libv4l bpf diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/m68k/use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/m68k/use.mask index 25d4d1977e..120f9403a7 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/m68k/use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/m68k/use.mask @@ -157,3 +157,7 @@ slang tcl tk xemacs + +# Andreas K. Hüttel +# Requires 32bit alignment, so we mask it for the moment +python_targets_python3_13 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/mips/mips64/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/mips/mips64/package.use.mask new file mode 100644 index 0000000000..c06ddc3a2a --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/mips/mips64/package.use.mask @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# matoro (2024-05-01) +# Sanitizers supported on 64-bit mips only, #779742 +sys-libs/compiler-rt-sanitizers -dfsan -lsan -msan -tsan -cfi diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/mips/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/mips/package.use.mask index d13f419ced..54c538bbcc 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/mips/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/mips/package.use.mask @@ -1,6 +1,32 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Arthur Zamarin (2024-07-01) +# simplify the dep tree +dev-python/click doc +dev-python/cython doc +dev-python/flake8 doc +dev-python/flask doc +dev-python/flit doc +dev-python/greenlet doc +dev-python/outcome doc +dev-python/pytest-cov doc +dev-python/pytest-trio doc +dev-python/stevedore doc +dev-python/sphinx-autodoc-typehints test + +# Andreas Sturmlechner (2024-06-29) +# media-libs/libplacebo is not keyworded +media-video/ffmpeg libplacebo + +# Michał Górny (2024-05-08) +# Requires sys-devel/{clang,llvm}:16. +dev-lang/python jit + +# matoro (2024-05-01) +# Sanitizers supported on both 32-bit and 64-bit mips, #779742 +sys-libs/compiler-rt-sanitizers -asan -profile -ubsan -safestack -scudo -xray + # matoro (2024-03-21) # Test suite is very fragile and doesn't even run on amd64. # No real point in running it here right now, bug #804115. @@ -99,10 +125,6 @@ net-dns/ddclient test dev-lang/gnat-gpl -fixed-point sys-devel/gcc -fixed-point -# matoro (2022-09-14) -# Not broken, but better wait on profiles: bug #515694 -dev-lang/rust system-llvm - # Matt Turner (2022-04-18) # app-text/nuspell is not keyworded app-text/enchant nuspell @@ -139,14 +161,6 @@ dev-libs/libgudev test # dev-python/django is not keyworded here dev-python/diskcache test -# Joshua Kinard (2021-05-20) -# mask USE 'test' on MIPS for setuptools and jaraco-path due to -# the very deep dependency chain that is enabled. Will unmask -# on a future date. -# Bug #774216 -dev-python/jaraco-path test -dev-python/setuptools test - # Sam James (2021-02-06) # media-sound/sndio is not yet keyworded here # bug #769098, bug #769122 @@ -265,9 +279,6 @@ media-video/mplayer ladspa # app-xemacs/ruby-modes is not keyworded on this arch dev-lang/ruby xemacs -# deps missing keywords -games-strategy/freeciv auth - # Mart Raudsepp (2010-09-27) # Extra functionality that has external unkeyworded dependencies # and is not tested yet diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/mips/use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/mips/use.mask index e253698571..a92babc251 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/mips/use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/mips/use.mask @@ -240,11 +240,6 @@ rpm # We don't have net-libs/libsmi keyworded smi -# Matt Turner (2010-12-13) -# We don't have sys-devel/llvm -llvm -llvm-libunwind - # Matt Turner (2011-06-14) # pdfannotextractor needs java pdfannotextractor diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/package.use.mask index ab34fd9573..5d7ca61a7c 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/package.use.mask @@ -1,6 +1,14 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Thomas Bettler (2024-06-10) +# requires dev-libs/apache-arrow which is net yet keyworded +sci-libs/gdal parquet + +# Arthur Zamarin (2024-05-13) +# Requires dev-util/shelltestrunner +app-arch/mt-st test + # Ionen Wolkens (2024-03-31) # MPV currently[1] has no plans to support >=lua5-3 making luajit # the only choice for maintained lua. Apply mask/force to override @@ -13,6 +21,7 @@ media-video/mpv -lua_single_target_lua5-1 lua_single_target_luajit # Andreas Sturmlechner (2024-03-24) # Requires unkeyworded dev-qt/qtwebengine (and revdeps) kde-apps/kleopatra pim +kde-plasma/plasma-nm openconnect net-irc/quassel urlpreview net-p2p/ktorrent rss @@ -72,6 +81,7 @@ dev-db/spatialite rttopo # Andrew Ammerlaan (2023-08-30) # Avoid keywordming more Qt stuff dev-python/pyside2 3d datavis scxml +dev-python/pyside6 3d scxml # Andrew Ammerlaan (2023-03-07) # nbval/nbclassic docs require pandoc which is not keyworded here yet @@ -178,10 +188,6 @@ www-client/chromium widevine # requires media-libs/sdl2-image, which is not yet keyworded app-emulation/qemu sdl-image -# Georgy Yakovlev (2020-01-25) -# requires fwupd, which is not yet keyworded -kde-plasma/discover firmware - # Rick Farina (2020-01-03) # ubertooth needs net-libs/libbtbb and net-wireless/ubertooth which aren't keyworded net-wireless/kismet ubertooth @@ -266,10 +272,6 @@ app-i18n/fcitx-libpinyin dictionary-manager # Requires java app-forensics/sleuthkit java -# Michał Górny (2017-08-10) -# Requires USE=ipmi which is masked in this profile. -sys-power/nut ups_drivers_nut-ipmipsu - # Michał Górny (2017-08-08) # Requires USE=opencl that is masked in this profile. net-misc/bfgminer adl lm-sensors @@ -347,10 +349,6 @@ media-libs/opencv vtk # Missing keywords, bug #495250 >=gnome-base/gnome-extra-apps-3.10 tracker -# Pacho Ramos (2013-11-28) -# Missing keywords, bug #492820 -net-im/telepathy-connection-managers sipe - # Pacho Ramos (2013-10-31) # Missing keywords, bug #478254 gnome-base/gnome classic extras diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/package.use.stable.mask index b7d60aceea..5d6791cd8c 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/package.use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/package.use.stable.mask @@ -17,6 +17,11 @@ #--- END OF EXAMPLES --- +# Joonas Niilola (2024-05-28) +# Depchain-destabilization on ppc (libsecret[test-rust] -> gjs -> spidermonkey) +app-crypt/libsecret test-rust +dev-util/glade gjs + # Mart Raudsepp (2023-12-25) # Libei not stable here yet x11-base/xwayland libei @@ -40,7 +45,7 @@ media-sound/jack2 ieee1394 # Sam James (2020-07-30) # vulkan-loader and glslang are not yet stable on ppc -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa video_cards_zink vulkan vulkan-overlay zink # Sergei Trofimovich (2019-12-12) # Needs stable net-libs/webkit-gtk, bug #684702 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/make.defaults index 12251d45c5..ef55cded6d 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/make.defaults +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/make.defaults @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # All extra USE/etc should be specified in sub-profiles. diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/package.use.mask index ba4f64dea0..04e2422180 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/package.use.mask @@ -1,6 +1,10 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James (2024-05-19) +# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 +media-gfx/graphicsmagick jpeg2k + # Sam James (2024-03-23) # sys-libs/libomp does not support ppc32 (bug #907213). sys-devel/clang-runtime openmp @@ -9,10 +13,7 @@ sys-devel/clang-runtime openmp # Fails tests, potential false negatives #911402 app-antivirus/clamav system-mspack -# Sam James (2024-01-17) -# The generated code is too large and it takes ages to build, bug #922249. -dev-python/mypy native-extensions - +# Marek Szuba (2024-04-24) # Sam James (2024-01-05) # sys-apps/keyutils not stable here, because of test failures. bug #636252 app-benchmarks/stress-ng keyutils @@ -20,7 +21,7 @@ app-crypt/mit-krb5 keyutils app-emulation/qemu keyutils net-fs/cifs-utils ads creds pam net-fs/samba ads -sys-auth/sssd keyutils +>=sys-libs/libblockdev-3.0.0 cryptsetup sys-libs/libnvme keyutils # Michał Górny (2023-10-15) diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/use.stable.mask index 848b8db5a5..ba9425aa2a 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc32/use.stable.mask @@ -1,6 +1,10 @@ # Copyright 2014-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Ionen Wolkens (2024-06-09) +# Qt6 is not stable here yet +qt6 + # Sam James (2024-03-07) # dev-lang/php:8.2 is not marked stable here yet (bug #920701) php_targets_php8-2 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64le/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64le/package.mask index aba0acfd08..aa4f7d7393 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64le/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64le/package.mask @@ -1,14 +1,22 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# WARNING: UnmatchedProfilePackageUnmask has a bug with false positives here +# https://github.com/pkgcore/pkgcheck/issues/685 + +# matoro (2024-06-10) +# Unmask for ppc64le, #892183 +-dev-python/sympy +-dev-python/symengine + +# Michał Górny (2024-04-24) +# Unmask ppc64le binpkg. +-dev-python/pypy-exe-bin + # Rahil Bhimjiani (2024-03-20) # https://bugs.gentoo.org/925111 -app-containers/podman -# Jimi Huotari (2023-01-11) -# Requires media-libs/libva since 29.0.0, which is unmasked here. -->=media-video/obs-studio-29.0.0 - # Sam James (2022-01-18) # No bootstrap binary available on big endian PPC64 right now, but there is # one for ppc64le. @@ -64,16 +72,6 @@ -sys-kernel/vanilla-kernel -virtual/dist-kernel -# Georgy Yakovlev (2020-01-25) -# libva unmasked on little-endian profile --net-im/telegram-desktop - -# Georgy Yakovlev (2020-01-21) -# works fine on little-endian --media-libs/libva --media-video/libva-utils --media-plugins/gst-plugins-vaapi - # Georgy Yakovlev (2019-08-14) # works fine on little-endian -x11-drivers/xf86-video-amdgpu diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64le/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64le/package.use.mask index e52371ee7c..db2c738617 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64le/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64le/package.use.mask @@ -5,10 +5,6 @@ # Needs USE=video_cards_amdgpu, which IS available on ppc64le. >=sys-apps/fwupd-1.9.10 -amdgpu -# Craig Andrews (2023-03-09) -# media-libs/libplacebo is keyworded here -media-video/ffmpeg -libplacebo - # Joonas Niilola (2022-11-10) # Doesn't work on ppc64, #871921 sci-mathematics/gmp-ecm custom-tune diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64ul/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64ul/package.mask index 7cd1ff04a6..0686d825e2 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64ul/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64ul/package.mask @@ -1,10 +1,20 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# matoro (2024-06-10) +# Requires ieee-long-double, i.e. ppc64le with 23.0 +# profiles and up, #892183 +dev-python/sympy +dev-python/symengine + # Rahil Bhimjiani (2024-03-20) # https://bugs.gentoo.org/925111 app-containers/podman +# Jimi Huotari (2023-01-11) +# Requires media-libs/libva since 29.0.0, which is masked here. +>=media-video/obs-studio-29.0.0 + # Georgy Yakovlev (2020-01-25) # Not all dependencies keyworded net-im/telegram-desktop diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64ul/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64ul/package.use.mask index 785e4d8dc7..02d3e897d4 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64ul/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/64ul/package.use.mask @@ -1,6 +1,11 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Joonas Niilola (2023-08-24) +# media-video/libva-utils is masked on ppc64, so hwaccel on Firefox +# wouldn't work. +www-client/firefox hwaccel + # Georgy Yakovlev (2022-02-16) # dev-python/networkx is keyworded here app-portage/nattka -depgraph-order diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/make.defaults index 93e2c5b69f..f981d6d162 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/make.defaults +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/make.defaults @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # All extra USE/etc should be specified in sub-profiles. diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.mask index 694da7e1f3..9b330b7b84 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.mask @@ -1,10 +1,6 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -# Jimi Huotari (2023-01-11) -# Requires media-libs/libva since 29.0.0. ->=media-video/obs-studio-29.0.0 - # Michał Górny (2022-08-25) # Only ppc64le binpkg is provided. dev-python/pypy-exe-bin @@ -61,12 +57,6 @@ sys-kernel/gentoo-kernel-bin sys-kernel/vanilla-kernel virtual/dist-kernel -# Georgy Yakovlev (2020-01-21) -# buggy on big-endian -media-libs/libva -media-video/libva-utils -media-plugins/gst-plugins-vaapi - # Georgy Yakovlev (2019-08-14) # buggy on big-endian x11-drivers/xf86-video-amdgpu diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.use.mask index bb9f219524..e57bdf031e 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.use.mask @@ -1,6 +1,15 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +app-crypt/pinentry qt6 +app-office/libreoffice qt6 + +# Sam James (2024-05-19) +# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 +media-gfx/graphicsmagick jpeg2k + # José de Paula R. N. Assis (2024-03-25) # No PyQt6 (which is needed by USE=qt6 for qscintilla-python) on ppc64. >=dev-python/qscintilla-python-2.14.1-r1 qt6 @@ -21,11 +30,6 @@ media-libs/libplacebo -shaderc # Qt 6 not keyworded here. dev-build/cmake gui -# Joonas Niilola (2023-08-24) -# media-video/libva-utils is masked on ppc64, so hwaccel on Firefox -# wouldn't work. -www-client/firefox hwaccel - # Alexey Sokolov (2023-08-14) # OpenMW is only playtested with LuaJIT, and in fact unit tests fail with Lua-5. # Therefore apply mask/force to override the profile's defaults, and invert on @@ -55,10 +59,6 @@ sci-libs/symengine tcmalloc # https://github.com/rustsec/rustsec/issues/707 dev-util/cargo-audit fix -# Andreas Sturmlechner (2022-07-17) -# dev-python/pyside2 is not keyworded -www-client/falkon python - # Jimi Huotari (2022-05-08) # Not keyworded here yet. lxqt-base/lxqt-meta desktop-portal @@ -136,10 +136,6 @@ x11-themes/arc-theme cinnamon # Bug #728558 media-video/ffmpeg -rav1e -# Andreas Sturmlechner (2020-07-02) -# media-libs/libplacebo is keyworded -media-video/vlc -libplacebo - # Georgy Yakovlev (2020-06-07) # works on ppc64 app-emulation/qemu -spice -usbredir diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.use.stable.mask index ca08aef619..dbbd4dfe61 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/package.use.stable.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 # When you add an entry to the top of this file, add your name, the date, and @@ -17,6 +17,14 @@ #--- END OF EXAMPLES --- +# Sam James (2024-04-30) +# sys-block/nbdkit is not yet marked stable here +app-emulation/libvirt nbd + +# Sam James (2024-04-24) +# sys-apps/flashrom is not marked stable on ppc64 yet +sys-apps/fwupd flashrom + # Sam James (2024-02-07) # grpc not stable here app-admin/syslog-ng grpc diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/use.mask index 34a2f70e2b..460ba125e9 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/ppc64/use.mask @@ -1,8 +1,12 @@ -# Copyright 2008-2023 Gentoo Authors +# Copyright 2008-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 ### THIS FILE IS ONLY FOR PACKAGES MASKED ON BOTH 64-BIT AND 32-BIT USERLAND!!! +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +kf6compat + # Paul Zander (2024-03-29) # not available here (see openexr, opencolorio, opencv) openvdb diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/use.mask index 15af1b44da..7a1c27c1b5 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/use.mask +++ b/sdk_container/src/third_party/portage-stable/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 (2020-01-25) # Requires qtwebengine, which is not ported to any of powerpc arches yet +pdfium webengine # Matt Turner (2018-09-18) @@ -45,10 +46,6 @@ video_cards_amdgpu video_cards_radeonsi clang -# Jeroen Roovers (2015-05-25) -# PowerPC has no support for this bootloader (bug #550322) -gnuefi - # These flags should only be used for ppc -cpu_flags_ppc_altivec -cpu_flags_ppc_vsx diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/use.stable.mask index 26c5e77569..cf5a25e06e 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/powerpc/use.stable.mask @@ -1,13 +1,9 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in use.mask -# Ionen Wolkens (2024-01-27) -# Qt6 is not stable here yet -qt6 - # Matt Turner (2018-04-25) # Dropped stable keywords octave diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/ppc/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/ppc/package.use.mask index 56ec9a5338..8c3b12715f 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/ppc/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/ppc/package.use.mask @@ -1,6 +1,10 @@ # Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Eli Schwartz (2024-06-05) +# tests require pytest-qt which is not keyworded +app-portage/elogviewer test + # Eray Aslan (2024-03-08) # mongodb dependencies are not keyworded mail-mta/postfix mongodb @@ -20,7 +24,3 @@ app-admin/syslog-ng grpc # Leonardo Hernández Hernández (2023-11-15) # media-libs/shaderc in not keyworded media-video/ffmpeg shaderc - -# Rich Freeman (2023-09-13) -# Tests require shellcheck which is not currently available -sys-process/systemd-cron test diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/riscv/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/riscv/package.use.mask index a5a54a1e90..1347f6f7f0 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/riscv/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/riscv/package.use.mask @@ -1,6 +1,19 @@ # Copyright 2019-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner (2024-06-15) +# Requires unkeyworded dev-qt/qtwebengine (and revdeps) +kde-plasma/plasma-nm openconnect + +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +app-crypt/pinentry qt6 +app-office/libreoffice qt6 + +# Sam James (2024-05-19) +# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 +media-gfx/graphicsmagick jpeg2k + # Robin H. Johnson (2023-11-22) -# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff) -# are only available for amd64, arm64 and riscv ->=gui-libs/wlroots-0.17.0 -drm -liftoff - # Ionen Wolkens (2023-10-09) # media-libs/shaderc is keyworded here. media-libs/libplacebo -shaderc @@ -216,7 +224,6 @@ dev-libs/mongo-c-driver test # LuaJIT does not support riscv app-text/texlive-core luajittex dev-texlive/texlive-basic luajittex -dev-texlive/texlive-context luajittex media-gfx/gimp lua www-servers/nginx nginx_modules_http_lua diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/riscv/use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/riscv/use.mask index 4eb16fdf74..87b8093152 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/riscv/use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/riscv/use.mask @@ -4,6 +4,10 @@ # Unmask the flag which corresponds to ARCH. -riscv +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +kf6compat + # Andrew Ammerlaan (2023-07-11) # Unmask secureboot flag on arches where sbsigntools is keyworded -secureboot @@ -22,6 +26,7 @@ # Yongxiang Liang (2024-01-16) # Requires qtwebengine, which is not ported to riscv +pdfium webengine # Marek Szuba (2021-08-14) diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/s390/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/s390/package.use.mask index 144e11dcf5..b0cfa52733 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/s390/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/s390/package.use.mask @@ -1,6 +1,10 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Michał Górny (2024-05-08) +# Requires sys-devel/{clang,llvm}:16. +dev-lang/python jit + # NRK (2024-04-08) # media-libs/libraw is not keyworded media-libs/imlib2 raw @@ -202,7 +206,7 @@ dev-python/diskcache test # Matt Turner (2020-08-11) # No drivers on this architecture support Vulkan -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa video_cards_zink vulkan vulkan-overlay zink # Hans de Graaff (2019-04-08) # Obsolete ruby version, no newer versions keyworded or stable. diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/make.defaults index 852a8fb95b..cf143847e9 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/make.defaults +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/make.defaults @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 ARCH="sparc" @@ -42,3 +42,7 @@ VIDEO_CARDS="fbdev mga r128 radeon" # Enable USE=libtirpc by default, to ease dependency resolution during # the stabilization of glibc-2.26. Bug 657148 USE="libtirpc" + +# Hans de Graaff (2024-05-20) +# Allow ruby32 stabling: https://bugs.gentoo.org/932285 +RUBY_TARGETS="ruby31 -ruby32" diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.mask index 538d5c80fc..dcbae565c2 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.mask @@ -1,6 +1,13 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# matoro (2024-06-11) +# Extensive use of unaligned access, no plans to fix, #636552 +# https://github.com/memcached/memcached/issues/902 +net-misc/memcached +dev-libs/libmemcached +dev-python/pylibmc + # matoro (2023-03-07) # Fails tests disastrously. Present evidence of passing test suite # before removing, please. diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.use.mask index de6fb1921f..854e02445f 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.use.mask @@ -1,6 +1,30 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner (2024-06-29) +# media-libs/libplacebo is not keyworded here +media-video/ffmpeg libplacebo + +# Sam James (2024-06-23) +# app-crypt/gcr:4[gtk] is not available here +app-crypt/pinentry gtk + +# matoro (2024-06-11) +# net-misc/memcached casualties, #636552 +# https://github.com/memcached/memcached/issues/902 +dev-python/pylibmc test +dev-python/pytest-services test +net-ftp/proftpd memcache +dev-ruby/dalli test + +# Sam James (2024-05-19) +# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559 +media-gfx/graphicsmagick jpeg2k + +# Arthur Zamarin (2024-05-13) +# Requires dev-util/shelltestrunner +app-arch/mt-st test + # Ionen Wolkens (2024-04-02) # dev-qt/qtsvg:6 is not keyworded here yet (bug #918896) dev-qt/qtdeclarative:6 svg @@ -32,6 +56,7 @@ sys-kernel/installkernel -grub net-libs/pjproject srtp net-misc/asterisk srtp +# Marek Szuba (2024-04-24) # Sam James (2024-01-05) # sys-apps/keyutils not stable here, because of test failures. bug #636252 app-benchmarks/stress-ng keyutils @@ -39,7 +64,7 @@ app-crypt/mit-krb5 keyutils app-emulation/qemu keyutils net-fs/samba ads net-fs/cifs-utils ads creds pam -sys-auth/sssd keyutils +>=sys-libs/libblockdev-3.0.0 cryptsetup sys-libs/libnvme keyutils # Sam James (2024-01-02) @@ -86,10 +111,6 @@ sys-apps/openrc s6 # Qt 6 not keyworded here. dev-build/cmake gui -# Rich Freeman (2023-09-13) -# Tests require shellcheck which is not currently available -sys-process/systemd-cron test - # Sam James (2023-07-21) # Requires app-emulation/qemu. sys-kernel/gentoo-kernel test @@ -301,7 +322,7 @@ media-libs/libsdl2 fcitx4 # Matt Turner (2020-08-11) # No drivers on this architecture support Vulkan -media-libs/mesa vulkan vulkan-overlay zink +media-libs/mesa video_cards_zink vulkan vulkan-overlay zink # Robin H. Johnson (2020-07-02) # Mask io-uring & zbc pending keywording @@ -606,10 +627,6 @@ gnome-base/gnome classic extras # Missing keywords, bug #493156 media-libs/libgphoto2 serial -# Pacho Ramos (2013-11-28) -# Missing keywords, bug #492820 -net-im/telepathy-connection-managers sipe - # Pacho Ramos (2013-07-20) # Keywords pending, bug #476710 >=gnome-base/gnome-extra-apps-3.8 games diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.use.stable.mask index 5451339c6b..2c3aef317e 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/package.use.stable.mask @@ -7,7 +7,6 @@ net-print/cups-filters pdf net-print/libcupsfilters pdf net-print/cups-meta pdf - # Sam James (2023-12-30) # Qt not marked stable here. app-text/doxygen gui diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/use.mask index 766fb7f8ce..c3222cbf6f 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/use.mask @@ -4,6 +4,11 @@ # Unmask the flag which corresponds to ARCH. -sparc +# matoro (2024-06-11) +# Extensive use of unaligned access, no plans to fix, #636552 +# https://github.com/memcached/memcached/issues/902 +memcached + # Ionen Wolkens (2024-01-27) # Needs bug #918896 for missing Qt6 keywords qt6 @@ -136,7 +141,6 @@ xfs musepack topal lqr -indi chm ebook capi diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/use.stable.mask index 79cf2319f1..865b799bc7 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/sparc/use.stable.mask @@ -4,6 +4,10 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in use.mask +# Hans de Graaff (2024-05-20) +# Allow ruby32 stabling: https://bugs.gentoo.org/932285 +ruby_targets_ruby32 + # Sam James (2024-03-07) # dev-lang/php:8.2 is not marked stable here yet (bug #920701) php_targets_php8-2 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/i486/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/i486/package.use.mask new file mode 100644 index 0000000000..5ed79144bc --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/i486/package.use.mask @@ -0,0 +1,8 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Ben Kohler (2024-05-03) +# Requires thin-provisioning-tools, which requires rust, which cannot currently +# build/install on i486 or any other CPU class lacking sse2. +sys-fs/lvm2 thin +app-containers/docker device-mapper diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/make.defaults index 2ff3ba0dff..16f6fbe98d 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/make.defaults +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/make.defaults @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # All extra USE/etc should be specified in sub-profiles. diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.mask index 9c933318d0..19f6423ba1 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.mask @@ -57,8 +57,6 @@ kde-apps/konqueror:5 kde-apps/konsolekalendar:5 kde-apps/kontact:5 kde-apps/korganizer:5 -kde-apps/ktp-accounts-kcm:5 -kde-apps/ktp-text-ui:5 kde-apps/libksieve:5 kde-apps/mailcommon:5 kde-apps/messagelib:5 @@ -66,7 +64,6 @@ kde-apps/mbox-importer:5 kde-apps/parley:5 kde-apps/pim-data-exporter:5 kde-apps/pim-sieve-editor:5 -kde-apps/plasma-telepathy-meta:5 kde-misc/kio-gdrive kde-misc/tellico:5 kde-misc/zanshin:5 @@ -74,7 +71,6 @@ media-gfx/digikam:5 media-gfx/luminance-hdr media-sound/frescobaldi media-sound/teamspeak-client:3 -media-video/openshot net-analyzer/nmapsi net-libs/signon-ui sci-geosciences/qmapshack diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use index 9770883187..9a904c7bc9 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use @@ -1,6 +1,11 @@ # Copyright 1999-2019 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Ben Kohler (2024-06-12) +# Disable thin volume support by default since it reuqires sse2 which most +# x86 cpus will lack +sys-fs/lvm2 -thin + # Ben Kohler (2022-06-07) # Enable BIOS target by default sys-apps/memtest86+ bios32 diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use.mask index 3a7916b4e2..a3cd3a0286 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use.mask @@ -1,22 +1,19 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +app-crypt/pinentry qt6 +app-office/libreoffice qt6 + # José de Paula R. N. Assis (2024-03-25) # No PyQt6 (which is needed by USE=qt6 for qscintilla-python) on x86. >=dev-python/qscintilla-python-2.14.1-r1 qt6 -# Andreas Sturmlechner (2024-03-24) -# Requires unkeyworded dev-qt/qtwebengine -net-p2p/ktorrent rss - # Andrew Ammerlaan (2024-03-21) # virt-firmware is keyworded here sys-kernel/installkernel -efistub -# Guilherme Amadio (2024-03-09) -# Qt6 not keyworded on x86 -sci-physics/root qt6 - # Sam James (2024-03-04) # Miscompiles rust and fails to bootstrap (bug #923278) >=dev-lang/rust-1.74.1 lto @@ -86,10 +83,6 @@ net-libs/pjproject webrtc # Needs x11-drivers/nvidia-drivers which is no longer available here. media-tv/mythtv nvdec -# Craig Andrews (2023-03-09) -# media-libs/libplacebo is keyworded here -media-video/ffmpeg -libplacebo - # Andreas Sturmlechner (2023-02-06) # Successful build of dev-qt/qtwebengine depends on 64-bit host # Bug #893234 @@ -103,15 +96,13 @@ kde-apps/kdenetwork-meta bittorrent kde-apps/kleopatra pim kde-apps/umbrello php kde-misc/kio-gdrive share +kde-plasma/plasma-nm openconnect net-irc/quassel urlpreview net-misc/fatrat bittorrent net-misc/seafile-client shibboleth +net-p2p/ktorrent rss sci-mathematics/yacas gui -sci-physics/root qt5 - -# Michał Górny (2022-11-16) -# spirv-llvm-translator is not keyworded x86. -dev-libs/libclc spirv +sci-physics/root qt5 qt6 # Ionen Wolkens (2022-11-07) # Vulkan is usable here. diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use.stable.mask index 98a331d0e7..7a39da3cbf 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/package.use.stable.mask @@ -17,6 +17,14 @@ #--- END OF EXAMPLES --- +# Sam James (2024-04-30) +# sys-block/nbdkit is not yet marked stable here +app-emulation/libvirt nbd + +# Matt Turner (2024-04-25) +# spirv-llvm-translator is not stable on x86. +dev-libs/libclc spirv + # Andrew Ammerlaan (2024-03-21) # Experimental, virt-firmware is keyworded only unstable sys-kernel/installkernel efistub diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/use.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/use.mask index 38dc83097d..2ef0d8e916 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/use.mask @@ -4,6 +4,10 @@ # Unmask the flag which corresponds to ARCH. -x86 +# Sam James (2024-06-13) +# Needs as-yet-unkeyworded KF6 (bug #934215) +kf6compat + # Paul Zander (2024-04-14) # media-libs/quirc is keyworded on amd64 -quirc @@ -31,6 +35,7 @@ color-management # Andreas Sturmlechner (2023-02-06) # Successful build of dev-qt/qtwebengine depends on 64-bit host # Bug #893234 +pdfium webengine # matoro (2022-09-29) diff --git a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/use.stable.mask index 6f373ce425..90b1e4500f 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/arch/x86/use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/arch/x86/use.stable.mask @@ -12,10 +12,6 @@ atlas # media-libs/jasper is not stable jasper -# Ionen Wolkens (2024-01-27) -# Qt6 is not stable here yet -qt6 - # Sam James (2020-11-10) # media-gfx/openvdb is not stable on x86 # ... and has failing tests right now anyway diff --git a/sdk_container/src/third_party/portage-stable/profiles/base/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/base/make.defaults index 7ed31693ca..957af187bd 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/base/make.defaults +++ b/sdk_container/src/third_party/portage-stable/profiles/base/make.defaults @@ -12,7 +12,7 @@ USE_EXPAND_VALUES_KERNEL="Darwin linux SunOS" # Env vars to expand into USE vars. Modifying this requires prior # discussion on gentoo-dev@lists.gentoo.org. -USE_EXPAND="ABI_MIPS ABI_S390 ABI_X86 ADA_TARGET ALSA_CARDS AMDGPU_TARGETS APACHE2_MODULES APACHE2_MPMS CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_ARM CPU_FLAGS_PPC CPU_FLAGS_X86 CURL_SSL ELIBC FFTOOLS GPSD_PROTOCOLS GRUB_PLATFORMS INPUT_DEVICES KERNEL L10N LCD_DEVICES LIBREOFFICE_EXTENSIONS LLVM_SLOT LLVM_TARGETS LUA_SINGLE_TARGET LUA_TARGETS MONKEYD_PLUGINS NGINX_MODULES_HTTP NGINX_MODULES_MAIL NGINX_MODULES_STREAM OFFICE_IMPLEMENTATION OPENMPI_FABRICS OPENMPI_OFED_FEATURES OPENMPI_RM PHP_TARGETS POSTGRES_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS RUBY_TARGETS SANE_BACKENDS UWSGI_PLUGINS VIDEO_CARDS VOICEMAIL_STORAGE XTABLES_ADDONS" +USE_EXPAND="ABI_MIPS ABI_S390 ABI_X86 ADA_TARGET ALSA_CARDS AMDGPU_TARGETS APACHE2_MODULES APACHE2_MPMS CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_ARM CPU_FLAGS_PPC CPU_FLAGS_X86 CURL_SSL CURL_QUIC ELIBC FFTOOLS GPSD_PROTOCOLS GRUB_PLATFORMS INPUT_DEVICES KERNEL L10N LCD_DEVICES LIBREOFFICE_EXTENSIONS LLVM_SLOT LLVM_TARGETS LUA_SINGLE_TARGET LUA_TARGETS MONKEYD_PLUGINS NGINX_MODULES_HTTP NGINX_MODULES_MAIL NGINX_MODULES_STREAM OFFICE_IMPLEMENTATION OPENMPI_FABRICS OPENMPI_OFED_FEATURES OPENMPI_RM PERL_FEATURES PHP_TARGETS POSTGRES_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS RUBY_TARGETS SANE_BACKENDS UWSGI_PLUGINS VIDEO_CARDS VOICEMAIL_STORAGE XTABLES_ADDONS" # USE_EXPAND variables whose contents are not shown in package manager # output. Changes need discussion on gentoo-dev. @@ -94,9 +94,9 @@ XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipp2p iface geoip fu LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text" # Manuel Rüger (2015-09-09) +# Hans de Graaff (2024-05-20) # Default Ruby build target(s) -# Updated to add ruby31 on 2023-05-29 and to drop ruby30 on 2023-06-17 -RUBY_TARGETS="ruby31" +RUBY_TARGETS="ruby31 ruby32" # Andreas K. Hüttel (2022-10-22) # These USE flags are what is common between the various sub-profiles. Stages 2 @@ -123,12 +123,13 @@ PYTHONDONTWRITEBYTECODE="1" # This MUST be kept in sync with the PYTHON_TARGETS below # Mike Gilbert (2018-05-23) # sys-apps/baselayout-2.5 needs split-usr enabled. -BOOTSTRAP_USE="unicode internal-glib pkg-config split-usr xml python_targets_python3_11 python_single_target_python3_11" +# dev-lang/python:3.13 and later needs gil enabled +BOOTSTRAP_USE="unicode pkg-config split-usr xml python_targets_python3_12 python_single_target_python3_12 gil" # Mike Gilbert (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 (2013-08-10) # Moved from portage's make.globals. @@ -164,7 +165,7 @@ POSTGRES_TARGETS="postgres15" # Moreover, it should only contain targets that have a stable version # of PHP, to avoid pulling in an unstable PHP on stable systems. # -PHP_TARGETS="php8-1" +PHP_TARGETS="php8-2" # Alfredo Tupone (2024-03-15) # diff --git a/sdk_container/src/third_party/portage-stable/profiles/base/package.use b/sdk_container/src/third_party/portage-stable/profiles/base/package.use index cf646b56fb..b4cc281eb2 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/base/package.use +++ b/sdk_container/src/third_party/portage-stable/profiles/base/package.use @@ -1,6 +1,13 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Andreas Sturmlechner (2024-05-30) +# Only up to python 3.11 supported, bug #929546 + (2024-03-23) # Used by pkgcheck, so let's make it easier for all developers to install it >=dev-libs/tree-sitter-bash-0.21.0 python diff --git a/sdk_container/src/third_party/portage-stable/profiles/base/package.use.force b/sdk_container/src/third_party/portage-stable/profiles/base/package.use.force index 65e6df80c2..1f124de03f 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/base/package.use.force +++ b/sdk_container/src/third_party/portage-stable/profiles/base/package.use.force @@ -1,6 +1,22 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Michał Górny (2024-06-29) +# Disabling GIL (enabling freethreading) is experimental and prone +# to break packages. Should you choose to test it, please do not file +# Gentoo bugs and report any issues you hit upstream. +dev-lang/python gil + +# Sam James (2024-06-03) +# Poor rendering performance otherwise (bug #931215). +kde-plasma/kwin caps + +# James Le Cuirot (2024-06-02) +# Requires FFmpeg 7.0, which we don't have yet, so force Chromium fork. +>=dev-libs/nwjs-0.88.0 ffmpeg-chromium +>=www-client/vivaldi-6.8.3371.4 ffmpeg-chromium +>=www-client/vivaldi-snapshot-6.8.3371.4 ffmpeg-chromium + # Ionen Wolkens (2024-04-10) # Flipping the zstd USE state is unsafe and can break *tons* of Qt revdeps # including many KDE packages and Qt itself without rebuilds due to losing @@ -174,10 +190,6 @@ net-misc/wget ssl # is maintained for experts only. sys-libs/libcxx libcxxabi -# Matt Turner (2019-09-01) -# (2019-08-17) # USE=-cxx us a sure way to break native install as modern gcc # requires C++ to bootstrap. But in rare cases it's useful @@ -241,6 +253,7 @@ app-shells/bash:0 readline dev-lang/python-exec python_targets_python3_10 dev-lang/python-exec python_targets_python3_11 dev-lang/python-exec python_targets_python3_12 +dev-lang/python-exec python_targets_python3_13 dev-lang/python-exec python_targets_pypy3 # Zac Medico (2010-10-20) diff --git a/sdk_container/src/third_party/portage-stable/profiles/base/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/base/package.use.mask index ac1edb0749..cb89826a5c 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/base/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/base/package.use.mask @@ -6,6 +6,40 @@ # This file is only for generic masks. For arch-specific masks (i.e. # mask everywhere, unmask on arch/*) use arch/base. +# Michał Górny (2024-06-29) +# JIT is experimental and prone to break packages. Should you choose +# to use it, please do not file Gentoo bugs and report any issues you +# hit upstream. +dev-lang/python jit + +# Sam James (2024-06-24) +# Breaks installed gems in hard-to-debug ways. +# bug #887223, bug #891367, bug #903891, bug #917139 +dev-lang/ruby static-libs + +# Alfredo Tupone (2024-05-28) +# Not working, bug #931046 +>=sci-libs/caffe2-2.3.0 rocm + +# Sam James (2024-05-09) +# Experimental option upstream which seems undertested and underdocumented. +# Fails to build with stricter C compilers too (bug #919685). +net-misc/openssh xmss + +# Matt Turner (2024-05-08) +# Brand new, introduces lots of new aspects to the build. +# Masked for further testing. +media-libs/mesa video_cards_nvk + +# Michał Górny (2024-04-27) +# dev-python/uv is nowhere near ready to be stabilized. +dev-python/build test-rust + +# Michał Górny (2024-04-23) +# app-forensics/libewf is being removed (TestDisk does not build +# successfully with our version anyway). +app-admin/testdisk ewf + # Mike Gilbert (2024-04-18) # Wayland client is broken/deprecated by upstream. Bug 930197. >=net-misc/freerdp-3 wayland @@ -18,23 +52,10 @@ dev-util/kdevelop reviewboard # sys-auth/pam_ssh is being last rited, bug #892031. sys-auth/pambase pam_ssh -# Andrew Ammerlaan (2024-03-22) -# Building with qt6 requires (masked) kde-frameworks:6 -app-admin/calamares qt6 - # Viorel Munteanu (2024-03-19) # The live version needs a new BDEPEND for doc =app-emulation/virtualbox-9999 doc -# Sam James (2024-03-18) -# Needs masked KF6 for Wayland at least. -app-crypt/pinentry qt6 - -# Michał Górny (2024-03-17) -# Suffers from unaligned accesses, upstream's working on it. -# https://github.com/psycopg/psycopg/issues/734 -<=dev-python/psycopg-3.1.18 native-extensions - # Guilherme Amadio (2024-03-09) # Requires manually installing dependencies, see bug #791802 # Please use MYCMAKEARGS instead. @@ -177,7 +198,7 @@ app-admin/ansible-molecule doc # William Hubbs (2023-06-30) # multiple repeated issues: Bug: #909394 # Joonas Niilola (2024-04-22) -# Can break reverse dependencies (Chromium, Firefox), debugging not always +# Can break reverse dependencies (Chromium, Firefox), debugging not always # obvious. net-libs/nodejs lto @@ -250,10 +271,6 @@ sci-libs/vtk debug # See also: https://bugs.gentoo.org/891499 sys-libs/libomp llvm_targets_AMDGPU -# Sam James (2023-01-21) -# Fails to compile: https://github.com/libffi/libffi/issues/760 - (2023-01-08) # Doesn't compile currently, bug #853094. >=net-dialup/freeradius-3.2.0 oracle @@ -271,10 +288,6 @@ app-misc/pax-utils seccomp # Broken when trying to use sys-libs/binutils-libs header, bug #879067 >=x11-libs/cairo-1.17.6 debug -# Joonas Niilola (2022-11-25) -# x11-wm/stumpwm-22.05_p20220818[doc] is totally broken. Bug #882935 -x11-wm/stumpwm doc - # Bernd Waibel (2022-11-25) # USE=tbb is broken in 7.7.0 # https://tracker.dev.opencascade.org/view.php?id=33152 @@ -596,10 +609,6 @@ app-office/abiword ots (2020-09-27) -# The respective dependencies are masked for removal. -net-im/telepathy-connection-managers gadu icq meanwhile steam yahoo - # Joonas Niilola (2020-09-23) # Highly experimental, may cause breakages when updating. Use with # caution! @@ -788,7 +797,6 @@ app-emulation/libvirt openvz # need or even advantage to set custom compiler flags at all. # Example: bug #619628 sys-boot/gnu-efi custom-cflags -sys-boot/refind custom-cflags # Andreas K. Hüttel (2017-05-29) # Does not build diff --git a/sdk_container/src/third_party/portage-stable/profiles/base/package.use.stable.force b/sdk_container/src/third_party/portage-stable/profiles/base/package.use.stable.force index f03d72a200..90c98d1e2a 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/base/package.use.stable.force +++ b/sdk_container/src/third_party/portage-stable/profiles/base/package.use.stable.force @@ -4,10 +4,6 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in package.use.force -# James Le Cuirot (2023-12-23) -# Force ffmpeg-chromium fork until ffmpeg-6.1 is stable. -www-client/vivaldi ffmpeg-chromium - ## Kent Fredric (2019-07-11) # The absense of these features require dev-perl/GD, which currently # can't be considered stable due to serious defects upstream. diff --git a/sdk_container/src/third_party/portage-stable/profiles/base/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/base/package.use.stable.mask index 242387dc57..8d78931262 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/base/package.use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/base/package.use.stable.mask @@ -4,6 +4,11 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in package.use.mask +# Andreas Sturmlechner (2024-06-13) +# Building with qt6 requires (masked) kde-frameworks:6 +app-admin/calamares qt6 +app-crypt/pinentry qt6 + # Andrew Ammerlaan (2024-04-14) # Qt6 dependencies are not yet available in stable. Moreover, # Qt6 support in freecad is not completely finished. @@ -39,7 +44,6 @@ sci-physics/lammps hip # Sam James (2022-12-07) # Needs unstable media-libs/libvpl -media-libs/gst-plugins-bad qsv media-video/ffmpeg qsv # Guillermo Joandet (2022-11-22) @@ -174,10 +178,6 @@ sys-auth/pambase sssd # Needs dev-ruby/asciidoctor which has a lot of unstable deps net-analyzer/wireshark doc -# Matthias Maier (2018-03-18) -# dev-libs/capstone hasn't been stabilized yet -app-emulation/qemu capstone - # Kent Fredric (2018-03-03) # Not an officially supported configuration, as it causes unpredictable # fragility and/or dependency headaches due to the very narrow interop window diff --git a/sdk_container/src/third_party/portage-stable/profiles/base/use.mask b/sdk_container/src/third_party/portage-stable/profiles/base/use.mask index f27ab3bcd0..3db1ca5d54 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/base/use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/base/use.mask @@ -4,14 +4,15 @@ # This file is only for generic masks. For arch-specific masks (i.e. # mask everywhere, unmask on arch/*) use arch/base. +# Andreas K. Hüttel (2024-05-01) +# PERL_FEATURES=debug is not a setting that should be used lightly. +# If you really need it, then unmask it... +perl_features_debug + # Andreas Sturmlechner (2024-04-06) # Telepathy is dead and packages masked for removal. telepathy -# Andreas Sturmlechner (2023-12-15) -# KF6 is not in ::gentoo yet. Move to stable.use.mask on KF6 intro. -kf6compat - # Hans de Graaff (2023-08-19) # Ruby 3.0 is not compatible with OpenSSL 3. Please upgrade to a newer # Ruby version. diff --git a/sdk_container/src/third_party/portage-stable/profiles/base/use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/base/use.stable.mask index 59d9eb195d..63704adbe4 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/base/use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/base/use.stable.mask @@ -4,20 +4,25 @@ # This file requires eapi 5 or later. New entries go on top. # Please use the same syntax as in use.mask +# Andreas Sturmlechner (2024-06-13) +# KF6 is not in stable yet. +kf6compat + +# Michał Górny (2024-05-08) +# Python implementations without stable keywords. +python_targets_python3_13 +python_single_target_python3_13 +python_targets_pypy3 +python_single_target_pypy3 + # Michał Górny (2024-04-04) # LLVM slots without stablekeywords. llvm_slot_18 # Hans de Graaff (2023-12-25) # Currently in testing and not ready to go stable yet. -ruby_targets_ruby32 ruby_targets_ruby33 # Michael Orlitzky (2023-12-05) # New unstable PHP slot. php_targets_php8-3 - -# Zac Medico (2016-09-01) -# Needs dev-python/pypy* stable -python_targets_pypy3 -python_single_target_pypy3 diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/deprecated new file mode 100644 index 0000000000..3cee563630 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/split-usr + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/deprecated new file mode 100644 index 0000000000..5250cf03f6 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/split-usr/desktop + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/gnome/deprecated new file mode 100644 index 0000000000..9a079e68be --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/split-usr/desktop/gnome + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..eca25d7adc --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/desktop/gnome/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/developer/deprecated new file mode 100644 index 0000000000..3cee563630 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/split-usr + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..217bbccd2d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/alpha/23.0/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/clang/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/clang/deprecated new file mode 100644 index 0000000000..f4c5ed652f --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/deprecated new file mode 100644 index 0000000000..fb300c26f9 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/hardened/deprecated new file mode 100644 index 0000000000..20c9fedaf0 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/hardened/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/hardened/selinux/deprecated new file mode 100644 index 0000000000..d11cd2c325 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/x32/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/x32/deprecated new file mode 100644 index 0000000000..69d1807d07 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/x32/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/x32 + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/x32/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/x32/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..1b33082739 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/x32/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/x32/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/clang/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/clang/deprecated new file mode 100644 index 0000000000..1087d3e339 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/clang/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/llvm + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/deprecated new file mode 100644 index 0000000000..1dfba2cdb1 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/deprecated new file mode 100644 index 0000000000..04b8c3bd66 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/desktop + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/gnome/deprecated new file mode 100644 index 0000000000..2b8cce7ee0 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/desktop/gnome + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..bb2fc8dfd7 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/desktop/gnome/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/plasma/deprecated new file mode 100644 index 0000000000..e0f4c8a253 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/desktop/plasma + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..1a027e1ea3 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/desktop/plasma/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..f8443e5de5 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/desktop/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/developer/deprecated new file mode 100644 index 0000000000..1dfba2cdb1 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/hardened/deprecated new file mode 100644 index 0000000000..f1d39a57a3 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/hardened + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/hardened/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/hardened/selinux/deprecated new file mode 100644 index 0000000000..3996638f2a --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/hardened/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/hardened/selinux + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/deprecated new file mode 100644 index 0000000000..33a1cf4ea2 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/no-multilib + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/hardened/deprecated new file mode 100644 index 0000000000..7f6226b802 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/no-multilib/hardened + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/hardened/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/hardened/selinux/deprecated new file mode 100644 index 0000000000..55b586baed --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/hardened/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..5dffabddd0 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/no-multilib/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/deprecated new file mode 100644 index 0000000000..0a7d7473d1 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/deprecated @@ -0,0 +1,33 @@ +default/linux/amd64/17.1/no-multilib/systemd/selinux/merged-usr + +As warned about previously in a news item, systemd-255 has dropped +support for split-usr systems. All Gentoo systems running systemd will +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/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/merged-usr/deprecated new file mode 100644 index 0000000000..ca932ac65f --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/no-multilib/systemd/selinux/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/selinux/deprecated new file mode 100644 index 0000000000..3996638f2a --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/split-usr/hardened/selinux + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/clang/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/clang/deprecated new file mode 100644 index 0000000000..e5a3dd1d75 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/clang/deprecated @@ -0,0 +1,33 @@ +default/linux/amd64/17.1/systemd/clang/merged-usr + +As warned about previously in a news item, systemd-255 has dropped +support for split-usr systems. All Gentoo systems running systemd will +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/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/clang/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/clang/merged-usr/deprecated new file mode 100644 index 0000000000..aa61cab28d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/clang/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/llvm/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..0da73aecf9 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/selinux/deprecated new file mode 100644 index 0000000000..736342a221 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/selinux/deprecated @@ -0,0 +1,33 @@ +default/linux/amd64/17.1/systemd/selinux/merged-usr + +As warned about previously in a news item, systemd-255 has dropped +support for split-usr systems. All Gentoo systems running systemd will +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/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/selinux/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/selinux/merged-usr/deprecated new file mode 100644 index 0000000000..e0853bb8ea --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/systemd/selinux/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/amd64/23.0/hardened/selinux/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/deprecated new file mode 100644 index 0000000000..45b5c52341 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4 + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/deprecated new file mode 100644 index 0000000000..45b5c52341 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4 + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/gnome/deprecated new file mode 100644 index 0000000000..45b5c52341 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4 + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/plasma/deprecated new file mode 100644 index 0000000000..45b5c52341 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4 + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/developer/deprecated new file mode 100644 index 0000000000..45b5c52341 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4 + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/deprecated new file mode 100644 index 0000000000..97e893728d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4t + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/deprecated new file mode 100644 index 0000000000..97e893728d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4t + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/gnome/deprecated new file mode 100644 index 0000000000..97e893728d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4t + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/plasma/deprecated new file mode 100644 index 0000000000..97e893728d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4t + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/developer/deprecated new file mode 100644 index 0000000000..97e893728d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv4t + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..39e9ddab5c --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv4t/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/armv4t/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/deprecated new file mode 100644 index 0000000000..021c24a339 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv5te + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/deprecated new file mode 100644 index 0000000000..021c24a339 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv5te + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/gnome/deprecated new file mode 100644 index 0000000000..021c24a339 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv5te + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/plasma/deprecated new file mode 100644 index 0000000000..021c24a339 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv5te + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/developer/deprecated new file mode 100644 index 0000000000..021c24a339 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/armv5te + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..7721e0101e --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv5te/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/armv5te/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/gnome/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/gnome/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/plasma/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/desktop/plasma/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/developer/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/developer/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/hardened/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/hardened/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/hardened/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/hardened/selinux/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/hardened/selinux/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/selinux/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/selinux/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv6j/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/developer/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/developer/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/hardened/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/hardened/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/hardened/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/hardened/selinux/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/hardened/selinux/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/armv7a/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/deprecated new file mode 100644 index 0000000000..ebd06e2074 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/deprecated new file mode 100644 index 0000000000..b65e6c8df8 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/desktop + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/gnome/deprecated new file mode 100644 index 0000000000..51ad785cb3 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/desktop/gnome + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..e79024de03 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/desktop/gnome/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/plasma/deprecated new file mode 100644 index 0000000000..4e44c2757a --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr/desktop/plasma + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/plasma/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..df5a51661d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/desktop/plasma/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/developer/deprecated new file mode 100644 index 0000000000..ebd06e2074 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/arm/23.0/split-usr + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv6j/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv6j/deprecated new file mode 100644 index 0000000000..5d36c73cd8 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv6j/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv6j/hardened/deprecated new file mode 100644 index 0000000000..de12cbfb22 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv6j/hardened/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv6j/hardened/selinux/deprecated new file mode 100644 index 0000000000..32c22267e8 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv7a/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv7a/deprecated new file mode 100644 index 0000000000..6fc6daceb3 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv7a/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv7a/hardened/deprecated new file mode 100644 index 0000000000..b06f94740d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv7a/hardened/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/17.0/musl/armv7a/hardened/selinux/deprecated new file mode 100644 index 0000000000..05defdaa72 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/armv6j_hf/musl/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/armv6j_hf/musl/package.use.mask similarity index 100% rename from sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/armv6j_hf/musl/package.use.stable.mask rename to sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/armv6j_hf/musl/package.use.mask diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/armv7a_hf/musl/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/armv7a_hf/musl/package.use.mask similarity index 100% rename from sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/armv7a_hf/musl/package.use.stable.mask rename to sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/armv7a_hf/musl/package.use.mask diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/musl/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/musl/package.use.stable.mask index c021f45d85..785b52ceb8 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/musl/package.use.stable.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/musl/package.use.stable.mask @@ -1,6 +1,11 @@ # Copyright 2024 Gentoo Authors # Distributed under the terms of the GNU General Public License, v2 +# Sam James (2024-06-16) +# Avoid pulling in sys-libs/compiler-rt-sanitizers which fails to build +# See bug #928936. +sys-devel/clang-runtime sanitize + # Andreas K. Hüttel (2024-03-20) # Does not compile with musl-1.2.4 sys-devel/gcc sanitize diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/package.use.mask similarity index 100% rename from sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/package.use.stable.mask rename to sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/split-usr/armv6j_hf/musl/package.use.mask diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/package.use.mask similarity index 100% rename from sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/package.use.stable.mask rename to sdk_container/src/third_party/portage-stable/profiles/default/linux/arm/23.0/split-usr/armv7a_hf/musl/package.use.mask diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/big-endian/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/big-endian/deprecated new file mode 100644 index 0000000000..680df0d1ab --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/big-endian/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/big-endian + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/big-endian/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/big-endian/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..c59e696188 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/big-endian/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/big-endian/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/deprecated new file mode 100644 index 0000000000..486ba33d3d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/deprecated new file mode 100644 index 0000000000..717b857534 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/desktop + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/gnome/deprecated new file mode 100644 index 0000000000..a97368ac1d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/desktop/gnome + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..668387f6a6 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/desktop/gnome/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/plasma/deprecated new file mode 100644 index 0000000000..ebb83e5535 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/desktop/plasma + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/plasma/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..ccd2417ba8 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/desktop/plasma/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..7b6310b03f --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/desktop/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/desktop/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/developer/deprecated new file mode 100644 index 0000000000..486ba33d3d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/hardened/deprecated new file mode 100644 index 0000000000..ae8d32507a --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/hardened/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/hardened + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/hardened/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/hardened/selinux/deprecated new file mode 100644 index 0000000000..04377eb07d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/hardened/selinux/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/hardened/selinux + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/llvm/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/llvm/deprecated new file mode 100644 index 0000000000..50d9447edf --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/llvm/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/split-usr/llvm + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/deprecated new file mode 100644 index 0000000000..96ea042000 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/hardened/deprecated new file mode 100644 index 0000000000..7a1a186593 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/hardened/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/hardened/selinux/deprecated new file mode 100644 index 0000000000..da1bf7ef37 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/llvm/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/musl/llvm/deprecated new file mode 100644 index 0000000000..8e6ae643ca --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/llvm/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/llvm/merged-usr/deprecated new file mode 100644 index 0000000000..a344c6d61e --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/llvm/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/llvm/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..d639e20f18 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/selinux/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/selinux/merged-usr/deprecated new file mode 100644 index 0000000000..826f54d8a3 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/arm64/17.0/systemd/selinux/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/arm64/23.0/hardened/selinux/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/desktop/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/desktop/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/developer/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/developer/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/hppa/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ + + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/deprecated new file mode 100644 index 0000000000..db515b7e21 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/ia64/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/deprecated new file mode 100644 index 0000000000..79f71ff588 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/ia64/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/gnome/deprecated new file mode 100644 index 0000000000..0eb67ae806 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/ia64/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..b367562fd1 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/ia64/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/developer/deprecated new file mode 100644 index 0000000000..db515b7e21 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/ia64/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..be9bc4b256 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ia64/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/ia64/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/deprecated new file mode 100644 index 0000000000..e014056c31 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/split-usr/lp64d + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/deprecated new file mode 100644 index 0000000000..7dad124056 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/split-usr/lp64d/desktop + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/deprecated new file mode 100644 index 0000000000..4f70ec5b09 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/split-usr/lp64d/desktop/gnome + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..2739d57076 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/gnome/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/lp64d/desktop/gnome/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/deprecated new file mode 100644 index 0000000000..fba6aacd50 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/split-usr/lp64d/desktop/plasma + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..dd2de41c7c --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/plasma/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/lp64d/desktop/plasma/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..a6a9180fad --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/desktop/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/lp64d/desktop/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/developer/deprecated new file mode 100644 index 0000000000..e014056c31 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/developer/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/split-usr/lp64d + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..3967f72298 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/loong/22.0/la64v100/lp64d/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/loong/23.0/la64v100/lp64d/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/m68k/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/m68k/17.0/deprecated new file mode 100644 index 0000000000..5b3bb8039b --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/m68k/17.0/deprecated @@ -0,0 +1,104 @@ +default/linux/m68k/23.0/split-usr + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/m68k/17.0/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/m68k/17.0/musl/deprecated new file mode 100644 index 0000000000..d9c8615f02 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/m68k/17.0/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/m68k/17.0/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..d551985946 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/m68k/17.0/systemd/merged-usr/deprecated @@ -0,0 +1,104 @@ +default/linux/m68k/23.0/systemd + +A profile upgrade to version 23.0 is available for your architecture. +The new 23.0 profiles enable some toolchain hardening features and +performance enhancements by default, and standardize settings. +You can find the list of changes on the wiki tracking page [1]. + +Upgrade instructions + +Note 1: If you have manually changed your CHOST to a value different from +what the stages and profiles set, you may have to do that in the future too. +In that case you should know what you are doing, hopefully; please read the +instructions with a critical eye then. + +Note 2: In case you are already familiar with binary packages, you should be +able to add "--getbinpkg" to the emerge calls to speed things up. +The use of binary packages is completely optional though, and also not +as much tested as the source-based upgrade path yet. + +1. Ensure your system backups are up to date. Please also update + your system fully and depclean before proceeding. + glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. + +2. If you are still using one of the long-deprecated amd64 17.0 profiles + (other than x32 or musl), then first complete the migration to the + corresponding 17.1 profile. Instructions can be found at [3]. + +3. If you are currently using systemd in a split-usr configuration, then first + complete the migration to the corresponding merged-usr profile of the + same profile version. Details on how to do this can be found in the news + item [4]. + If you are currently using openrc, migrate to 23.0 first, keeping your disk + layout. If you want to move from split-usr to merged-usr, do that afterwards. + +4. Run "emerge --info" and note down the value of the CHOST variable. + +5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, + remove it. Also delete all lines defining CHOST_... variables. + +6. Select the 23.0 profile corresponding to your current profile, either using + "eselect profile" or by manually setting the profile symlink. + Note that old profiles are by default split-usr and the 23.0 profiles by + default merged-usr. Do NOT change directory scheme now, since this will + mess up your system! + Instead, make sure that the new profile has the same property: for example, + OLD default/linux/amd64/17.1 + ==> NEW default/linux/amd64/23.0/split-usr + (added "split-usr") + OLD default/linux/amd64/17.1/systemd/merged-usr + ==> NEW default/linux/amd64/23.0/systemd + (removed "merged-usr") + A detailed table of the upgrade paths can be found at [5]. Please consult it. + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). + +7. Delete the contents of your binary package cache at ${PKGDIR} + rm -r /var/cache/binpkgs/* + +8. In the file or directory /etc/portage/binrepos.conf (if existing), update + the URI in all configuration such that they point to 23.0 profile binhost + directories. The exact paths can be found in the table at [5], too. + +9. Rebuild or reinstall from binary (if available) the following packages in + this order, with the same version as already active: + emerge --ask --oneshot sys-devel/binutils + (you may have to run binutils-config and re-select your binutils now) + emerge --ask --oneshot sys-devel/gcc + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) + (you may have to run gcc-config and re-select your gcc now) + and the C library, i.e. for glibc-based systems + emerge --ask --oneshot sys-libs/glibc + or for musl-based systems + emerge --ask --oneshot sys-libs/musl + +10. Re-run "emerge --info" and check if CHOST has changed compared to step 4. + +If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, + +11. Recheck with binutils-config and gcc-config that valid installed versions + of binutils and gcc are selected. + +12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that + refer to the *OLD* CHOST value, and remove them. + Examples how to do this can be found in the similar procedure at [6]. + +13. Run env-update && source /etc/profile + +14. Re-emerge libtool: + emerge --ask --oneshot libtool + +15. Just for safety, delete the contents of your binary package cache at + ${PKGDIR} again: + rm -r /var/cache/binpkgs/* + +16. Rebuild world: + emerge --ask --emptytree @world + +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline +[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html +[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n32/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n32/deprecated new file mode 100644 index 0000000000..a88072d796 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n32/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n32/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..91dd79c36c --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n64/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n64/deprecated new file mode 100644 index 0000000000..d30a7d94ed --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n64/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/n64/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..546f248151 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/o32/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/o32/deprecated new file mode 100644 index 0000000000..0b4da443b6 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/multilib/o32/deprecated @@ -0,0 +1 @@ +default/linux/mips/17.0/mipsel/o32 diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n32/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n32/deprecated new file mode 100644 index 0000000000..e8ef1fd920 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n32/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n32/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..d98cd50d49 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n64/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n64/deprecated new file mode 100644 index 0000000000..d27ee875a2 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n64/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n64/musl/deprecated new file mode 100644 index 0000000000..085b11b8d9 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n64/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/n64/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..0f1d363723 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/o32/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/o32/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/o32/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/o32/musl/deprecated new file mode 100644 index 0000000000..970442e531 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/o32/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/mipsel/o32/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/n32/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/n32/deprecated new file mode 100644 index 0000000000..a4a9ed8007 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/n32/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/n32/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..372276d3f1 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/n64/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/n64/deprecated new file mode 100644 index 0000000000..a086d5b8f3 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/o32/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/o32/deprecated new file mode 100644 index 0000000000..98ce3606a0 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/multilib/o32/deprecated @@ -0,0 +1 @@ +default/linux/mips/17.0/o32 diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n32/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n32/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n32/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n32/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n64/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n64/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n64/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n64/musl/deprecated new file mode 100644 index 0000000000..4f0f9630ce --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n64/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/n64/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/o32/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/o32/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/o32/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/o32/musl/deprecated new file mode 100644 index 0000000000..0eadddb9a3 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/o32/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/o32/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/package.use.mask new file mode 100644 index 0000000000..ca4cfb9315 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/package.use.mask @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# matoro (2022-09-14) +# Not broken, but better wait on profiles: bug #515694 +dev-lang/rust system-llvm diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/use.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/use.mask new file mode 100644 index 0000000000..40a63a664e --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/mips/17.0/use.mask @@ -0,0 +1,7 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Matt Turner (2010-12-13) +# We don't have sys-devel/llvm +llvm +llvm-libunwind diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/deprecated new file mode 100644 index 0000000000..4b91a95b37 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/deprecated new file mode 100644 index 0000000000..0159d2926b --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/deprecated new file mode 100644 index 0000000000..0c3059bbec --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..78c0773972 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/powerpc/ppc64/17.0/32bit-userland/developer/deprecated new file mode 100644 index 0000000000..4b91a95b37 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/deprecated new file mode 100644 index 0000000000..4b91a95b37 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/desktop/deprecated new file mode 100644 index 0000000000..0159d2926b --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/desktop/gnome/deprecated new file mode 100644 index 0000000000..0c3059bbec --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..4c39f7d0e8 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/developer/deprecated new file mode 100644 index 0000000000..4b91a95b37 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/musl/deprecated new file mode 100644 index 0000000000..e719c63002 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/musl/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/musl/hardened/deprecated new file mode 100644 index 0000000000..4f477a5098 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/17.0/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..030e189b86 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/23.0/musl/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/23.0/musl/package.use.mask index 80fbaf3654..c7d54156ad 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/23.0/musl/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc/23.0/musl/package.use.mask @@ -1,6 +1,11 @@ -# Copyright 2023 Gentoo Authors +# Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James (2024-06-16) +# Avoid pulling in sys-libs/compiler-rt-sanitizers which fails to build +# See bug #928936. +sys-devel/clang-runtime sanitize + # Sam James (2023-01-29) # Fails to build on combination of ppc* + musl because of mcontext. # libsanitizer needs adapting, bug #892079. diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/deprecated new file mode 100644 index 0000000000..d41b17886e --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/desktop/deprecated new file mode 100644 index 0000000000..d76d864e18 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/desktop/gnome/deprecated new file mode 100644 index 0000000000..5140905bc8 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..8dd6e72c37 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/developer/deprecated new file mode 100644 index 0000000000..d41b17886e --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/musl/deprecated new file mode 100644 index 0000000000..7b217795bc --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/musl/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/musl/hardened/deprecated new file mode 100644 index 0000000000..254125d4eb --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/package.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/package.mask new file mode 100644 index 0000000000..f59665ea74 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/package.mask @@ -0,0 +1,7 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# matoro +# Requires USE=ieee-long-double, so mask on 17.0, #892183 +dev-python/sympy +dev-python/symengine diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64/17.0/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..dfa8e211fd --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/deprecated new file mode 100644 index 0000000000..ee7320f6f7 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/deprecated new file mode 100644 index 0000000000..a4ec403f1a --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/gnome/deprecated new file mode 100644 index 0000000000..32232b7ffd --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..1b0374bba6 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/plasma/deprecated new file mode 100644 index 0000000000..7d25eb99fd --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/plasma/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..225eb9579c --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/desktop/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..31f5006e0c --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/developer/deprecated new file mode 100644 index 0000000000..ee7320f6f7 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/ieee-long-double/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/ieee-long-double/deprecated new file mode 100644 index 0000000000..ee7320f6f7 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/musl/deprecated new file mode 100644 index 0000000000..f439ee75b0 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/musl/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/musl/hardened/deprecated new file mode 100644 index 0000000000..41718e4bc2 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/ppc64le/17.0/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..e4eebc79b2 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/deprecated new file mode 100644 index 0000000000..e49def3f49 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/deprecated new file mode 100644 index 0000000000..6c2be8c5f6 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/deprecated new file mode 100644 index 0000000000..fb525dece1 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..b9f28caee6 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/deprecated new file mode 100644 index 0000000000..8d8c0756f8 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..beb2580f56 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/desktop/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..338c8842c0 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/musl/deprecated new file mode 100644 index 0000000000..892b778d21 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..b7fc6f9231 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/deprecated new file mode 100644 index 0000000000..540d5a7a8b --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/deprecated new file mode 100644 index 0000000000..5e2131dd0c --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/deprecated new file mode 100644 index 0000000000..2364215f95 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..bb4966dda9 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/deprecated new file mode 100644 index 0000000000..41bf9a8a88 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..a6e661c974 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/desktop/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..b551ec79fb --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/musl/deprecated new file mode 100644 index 0000000000..d7c4a35e16 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/lp64d/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..cb41936251 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/multilib/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/multilib/deprecated new file mode 100644 index 0000000000..a4771c0b41 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/multilib/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/20.0/rv64gc/multilib/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..80d5cdfc4e --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/23.0/rv64/lp64d/musl/package.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/23.0/rv64/lp64d/musl/package.mask new file mode 100644 index 0000000000..36b75d044c --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/23.0/rv64/lp64d/musl/package.mask @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors. +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin (2024-06-12) +# rust-bin is available on riscv musl +-dev-lang/rust-bin diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64d/musl/package.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64d/musl/package.mask new file mode 100644 index 0000000000..36b75d044c --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/riscv/23.0/rv64/split-usr/lp64d/musl/package.mask @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors. +# Distributed under the terms of the GNU General Public License v2 + +# Arthur Zamarin (2024-06-12) +# rust-bin is available on riscv musl +-dev-lang/rust-bin diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/deprecated new file mode 100644 index 0000000000..61ac072431 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/s390x/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/s390x/deprecated new file mode 100644 index 0000000000..c11e580933 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/s390x/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/s390x/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..c0dbaaa46c --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/s390/17.0/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..7f3fc08d28 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/deprecated new file mode 100644 index 0000000000..74bb6bf3ae --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/desktop/deprecated new file mode 100644 index 0000000000..18cc090c46 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/developer/deprecated new file mode 100644 index 0000000000..74bb6bf3ae --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/64ul/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..a1b8be4d89 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/deprecated new file mode 100644 index 0000000000..60588d75d0 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/desktop/deprecated new file mode 100644 index 0000000000..954e061651 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/developer/deprecated new file mode 100644 index 0000000000..60588d75d0 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/sparc/17.0/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..f43dfd7a92 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/gnome/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/gnome/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/gnome/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/gnome/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/plasma/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/plasma/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/plasma/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/desktop/plasma/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/developer/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/developer/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/hardened/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/hardened/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/hardened/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/hardened/selinux/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/musl/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/musl/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/musl/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/musl/selinux/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/selinux/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/selinux/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/systemd/merged-usr/deprecated b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/17.0/systemd/merged-usr/deprecated new file mode 100644 index 0000000000..063fe9af04 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/musl/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/musl/package.use.mask index b794980bda..0f0f54b0e2 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/musl/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/musl/package.use.mask @@ -1,6 +1,15 @@ -# Copyright 1999-2020 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License, v2 +# Sam James (2024-06-16) +# Avoid pulling in sys-libs/compiler-rt-sanitizers which fails to build +# See bug #928936. +sys-devel/clang-runtime sanitize + +# Ian Jordan (2024-05-20) +# Does not compile with musl-1.2.4+ +sys-devel/gcc sanitize + # Anthony G. Basile (2020-09-06) # The patch added for 5.39-r1 breaks on musl i686 # file-5.39-seccomp_sandbox.patch is okay diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/musl/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/musl/package.use.stable.mask deleted file mode 100644 index c021f45d85..0000000000 --- a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/musl/package.use.stable.mask +++ /dev/null @@ -1,6 +0,0 @@ -# Copyright 2024 Gentoo Authors -# Distributed under the terms of the GNU General Public License, v2 - -# Andreas K. Hüttel (2024-03-20) -# Does not compile with musl-1.2.4 -sys-devel/gcc sanitize diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.mask index b794980bda..d3fa26567c 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.mask @@ -1,6 +1,10 @@ -# Copyright 1999-2020 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License, v2 +# Ian Jordan (2024-05-20) +# Does not compile with musl-1.2.4+ +sys-devel/gcc sanitize + # Anthony G. Basile (2020-09-06) # The patch added for 5.39-r1 breaks on musl i686 # file-5.39-seccomp_sandbox.patch is okay diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.stable.mask deleted file mode 100644 index c021f45d85..0000000000 --- a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i486/split-usr/musl/package.use.stable.mask +++ /dev/null @@ -1,6 +0,0 @@ -# Copyright 2024 Gentoo Authors -# Distributed under the terms of the GNU General Public License, v2 - -# Andreas K. Hüttel (2024-03-20) -# Does not compile with musl-1.2.4 -sys-devel/gcc sanitize diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/musl/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/musl/package.use.mask index b794980bda..0f0f54b0e2 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/musl/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/musl/package.use.mask @@ -1,6 +1,15 @@ -# Copyright 1999-2020 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License, v2 +# Sam James (2024-06-16) +# Avoid pulling in sys-libs/compiler-rt-sanitizers which fails to build +# See bug #928936. +sys-devel/clang-runtime sanitize + +# Ian Jordan (2024-05-20) +# Does not compile with musl-1.2.4+ +sys-devel/gcc sanitize + # Anthony G. Basile (2020-09-06) # The patch added for 5.39-r1 breaks on musl i686 # file-5.39-seccomp_sandbox.patch is okay diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/musl/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/musl/package.use.stable.mask deleted file mode 100644 index c021f45d85..0000000000 --- a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/musl/package.use.stable.mask +++ /dev/null @@ -1,6 +0,0 @@ -# Copyright 2024 Gentoo Authors -# Distributed under the terms of the GNU General Public License, v2 - -# Andreas K. Hüttel (2024-03-20) -# Does not compile with musl-1.2.4 -sys-devel/gcc sanitize diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.mask index b794980bda..d3fa26567c 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.mask @@ -1,6 +1,10 @@ -# Copyright 1999-2020 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License, v2 +# Ian Jordan (2024-05-20) +# Does not compile with musl-1.2.4+ +sys-devel/gcc sanitize + # Anthony G. Basile (2020-09-06) # The patch added for 5.39-r1 breaks on musl i686 # file-5.39-seccomp_sandbox.patch is okay diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.stable.mask b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.stable.mask deleted file mode 100644 index c021f45d85..0000000000 --- a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/split-usr/musl/package.use.stable.mask +++ /dev/null @@ -1,6 +0,0 @@ -# Copyright 2024 Gentoo Authors -# Distributed under the terms of the GNU General Public License, v2 - -# Andreas K. Hüttel (2024-03-20) -# Does not compile with musl-1.2.4 -sys-devel/gcc sanitize diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/eapi b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/eapi new file mode 100644 index 0000000000..7ed6ff82de --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/eapi @@ -0,0 +1 @@ +5 diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/make.defaults new file mode 100644 index 0000000000..e842848fb6 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/make.defaults @@ -0,0 +1,5 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +CHOST="i686-pc-linux-gnut64" +CHOST_x86="${CHOST}" diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/parent b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/parent new file mode 100644 index 0000000000..1072670e42 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/parent @@ -0,0 +1,2 @@ +.. +../../../../../../features/time64 diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/systemd/eapi b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/systemd/eapi new file mode 100644 index 0000000000..7ed6ff82de --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/systemd/eapi @@ -0,0 +1 @@ +5 diff --git a/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/systemd/parent b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/systemd/parent new file mode 100644 index 0000000000..44f88d3e2d --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/default/linux/x86/23.0/i686/time64/systemd/parent @@ -0,0 +1,2 @@ +.. +../../../../../../../targets/systemd diff --git a/sdk_container/src/third_party/portage-stable/profiles/desc/amdgpu_targets.desc b/sdk_container/src/third_party/portage-stable/profiles/desc/amdgpu_targets.desc index d520807819..8f337b03f6 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/desc/amdgpu_targets.desc +++ b/sdk_container/src/third_party/portage-stable/profiles/desc/amdgpu_targets.desc @@ -1,15 +1,21 @@ -# Copyright 1999-2023 Gentoo Authors. +# Copyright 1999-2024 Gentoo Authors. # Distributed under the terms of the GNU General Public License v2 -# Reference: -# GPU name and Architecture codename: https://github.com/GPUOpen-Tools/device_info/blob/master/DeviceInfo.cpp -# See also: https://www.coelacanth-dream.com/posts/2019/12/30/did-rid-product-matome-p2/#fn:67 +# Reference: GPU name and architecture codename documented by +# GPUOpen-Tools https://github.com/GPUOpen-Tools/device_info/blob/master/DeviceInfo.cpp +# ROCm official document (Instinct accelerator only) https://rocm.docs.amd.com/en/latest/reference/gpu-arch/gpu-arch-spec-overview.html +# Kernel document (note: GC version is not amdgpu gfx target) https://www.kernel.org/doc/html/latest/gpu/amdgpu/driver-misc.html#discrete-gpu-info +# Kernel source code (map of IP version vs amdgpu gfx target) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/amd/amdkfd/kfd_device.c kgd2kfd_probe function +# Mesa drm source code https://gitlab.freedesktop.org/mesa/drm/blob/main/data/amdgpu.ids gfx803 - Fiji GPU, codename fiji, including Radeon R9 Nano/Fury/FuryX, Radeon Pro Duo, FirePro S9300x2, Radeon Instinct MI8 gfx900 - Vega GPU, codename vega10, including Radeon Vega Frontier Edition, Radeon RX Vega 56/64, Radeon RX Vega 64 Liquid, Radeon Pro Vega 48/56/64/64X, Radeon Pro WX 8200/9100, Radeon Pro V320/V340/SSG, Radeon Instinct MI25 gfx906 - Vega GPU, codename vega20, including Radeon (Pro) VII, Radeon Instinct MI50/MI60 gfx908 - CDNA Accelerator, codename arcturus, including AMD Instinct MI100 Accelerator gfx90a - CDNA2 Accelerator, codename aldebaran, including AMD Instinct MI200 series Accelerators +gfx940 - CDNA3 Accelerator, codename aqua_vangaram, MI300A rev 0 +gfx941 - CDNA3 Accelerator, codename aqua_vangaram, MI300X rev 0 +gfx942 - CDNA3 Accelerator, codename aqua_vangaram, MI300A and MI300X rev >=1 gfx1010 - RDNA GPU, codename navi10, including Radeon RX 5700XT/5700/5700M/5700B/5700XTB/5600XT/5600/5600M, Radeon Pro 5700XT/5700, Radeon Pro W5700X/W5700 gfx1011 - RDNA GPU, codename navi12, including Radeon Pro 5600M/V520 gfx1012 - RDNA GPU, codename navi14, including Radeon RX 5500XT/5500/5500M/5500XTB/5300/5300M, Radeon Pro 5500XT/5500M/5300/5300M, Radeon Pro W5500X/W5500/W5500M/W5300M diff --git a/sdk_container/src/third_party/portage-stable/profiles/desc/curl_quic.desc b/sdk_container/src/third_party/portage-stable/profiles/desc/curl_quic.desc new file mode 100644 index 0000000000..372bb9ce8f --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/desc/curl_quic.desc @@ -0,0 +1,7 @@ +# Copyright 1999-2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# This file contains descriptions of CURL_QUIC USE_EXPAND flags for net-misc/curl + +openssl - Use OpenSSL +ngtcp2 - Use ngtcp2 diff --git a/sdk_container/src/third_party/portage-stable/profiles/desc/curl_ssl.desc b/sdk_container/src/third_party/portage-stable/profiles/desc/curl_ssl.desc index 9023283859..3ac2d3b60f 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/desc/curl_ssl.desc +++ b/sdk_container/src/third_party/portage-stable/profiles/desc/curl_ssl.desc @@ -1,8 +1,7 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # This file contains descriptions of CURL_SSL USE_EXPAND flags for net-misc/curl -# spnego - Use SPNEGO fbopenssl - to be added gnutls - Use GnuTLS mbedtls - Use mbed TLS diff --git a/sdk_container/src/third_party/portage-stable/profiles/desc/gpsd_protocols.desc b/sdk_container/src/third_party/portage-stable/profiles/desc/gpsd_protocols.desc index c27e9b112a..31d9dbaf91 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/desc/gpsd_protocols.desc +++ b/sdk_container/src/third_party/portage-stable/profiles/desc/gpsd_protocols.desc @@ -1,4 +1,4 @@ -# Copyright 1999-2019 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # This file contains descriptions of possible protocols for gpsd package. @@ -17,14 +17,10 @@ gpsclock - GPSclock protocol support greis - Javad GREIS protocol support isync - Isync protocol support itrax - iTrax protocol support -mtk3301 - MTK-3301 protocol support navcom - Navcom protocol support -nmea0183 - NMEA protocol support nmea2000 - NMEA2000/CAN support -ntrip - NTRIP protocol support oceanserver - OceanServer protocol support oncore - OnCore protocol support -passthrough - Pass through JSON data rtcm104v2 - RTCM104V2 protocol support rtcm104v3 - RTCM104V3 protocol support sirf - SiRF protocol support diff --git a/sdk_container/src/third_party/portage-stable/profiles/desc/nginx_modules_http.desc b/sdk_container/src/third_party/portage-stable/profiles/desc/nginx_modules_http.desc index ce7da74c63..dd1d7ea38a 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/desc/nginx_modules_http.desc +++ b/sdk_container/src/third_party/portage-stable/profiles/desc/nginx_modules_http.desc @@ -73,4 +73,5 @@ upstream_zone - This module makes it possible to define a shared memory zone tha userid - This module gives out cookies for identification of clients. uwsgi - External module for the uWSGI protocol for python web apps. vhost_traffic_status - This module provides access to virtual host status information. +vod - Adds support for video streaming using DASH, HDS, HLS, MSS. xslt - This module is a filter which converts an XML response with the aid of one or more XSLT templates. diff --git a/sdk_container/src/third_party/portage-stable/profiles/desc/perl_features.desc b/sdk_container/src/third_party/portage-stable/profiles/desc/perl_features.desc new file mode 100644 index 0000000000..22d84ca5b4 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/desc/perl_features.desc @@ -0,0 +1,9 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# This file contains descriptions of PERL_FEATURES USE_EXPAND flags. + +# Keep it sorted. +debug - PERL_FEATURES setting enabling internal debug support in Perl +ithreads - PERL_FEATURES setting enabling interpreter level threads, has some compatibility problems +quadmath - PERL_FEATURES setting enabling 128bit floating point arithmetic via libquadmath diff --git a/sdk_container/src/third_party/portage-stable/profiles/desc/python_single_target.desc b/sdk_container/src/third_party/portage-stable/profiles/desc/python_single_target.desc index 8a9f6479f1..427e206dd1 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/desc/python_single_target.desc +++ b/sdk_container/src/third_party/portage-stable/profiles/desc/python_single_target.desc @@ -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 # This file contains descriptions of PYTHON_SINGLE_TARGET USE_EXPAND flags. @@ -6,4 +6,5 @@ python3_10 - Build for Python 3.10 only python3_11 - Build for Python 3.11 only python3_12 - Build for Python 3.12 only +python3_13 - Build for Python 3.13 only pypy3 - Build for PyPy3 only diff --git a/sdk_container/src/third_party/portage-stable/profiles/desc/python_targets.desc b/sdk_container/src/third_party/portage-stable/profiles/desc/python_targets.desc index 7bde52333b..b48cc57e99 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/desc/python_targets.desc +++ b/sdk_container/src/third_party/portage-stable/profiles/desc/python_targets.desc @@ -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 # This file contains descriptions of PYTHON_TARGETS USE_EXPAND flags. @@ -6,4 +6,5 @@ python3_10 - Build with Python 3.10 python3_11 - Build with Python 3.11 python3_12 - Build with Python 3.12 +python3_13 - Build with Python 3.13 pypy3 - Build with PyPy3 diff --git a/sdk_container/src/third_party/portage-stable/profiles/desc/video_cards.desc b/sdk_container/src/third_party/portage-stable/profiles/desc/video_cards.desc index 0a78c8c126..e54f4b53d7 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/desc/video_cards.desc +++ b/sdk_container/src/third_party/portage-stable/profiles/desc/video_cards.desc @@ -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 # This file contains descriptions of VIDEO_CARDS USE_EXPAND flags. @@ -21,6 +21,7 @@ lima - VIDEO_CARDS setting to build driver for Mali 200/400 video cards mga - VIDEO_CARDS setting to build driver for mga video cards nouveau - VIDEO_CARDS setting to build reverse-engineered driver for nvidia cards nvidia - VIDEO_CARDS setting to build driver for nvidia video cards +nvk - VIDEO_CARDS setting to build nouveau vulkan driver for nvidia cards (Turing and newer) omap - VIDEO_CARDS setting to build DRM driver for TI OMAP video cards qxl - VIDEO_CARDS setting to build driver for qxl (QEMU virtual GPU) panfrost - VIDEO_CARDS setting to build driver for Mali 600/700/800 video cards @@ -42,3 +43,4 @@ virgl - VIDEO_CARDS setting to build driver for virgil (virtual 3D GPU) virtualbox - VIDEO_CARDS setting to build driver for virtualbox emulation vivante - VIDEO_CARDS setting to build etnaviv driver for vivante video cards vmware - VIDEO_CARDS setting to build driver for vmware video cards +zink - VIDEO_CARDS setting to build Zink OpenGL-over-Vulkan Gallium driver diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/package.mask b/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/package.mask index 407bf030c9..e285ef20c4 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/package.mask @@ -1,6 +1,16 @@ # Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Michał Górny (2024-06-07) +# dev-python/tables is broken on big endian platforms. Bug #922235. +dev-python/tables + +# Michał Górny (2024-06-05) +# media-libs/exempi is seriously broken on big endian platforms. +# https://gitlab.freedesktop.org/libopenraw/exempi/-/merge_requests/8#note_2277243 +dev-python/python-xmp-toolkit +media-libs/exempi + # matoro (2024-01-09) # Test failures on BE (#920353, #902191) net-misc/nextcloud-client diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/package.use.mask index a83df9315c..7190612223 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/package.use.mask @@ -1,6 +1,15 @@ -# Copyright 2023 Gentoo Authors +# Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Michał Górny (2024-06-05) +# media-libs/exempi is seriously broken on big endian platforms. +# https://gitlab.freedesktop.org/libopenraw/exempi/-/merge_requests/8#note_2277243 +app-misc/tracker-miners xmp +games-fps/eduke32 xmp +gnome-extra/nemo xmp +media-gfx/eog xmp +media-libs/gexiv2 test + # matoro (2023-11-16) # media-libs/libvpx casualties (#700902) media-video/ffmpeg vpx diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/use.mask b/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/use.mask index 49de7dd81e..792562b3f9 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/features/big-endian/use.mask @@ -1,4 +1,4 @@ -# Copyright 2023 Gentoo Authors +# Copyright 2023-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # matoro (2023-06-30) diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/llvm/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/features/llvm/make.defaults index ce34012226..defd200ce9 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/llvm/make.defaults +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/features/llvm/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/features/llvm/package.use.mask index 2b52ec2721..44b8fcea3c 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/llvm/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/features/llvm/package.use.mask @@ -1,4 +1,4 @@ -# Copyright 2022-2023 Gentoo Authors +# Copyright 2022-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # Sam James (2023-07-22) @@ -8,6 +8,3 @@ sys-devel/binutils pgo # Sam James (2022-09-15) # Works on pure LLVM systems: bug #870211. dev-lang/rust -llvm-libunwind - -# libquadmath is gcc-specific -dev-lang/perl quadmath diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/llvm/use.mask b/sdk_container/src/third_party/portage-stable/profiles/features/llvm/use.mask new file mode 100644 index 0000000000..c742acc9c6 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/profiles/features/llvm/use.mask @@ -0,0 +1,6 @@ +# Copyright 2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# Sam James (2024-05-08) +# libquadmath is gcc-specific +perl_features_quadmath diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.mask b/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.mask index 7773402d23..b9e64b3d1b 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.mask @@ -1,6 +1,16 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Robert Förster (2024-05-06) +# needs mongodb +net-wireless/unifi + +# Robert Förster (2024-05-06) +# bundles old gperftools not supporting musl, +# among not being buildable itself +# bug #906782, #716296, et al. +dev-db/mongodb + # Akinori Hattori (2024-04-14) # musl iconv does not implement required encodings. app-i18n/nkf @@ -160,7 +170,6 @@ net-analyzer/openvas-scanner net-analyzer/ospd-openvas net-misc/grive net-print/pnm2ppa -net-wireless/neard sys-apps/noexec # Giuseppe Foti (2023-05-19) @@ -302,6 +311,7 @@ games-strategy/knights-demo games-strategy/majesty-demo gnome-extra/nautilus-dropbox kde-apps/dolphin-plugins-dropbox +mail-client/thunderbird-bin mate-extra/caja-dropbox media-gfx/brscan4 media-libs/amdgpu-pro-vulkan @@ -332,24 +342,23 @@ net-nntp/sabnzbd net-p2p/resilio-sync net-print/cnijfilter2 net-print/hplip-plugin +net-vpn/microsoft-azurevpnclient sci-chemistry/cara-bin sci-electronics/eagle sci-electronics/labone +sci-libs/mkl sci-mathematics/gimps sci-misc/jupyterlab-desktop-bin sci-misc/netlogo-bin -sci-libs/mkl +sys-apps/intune-portal sys-apps/ipmicfg sys-apps/tas sys-block/hpssacli sys-block/megacli www-apps/chromedriver-bin www-apps/grafana-bin -www-apps/jellyfin www-apps/kibana-bin -www-apps/prowlarr -www-apps/radarr -www-apps/readarr +www-client/firefox-bin www-client/google-chrome www-client/google-chrome-beta www-client/google-chrome-unstable @@ -459,5 +468,3 @@ sys-block/wait-for-dri-devices-rules # rust-bin isn't available on all platforms dev-lang/rust-bin -mail-client/thunderbird-bin -www-client/firefox-bin diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.use.force b/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.use.force index 78001ea4cd..5dc756fc6d 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.use.force +++ b/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.use.force @@ -1,6 +1,11 @@ # Copyright 1999-2024 Gentoo Authors. # Distributed under the terms of the GNU General Public License v2 +# Sam James (2024-06-03) +# Poor rendering performance otherwise (bug #931215) but it doesn't +# work on musl. +kde-plasma/kwin -caps + # Violet Purcell (2023-04-25) # SBCL Upstream does not provide musl binaries for bootstrap, use CLisp. dev-lisp/sbcl system-bootstrap diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.use.mask index 07d0f014aa..9cb4b9e5ab 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/features/musl/package.use.mask @@ -1,6 +1,35 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Sam James (2024-06-03) +# Poor rendering performance otherwise (bug #931215) but it doesn't +# work on musl. +kde-plasma/kwin caps + +# Violet Purcell (2024-05-15) +# Python does not support JIT on musl, see +# https://peps.python.org/pep-0744/#support. +dev-lang/python jit + +# Robert Förster (2024-05-06) +# dev-db/mongodb is masked on musl +dev-libs/mongo-c-driver test +dev-php/pecl-mongodb test +dev-python/pymongo test-full +net-analyzer/zmap mongo + +# Andrew Ammerlaan (2024-04-25) +# No Level-Zero on musl +sys-apps/hwloc l0 + +# Paul Zander (2024-04-20) +# Renderdoc masked on musl, bug #853856 +media-gfx/blender renderdoc + +# Paul Zander (2024-04-20) +# Support for L0 needs RTLD_DEEPBIND, which does not exist on musl. +media-gfx/blender oneapi + # Akinori Hattori (2024-04-15) # app-i18n/nkf is masked on musl app-i18n/multiskkserv test @@ -131,6 +160,7 @@ net-misc/iputils rarpd # Sam James (2021-11-20) # Pulls in po4a which doesn't seem to work on musl (wants /usr/bin/locale) app-arch/dpkg nls +app-crypt/loop-aes-losetup nls app-emulation/guestfs-tools doc app-emulation/libguestfs doc app-text/bibletime doc diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/prefix/standalone/kernel-2.6.16+/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/features/prefix/standalone/kernel-2.6.16+/package.use.mask index b838f9fa82..266afd1a1e 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/prefix/standalone/kernel-2.6.16+/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/features/prefix/standalone/kernel-2.6.16+/package.use.mask @@ -1,4 +1,4 @@ -# Copyright 1999-2022 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # Benda Xu (2019-10-14) @@ -6,7 +6,6 @@ # without checking. That results on build time failure, because we have # stripped away F_DUPFD_CLOEXEC from glibc for this profile. media-libs/mesa gles2 llvm -media-libs/libepoxy egl # Benda Xu (2018-02-21) # We are on an old kernel that only glibc-2.19 is supported. That glibc does diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/time64/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/features/time64/make.defaults index 993dd21b61..0edc40fa68 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/time64/make.defaults +++ b/sdk_container/src/third_party/portage-stable/profiles/features/time64/make.defaults @@ -1,3 +1,15 @@ # Copyright 2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Many profiles and stages override CFLAGS etc, and need then to eat their +# own dogfood. For those who don't... +__COMMON_FLAGS_TIME64="-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64" + +CFLAGS="${CFLAGS} ${__COMMON_FLAGS_TIME64} -Werror=implicit-function-declaration -Werror=implicit-int -Werror=incompatible-pointer-types -Werror=return-type -Werror=int-conversion" +CXXFLAGS="${CXXFLAGS} ${__COMMON_FLAGS_TIME64}" +FCFLAGS="${FCFLAGS} ${__COMMON_FLAGS_TIME64}" +FFLAGS="${FFLAGS} ${__COMMON_FLAGS_TIME64}" + +# We need to switch this explicitly on since it's explicitly disabled +# in profiles otherwise. +enable_year2038="yes" diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/wd40/package.mask b/sdk_container/src/third_party/portage-stable/profiles/features/wd40/package.mask index 999cc6d4ee..8907507bef 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/wd40/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/features/wd40/package.mask @@ -68,6 +68,7 @@ dev-python/jupyter-lsp dev-python/jupyter-server dev-python/jupyter-server-mathjax dev-python/jupyter-server-terminals +dev-python/jupyterlab-widgets dev-python/jupyterlab-server dev-python/jupyterlab dev-python/keyring @@ -104,6 +105,8 @@ dev-python/pyfuse3 dev-python/pymdown-extensions dev-python/pyspelling dev-python/pyspnego +dev-python/pyproject-fmt +dev-python/pyproject-fmt-rust dev-python/pytest-jupyter dev-python/pytest-localftpserver dev-python/pytest-salt-factories diff --git a/sdk_container/src/third_party/portage-stable/profiles/features/wd40/package.use.mask b/sdk_container/src/third_party/portage-stable/profiles/features/wd40/package.use.mask index 4d70f8b959..b253ee7d0d 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/features/wd40/package.use.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/features/wd40/package.use.mask @@ -87,6 +87,7 @@ dev-libs/tree-sitter-c-sharp test dev-libs/tree-sitter-cpp test dev-libs/tree-sitter-css test dev-libs/tree-sitter-embedded-template test +dev-libs/tree-sitter-gleam test dev-libs/tree-sitter-go test dev-libs/tree-sitter-haskell test dev-libs/tree-sitter-html test @@ -95,15 +96,22 @@ dev-libs/tree-sitter-javascript test dev-libs/tree-sitter-jsdoc test dev-libs/tree-sitter-json test dev-libs/tree-sitter-julia test +dev-libs/tree-sitter-lua test +dev-libs/tree-sitter-markdown test +dev-libs/tree-sitter-markdown-inline test dev-libs/tree-sitter-ocaml test dev-libs/tree-sitter-php test dev-libs/tree-sitter-python test dev-libs/tree-sitter-ql test +dev-libs/tree-sitter-query test dev-libs/tree-sitter-ruby test dev-libs/tree-sitter-rust test dev-libs/tree-sitter-scala test dev-libs/tree-sitter-tsq test +dev-libs/tree-sitter-tsx test dev-libs/tree-sitter-typescript test +dev-libs/tree-sitter-vim test +dev-libs/tree-sitter-vimdoc test # Sam James (2022-11-19) # GNOME packages pulling in e.g. gjs which then needs Rust. @@ -119,7 +127,6 @@ net-vpn/networkmanager-vpnc gtk # Michał Górny (2022-07-29) # More packages requiring dev-python/cryptography or its revdeps. app-admin/salt keyring neutron -dev-python/dask test dev-python/docker test dev-python/google-api-python-client test dev-python/httpx-socks test @@ -155,6 +162,7 @@ dev-python/anyio test dev-python/httpcore test dev-python/httpx test dev-python/aiohttp-socks test +dev-python/truststore test # WANG Xuerui (2022-05-13) # dev-lang/rust is not available on ${arch} yet. diff --git a/sdk_container/src/third_party/portage-stable/profiles/license_groups b/sdk_container/src/third_party/portage-stable/profiles/license_groups index d9c23c07bc..3f290222e4 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/license_groups +++ b/sdk_container/src/third_party/portage-stable/profiles/license_groups @@ -25,7 +25,7 @@ FSF-APPROVED @GPL-COMPATIBLE AFL-2.1 AFL-3.0 Apache-1.0 Apache-1.1 APSL-2 BSD-4 # Note that the FSF lists these as nonfree: Artistic NOSA Watcom-1.0 # We exclude NOSA and Watcom-1.0, but we keep Artistic because Debian # considers it DFSG-free. -OSI-APPROVED-FREE 0BSD AFL-3.0 AGPL-3 AGPL-3+ Apache-1.1 Apache-2.0 APL-1.0 APSL-2 Artistic Artistic-2 Boost-1.0 BSD BSD-2 CDDL CNRI CPAL-1.0 CPL-1.0 ECL-2.0 EPL-1.0 EPL-2.0 EUPL-1.1 EUPL-1.2 GPL-1 GPL-1+ GPL-2 GPL-2+ GPL-3 GPL-3+ HPND IBM IPAfont ISC LGPL-2 LGPL-2+ LGPL-2.1 LGPL-2.1+ LGPL-3 LGPL-3+ LPL-1.02 LPPL-1.3c MirOS MIT MIT-0 MPL-1.0 MPL-1.1 MPL-2.0 Ms-PL Ms-RL nethack OFL-1.1 OSL-2.1 PHP-3 PHP-3.01 POSTGRESQL PSF-2 QPL-1.0 Sleepycat Unicode-DFS-2016 Unlicense UPL-1.0 UoI-NCSA W3C wxWinLL-3 ZLIB ZPL +OSI-APPROVED-FREE 0BSD AFL-3.0 AGPL-3 AGPL-3+ Apache-1.1 Apache-2.0 APL-1.0 APSL-2 Artistic Artistic-2 Boost-1.0 BSD BSD-2 CDDL CNRI CPAL-1.0 CPL-1.0 ECL-2.0 EPL-1.0 EPL-2.0 EUPL-1.1 EUPL-1.2 GPL-1 GPL-1+ GPL-2 GPL-2+ GPL-3 GPL-3+ HPND IBM IPAfont ISC LGPL-2 LGPL-2+ LGPL-2.1 LGPL-2.1+ LGPL-3 LGPL-3+ LPL-1.02 LPPL-1.3c MirOS MIT MIT-0 MPL-1.0 MPL-1.1 MPL-2.0 Ms-PL Ms-RL nethack OFL-1.1 OSL-2.1 PHP-3 PHP-3.01 POSTGRESQL PSF-2 QPL-1.0 Sleepycat Unicode-3.0 Unicode-DFS-2016 Unlicense UPL-1.0 UoI-NCSA W3C wxWinLL-3 ZLIB ZPL # Misc licenses that are probably free software, i.e. follow the # Free Software Definition at https://www.gnu.org/philosophy/free-sw.html @@ -43,7 +43,7 @@ FREE-SOFTWARE @FSF-APPROVED @OSI-APPROVED-FREE @MISC-FREE # FSF-approved licenses for "free documentation" and "works of # practical use besides software and documentation" (including fonts) -FSF-APPROVED-OTHER Arphic CC-BY-2.0 CC-BY-2.5 CC-BY-3.0 CC-BY-4.0 CC-BY-SA-2.0 CC-BY-SA-2.5 CC-BY-SA-3.0 CC-BY-SA-4.0 FDL-1.1 FDL-1.1+ FDL-1.2 FDL-1.2+ FDL-1.3 FDL-1.3+ Free-Art-1.2 Free-Art-1.3 GPL-1 GPL-1+ GPL-2 GPL-2+ GPL-3 GPL-3+ IPAfont OFL OFL-1.1 OPL +FSF-APPROVED-OTHER Arphic CC-BY-2.0 CC-BY-2.5 CC-BY-3.0 CC-BY-4.0 CC-BY-SA-2.0 CC-BY-SA-2.5 CC-BY-SA-3.0 CC-BY-SA-4.0 FDL-1.1 FDL-1.1+ FDL-1.2 FDL-1.2+ FDL-1.3 FDL-1.3+ Free-Art-1.2 Free-Art-1.3 GPL-1 GPL-1+ GPL-2 GPL-2+ GPL-3 GPL-3+ IPAfont OFL-1.0 OFL-1.1 OPL # Misc licenses for free documents and other works (including fonts) # that follow the definition at https://freedomdefined.org/ but are NOT @@ -69,7 +69,7 @@ FREE @FREE-SOFTWARE @FREE-DOCUMENTS # - IF (and only if) there is an explicit inclusion requirement, # USE=bindist MUST cause a copy of the license to be installed # in a file location compliant with the license -BINARY-REDISTRIBUTABLE @FREE Atmel AVASYS bh-luxi bonnie Broadcom freedist intel-ucode ipw2100-fw ipw2200-fw ipw3945 ISSL JSON linux-fw-redistributable LSI-tw_cli Mellanox-AS-IS MicroChip-SDCC no-source-code NOSA NVIDIA-r1 NVIDIA-r2 qlogic-fibre-channel-firmware shmux unRAR +BINARY-REDISTRIBUTABLE @FREE Atmel AVASYS bh-luxi bonnie Broadcom freedist intel-ucode ipw2100-fw ipw2200-fw ISSL JSON linux-fw-redistributable LSI-tw_cli Mellanox-AS-IS MicroChip-SDCC no-source-code NOSA NVIDIA-r1 NVIDIA-r2 qlogic-fibre-channel-firmware shmux unRAR ###################################################################### @@ -81,7 +81,7 @@ OSI-APPROVED @OSI-APPROVED-FREE @OSI-APPROVED-NONFREE # License agreements that try to take away your rights. These are more # restrictive than "all-rights-reserved" or require explicit approval. -EULA 2dboy-EULA AMD-GPU-PRO-EULA android AnyDesk-TOS Aseprite-EULA baudline bestcrypt CAPYBARA-EULA Coherent-Graphics Dell-EULA ETQW f.lux FAH-EULA-2014 Flightradar24 Gameplay-Group-EULA geekbench genymotion GIMPS GOG-EULA google-chrome Intel-SDP Introversion JoyPixels LOKI-EULA MakeMKV-EULA Microsemi microsoft-edge Microsoft-vscode Mojang MTA-0.5 NVIDIA-CUDA NVIDIA-SDK Ookla OPERA-2018 PAPERS-PLEASE PassMark-EULA PICO-8 Primate-Plunge PUEL-11 Q3AEULA-20000111 QUAKE4 RAR sfpg SPS Steam supermicro Synology teamspeak3 teamspeak5 TeamViewer THINKTANKS TIK ubiquiti ut2003 ut2003-demo Vivaldi worklog-assistant WPS-EULA zi-labone +EULA 2dboy-EULA AMD-GPU-PRO-EULA android AnyDesk-TOS Aseprite-EULA baudline bestcrypt CAPYBARA-EULA Coherent-Graphics Dell-EULA ETQW f.lux FAH-EULA-2014 Flightradar24 Gameplay-Group-EULA geekbench genymotion GIMPS GOG-EULA google-chrome Intel-SDP Introversion JoyPixels LOKI-EULA MakeMKV-EULA Microsemi microsoft-azurevpnclient microsoft-edge Microsoft-vscode Mojang MTA-0.5 NVIDIA-CUDA NVIDIA-SDK Ookla OPERA-2018 PAPERS-PLEASE PassMark-EULA PICO-8 Primate-Plunge PUEL-11 Q3AEULA-20000111 QUAKE4 RAR sfpg SPS Steam supermicro Synology teamspeak3 teamspeak5 TeamViewer THINKTANKS TIK ubiquiti ut2003 ut2003-demo Vivaldi worklog-assistant WPS-EULA zi-labone # Deprecated license labels, used by repoman and pkgcheck #DEPRECATED (currently none) diff --git a/sdk_container/src/third_party/portage-stable/profiles/package.deprecated b/sdk_container/src/third_party/portage-stable/profiles/package.deprecated index ef557ec07d..0477231a60 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/package.deprecated +++ b/sdk_container/src/third_party/portage-stable/profiles/package.deprecated @@ -17,6 +17,11 @@ #--- END OF EXAMPLES --- +# Michał Górny (2024-06-15) +# Stop-gap compatibility package. Upstreams really need to move away +# from the removed cgi module rather than rely on this. +dev-python/legacy-cgi + # Volkmar W. Pogatzki (2024-03-10) # ant-core should no longer be ussed as of version 1.10.14 or higher. # It is now completely integrated in dev-java/ant and will be removed after a @@ -53,15 +58,6 @@ net-p2p/bitcoind # Bug 915779 dev-qt/qtscript:5 -# Michał Górny (2023-06-18) -# Superseded by dev-python/pdm-backend. The migration guide is at: -# https://pdm-backend.fming.dev/migration/ -dev-python/pdm-pep517 - -# Sam James (2023-06-18) -# Merged into dev-perl/Type-Tiny. Please depend on that instead. -dev-perl/Type-Tie - # Andreas Sturmlechner (2023-06-10) # Obsolete transitional meta package. Switch to media-libs/libpulse # which ensures a sound server is installed via PDEPEND. diff --git a/sdk_container/src/third_party/portage-stable/profiles/package.mask b/sdk_container/src/third_party/portage-stable/profiles/package.mask index 3654f7ca45..de3e1a56af 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/package.mask @@ -33,51 +33,529 @@ #--- END OF EXAMPLES --- -# Arthur Zamarin (2024-04-20) -# EAPI6 package, with no reverse dependencies. Not really maintained -# since gentoo's transition to git. Distfile is fetch and mirror -# restricted, and based on comment in ebuild, the source isn't stable -# and we can lose the only source for distfile. -# Removal on 2024-05-20, bug #930346. -sys-block/megamgr +# Michał Górny (2024-07-01) +# Refuses to boot if initramfs was built with an older systemd version +# that enabled "cgroups v1". Bug #935261. +>=sys-apps/systemd-256 -# Maciej Barć (2024-04-20) -# No reverse dependencies, old packages for mono, uses abandoned mono.eclass. -# Dotnet Project is not willing to take up those packages. -# Open bugs: #679440 -# Removal on 2024-05-20 -dev-dotnet/monocalendar -dev-dotnet/ndesk-dbus -dev-dotnet/ndesk-dbus-glib +# Sam James (2024-06-25) +# Subvolume printing is broken: https://github.com/kdave/btrfs-progs/issues/829 +=sys-fs/btrfs-progs-6.9.1 -# Arthur Zamarin (2024-04-19) -# EAPI=6, library only without any reverse dependencies, uses -# deprecated go eclasses, maintainer-needed. -# Removal on 2024-05-19, bug #930249 -dev-go/qr -dev-go/twofactor +# Sam James (2024-06-25) +# The symbol versioning "fix" breaks anything built with 3.0.0. +=dev-libs/libassuan-3.0.1 -# Andrew Ammerlaan (2024-04-18) -# Upstream gone, unfetchable, stuck on EAPI 6. Bug 605796 -# Removal on 2024-05-18 -sci-visualization/spectromatic +# NHOrus (2024-06-24) +# Masked for removal in 30 days. +# It's a dependency of cinelerra, written for cinelerra. +# We don't ship cinelerra. It should be removed when we removed cinelerra +# +# Bugs #871387, #907261, #712480, #931765. +media-libs/libmpeg3 -# Fabian Groffen (2024-04-16) -# Official latest Python support 3.8, replacement app-metrics/go-carbon -# is more performant and designed to be a drop-in replacement. -# Removal on 2024-05-16, bug #929444 -dev-python/carbon +# Arthur Zamarin (2024-06-22) +# EAPI=6, no reverse-dependencies, various issues with modern C, +# installs libtools files. +# Removal on 2024-07-22. Bugs #934689, #741440, #849920, #832789, #862714, #828579. +sci-libs/h5hut -# Fabian Groffen (2024-04-13) -# Python wrapper around liblmsensors, no reverse dependencies -# Removal on 2024-05-13, bug #929495 -dev-python/PySensors +# Arthur Zamarin (2024-06-22) +# EAPI=6, failing tests, fails to compile in various envs, various +# QA issues. +# Removal on 2024-07-22. Bugs #934687, #928028, #862687, #836104, #741430, #811561, #526442. +sci-libs/coinor-os -# Arthur Zamarin (2024-04-12) -# EAPI6. Fails to compile with go versions in tree. Upstream is archived. -# Uses deprecated go eclasses. Maintainer needed, no rev deps. -# Removal: 2024-05-12. Bugs #794913, #679348, #771072, #844607. -app-emulation/runv +# Michał Górny (2024-06-21) +# An obsolete timezone distribution for Python. No revdeps left. +# Removal on 2024-07-21. Bug #934681. +dev-python/pytzdata + +# Arthur Zamarin (2024-06-21) +# EAPI=6, not maintained in gentoo for a long time, fails to +# configure. +# Removal on 2024-07-21. Bugs #934680, #677444, #898100. +sci-astronomy/aatm + +# Arthur Zamarin (2024-06-21) +# Last dev-php/* EAPI=6 packages, and reverse dependencies of them. +# composer has active security vulnerabilities. Others are waiting +# for version bumps, and unbundling of dependencies. +# Removal on 2024-07-21. Bugs #934666. +dev-php/phpDocumentor +dev-php/phpcov +dev-php/phpdepend +dev-php/phpdocumentor-reflection-common +dev-php/phpdocumentor-reflection-docblock +dev-php/phpdocumentor-type-resolver +dev-php/stringparser_bbcode +dev-php/symfony-config +dev-php/symfony-console +dev-php/symfony-dependency-injection +dev-php/symfony-event-dispatcher +dev-php/symfony-yaml +dev-php/composer + +# Hans de Graaff (2024-06-21) +# Obsolete slot. Please use a newer slot instead. +# Masked for removal on 2024-07-21. +dev-ruby/public_suffix:4 + +# Martin Dummer (2024-06-21) +# Upstream dead, was an optional package for a reverse dependency +# which is gone. +# Removal on 2024-07-21. Bug #791904 +media-video/vdr2jpeg + +# James Le Cuirot (2024-06-20) +# Ancient, dead upstream, X11-based, probably doesn't work any more, and there +# are better ways of running games in different sessions now. +# Removal on 2024-07-20. Bug #934640. +games-util/xgame +games-util/xgame-gtk2 + +# James Le Cuirot (2024-06-20) +# Apparently a good game, but you cannot buy the full Linux version any more. +# Get the HD version from Steam or the Windows original from GOG instead. +# Removal on 2024-07-20. Bug #934637. +games-strategy/majesty-demo + +# Arthur Zamarin (2024-06-20) +# EAPI=6, keyworded for x86 only (making it hard to debug), has +# open bugs for modern C and not using correct toolchain commands. +# Removal on 2024-07-20. Bugs #934621, #925090, #724078, #727438. +dev-debug/ald + +# Arthur Zamarin (2024-06-20) +# EAPI=6, no reverse dependencies, waiting for a version bump. +# Removal on 2024-07-20. Bugs #934619, #730758, #713760. +media-gfx/dawn + +# Jakov Smolić (2024-06-18) +# Outdated by several versions, very difficult to package due to the +# complicated Cargo dependency management. +# Removal on 2024-07-18. Bug #922378. +app-emulation/cloud-hypervisor + +# Michał Górny (2024-06-17) +# A compatibility shim for ancient versions of flake8. Upstream project +# is gone. No revdeps. +# Removal on 2024-07-17. Bug #934466. +dev-python/flake8-polyfill + +# Hans de Graaff (2024-06-17) +# Obsolete slot with failing tests. Use the newer slot instead. No +# reverse dependencies. Masked for removal on 2024-07-17. +dev-ruby/net-imap:0 + +# Andreas Sturmlechner (2024-06-16) +# No release since 2021-06-10 and effectively declared unmaintained by +# upstream since then; now conflicting with Plasma 6 by pulling in old +# kde-plasma/libksysguard:5. Removal on 2024-08-24. +kde-plasma/ksysguard + +# Andreas Sturmlechner (2024-06-16) +# After most protocol support is gone, there is barely anything usable +# left in kde-apps/kopete. It is also unmaintained and still depends on +# kf5-portingaids, as well as conflicting kde-apps in slot 5. bug #760555 +# Removal on 2024-07-24. +kde-apps/kopete + +# Arthur Zamarin (2024-06-15) +# EAPI=6, no reverse dependencies, not packaged on other distributions, +# waiting for a version bump (which is hard since ebuild used debian +# patches). Not really maintained in Gentoo for a long time. +# Removal on 2024-07-15. Bugs #934366, #871378, #716084, #924302. +sci-astronomy/predict + +# Arthur Zamarin (2024-06-15) +# EAPI=6, no reverse dependencies, manifest doesn't match upstream. +# Removal on 2024-07-15. Bugs #934365, #832746. +sci-chemistry/xds-bin + +# Cédric Krier (2023-06-15) +# critical regression with potential data loss: +# https://lists.mercurial-scm.org/pipermail/mercurial-devel/2024-June/297954.html +# Bug #934138 +~dev-vcs/mercurial-6.7 +~dev-vcs/mercurial-6.7.1 +~dev-vcs/mercurial-6.7.2 +~dev-vcs/mercurial-6.7.3 + +# Maciej Barć (2024-06-14) +# EAPI=6, now shipped in official gambit and so it fails to merge from file +# collision. Bug: #832334 +# Removal on 2024-07-14. +dev-scheme/termite + +# Arthur Zamarin (2024-06-14) +# EAPI=6, no reverse dependencies, maintainer-needed, installation +# blocked by iproute2. +# Removal on 2024-07-14. Bugs #934242, #430816. +net-misc/arpd + +# Arthur Zamarin (2024-06-14) +# EAPI=6, many compilation issues, upstream is gone, not maintained for +# many years. +# Removal on 2024-07-14. Bugs #934240. +sci-electronics/vbs + +# Arthur Zamarin (2024-06-14) +# EAPI=6, dead upstream website, Gentoo is last distribution to +# package it. +# Removal on 2024-07-14. Bug #934232. +sci-chemistry/xyza2pipe + +# Arthur Zamarin (2024-06-14) +# EAPI=6, not maintained for ~7 years in gentoo, waiting for version +# bump. Fetch restricted, and fails to build after manual fetch. +# Removal on 2024-07-14. Bugs #934228, #686860, #686858, #686856. +sci-chemistry/namd + +# Arthur Zamarin (2024-06-14) +# EAPI=6, not maintained in Gentoo for a long time. procheck is +# fetch restricted, and the file you download from upstream +# doesn't match size and manifests. aqua depends on procheck. +# Removal on 2024-07-14. Bugs #928067, #928068. +sci-chemistry/aqua +sci-chemistry/procheck + +# Arthur Zamarin (2024-06-14) +# EAPI=6, maintainer-needed, no reverse dependencies. +# Removal on 2024-07-14. Bugs #934227, #898840. +www-misc/log-toolkit + +# Arthur Zamarin (2024-06-12) +# EAPI=6, maintainer needed, no reverse dependencies. Not maintained in +# gentoo for a long time. +# Removal on 2024-07-12. Bugs #934156, #636422. +net-misc/bfgminer + +# Arthur Zamarin (2024-06-12) +# EAPI=6, library with no reverse dependencies, fails tests, has +# issues with modern C. +# Removal on 2024-07-12. Bugs #934133, #725622, #813240. +sci-libs/o2scl + +# Viorel Munteanu (2024-06-11) +# dev-php/pear, dev-php/PEAR-* and their reverse dependencies: mask for removal +# in 30 days. +# They are all unmaintained, most of the ebuilds are still EAPI 6, and together +# they have around 40 bugs. +# Removal: 2024-07-11. Bug #933998. +dev-php/PEAR-Cache +dev-php/PEAR-Cache_Lite +dev-php/PEAR-Console_Getargs +dev-php/PEAR-Crypt_CHAP +dev-php/PEAR-Crypt_HMAC +dev-php/PEAR-Crypt_HMAC2 +dev-php/PEAR-DB +dev-php/PEAR-DB_DataObject +dev-php/PEAR-Date +dev-php/PEAR-File +dev-php/PEAR-File_Archive +dev-php/PEAR-File_Find +dev-php/PEAR-File_Fortune +dev-php/PEAR-File_Gettext +dev-php/PEAR-File_SMBPasswd +dev-php/PEAR-HTML_AJAX +dev-php/PEAR-HTML_CSS +dev-php/PEAR-HTML_Common +dev-php/PEAR-HTML_Common2 +dev-php/PEAR-HTML_Javascript +dev-php/PEAR-HTML_QuickForm2 +dev-php/PEAR-HTML_Table +dev-php/PEAR-HTML_Table_Matrix +dev-php/PEAR-HTML_Template_Flexy +dev-php/PEAR-HTML_Template_Sigma +dev-php/PEAR-HTTP +dev-php/PEAR-HTTP_Header +dev-php/PEAR-HTTP_Request2 +dev-php/PEAR-HTTP_Session2 +dev-php/PEAR-Image_Color2 +dev-php/PEAR-Image_GraphViz +dev-php/PEAR-Image_IPTC +dev-php/PEAR-Image_Text +dev-php/PEAR-Log +dev-php/PEAR-MDB +dev-php/PEAR-MDB2 +dev-php/PEAR-MDB2_Driver_mssql +dev-php/PEAR-MDB2_Driver_mysqli +dev-php/PEAR-MDB2_Driver_oci8 +dev-php/PEAR-MDB2_Driver_pgsql +dev-php/PEAR-MIME_Type +dev-php/PEAR-Mail +dev-php/PEAR-Mail_mimeDecode +dev-php/PEAR-Math_BigInteger +dev-php/PEAR-Net_DNS +dev-php/PEAR-Net_DNS2 +dev-php/PEAR-Net_DNSBL +dev-php/PEAR-Net_IDNA2 +dev-php/PEAR-Net_IPv4 +dev-php/PEAR-Net_IPv6 +dev-php/PEAR-Net_LDAP2 +dev-php/PEAR-Net_POP3 +dev-php/PEAR-Net_Ping +dev-php/PEAR-Net_SmartIRC +dev-php/PEAR-Net_Traceroute +dev-php/PEAR-Net_URL +dev-php/PEAR-Net_URL2 +dev-php/PEAR-Net_UserAgent_Detect +dev-php/PEAR-Numbers_Words +dev-php/PEAR-OLE +dev-php/PEAR-PHP_Beautifier +dev-php/PEAR-PHP_Debug +dev-php/PEAR-Pager +dev-php/PEAR-Services_JSON +dev-php/PEAR-Services_TinyURL +dev-php/PEAR-Services_W3C_CSSValidator +dev-php/PEAR-Spreadsheet_Excel_Writer +dev-php/PEAR-System_Command +dev-php/PEAR-Text_CAPTCHA +dev-php/PEAR-Text_CAPTCHA_Numeral +dev-php/PEAR-Text_Figlet +dev-php/PEAR-Text_Highlighter +dev-php/PEAR-Text_Password +dev-php/PEAR-Text_Wiki +dev-php/PEAR-Text_Wiki_BBCode +dev-php/PEAR-Text_Wiki_Mediawiki +dev-php/PEAR-Validate +dev-php/PEAR-Var_Dump +dev-php/PEAR-XML_Parser +dev-php/PEAR-XML_RSS +dev-php/PEAR-XML_Serializer +dev-php/YAML +dev-php/cphplib +www-apps/dotproject + +# Michał Górny (2024-06-10) +# Merged into dev-python/rapidfuzz. No revdeps left. +# Removal on 2024-07-10. Bug #934002. +dev-python/rapidfuzz-capi + +# Viorel Munteanu (2024-06-10) +# Masked for removal in 30 days. EAPI 6, unmaintained, last upstream +# release in 2011, no upstream activity since 2013. +# There are other static generators in gentoo, like www-apps/hugo or +# app-text/txt2tags. +# Removal: 2024-07-10. Bugs #295842, #526340. +www-apps/nanoblogger + +# James Le Cuirot (2024-06-09) +# Long dead upstream. Probably broken. Use games-emulation/dolphin instead. +# Removal on 2024-07-09. Bug #739140. +games-emulation/gcube + +# James Le Cuirot (2024-06-09) +# Super ancient and broken 32-bit only port. Package ECWolf instead. +# Removal on 2024-07-09. Bug #926467. +games-fps/wolfgl + +# James Le Cuirot (2024-06-09) +# Download no longer available, license prevents mirroring. +# Removal on 2024-07-09. Bug #791115. +games-strategy/darwinia-demo + +# Alfredo Tupone (2024-06-09) +# Not ready for testing +>=dev-lang/ocaml-5 +dev-ml/sexplib0:0/0.17 +dev-ml/ocaml_intrinsics:0/0.17 +dev-ml/ocaml_intrinsics_kernel:0/0.17 +dev-ml/base:0/0.17 +dev-ml/fieldslib:0/0.17 +dev-ml/stdio:0/0.17 +>=dev-ml/ocaml-compiler-libs-0.17 +>=dev-ml/ppxlib-0.32.1 +dev-ml/ppx_cold:0/0.17 +dev-ml/ppxlib_jane +dev-ml/ppx_compare:0/0.17 +dev-ml/ppx_enumerate:0/0.17 +dev-ml/ppx_globalize:0/0.17 +dev-ml/ppx_sexp_conv:0/0.17 +dev-ml/ppx_hash:0/0.17 +dev-ml/ppx_base:0/0.17 +dev-ml/ppx_fields_conv:0/0.17 +dev-ml/ppx_fixed_literal:0/0.17 +dev-ml/ppx_here:0/0.17 +dev-ml/ppx_let:0/0.17 +dev-ml/ppx_sexp_message:0/0.17 +dev-ml/ppx_sexp_value:0/0.17 +dev-ml/ppx_assert:0/0.17 +dev-ml/jane-street-headers:0/0.17 +dev-ml/ppx_optcomp:0/0.17 +dev-ml/jst-config:0/0.17 +dev-ml/time_now:0/0.17 +dev-ml/ppx_inline_test:0/0.17 +dev-ml/ppx_bench:0/0.17 +dev-ml/splittable_random:0/0.17 +dev-ml/base_quickcheck:0/0.17 +dev-ml/ppx_stable:0/0.17 +dev-ml/ppx_string:0/0.17 +dev-ml/ppx_expect:0/0.17 +dev-ml/parsexp:0/0.17 +dev-ml/sexplib:0/0.17 +dev-ml/variantslib:0/0.17 +dev-ml/ppx_variants_conv:0/0.17 +dev-ml/ppx_log:0/0.17 +dev-ml/ppx_ignore_instrumentation:0/0.17 +dev-ml/typerep:0/0.17 +dev-ml/ppx_typerep_conv:0/0.17 +dev-ml/ppx_tydi:0/0.17 +dev-ml/capitalization:0/0.17 +dev-ml/ppx_string_conv:0/0.17 +dev-ml/ppx_stable_witness:0/0.17 +dev-ml/ppx_pipebang:0/0.17 +dev-ml/ppx_optional:0/0.17 +dev-ml/ppx_module_timer:0/0.17 +dev-ml/ppx_disable_unused_warnings:0/0.17 +dev-ml/ppx_custom_printf:0/0.17 +dev-ml/bin_prot:0/0.17 +dev-ml/ppx_bin_prot:0/0.17 +dev-ml/ppx_jane:0/0.17 +dev-ml/gel:0/0.17 +dev-ml/ppx_diff:0/0.17 +dev-ml/int_repr:0/0.17 +dev-ml/base_bigstring:0/0.17 +dev-ml/core:0/0.17 +dev-ml/uopt:0/0.17 +dev-ml/core_kernel:0/0.17 +dev-ml/timezone:0/0.17 +dev-ml/sexp_pretty:0/0.17 +dev-ml/expect_test_helpers_core:0/0.17 +dev-ml/core_unix:0/0.17 +dev-ml/async_kernel:0/0.17 +dev-ml/async_unix:0/0.17 +dev-ml/protocol_version_header:0/0.17 +dev-ml/async_rpc_kernel:0/0.17 +dev-ml/async_log:0/0.17 +dev-ml/textutils:0/0.17 +dev-ml/async:0/0.17 +>=dev-ml/labltk-8.06.14 +dev-ml/patience_diff:0/0.17 +>=dev-ml/ppx_deriving-6.0.2 + +# Arthur Zamarin (2024-06-08) +# EAPI=6, waiting for a version bump, not maintained for many years. +# Removal on 2024-07-08. Bug #933850. +www-apps/wiliki + +# Arthur Zamarin (2024-06-08) +# Various apache modules with no reverse dependencies, EAPI=6, +# some maintainer-needed. +# Removal on 2024-07-08. Bugs #933847, #742452. +www-apache/mod_vdbh +www-apache/modsec-flameeyes + +# Arthur Zamarin (2024-06-08) +# EAPI=6, maintainer-needed, no reverse dependencies. +# Removal on 2024-07-08. Bugs #933846, #598678, #916203. +sys-power/powernowd + +# Arthur Zamarin (2024-06-08) +# EAPI=6, no reverse dependencies, maintainer-needed, various QA issues. +# Removal on 2024-07-08. Bugs #933843, #695068, #677432. +net-analyzer/check_mk_agent + +# Arthur Zamarin (2024-06-08) +# EAPI=6, no reverse dependencies, fails to compile with LLVM or musl, +# various QA issues. +# Removal on 2024-07-08. Bugs #933837, #832891, #740364, #751697, #403627. +media-sound/herrie + +# Arthur Zamarin (2024-06-08) +# EAPI=6, fetch restricted, waiting for a version bump. +# Removal on 2024-07-08. Bug #933836. +sci-libs/coinhsl + +# Michał Górny (2024-06-08) +# Prereleases of Xfce 4.20. Masking upon popular request, due to +# a large number of regressions in every new release. +>=dev-build/xfce4-dev-tools-4.19 +>=xfce-base/exo-4.19 +>=xfce-base/garcon-4.19 +>=xfce-base/libxfce4ui-4.19 +>=xfce-base/libxfce4util-4.19 +>=xfce-base/thunar-4.19 +>=xfce-base/tumbler-4.19 +>=xfce-base/xfce4-appfinder-4.19 +>=xfce-base/xfce4-panel-4.19 +>=xfce-base/xfce4-power-manager-4.19 +>=xfce-base/xfce4-session-4.19 +>=xfce-base/xfce4-settings-4.19 +>=xfce-base/xfconf-4.19 +>=xfce-base/xfdesktop-4.19 + +# David Seifert (2024-06-08) +# Last release 12 years ago, clearly abandoned upstream, EAPI 6, no +# other major distro still carries this. +# Removal on 2024-07-08. Bug #933825. +app-i18n/imhangul + +# Arthur Zamarin (2024-06-08) +# EAPI=6, not maintained since cvs days. Keyworded for x86 and ppc +# only. Fails to compile with modern C. +# Removal on 2024-07-08. Bugs #933824, #927783. +net-p2p/gnut + +# Arthur Zamarin (2024-06-07) +# EAPI=6, no reverse dependencies, failing tests, various QA issues. +# Removal on 2024-07-07. Bugs #933768, #849923, #882403, #837020, +# #741444, #831092, #862717. +sci-libs/h5part + +# Maciej Barć (2024-06-05) +# Old and experimental Scheme compiler. +# Bugs: 870472 and 906863 +# Removal on 2024-07-05. +dev-scheme/scheme48 + +# Maciej Barć (2024-06-04) +# Deprecated git integration backend of "app-emacs/magit". +# No longer supported by upstream. Fails to compile (bug 928920). +# Removal on 2024-07-04. +app-emacs/libegit2 + +# Mike Gilbert (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 (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 (2024-05-31) +# EAPI=6, maintainer-needed, incorrect LICENSE, fails to compile with +# clang. +# Removal on 2024-06-30. Bugs #933241, #889912, #880267, #562822, #930500. +net-mail/gnubiff + +# Arthur Zamarin (2024-05-31) +# EAPI=6, no activity upstream, maintianer-needed. +# Removal on 2024-06-30. Bugs #933239, #828068. +app-emulation/phpvirtualbox + +# Sam James (2024-05-28) +# Breaks reverse dependencies like protobuf-c (bug #932857) and protobuf-26.1 +# itself isn't compatible with this abseil-cpp version (bug #932848). +# In addition, we still need to establish a new approach like a virtual +# for protobuf because of its abseil dependency - see the discussion in bug #912819. +~dev-libs/protobuf-26.1 +~dev-cpp/abseil-cpp-20240116.2 + +# Sam James (2024-04-28) +# Masked for testing. Tracker bug: bug #930805. +>=sys-libs/ncurses-6.5 # Michał Górny (2024-04-11) # Contains a bug that could render the kernel fail to boot. @@ -89,85 +567,15 @@ app-emulation/runv =sys-kernel/vanilla-kernel-6.6.26 =sys-kernel/vanilla-kernel-6.8.5 -# Volkmar W. Pogatzki (2024-04-08) -# Obsolete java-vm, bugs #848804 #830248. -# Removal on 2024-05-08 -dev-java/icedtea-bin - -# Volkmar W. Pogatzki (2024-04-08) -# Java libraries without consumers. -# Removal on 2024-05-08, bugs #853100 #716228. -dev-java/gin -dev-java/gwt -dev-java/validation-api - -# Ben Kohler (2024-04-07) -# Abandoned upstream long ago in favor of Unifi Protect (running only on an -# official Unifi appliance. Likely contains lots of security holes in bundled -# libs. -# Removal on 2024-05-07. Bug #928881 -acct-group/unifi-video -acct-user/unifi-video -media-video/unifi-video - -# Ben Kohler (2024-04-07) -# Long ago forked to and obsoleted by sys-apps/memtest86+. Upstream has -# abandoned this for their proprietary UEFI-based one (packaged in gentoo as -# as sys-apps/memtest86-bin). -# Removal on 2024-05-07. Bug #502464, #607494, #628528, #750677, #887003, -# #912973, #920109 -sys-apps/memtest86 - -# Andreas Sturmlechner (2024-04-06) -# Dead upstream for many years, in a state of decay and no revdeps. -# Removal on 2024-05-06. Bug #926193, #891791 -net-im/telepathy-connection-managers -net-libs/sofia-sip -net-libs/telepathy-accounts-signon -net-libs/telepathy-farstream -net-libs/telepathy-qt -net-voip/telepathy-gabble -net-voip/telepathy-rakia -net-voip/telepathy-salut - -# Andreas Sturmlechner (2024-04-06) -# Dead upstream, as is the whole telepathy stack. Some parts depend on -# dev-qt/qtwebengine:5. -# Removal on 2024-05-06. Bug #926679 -kde-apps/ktp-accounts-kcm -kde-apps/ktp-approver -kde-apps/ktp-auth-handler -kde-apps/ktp-common-internals -kde-apps/ktp-contact-list -kde-apps/ktp-contact-runner -kde-apps/ktp-desktop-applets -kde-apps/ktp-filetransfer-handler -kde-apps/ktp-kded-module -kde-apps/ktp-send-file -kde-apps/ktp-text-ui -kde-apps/plasma-telepathy-meta -net-libs/telepathy-logger-qt - -# James Le Cuirot (2024-04-05) -# Dead upstream and broken beyond repair. Removal on 2024-05-05. Bug #928591. -games-board/xmille - -# Michał Górny (2024-03-30) -# NIH package that was added for dev-python/setuptools but is no longer -# used there. -# Removal on 2024-04-29. Bug #928270. -dev-python/nspektr - -# James Le Cuirot (2024-03-30) -# Old, ugly, broken, and requires OSS sound. Removal on 2024-04-30. Bug #928066. -games-sports/gracer - # Sam James (2024-03-28) -# Newer releases were signed by a potentially compromised upstream maintainer. +# Newer 5.4.x releases were signed by a potentially compromised upstream maintainer. # There is no evidence that these releases contain malicious code, but masked # out of an abundance of caution. See bug #928134. sec-keys/openpgp-keys-jiatan ->=app-arch/xz-utils-5.4.3 +~app-arch/xz-utils-5.4.3 +~app-arch/xz-utils-5.4.4 +~app-arch/xz-utils-5.4.5 +~app-arch/xz-utils-5.4.6 # Sam James (2024-03-28) # Backdoor discovered in release tarballs. DOWNGRADE NOW. @@ -178,556 +586,15 @@ sec-keys/openpgp-keys-jiatan ~app-arch/xz-utils-5.6.0 ~app-arch/xz-utils-5.6.1 -# Michał Górny (2024-03-26) -# Last release in 2012. No reverse dependencies. -# Removal on 2024-04-25. Bug #927524. -dev-python/simplegeneric - -# Michał Górny (2024-03-26) -# Unmaintained. EAPI 6. Homepage gone. No keywords for modern -# architectures. -# Removal on 2024-04-25. Bug #927208. -net-misc/blinkperl - -# Michał Górny (2024-03-26) -# Unmaintained. Multiple bugs open. The current version is from 2018, -# and it has been discontinued as a separate package since. -# Removal on 2024-04-25. Bug #926861. -net-misc/felix - -# Michał Górny (2024-03-26) -# Unmaintained. EAPI 6. Homepage gone. -# Removal on 2024-04-25. Bug #926860. -app-pda/iripdb - -# Michał Górny (2024-03-26) -# Unfetchable proprietary fonts. The alternatives include -# media-fonts/jomolhari and "Noto Serif Tibetan" from media-fonts/noto. -# Removal on 2024-04-25. Bug #926836. -media-fonts/dzongkha-fonts - -# Michał Górny (2024-03-26) -# A dead wiget library with no reverse dependencies. Homepage gone. -# Removal on 2024-04-25. Bug #926604. -x11-libs/scw - -# Michał Górny (2024-03-26) -# Deprecated upstream and the URL no longer works. -# Removal on 2024-04-25. Bug #926550. -sys-firmware/bluez-firmware - -# Michał Górny (2024-03-26) -# Unfinished package from 2021 that was added as a short-lived -# dependency of dev-python/GitPython. No reverse dependencies remain. -# Removal on 2024-04-25. Bug #924683. -dev-python/sumtypes - -# Michał Górny (2024-03-26) -# Uses deprecated distutils-r1 API. The current version is outdated, -# from mid-2022. No reverse dependencies. -# Removal on 2024-04-25. Bug #910015. -sci-biology/HTSeq - -# Michał Górny (2024-03-26) -# Uses deprecated distutils-r1 API. Depends on dev-qt/qtwebengine:5. -# Includes the libraries with no other reverse dependencies. -# Removal on 2024-04-25. Bug #909996. -media-libs/libopenshot -media-libs/libopenshot-audio -media-video/openshot - -# Michał Górny (2024-03-26) -# Issues with OpenSSL 3. Unmaintained. Last activity in 2019. -# Removal on 2024-04-25. Bug #892031. -sys-auth/pam_ssh - -# Michał Górny (2024-03-26) -# Fails to compile. Unmaintained. Last activity in 2016. -# Depends on an old wxGTK slot. -# Removal on 2024-04-25. Bug #895222. -app-misc/tek - -# Michał Górny (2024-03-26) -# Bad C++ code. Unmaintained. Carries a number of patches already. -# No reverse dependencies. -# Removal on 2024-04-25. Bug #924925. -dev-libs/zthread - -# Eli Schwartz (2024-03-24) -# Broken with modern compilers, broken with LTO. Upstream website no -# longer exists. Unmaintained in Gentoo, no reverse dependencies. -# Removal on 2024-04-23. Bug #731942, #863041, #898298. -sci-libs/xgks-pmel - -# Michał Górny (2024-03-23) -# No maintainer. Broken tests. Not ported to PEP517 build. -# No release since 2020, little activity since. No revdeps. -# Removal on 2024-04-22. Bug #911780. -dev-python/prov - -# Michał Górny (2024-03-23) -# Apparently broken. No tests. Last code change in 2016. No revdeps. -# Removal on 2024-04-22. Bug #892613. -dev-python/sphinxcontrib-asyncio - -# Conrad Kostecki (2024-03-22) -# Stuck on old EAPI6. Last stable release over 10 years ago. -# Not compatible with PHP8. Removal on 2024-04-22. -dev-php/onphp - -# Conrad Kostecki (2024-03-22) -# Stuck on old EAPI6. PEAR channel long dead. -# Removal on 2024-04-22. -dev-php/mockery - -# Conrad Kostecki (2024-03-22) -# Stuck on old EAPI6. Not compatible with PHP7 and newer. -# Upstream stopped development. -# Removal on 2024-04-22. -dev-php/libchart - -# Hans de Graaff (2024-03-22) -# Broken with modern compilers, bug 884249. No longer maintained -# upstream, last release 5 years ago. No reverse dependencies left. Use -# dev-ruby/concurrent-ruby instead. -# Removal on 2024-04-22. -dev-ruby/atomic - -# Rahil Bhimjiani (2024-03-17) -# buildah-1.34.0 isn't getting security fixes from upstream -# https://github.com/containers/buildah/issues/5320 -=app-containers/buildah-1.34.0 - # Eray Aslan (2024-03-10) # Mask experimental software =mail-mta/postfix-3.10* -# Andreas Sturmlechner (2024-04-16) -# KDE Plasma 6.0.4, Gear 24.02.2 and Frameworks 6.1.0 mask -# -# Don't do anything unless you're intentionally moving to Plasma 6, which is -# masked still for a reason. If you get this message just from conflicts where -# you're not trying to do that, please cleanup stale entries in /etc/portage -# and your world file. -# -# Plasma 6 replaces 5. For conflict resolution between KF5- and KF6-packages: -# - put '-kf6compat' into /etc/portage/profile/use.mask -# - enable USE=kf6compat globally -# - if you have the following packages installed, put the following into -# /etc/portage/package.use in order to avoid conflicts: -# dev-util/kdevelop:5 -gdbui -plasma -# If you encounter ... -# - build-time/packaging bugs: -# - file a bug after making sure none exists yet for your issue -# - runtime bugs: https://community.kde.org/Plasma/Plasma_6#How_to_use/test_it -# - work with upstream and help test patches using /etc/portage/patches -~kde-frameworks/frameworkintegration-6.1.0 -~kde-frameworks/attica-6.1.0 -~kde-frameworks/bluez-qt-6.1.0 -~kde-frameworks/breeze-icons-6.1.0 -~kde-frameworks/extra-cmake-modules-6.1.0 -~kde-frameworks/karchive-6.1.0 -~kde-frameworks/kcalendarcore-6.1.0 -~kde-frameworks/kcodecs-6.1.0 -~kde-frameworks/kconfig-6.1.0 -~kde-frameworks/kcoreaddons-6.1.0 -~kde-frameworks/kdbusaddons-6.1.0 -~kde-frameworks/kdnssd-6.1.0 -~kde-frameworks/kguiaddons-6.1.0 -~kde-frameworks/kholidays-6.1.0 -~kde-frameworks/ki18n-6.1.0 -~kde-frameworks/kidletime-6.1.0 -~kde-frameworks/kirigami-6.1.0 -~kde-frameworks/kitemmodels-6.1.0 -~kde-frameworks/kitemviews-6.1.0 -~kde-frameworks/kplotting-6.1.0 -~kde-frameworks/kquickcharts-6.1.0 -~kde-frameworks/ktexttemplate-6.1.0 -~kde-frameworks/kuserfeedback-6.1.0 -~kde-frameworks/kwidgetsaddons-6.1.0 -~kde-frameworks/kwindowsystem-6.1.0 -~kde-frameworks/modemmanager-qt-6.1.0 -~kde-frameworks/networkmanager-qt-6.1.0 -~kde-frameworks/prison-6.1.0 -~kde-frameworks/solid-6.1.1 -~kde-frameworks/sonnet-6.1.0 -~kde-frameworks/syntax-highlighting-6.1.0 -~kde-frameworks/threadweaver-6.1.0 -~kde-frameworks/kauth-6.1.0 -~kde-frameworks/kcolorscheme-6.1.0 -~kde-frameworks/kcompletion-6.1.0 -~kde-frameworks/kcontacts-6.1.0 -~kde-frameworks/kcrash-6.1.0 -~kde-frameworks/kdoctools-6.1.0 -~kde-frameworks/kfilemetadata-6.1.0 -~kde-frameworks/kimageformats-6.1.0 -~kde-frameworks/kjobwidgets-6.1.0 -~kde-frameworks/knotifications-6.1.0 -~kde-frameworks/kpackage-6.1.0 -~kde-frameworks/kpeople-6.1.0 -~kde-frameworks/kpty-6.1.0 -~kde-frameworks/kstatusnotifieritem-6.1.0 -~kde-frameworks/ksvg-6.1.0 -~kde-frameworks/kunitconversion-6.1.0 -~kde-frameworks/syndication-6.1.0 -~kde-frameworks/baloo-6.1.0 -~kde-frameworks/kbookmarks-6.1.0 -~kde-frameworks/kcmutils-6.1.0 -~kde-frameworks/kconfigwidgets-6.1.0 -~kde-frameworks/kdav-6.1.0 -~kde-frameworks/kdeclarative-6.1.0 -~kde-frameworks/kded-6.1.0 -~kde-frameworks/kdesu-6.1.0 -~kde-frameworks/kglobalaccel-6.1.0 -~kde-frameworks/kiconthemes-6.1.0 -~kde-frameworks/kio-6.1.0 -~kde-frameworks/knewstuff-6.1.0 -~kde-frameworks/knotifyconfig-6.1.0 -~kde-frameworks/kparts-6.1.0 -~kde-frameworks/krunner-6.1.0 -~kde-frameworks/kservice-6.1.0 -~kde-frameworks/ktexteditor-6.1.0 -~kde-frameworks/ktextwidgets-6.1.0 -~kde-frameworks/kwallet-6.1.0 -~kde-frameworks/kxmlgui-6.1.0 -~kde-frameworks/purpose-6.1.0 -~kde-frameworks/qqc2-desktop-style-6.1.0 -~kde-plasma/bluedevil-6.0.4 -~kde-plasma/breeze-6.0.4 -~kde-plasma/breeze-grub-6.0.4 -~kde-plasma/breeze-gtk-6.0.4.1 -~kde-plasma/breeze-plymouth-6.0.4.1 -~kde-plasma/discover-6.0.4 -~kde-plasma/drkonqi-6.0.4 -~kde-plasma/flatpak-kcm-6.0.4 -~kde-plasma/kactivitymanagerd-6.0.4 -~kde-plasma/kde-cli-tools-6.0.4 -~kde-plasma/kde-gtk-config-6.0.4 -~kde-plasma/kdecoration-6.0.4 -~kde-plasma/kdeplasma-addons-6.0.4 -~kde-plasma/kgamma-6.0.4 -~kde-plasma/kglobalacceld-6.0.4 -~kde-plasma/kinfocenter-6.0.4 -~kde-plasma/kmenuedit-6.0.4 -~kde-plasma/kpipewire-6.0.4 -~kde-plasma/kscreen-6.0.4 -~kde-plasma/kscreenlocker-6.0.4 -~kde-plasma/ksshaskpass-6.0.4 -~kde-plasma/ksystemstats-6.0.4 -~kde-plasma/kwallet-pam-6.0.4 -~kde-plasma/kwayland-6.0.4 -~kde-plasma/kwayland-integration-6.0.4 -~kde-plasma/kwin-6.0.4 -~kde-plasma/kwrited-6.0.4 -~kde-plasma/layer-shell-qt-6.0.4 -~kde-plasma/libkscreen-6.0.4 -~kde-plasma/libksysguard-6.0.4 -~kde-plasma/libplasma-6.0.4 -~kde-plasma/milou-6.0.4 -~kde-plasma/ocean-sound-theme-6.0.4 -~kde-plasma/oxygen-6.0.4 -~kde-plasma/oxygen-sounds-6.0.4 -~kde-plasma/plasma-activities-6.0.4 -~kde-plasma/plasma-activities-stats-6.0.4 -~kde-plasma/plasma-browser-integration-6.0.4 -~kde-plasma/plasma-desktop-6.0.4 -~kde-plasma/plasma-disks-6.0.4 -~kde-plasma/plasma-firewall-6.0.4 -~kde-plasma/plasma-integration-6.0.4 -~kde-plasma/plasma-meta-6.0.4 -~kde-plasma/plasma-nm-6.0.4 -~kde-plasma/plasma-pa-6.0.4 -~kde-plasma/plasma-sdk-6.0.4 -~kde-plasma/plasma-systemmonitor-6.0.4 -~kde-plasma/plasma-thunderbolt-6.0.4 -~kde-plasma/plasma-vault-6.0.4 -~kde-plasma/plasma-welcome-6.0.4 -~kde-plasma/plasma-workspace-6.0.4 -~kde-plasma/plasma-workspace-wallpapers-6.0.4 -~kde-plasma/plasma5support-6.0.4 -~kde-plasma/plymouth-kcm-6.0.4 -~kde-plasma/polkit-kde-agent-6.0.4 -~kde-plasma/powerdevil-6.0.4 -~kde-plasma/print-manager-6.0.4 -~kde-plasma/qqc2-breeze-style-6.0.4 -~kde-plasma/sddm-kcm-6.0.4 -~kde-plasma/systemsettings-6.0.4 -~kde-plasma/wacomtablet-6.0.4 -~kde-plasma/xdg-desktop-portal-kde-6.0.4 -~kde-apps/baloo-widgets-24.02.2 -~kde-apps/dolphin-24.02.2 -~kde-apps/ffmpegthumbs-24.02.2 -~kde-apps/kate-24.02.2 -~kde-apps/kate-addons-24.02.2 -~kde-apps/kate-lib-24.02.2 -~kde-apps/kde-apps-meta-24.02.2 -~kde-apps/kdecore-meta-24.02.2 -~kde-apps/khelpcenter-24.02.2 -~kde-apps/konsole-24.02.2 -~kde-apps/kwrite-24.02.2 -~kde-apps/kdialog-24.02.2 -~kde-apps/keditbookmarks-24.02.2 -~kde-apps/kfind-24.02.2 -~kde-apps/konqueror-24.02.2 -~www-client/falkon-24.02.2 -~app-accessibility/kontrast-24.02.2 -~kde-apps/kdeaccessibility-meta-24.02.2 -~kde-apps/kmag-24.02.2 -~kde-apps/kmousetool-24.02.2 -~kde-apps/kmouth-24.02.2 -~kde-apps/kdeadmin-meta-24.02.2 -~kde-apps/kcron-24.02.2 -~kde-apps/ksystemlog-24.02.2 -~kde-apps/analitza-24.02.2 -~kde-apps/blinken-24.02.2 -~kde-apps/kalgebra-24.02.2 -~kde-apps/kanagram-24.02.2 -~kde-apps/kbruch-24.02.2 -~kde-apps/kdeedu-meta-24.02.2 -~kde-apps/kgeography-24.02.2 -~kde-apps/khangman-24.02.2 -~kde-apps/kiten-24.02.2 -~kde-apps/klettres-24.02.2 -~kde-apps/kturtle-24.02.2 -~kde-apps/kwordquiz-24.02.2 -~kde-apps/libkeduvocdocument-24.02.2 -~kde-apps/parley-24.02.2 -~kde-apps/bomber-24.02.2 -~kde-apps/bovo-24.02.2 -~kde-apps/granatier-24.02.2 -~kde-apps/kajongg-24.02.2 -~kde-apps/kapman-24.02.2 -~kde-apps/katomic-24.02.2 -~kde-apps/kblackbox-24.02.2 -~kde-apps/kblocks-24.02.2 -~kde-apps/kbounce-24.02.2 -~kde-apps/kbreakout-24.02.2 -~kde-apps/kdegames-meta-24.02.2 -~kde-apps/kdiamond-24.02.2 -~kde-apps/kfourinline-24.02.2 -~kde-apps/kgoldrunner-24.02.2 -~kde-apps/kigo-24.02.2 -~kde-apps/killbots-24.02.2 -~kde-apps/kiriki-24.02.2 -~kde-apps/kjumpingcube-24.02.2 -~kde-apps/klickety-24.02.2 -~kde-apps/klines-24.02.2 -~kde-apps/kmahjongg-24.02.2 -~kde-apps/kmines-24.02.2 -~kde-apps/knavalbattle-24.02.2 -~kde-apps/knetwalk-24.02.2 -~kde-apps/knights-24.02.2 -~kde-apps/kolf-24.02.2 -~kde-apps/kollision-24.02.2 -~kde-apps/konquest-24.02.2 -~kde-apps/kpat-24.02.2 -~kde-apps/kreversi-24.02.2 -~kde-apps/kshisen-24.02.2 -~kde-apps/ksirk-24.02.2 -~kde-apps/ksnakeduel-24.02.2 -~kde-apps/kspaceduel-24.02.2 -~kde-apps/ksquares-24.02.2 -~kde-apps/ksudoku-24.02.2 -~kde-apps/ktuberling-24.02.2 -~kde-apps/kubrick-24.02.2 -~kde-apps/libkdegames-24.02.2 -~kde-apps/libkmahjongg-24.02.2 -~kde-apps/lskat-24.02.2 -~kde-apps/palapeli-24.02.2 -~kde-apps/picmi-24.02.2 -~kde-apps/gwenview-24.02.2 -~kde-apps/kamera-24.02.2 -~kde-apps/kcolorchooser-24.02.2 -~kde-apps/kdegraphics-meta-24.02.2 -~kde-apps/kdegraphics-mobipocket-24.02.2 -~kde-apps/kruler-24.02.2 -~kde-apps/libkdcraw-24.02.2 -~kde-apps/libkexiv2-24.02.2 -~kde-apps/okular-24.02.2 -~kde-apps/spectacle-24.02.2 -~kde-apps/svgpart-24.02.2 -~kde-apps/thumbnailers-24.02.2 -~kde-misc/colord-kde-24.02.2 -~media-gfx/skanpage-24.02.2 -~media-libs/ksanecore-24.02.2 -~kde-apps/audiocd-kio-24.02.2 -~kde-apps/dragon-24.02.2 -~kde-apps/juk-24.02.2 -~kde-apps/kdemultimedia-meta-24.02.2 -~kde-apps/kdenlive-24.02.2 -~kde-apps/libkcddb-24.02.2 -~kde-apps/libkcompactdisc-24.02.2 -~media-sound/elisa-24.02.2 -~media-sound/kasts-24.02.2 -~media-sound/krecorder-24.02.2 -~kde-apps/dolphin-plugins-dropbox-24.02.2 -~kde-apps/kaccounts-integration-24.02.2 -~kde-apps/kaccounts-providers-24.02.2 -~kde-apps/kdenetwork-meta-24.02.2 -~kde-apps/kdenetwork-filesharing-24.02.2 -~kde-apps/kget-24.02.2 -~kde-apps/kio-extras-24.02.2 -~kde-apps/krfb-24.02.2 -~kde-apps/signon-kwallet-extension-24.02.2 -~kde-misc/kdeconnect-24.02.2 -~kde-misc/kio-gdrive-24.02.2 -~net-im/neochat-24.02.2 -~net-im/tokodon-24.02.2 -~net-irc/konversation-24.02.2 -~net-libs/libktorrent-24.02.2 -~net-misc/kio-zeroconf-24.02.2 -~net-news/alligator-24.02.2 -~net-p2p/ktorrent-24.02.2 -~app-office/merkuro-24.02.2 -~dev-libs/kopeninghours-24.02.2 -~dev-libs/kosmindoormap-24.02.2 -~dev-libs/kpublictransport-24.02.2 -~kde-apps/akonadi-24.02.2 -~kde-apps/akonadi-calendar-24.02.2 -~kde-apps/akonadi-contacts-24.02.2 -~kde-apps/akonadi-import-wizard-24.02.2 -~kde-apps/akonadi-mime-24.02.2 -~kde-apps/akonadi-notes-24.02.2 -~kde-apps/akonadi-search-24.02.2 -~kde-apps/akonadiconsole-24.02.2 -~kde-apps/akregator-24.02.2 -~kde-apps/calendarjanitor-24.02.2 -~kde-apps/calendarsupport-24.02.2 -~kde-apps/eventviews-24.02.2 -~kde-apps/grantlee-editor-24.02.2 -~kde-apps/grantleetheme-24.02.2 -~kde-apps/incidenceeditor-24.02.2 -~kde-apps/kaddressbook-24.02.2 -~kde-apps/kalarm-24.02.2 -~kde-apps/kcalutils-24.02.2 -~kde-apps/kdepim-addons-24.02.2 -~kde-apps/kdepim-meta-24.02.2 -~kde-apps/kdepim-runtime-24.02.2 -~kde-apps/kidentitymanagement-24.02.2 -~kde-apps/kimap-24.02.2 -~kde-apps/kitinerary-24.02.2 -~kde-apps/kldap-24.02.2 -~kde-apps/kleopatra-24.02.2 -~kde-apps/kmail-24.02.2 -~kde-apps/kmail-account-wizard-24.02.2 -~kde-apps/kmailtransport-24.02.2 -~kde-apps/kmbox-24.02.2 -~kde-apps/kmime-24.02.2 -~kde-apps/knotes-24.02.2 -~kde-apps/konsolekalendar-24.02.2 -~kde-apps/kontact-24.02.2 -~kde-apps/kontactinterface-24.02.2 -~kde-apps/korganizer-24.02.2 -~kde-apps/kpimtextedit-24.02.2 -~kde-apps/kpkpass-24.02.2 -~kde-apps/ksmtp-24.02.2 -~kde-apps/libgravatar-24.02.2 -~kde-apps/libkdepim-24.02.2 -~kde-apps/libkgapi-24.02.2 -~kde-apps/libkleo-24.02.2 -~kde-apps/libksieve-24.02.2 -~kde-apps/libktnef-24.02.2 -~kde-apps/mailcommon-24.02.2 -~kde-apps/mailimporter-24.02.2 -~kde-apps/mbox-importer-24.02.2 -~kde-apps/messagelib-24.02.2 -~kde-apps/mimetreeparser-24.02.2 -~kde-apps/pim-data-exporter-24.02.2 -~kde-apps/pim-sieve-editor-24.02.2 -~kde-apps/pimcommon-24.02.2 -~kde-misc/zanshin-24.02.2 -~kde-apps/dolphin-plugins-git-24.02.2 -~kde-apps/dolphin-plugins-mercurial-24.02.2 -~kde-apps/dolphin-plugins-subversion-24.02.2 -~kde-apps/kapptemplate-24.02.2 -~kde-apps/kcachegrind-24.02.2 -~kde-apps/kde-dev-utils-24.02.2 -~kde-apps/kdesdk-meta-24.02.2 -~app-cdr/dolphin-plugins-mountiso-24.02.2 -~app-cdr/isoimagewriter-24.02.2 -~app-crypt/keysmith-24.02.2 -~kde-apps/ark-24.02.2 -~kde-apps/filelight-24.02.2 -~kde-apps/kbackup-24.02.2 -~kde-apps/kcalc-24.02.2 -~kde-apps/kcharselect-24.02.2 -~kde-apps/kdebugsettings-24.02.2 -~kde-apps/kdeutils-meta-24.02.2 -~kde-apps/kdf-24.02.2 -~kde-apps/kgpg-24.02.2 -~kde-apps/kteatime-24.02.2 -~kde-apps/ktimer-24.02.2 -~kde-apps/kwalletmanager-24.02.2 -~kde-apps/sweeper-24.02.2 -~kde-apps/yakuake-24.02.2 -~kde-misc/kclock-24.02.2 -~kde-misc/kweather-24.02.2 -~kde-misc/markdownpart-24.02.2 -~sys-block/partitionmanager-24.02.2 -~sys-libs/kpmcore-24.02.2 -=kde-apps/kio-extras-23.08.5-r100 -=kde-apps/libkgapi-23.08.5-r100 -=kde-misc/kio-gdrive-23.08.5-r1 -=kde-plasma/print-manager-23.08.5-r100 -~kde-misc/kio-fuse-5.1.0 -~kde-misc/plasma-pass-1.2.2 -~app-editors/kile-2.9.94 -~dev-db/futuresql-0.1.1 -~dev-libs/appstream-1.0.2 -~dev-libs/kdiagram-3.0.1 -~dev-libs/kirigami-addons-1.1.0 -~dev-libs/ktextaddons-1.5.4 -~dev-libs/kweathercore-0.8.0 -~games-puzzle/skladnik-0.5.2 -~gui-apps/xwaylandvideobridge-0.4.0 -~kde-frameworks/oxygen-icons-6.0.0 -=media-libs/kquickimageeditor-0.3.0-r100 -~media-libs/libqaccessibilityclient-0.6.0 -~media-libs/mpvqt-1.0.0 -~media-libs/phonon-4.12.0 -~media-libs/phonon-vlc-0.12.0 -~media-libs/pulseaudio-qt-1.4.0 -~net-libs/kdsoap-2.2.0 -~net-libs/kdsoap-ws-discovery-client-0.4.0 -~net-libs/signon-ui-0.15_p20231016 -~net-libs/accounts-qt-1.17 -~net-libs/accounts-qml-0.7_p20231028 -~net-libs/signon-oauth2-0.25_p20210102 -=net-libs/signond-8.61-r100 -=net-misc/smb4k-3.2.5-r2 -~sys-auth/polkit-qt-0.200.0 ->=sys-libs/snapd-glib-1.64-r100 - -# Sam James (2024-02-18) -# Lots of changes, including a port to a new build system. Needs lots of testing. -=sys-apps/gentoo-functions-1* - -# Sam James (2024-02-15) -# May break on some arches b/c of visibility/map changes to ffi_type_longdouble -=dev-libs/libffi-3.4.5 - # Ulrich Müller (2024-02-08) # Masked for testing. # Test failure in watchpoints.dem, undefined function FresnelC. ~sci-visualization/gnuplot-6.0.0 -# Andrew Ammerlaan (2024-01-24) -# app-misc/ddcutil-2.1.0 causes core-dump crashes in -# kde-plasma/powerdevil[brightness-control]. -~app-misc/ddcutil-2.1.0 -~app-misc/ddcui-0.5.0 - -# Patrick Lauer (2023-12-23) -# ROCm-6 builds but has runtime issues for me ->=dev-libs/roct-thunk-interface-6.0.0 ->=dev-libs/rocr-runtime-6.0.0 ->=dev-libs/rocm-comgr-6.0.0 ->=dev-libs/rocm-device-libs-6.0.0 ->=dev-libs/rocm-opencl-runtime-6.0.0 ->=dev-util/hipcc-6.0.0 ->=dev-util/hip-6.0.0 ->=dev-util/rocminfo-6.0.0 - # Sam James (2023-12-14) # Gentoo's kernel maintainers have decided to discontinue gentoo-sources and # gentoo-kernel for old kernel LTS branches because of the resources to require @@ -746,39 +613,6 @@ dev-ruby/atomic (2023-12-09) -# ext4 corruption bug: https://lore.kernel.org/stable/20231205122122.dfhhoaswsfscuhc3@quack3/ (bug #919675) -# Please update immediately to the latest versions in each series. -=sys-kernel/gentoo-sources-6.1.64 -=sys-kernel/gentoo-sources-6.1.64-r1 -=sys-kernel/gentoo-sources-6.1.65 -=sys-kernel/gentoo-kernel-6.1.64 -=sys-kernel/gentoo-kernel-6.1.64-r1 -=sys-kernel/gentoo-kernel-6.1.65 -=sys-kernel/vanilla-sources-6.1.64 -=sys-kernel/vanilla-sources-6.1.65 -=sys-kernel/vanilla-kernel-6.1.64 -=sys-kernel/vanilla-kernel-6.1.65 - -# Eli Schwartz (2023-12-02) -# Has a bug that breaks sys-apps/portage. Upgrade to 1.3.0-r1 instead. -# Bug #919072. -=dev-build/meson-1.3.0 - -# Sam James (2023-11-25) -# Breaks desktop icon rendering, see bug #904468. -# Upstream bug: https://gitlab.xfce.org/xfce/xfdesktop/-/issues/242 -=xfce-base/xfdesktop-4.19.2 -=xfce-base/xfdesktop-4.19.1 - -# Sam James (2023-11-22) -# Further bugs with CoW via copy_file_range (bug #917224, https://github.com/openzfs/zfs/issues/15526). -# The issue is very similar to bug #815469. -# ZFS 2.2.1 has a workaround but if you haven't already upgraded your pool to -# use the new block cloning feature, consider using (2023-11-19) # GCC 10 and older no longer receive upstream support or fixes for # bugs. Please switch to a newer GCC version using gcc-config. @@ -786,21 +620,6 @@ dev-ruby/atomic (2023-11-05) -# Mask broken versions: -# - sys-fs/btrfs-progs-6.6(-r0) was respun upstream. -# - sys-fs/btrfs-progs-6.6-r1 had the fixed tarball, but contained an upstream -# bug in the ioctl numbers. -# Please use sys-fs/btrfs-progs-6.6-r2 or, better, sys-fs/btrfs-progs-6.6.1 -# (identical in functional contents). -=sys-fs/btrfs-progs-6.6 -=sys-fs/btrfs-progs-6.6-r1 -=sys-fs/btrfs-progs-6.6-r2 - -# Sam James (2023-10-06) -# Breaks building scipy: https://github.com/cython/cython/issues/5748 -=dev-python/cython-3.0.3 - # Sam James (2023-09-09) # OpenSSL 1.1.x is EOL on 2023-09-11. Please upgrade immediately to >= OpenSSL 3. # https://www.openssl.org/blog/blog/2023/03/28/1.1.1-EOL/ @@ -817,10 +636,6 @@ dev-ruby/atomic # may or may not lead to useful results. (2023-07-06) -# GNOME 45 mask ->=gnome-extra/gnome-logs-45_alpha - # Michał Górny (2023-06-21) # suitesparseconfig-7.0.0 fails to build with multilib enabled # because of dependencies that cannot be satisfied. All the other @@ -869,11 +684,6 @@ x11-drivers/nvidia-drivers:0/390 # Breaks too many revdeps for now =app-text/discount-3* -# John Helmert III (2022-10-16) -# (2022-04-29) # Apparently the "b" in version means "beta". 3.24 is available, we # should update to that. #841437 @@ -884,11 +694,6 @@ x11-drivers/nvidia-drivers:0/390 # This is likely to cause issues in tests; Unmask if using for other purposes >=dev-php/PHP_Timer-5.0 -# Volkmar W. Pogatzki (2021-11-23) -# Does not support updated dev-java/pdfbox-2.0.24, Bug #803488 -# Blocks (CVE-2018-11797, CVE-2021-{27807,27906,31811,31812}) -dev-tex/pdfannotextractor - # Ionen Wolkens (2021-10-09) # Vulkan beta driver branch aimed at Vulkan developers for testing # new features. Beside vulkan, it is typically behind the main branch diff --git a/sdk_container/src/third_party/portage-stable/profiles/prefix/darwin/macos/package.mask b/sdk_container/src/third_party/portage-stable/profiles/prefix/darwin/macos/package.mask index 9290181142..962e14e44e 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/prefix/darwin/macos/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/prefix/darwin/macos/package.mask @@ -1,6 +1,10 @@ # Copyright 1999-2023 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Fabian Groffen (2024-05-28) +# Fails to compile on any macOS, bug #932809, pending investigation +=net-dns/c-ares-1.29.0 + # Benda Xu (2023-08-20) # Does not play well with linkers under macOS. # Undefined symbols for architecture x86_64: diff --git a/sdk_container/src/third_party/portage-stable/profiles/prefix/sunos/solaris/package.mask b/sdk_container/src/third_party/portage-stable/profiles/prefix/sunos/solaris/package.mask index d9757c8bbe..1971a00902 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/prefix/sunos/solaris/package.mask +++ b/sdk_container/src/third_party/portage-stable/profiles/prefix/sunos/solaris/package.mask @@ -1,6 +1,12 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Fabian Groffen (2024-05-19) +# Fails to compile due to undefined INT_MAX +# https://github.com/libarchive/libarchive/issues/2162 +# https://github.com/libarchive/libarchive/commit/6ff1cd1e487ddf545337b88da3f1f5ca69a2f958 +=app-arch/libarchive-3.7.4 + # Fabian Groffen (2023-06-23) # Fails to link due to missing libintl, already fixed upstream: # https://git.savannah.gnu.org/cgit/tar.git/commit/?id=8632df398b2f548465ebe68b8f494c0d6f8d913d diff --git a/sdk_container/src/third_party/portage-stable/profiles/profiles.desc b/sdk_container/src/third_party/portage-stable/profiles/profiles.desc index 3a9f5b22b1..ac4aea804a 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/profiles.desc +++ b/sdk_container/src/third_party/portage-stable/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/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/make.defaults b/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/make.defaults index caccdbdd22..3cba94431b 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/make.defaults +++ b/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/make.defaults @@ -1,4 +1,4 @@ -# Copyright 1999-2023 Gentoo Authors +# Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 -USE="a52 aac acpi alsa bluetooth branding cairo cdda cdr cups dbus dri dts dvd dvdr elogind encode exif flac gif gpm gtk gui icu jpeg lcms libnotify mad mng mp3 mp4 mpeg ogg opengl pango pdf png policykit ppds qt5 sdl sound spell startup-notification svg tiff truetype vorbis udev udisks unicode upower usb vulkan wxwidgets X xcb xft x264 xml xv xvid" +USE="a52 aac acpi alsa bluetooth branding cairo cdda cdr cups dbus dri dts dvd dvdr elogind encode exif flac gif gpm gtk gui icu jpeg kf6compat lcms libnotify mad mng mp3 mp4 mpeg ogg opengl pango pdf png policykit ppds qt5 sdl sound spell startup-notification svg tiff truetype vorbis udev udisks unicode upower usb vulkan wxwidgets X xcb xft x264 xml xv xvid" diff --git a/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/package.use.force b/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/package.use.force index 77925d886d..a95659f9f0 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/package.use.force +++ b/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/package.use.force @@ -3,9 +3,10 @@ # Andreas Sturmlechner (2024-03-10) # Ensure that KF5- and Qt5-based applications, of which there are still -# many (even as part of KDE Gear 24.02), will not exhibit bugs and look -# out of place in Plasma 6 sessions. -=kde-plasma/plasma-meta-6.0*:6 qt5 +# many (even as part of KDE Gear 24.05), will not exhibit bugs and look +# out of place in Plasma 6 sessions. Do *not* file upstream bugs for Qt5- +# based packages if unsetting this. + (2014-06-03) # Ensure shared-mime-info is pulled in by glib, otherwise GNOME, XFCE, and diff --git a/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/plasma/package.use b/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/plasma/package.use index 55e470e11b..a1928b24e0 100644 --- a/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/plasma/package.use +++ b/sdk_container/src/third_party/portage-stable/profiles/targets/desktop/plasma/package.use @@ -1,6 +1,24 @@ # Copyright 1999-2024 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 +# Resolve conflict between Plasma 6 and KDevelop 24.05 +>=dev-util/kdevelop-24.05.1:5 -plasma + +# Sam James (2024-06-13) +# Needed by dependencies of KDE Plasma and KDE Gear +app-crypt/gpgme qt6 +app-crypt/pinentry qt6 +app-crypt/qca qt6 +app-text/poppler qt6 +dev-libs/qtkeychain qt6 +media-libs/phonon qt6 +media-libs/phonon-vlc qt6 +net-libs/accounts-qml qt6 +net-libs/accounts-qt qt6 +net-libs/signond qt6 +net-libs/signon-oauth2 qt6 +sys-auth/polkit-qt qt6 + # Alfred Wingate (2023-12-25) # Prefer wayland over X with REQUIRED_USE: ^^ ( gbm wayland X ) >=media-tv/kodi-20.2 wayland -X @@ -38,9 +56,6 @@ dev-qt/qtscript:5 scripttools # Required by kde-apps/akonadi:5 dev-qt/qtsql:5 mysql -# Required by kde-apps/ktp-text-ui -kde-apps/ktp-common-internals otr - # Enable by default, requires kde-frameworks/kwayland kde-apps/yakuake absolute-position @@ -72,7 +87,6 @@ sys-libs/zlib minizip # Keep existing defaults after dropping IUSE=phonon from make.defaults