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