While doing a general cleanup, I noticed I had both slots of udisks installed (1.0.4-r4 in slot 0, 2.0.91 in slot 2) and that the only thing requiring slot 0 was kdelibs-4.9.5. Looking at the kdelibs ebuild, it looks like adding the udisks2 use flag for kdelibs should switch its dependency from slot 0 to slot 2. So,

Why is it failing to pick up the udisks2 flag? I've looked at this bug which implies that for kde 4.10, udisks2 will be the only option. I'm not ready to jump to 4.10 yet, but I don't see anything to suggest that 4.9.5 shouldn't be able to use udisks2.

Any suggestions? Am I missing something obvious? Something not so obvious?

Last edited by genterminl on Mon Mar 11, 2013 11:40 pm; edited 1 time in total

As you can see from my first post, I have specifically added udisks2 to my portage.use file. I have not masked it, nor do I see it in the portage package.mask file. That's really my question - the ebuild refers to it, I've added it to package.use, but emerge is not picking it up. Is it masked somewhere I'm not looking, do I have some configuration problem, or is there a bug in emerge?

Well that was convoluted. The actual fix needed to be in file /etc/portage/profile/package.use.mask as

Code:

kde-base/kdelibs -udisks2

The emerge is still running.

I know it seems backwards but you are subtracting the flag udisks2 from the global package.mask file. Since it was set there as +udisks2, you must use a minus. The plus is understood, kinda like a positive number._________________The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735Adopt a Post | Strip Comments| Emerge Wrapper

Actually it wasn't the minus sign that got me - it was using package.use.mask instead of package.mask, and having to put it in a profile directory instead of just being able to put it in /etc/portage/package.use, or even /etc/portage.package.use.mask or package.use.unmask.

Emerge completed successfully. Dolphin does have a delay in starting up, which I kind of expected based on the bug I referenced in my first post, so I consider this solved, and I'll update the subject accordingly.

Thanks for all the help.

edit: I can edit the subject of the first post - but not add [solved] since I can't make it any longer than it is. Is this a bug in the forum software?

Thanks. It looks like Chrome (I have Chromium) doesn't wrap the long lines in the [code] section with my emerge --info, as well as having all the [code] and [quote] boxes indented much farther than they appear in Firefox.

Thanks. It looks like Chrome (I have Chromium) doesn't wrap the long lines in the code section with my emerge --info, as well as having all the code and quote boxes indented much farther than they appear in Firefox.

The current Site Admin is emerging Chrome as we Speak. He suggested, we edit our posts, so I'm going to ask you to remove every Linebreak in your 'code' tags, and let's see what happens..._________________The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735Adopt a Post | Strip Comments| Emerge Wrapper

All my [code] block contents were copy/pasted from terminal output without manual editing, so all linebreaks really do separate distinct lines of output. Besides - it looks like the problem is long lines, not extra linebreak's - unless I misunderstand what you are asking me to do. Would this be easier to discuss by IM or IRC?