emerge kde-meta not possible: udev gudev conflict

mwalker · n00b Joined: 29 Dec 2008 Posts: 18 Location: Bay area, CA

When trying to emerge kde-meta (pretend - emerge -p kde-meta), it won't even start building and complains that "sys-fs/udev is blocking sys-fs/eudev-0". Removing udev doesn't help because it get reinstalled then blocks eudev again - I think something else required udev. I've seen some comments from others that say to do an emerge --sync but that does not work for me. This is a brand new install. Both x86 and amd64 have the same problem.

Here is the relavent output from emerge (-p):

The Doctor · Moderator Joined: 27 Jul 2010 Posts: 2678

eudev is a fork of udev. You can't have both, and if you don't know which to choose stick with udev. The problem will likely resolve if you run emerge -auvND world first.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.

mwalker · n00b Joined: 29 Dec 2008 Posts: 18 Location: Bay area, CA

I understand what eudev is and that only one should/can be used at a time. The problem is that gentoo seems to want them both - different packages depend on one or the other in kde-meta, so gentoo tried to install both udev and eudev.

Since this is a brand new install, I don't think emerge world will help here. Instead, I somehow need to force all packages to use one or the other, which means somehow changing what some of the packages depend on. Is there a way to force them all to depend on udev?
_________________
----------* DANG!

Do not look into laser
With remaining eye

The Doctor · Moderator Joined: 27 Jul 2010 Posts: 2678

This would not be the first time that the stage3 comes with issues. In this case, nothing should directly depend on eudev or udev. They should be depending on the udev virtual. You may as well try updating first, or syncing the tree. New installs are not immune from changing use flags or new updates.

It looks to me like the virtual may not be installed so portage is getting confused, or something similar. You message indicates that nothing is really being blocked. Gentoo should take care of that itself.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.

mwalker · n00b Joined: 29 Dec 2008 Posts: 18 Location: Bay area, CA

The Doctor · Moderator Joined: 27 Jul 2010 Posts: 2678

You appear to be missing the point I am making: the stage3 looks like it is at fault. Updating should fix it or at least give a more descriptive error.

You should try updating as portage suggests. The virtual should take care of all this. I have KDE installed without this problem so I know that KDE is not at fault. The problem is somewhere in your system. There is no requirement in any ebuild for eudev or udev specificity. Following portage's recommendations usually works.

mwalker · n00b Joined: 29 Dec 2008 Posts: 18 Location: Bay area, CA

The Doctor · Moderator Joined: 27 Jul 2010 Posts: 2678

The stage3 does not come up to date. It looks like this one was uploaded December 10. There should be a few packages that need updating. The udev virtual is probably one. It is very new, as in the past few weeks. It is a reasonable assumption that it may not have been in the stage3.

emerge --sync does not update your system, It only updates the portage tree. To update, you need to run emerge -auvND world the u stands for update, a stands for ask, v, stands fro verbose, N stands for new use, and D stands for deep (as in the dependencies of dependencies). At the least, it should narrow down the problem space.

By the way, at this point your install media is irrelevant since you don't actually keep any parts of the live CD environment. You just use it as a tool box.
The portage snapshot got overwritten when you used emerge --sync and updated portage. The material in the stage3 is basically just a starter kit. After you update, there should be no practical difference between your install and one that is a few years old. Since gentoo is version less, important updates can and do arrive any time. One of these seems to have been between the generation of your stage3 and your attempt to install KDE.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.

mwalker · n00b Joined: 29 Dec 2008 Posts: 18 Location: Bay area, CA

When I rebuild a system, I'm formatting the hard disk partitions, using the minimal install disk to install everything from scratch, building a new kernel, building KDE from new, etc. Doesn't that mean that "emerge -world" doesn't apply? There's no world to update - it's all being build NEW.

I think this is where we are talking past each other. You want me to update, but I am updating in the most severe way possible - NUKE and rebuild completely.
_________________
----------* DANG!

Do not look into laser
With remaining eye

The Doctor · Moderator Joined: 27 Jul 2010 Posts: 2678

If you try the command, you should see it does. In this case, "world" will catch everything. You didn't nuke everything. You nuked your old system and put an identical new system that was about a week out of date in its place. The new system was already out of date. The starge3 contains about 60 or so packages in the system set, but emerge -auvND world will catch those as well (That is partial what the -D is for). When you install a new stage3 you still need to update it. You should see some output if you try it and it should take about 10 seconds, longer if there are updates. This command will do absolutely nothing if there are no packages that need to be updated or merged.

