#8906 NORM Not Tri: collection can leave a .xol file in ~olpc/.sugar/default/data , then can't erase

[Zarro Boogs per Child]

#8906: collection can leave a .xol file in ~olpc/.sugar/default/data , then can't
erase
------------------------+---------------------------------------------------
  Reporter:  skierpage  |           Owner:  marco        
      Type:  defect     |          Status:  new          
  Priority:  normal     |       Milestone:  Not Triaged  
 Component:  sugar      |         Version:  not specified
  Keywords:             |     Next_action:  never set    
Spec_stage:  unknown    |       Blockedby:               
  Blocking:             |   Spec_reviewer:               
  Verified:  0          |   Spec_reviewed:  0            
------------------------+---------------------------------------------------
 In 8.2.0, along with david at lang.hm I tried making collections based on
 http://wiki.laptop.org/go/Content_bundle_making_script

 If the .xol bundle's library/library.info does not have a category= line,
 the Journal silently fails to install the collection and leaves a copy in
 ~olpc/.sugar/default/data/.  With a category line, the Journal installs it
 and runs Browse, but still leaves a copy of the .xol file in
 ~olpc/.sugar/default/data/.

 If the collection installed OK, you can later remove it from the library
 by locating the .xol in the journal and choosing Erase.  But the file
 remains in ~olpc/.sugar/default/data/

 To reproduce, download http://www.skierpage.com/olpc/test_xol.xol and open
 it in Journal.  (It creates a "test_xol" entry under "media" in the
 Library.)

 Other .xol files like "World culture" v 3 don't have this problem, so the
 bugs may be a) Content_bundle_making_script is inaccurate and b)
 Sugar/Journal's .xol processing isn't very robust.

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