> 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: signature.asc
Description: OpenPGP digital signature

Reply via email to