I did notice the context and the forum this is posted in. I do realise that you have been using Gentoo since 2009 and this is a fresh install. that What I have been saying is the stage3 is not perfect and not up to date. In this case a critical change appears to have been introduced between when the stage was built and when you installed it. The proper fix for this is to use portage to update your system.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.

mwalker · n00b Joined: 29 Dec 2008 Posts: 18 Location: Bay area, CA

Cool, I'll give that a shot then. So, update world right after the initial installation of the basic, bootable system.

Thanks.
_________________
----------* DANG!

Do not look into laser
With remaining eye

miroR · l33t Joined: 05 Mar 2008 Posts: 826

mwalker · n00b Joined: 29 Dec 2008 Posts: 18 Location: Bay area, CA

Sorry, was drinking Sunday so I could go to work the next day, then I was really tired after work on Monday

I'm doing the update now, then I will install X and KDE.
_________________
----------* DANG!

Do not look into laser
With remaining eye

mwalker · n00b Joined: 29 Dec 2008 Posts: 18 Location: Bay area, CA

No luck, "emerge -p kde-meta" still says udev is blocking eudev. When I did "auvND world" glibc failed to compile (gcc followed it), but I thought might just be ok. It doesn't seem like it should affect (e)udev though...
_________________
----------* DANG!

Do not look into laser
With remaining eye

The Doctor · Moderator Joined: 27 Jul 2010 Posts: 2678

Well, glibc is REALLY important. You should try with the new gcc.

You are right that this should not affect eudev/udev. The package I would expect to solve this is virtual/udev. Did the glibc failures stop if from being merged? You can try emerge -pv virtual/udev to see if it needs to be installed, and if it does, emerge it with the -1 option. (-1 is for oneshot since the virtual should not go in the world file.)

If it was installed, then things may get a little tricky. In that case, please post the entire output of emerge -pvtND kde-meta the -t stands for tree so we can see what is pulling everything. If it is particularity long, please use wgetpaste or similar.

EDIT: It looks like the virtual hit the tree on Dec 12, so your tarball is too early to include it since it was last modified on the Dec 10.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.

miroR · l33t Joined: 05 Mar 2008 Posts: 826

Deathwing00 · Posted: Fri Dec 21, 2012 12:50 am Post subject:

Moved from Installing Gentoo to Desktop Environments.

mwalker · n00b Joined: 29 Dec 2008 Posts: 18 Location: Bay area, CA

The Doctor · Moderator Joined: 27 Jul 2010 Posts: 2678

This is starting to sound like a problem that may reach beyond kde.

I don't think that reinstalling will solve any of your problems, even from a stage 1. A stage 3 is identical to a stage 1, just skipping all the pain of the stage 1. Reinstalling will just give you the opportunity to make the same mistakes.If you want to wait for a new stage3, you can look at the mirrors here to check the upload date.

We may still be able to get to the root of your troubles.
Can you post the output of

wgetpaste /etc/portage/make.conf

wgetpaste /etc/make.conf

emerge -pvt kde-meta virtual/udev| wgetpaste

You may need to emerge wgetpaste. Its a handy little tool for occasions like this. It will upload your files or output to a paste bin and return a url which you can copy much more easily.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.

mwalker · n00b Joined: 29 Dec 2008 Posts: 18 Location: Bay area, CA

Ok, this is interesting. virtual/udev is present:

The Doctor · Moderator Joined: 27 Jul 2010 Posts: 2678

So I guess that solves the udev problem. Your make.conf looks good. The -j6 might be bit too aggressive for some packages, but I don't think -j6 is generally a problem. You might want to try MAKEOPTS="-j1" emerge -uv glibc to see if that is the case for glibc or if the error is easer to find.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.

mwalker · n00b Joined: 29 Dec 2008 Posts: 18 Location: Bay area, CA

Yeah, I'll try -j1 for glibc. I think I remember cases where multi-core compiling caused failures before, fortunately not very often. Strangely, I think with multi-threading turned off in the BIOS, compilation is a whole lot faster. That's why it isn't -j12. I'll have to verify that though.

Thanks.
_________________
----------* DANG!

Do not look into laser
With remaining eye