Am Freitag, 2. Oktober 2009 schrieb Nikos Chantziaras:
> Er, what the heck is this one:
>
> emerge -av1 x11-libs/libXScrnSaver
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild N ] x11-proto/scrnsaverproto-1.2.0 49 kB
> [ebuild N ] x11-libs/libXScrnSaver-1.1.3 USE="-debug" 0 kB
> [blocks B ] <x11-libs/libXScrnSaver-1.2
> ("<x11-libs/libXScrnSaver-1.2" is blocking x11-proto/scrnsaverproto-1.2.0)
>
> Total: 2 packages (2 new), Size of downloads: 49 kB
> Conflict: 1 block (1 unsatisfied)
>
> * Error: The above package list contains packages which cannot be
> * installed at the same time on the same system.
>
> ('ebuild', '/', 'x11-libs/libXScrnSaver-1.1.3', 'merge') pulled in by
> x11-libs/libXScrnSaver
fr...@eisen ~ $ eix scrnsaverproto
[I] x11-proto/scrnsaverproto
Available versions: 1.1.0 [M]~1.2.0
So, scrnsaverproto-1.2.0 is still masked and its ebuild says:
!<x11-libs/libXScrnSaver-1.2
But
fr...@eisen ~ $ eix libXScr
[I] x11-libs/libXScrnSaver
Available versions: 1.1.3 {debug}
My portage, last synced an hour ago, doesn't know _any_ libXScrnSaver which
scrnsaverproto accepts (assuming no overlays in that area, I only have
sunrise and kde-testing).
Here, >=scrnsaverproto-1.1 is a dependency of libXScrnSaver-1.1.3. But since
you want to update scrnsaverproto, you could see what other packages need it.
Perhaps you can remove it from your sys without complications. On my system
those are mainly KDE apps plus mplayer through xscreensaver useflag, but
perhaps you're a Gnome dude or XFCE chap or whatever. :-)
--
Gruß | Greetings | Qapla'
Light travels faster than sound. This is why some
people appear bright until you hear them speak...
signature.asc
Description: This is a digitally signed message part.
