okay, that is indeed very sophisticated, but I'm still trying to figure out why I ended up with an unbootable system. In that scenario I was doing a downgrade from a newer/updated version of the beta.
I note that /boot was not deleted. one possibility that comes to mind is that the newer kernel was not removed, while the rest of the system was downgraded. Then grub came along and set the newest kernel it found to be the default boot kernel. But in the case of a downgrade the newest kernel might not be compatible with the older system. as a further thought, it sounds like what you are describing is an in- place dist-upgrade, which is not at all what the dialogs state that the installer will do. Release notes often caution against doing a dist- upgrade and instead tell you to do a clean install, due to various compatibility/upgrade issues. So, if I am doing what I think is a clean install, and instead what I get is a dist-upgrade then either the dialogs are wrong or the installer behavior is wrong. Perhaps add an additional option to the installer where you can explicitly request an upgrade? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296071 Title: install over existing does not delete old - result in corrupt install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1296071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
