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