On Thu, Dec 11, 2014 at 10:58:12AM +0000, Peter Humphrey wrote: > Hello list, > > Today when I ran my usual upgrade I ran into a problem. Portage told me it > had skipped net-libs/libkgapi:4 because of unsatisfied dependencies. All it > could tell me was that >=kde-base/kdepimlibs-4.14:4 required it. > > So I embarked on one of those fruitless cycles of adding packages to > package.keywords, one at a time as they caused portage to stop, until after > about 8 additions I hit the inevitable show-stopper. The mixing of versions > of parts of KDE resulted in both 4.14.3 and 4.12.5 of kdelibs being required > at the same time. > > It looks as though someone has allowed something from ~amd64 out of the wild > and into the peace of amd64. Does anyone have a clue to what it is? I > thought it might be chromium, since libkgapi is for handling Google > calendars and contacts, but eix tells me I already have the latest stable > version. >
Hello Peter, if I'd be in your place I'd try to run emerge @world -uvDNta (the most important one here is the -t for showing the dependency tree, you could also play with --backtrack=30 to resolve possible issues with the dependency calculation), after you removed the keyword stuff you just added. >From your fist statement (required by >=kde-base/kdepimlibs-4.14:4) I guess that you keyworded something that depends on kdepimlibs or kdepimlibs itself in the past. Another option would be to try equery d kdepimlibs : it should show everything that depends on it (and you can crosscheck that with your keywords). As a final straw (or first option - depending on you preferences) you could resync the tree: maybe you've gotten an incomplete version/revbump that already is resolved in later versions of the tree. WKR Hinnerk
