#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 cscott):

 Replying to [comment:3 skierpage]:
 > 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.

 That's not exactly true; irsync_pristine has a number of hacks hard-coded
 to make it expected to succeed on 'normal' systems.  But it's not perfect
 (it will be in the 9.1 timeframe, as mstone says), and you can still dirty
 your pristine copy in some situtations.

 This seems to be one of them: how on earth are you writing to
 /etc/localtime?  Sugar's timezone setting feature explicitly does *not*
 set this.  Elsewhere /etc/avahi/etc/localtime was fingered as a co-culprit
 -- is there some network environment in which avahi can be induced into
 writing to /etc/localtime?  That certainly doesn't happen at 1cc.  I'd be
 interested in more information.  Perhaps an Apple machine is on the
 network, broadcasting "interesting" mDNS services?

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