Bug 349838 – Merging kde-base/kde-meta involves a lot of 'Your system configuration contains neither "kde-base/kdebase-runtime-meta" nor "kde-base/kdebase-startkde".' warnings

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Ivan Yarych 2010-12-27 08:14:01 UTC]

Emergeing KDE meta package the first time creates a lot of spam warnings regarding not installed (yet) "kde-base/kdebase-runtime-meta" or "kde-base/kdebase-startkde".

Reproducible: Always

Steps to Reproduce:
1. emerge kde-base/kde-meta
2.
3.

Actual Results:  
Each KDE package merged before kde-base/kdebase-startkde shows warning message:

WARNING! Your system configuration contains neither "kde-base/kdebase-runtime-meta"                                                                                                 
nor "kde-base/kdebase-startkde". You need one of above.                                                                                                                             
With this setting you are unsupported by KDE team.                                                                                                                                  
All missing features you report for misc packages will be probably ignored or closed as INVALID.                                                                                    


Expected Results:  
None of those warning should be displayed or it must be displayed only once per merge proccess.

[Comment 1 Fab 2011-01-31 23:00:35 UTC]

Same problem here. First time that I install kde, following this guide [1], I run:
> emerge -av kdebase-meta


--> my mailbox is spammed by this warning on each package.


[1] http://www.gentoo.org/proj/en/desktop/kde/kde4-guide.xml

[Comment 2 Branden 2011-02-22 04:46:23 UTC]

I have had this same error and the way to fix it would to emerge it before you start emerging the rest of KDE. It would save _a lot_ of error messages, and stopping when installing the KDE plasma desktop. The error occurred with me on amd64 platform. I found out this error when I first emerged kde-mta and when I went to start it, it gave me a kernel panic. At first I did not know what was going on until I sat down and checked out the call trace. So I would advise to fix this that you emerge kde-base/kde-base-runtime-meta before you emerge the rest of kde-meta.

[Comment 3 Ivan Yarych 2011-02-22 07:15:19 UTC]

So I suppose this can be solved by some kind of (virtual) dependency.

[Comment 4 Tomáš Chvátal (RETIRED) 2011-02-22 13:10:28 UTC]

This is already fixed in overlay eclass. But it wont be ready for consumption for 1 month or so.

Just wait for it :)

[Comment 5 Theo Chatzimichos (RETIRED) 2011-02-22 13:42:19 UTC]

resolving per comment 4