Main menu:

Sponsoring

Please consider a small donation:

 

 

Or you can donate bitcoin:

 

Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank

Fame

FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.

Search

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 307 other subscribers

My Favourites

Slackware

Calendar

July 2017
M T W T F S S
« Jun    
 12
3456789
10111213141516
17181920212223
24252627282930
31  

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current

Meta

Adobe Flash security update May ’17

adobe_flash_8s600x600_2I do not post every security update in my repository, but let’s do one again for good measure and to keep y’all sharp and focused.
There’s a new security update for the Flash Player plugin which was released by Adobe earlier today. Check here what version (if any) of the Flash plugin your browser is carrying.
Version 25.0.0.171 is now available for both the PPAPI (Google Chrome and friends) and the NPAPI (Mozilla Firefox and friends) based plugins. Note that these 24.x Flashplayer releases do not support DRM or hardware acceleration as Adobe first wants to focus on security.

You can find Slackware packages for these Flash plugins in the following locations (mirrors may take up to 24 hours to sync):

Have fun.

Some thoughts on the recent updates in Slackware-current

 Last week, a new LTS kernel (4.9.26), new glibc (2.25) and a new gcc compiler suite (7.1.0) landed in Slackware-current. Note that gcc no longer contains the Java compiler (gcj): subsequently Slackware’s gcc-java package has been removed from slackware-current.
We are at the head of the herd again folks. There is not yet any other distro that ships with the gcc-7 compiler by default. This will certainly pose some challenges for people who compile their stuff themselves – the SBo team warned their community about scripts that require patches to compile against gcc-7.

I have my set of challenges myself too… until now, I have not been able to compile the multilib versions of the gcc compiler suite. That’s infuriating, I can tell you. Specifically, I have issues with brig, gnat, go and objc compilers; the 7.1.0 versions of c and c++ compilers are just fine. I hope to resolve this soon-ish… until then, you will have to wait for new multilib compilers. If you really need a gcc 7.1.0 compiler (for instance, to compile a kernel module) I suggest that you (temporarily) switch to Slackware-current’s gcc 7.1.0 packages. Running your multilib system is of course not affected by this – gcc is only needed to compile stuff. I will probably release glibc-2.25_multilib packages ahead of the problematic gcc multilib packages to give you at least something.

Another interesting addition is lame. After the last Fraunhofer MP3 patent expired on 16 April 2017, the doors were opened to enable MP3 encoding support in Slackware. Several packages have been recompiled to take advantage of the new MP3 encoding capability (cdrdao, sox, ffmpeg, MPlayer, audacious-plugins) and the gstreamer packages were updated for good measure.

I have added ‘lame’ to the ‘massconvert32.sh‘ script of my compat32-tools package and updated the set of “compat32” packages in my multilib repository.

May updates for Plasma 5 (Slackware)

The May 2017 updates for my ‘ktown’ repository are fairly minimal, but anyway here it is: KDE 5_17.05.
This new release contains: KDE Frameworks 5.33.0, Plasma 5.9.5 and Applications 17.04.0. All of this is still built on top of Qt 5.7.1.

NOTE: I will no longer be releasing Plasma 5 packages for 32bit Slackware 14.2.

What’s new in KDE 5_17.05?

  • The ‘deps’ section has two updated packages: json-glib and sip.
  • Plasma 5.9.5 is the final bugfix release of the 5.9 series before 5.10. The oxygen theme package is now extended with Qt4 support so that KDE4 applications can blend in with the Plasma 5 applications if you use the
    Oxygen theme. See https://www.kde.org/announcements/plasma-5.9.5.php .
  • In applications-extra I updated krita and krusader, and rebuilt calligra.
  • In kde4-extragear I added a patched oxygen-gtk2 package which should fix crashes in firefox-derived browsers such as Pale Moon.

This upgrade should be relatively straightforward if you already have Plasma 5 installed. See below for install/upgrade instructions. For users who are running slackware-current, the most crucial part is making sure that you end up with Slackware’s packages for ‘libinput‘ and ‘libwacom‘. I had those two packages in the ‘current’ section of my repository for a while (they are still part of the ‘14.2’ section) but Slackware added them to the core OS. Failing to install the correct (i.e. Slackware) packages, may render your input devices (mouse and keyboard) inoperative in X.Org.

Non-ktown packages you probably want anyway

