| 1 |
On Sat, 25 Mar 2017 08:10:25 -0600, thelma@×××××××××××.com wrote: |
| 2 |
|
| 3 |
> > The full output of emerge, with the --tree option, would put these |
| 4 |
> > messages in context. |
| 5 |
> > |
| 6 |
> >> sys-fs/eudev:0 |
| 7 |
> >> |
| 8 |
> >> (sys-fs/eudev-3.1.5:0/0::gentoo, ebuild scheduled for merge) pulled |
| 9 |
> >> in by (no parents that aren't satisfied by other packages in this |
| 10 |
> >> slot) |
| 11 |
> >> |
| 12 |
> >> (sys-fs/eudev-3.1.5:0/0::gentoo, installed) pulled in by |
| 13 |
> >> >=sys-fs/eudev-1.3:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?] |
| 14 |
> >> >required by (virtual/libudev-215-r1:0/1::gentoo, installed) |
| 15 |
> > |
| 16 |
> > This one is usually caused by mismatched USE flags on the virtual and |
| 17 |
> > the choice you have installed. Make sure virtual/libudev and eudev |
| 18 |
> > have the same USE flags, otherwise portage will try to install udev |
| 19 |
> > instead. |
| 20 |
|
| 21 |
> And tried "--tree" option as you suggested. I was doing "@world" |
| 22 |
> But have learned from previous post I have do do in smaller sections so |
| 23 |
> going with @system is showing me the some packages wants to go with |
| 24 |
> "udev" instead of "eudev" |
| 25 |
> |
| 26 |
> [blocks B ] sys-fs/udev ("sys-fs/udev" is blocking |
| 27 |
> sys-fs/eudev-3.1.5) |
| 28 |
|
| 29 |
There must have been something before this. Show the full output, which |
| 30 |
tells us exactly what portage wants to do, and use -v so all USE flags |
| 31 |
are shown. |
| 32 |
|
| 33 |
> * Error: The above package list contains packages which cannot be |
| 34 |
> * installed at the same time on the same system. |
| 35 |
> |
| 36 |
> (sys-fs/eudev-3.1.5:0/0::gentoo, installed) pulled in by |
| 37 |
> >=sys-fs/eudev-1.3:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?] |
| 38 |
> >(>=sys-fs/eudev-1.3:0/0[abi_x86_32(-),abi_x86_64(-)]) required by |
| 39 |
> >(virtual/libudev-215-r1:0/1::gentoo, installed) |
| 40 |
> sys-fs/eudev required by @selected |
| 41 |
> |
| 42 |
> (sys-fs/udev-225-r1:0/0::gentoo, ebuild scheduled for merge) pulled |
| 43 |
> in by |
| 44 |
> >=sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?] |
| 45 |
> >(>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required |
| 46 |
> >by (virtual/libudev-215-r1:0/1::gentoo, installed) |
| 47 |
|
| 48 |
I still suspect a USE flag mismatch here. What does |
| 49 |
|
| 50 |
grep -r udev /etc/portage |
| 51 |
|
| 52 |
show? |
| 53 |
|
| 54 |
To repeat what I said before, a virtual and the package satisfying it |
| 55 |
must have matching USE flags. If your flags for virtual/libudev and eudev |
| 56 |
don't match, portage will try to install the default for libudev, which |
| 57 |
is udev. That then causes a conflict as you can't have udev and libudev |
| 58 |
installed at the same time. |
| 59 |
|
| 60 |
|
| 61 |
-- |
| 62 |
Neil Bothwick |
| 63 |
|
| 64 |
Ninety-Ninety Rule Of Project Schedules - The first ninety percent of |
| 65 |
the task takes ninety percent of the time, and the last ten percent |
| 66 |
takes the other ninety percent of the time. |
Archives