| 1 |
On 03/25/2018 05:10:29 PM, Ian Zimmerman wrote: |
| 2 |
> On 2018-03-25 13:50, Neil Bothwick wrote: |
| 3 |
> |
| 4 |
> > The only hard block here appears to be xscrnsaverproto, unmerge |
| 5 |
> that and |
| 6 |
> > the rest should take care of themselves. I had all the soft blocks |
| 7 |
> today |
| 8 |
> > but not that one, and everything worked fine. |
| 9 |
> |
| 10 |
> But ... I actually have packages that depend on scrnsaverproto: |
| 11 |
> |
| 12 |
> So I have to unmerge xautolock and xssstate too? That will be painful |
| 13 |
> because they're baked deep into my X configuration. I think it will |
| 14 |
> require a trip to the Linux console :-P |
| 15 |
> |
| 16 |
|
| 17 |
No, |
| 18 |
|
| 19 |
I have x11-base/xorg-proto-2018.4 and x11-proto/scrnsaverproto-1.2.2-r2 |
| 20 |
install here. |
| 21 |
|
| 22 |
Try to emerge x11-base/xorg-proto and x11-proto/scrnsaverproto |
| 23 |
simultaneously. |
Archives