There are a couple of *runtime* dependencies that I did not add to the ‘ktown’ repository, but you may want to consider installing them yourself because they enable functionality in Plasma 5 that you would otherwise miss:

  • vlc: will give phonon another backend to select from.
  • freerdp: access RDP servers through krdc.

All of the above can be found in my regular package repository.

In order for kdenlive to reach its full potential, you might want to consider replacing Slackware’s ‘ffmpeg‘ package by my version with extended functionality: more supported codecs including AAC, MP3 and H.264 encoders.

Multilib considerations

If you install a 32bit program on a 64bit Slackware computer with multilib and that program needs legacy system tray support (think of Skype for instance), you will have to grab the 32-bit version of Slackware’s ‘libdbusmenu-qt’ and my ktown-deps package ‘sni-qt’, and run the ‘convertpkg-compat32 -i‘ command on them to create ‘compat32’ versions of these packages. Then install both ‘libdbusmenu-qt-compat32‘ and ‘sni-qt-compat32‘.
Those two are mandatory addons for displaying system tray icons of 32bit binaries in 64bit multilib Plasma5.

Installing or upgrading Frameworks 5, Plasma 5 and Applications

You can skip the remainder of the article if you already have my Plasma 5 installed and are familiar with the upgrade process. Otherwise, stay with me and read the rest.

As always, the accompanying README file contains full installation & upgrade instructions. Note that the packages are available in several subdirectories below “kde”, instead of directly in “kde”. This makes it easier for me to do partial updates of packages. The subdirectories are “kde4“, “kde4-extragear“, “frameworks“, “kdepim“, “plasma“, “plasma-extra“, “applications“, “applications-extra” and “telepathy“.

Upgrading to this KDE 5 is not difficult, especially if you already are running KDE 5_17.04. You will have to remove old KDE 4 packages manually. If you do not have KDE 4 installed at all, you will have to install some of Slackware’s own KDE 4 packages manually. Luckily, KDE 5 is mature enough that there’s almost nothing left from old KDE 4 that you would really want.

What I usually do is: download all the ‘ktown’ packages for the new release to a local disk. Then run “upgrade –install-new” on all these packages. Then I check the status of my Slackware-current, upgrading the stock packages where needed. The slackpkg tool is invaluable during this process of syncing the package installation status to the releases.

Note:

If you are using slackpkg+, have already moved to KDE 5_17.04 and are adventurous, you can try upgrading using the following set of commands. This should “mostly” work but you still need to check the package lists displayed by slackpkg to verify that you are upgrading all the right packages. Feel free to send me improved instructions if needed. In below example I am assuming that you tagged my KDE 5 repository with the name “ktown” in the configuration file “/etc/slackpkg/slackpkgplus.conf“):
# slackpkg update
# slackpkg install ktown (to get the newly added packages from my repo)
# slackpkg install-new (to get the new official Slackware packages that were part of my deps previously)
# slackpkg upgrade ktown (upgrade all existing packages to their latest versions)
# slackpkg upgrade-all (upgrade the remaining dependencies that were part of my repo previously)

And doublecheck that you have not inadvertently blacklisted my packages in “/etc/slackpkg/blacklist“! Check for the existence of a line in that blacklist file that looks like “[0-9]+alien” and remove it if you find it!

Recommended reading material

There have been several posts now about KDE 5 for Slackware-current. All of them contain useful information, tips and gotchas. If you want to read them, here they are: http://alien.slackbook.org/blog/tag/kde5/

A note on Frameworks

The KDE Frameworks are extensions on top of Qt 5.x and their usability is not limited to the KDE Software Collection. There are other projects such as LXQT which rely (in part) on the KDE Frameworks, and if you are looking for a proper Frameworks repository which is compatible with Slackware package managers such as slackpkg+, then you can use these URL’s to assure yourself of the latest Frameworks packages for Slackware-current (indeed, this is a sub-tree of my KDE 5 repository):

The same goes for Frameworks for Slackware 14.2 (change ‘current’ to ‘14.2’ in the above URLs).

Where to get the new packages for Plasma 5

A Plasma5 Live ISO image will follow shortly on http://bear.alienbase.nl/mirrors/slackware-live/latest/ in case you want to try it out first (check the timestamp of the ISO on the web page).

Package download locations are listed below (you will find the sources in ./source/5/ and packages in /current/5/ and  /14.2/5/ subdirectories). If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.

Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

Plasma 5 for Slackware – April edition

