On 03/26/2017 05:34 PM, Neil Bothwick wrote: > On Sat, 25 Mar 2017 16:58:25 -0600, the...@sys-concept.com wrote: > >>> To repeat what I said before, a virtual and the package satisfying it >>> must have matching USE flags. If your flags for virtual/libudev and >>> eudev don't match, portage will try to install the default for >>> libudev, which is udev. That then causes a conflict as you can't have >>> udev and libudev installed at the same time. >> >> Here is the output: >> >> grep -r udev /etc/portage >> /etc/portage/package.use:sys-fs/udev extras >> /etc/portage/package.use:=sys-fs/eudev-1.10-r2 abi_x86_32 >> /etc/portage/package.use:>=virtual/libudev-215-r1 abi_x86_32 >> /etc/portage/package.use:>=sys-fs/udev-225-r1 abi_x86_32 >> /etc/portage/package.use:>=dev-libs/libgudev-230-r1 abi_x86_32 > > There's the problem, you have enabled the abi_x86_32 USE flag for all > versions of udev and the libudev virtual, bit only for one specific > version of eudev, so the only way portage can upgrade virtual/libudev is > to install udev, which conflicts with eudev. Fix package.use to the > entries for libudev and eudev match.
Yes, that might have been a problem. I got tired rebuilding the same packages over again and adding with each new version "abi_x86_32" flag to package.use. I just added to make.conf ABI_X86="32 64" After upgrading several 1-year old systems I think best approach is to make a backup of "world" emerge -C world Restore the world from backup and do emerge world -- Thelma
