#12650 NORM 13.2.0: olpc-contents-verify (fv) fails due to 'x' attribute

[Zarro Boogs per Child]

#12650: olpc-contents-verify (fv) fails due to 'x' attribute
-----------------------------+----------------------------------------------
 Reporter:  dsd              |                 Owner:  dsd          
     Type:  defect           |                Status:  new          
 Priority:  normal           |             Milestone:  13.2.0       
Component:  upgrade utility  |               Version:  not specified
 Keywords:                   |           Next_action:  never set    
 Verified:  0                |   Deployment_affected:               
Blockedby:                   |              Blocking:               
-----------------------------+----------------------------------------------
 In 13.2.0 build 3, the generated contents manifest comes with an 'x'
 attribute for /usr/bin/ping listing the one xattr that the file has
 (security.capabilities).

 This has appeared as a result of setting ping as suid root (#12427). I
 can't explain why setting the suid bit causes the xattr to appear in the
 manifest, and without suid the xattr doesn't get detected/listed, but I've
 double checked, and this is what is happening.

 This is further complicated by the fact that fv (the implementation of
 olpc-contents-verify) regards 'x' as bad data, causing a contents manifest
 failure on olpc-update to this new build. As fv has been shipped for a
 long time now, this means that we cannot support the 'x' attribute until
 we make a backwards-incompatible change in the manifest format to
 officially add this.

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