Ian Zimmerman 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 pref
2018-03-25 22:25 GMT+03:00 Ian Zimmerman :
> 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
> sna
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),
scrns
Akater wrote:
> I just tried
>
>> emerge --ask --verbose --update --oneshot x11-base/xorg-proto x11-proto/s=
> crnsaverproto
>
> > (x11-proto/scrnsaverproto-1.2.2-r1:0/0::gentoo, installed) pulled in by
> >x11-proto/scrnsaverproto
It should be scrnsaverproto-1.2.2-r2 which is pulled in.
Mayb
4 matches
Mail list logo