From: Andreas Fink <finkandreas@web.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] WARNING: Do not update your system on ~amd64
Date: Wed, 17 Jun 2020 07:34:41 +0200 [thread overview]
Message-ID: <1N9cHX-1iqyZS0VpV-015TL9@smtp.web.de> (raw)
Hello,
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.
One system that I updated and restarted, I cannot login to it anymore
(or ssh into it). Another system that I updated and currently am
writing from, I'm still logged in after the broken update. and I can
see the following error message (before disabling the USE flag passwdqc
for the package pambase):
PAM unable to dlopen(/lib64/security/pam_cracklib.so): /lib64/security/pam_cracklib.so: cannot open shared object file: No such file or directory
PAM adding faulty module: /lib64/security/pam_cracklib.so
After doing a
USE=-passwdqc emerge -a1 pambase
the error messages disappear from the system logs and I am able to
login to my machine again. However if you reboot with the broken state
you will have a hard time updating it, since you cannot login to your
machine anymore and need a chroot from a live system.
The bug report for passwdqc is here:
https://bugs.gentoo.org/728528
Cheers
Andreas
next reply other threads:[~2020-06-17 5:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 5:34 Andreas Fink [this message]
2020-06-17 8:29 ` [gentoo-user] WARNING: Do not update your system on ~amd64 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 ` [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=1N9cHX-1iqyZS0VpV-015TL9@smtp.web.de \
--to=finkandreas@web.de \
--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