#6470 NORM Never A: olpc-update doesn't let users manage their software builds

[Zarro Boogs per Child]

#6470: olpc-update doesn't let users manage their software builds
------------------------------+---------------------------------------------
  Reporter:  gnu              |       Owner:  cscott                           
      Type:  defect           |      Status:  new                              
  Priority:  normal           |   Milestone:  Never Assigned                   
 Component:  upgrade utility  |     Version:  Development build as of this date
Resolution:                   |    Keywords:                                   
  Verified:  0                |    Blocking:                                   
 Blockedby:                   |  
------------------------------+---------------------------------------------

Comment(by mikus):

 Replying to [comment:4 gnu]:
 > Here's an example of how others also don't understand olpc-update:

 gnu - I'm not sure why you used my name here.

 The point I was trying to make is that I __do__ understand what 'olpc-
 update' is trying to do.  [And I *do* use how it works to manage what is
 on my XO.]

 As I said, I have installed both Joyride (normally primary) and Update.1
 (normally alternate) builds.  I booted Joyride, and used 'olpc-update' to
 replace the ("not running" from the viewpoint of Joyride) Update.1 build
 with the latest Update.1 version.

 When I had finished installing the latest Update.1 version, I booted
 Update.1.  Update.1 was now my current primary, and the (previously used)
 Joyride was now my alternate.  I now used 'olpc-update' to replace the
 ("not running" from the viewpoint of Update.1) Joyride build with the
 latest Joyride version.

 --------

 I had done this kind of "build management" many times before.  What was
 different yesterday was that I installed new versions of *both* kinds of
 builds on the same day.

 My experience has been that whenever I install a new build version, the
 customizations I had applied to the earlier version of that kind of build
 have been over-written with "pristine" content from the build I just
 installed.  [Meaning I have to re-apply my customizations.]


 The reason I posted yesterday was NOT confusion between primary vs.
 alternate.  It was because I thought I had applied customizations only
 once (to Joyride, with Joyride booted), but found my customizations also
 in Update.1 (with Update.1 booted).

 I do *not* believe that 'olpc-update' failed to newly install both builds
 -- whichever one I boot, 'About this XO' (on Main view) shows the
 __correct__ (installed yesterday) version.
 .

-- 
Ticket URL: <http://dev.laptop.org/ticket/6470#comment:6>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system