On Thu, 13 Dec 2012 15:39:59 +0000 (UTC)
James <[email protected]> wrote:
> Upon syncing, my system wants to upgrade to eudev.
>
> [blocks B] sys-fs/udev ("sys-fs/udev" is blocking sys-fs/eudev-0)
>
>
> Not much out there; but I gleaned it is for those
> that insist on a separate partition for /var and /usr.
> Any other motivating reasons?
>
> equery depends eudev
> * These packages depend on eudev:
> virtual/udev-196
> (>=sys-fs/eudev-1_beta1[gudev?,hwdb?,introspection?,keymap?
> ,selinux?,static-libs?])
>
>
> I really do not want eudev, at this time. I just recovered
> a system that is now running sys-fs/udev-196-r1.
>
> I did recently put these into my package.keywords.
>
> =sys-fs/udev-196-r1 ~amd64
> =virtual/udev-196 ~amd64
> =sys-fs/udev-init-scripts-17-r1 ~amd64
>
> But I do not want to go to eudev (not till it's sable
> and necessary.
>
> Is this the best (most current) info on setting up udev-196 ?
> http://wiki.gentoo.org/wiki/Udev
>
>
> Some discussion and guidance would be keenly appreciated.
>
>
> cautiously,
> James
Hi James,
My guess is that you've unmasked sys-fs/udev-196 only partially.
Portage tries to calculate the dependencies for it and finds that
something is still missing (e.g. you need to ~amd64 more packages) so
Portage stops with sys-fs/udev and tries to satisfy virtual/udev with
eudev instead.
Try an "emerge -pv =sys-fs/udev-196-r1" and see if that gives any
reason why Portage isn't happy with it.
HTH,
Bryan
