Re: KDEPIM transition

[Martin Steigerwald]

Martin Steigerwald - 08.01.23, 12:24:53 CET:
> Martin Steigerwald - 05.01.23, 11:32:17 CET:
> > As you may have already noticed as Patrick uploaded the packages to
> > unstable yesterday.
> 
> Update to KDEPIM 22.12 and new Plasma 5.26.5 and quite some other new
> KDE Application packages 22.12.1 went through just fine on AMD64.
> Digikam, KMyMoney and others have been rebuilt.

This is on Unstable. Testing will take longer.

-- 
Martin

Re: KDEPIM transition

[Martin Steigerwald]

Martin Steigerwald - 05.01.23, 11:32:17 CET:
> As you may have already noticed as Patrick uploaded the packages to
> unstable yesterday.

Update to KDEPIM 22.12 and new Plasma 5.26.5 and quite some other new 
KDE Application packages 22.12.1 went through just fine on AMD64. 
Digikam, KMyMoney and others have been rebuilt.

Best,
-- 
Martin

Re: KDEPIM 21.08: blank settings window in KMail

[Dietz Proepper]

Am Samstag, 28. August 2021, 16:36:52 CEST schrieb Martin Steigerwald:
> Dietz Proepper - 28.08.21, 14:31:45 CEST:
> > Am Mittwoch, 25. August 2021, 09:50:16 CEST schrieb Martin
> 
> Steigerwald:
> > > Hi.
> > > 
> > > KDEPIM upgrade to 21.08 in Debian Unstable should be possible,
> > > unless
> > > you rely on Digikam. digikam-private-libs still needs a rebuilt.
> > > 
> > > Did anyone update? Do you also see a blank settings window in KMail?
> > 
> > As a quick workaround, if I use kmail from within Kontact, I can
> > access all kmail settings via the Kontact setup dialog.
> 
> Thanks, that is a really nice work-around. I did not think of trying
> this!

I found it out by accident ;-).

signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 21.08: blank settings window in KMail

[Martin Steigerwald]

Dietz Proepper - 28.08.21, 14:31:45 CEST:
> Am Mittwoch, 25. August 2021, 09:50:16 CEST schrieb Martin 
Steigerwald:
> > Hi.
> > 
> > KDEPIM upgrade to 21.08 in Debian Unstable should be possible,
> > unless
> > you rely on Digikam. digikam-private-libs still needs a rebuilt.
> > 
> > Did anyone update? Do you also see a blank settings window in KMail?
> 
> As a quick workaround, if I use kmail from within Kontact, I can
> access all kmail settings via the Kontact setup dialog.

Thanks, that is a really nice work-around. I did not think of trying 
this!

Best,
-- 
Martin

Re: KDEPIM 21.08: blank settings window in KMail

[Dietz Proepper]

Am Mittwoch, 25. August 2021, 09:50:16 CEST schrieb Martin Steigerwald:
> Hi.
> 
> KDEPIM upgrade to 21.08 in Debian Unstable should be possible, unless
> you rely on Digikam. digikam-private-libs still needs a rebuilt.
> 
> Did anyone update? Do you also see a blank settings window in KMail?

As a quick workaround, if I use kmail from within Kontact, I can access all 
kmail settings via the Kontact setup dialog.

signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 21.08: blank settings window in KMail

[Diederik de Haas]

On donderdag 26 augustus 2021 18:35:25 CEST Martin Steigerwald wrote:
> > I first upgraded my version 5.83 packages to the ones in unstable:
> > aptitude safe-upgrade ~i~V5.83.0 -t experimental
> 
> In Experimental.

You're absolutely correct.
I mentioned it as I saw various 5.83 programs/libraries and you apparently 
already had some programs from Norbert installed.

> But it could be that this was related to the library mentioned above, so
> yeah, could be that some other 5.83 libraries were in use.

As mentioned above, that was my 'suspicion' (from the output you posted 
earlier).

signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 21.08: blank settings window in KMail

[Martin Steigerwald]

Diederik de Haas - 26.08.21, 15:44:00 CEST:
> On donderdag 26 augustus 2021 14:35:08 CEST Martin Steigerwald wrote:
> > > Can those of you who see this problem, please try the kmail
> > > package
> > > https://download.opensuse.org/repositories/home:/npreining:/
> > > debian-kde:/apps2108/Debian_Unstable/amd64/
> > > kmail_21.08.0-1~np1_amd64.deb (for
> > > Debian_Unstable, for testing use Debian_Testing)
> > > It should be installable as is.
> > 
> > Not with Debian Unstable packages:
> > 
> > LANG=en dpkg -i kmail_21.08.0-1~np1_amd64.deb
> > (Reading database ... 417884 files and directories currently
> > installed.) Preparing to unpack kmail_21.08.0-1~np1_amd64.deb ...
> > Unpacking kmail (4:21.08.0-1~np1) over (4:21.08.0-1~np1) ...
> > dpkg: dependency problems prevent configuration of kmail:
> > kmail depends on libkf5coreaddons5 (>= 5.84.0); however:
> > Version of libkf5coreaddons5:amd64 on system is 5.83.0-2.
> > kmail depends on libkf5kcmutils5 (>= 5.85.0-1~np1); however:
> > Version of libkf5kcmutils5:amd64 on system is 5.83.0-2.
> > kmail depends on libkf5xmlgui5 (>= 5.85.0-1~np1); however:
> > Version of libkf5xmlgui5:amd64 on system is 5.83.0-2.
> 
> I first upgraded my version 5.83 packages to the ones in unstable:
> aptitude safe-upgrade ~i~V5.83.0 -t experimental

In Experimental.

> Started KMail and settings window still didn't work. I did it without
> logging out or anything, so there's a reasonable chance the 5.83
> versions were still in use.

Hmm, here KMail after installation as above just didn't start as it 
didn't find some library symbols. But it could be that this was related 
to the library mentioned above, so yeah, could be that some other 5.83 
libraries were in use.

Ciao,
-- 
Martin

Re: KDEPIM 21.08: blank settings window in KMail

[Diederik de Haas]

On donderdag 26 augustus 2021 14:35:08 CEST Martin Steigerwald wrote:
> > Can those of you who see this problem, please try the kmail package
> > https://download.opensuse.org/repositories/home:/npreining:/
> > debian-kde:/apps2108/Debian_Unstable/amd64/
> > kmail_21.08.0-1~np1_amd64.deb (for
> > Debian_Unstable, for testing use Debian_Testing)
> > It should be installable as is.
> 
> Not with Debian Unstable packages:
> 
> LANG=en dpkg -i kmail_21.08.0-1~np1_amd64.deb
> (Reading database ... 417884 files and directories currently installed.)
> Preparing to unpack kmail_21.08.0-1~np1_amd64.deb ...
> Unpacking kmail (4:21.08.0-1~np1) over (4:21.08.0-1~np1) ...
> dpkg: dependency problems prevent configuration of kmail:
>  kmail depends on libkf5coreaddons5 (>= 5.84.0); however:
>   Version of libkf5coreaddons5:amd64 on system is 5.83.0-2.
>  kmail depends on libkf5kcmutils5 (>= 5.85.0-1~np1); however:
>   Version of libkf5kcmutils5:amd64 on system is 5.83.0-2.
>  kmail depends on libkf5xmlgui5 (>= 5.85.0-1~np1); however:
>   Version of libkf5xmlgui5:amd64 on system is 5.83.0-2.

I first upgraded my version 5.83 packages to the ones in unstable:
aptitude safe-upgrade ~i~V5.83.0 -t experimental

Started KMail and settings window still didn't work. I did it without logging 
out or anything, so there's a reasonable chance the 5.83 versions were still 
in use.

I downloaded only kmail_21.08.0-1~np1_amd64.deb and after a reboot, so 5.85 
was surely in use, I did 'sudo dpkg -i kmail_21.08.0-1~np1_amd64.deb':
[sudo] password for diederik: 
dpkg: warning: downgrading kmail from 4:21.08.0-1 to 4:21.08.0-1~np1
(Reading database ... 698466 files and directories currently installed.)
Preparing to unpack kmail_21.08.0-1~np1_amd64.deb ...
Unpacking kmail (4:21.08.0-1~np1) over (4:21.08.0-1) ...
Setting up kmail (4:21.08.0-1~np1) ...
Processing triggers for libc-bin (2.31-17) ...
Processing triggers for mailcap (3.70) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...

And now KMail's settings window does work :-)

Cheers,
  Diederik

signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 21.08: blank settings window in KMail

[Martin Steigerwald]

Norbert Preining - 26.08.21, 13:21:33 CEST:
> > Did anyone update? Do you also see a blank settings window in KMail?
> 
> I did some experiments:
> 
> * frameworks 5.85 (OBS) with kmail from sid (compiled against
> frameworks 5.83)
>   black windows
> * installed kmail from my OBS (downgrade to -1~np1) which is compiled
>   against frameworks 5.85 and running against 5.85
>   settings window shows up fine
> 
> 
> Can those of you who see this problem, please try the kmail package
>   https://download.opensuse.org/repositories/home:/npreining:/
>   debian-kde:/apps2108/Debian_Unstable/amd64/
>   kmail_21.08.0-1~np1_amd64.deb (for
> Debian_Unstable, for testing use Debian_Testing)
> It should be installable as is.

Not with Debian Unstable packages:

LANG=en dpkg -i kmail_21.08.0-1~np1_amd64.deb
(Reading database ... 417884 files and directories currently installed.)
Preparing to unpack kmail_21.08.0-1~np1_amd64.deb ...
Unpacking kmail (4:21.08.0-1~np1) over (4:21.08.0-1~np1) ...
dpkg: dependency problems prevent configuration of kmail:
 kmail depends on libkf5coreaddons5 (>= 5.84.0); however:
  Version of libkf5coreaddons5:amd64 on system is 5.83.0-2.
 kmail depends on libkf5kcmutils5 (>= 5.85.0-1~np1); however:
  Version of libkf5kcmutils5:amd64 on system is 5.83.0-2.
 kmail depends on libkf5xmlgui5 (>= 5.85.0-1~np1); however:
  Version of libkf5xmlgui5:amd64 on system is 5.83.0-2.

dpkg: error processing package kmail (--install):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.31-17) ...
Processing triggers for mailcap (3.70) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Errors were encountered while processing:
 kmail

Thanks,
-- 
Martin

Re: KDEPIM 21.08: blank settings window in KMail

[Patrick Franz]

Hej,

Am Donnerstag, 26. August 2021, 13:21:33 CEST schrieb Norbert Preining:
[...]
> 
> That would give tests with
>   kmail compiled against frameworks 5.85 but running at 5.83

I was running Frameworks 5.85 from experimental and kmail 21.08 from 
unstable (compiled against 5.83) and I got the blank window.

With Norbert's kmail version compiled against Frameworks 5.85, the 
settings window is back to normal.


> If that fails, then I suspect a bug in 5.83 and suggest we upload 5.85
> ASAP.

Agree.


-- 
Med vänliga hälsningar

Patrick Franz

Re: KDEPIM 21.08: blank settings window in KMail

[Norbert Preining]

Hi all,

> Did anyone update? Do you also see a blank settings window in KMail?

I did some experiments:

* frameworks 5.85 (OBS) with kmail from sid (compiled against frameworks
  5.83)
black windows
* installed kmail from my OBS (downgrade to -1~np1) which is compiled
  against frameworks 5.85 and running against 5.85
settings window shows up fine


Can those of you who see this problem, please try the kmail package

https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/apps2108/Debian_Unstable/amd64/kmail_21.08.0-1~np1_amd64.deb
(for Debian_Unstable, for testing use Debian_Testing)
It should be installable as is.

That would give tests with 
kmail compiled against frameworks 5.85 but running at 5.83

If that fails, then I suspect a bug in 5.83 and suggest we upload 5.85
ASAP.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Re: KDEPIM 21.08: blank settings window in KMail

[Marco Valli]

> Did anyone update? 

Yes, i did

> Do you also see a blank settings window in KMail?

Yes, i see it.
In spite of everything, kmail works perfectly, so I too will check better when 
I will have more time.
Regards

-- 
Marco Valli

Re: KDEPIM 21.08 coming to unstable

[Diederik de Haas]

On maandag 23 augustus 2021 09:21:59 CEST Martin Steigerwald wrote:
> Norbert is uploading KDEPIM / Akonadi 21.08. Please wait for builds to
> complete their work.
> 
> In generally be careful. Unstable is much more unstable again

If you stick to using 'safe-upgrade' you should be fine in Unstable.
You will see sth like "and 51 not upgraded" and that is fine. When all the 
dependencies are there, safe-upgrade will upgrade KDEPIM/Akonadi too.

signature.asc
Description: This is a digitally signed message part.

Re: Kaidan XMPP client [was Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now]

[John Scott]

(cc'ing packaging list in case anyone there knows or is working on it)

On Thursday, May 28, 2020 7:15:24 AM EDT Martin Steigerwald wrote:
> Fair enough. I was not able to use it as a XMPP client reliably.
I am in exactly the same boat as you. Never got Kopete or KDE Telepathy to 
work with XMPP, granted KTp as packaged is pretty old ATM. There is a new 
XMPP-centric KDE program called Kaidan [1] that looks very nice.

It already supports Jingle. I was able to build it from source a while ago, 
all deps are packaged and it just needed a library version from experimental.
They produce their own not-necessarily-high-quality/automatic debs upstream. I 
asked them here [2] if they'd talked to anyone about packaging it in Debian 
proper, or if it were a good idea since Kaidan is still semi-betaish.

I didn't hear back but it looks very promising.

[1] https://www.kaidan.im/2020/04/06/kaidan-0.5.0/
[2] https://invent.kde.org/network/kaidan/-/issues/29

signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 20.04 and KDE Frameworks coming to unstable now

[MERLIN Philippe]

Le jeudi 28 mai 2020, 16:42:52 CEST Martin Steigerwald a écrit :
> Hi Merlin.
> 
> MERLIN Philippe - 28.05.20, 16:24:52 CEST:
> > Is it normal today that under Sid Kdepim is still in version 17.12 ?
> 
> That is just a meta package to install the set of packages to have
> KDEPIM. Those do not need to be changed all that often.
> 
> Look at versions of packages like kmail, kontact or so or just about
> version in the application or…
> 
> % akonadictl --version
> akonadictl 5.14.1 (20.04.0)
> % kmail --version
> kmail2 5.14.1 (20.04.0)
> 
> 
> Ciao,
Ok. 
For the update I use apt and it asked me to delete Kontact Kmail ... Kdepim 
also I blocked the update following your message , I tried aptitude and the 
update seems to be carried out correctly.
Thank you very much.
Cheers.
Philippe Merlin

Re: KDEPIM 20.04 and KDE Frameworks coming to unstable now

[MERLIN Philippe]

HI!
Is it normal today that under Sid Kdepim is still in version 17.12 ?
Cheers.
Philippe Merlin
Le mercredi 27 mai 2020, 08:53:42 CEST Martin Steigerwald a écrit :
> Hi!
> 
> Woooho… it's all coming now!
> 
> As usual wait till complete.
> 
> Right now apt dist-upgrading would remove quite some packages here.
> 
> Thank you a lot, Sandro! And everyone else who may have helped with
> that.
> 
> I know it is a lot of packages. It is a lot of work to do. Even with
> some automation in place, there is still quite some manual work involved
> to have high quality packages!
> 
> Best,

Re: KDEPIM 20.04 and KDE Frameworks coming to unstable now

[Martin Steigerwald]

Hi Merlin.

MERLIN Philippe - 28.05.20, 16:24:52 CEST:
> Is it normal today that under Sid Kdepim is still in version 17.12 ?

That is just a meta package to install the set of packages to have 
KDEPIM. Those do not need to be changed all that often.

Look at versions of packages like kmail, kontact or so or just about 
version in the application or…

% akonadictl --version
akonadictl 5.14.1 (20.04.0)
% kmail --version
kmail2 5.14.1 (20.04.0)


Ciao,
-- 
Martin

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Martin Steigerwald]

Sorry, accidentally sent half finished mail before due to typo which 
triggered sending the mail.

Martin Steigerwald - 28.05.20, 09:19:00 CEST:
> Sedat Dilek - 27.05.20, 13:03:40 CEST:
> > Some stuff like kmail I have stolen from
> > incoming.d.o/buildd-unstable.
> So I did something ridiculous: I actually waited till I could upgrade
> using just the packages from unstable  – Kopete still got
> uninstalled, but as I do not need it and I think its not even up to
> date regarding XMPP/Jabber and OMEMO… I said, yes, go ahead. Thing
> is, right now it appears to me KDE does not have any suitable chat
> application. Konversation for IRC may be good to go, but I use
> Quassel IRC with core running on my server for that. But Kopete or
> KDE Telepathy appear to be mostly unmaintained and buggy.

About kopete:

I still had it from experimental. The older version has been removed 
from unstable due to using Qt4 and the newer version while based in Qt 5 
may just not be suitable for inclusion at the moment.

Fair enough. I was not able to use it as a XMPP client reliably. 

Bug#935659: Removed package(s) from unstable

https://bugs.debian.org/935659

Ciao,
-- 
Martin

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Martin Steigerwald]

Martin Steigerwald - 28.05.20, 09:19:00 CEST:
> Sedat Dilek - 27.05.20, 13:03:40 CEST:
> > Some stuff like kmail I have stolen from
> > incoming.d.o/buildd-unstable.
> So I did something ridiculous: I actually waited till I could upgrade
> using just the packages from unstable  – Kopete still got
> uninstalled, but as I do not need it and I think its not even up to
> date regarding XMPP/Jabber and OMEMO… I said, yes, go ahead. Thing
> is, right now it appears to me KDE does not have any suitable chat
> application. Konversation for IRC may be good to go, but I use
> Quassel IRC with core running on my server for that. But Kopete or
> KDE Telepathy appear to be mostly unmaintained and buggy.

About kopete:

I still had it from experimental. The older version has been removed 
from unstable due to using Qt4 and the newer version while based in Qt 5 
may just not be suitable for inclusion at the moment.


Bug#935659: Removed package(s) from unstable

https://bugs.debian.org/935659



Ciao,
-- 
Martin

Re: [Nicholas D Steeves] Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Sandro Knauß]

Hey,

> Also replying to debian-qt-kde, in case some team members are not
> following debian-kde.

this list is for bugreports only. If you want to reach the Maintainer team you 
need to use the pkg-kde-t...@alioth-lists.debian.net.

hefee

signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Martin Steigerwald]

Hi Sedat, hi community!

Sedat Dilek - 27.05.20, 13:03:40 CEST:
> Some stuff like kmail I have stolen from incoming.d.o/buildd-unstable.

So I did something ridiculous: I actually waited till I could upgrade 
using just the packages from unstable :) – Kopete still got uninstalled, 
but as I do not need it and I think its not even up to date regarding 
XMPP/Jabber and OMEMO… I said, yes, go ahead. Thing is, right now it 
appears to me KDE does not have any suitable chat application. 
Konversation for IRC may be good to go, but I use Quassel IRC with core 
running on my server for that. But Kopete or KDE Telepathy appear to be 
mostly unmaintained and buggy.

So far everything works.

Three observations so far:

- I got a warning of KAlarm about using archived alarms without having a 
calendar for it. Well I just told it not to archive alarms. So far so 
good.

- A connection error I got with a nice mail provider I use some accounts 
with IMAP got more specific and I now see that it was related to sieve 
protocol. As I don't use sieve filtering on that account I just disabled 
it. Also good.

- Unread mails in message list in KMail show in *purple* color. 
Interesting choice. So I told it to use custom color scheme and set a 
color that better suits my taste. I may report a bug about this, as with 
white background that purple really does not look that readable.

Let's see whether anything else comes up.

I do hope that the frequent stalls during POP3 retrieval or message 
filtering are gone now. They appeared somewhat before KDEPIM/Akonadi 
19.08 tough. If they aren't gone: I have not much of an idea on how to 
provide a useful upstream bug report about it, cause I have no idea what 
is causing those stalls and I see nothing obvious in logs. I am pretty 
certain tough that these are not caused by my Dovecot POP3/IMAP server.

Best,
-- 
Martin

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Sandro Knauß]

Hey,

this is more a request to out packaging list pkg-kde-talk and not for the 
users list.

@Nicholas: I'm very happy about all your work! And try to help where I can.

hefee 

--

> Kio-gdrive has a new upstream version in git.  IIRC it is also
> implicated by a bug where Google broke app authentication, and IIRC the
> fix for this is in kaccounts-integration and/or kaccounts-providers.
> I'm working on updating both of these packages.
> 
> Hefee has been teaching me about symbol files and working with me on an
> MR for kaccounts-integration.  At this time we're discussing whether now
> is the time to introduce DebianABIManager to this package.
> 
> If anyone would like to upload kio-gdrive, kaccounts-integration, or
> kaccounts-providers, please check with me first.
> 
> If this work isn't complete when hefee runs out of free time, would
> someone please volunteer to guide me through the final steps?
> 
> Thank you,
> Nicholas



signature.asc
Description: This is a digitally signed message part.

[Nicholas D Steeves] Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Nicholas D Steeves]

Also replying to debian-qt-kde, in case some team members are not
following debian-kde.

Hi!

Martin Steigerwald  writes:

> Martin Steigerwald - 27.05.20, 08:53:42 CEST:
>> Woooho=E2=80=A6 it's all coming now!
>>

:-D  Thanks to everyone who worked on this; it's a tonne of work!

>> As usual wait till complete.
>
> As Sandro told, some packages need to be recompiled. Here the list he=20
> posted:
>
> digikam
> kgpg
> kio-gdrive
> kjots
> kmymoney
> kraft
> zanshin
>
> So if you rely on any of these these, you may need to wait a little bit=20
> longer than the building of KDEPIM 20.04 and KDE Framework 5.70=20
> packages.
>

Kio-gdrive has a new upstream version in git.  IIRC it is also
implicated by a bug where Google broke app authentication, and IIRC the
fix for this is in kaccounts-integration and/or kaccounts-providers.
I'm working on updating both of these packages.

Hefee has been teaching me about symbol files and working with me on an
MR for kaccounts-integration.  At this time we're discussing whether now
is the time to introduce DebianABIManager to this package.

If anyone would like to upload kio-gdrive, kaccounts-integration, or
kaccounts-providers, please check with me first.

If this work isn't complete when hefee runs out of free time, would
someone please volunteer to guide me through the final steps?

Thank you,
Nicholas


signature.asc
Description: PGP signature

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Nicholas D Steeves]

Hi!

Martin Steigerwald  writes:

> Martin Steigerwald - 27.05.20, 08:53:42 CEST:
>> Woooho… it's all coming now!
>>

:-D  Thanks to everyone who worked on this; it's a tonne of work!

>> As usual wait till complete.
>
> As Sandro told, some packages need to be recompiled. Here the list he 
> posted:
>
> digikam
> kgpg
> kio-gdrive
> kjots
> kmymoney
> kraft
> zanshin
>
> So if you rely on any of these these, you may need to wait a little bit 
> longer than the building of KDEPIM 20.04 and KDE Framework 5.70 
> packages.
>

Kio-gdrive has a new upstream version in git.  IIRC it is also
implicated by a bug where Google broke app authentication, and IIRC the
fix for this is in kaccounts-integration and/or kaccounts-providers.
I'm working on updating both of these packages.

Hefee has been teaching me about symbol files and working with me on an
MR for kaccounts-integration.  At this time we're discussing whether now
is the time to introduce DebianABIManager to this package.

If anyone would like to upload kio-gdrive, kaccounts-integration, or
kaccounts-providers, please check with me first.

If this work isn't complete when hefee runs out of free time, would
someone please volunteer to guide me through the final steps?

Thank you,
Nicholas


signature.asc
Description: PGP signature

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Sedat Dilek]

On Wed, May 27, 2020 at 1:43 PM Sedat Dilek  wrote:
>
> As an addendum:
>
> 4 packages were uninstalled.
>
> # diff -uprN packages_before-transition-KDEPIM-and-KDE-Frameworks.txt
> packages_after-transition-KDEPIM-and-KDE-Frameworks.txt | egrep
> '^[+|-]ii' | grep -v wireless-regdb | egrep
> 'kdav|task-kde-desktop|kde-standard'
> -ii kde-standard 5:104
> -ii libkpimkdav-data 19.08.3-1
> -ii libkpimkdav5abi2:amd64 19.08.3-1
> -ii task-kde-desktop 3.59
>

I have to correct myself: libkpimkdav* was replaced by libkf5dav* packages.

+ii libkf5dav-data 20.04.1-1
+ii libkf5dav5:amd64 20.04.1-1
-ii libkpimkdav-data 19.08.3-1
-ii libkpimkdav5abi2:amd64 19.08.3-1

- Sedat -

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Sedat Dilek]

Addendum #2:

As a Debian/testing user you need:

[ cat /etc/apt/sources.list.d/debian-unstable.list ]

  deb http://ftp.debian.org/debian unstable main contrib non-free
  deb https://deb.debian.org/debian unstable main non-free contrib
##deb-src https://deb.debian.org/debian unstable main non-free contrib

[ cat /etc/apt/preferences.d/99_debian-unstable ]

Package: *
Pin: release o=Debian,a=unstable
Pin-Priority: 99

- Sedat -

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Sedat Dilek]

As an addendum:

4 packages were uninstalled.

# diff -uprN packages_before-transition-KDEPIM-and-KDE-Frameworks.txt
packages_after-transition-KDEPIM-and-KDE-Frameworks.txt | egrep
'^[+|-]ii' | grep -v wireless-regdb | egrep
'kdav|task-kde-desktop|kde-standard'
-ii kde-standard 5:104
-ii libkpimkdav-data 19.08.3-1
-ii libkpimkdav5abi2:amd64 19.08.3-1
-ii task-kde-desktop 3.59

kde-standard and task-kde-desktop are meta-packages and guess will get
a version-bump.

As a sidenote:

Qt packages from Debian/experimental with version 5.14.2 are not
co-installable after installation of this transition.

- Sedat -

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Martin Steigerwald]

Sandro Knauß - 27.05.20, 12:59:42 CEST:
> > Thanks again for all your work. And also to Scarlett for the lintian
> > cleanup.
> 
> thanks for appreciate the new pacakges. But Pino also pushed several
> patches to update symbols and install files in background and drove
> 5.69 to experimental... Others helped in improving in different ways,
> like testing the packages on experimental  or proposing fixes for
> armel or being available for chatting/discussing things etc. in the
> end never  forget it is not a one or two person show it is a team
> effort and I am very happy for all those help. In the end only one
> person can trigger the upload and so the work of others is often
> invisible...

Yeah, I sometimes wonder whether to just thank the whole team. It is so 
easily to miss someone. However, initially I used the phrase "and 
everyone who may have helped" as well.

Well anyway: Thank you to the whole Debian/Kubuntu Qt/KDE team!

Pino is doing a lot of quality work on packages, I pointed some of that 
out in other mails. Thank you, Pino!

Ciao,
-- 
Martin

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Sedat Dilek]

[ Please CC me I am not subscribed to this ML ]
[ Original Email see [1] ]

Hi,

I was able to upgrade from Debian/testing AMD64 to KDEPIM 20.04 and
KDE Frameworks 5.70 from Debian/unstable.

Good news - no rc packages after successful installation:

# dpkg -l | grep ^rc
[ EMPTY ]

Some stuff like kmail I have stolen from incoming.d.o/buildd-unstable.

You need:

[ /etc/apt/sources.list.d/debian-buildd-unstable.list ]
  deb https://incoming.debian.org/debian-buildd buildd-unstable
main contrib non-free
##deb-src https://incoming.debian.org/debian-buildd buildd-unstable
main contrib non-free

[ /etc/apt/preferences.d/99_debian-buildd-unstable ]
Package: *
Pin: release o=Debian,a=buildd-unstable
Pin-Priority: 99

...and install like this:

# apt install -t buildd-unstable kmail

The only stuff got removed is KDAV (what was expected see [2]):

# diff -uprN packages_before-transition-KDEPIM-and-KDE-Frameworks.txt
packages_after-transition-KDEPIM-and-KDE-Frameworks.txt | egrep
'^[+|-]ii' | grep -v wireless-regdb | grep -i kdav
-ii libkpimkdav-data 19.08.3-1
-ii libkpimkdav5abi2:amd64 19.08.3-1

Full diff below.

Thanks Sandro & Team.

Regards,
- Sedat -

[1] https://lists.debian.org/debian-kde/2020/05/msg00039.html
[2] https://release.debian.org/transitions/html/auto-kdav.html

P.S.: Full diff transition "KDEPIM 20.04 and KDE Frameworks 5.70"

# diff -uprN packages_before-transition-KDEPIM-and-KDE-Frameworks.txt
packages_after-transition-KDEPIM-and-KDE-Frameworks.txt | egrep
'^[+|-]ii' | grep -v wireless-regdb
-ii accountwizard 4:19.08.3-1
+ii accountwizard 4:20.04.1-1
-ii akonadi-backend-mysql 4:19.08.3-1
-ii akonadi-contacts-data 4:19.08.3-1
-ii akonadi-mime-data 4:19.08.3-1
-ii akonadi-server 4:19.08.3-1
-ii akregator 4:19.08.3-1
+ii akonadi-backend-mysql 4:20.04.1-1
+ii akonadi-contacts-data 4:20.04.1-1
+ii akonadi-mime-data 4:20.04.1-1
+ii akonadi-server 4:20.04.1-1
+ii akregator 4:20.04.1-1
-ii baloo-kf5 5.62.0-2+b1
+ii baloo-kf5 5.70.0-1
-ii breeze-icon-theme 4:5.62.0-1
+ii breeze-icon-theme 4:5.70.0-1
-ii frameworkintegration 5.62.0-1+b1
+ii frameworkintegration 5.70.0-1
-ii kactivities-bin 5.62.0-1+b2
+ii kactivities-bin 5.70.0-1
-ii kaddressbook 4:19.08.3-1
+ii kaddressbook 4:20.04.1-1
-ii kde-config-mailtransport:amd64 19.08.3-1
+ii kde-config-mailtransport:amd64 20.04.1-1
-ii kde-standard 5:104
-ii kded5 5.62.0-1+b1
-ii kdepim-addons:amd64 19.08.3-1
-ii kdepim-runtime 4:19.08.3-2
-ii kdepim-themeeditors 4:19.08.3-1
+ii kded5 5.70.0-1
+ii kdepim-addons:amd64 20.04.1-1
+ii kdepim-runtime 4:20.04.1-1
+ii kdepim-themeeditors 4:20.04.1-1
-ii kdoctools5 5.62.0-1
+ii kdoctools5 5.70.0-1
-ii kf5-kdepim-apps-libs-data 4:19.08.3-1
-ii kf5-messagelib-data 4:19.08.3-1
+ii kf5-kdepim-apps-libs-data 4:20.04.1-1
+ii kf5-messagelib-data 4:20.04.1-1
-ii kimageformat-plugins 5.62.0-1+b1
+ii kimageformat-plugins 5.70.0-1
-ii kinit 5.62.0-1+b1
-ii kio 5.62.1-2+b1
+ii kinit 5.70.0-1
+ii kio 5.70.1-1
-ii kio-ldap:amd64 19.08.3-1
+ii kio-ldap:amd64 20.04.1-1
-ii kmail 4:19.08.3-1
+ii kmail 4:20.04.1-1
-ii knotes 4:19.08.3-1
+ii knotes 4:20.04.1-1
-ii korganizer 4:19.08.3-1
-ii kpackagelauncherqml 5.62.0-1+b2
-ii kpackagetool5 5.62.0-1
+ii korganizer 4:20.04.1-1
+ii kpackagelauncherqml 5.70.0-1
+ii kpackagetool5 5.70.0-1
-ii kross 5.62.0-1+b1
+ii kross 5.70.0-1
-ii ktexteditor-data 5.62.0-1
-ii ktexteditor-katepart 5.62.0-1+b1
+ii ktexteditor-data 5.70.1-1
+ii ktexteditor-katepart 5.70.1-1
-ii kwayland-data 4:5.62.0-2
+ii kwayland-data 4:5.70.0-1
-ii libkf5activities5:amd64 5.62.0-1+b2
-ii libkf5activitiesstats1:amd64 5.62.0-1
-ii libkf5akonadi-data 4:19.08.3-1
-ii libkf5akonadiagentbase5:amd64 4:19.08.3-1
-ii libkf5akonadicalendar-data 4:19.08.3-1
-ii libkf5akonadicalendar5abi1:amd64 4:19.08.3-1
-ii libkf5akonadicontact5:amd64 4:19.08.3-1
-ii libkf5akonadicore5abi2:amd64 4:19.08.3-1
-ii libkf5akonadimime5:amd64 4:19.08.3-1
-ii libkf5akonadinotes5:amd64 4:19.08.3-1
-ii libkf5akonadiprivate5abi2:amd64 4:19.08.3-1
-ii libkf5akonadisearch-bin 4:19.08.3-1
-ii libkf5akonadisearch-data 4:19.08.3-1
-ii libkf5akonadisearch-plugins:amd64 4:19.08.3-1
-ii libkf5akonadisearchcore5:amd64 4:19.08.3-1
-ii libkf5akonadisearchdebug5:amd64 4:19.08.3-1
-ii libkf5akonadisearchpim5:amd64 4:19.08.3-1
-ii libkf5akonadisearchxapian5:amd64 4:19.08.3-1
-ii libkf5akonadiwidgets5abi1:amd64 4:19.08.3-1
-ii libkf5alarmcalendar-data 4:19.08.3-1
-ii libkf5alarmcalendar5abi1:amd64 4:19.08.3-1
-ii libkf5archive5:amd64 5.62.0-1
-ii libkf5attica5:amd64 5.62.0-1
-ii libkf5auth-data 5.62.0-1
-ii libkf5auth5:amd64 5.62.0-1+b1
-ii libkf5authcore5:amd64 5.62.0-1+b1
-ii libkf5baloo5 5.62.0-2+b1
-ii libkf5balooengine5 5.62.0-2+b1
+ii libkf5activities5:amd64 5.70.0-1
+ii libkf5activitiesstats1:amd64 5.70.0-1
+ii libkf5akonadi-data 4:20.04.1-1
+ii libkf5akonadiagentbase5:amd64 4:20.04.1-1
+ii libkf5akonadicalendar-data 4:20.04.1-1
+ii libkf5akonadicalendar5abi1:amd64 4:20.04.1-1
+ii libkf5akonadicontact5:amd64 4:20.04.1-1
+ii libkf5akonadicore5abi2:amd64 

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Sandro Knauß]

