Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)

[Martin Steigerwald]

Hello Lisandro,

Am Samstag, 2. Juli 2016, 21:46:48 CEST schrieb Lisandro Damián Nicanor Pérez 
Meyer:
> Currently the latest version of kdepim is available in experimental.
> According to our limited tests it's working way better than kdepim 4.14
> (more stable, more performant, less bugs). However migrating from one to
> the other is not a trivial process (distribution wise, hopefully not for
> our users).
> 
> If you are still reading, please check the full text in [link].
> 
> [link]
>  ble.html>
> 
> Happy hacking!

Still reading and even replying to it :)

Thanks a lot for the preliminal information on this.

All I can say is:

KDEPIM/Akonadi 16.04 is so much better than any Akonadi based KDEPIM version 
ever before.


That said, I still have self-compiled KMyMoney as even installing the kmymoney 
package from experimental would remove KDEPIM from experimental again.

I do hope that the KF5 based KMyMoney will be ready in time for Stretch. The 
version I have works reasonably okay, I had a few crashes on updating online 
accounts that may also be related to AQBanking/Ghenwhyfar stuff, but otherwise 
its okay. Yet I wasn´t able to complete KMyMoney after KDE Randa Meetings, but 
I didn´t review this anymore, so compiling my work again. However its not yet 
released.


merkaba:~#100> LANG=C apt install -t experimental kmymoney
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 kmymoney : Depends: libakonadi-kde4 (>= 4:4.5.86) but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.
merkaba:~#100> LANG=C apt install -t experimental libakonadi-kde4
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer 
required:
  libdbus-c++-1-0v5 libyaml-cpp0.5v5 python-unidecode
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  accountwizard akonadiconsole akregator blogilo kaddressbook kalarm 
libakonadiprotocolinternals1
The following packages will be REMOVED:
  akonadi-server kdepim kdepim-runtime kmail knotes konsolekalendar kontact 
korganizer
The following NEW packages will be installed:
  libakonadi-kde4 libakonadiprotocolinternals1
The following packages will be upgraded:
  accountwizard akonadiconsole akregator blogilo kaddressbook kalarm
6 upgraded, 2 newly installed, 8 to remove and 243 not upgraded.
Need to get 3934 kB of archives.
After this operation, 21.2 MB disk space will be freed.
Do you want to continue? [Y/n] ^C


This issue is recording as:

#823215 [i|  |  ] [kmymoney] kmymoney: not compatible with KDE PIM 5
https://bugs.debian.org/823215

Thanks,
-- 
Martin

Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)

[David Goodenough]

On Saturday 02 July 2016 21:46:48 Lisandro Damián Nicanor Pérez Meyer wrote:
> Currently the latest version of kdepim is available in experimental.
> According to our limited tests it's working way better than kdepim 4.14
> (more stable, more performant, less bugs). However migrating from one to
> the other is not a trivial process (distribution wise, hopefully not for
> our users).
> 
> If you are still reading, please check the full text in [link].
> 
> [link]
>  ble.html>
> 
> Happy hacking!
Is there a migration guide so that we know what to expect (and when to panic)?

David

Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)

[Rainer Dorsch]

On Sunday 03 July 2016 11:49:42 David Goodenough wrote:
> On Saturday 02 July 2016 21:46:48 Lisandro Damián Nicanor Pérez Meyer wrote:
> > Currently the latest version of kdepim is available in experimental.
> > According to our limited tests it's working way better than kdepim 4.14
> > (more stable, more performant, less bugs). However migrating from one to
> > the other is not a trivial process (distribution wise, hopefully not for
> > our users).
> > 
> > If you are still reading, please check the full text in [link].
> > 
> > [link]
> >  > a
> > ble.html>
> > 
> > Happy hacking!
> 
> Is there a migration guide so that we know what to expect (and when to
> panic)?

Yes, that would be useful. Maybe on a wiki page, which could be updated by 
developers and advanced users...

E.g. is akonadi supposed to be migrated? Are mailbox (e.g. imap) settings 
preserved?

Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)

[Diederik de Haas]

On zondag 3 juli 2016 18:40:15 CEST Rainer Dorsch wrote:
> E.g. is akonadi supposed to be migrated? Are mailbox (e.g. imap) settings 
> preserved?

Yes and yes.
It is important that akonadi-server packages are upgraded, but that should be 
taken care of with kdepim 4:16.04.2-1 (or later)


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

Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)

[Martin Steigerwald]

Am Sonntag, 3. Juli 2016, 18:40:15 CEST schrieb Rainer Dorsch:
> On Sunday 03 July 2016 11:49:42 David Goodenough wrote:
> > On Saturday 02 July 2016 21:46:48 Lisandro Damián Nicanor Pérez Meyer 
wrote:
> > > Currently the latest version of kdepim is available in experimental.
> > > According to our limited tests it's working way better than kdepim 4.14
> > > (more stable, more performant, less bugs). However migrating from one to
> > > the other is not a trivial process (distribution wise, hopefully not for
> > > our users).
> > > 
> > > If you are still reading, please check the full text in [link].
> > > 
> > > [link]
> > >  > > st
> > > a
> > > ble.html>
> > > 
> > > Happy hacking!
> > 
> > Is there a migration guide so that we know what to expect (and when to
> > panic)?
> 
> Yes, that would be useful. Maybe on a wiki page, which could be updated by
> developers and advanced users...
> 
> E.g. is akonadi supposed to be migrated? Are mailbox (e.g. imap) settings
> preserved?

I wrote on this list about this before.

See my last mail in the thread "kdepim 16.04 from experimental":

lists.debian.org/1804539.YkVyMII8Xc@merkaba

Feel free to start a wiki page from this based on this.

My migration experience is outdated, as I migrated last autumn already with a 
much earlier version of the Qt/KF5 based KDEPIM and Akonadi, but for me the 
automatic migration basically worked. Still make a backup before you upgrade 
as I described in that mail.

And I wouldn´t use export/import, it never worked for me.


If you have a mixed maildir resource currently, there is one thing you could 
do: You could move any mbox based folders, if you have some, out of it, and 
then delete the resource and add a maildir resource pointing to the directory 
with the mail, if there are still in ~/.kde/share/apps/kmail, I´d move them to 
~/.local/share/local-mail.

Why? As to my knowledge the pure maildir resource is better tested than the 
mixed maildir one. Although I miss it.

But anyhow, if automatic migration works nicely for you, I´d probably just go 
with it, no matter whether you have a mixed maildir resource or not.

Thanks,
-- 
Martin

Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)

[Martin Steigerwald]

Am Sonntag, 3. Juli 2016, 19:17:19 CEST schrieb Martin Steigerwald:
> And I wouldn´t use export/import, it never worked for me.

No, thats not quite accurate, I am not sure I tried it after having read from 
many users in upstream mailinglist, that it often does not work. Well I think 
I once used it and it was a desaster, but thats really a long, long time ago, 
so I am not quite sure. But I think from back then I found that in case you 
need to import something: Create a suitable resource for the data you want to 
import, point it at the data and let it index it is way more reliable and 
faster.

Still the automatic migration will likely always be faster and require less 
manual work than any other approach – none in the optimal case, so I suggest 
you always just try to let automatic migration do its shop.

Be prepared that it will do a MySQL database schema upgrade, add in new 
indexes and also use a two-level file_db_data, so once you upgrade akonadi-
server there is no easy and supported way back. So again, have a backup, just 
in case.

And be prepared that it can take a longer time where your Akonadi is basically 
busy with the migration and not responding, at least not timely, to anything 
else. Depending on whether your system has an SSD, migration may be quite 
quick, but for harddisk based systems with huge amounts of mails and a large 
MySQL database it can take several hours I think. There may or may not be some 
progress indication in Akonadiconsole.

Thanks,
-- 
Martin

Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)

[Martin Steigerwald]

Am Sonntag, 3. Juli 2016, 19:17:19 CEST schrieb Martin Steigerwald:
> Am Sonntag, 3. Juli 2016, 18:40:15 CEST schrieb Rainer Dorsch:
> > On Sunday 03 July 2016 11:49:42 David Goodenough wrote:
[…]
> > > Is there a migration guide so that we know what to expect (and when to
> > > panic)?
> > 
> > Yes, that would be useful. Maybe on a wiki page, which could be updated by
> > developers and advanced users...
> > 
> > E.g. is akonadi supposed to be migrated? Are mailbox (e.g. imap) settings
> > preserved?
> 
> I wrote on this list about this before.
> 
> See my last mail in the thread "kdepim 16.04 from experimental":
> 
> lists.debian.org/1804539.YkVyMII8Xc@merkaba

After migration I´d do some maintenance steps:

1. akonadictl fsck

2. remove directory ~/.local/share/akonadi/file_lost+found

The first two steps will get rid of leaked (no longer referenced and uses) 
files in file_db_data.


As I think the migration will not do it, I´d also do:

3. akonadictl vacuum

This will remove unused records from the MySQL database, making it smaller, 
and if the filesystem it is on has enough free space, also defragment it, as 
it rewrites the file for each table during removing unused records.

Ciao,
-- 
Martin

plasmashell oomk

[Thomas Fjellstrom]

Hi,

I've got plasma-desktop 4.6.4 installed and its been getting oomkilled 
regularly. This box has 32GB of ram, and only about 2GB used at the moment.

Is this a known problem?

-- 
Thomas Fjellstrom
tho...@fjellstrom.ca