| 1 |
On Wed, 17 Jun 2020 09:51:13 +0100 |
| 2 |
Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 3 |
|
| 4 |
> On Wednesday, 17 June 2020 09:29:39 BST Neil Bothwick wrote: |
| 5 |
> > On Wed, 17 Jun 2020 07:34:41 +0200, Andreas Fink wrote: |
| 6 |
> > > I've noticed a problem with the current PAM update to |
| 7 |
> > > sys-libs/pam-1.4.0. |
| 8 |
> > > The update adds passwdqc USE to sys-auth/pambase, which pulls in |
| 9 |
> > > sys-auth/passwdqc. However sys-auth/passwdqc fails to build on my |
| 10 |
> > > system, and leaves me with an installed sys-libs/pam-1.4.0 which is |
| 11 |
> > > broken and does not allow any new login. |
| 12 |
> > > The end result is that sys-libs/pam-1.4.0 was successfully merged but |
| 13 |
> > > sys-auth/pambase will not be merged, due to a build failure in passwdqc. |
| 14 |
> > > Disabling the USE flag passwdqc for pambase allows an update to pambase |
| 15 |
> > > too, and logins work again. |
| 16 |
> > > This is a warning to anyone out there who updates daily and runs an |
| 17 |
> > > ~amd64. |
| 18 |
> > |
| 19 |
> > Thanks for the heads up. To play safe, I emerge passwdqc before emerging |
| 20 |
> > @world. It actually emerge without complaint on the three systems I |
| 21 |
> > tried. I also made sure I could SSH in after updating PAM before |
| 22 |
> > terminating the existing session. |
| 23 |
> |
| 24 |
> MAKEOPTS="-j1" emerge -1 passwdqc worked here. Sys-libs/pam had already |
| 25 |
> installed by the time passwdqc failed the first time. Sys-auth/pam is not in my |
| 26 |
> update list, but sys-auth/pambase is, and has installed without protest. |
| 27 |
> |
| 28 |
|
| 29 |
Either USE="-passwdqc" for pambase or MAKEOPTS="-j1" for passwdqc works |
| 30 |
consistently for me too. I think you just need to make sure that |
| 31 |
pam+pambase are both updated before logging out ;) |
| 32 |
One system that I had to rescue from a live system + chroot :( |
Archives