Hey,

> Thanks again for all your work. And also to Scarlett for the lintian 
cleanup.

thanks for appreciate the new pacakges. But Pino also pushed several patches 
to update symbols and install files in background and drove 5.69 to 
experimental... Others helped in improving in different ways, like testing the 
packages on experimental  or proposing fixes for armel or being available for 
chatting/discussing things etc. in the end never  forget it is not a one or 
two person show it is a team effort and I am very happy for all those help. In 
the end only one person can trigger the upload and so the work of others is 
often invisible...

hefee

signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Sandro Knauß]

Hey,

debian-kde is a user centric list and your question is more about packaging, 
so move this discussion to pkg-kde-talk.

> while working on Elisa master branch with the newly available frameworks, I
> noticed a problem with Kirigami.
> 
> I have created a merge request
> (https://invent.kde.org/frameworks/kirigami/-/ merge_requests/9 ). If
> accepted in kirigami, is it possible to backport it into the package ?

It affects elisa, so yes a backport is possible. Just provide a MR or release a 
new version yourself. As you are part of the KDE/Qt maintainer team - Everyone 
in the team is allowed to push updates!

hefee


signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Matthieu Gallien]

Hello,

On mercredi 27 mai 2020 10:15:05 CEST Sandro Knauß wrote:
> Hey,
> 
> > It appears to me that above packages are not tracked in any of those,
> > but I may just be overlooking it. They can be rebuilt once their
> > dependencies are at the required version. Which as far as I see may not
> > require all of KDEPIM packages to be built in their newest versions.
> 
> They are tracked there and it is getting more obvious, as these packages do
> not hat green checkmarks. But yes the list is quite big, but most of the
> packages are part of kdepim anyways, so they get rebuild anyways.
> 
> > This appears to be from a previous transition. KDAV became a framework
> 
> before KF 5.70 already.
> 
> That is incorrect. KDAV is still part of KDE PIM but they are preparing to
> ship it as Framework and already updated the name of the libraries. The
> release as Frameworks is planned for June or July Frameworks release (5.72
> or 5.73).
> 
> hefee

while working on Elisa master branch with the newly available frameworks, I 
noticed a problem with Kirigami.

I have created a merge request (https://invent.kde.org/frameworks/kirigami/-/
merge_requests/9 ). If accepted in kirigami, is it possible to backport it 
into the package ?

Thanks for your work, this is really nice for us users !

Best regards

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Martin Steigerwald]

Hi.

Thanks again for all your work. And also to Scarlett for the lintian 
cleanup.

Sandro Knauß - 27.05.20, 10:15:05 CEST:

> > It appears to me that above packages are not tracked in any of
> > those,
> > but I may just be overlooking it. They can be rebuilt once their
> > dependencies are at the required version. Which as far as I see may
> > not require all of KDEPIM packages to be built in their newest
> > versions.
> They are tracked there and it is getting more obvious, as these
> packages do not hat green checkmarks. But yes the list is quite big,
> but most of the packages are part of kdepim anyways, so they get
> rebuild anyways.

Ah, okay, then I missed those as I browsed the lists.

> > This appears to be from a previous transition. KDAV became a
> > framework
> before KF 5.70 already.
> 
> That is incorrect. KDAV is still part of KDE PIM but they are
> preparing to ship it as Framework and already updated the name of the
> libraries. The release as Frameworks is planned for June or July
> Frameworks release (5.72 or 5.73).

Thanks for correcting this. I mistook it for some other KDEPIM thing 
that became a framework before then. Difficult to keep track.

Best,
-- 
Martin

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Sandro Knauß]

Hey,
 
> It appears to me that above packages are not tracked in any of those,
> but I may just be overlooking it. They can be rebuilt once their
> dependencies are at the required version. Which as far as I see may not
> require all of KDEPIM packages to be built in their newest versions.

They are tracked there and it is getting more obvious, as these packages do 
not hat green checkmarks. But yes the list is quite big, but most of the 
packages are part of kdepim anyways, so they get rebuild anyways.

> This appears to be from a previous transition. KDAV became a framework 
before KF 5.70 already.

That is incorrect. KDAV is still part of KDE PIM but they are preparing to 
ship it as Framework and already updated the name of the libraries. The 
release as Frameworks is planned for June or July Frameworks release (5.72 or 
5.73).

hefee

signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Martin Steigerwald]

Martin Steigerwald - 27.05.20, 09:11:17 CEST:
> Sandro requested the transition regarding KDEPIM and KDE Frameworks
> here:
> 
> transition: KDEPIM and KDE Frameworks
> 
> https://bugs.debian.org/960534
> 
> Sandro already asked for above packages to be rebuilt once the
> required versions of KDEPIM / KDE Frameworks packages are built.
> 
> 
> This larger transition consists of several parts. Ongoing is:
> 
> https://release.debian.org/transitions/html/auto-kdav.html

This appears to be from a previous transition. KDAV became a framework 
before KF 5.70 already.

> Then comes:
> 
> https://release.debian.org/transitions/html/kcalcore.html
> 
> https://release.debian.org/transitions/html/kcontacts.html
> 
> https://release.debian.org/transitions/html/kdepim-20.04.html
> 
> That way you can at least check when KDEPIM is complete.


-- 
Martin

Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now

[Martin Steigerwald]

Martin Steigerwald - 27.05.20, 08:53:42 CEST:
> Woooho… it's all coming now!
> 
> As usual wait till complete.

As Sandro told, some packages need to be recompiled. Here the list he 
posted:

digikam
kgpg
kio-gdrive
kjots
kmymoney
kraft
zanshin

So if you rely on any of these these, you may need to wait a little bit 
longer than the building of KDEPIM 20.04 and KDE Framework 5.70 
packages.


Sandro requested the transition regarding KDEPIM and KDE Frameworks 
here:

transition: KDEPIM and KDE Frameworks

https://bugs.debian.org/960534

Sandro already asked for above packages to be rebuilt once the required 
versions of KDEPIM / KDE Frameworks packages are built.


This larger transition consists of several parts. Ongoing is:

https://release.debian.org/transitions/html/auto-kdav.html

Then comes:

https://release.debian.org/transitions/html/kcalcore.html

https://release.debian.org/transitions/html/kcontacts.html

https://release.debian.org/transitions/html/kdepim-20.04.html

That way you can at least check when KDEPIM is complete.

It appears to me that above packages are not tracked in any of those, 
but I may just be overlooking it. They can be rebuilt once their 
dependencies are at the required version. Which as far as I see may not 
require all of KDEPIM packages to be built in their newest versions.

You can always check for any transitions on the way by looking at:

https://release.debian.org/transitions/

Anyway, as usual just check output of 'apt dist-upgrade' carefully 
before proceeding :)

Best,
-- 
Martin

Processed: Re: kdepim: Limit CVE-2017-17689 (EFAIL) even more for kmail

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:kdepim
Bug #899128 [kdepim] Limit CVE-2017-17689 (EFAIL) for kmail
Bug reassigned from package 'kdepim' to 'src:kdepim'.
Ignoring request to alter found versions of bug #899128 to the same values 
previously set
Ignoring request to alter fixed versions of bug #899128 to the same values 
previously set

-- 
899128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: KDEPIM 18.08.3 for Buster

[Christian Hilberg]

Am Freitag, 15. März 2019, 12:39:55 CET schrieb Christian Hilberg:
> Hi,
> 
> Am Freitag, 15. März 2019, 12:02:42 CET schrieb Andy G Wood:
> > Hello,
> > 
> > I have also been suffering from infrequent kmail crashes in recent weeks.
> > It is not related to filtering, nor is it specific to nouveau (I use the
> > NVIDIA proprietary display driver).
> 
> I'm seeing the issue with both, nouveau and (legacy 390) nvidia blob.
> Currently running Kontact inside a VM instead, let's see what that does.

(1) KMail in a Buster VirtualBox VM did not show the issue

(2) Using nouveau, it showed that the crash path led through Qt WebEngine,
but ended in the nouveau DRI lib, which is a known issue [0], [1].
Got there through the bug I filed on bugs.kde.org [2].

