desktopcouch

lp:~mandel/desktopcouch/fix_pairing

Created by Manuel de la Peña on 2010-09-10 and last modified on 2010-09-10

Only Manuel de la Peña can upload to this branch. If you are Manuel de la Peña please log in for upload directions.

No branches dependent on this one.

Merged into lp:desktopcouch at revision 172

Chad Miller (community): Approve on 2010-09-10

Eric Casteleijn (community): Approve on 2010-09-10

Natalia Bidart (community): Approve on 2010-09-10

Bug #634396: desktopcouch pairing broken	Critical	Fix Released
Bug #634784: Desktopcouch call back for ubuntu_sso signal does not have the correct number of parameters	Critical	Fix Released

172. By Manuel de la Peña on 2010-09-10: Ensures that the logging does not throw any exception and that the callback used to listen the new credentials does have the correct number of parameters.
171. By Chad Miller on 2010-09-09: new source release, 0.6.7.
170. By Chad Miller on 2010-09-09: Add the Ubuntu One pairing to the desktopcouch code
169. By Chad Miller on 2010-09-09: Instead of giving python-couchdb view objects to the user, give an object we
own that implements reconnecting to the server on errors, and proxies commands
otherwise.
168. By Chad Miller on 2010-09-09: On couchdb failure, reconnect with logic that starts up the couchdb server again and uses the new port.
167. By Chad Miller on 2010-07-27: Make Basic-auth part of compulsory INI file. (LP: #599745)
166. By Chad Miller on 2010-07-20: Support new Basic auth for HTTP that our bookmark file requires. (LP: #599745)
165. By Chad Miller on 2010-07-12: When a stored record exists and is marked as deleted, and a user tries to store a new record with the same ID, do some ugly work to make the user's record be the deleted-record's successor. (LP: #462245)
164. By Chad Miller on 2010-06-22: New release 0.6.6. This may be skipping some pseudo-0.6.5 versions in the wild.
163. By Chad Miller on 2010-06-22: Don't spam users with debug messages. Keep log files small.

This branch contains Public information

Everyone can see this information.