Hi Andreas,
If I can give my cent...
1. keep your 3.0.2 database backup safe
2. do not use „load sidecar file …“ which is buggy
3. ... try the different configuration options after replaying the
migration ... but here I cannot help much. Using "legacy module order"
you should be able to keep your module order safe. You may try to set
"legacy order" on a 3.0.2 database, at least on some images as a test,
before migration to 3.2.1... (and disable write xmp file to not to lose
them)
Hoping that will help.
Philippe
On 12/08/2020 16:42, Andreas Herold wrote:
Hi Richard,
thank you. I tried It, but applied afterwards the order has not changed back.
I have enabled writing of xmp files and I’m seeing that the timestamps of xmp
files of images I had not opened yet, are still before the upgrade to 3.2.1.
Most xmp files should still contain the right information. Do I have a chance
to load this information from xmp files? The „load sidecar file …“ button is
not an option. It’s too much work to do it for so many pictures.
I also have a backup of the old library and could switch back to version 3.0.2.
I would then disable auto apply of pixel workflow before doing the upgrade.
Do you have any idea, what’s the preferred/better way?
Andreas
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
