From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] curses of ncurses :(
Date: Thu, 27 Aug 2015 17:42:07 +0200 [thread overview]
Message-ID: <12316003.TfusLl0gel@andromeda> (raw)
In-Reply-To: <55DF2DCD.3080105@gmail.com>
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 <marcec@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
next prev parent reply other threads:[~2015-08-27 15:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 14:34 [gentoo-user] curses of ncurses :( gevisz
2015-08-27 14:43 ` Alexander Kapshuk
2015-08-27 14:53 ` Alexander Kapshuk
2015-08-27 15:16 ` gevisz
2015-08-27 15:18 ` Alexander Kapshuk
2015-08-27 15:28 ` gevisz
2015-08-27 14:52 ` Marc Joliet
2015-08-27 15:25 ` gevisz
2015-08-27 15:33 ` Alan McKinnon
2015-08-27 15:42 ` J. Roeleveld [this message]
2015-08-27 16:19 ` [gentoo-user] " James
2015-08-27 17:02 ` [gentoo-user] " Alec Ten Harmsel
2015-08-27 17:13 ` Marc Joliet
2015-08-28 9:44 ` J. Roeleveld
2015-08-28 12:56 ` Marc Joliet
2015-08-27 17:21 ` Neil Bothwick
2015-08-28 4:03 ` gevisz
2015-08-28 9:34 ` gevisz
2015-08-28 10:25 ` Alec Ten Harmsel
2015-08-28 11:16 ` Rich Freeman
2015-08-27 16:58 ` Marc Joliet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12316003.TfusLl0gel@andromeda \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox