public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] WARNING: Do not update your system on ~amd64
Date: Wed, 17 Jun 2020 10:38:54 +0100	[thread overview]
Message-ID: <20200617103854.600cc6ee@digimed.co.uk> (raw)
In-Reply-To: <0MOzwh-1jrEsA1EBz-006LGd@smtp.web.de>

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

On Wed, 17 Jun 2020 11:03:00 +0200, Andreas Fink wrote:

> > > Thanks for the heads up. To play safe, I emerge passwdqc before
> > > emerging @world. It actually emerge without complaint on the three
> > > systems I tried. I also made sure I could SSH in after updating PAM
> > > before terminating the existing session.  
> >
> > MAKEOPTS="-j1" emerge -1 passwdqc worked here. Sys-libs/pam had
> > already installed by the time passwdqc failed the first time.
> > Sys-auth/pam is not in my update list, but sys-auth/pambase is, and
> > has installed without protest. 
> 
> Either USE="-passwdqc" for pambase or MAKEOPTS="-j1" for passwdqc works
> consistently for me too. I think you just need to make sure that
> pam+pambase are both updated before logging out ;)
> One system that I had to rescue from a live system + chroot :(

Interestingly, I've now emerged passwordqc successfully on four systems,
with MAKEOPTS ranging from -j2 to j8. Only the 4th failed, and that
worked when I went from -j4 to -j3. This appears to be a bit of a
borderline case, which may explain why it slipped through.


-- 
Neil Bothwick

If at first you don't succeed, give up. No use being a damn fool.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-17  9:39 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 [this message]
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 ` [gentoo-user] " Rich Freeman

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=20200617103854.600cc6ee@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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