Hi,
I found a mail at the Ximian that explained how to make forced migration. This worked at least for me:
From guenther
guenther@rudersport.de:
"Q: "How can I force migration of 1.4.x data?"
FWIW: This option has been removed from the stable release, cause it was
meant for excessive beta testing only. Anyway, there is a way to force
migration.
Note: You will do anything mentioned below ON YOUR OWN RISK. Create a
backup in case anything goes wrong -- backup your old ~/evolution
directory as well as the new 1.5/2.0 ~/.evolution directory.
Make sure the old 1.4 directory still exists and holds all the *latest*
data.
Now here is how to manually force migration again:
* Shutdown any running evolution processes.
$ evolution-2.0 --force-shutdown
* Edit the GConf keys /apps/evolution/version and last_version to read
"1.4.0". You can use gconf-editor or the command line interface:
$ gconftool-2 --set /apps/evolution/version --type string "1.4.0"
$ gconftool-2 --set /apps/evolution/last_version --type string "1.4.0"
* Remove (do you have a backup?) or rename (as shown) the new hidden
~/.evolution directory:
$ mv ~/.evolution ~/old-evolution-2.0.0
* Then run Evolution 2.0.0 and it should migrate your 1.4.x data again.
Lean back and have a good cup of coffee, beer, whatever... :-)
Reset both GConf keys to "2.0.0", if not already done. AFAIK
last_version will not be reset.
HTH
...guenther"
I hope this helps,
Jonne.