Hello,
I have just a small warning for users of kde-redhat repo.
If you installed kde 4.5.0 (or 4.5.1) from kde-unstable and let this repository enabled, the new kdepim (4.4.93) will arrive to you as an update. It is NOT stable release and MAY corrupt your PIM data (e-mails etc.).
You should be aware that this can happened when you're using _unstable_ repo, but I think many people enabled unstable repo just for kde 4.5.* (like me) and don't want to risk to lost their PIM data (like me).
Radek Novacek
The update went fine for me (thanks Rex - I'd been trying and failing to build it myself) with a simple pop+maildir configuration.
Be warned however, that the new kmail will consume A LOT of disk space and you won't be able to see the message bodies if you run out of disk space. There is no warning of this. I filed a bug for this - https://bugs.kde.org/show_bug.cgi?id=249987 - and I would suggest that this be regarded as a blocker for inclusion in Fedora.
I presume this disk use is due to indexing? Seems a bit excessive though - the migration used up 3.5Gb for a 15Gb set of maildirs.
Also beware that the migration will hog your system for quite a while as it indexes everything - took an hour or so of 9.95 system load on my system (2.5Ghz dual core with ssd), so likely be very painful on an older system.
Apart from that all works fine.
cheers M.
On Fri, Sep 3, 2010 at 10:59 AM, Radek Novacek rnovacek@redhat.com wrote:
Hello,
I have just a small warning for users of kde-redhat repo.
If you installed kde 4.5.0 (or 4.5.1) from kde-unstable and let this repository enabled, the new kdepim (4.4.93) will arrive to you as an update. It is NOT stable release and MAY corrupt your PIM data (e-mails etc.).
You should be aware that this can happened when you're using _unstable_ repo, but I think many people enabled unstable repo just for kde 4.5.* (like me) and don't want to risk to lost their PIM data (like me).
Radek Novacek _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Radek Novacek wrote:
I have just a small warning for users of kde-redhat repo.
If you installed kde 4.5.0 (or 4.5.1) from kde-unstable and let this repository enabled, the new kdepim (4.4.93) will arrive to you as an update. It is NOT stable release and MAY corrupt your PIM data (e-mails etc.).
Indeed. kde-unstable is precisely that. Now that kde-4.5.x is in kde- testing, if that's all you want, that's all you should be using. That should be safe. kde-unstable sometimes isn't.
My sincere apologies if that wasn't entirely clear before and caught folks by surprise.
-- Rex
On Friday 03 September 2010 12:50:21 Rex Dieter wrote:
Indeed. kde-unstable is precisely that. Now that kde-4.5.x is in kde- testing, if that's all you want, that's all you should be using. That should be safe. kde-unstable sometimes isn't.
My sincere apologies if that wasn't entirely clear before and caught folks by surprise.
-- Rex
I had updated by mistake, I was in doing several jobs at the same time and did not notice that the kdepim* packages were among the updates, even though I remembered your note.
I have 9 dimap accounts configured. The migration process did not went well, for those accounts that are based on google.mail it worked but some other that work now it failled.
Even after the migration process was completed kmail would not appear. Recalling kmail again would import again some of the failled accounts in to a local archive. The final result was that I had several copies of some of the accounts and I has not able to remove them from akonadi.
As others have noted previously for large volumes of email the system becomes really slow, the memory used is so large that the swap is used and then no work is done.
Several quirks from the process, akonadi throws several pop-ups if some message is not well downloaded. This is disastrous, you can end with more than 300 pop-ups open. Clearly a pop-up to tell such a trivial thing is not a solution.
During the migration process I got messages like: Error while creating item: Unknown error. (NO Unable to write item changes into the database)
The system was unusable at the end so I had to downgrade to the previous version.
Due to all the work that was done to insure that a downgrade works I had no problem reverting to the previous version. (I had to reset the ~/.local/share/akonadi directory because the previous one had 14 GB, and akonadi would take long time to start)
On Monday, September 06, 2010 11:18:02 am José Matos wrote:
On Friday 03 September 2010 12:50:21 Rex Dieter wrote:
Indeed. kde-unstable is precisely that. Now that kde-4.5.x is in kde- testing, if that's all you want, that's all you should be using. That should be safe. kde-unstable sometimes isn't.
My sincere apologies if that wasn't entirely clear before and caught folks by surprise.
-- Rex
I had updated by mistake, I was in doing several jobs at the same time and did not notice that the kdepim* packages were among the updates, even though I remembered your note.
I have 9 dimap accounts configured. The migration process did not went well, for those accounts that are based on google.mail it worked but some other that work now it failled.
Even after the migration process was completed kmail would not appear. Recalling kmail again would import again some of the failled accounts in to a local archive. The final result was that I had several copies of some of the accounts and I has not able to remove them from akonadi.
As others have noted previously for large volumes of email the system becomes really slow, the memory used is so large that the swap is used and then no work is done.
Several quirks from the process, akonadi throws several pop-ups if some message is not well downloaded. This is disastrous, you can end with more than 300 pop-ups open. Clearly a pop-up to tell such a trivial thing is not a solution.
During the migration process I got messages like: Error while creating item: Unknown error. (NO Unable to write item changes into the database)
The system was unusable at the end so I had to downgrade to the previous version.
Due to all the work that was done to insure that a downgrade works I had no problem reverting to the previous version. (I had to reset the ~/.local/share/akonadi directory because the previous one had 14 GB, and akonadi would take long time to start)
Would be great to forward this experience to upstream developers.
R.
On Monday 06 September 2010 13:58:32 Jaroslav Reznik wrote:
Would be great to forward this experience to upstream developers.
R.
Done: https://bugs.kde.org/show_bug.cgi?id=250373