The KDE team released the next update in the KDE 4.8 cycle today. As expected it is mostly on target again.
The sources were made available to packagers some days earlier and that enabled me to update my scripts and start building on time.
I am running KDE 4.8.2 myself and so far, have not found issues. If you find any, be sure to discuss them on this blog page. I have packages ready for you to download & enjoy!
- http://alien.slackbook.org/ktown/4.8.2/ (the master repository), rsync URI: rsync://alien.slackbook.org/alien/ktown/4.8.2/
- http://taper.alienbase.nl/mirrors/alien-kde/4.8.2/ (my fast mirror), rsync URI: rsync://taper.alienbase.nl/mirrors/alien-kde/4.8.2/
- http://repo.ukdw.ac.id/alien-kde/4.8.2/ (willysr’s Indonesian mirror), rsync URI: rsync://repo.ukdw.ac.id/alien-kde/4.8.2/
- http://scw.net.br/alien-ktown/4.8.2/ (a mirror maintained by Herbert Alexander Faleiros), rsync URI: rsync://rsync.scw.net.br/alien-ktown/4.8.2/
As usual, my README file contains detailed installation/upgrade instructions. Do not fail to follow those instructions!
I have updated quite a lot of the dependencies for this release, in particular qt, libdbusmenu-qt, sg3_utils, sip, PyQt, QScintilla, shared-desktop-ontologies, raptor2, rasqal, redland, grantlee, phonon, phonon-mplayer, soprano, akonadi. I also moved libktorrent back from the “deps” directory into KDE’s “extragear” because libktorrent depends on kdelibs and therefore should be considered as being a KDE component.
And there may even better news in the near future. Pat Volkerding grabbed my build scripts to create official KDE 4.8.2 packages for Slackware-current which hopefully will be showing up in the repositories soon. This means that finally with the update from 4.5.5 to 4.8.2 (and skipping all the 4.6 and 4.7 releases) Slackware again would have a real “current” KDE environment by default. Let’s all hope Pat does not get distracted by the hordes of fans demanding attention!
Have fun! Eric
There are the need to update glibc? (as current is using 2.15 now and I have 2.14.1 installed on my system)
Yes. as I stated, you need to be running slackware-current. And glibc-14.1 is no longer part of slackware-current.
Eric
thanks as usual, Eric, especially for qt-4.8.1 (and patches) 🙂
Wow that was quick. Thanks 🙂
Thanks!!!
Thanks a lot for your work from Russia!
PS. there are two versions of oxygen-gtk2 pakage. Is it realy necessary?
LOE, you are right. I have now removed the bad package in the 32bit section, thanks for noticing it.
Eric
Virtuoso-OSE is missing from the source directory and the package directories as well, and it complains about it missing if you try to run the alldeps.SlackBuild
Slackware with KDE 4.8, nice…. thanks for your works on KDE. I’m mirroring it now :-p
Many thanks again Eric for your treats to devoted slackers.
Let’s hope that Pat has a really boring spring:)
Hi! On u tutorial used rsync “ok”… i get all files (32bits and 64bits) my system is 64…. i need get all files?!
Thks!
Thanks Eric!
Thanks Eric – installed and running smooth for 12 hours now.
Thanks Eric! Sailing smoothly!
Hi LukeWolf
virtuoso-ose was updated in Slackware-current, therefore there was no longer a need for me to supply the package as part of the KDE set… please upgrade to slackware-current first.
I will update the “alldeps.SlackBuild” script on the first occasion.
Eric
Hi Eric,
I have installed your KDE 4.8.1 packages and I am quite happyily using them (-: !! However, I had to recompile and upgrade audacious. Another thing I would like to know is which packets I need to deactivate in slackpkg if I wanted to use it to have my slackware current installation up to date. Currently it always tries to downgrade to KDE 4.5.5.
Cheers and many thanks
Steph
Very good, I would like to see the python 2.7 on Slackware
Thanks, upgraded from 4.8.1. Some as silk.
Stephan,
I have the following two lines in the file “/etc/slackpkg/blacklist”:
[0-9]+_SBo
[0-9]+alien
This keeps all my packages safe from overwriting/deleting (they all have an “alien” tag) and also all packages created by scripts hosted on http://slackbuilds.org/ (whose default tag is “SBo”).
Eric
Hi Eric,
thanks for this straight forward and easy to understand solution to my little issue (-: ! I am delighted !!!!!
All the best for Easter from Berlin
Stephan
Thanks, everything is working well.
I would like to ask if it would be possible to put the doc in the qt-4.8.2 package in a separate one, since this doc is not used by most users. I am also using “multilib”, and these giant docs appear now twice, in /usr/lib64 and /usr/lib.
Thank You! Piece of great work, as usual!
Thanks Eric!!
Hi Eric. A little bit off topic: it seems that the calibre slackbuild beome incompatible with -cuurent since the imagemagick update. I’m gettting this error: RuntimeError: Failed to load ImageMagick: libMagickWand.so.4: cannot open shared object file: No such file or directory
Hi escaflown
Unless you want to add imagemagick as static dependency into the package, you can do a simple hack which was enough to get Calibre running (no idea if it affects its functionality or stability):
( cd /usr/lib64 ; ln -s libMagickWand.so.5 libMagickWand.so.4 ; ln -s libMagickCore.so.5 libMagickCore.so.4 )
Of course, you can always recompile the Calibre package yourself on Slackware-current which will also get rid of the library version conflict.
Eric
Thanks Eric! The hack did it.
Hi Eric! Sorry for newbie question and my English. Is it possible to upgrade only glibc package without kernel and then upgrade to KDE 4.8.2?
Hi dr_alex
You can try upgrading only glibc but I make no guarantees. If you want KDE 4.8.2 so badly then either upgrade to slackware-current or recompile KDE 4.8.2 yourself for your version of Slackware.
Eric
Hi Eric! Not that this is related to KDE, but I was wondering how you were going with creating packages for LibreOffice 3.5. Are you still plagued by the same troubles you were encountering earlier in attempting to package it? Do you think you’ll be successful in creating packages for next month’s 3.5.3 release? If you are successful, will you package it for Slackware 13.37 or Current? Your hard work in packaging for Slackware is greatly appreciated, and us Slackers eagerly anticipate your results! 🙂
Hi jaycee
I did not yet try LibreOffice 3.5.2, but I did not have success with the earlier sources. I gave my scipts to Willy Sudiarto but he did not find a solution either: http://slackblogs.blogspot.com/2012/03/compiling-libreoffice-still-no-success.html
Currently I do not have the time to troubleshoot the build, since it takes a day between every iteration… the sources are too big.
Eric
@jaycee:
Still no progress on LibreOffice build. I tried to update Eric’ slackbuild script, but still no luck as well.
Your best chance is to use the one provided in SBo project for now.
Hey Eric and Willy! Thanks for the update!
That’s a shame about the build failures. At least your LO 3.4.5 build is fully functional. 🙂 Admittedly I don’t really need LO 3.5 – it was more out of curiosity to see if the .doc support had made any improvements at all (although it’s already good as it is). Should I encounter any .doc files that render poorly, I can indeed use the SBo build as Willy suggested to give LO 3.5 a shot. Thank you both again for such quick replies! 🙂
In most cases, docs are well supported since the era of OpenOffice.org, but it keeps getting better in LibreOffice.
You will not find any major problems when you are trying to view a simple documents with no os-spesific fonts or features.
i’ve got the feeling slackware 14 rc1 is coming 🙂
there’s been a lot of updates in the current and now this post about kde-4.8.2 replacing 4.5.5 🙂
and in two weeks it’s a year since the previous release 🙂
this is it guys a month (or more likely two) and we will have slackware 14 🙂
Eric if you can comment on that i’m sure all your followers would love to hear it 🙂
@toudi
i’m really not sure about having an RC in short time, since there are still a lot of things to update and i guess the new GCC and GLIBC still have some problems with some applications out there. They might take some time to stabilize.
Having a new KDE release in -Current doesn’t mean that we are near the RC since a lot of others are still in Pat’s TODO list, such as XOrg and other libraries.
It’s most likely that next Slackware will be released this year, but only Pat can decide when willl that time be 🙂
Of course there is not going to be a RC soon.
Remember, Slackware is ready when it’s ready, not when a year passes.
Perhaps we will see KDE 4.8.2 next in Slackware-current, but nothing is certain yet. Even when it gets added, we will have to allow for a lot of time to find the bugs and fix them.
Hi Eric,
Thanks for the updates. A non-technical question…I’d be interested to hear about how your get your kde sources-do you use git? The src tarballs only seem accessible individually which takes 000’s of mouse clicks!
@Kristian
I do not know what you mean with “The src tarballs only seem accessible individually which takes 000?s of mouse clicks”. You can easily download all my sources with a single command, like I explain in the README.
The official KDE SC sources are taken from the KDE ftp server, and several of the other sources which I use are checkouts from the KDE git repository at http://quickgit.kde.org/
Eric
Hi Eric,
Thanks-I meant to ask about how you get the sources that you host on your rsync server, rather than how I obtain them from your server. The kde ftp site seems to only have individual tarballs for the kde source rather than an easy way of downloading them all at once.
Best,
Kristian
The package is now officially landed in -Current 🙂
@Kristian
The KDE SC sources can be downloaded with a single lftp command using ftp://ftp.kde.org/pub/kde/stable/4.8.2/src/ or else you can use a single rsync command to get rsync://ftp.kde.org/kdestableftp/4.8.2/src/
Many of the other sources I used are taken from git repositories or from other locations at http://ftp.kde.org and I grab those on an individual basis. If you want to repeat that process instead of getting them from my repository, be my guest.
Eric