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.
pgpg4JnlwkzdG.pgp
Description: OpenPGP digital signature
