soledad client: db is not initialized from debian package
The observable symptom of this bug is that the local sqlcipher database for the soledad client is apparently initialized correctly (the u1db tables are apparently created, and during the first use everything seems to be ok), but after the db_handle is closed and opened again one can see that data has not been written to disk (the db file has zero size). This only happens for the debian package, and not for the pypi version (that's built from the amalgamation).
This is a followup to the problems in #3619 and #5562 (closed), in an attempt to isolate the real problem. I think I might have misdiagnosed the issue, blaming the WAL functionality when the scope of the problem is indeed broader. A minimal example where the problem can be reproduced should be made, and compare what's different in the context of the pypi package from the debian package.
(from redmine: created on 2015-01-30, closed on 2015-09-02)
- Relations:
- relates #3619
- relates #5562 (closed)
- Uploads: