darktable 1.4.1 won't refuse to load but instead throw a bunch of errors if the database has been upgraded by running git master
I'm been testing git master in /opt/darktable/bin/darktable but still have 1.4.1 installed and first in my path. When I screwed up and ran that instead I noticed that it actually ran and opened the database but only after spitting out a bunch of errors.
Shouldn't 1.4.1 just refuse to run when the database is newer than what it knows how to handle?
#3 Updated by Pedro Côrte-Real almost 6 years ago
Pull request submitted for this:
#4 Updated by Tobias Ellinghaus almost 6 years ago
- System changed from Ubuntu to all
- % Done changed from 0 to 100
- Target version set to Candidate for next patch release
- Status changed from Closed: invalid to Fixed
- Category set to General
Even if the requested actions are impossible we got it for the next release of the 14x branch.