Showing posts from May, 2016

Security Update: php, libxml2, and libxslt

Three security updates were released this morning for Slackware 14.0 and newer:
libxslt: upgraded to 1.1.29 php: upgraded to 5.6.22libxml2: upgraded to 2.9.4 Meanwhile in current, some bug fixes were pushed as well:
sysvinit-scripts: fix cgroup, cgmanager, and cgproxy handling ghostscript: use bundled openjpeg librarylxc: merge rc.S changesqeegie: upgraded to 1.3rc.dropbear is now executable in the images

Security Update: libarchive and Poppler Effect

One security update was released by Pat for Slackware 14.1 and current: libarchive. This package is now updated to 3.1.2 for both version.

More changes coming to current while some bugs were squashed as well to make sure our next release still have the same quality as previous releases. Here are the highlights:
syslinux: upgraded to 4.0.7e2fsprogs: rebuilt to fix the ext4 issuempg123: upgraded to 1.23.4git: upgraded to 2.8.3poppler: upgraded to 0.44.0gnutls: upgraded to 3.4.12MPlayer: rebuilt with --disable-ossaudioxf86-input-wacom: upgraded to 0.33.0ghostscript: upgraded to 9.19libpng: upgraded to 1.6.22libtiff: upgraded to 4.0.6bind: upgraded to 9.10.4_P1libXfixes: upgraded to 5.0.2libxproto: upgraded to 7.0.29imagemagick: upgraded to 6.9.4_4 Due to changes in poppler which bumped the soname library, atril in my MSB project needs to be rebuilt or otherwise you will not be able to load PDF files. I have uploaded the rebuilt version in both repositories (mix and full GTK+3 build), but …

Security Update: curl and Slackware Live 1.0

One security update has been released today by Pat for all Slackware releases back to 13.0. It's on curl package and it's now upgraded to 7.49.0.

Things gets little busy in current since there has been some updates:
kernel: upgraded to 4.4.11kernel-firmware: upgraded to latest git snapshotbtrfs-progs: upgraded to 4.5.3e2fsprogs: upgraded to 1.43gzip: upgraded to 1.8tar: upgraded to 1.29lxc: upgraded to 2.0.1sqlite: upgraded to 3.13.0vim/gvim: upgraded to 7.4.1832dnsmasq: upgraded to 2.76lftp: upgraded to 4.72mercurial: upgraded to 3.8.2gdbm: upgraded to 1.12libmtp: upgraded to 1.1.11libndp: upgraded to 1.16lvm2: upgraded to 2.02.154python-setuptools: upgraded to 21.0.0kernel config for 4.5 and 4.6 were added in testing/ Slackware current is now getting closer to release and most of the packages that comes with next Slackware 14.2 should be up to date enough for the next few years of usage.

In other story, Eric Hameleers have declared his Slackware Live project stable enough to …

Security Update: thunderbird, imagemagick

Two security updates were released in the last few days and one of them is quite nasty (imagetragick):

thunderbird: Upgraded to 45.1.0 for Slackware 14.1 and newerimagemagic: Upgraded to 6.7.7_10 for Slackware 14.0, 6.8.6_10 for Slackware 14.1, and 6.9.4_1 for current Besides these two security updates, current is now moving as well: kernel: upgraded to 4.4.10kernel-firmware: upgraded to latest git snapshotman-pages: upgraded to 4.0.6NetworkManager and network-manager-applet: Upgraded to 1.2.2moc: upgraded to 2.5.1slackpkg: upgraded to 2.82.1 (now support 14.2 mirror sites)openvpn: upgraded to 2.3.11mesa: upgraded to 11.2.2

MATE 1.14 with GTK+3 for Testing

Since i have reorganized my GTK3 branch for easily building MATE against fully GTK+3 instead of a mix of GTK+2 and GTK+3, i simply used them to build a fully GTK+3 build of MATE 1.14 and publish them on the same repository, but with -gtk3 naming: 1.14-gtk3. (beware: they all have the same name).

