On 09/02/2016 16:42, James wrote:
> James <wireless <at> tampabay.rr.com> writes:
>
>
> Boy this just keeps getting stranger and stranger.
> So I::
>
> emerge -C sys-fs/udev
> emerge eudev
>
> no problems,
>
> then in /etc/portage/package.mask I masked off::
>
> sys-apps/systemd
> sys-apps/gentoo-systemd-integration
>
>
> On a normal, routine update, I have about 6 packages that need to
> be compile. But now I still have these blockers::
>
> [blocks B ] sys-apps/gentoo-systemd-integration
> ("sys-apps/gentoo-systemd-integration" is blocking sys-fs/eudev-3.1.5)
> [blocks B ] sys-fs/eudev ("sys-fs/eudev" is blocking
> sys-apps/gentoo-systemd-integration-4, sys-apps/systemd-226-r2)
> [blocks B ] sys-apps/systemd ("sys-apps/systemd" is blocking
> sys-fs/eudev-3.1.5)
>
>
> eudev is now installed::
>
> [I] sys-fs/eudev
> Installed versions: 3.1.5(09:28:52 AM 02/09/2016)(hwdb kmod
> -introspection -rule-generator -selinux -static-libs -test ABI_MIPS="-n32
> -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32")
>
>
>
> ANY IDEAS how to discover and fix these (systemd) blockers.
Yes. The correct idea really should have been your first impulsive knee
jerk reaction, and it was JC's first answer (which you have not posted yet)
emerge -pvt <whatever>
That always tells you exactly what is pulling in what. Just like the
docs have described for years.
--
Alan McKinnon
alan.mckin...@gmail.com
