#6400: "update streams" wipe out user improvements without notice
-----------------------------+----------------------------------------------
Reporter: gnu | Owner: cscott
Type: defect | Status: new
Priority: high | Milestone: Never Assigned
Component: upgrade utility | Version: Build 650
Keywords: | Verified: 0
Blocking: | Blockedby:
-----------------------------+----------------------------------------------
My MP XO, serial number CSN7500230F, appears to have been forcibly
upgraded to Build 656, remotely, last night.
This occured within an hour after I had explicitly upgraded it to the
latest update.1-691 build. It had previously been running update.1-690.
Now there is no trace of update.1 on the machine!
The only way I had any clue of what happened is that (1) the machine was
sitting idle in Build 650 after having finished the olpc-update from
update.1-690 to update.1-691, when it suddenly rebooted and I saw it do
so. This was curious, but I had no idea why it would reboot. (2) I saw
something in the weekly news about "100 randomly selected laptops" having
been forcibly upgraded. (3) The login console now shows "build 656",
which I don't think I ever loaded on it.
It's already hard enough to manage "olpc-update" upgrades -- without
having them happen at random times under remote control! They are
destructive in a way that "yum" or "apt-get" updates are not; they
wantonly destroy all kinds of things that the user may have deliberately
modified. And the user's ability to choose an OS version to keep as the
backup version, when running olpc-update, is nonobvious at best. When
remotely commanded, there is NO ability to choose an OS to keep as the
backup.
--
Ticket URL: <http://dev.laptop.org/ticket/6400>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system