¡Hola Garrett! El 2016-09-03 a las 19:32 -0400, Garrett Kajmowicz escribió:
Can we get some traction on this issue. I'm having the exact same problem. However, I don't want to delete my SQLITE databases because they contain any additional annotations and tags that I've added. I would expect a software version upgrade to handle this transparently.
Ideally, you should be able to dump the sqlite data (unless the database can't be opened anymore, which I don't think it's the case), move the old database away, generate a new one starting akonadi, and load the data back.
If the issue is produced by the akonadi upgrade, having a way to reproduce the issue (as minimal as possible) should help.
Something along the lines: Initial environment: - Starting a new vm from foobar. - Running the akonadi, kmail, and such as such packages from the snapshot [1] version X (or from jessie) Working configuration: - Setting up sqlite - Configuring kmail2 * Everything works - Backup the database for future checks Upgrade: - Upgrading only such and such packages to version X, Y * Results in a database corruption - Backup the database for further debugging Test restoring the old database: - ... Test deleting the database: - ... Test new user: - Setting up sqlite - Configuring kmail2 * Everything works - Backup database for further debuggingCould you try to produce such a recipe for reproducing the issue and report the issue upstream?
Happy hacking, [1] http://snapshot.debian.org/ -- "If I ask another professor what he teaches in the introductory programming course, whether he answers proudly "Pascal" or diffidently "FORTRAN," I know that he is teaching a grammar, a set of semantic rules, and some finished algorithms, leaving the students to discover, on their own, some process of design." -- Robert W. Floyd Saludos /\/\ /\ >< `/
Attachment:
signature.asc
Description: PGP signature