touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #53765
[Bug 1383490] Re: Device automatically updated after rebooting into recovery (without telling the system to update)
This bug report is a bit old (bugs on the project get a lot more timely
review than bugs on the Ubuntu package), however, I think this is still
invalid.
IIUC, what I think was happening was that the ubuntu_command file was
written to recovery in preparation for applying at reboot time. The
presence of that file is what tells recovery that it needs to apply the
update, and actually contains the commands to run. So probably once you
were in recovery, if you had deleted the ubuntu_command file, it
wouldn't have gotten applied.
I think this is a corner case outside the normal use case, so I'm going
to mark it as Won't Fix. If you feel strongly about it, create a bug
task on this bug for the ubuntu-system-image project and provide any
other information that makes sense. This probably *could* be supported
by deferring the write of the ubuntu_command file until the
.ApplyUpdate() method is called. Changing that alone wouldn't be
difficult, but making the test suite work again would probably be a
PITA. :)
** Changed in: system-image (Ubuntu)
Status: New => Won't Fix
--
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/1383490
Title:
Device automatically updated after rebooting into recovery (without
telling the system to update)
Status in system-image package in Ubuntu:
Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
Invalid
Bug description:
I have auto-download updates enabled by default, and I noticed one
update was downloaded automatically, but I didn't want the device to
update itself, as I was changing the system for development purposes.
After calling 'adb reboot recovery', it automatically flashed the new
image (that was cached), even though I had never asked that.
I don't think we should be automatically hooking up the auto-flash
when you run recover, unless the user accepts that (as it can cause
all sorts of issues when you're changing the base system).
Using image RTM 118 on krillin.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1383490/+subscriptions