#9657 NORM 1.5-F11: Journal Entry storage / sharing via USB stick doesn't work

[Zarro Boogs per Child]

#9657: Journal Entry storage / sharing via USB stick doesn't work
------------------------------+---------------------------------------------
 Reporter:  martin.langhoff   |                 Owner:  tomeu        
     Type:  defect            |                Status:  new          
 Priority:  normal            |             Milestone:  1.5-F11      
Component:  journal-activity  |               Version:  not specified
 Keywords:                    |           Next_action:  never set    
 Verified:  0                 |   Deployment_affected:               
Blockedby:                    |              Blocking:               
------------------------------+---------------------------------------------
 On os34, if I

 1 - create a new Journal entry (named "F11-100") with some content
 (and exit activity)
 2 - plug in a USB stick
 3 - copy the Journal entry to the USB stick via drag-n-drop in the
 Journal...
 4 - exploring the USB disk shows a F11-100.gtar file with _no_
 metadata, and the metadata seems to (maybe) be stored in a database in
 .olpc.store/index

 and then...

 5 - unmount, unplug the USB disk
 6 - plug it back in, wait for it to mount...
 7 - Journal shows F11-100.gtar, and doesn't know what to do with it.

 Sugar 0.84 has fixed an old problem (the Journal going to la-la-land
 if the .olpc.store/inded DB was corrupt) by completely ignoring the
 metadata DB.

 Now, the metadata DB had a role in the workflow I describe above. Has
 anything taken that role? Maybe the new mechanism isn't kicking in
 correctly? Does it work on 0.86 somehow? (Maybe we can backport it?)

 In the field, exchanging and storing journal entries via USB stick is a
 major thing.

 In the back of my mind, I had expected that Journal Entry Bundles
 (JEBs) would be used for this, but

  - the Journal doesn't store a JEB on the disk
  - the Journal doesn't recognize a valid JEB on the disk

 If there is no other fix in sight, the best course of action I can propose
 is to use JEBs as I describe here.

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