2018-03-25 22:25 GMT+03:00 Ian Zimmerman <i...@very.loosely.org>:
> On 2018-03-25 17:49, Martin Vaeth wrote:
>
>> It should be scrnsaverproto-1.2.2-r2 which is pulled in.
>> Maybe you sync'ed at an unfortunate moment. Try emerge --sync again.
>
> In my case at least, the root cause was this: in the nightly webrsync
> snapshot (which I prefer to use instead of rsync),
> scrnsaverproto-1.2.2-r2 is keyworded and not stable. Adding it to
> portage/package.use magically unblocks everything.
The same here:
$ eix scrnsaverproto
* x11-proto/scrnsaverproto
Available versions: 1.2.2-r1 ~1.2.2-r2 {doc ABI_MIPS="n32 n64
o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32"}
Homepage: https://www.x.org/wiki/
Description: X.Org ScrnSaver protocol headers
And I also use webrsync.
