2018-03-25 21:40 GMT+03:00 Franz Fellner <alpine.art...@gmail.com>: > Just a stupid question: Did you add =scrnsaverproto-1.2.2-r1 to > package.mask? Because the -r2 is stable and nothing should prevent it from > being merged... > I am running partly testing and the time xorg-proto was added I had to deal > with hard blocks which I circumvented by un-keywording (remove from > package.accept-keywords) and selectively masking.
Making emerge-webrsync the next day solved the problem. Now x11-proto/scrnsaverproto-1.2.2-r2 is marked stable and x11-proto/xcb-proto-1.13 is marked unstable, whereas yesterday it was vice versa.
