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

Notices

Reply
 
Search this Thread
Old 10-15-2013, 04:10 PM   #1
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,478

Rep: Reputation: Disabled
upgrade from 13.37


Hi all,

Getting excited about the imminent release...

If I remember, in the past it was recommended to do progressive upgrades and not skip a version. I usually use slackpkg to upgrade. Assuming I do slackpkg clean-system at the end, is there any reason not to upgrade directly to 14.1 from 13.37?

Brian
 
Old 10-15-2013, 04:15 PM   #2
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,359

Rep: Reputation: 184Reputation: 184
I tried it just recently on a system and started getting errors not very long into the install. Don't remember what the error was, something about ild or ld not for sure what it was. I used the option to download all files before installing. On the second try, I followed the upgrade to 14 text to upgrade from 13.37 to current and still got same error.

Last edited by colorpurple21859; 10-15-2013 at 04:16 PM.
 
Old 10-15-2013, 04:21 PM   #3
Habitual
Senior Member
 
Registered: Jan 2011
Distribution: Undecided
Posts: 3,577
Blog Entries: 1

Rep: Reputation: Disabled
http://alien.slackbook.org/blog/local-slackware-mirror/
 
Old 10-15-2013, 07:45 PM   #4
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,478

Original Poster
Rep: Reputation: Disabled
@colorpurple - So you got the errors even though you did incremental upgrades? Did the upgrade ever complete?

@Habitual - I couldn't find in the link where he addresses my questions

Brian
 
Old 10-15-2013, 08:10 PM   #5
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,359

Rep: Reputation: 184Reputation: 184
I had 13.7 on vmware and tried to do an upgrade straight to current, skipping 14 with slackpkg update, slackpkg installnew, slackpkg upgradeall. walked away while it was downloading everthing, came back and was getting errors during the installs. Then tried it again 13.37 to current skipping 14, but following the upgrade.txt that was provided to upgrade to 14. Still got the errors. Now I think about it I was tired so I might have missed one of the preliminary installs before installing everything else, but not sure.

Last edited by colorpurple21859; 10-15-2013 at 08:13 PM.
 
Old 10-16-2013, 12:06 AM   #6
number22
Member
 
Registered: Sep 2006
Location: Earth
Distribution: Slackware 14.1 Slackware64-current multilib
Posts: 195
Blog Entries: 2

Rep: Reputation: Disabled
I wrote a blog how to upgrade from early version to current, check it out, beware, you will missing some libraries, which you have to manually download from L directory and install these libraries.

Basically, need upgrade kernel first, then you wouldn't get old kernel panic problem, then you need manually build and upgrade lilo, mkinitrd, so you can use new kernel.

I wrote the blog for 64bit, making changes the directory if you are using 32bit. (note: you might need to rebuild udev package after full upgrade.)

Good luck.

Last edited by number22; 10-16-2013 at 12:27 AM.
 
1 members found this post helpful.
Old 10-16-2013, 12:48 AM   #7
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,658
Blog Entries: 3

Rep: Reputation: 222Reputation: 222Reputation: 222
13.37 to 14.0 was some huge changes in kde etc etc. if you upgrade from slackpkg I always do an install-new first then upgrade all.
but if you did it from UPGRADE.TXT it should be ok. this little script has helped me many times when working with current and rolling back to a earlier version

Quote:
#!/bin/sh
for dir in a ap d e f k kde l n t tcl x xap xfce y ; do
( cd $dir ; upgradepkg --install-new *.t?z )
done
 
Old 10-16-2013, 06:02 AM   #8
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,334

Rep: Reputation: Disabled
FYI, using slackpkg for upgrades will only work if you upgrade to the next release and do not skip a release.

When you run "slackpkg install-new" in order to install packages which have been added to Slackware since the previous release, slackpkg will check the ChangeLog.txt of that release for lines that have the string "Added." in them. If you skip a release, then any package that was added to Slackware in that skipped release, will not get installed on your computer. That is a recipe for disaster.

If you want to skip one or more releases, you will have to do so manually, using the instructions from UPGRADE.TXT of your new Slackware release as well as the UPGRADE.TXT files of the skipped release(s).
But you might consider doing a full re-install from scratch instead.

Eric
 
5 members found this post helpful.
Old 10-16-2013, 06:36 AM   #9
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,359

