On 21/12/2016 11:05, Peter Humphrey wrote: > On Tuesday 20 Dec 2016 19:24:51 Alan McKinnon wrote: >> Looks like a reasonably straightforward set of blockers. Your core >> problem seems to be that portage wants to install kmail:4 but if I read >> you correctly earlier in the thread, you want to install kmail-16.12.0. >> >> Correct? > > Yes, and I'd also like just to update the system against the portage tree. > >> So what wants to install kmail:4 if that's not what you are after? > > If I clear everything out of the way beforehand, it's happy to install lots > of 16.12.0 packages, including KMail, but then it wants to reinstall the > superseded packages as well, which is where the mess appears. > >> please re-run the emerge command with option -t that produced that wilco >> file. > > I will if I can remember what I did: the command history was lost when I > recovered from backup. > >> p.s. I have a strong hunch that the time has now come where kmail:4 >> simply cannot co-exist with KDE-5 anymore... > > I thought we'd reached the point where kmail:4 could just be quietly > forgotten. And not before time. > >> I see a few more things you can look at, but one thing at a time >
After a day at work away from gentoo-user, here's what I'd do: The main problem seems to be something pulling in kmail:4, so emerge -C kmail:4 depclean to get rid of its deps add kmail:4 to your package.mask and run a full battery of updates, like I use: emerge -avuND world emerge @preserved-world depclean revdep-rebuild At some point with that mask you might hit a snag, but I reckon the error message will have enough info to tell you what's the real source of the problem -- Alan McKinnon alan.mckin...@gmail.com
