public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] WARNING: Do not update your system on ~amd64
Date: Fri, 19 Jun 2020 08:52:19 -0400	[thread overview]
Message-ID: <CAGfcS_ko+dZbKz_LTSS-6Y86zuGS37o5-Co+bcfSSaH3zg4Fig@mail.gmail.com> (raw)
In-Reply-To: <1N9cHX-1iqyZS0VpV-015TL9@smtp.web.de>

On Wed, Jun 17, 2020 at 1:34 AM Andreas Fink <finkandreas@web.de> wrote:
>
> The bug report for passwdqc is here:
> https://bugs.gentoo.org/728528
>

Since this thread seems to still be a thing, I'll point out that this
bug was fixed not too long after this thread started.  At this point
there is probably little reason to worry about this update.  Certainly
at the time the warning was useful.

It was just a multi-threaded build issue.  Hard to believe upstream
devs still are creating these issues in the era of Ryzen, but it was
fixed with forcing -j1 in the ebuild.  If you see problems like this
setting -j1 via package.env will generally address the problem.  And
yes, the fact that sometimes it failed and other times it didn't is
the hallmark of these sorts of issues - it is a race condition.

-- 
Rich


      parent reply	other threads:[~2020-06-19 12:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17  5:34 [gentoo-user] WARNING: Do not update your system on ~amd64 Andreas Fink
2020-06-17  8:29 ` Neil Bothwick
2020-06-17  8:51   ` Peter Humphrey
2020-06-17  9:03     ` Andreas Fink
2020-06-17  9:38       ` Neil Bothwick
2020-06-19  9:55         ` Peter Humphrey
2020-06-19 10:49           ` Neil Bothwick
2020-06-19 12:31             ` Arve Barsnes
2020-06-19 15:43               ` [gentoo-user] " Nikos Chantziaras
2020-06-20 21:41                 ` Viktar Patotski
2020-06-21 13:08                   ` Nikos Chantziaras
2020-06-19 12:52 ` Rich Freeman [this message]

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=CAGfcS_ko+dZbKz_LTSS-6Y86zuGS37o5-Co+bcfSSaH3zg4Fig@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@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