I'm sure there's a better summary. I have this KDE machine and there's a major problem with the upgrade to 4.3.0 from 4.2.4. I can't think of anything else reasonable I can try, so hopefully filing this as a bug will bring some attention to it from the devs and fix whatever needs to get fixed. To eschew surplusage, please see this report's URL, where I originally posted about it. Reproducible: Always Steps to Reproduce: 1. Have existing system with KDE-4.2.4 and a lot of 4.2.4 packages 2. emerge --sync 3. Upgrade to KDE-4.3.0 Actual Results: Blockers that I can't resolve by any means I'm aware of. Expected Results: Upgrade, please!
This is most certainly caused by entries in the world/world_sets files. See the duplicate bug for more info and join #gentoo-kde if you need help. *** This bug has been marked as a duplicate of bug 280727 ***
Does this mean I should simply remove kde-base/* from /var/lib/portage/world?
I'm really sorry, but I'm re-opening this bug. The "duplicate" one is marked as RESOLVED FIXED. I see neither a clear, well-explained resolution nor a fix. There is something really wonky in the upgrade to 4.3.0 that needs to be addressed.
It is quite well described in the guide but once more. in /var/lib/portage/world check if your kde-base/anything entries dont have some :slot stuff (ie kde-base/konsole:4.2), if they do so remove the line entirely if you use metapackages/sets or just remove the slot specification so result look like (kde-base/konsole). Next thing is that if you use sets then you have to check /var/lib/portage/world_sets where the sets are listed like (@kdebase @kdegames...) and if they look like @kdebase-4.2 again you have to update it to @kdebase-4.3 or to unversioned @kdebase.
"in /var/lib/portage/world check if your kde-base/anything entries dont have some :slot stuff (ie kde-base/konsole:4.2), if they do so remove the line entirely if you use metapackages/sets or just remove the slot specification so result look like (kde-base/konsole)." I don't have sets for KDE. I don't have any slot stuff in /var/lib/portage/world. "Next thing is that if you use sets then you have to check /var/lib/portage/world_sets where the sets are listed like (@kdebase @kdegames...) and if they look like @kdebase-4.2 again you have to update it to @kdebase-4.3 or to unversioned @kdebase." There aren't any sets other than @system in /var/lib/portage/world_sets. Still not able to upgrade. What next?
Created attachment 201035 [details] Output of emerge -pvuDN world
You still have a versioned atom in the world file. ('installed', '/', 'kde-base/kephal-4.2.4', 'nomerge') pulled in by kde-base/kephal:4.2 required by @world >=kde-base/kephal-4.2.4:4.2[-kdeprefix] required by ('installed', '/', 'kde-base/kwin-4.2.4', 'nomerge') Bugzilla is not the correct medium to request support. Please use the forums or #gentoo-kde in the freenode irc network instead.
Created attachment 201042 [details] World file, no versioned packages
Created attachment 201044 [details] New output of emerge -pvuDN world
Now, here is my world file after I removed the versioned packages, followed by the output of the subsequent emerge -pvuDN world. As you can see, there is still a problem.
I'm not requesting a support. I am saying that I have tried the support venues and nobody has an answer, so I am filing this bug, not knowing what else to do.
Further, my KDE is now broken on this machine due to "attempts" to "fix" the "upgrade". I'm using Gnome as a DE to log on to this machine right now. KDE will attempt to load and flip right back to the login screen. So, PLEASE take this for the bug it is. I'm either not the only one having this problem, or I won't be. I'm absolutely positive I'm not super-unique in my configuration here. :-P
It is compiz fault. --- kde? ( || ( kde-base/kwin:3.5 kde-base/kdebase:3.5 ) dev-libs/dbus-qt3-old ) kde4? ( || ( kde-base/kwin:4.2 kde-base/kwin:live ) ) --- Just uninstall it and kde will upgrade. @jmbsvicetto: boss isn't this yarr package? :D
For the time being before it is fixed in main tree, please do this: <jmbsvicetto> scarabeus: For the time being, tell the user to grab compiz-0.8.2-r3 from the overlay <jmbsvicetto> (desktop-effects overlay)
Well, I've already uninstalled compiz and all this is still going wrong. Plus, I don't want compiz.
(In reply to comment #15) > Well, I've already uninstalled compiz and all this is still going wrong. Plus, > I don't want compiz. If you don't want to use irc for support, feel free to mail me personally and I'll try to help you, but please don't add more support requests here.
Thank you. Again, this was not a support request. I am quite familiar with the concept of bug reports. All the best working out the kinks in the latest KDE.
compiz-0.8.2-r3 has been added to the tree, so there should be no package left causing any blocks. If you hit the blocks, remember to look at /var/lib/portage/world* and check for versioned atoms (=kde-base/konqueror:4.2, =kde-base/kdebase-startkde-4.2.4 or @kdebase-4.2) and replace them with unversioned atoms (kde-base/konqueror, kde-base/kdebase-startkde and @kdebase).
