| 1 |
Dale writes: |
| 2 |
|
| 3 |
> I am running into the same thing. I'm updating everything else then |
| 4 |
> going to tackle this. In theory, you have to unmerge device-mapper |
| 5 |
> then let it update. Something like: |
| 6 |
> |
| 7 |
> emerge -C device-mapper && emerge -uvDN world |
| 8 |
> |
| 9 |
> That's my plan at least. Unless someone else posts a better one. |
| 10 |
|
| 11 |
I just unmerged device-mapper and updated lvm2 right after that. So in |
| 12 |
case of a crash or something during a longer world update I still have an |
| 13 |
intact system. I'm not sure if it would boot with the old lvm2 and without |
| 14 |
device-mapper, probably yes, but I did not want to take any risk. |
| 15 |
|
| 16 |
Um, shouldn't the new portage have dealt auto-magically with this blocker? |
| 17 |
|
| 18 |
Wonko |
Archives