I agree with Peter. The problem isn't that an old cryptsetup was used, that worked fine with the older release. That's just the cause of the problem. The real problem is that upgrading to Karmic will result in a system that isn't bootable and difficult for non-technical people to fix. I imagine that the full disk encryption is a popular option on laptops (since they are easier to steal) so I would think this a release-blocking bug. I'm not sure that big warnings in the release notes would help either given how easy it is to upgrade from update-manager. Better to try to detect this configuration and refuse to update with an error pointing to the bug if this cannot be fixed by release.
I agree with Peter. The problem isn't that an old cryptsetup was used, that worked fine with the older release. That's just the cause of the problem. The real problem is that upgrading to Karmic will result in a system that isn't bootable and difficult for non-technical people to fix. I imagine that the full disk encryption is a popular option on laptops (since they are easier to steal) so I would think this a release-blocking bug. I'm not sure that big warnings in the release notes would help either given how easy it is to upgrade from update-manager. Better to try to detect this configuration and refuse to update with an error pointing to the bug if this cannot be fixed by release.