lp:~statik/ubuntu/lucid/desktopcouch/0.6.3-bugfixes

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

21. By Elliot Murphy on 2010-03-10

Drop patches that were included in upstream bugfix release.

20. By Elliot Murphy on 2010-03-10

* New upstream bugfix release.
  - Provide more isolation in tests to avoid polluting the env when
    running tests.
  - Drop no_uri.patch and revert_dbus_getport.patch (included upstream)
  - Don't depend on simplejson, use built in json (LP: #511427)
  - Provide a method for clients to enable/disable replication of
    arbitrary databases with Ubuntu One (needed to allow enabling and
    disabling of gwibber and contact syncing).

19. By Ken VanDine on 2010-03-04

releasing version 0.6.2-0ubuntu3

18. By Elliot Murphy on 2010-03-02

In the last upload, I incorrectly resolved the merge presented
after running bzr merge-upstream --version=0.6.2
../desktopcouch_0.6.2.orig.tar.gz. So, the last upload had incorrect
contents in the tarball for desktopcouch/records/server_base.py and
desktopcouch/replication.py. This revision restores the correct contents
of those two files to match what was shipped in the upstream tarball.

17. By Elliot Murphy on 2010-03-01

Fixed the execute bit on desktopcouch-stop.

16. By Elliot Murphy on 2010-03-01

fixed a missing file from desktopcouch.

15. By Elliot Murphy on 2010-03-01

Fix standards version.

14. By Elliot Murphy on 2010-03-01

* New upstream bugfix release.
  - Include a new program bin/desktopcouch-get-port .
  - Use DBus to get port, and thereby start the service daemon, on normal
    Python access to the database. (LP: #519444)
  - Update docs to be explicit about put_record(r) mutating r .
  - Add new method put_records_batch(iterable_of_records) .
  - Fix up apport collection.
  - Fix a problem with couchdb mutating its INI file to store a hashed
    password, which is useless for HTTP Basic auth in the bookmark file.
  - Fix obscure bugs in couchdb startup regarding port availability.
  - Update execute_view() ti take a dict of additional parameters for
    execution.
  - Add has_key() method to desktopcouch.record.RecordDict so that it
    behaves more like a dictionary.

13. By Elliot Murphy on 2010-02-03

* New upstream release.
  - When logging replication events, replace all oauth secrets with a
    string of the same length.
  - Add CouchDatabase.report_changes() method.
  - Don't remove the HTML file that bookmarks point to.
  - Improve test coverage.
  - Use an explicit test context for testing.
  - For startup, loop over finding the port in case the port is not
    available when the PID is.
  - Ensure that the method that tests for the presence of a record does
    not just check if the field is present but ensures that the value
    is correct.
  - Do not read from the keyring if we have a configuration file that
    already has the info we need.
  - Move record_id to be a property rather than an attribute.
  - Improved pairing tool reliability by fixing race conditions.
  - Make the database generate it's own record IDs at "put" time, avoiding
    issues with non-idempotency of POST for doc creation.
  - Add Record.record_revision attribute to make it easier to get a records
    revision ID.
* debian/control
  - bumped standards version to 3.8.3

12. By Chad Miller on 2009-10-22

* New upstream release.
  + Fix remote-db-listing bug for SSL/HTTPS services. (LP: #458540)
  + Fix OAuth signatures for SSL urls.
  + Avoid couchdb bug where users' PID files are incorrectly interpreted as
    valid by couchdb, and so after slightly different boot, desktopcouch can
    never start couchdb, causing desktopcouch to quit. (LP: #442120)
  + For dbus, do not resolve data for events signaling a service disappears,
    and use explicit veriable-passing / references. (LP: #440072)
  + Flip push/pull logic in replication information.
  + When pulling from remote DB, do not try to access remote management DB.
  + Use meaningful names for keyring access. (LP: #451333)