How do I upgrade KMail/Kontact/Akondi?

I have just upgraded from opensuse 10.3 to 10.4 (clean install). To avoid having to re-configure KMail I restored the mail files along with:
.kde4/share/config/kmailrc
.kde4/share/config/mailtransports
.kde4/share/config/emaildefaults
.kde4/share/config/emailidentities
.kde4/share/apps/kmail/*
.local/share/akonadi/

I found this last restore (akonadi) caused kontact to lockup when I send an email with the following error messages:

kontact(17163)/kio (KIOJob) KIO::TransferJob::slotData: mimeType() not emitted when sending first data!; job URL = KUrl("<snip>") data size = 0
martin@linux-lkky:~> kontact(17163)/kio (KIOJob) KIO::TransferJob::slotData: mimeType() not emitted wht data!; job URL = KUrl("<snip>") data size = 0

So I reverted back to the original akonadi database and it now seems to work fine, however I am curious for future upgrades I may have to do, what is the correct procedure for upgrading akonadi database when doing an update with clean install? What data do I loose by not restoring akonadi database?

Martin

Correction:
of course I meant:
upgraded from opensuse 11.3 to 11.4 (clean install)

One thing I seem to have lost is that I now need to provide a password at startup before KMail will access the network.

Martin

MY akonadi server stores contacts and events/appointments/…

Is there a reason you did not copy your whole home directory?
This way you can restore most of your settings.

> Is there a reason you did not copy your whole home directory?
> This way you can restore most of your settings.

Because I have found, in the past, that sometimes file formats etc. change and cause programs to malfunction. At least if I do this a few files at a time I can see what is causing the problem.

As far as I can see something must have changed in the akonadi database because the old version is causing the errors above.

Or perhaps the old database is causing problems because its out of step with other files? So perhaps I should have restored all of my home directory in one go?

Martin

Akonadi stores some files in ~/.config

Thanks, that’s fixed it.

I have now restored both:
.local/share/akonadi/*
.config/akonadi/*
and I now have access to my contacts data again.

I guess this is not the place to raise concerns about this, but it does worry me that this information is held in a database. One of the things that I liked about kontact/kmail was that everything was held in simple text configuration files so if anything went wrong I could always get my data using a text editor.

Anyway, thanks for your help,

Martin

Right, forgot about ~/.local

At the moment, the Akonadi data is spread over the whole system, I don’t
like this, too …

where could one post a feature request to have this behavior fixed (eventually the possibility to perform a “migration backup” with one click of all kontakt/akonadi data with one click. Or would this be a bad idea for some reason?

Since KDE 4.6 (I think) Nepomuk has the feature to create backups and
restore them, so why not Akonadi, too?

I would start by asking in the KDE forums:
http://forums.kde.org/

If you start a thread, maybe you can post a link here.