Hi Jared, (and Hi to other intrepid users),

Here's what occurred for me for nine collections when restoring from
osaf.us after the migration to Cosmo 0.6 and using my existing .ini file
with the test/restore settings menu option:

No. of collections     Error msg in the restore dialogue boxes

1                          Global name 'M2Crypto' is not defined
1                          Can't parse webpage
1                          <class 'zanshin http HTTPError'> (500)>
1                          <class 'zanshin http HTTPError'> (501)>
1                          That collection was not found
4                          [no error msg...collection restored]

Of the five collections that didn't initially restore, when using next
the Share/Restore published share menu option, I was able to restore
four more collections. The last collection failed consistently to
restore on a particular event (the name of the event being displayed for
some time) finally showing the error message: Connection was closed
cleanly. This is the collection that generated the M2Crypto message
above. Deleting the apparently offensive event revealed more offending
events. After deleting the offending events from this collection via the
Cosmo UI, the ninth and final collection was finally able to be
restored.

Whew!
Andre

On Tue, 27 Feb 2007 18:39:28 -0800, "Jared Rhine" <[EMAIL PROTECTED]>
said:
> Hello, wonderful OSAF users!
> 
> If you are using the OSAF hosted service (osaf.us), it has been updated. 
>   You may need to make changes to your configuration per the 
> instructions below.  Please let us know here (the chandler-users list) 
> if you are having any problems with the service after this update.
> 
> -------- Original Message --------
> Subject: osaf.us updated to Cosmo 0.6.0
> Date: Tue, 27 Feb 2007 18:36:30 -0800
> From: Jared Rhine <[EMAIL PROTECTED]>
> To: [email protected]
> 
> The osaf.us sharing server has been updated to Cosmo 0.6.0.
> 
> All accounts and data have been preserved.
> 
> However, some URLs have changed.  If you were subscribing to a
> collection via ATOM or iCal (webcal), you will need to update your
> clients to new URLs.
> 
> To determine the new URLs that you'll need to put into iCal, Google
> Reader, or whatnot, login to the Cosmo user interface
> (http://osaf.us/cosmo/) and select your collection from the left-hand
> drop-down menu.  Then click on the "i" button next to that menu.  From
> there you'll be able to get the proper URL to use in your client.
> (Select "Feed Reader" for an ATOM reader like Google Reader and "Apple
> iCal 2.x" for iCal or other webcal client).
> 
> Additionally, some people have had difficulty with their Chandler
> collections not synchronizing after the server update (not everyone is
> affected).  If you have problems, and your collections show an error
> icon, then you may need to restore your shares via the "restore
> settings" or "restore shares" dialogs in the Chandler desktop menus.
> 
> We'll provide more instructions if additional problems are seen or
> people need extra help in using the updated system.
> 
> Thanks!  Your patience and use of the OSAF products is appreciated!
> 
> -- Jared
> 
> _______________________________________________
> chandler-users mailing list
> [EMAIL PROTECTED]
> http://lists.osafoundation.org/mailman/listinfo/chandler-users
-- 
  Andre Mueninghoff
  [EMAIL PROTECTED]

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to