Bug: https://bugs.gentoo.org/802210 Signed-off-by: Sam James <s...@gentoo.org> --- .../2021-06-30-libxcrypt-migration.en.txt | 9 +++++++++ 1 file changed, 9 insertions(+)
diff --git a/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt index 5a78036..e1a7ac5 100644 --- a/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt +++ b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt @@ -48,9 +48,18 @@ a bug in PAM [0][1] may mean that you were unable to login. We recommend using `passwd` to change/refresh your passwrd so it is using modern 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 +libcrypt and libxcrypt first: + +# emerge -v1 virtual/libcrypt sys-libs/libxcrypt + +And then continue the world upgrade with --keep-going=y. + For more information, please see: * https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation * https://bugs.gentoo.org/699422 [0] https://bugs.gentoo.org/802267 [1] https://bugs.gentoo.org/802807 +[2] https://bugs.gentoo.org/802210 -- 2.32.0