During the past week (ever since the source tarballs for the new Applications were made available to packagers) I have been working toward an April 2017 release of my ‘ktown’ repository: KDE 5_17.04.
This new release contains: KDE Frameworks 5.33.0, Plasma 5.9.4 and Applications 17.04.0. All of this is still built on top of Qt 5.7.1.
A Plasma5 Live ISO image will follow shortly in the usual location.
NOTE: I will no longer be releasing Plasma 5 packages for 32bit Slackware 14.2.

What’s new in KDE 5_17.04?

  • The ‘deps’ section has one recompiled package (because of incompatible library updates in slackware-current): dvdauthor, and five upgrades: accountsservicefrei0r-plugins, gpgme, ninja and poppler.
    There’s also one new package (but only for the Slackware -current package set): qtav as a new dependency for digikam.
  • Frameworks 5.33.0 is an enhancement release. See https://www.kde.org/announcements/kde-frameworks-5.33.0.php
  • Plasma 5.9.4 is an incremental bugfix of the 5.9 series with small fixes only. See https://www.kde.org/announcements/plasma-5.9.4.php . At first I wanted to wait for the 5.9.5 release which is around the corner but decided not to waste another couple of days. I may add the 5.9.5 later on, since that will be the final iteration for 5.9.
    I am not sticking with the long term support (LTS) releases of Plasma 5.8, as I think LTS should be targeting stable Slackware. If you want to know more about the long term support plans, go read: https://www.kde.org/announcements/plasma-5.8.0.php .
  • Applications 17.04.0 is a new major release and marks the transition of yet another pack of applications from the old kdelibs4 to KDE Frameworks (KF5). I should check what’s still based on kdelibs4 sometimes… can’t be too many left. See https://www.kde.org/announcements/announce-applications-17.04.0.php . And the release notes give more detail about the changes in packages.
    Since k3b is now part of the Applications suite, I have removed the package that I had added to ‘applications-extra’ (which was based on a git snapshot). Another package which is no longer part of my ‘ktown’ set: kajongg (it requires python3 now which is not part of Slackware). And two packages are no longer shipped because their sources are no longer part of Applications: pim-storage-service-manager and kommander.
  • In ‘applications-extra’ I added the latest releases of krita, the KDEvelop suite and of kpmcore (the partitionmanager core libraries). I rebuilt digikam against qtav.
    The newest calligra was already added last week as part of a package rebuild, caused by slackware-current library updates. Worth mentioning is that calligra, krita, ktorrent, partitionmanager, skanlite and the KDE Development Suite in ‘applications-extra’ are all KF5 based.
  • In ‘kde4-extragear’ I have added audiocd-kio4 and libkcompactdisc4 which are built from the kdelibs4-based Applications 16.08.3 sources. All of audiocd-kio4libkcddb4 and libkcompactdisc4 packages are (only) required by Slackware’s kaudiocreator.

This upgrade should be relatively straightforward if you already have Plasma 5 installed. See below for install/upgrade instructions. For users who are running slackware-current, the most crucial part is making sure that you end up with Slackware’s packages for ‘libinput‘ and ‘libwacom‘. I had those two packages in the ‘current’ section of my repository for a while (they are still part of the ‘14.2’ section) but Slackware added them to the core OS. Failing to install the correct (i.e. Slackware) packages, may render your input devices (mouse and keyboard) inoperative in X.Org.

You may want to check out the new Plasma 5 before installing. For this purpose, I have generated a new Live ISO for the PLASMA5 variant. Look for that ISO on http://bear.alienbase.nl/mirrors/slackware-live/latest/ .

Non-ktown packages you probably want anyway

There are a couple of *runtime* dependencies that I did not add to the ‘ktown’ repository, but you may want to consider installing them yourself because they enable functionality in Plasma 5 that you would otherwise miss:

  • vlc: will give phonon another backend to select from.
  • freerdp: access RDP servers through krdc.

All of the above can be found in my regular package repository.

In order for kdenlive to reach its full potential, you might want to consider replacing Slackware’s ‘ffmpeg‘ package by my version with extended functionality: more supported codecs including AAC, MP3 and H.264 encoders.

Multilib considerations

