What Happened in 10 Days of Development?

My last post was about 11 days ago when we were talking about security update for kdelibs and freetype. Since then, -current is still progressing but i didn't write anything for the past 10 days. So, what happened in the past 10 days?

First, we have a new kernel. It jumped 2 minor releases to 4.9.30, the latest LTS release from 4.9.x branch, maintained by Greg K-H. Next we have mesa upgraded to 17.1.1 along with enabled Vulkan drivers for Intel and Radeon, thanks to a new package vulkan-sdk.

alsa-lib and alsa-plugins are now upgraded to 1.1.4, bringing many updates to the sound stack. ffmpeg also received it's first minor release, 3.3.1 fixing tons of bugs. We also see many updated packages:
aaa_terminfo: Upgraded to 6.0 bash: Upgraded to 4.4.012 ccache: Upgraded to 3.3.4gkrellm: Upgraded to 2.3.10 mozilla-firefox: Upgraded to 52.1.2esrnano: Upgraded to 2.8.4 NetworkManager: Upgraded to 1.8.0 newt: Upgraded to 0.52.20 pango: Upgraded to 1.40.6samba: Upgraded to 4.6.4 (security …

Security Update: kdelibs, freetype

Current is progressing nicely after a basic toolchain bump last week. The kernel stock is bumped rapidly and bugs are squashed while security updates were deployed in short period. There are two security updates that were recently released:
kdelibs: Upgraded to 4.14.32freetype: Rebuilt to fix out-of-bound heap-based overflow Lots of small improvements were added into current's mkinitrd, elilo, and sysvinit-scripts. The kernel also received 2 changes during the last two updates: 9P_FS_POSIX_ACL and CIFS_SMB2. These two were requested in LQ. Patrick is following mesa development as well so at this moment, we have latest mesa available in -current. We also have the latest git 2.13.0 which includes big changes for developers.

Having latest version on a package comes with a price, especially when it relates to GCC. Since Slackware jumped from 5.3.0 to 7.1.0 in -current (6.3.0 was in /testing for a while) and the changes itself are quite big, some users quickly found some scripts in SBo …

Cinnamon 3.4 for Slackware 14.2

I have just pushed necessary changes to bring Cinnamon 3.4 packages for Slackware 14.2 users. I bumped some dependencies in the process, but not all deps are bumped since some requires newer GTK+3 stack, which only happening in current.

There are some notes on this packages:
I keep mozjs 24.x branch in 14.2 since it works fineSame thing with cjs 3.2.0 since newer cjs requires newer librariesCinnamon 3.4 can work with cjs 3.2 or 3.4.I disabled wacom support in cinnamon-control-center to avoid adding another dependency (libwacom). This package already exists in Slackware-Current, so it's built with wacom support. For those who want to compile Cinnamon 3.4 for Slackware 14.2, please use 14.2 branch. Master branch is now used for tracking Slackware-Current.

Let me know if you found any trouble using Cinnamon 3.4.

MP3 support in Current

Since MP3 patent has expired in April, some distributions is planning to add full MP3 support by default, starting with Fedora and now Slackware is doing the same thing, except that it has been included in the latest -current tree by the addition of lame package and all relevant packages are being rebuilt to support libmp3lame. I hoped that someday x264 can be included as well or even better x265. They are released under GNU GPL v2.

Another multimedia-related packages being bumped are GStreamer and gst-plugins-{base,good,libav}. They are now upgraded to 1.12.0 which was released few days ago. Flex is now bumped to 2.6.4 which should honor yy_* macros and fix many issues in other open source projects. Lastly, glibc is rebuilt to revert a patch that caused IFUNC errors to be emitted during boot. It's just purely cosmetic.

I'm pretty sure next Slackware release will be another awesome release with all the great goodies. If you are planning to test the latest Slackware-Current wi…

Cinnamon 3.4 Packages for Current

I have just pushed latest Cinnamon 3.4.0 changes in master branch of my CSB project and also pushed the binary packages into the usual testing playground (Thanks to Tadgy).  At this moment, i just tested against -current (it was built on top of latest May 5 update with the latest toolchain) and i still haven't decided whether i will backport this into 14.2 or not.

I made some changes in some script to have them built as noarch since most of them are translations, icons, images, and theme files. This will reduce the build time when building for two architectures. The biggest change in Cinnamon 3.4 packages is the new mozjs which is based on Firefox 38.8.0. In future release, upstream is planning to push forward and rebase it from newer Firefox source such as 45 and 51. For now, Cinnamon added support for mozjs 38.8.0 and we will use that version.

Looking at previous releases, it will take some time to stabilize Cinnamon and there will be several minor releases following changes ups…

NVidia and VMWare Workstation on Linux Kernel 4.9

As mentioned before, Slackware jumped to Linux Kernel 4.9 and this will surely caused NVidia and VMWare Workstation to break. I was quite lucky since Linux Kernel 4.9 has been around for some time and other people have found a way to solve this problem. This post is intended to be a self note just in case i need to re-do the same steps.

NVidia 304.135
My desktop is still using the legacy NVidia driver 304.135. There's no new release for now, so we will need to patch 2 things: the kernel and the driver.
First, you need to patch the kernel using the mtrr.patch as listed in my SlackHacks. Oncerebooted, you will be using the new patched kernel image. Time to go to patch the NVidia driver. Let's extract the source of the NVidia driver:
./NVIDIA-Linux-x86-304.135 --extract-only
cd  NVIDIA-Linux-x86-304.135
patch -p1 < /path/to/kernel-4.9.patch

at this point, the installer will work with Linux Kernel 4.9. As a bonus, i accepted NVidia's new xorg.conf and i got a …

New Toolchain

Patrick finally pushed the basic toolchain in the latest batch of update and it was kinda surprising. First of all, it jumped from GCC 5.4.0 into the newly released GCC 7.1.0. There were a GCC 6.2.0 packages in testing/, but it seems that Patrick decided to abandon that version and go with the latest version instead. The latest GCC 7.1.0 version removed gcc-java and added gcc-brig.

Second toolchain that got bumped is glibc. It's now using the latest glibc 2.25. Some coverage for glibc 2.25 can be read from Phoronix site. I really like this new feature: the stack smashing protector being enabled via --enable-stack-protector=strong.

Third toolchain is the kernel. Patrick is switching to latest LTS release: 4.9.x branch. It's at 4.9.26 at the moment, but it will be bumped as new version got released. I was hoping to get 4.10 or even 4.11, but it seems it would be safer to use LTS kernel.

That's the good side. Now let's see the side effect.

Most likely some of the scripts …

New GTK+3 Stack and MATE Development Changes

This morning, Patrick has just pushed changes to GTK+3 stack into -current, thanks to Robby Workman. Slackware-Current now ships GTK+3-3.22.10, the latest GTK+3 version available at this moment and also the last 3.x release. There won't be any 3.x release, just bumping on minor releases due to bug fixing.

Along with the GTK updates, there are also other updates such as:
btrfs-progs: Upgraded to 4.10.2 grub: Upgraded to 2.02lvm2: Upgraded to 2.02.17xfsprogs: Upgraded to 4.10.0tmux: Upgraded to 2.4swig: Upgraded to 3.0.12freetype: Upgraded to 2.7.1harfbuzz: Upgraded to 1.4.6pygobject3: Upgraded to 3.24.1shared-mime-info: Upgraded to 1.7sip: Upgraded to 4.19.2vte: Upgraded to 0.44.3bluez: Upgraded to 5.44iproute2: Upgraded to 4.10.0gparted: Upgraded to 0.28.1many xfce-related updates. With this update, MATE development will have to change as well. Previously, master and 14.2-mate-1.18 branch is equal since they all use the same GTK+3 version and i can use the same branch to build MATE…