| 1 |
On Sun, 25 Mar 2018 08:10:29 -0700, Ian Zimmerman wrote: |
| 2 |
|
| 3 |
> > The only hard block here appears to be xscrnsaverproto, unmerge that |
| 4 |
> > and the rest should take care of themselves. I had all the soft |
| 5 |
> > blocks today but not that one, and everything worked fine. |
| 6 |
> |
| 7 |
> But ... I actually have packages that depend on scrnsaverproto: |
| 8 |
> |
| 9 |
> matica!524 ~# equery d scrnsaverproto |
| 10 |
|
| 11 |
equery d is unreliable, emerge -cav is a better check if deps. |
| 12 |
|
| 13 |
> * These packages depend on scrnsaverproto: |
| 14 |
> x11-base/xorg-server-1.19.5-r1 (>=x11-proto/scrnsaverproto-1.1) |
| 15 |
> x11-libs/libXScrnSaver-1.2.2-r1 |
| 16 |
> (>=x11-proto/scrnsaverproto-1.2.2-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) |
| 17 |
> x11-misc/xautolock-2.2_p5_p1 (x11-proto/scrnsaverproto) |
| 18 |
> x11-misc/xssstate-1.1 (x11-proto/scrnsaverproto) |
| 19 |
|
| 20 |
When one package blocks another, it is often because both provide the |
| 21 |
same files. It looks like xorg-proto is replacing a load f x11-proto |
| 22 |
package. Remove the old one and let emerge work it out for you. |
| 23 |
|
| 24 |
> |
| 25 |
> So I have to unmerge xautolock and xssstate too? |
| 26 |
|
| 27 |
Unlikely, because they will probably be satisfied by xorg-proto too, but |
| 28 |
quickpkg anything you are going to remove, just in case. |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Neil Bothwick |
| 33 |
|
| 34 |
"You know how dumb the average person is? Well, statistically, half of |
| 35 |
them are even dumber than that" - Lewton, P.I. |
Archives