Installed 10.04.1 wubi, ran updates, upgraded to maverick.
Results
=======
Successful upgrade on two different computers, one with wubi installed to a different partition than windows, one on the same partition.
Bugs:
On the first test, the install would not boot after upgrade (bug 628349). I haven't been able to duplicate this problem. On this test I also allowed grub to install itself to the MBR to confirm that this issue is still present (only affects wubi installs on partitions other than windows - existing bug 610898). I ran this test again to see if it would fail to boot after the upgrade and couldn't duplicate it - therefore I've marked the bug 628349 invalid. The issue regarding overwriting the MBR still exists.
On the second test (same partition as windows) the upgrade went fine, but I ran into the kernel bug associated with ndiswrapper (bug 613796)
On the third test (different partition as windows) the upgrade went fine, no issues.
Since the first issue is not a normal case (installing grub to the MBR), I'm not marking it as a fail, however, we've seen users fall for this on the 10.04.1 upgrade, so it should be taken seriously.
This is the full description of the first test.
1. Installed wubi 10.04.1 on non windows partition /dev/sdb8 (fat32) with a 5GB install.
2. Ran updates
3. Checked for more updates - none
4. Ran 'update-manager -d -c'
5. Update manager showed "New Ubuntu release '10.10' is available"
6. Click on Upgrade
7. Showed Release notes "This is a ALPHA release. Do not install it on production machines"
8. Clicked on upgrade
prompted to download 510MB of data etc. clicked to proceed
Getting new packages - 1053 files downloaded.
Eventually a screen popped up:
Title: Debconf on ubuntu
Banner: Configuring grub-pc
Checkbox: Continue without installing GRUB?
Button: Help
I clicked on Help:
You chose not to install GRUB to any devices. If you continue the boot loader may not be properly configured and when your computer next starts up it will use whatever was previously in the boot sector. If there is an earlier version of GRUB 2 in the boot sector, it may be unable to load modules or handle the current configuration file.
If you are already running a different boot loader and want to carry on doing so, or if this is a special environment where you do not need a boot loader, then you should continue anyway. Otherwise you should install GRUB somewhere.
Button: Close
I clicked Forward
it presented three options
/dev/sda (78518MB, ST98823AS)
/dev/sdb (100256 MB, OneTouch_II)
/dev/loop0 (1472MB, ???
I selected /dev/sda (my internal drive) and hit forward. This installed grub2 bootloader to the drive MBR pointing to partition #256
Fixed before rebooting. Attempting to restart failed on first upgrade, but I was unable to duplicate problem on identical test.
| 