Rep: Reputation: 184Reputation: 184
Played around with it last night on vmware. I got it to install with upgrading kernels, lilo, rerunning lilo and rebooting to use new kernels before installing a/glibc-solibs. Installed everything else without error. When I went to reboot started to get errors about modprobe.d and wasn't able to reconnect to internet. I only had a, ap, l, n installed. I suspect the problems was caused by the install-new issues mentioned by Alien Bob

Last edited by colorpurple21859; 10-16-2013 at 06:39 AM.
 
Old 10-16-2013, 08:08 AM   #10
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,486

Rep: Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856
@Alien Bob
Thanks for the description of the pitfall in post #8.
Perhaps this could be made more explicit in your article at SlackDocs. http://docs.slackware.com/howtos:sla...:systemupgrade
This is going to get a heavy workout in the near future.
 
Old 10-16-2013, 09:19 AM   #11
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,478

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Alien Bob View Post
When you run "slackpkg install-new" in order to install packages which have been added to Slackware since the previous release, slackpkg will check the ChangeLog.txt of that release for lines that have the string "Added." in them. If you skip a release, then any package that was added to Slackware in that skipped release, will not get installed on your computer. That is a recipe for disaster.
That's exactly what I wanted to know. Makes perfect sense.

Thanks, Brian

PS And thanks to everyone else who took the time to reply.
 
Old 10-16-2013, 10:32 AM   #12
GazL
Senior Member
 
Registered: May 2008
Posts: 3,481

Rep: Reputation: 1016Reputation: 1016Reputation: 1016Reputation: 1016Reputation: 1016Reputation: 1016Reputation: 1016Reputation: 1016
I wrote a script that compares available package files with installed packages rather than trying to parse the Changelog like slackpkg does but it only works with packages stored on your local filesystem, so you'd need a local mirror of the slackware packages to use it. Works really well for me, but I know not everyone likes to keep a local mirror (which IMO is short-sighted as it's a handful of GB well spent and has saved my bacon numerous times).
 
Old 10-16-2013, 11:17 AM   #13
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,896

Rep: Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952
Quote:
Originally Posted by GazL View Post
I wrote a script that compares available package files with installed packages
You mean something like this?

Code:
diff <(sed -nr 's/^PACKAGE NAME:  ([[:graph:]]+)(-[[:alnum:]\.\+_]+){3}.t.z$/\1/p' PACKAGES.TXT | sort) <(ls /var/log/packages | sed -nr 's/^([[:graph:]]+)(-[[:alnum:]\.\+_]+){3}$/\1/p' | sort)
Note: I am assuming bash and that PACKAGES.TXT is in the current working directory.
 
Old 10-16-2013, 11:20 AM   #14
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,896

Rep: Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952
You could also pipe the result of that through "grep '^>'" to see a list of just the non-official packages you have installed or "grep '^<'" just to see the official packages you are missing.

Last edited by ruario; 10-16-2013 at 11:21 AM.
 
Old 10-16-2013, 12:43 PM   #15
GazL
Senior Member
 
Registered: May 2008
Posts: 3,481

Rep: Reputation: 1016Reputation: 1016Reputation: 1016Reputation: 1016Reputation: 1016Reputation: 1016Reputation: 1016Reputation: 1016
Quote:
Originally Posted by ruario View Post
You mean something like this?
Not exactly, it was a bit more involved than that and allows for multiple package sources without reading any meta-data files.

I posted this once before, but nobody seemed interested.


P.S.

I usually use it like this (though this doesn't cater for any ordering requirements):
Code:
while read package
do
  gpg --verify $package.asc $package && upgradepkg --install-new $package
done < <( slacklist upgrade install | sort)

slacklist remove | xargs -r -- removepkg

Last edited by GazL; 05-23-2014 at 12:50 PM.
 
2 members found this post helpful.
  


Reply


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
Upgrade and dist-upgrade problem reinstall aMule end packare libupnp6 anunix Debian 2 05-12-2012 02:36 PM
Upgrade and dist-upgrade problem reinstall aMule end packare libupnp6 anunix Debian 1 05-12-2012 10:06 AM
How to upgrade kernel in rhel6/centos6 with internet. manually download and upgrade. Gil@LQ Linux - Kernel 3 03-12-2012 06:07 PM
Partial Upgrade of BIG NEW KDE UPGRADE (debsig-verify related?) linuxStudent11 Debian 1 04-27-2011 01:29 PM
Will 'aptitude upgrade or dist-upgrade' downgrade manually installed deb package? Akhran Debian 3 03-14-2006 03:40 PM


All times are GMT -5. The time now is 07:32 AM.

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