On Sun, 11 Aug 2013 10:25:33 -0400, Tanstaafl wrote:

> On 2013-08-11 6:04 AM, Neil Bothwick <n...@digimed.co.uk> wrote:
> > I'm afraid that doesn't solve the problem I had at all, because I'm
> > running ~arch. It's as Samuli said, the eudev release lagged behind
> > udev, causing the virtual to look elsewhere for its satisfaction.  
> 
> So, looks like the best strategy is not to blindly update eudev, and 
> always check these things, before attempting an upgrade, and waiting
> for it to catch up if/when it happens.

Well, you shouldn't blindly update anything, but the issue here was
eudev *not* being updated when the virtual was, and both cause and
result were quite clear.
 
> No biggie, except maybe for those used to just blindly updating 
> everything without looking.

Those people are used to dealing with breakage, or soon will be :)


-- 
Neil Bothwick

Save the whales. Collect the whole set.

Attachment: signature.asc
Description: PGP signature

Reply via email to