I declined the hardy/intrepid/jaunty nominations. I don't think that there's anything to do there:
* In these releases, cryptsetup still was broken, but vol_id preferred luks over other FSes, so it didn't manifest as a practical problem. * Fixing cryptsetup in those releases can't be sufficient; we cannot assume that updating cryptsetup in stables magically fixes all the existing unclean superblocks out there. * Introducing complex migration scripts into stable releases is out of the question, since they have a high potential to screw everything up even further. We need to introduce migration scripts into the release that stops preferring luks over other FSes. As discusssed above, it's too late to do that for karmic, so it should be done in lucid (which is also LTS, and thus a convenient place to do that). -- luks encrypted partition not detected https://bugs.launchpad.net/bugs/428435 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