If you install a 32bit program on a 64bit Slackware computer with multilib and that program needs legacy system tray support (think of Skype for instance), you will have to grab the 32-bit version of Slackware’s ‘libdbusmenu-qt’ and my ktown-deps package ‘sni-qt’, and run the ‘convertpkg-compat32 -i‘ command on them to create ‘compat32’ versions of these packages. Then install both ‘libdbusmenu-qt-compat32‘ and ‘sni-qt-compat32‘.
Those two are mandatory addons for displaying system tray icons of 32bit binaries in 64bit multilib Plasma5.

Installing or upgrading Frameworks 5, Plasma 5 and Applications

You can skip the remainder of the article if you already have my Plasma 5 installed and are familiar with the upgrade process. Otherwise, stay with me and read the rest.

As always, the accompanying README file contains full installation & upgrade instructions. Note that the packages are available in several subdirectories below “kde”, instead of directly in “kde”. This makes it easier for me to do partial updates of packages. The subdirectories are “kde4“, “kde4-extragear“, “frameworks“, “kdepim“, “plasma“, “plasma-extra“, “applications“, “applications-extra” and “telepathy“.

Upgrading to this KDE 5 is not difficult, especially if you already are running KDE 5_17.03. You will have to remove old KDE 4 packages manually. If you do not have KDE 4 installed at all, you will have to install some of Slackware’s own KDE 4 packages manually. Luckily, KDE 5 is mature enough that there’s almost nothing left from old KDE 4 that you would really want.

What I usually do is: download all the ‘ktown’ packages for the new release to a local disk. Then run “upgrade –install-new” on all these packages. Then I check the status of my Slackware-current, upgrading the stock packages where needed. The slackpkg tool is invaluable during this process of syncing the package installation status to the releases.

Note:

If you are using slackpkg+, have already moved to KDE 5_17.03 and are adventurous, you can try upgrading using the following set of commands. This should “mostly” work but you still need to check the package lists displayed by slackpkg to verify that you are upgrading all the right packages. Feel free to send me improved instructions if needed. In below example I am assuming that you tagged my KDE 5 repository with the name “ktown” in the configuration file “/etc/slackpkg/slackpkgplus.conf“):
# slackpkg update
# slackpkg install ktown (to get the newly added packages from my repo)
# slackpkg install-new (to get the new official Slackware packages that were part of my deps previously)
# slackpkg upgrade ktown (upgrade all existing packages to their latest versions)
# slackpkg upgrade-all (upgrade the remaining dependencies that were part of my repo previously)

And doublecheck that you have not inadvertently blacklisted my packages in “/etc/slackpkg/blacklist“! Check for the existence of a line in that blacklist file that looks like “[0-9]+alien” and remove it if you find it!

Recommended reading material

There have been several posts now about KDE 5 for Slackware-current. All of them contain useful information, tips and gotchas. If you want to read them, here they are: http://alien.slackbook.org/blog/tag/kde5/

A note on Frameworks

The KDE Frameworks are extensions on top of Qt 5.x and their usability is not limited to the KDE Software Collection. There are other projects such as LXQT which rely (in part) on the KDE Frameworks, and if you are looking for a proper Frameworks repository which is compatible with Slackware package managers such as slackpkg+, then you can use these URL’s to assure yourself of the latest Frameworks packages for Slackware-current (indeed, this is a sub-tree of my KDE 5 repository):

The same goes for Frameworks for Slackware 14.2 (change ‘current’ to ‘14.2’ in the above URLs).

Where to get the new packages for Plasma 5

Download locations are listed below (you will find the sources in ./source/5/ and packages in /current/5/ and  /14.2/5/ subdirectories). If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.

Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

For your Slackware-current: KDE 5_17.03 with lots of goodies

Those of you who follow my repository RSS feeds have already noticed, but many people rely on the announcements I make on this blog (plus, I can give a lot more detail here).
I uploaded the packages for the March 2017 release of my ‘ktown’ repository: KDE 5_17.03. Actually, there is a lot of interesting stuff going on in this release, because I decided to do some things that were on my TODO for a long while. Read more about that below in the “NEWS” section.
What you get in this new release is: KDE Frameworks 5.32.0, Plasma 5.9.3 and Applications 16.12.3. All of this is still built on top of Qt 5.7.1.
This Plasma 5 release targets only Slackware-current for the moment, because of the PLASMA5 Live that I release in parallel. But packages for Slackware 14.2 (only 64bit) are already being compiled at the moment, so updates will be visible in my 14.2 repository in a couple of days at most.
NOTE: I will no longer be releasing Plasma 5 packages for 32bit Slackware 14.2.

