From: "Vernon A. Fort" <vfort@provident-solutions.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] pam errors in update world - how to trackdown
Date: Fri, 12 Oct 2007 18:34:19 -0500 [thread overview]
Message-ID: <4710047B.5060307@provident-solutions.com> (raw)
In-Reply-To: <87ejg1fwfg.fsf@newsguy.com>
reader@newsguy.com wrote:
> I'm getting an error when update world tries to install sys-libs/pam
> that tell me this:
>
>
>>>> Merging sys-libs/pam-0.99.8.1-r1 to /
>>>>
> *
> * Your current setup is using one or more of the following modules,
> * that are not built or supported anymore:
> * pam_pwdb, pam_radius, pam_timestamp
> * If you are in real need for these modules, please contact the maintainers
> * of PAM through http://bugs.gentoo.org/ providing information about its
> * use cases.
> *
> * ERROR: sys-libs/pam-0.99.8.1-r1 failed.
> * Call stack:
> * ebuild.sh, line 1703: Called dyn_preinst
> * ebuild.sh, line 1142: Called pkg_preinst
> * pam-0.99.8.1-r1.ebuild, line 162: Called die
> * The specific snippet of code:
> * check_old_modules || die "deprecated PAM modules still used"
> * The die message:
> * deprecated PAM modules still used
>
>
> Apparently I need to remove one or more of those listed but having a
> time finding them.
>
> equery files pam turns up nothing with those names
> equery list|grep shows no promising hits on pwdb, radius or timestamp
>
> I did find a pwdb package but it shows no hits on those names either.
>
> How might I track this down? Or is the error really about something
> else?
>
had the same issue - re-emerge cracklib (emerge cracklib) - look at the
errors just above.
Vernon
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-12 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 16:28 [gentoo-user] pam errors in update world - how to trackdown reader
2007-10-12 23:34 ` Vernon A. Fort [this message]
2007-10-13 4:08 ` [gentoo-user] " reader
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=4710047B.5060307@provident-solutions.com \
--to=vfort@provident-solutions.com \
--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