#10079 NORM Not Tri: olpc-update of 2g machine fails, causes disk-full on next boot

[Zarro Boogs per Child]

#10079: olpc-update of 2g machine fails, causes disk-full on next boot
------------------------------------+---------------------------------------
           Reporter:  pgf           |       Owner:               
               Type:  defect        |      Status:  new          
           Priority:  normal        |   Milestone:  Not Triaged  
          Component:  not assigned  |     Version:  not specified
         Resolution:                |    Keywords:               
        Next_action:  never set     |    Verified:  0            
Deployment_affected:                |   Blockedby:               
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by Quozl):

 agreed, removing a failed update might be useful, but this prevents
 eventual gradual use of olpc-update; a laptop that had insufficient space
 for the update would repeatedly download and then have the downloaded data
 destroyed.

 it may be better to just not do an olpc-update unless sufficient space is
 available.  that is have it fail with an error rather than begin the task.

 this may mean that olpc-update cannot be run on laptops with too many
 activities or stored content; but that's always been the case.

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