Linux News Today: Chakra GNU/Linux Users Get KDE Plasma 5.6.3 and KDE Applications 16.04.0, More
Just a few moments ago, the maintainers of the Chakra GNU/Linux operating system had announced that an important update has hit the main software repositories bringing lots of goodies.
Yes, that’s right, we’re talking about the latest KDE Plasma 5.6.3 desktop environment and KDE Applications 16.04.0 software suite, which have been teased to the public since last week, when the distribution’s maintainers announced the availability of Linux kernel 4.5.1 and latest AMDGPU graphics drivers.
“The latest updates for KDE’s Plasma and Applications series are now available to all Chakra users, together with other package updates. A manual intervention is needed for this upgrade, due to a preexisting file that was dropped and now reintroduced in the kde-runtime package,” said Neofytos Kolokotronis in today’s announcement.
OpenJDK 8 Update 92, digiKam 5.0.0 Beta 6, and KDevelop 4.90.91 arrived too
Besides the addition of the major KDE Plasma 5.6.3 and KDE Applications 16.04 packages, the Chakra GNU/Linux maintainers also managed to update some useful applications and utilities, among which we can mention digiKam 5.0.0 Beta 6, KDevelop 4.90.91, OpenJDK 8 Update 92, Zanshin 0.4.0, as well as Hugin 2016.0.0.
On this occasion, Chakra GNU/Linux users are being informed that the libgit2 0.24 and exiv2 0.25 packages received updated that brake backwards compatibility, which means that if they’re using local packages or CCR-installed packages which depend on those libraries, they’ll need to rebuild them.
All Chakra GNU/Linux users are urged to update their installations as soon as possible. For a correct update process, you’ll need to execute the following commands in the terminal emulator. Please note that not all mirrors have been synchronized with the main server at the moment of writing this article, so check the mirror status page.
sudo pacman -Syu > this will return the expected error
sudo pacman -S kde-runtime --force > this will workaround the problem
sudo pacman -Syu > to continue the upgrade as usual