Re: Goodbye for now, kmail

Daniel Vrátil <[email protected]> Sun, 07 May 2017 00:04:19 +0200
Newsgroups	gmane.comp.kde.users.pim
Organization	KDE
Message-ID	<2822562.1Pu9rkB8E5@mjollnir>
On Saturday, May 6, 2017 2:47:21 PM CEST ianseeks wrote:
> On Saturday, 6 May 2017 11:04:33 BST Daniel Vrátil wrote:
> > On Saturday, May 6, 2017 11:11:27 AM CEST ianseeks wrote:
> > > On Saturday, 6 May 2017 09:36:51 BST Martin Steigerwald wrote:
> > > > ianseeks - 06.05.17, 08:29:
> > > > > > This is the really annoying part: it all just works for me. I
> > > > > > don't
> > > > > > know
> > > > > > what I'm doing wrong, but it just works. I can't reproduce many of
> > > > > > the
> > > > > > misbehaviors and issues that users report and without that I can't
> > > > > > fix
> > > > > > them. Believe me that it really annoys me and that I'd much rather
> > > > > > had
> > > > > > the
> > > > > > most broken setup ever that I could just analyze and fix, but I
> > > > > > guess
> > > > > > I'm
> > > > > > just too lucky (or unlucky, depends on the point of view :-))
> > > > > 
> > > > > Is there someway we can all check release levels are all consistent
> > > > > with
> > > > > all  the software required for KDEPIM?  It could be that all your
> > > > > pieces
> > > > > of
> > > > > software are correctly matched with each other whereas a lot of us
> > > > > just
> > > > > accept the upgrades and some of us may now have misaligned software
> > > > > releases
> > > > 
> > > > Well at least that one should be easy enough as Akonadi and KDEPIM has
> > > > same
> > > > version number on each release since quite some time.
> > > 
> > > I was thinking more of versions of individual bits of software within
> > > the
> > > major versions, all it takes is for one failed update of one small piece
> > > of
> > > software to perhaps cause an issue.  As Dan  is not able to reproduce a
> > > lot
> > > of issues, maybe we should be able to validate our installation against
> > > his
> > > to see if there are differences.
> > 
> > Ensuring that you have all the parts in the same version is usually up to
> > the distribution (and you checking package manager logs :-))
> 
> Indeed.
> 
> Is your working KDEPIM installation from a Distro packaging system or one
> you put together yourself?  If so, can you tell us which distro you use so
> we can possibly see if all users of that distro also have a working system.
>  I realise I am grasping at straws here and will be my last grab at a straw
> :)

I'm on Fedora, but I'm running a self-compiled git master of KDE PIM (on top 
of self-compiled KDE Frameworks). I use the same build for both development 
and production use (the latter forces me to make sure I don't brake things too 
much :-))

I don't wipe Akonadi DB at all and I cary my Akonadi/KMail config since for 5 
or so years, so it's not that I would be using a pristine setup either.

> > Anyway, I think most of the issues boil down to different configurations,
> > setups and similar factors - and in KDE PIM, that's almost an infinite
> > number of combinations :-)
> > 
> > > > On Debian I´d try
> > > > 
> > > > apt list | egrep "akonadi|kmail|kdepim-runtime"
> > > > 
> > > > and make sure that Akonadi packages, libakonadi packages,
> > > > libkf5akonadi
> > > > packages as well as kdepim-runtime (containing the Akonadi resources
> > > > for
> > > > KDEPIM like IMAP or maildir resource) and kmail package are all the
> > > > the
> > > > same major version, i.e. currently 16.04. But if you can I suggest you
> > > > try to use a later version, cause 16.04 is older than a year already.
> > > > However for me this one works pretty stable except for the performance
> > > > related shortcomings.
> > > > 
> > > > Oh, BTW the folder has still not been moved.
> > > > 
> > > > Ciao,


-- 
Daniel Vrátil
www.dvratil.cz | [email protected]
IRC: dvratil on Freenode (#kde, #kontact, #akonadi, #fedora-kde)

GPG Key: 0x4D69557AECB13683
Fingerprint: 0ABD FA55 A4E6 BEA9 9A83 EA97 4D69 557A ECB1 3683
signature.asc (application/pgp-signature, 833 B)