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 09:29:39 +0100 [thread overview]
Message-ID: <20200617092939.2da427be@digimed.co.uk> (raw)
In-Reply-To: <1N9cHX-1iqyZS0VpV-015TL9@smtp.web.de>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
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.
--
Neil Bothwick
IBM: Itty Bitty Mentality
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-17 8:29 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 [this message]
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=20200617092939.2da427be@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