Re: [Evolution] Manual migration of evolution to new machine

[Milan Crha <mcrha redhat com>]

On Mon, 2016-08-08 at 14:00 -0400, chernoff astro cornell edu wrote:
> My plan, based on the help page
>
> https://help.gnome.org/users/evolution/stable/data-storage.html.en
>
> is to copy .local/share/evolution, .config/evolution, 
> .config/evolution/sources
> and .config/dconf from the week old image to the new Fedora installation 
> (removing whatever might be there) and then add in the files modified in the last 
> week.

        Hi,
skip the ~/.config/dconf, it contains your settings with respect of the
options. When you copy to ~/.config/evolution, then you've already
covered ~/.config/evolution/sources.

> I am ignoring the older evolution-backup...tar.gz file since it's
> older; I will remove the folders.db files since it can't be correct.

Maybe restore from the old backup first, then overwrite/add new files
from the home directory. That way you get quite close to the previous
state.

> Will this be sufficient? For example, do I need to re-trigger the "first 
> run assistant"?

The migration between versions is done automatically. Ideally unset
everything under /org/gnome/evolution* GSettings/DConf options first,
because there is stored whether the migration had been already done or
not. Once you restore from the backup file you get the options
overwritten too, though not all of them.

As you are going to play with the internal Evolution files, ideally do
that with the background evolution processes stopped. The problem is
that these can be restarted by your desktop environment, like GNOME
Shell does restart the evolution-calendar-factory on its own. Thus
ideally copy files from a text terminal, rather than from a graphical
UI, and verify that none evolution background process is running before
playing with those internal files (`ps ax | grep evolution` will show
you which evolution-related processes are still running).

        Bye,
        Milan