Showing posts from June, 2010

Security Updates: libpng and libtiff

Two libraries are being upgraded to fix security vulnerabilities. They are libpng and libtiff. The announcement from Slackware-Security mailing list hasn't arrived yet, but the packages has arrived in public mirrors, so go get them while it's still fresh

KDE 4.5 RC 1 from AlienBOB

Erik (aka AlienBOB) has uploaded Slackware packages for KDE 4.5 RC 1 on his KTown repository and now it has been mirrored on UKDW's Repository for local access. Even though there hasn't been any official announcement (which made me think that it was behind schedule), the sources for RC 1 has been available for few days on their FTP Server (i didn't check this). Maybe they are waiting for Monday for an official announcement.

Anyways, KDE 4.5 RC 1 will have a different dependencies compared in Beta 2, so you will have to upgrade several packages in deps/ directory as well.

For you who enjoyed testing KDE packages, this is your chance to test the upcoming KDE 4.5 which is planned to be released on August 2010.

Note: You will need to use Slackware 13.1 and newer in order to use this packages. Please read the instructions on the repository.

Ghostscript Update to Fix Printing Black Pages

Several users are complaining that they had a problem with CUPS resulting a black paper when printing. Today, a new update has been released on 13.1 and -Current to merge an upstream patch which hopefully be able to fix the problem.

Also, i noticed Firefox 3.6.6 has been released today. I wonder, since few days ago they released 3.6.4 and i didn't see any 3.6.5 release but they bumped into 3.6.6. The only change is the increment of amount of time that plugins are allowed to be non-responsive before being terminated.

I don't think it will be released as a security update, but rather a minor update.

Bunch of Security Updates

Bunch of security updates are being released in -Current as well as in -Stable. Mozilla Firefox, Thunderbird, and Seamonkey are upgraded to the latest stable version to fix almost the same problem since they shared the code, while CUPS and BIND are upgraded to fix CSRF and Cache Poisoning problems.

There are several other packages in -Current which are rebuilt and upgraded as well to fix common problem.

Building GIMP 2.6.9

GIMP 2.6.9 has been released by the upstream developers. While -Current hasn't been officially started yet, it would take some time before this version coming up in -Current, so i tried to compile it manually using SlackBuild script found on source/ directory on Slackware mirrors (i used OSUOSL)

One note if you want to build GIMP 2.6.9 is that you will not require any libpng patch anymore, since it has been included in the source, so remove the following line:
zcat $CWD/gimp.png14.diff.gz | patch -p1 --verbose || exit 1

Don't forget to update the version number and build number and you are ready to compile GIMP 2.6.9

PS: It would take some time to build, so do something else

New btrfs-convert tool

One new package has been added in testing/ directory which is btrfs-progs that consist of btrfs-convert. It's a conversion tool which can be used to convert ext2 to btrfs filesystem. If you need to convert from ext3 or ext4 to btrfs, please have a look on this wiki page.

This filesystem will be used as a default filesystem in some of the future release of other Linux distribution, namely Fedora 14 and Ubuntu 10.10. It's gaining some popularity, so i guess Slackware 14 might have a chance to support this filesystem as well in the future

Security Update: Samba

Today, the first Slackware Security update for 13.1 and goes along to Slackware 10.0 has been released. It's Samba package which is now upgraded to 3.5.3.

Along with this update, several packages has been patched to fix some problem, such as alsa-utils, kdebase-workspace, and xfce.

This is also the marks of first changes in -Current

First SBo Submission

Finally, my first submission to SBo (SlackBuild Project) is accepted and approved by Erik Hanson. I had to re-submit since the package has been accepted once in 13.0 repository, so i had to asked for approval from the previous maintainer before i can become a maintainer for the package.

I mailed the previous maintainer and he agreed to give the maintainer position to me and once i got the approval, i re-submit the package to the SBo and adapted the new SBo template. Today, the package is approved and it has been displayed in the SBo page. The package i submitted was guvcview.

I used this package during my testing with wxCam. The latest version still not working on my laptop and the developer suggested me to test using guvcview and it worked. That's how i get close to guvcview.

Anyway, i have submitted another update to the package since it has released 1.4.0 version (the original submission was 1.3.1). Wait for the next update and it should be there

Just a small tips before you submi…

KDE 4.5 Beta 2 by Eric

Since Eric has posted his work related to KDE 4.5 Beta 2 on his blog, i took a chance to pull his work into our local repo server using rsync to his alien-kde repositories and soon, it will be accessible by going through:

There will be new dependencies as well, so make sure you have installed all the dependencies before upgrading and testing KDE SC 4.5 Beta 2 on your system.

WARNING: KDE SC 4.5 is still in Beta and NOT RECOMMENDED for daily usage system, unless you are a tester or developer who need to try latest KDE version or you are willing to take the risk of having an unstable desktop.

Update (12:36 PM): The repository has been fully synced with Eric's KDE repository now. Everything is mirrored on the repo and it has all the READMEs included in each directory. Enjoy the repositroy

Local KDE SC 4.4.4 Repository

Even though Eric's repository is quite fast (i rsynced his server and got a full speed using my Internet connection at home), for some people, it's still quite slow as it's located outside Indonesia.

Therefore, i am providing a local KDE repositories synced with Eric's repository in UKDW Repository server (connected to Indonesian IIX networks). It will contain Eric's KDE repository starting from 4.4.4 onward. I hope it can help people having problem to download KDE SC and try it on their computers.

You can also use rsync to get the repository using this command:
rsync -vaz --delete rsync://

Remember, you will need Slackware 13.1 and newer to use KDE SC 4.4.4 and future release.

Enjoy KDE 4.4.4

KDE SC 4.4.4 Rsync Service

Eric has updated his blog with a new information about rsync service for his KDE SC 4.4.4 repository. You can use rsync to download the KDE packages using these command (pick the correct architecture):

rsync -av –progress rsync:// .
rsync -av –progress rsync:// .

Please note that there's a not in the last part which denotes a current directory and as the result, a new directory (x86 or x86_64) will be made on the current directory where you execute this command which consists of all packages of KDE SC 4.4.4

When you are finished with the rsync, you can upgrade all the packages using
upgradepkg --reinstall --install-new x86/kde/*.t?z
upgradepkg --reinstall --install-new x86_64/kde/*.t?z

Kudos to Eric

KDE 4.4.4 by Eric

Slackware 13.1 has been released and usually, there will be a two or three months gap before development of Slackware-Current starts again, but KDE team didn't waste their time developing KDE, so they release KDE SC 4.4.4 this month and they will release 4.5 release on July, so Eric has stepped up to provide us with monthly updates of KDE SC 4.4.4 on his repository after Pat has given him an approval.

The full story can be read on Eric's blog.

IMHO, the changes in KDE SC 4.4.4 is not as big as usual, so if you are fine with KDE SC 4.4.3 and lack of bandwidth or having a slow Internet connection, you can stay with KDE SC 4.4.3 for now. 3.2.1 Released

Image 3.2.1 has been released with a new brand. Since Oracle has acquisited Sun, the logo which is displayed in the latest now shows Oracle instead of Sun. I believe the logo is now much more simpler and elegant, with white as dominant color.

As usual, i took a chance to test OOo package in Slackware and the result is excelent. While the SlackBuild script hasn't been updated yet, i'm using the rpm2tgz utilities provided by Slackware to convert the RPM package into tgz and it does works. In order to obtain best result, it would be good idea to remove the old version and then do install new packages instead of upgrading using upgradepkg.

If you are curious about the latest OOo, here's a screenshot about the About

New Poll

Slackware 13.1 has been out for a week and the ISOs has been spreading all around the mirrors around the world and it's time for new poll, so the next questions is "Have you used Slackware 13.1?"

Time to give your votes

This will be a two months votes

Poll Results

One month period is now over and the poll has been closed. Time to get the results. After looking at the results (which i have predicted before), it seems that most of the users are not using encryption features in Slackware and they just store their data normally. I'm not sure why, but there are two possibilities:
it's not easy to setup an encryption on the filesystemsthey don't need an encryption on their dataAnyways, here's the poll results:
Yes, all of my data are encrypted 5 (6%)
Yes, some of my data are encrypted 9 (12%)
No, but i'm planning to use it 17 (23%)
No, i'm fine with my current condition 41 (56%)

wxCAM Works Again

After upgrading to libjpeg v8 in -Current (now has become 13.1), my wxCam suddenly malfunction. I have tried to recompile every dependencies related to wxCam, but still it failed until i got a reply from the developer (in Italian, so i had to use Google Translate to translate it for me ) stating that it doesn't relate directly to libjpeg (which i assumed to be root problem), but it connects to wxImage (which in turns relates to libjpeg).

Here's the error messages i got when running wxCam using the old wxGTK:

Determining video4linux API version...
Using video4linux 2 API
V4L2_CID_SATURATION is not supported
Determining pixel format...
pixel format: JPEG
Found V4L2_PIX_FMT_JPEG pixel format
Wrong JPEG library version: library is 80, caller expects 62
Segmentation faultAs you can see, wxGTK expects to see the old version of libjpeg (62) and the current version is 80. So the solution is to recompile wxGTK (don't forget to apply the patch from SlackBuilds in order for wxGTK to be builda…