Since i publish a new poll in this blog about which MATE should be used for Slackware 14.2, some people have voted in and i found that almost all of the voters (20 out of 21) said that i should build MATE against fully GTK+3 instead of a mix one.Well, here's a good chance for you to compare between a mix build and fully GTK+3 build of MATE 1.14 against latest Slackware Current.

GTK+3 build still have some issues to tackle in (see upstream notes) and some of them are considered major. Other that the issues mentioned there, it's perfectly usable, but still considered experimental by upstream. More bug fixes are coming all the way in the development cycle and i have been monitoring them s…

Building MATE Against GTK3

Since 1.14 branch has been merged into master yesterday, i decided to rebase my GTK3 branch against master so that i can test the new GTK+3 build easily.

Things have changed since GTK3 branch was last modified and some of the work in that branch have been integrated in master, so it took some time to reorganize the commit history to make it linear.

Good news that it's now done. You can fully build MATE against GTK+3 (by default still GTK+2, except for some components which was already ported to GTK+3 in 1.14 cycle) simply by running this command:
git pull  git checkout GTK3./ && ./ &&./ As there has been some packages gets added and removed during 1.14 and Slackware 14.2 cycle, please make sure to read MATE-1.14-CHANGES.TXT before building it from source if you are planning to upgrade from MATE 1.12. It's also suggested to log out of MATE before building as you might get locked in while screensaver is active…

Change of Plan for MATE in 14.2

After thinking about this for a while, i am thinking of changing some of my original idea about MATE for Slackware 14.2.

My original idea is to provide BOTH MATE 1.12 and 1.14 for Slackware 14.2. MATE 1.12 has no changes in terms of number of packages since 1.10 as it was only a bug fixes releases and was done in a short development cycle. At that time, MATE 1.14 was still in the development. I wasn't sure whether i want to take 1.14 because it was late in Slackware's development cycle.

Surprisingly, MATE 1.14 was released in last April and it bring some major changes such as GTK+3 porting, package merge, and many other library bumps here and there. However, it was tested by some people and turns out to be stable for daily usage.

Based on above fact that MATE 1.14 is stable enough and i'm the only maintainer for MSB at this moment, i want to keep the maintenance load in a maintainable level. Hence, my new plan is to provide MATE binary packages starting at 1.14 for Slackwa…

Security Update: mercurial and openssl

There were 2 security updates released this week:
mercurial: upgraded to 3.8.1 and backported to all Slackware releases back to 13.0openssl: upgraded to 1.0.1t for Slackware 14.0 and 14.1 and 1.0.2h for current More updates were released in current:
kernel: upgraded to 4.4.9tmux: downgraded to 2.1 but 2.2 still in testing/samba: upgraded to 4.4.3imagemagick: upgraded to 6.9.3_9hexchat: upgraded to 2.12.1bind: upgraded to 9.10.4hplip: upgraded to 3.16.5mozilla-firefox: upgraded to 45.1.1esrmutt: upgraded to 1.6

Security Update: ntp, php, subversion

There were 3 security updates in the past few days along with many changes in current shaping up to the final version:
ntp: Upgraded to 4.2.8p7: backported to all Slackware stable releasesphp: Upgraded to 5.6.21: backported to Slackware 14.0 and 14.1subversion: Upgraded to 1.7.22 for Slackware 14.0 and 14.1 and 1.9.4 for current Highlights of updates in current:
lvm2: upgraded to 2.02.152gphoto2/libgphoto2: upgraded to 2.5.10 mariadb: upgraded to 10.0.25 vim/gvim: upgrade to 7.4.1811git: upgraded to 2.8.2ruby: upgraded to 2.2.5whois: upgraded to 5.2.12xf86-input-evdev: upgraded to 2.10.2perl: upgraded to 5.22.2poppler: upgraded to 0.43.0libdrm: upgraded to 2.4.68 overall, things are shaping very well and i think everyone will be pleased with the final results when it's released.