public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDEPIM-4.7.3 hits the stable tree ...  brrrrr!
Date: Thu, 8 Dec 2011 06:45:12 +0100	[thread overview]
Message-ID: <20111208054512.GA13528@eisen.lan> (raw)
In-Reply-To: <201112071912.23133.michaelkintzios@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2081 bytes --]

On Wed, Dec 07, 2011 at 07:11:53PM +0000, Mick wrote:
> Thankfully eselect news spells it out and this link makes me thing twice about 
> my next steps:
> 
>   http://wiki.gentoo.org/wiki/KDEPIM-4.7_upgrade
> 
> Following Alan's disastrous experience where he saw all his messages disappear 
> before his eyes I am doubly cautious.
> 
> Has anyone tried the migration to 4.7 yet?
> 
> Only to make things slightly more complicated ... has anyone tried it who's 
> been using sqlite3 like I do, instead of the recommended MySQL?
> 
> Any gotchas other than backups of everything recommended in the news article?

I installed my first 4.7.x kdepim on 30th of July. I was quite happy with it.
Migration went smooth and I only had to recreate my filters, I guess because
the filters’ target folders were now addressed differently.

kdepimlibs-4.7.3 came on 4th of november. The only thing I remember from
the last weeks is that I was unable to read any mail. All I got in KMail were
revolving cirlces and “Fetching folder content” screens. I didn’t lose any
mail, as far as I can tell. But I was growing tired of Akondi even before that.
So being unable to read anything finally pushed me to mutt. ^^

I don’t have _that_ many mails, at the time of my switching about 13000 or so,
mostly in a few mailing lists. The average dev probably has much more than
that. But even with that number, I had more than 30 seconds of additional full
HDD load after login (once I removed the mail resources, login time until idle
went from 1:05 to ~33 seconds). Plus, all mail files were individually
duplicated in the Akonadi folder... what gives? While I understand the
reasoning behind Akonadi and its potential, I do question the implementation.

I might try it again in 4.8, but right now I’m keeping my hands off.
That’s probably not what you wanted to hear, but I just couldn’t resist.
-- 
Gruß | Greetings | Qapla'
I forbid any use of my email addresses with Facebook services.

Being adult means that nothing is being added upstairs.

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-12-08  5:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 19:11 [gentoo-user] KDEPIM-4.7.3 hits the stable tree ... brrrrr! Mick
2011-12-08  5:45 ` Frank Steinmetzger [this message]
2011-12-08  6:47   ` Mick
2011-12-08 14:51     ` Frank Steinmetzger
2011-12-08 19:57       ` Mick
2011-12-08 16:26 ` Dương "Yang" ヤン Hà Nguyễn
2011-12-08 22:17   ` Frank Steinmetzger
2011-12-11 19:06   ` Daniel D Jones
     [not found] <i5vc6-3Se-15@gated-at.bofh.it>
     [not found] ` <i5FXP-55F-3@gated-at.bofh.it>
     [not found]   ` <i5NC2-12J-5@gated-at.bofh.it>
     [not found]     ` <i5Sim-vr-5@gated-at.bofh.it>
2011-12-09 15:47       ` Indi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111208054512.GA13528@eisen.lan \
    --to=warp_7@gmx.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox