| 1 |
On Sat, 25 Mar 2017 16:58:25 -0600, thelma@×××××××××××.com wrote: |
| 2 |
|
| 3 |
> > To repeat what I said before, a virtual and the package satisfying it |
| 4 |
> > must have matching USE flags. If your flags for virtual/libudev and |
| 5 |
> > eudev don't match, portage will try to install the default for |
| 6 |
> > libudev, which is udev. That then causes a conflict as you can't have |
| 7 |
> > udev and libudev installed at the same time. |
| 8 |
> |
| 9 |
> Here is the output: |
| 10 |
> |
| 11 |
> grep -r udev /etc/portage |
| 12 |
> /etc/portage/package.use:sys-fs/udev extras |
| 13 |
> /etc/portage/package.use:=sys-fs/eudev-1.10-r2 abi_x86_32 |
| 14 |
> /etc/portage/package.use:>=virtual/libudev-215-r1 abi_x86_32 |
| 15 |
> /etc/portage/package.use:>=sys-fs/udev-225-r1 abi_x86_32 |
| 16 |
> /etc/portage/package.use:>=dev-libs/libgudev-230-r1 abi_x86_32 |
| 17 |
|
| 18 |
There's the problem, you have enabled the abi_x86_32 USE flag for all |
| 19 |
versions of udev and the libudev virtual, bit only for one specific |
| 20 |
version of eudev, so the only way portage can upgrade virtual/libudev is |
| 21 |
to install udev, which conflicts with eudev. Fix package.use to the |
| 22 |
entries for libudev and eudev match. |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
Neil Bothwick |
| 27 |
|
| 28 |
An expert is nothing more than an ordinary person away from home. |
Archives