Package: yaird Version: 0.0.12-1 Followup-For: Bug #343042 Confirmed Paulo's suggestion above to be working.
This problem is hitting everyone I know who has updated today. The fact that the broken yaird was released on the same day as a new kernel means that a lot of people are going to hit this, because they will actually be using yaird today. Unfortunaly on a couple of boxes I only had the one kernel installed, and with the minor update it overwrote the exisitng version instead of installing along side, leaving me with unbootable boxes. Considering the potential for harm I wonder if there could be something done to mitigate this happening again in future. Avoiding releasing yaird at the same time as a minor kernel update would have helped, because the bug would have only been hit by a small number before it could be fixed. However perhaps the more important issue is that of releasing minor kernel updates that overwrite the existing kernel, this is obviously vunerable to more problems than just a badly timed yaird break. That's obviously an issue for the kernel maintainers. Richard. p.s. before anyone tells me, i have been reminded of why it's a good idea to keep a known working kernel on the box ;-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
