Abuse filter log

From Gentoo Wiki
Abuse Filter navigation (Home | Recent filter changes | Examine past edits | Abuse log)
Jump to:navigation Jump to:search
Details for log entry 4,814

19:49, 22 March 2024: Dilfridge (talk | contribs) triggered filter 30, performing the action "edit" on Project:Toolchain/23.0 update instructions. Actions taken: Disallow; Filter description: Disable writing internal wiki links as external besides required links. If absolutely necessary, use wiki.g.o as a workaround. (examine)

Changes made in edit

−
{{WIP|author=Dilfridge}}
 
−
 
−
{{Warning|Do not try to use these profiles on production systems until they are officially announced via a news item.}}
 
−
 
−
The following text is in preparation of the profile upgrade newsitem.
 
−
 
 
<pre>
 
<pre>
 
Title: Profile upgrade to version 23.0 available
 
Title: Profile upgrade to version 23.0 available
 
Author: Andreas K. Huettel <dilfridge@gentoo.org>
 
Author: Andreas K. Huettel <dilfridge@gentoo.org>
−
Posted: yyyy-mm-dd
+
Posted: 2024-03-22
 
Revision: 1
 
Revision: 1
 
News-Item-Format: 2.0
 
News-Item-Format: 2.0
−
 
+
Display-If-Profile: default/linux/alpha/17.0
−
[*** Ignore this message for now if you are using musl on (32bit)
+
Display-If-Profile: default/linux/alpha/17.0/*
−
    arm and x86. These configurations are not ready yet.         ***]
+
Display-If-Profile: default/linux/amd64/17.0
 +
Display-If-Profile: default/linux/amd64/17.0/*
 +
Display-If-Profile: default/linux/amd64/17.1
 +
Display-If-Profile: default/linux/amd64/17.1/*
 +
Display-If-Profile: default/linux/arm/17.0
 +
Display-If-Profile: default/linux/arm/17.0/*
 +
Display-If-Profile: default/linux/arm64/17.0
 +
Display-If-Profile: default/linux/arm64/17.0/*
 +
Display-If-Profile: default/linux/hppa/17.0
 +
Display-If-Profile: default/linux/hppa/17.0/*
 +
Display-If-Profile: default/linux/ia64/17.0
 +
Display-If-Profile: default/linux/ia64/17.0/*
 +
Display-If-Profile: default/linux/loong/22.0
 +
Display-If-Profile: default/linux/loong/22.0/*
 +
Display-If-Profile: default/linux/m68k/17.0
 +
Display-If-Profile: default/linux/m68k/17.0/*
 +
Display-If-Profile: default/linux/mips/17.0
 +
Display-If-Profile: default/linux/mips/17.0/*
 +
Display-If-Profile: default/linux/powerpc/ppc64/17.0/*
 +
Display-If-Profile: default/linux/ppc/17.0
 +
Display-If-Profile: default/linux/ppc/17.0/*
 +
Display-If-Profile: default/linux/ppc64/17.0
 +
Display-If-Profile: default/linux/ppc64/17.0/*
 +
Display-If-Profile: default/linux/ppc64le/17.0
 +
Display-If-Profile: default/linux/ppc64le/17.0/*
 +
Display-If-Profile: default/linux/riscv/20.0/*
 +
Display-If-Profile: default/linux/s390/17.0
 +
Display-If-Profile: default/linux/s390/17.0/*
 +
Display-If-Profile: default/linux/sparc/17.0
 +
Display-If-Profile: default/linux/sparc/17.0/*
 +
Display-If-Profile: default/linux/x86/17.0
 +
Display-If-Profile: default/linux/x86/17.0/*
  
 
A profile upgrade to version 23.0 is available for your architecture.  
 
A profile upgrade to version 23.0 is available for your architecture.  
 
We strongly advise to precisely follow the upgrade instructions found
 
We strongly advise to precisely follow the upgrade instructions found
 
below. The 17.0, 17.1, 20.0, and 22.0 profiles will be marked deprecated  
 
below. The 17.0, 17.1, 20.0, and 22.0 profiles will be marked deprecated  
−
in 2 months and removed a year later. The exact dates depend on the  
+
in 2 months and removed a year later. The exact dates may depend on the  
 
architecture, see [2].
 
architecture, see [2].
  
 
             (removed "merged-usr")
 
             (removed "merged-usr")
 
   A detailed table of the upgrade paths can be found at [5]. Please consult it.
 
   A detailed table of the upgrade paths can be found at [5]. Please consult it.
−
   In rare cases (hppa, x86) the table will tell you to pick between two choices.  
+
   In some cases (hppa, x86) the table will tell you to pick between two choices.  
−
   What you need should be obvious from your *OLD* CHOST value (from step 4).
+
   What you need should be obvious from your *old* CHOST value (from step 4).
  
 
7. Delete the contents of your binary package cache at ${PKGDIR}
 
7. Delete the contents of your binary package cache at ${PKGDIR}
 
   (you may have to run binutils-config and re-select your binutils now)
 
   (you may have to run binutils-config and re-select your binutils now)
 
     emerge --ask --oneshot --getbinpkg sys-devel/gcc
 
     emerge --ask --oneshot --getbinpkg sys-devel/gcc
−
   (If this command wants to rebuild glibc first, do *not* let it do that;
+
   (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do  
−
    instead, abort and try again with only --nodeps added to the command line.)
+
    that; instead, abort and try again with --nodeps added to the command line.)
 
   (you may have to run gcc-config and re-select your gcc now)
 
   (you may have to run gcc-config and re-select your gcc now)
 
   and the C library, i.e. for glibc-based systems
 
   and the C library, i.e. for glibc-based systems
  
  
−
[1] https://wiki.g.o/wiki/Project:Toolchain/23.0_profile_transition
+
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
−
[2] https://wiki.g.o/wiki/Project:Toolchain/23.0_profile_timeline
+
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
 
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
 
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
 
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
 
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
−
[5] https://wiki.g.o/wiki/Project:Toolchain/23.0_update_table
+
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
−
[6] https://wiki.g.o/wiki/Changing_the_CHOST_variable#Verifying_things_work
+
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
 
</pre>
 
</pre>

Action parameters

VariableValue
Edit count of the user (user_editcount)
1307
Name of the user account (user_name)
'Dilfridge'
Age of the user account (user_age)
392851845
Page ID (page_id)
347456
Page namespace (page_namespace)
510
Page title (without namespace) (page_title)
'Toolchain/23.0 update instructions'
Full page title (page_prefixedtitle)
'Project:Toolchain/23.0 update instructions'
Action (action)
'edit'
Edit summary/reason (summary)
'published newsitem version'
Old content model (old_content_model)
'wikitext'
New content model (new_content_model)
'wikitext'
Old page wikitext, before the edit (old_wikitext)
'{{WIP|author=Dilfridge}} {{Warning|Do not try to use these profiles on production systems until they are officially announced via a news item.}} The following text is in preparation of the profile upgrade newsitem. <pre> Title: Profile upgrade to version 23.0 available Author: Andreas K. Huettel <dilfridge@gentoo.org> Posted: yyyy-mm-dd Revision: 1 News-Item-Format: 2.0 [*** Ignore this message for now if you are using musl on (32bit) arm and x86. These configurations are not ready yet. ***] A profile upgrade to version 23.0 is available for your architecture. The new 23.0 profiles enable some toolchain hardening features and performance enhancements by default, and standardize settings. You can find the list of changes on the wiki tracking page [1]. We strongly advise to precisely follow the upgrade instructions found below. The 17.0, 17.1, 20.0, and 22.0 profiles will be marked deprecated in 2 months and removed a year later. The exact dates depend on the architecture, see [2]. Upgrade instructions Note 1: The use of binary packages is completely optional, and also not as much tested as the source-based upgrade path yet. If you prefer to only use the traditional source-based installation, omit the "--getbinpkg" parameter in all emerge invocations. Note 2: If you have manually changed your CHOST to a value different from what the stages and profiles set, you may have to do that in the future too. In that case you should know what you are doing, hopefully; please read the instructions with a critical eye then. 1. Ensure your system backups are up to date. Please also update your system fully and depclean before proceeding. glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. 2. If you are still using one of the long-deprecated amd64 17.0 profiles (other than x32 or musl), then first complete the migration to the corresponding 17.1 profile. Instructions can be found at [3]. 3. If you are currently using systemd in a split-usr configuration, then first complete the migration to the corresponding merged-usr profile of the same profile version. Details on how to do this can be found in the news item [4]. If you are currently using openrc, migrate to 23.0 first, keeping your disk layout. If you want to move from split-usr to merged-usr, do that afterwards. 4. Run "emerge --info" and note down the value of the CHOST variable. 5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, remove it. Also delete all lines defining CHOST_... variables. 6. Select the 23.0 profile corresponding to your current profile, either using "eselect profile" or by manually setting the profile symlink. Note that old profiles are by default split-usr and the 23.0 profiles by default merged-usr. Do NOT change directory scheme now, since this will mess up your system! Instead, make sure that the new profile has the same property: for example, OLD default/linux/amd64/17.1 ==> NEW default/linux/amd64/23.0/split-usr (added "split-usr") OLD default/linux/amd64/17.1/systemd/merged-usr ==> NEW default/linux/amd64/23.0/systemd (removed "merged-usr") A detailed table of the upgrade paths can be found at [5]. Please consult it. In rare cases (hppa, x86) the table will tell you to pick between two choices. What you need should be obvious from your *OLD* CHOST value (from step 4). 7. Delete the contents of your binary package cache at ${PKGDIR} rm -r /var/cache/binpkgs/* 8. In the file or directory /etc/portage/binrepos.conf (if existing), update the URI in all configuration such that they point to 23.0 profile binhost directories. The exact paths can be found in the table at [5], too. 9. Rebuild or reinstall from binary (if available) the following packages in this order, with the same version as already active: emerge --ask --oneshot --getbinpkg sys-devel/binutils (you may have to run binutils-config and re-select your binutils now) emerge --ask --oneshot --getbinpkg sys-devel/gcc (If this command wants to rebuild glibc first, do *not* let it do that; instead, abort and try again with only --nodeps added to the command line.) (you may have to run gcc-config and re-select your gcc now) and the C library, i.e. for glibc-based systems emerge --ask --oneshot --getbinpkg sys-libs/glibc or for musl-based systems emerge --ask --oneshot --getbinpkg sys-libs/musl 10. Re-run "emerge --info" and check if CHOST has changed compared to step 3. If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, 11. Recheck with binutils-config and gcc-config that valid installed versions of binutils and gcc are selected. 12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that refer to the *OLD* CHOST value, and remove them. Examples how to do this can be found in the similar procedure at [6]. 13. Run env-update && source /etc/profile 14. Re-emerge libtool: emerge --ask --oneshot --getbinpkg libtool 15. Just for safety, delete the contents of your binary package cache at ${PKGDIR} again: rm -r /var/cache/binpkgs/* 16. Rebuild world: emerge --ask --emptytree --getbinpkg @world [1] https://wiki.g.o/wiki/Project:Toolchain/23.0_profile_transition [2] https://wiki.g.o/wiki/Project:Toolchain/23.0_profile_timeline [3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html [4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html [5] https://wiki.g.o/wiki/Project:Toolchain/23.0_update_table [6] https://wiki.g.o/wiki/Changing_the_CHOST_variable#Verifying_things_work </pre>'
New page wikitext, after the edit (new_wikitext)
'<pre> Title: Profile upgrade to version 23.0 available Author: Andreas K. Huettel <dilfridge@gentoo.org> Posted: 2024-03-22 Revision: 1 News-Item-Format: 2.0 Display-If-Profile: default/linux/alpha/17.0 Display-If-Profile: default/linux/alpha/17.0/* Display-If-Profile: default/linux/amd64/17.0 Display-If-Profile: default/linux/amd64/17.0/* Display-If-Profile: default/linux/amd64/17.1 Display-If-Profile: default/linux/amd64/17.1/* Display-If-Profile: default/linux/arm/17.0 Display-If-Profile: default/linux/arm/17.0/* Display-If-Profile: default/linux/arm64/17.0 Display-If-Profile: default/linux/arm64/17.0/* Display-If-Profile: default/linux/hppa/17.0 Display-If-Profile: default/linux/hppa/17.0/* Display-If-Profile: default/linux/ia64/17.0 Display-If-Profile: default/linux/ia64/17.0/* Display-If-Profile: default/linux/loong/22.0 Display-If-Profile: default/linux/loong/22.0/* Display-If-Profile: default/linux/m68k/17.0 Display-If-Profile: default/linux/m68k/17.0/* Display-If-Profile: default/linux/mips/17.0 Display-If-Profile: default/linux/mips/17.0/* Display-If-Profile: default/linux/powerpc/ppc64/17.0/* Display-If-Profile: default/linux/ppc/17.0 Display-If-Profile: default/linux/ppc/17.0/* Display-If-Profile: default/linux/ppc64/17.0 Display-If-Profile: default/linux/ppc64/17.0/* Display-If-Profile: default/linux/ppc64le/17.0 Display-If-Profile: default/linux/ppc64le/17.0/* Display-If-Profile: default/linux/riscv/20.0/* Display-If-Profile: default/linux/s390/17.0 Display-If-Profile: default/linux/s390/17.0/* Display-If-Profile: default/linux/sparc/17.0 Display-If-Profile: default/linux/sparc/17.0/* Display-If-Profile: default/linux/x86/17.0 Display-If-Profile: default/linux/x86/17.0/* A profile upgrade to version 23.0 is available for your architecture. The new 23.0 profiles enable some toolchain hardening features and performance enhancements by default, and standardize settings. You can find the list of changes on the wiki tracking page [1]. We strongly advise to precisely follow the upgrade instructions found below. The 17.0, 17.1, 20.0, and 22.0 profiles will be marked deprecated in 2 months and removed a year later. The exact dates may depend on the architecture, see [2]. Upgrade instructions Note 1: The use of binary packages is completely optional, and also not as much tested as the source-based upgrade path yet. If you prefer to only use the traditional source-based installation, omit the "--getbinpkg" parameter in all emerge invocations. Note 2: If you have manually changed your CHOST to a value different from what the stages and profiles set, you may have to do that in the future too. In that case you should know what you are doing, hopefully; please read the instructions with a critical eye then. 1. Ensure your system backups are up to date. Please also update your system fully and depclean before proceeding. glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. 2. If you are still using one of the long-deprecated amd64 17.0 profiles (other than x32 or musl), then first complete the migration to the corresponding 17.1 profile. Instructions can be found at [3]. 3. If you are currently using systemd in a split-usr configuration, then first complete the migration to the corresponding merged-usr profile of the same profile version. Details on how to do this can be found in the news item [4]. If you are currently using openrc, migrate to 23.0 first, keeping your disk layout. If you want to move from split-usr to merged-usr, do that afterwards. 4. Run "emerge --info" and note down the value of the CHOST variable. 5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, remove it. Also delete all lines defining CHOST_... variables. 6. Select the 23.0 profile corresponding to your current profile, either using "eselect profile" or by manually setting the profile symlink. Note that old profiles are by default split-usr and the 23.0 profiles by default merged-usr. Do NOT change directory scheme now, since this will mess up your system! Instead, make sure that the new profile has the same property: for example, OLD default/linux/amd64/17.1 ==> NEW default/linux/amd64/23.0/split-usr (added "split-usr") OLD default/linux/amd64/17.1/systemd/merged-usr ==> NEW default/linux/amd64/23.0/systemd (removed "merged-usr") A detailed table of the upgrade paths can be found at [5]. Please consult it. In some cases (hppa, x86) the table will tell you to pick between two choices. What you need should be obvious from your *old* CHOST value (from step 4). 7. Delete the contents of your binary package cache at ${PKGDIR} rm -r /var/cache/binpkgs/* 8. In the file or directory /etc/portage/binrepos.conf (if existing), update the URI in all configuration such that they point to 23.0 profile binhost directories. The exact paths can be found in the table at [5], too. 9. Rebuild or reinstall from binary (if available) the following packages in this order, with the same version as already active: emerge --ask --oneshot --getbinpkg sys-devel/binutils (you may have to run binutils-config and re-select your binutils now) emerge --ask --oneshot --getbinpkg sys-devel/gcc (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do that; instead, abort and try again with --nodeps added to the command line.) (you may have to run gcc-config and re-select your gcc now) and the C library, i.e. for glibc-based systems emerge --ask --oneshot --getbinpkg sys-libs/glibc or for musl-based systems emerge --ask --oneshot --getbinpkg sys-libs/musl 10. Re-run "emerge --info" and check if CHOST has changed compared to step 3. If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, 11. Recheck with binutils-config and gcc-config that valid installed versions of binutils and gcc are selected. 12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that refer to the *OLD* CHOST value, and remove them. Examples how to do this can be found in the similar procedure at [6]. 13. Run env-update && source /etc/profile 14. Re-emerge libtool: emerge --ask --oneshot --getbinpkg libtool 15. Just for safety, delete the contents of your binary package cache at ${PKGDIR} again: rm -r /var/cache/binpkgs/* 16. Rebuild world: emerge --ask --emptytree --getbinpkg @world [1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition [2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline [3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html [4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html [5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table [6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work </pre>'
Unified diff of changes made by edit (edit_diff)
'@@ -1,17 +1,42 @@ -{{WIP|author=Dilfridge}} - -{{Warning|Do not try to use these profiles on production systems until they are officially announced via a news item.}} - -The following text is in preparation of the profile upgrade newsitem. - <pre> Title: Profile upgrade to version 23.0 available Author: Andreas K. Huettel <dilfridge@gentoo.org> -Posted: yyyy-mm-dd +Posted: 2024-03-22 Revision: 1 News-Item-Format: 2.0 - -[*** Ignore this message for now if you are using musl on (32bit) - arm and x86. These configurations are not ready yet. ***] +Display-If-Profile: default/linux/alpha/17.0 +Display-If-Profile: default/linux/alpha/17.0/* +Display-If-Profile: default/linux/amd64/17.0 +Display-If-Profile: default/linux/amd64/17.0/* +Display-If-Profile: default/linux/amd64/17.1 +Display-If-Profile: default/linux/amd64/17.1/* +Display-If-Profile: default/linux/arm/17.0 +Display-If-Profile: default/linux/arm/17.0/* +Display-If-Profile: default/linux/arm64/17.0 +Display-If-Profile: default/linux/arm64/17.0/* +Display-If-Profile: default/linux/hppa/17.0 +Display-If-Profile: default/linux/hppa/17.0/* +Display-If-Profile: default/linux/ia64/17.0 +Display-If-Profile: default/linux/ia64/17.0/* +Display-If-Profile: default/linux/loong/22.0 +Display-If-Profile: default/linux/loong/22.0/* +Display-If-Profile: default/linux/m68k/17.0 +Display-If-Profile: default/linux/m68k/17.0/* +Display-If-Profile: default/linux/mips/17.0 +Display-If-Profile: default/linux/mips/17.0/* +Display-If-Profile: default/linux/powerpc/ppc64/17.0/* +Display-If-Profile: default/linux/ppc/17.0 +Display-If-Profile: default/linux/ppc/17.0/* +Display-If-Profile: default/linux/ppc64/17.0 +Display-If-Profile: default/linux/ppc64/17.0/* +Display-If-Profile: default/linux/ppc64le/17.0 +Display-If-Profile: default/linux/ppc64le/17.0/* +Display-If-Profile: default/linux/riscv/20.0/* +Display-If-Profile: default/linux/s390/17.0 +Display-If-Profile: default/linux/s390/17.0/* +Display-If-Profile: default/linux/sparc/17.0 +Display-If-Profile: default/linux/sparc/17.0/* +Display-If-Profile: default/linux/x86/17.0 +Display-If-Profile: default/linux/x86/17.0/* A profile upgrade to version 23.0 is available for your architecture. @@ -22,5 +47,5 @@ We strongly advise to precisely follow the upgrade instructions found below. The 17.0, 17.1, 20.0, and 22.0 profiles will be marked deprecated -in 2 months and removed a year later. The exact dates depend on the +in 2 months and removed a year later. The exact dates may depend on the architecture, see [2]. @@ -70,6 +95,6 @@ (removed "merged-usr") A detailed table of the upgrade paths can be found at [5]. Please consult it. - In rare cases (hppa, x86) the table will tell you to pick between two choices. - What you need should be obvious from your *OLD* CHOST value (from step 4). + In some cases (hppa, x86) the table will tell you to pick between two choices. + What you need should be obvious from your *old* CHOST value (from step 4). 7. Delete the contents of your binary package cache at ${PKGDIR} @@ -85,6 +110,6 @@ (you may have to run binutils-config and re-select your binutils now) emerge --ask --oneshot --getbinpkg sys-devel/gcc - (If this command wants to rebuild glibc first, do *not* let it do that; - instead, abort and try again with only --nodeps added to the command line.) + (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do + that; instead, abort and try again with --nodeps added to the command line.) (you may have to run gcc-config and re-select your gcc now) and the C library, i.e. for glibc-based systems @@ -117,9 +142,9 @@ -[1] https://wiki.g.o/wiki/Project:Toolchain/23.0_profile_transition -[2] https://wiki.g.o/wiki/Project:Toolchain/23.0_profile_timeline +[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition +[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline [3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html [4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html -[5] https://wiki.g.o/wiki/Project:Toolchain/23.0_update_table -[6] https://wiki.g.o/wiki/Changing_the_CHOST_variable#Verifying_things_work +[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table +[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work </pre> '
Old page size (old_size)
5790
Lines added in edit (added_lines)
[ 0 => 'Posted: 2024-03-22', 1 => 'Display-If-Profile: default/linux/alpha/17.0', 2 => 'Display-If-Profile: default/linux/alpha/17.0/*', 3 => 'Display-If-Profile: default/linux/amd64/17.0', 4 => 'Display-If-Profile: default/linux/amd64/17.0/*', 5 => 'Display-If-Profile: default/linux/amd64/17.1', 6 => 'Display-If-Profile: default/linux/amd64/17.1/*', 7 => 'Display-If-Profile: default/linux/arm/17.0', 8 => 'Display-If-Profile: default/linux/arm/17.0/*', 9 => 'Display-If-Profile: default/linux/arm64/17.0', 10 => 'Display-If-Profile: default/linux/arm64/17.0/*', 11 => 'Display-If-Profile: default/linux/hppa/17.0', 12 => 'Display-If-Profile: default/linux/hppa/17.0/*', 13 => 'Display-If-Profile: default/linux/ia64/17.0', 14 => 'Display-If-Profile: default/linux/ia64/17.0/*', 15 => 'Display-If-Profile: default/linux/loong/22.0', 16 => 'Display-If-Profile: default/linux/loong/22.0/*', 17 => 'Display-If-Profile: default/linux/m68k/17.0', 18 => 'Display-If-Profile: default/linux/m68k/17.0/*', 19 => 'Display-If-Profile: default/linux/mips/17.0', 20 => 'Display-If-Profile: default/linux/mips/17.0/*', 21 => 'Display-If-Profile: default/linux/powerpc/ppc64/17.0/*', 22 => 'Display-If-Profile: default/linux/ppc/17.0', 23 => 'Display-If-Profile: default/linux/ppc/17.0/*', 24 => 'Display-If-Profile: default/linux/ppc64/17.0', 25 => 'Display-If-Profile: default/linux/ppc64/17.0/*', 26 => 'Display-If-Profile: default/linux/ppc64le/17.0', 27 => 'Display-If-Profile: default/linux/ppc64le/17.0/*', 28 => 'Display-If-Profile: default/linux/riscv/20.0/*', 29 => 'Display-If-Profile: default/linux/s390/17.0', 30 => 'Display-If-Profile: default/linux/s390/17.0/*', 31 => 'Display-If-Profile: default/linux/sparc/17.0', 32 => 'Display-If-Profile: default/linux/sparc/17.0/*', 33 => 'Display-If-Profile: default/linux/x86/17.0', 34 => 'Display-If-Profile: default/linux/x86/17.0/*', 35 => 'in 2 months and removed a year later. The exact dates may depend on the ', 36 => ' In some cases (hppa, x86) the table will tell you to pick between two choices. ', 37 => ' What you need should be obvious from your *old* CHOST value (from step 4).', 38 => ' (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do ', 39 => ' that; instead, abort and try again with --nodeps added to the command line.)', 40 => '[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition', 41 => '[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline', 42 => '[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table', 43 => '[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work' ]
Lines removed in edit (removed_lines)
[ 0 => '{{WIP|author=Dilfridge}}', 1 => '', 2 => '{{Warning|Do not try to use these profiles on production systems until they are officially announced via a news item.}}', 3 => '', 4 => 'The following text is in preparation of the profile upgrade newsitem.', 5 => '', 6 => 'Posted: yyyy-mm-dd', 7 => '', 8 => '[*** Ignore this message for now if you are using musl on (32bit)', 9 => ' arm and x86. These configurations are not ready yet. ***]', 10 => 'in 2 months and removed a year later. The exact dates depend on the ', 11 => ' In rare cases (hppa, x86) the table will tell you to pick between two choices. ', 12 => ' What you need should be obvious from your *OLD* CHOST value (from step 4).', 13 => ' (If this command wants to rebuild glibc first, do *not* let it do that;', 14 => ' instead, abort and try again with only --nodeps added to the command line.)', 15 => '[1] https://wiki.g.o/wiki/Project:Toolchain/23.0_profile_transition', 16 => '[2] https://wiki.g.o/wiki/Project:Toolchain/23.0_profile_timeline', 17 => '[5] https://wiki.g.o/wiki/Project:Toolchain/23.0_update_table', 18 => '[6] https://wiki.g.o/wiki/Changing_the_CHOST_variable#Verifying_things_work' ]
New page text, stripped of any markup (new_text)
'Title: Profile upgrade to version 23.0 available Author: Andreas K. Huettel &lt;dilfridge@gentoo.org&gt; Posted: 2024-03-22 Revision: 1 News-Item-Format: 2.0 Display-If-Profile: default/linux/alpha/17.0 Display-If-Profile: default/linux/alpha/17.0/* Display-If-Profile: default/linux/amd64/17.0 Display-If-Profile: default/linux/amd64/17.0/* Display-If-Profile: default/linux/amd64/17.1 Display-If-Profile: default/linux/amd64/17.1/* Display-If-Profile: default/linux/arm/17.0 Display-If-Profile: default/linux/arm/17.0/* Display-If-Profile: default/linux/arm64/17.0 Display-If-Profile: default/linux/arm64/17.0/* Display-If-Profile: default/linux/hppa/17.0 Display-If-Profile: default/linux/hppa/17.0/* Display-If-Profile: default/linux/ia64/17.0 Display-If-Profile: default/linux/ia64/17.0/* Display-If-Profile: default/linux/loong/22.0 Display-If-Profile: default/linux/loong/22.0/* Display-If-Profile: default/linux/m68k/17.0 Display-If-Profile: default/linux/m68k/17.0/* Display-If-Profile: default/linux/mips/17.0 Display-If-Profile: default/linux/mips/17.0/* Display-If-Profile: default/linux/powerpc/ppc64/17.0/* Display-If-Profile: default/linux/ppc/17.0 Display-If-Profile: default/linux/ppc/17.0/* Display-If-Profile: default/linux/ppc64/17.0 Display-If-Profile: default/linux/ppc64/17.0/* Display-If-Profile: default/linux/ppc64le/17.0 Display-If-Profile: default/linux/ppc64le/17.0/* Display-If-Profile: default/linux/riscv/20.0/* Display-If-Profile: default/linux/s390/17.0 Display-If-Profile: default/linux/s390/17.0/* Display-If-Profile: default/linux/sparc/17.0 Display-If-Profile: default/linux/sparc/17.0/* Display-If-Profile: default/linux/x86/17.0 Display-If-Profile: default/linux/x86/17.0/* A profile upgrade to version 23.0 is available for your architecture. The new 23.0 profiles enable some toolchain hardening features and performance enhancements by default, and standardize settings. You can find the list of changes on the wiki tracking page [1]. We strongly advise to precisely follow the upgrade instructions found below. The 17.0, 17.1, 20.0, and 22.0 profiles will be marked deprecated in 2 months and removed a year later. The exact dates may depend on the architecture, see [2]. Upgrade instructions Note 1: The use of binary packages is completely optional, and also not as much tested as the source-based upgrade path yet. If you prefer to only use the traditional source-based installation, omit the "--getbinpkg" parameter in all emerge invocations. Note 2: If you have manually changed your CHOST to a value different from what the stages and profiles set, you may have to do that in the future too. In that case you should know what you are doing, hopefully; please read the instructions with a critical eye then. 1. Ensure your system backups are up to date. Please also update your system fully and depclean before proceeding. glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. 2. If you are still using one of the long-deprecated amd64 17.0 profiles (other than x32 or musl), then first complete the migration to the corresponding 17.1 profile. Instructions can be found at [3]. 3. If you are currently using systemd in a split-usr configuration, then first complete the migration to the corresponding merged-usr profile of the same profile version. Details on how to do this can be found in the news item [4]. If you are currently using openrc, migrate to 23.0 first, keeping your disk layout. If you want to move from split-usr to merged-usr, do that afterwards. 4. Run "emerge --info" and note down the value of the CHOST variable. 5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, remove it. Also delete all lines defining CHOST_... variables. 6. Select the 23.0 profile corresponding to your current profile, either using "eselect profile" or by manually setting the profile symlink. Note that old profiles are by default split-usr and the 23.0 profiles by default merged-usr. Do NOT change directory scheme now, since this will mess up your system! Instead, make sure that the new profile has the same property: for example, OLD default/linux/amd64/17.1 ==&gt; NEW default/linux/amd64/23.0/split-usr (added "split-usr") OLD default/linux/amd64/17.1/systemd/merged-usr ==&gt; NEW default/linux/amd64/23.0/systemd (removed "merged-usr") A detailed table of the upgrade paths can be found at [5]. Please consult it. In some cases (hppa, x86) the table will tell you to pick between two choices. What you need should be obvious from your *old* CHOST value (from step 4). 7. Delete the contents of your binary package cache at ${PKGDIR} rm -r /var/cache/binpkgs/* 8. In the file or directory /etc/portage/binrepos.conf (if existing), update the URI in all configuration such that they point to 23.0 profile binhost directories. The exact paths can be found in the table at [5], too. 9. Rebuild or reinstall from binary (if available) the following packages in this order, with the same version as already active: emerge --ask --oneshot --getbinpkg sys-devel/binutils (you may have to run binutils-config and re-select your binutils now) emerge --ask --oneshot --getbinpkg sys-devel/gcc (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do that; instead, abort and try again with --nodeps added to the command line.) (you may have to run gcc-config and re-select your gcc now) and the C library, i.e. for glibc-based systems emerge --ask --oneshot --getbinpkg sys-libs/glibc or for musl-based systems emerge --ask --oneshot --getbinpkg sys-libs/musl 10. Re-run "emerge --info" and check if CHOST has changed compared to step 3. If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, 11. Recheck with binutils-config and gcc-config that valid installed versions of binutils and gcc are selected. 12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that refer to the *OLD* CHOST value, and remove them. Examples how to do this can be found in the similar procedure at [6]. 13. Run env-update &amp;&amp; source /etc/profile 14. Re-emerge libtool: emerge --ask --oneshot --getbinpkg libtool 15. Just for safety, delete the contents of your binary package cache at ${PKGDIR} again: rm -r /var/cache/binpkgs/* 16. Rebuild world: emerge --ask --emptytree --getbinpkg @world [1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition [2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline [3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html [4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html [5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table [6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work'
Parsed HTML source of the new revision (new_html)
'<div class="mw-parser-output"><pre>Title: Profile upgrade to version 23.0 available Author: Andreas K. Huettel &lt;dilfridge@gentoo.org&gt; Posted: 2024-03-22 Revision: 1 News-Item-Format: 2.0 Display-If-Profile: default/linux/alpha/17.0 Display-If-Profile: default/linux/alpha/17.0/* Display-If-Profile: default/linux/amd64/17.0 Display-If-Profile: default/linux/amd64/17.0/* Display-If-Profile: default/linux/amd64/17.1 Display-If-Profile: default/linux/amd64/17.1/* Display-If-Profile: default/linux/arm/17.0 Display-If-Profile: default/linux/arm/17.0/* Display-If-Profile: default/linux/arm64/17.0 Display-If-Profile: default/linux/arm64/17.0/* Display-If-Profile: default/linux/hppa/17.0 Display-If-Profile: default/linux/hppa/17.0/* Display-If-Profile: default/linux/ia64/17.0 Display-If-Profile: default/linux/ia64/17.0/* Display-If-Profile: default/linux/loong/22.0 Display-If-Profile: default/linux/loong/22.0/* Display-If-Profile: default/linux/m68k/17.0 Display-If-Profile: default/linux/m68k/17.0/* Display-If-Profile: default/linux/mips/17.0 Display-If-Profile: default/linux/mips/17.0/* Display-If-Profile: default/linux/powerpc/ppc64/17.0/* Display-If-Profile: default/linux/ppc/17.0 Display-If-Profile: default/linux/ppc/17.0/* Display-If-Profile: default/linux/ppc64/17.0 Display-If-Profile: default/linux/ppc64/17.0/* Display-If-Profile: default/linux/ppc64le/17.0 Display-If-Profile: default/linux/ppc64le/17.0/* Display-If-Profile: default/linux/riscv/20.0/* Display-If-Profile: default/linux/s390/17.0 Display-If-Profile: default/linux/s390/17.0/* Display-If-Profile: default/linux/sparc/17.0 Display-If-Profile: default/linux/sparc/17.0/* Display-If-Profile: default/linux/x86/17.0 Display-If-Profile: default/linux/x86/17.0/* A profile upgrade to version 23.0 is available for your architecture. The new 23.0 profiles enable some toolchain hardening features and performance enhancements by default, and standardize settings. You can find the list of changes on the wiki tracking page [1]. We strongly advise to precisely follow the upgrade instructions found below. The 17.0, 17.1, 20.0, and 22.0 profiles will be marked deprecated in 2 months and removed a year later. The exact dates may depend on the architecture, see [2]. Upgrade instructions Note 1: The use of binary packages is completely optional, and also not as much tested as the source-based upgrade path yet. If you prefer to only use the traditional source-based installation, omit the "--getbinpkg" parameter in all emerge invocations. Note 2: If you have manually changed your CHOST to a value different from what the stages and profiles set, you may have to do that in the future too. In that case you should know what you are doing, hopefully; please read the instructions with a critical eye then. 1. Ensure your system backups are up to date. Please also update your system fully and depclean before proceeding. glibc older than 2.36 and musl older than 1.2.4 is not supported anymore. 2. If you are still using one of the long-deprecated amd64 17.0 profiles (other than x32 or musl), then first complete the migration to the corresponding 17.1 profile. Instructions can be found at [3]. 3. If you are currently using systemd in a split-usr configuration, then first complete the migration to the corresponding merged-usr profile of the same profile version. Details on how to do this can be found in the news item [4]. If you are currently using openrc, migrate to 23.0 first, keeping your disk layout. If you want to move from split-usr to merged-usr, do that afterwards. 4. Run "emerge --info" and note down the value of the CHOST variable. 5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable, remove it. Also delete all lines defining CHOST_... variables. 6. Select the 23.0 profile corresponding to your current profile, either using "eselect profile" or by manually setting the profile symlink. Note that old profiles are by default split-usr and the 23.0 profiles by default merged-usr. Do NOT change directory scheme now, since this will mess up your system! Instead, make sure that the new profile has the same property: for example, OLD default/linux/amd64/17.1 ==&gt; NEW default/linux/amd64/23.0/split-usr (added "split-usr") OLD default/linux/amd64/17.1/systemd/merged-usr ==&gt; NEW default/linux/amd64/23.0/systemd (removed "merged-usr") A detailed table of the upgrade paths can be found at [5]. Please consult it. In some cases (hppa, x86) the table will tell you to pick between two choices. What you need should be obvious from your *old* CHOST value (from step 4). 7. Delete the contents of your binary package cache at ${PKGDIR} rm -r /var/cache/binpkgs/* 8. In the file or directory /etc/portage/binrepos.conf (if existing), update the URI in all configuration such that they point to 23.0 profile binhost directories. The exact paths can be found in the table at [5], too. 9. Rebuild or reinstall from binary (if available) the following packages in this order, with the same version as already active: emerge --ask --oneshot --getbinpkg sys-devel/binutils (you may have to run binutils-config and re-select your binutils now) emerge --ask --oneshot --getbinpkg sys-devel/gcc (IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do that; instead, abort and try again with --nodeps added to the command line.) (you may have to run gcc-config and re-select your gcc now) and the C library, i.e. for glibc-based systems emerge --ask --oneshot --getbinpkg sys-libs/glibc or for musl-based systems emerge --ask --oneshot --getbinpkg sys-libs/musl 10. Re-run "emerge --info" and check if CHOST has changed compared to step 3. If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise, 11. Recheck with binutils-config and gcc-config that valid installed versions of binutils and gcc are selected. 12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that refer to the *OLD* CHOST value, and remove them. Examples how to do this can be found in the similar procedure at [6]. 13. Run env-update &amp;&amp; source /etc/profile 14. Re-emerge libtool: emerge --ask --oneshot --getbinpkg libtool 15. Just for safety, delete the contents of your binary package cache at ${PKGDIR} again: rm -r /var/cache/binpkgs/* 16. Rebuild world: emerge --ask --emptytree --getbinpkg @world [1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition [2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline [3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html [4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html [5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table [6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work </pre> '
Unix timestamp of change (timestamp)
1711136981
Retrieved from "https://wiki.gentoo.org/wiki/Special:AbuseLog/4814"