public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/
Date: Thu, 22 Jul 2021 23:41:23 +0000 (UTC)	[thread overview]
Message-ID: <1626997270.b941f15ae7ad7e46c89e1ac42495e5d95893cc5a.sam@gentoo> (raw)

commit:     b941f15ae7ad7e46c89e1ac42495e5d95893cc5a
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 20 17:44:48 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jul 22 23:41:10 2021 +0000
URL:        https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=b941f15a

2021-06-30-libxcrypt-migration: mention possible build order problems

Bug: https://bugs.gentoo.org/802210
Signed-off-by: Sam James <sam <AT> gentoo.org>

 .../2021-06-30-libxcrypt-migration.en.txt                     | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

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 2ba8523..fb16a29 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 password so it is using modern
 methods. A new version of PAM has been added to the tree to resolve this issue.
 
-For more information, please see:
+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 Portage's "--keep-going=y".
+
+For more information or troubleshooting tips, 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


             reply	other threads:[~2021-07-22 23:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 23:41 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-22 23:41 [gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/ Sam James
2021-07-05 23:46 Sam James
2021-07-01  6:51 Sam James
2021-06-30 21:18 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=1626997270.b941f15ae7ad7e46c89e1ac42495e5d95893cc5a.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.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