Re: [gentoo-user] strange blocks b behavior

[John covici]

on Wednesday 04/30/2008 Alan McKinnon(alan.mckinnon@×××××.com) wrote
 > On Wednesday 30 April 2008, John covici wrote:
 > 
 > > OK, here is the requested output.
 > 
 > These questions are coming up a lot lately, and it's always the same 
 > stuff: how the hell do I read this output? I don;t have these things 
 > installed. Basic ideas of blockers;
 > 
 > The output doesn't mean that you have such-and-such and it is causing a 
 > problem. What it does mean is that in the list of stuff portage wants 
 > to update, there are packages that conflict with other packages. They 
 > may or may not be installed already, that is irrelevant. The fact is 
 > that portage *wants* to install them, but *can't* ecuase of blockers. 
 > You have to look at the first field on each line between [] so get more 
 > detail: U means upgrade, R means replace, N means new (as in you don;t 
 > have it already installed), D means downgrade and nomerge shows up when 
 > you use --tree, a package to be merged will show the parents that are 
 > pulling it in, even if the parent doesn't need updating.
 > 
 > 
 > p.s. Something went wrong with your mailer, it mangled line breaks and 
 > mushed the entire output into one huge para :-(  So I've copy-pasted 
 > from the original instead. Hope this makes sense, I copied the parts 
 > that show the dependencies then the related block from the end, and 
 > done it for gtk-doc and gstreamer.
 > 
 > I'm giving a lot of detail, as it is *vital* when using Gentoo that you 
 > completely totally and utterly grasp how the emerge output works and 
 > how to resolve blockers. 
 > 
 > [nomerge      ] gnome-base/gnome-2.20.3  USE="accessibility cdr cups 
 > dvdr esd ldap -mono" 
 > [ebuild     U ]  app-text/evince-2.22.1.1 [2.20.2] USE="dbus doc gnome 
 > tiff* -debug -djvu -dvi -gnome-keyring% -t1lib" 1,610 kB 
 > [ebuild     U ]  mail-client/evolution-2.22.1 [2.12.3-r1] USE="crypt 
 > dbus hal ipv6 ldap spell 
 > ssl -debug -kerberos -krb4 -mono -networkmanager -nntp -pda -profile 
 > (-doc%*)" 30,227 kB 
 > [ebuild     U ]  x11-libs/libwnck-2.22.1 [2.20.3] USE="doc -debug" 672 
 > kB 
 > [ebuild     U ]  gnome-extra/evolution-data-server-2.22.1 [1.12.3] 
 > USE="doc ipv6 ldap ssl -debug -gnome-keyring% -kerberos -krb4 
 > (-keyring%)" 7,424 kB 
 > [ebuild     U ]   x11-libs/gtk+-2.12.9-r2 [2.12.8] USE="X cups doc jpeg 
 > tiff* -debug -vim-syntax -xinerama" 15,652 kB 
 > [ebuild  N    ]    dev-util/gtk-doc-am-1.10-r1  395 kB 
 > [ebuild     U ]    dev-util/gtk-doc-1.10-r1 [1.8-r2] 
 > USE="doc -debug -emacs" 0 kB 
 > 
 > [blocks B     ] dev-util/gtk-doc-am (is blocking 
 > dev-util/gtk-doc-1.8-r2)
 > 
 > So, you currently have gtk-doc-1.8.-r2 and gtk+ wants to merge 
 > gtk-doc-1.10-r1 and gtk-doc-am-1.10-r1. Obviously, 1.10 was split into 
 > two packages (doc and doc-am) to make someone's life easier. However, 
 > one or more files from doc-am-1.10-r1 collides with something that came 
 > from doc-1.8-r2. Portage will not do this without serious intervention, 
 > otherwise package A obliterates package B's stuff.
 > 
 > Solution: unmerge the existing version of gtk-doc:
 > 
 > emerge -avC gtk-doc
 > 
 > emerge world should later pick it up and replace it with the correct 
 > one. Check again once emerge world is complete if gtk-doc did in fact 
 > get put back.
 > 
 > 
 > 
 > 
 >  
 > [nomerge      ] media-sound/sound-juicer-2.22.0 [2.20.1-r1] 
 > USE="-debug -test (-flac%*) (-ogg%*)" 
 > [ebuild     U ]  media-plugins/gst-plugins-meta-0.10-r2 [0.10] USE="X 
 > alsa dvd%* esd mad%* mpeg%* ogg%* vorbis%* 
 > xv -a52% -dvb% -ffmpeg% -flac% -mythtv% -oss* -theora%" 0 kB 
 > [ebuild  N    ]   media-libs/gst-plugins-ugly-0.10.6  USE="-debug" 0 kB
 > [nomerge      ] media-libs/gst-plugins-ugly-0.10.6  USE="-debug" 
 > [ebuild     UD]  media-libs/gstreamer-0.10.14 [0.10.19] USE="(-debug%) 
 > (-nls%*) (-test%)" 0 kB 
 > 
 > [blocks B     ] <media-libs/gst-plugins-ugly-0.10.6-r1 (is blocking 
 > media-libs/gstreamer-0.10.19)
 > 
 > This is similar to the above. portage wants to merge the latest 
 > gstreamer, but that conflicts with an earlier gst-plugins-ugly that you 
 > already have. gstreamer and it's plugins tend to come as matched pair 
 > but they can only be merged one by one, so something has to come off 
 > first before two new packages can go on. Easiest is to unmerge the 
 > plugin, as you have gst-plugins-meta which will put it back:
 > 
 > emerge -avC gst-plugins-ugly ; emerge -av gstreamer gst-plugins-meta
 > 
 > 
 > Run these and check the various outputs that emerge does the right thing 
 > each time, I can't guarantee 100% results. You'll have to compensate 
 > for my lack of a crystal ball by using your eye balls ;-)

OK, the gtk-doc one worked the plugins did not since I don't have the
package to unmerge at all i.e. I have no gst-plugins-ugly and I
unmerged gst-plugins-meta, but I still am getting the blocks -b.

Should I send another --tree output?

P.S. I think I know why the line breaks didn't work -- there were
carriage returns in there by themselves for some reason.

Thanks.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@××××××××××.com
-- 
gentoo-user@l.g.o mailing list