>=x11-proto/xproto-7.0.6 package conflicts with x11-proto/xproto-7.0.7, neither of which are installed which seems to point to a package, not installed: emerge --unmerge x11-proto/xproto --- Couldn't find 'x11-proto/xproto' to unmerge. >>> No packages selected for removal by unmerge blocking a later version of the same package, which itself is not installed: emerge x11-proto/xproto --pretend These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] x11-proto/xproto-7.0.7 USE="-debug" [blocks B ] >=x11-proto/xproto-7.0.6 (is blocking x11-libs/libX11-1.0.1-r1) Reproducible: Always Steps to Reproduce: 1.emerge sync 2.emerge --deep world this is a new build, using 'live-cd' to install X starts up together with Gnome but some features fail, namely, gnome-xterm seg faults - it is an old version in need of update there are many updates pending, I will likely be able to do all updates prior to the above package but will fail at this point
Run: emerge --sync emerge -1v libX11 (In reply to comment #0) > >=x11-proto/xproto-7.0.6 package conflicts with x11-proto/xproto-7.0.7 You misdiagnosed problem. > [blocks B ] >=x11-proto/xproto-7.0.6 (is blocking x11-libs/libX11-1.0.1-r1) It conflicts with you old libX11.
It's not xproto blocking.
did an emerge --unmerge libX11 block was *removed* :):):) excellent - many thanks for guidance, will try to better diagnose next time also, thanks for rapid update - I was astonished at speed of response JOn