#8931 NORM Not Tri: Deleting .xo bundle from Journal deletes activity

[Zarro Boogs per Child]

#8931: Deleting .xo bundle from Journal deletes activity
------------------------------+---------------------------------------------
 Reporter:  bogstad           |                 Owner:  tomeu        
     Type:  defect            |                Status:  new          
 Priority:  normal            |             Milestone:  Not Triaged  
Component:  journal-activity  |               Version:  not specified
 Keywords:                    |           Next_action:  reproduce    
 Verified:  0                 |   Deployment_affected:               
Blockedby:                    |              Blocking:               
------------------------------+---------------------------------------------
 Deleting a downloaded *.xo bundle from Journal results in the activity
 being deleted as well.

 This can easily be reproduced by using Browse to download an activity,
 verifying that it has been installed as a new activity, deleting entry
 from Journal, and verifying activity is gone.

 This behavior may have made sense when Sugar didn't have a way to
 remove an activity explicitly from the home view, but now that
 it does the Journal entry should be managed separately from the
 installed Activities directory.  Not managing these separately results in
 two copies being kept on the XO.  An unpacked copy in the Activities
 directory and the *.xo copy in the datastore.  For
 large activities (say Help, Scratch or even worse WikipediaEN),
 the extra space taken up even by the zipped second copy in the datastore
 could be a problem.  BTW, erasing the activity from the
 Home view has no effect on the journal.

 Note: This is in 767 aka 8.2.  The version field in trac doesn't seem to
 have been updated to accept either of those yet.  I suppose that might be
 considered a metabug...

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