| 1 |
On Thu, 15 Jun 2006 15:35:35 +0200, Jarry wrote: |
| 2 |
|
| 3 |
> emerge --pretend --update --deep --newuse world |
| 4 |
> [blocks B ] sys-apps/utempter (is blocking sys-libs/libutempter-1.1.2.1) |
| 5 |
> [blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.15-r2) |
| 6 |
> [ebuild N ] sys-libs/libutempter-1.1.2.1 |
| 7 |
> [ebuild U ] x11-terms/xterm-212-r3 [207] |
| 8 |
> [ebuild U ] sys-apps/shadow-4.0.15-r2 [4.0.14-r1] |
| 9 |
> |
| 10 |
> What is the proper way of dealing with it? |
| 11 |
|
| 12 |
This has already been discussed several times in the past week or so. |
| 13 |
|
| 14 |
> Should I simply unmerge |
| 15 |
> (-C) utempter and pam-login? |
| 16 |
|
| 17 |
Yes. |
| 18 |
|
| 19 |
> Is it not dangerous? I do not know what |
| 20 |
> utempter is good for, but if I unmerge pam-login and then from some |
| 21 |
> reason I will not succeed in updating shadow, I will not be able |
| 22 |
> to log in at all... |
| 23 |
|
| 24 |
In the unlikely event that were to happen, simply re-emerge pam-login. |
| 25 |
If you don't have the blocking shadow, it won't complain. |
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
Neil Bothwick |
| 30 |
|
| 31 |
WinErr 005: Multitasking attempted - System confused |
Archives