| 1 |
I've been experiencing this issue whenever I tried to update in the |
| 2 |
fairly recent weeks/days. ‘emerge -avutND’ produces a long list of |
| 3 |
packages (see attachment) and then fails due to a block. |
| 4 |
|
| 5 |
> [blocks B ] <=app-emulation/emul-linux-x86-xlibs-20130224 |
| 6 |
> ("<=app-emulation/emul-linux-x86-xlibs-20130224" is blocking |
| 7 |
> x11-libs/libXdmcp-1.1.1-r1, x11-libs/libXtst-1.2.1-r1, |
| 8 |
> x11-libs/libXt-1.1.3-r1, x11-proto/renderproto-0.11.1-r1, |
| 9 |
> x11-libs/libXext-1.3.1-r1, x11-libs/libXcomposite-0.4.4-r1, |
| 10 |
> x11-libs/libXxf86vm-1.1.2-r1, x11-libs/libXpm-3.5.10-r1, |
| 11 |
> media-libs/fontconfig-2.10.2-r1, x11-proto/inputproto-2.3, |
| 12 |
> x11-libs/libXdamage-1.1.4-r1, x11-proto/xf86bigfontproto-1.2.0-r1, |
| 13 |
> x11-libs/libXaw-1.0.11-r2, x11-libs/libICE-1.0.8-r1, |
| 14 |
> x11-proto/xproto-7.0.23-r2, x11-libs/libX11-1.5.0-r1, |
| 15 |
> x11-libs/libXi-1.7, x11-libs/libXrender-0.9.7-r1, |
| 16 |
> x11-libs/libXmu-1.1.1-r1, media-libs/freetype-2.4.11-r2, |
| 17 |
> x11-proto/damageproto-1.2.1-r1, x11-proto/recordproto-1.14.2-r1, |
| 18 |
> x11-libs/libXfixes-5.0-r1, x11-libs/libXrandr-1.4.0-r1, |
| 19 |
> x11-proto/xf86vidmodeproto-2.3.1-r1, x11-proto/kbproto-1.0.6-r1, |
| 20 |
> x11-libs/libXau-1.0.7-r1, x11-proto/compositeproto-0.4.2-r1, |
| 21 |
> dev-libs/libpthread-stubs-0.3-r1, x11-proto/xcb-proto-1.8-r2, |
| 22 |
> x11-proto/randrproto-1.4.0-r1, x11-proto/fixesproto-5.0-r1, |
| 23 |
> x11-libs/libpciaccess-0.13.1-r1, x11-libs/libXcursor-1.1.13-r1, |
| 24 |
> x11-libs/libxcb-1.9-r1, x11-proto/xextproto-7.2.1-r1, |
| 25 |
> x11-libs/libSM-1.2.1-r1, x11-libs/libXft-2.3.1-r1) |
| 26 |
|
| 27 |
|
| 28 |
Usually I'd unmerge one of the packages in question if I deem that I |
| 29 |
don't need them but I'm unsure as to what the package actually does |
| 30 |
nor what do the packages that it's blocking exactly do. Googling |
| 31 |
around for the package name doesn't give much information. |
| 32 |
|
| 33 |
Any suggestions as to how I could go about resolving this particular |
| 34 |
block? |
| 35 |
|
| 36 |
Quick ‘equery’ shows only a few things that depend on it: |
| 37 |
|
| 38 |
> ✓ ShanaX61s shana % equery d emul-linux-x86-gtklibs % [P ~ ] [J 0 ] [L 38 ] |
| 39 |
> * These packages depend on emul-linux-x86-gtklibs: |
| 40 |
> dev-util/android-sdk-update-manager-21 (amd64 ? app-emulation/emul-linux-x86-gtklibs) |
| 41 |
> sys-devel/gcc-4.5.4 (multilib ? app-emulation/emul-linux-x86-gtklibs) |
| 42 |
> sys-devel/gcc-4.6.3 (multilib ? app-emulation/emul-linux-x86-gtklibs) |
| 43 |
> sys-devel/gcc-4.7.2-r1 (multilib ? app-emulation/emul-linux-x86-gtklibs) |
| 44 |
|
| 45 |
|
| 46 |
I have neither ‘amd64’ nor ‘multilib’ set which raises the question of |
| 47 |
how and why it got onto my system in the first place… I'm still |
| 48 |
somewhat wary of clobbering something that has ‘gcc’ in its depgraph… |
| 49 |
|
| 50 |
-- |
| 51 |
Mateusz K. |
Archives