touch-packages team mailing list archive

[John McAleely <1403463@xxxxxxxxxxxxxxxxxx>]

You're quite right mpt. Not sure what possessed me to file this in UX.
the linked bug I raised it from even seems clear on the matter.

To be double sure, I just tried it on #201, and observed that when an
update has been downloaded (but you have not pressed the offered
'install' button), if you reboot into recovery, the update is applied
anyway.

That's just a bug in system settings or the system updater. will refile
appropriately.

** Also affects: ubuntu-system-settings (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: system-image (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: ubuntu-ux
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1403463

Title:
  System Updates should not always be automatic

Status in the base for Ubuntu mobile products:
  Incomplete
Status in Ubuntu UX bugs:
  Invalid
Status in system-image package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Currently, the update process on a phone image is two stages -
  download the update, and then reboot to a maintenance mode (recovery)
  to install the update. A final reboot brings the phone back up in the
  updated form.

  The UI treats this as one operation, and once started, the update
  cannot be stopped. This causes specific problems when an update has
  downloaded, and (for unrelated reasons) a reboot is needed to
  recovery. At this point, the phone will always try to apply any
  pending update.

  Sometimes this is the exact opposite of what the user needs. The user
  may be aware of problems with the device, and be rebooting into
  recovery to perform other maintenance tasks. It is possible that
  applying an update will make matters worse, and will certainly
  inconvenience the user, who will wish to do maintenance, not wait for
  an update to occur.

  The biggest class of users this will impact is developers, who will
  often wish to reboot to recovery for image maintenance tasks, and who
  may not have elected to entirely disable automatic updates.

  The other important use case is users with machines exhibiting
  problematic symptoms who are working with support personnel. Those
  users have no way to be sure that a reboot to recovery will not
  trigger an invasive update to the system.

  This bug is to request user interface that allows the user to express
  the notion 'please don't install any downloaded update on the next
  reboot'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1403463/+subscriptions