Share your knowledge at the LQ Wiki.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 09-13-2016, 12:05 PM   #1
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2 XDM_Themes/WMaker
Posts: 736

Rep: Reputation: 229Reputation: 229Reputation: 229
Liveslak 1.1.3 slackpkgplus configuration updates for 14.2, block downgrades and fix kmail.

I've installed liveslack 1.1.3 to my LUKS/LVM hard drive. My understanding from AlienBob's blog is that 1.1.3 has 14.2 plus special builds for latest glib and gcc, as well as PLASMA5 with latest ktown. The DVD ran wonderfully was fast and stable. PLASMA5 looks modern and snappy. The install on my HD was fast and stable. I then proceeded to update my installation for security patches. So I examined Slackpkgplus.conf it is pointed to current and not 14.2. I re-set the slackpkgplus.conf to point at 14.2 repositories and then updated to the latest patches and PLASMA5 ktown (latest) updates (all were version upgrades from previous version installed). Slackpkg update also wanted to downgrade many apps to slackware64 versions which I rejected. Unfortunately the result is kmail is crashing when attempting to create an account with deny kwallet password storing.

Have I done something essentially wrong when changing slackpkgplus to point to 14.2 rather than current? Or is this a bug with setting up an account for kmail without kwallet?

Old 09-13-2016, 01:58 PM   #2
Alien Bob
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,477

Rep: Reputation: 7787Reputation: 7787Reputation: 7787Reputation: 7787Reputation: 7787Reputation: 7787Reputation: 7787Reputation: 7787Reputation: 7787Reputation: 7787Reputation: 7787
From the liveslak ISO release README:
== Slackware Live Edition ==

22-Aug-2016: 1.1.3.
  ISOs based on slackware64-current "Thu Aug 11 18:24:29 UTC 2016".
  Note: the PLASMA5 ISO contains an experimental setup for testing Wayland.
Installing the content of the Plasma 5 ISO to your hard drive will of course work, and it will perform at least as well as a regular install from the 'ktown' repository.
However, this particular liveslak-1.1.3 ISO contains a testing release of my ktown packages on top of Slackware-current, with mesa, xorg-server and qt5 recompiled against wayland and some other stuff added that is not ready for Slackware (such as elogind, the extracted and standalone version of the'logind' systemd component).

So, when you install this to your harddrive and then configure slackpkg to "upgrade" this installation using Slackware 14.2 repositories, you are on a certain road to disaster. You will probably end up with a Frankenstein mix of Slackware 14.2 and -current packages, and the results of that are undetermined.
1 members found this post helpful.
Old 09-13-2016, 03:00 PM   #3
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2 XDM_Themes/WMaker
Posts: 736

Original Poster
Rep: Reputation: 229Reputation: 229Reputation: 229
Thanks Eric. You've mentioned this twice to me and I didn't catch what you were saying.. i.e. that 1.1.3 is not based on 14.2 but on -current. I must apologize for my blindness!

From your reply it appears that with liveslak 1.1.3 installed the upgrade path is -current only. So I have options, 1) correct my slackpkgplus.conf to -current and upgrade again with extra caution reading all upgrade info/readme's to check for breakage potential or 2.) re-install the stable 14.2. I see from the -current change logs that the kernel changes quite frequently and many packages get updated each week. This means more kernel source, headers, modules, firmware on my "/" drive. IF running -current what is the recommended "/" size to keep up with -current changes prior to next stable release? I recently re-partitioned it to 32G is that enough?

This is my first time running on -current. I've always used stable with 14.1, 14.0 and 13.37. The liveslak "install" was because when I attempted to slackpkg upgrade from 14.1 to 14.2 my system borked with a kernel panic (did check lilo.conf and lilo still kernel panicked after issuing lilo command). I had a copy of the liveslak on DVD and thought "why not use that nifty new instead" which worked cleanly, so I guess I'm now a -current user. I'll have to read-up on how to live on the edge with -current. I've read past posts that indicate running current is NOT risky, IF you know slackware - so I guess I'll have to study more. Any recommendations on what to read to stay safest when running current, excluding this LQ and official change log?


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Could not refresh the list of updates. I tried to fix it but no go L a r r y Linux - Software 7 08-09-2016 07:32 AM
[SOLVED] kmail broken by latest -current updates? pchristy Slackware 2 08-26-2015 01:36 PM
How to fix the software updates on mint 15 mlytle Linux - Software 7 08-02-2014 06:16 PM
Automatic Updates in Suse 11.2 (11.3 too?) fix unassassinable Linux - Desktop 2 11-02-2010 06:34 PM
kmail configuration ??? bigjohn Linux - Software 3 07-25-2003 04:56 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:01 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration