From: "Carter, Dwayne" <DCarter@nettelcos.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] portage problems
Date: Sat, 2 Feb 2008 16:02:05 -0500 [thread overview]
Message-ID: <9D4E782526F9314EB25B3B2BEB4D2A2DAC8DF8@intexch1.cbb.local> (raw)
In-Reply-To: <47A42458.3050309@bellsouth.net>
Dale:
Thanks for the input, I have successfully resolved the pam-login issue,
I have to adjusted all the /etc/pam.d entry to remove the pam_stack
entry and update them with "<type> include system-auth".
I just removed the dhcpcd-2.0.0 since it is not part of the system tree
anymore.
I am still working on the python and modutils. As far as updates I just
inherited this server at work so, I don't really know when it was last
updated.
Thanks for the great information and input.
Dwayne Carter
-----Original Message-----
From: Dale [mailto:dalek1967@bellsouth.net]
Sent: Saturday, February 02, 2008 3:06 AM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage problems
Carter, Dwayne wrote:
> << SNIP >>
> [blocks B ] <dev-lang/python-2.3.6-r2 (is blocking
app-admin/python-updater-0.2)
>
> [blocks B ] sys-apps/pam-login (is blocking
sys-apps/shadow-4.0.18.1-r1)
> [blocks B ] <net-misc/dhcpcd-2.0.0 (is blocking
sys-apps/baselayout-1.12.10-r5)
> [blocks B ] sys-apps/modutils (is blocking
sys-apps/module-init-tools-3.4)
> << SNIP >>
Normally I would say unmerge the blocks and emerge the blockers and
update them first. However, I'm not sure about that pam-login one. If
you do unmerge that one, do NOT logout until you have it updated. I
would recommend switching to another console and logging in to make sure
it works too.
> [ebuild U ] dev-libs/expat-2.0.1 [1.95.6-r1]
Oh no, is that the one I think it is. You may want to search the forums
for the expat update. Let me know if you can't find it. Has it been a
while since you updated?
Maybe someone else will see something else and chime in.
Dale
:-) :-)
--
gentoo-user@lists.gentoo.org mailing list
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-02 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 22:54 [gentoo-user] portage problems Carter, Dwayne
2008-02-01 23:03 ` Alan McKinnon
2008-02-02 6:02 ` Carter, Dwayne
2008-02-02 8:05 ` Dale
2008-02-02 8:55 ` Alan McKinnon
2008-02-02 21:02 ` Carter, Dwayne [this message]
2008-02-02 10:20 ` Daniel Pielmeier
2008-02-02 14:28 ` Alan McKinnon
2008-02-02 14:55 ` Daniel Pielmeier
2008-02-02 15:14 ` Alan McKinnon
-- strict thread matches above, loose matches on Subject: below --
2004-12-05 21:37 Luigi Pinna
2004-12-05 23:52 ` Bastian Balthazar Bux
2004-12-06 0:07 ` Luigi Pinna
2004-12-06 0:46 ` Bastian Balthazar Bux
2004-12-06 0:46 ` Jason Stubbs
2004-12-06 0:58 ` Luigi Pinna
2004-12-06 3:38 ` cdemarco
2004-12-06 3:58 ` Jason Stubbs
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=9D4E782526F9314EB25B3B2BEB4D2A2DAC8DF8@intexch1.cbb.local \
--to=dcarter@nettelcos.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