From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: pr@gentoo.org, toolchain@gentoo.org, Sam James <sam@gentoo.org>
Subject: [gentoo-dev] [PATCH 2/2] 2021-06-30-libxcrypt-migration: mention possible build order problems
Date: Tue, 20 Jul 2021 18:45:47 +0100 [thread overview]
Message-ID: <20210720174547.1946438-2-sam@gentoo.org> (raw)
In-Reply-To: <20210720174547.1946438-1-sam@gentoo.org>
Bug: https://bugs.gentoo.org/802210
Signed-off-by: Sam James <sam@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
next prev parent reply other threads:[~2021-07-20 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 17:45 [gentoo-dev] [PATCH 1/2] 2021-06-30-libxcrypt-migration: mention PAM/md5crypt issues Sam James
2021-07-20 17:45 ` Sam James [this message]
2021-07-20 19:57 ` Ulrich Mueller
2021-07-20 21:24 ` Sam James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210720174547.1946438-2-sam@gentoo.org \
--to=sam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@gentoo.org \
--cc=toolchain@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox