URL: https://linuxfr.org/forums/linux-mandriva/posts/mandrake-101-probleme-de-migration-devolution-14-vers-2 Title: Mandrake 10.1 : Probleme de Migration d'EVOLUTION 1.4 vers 2 Authors: Fakir Date: 2005年01月18日T16:17:56+01:00 Tags: Score: 0 En fait là c'est mon ignorance de l'anglais qui me handicape. J'ai peur de faire une boulette. Tout ceci est un peu confus pour moi. Et apparement c'est pas sans danger (becareful ça je comprends) ! Je vous transmets le contenu de mes recherches. Si quelqu'un peut me dire ce que je dois faire cela m'aiderai sérieusement. On Tue, 2004年10月26日 at 15:28 +0000, Eric wrote: > I'm using evolution 1.4.6, how much of a job is it to upgrade to 2.x? > Thanks > Eric Should be as simple as 'urpmi evolution', at a root command prompt, assuming all your urpmi sources are up-to-date. It will automatically resolve all required dependencies and update. Be warned, though, Evolution relies on a *lot* of packages (mostly because the packages it directly relies on also rely on others, which rely on others, and so on); if you haven't kept your system up-to-date, this may result in a *large* set of files being downloaded. After installing the packages, just run Evolution as you normally would; the first time you do this, it should detect that you were running 1.4 and automatically migrate to the new 2.x standards. As a nice side benefit, because 2.x stores its data in ~/.evolution instead of ~/evolution it's easy to backpedal if you decide you don't like it (of course, you'll lose whatever changes you might have made since starting to use 2.x, but you should know pretty quick whether 2.x is worth it or not). If updating packages via urpmi results in a massive download list, you might want to consider just upgrading to 10.1 instead; I believe it has a pre-release version (1.5.93 or something like that) which can be updated to 2.0 final in the same way as mentioned above. I'm not sure, though, as I keep up with Cooker, instead of the formal releases (running an AMD64 box, so I generally have to build from the source packages instead). -------------------------------------------------------------------------- > for your interest: > evolution <=1.4.x used to use the directory "~/evolution". > "~/.evolution" is the directory which is used by evolution 1.5.x/2.0.x > to store its data. > > both your questions should be solved by forcing evolution to explicitly > import all data by starting it with "evolution --force-migrate". > evolution should recognize the old 1.4 data in the folder "~/evolution" > and should convert it to "~/.evolution". > since i assume that you have already used 2.0.x, evolution should > *normally* ask you questions since some files already exist (but be > careful to not overwrite your new email files with the old ones by > fault!). therefore it's a bit risky and i'd strongly consider to backup > everything before doing this, e.g. by shutting down evolution properly > by "evolution --force-shutdown" and then .tar.gz'ing both the 2.0.x > directory (~/.evolution) and ~/.gconf/apps/evolution if you also > want your settings. make sure to also shutdown gconf (gconftool-2 > --shutdown) before restoring the files otherwise it may not pick them up > properly. > > take a look into the archives for an exact description of it... Here's how to force migration: [http://lists.ximian.com/archives/public/evolution/2004-September/03(...)](http://lists.ximian.com/archives/public/evolution/2004-September/039343.html) Be careful! This will overwrite all your Evolution 2.0.x data! This likely isn't an issue for you, if you did not change/add any vital data like Contacts, account settings or local mail. FYI : Evolution would have automagically migrated all your old stuff, if you would have restored the old (1.4.x) ~/evolution directory before running Evolution 2.0.x for the first time... ....guenther -------------------------------------------------------------------------- "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. ...guenther -------------------------------------------------------------------------- Merci

AltStyle によって変換されたページ (->オリジナル) /