On Thursday, August 27, 2015 05:33:33 PM Alan McKinnon wrote: > On 27/08/2015 17:25, gevisz wrote: > > 2015-08-27 17:52 GMT+03:00 Marc Joliet <mar...@gmx.de>:
> > P.S. I have too much "required by" lines. So, if the portage will not > > > > resolve this issue automatically, I will stop to update my system > > at all. > > I don't think that's the right attitude, portage really only needs to > tell you the first one. > > What is happening is two SLOTs of the same package want to be updated, > but the specific versions block each other (this is definitely a bug of > some kind as the whole point of SLOTs is you *can* have both) > > So portage is telling you that it can't do what it wants to do with > ncurses as there is a blocker. It needs to update ncurses because procps > wants it. And so does Vim. And gvim, zsh, ruby and more. Why so many? > Because ncurses is a very basic piece of code and lots of things use it, > and portage blindly printed all of them > > You only have one error. The 50 or more Required lines are total noise > at this point and distract you from seeing things in the proper light. > Portage is well known for often giving really sucky output, this is such > a time. > > Fix the real error, and all that junk on the screen goes away. No reason > to stop updating. I only had 1 required by set. Which basically got me to remove the llvm use-flag from mesa. That solved the block for me as it ended up removing "llvm" What is "llvm" actually used for? -- Joost
