| 1 |
Ian Zimmerman <itz@××××××××××××.org> writes: |
| 2 |
|
| 3 |
> On 2018-03-25 17:49, Martin Vaeth wrote: |
| 4 |
> |
| 5 |
>> It should be scrnsaverproto-1.2.2-r2 which is pulled in. |
| 6 |
>> Maybe you sync'ed at an unfortunate moment. Try emerge --sync again. |
| 7 |
> |
| 8 |
> In my case at least, the root cause was this: in the nightly webrsync |
| 9 |
> snapshot (which I prefer to use instead of rsync), |
| 10 |
> scrnsaverproto-1.2.2-r2 is keyworded and not stable. Adding it to |
| 11 |
> portage/package.use magically unblocks everything. |
| 12 |
|
| 13 |
Yep. webrsync here too. Adding |
| 14 |
|
| 15 |
> =x11-proto/scrnsaverproto-1.2.2-r2 ~amd64 |
| 16 |
|
| 17 |
to package.accept_keywords unblocked everything for me. Thank you. |
Archives