On 25/04/2015 18:07, meino.cra...@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: > > 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) > ^ ^^^^^ > > 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) > ^ ^^^^^ > > 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. > > It seems that the inner light of the Zen of Gentoo will not be shed on > everyone... > > ;) > > Any enlightenment is hardly welcome! > > Best regards, > a Novice > (at least when it comes to this output)
So here's how you read that dense stuff: <x11-libs/libXfont-1.5.0 required by (x11-base/xorg-server-1.12.4-r4:0/1.12.4::gentoo, installed) This means that you have xorg-server-1.12.4-r4 installed which depends on libXfont with this limitation: <x11-libs/libXfont-1.5.0 You only get that sort of emerge output when portage is forced to install a package that is NOT latest due to some other package having a constraint on it dependencies. Look at eix for libXfont, there's a version 1.5.1 available but portage can't use it because of limitations from your current version of xorg-server. The same process applies to fontsproto as well. There is nothing for you to do with this output, it is informational (but not labelled as such so you can see it). Maybe run emerge without -v, see if that removes the output tl;dr Why is this confusing? Well, it's because portage's output is ass-hat backwards. Portage is actually making a fundamental cock-up in output design called "exposing the underlying interface in the output" and it's a sign of lazy design. What you really want to know is "libXfont-1.5.1 is available, so why can't portage use it?" The output dumps the depends tree to screen and totally doesn't say what you really want to know. So now you have to run eix and read ebuilds to get a proper answer. Stupid really, when portage already has all of the information available to it! -- Alan McKinnon alan.mckin...@gmail.com
