On Thu, Feb 5, 2009 at 12:20 PM, Paul Hartman
<[email protected]> wrote:
> On Thu, Feb 5, 2009 at 1:31 PM, Mark Knecht <[email protected]> wrote:
>> On Wed, Feb 4, 2009 at 3:00 PM, Paul Hartman
>> <[email protected]> wrote:
>> <SNIP>
>>>
>>> it is hwclock on my system. it belongs to sys-apps/openrc-0.4.2 which
>>> you may not be using.
>>>
>>
>> Everyone's sort of quiet today...
>>
>> So, reading back through this thread I'm wondering what the risk level
>> is in going to the newer baselayout stuff? If I keyword baselayout
>> ~amd64 then it wants openrc. If I then keyword openrc ~amd64 it wants
>> me to emerge -C stuff that, should the power go off during the
>> process, might leave the system unbootable.
>>
>> Is udev *really* going away?
>>
>> - Mark
>>
>> lightning ~ # emerge -pvDuN system
>>
>> These are the packages that would be merged, in order:
>>
>> Calculating dependencies... done!
>> [ebuild     U ] sys-apps/baselayout-2.0.0 [1.12.11.1] USE="-build
>> (-bootstrap%) (-static%) (-unicode%*)" 23 kB
>> [ebuild  N    ] sys-apps/openrc-0.4.2  USE="ncurses pam unicode -debug" 142 
>> kB
>> [blocks B     ] <sys-fs/udev-133 ("<sys-fs/udev-133" is blocking
>> sys-apps/openrc-0.4.2)
>> [blocks B     ] <sys-apps/sysvinit-2.86-r11
>> ("<sys-apps/sysvinit-2.86-r11" is blocking sys-apps/openrc-0.4.2)
>>
>>
>
> openrc-0.4.2 needs udev greater than 133. udev isn't going anywhere,
> you just need a newer version.
>
> I'm using a fully ~amd64 set-up and have sys-fs/udev-135-r4
>
> I've never tried mixing arch & ~arch so I'm guessing these kinds of
> things are probably common.
>
> It also might be affected by which profile you're using...

Duncan has scared me off of this path for now. I'll continue down the
.critical file method until it succeeds or fails.

I don't run anything ~amd64 in @system. I can wait for that. This
isn't a 'failure'. It's an annoyance only. I can live with it until
it's fixed in stable.

I'm just surprised that I didn't have this problem until maybe the
last 5-10 weeks. Seems it's been there for a long time...

Thanks,
Mark

Reply via email to