1 |
On Sun, 26 Mar 2017 18:30:12 -0600, thelma@×××××××××××.com wrote: |
2 |
|
3 |
> >> grep -r udev /etc/portage |
4 |
> >> /etc/portage/package.use:sys-fs/udev extras |
5 |
> >> /etc/portage/package.use:=sys-fs/eudev-1.10-r2 abi_x86_32 |
6 |
> >> /etc/portage/package.use:>=virtual/libudev-215-r1 abi_x86_32 |
7 |
> >> /etc/portage/package.use:>=sys-fs/udev-225-r1 abi_x86_32 |
8 |
> >> /etc/portage/package.use:>=dev-libs/libgudev-230-r1 abi_x86_32 |
9 |
> > |
10 |
> > There's the problem, you have enabled the abi_x86_32 USE flag for all |
11 |
> > versions of udev and the libudev virtual, bit only for one specific |
12 |
> > version of eudev, so the only way portage can upgrade virtual/libudev |
13 |
> > is to install udev, which conflicts with eudev. Fix package.use to the |
14 |
> > entries for libudev and eudev match. |
15 |
> |
16 |
> Yes, that might have been a problem. I got tired rebuilding the same |
17 |
> packages over again and adding with each new version "abi_x86_32" flag |
18 |
|
19 |
But the solution was posted last week. |
20 |
|
21 |
> to package.use. |
22 |
|
23 |
You can use etc-update or equivalent to do that. |
24 |
|
25 |
> I just added to make.conf |
26 |
> ABI_X86="32 64" |
27 |
|
28 |
You can do that, but it build a lot of 32 bit libraries that you don't |
29 |
need, significantly increasing build times. |
30 |
|
31 |
> |
32 |
> After upgrading several 1-year old systems I think best approach is to |
33 |
> make a backup of "world" |
34 |
> emerge -C world |
35 |
> Restore the world from backup and do emerge world |
36 |
|
37 |
How is that different from emerge -e @world? |
38 |
|
39 |
|
40 |
-- |
41 |
Neil Bothwick |
42 |
|
43 |
Do hungry crows have ravenous appetites? |