Project

General

Profile

Bug #11673

Module basecurve version mismatch 4 !=5

Added by Alex Mozheiko almost 2 years ago. Updated over 1 year ago.

Status:
Closed: invalid
Priority:
Low
Assignee:
-
Category:
Darkroom
Target version:
Start date:
07/21/2017
Due date:
% Done:

0%

Affected Version:
2.2.5
System:
Ubuntu
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Hello guys,
I was running 2.2.4 version until recently I switched to 2.2.5. After the upgrade to 2.2.5 version (though grabbed from Ubuntu repo) DT started pushing the following message '[image name] module 'basecurve' version mismatch: 4 !=5' Now, the module is off by default unless I explicitly turn it on. Also I can use some of its presets except for the custom.
The previous setup contained custom presets I had developed per each ISO of my camera. Now they cannot be clicked and thus used. I suspect their incompatibility with the new settings environment. Also many of the instances used for particular images disappeared from the image history.
What do I do to use to restore the presets and the history in version 2.2.5?
Regards,
Alex

History

#1 Updated by Alex Mozheiko almost 2 years ago

PS the previous 2.2.4 version was installed from GIT

#2 Updated by Roman Lebedev almost 2 years ago

  • Status changed from New to Incomplete
  • % Done changed from 0 to 20

Alex Mozheiko wrote:

Hello guys,
I was running 2.2.4 version until recently I switched to 2.2.5. After the upgrade to 2.2.5 version (though grabbed from Ubuntu repo) DT started pushing the following message '[image name] module 'basecurve' version mismatch: 4 !=5' Now, the module is off by default unless I explicitly turn it on. Also I can use some of its presets except for the custom.
The previous setup contained custom presets I had developed per each ISO of my camera. Now they cannot be clicked and thus used. I suspect their incompatibility with the new settings environment. Also many of the instances used for particular images disappeared from the image history.
What do I do to use to restore the presets and the history in version 2.2.5?
Regards,
Alex

That version mismatch means that you somehow upgraded git master (2.3.0), run darktable at least once, and then downgraded to 2.2.x
That is expected to fail, downgrading is not possible
Look in apt logs (/var/log/dpkg.log, /var/log/aptitude, /var/log/apt/history.log, /var/log/apt/term.log), about which versions of the darktable package it talks?
This is probably a user error.

#3 Updated by Alex Mozheiko almost 2 years ago

My sincere apologizes Roman, you are absolutely right - I was using 2.3.0 instead of 2.2.4. Installing it late at night I was sure I cloned 2.2.3 version, while it was 2.3.0 in fact. So it appears now I have installed 2.2.5 alongside 2.3.0.

Here's the dpkg.log output

2017-07-21 14:58:03 install darktable:amd64 <none> 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:03 status half-installed darktable:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:04 status triggers-pending hicolor-icon-theme:all 0.15-0ubuntu1
2017-07-21 14:58:04 status half-installed darktable:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:04 status triggers-pending man-db:amd64 2.7.5-1
2017-07-21 14:58:04 status triggers-pending desktop-file-utils:amd64 0.22-1ubuntu5.1
2017-07-21 14:58:04 status half-installed darktable:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:04 status triggers-pending gnome-menus:amd64 3.13.3-6ubuntu3.1
2017-07-21 14:58:04 status triggers-pending mime-support:all 3.59ubuntu1
2017-07-21 14:58:04 status unpacked darktable:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:04 status unpacked darktable:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:04 install darktable-dbg:amd64 <none> 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:04 status half-installed darktable-dbg:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:06 status unpacked darktable-dbg:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:06 status unpacked darktable-dbg:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:06 trigproc hicolor-icon-theme:all 0.15-0ubuntu1 <none>
2017-07-21 14:58:06 status half-configured hicolor-icon-theme:all 0.15-0ubuntu1
2017-07-21 14:58:06 status installed hicolor-icon-theme:all 0.15-0ubuntu1
2017-07-21 14:58:06 trigproc man-db:amd64 2.7.5-1 <none>
2017-07-21 14:58:06 status half-configured man-db:amd64 2.7.5-1
2017-07-21 14:58:07 status installed man-db:amd64 2.7.5-1
2017-07-21 14:58:07 trigproc desktop-file-utils:amd64 0.22-1ubuntu5.1 <none>
2017-07-21 14:58:07 status half-configured desktop-file-utils:amd64 0.22-1ubuntu5.1
2017-07-21 14:58:07 status installed desktop-file-utils:amd64 0.22-1ubuntu5.1
2017-07-21 14:58:07 trigproc gnome-menus:amd64 3.13.3-6ubuntu3.1 <none>
2017-07-21 14:58:07 status half-configured gnome-menus:amd64 3.13.3-6ubuntu3.1
2017-07-21 14:58:07 status installed gnome-menus:amd64 3.13.3-6ubuntu3.1
2017-07-21 14:58:07 trigproc mime-support:all 3.59ubuntu1 <none>
2017-07-21 14:58:07 status half-configured mime-support:all 3.59ubuntu1
2017-07-21 14:58:08 status installed mime-support:all 3.59ubuntu1
2017-07-21 14:58:08 startup packages configure
2017-07-21 14:58:08 configure darktable:amd64 1:2.2.5-0pmjdebruijn1~xenial <none>
2017-07-21 14:58:08 status unpacked darktable:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:08 status half-configured darktable:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:08 status installed darktable:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:08 configure darktable-dbg:amd64 1:2.2.5-0pmjdebruijn1~xenial <none>
2017-07-21 14:58:08 status unpacked darktable-dbg:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:08 status half-configured darktable-dbg:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:08 status installed darktable-dbg:amd64 1:2.2.5-0pmjdebruijn1~xenial
2017-07-21 14:58:08 startup packages configure

The rest of the logs identify the last installation as 2.2.5, which obviously it is
Any chances to use the basecurve presets in 2.2.5? What do you think about exporting from 2.3.0 and importing them into 2.2.5?

Regards,
Alex

#4 Updated by Tobias Ellinghaus almost 2 years ago

I see six ways for you to get your presets back, easiest first, hardest last:

  1. Restore them from a backup if you have one
  2. Find an image that uses the settings from the preset and that wasn't opened with 2.3.0. Open it in darkroom and create a new preset from that
  3. Find an image exported (as JPEG) with darktable 2.2.* that had the settings from the preset applied, manually load that in lighttable as the sidecar of some random raw file, then proceed as before
  4. Upgrade to git master and use that, it works quite well
  5. Recreate your preset manually
  6. As a last resort: use an hex editor to turn the preset into something 2.2.5 will understand

For rescuing the image settings that got updated when you opened them in 2.3.0 only 1, 4, 5 and 6 will work

#5 Updated by Alex Mozheiko almost 2 years ago

Thank you Tobias, I relied on your word and used option 4 upgrading to git master. It works well now.
I'm such a fool, thank you guys for your patience, Looking forward to 2.3.x release!

#6 Updated by Roman Lebedev almost 2 years ago

  • Status changed from Incomplete to Closed: invalid
  • % Done changed from 20 to 0

Alex Mozheiko wrote:

Thank you Tobias, I relied on your word and used option 4 upgrading to git master. It works well now.
I'm such a fool, thank you guys for your patience, Looking forward to

2.3.x release!

2.4
even - stable releases; odd - dev versions

#7 Updated by Roman Lebedev over 1 year ago

  • Target version changed from Candidate for next patch release to 2.4.0

Also available in: Atom PDF