Ian Zimmerman <i...@very.loosely.org> writes:

> 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.

Yep. webrsync here too. Adding

> =x11-proto/scrnsaverproto-1.2.2-r2 ~amd64

to package.accept_keywords unblocked everything for me. Thank you.

Attachment: signature.asc
Description: PGP signature

Reply via email to