Created by Thomas Vander Stichele and last modified
Get this branch:
bzr branch lp:~thomasvs/desktopcouch/0.5-keyring
Only Thomas Vander Stichele can upload to this branch. If you are Thomas Vander Stichele please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Thomas Vander Stichele

Recent revisions

101. By Thomas Vander Stichele <email address hidden>

add a maemo detection hack

100. By Thomas Vander Stichele <email address hidden>

Fix one use of key when writing ini file

99. By Thomas Vander Stichele <email address hidden>

move to keyring module (in an incompatible way, since we can't specify the attributes)

98. By Thomas Vander Stichele <email address hidden>

extracting all keyring access to a separate desktoptouch.key module

97. By Chad Miller

Bump version number for release.

96. By Chad Miller

I made a bad assumption about port availibility, namely that once couchdb
writes its PID file, that the port is already open and we should be able to
discover it. This is not true; there is a tiny fraction of time in which we
can suceed in getting the process ID, and then fail to get the port number.
This makes us raise an exception. This timing bug problem happens regularly
on some classes of computers.

This is a backport of the fix applied to development trunk, with minimal
extra changes.

95. By Chad Miller

Release 0.5. This makes pull replication work from HTTPS-protected services.

94. By Eric Casteleijn

pull replication no longer uses a http call to get remote database names in case of ssl

93. By Chad Miller

Release 0.4.6.

92. By Chad Miller

Couchdb does not check validity of PID files, and happily reports that it is already running if a process exists that is referred to by a stale file. (LP: #442120)

Now, remove PID file before we try starting couch, if we detect it is invalid.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.