Posts

Showing posts from May, 2014

KDE 4.13.1 and LibreOffice 4.2.4 Packages

Eric Hameleers has pushed his update on KDE 4.13.1 for Slackware-Current users and also LibreOffice 4.2.4 for Slackware 14.1 and also Slackware-Current users.

One big change in KDE 4.13.1 is that Baloo now enables you to completely disabled desktop search from System Settings GUI. There has been so many improvements on Baloo as well on this release which can be seen on the issue tracker. LibRaw, KDevelop, oxygen-gtk2, and libkscreen are also upgraded to the latest version following the previous KDE 4.12.x updates.

Get the KDE packages from these mirror sites:
http://alien.slackbook.org/ktown/rsync URI: rsync://alien.slackbook.org/alien/ktown/http://taper.alienbase.nl/mirrors/alien-kde/rsync URI: rsync://taper.alienbase.nl/mirrors/alien-kde/http://repo.ukdw.ac.id/alien-kde/rsync URI: rsync://repo.ukdw.ac.id/alien-kde/http://slackware.org.uk/people/alien-kde/rsync URI: rsync://slackware.org.uk/people/alien-kde/ Meanwhile, LibreOffice is also moving forward with 4.2.4 release and it also …

Kernel 3.14.4 Landed in Current

Slackware-Current has moved to the latest kernel 3.14.4 which brings two changes: disabling CONFIG_DEBUG_KERNEL which disabled some proprietary NVidia drivers to be built against Linux Kernel 3.14.x and also it fixed CVE-2014-0196 which was a race condition that could cause a kernel panic, memory corruption and system crash if the exploit were ran in current machine. I have tested the exploit code and it did freeze my desktop and i had to do a hard reset.

There are several packages which is changed on this batch of updates:
gdb upgraded to 7.7.1libelf rebuilt to link headers in /usr/include and enable -D_FILE_OFFSET_BITS=64 parameter on 32 bit machineddd rebuilt to fix the machine code view Go download and test :)

Security Update: Seamonkey

New Seamonkey has been released and this brings security update for Slackware 14.1 and -Current. Firefox is also upgraded in -Current, but since it's a maintenance release and it only fixed some regressions found after 29.0 was released, no security advisories was issued for this update.

Slackware-Current Started Again

Patrick has just finished uploading his latest work for Slackware-Current branch that indicates next development cycle for next Slackware release is now officially started.

In this batch of update, he upgraded GLIBC to 2.19 and the Linux Kernel to 3.14.3, the latest version available at this time. There are several new packages as well in networking area, such as libnftnl and nftables which is the future potential replacement for iptables.

There's also a fix on bash-completion so that it's working well with newer bash 4.3.

I still don't see GCC gets upgraded at this time, but hopefully GCC 4.9.0 could make it into -current soon.

Start your current engine and start testing guys :)

Early Notice for Future MATE Releases

I have posted this on my Google+, but just in case you didn't see them, i will copy and paste it here:
Some headsup for future MATE 1.10 release:
We (me and Chess Griffin) have decided that we will build future MATE 1.10 for Slackware 14.1 against GTK+2, the same toolkit we used to build MATE 1.8. Although MATE 1.10 will fully support GTK+3, we think it's not a good idea to introduce such as a big change for our users. This is assuming that MATE 1.10 will be released before next Slackware gets released.

However, please note that for next Slackware release, we will build MATE against GTK+3 toolkit. Expect some big changes, mainly in the UI look and feel. Have a look on this blog post by Clasen about what to expect in GTK+3-3.12 dialogs (which i think will be landing in the next Slackware release): http://blogs.gnome.org/mclasen/2014/03/21/dialogs-in-gtk-3-12/.

I know some of you may like or dislike it, but we will try to keep our policy of bringing MATE desktop on top of …

New Poll: Default Kernel in Next Release

It's quite interesting to find out which kernel releases that will be picked up by Patrick Volkerding for the next release of Slackware. I have added a new poll for that and the time frame for voting is two months from now. I have prepared 5 options which should be more than enough for the next development cycle to pick.

During the development cycle that lead to creation of Slackware 14.1, there were some kernel hopping between releases. Originally, the plan was to use the LTS kernel 3.4.x branch, but then Greg K-H decided to make Linux Kernel 3.10 to be his next LTS kernel and Pat decided to take  that chance to upgrade to 3.10 and picked it up as the default kernel in Slackware 14.1. I wonder what will happen during this cycle. Definitely fun to follow :)

Go vote!!

Poll Results

Two months ago, i asked about how people installed packages from SBo repositories and there were 139 votes so far. Thanks to all who have voted and here are the results:
Download and build manually 66 (47%) 
Using sbopkg 50 (35%)
Using sbopkg + sqg 23 (16%)

It seems that almost half of the voters would rather download the script and source manually instead of using automated tools such as sbopkg (and sqg). It's a matter of preferences and it's fine with that, but for those who would like to have easier experiences installing SBo packages, feel free to read my previous article in January about Managing SBo dependencies Easily through the use of sbopkg + sqg for building up the queues files for you.