| 1 |
Bug: https://bugs.gentoo.org/802210 |
| 2 |
Signed-off-by: Sam James <sam@g.o> |
| 3 |
--- |
| 4 |
.../2021-06-30-libxcrypt-migration.en.txt | 11 ++++++++++- |
| 5 |
1 file changed, 10 insertions(+), 1 deletion(-) |
| 6 |
|
| 7 |
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 |
| 8 |
index 2ba8523..fb16a29 100644 |
| 9 |
--- a/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt |
| 10 |
+++ b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt |
| 11 |
@@ -48,9 +48,18 @@ a bug in PAM [0][1] may mean that you were unable to login. We recommend |
| 12 |
using "passwd" to change/refresh your password so it is using modern |
| 13 |
methods. A new version of PAM has been added to the tree to resolve this issue. |
| 14 |
|
| 15 |
-For more information, please see: |
| 16 |
+In some cases, Portage may schedule a rebuild of certain packages in an |
| 17 |
+incorrect order [2]. If building a package fails, please try upgrading |
| 18 |
+libcrypt and libxcrypt first: |
| 19 |
+ |
| 20 |
+# emerge -v1 virtual/libcrypt sys-libs/libxcrypt |
| 21 |
+ |
| 22 |
+And then continue the world upgrade with Portage's "--keep-going=y". |
| 23 |
+ |
| 24 |
+For more information or troubleshooting tips, please see: |
| 25 |
* https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation |
| 26 |
* https://bugs.gentoo.org/699422 |
| 27 |
|
| 28 |
[0] https://bugs.gentoo.org/802267 |
| 29 |
[1] https://bugs.gentoo.org/802807 |
| 30 |
+[2] https://bugs.gentoo.org/802210 |
| 31 |
-- |
| 32 |
2.32.0 |
Archives