On Sun, 26 Mar 2017 18:30:12 -0600, the...@sys-concept.com wrote:

> >> 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

But the solution was posted last week.

> to package.use.

You can use etc-update or equivalent to do that.

> I just added to make.conf
> ABI_X86="32 64"

You can do that, but it build a lot of 32 bit libraries that you don't
need, significantly increasing build times.

> 
> 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

How is that different from emerge -e @world?


-- 
Neil Bothwick

Do hungry crows have ravenous appetites?

Attachment: pgp66tIMMZflp.pgp
Description: OpenPGP digital signature

Reply via email to