On 03/30/2013 11:24 PM, Tanstaafl
wrote:
Ok, I don't understand this... My reading is: there are some packages either in your tree or being pulled in that require a later version of udev. So even if you mask udev-197, it's still being pulled in by something else. You have to uninstall / mask those package versions as well. How they got there or what they are, I don't know. If you're unlucky that might just be because the portage tree was in the middle of syncing... As for 186, emerge is hilariously tripping all over itself here. sys-fs/udev is being upgraded, but it requires udev-init-scripts to be installed. And udev-init-scripts conflicts with older versions of udev which is installed, so... Try increasing the backtrack to see if emerge can resolve it automatically. --backtrack=30. If it can't, the canon advice would be to manually uninstall (emerge -C --deselect=n) the older version before installing the newer one. |
- [gentoo-user] udev-197 vs udev-200?? Tanstaafl
- Re: [gentoo-user] udev-197 vs udev-200?? Neil Bothwick
- Re: [gentoo-user] udev-197 vs udev-200?? Tanstaafl
- Re: [gentoo-user] udev-197 vs udev-200?? Neil Bothwick
- Re: [gentoo-user] udev-197 vs udev-200?... Neil Bothwick
- Re: [gentoo-user] udev-197 vs udev-200?? Mark David Dumlao
- Re: [gentoo-user] udev-197 vs udev-200?? Tanstaafl