doing sudo apt-get dist-upgrade on trusty r79 will corrupt the boot image

[mhb]

i wanted to upgrade the packages so i ran sudo apt-get dist-upgrade. it downloaded 74mbs. after a reboot android wouldn't boot. flashing the boot image from my current android rom fixed the issue

[mhb (hexed)]

sorry now that i've seen reported bugs i see this is more of a ubuntu touch bug than a dual boot installer bug but then again if ubuntu touch is installed using phablet flash and not dual boot, altering the boot image isn't a bug.

[mhb (hexed)]

i tried to install mtp-tools (to see if i can access sdcard) and saw this at the end :
    Processing triggers for initramfs-tools ...
    update-initramfs: Generating /boot/initrd.img-touch
    dpkg: warning: version 'touch' has bad syntax: version number does not start with digit
    grep: /boot/config-touch: No such file or directory
    WARNING: missing /lib/modules/touch
    Device driver support needs thus be built-in linux image!
    depmod: FATAL: touch: not absolute path.
    depmod: ERROR: could not open directory /tmp/mkinitramfs_NsUQks/lib/modules/3.4.0-3-mako: No such file or directory
    depmod: FATAL: could not search modules: No such file or directory
    reading ramdisk from /boot/initrd.img-touch
>>Writing Boot Image /dev/disk/by-partlabel/boot<<
why does it even write to boot image for something that has nothing to do with boot

[Ondrej Kubik (ondrak)]

Any manipulation from Ubuntu which will result in boot partition update will break dualboot setup.
This is something hard to avoid, since there is potentially unlimited amount of components which can cause this.

While there is no way to avoid this problem, there should be way to restore back Android boot partition, preferably using user friendly steps.
Proposed solution could be:
- when we backup Android recovery partition, also backup Android boot partition - This should be added regardless of this bug.
- add to ubuntu dualboot application settings option to restore boot partition from backup

However this would just restore Android functionality, and potentially revert change which was deliberately done. So we will also need to copy content of boot partition to recovery partition to keep changes committed on Ubuntu boot image.

Setting importance to medium, since this happened only when modifying Ubuntu image, and it's out of normal usage pattern.

[Rex Tsai (chihchun)]

The default ubuntu touch image is read-only, the user should upgrade his/her system with system-image-cli[1].

I don't think apt-get upgrade is expected behavior.

[1] http://wiki.ubuntu.com/ImageBasedUpgrades

[Ondrej Kubik (ondrak)]

This is no dualboot bug, and it cannot be fixed from dualboot.
It is advance use of Ubuntu where Ubnutu boot image is modified on running system, against which dualboot application cannot protect.
However Ubuntu Engineering team did changes which should prevent this happening