Bug 180676 - migration from KDE 3 to KDE 4 kmail identities and so on
Summary: migration from KDE 3 to KDE 4 kmail identities and so on
Status: RESOLVED DUPLICATE of bug 169827
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-14 15:54 UTC by Frank Andreas
Modified: 2009-02-08 19:12 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Andreas 2009-01-14 15:54:46 UTC
Version:            (using KDE 3.5.10)
Installed from:    SuSE RPMs

There is no posibility to migrate from KDE 3 to 4 without loosing 
* Identities
* SMTP-Server-Settings 
* Mail-Filters
etc in KMail.
It make a lot of trubble to migrate this by hand.
Comment 1 Kevin Krammer 2009-01-15 20:27:44 UTC
Please check if KDE4 is properly configured to use the same local prefix, e.g. by running

% kde4-config --localprefix

That should be the same as running

% kde-config --localprefix

If it is not, e.g. the KDE4 one being $HOME/.kde4 and the one for KDE3 being $HOME/.kde then the distributions upgrade tool/script did not properly copy/link the files to the location they chose.
In which case it might be better to file a buf report on their bug tracker.
Comment 2 Krzysztof Sobolewski 2009-02-07 21:05:02 UTC
I don't know if it changed in KDE 4.2, but copying kmail files from ~/.kde to ~/.kde4 does not work (or at least did not work last I tried). So I'm gonna have to vote for this bug and hope for a less painful migration :)
Comment 3 Kevin Krammer 2009-02-08 02:43:23 UTC
Can you check if it works if you remove/move .kde4 and copy the whole tree before starting KDE4?

KDE uses .kde in both versions and therefore all upgrade facilitied assume they have access to the older version's files.
If a distributor decides to use different prefixes, it is up to them to provide migration tools.
Comment 4 Kevin Krammer 2009-02-08 13:56:43 UTC

*** This bug has been marked as a duplicate of bug 169827 ***
Comment 5 Krzysztof Sobolewski 2009-02-08 19:12:05 UTC
Amazing! It worked! :D
Honestly, I don't know what to say ;)