From: Dan Farrell <dan@spore.ath.cx>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] pam upgrade issue
Date: Tue, 29 Jan 2008 23:22:13 -0600 [thread overview]
Message-ID: <20080129232213.0212d62b@pascal.spore.ath.cx> (raw)
In-Reply-To: <697772.28752.qm@web31704.mail.mud.yahoo.com>
On Tue, 29 Jan 2008 16:32:19 -0800 (PST)
maxim wexler <blissfix@yahoo.com> wrote:
> Hi group,
>
> Now emerge -uD world barfs at pam-0.99 and directs me
> to
>
> http://www.gentoo.org/proj/en/base/pam/upgrade-0.99.xml
>
> Here, among other things, it says to edit certain
> files, but it doesn't say which ones? Unless it means
> all of the ones under /etc/pam.d/ I checked several of
> them and none mentions pam_stack.so
>
> It mentions two new packages pam_userdb and
> pam_chroot.
> Doesn't say to emerge them but I tried nonetheless.
> Attempts to emerge them fail with the same notice for
> both of them:
>
>
> * Your current setup is using the pam_stack module.
> * This module is deprecated and no longer supported,
> and since version
> * 0.99 is no longer installed, nor provided by any
> other package.
> * The package will be built (to allow binary package
> builds), but will
> * not be installed.
> * Please replace pam_stack usage with proper include
> directive usage,
> * following the PAM Upgrade guide at the following
> URL
> *
> http://www.gentoo.org/proj/en/base/pam/upgrade-0.99.xml
> *
>
> I took a chance and unmerged the deprecated pam and
> now I can't su and probably other stuff I don't know
> about yet.
>
Leave all your root consoles open. You won't be able to log in
until you fix PAM. From your source:
"All the changes described have to be applied to each file in
the /etc/pam.d/ directory (the PAM configuration files). Please make
sure you remove eventual backup files (*~) before trying to update
sys-libs/pam, or the emerge process will fail as a safety measure.
As a safety device, the sys-libs/pam ebuild checks the files present
in /etc/pam.d/ for the now-deprecated modules, and stops the merge
process in case they are still used, to avoid locking you out of your
own system. "
All files in /etc/pam.d must be updated; if you unmerged PAM might
well have been the only version available:
> * The package will be built (to allow binary package
> builds), but will not be installed.
Update the config files (as necessary - and remove backup copies) and
then remerge the package.
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-30 5:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 0:32 [gentoo-user] pam upgrade issue maxim wexler
2008-01-30 5:22 ` Dan Farrell [this message]
2008-01-30 5:23 ` Hal Martin
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=20080129232213.0212d62b@pascal.spore.ath.cx \
--to=dan@spore.ath.cx \
--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