From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JK5Os-0003wC-Bc for garchives@archives.gentoo.org; Wed, 30 Jan 2008 05:22:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0FE84E02FD; Wed, 30 Jan 2008 05:22:14 +0000 (UTC) Received: from spore.ath.cx (66-191-143-114.static.roch.mn.charter.com [66.191.143.114]) by pigeon.gentoo.org (Postfix) with ESMTP id E4F87E02FD for ; Wed, 30 Jan 2008 05:22:13 +0000 (UTC) Received: from pascal.spore.ath.cx (pascal.spore.ath.cx [192.168.1.100]) by spore.ath.cx (Postfix) with ESMTP id 9A0594FE6 for ; Tue, 29 Jan 2008 23:22:13 -0600 (CST) Date: Tue, 29 Jan 2008 23:22:13 -0600 From: Dan Farrell To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] pam upgrade issue Message-ID: <20080129232213.0212d62b@pascal.spore.ath.cx> In-Reply-To: <697772.28752.qm@web31704.mail.mud.yahoo.com> References: <697772.28752.qm@web31704.mail.mud.yahoo.com> Organization: Spore, Ltd. X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.1; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 5510b73e-425d-48e3-aa7c-426517a778c0 X-Archives-Hash: d4246be3de2465df0ee373e2146a75e0 On Tue, 29 Jan 2008 16:32:19 -0800 (PST) maxim wexler 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