Re: [gentoo-user] Re: New xorg-proto package blocks everything else.
On Sun, 25 Mar 2018 08:10:29 -0700, Ian Zimmerman wrote: > > The only hard block here appears to be xscrnsaverproto, unmerge that > > and the rest should take care of themselves. I had all the soft > > blocks today but not that one, and everything worked fine. > > But ... I actually have packages that depend on scrnsaverproto: > > matica!524 ~# equery d scrnsaverproto equery d is unreliable, emerge -cav is a better check if deps. > * These packages depend on scrnsaverproto: > x11-base/xorg-server-1.19.5-r1 (>=x11-proto/scrnsaverproto-1.1) > x11-libs/libXScrnSaver-1.2.2-r1 > (>=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(-)?]) > x11-misc/xautolock-2.2_p5_p1 (x11-proto/scrnsaverproto) > x11-misc/xssstate-1.1 (x11-proto/scrnsaverproto) When one package blocks another, it is often because both provide the same files. It looks like xorg-proto is replacing a load f x11-proto package. Remove the old one and let emerge work it out for you. > > So I have to unmerge xautolock and xssstate too? Unlikely, because they will probably be satisfied by xorg-proto too, but quickpkg anything you are going to remove, just in case. -- Neil Bothwick "You know how dumb the average person is? Well, statistically, half of them are even dumber than that" - Lewton, P.I. pgpVFwMYJT9C0.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: New xorg-proto package blocks everything else.
On 03/25/2018 05:10:29 PM, Ian Zimmerman wrote: On 2018-03-25 13:50, Neil Bothwick wrote: > The only hard block here appears to be xscrnsaverproto, unmerge that and > the rest should take care of themselves. I had all the soft blocks today > but not that one, and everything worked fine. But ... I actually have packages that depend on scrnsaverproto: So I have to unmerge xautolock and xssstate too? That will be painful because they're baked deep into my X configuration. I think it will require a trip to the Linux console :-P No, I have x11-base/xorg-proto-2018.4 and x11-proto/scrnsaverproto-1.2.2-r2 install here. Try to emerge x11-base/xorg-proto and x11-proto/scrnsaverproto simultaneously.
[gentoo-user] Re: New xorg-proto package blocks everything else.
On 2018-03-25 13:50, Neil Bothwick wrote: > The only hard block here appears to be xscrnsaverproto, unmerge that and > the rest should take care of themselves. I had all the soft blocks today > but not that one, and everything worked fine. But ... I actually have packages that depend on scrnsaverproto: matica!524 ~# equery d scrnsaverproto * These packages depend on scrnsaverproto: x11-base/xorg-server-1.19.5-r1 (>=x11-proto/scrnsaverproto-1.1) x11-libs/libXScrnSaver-1.2.2-r1 (>=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(-)?]) x11-misc/xautolock-2.2_p5_p1 (x11-proto/scrnsaverproto) x11-misc/xssstate-1.1 (x11-proto/scrnsaverproto) So I have to unmerge xautolock and xssstate too? That will be painful because they're baked deep into my X configuration. I think it will require a trip to the Linux console :-P -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. To reply privately _only_ on Usenet and on broken lists which rewrite From, fetch the TXT record for no-use.mooo.com.
