On 2013-08-11 11:15 AM, Neil Bothwick <n...@digimed.co.uk> wrote:
On Sun, 11 Aug 2013 10:25:33 -0400, Tanstaafl wrote:
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,
True... and I never do. I sync daily, then do an emerge -pvuDN world,
and note which packages want to be updated. I then track them, and after
a few days, if nothing has changed, update them.
For critical apps (boot/system related or server app related (ie,
postfix, dovecot, etc), I also always google for any problems with them
(gentoo+appver) right before updating.
I was always fairly careful in the past, but I started being anal about
it after I got bit by the minor mailman version bump a while (few
years?) ago that changed the locations of critical stuff (like, where
the lists were stored), thereby violating one of gentoo's cardinal rules
that minor version bumps don't make changes that break things, at least
not without lots of warning in the form of a detailed news item
explaining what needs to be done to avoid the breakage.
but the issue here was eudev *not* being updated when the virtual
was, and both cause and result were quite clear.
Right, but I was talking about not updating *anything* related to any
mission critical apps, and that would include the virtual/udev as well.
That said - shouldn't this be taken care of by the the virtual/udev
package itself? Shoudln't it keep track of what versions of udev *and*
eudev it supports, and warn you (via a [B]blocker)?
