#9658 NORM 1.5-F11: New journal cannot read old stored Journal Entries

[Zarro Boogs per Child]

#9658: New journal cannot read old stored Journal Entries
----------------------------------------+-----------------------------------
           Reporter:  martin.langhoff   |       Owner:  tomeu                            
               Type:  defect            |      Status:  new                              
           Priority:  normal            |   Milestone:  1.5-F11                          
          Component:  journal-activity  |     Version:  Development build as of this date
         Resolution:                    |    Keywords:                                   
        Next_action:  diagnose          |    Verified:  0                                
Deployment_affected:                    |   Blockedby:                                   
           Blocking:                    |  
----------------------------------------+-----------------------------------

Comment(by martin.langhoff):

 Quozl - seems #9559 is about Journal entries in the datastore, not on
 external storage; so probably not.

 Tomeu:

 I proposed using JEBs in external storage, but both people raised valid
 concerns around the fact that external apps can't open them. So an
 abiword/Write.xo document goes from rtf which can be edited anywhere, to
 something obscure and unknown (.xoj)

 The question -- however -- is more relevant to #9657 . This bug we are
 discussing here was filed so that we remember that we _also_ need compat
 code to at least _read_ the oldstyle .olpc.store directory (while still
 ignoring it if it's corrupt).

 We have 2 things to address:

  - sharing from Sugar 0.84 to Sugar 0.84 via external removable disk
 (#9657)
  - sharing from Sugar 0.82 to Sugar 0.84 via external removable disk (this
 bug here)

 there is also sharing "backwards" from 0.84 to 0.82 but all the solutions
 are ugly, it is compounded with _activity_ backwards compat, and it is
 just less of a priority, since deployments must upgrade per-school and
 (relatively quickly) upgrade the whole deployment...

 trying to support backwardst compat across the board is a veritable
 nightmare...

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