-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 15/11/13 02:24 PM, Tom Wijsman wrote: > On Thu, 14 Nov 2013 20:56:32 -0800 Matt Turner > <matts...@gentoo.org> wrote: > >> Attempting to merge =x11-proto/kbproto-1.0.6-r1 results in: >> >> x11-proto/kbproto:0 >> >> (x11-proto/kbproto-1.0.6-r1::gentoo, ebuild scheduled for merge) >> pulled in by (no parents that aren't satisfied by other packages >> in this slot) >> >> (x11-proto/kbproto-1.0.6-r1::gentoo, installed) pulled in by >> x11-proto/kbproto[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?] >> >> required by (x11-libs/libX11-1.6.2::gentoo, installed) >> x11-proto/kbproto[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?] >> >> required by (x11-libs/libXt-1.1.4::gentoo, installed) > > No, it doesn't, it gives you a lot more output than that; you > appear to be distracted by something that doesn't appear to be a > problem at all. >
Not only that, but these spurious slot collision "errors" pop up all the time and are useful only for confusing portage users, unless they actually get it right in the very rare cases -- and they only get it right, it seems, when you don't see "no parents that aren't satisfied by other packages in this slot" on one side of the collision. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlKGdogACgkQ2ugaI38ACPBlWAD8CxzN2Q2jnkCZkmrXcBpTQNoD v30A1BnDvJen3JilQf0A/jm3aT/2B7vY7xwqTCnlaRE8VQNjgJQptn3HT7LRCic0 =nEcM -----END PGP SIGNATURE-----
