* Adam C Powell IV <[EMAIL PROTECTED]> [2005-06-19 20:02]: > The transition from raidtools2 to mdadm breaks all installations with > more than one RAID array
> That the transitional raidtools2 package entered sarge just days before > the release (and that sarge had zero testing cycles, unlike potato or > woody) means that there was just about zero testing for it, and it is > too late for those admins who like me have since rebooted had the same > problem. But for those who have not needed to reboot, please upload a > fix (translate raidtab to something mdadm understands?) or a *prominent* > debconf warning (maybe even a warning in the raidtools2 description) to > testing-proposed-updates. The fact that raidtools2 entered sarge relatively late doesn't really have much to do with it since it was pretty clear what would break and what wouldn't. However, our assumption was that most people would use RAID devices that are set to autoconfiguration (and therefore don't need a configuration file for mdadm to work) and that the rest would be experienced enough to read the release notes or NEWS.Debian after an upgrade. While there's no debconf message, there is a clear NEWS.Debian message which explains exactly what you need to do. I'm not sure about what to do. Obviously, the situation isn't ideal but I thought a dummy package depending on mdadm and including a NEWS.Debian was better than nothing at all - since it will work for most people. In any case, I'm not sure how many people will not have upgraded before r1 given that kernel security fixes are schedulded to come out before. If you have any idea about a good solution that is acceptable for r1, I'd certainly like to hear it. But personally I'm not sure what to do. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
