On Wed, 17 Jun 2020 09:51:13 +0100 Peter Humphrey <pe...@prh.myzen.co.uk> wrote:
> On Wednesday, 17 June 2020 09:29:39 BST Neil Bothwick wrote: > > On Wed, 17 Jun 2020 07:34:41 +0200, Andreas Fink wrote: > > > I've noticed a problem with the current PAM update to > > > sys-libs/pam-1.4.0. > > > The update adds passwdqc USE to sys-auth/pambase, which pulls in > > > sys-auth/passwdqc. However sys-auth/passwdqc fails to build on my > > > system, and leaves me with an installed sys-libs/pam-1.4.0 which is > > > broken and does not allow any new login. > > > The end result is that sys-libs/pam-1.4.0 was successfully merged but > > > sys-auth/pambase will not be merged, due to a build failure in passwdqc. > > > Disabling the USE flag passwdqc for pambase allows an update to pambase > > > too, and logins work again. > > > This is a warning to anyone out there who updates daily and runs an > > > ~amd64. > > > > 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 :(
