I don't agree with the severity classification or tagging of either of these bug reports.
The end result for anyone struck by this bug (same for both reports) is that MySQL is either removed or left in a non-functional state. Sure, they can remove the offending database, losing the data. They could also go through some convoluted work around (assuming they have another system lying around). The proper severity for this bug appears to be Important, "a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone." This is clearly the case for those effected. I'll admit, one of my packages mediamate uses ISAM tables. I wasn't aware they were being phased out. I don't normally go hunting through the syslog looking for errors/warnings when things are working. I suspect many other Debian users are in the same boat. This problem needs to be properly addressed prior to etch's release. With properly being in such a way as to allow the admin of the box a clean method of updating the tables or automatically performing the update for them. Leaving them with a broken installation or completely without MySQL after the upgrade isn't an option that should be considered viable for etch. -- Jamin W. Collins -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
