#7760 NORM Opportu: problems with Software update in the Sugar Control Panel

[Zarro Boogs per Child]

#7760: problems with Software update in the Sugar Control Panel
-------------------------------+--------------------------------------------
   Reporter:  walter           |       Owner:  cscott       
       Type:  enhancement      |      Status:  reopened     
   Priority:  normal           |   Milestone:  Opportunity  
  Component:  upgrade utility  |     Version:  not specified
 Resolution:                   |    Keywords:               
Next_action:  never set        |    Verified:  0            
  Blockedby:                   |    Blocking:               
-------------------------------+--------------------------------------------
Changes (by mikus):

 * cc: mikus at bga.com (added)
  * status:  closed => reopened
  * type:  defect => enhancement
  * resolution:  invalid =>
  * milestone:  8.2.0 (was Update.2) => Opportunity


Comment:

 There is a philosophy question here.

 All these problems funnel through a specific point - the updater.  Sure
 you can say that it is not the fault of the updater -- but OLPC users will
 see these problems when they use the *updater*, not when they use the
 individual activity.

 I think it would be "worthwhile" to have the updater warn the user about
 'problems in updating' caused by identifiable inconsistencies in the
 activities, rather than have the user sooner or later encounter OLPC
 behavior that he does not understand (such as forever updating Scratch).

 I'm suggesting that updater inspect the activity.info file in the bundle,
 to see if the values specified there (e.g., Name, Version) could cause
 conflicts if the bundle were installed.

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