| 1 |
On Wednesday 30 April 2008, John covici wrote: |
| 2 |
|
| 3 |
> OK, here is the requested output. |
| 4 |
|
| 5 |
These questions are coming up a lot lately, and it's always the same |
| 6 |
stuff: how the hell do I read this output? I don;t have these things |
| 7 |
installed. Basic ideas of blockers; |
| 8 |
|
| 9 |
The output doesn't mean that you have such-and-such and it is causing a |
| 10 |
problem. What it does mean is that in the list of stuff portage wants |
| 11 |
to update, there are packages that conflict with other packages. They |
| 12 |
may or may not be installed already, that is irrelevant. The fact is |
| 13 |
that portage *wants* to install them, but *can't* ecuase of blockers. |
| 14 |
You have to look at the first field on each line between [] so get more |
| 15 |
detail: U means upgrade, R means replace, N means new (as in you don;t |
| 16 |
have it already installed), D means downgrade and nomerge shows up when |
| 17 |
you use --tree, a package to be merged will show the parents that are |
| 18 |
pulling it in, even if the parent doesn't need updating. |
| 19 |
|
| 20 |
|
| 21 |
p.s. Something went wrong with your mailer, it mangled line breaks and |
| 22 |
mushed the entire output into one huge para :-( So I've copy-pasted |
| 23 |
from the original instead. Hope this makes sense, I copied the parts |
| 24 |
that show the dependencies then the related block from the end, and |
| 25 |
done it for gtk-doc and gstreamer. |
| 26 |
|
| 27 |
I'm giving a lot of detail, as it is *vital* when using Gentoo that you |
| 28 |
completely totally and utterly grasp how the emerge output works and |
| 29 |
how to resolve blockers. |
| 30 |
|
| 31 |
[nomerge ] gnome-base/gnome-2.20.3 USE="accessibility cdr cups |
| 32 |
dvdr esd ldap -mono" |
| 33 |
[ebuild U ] app-text/evince-2.22.1.1 [2.20.2] USE="dbus doc gnome |
| 34 |
tiff* -debug -djvu -dvi -gnome-keyring% -t1lib" 1,610 kB |
| 35 |
[ebuild U ] mail-client/evolution-2.22.1 [2.12.3-r1] USE="crypt |
| 36 |
dbus hal ipv6 ldap spell |
| 37 |
ssl -debug -kerberos -krb4 -mono -networkmanager -nntp -pda -profile |
| 38 |
(-doc%*)" 30,227 kB |
| 39 |
[ebuild U ] x11-libs/libwnck-2.22.1 [2.20.3] USE="doc -debug" 672 |
| 40 |
kB |
| 41 |
[ebuild U ] gnome-extra/evolution-data-server-2.22.1 [1.12.3] |
| 42 |
USE="doc ipv6 ldap ssl -debug -gnome-keyring% -kerberos -krb4 |
| 43 |
(-keyring%)" 7,424 kB |
| 44 |
[ebuild U ] x11-libs/gtk+-2.12.9-r2 [2.12.8] USE="X cups doc jpeg |
| 45 |
tiff* -debug -vim-syntax -xinerama" 15,652 kB |
| 46 |
[ebuild N ] dev-util/gtk-doc-am-1.10-r1 395 kB |
| 47 |
[ebuild U ] dev-util/gtk-doc-1.10-r1 [1.8-r2] |
| 48 |
USE="doc -debug -emacs" 0 kB |
| 49 |
|
| 50 |
[blocks B ] dev-util/gtk-doc-am (is blocking |
| 51 |
dev-util/gtk-doc-1.8-r2) |
| 52 |
|
| 53 |
So, you currently have gtk-doc-1.8.-r2 and gtk+ wants to merge |
| 54 |
gtk-doc-1.10-r1 and gtk-doc-am-1.10-r1. Obviously, 1.10 was split into |
| 55 |
two packages (doc and doc-am) to make someone's life easier. However, |
| 56 |
one or more files from doc-am-1.10-r1 collides with something that came |
| 57 |
from doc-1.8-r2. Portage will not do this without serious intervention, |
| 58 |
otherwise package A obliterates package B's stuff. |
| 59 |
|
| 60 |
Solution: unmerge the existing version of gtk-doc: |
| 61 |
|
| 62 |
emerge -avC gtk-doc |
| 63 |
|
| 64 |
emerge world should later pick it up and replace it with the correct |
| 65 |
one. Check again once emerge world is complete if gtk-doc did in fact |
| 66 |
get put back. |
| 67 |
|
| 68 |
|
| 69 |
|
| 70 |
|
| 71 |
|
| 72 |
[nomerge ] media-sound/sound-juicer-2.22.0 [2.20.1-r1] |
| 73 |
USE="-debug -test (-flac%*) (-ogg%*)" |
| 74 |
[ebuild U ] media-plugins/gst-plugins-meta-0.10-r2 [0.10] USE="X |
| 75 |
alsa dvd%* esd mad%* mpeg%* ogg%* vorbis%* |
| 76 |
xv -a52% -dvb% -ffmpeg% -flac% -mythtv% -oss* -theora%" 0 kB |
| 77 |
[ebuild N ] media-libs/gst-plugins-ugly-0.10.6 USE="-debug" 0 kB |
| 78 |
[nomerge ] media-libs/gst-plugins-ugly-0.10.6 USE="-debug" |
| 79 |
[ebuild UD] media-libs/gstreamer-0.10.14 [0.10.19] USE="(-debug%) |
| 80 |
(-nls%*) (-test%)" 0 kB |
| 81 |
|
| 82 |
[blocks B ] <media-libs/gst-plugins-ugly-0.10.6-r1 (is blocking |
| 83 |
media-libs/gstreamer-0.10.19) |
| 84 |
|
| 85 |
This is similar to the above. portage wants to merge the latest |
| 86 |
gstreamer, but that conflicts with an earlier gst-plugins-ugly that you |
| 87 |
already have. gstreamer and it's plugins tend to come as matched pair |
| 88 |
but they can only be merged one by one, so something has to come off |
| 89 |
first before two new packages can go on. Easiest is to unmerge the |
| 90 |
plugin, as you have gst-plugins-meta which will put it back: |
| 91 |
|
| 92 |
emerge -avC gst-plugins-ugly ; emerge -av gstreamer gst-plugins-meta |
| 93 |
|
| 94 |
|
| 95 |
Run these and check the various outputs that emerge does the right thing |
| 96 |
each time, I can't guarantee 100% results. You'll have to compensate |
| 97 |
for my lack of a crystal ball by using your eye balls ;-) |
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
-- |
| 103 |
Alan McKinnon |
| 104 |
alan dot mckinnon at gmail dot com |
| 105 |
|
| 106 |
-- |
| 107 |
gentoo-user@l.g.o mailing list |
Archives