From: Meino.Cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] And so the emerge spake: Let there be conflicts...and see, everything was chaos and sin...
Date: Sun, 26 Apr 2015 04:06:53 +0200 [thread overview]
Message-ID: <20150426020653.GA4390@solfire> (raw)
In-Reply-To: <553BF5F8.20008@gmail.com>
Daniel Frey <djqfrey@gmail.com> [15-04-26 03:12]:
> On 04/25/2015 09:07 AM, Meino.Cramer@gmx.de wrote:
> > Hi,
> >
> > A novice asks the master Emerge:
> > "Is there Zen also in every upgrade, which will serve to Gentoo?"
> >
> > Master Emerge moved a little bit and spoke:
> >
> > WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:
>
> Hah!
>
> >
> > x11-libs/libXfont:0
> >
> > (x11-libs/libXfont-1.5.1:0/0::gentoo, ebuild scheduled for merge) conflicts with
> > <x11-libs/libXfont-1.5.0 required by (x11-base/xorg-server-1.12.4-r4:0/1.12.4::gentoo, installed)
> > ^ ^^^^^
>
> Emerge is trying to install libXfont 1.5.1 but the xorg-server version
> installed requires 1.5.0.
>
> >
> > x11-proto/fontsproto:0
> >
> > (x11-proto/fontsproto-2.1.3:0/0::gentoo, ebuild scheduled for merge) conflicts with
> > <x11-proto/fontsproto-2.1.3 required by (x11-libs/libXfont-1.4.9:0/0::gentoo, installed)
> > ^ ^^^^^
> > <x11-proto/fontsproto-2.1.3 required by (x11-base/xorg-server-1.12.4-r4:0/1.12.4::gentoo, installed)
> > ^ ^^^^^
> >
>
> It can't upgrade fontsproto because the current installed version of
> libXfont requires 2.1.3.
>
> Looks like all these messages are thrown because of libXfont.
>
> > The novice was buffled and did not understand a single word.
> > He tries hard to circumvent any conflict with the master but
> > finally he struggled and failed.
>
> Looks like Master Emerge was confused by a circular dependency it could
> not resolve.
>
> Dan
>
Hi Dan,
Thanks for your Koan! :)
...and the novice is confused still...
I tried (after shuttong down X) to remove libXfont and fontsproto (to
install it later again) but this does not help...
How can I get out of this?
Best regards,
Meino
next prev parent reply other threads:[~2015-04-26 2:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 16:07 [gentoo-user] And so the emerge spake: Let there be conflicts...and see, everything was chaos and sin Meino.Cramer
2015-04-25 20:15 ` Daniel Frey
2015-04-26 2:06 ` Meino.Cramer [this message]
2015-04-26 7:38 ` Alan McKinnon
2015-04-26 14:16 ` Daniel Frey
2015-04-26 6:49 ` [gentoo-user] " Martin Vaeth
2015-04-26 7:32 ` Meino.Cramer
2015-04-26 13:13 ` Martin Vaeth
2015-04-26 13:30 ` Meino.Cramer
2015-04-26 8:19 ` Neil Bothwick
2015-04-26 13:08 ` Martin Vaeth
2015-04-26 7:35 ` [gentoo-user] " Alan McKinnon
2015-04-26 7:57 ` Meino.Cramer
2015-04-26 11:30 ` Alan McKinnon
2015-04-26 11:45 ` Meino.Cramer
2015-04-26 8:17 ` Neil Bothwick
2015-04-26 13:49 ` Alan McKinnon
2015-04-26 15:14 ` Peter Humphrey
2015-04-26 16:07 ` [gentoo-user] " walt
2015-04-26 17:17 ` [gentoo-user] " Neil Bothwick
2015-04-26 19:17 ` Philip Webb
2015-04-26 20:23 ` Michael Orlitzky
2015-04-26 21:28 ` Philip Webb
2015-04-26 22:06 ` Neil Bothwick
2015-04-26 22:23 ` Michael Orlitzky
2015-04-27 5:47 ` Alan McKinnon
2015-04-28 14:11 ` Dale
2015-04-28 16:34 ` Philip Webb
2015-04-27 5:40 ` Alan McKinnon
2015-04-27 7:30 ` [gentoo-user] " Martin Vaeth
2015-04-26 20:48 ` james
2015-04-27 20:11 ` Michael Orlitzky
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=20150426020653.GA4390@solfire \
--to=meino.cramer@gmx.de \
--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