Showing posts from November, 2014

New Kernel Playground

The default kernel stock has been raised once again in -current branch. The latest stable LTS kernel release (3.14.24) is now being used while config for latest stable kernel (3.17.3) has been included as well for those brave enough or need newer kernel to test new features or need support for newer hardware.

Firefox 33.1.1 is also included in this batch of update, so if you have issues regarding graphic drivers in Firefox, then perhaps this version can fix your problem.

Bad News for DigiKam Users

I may have a bad news for DigiKam users that are using Slackware-Current. DigiKam 4.5.0 has been released and i have pushed the updates to SlackBuilds project. This package works well under Slackware 14.1 stable, but unfortunately this may not work if you are using -current under a certain configuration.

If you have upgraded to the latest KDE 4.14.3 and KDE framework 5 along with Plasma 5 provided by Eric Hameleers, then you may not be able to use digiKam properly. I have tried many combinations, but still it ended with a segfault or build failure.

The possible solution is basically to upgrade exiv2 to 0.24 and have libkexiv2 in KDE 4.14.3 recompiled against exiv2 and then you can have a working digiKam.I have discussed it with digiKam maintainer and we believe this is the reason why it failed on my machine.

If you can build and run it properly without having to upgrade exiv2 and recompile KDE 4.14.3, then i will gladly hear your input on this issue.

Fix regressions

There are two regressions found on previous security updates: mariadb and pidgin. MariaDB developers made some changes in one of their headers, my_config.h that caused some problems with other packages that are linked against it.

I first spotted this problem when trying to compile gdal on SlackBuilds repository. I reported this to the maintainer and soon after, we both found that it's not just gdal that were broken, but many others, namely php, apr-utils, mysql-workbench, etc. I googled a bit and found a patch in other project, so i tried to apply it on my own computer and it worked, so i proposed the patch to Patrick and got accepted.

Second regression was on pidgin. Upstream developers broke Gadu-Gadu protocol when providing security update. Mancha found a patch to fix the problem and got accepted as well.

In -current, firefox has been upgraded to 33.1 as well.

New Kernels on -Current

New LTS kernel release appearing on -current branch along with small number of packages that are being upgraded to the latest version.

The default kernel stock in -current branch has been raised to 3.14.23 and this will continues to go on unless a new LTS version is announced and then probably we will move to that new version. Personally, i'm fine with this version as my personal need (NVidia driver and VMWare Workstation) works perfectly on this kernel without requiring patches at all. It works flawlessly.

Another important update on this batch is bash which is now includes the latest patch available upstream. For now, this should fix all the remaining questions whether the bash package included in Slackware is insecure.

Other changes were minors. btrfs-progs is upgraded and added a header files, mpg123 is also upgraded to the latest version and so does for xfce4-weather-plugin (this should solve a problem reported in LQ).

Multiple Advisories: firefox, seamonkey, php, and mariadb

Multiple advisories has been released for Slackware 14.0 and 14.1 (and of course -current) branches. Most of them are Mozilla-based products, such as Firefox and Seamonkey and the rest are php and mariadb.

Firefox has been upgraded to the next ESR (Extended Support Release), which is based on Firefox 31 branch. This is expected as some big companies (namely Google) has dropped support for older ESR version, forcing users to upgrade to the latest version or latest ESR version, which is what Slackware users get (ESR in -stable and latest version in -current branch).

Slackware 14.0 users who uses Seamonkey still gets an update on this release to 2.30, which is basically the latest version of seamonkey available right now. The same thing happened on php update, which is backported to Slackware 14.0 as well. They will all get PHP 5.4.34.

As of MariaDB, the update was only backported to Slackware 14.1, since Slackware 14.0 still uses MySQL and there's no more updates on the version incl…