FS#51848 - [darktable] `library.db' is too new

Attached to Project: Community Packages
Opened by Ignace Libre (ignace72) - Wednesday, 16 November 2016, 08:22 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 02 December 2016, 15:41 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi.

$ darktable
[init] database version of `library.db' is too new for this build of darktable. aborting ERROR : cannot open database

Thank you.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Friday, 02 December 2016, 15:41 GMT
Reason for closing:  Fixed
Additional comments about closing:  someone who switched to 2.2 should restore this file from backup or continue using 2.2 from [community-testing]
Comment by Levente Polyak (anthraxx) - Wednesday, 16 November 2016, 11:28 GMT
its incompatible, you will need to get your database setup again i think there is no way to migrate the format backwards. What you experience is the result of a rollback to the latest stable version after a invalid update to a in-dev RC version.
Comment by Ignace Libre (ignace72) - Wednesday, 16 November 2016, 13:12 GMT
Thank you for this quick response.
I have recovered the old database since backing up my /home that I made Monday.
I think it will be problematic for all those who do not have backup.
I think those who do not have backup should be able to solve this by installing the AUR package: darktable-git.
Comment by Sergej Pupykin (sergej) - Wednesday, 16 November 2016, 16:28 GMT
In worst case you can try to edit library.db using sqlite3 or sqlitebrowser and set db_info.version to 11. But it is slightly dangerous)
Comment by Doug Newgard (Scimmia) - Wednesday, 16 November 2016, 16:53 GMT
That seems like a really, really bad idea if you don't know what else has changed
Comment by Mikołaj (travnick) - Wednesday, 16 November 2016, 18:07 GMT
Same here, after updating from darktable 2.2 rc to 2.2.0 stable (from normal repository!)
Comment by Mikołaj (travnick) - Wednesday, 16 November 2016, 18:22 GMT
LOL. Now I realized what happened:

[2016-11-15 01:42] [ALPM] upgraded darktable (1:2.0.7-2 -> 1:2.2.0rc0-1)
[2016-11-16 01:41] [ALPM] upgraded darktable (1:2.2.0rc0-1 -> 2:2.0.7-1)

Package maintainer did VERY VERY nasty thing here.
Comment by Sergej Pupykin (sergej) - Wednesday, 16 November 2016, 19:11 GMT
I've put darktable 2.2.0rc0 back to testing, so users who had important data without backup can use rc0 at least.

Sorry guys.

Loading...