pnunn wrote:Guys,
you cannot ship Mageia with kontact the way it is.
We can't really avoid it since there's several changes in kdepimlibs but also on others dependencies need by kde & used by kdepim which prevent us to stick to kmail1.
Also there's several improvement to korganizer/kaddressbook which can't be easily backported to kdepim 4.4.x
pnunn wrote:Each time a new update comes out I try it again to see if its still broken or not.. it gets worse.
Hum here it's seems to get better everytime.
But it's probably because i started from a *fresh* config and *did* not use the migration tool (which indeed gave me when i tried the idea to switch to another MUA...)
pnunn wrote:akregator does not show anything at all at the moment (although it works just fine stand alone).
hum, you should open a bug report against it if it's not working as expected (on bugs.kde.org) & add me in cc so i can pickup the fix eventually if it does not get inside the 4.8.x branch.
kmail pops up a box "Unknown error. (Unable to fetch item for backend) each time I tried to do anything. It seems to be working (all be it VERY slowly) but the errors are consistent.
pnunn wrote:I know its not the packagers at fault, but does anyone have any contact with the developers? I can't believe how they have managed to screw up what was a good mail client so badly.
Upstream say that they switching to kdepim 4.6.x and kmail2, that's all ;o)
However even if it can seems problematic, more & more developpers are working on kdepim 4.8.x currently while kdepim 4.4.x was more or less abandonned so..
It's probably difficult & we'll get somewhat a decent kmail2 only with kdepim 4.8.3 or more but that's why we need to report bug upstream as much as we can.