(3) Using NVidia 390xx legacy blob with vblank_mode=0 __GL_SYNC_TO_VBLANK=0
relaxed the situation for me, the error does not seem to occur
(at least after a few hours there's no crash yet)

(4) disabling vblank did _not_ resolve the issue when using the nouveau
driver

(5) I've seen reports where building Qt against OpenGL ES instead of GLX
resolved the issue (but made e.g. WebGL not working)

Just 2 cents.

[0] https://bugreports.qt.io/browse/QTBUG-41242
[1] https://bugreports.qt.io/browse/QTBUG-49243
[2] https://bugs.kde.org/show_bug.cgi?id=405491

> > Not currently reproducible ... and yes I need to install debug syms in
> > order to provide more than a "me too".  The impact may be wider than
> > kmail because I have also had one okular crash too.
> 
> Regarding wider impact, the traces I've seen so far point towards
> QtWebEngine, so any app integrating this might be affected.
> 
> > Andy.
> > 
> > On Friday, 15 March 2019 09:55:10 GMT Christian Hilberg wrote:
> > > Hi there,
> > > 
> > > Am Donnerstag, 7. Februar 2019, 13:20:00 CET schrieb Martin Steigerwald:
> > > > Sandro Knauß - 07.02.19, 00:33:
> > > > > Hey,
> > > > > 
> > > > > as Debian is already in freeze, the version of KDEPIM that will
> > > > > shipped with the next stable is 18.08.3. That was uploaded same days
> > > > > ago. There is no time to package 18.12.X sorry for that.
> > > > > So please test this version in more depth and report issues. If you
> > > > > also manage to point to existing bugfixes like done in #921535 it is
> > > > > very likely we can ship a that bugfix also for Buster.
> > > > 
> > > > The other issue I have since 18.08 packages is:
> > > > 
> > > > Debian #921624: kmail: Crash during/after filtering inbox, probably
> > > > related to Qt WebEngine integration
> > > > https://bugs.debian.org/921624
> > > > 
> > > > Crash during/after filtering inbox, probably related to Qt WebEngine
> > > > integration
> > > > https://bugs.kde.org/404052
> > > 
> > > Filed another one (since 18.08):
> > > 
> > > KMail (in Kontact) crashing upon start or shortly after
> > > https://bugs.kde.org/405491
> > > 
> > > It might be related (or even duplicate) to #404052,
> > > only that I do not need to have mails filtered for
> > > KMail to crash. Looks like a QtWebEngine thing.
> > > 
> > > Just like Martin, I missed out on debug syms. Got them
> > > installed now and trying to get another backtrace.
> > > 
> > > > I can add more backtraces to the upstream bug report. For some reason
> > > > DrKonqi shortened the second backtrace I had it generate after fully
> > > > upgrading to 18.08.3-1.
> > > > 
> > > > At least this one produces a crash, instead of just stalling… for
> > > > whatever reason.
> > > > 
> > > > Thanks,

(Bye)²,

Christian

-- 



signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 18.08.3 for Buster

[Christian Hilberg]

Hi,

Am Freitag, 15. März 2019, 12:02:42 CET schrieb Andy G Wood:
> Hello,
> 
> I have also been suffering from infrequent kmail crashes in recent weeks. 
> It is not related to filtering, nor is it specific to nouveau (I use the
> NVIDIA proprietary display driver).

I'm seeing the issue with both, nouveau and (legacy 390) nvidia blob.
Currently running Kontact inside a VM instead, let's see what that does.

> Not currently reproducible ... and yes I need to install debug syms in order
> to provide more than a "me too".  The impact may be wider than kmail
> because I have also had one okular crash too.

Regarding wider impact, the traces I've seen so far point towards QtWebEngine,
so any app integrating this might be affected.

> Andy.
> 
> On Friday, 15 March 2019 09:55:10 GMT Christian Hilberg wrote:
> > Hi there,
> > 
> > Am Donnerstag, 7. Februar 2019, 13:20:00 CET schrieb Martin Steigerwald:
> > > Sandro Knauß - 07.02.19, 00:33:
> > > > Hey,
> > > > 
> > > > as Debian is already in freeze, the version of KDEPIM that will
> > > > shipped with the next stable is 18.08.3. That was uploaded same days
> > > > ago. There is no time to package 18.12.X sorry for that.
> > > > So please test this version in more depth and report issues. If you
> > > > also manage to point to existing bugfixes like done in #921535 it is
> > > > very likely we can ship a that bugfix also for Buster.
> > > 
> > > The other issue I have since 18.08 packages is:
> > > 
> > > Debian #921624: kmail: Crash during/after filtering inbox, probably
> > > related to Qt WebEngine integration
> > > https://bugs.debian.org/921624
> > > 
> > > Crash during/after filtering inbox, probably related to Qt WebEngine
> > > integration
> > > https://bugs.kde.org/404052
> > 
> > Filed another one (since 18.08):
> > 
> > KMail (in Kontact) crashing upon start or shortly after
> > https://bugs.kde.org/405491
> > 
> > It might be related (or even duplicate) to #404052,
> > only that I do not need to have mails filtered for
> > KMail to crash. Looks like a QtWebEngine thing.
> > 
> > Just like Martin, I missed out on debug syms. Got them
> > installed now and trying to get another backtrace.
> > 
> > > I can add more backtraces to the upstream bug report. For some reason
> > > DrKonqi shortened the second backtrace I had it generate after fully
> > > upgrading to 18.08.3-1.
> > > 
> > > At least this one produces a crash, instead of just stalling… for
> > > whatever reason.
> > > 
> > > Thanks,

(Bye)²,

Christian

-- 

Re: KDEPIM 18.08.3 for Buster

[Andy G Wood]

Hello,

I have also been suffering from infrequent kmail crashes in recent weeks.  It 
is not related to filtering, nor is it specific to nouveau (I use the NVIDIA 
proprietary display driver).
Not currently reproducible ... and yes I need to install debug syms in order 
to provide more than a "me too".  The impact may be wider than kmail because I 
have also had one okular crash too.

Andy.

On Friday, 15 March 2019 09:55:10 GMT Christian Hilberg wrote:
> Hi there,
> 
> Am Donnerstag, 7. Februar 2019, 13:20:00 CET schrieb Martin Steigerwald:
> > Sandro Knauß - 07.02.19, 00:33:
> > > Hey,
> > > 
> > > as Debian is already in freeze, the version of KDEPIM that will
> > > shipped with the next stable is 18.08.3. That was uploaded same days
> > > ago. There is no time to package 18.12.X sorry for that.
> > > So please test this version in more depth and report issues. If you
> > > also manage to point to existing bugfixes like done in #921535 it is
> > > very likely we can ship a that bugfix also for Buster.
> > 
> > The other issue I have since 18.08 packages is:
> > 
> > Debian #921624: kmail: Crash during/after filtering inbox, probably
> > related to Qt WebEngine integration
> > https://bugs.debian.org/921624
> > 
> > Crash during/after filtering inbox, probably related to Qt WebEngine
> > integration
> > https://bugs.kde.org/404052
> 
> Filed another one (since 18.08):
> 
> KMail (in Kontact) crashing upon start or shortly after
> https://bugs.kde.org/405491
> 
> It might be related (or even duplicate) to #404052,
> only that I do not need to have mails filtered for
> KMail to crash. Looks like a QtWebEngine thing.
> 
> Just like Martin, I missed out on debug syms. Got them
> installed now and trying to get another backtrace.
> 
> > I can add more backtraces to the upstream bug report. For some reason
> > DrKonqi shortened the second backtrace I had it generate after fully
> > upgrading to 18.08.3-1.
> > 
> > At least this one produces a crash, instead of just stalling… for
> > whatever reason.
> > 
> > Thanks,
> (Bye)²,
>   Christian

Re: KDEPIM 18.08.3 for Buster

[Christian Hilberg]

Hi there,

Am Donnerstag, 7. Februar 2019, 13:20:00 CET schrieb Martin Steigerwald:
> Sandro Knauß - 07.02.19, 00:33:
> > Hey,
> > 
> > as Debian is already in freeze, the version of KDEPIM that will
> > shipped with the next stable is 18.08.3. That was uploaded same days
> > ago. There is no time to package 18.12.X sorry for that.
> > So please test this version in more depth and report issues. If you
> > also manage to point to existing bugfixes like done in #921535 it is
> > very likely we can ship a that bugfix also for Buster.
> 
> The other issue I have since 18.08 packages is:
> 
> Debian #921624: kmail: Crash during/after filtering inbox, probably
> related to Qt WebEngine integration
> https://bugs.debian.org/921624
> 
> Crash during/after filtering inbox, probably related to Qt WebEngine
> integration
> https://bugs.kde.org/404052

Filed another one (since 18.08):

KMail (in Kontact) crashing upon start or shortly after
https://bugs.kde.org/405491

It might be related (or even duplicate) to #404052,
only that I do not need to have mails filtered for
KMail to crash. Looks like a QtWebEngine thing.

Just like Martin, I missed out on debug syms. Got them
installed now and trying to get another backtrace.

> I can add more backtraces to the upstream bug report. For some reason
> DrKonqi shortened the second backtrace I had it generate after fully
> upgrading to 18.08.3-1.
> 
> At least this one produces a crash, instead of just stalling… for
> whatever reason.
> 
> Thanks,

(Bye)²,

Christian

-- 

Re: KDEPIM 18.08.3 for Buster

[Martin Steigerwald]

Hi Libor.

Libor Klepáč - 07.02.19, 13:03:
> Hi,
> i'm using EWS without problems for some time (well - sometimes, i have to
> restart akonadi or it won't sync emails ...).
> I have attached my setup as screenshot. (I have autodiscovery disabled and
> use "user agent"="Outlook 2016" on other tab).
>
> You have to install package kmailtransport-akonadi to be able to send emails
> thru EWS.
> This package is not recommended by any other package so it is not installed
> by default.

Thanks for your help.

Akonadi EWS is working here too now, at least to some extent. There are some
interim failures at times but I am not sure whether they are Akonadi or Office
365 related.

--
Martin Steigerwald • Proact Deutschland GmbH
Trainer

Telefon: +49 911 30999 55 • Fax: +49 911 30999 99
Südwestpark 43 • 90449 Nürnberg • Germany
martin.steigerw...@proact.de • www.proact.de

Amtsgericht Nürnberg • HRB 18320
Geschäftsführer: Oliver Kügow • Richard Müller • Jakob Høholdt • Peter Mikael
Javestad



Mit freundlichen Grüßen / With kind regards
Martin Steigerwald •
Proact Deutschland GmbH
Trainer
Telefon: +49 911 30999 0 •
Fax: +49 911 30999 99
Südwestpark 43 •
90449 Nürnberg •
Germany
martin.steigerw...@proact.de •
www.proact.de
Amtsgericht Nürnberg
 •
HRB 18320
Geschäftsführer:
Oliver Kügow •
Richard Müller •
Jakob Høholdt
 •
Peter Mikael Javestad
– Delivering Business Agility –

Re: KDEPIM 18.08.3 for Buster

[Sandro Knauß]

Hey,

> Debian #921624: kmail: Crash during/after filtering inbox, probably
> related to Qt WebEngine integration
> https://bugs.debian.org/921624
> 
> Crash during/after filtering inbox, probably related to Qt WebEngine
> integration
> https://bugs.kde.org/404052
> 
> I can add more backtraces to the upstream bug report. For some reason
> DrKonqi shortened the second backtrace I had it generate after fully
> upgrading to 18.08.3-1.
> 
> At least this one produces a crash, instead of just stalling… for
> whatever reason.

Pelase add debug symbols for 
libKF5AkonadiCore.so.5abi2
KF5CoreAddons.so.5

otherwise the backtraces are not that helpful. 

hefee

signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 18.08.3 for Buster

[Martin Steigerwald]

Sandro Knauß - 07.02.19, 00:33:
> Hey,
> 
> as Debian is already in freeze, the version of KDEPIM that will
> shipped with the next stable is 18.08.3. That was uploaded same days
> ago. There is no time to package 18.12.X sorry for that.
> So please test this version in more depth and report issues. If you
> also manage to point to existing bugfixes like done in #921535 it is
> very likely we can ship a that bugfix also for Buster.

The other issue I have since 18.08 packages is:

Debian #921624: kmail: Crash during/after filtering inbox, probably 
related to Qt WebEngine integration
https://bugs.debian.org/921624

Crash during/after filtering inbox, probably related to Qt WebEngine 
integration
https://bugs.kde.org/404052

I can add more backtraces to the upstream bug report. For some reason 
DrKonqi shortened the second backtrace I had it generate after fully 
upgrading to 18.08.3-1.

At least this one produces a crash, instead of just stalling… for 
whatever reason.

Thanks,
-- 
Martin

Re: KDEPIM 18.08.3 for Buster

[Libor Klepáč]

Hi,
thanks for update.

Works ok, no problems. It took while to startup kontact on first run.

I still have problem with 100% CPU usage in kontact (and/or kmail).
It's using CPU even if i shutdown akonadi server.
I don't know how to debug. 
According to strace, it's pooling file descriptor 5 in loop, which is [eventfd].

[pid  2317] poll([{fd=5, events=POLLIN}, {fd=8, events=POLLIN}, {fd=56, 
events=POLLIN}, {fd=170, events=POLLIN}, {fd=174, events=POLLIN}, {fd=175, 
events=POLLIN}, {fd=176, events=POLLIN}, {fd=177, events=POLLPRI}, {fd=178, 
events=POLLIN}], 9, 0) = 1 ([{fd=5, revents=POLLIN}])
[pid  2317] read(5, "\1\0\0\0\0\0\0\0", 16) = 8
[pid  2317] write(5, "\1\0\0\0\0\0\0\0", 8) = 8
[pid  2317] poll([{fd=5, events=POLLIN}, {fd=8, events=POLLIN}, {fd=56, 
events=POLLIN}, {fd=170, events=POLLIN}, {fd=174, events=POLLIN}, {fd=175, 
events=POLLIN}, {fd=176, events=POLLIN}, {fd=177, events=POLLPRI}, {fd=178, 
events=POLLIN}], 9, 0) = 1 ([{fd=5, revents=POLLIN}])
[pid  2317] read(5, "\1\0\0\0\0\0\0\0", 16) = 8
[pid  2317] write(5, "\1\0\0\0\0\0\0\0", 8) = 8


Libor



On čtvrtek 7. února 2019 0:33:38 CET Sandro Knauß wrote:
> Hey,
> 
> as Debian is already in freeze, the version of KDEPIM that will shipped with
> the next stable is 18.08.3. That was uploaded same days ago. There is no
> time to package 18.12.X sorry for that.
> So please test this version in more depth and report issues. If you also
> manage to point to existing bugfixes like done in #921535 it is very likely
> we can ship a that bugfix also for Buster.
> 
> hefee

KDEPIM with Office 365 (was: Re: KDEPIM 18.08.3 for Buster)

[Martin Steigerwald]

Hi Libor.

Libor Klepáč - 07.02.19, 13:03:
> i'm using EWS without problems for some time (well - sometimes, i have
> to restart akonadi or it won't sync emails ...).

There is some bug report about that in upstream bug tracker. Unresolved 
so far.

> I have attached my setup as screenshot. (I have autodiscovery disabled
> and use "user agent"="Outlook 2016" on other tab).

Thank you very much. AFAIR on my various attempts I had it like this at 
least once. Well except for the user-agent setting. I will have a go 
with that next week and report back.

> You have to install package kmailtransport-akonadi to be able to send
> emails thru EWS.

It is installed here.

> This package is not recommended by any other package so it is not
> installed by default.

Thanks for letting me know.

Ciao,
-- 
Martin

Re: KDEPIM 18.08.3 for Buster

[Libor Klepáč]

Hi,
i'm using EWS without problems for some time (well - sometimes, i have to 
restart akonadi or it won't sync emails ...).
I have attached my setup as screenshot. (I have autodiscovery disabled and use 
"user agent"="Outlook 2016" on other tab).

You have to install package kmailtransport-akonadi to be able to send emails 
thru EWS.
This package is not recommended by any other package so it is not installed by 
default.

Libor


On čtvrtek 7. února 2019 11:10:21 CET you wrote:
> Hello Sandro.
> 
> Sandro Knauß - 07.02.19, 00:33:
> > as Debian is already in freeze, the version of KDEPIM that will
> > shipped with the next stable is 18.08.3. That was uploaded same days
> > ago. There is no time to package 18.12.X sorry for that.
> > So please test this version in more depth and report issues. If you
> > also manage to point to existing bugfixes like done in #921535 it is
> > very likely we can ship a that bugfix also for Buster.
> 
> While I had hoped for KDEPIM 18.12, I certainly accept and understand
> your decision.
> 
> I probably will test whether I can get Akonadi EWS with Office 365 – not
> my choice, mind you – to work for me with that version. So far I was not
> able to, but by triaging upstream reports I did not yet find one that
> applies to my situation. So maybe it is still a configuration issue on my
> side. Evolution with EWS just works fine, including calendar.
> 
> Aside from that since KDEPIM/Akonadi 18.08 I see stalls when downloading
> POP3 messages from my private Dovecot server. Often Akonadi/KMail just
> sits there, according to atop apparently doing nothing, for up to a
> minute, before continuing as if nothing has happened. That behavior has
> been so erratic, that I did not yet invest more time to actually find out
> what is going on here. Sometimes it works normally and sometimes I see
> those stalls. I was disappointed cause I expected the work of Daniel¹ to
> improve performance of KDEPIM/Akonadi quite a bit and did not have those
> delays with earlier KDEPIM/Akonadi. According to akonadictl fsck there
> are quite some issues with my setup… and I wonder whether to recreate it
> once again as akonadictl fsck does not seem to fix any of those. However…
> that would be something for upstream mailing list kdepim-users (where I
> raised this issue quite some time ago).
> 
> I know both upstream development and packaging it can use more hands. So
> I mean no offense to anybody with that.
> 
> [1] https://www.dvratil.cz/2018/04/my-kde-pim-update/
> 
> Thanks,



[1] mailto:libor.kle...@bcom.cz
[2] tel:+420377457676
[3] http://www.bcom.cz

Re: KDEPIM 18.08.3 for Buster

[Martin Steigerwald]

Hello Sandro.

Sandro Knauß - 07.02.19, 00:33:
> as Debian is already in freeze, the version of KDEPIM that will
> shipped with the next stable is 18.08.3. That was uploaded same days
> ago. There is no time to package 18.12.X sorry for that.
> So please test this version in more depth and report issues. If you
> also manage to point to existing bugfixes like done in #921535 it is
> very likely we can ship a that bugfix also for Buster.

While I had hoped for KDEPIM 18.12, I certainly accept and understand 
your decision.

I probably will test whether I can get Akonadi EWS with Office 365 – not 
my choice, mind you – to work for me with that version. So far I was not 
able to, but by triaging upstream reports I did not yet find one that 
applies to my situation. So maybe it is still a configuration issue on my 
side. Evolution with EWS just works fine, including calendar.

Aside from that since KDEPIM/Akonadi 18.08 I see stalls when downloading 
POP3 messages from my private Dovecot server. Often Akonadi/KMail just 
sits there, according to atop apparently doing nothing, for up to a 
minute, before continuing as if nothing has happened. That behavior has 
been so erratic, that I did not yet invest more time to actually find out 
what is going on here. Sometimes it works normally and sometimes I see 
those stalls. I was disappointed cause I expected the work of Daniel¹ to 
improve performance of KDEPIM/Akonadi quite a bit and did not have those 
delays with earlier KDEPIM/Akonadi. According to akonadictl fsck there 
are quite some issues with my setup… and I wonder whether to recreate it 
once again as akonadictl fsck does not seem to fix any of those. However… 
that would be something for upstream mailing list kdepim-users (where I 
raised this issue quite some time ago).

I know both upstream development and packaging it can use more hands. So 
I mean no offense to anybody with that.

[1] https://www.dvratil.cz/2018/04/my-kde-pim-update/

Thanks,
-- 
Martin

Re: KDEPIM broken after upgrades in Buster [Was: Re: KDEPIM 18.08 broken icons in Kontact application switcher toolbar]

[Sandro Knauß]

Hey,

yeah the automatic logic for migrations to testing fail on kdepim, because 
some archs do not built that fast only some packages have been build on all 
archs and those are migrating to testing without the rest of kdepim and as the 
packages in testing tell a minimal version and not a maximum some packages get 
updated and than things break. I hoped that with proper ABI bumps things get 
better. but it doesn't looks it is enough...

hefee

--
On Montag, 8. Oktober 2018 19:51:50 CEST Luigi Toscano wrote:
> /dev/fra ha scritto:
> > On 08/10/18 15:26:25 CEST, Brad Rogers wrote:
> >> On Sun, 07 Oct 2018 12:18:32 +0200
> >> 
> >> Martin Steigerwald  wrote:
> >>> Anyone else seeing this? I like to rule out an installation issue
> >>> before I report a bug.
> >> 
> >> Is this in testing?
> >> 
> >> Today, a few packages were upgraded to 18.08 from 17.2 in testing.  It
> >> broke several things, including korganiser & kaddressbook.  A quick look
> >> at packages.debian informs me that the 17.2 to 18.08 transition is far
> >> from complete, and thus likely to break things in testing for a while.
> > 
> > Sorry to hijack the thread, but indeed the upgrades of today broke the
> > entire KDEPIM I suppose, as not even Kmail was working afterwards.
> > 
> > These the relevant packages that have been installed and upgraded:
> > 
> > - installed
> > 
> >libkf5imap-data:amd64 (18.08.1-1, automatic)
> > 
> > - upgraded
> > 
> >libkf5kontactinterface5:amd64 (17.12.3-1, 18.08.1-1)
> >libkf5mime-data:amd64 (17.12.3-2, 18.08.1-1)
> >libkf5grantleetheme5:amd64 (17.12.3-1, 18.08.1-1)
> >libkf5grantleetheme-plugins:amd64 (17.12.3-1, 18.08.1-1)
> >libkf5imap5:amd64 (17.12.3-2, 18.08.1-1)
> >libkf5mime5abi1:amd64 (17.12.3-2, 18.08.1-1)
> >libkf5kontactinterface-data:amd64 (17.12.3-1, 18.08.1-1)
> >libkf5mbox5:amd64 (17.12.3-1, 18.08.1-1)
> > 
> > Uninstalling libkf5imap-data and downgrading back the other packages
> > solved
> > the problem for now.
> 
> Or just upgrade every KDEPIM package to 18.08 from sid.



signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM broken after upgrades in Buster [Was: Re: KDEPIM 18.08 broken icons in Kontact application switcher toolbar]

[Luigi Toscano]

/dev/fra ha scritto:

On 08/10/18 15:26:25 CEST, Brad Rogers wrote:

On Sun, 07 Oct 2018 12:18:32 +0200
Martin Steigerwald  wrote:

Anyone else seeing this? I like to rule out an installation issue
before I report a bug.


Is this in testing?

Today, a few packages were upgraded to 18.08 from 17.2 in testing.  It
broke several things, including korganiser & kaddressbook.  A quick look
at packages.debian informs me that the 17.2 to 18.08 transition is far
from complete, and thus likely to break things in testing for a while.


Sorry to hijack the thread, but indeed the upgrades of today broke the entire
KDEPIM I suppose, as not even Kmail was working afterwards.

These the relevant packages that have been installed and upgraded:

- installed
   libkf5imap-data:amd64 (18.08.1-1, automatic)

- upgraded
   libkf5kontactinterface5:amd64 (17.12.3-1, 18.08.1-1)
   libkf5mime-data:amd64 (17.12.3-2, 18.08.1-1)
   libkf5grantleetheme5:amd64 (17.12.3-1, 18.08.1-1)
   libkf5grantleetheme-plugins:amd64 (17.12.3-1, 18.08.1-1)
   libkf5imap5:amd64 (17.12.3-2, 18.08.1-1)
   libkf5mime5abi1:amd64 (17.12.3-2, 18.08.1-1)
   libkf5kontactinterface-data:amd64 (17.12.3-1, 18.08.1-1)
   libkf5mbox5:amd64 (17.12.3-1, 18.08.1-1)

Uninstalling libkf5imap-data and downgrading back the other packages solved
the problem for now.



Or just upgrade every KDEPIM package to 18.08 from sid.

--
Luigi

KDEPIM broken after upgrades in Buster [Was: Re: KDEPIM 18.08 broken icons in Kontact application switcher toolbar]

[/dev/fra]

On 08/10/18 15:26:25 CEST, Brad Rogers wrote:
> On Sun, 07 Oct 2018 12:18:32 +0200
> Martin Steigerwald  wrote:
> >Anyone else seeing this? I like to rule out an installation issue
> >before I report a bug.
> 
> Is this in testing?
> 
> Today, a few packages were upgraded to 18.08 from 17.2 in testing.  It
> broke several things, including korganiser & kaddressbook.  A quick look
> at packages.debian informs me that the 17.2 to 18.08 transition is far
> from complete, and thus likely to break things in testing for a while.

Sorry to hijack the thread, but indeed the upgrades of today broke the entire 
KDEPIM I suppose, as not even Kmail was working afterwards.

These the relevant packages that have been installed and upgraded:

- installed
  libkf5imap-data:amd64 (18.08.1-1, automatic)

- upgraded
  libkf5kontactinterface5:amd64 (17.12.3-1, 18.08.1-1)
  libkf5mime-data:amd64 (17.12.3-2, 18.08.1-1)
  libkf5grantleetheme5:amd64 (17.12.3-1, 18.08.1-1)
  libkf5grantleetheme-plugins:amd64 (17.12.3-1, 18.08.1-1)
  libkf5imap5:amd64 (17.12.3-2, 18.08.1-1)
  libkf5mime5abi1:amd64 (17.12.3-2, 18.08.1-1)
  libkf5kontactinterface-data:amd64 (17.12.3-1, 18.08.1-1)
  libkf5mbox5:amd64 (17.12.3-1, 18.08.1-1)

Uninstalling libkf5imap-data and downgrading back the other packages solved 
the problem for now.

Cheers

Re: KDEPIM 18.08 broken icons in Kontact application switcher toolbar

[Brad Rogers]

On Sun, 07 Oct 2018 12:18:32 +0200
Martin Steigerwald  wrote:

Hello Martin,

>Anyone else seeing this? I like to rule out an installation issue
>before I report a bug.

Is this in testing?

Today, a few packages were upgraded to 18.08 from 17.2 in testing.  It
broke several things, including korganiser & kaddressbook.  A quick look
at packages.debian informs me that the 17.2 to 18.08 transition is far
from complete, and thus likely to break things in testing for a while.

That said, I can't help with your original question about kontact as
that's one part of kdepim I don't use.  Sorry.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
When I say ugly, I don't mean rough looking, I mean hideous
Ugly - The Stranglers


pgp6IA6E__yzE.pgp
Description: OpenPGP digital signature

Re: kdepim 18.08.1 entering unstable

[Libor Klepáč]

On neděle 7. října 2018 0:42:29 CEST Martin Steigerwald wrote:
> Libor Klepáč - 06.10.18, 19:32:
> > On sobota 6. října 2018 11:49:26 CEST Martin Steigerwald wrote:
> > > Martin Steigerwald - 06.10.18, 11:09:
> […]
> 
> > > One minor thing I found: I now have that sidebar telling me whether
> > > it is a HTML message or not. I think I made it to be gone before,
> > > but did not find that option anymore. I remember having seen a bug
> > > report about this.
> > > 
> > > Anyway, that is clearly an upstream issue.
> > 
> > my kmail shows this sidebar without problems in new version
> 
> Sure it does.
> 
> But I prefer it not to be there.
> 
> Thanks,

Hi,
sorry, i did read your email other way around.


Libor

Re: KDEPIM 18.08 broken icons in Kontact application switcher toolbar

[local10]

Oct 7, 2018, 6:18 AM by mar...@lichtvoll.de:

> Work-around: Switch to text instead of symbols.
>
> Anyone else seeing this? I like to rule out an installation issue before 
> I report a bug.
>

I'm experiencing an issue with disappearing icons in the Application Menu 
launcher. Maybe it's related to the issue you have, maybe not. Some icons in 
the Power / Session menu have disappeared (e.g. Switch user, Suspend, 
Hibernate, Reboot) yet some are still there (Lock, Logout, Shutdown). I think 
it happened after I removed from and and added to the favorites some of the 
Power / Session menu items.

Also, the KDE icon in the Application Launcher (not to be confused with the 
Application Menu launcher) has absolutely ridiculous size when used with used a 
vertical taskbar (I tried it with the vertical taskbar width of about 8-10% of 
the screen width). Had to switch to the Application Menu launcher because of 
that.

Regards,

Re: kdepim 18.08.1 entering unstable

[Sune Vuorela]

On 2018-10-06, Martin Steigerwald  wrote:
> One minor thing I found: I now have that sidebar telling me whether it 
> is a HTML message or not. I think I made it to be gone before, but did 
> not find that option anymore. I remember having seen a bug report about 
> this.

IIRC it was an active decision in some of the EFAIL mitigations to be
more clear about what was html mails and what wasn't.

/Sune

Re: kdepim 18.08.1 entering unstable

[Martin Steigerwald]

Martin Steigerwald - 06.10.18, 11:09:
> Martin Steigerwald - 03.10.18, 08:16:
> > Since I use kmymoney quite often meanwhile, I will likely wait till
> > it all fits together before I upgrade.
> 
> What gives. I can do without KMyMoney for a while, so I just upgraded.

Pino uploaded kmymoney 5.0.1-3 which works with KDEPIM/Akonadi 18.08 
packages. Thank you.

Thanks,
-- 
Martin

Re: kdepim 18.08.1 entering unstable

[Martin Steigerwald]

Libor Klepáč - 06.10.18, 19:32:
> On sobota 6. října 2018 11:49:26 CEST Martin Steigerwald wrote:
> > Martin Steigerwald - 06.10.18, 11:09:
[…]
> > One minor thing I found: I now have that sidebar telling me whether
> > it is a HTML message or not. I think I made it to be gone before,
> > but did not find that option anymore. I remember having seen a bug
> > report about this.
> > 
> > Anyway, that is clearly an upstream issue.
>
> my kmail shows this sidebar without problems in new version

Sure it does.

But I prefer it not to be there.

Thanks,
-- 
Martin

Re: kdepim 18.08.1 entering unstable

[Libor Klepáč]

Hi, 
my kmail shows this sidebar without problems in new version

Libor


On sobota 6. října 2018 11:49:26 CEST Martin Steigerwald wrote:
> Martin Steigerwald - 06.10.18, 11:09:
> > Martin Steigerwald - 03.10.18, 08:16:
> > > Since I use kmymoney quite often meanwhile, I will likely wait till
> > > it all fits together before I upgrade.
> > 
> > What gives. I can do without KMyMoney for a while, so I just upgraded.
> > 
> > All well so far. :)
> 
> One minor thing I found: I now have that sidebar telling me whether it
> is a HTML message or not. I think I made it to be gone before, but did
> not find that option anymore. I remember having seen a bug report about
> this.
> 
> Anyway, that is clearly an upstream issue.
> 
> Thanks,

Re: kdepim 18.08.1 entering unstable

[Martin Steigerwald]

Martin Steigerwald - 06.10.18, 11:09:
> Martin Steigerwald - 03.10.18, 08:16:
> > Since I use kmymoney quite often meanwhile, I will likely wait till
> > it all fits together before I upgrade.
> 
> What gives. I can do without KMyMoney for a while, so I just upgraded.
> 
> All well so far. :)

One minor thing I found: I now have that sidebar telling me whether it 
is a HTML message or not. I think I made it to be gone before, but did 
not find that option anymore. I remember having seen a bug report about 
this.

Anyway, that is clearly an upstream issue.

Thanks,
-- 
Martin

Re: kdepim 18.08.1 entering unstable

[Martin Steigerwald]

Martin Steigerwald - 03.10.18, 08:16:
> Since I use kmymoney quite often meanwhile, I will likely wait till it
> all fits together before I upgrade.

What gives. I can do without KMyMoney for a while, so I just upgraded.

All well so far. :)

Thanks again.

Ciao,
-- 
Martin

Re: kdepim 18.08.1 entering unstable

[Libor Klepáč]

Hi,
just upgraded, everything seems to be ok, thank you very much.

I had problem before, kontact was eating 100% cpu, it is still eating 100% 
after upgrade.

It's polling FD=5
poll([{fd=5, events=POLLIN}, {fd=8, events=POLLIN}, {fd=341, events=POLLIN}, 
{fd=397, events=POLLIN}, {fd=436, events=POLLIN}, {fd=445, events=POLLIN}, 
{fd=447, events=POLLIN}, {fd=449, events=POLLIN}, {fd=451, events=POLLIN}, 
{fd=452, events=POLLIN}, {fd=456, events=POLLIN}, {fd=458, events=POLLIN}, 
{fd=459, events=POLLIN},

which is something called [eventfd]


Libor



On středa 3. října 2018 0:15:21 CEST Sandro Knauß wrote:
> Hey,
> 
> I uploaded kdepim 18.08.1 to unstable some minutes ago. I tested it for
> around 15 days, without any issues. It may take some days till the dust
> will settle. It is additionally known, that ktorrent, kio-gdrive, blogilo,
> kjots, zanshin, digikam, kraft and kmymoney needs to be recompiled against
> kdepim 18.08. This will done within the transition #909288.
> 
> kmymoney in experimental will get an update within the next days and should
> be working with new kdepim afterwards.
> 
> hefee



[1] mailto:libor.kle...@bcom.cz
[2] tel:+420377457676
[3] http://www.bcom.cz

Re: kdepim 18.08.1 entering unstable

[Martin Steigerwald]

Hey Sandro.

Sandro Knauß - 03.10.18, 00:15:
> I uploaded kdepim 18.08.1 to unstable some minutes ago. I tested it
> for around 15 days, without any issues. It may take some days till
> the dust will settle. It is additionally known, that ktorrent,
> kio-gdrive, blogilo, kjots, zanshin, digikam, kraft and kmymoney
> needs to be recompiled against kdepim 18.08. This will done within
> the transition #909288.
> 
> kmymoney in experimental will get an update within the next days and
> should be working with new kdepim afterwards.

Yes, I rejoiced as I saw it coming in debian-devel-changes mailinglist.

Thank you very much for this complex packaging work.

I am looking forward to check out the performance improvements due to 
the notification payload work by Daniel. And all the other improvements 
since 17.12.

Any interested in a summary of the of major changes can check out (under 
"Office"):

https://www.kde.org/announcements/announce-applications-18.08.0.php

https://www.kde.org/announcements/announce-applications-18.04.0.php


Since I use kmymoney quite often meanwhile, I will likely wait till it 
all fits together before I upgrade.


I bet 18.08.something will be the version of KDEPIM + Akonadi for 
Buster, as 18.12 would be rather tight before the transition freeze¹.

[1] https://release.debian.org/buster/freeze_policy.html

Thanks,
-- 
Martin

Re: KDEPIM 17.12: pane that show message structure missing?

[Rob Brewer]

Diederik de Haas wrote:

> The following was posted to debian-qt-kde ML, I assume by accident:
> 
> Use Settings, Configure Toolbar,
> Move Show Message Structure
> 
> Reinhard

Yes that adds a "Show Massage Structure" item to the Main Toolbar from where 
I can toggle the lower pane on and off.  

Many Thanks

Rob

Re: KDEPIM 17.12: pane that show message structure missing?

[David Goodenough]

On Thursday, 12 April 2018 08:33:43 BST Martin Steigerwald wrote:
> Hello.
> 
> With KDEPIM prior 17.12 I always had a pane that shows the message
> structure where I could select which part of the message to view in the
> message content display area. So with messages that are both available
> as text and HTML I could select which one to view.
> 
> This is gone since KDEPIM 17.12 and I found no way to enable it again. I
> remember there was an option but I digged through all menus and
> configuration options three times without finding it.
> 
> Any idea?
> 
> Thanks,
Try Folder->Message Default Format

David

Re: KDEPIM 17.12: pane that show message structure missing?

[Diederik de Haas]

On donderdag 12 april 2018 12:11:43 CEST Rob Brewer wrote:
> Thanks Xavier, but I have the same problem as Martin, but I can't find the
> option you suggested. The third menu here is "View" but I can't see any item
> that relates to "affichage" which is presumably "Display" in english.
> 
> kdepim Version: 4:17.12.3+5.101

The following was posted to debian-qt-kde ML, I assume by accident:

Use Settings, Configure Toolbar,
Move Show Message Structure

Reinhard


signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 17.12: pane that show message structure missing?

[Rob Brewer]

Xavier Brochard wrote:

> Le jeudi 12 avril 2018, 09:33:43 CEST Martin Steigerwald a écrit :
>> Hello.
>> 
>> With KDEPIM prior 17.12 I always had a pane that shows the message
>> structure where I could select which part of the message to view in the
>> message content display area. So with messages that are both available
>> as text and HTML I could select which one to view.
>> 
>> This is gone since KDEPIM 17.12 and I found no way to enable it again. I
>> remember there was an option but I digged through all menus and
>> configuration options three times without finding it.
>> 
>> Any idea?
>> 
> 
> The option is in the "display" or "show" menu (third menu). I don't know
> the exact name, but in french it is "affichage"
> 

Thanks Xavier, but I have the same problem as Martin, but I can't find the 
option you suggested. The third menu here is "View" but I can't see any item 
that relates to "affichage" which is presumably "Display" in english.

kdepim Version: 4:17.12.3+5.101


Rob

Re: KDEPIM 17.12: pane that show message structure missing?

[Xavier Brochard]

Le jeudi 12 avril 2018, 09:33:43 CEST Martin Steigerwald a écrit :
> Hello.
> 
> With KDEPIM prior 17.12 I always had a pane that shows the message
> structure where I could select which part of the message to view in the
> message content display area. So with messages that are both available
> as text and HTML I could select which one to view.
> 
> This is gone since KDEPIM 17.12 and I found no way to enable it again. I
> remember there was an option but I digged through all menus and
> configuration options three times without finding it.
> 
> Any idea?
> 

The option is in the "display" or "show" menu (third menu). I don't know the 
exact name, but in french it is "affichage"

-- 
Librement,
Xavier Brochard - 07 68 13 14 35
« La liberté est à l'homme ce que les ailes sont à l'oiseau »
(Jean-Pierre Rosnay)

Re: KDEPIM 17.12: pane that show message structure missing?

[Martin Steigerwald]

Reinhard Karcher - 12.04.18, 10:04:
> Am Thursday, 12 April 2018, 09:33:43 CEST schrieb Martin Steigerwald:
> > With KDEPIM prior 17.12 I always had a pane that shows the message
> > structure where I could select which part of the message to view in
> > the message content display area. So with messages that are both
> > available as text and HTML I could select which one to view.
> > 
> > This is gone since KDEPIM 17.12 and I found no way to enable it
> > again. I remember there was an option but I digged through all
> > menus and configuration options three times without finding it.
> > 
> > Any idea?
> > 
> > Thanks,
> 
> Use Settings, Configure Toolbar,
> Move Show Message Structure

Thank you Reinhard. Wonderful. So I disable show HTML by default again.

-- 
Martin

Re: KDEPIM 17.12: pane that show message structure missing?

[Reinhard Karcher]

Am Thursday, 12 April 2018, 09:33:43 CEST schrieb Martin Steigerwald:
> Hello.
> 
> With KDEPIM prior 17.12 I always had a pane that shows the message
> structure where I could select which part of the message to view in the
> message content display area. So with messages that are both available
> as text and HTML I could select which one to view.
> 
> This is gone since KDEPIM 17.12 and I found no way to enable it again. I
> remember there was an option but I digged through all menus and
> configuration options three times without finding it.
> 
> Any idea?
> 
> Thanks,

Use Settings, Configure Toolbar,
Move Show Message Structure

Reinhard

Re: kdepim 17.12.3 entering unstable

[Klaus Becker]

Le jeudi 5 avril 2018, 19:38:25 CEST Sandro Knauß a écrit :
> Hey,
> 
> > > > # akonadictl restart
> > > > D-Bus session bus is not available!
> > > > Abandon
> > > 
> > > You tried to restart it as root? Both setup the qtlogging.ini and
> > > restart
> > > Akonadi needs to be done as normal user NOT as root.
> > 
> > But there is still the issue above about deleted messages.
> 
> "D-Bus session bus is not available!" indicate, that D-Bus is not running,
> this can't be because the communication between Kmail and Akonadi using
> D-Bus. This normally means you are running "akonadictl restart" as root or
> from a termial (Alt+Ctrl+F1) and not within your X-user session.
> 
> But you need to run it as login user.

I understood :-)

Klaus

> 
> hefee

Re: kdepim 17.12.3 entering unstable

[Sandro Knauß]

Hey,

> > > # akonadictl restart
> > > D-Bus session bus is not available!
> > > Abandon
> > 
> > You tried to restart it as root? Both setup the qtlogging.ini and restart
> > Akonadi needs to be done as normal user NOT as root.
 
> But there is still the issue above about deleted messages.

"D-Bus session bus is not available!" indicate, that D-Bus is not running, 
this can't be because the communication between Kmail and Akonadi using D-Bus. 
This normally means you are running "akonadictl restart" as root or from a 
termial (Alt+Ctrl+F1) and not within your X-user session.

But you need to run it as login user.

hefee


signature.asc
Description: This is a digitally signed message part.

Re: kdepim 17.12.3 entering unstable

[Klaus Becker]

Le jeudi 5 avril 2018, 12:09:06 CEST Sandro Knauß a écrit :
> Hey,
> 
> > Can there be a relation with graphic card driver ?
> > 
> > I have 01:00.0 VGA compatible controller: NVIDIA Corporation GT218
> > [GeForce
> > 210] (rev a2) and I used nouveau.
> > 
> > There are 2-3 days, I installed xserver-xorg-video-nvidia-legacy-304xx and
> > kmail became more stable.
> > 
> > Yesterday I uninstalled xserver-xorg-video-nvidia-legacy-304xx and I have
> > again the same problems as befor.
> 
> sounds very likely. as the mailviewer using QtWebEngine for displaying
> mails. and QtWebEngine is using OpenGl etc
> 
> > > > But when I delete messages, they still appear in the list, and when I
> > > > delete them twice, they become grey in the liste.
> > > > 
> > > > To make them disappear, I have to click on another folder and then
> > > > return
> > > > to the incoming folder.
> > > 
> > > do you use imap or pop? It sounds like the akonadi resource can't handle
> > > the requests within time...
> > 
> > I use pop
> > 
> > > and than restart akonadi (akonadictl restart) and you see the debug log
> > > in
> > > the konsole.
> > 
> > # akonadictl restart
> > D-Bus session bus is not available!
> > Abandon
> 
> You tried to restart it as root? Both setup the qtlogging.ini and restart
> Akonadi needs to be done as normal user NOT as root.
> 
> hefee


I did it as user, but kmail still crashes.

So I reinstalled xserver-xorg-video-nvidia-legacy-340xx, I rebooted and kmail 
crashes no more.

But there is still the issue above about deleted messages.

Bye

Klaus

Re: kdepim 17.12.3 entering unstable

[Sandro Knauß]

Hey,

> Can there be a relation with graphic card driver ?
> 
> I have 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce
> 210] (rev a2) and I used nouveau.
> 
> There are 2-3 days, I installed xserver-xorg-video-nvidia-legacy-304xx and
> kmail became more stable.
> 
> Yesterday I uninstalled xserver-xorg-video-nvidia-legacy-304xx and I have
> again the same problems as befor.

sounds very likely. as the mailviewer using QtWebEngine for displaying mails. 
and QtWebEngine is using OpenGl etc
 
> > > But when I delete messages, they still appear in the list, and when I
> > > delete them twice, they become grey in the liste.
> > > 
> > > To make them disappear, I have to click on another folder and then
> > > return
> > > to the incoming folder.
> > 
> > do you use imap or pop? It sounds like the akonadi resource can't handle
> > the requests within time...
> 
> I use pop

> > and than restart akonadi (akonadictl restart) and you see the debug log in
> > the konsole.
> 
> # akonadictl restart
> D-Bus session bus is not available!
> Abandon

You tried to restart it as root? Both setup the qtlogging.ini and restart 
Akonadi needs to be done as normal user NOT as root.

hefee

signature.asc
Description: This is a digitally signed message part.

Re: kdepim 17.12.3 entering unstable

[Sandro Knauß]

Hey,

> Since 2-3 days, kmail in unstable is much less "unstable". Before it was
> crashing very often, now it crashes no more. I appreciate a lot.

what exactly was crashing?

> But when I delete messages, they still appear in the list, and when I delete
> them twice, they become grey in the liste.
> 
> To make them disappear, I have to click on another folder and then return to
> the incoming folder.

do you use imap or pop? It sounds like the akonadi resource can't handle the 
requests within time...

For all if you face issues with KDE Pim, the first thing you should consider 
is to enable debug logging, so we have a better overview what is going on. To 
get debug logging you need to create/modify the file 
~/.config/QtProject/qtlogging.ini with following content:

[Rules]
*.warning=true
*.critical=true

*=true

qt.*=false
sonnet.*=false

and than restart akonadi (akonadictl restart) and you see the debug log in the 
konsole.

Keep in mind to remove the file again / or change *=true to *=false 
afterwards, otherwise your .xsession-errors will fill up with all the output.

hefee

signature.asc
Description: This is a digitally signed message part.

Re: kdepim 17.12.3 entering unstable

[Sandro Knauß]

Hey,

> Thank you for the greet work you do.
> Since this update i have a problem with Kmail or akonadi, when i write a
> message i obtain an orange warning in French "Dossier des messages envoyés
> non défini. Veuillez le vérifier avant d'envoyer le message " I translate
> like this " File of the sent messages not defined. Please verify him before
> sending the message"  or an File "Sent-mail " exist and contains all my
> send messages , I don't know how configure this file?

Well you should check for the sent folder setting for the identity:
Settings->Identitiy->"select identity"->Modify->Advanced->Sent-mail folder

> Another problem not new wiith this update.
> Kontact crash at session end and also at the start of the session.

This should be fixed with 18.04. it is not a big issue, it is just that 
kontact tried to delete things two times and fails obviously at the second 
run.

hefee


signature.asc
Description: This is a digitally signed message part.

Re: kdepim 17.12.3 entering unstable

[Klaus Becker]

Le mercredi 4 avril 2018, 17:59:21 CEST MERLIN Philippe a écrit :
> Le samedi 31 mars 2018, 23:11:04 CEST Sandro Knauß a écrit :
> > Hey,
> 
> Thank you for the greet work you do.
> Since this update i have a problem with Kmail or akonadi, when i write a
> message i obtain an orange warning in French "Dossier des messages envoyés
> non défini. Veuillez le vérifier avant d'envoyer le message " I translate
> like this " File of the sent messages not defined. Please verify him before
> sending the message"  or an File "Sent-mail " exist and contains all my
> send messages , I don't know how configure this file?
> May you help me.
> Another problem not new wiith this update.
> Kontact crash at session end and also at the start of the session.
> Thank you.
> Philippe Merlin

Hi,

Since 2-3 days, kmail in unstable is much less "unstable". Before it was 
crashing very often, now it crashes no more. I appreciate a lot.

But when I delete messages, they still appear in the list, and when I delete 
them twice, they become grey in the liste.

To make them disappear, I have to click on another folder and then return to 
the incoming folder.

Bye

Klaus

Re: kdepim 17.12.3 entering unstable

[MERLIN Philippe]

Le samedi 31 mars 2018, 23:11:04 CEST Sandro Knauß a écrit :
> Hey,
> 
Thank you for the greet work you do.
Since this update i have a problem with Kmail or akonadi, when i write a 
message i obtain an orange warning in French "Dossier des messages envoyés non 
défini. Veuillez le vérifier avant d'envoyer le message " I translate like 
this " File of the sent messages not defined. Please verify him before sending 
the message"  or an File "Sent-mail " exist and contains all my send messages 
, I don't know how configure this file?
May you help me.
Another problem not new wiith this update.
Kontact crash at session end and also at the start of the session.
Thank you.
Philippe Merlin

Re: kdepim 17.12.3 entering unstable

[Libor Klepáč]

Hi,
thanks for all packages. I have used it also in experimental, everything is 
ok.
I was able to switch from self-compiled akonadi-ews to one included in this 
new kdepim packages.
But i was still missing EWS based send account.

This problem can be fixed by installing kmailtransport-akonadi, 
so maybe kdepim-runtime should recommend this package.





On sobota 31. března 2018 23:11:04 CEST Sandro Knauß wrote:
> Hey,
> 
> I now started to upload kdepim 17.12.3 to unstable. It will take some days
> till the dust will settle.  It is known, that kjots, digikam, zanshin and do
> not play nicely toget with kdepim 17.12 and need to recompiled. This will
> done within the transition #94342.
> 
> kmymoney in experimental will get an update within the next days and should
> be working with new kdepim afterwards.
> 
> Unfortunately you need to say goodbye to blogilo, it was moved to
> unmaintained by upstream and it does not build anymore with kdepim 17.12.
> If anyone wants to step up for the mantainership...
> 
> Additionally libkolab will be removed, too. Kolab do not ship updates
> anymore, that's why kdepim now add a copy of libkolab inide kdepim-runtime.
> So you don't loose support for your kolab accounts - but do not need
> libkolab anymore.
> 
> hefee

Processed: Re: kdepim-addons: File conflict with akonadi-contacts-data 4:17.08.3-2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #894587 [src:kdepim-addons] kdepim-addons: File conflict with 
akonadi-contacts-data 4:17.08.3-2
Added tag(s) patch.

-- 
894587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: kdepim 17.12.3 entering unstable

[Martin Steigerwald]

Hey Sandro.

Sandro Knauß - 31.03.18, 23:11:
> I now started to upload kdepim 17.12.3 to unstable. It will take some days
> till the dust will settle.  It is known, that kjots, digikam, zanshin and do
> not play nicely toget with kdepim 17.12 and need to recompiled. This will
> done within the transition #94342.
> 
> kmymoney in experimental will get an update within the next days and should
> be working with new kdepim afterwards.

Thank you very much, Sandro.

Successfully installed KDEPIM while keeping both kmymoney and digikam. So nice 
that the composer in KMail always in rich text edit mode bug is gone.

kde-full metapackage has been uninstalled, but you uploaded an uploaded for 
that already. So unless one uses Zanshin, I think one can upgrade safely. And 
reinstall kde-full package once the updated version is available.

Of course, always look what apt tells you. :)

Thanks,
-- 
Martin

Re: KDEPIM 17.08: The whole thing works

[Libor Klepáč]

Hi,

On středa 22. listopadu 2017 16:31:21 CET Sandro Knauß wrote:
> Hey,
> 
> > I find using aptitude easier for upgrades.
> > I just choose some major package like kdepim or kontact or kmail for 
upgrade
> > and then jump over broken packages with "b" until everything is ok, then
> > press "g" for list of upgraded and not upgaded packages and skim thru not
> > upgraded for any forgoten packages.
> 
> that sounds like a lot of clicky-clicky :) 
> apt install -t experimental kontact finds a solution that works. Without 
> manually to solve broken packages.
> Okay finding packages that could/should be updated to is not that easy.
>  
Yeah, but it's my morning ritual ;) (and i'm little old-fashioned and like to 
choose upgrades by hand)
And i don't upgrade everything to experimental, for example i was waiting for 
long time for Mesa and libva2.

> > Btw. is there a plan for newer versions of kdepim?
> 
> as always for Debian - it is ready when it is ready - as you see in other 
mail 
> thread - pino already started to package 17.08.3 and uploading to unstable.
> 
Sorry i missed that, thanks (i'm not trying to push anyone to making new 
packages)

> > I have problem with akonadi-ews , unable to send it's emails, which should
> > already be fixed in 17.08.0, but i'm still unable to send emails (I 
noticed
> > it after 4 days, with over 20 work emails in my outgoing folder ...)
> > https://github.com/KrissN/akonadi-ews/issues/35
> 
> github is not the official channel to communicate with kde software. You 
> should use bugs.kde.org for this. Just a small subset of KDE developers care 
> about github...
It's not my bug report ;) 
And author of akonadi-ews says here, that everything is working for him with 
newest kdepim (that's reason of my question on newer kdepim packages) - i have 
reverted to using SMTP for now.

> 
> Best Regards,
> 
> hefee
> 

Thanks,
Libor

Re: KDEPIM 17.08: The whole thing works

[Sandro Knauß]

Hey,

> I find using aptitude easier for upgrades.
> I just choose some major package like kdepim or kontact or kmail for upgrade
> and then jump over broken packages with "b" until everything is ok, then
> press "g" for list of upgraded and not upgaded packages and skim thru not
> upgraded for any forgoten packages.

that sounds like a lot of clicky-clicky :) 
apt install -t experimental kontact finds a solution that works. Without 
manually to solve broken packages.
Okay finding packages that could/should be updated to is not that easy.
 
> Btw. is there a plan for newer versions of kdepim?

as always for Debian - it is ready when it is ready - as you see in other mail 
thread - pino already started to package 17.08.3 and uploading to unstable.

> I have problem with akonadi-ews , unable to send it's emails, which should
> already be fixed in 17.08.0, but i'm still unable to send emails (I noticed
> it after 4 days, with over 20 work emails in my outgoing folder ...)
> https://github.com/KrissN/akonadi-ews/issues/35

github is not the official channel to communicate with kde software. You 
should use bugs.kde.org for this. Just a small subset of KDE developers care 
about github...

Best Regards,

hefee


signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 17.08: The whole thing works

[Libor Klepáč]

Hi,
it works,hurray ;) 

I find using aptitude easier for upgrades.
I just choose some major package like kdepim or kontact or kmail for upgrade 
and then jump over broken packages with "b" until everything is ok, then press 
"g" for list of upgraded and not upgaded packages and skim thru not upgraded 
for any forgoten packages.

After upgrade akonadi started it's db upgrade, but my FS became full, i 
noticed it after day of my disk LED constantly blinking.

Maybe some warning/news in akonadi package should be in place? (about resource 
heavy upgrade of DB)

So big thanks to maintainers for fresh packages.

Btw. is there a plan for newer versions of kdepim? 
I have problem with akonadi-ews , unable to send it's emails, which should 
already be fixed in 17.08.0, but i'm still unable to send emails (I noticed it 
after 4 days, with over 20 work emails in my outgoing folder ...)
https://github.com/KrissN/akonadi-ews/issues/35


Libor

On pátek 17. listopadu 2017 0:01:45 CET Martin Steigerwald wrote:
> Hello.
> 
> Okay, so I installed Akonadi + KDEPIM 17.08 and the whole things works.
> 
> I had some issues tough.
> 
> What did I do?
> 
> 1. apt install -t experimental kmail – kdewebdev got removed, it appears
> it needs an update. Also kdepim related kio plugins got removed, maybe
> thats intentional.
> 
> 2. Rebooted and started KMail. Akonadi produced lots of database load
> and after a while KMail complained it would not start. Akonadi was indeed
> not running only
> 
> 3. I then looked for old 16.04 packages and did the following:
> 
> apt install -t experimental libkf5akonadisearch-data 
libkf5akonadisearchxapian5 libkf5akonadinotes5 libkf5akonadisearchcore5
> 
> apt install -t experimental libkf5libkdepim-plugins:amd64
> 
> apt purge kf5-kdepimlibs-kio-plugins kdepimlibs-data
> 
> (old transitional packages)
> 
> 4. I logged out and in again, making sure that all processes of the user are 
gone.
> 
> 5. Again Akonadi stopped after a while, complaining it could not find MySQL
> socket file, I did not look much closer, MySQL was running initially just
> fine and there has been quite some MySQL load.
> 
> 6. But this time KMail offered to start Akonadi again, which I did
> 
> 7. Then KMail said that Akonadi is updating the database to improve
> performance.
> 
> 8. It took about 15 minutes or so.
> 
> 9. KAlarm asked about upgrading archived alarms to a new format.
> 
> 
> I was able to read news feeds in Akregator during the upgrade. Akgregator
> is still not Akonadi based. But well whatever the reported crash on start
> bug is about, I did not see it.
> 
> 
> Thats for now. Time to sleep.
> 
> Now let´s see whether it sends this mail :)
> 
> Thanks,
> 



[1] mailto:libor.kle...@bcom.cz
[2] tel:+420377457676
[3] http://www.bcom.cz

Re: Akonadi database (war: Re: KDEPIM 17.08: The whole thing works)

[Frank Mehnert]

On Freitag, 17. November 2017 16:11:39 CET Martin Steigerwald wrote:
> Martin Steigerwald - 17.11.17, 11:27:
> > However all of that is nothing that makes sense to discuss here – as that
> > are upstream matters. You may try to discuss this with upstream
> > developers,
> > but be prepared that they may not like the database or not discussion once
> > again. This is really a question that I have seen *a ton of times* in
> > various places. This is a touchy subject with upstream developers I think.
> > 
> > I kindly ask you to drop the discussion on this matter here, as it would
> > just be a waste of time here on this list. Thank you.
> > 
> > Even if you go on… I may not reply anymore – I took a lot of time for this
> > detailed reply already. See kdepim-users and kde-pim upstream mailing
> > lists
> > as well as various upstream bug reports or even discussions in debian-kde
> > for tons of discussions on this matter. Anything is there, including the
> > hints about optimizing the database.
> > 
> > Yes, I am a bit annoyed that you brought the database or not question up
> > once again. It has been discussed to death already. However, I also
> > understand that there is no central place for all of the information
> 
> […]
> 
> I am sorry, Frank.
> 
> This was partly uncalled for as I understand after doing some releasing.
> 
> I still think these are upstream matters, however it was perfectly within my
> responsibility if I answer and if so how much time I take for it.

Did you actually see my other mail? Again, my question was not about having a
DB or not, it was about whether it's possible to take a shortcut during KDE
upgrade or not and about possible consequences. And it was definitely not
meant to start another discussion.

I'm still interested in the answer to my question.

Kind regards,

Frank

Re: KDEPIM 17.08: The whole thing works

[Martin Steigerwald]

Hello Sandro.

Martin Steigerwald - 17.11.17, 14:04:
> > 3. akonadictl start
> > 
> > But I had issues with the database upgrade. Because it needs to create a
> > temporary table, that was too big for my tmp filesystem
> > The error is:
> > Got error 64 'Temp file write failure' from InnoDB
[…]
> > I solved this with setting the tempdir in
> > ~/.local/share/akonadi/mysql.conf
> > [mysqld]
> > tmpdir = /usefullpath
> 
> Maybe it would be good to implement to safeguard this in upstream code base
> somehow. I.e. check free space beforehand and notify the user if there is
> not enough.
[…]
> IMHO thats another disadvantage of using MySQL/MariaDB by default. Much
> temporary space needed for… things like this.

First I told Frank to drop the topic, and then, as I sense a Debian KDE user 
who also works as Debian Qt/KDE team packager and as an upstream developer, I 
bring it up myself.

Sandro, feel free to just ignore my nitpicking.

Thank you,
-- 
Martin

Re: Akonadi database (war: Re: KDEPIM 17.08: The whole thing works)

[Martin Steigerwald]

Hello Frank.

Martin Steigerwald - 17.11.17, 11:27:
> However all of that is nothing that makes sense to discuss here – as that
> are upstream matters. You may try to discuss this with upstream developers,
> but be prepared that they may not like the database or not discussion once
> again. This is really a question that I have seen *a ton of times* in
> various places. This is a touchy subject with upstream developers I think.
> 
> I kindly ask you to drop the discussion on this matter here, as it would
> just be a waste of time here on this list. Thank you.
> 
> Even if you go on… I may not reply anymore – I took a lot of time for this
> detailed reply already. See kdepim-users and kde-pim upstream mailing lists
> as well as various upstream bug reports or even discussions in debian-kde
> for tons of discussions on this matter. Anything is there, including the
> hints about optimizing the database.
> 
> Yes, I am a bit annoyed that you brought the database or not question up
> once again. It has been discussed to death already. However, I also
> understand that there is no central place for all of the information
[…]

I am sorry, Frank.

This was partly uncalled for as I understand after doing some releasing.

I still think these are upstream matters, however it was perfectly within my 
responsibility if I answer and if so how much time I take for it.

Thanks,
-- 
Martin

Re: KDEPIM 17.08: The whole thing works

[Martin Steigerwald]

Hey Sandro,

Sandro Knauß - 17.11.17, 13:42:
> > Okay, so I installed Akonadi + KDEPIM 17.08 and the whole things works.
[…]
> 3. akonadictl start
> 
>  But I had issues with the database upgrade. Because it needs to create a
> temporary table, that was too big for my tmp filesystem
> The error is:
> Got error 64 'Temp file write failure' from InnoDB

Oh.

I think as the largest table here, the part table is about 3,2 GiB, this still 
fitted into:

martin@merkaba:~> LANG=C df -hT /tmp
Filesystem Type   Size  Used Avail Use% Mounted on
tmpfs  tmpfs  4.7G  356K  4.7G   1% /tmp

> I solved this with setting the tempdir in ~/.local/share/akonadi/mysql.conf
> [mysqld]
> tmpdir = /usefullpath

Maybe it would be good to implement to safeguard this in upstream code base 
somehow. I.e. check free space beforehand and notify the user if there is not 
enough.

I think using /tmp may be less than optimal on machines with little RAM. Sure 
if the machine has lots of RAM, like this ThinkPad T520 with 16 GiB of it, it 
is beneficial. But a machine with just 4 GiB may only have 1 GiB of /tmp in 
most desktop distributions that use tmpfs for /tmp.

Maybe it would be better to use /var/tmp, however as that is on / filesystem 
for many setups… well…

IMHO thats another disadvantage of using MySQL/MariaDB by default. Much 
temporary space needed for… things like this.

> At least for me the switching folder is much faster (because now the
> threading is cached and not recreated every time).

Wow, yes!

I did not notice that yet. This is really noticeable.

Thanks for pointing it out.

Other than that tuning MariaDB database did the trick, so mail filtering 
appears similary fast than before.

I noticed something else:

The expandable progress bar stuff in the bottom of the kmail window is gone. 
Well often it was not too useful anyway.

Thanks,
-- 
Martin

Re: KDEPIM 17.08: The whole thing works

[Sandro Knauß]

Hey,

> Okay, so I installed Akonadi + KDEPIM 17.08 and the whole things works.

1. akonadictl stop

2. I updated to experimental packages too. I used:
apt install -t experimental kontact

2.1 I also had to update some packages by hand:
apt install -t experimental libkf5akonadisearch-data 
libkf5akonadisearchxapian5 libkf5akonadinotes5 libkf5akonadisearchcore5
apt install -t experimental libkf5libkdepim-plugins:amd64

(the purging was already done by updating kontact)

3. akonadictl start

 But I had issues with the database upgrade. Because it needs to create a 
temporary table, that was too big for my tmp filesystem
The error is:
Got error 64 'Temp file write failure' from InnoDB

I solved this with setting the tempdir in ~/.local/share/akonadi/mysql.conf
[mysqld]
tmpdir = /usefullpath

After that the upgrade started successfully and after some minutes I had a 
fully working kontact.

At least for me the switching folder is much faster (because now the threading 
is cached and not recreated every time).

Best regards,

sandro



signature.asc
Description: This is a digitally signed message part.

Re: KDEPIM 17.08: The whole thing works

[Martin Steigerwald]

Martin Steigerwald - 17.11.17, 11:01:
> Performance-wise I am not very impressed so far. For me it appears mail
> filtering probably even got a bit slower. However, its too soon so say
> something for sure.

I bet that has been due to the fact that Akonadi upgrade undid my MariaDB 
optimization in mysql.conf. I redid these optimizations at it feels to me that 
I am back at regular speed again. However, its a bit early to say this and its 
all my subjective impression anyway.  Time will tell.

-- 
Martin

Akonadi database (war: Re: KDEPIM 17.08: The whole thing works)

[Martin Steigerwald]

Hello Frank,

Frank Mehnert - 17.11.17, 09:17:
> Martin,
> 
> thank you for sharing your experiences!
> 
> Regarding the database optimization: Would it be possible to remove
> the complete database in certain cases? AFAIR, the Akonadi DB does
> not store the messages itself, it only stores indexing information,
> probably also flags / message tags etc...

Anything is possible.

Will you do it? The current KDEPIM developers will not do it. And I am quite 
certain I can say this here from what I remember of past discussions on this 
matter. They replied to this question countless of times.

Akonadi caches messages, but it does not store them permanently. This has been 
addressed several times in various places as well already.

As far as I understand the changes in indexing that Daniel works on will mean 
that for indexing the mails, contacts, events, whatever do not need to go into 
the Akonadi database temporarily anymore.

I totally get the skepticism about the database, but a database does not need 
to be an issue. Zimbra uses a MySQL database too and its blazingly fast even 
with 45+ mails in *one* folder. However what I dislike a bit is that 
Akonadi uses a database, yet does not really totally free the user from 
handling it. Anyone with a larger set of mails needs to tune the MySQL 
database as I described here and on kdepim-users before… wait… maybe that is 
the performance drop I currently see in Akonadi/KDEPIM 17.08

Yep, the upgrade undid my optimizations:

-innodb_buffer_pool_size=1024M
+innodb_buffer_pool_size=128M

(this is already more than the 64 MiB it used initially)
  
 # Buffer size used to write to the log files on disk (default:1M for builtin, 
8M for plugin)
 # larger values means less I/O
-innodb_log_buffer_size=32M
+innodb_log_buffer_size=1M

(and yes, I think I still have an bug report this open in upstream bugtracker)

I suggest anyone with a large body of mails and stuff to run mysqltuner.pl on 
the database and tune it.

I will redo the tuning now against the newly installed database configuration. 
I think this will fix the performance drop in mail filtering I perceived.

So all that is my main critique regarding the database: The user should not be 
required to do things like this. So either Akonadi could handle MySQL or 
PostgreSQL with high performance *all by itself*, so maybe, just maybe, 
another database which does not require the user to be a part-time database 
admin would be in order.

Another critique of mine is: Akonadi 16.04 at least did way to much and was 
still not really optimized as much as it can regarding database queries. 
KDEPIM developers are application developers, not really database experts, it 
appears to me. Additionally Akonadi 16.04 did to much on mail filtering with 
local maildirs anyway: It synchronized each folder after each few mails it 
placed there. Yet, no one else is changing those maildirs, it moved the mails, 
so why check in the first place? Synchronizing means it lists the directory 
contents and synchronizes it with the information it has in the database. Also 
with IMAP in 16.04 the folder synchronisation happened much too often. Even 
just after deleting a few mails.

Actually I think a kind of database is needed. Going back to pre-akonadi times 
of using index files within KMail itself does not really make sense to me. The 
probable Akonadi replacement Sink that Kube mail client uses, also uses a 
database. I am not completely sure, but I think its LMDB, the Lightning Memory 
Database of the OpenLDAP project. It may be something else tough. But I would 
not hold my breath on Sink replacing Akonadi for KDEPIM anytime soon. Its the 
implementation that at least with 16.04 left a lot to be desired, not the 
usage of the database itself that is the main issue here. 

However all of that is nothing that makes sense to discuss here – as that are 
upstream matters. You may try to discuss this with upstream developers, but be 
prepared that they may not like the database or not discussion once again. 
This is really a question that I have seen *a ton of times* in various places. 
This is a touchy subject with upstream developers I think.

I kindly ask you to drop the discussion on this matter here, as it would just 
be a waste of time here on this list. Thank you.

Even if you go on… I may not reply anymore – I took a lot of time for this 
detailed reply already. See kdepim-users and kde-pim upstream mailing lists as 
well as various upstream bug reports or even discussions in debian-kde for 
tons of discussions on this matter. Anything is there, including the hints 
about optimizing the database.

Yes, I am a bit annoyed that you brought the database or not question up once 
again. It has been discussed to death already. However, I also understand that 
there is no central place for all of the information I provided or hinted at 
above. I think at least the database optimization should go into upstream 
wiki, but I never took the 

Re: KDEPIM 17.08: The whole thing works

[Martin Steigerwald]

Martin Steigerwald - 17.11.17, 00:01:
> Okay, so I installed Akonadi + KDEPIM 17.08 and the whole things works.

Some additional notes:

It triggers a complete re-indexing of all mails. I aborted it now, cause I 
have *tons* of mails in folders for archival and I am happy for now when its 
just indexes with what I work with for now. Also Daniel Vrátil works on 
considerable changes to the indexing architecture that will make a complete 
rebuild of the index necessary anyway:

Randa Report Part 2
https://www.dvratil.cz/2017/09/randa-report-part-2/

Performance-wise I am not very impressed so far. For me it appears mail 
filtering probably even got a bit slower. However, its too soon so say 
something for sure.

I did not see many visible changes in KMail so far. Mail source view syntax 
highlighted now :)

I reviewed KDE Application changelogs. Some things that stood out to me. In 
each release there is a huge ton of bug fixes according to full changelogs. I 
mainly looked about Akonadi + KDEPIM Runtime, KMail and Akregator, as that is 
what I mainly use.

https://www.kde.org/announcements/

https://www.kde.org/announcements/announce-applications-17.08.0.php
- KMail can use external editor, implemented by plugin
- Bugfixes and regex line editor in Sieve editor 
- Some changes in KMail transport that I do not really understand
- Seamonkey import in Akonadi import wizard
- Updates to KMail documentation

https://www.kde.org/announcements/announce-applications-17.04.0.php
- Akonadi import wizard can import Sieve rules (I am not sure whether this 
wizard is something introduced with 16.12… or was just marked as new there due 
to packaging splits, which brought us the delay in NEW queue)
- Better performance for search dialog by caching collection paths

https://www.kde.org/announcements/announce-applications-16.12.0.php:
- KMail and Akregator can use Google Safe Browsing to check if a link being 
clicked is malicious. Both have also added back printing support (needs Qt 
5.8). => well I will disable that one, should I find in settings, okay, in 
KMail it is disabled by default (under "Security / Reading"), as well as in 
Akregator (under "Browser")

https://www.kde.org/announcements/announce-applications-16.08.0.php:
- more Qt WebEngine (instead of Webkit, I think KMail)
- detailed changelog: quicker access to search (via class instead of DBUS)

This is just what I found. I bet I may have overlooked quite a bit and there 
can be stuff that is important to you, but not to me.

Thanks,
-- 
Martin

Re: KDEPIM 17.08: The whole thing works

[Frank Mehnert]

Martin,

thank you for sharing your experiences!

Regarding the database optimization: Would it be possible to remove
the complete database in certain cases? AFAIR, the Akonadi DB does
not store the messages itself, it only stores indexing information,
probably also flags / message tags etc...

Frank

Re: Kdepim is a pending upload?

[Sandro Knauß]

Hey,

> I wonder, why a pending upload now needs more than 2 month to be really
> uploaded.

