| 1 |
On 2013-03-17 2:17 PM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Sun, 17 Mar 2013 13:46:39 -0400, Tanstaafl wrote: |
| 3 |
> |
| 4 |
>> Also, should I manually fix the blockers: |
| 5 |
>> |
| 6 |
>>> [blocks B ] sys-apps/module-init-tools |
| 7 |
>>> ("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1) |
| 8 |
>>> [blocks B ] sys-apps/kmod ("sys-apps/kmod" is blocking |
| 9 |
>>> sys-apps/module-init-tools-3.16-r2) |
| 10 |
>> |
| 11 |
>> by doing "emerge -C module-init-tools && emerge kmod" *before* |
| 12 |
>> upgrading udev? |
| 13 |
> |
| 14 |
> No, because that adds kmod to world. Just unmerge module-init-tools and |
| 15 |
> then emerge world, letting portage install what it needs |
| 16 |
|
| 17 |
Ah, ok... but as for the rest... I should be able to safely upgrade |
| 18 |
udev, with a reasonable (I know there are no guarantees) expectation of |
| 19 |
everything 'just working' (ie, my lvm managed /usr partition shouldn't |
| 20 |
be an issue like it would have been earlier on in this process)? |
| 21 |
|
| 22 |
Thanks Neil |
Archives