Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


Search this Thread
Old 11-08-2013, 09:11 AM   #1
Registered: Jan 2009
Distribution: Slackware 14.1
Posts: 328

Rep: Reputation: 56
Upgrading via slackpkg

Hi all, like the rest of us I'm looking forward to updating to the new release. I have a few questions about the process though. UPGRADE.TXT has instructions that involve the use of a CD, or otherwise having the packages local on your system. I would prefer to use slackpkg if possible, and I feel like I've upgraded this way in the past... I think from 13.0 to 13.37. However, when I upgraded from 13.37 to 14.0 this way my machine wouldn't boot afterward, and I ended up doing a fresh install.

I'm also multilib, and the instructions in UPGRADE.TXT don't seem to account for that. I seem to recall reading that upgrading multilib systems needs to be done with care.

I think there are instructions for this on, but it seems to be either down or very slow right now.

So, can I upgrade via slackpkg by simply changing the mirror from 14.0 to 14.1? If so, why doesn't UPGRADE.TXT say so? It seems to be a lot more convenient to upgrade this way, rather than using a CD.

Old 11-08-2013, 09:14 AM   #2
Registered: Jun 2013
Location: Germany
Distribution: Slackware
Posts: 144

Rep: Reputation: Disabled
also one should think about people how simply dont have a cd/dvd/bd drive and cant get one too.

just for the record.
Old 11-08-2013, 09:30 AM   #3
Senior Member
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 137Reputation: 137
I upgraded using the dvd (minus KDE) by following the upgrade.txt, then updated multi-lib and KDE using slackpkg+ and modifying the mirror in /etc/slackpkg/mirrors.conf and the repos in
/etc/slackpkg/slackpkgplus.conf to 14.1 for most of them but current for ktown and then left the machine running overnight. All I had to do was install the new version of the nvidia driver and tweak a bit.

Old 11-08-2013, 10:51 AM   #4
Senior Member
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,756

Rep: Reputation: 528Reputation: 528Reputation: 528Reputation: 528Reputation: 528Reputation: 528
You can use slackpkg to upgrade between versions
I upgraded my server from 12.2 incrementally to 14.0 using slackpkg and i'm planning to upgrade to slackware 14.1 soon

I personally use these common steps
Point to slackware 14.1 mirror
slackpkg update
slackpkg install-new (look at CHANGES_AND_HINTS)
slackpkg upgrade-all
slackpkg clean-system

It would be better if you have a local repository
3 members found this post helpful.
Old 11-08-2013, 12:09 PM   #5
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,216

Rep: Reputation: 294Reputation: 294Reputation: 294

In addition to Willysr's way I usually upgrade slackpkg itself before those steps. That will stop slackpkg stopping in the middle and asking you to run slackpkg update again. So my steps + Willysr's:

Edit mirrors file.
slackpkg update
slackpkg upgrade slackpkg
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system

I have so far done 4 chroots like this. I have two multilib hosts to do yet though (probably saturday) and this will be the first time I've had to do this on a multilib system so I've no real plan in mind yet. What I will probably do is backup my slackpkg blacklist file and remove all the multilib/sbo stuff on it ([0-9]+_SBo and [0-9]+alien) and anything else that needs taking out. Then I will follow the steps above to install the pure 64bit system, then run my multilib script to install alienBob's multilib stuff (script below) and then add back in the blacklisted stuff from above. Hopefully, that should work ok.

My multilib rsync/install script:


set -e 


rsync -ruhv --progress --exclude=debug/ --include=*/ --include=*t?z \
--delete --exclude=* $URL ./

upgradepkg --reinstall --install-new *.t?z
upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z
WARNING! Create a multilib directory for this to run in first and run the script inside it or you'll kill your $HOME.
3 members found this post helpful.
Old 11-08-2013, 12:16 PM   #6
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Whatever fits the task best
Posts: 16,250
Blog Entries: 2

Rep: Reputation: 4445Reputation: 4445Reputation: 4445Reputation: 4445Reputation: 4445Reputation: 4445Reputation: 4445Reputation: 4445Reputation: 4445Reputation: 4445Reputation: 4445
It is indeed recommended to upgrade slackpkg first, since there were changes made in the default options. Without the changed options (in this case the important one is "DOWNLOAD_ALL", which is now set to on by default) your wget will break during the upgrade process, making it impossible to do further upgrades without having a local package repository (or the DVD, which is basically the same).
Don't forget that you have to upgrade your multilib, too. It is, thanks to zerouno and phenixia2003, exceptionally easy to install and maintain multilib (and other repositories) with the slackpkg+ plugin.

Last edited by TobiSGD; 11-10-2013 at 05:02 PM. Reason: added missing credits
1 members found this post helpful.
Old 11-08-2013, 12:29 PM   #7
Registered: Jan 2009
Distribution: Slackware 14.1
Posts: 328

Original Poster
Rep: Reputation: 56
Thanks for the tips everyone, I'll likely start updating my machines over the weekend. What about the kernel? Step 7 of UPGRADE.TXT seems pretty important...
Old 11-08-2013, 12:33 PM   #8
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,216

Rep: Reputation: 294Reputation: 294Reputation: 294
Originally Posted by mattca View Post
What about the kernel? Step 7 of UPGRADE.TXT seems pretty important...
Edit your lilo config (/etc/lilo.conf) to point to the new kernel (check /boot to find the new version) before running lilo.

The first 5 paragraphs of step 7 are for people using an initrd. More info here:

Last edited by dive; 11-08-2013 at 12:36 PM.
1 members found this post helpful.
Old 11-10-2013, 12:09 PM   #9
Registered: Dec 2002
Distribution: slackware!
Posts: 278

Rep: Reputation: 31
upgraded 32/64 following mentioned suggestions, everything is working good, thank you
Old 11-10-2013, 12:16 PM   #10
Senior Member
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware
Posts: 4,521

Rep: Reputation: 692Reputation: 692Reputation: 692Reputation: 692Reputation: 692Reputation: 692
Further to willysr's excellent post I also run slackpkg update gpg just prior to running slackpkg update.


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] Slackpkg .... download updates first before upgrading? barry_lamb Slackware 2 04-02-2013 12:17 PM
[SOLVED] slackpkg upgrade...not upgrading :-( the_penguinator Slackware 3 03-24-2010 07:14 PM
After upgrading with latest slackpkg samac Slackware 2 09-12-2009 06:12 AM
Upgrading glibc 2.3.4 -> 2.3.6 with slackpkg kuitang Slackware 3 03-13-2006 06:36 PM
upgrading the kernel using slackpkg cavalier Slackware 17 05-27-2005 05:54 PM

All times are GMT -5. The time now is 01:47 AM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration