I’ve noticed something strange with various akonadi packages.
I’m using Leap 42.1, with the standard repositories and the extra KDE ones (KDE frameworks, KDE applications, KDE extra, QT5).
The current version of akonadi packages seem to be 16.04.01, with some notable exceptions: akonadi5, akonadi-server and libKF5AkonadiPrivate5 are still stuck at the 15.12.3 version.
I thought at first at some errors in my configuration, but checking with the package search web interface I noticed that newer versions don’t seem available at all (link, link, link); only akonadi-server is available in the current 16.04.01 version, but trying to install it will remove the other two packages, making the whole akonadi unusable.
Why those packages aren’t available? And, why on a single repository (namely KDE:Applications) the packages related to a single application don’t have all the same version, leaving with a mix of new and old packages that could lead to problems?
At the moment the only strange behaviour that I’ve noticed is the impossibility to run akonadiconsole, but I can’t be sure that other things aren’t affected as well.
akonadi5 and libKF5AkonadiPrivate5 have been removed in 16.04, so you see the version from the Leap 42.1 Update repo.
akonadi-server is available as 16.04.1 in KDE:Applications though, click on the “Versions” tab in YaST and install that version.
I thought at first at some errors in my configuration, but checking with the package search web interface I noticed that newer versions don’t seem available at all (link, link, link); only akonadi-server is available in the current 16.04.01 version, but trying to install it will remove the other two packages, making the whole akonadi unusable.
As written above, they are removed on purpose. Their content is now included in the main akonadi-server package, as it is private (see the package name) anyway.
And uninstalling them should not make the whole akonadi unusable, provided that all other packages are up-to-date.
And, why on a single repository (namely KDE:Applications) the packages related to a single application don’t have all the same version, leaving with a mix of new and old packages that could lead to problems?
There is no mix in KDE:Applications, AFAICS.
Also, the version number doesn’t matter much anyway, it is just a number.
The important thing is that all the packages are built against each other…
Thank you for your detailed answer.
I had already tried to perform this upgrade but it caused the various apps that rely on akonadi to behave strangely; this time I have restarted the session after the new packages were installed and everything went fine.
Thank you again.
Restarting the session after installing KDE-related updates is always a good idea, as otherwise the old versions are still running after the update.
And you will even get a mixture of old and new stuff running (newly started programs will of course be the newer versions and might have problems talking to the “old” stuff).
This is not as problematic as it was in the past (before KDE 4.12.2 IIRC), but can lead to problems none-the-less.
PS: in this particular case, only restarting the Akonadi server should have been sufficient too to “fix” it though.
akonadictl restart