Project

General

Profile

Bug #9888

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

Added by Pedro Côrte-Real almost 6 years ago. Updated almost 6 years ago.

Status:
Fixed
Priority:
Low
Assignee:
-
Category:
General
Start date:
04/03/2014
Due date:
% Done:

100%

Estimated time:
Affected Version:
1.4.1
System:
all
bitness:
32-bit
hardware architecture:
amd64/x86

Description

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?

Associated revisions

Revision 986166e0 (diff)
Added by Pedro Côrte-Real almost 6 years ago

Fix bug #9888 my checking for db_info table

Revision 1ba6ae75
Added by Pascal de Bruijn almost 6 years ago

Merge pull request #517 from pedrocr/fix-db-detection

Fix bug #9888 my checking for db_info table

History

#1 Updated by Tobias Ellinghaus almost 6 years ago

  • Status changed from New to Closed: invalid

And how are we supposed to change the logic of a released software? Just don't go back. It will break eventually.

#2 Updated by Pedro Côrte-Real almost 6 years ago

You don't. But you can fix it in 1.4.2, no?

#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.

Also available in: Atom PDF

Go to top