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 | 9 +++++++++ |
5 |
1 file changed, 9 insertions(+) |
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 5a78036..e1a7ac5 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 passwrd so it is using modern |
13 |
methods. A new version of PAM has been added to the tree to resolve this issue. |
14 |
|
15 |
+In some cases, Portage may schedule a rebuild of certain packages in an |
16 |
+incorrect order [2]. If building a package fails, please try upgrading |
17 |
+libcrypt and libxcrypt first: |
18 |
+ |
19 |
+# emerge -v1 virtual/libcrypt sys-libs/libxcrypt |
20 |
+ |
21 |
+And then continue the world upgrade with --keep-going=y. |
22 |
+ |
23 |
For more information, please see: |
24 |
* https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation |
25 |
* https://bugs.gentoo.org/699422 |
26 |
|
27 |
[0] https://bugs.gentoo.org/802267 |
28 |
[1] https://bugs.gentoo.org/802807 |
29 |
+[2] https://bugs.gentoo.org/802210 |
30 |
-- |
31 |
2.32.0 |