What’s new in KDE 5_17.03?

  • Let’s start with the ‘deps’ section this time as there are some interesting updates to be checked out. You will find two upgraded packages: phonon-vlc and qca-qt5. Also six entirely new ones to support digikam and kdenlive: lensfun, opencv, frei0r-plugins, vid.stab, dvdauthor and mlt. You may already have one or more of these installed from SBo, so make sure to upgrade to my ‘ktown‘ versions to prevent breakage in digikam and kdenlive. Notably, the SBo version of my ‘frei0r-plugins‘ package is called ‘frei0r‘.
    The two packages that required the addition of these new dependencies: ‘digikam‘ (in kde/applications-extra) and ‘kdenlive‘ (in kde/applications) were on my TODO for a long time, but they depended on ffmpeg (amongst others) and although I have been adding many dependency packages to ‘ktown’, a ffmpeg package was one bridge too far. Now that Slackware (in the -current development tree) finally has its own ‘ffmpeg’ package, I decided to go ahead and investigate what else was required to finally add digikam/kdenlive.
  • Frameworks 5.32.0 is an enhancement release. See https://www.kde.org/announcements/kde-frameworks-5.32.0.php
  • Plasma 5.9.3 is the third iteration of the 5.9 series with small fixes only. See https://www.kde.org/announcements/plasma-5.9.3.php . I am not sticking with the long term support (LTS) releases of Plasma 5.8, as I think LTS should be targeting stable Slackware. If you want to know more about the long term support plans, go read: https://www.kde.org/announcements/plasma-5.8.0.php .
    My observations about Plasma 5.9:

    • Along with Plasma 5.9 a new network configurator was added to System Settings. The NetworkManager-openvpn plugin package I added to my regular repository and which I also added to the PLASMA5 Live Edition, allows you to define new OpenVPN connections in this Plasma network configurator. Unfortunately, when choosing “import existing vpn configuration” the editor always crashes the very moment I click on a openvpn configuration file. I can however create the desired VPN configuration using the GTK based “nm-connection-editor” instead. Afterwards, this new VPN definition is visible and usable in the Plasma 5. But I really would like the Plasma editor to work too. A bug report which I opened could not be confirmed  by the developer because he can not reproduce it – apparently the cause is something in Slackware, or in my packages.
  • Applications 16.12.3 is an incremental fix-release in the 16.12 series. See https://www.kde.org/announcements/announce-applications-16.12.3.php . I was finally able to compile the ‘libkface‘ and ‘kdenlive‘ packages now that their dependencies have been fulfilled. Kdenlive is a (free and powerful) non-linear video editor and having this in Slackware’s Plasma 5 is an exciting enhancement.
  • Applications-extra contains two new packages: ‘digikam‘ and ‘krusader‘. Krusader is a KF5-based advanced twin panel (commander style) file manager with lots of data manipulation tools. I added this one on request of one of my readers. And Digikam is the well-known photo management suite for KDE. Its KF5 port needed some dependencies which I finally fulfilled so I could add it to my repository. And glad about that, too. Years ago I ranted about how the digikam developers made it impossible for packagers to fulfill the program’s dependencies on a stable platform like Slackware and at that time I made the decision to stop making packages for it out of sheer frustration at the lack of answers.
    I have also added a beta release of k3b (now finally a KF5 port) which will see its first new official release as part of Applications 17.04 next month. Lastly I upgraded the kdevelop related packages.
  • In plasma-extra I rebuilt the sddm-qt5 package, enabling the dutch translation and making sure that SDDM picks up your $LANG settings.
  • Also worth mentioning: with every release of Plasma and Applications, the Qt4 legacy becomes smaller. Only a limited amount of qt4/kdelibs4 packages remains. And KF5 ports of k3b, calligra, krita, ktorrent, partitionmanager, skanlite and the KDE Development Suite can be found in the “kde/applications-extra” subdirectory.

This upgrade should be relatively straightforward if you already have Plasma 5 installed. See below for install/upgrade instructions. For users who are running slackware-current, the most crucial part is making sure that you end up with Slackware’s packages for ‘libinput‘ and ‘libwacom‘. I had those two packages in the ‘current’ section of my repository for a while (they are still part of the ‘14.2’ section) but Slackware added them to the core OS. Failing to install the correct (i.e. Slackware) packages, may render your input devices (mouse and keyboard) inoperative in X.Org.

