December packages… not Santa Claus but Plasma 5

plasma5_startupI wanted to have the last 16.08.x release of KDE Applications available in my repository before the new 16.12.x releases start coming. There are some big changes in Applications 16.12 for which I need to time to review, plan and build packages. Therefore you will probably not see packages for Applications 16.12.0 in 2016.
So, my december release of the ‘ktown’ packages – KDE 5_16.12 – is sporting KDE Frameworks 5.28.0, Plasma 5.8.4 and Applications 16.08.3 for Slackware, built on top of Qt 5.7.0 which was recompiled with a patch which should improve stability. You can use the latest KDE 5 on Slackware 14.2 and -current.

And because there’s some people who do not read my posts all too carefully, let me again state strongly: my repository contains “latest” and “testing” releases. Currently, the “testing” release is severely outdated and will probably not work at all, or at a minimum give you headaches. The repository you are downloading from should either have “14.2/latest” (for Slackware 14.2) or “current/latest” (for Slackware -current) as part of the URL. When I have time and feel confident, I will re-visit the “testing” repository and work on the Wayland support, which is what that repository is meant for.
Be sure to check your automated package management programs for the correct repository URL!

What’s new in KDE 5_16.12?

  • Frameworks 5.28.0 is an enhancement release with one new framework, ‘syntax-highlighting‘. See https://www.kde.org/announcements/kde-frameworks-5.28.0.php
  • Plasma 5.8.4 is an incremental bug fix release for the 5.8 series. Plasma 5.8 is labeled a Long Term Support (LTS) release.
    See https://www.kde.org/announcements/plasma-5.8.4.php and if you want to know more about the LTS, go read: https://www.kde.org/announcements/plasma-5.8.0.php
  • Applications 16.08.3 is a maintenance upgrade. See https://www.kde.org/announcements/announce-applications-16.08.3.php .
  • In the ‘deps’ section, as previously stated I patched “qt5”. Also I added a “gpgme” package as an update to the stock Slackware version. It’s needed now to compile Kwallet and Telepathy.
  • Telepathy was enhanced with support for the Telegram IM protocol. Please tell me if it works for you – I could not successfully send a chat although the program registers itself with the Telegram servers properly.
  • I have removed baloo and baloo-widgets from the ‘kde4’ package subset. These two kdelibs4-based packages are no longer used by other packages.

This upgrade should be straightforward if you already have Plasma 5 installed. See below for install/upgrade instructions. And if you want to check it out before installing, I have generated a new Live ISO for the PLASMA5 variant. Look for that ISO on http://bear.alienbase.nl/mirrors/slackware-live/latest/ soon. Check the timestamp of the “slackware64-live-plasma5-current.iso” ISO.

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_16.11. 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_16.11 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

