Joseph wrote:
> On 02/15/13 07:58, Florian Philipp wrote:
>> Am 15.02.2013 03:38, schrieb Canek Peláez Valdés:
>>> On Thu, Feb 14, 2013 at 7:06 PM, Joseph <syscon...@gmail.com> wrote:
>>>> Is it safe to unmerge "sys-fs/udev-171-r9" it is blocking udev-197
>>>
>>> As long as you don't stop udev, nor try to reboot before merging the
>>> new version, yes.
>>>
>>> Regards.
>>>
>>
>> The more important question is: Why does it block? udev is not slotted.
>> An update shouldn't block itself. Something's not right here.
>>
>> Regards,
>> Florian Philipp
>
> That is a good question. I had three blocks:
> [blocks B ] <sys-fs/lvm2-2.02.97-r1 ("<sys-fs/lvm2-2.02.97-r1" is
> blocking sys-fs/udev-197-r4)
> [blocks B ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking
> sys-fs/udev-init-scripts-22)
> [blocks B ] <sys-kernel/genkernel-3.4.25
> ("<sys-kernel/genkernel-3.4.25" is blocking sys-fs/udev-197-r4)
>
> I upgraded genkernel and lvm2 and the udev bloc resolved itself.
I ran into something like this too but no genkernel here. I switched to
eudev so not sure how to get around it since I had to unmerge udev to
install eudev anyway. I would suggest going to the boot runlevel at
least tho. Then unmerge things until it is happy. That was what I had
to do.
Don't forget udev is a service so after the update, either reboot or
restart the service. I would restart the sservice because the device
nodes should already be there but will be gone if you reboot.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how
you interpreted my words!
