GNOME Bugzilla – Bug 682820
Settings not converted on backup restore
Last modified: 2012-09-05 09:09:52 UTC
Hi, I did not ind any bugs related to what I'm face of... I'm using around 30 labels for mail tags, and used to filter in vfolders. While upgrading fedora 16 to 17, evolution 3.2.3 to 3.4.3, all my labels disappeared. I tried to import a 3.2.3 backup file, but same behavior. Let me know what I can do to help in providing you more details. Thanks
I found the reason: Some configurations data has been moved from gconf to gsettings. I used gsetting-data-convert to restore my labels (and other folder settings). I think evolution should do the conversion if we are upgrading. Is there any reason why it is not executed? Thanks
Thanks for a bug report. I thought the conversion is run on its own, though I didn't know when it's run. Do you think it's an issue of packaging, rather than upstream?
From the packaging point of view, ie RPM, may be the call to 'gsetting-data-convert' should be an idea. But, as I imagine that existing evolution data are stored with the evolution version (let's say 3.2.3), then when we start the new version ie 3.4.3, evolution should detect this change and start settings conversion from gconf to gsettings. I think this should be the best place for conversion. Related to backup/restore, it may be the same case. The backup is made under an old version ie 3.2.3 using gconf. So, as soon as data are restored (untar), and detected as an old data version ie 3.2.3, then the gconf to gsettings should be executed. As of now, from what I see, the backup made under 3.4.3 is still using gconf... So, this means the backup will lost evolution setting. Not good at all. Hope it will help...
You are right, the restore should run the data convert when it's done. I'll cook something for that. Thanks for the opinion.
Created attachment 223504 [details] [review] evo patch for evolution; This calls gsettings-data-convert after import of old keys into GConf. This is not fully applicable to 3.4.x, but I think it may work too there.
Created commit 39cf487 in evo master (3.5.92+)