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