On 20/12/2016 19:09, Peter Humphrey wrote: > On Tuesday 20 Dec 2016 11:17:54 J. Roeleveld wrote: >> On Tuesday, December 20, 2016 09:59:44 AM Peter Humphrey wrote: >>> /mnt/main is where my rescue system mounts the main system for backup. >>> Do I need to add --xattrs to the tar command? >> >> I do, when it comes to creating a stage4 tarfile. Not sure if this is >> necessary. >> >> Maybe that is used somewhere, or is it possible you miss something in the >> main system mount? > > I'm sure the problem isn't in my backup script. It's always worked perfectly > before. All the same, I have now added --xattrs to every tar command in it. > > D'you want to know what else I've been doing all day? Go on, do you? > > I'll tell you anyway. > > To stand any chance of upgrading KDE apps to 16.12.0, I first evicted every > package returned by eix -Cc dev-qt and eix -Cc kde-plasma, plus a few more > individual packages that were also getting in the way. (The eix man page is > helpful in showing how to extract just the cat/pkg from a list of package > names. Full marks for ingenuity!) > > Then I ran a -uaDvU world to install 300 "new" packages. Hours later, I had > a load more @preserved-rebuild packages to install. I've attached the > output, which shows that it wants to go back to the superseded versions. [0] > shows what it thinks it can install, while [1] lists all the things that > stop it doing anything > > Still absolutely no go. Oddly enough, BGO has only a few 16.12.0 package > bugs and they're all about single packages - nothing to indicate the system- > wide problems I'm having, so it looks as though I have a combination of > packages that cause problems themselves. > > I've now reverted to the good backup I made this morning. I shall have to > consider whether to start building a new system from scratch, a bit at a > time, until I find the culprit. It'd keep me occupied over Christmas, > anyway. > > [0] wilco > [1] blocks.etc >
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? So what wants to install kmail:4 if that's not what you are after? please re-run the emerge command with option -t that produced that wilco file. 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 see a few more things you can look at, but one thing at a time -- Alan McKinnon alan.mckin...@gmail.com