You may want to check out the new Plasma 5 before installing. For this purpose, I have generated a new Live ISO for the PLASMA5 variant. Look for that ISO on http://bear.alienbase.nl/mirrors/slackware-live/latest/ .

Non-ktown packages you probably want anyway

There are a couple of *runtime* dependencies that I did not add to the ‘ktown’ repository, but you may want to consider installing them yourself because they enable functionality in Plasma 5 that you would otherwise miss:

  • vlc – will give phonon another backend to select from.
  • python-twisted – required by kajongg to start & run.
  • freerdp: access RDP servers through krdc.

All of the above can be found in my regular package repository.

In order for kdenlive to reach its full potential, you might want to consider replacing Slackware’s ‘ffmpeg‘ package by my version with extended functionality: more supported codecs including AAC, MP3 and H.264 encoders.

Multilib considerations

If you install a 32bit program on a 64bit Slackware computer with multilib and that program needs legacy system tray support (think of Skype for instance), you will have to grab the 32-bit version of Slackware’s ‘libdbusmenu-qt’ and my ktown-deps package ‘sni-qt’, and run the ‘convertpkg-compat32 -i‘ command on them to create ‘compat32’ versions of these packages. Then install both ‘libdbusmenu-qt-compat32‘ and ‘sni-qt-compat32‘.
Those two are mandatory addons for displaying system tray icons of 32bit binaries in 64bit multilib Plasma5.

Installing or upgrading Frameworks 5, Plasma 5 and Applications

You can skip the remainder of the article if you already have my Plasma 5 installed and are familiar with the upgrade process. Otherwise, stay with me and read the rest.

As always, the accompanying README file contains full installation & upgrade instructions. Note that the packages are available in several subdirectories below “kde”, instead of directly in “kde”. This makes it easier for me to do partial updates of packages. The subdirectories are “kde4“, “kde4-extragear“, “frameworks“, “kdepim“, “plasma“, “plasma-extra“, “applications“, “applications-extra” and “telepathy“.

Upgrading to this KDE 5 is not difficult, especially if you already are running KDE 5_17.02. You will have to remove old KDE 4 packages manually. If you do not have KDE 4 installed at all, you will have to install some of Slackware’s own KDE 4 packages manually.

What I usually do is: download all the ‘ktown’ packages for the new release to a local disk. Then run “upgrade –install-new” on all these packages. Then I check the status of my Slackware-current, upgrading the stock packages where needed. The slackpkg tool is invaluable during this process of syncing the package installation status to the releases.

Note:

If you are using slackpkg+, have already moved to KDE 5_17.02 and are adventurous, you can try upgrading using the following set of commands. This should “mostly” work but you still need to check the package lists displayed by slackpkg to verify that you are upgrading all the right packages. Feel free to send me improved instructions if needed. In below example I am assuming that you tagged my KDE 5 repository with the name “ktown” in the configuration file “/etc/slackpkg/slackpkgplus.conf“):
# slackpkg update
# slackpkg install ktown (to get the newly added packages from my repo)
# slackpkg install-new (to get the new official Slackware packages that were part of my deps previously)
# slackpkg upgrade ktown (upgrade all existing packages to their latest versions)
# slackpkg upgrade-all (upgrade the remaining dependencies that were part of my repo previously)

And doublecheck that you have not inadvertently blacklisted my packages in “/etc/slackpkg/blacklist“! Check for the existence of a line in that blacklist file that looks like “[0-9]+alien” and remove it if you find it!

Recommended reading material

There have been several posts now about KDE 5 for Slackware-current. All of them contain useful information, tips and gotchas. If you want to read them, here they are: http://alien.slackbook.org/blog/tag/kde5/

A note on Frameworks

The KDE Frameworks are extensions on top of Qt 5.x and their usability is not limited to the KDE Software Collection. There are other projects such as LXQT which rely (in part) on the KDE Frameworks, and if you are looking for a proper Frameworks repository which is compatible with Slackware package managers such as slackpkg+, then you can use these URL’s to assure yourself of the latest Frameworks packages for Slackware-current (indeed, this is a sub-tree of my KDE 5 repository):

The same goes for Frameworks for Slackware 14.2 (change ‘current’ to ‘14.2’ in the above URLs).

Where to get the new packages for Plasma 5

Download locations are listed below (you will find the sources in ./source/5/ and packages in /current/5/ and  /14.2/5/ subdirectories). If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.

Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric