[gentoo-user] emerge --update: utempter/pam-login is blocking...

[gentoo-user] emerge --update: utempter/pam-login is blocking...

[Jarry]

Hi,
I tried to update my gentoo-laptop but I got this message:

emerge --update --deep --newuse world
!!! Error: the sys-apps/utempter package conflicts with another package
!!! the two packages cannot be insalled on the same system together.
!!! Please use 'emerge --pretend' to determine blockers.

emerge --pretend --update --deep --newuse world
[blocks B ] sys-apps/utempter (is blocking sys-libs/libutempter-1.1.2.1)
[blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.15-r2)
[ebuild N ] sys-libs/libutempter-1.1.2.1
[ebuild U ] x11-terms/xterm-212-r3 [207]
[ebuild U ] sys-apps/shadow-4.0.15-r2 [4.0.14-r1]

What is the proper way of dealing with it? Should I simply unmerge
(-C) utempter and pam-login? Is it not dangerous? I do not know what
utempter is good for, but if I unmerge pam-login and then from some
reason I will not succeed in updating shadow, I will not be able
to log in at all...

Jarry
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --update: utempter/pam-login is blocking...

[Nico Schümann]

[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]

2006/6/15, Jarry <jarry@gmx.net>:
>
> Hi,
> I tried to update my gentoo-laptop but I got this message:
>
> emerge --update --deep --newuse world
> !!! Error: the sys-apps/utempter package conflicts with another package
> !!! the two packages cannot be insalled on the same system together.
> !!! Please use 'emerge --pretend' to determine blockers.
>
> emerge --pretend --update --deep --newuse world
> [blocks B ] sys-apps/utempter (is blocking sys-libs/libutempter-1.1.2.1)
> [blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.15-r2)
> [ebuild N ] sys-libs/libutempter-1.1.2.1
> [ebuild U ] x11-terms/xterm-212-r3 [207]
> [ebuild U ] sys-apps/shadow-4.0.15-r2 [4.0.14-r1]
>
> What is the proper way of dealing with it? Should I simply unmerge
> (-C) utempter and pam-login? Is it not dangerous? I do not know what
> utempter is good for, but if I unmerge pam-login and then from some
> reason I will not succeed in updating shadow, I will not be able
> to log in at all...
>
> Jarry
> --
> gentoo-user@gentoo.org mailing list
>
>
emerge --unmerge utempter
emerge --unmerge pam-login

I think, they've changed something (login etc. is provided by shadow, now /
utempter / libutempter seems to be a rename)

You can log in again if the emerge -uDav is finished (everything works fine
after I've done that way)

[-- Attachment #2: Type: text/html, Size: 1707 bytes --]

[gentoo-user] Re: emerge --update: utempter/pam-login is blocking...

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 777 bytes --]

> emerge --pretend --update --deep --newuse world
> [blocks B ] sys-apps/utempter (is blocking sys-libs/libutempter-1.1.2.1)
> [blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.15-r2)
> [ebuild N ] sys-libs/libutempter-1.1.2.1
> [ebuild U ] x11-terms/xterm-212-r3 [207]
> [ebuild U ] sys-apps/shadow-4.0.15-r2 [4.0.14-r1]
> 
> What is the proper way of dealing with it? Should I simply unmerge
> (-C) utempter and pam-login? Is it not dangerous? I do not know what
> utempter is good for, but if I unmerge pam-login and then from some
> reason I will not succeed in updating shadow, I will not be able
> to log in at all...

Unmerge pam-login, and emmediatly do a "emerge -1 shadow" after that.
shadow now provides the things necessary to login.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

Re: [gentoo-user] emerge --update: utempter/pam-login is blocking...

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

On Thu, 15 Jun 2006 15:35:35 +0200, Jarry wrote:

> emerge --pretend --update --deep --newuse world
> [blocks B ] sys-apps/utempter (is blocking sys-libs/libutempter-1.1.2.1)
> [blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.15-r2)
> [ebuild N ] sys-libs/libutempter-1.1.2.1
> [ebuild U ] x11-terms/xterm-212-r3 [207]
> [ebuild U ] sys-apps/shadow-4.0.15-r2 [4.0.14-r1]
> 
> What is the proper way of dealing with it?

This has already been discussed several times in the past week or so.

> Should I simply unmerge
> (-C) utempter and pam-login?

Yes.

> Is it not dangerous? I do not know what
> utempter is good for, but if I unmerge pam-login and then from some
> reason I will not succeed in updating shadow, I will not be able
> to log in at all...

In the unlikely event that were to happen, simply re-emerge pam-login.
If you don't have the blocking shadow, it won't complain.


-- 
Neil Bothwick

WinErr 005: Multitasking attempted - System confused

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]