53 thoughts on “December packages… not Santa Claus but Plasma 5


  1. The above results in the problem I had with SDDM in the previous version. And now the HiDPI option doesn’t work anymore so SDDM is unusable again.


  2. I fail to see how all the .new files would be gone, unless installpkg/upgradepkg had checked the original file and concluded that there is no difference between original and .new files. You are providing insufficient background info to make an educated guess. You tell exactly zero about your upgrade steps.

    What package tool are you using to do the upgrade? How does a .new file affect your HiDPI settings? Also, the previous Plasma5 package set (the one I released early november) already had this SDDM package on board, so your pkgtools should not even have touched the sddm package or its config file.


  3. 1st I did:
    If you have my ‘ktown’ set of KDE 5_16.11 installed:
    – Upgrade to KDE 5_16.12
    Remove the packages that no longer exist in KDE 5_16.12:
    * removepkg baloo
    * removepkg baloo-widgets

    2nd
    On Slackware 64-bit:
    # upgradepkg –reinstall –install-new x86_64/deps/*.t?z
    # upgradepkg –reinstall –install-new x86_64/deps/telepathy/*.t?z
    # upgradepkg –reinstall –install-new x86_64/kde/*/*.t?z

    3rd
    upgradepkg x86_64/kdei/*.t?z

    4th
    find /etc/ -name “*.new”
    Which finds nothing and the edited file /etc/sddm.conf is gone. I’ve edited back the “HiDPI=false” but now this doesn’t work anymore. SDDM just crashes. /var/log/sddm.log only has
    [10:43:04.580] (II) DAEMON: Display server starting…
    [10:43:04.580] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{c8ab24a1-47ef-4c1c-a3e3-5e6b084f8b5e} -background none -noreset -displayfd 18 vt7
    [10:43:05.665] (II) DAEMON: Running display setup script “/usr/share/sddm/scripts/Xsetup”
    [10:43:05.668] (II) DAEMON: Display server started.
    [10:43:05.668] (II) DAEMON: Socket server starting…
    [10:43:05.668] (II) DAEMON: Socket server started.
    [10:43:05.669] (II) DAEMON: Greeter starting…
    [10:43:05.669] (II) DAEMON: Adding cookie to “/var/run/sddm/{c8ab24a1-47ef-4c1c-a3e3-5e6b084f8b5e}”
    [10:43:05.683] (II) DAEMON: Greeter session started successfully
    [10:43:05.727] (II) DAEMON: Message received from greeter: Connect
    [10:43:19.012] (WW) DAEMON: Signal received: SIGTERM
    [10:43:19.013] (II) DAEMON: Greeter stopping…
    [10:43:19.013] (II) DAEMON: Socket server stopping…
    [10:43:19.013] (II) DAEMON: Socket server stopped.
    [10:43:19.013] (II) DAEMON: Display server stopping…
    [10:43:24.017] (II) DAEMON: Display server stopping…

    Can I go back to KDM?


  4. i have already compiled all latest kde, 😉

    but i have tested your news packages, except telepathy part.

    all work fine here 😉

    a new version of kdeconnect-kde-1.0.2 is available this version seem worked better that the 1.0.0 version, here.


  5. Mikel Nies, I just ran this test:
    I modified my /etc/sddm.conf and then ran “upgradepkg –reinstall” on the sddm-qt5 package. My modification in the /etc/sddm.conf file was still there. As expected, and as previously tested and validated here but I had to be sure. Your installation process is flawed somewhere, even if you say you copied the commands from the README verbatim. Check your command history, perhaps it will shed light on what went wrong.

    If you want KDM back, that is entirely possible. You’ll have to go all the way though: downgrade from Plasma5 to the stock KDE4 of Slackware. There is no KDM in Plasma5. Ever thought of runlevel 3? That still works if your SDDM fails.


  6. Well my commands are copy&pasted and check out in my bash_history. I can’t find an error there. I did make an error editing /etc/sddm.conf so SDDm is working again. My config did get overwritten somehow. And I didn’t have a .new file.
    Copied from my bash_history:

    removepkg baloo
    removepkg baloo-widgets
    cd /home/mikel/Data/alien/new/5
    upgradepkg –reinstall –install-new x86_64/deps/*.t?z
    upgradepkg –reinstall –install-new x86_64/deps/telepathy/*.t?z
    upgradepkg –reinstall –install-new x86_64/kde/*/*.t?z
    upgradepkg x86_64/kdei/*.t?z
    ls /var/log/packages | grep kde-l10n
    ls /var/log/packages | grep l10n
    upgradepkg –install-new x86_64/kdei/kde-l10n-nl-*.t?z
    slackpkg new-config
    find /etc/ -name “*.new”

    I don’t see the error?


  7. just little report the source of plasma are in:

    /kde/src/plasma/plasma/, instead of /kde/src/plasma/

    it seem on all mirrors 😉


  8. Mikel, you did both “slackpkg new-config” and “find /etc/ -name “*.new”. If you finish with the slackpkg command and dealt with every file it proposed, your second command will not find any .new files. My guess is that you told slackpkg to overwrite the existing /etc/sddm.conf file with the .new file.


  9. Gérard yeah I should fix that for the next release. Fortunately the SlackBuild script does not care where these source tarballs are, as long as they are somewhere below ./src …



  10. Dear Eric,

    Thanks for the new year gift. It sounds that “(note that
    there is a dot at the end of these commands!)” in the README is not needed anymore 😉




  11. Bravo Eric! So far, all seems well from your end. I see I’ve a /home drive about to die on me, and THIS likely is what’s plagued my system for a week or so. Once I rid myself of it, I can tell you more if there is need to.


  12. Eric,
    First, thank you very much for all your efforts around Slackware and Plasma 5 in particular.

    I followed your instructions on upgrading from 5_16.11, but upon rebooting, Kleopatra throws the following error:

    “The version of the GpgME library you are running against is older than the one that the GpgME++ library was built against.
    Kleopatra will not function in this setting.
    Please ask your administrator for help in resolving this issue.”

    I have verified that I have the correct gpgme-1.7.1-x86_64-1alien and gpgmepp-16.08.3-x86_64-1alien from this release.

    Any thoughts or assistance is most appreciated!


  13. I had no new files either, using “slackpkg new-config”. I upgraded from -current though, with no previous plasma installed. Everything seems to work after running xwmconfig, although I have to find a theme I like. This thing is fugly out of the box. I wonder if keramic is still available? Off to search something to look at – and
    Thanks Eric!


  14. Just upgraded on my Toshiba laptop from KDE 5_16.11. Looks ok, shutdown process is at least five times faster. Some plasmoid widgets still doesn’t work.


  15. One other thing since I seem to be brain-dead. How do I configure slackpkg+ to exclude upgrading kde? In PKGS PRIORITY I put alien-kde:.* I must be forgetting something…..



  16. I believe this all the relevant part. What happens is after I set the config, I issued “slackpkg update”. Next, I issued “slackpkg upgrade-all”. It shows all of Slackware’s kde to be upgraded. It really should show nothing?


  17. It should not show all the Slackware KDE packages as candidates for upgrade. Again, if you do not share your slackpkgplus.conf I can not give you a useful anwer.


  18. I had it on the clipboard……looks like I forgot the important part.

    # Configuration for slackpkg+. See /usr/doc/slackpkg+-*/README for more details

    # Enable (on) / Disable (off) slackpkg+
    SLACKPKGPLUS=on

    # set to \’0\’ to never show the download progress bar
    # set to \’1\’ to show the bar only in download packages (default)
    # set to \’2\’ to always show the download bar
    # set to \’3\’ for a debug mode
    VERBOSE=1

    # By default slackpkg+ deny to install 32bit packages.
    #
    # Set this flag to \’on\’ allow slackpkg+ to install 32bit packages on a 64bit slackware
    # installation (possibly unsafe). Please, do not install both 32 and 64bit of the same
    # package to avoid problems, and NEVER upgrade existant 64bit packages with relative 32bit package.
    # Do not forget to install the multilibs.
    ALLOW32BIT=off

    # Enable (1) / Disable (0) the official slackpkg blacklist. May be useful to temporarily skip
    # the slackware blacklist. You can also override it from command line:
    # \’USEBL=0 slackpkg upgrade-all\’
    USEBL=1

    # Add custom option to \’wget\’.
    # You can solve the repository indisponibility issue by set a timeout here
    WGETOPTS=\”–timeout=20 –tries=2\”

    # If you want replace wget with another downloader search DOWNLOADCMD in documentation
    # at /usr/doc/slackpkg+-*/README
    #DOWNLOADCMD=\”wget -O\”

    # Use the cache for metadata files (CHECKSUMS.md5,…). Enable it (on) to speedup the slackpkg update
    # process by downloading just new files (see README). Disabled by default (off)
    CACHEUPDATE=off

    # You can download-only by setting DOWNLOADONLY to \’on\’. You may (you should) also use it in commandline
    # for example: \”DOWNLOADONLY=on slackpkg upgrade-all\”. Useful for large upgrades.
    #DOWNLOADONLY=off

    # Enable (on) / Disable (off) notification events (see notifymsg.conf)
    #ENABLENOTIFY=off

    # Enable (on) / Disable (off) the greylist feature. See /etc/slackpkg/greylist
    GREYLIST=on

    # Defines if commands \’search\’ and \’file-search\’ are case-sensitive (on) or not (off). Default to \”on\”
    SENSITIVE_SEARCH=on

    # Select the show order in dialogbox. Available \”package\” \”repository\” \”tag\” \”path\” \”arch\”
    SHOWORDER=package

    # If two or more repositories contains some same packages, you can specify
    # from which repository you prefer to search it.
    # The syntax is \”:\”
    # Accepts regular expressions. To give priority to an entire repository use \”\”

    # Examples:
    #PKGS_PRIORITY=( restricted:vlc )
    # OR
    #PKGS_PRIORITY=( myrepo )
    #
    # if you have two reporitories to give priority you must set both in the same line
    #PKGS_PRIORITY=( myrepo restricted:vlc )
    #
    # if you want to install \’ktown\’ repository you must set it here
    PKGS_PRIORITY=( alien-kde:.* )
    # and DO NOT MISS to read special instruction on /usr/doc/slackpkg+-*/repositories.txt
    #
    # If you want a multilib system, uncomment the multilib repository and set:
    #PKGS_PRIORITY=( multilib )
    #
    # (Use /usr/doc/slackpkg+-*/setupmultilib.sh to setup a multilib configuration)
    #
    # For both multilib and ktown set
    PKGS_PRIORITY=( restricted:vlc )

    # Otherwise you can try to upgrade a package from a repository that contains a package with the
    # same tag of the already installed package. Tipically that means to upgrade a package from the
    # same author of the already installed package.
    # Note that this method may not works properly where two repositories contains a package with the
    # same tag.
    # Set TAG_PRIORITY to \’on\’ to enable this function
    TAG_PRIORITY=off

    # List repositories you want to use (defined below)
    # remember to launch \’slackpkg update\’ if you modify that row.
    REPOPLUS=( slackpkgplus restricted alienbob alien-kde )

    # Define mirrors (uncomment one or more mirror; remember to add it to REPOPLUS)
    # GPG Note: after adding a repository, you must to run \’slackpkg update gpg\’
    # some repositories as salixos or slackel, have a partial GPG support;
    # for that repositories you may need to run slackpkg with \’slackpkg -checkgpg=off …\’

    # Slackware 14.2 – x86_64
    #MIRRORPLUS[\’multilib\’]=http://bear.alienbase.nl/mirrors/people/alien/multilib/current/
    MIRRORPLUS[\’alienbob\’]=http://bear.alienbase.nl/mirrors/people/alien/sbrepos/current/x86_64/
    MIRRORPLUS[\’alien-kde\’]=http://bear.alienbase.nl/mirrors/alien-kde/current/5/x86_64/
    MIRRORPLUS[\’restricted\’]=http://bear.alienbase.nl/mirrors/people/alien/restricted_sbrepos/current/x86_64/
    #MIRRORPLUS[\’slacky\’]=http://repository.slacky.eu/slackware64-14.1/

    # use this to keep the slackpkg+ package updated
    MIRRORPLUS[\’slackpkgplus\’]=http://slakfinder.org/slackpkg+/

    # Slackware current – x86_64
    #MIRRORPLUS[\’multilib\’]=http://bear.alienbase.nl/mirrors/people/alien/multilib/current/

    # Local repository:
    #MIRRORPLUS[\’alienbob\’]=file://repositories/alien/sbrepos/14.1/x86/
    #
    # Local packages (you do not need metadata nor \’slackpkg update\’ command):
    #MIRRORPLUS[\’myrepo\’]=dir://repositories/mypackages/

    #
    # Supported Repositories (see /usr/doc/slackpkg+-* for details and notes):
    #

    #Supports GPG
    #slackpkgplus: http://slakfinder.org/slackpkg+/
    #multilib: http://bear.alienbase.nl/mirrors/people/alien/multilib/{13.37,14.0,14.1,current}/
    #alienbob: http://bear.alienbase.nl/mirrors/people/alien/sbrepos/{13.37,14.0,14.1,current}/{x86,x86_64}/
    #ktown: http://bear.alienbase.nl/mirrors/alien-kde/{13.37,14.0,14.1,current}/{latest,testing}/{x86,x86_64}/
    #restricted: http://bear.alienbase.nl/mirrors/people/alien/restricted_sbrepos/{13.37,14.0,14.1,current}/{x86,x86_64}/
    #slacky: http://repository.slacky.eu/slackware{,64}-{13.37,14.0,14.1}/
    #mleddesktop: http://www.microlinux.fr/microlinux/desktop-{14.1,14.2}-{32,64}bit/
    #mledextras: http://www.microlinux.fr/microlinux/extras-{14.1,14.2}-{32,64}bit/
    #mles: http://www.microlinux.fr/microlinux/server-{14.0,14.1,14.2}-{32,64}bit/
    #msb: http://slackware.org.uk/msb/{14.0,14.1,testing}/{1.6,1.8,1.10,1.12}/{x86,x86_64}/
    #slackers: http://ponce.cc/slackers/repository/
    #slacke18: http://ngc891.blogdns.net/pub/slacke18/slackware{,64,arm}-14.1/
    #studioware: http://studioware.org/files/packages/slackware{,64}-{13.37,14.0,14.1}/
    #slackonly: http://packages.slackonly.com/pub/packages/{14.1,current}-{x86,x86_64}/
    #rlworkman: http://rlworkman.net/pkgs/{13.37,14.0,14.1,current}/
    #slackel: http://www.slackel.gr/repo/{i486,x86_64}/{current,kde5}/
    #
    #Does NOT support GPG
    #salixos(*): http://download.salixos.org/{i486,x86_64}/{13.37,14.0,14.1}/


  19. Hallo Eric,
    same Tyler C. Hayward’s issue:
    “The version of the GpgME library you are running against is older than the one that the GpgME++ library was built against.
    Kleopatra will not function in this setting.
    Please ask your administrator for help in resolving this issue.”

    Notwithstanding correct packages installed.

    Any hints?
    Thanks


  20. You have defined PKGS_PRIORITY twice, and I assume that the second occurrence is overruling the first:

    PKGS_PRIORITY=( alien-kde:.* )
    PKGS_PRIORITY=( restricted:vlc )

    Please: next time, try to NOT paste all the irrelevant comments but leave just the relevant lines… makes your post smaller and this page a lot easier to read.



  21. That did the trick Eric, thanks!
    Sorry about the full paste….:(
    I still had to look hard to find the two instances. Good grief…..



  22. Dear Eric,

    I’ve been following your epic KDE achievements since KDE 4 (while stock -current was 4.7~8 or so).

    Well, I moved out from the previous KDE WM and have been using awesome WM for the last year and half. Nonetheless I always kept my eye on your Ktown adventures.

    Today I moved from my previous KDE 4.14 to your brand new KDE 5_16.12. Apart from some glitches because the mix between awesome WM and KDE itself and other minor config stuff, it was a pretty smooth path.

    So I’m here just to tell you this: I’m always amazed by your organizational methods, precise wording and technical description for documentation matters and the high quality of the products you deliver. But this time you had exceeded yourself. Ktown is greatest then it already was before!

    Thank you for your work. Pat and the whole Slackware community is going to receive a rock solid KDE 5 when its time arrive.




  23. Just an fyi session selection doesn’t work for me in sddm if I select the elarun theme. Works fine with the maldives theme & the background is easily changed just edit /usr/share/sddm/themes/maldives/theme.conf or create /usr/share/sddm/themes/maldives/theme.conf.user and customize there (untested by me)

    As always big thanks to Alien Bob for doing all the hard work so I don’t have to 🙂


  24. Eric, I noticed your Slackbuild directory for gpgme contains the src for both 1.7.1 and 1.8.0, which version was gpgmepp compiled against? I am trying to build my own package to figure out where the problem lies.


  25. I originally tried with gpgme 1.8.0 but that version is broken, and even with the patch I tried (it’s also in that same source location under ./patches/) there were issues. Other distros report the same thing so everyone sticks with 1.7.1. Therefore I built my package using 1.7.1.



  26. Telegram doesn’t work:
    I can add account, but when trying to Go Online I get:
    There was a problem while trying to connect – An unknown error was encountered (org.freedesktop.DBus.Error.Failed), please report this



  27. Thanks Eric, it was me who asked it. No problem here, maybe it will work in further versions. I wonder if it works in current KDE neon though..


  28. I did try telepathy with telegram yesterday. It connected and at first nothing seemed to work. Anyway after a while it somehow syncronized with the previous status of the various chats I had and it has worked. Anyway I found it disappointing because it lacks many features in current status. So I’m back to Pidgin + purple-telegram for desktop usage.


  29. I have downloaded the file slackware64-live-plasma5-current.iso and recorded on a DVD, started correctly on my 64bit machine and asks me for a password … for more that I searched on your blog I can not find any reference .. .. ???
    Is it okay for a Live to ask for a password?



  30. Hi eric!

    After kde plasma updated, the panel always lag when opened more application. For running back i always run \”alt+f2\” then type kill plasmashell and run again plasmashell &.

    In earlier, i was rebuilt qt5 and nothing.



  31. Tony, if you are using slackpkg and have Plasma 5 packages installed, you will have to do one of two things:
    (1) blacklist my packages in the /etc/slackpkg/blacklist
    (2) install slackpkg+ and configure it to use my ‘ktown’ repository.
    If you do not pick either of these two options, then slackpkg will always give higher priority to an official Slackware package if you have a 3rd-party package with the same name installed.




  32. @Gerard & alienbob

    So is it enough to recompile only qt5 in order to run with current from Jan. 18? Pat has recompiled quite a few kde4 packages.
    Thanks.


  33. Strange problem with this Plasma5 set and with older set. Sometimes there is somehow generated file qt.conf in directory /usr/bin and plasma wont start. After deletions of this file everything is normal. Still didn’t noticed why and when this file is generated. At this moment it looks like very random.



  34. Hey Eric,

    I just rsync’d your Plasma 5 packages from “bear” and ran a checksum test on them. I got two errors;

    ./kde/applications-extra/ktorrent-5.0.1-x86_64-1alien.txz.asc: FAILED
    ./kde/applications-extra/libktorrent-2.0.1-x86_64-1alien.txz.asc: FAILED

    So I tried from slackware.uk and got the same errors.


  35. Hi Skaendo

    I’ll generate new CHECKSUMS.md5 when I upload new packages. That will probably be around the weekend, if I can fix my issues with the new Applications 16.12.x.

    The two .asc files themselves are OK by the way. It’s just their md5 checksums that are incorrect. So, slackpkg’s GPG signature check will not fail.



  36. Yea, I figured it was just something silly like that. Just thought that I’d give you a heads-up.

    Thanks for making sure.


Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.