summaryrefslogtreecommitdiff
path: root/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt
diff options
context:
space:
mode:
Diffstat (limited to 'metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt')
-rw-r--r--metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt b/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt
index 63eaaa8f8a32..feddaf62ba42 100644
--- a/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt
+++ b/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt
@@ -21,6 +21,11 @@ specific case, it is useful to have a simplified depgraph
to ensure that Portage is able to smoothly calculate
an upgrade path.
+We also recommend being in a root shell (not via 'sudo'
+or similar tools) so that if any issues occur during the upgrade,
+you are not locked out of the console. It is not expected
+that any such issues will occur but this is a precaution.
+
It is also recommended that users do _not_ have
FEATURES="collision-protect" enabled because it is
aggressive in protecting even orphaned files. Instead,
@@ -55,8 +60,10 @@ methods. A new version of PAM has been added to the tree to resolve this issue.
In some cases, Portage may schedule a rebuild of certain packages in an
incorrect order [2]. If building a package fails, please try upgrading
+Python itself to help avoid spurious build failures, and then
libcrypt and libxcrypt first:
+# emerge -v1 --ignore-built-slot-operator-deps=y dev-lang/python:3.8 dev-lang/python:3.9
# emerge -v1 virtual/libcrypt sys-libs/libxcrypt
And then continue the world upgrade with Portage's "--keep-going=y".