commit: 1c4eb83b3e4a1f453d16e8a2356ddf61651b5310 Author: Sam James <sam <AT> gentoo <DOT> org> AuthorDate: Fri Nov 12 04:58:26 2021 +0000 Commit: Sam James <sam <AT> gentoo <DOT> org> CommitDate: Fri Nov 12 04:58:26 2021 +0000 URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=1c4eb83b
2021-10-18-libxcrypt-migration-stable: mention being in root shell if possible Bug: https://bugs.gentoo.org/699422 Bug: https://bugs.gentoo.org/809410 Signed-off-by: Sam James <sam <AT> gentoo.org> .../2021-10-18-libxcrypt-migration-stable.en.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt b/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt index 26aa53a..feddaf6 100644 --- a/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt +++ b/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,
