Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Slackware - Installation This forum is for the discussion of installation issues with Slackware.


  Search this Thread
Old 06-10-2015, 09:57 AM   #16
LQ Guru
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,330

Rep: Reputation: 5042Reputation: 5042Reputation: 5042Reputation: 5042Reputation: 5042Reputation: 5042Reputation: 5042Reputation: 5042Reputation: 5042Reputation: 5042Reputation: 5042

Originally Posted by mfoley View Post
Is there no way to force a reinstallation/update of every package?
Easiest way I can think of is to mount the Slackware DVD (or DVD iso) to a directory and then just run upgradepkg --reinstall --install-new /location/to/slackware-dvd/slackware64/*/*.txz. Once this is done, you should have all the stock packages reinstalled. Then, hopefully, it should just be a matter of using slackpkg to update the system to get the latest packages.

Keep in mind, since you showed multiple openssl packages (and there's the possibility other packages had multiple versions installed), you may end up with files that belong to no recognized package. This may or may not cause problems when compiling software that relies on those packages.

You may also be able to reinstall everything with slackpkg, but as I said before, I'm not too familiar with the program. You might be able to do it with one of the below commands (since /var/log/packages was cleared, it might require the "install" option instead of the "reinstall"):

slackpkg install slackware64
slackpkg reinstall slackware64
Good luck!
Old 06-15-2015, 10:52 PM   #17
Senior Member
Registered: May 2015
Location: Utah, USA
Distribution: Slackware, OpenBSD
Posts: 1,442

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
Originally Posted by mfoley View Post
> slackpkg info openssl

PACKAGE NAME: openssl-1.0.1m-x86_64-1_slack14.1.txz
PACKAGE LOCATION: ./patches/packages
PACKAGE SIZE (compressed): 2912 K
PACKAGE SIZE (uncompressed): 13070 K

PACKAGE NAME: openssl-1.0.1e-x86_64-1.txz
PACKAGE LOCATION: ./slackware64/n
PACKAGE SIZE (compressed): 2844 K
PACKAGE SIZE (uncompressed): 12670 K
If you notice the package location of each openssl package you will see that one is a patch and the other is the full package that had been patched. slackpkg will list all packages you query as well as their subsequent patches. You were mistaken not to read the path of the package in the output.

The following will show all packages and patches for the system.
slackpkg info openssl
The command you should be using with slackpkg to see what is installed / upgraded / uninstalled are:
slackpkg search openssl
If you cannot find the package by that name for whatever reason, then there is the 'file-search' option. This option will list the packages, related packages, and any other packages with files or dependencies related to that string query.
slackpkg file-search openssl
I suppose though the point is moot now. If you deleted all those files you mentioned and pkgtool is missing, you have bigger problems!

OK, I'm cleaning out /var/lib/slackpkg/ /var/log/packages and /var/log/scripts/, removing /tmp/slackpkg.* and starting from absolute scratch. For postmortem analysis I changed /etc/slackpkg.conf to set DELALL=off (don't delete files after installing) and DOWNLOAD_ALL=off (to install as it goes instead of waiting until the end).
1 00:11:29 root@webserver:~
> pkgtool
-su: pkgtool: command not found
1 00:11:35 root@webserver:~
> find / -xdev -name pkgtool
1 00:11:45 root@webserver:~
You should have checked your PATH variable as well as used the which command like so:
root@exitstatusone:~# which pkgtool
Old 06-15-2015, 11:03 PM   #18
Registered: Aug 2014
Location: Orestiada, GR
Distribution: Slackware 14.1 x86_64 -stable
Posts: 145

Rep: Reputation: 31
As I mentioned above shalt taste the slpkg? if you do not then fine.
Old 06-17-2015, 05:28 PM   #19
Senior Member
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,789

Original Poster
Rep: Reputation: 139Reputation: 139
I think I've figured out what went wrong. I cleaned out everything I could find with slackpkg logs, downloads, etc. Started `slackpkg update`, which did download a bunch of stuff. Then `slackpkg ugrade-all`, but at the end of that, I still had my old programs; e.g. openssl 1.0.1e, not 1.0.1m.

So, I tried hand-upgrading. That worked for openssl and for samba (4.1.0 -> 4.1.17), but after upgrading httpd from 2.4.6 to 2.4.12 I got "httpd: symbol lookup error: httpd: undefined symbol: apr_table_getm". So did `slackpkg install apr` which did upgrade that package, but httpd then gave an undenfied symbol error with mod_proxy. I couldn't find a way to upgrade httpd modules (the install of the new httpd didn't do it), so I restored everything from before I started messing, upgraded openssl and samba and left it at that.

Later, I installed Slackware 64 4.1 on a completely different computer from the same DVD. I did the `slackpkg update` and `slackpkg upgrade-all` (it ran for about 20 hours!) and everything upgraded just fine.

What I think happened was that after installing the 1st system and before doing the upgrades, I restored production directories from the original backup (this was an update of an existing system). Those directories included /var/log and /root which hold slackpkg info. I apparently clobbered enough config stuff that slackpkg was hopelessly lost. A lesson for next time!

What would be really nice would be a `slacpkg reset-all` that would put things back to the as-installed state, because restores happen! Or even a `slackpgk discover-all` which would examine all the packages and correct the package archives depending on the actual version installed.

Last edited by mfoley; 06-17-2015 at 05:32 PM.
Old 06-19-2015, 08:32 AM   #20
Alien Bob
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,133

Rep: Reputation: 6994Reputation: 6994Reputation: 6994Reputation: 6994Reputation: 6994Reputation: 6994Reputation: 6994Reputation: 6994Reputation: 6994Reputation: 6994Reputation: 6994
If you overwrite /var/log/packages and /var/log/scripts with backups from other computers, then there is nothing you can do to fix that. These directories can not be re-populated from your computer's content.
It's no different when you kill a RPM database on a Redhat machine by the way.
Be more careful with the package database next time.



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
Errors while updating with slackpkg aaditya Slackware 2 12-31-2013 04:11 AM
Updating packages w/out Slackpkg Konphine Slackware 4 09-25-2011 02:40 PM
slackpkg clean-system njb Slackware 1 08-02-2010 12:13 PM
Slackpkg updating not able to connect foolio1990 Linux - Newbie 2 09-04-2008 10:48 PM
Updating to -current with slackpkg macbeth8 Slackware 8 04-04-2008 07:14 PM > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation

All times are GMT -5. The time now is 12:44 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