No there are no "real" reasons, why it takes that long staying in NEW 
queue[0], except than human capacity of the FTP masters to get through the 
list of all new packages and approve/decline them. So the acceptance of the 
packages is not in our hands :( 

> Does anybody know, when we (users not afraid to try ' debian
> experimental') can use kontact, kmail, kaddressbook, etc again. 

you can use the packages from experimental, but there are packages inside NEW 
queue are not accepted inside Debian, so you have to build them on your own. I 
don't know any way how you can reach the packages inside the NEW queue.

> Do you need help? Or do we have to compile on our own, if we want nearly 
actual versions of the most valuable kde packages and not be stuck in the 
depth of nowhere. In my opinion the best way to loose early adopters, the best 
testers on this planet.

Well we always need manpower - the Qt/KDE Team in Debian is quite small, so 
the workload is sometimes quite big. But unfortunately for this specific issue 
"to get KDE Application 17.08 to Debian", we can't do anything except helping 
the FTP masters (Don't know if and how they need help) or being patient.

Just to make it clear, we are not happy with the current situation and I share 
the point, that getting KDE Application 17.08 to unstable fast would be great. 

There is also a thread about this at the debian-kde ml:
https://lists.debian.org/debian-kde/2017/10/msg00039.html

Best regards,

sandro

[0] https://ftp-master.debian.org/new.html


signature.asc
Description: This is a digitally signed message part.

Re: Kdepim is a pending upload?

[Sandro Knauß]

Hey,

> I wonder, why a pending upload now needs more than 2 month to be really
> uploaded.

No there are no "real" reasons, why it takes that long staying in NEW 
queue[0], except than human capacity of the FTP masters to get through the 
list of all new packages and approve/decline them. So the acceptance of the 
packages is not in our hands :( 

> Does anybody know, when we (users not afraid to try ' debian
> experimental') can use kontact, kmail, kaddressbook, etc again. 

you can use the packages from experimental, but there are packages inside NEW 
queue are not accepted inside Debian, so you have to build them on your own. I 
don't know any way how you can reach the packages inside the NEW queue.

> Do you need help? Or do we have to compile on our own, if we want nearly 
actual versions of the most valuable kde packages and not be stuck in the 
depth of nowhere. In my opinion the best way to loose early adopters, the best 
testers on this planet.

Well we always need manpower - the Qt/KDE Team in Debian is quite small, so 
the workload is sometimes quite big. But unfortunately for this specific issue 
"to get KDE Application 17.08 to Debian", we can't do anything except helping 
the FTP masters (Don't know if and how they need help) or being patient.

Just to make it clear, we are not happy with the current situation and I share 
the point, that getting KDE Application 17.08 to unstable fast would be great. 

There is also a thread about this at the debian-kde ml:
https://lists.debian.org/debian-kde/2017/10/msg00039.html

Best regards,

sandro

[0] https://ftp-master.debian.org/new.html


signature.asc
Description: This is a digitally signed message part.

Re: KdePIM results testing migration from Plasma 4 to Plasma 5

[Martin Steigerwald]

Hello Shawn,

Am Donnerstag, 2. Februar 2017, 16:00:02 CET schrieb Shawn Sörbom:
> On Thursday, November 17, 2016 2:35:47 AM PST Shawn Sörbom wrote:
[…]
> Hi, I recently made the switch to testing and it seems that almost
> everything migrated without any intervention from me. It would seem that my
> fears were largely unfounded the only thing I had to fiddle with was
> migrating kwallet data, which didn't work the first time I ran it. But I
> got around that by resetting the migrated value in
> ~/.local/share/kwalletd/kwalletrc to "no", and then restarting kwalletd and
> kwalletd5 from the command line. A migration assistant will then ask for
> your old wallet's password. this should be the last time this ever happens,
> as the new wallet appears to be integrated with PAM. Is there any chance of
> getting this added to the Debian wiki? I feel it may be useful there.

Feel free to create an account there and add it yourself.

With your contribution to the wiki you help other Debian users.

Thanks,
-- 
Martin

Re: KdePIM results testing migration from Plasma 4 to Plasma 5

[Shawn Sörbom]

On Thursday, November 17, 2016 2:35:47 AM PST Shawn Sörbom wrote:
> On Wednesday, November 16, 2016 23:05:17 Martin Steigerwald wrote:
> > Hello.
> > 
> > Am Mittwoch, 16. November 2016, 13:31:12 CET schrieb Shawn Sörbom:
> > > 2. My messages imported alright...but they were imported as a separate
> > > directory structure. Long story short, I now have two "inboxes"-one of
> > > which  is empty.
> > 
> > I didn´t use any KDEPIM Settings Importer or other import functionality in
> > KMail. I just moved the maildir directories over to the new location in
> > ~/.local/share/local-mails and pointed the maildir resource there, then
> > gave it some time to synchronise. Also I let it pick up the old kmailrc.
> > 
> > Okay, there is one additional step: Before that with KDEPIM 4 I moved all
> > mbox archival folders I had in the mixed maildir resource to an extra
> > resource and switched the main maildir resource from mixed maildir to
> > plain
> > maildir. I still didn´t point a mixed maildir resource to the old archived
> > mails in KDEPIM 5 as last times I tried to do it ate all memory.
> > 
> > Maybe you have two mail related resources now. If so you can remove one
> > with Akonadiconsole for example. But make sure to pick the right one :).
> > But even if you pick to wrong one, you can recreate a maildir resource
> > and point it to the maildir location again, as deleting the resource does
> > not delete the data it handles.
> > 
> > Read:
> > 
> > Akonadi misconception #1: where is my data?
> > Submitted by amantia
> > https://blogs.kde.org/2011/11/13/akonadi-misconception-1-where-my-data
> > 
> > And this one:
> > 
> > akonadi/KDE PIM backup/restore
> > https://mail.kde.org/pipermail/kdepim-users/2016-October/000351.html
> > 
> > > How do I go about providing bug reports from here?
> > 
> > Thats a tough one. Why?
> > 
> > - I think upstream as in bugs.kde.org would be the right recipient.
> > 
> > - But I think upstream neither has the interest nor the manpower to handle
> > issues related to migrate from KDEPIM 4 to 5 anymore – unless it a fix for
> > a bug reproducable within KDEPIM + Akonadi 5. Stable Debian users are
> > among the latest users to migrate.
> > 
> > - Quite some of the issue like loosing filters may already be reported and
> > lingering in upstream bugzilla.
> > 
> > - Report in Debian then? I think Debian Qt/KDE maintainers do not have the
> > resources to do much more than to refer to upstream. I am happy they are
> > able to provide packages, although for KDEPIM it would be good to have
> > 16.08 instead of 16.04, but this AFAIK is still blocked by packaging Qt
> > WebEngine, which basically is a port of Chromium´s Blink webengine.
> > 
> > Still if you want to report anything: Good luck!
> > 
> > Otherwise I suggest to struggle your way through. Review resources in this
> > list and in upstream kdepim-users list. Especially in kdepim-users mailing
> > list, but I think also here I covered migration issues more than once. And
> > so did others. Most if not all questions have been answered already and I
> > don´t even completely recall it all. I migrated more than a year ago and
> > forgot most of the process. If you need help, ask. At least you do the
> > migration only once.
> > 
> > I especially would ask in kdepim-users for any open migration issues.
> > There
> > are a lot of users who did the migration and there are upstream
> > developers,
> > too.
> > 
> > Am I happy with that? Not really. But thats how I see the situation.
> > Migrating from KDEPIM 4 to 5 has been rough for many users.
> > 
> > Thanks,
> 
> Moving to .local/share/local-mails did the trick. Thank you.
> Still no filters after I copied over the directories, but I should be able
> to fix that by importing them separately when I upgrade for real. I'm sure
> glad I'm discovering this now as opposed to later!
> Thank you so much!
> 
> Its a shame this doesn't get fixed, I suspect it would be simple to detect a
> plasma 4 backup and handle accordingly. I might just report it...

Hi, I recently made the switch to testing and it seems that almost everything 
migrated without any intervention from me. It would seem that my fears were 
largely unfounded the only thing I had to fiddle with was migrating kwallet 
data, which didn't work the first time I ran it. But I got around that by 
resetting the migrated value in ~/.local/share/kwalletd/kwalletrc to "no", and 
then restarting kwalletd and kwalletd5 from the command line. A migration 
assistant will then ask for your old wallet's password. this should be the 
last time this ever happens, as the new wallet appears to be integrated with 
PAM. Is there any chance of getting this added to the Debian wiki? I feel it 
may be useful there.
--Shawn

Re: KdePIM results testing migration from Plasma 4 to Plasma 5

[Sandro Knauß]

Hey,

> Thats a tough one. Why?
> 
> - I think upstream as in bugs.kde.org would be the right recipient.
> 
> - But I think upstream neither has the interest nor the manpower to handle
> issues related to migrate from KDEPIM 4 to 5 anymore – unless it a fix for a
> bug reproducable within KDEPIM + Akonadi 5. Stable Debian users are among
> the latest users to migrate.

The thing with migration issues, is that a user want to migrate once and than 
never again. So it is quite hard to reproduce issues, I had often discussions, 
and than suddenly the users said - oh now the old data is gone, so nothing to 
reproduce. If you have some that can be reproduced for the developers, they 
can help. And before make sure, that the the issue is maybe already known in 
bugs.kde.org. But keep in mind kdepim is not a big team, so they may also 
answer, that they want to focus to something else.

> - Report in Debian then? I think Debian Qt/KDE maintainers do not have the
> resources to do much more than to refer to upstream. I am happy they are
> able to provide packages, although for KDEPIM it would be good to have
> 16.08 instead of 16.04, but this AFAIK is still blocked by packaging Qt
> WebEngine, which basically is a port of Chromium´s Blink webengine.

If there are concrete patches, I'm happy to backport them! 16.08 won't help in 
the migration problem, because as you said already, Debian is one of the last 
that are doing the migration.

> Otherwise I suggest to struggle your way through. Review resources in this
> list and in upstream kdepim-users list. Especially in kdepim-users mailing
> list, but I think also here I covered migration issues more than once. And
> so did others. Most if not all questions have been answered already and I
> don´t even completely recall it all. I migrated more than a year ago and
> forgot most of the process. If you need help, ask. At least you do the
> migration only once.
> 
> I especially would ask in kdepim-users for any open migration issues. There
> are a lot of users who did the migration and there are upstream developers,
> too.
> 
> Am I happy with that? Not really. But thats how I see the situation.
> Migrating from KDEPIM 4 to 5 has been rough for many users.

For other Debian user it would help to document a little bit solutions for 
issues while migration under wiki.debian.org, so others do not need to search 
though the mailing list archives.

Best Regards,

sandro

signature.asc
Description: This is a digitally signed message part.

Re: KdePIM results testing migration from Plasma 4 to Plasma 5

[Shawn Sörbom]

On Wednesday, November 16, 2016 23:05:17 Martin Steigerwald wrote:
> Hello.
> 
> Am Mittwoch, 16. November 2016, 13:31:12 CET schrieb Shawn Sörbom:
> > 2. My messages imported alright...but they were imported as a separate
> > directory structure. Long story short, I now have two "inboxes"-one of
> > which  is empty.
> 
> I didn´t use any KDEPIM Settings Importer or other import functionality in
> KMail. I just moved the maildir directories over to the new location in
> ~/.local/share/local-mails and pointed the maildir resource there, then gave
> it some time to synchronise. Also I let it pick up the old kmailrc.
> 
> Okay, there is one additional step: Before that with KDEPIM 4 I moved all
> mbox archival folders I had in the mixed maildir resource to an extra
> resource and switched the main maildir resource from mixed maildir to plain
> maildir. I still didn´t point a mixed maildir resource to the old archived
> mails in KDEPIM 5 as last times I tried to do it ate all memory.
> 
> Maybe you have two mail related resources now. If so you can remove one with
> Akonadiconsole for example. But make sure to pick the right one :). But
> even if you pick to wrong one, you can recreate a maildir resource and
> point it to the maildir location again, as deleting the resource does not
> delete the data it handles.
> 
> Read:
> 
> Akonadi misconception #1: where is my data?
> Submitted by amantia
> https://blogs.kde.org/2011/11/13/akonadi-misconception-1-where-my-data
> 
> And this one:
> 
> akonadi/KDE PIM backup/restore
> https://mail.kde.org/pipermail/kdepim-users/2016-October/000351.html
> 
> > How do I go about providing bug reports from here?
> 
> Thats a tough one. Why?
> 
> - I think upstream as in bugs.kde.org would be the right recipient.
> 
> - But I think upstream neither has the interest nor the manpower to handle
> issues related to migrate from KDEPIM 4 to 5 anymore – unless it a fix for a
> bug reproducable within KDEPIM + Akonadi 5. Stable Debian users are among
> the latest users to migrate.
> 
> - Quite some of the issue like loosing filters may already be reported and
> lingering in upstream bugzilla.
> 
> - Report in Debian then? I think Debian Qt/KDE maintainers do not have the
> resources to do much more than to refer to upstream. I am happy they are
> able to provide packages, although for KDEPIM it would be good to have
> 16.08 instead of 16.04, but this AFAIK is still blocked by packaging Qt
> WebEngine, which basically is a port of Chromium´s Blink webengine.
> 
> Still if you want to report anything: Good luck!
> 
> Otherwise I suggest to struggle your way through. Review resources in this
> list and in upstream kdepim-users list. Especially in kdepim-users mailing
> list, but I think also here I covered migration issues more than once. And
> so did others. Most if not all questions have been answered already and I
> don´t even completely recall it all. I migrated more than a year ago and
> forgot most of the process. If you need help, ask. At least you do the
> migration only once.
> 
> I especially would ask in kdepim-users for any open migration issues. There
> are a lot of users who did the migration and there are upstream developers,
> too.
> 
> Am I happy with that? Not really. But thats how I see the situation.
> Migrating from KDEPIM 4 to 5 has been rough for many users.
> 
> Thanks,

Moving to .local/share/local-mails did the trick. Thank you.
Still no filters after I copied over the directories, but I should be able to 
fix that by importing them separately when I upgrade for real. I'm sure glad 
I'm discovering this now as opposed to later!
Thank you so much!

Its a shame this doesn't get fixed, I suspect it would be simple to detect a 
plasma 4 backup and handle accordingly. I might just report it...

Re: KdePIM results testing migration from Plasma 4 to Plasma 5

[Martin Steigerwald]

Hello.

Am Mittwoch, 16. November 2016, 13:31:12 CET schrieb Shawn Sörbom:
> 2. My messages imported alright...but they were imported as a separate 
> directory structure. Long story short, I now have two "inboxes"-one of
> which  is empty.

I didn´t use any KDEPIM Settings Importer or other import functionality in 
KMail. I just moved the maildir directories over to the new location in 
~/.local/share/local-mails and pointed the maildir resource there, then gave 
it some time to synchronise. Also I let it pick up the old kmailrc.

Okay, there is one additional step: Before that with KDEPIM 4 I moved all mbox 
archival folders I had in the mixed maildir resource to an extra resource and 
switched the main maildir resource from mixed maildir to plain maildir. I 
still didn´t point a mixed maildir resource to the old archived mails in 
KDEPIM 5 as last times I tried to do it ate all memory.

Maybe you have two mail related resources now. If so you can remove one with 
Akonadiconsole for example. But make sure to pick the right one :). But even 
if you pick to wrong one, you can recreate a maildir resource and point it to 
the maildir location again, as deleting the resource does not delete the data 
it handles.

Read:

Akonadi misconception #1: where is my data?
Submitted by amantia 
https://blogs.kde.org/2011/11/13/akonadi-misconception-1-where-my-data

And this one:

akonadi/KDE PIM backup/restore
https://mail.kde.org/pipermail/kdepim-users/2016-October/000351.html

> How do I go about providing bug reports from here?

Thats a tough one. Why?

- I think upstream as in bugs.kde.org would be the right recipient.

- But I think upstream neither has the interest nor the manpower to handle 
issues related to migrate from KDEPIM 4 to 5 anymore – unless it a fix for a 
bug reproducable within KDEPIM + Akonadi 5. Stable Debian users are among the 
latest users to migrate.

- Quite some of the issue like loosing filters may already be reported and 
lingering in upstream bugzilla.

- Report in Debian then? I think Debian Qt/KDE maintainers do not have the 
resources to do much more than to refer to upstream. I am happy they are able 
to provide packages, although for KDEPIM it would be good to have 16.08 
instead of 16.04, but this AFAIK is still blocked by packaging Qt WebEngine, 
which basically is a port of Chromium´s Blink webengine.

Still if you want to report anything: Good luck!

Otherwise I suggest to struggle your way through. Review resources in this 
list and in upstream kdepim-users list. Especially in kdepim-users mailing 
list, but I think also here I covered migration issues more than once. And so 
did others. Most if not all questions have been answered already and I don´t 
even completely recall it all. I migrated more than a year ago and forgot most 
of the process. If you need help, ask. At least you do the migration only 
once.

I especially would ask in kdepim-users for any open migration issues. There 
are a lot of users who did the migration and there are upstream developers, 
too.

Am I happy with that? Not really. But thats how I see the situation. Migrating 
from KDEPIM 4 to 5 has been rough for many users.

Thanks,
-- 
Martin

Re: KDEPIM: Display glitches

[Michael Schuerig]

On Samstag, 6. August 2016 18:08:09 CEST Luigi Toscano wrote:
> Il 06 agosto 2016 16:16:50 CEST, Michael Schuerig 
 ha scritto:
> >As far as I can tell, yet, things are working. But there are a number
> >of
> >display glitches in several programs.
> >
> >KMail
> >* Message Headers are missing
> >* Menu View > Headers does not have a submenu
> 
> Install kdepim-addons.

Thanks, that was apparently missing.

Michael

-- 
Michael Schuerig
mailto:mich...@schuerig.de
http://www.schuerig.de/michael/