#8190 NORM Not Tri: olpc-update's irsync_pristine step always fails with "Contents manifest failure at line 383" on localtime

[Zarro Boogs per Child]

#8190: olpc-update's irsync_pristine step always fails with "Contents manifest
failure at line 383" on localtime
-------------------------------+--------------------------------------------
   Reporter:  skierpage        |       Owner:  cscott                           
       Type:  defect           |      Status:  new                              
   Priority:  normal           |   Milestone:  Not Triaged                      
  Component:  upgrade utility  |     Version:  Development build as of this date
 Resolution:                   |    Keywords:                                   
Next_action:  never set        |    Verified:  0                                
  Blockedby:                   |    Blocking:                                   
-------------------------------+--------------------------------------------

Comment(by skierpage):

 Replying to [comment:1 mavrothal]:
 > and in the middle of it (after ~5 minuts) crashes gives a white screen
 then a black screen with running text (that I can not read) and restarts
 Sugar (it does not reboot) with my old build

 That sounds like bug #5954.  As I understand it, olpc-update uses a lot of
 memory and the kernel's out-of-memory handler kills the X Window System
 which restarts.  In a terminal enter dmesg | less and you may see
 references to memory and oom.

 As for this bug, m_stone commented on IRC "irsync_pristine is always going
 to fail until we actually manage to make the root filesystem readonly. (we
 were close to that for a while, then were pulled farther away, and now are
 getting close again)"  Maybe that option should be removed from "hints" in
 /usr/bin/olpc-update.

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