LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices


Reply
  Search this Thread
Old 07-08-2015, 03:52 PM   #1
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,904

Rep: Reputation: 147Reputation: 147
Having trouble upgrading package with slackpkg


Back again with more slackpkg issues ...

I want to update my httpd. I've run `slackpkg update` to get the latest package list. Then I ran `slackpkg search httpd` to see what's available. I got:
Code:
> slackpkg search httpd

Looking for httpd in package list. Please wait... DONE

The list below shows all packages with name matching "httpd".

[  upgrade  ] - httpd-2.4.10-x86_64-1_slack14.1 --> httpd-2.4.12-x86_64-1_slack14.1

You can search specific files using "slackpkg file-search file".
I have 2.4.10 and I want 2.4.12. I've tried:

slackpkg upgrade http

slackpkg upgrade httpd-2.4.12-x86_64-1_slack14.1

Not sure which it right, if either. In both cases I got a list of 78 packages, including samba, openssl, wget, seamonkey, bash, glibc and a raft of others, then the prompt:

"You can (B)lacklist, (R)emove, or (I)gnore these packages."

Selecting "I" terminates the operation. I don't think I really want to blacklist or remove these packages -- they all seem pretty important. I don't know what this list has to do with my desire to upgrade httpd.

Stuck. What should I do?
 
Old 07-08-2015, 04:09 PM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,928

Rep: Reputation: Disabled
It could be that your /var/log/packages directory be seriously messed up, as in this thread as you overwrote it with files coming from another system.

Then as already pointed out by Alien Bob in the previous thread there is nothing you can do to fix that (but reinstalling from scratch, of course).
 
Old 07-08-2015, 04:18 PM   #3
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 14.1, 14.2, current, slackware-arm-currnet
Posts: 5,764

Rep: Reputation: 705Reputation: 705Reputation: 705Reputation: 705Reputation: 705Reputation: 705Reputation: 705
Have ever done a 'slackpkg upgrade-all' since you first installed? If not, that is where to start.

There are four commands to run as root.

1. slackpkg update

2. slackpkg install-new

3. slackpkg upgrade-all

4. slackpkg clean-system

This is a very safe approach, installs all the patches made available that are not installed, and removes anything that is not part of the base system.

Step 4, be careful if you have packages from SBo installed, ( or any other packages ) it will remove them unless you edit /etc/slackpkg/blacklist and blacklist the packages you have added. The file is commented and shows you how to add things from SBo.
 
Old 07-09-2015, 09:46 AM   #4
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,904

Original Poster
Rep: Reputation: 147Reputation: 147
Didier:
Quote:
It could be that your /var/log/packages directory be seriously messed up, as in this thread as you overwrote it with files coming from another system.
This is a different system than the one in my previous post. This one was never overwritten or otherwise messed up. It was a scratch install.

camorri:
Quote:
Have ever done a 'slackpkg upgrade-all' since you first installed? If not, that is where to start.
Yes, This system was built about 6 months ago and I did the procedure you describe at that time. I don't believe I've done any slackpkg on this system since.

So, the consensus is that the slackpkg system is messed up and useless on this computer at this point?
 
Old 07-09-2015, 10:00 AM   #5
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,928

Rep: Reputation: Disabled
What happens then if you try 'slackpkg update' then 'slackpkg upgrade-all'?

You should see a bunch of proposed upgrade: all those listed in the ChangeLog that are more recent that your last upgrade, and that are currently in /patches (of course if a package was upgraded several time you'll get the most recent version only). It's a good idea to accept them all as that are mostly security fixes. Just be careful for kernel upgrades if any: preferably do that manually.
 
Old 07-09-2015, 11:56 AM   #6
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,904

Original Poster
Rep: Reputation: 147Reputation: 147
I'll try that after hours on Friday ... just in case!
 
Old 07-11-2015, 12:05 PM   #7
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware on ARM and Aarch64
Posts: 1,573

Rep: Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892
The slackpkg documentation might be helpful to read as well. Here is a link for your reference:

http://docs.slackware.com/slackware:slackpkg
 
Old 07-13-2015, 12:36 AM   #8
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,904

Original Poster
Rep: Reputation: 147Reputation: 147
Quote:
Originally Posted by Didier Spaier View Post
What happens then if you try 'slackpkg update' then 'slackpkg upgrade-all'?
... Just be careful for kernel upgrades if any: preferably do that manually.
Actually, I'm chickening out from doing the upgrade-all. This is an important production machine and I don't want to risk having to restore everything from backups if something goes wrong with the upgrade.

I've been using slackware for about 15+ years, but just started mucking with slackpkg this year on 14.1. I've used get-apt on Ubuntu/Debian without incident, but I've had a very mixed experience with slackpkg so far -- certainly user error on my part, but on the other hand, I'm not exactly a newbie and things must not be very clear if I'm messing up routinely. I think one problem is mixing slackpkg configs and logs in with directories containing things that are likely to be restored after a scratch build, like /var/log and /root. If the slackpkg stuff were more centralized in its own folder(s), those directories could be easily excluded from the restore.

For years I've simply lived with the CD installation and "upgraded" programs as-needed by downloading and installing the specific tar file. After some period of time, I just scratch-build a new release to get caught up. Given that I'm somehow already messed up with slackpkg, I think I'll stick to that method until the next release and I'll try slackpkg again then.

mralk3: Thanks for the link, but doesn't shed much new light over the man pages. Nowhere does it provide any insight on the "(B)lacklist, (R)emove, or (I)gnore" message when running slackpkg upgrade

Last edited by mfoley; 07-13-2015 at 12:39 AM.
 
Old 07-13-2015, 07:57 AM   #9
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,268

Rep: Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859
If you do upgrade-all, it will still present you with a dialog box asking which updates you'd like to install (in Slackware fasion, it pays no attention to version numbers and just offers you "updates" if they're different from what you have installed -- so if you customized any stock Slackware packages, make sure to uncheck them or add them to /etc/slackpkg/blacklist). At this point, it should be no different than running individual upgradepkg for each program. But if you run upgrade-pkg and it shows an error or no updates, then that is something else we'd need to try and address.
 
Old 07-13-2015, 10:24 AM   #10
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware on ARM and Aarch64
Posts: 1,573

Rep: Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892
I may have assumed too much about your comment because you are vague about what you mean.

Quote:
Originally Posted by mfoley View Post
mralk3: Thanks for the link, but doesn't shed much new light over the man pages. Nowhere does it provide any insight on the "(B)lacklist, (R)emove, or (I)gnore" message when running slackpkg upgrade
Are you referring to how new configuration files are handled at the end of an upgrade? If so, you can skip that and actually find the resulting .new configuration files by running as root:

Code:
find /etc/ -type f -name '*.new'
This will show you configuration files that were edited by the new tarballs installed by slackpkg. I usually use the (P)rompt option and skip a file if it needs manual editing after an upgrade. These configuration files ending in ".new" are not specific to slackpkg and will appear even when just running "upgradepkg".
 
Old 07-13-2015, 02:20 PM   #11
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,505

Rep: Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890
Quote:
Originally Posted by mfoley View Post
Nowhere does it provide any insight on the "(B)lacklist, (R)emove, or (I)gnore" message when running slackpkg upgrade
Slackpkg will ask that question if it finds multiple versions of the same package installed in /var/log/packages.
 
Old 07-14-2015, 12:03 AM   #12
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,904

Original Poster
Rep: Reputation: 147Reputation: 147
bassmadrigal: OK, You've re-convinced me to try the upgrade-all and select a single package ... to see. That may have to wait a day or two until I have a window to restore if I completely mess up the system. Will give it a shot and post back results.

mralk3: "Are you referring to how new configuration files are handled at the end of an upgrade?"

No, I get that part. See my response to Alien Bob below for my conundrum.

Alien Bob: "Slackpkg will ask that question [(B)lacklist, (R)emove, or (I)gnore] if it finds multiple versions of the same package installed in /var/log/packages."

So, that is what I am confused about. For one thing, I don't know why it would find multiple version of the package. I don't believe I've done anything "funny" with this host and slackpkg. In any case, the multiple versions are generally of the format: shadow-4.1.5.1-x86_64-2 and shadow-4.1.5.1-x86_64-3_slack14.1 -- in this case, the first "version" has location ./slackware64/a and the 2nd version has location ./patches/packages. To me this looks like version 3 was a superseded, patch of version 2. That seems OK to me. Confusing.

But mainly there's this: when I run e.g. slackpkg upgrade httpd, I get the following warning:


Checking local integrity... DONE
You have a broken /var/log/packages - with two versions of the same package.
The list of packages duplicated in your machine are shown below, but don't
worry about this list - when you select your action, slackpkg will show a
better list.

Don't worry about the list? Really. My "actions" are (B)lacklist and (R)emove. To me, "blacklist" means the package will never, ever be upgraded again. Am I wrong? To me, "remove" means the package will be removed from my system and e.g. wpa_supplicant, sudo, samba, etc will cease to work. Neither of these seem like reasonable consequences when all I want to do is upgrade httpd. Maybe I don't understand the meaning of "blacklist" (but the manpage says, "Blacklisted packages will not be installed, upgraded, or removed by slackpkg") or the meaning of "remove" (but the manpage says, "With remove, you can remove certain installed packages"). Both of these options seem rather dramatic and far-reaching aside from having nothing to do with the httpd package and to me, neither of these options would fall under "don't worry about this list." What am I missing and why should I "not worry about this list"?

For completeness, here is the list of packages that I can supposedly blacklist or remove "without worrying".
Code:
bash-4.2.045-x86_64-1
bash-4.2.053-x86_64-1_slack14.1
bind-9.9.5_P1-x86_64-1_slack14.1
bind-9.9.6_P1-x86_64-1_slack14.1
btrfs-progs-20130418-x86_64-1
btrfs-progs-20150213-x86_64-1
freetype-2.5.0.1-x86_64-1
freetype-2.5.5-x86_64-1_slack14.1
glibc-2.17-x86_64-10_slack14.1
glibc-2.17-x86_64-7
glibc-i18n-2.17-x86_64-10_slack14.1
glibc-i18n-2.17-x86_64-7
glibc-profile-2.17-x86_64-10_slack14.1
glibc-profile-2.17-x86_64-7
glibc-solibs-2.17-x86_64-10_slack14.1
glibc-solibs-2.17-x86_64-7
glibc-zoneinfo-2013d-noarch-7
glibc-zoneinfo-2014j-noarch-1
kernel-generic-3.10.17-x86_64-2
kernel-generic-3.10.17-x86_64-3
kernel-huge-3.10.17-x86_64-2
kernel-huge-3.10.17-x86_64-3
kernel-modules-3.10.17-x86_64-2
kernel-modules-3.10.17-x86_64-3
mariadb-5.5.37-x86_64-1_slack14.1
mariadb-5.5.40-x86_64-2_slack14.1
mozilla-firefox-24.7.0esr-x86_64-1_slack14.1
mozilla-firefox-31.4.0esr-x86_64-1_slack14.1
mozilla-nss-3.16-x86_64-1_slack14.1
mozilla-nss-3.16.5-x86_64-1_slack14.1
mozilla-thunderbird-24.7.0-x86_64-1_slack14.1
mozilla-thunderbird-31.4.0-x86_64-1_slack14.1
ntp-4.2.6p5-x86_64-5_slack14.1
ntp-4.2.8-x86_64-1_slack14.1
openssh-6.6p1-x86_64-3_slack14.1
openssh-6.7p1-x86_64-2_slack14.1
openssl-1.0.1i-x86_64-1_slack14.1
openssl-1.0.1k-x86_64-1_slack14.1
openssl-solibs-1.0.1e-x86_64-1
openssl-solibs-1.0.1i-x86_64-1_slack14.1
openvpn-2.3.2-x86_64-1
openvpn-2.3.6-x86_64-1_slack14.1
patch-2.7-x86_64-2
patch-2.7.4-x86_64-1_slack14.1
php-5.4.30-x86_64-1_slack14.1
php-5.4.36-x86_64-1_slack14.1
pidgin-2.10.11-x86_64-1_slack14.1
pidgin-2.10.9-x86_64-1_slack14.1
samba-4.1.11-x86_64-1_slack14.1
samba-4.1.16-x86_64-1_slack14.1
seamonkey-2.26.1-x86_64-1_slack14.1
seamonkey-2.32.1-x86_64-1_slack14.1
seamonkey-solibs-2.26.1-x86_64-1_slack14.1
seamonkey-solibs-2.32.1-x86_64-1_slack14.1
shadow-4.1.5.1-x86_64-2
shadow-4.1.5.1-x86_64-3_slack14.1
sudo-1.8.12-x86_64-1_slack14.1
sudo-1.8.6p8-x86_64-1
udisks-1.0.4-x86_64-2
udisks-1.0.5-x86_64-1_slack14.1
udisks2-2.1.0-x86_64-1
udisks2-2.1.3-x86_64-1_slack14.1
wget-1.14-x86_64-2
wget-1.14-x86_64-3_slack14.1
wpa_supplicant-2.0-x86_64-1
wpa_supplicant-2.3-x86_64-1_slack14.1
xfce4-weather-plugin-0.8.3-x86_64-2
xfce4-weather-plugin-0.8.4-x86_64-1_slack14.1
xorg-server-1.14.3-x86_64-2
xorg-server-1.14.3-x86_64-3_slack14.1
xorg-server-xephyr-1.14.3-x86_64-2
xorg-server-xephyr-1.14.3-x86_64-3_slack14.1
xorg-server-xnest-1.14.3-x86_64-2
xorg-server-xnest-1.14.3-x86_64-3_slack14.1
xorg-server-xvfb-1.14.3-x86_64-2
xorg-server-xvfb-1.14.3-x86_64-3_slack14.1
better list:

Last edited by mfoley; 07-14-2015 at 12:05 AM.
 
Old 07-14-2015, 03:02 AM   #13
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,505

Rep: Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890Reputation: 7890
Obviously you have been using "installpkg" instead of "upgradepkg" when installing the Slackware 14.1 patches. That is how you ended up with multiply installed versions of a lot of software.
The remedy is to stick to using "upgradepkg" in future when you want to upgrade a software package. You only use "installpkg" when you want to install a piece of software that is not yet present on your computer.

And to remove the redundant packages: first use "removepkg /var/log/packages/name_of_the_redundant_package-version-arch-build" to remove all those doublures. Make sure to use the exact name of the files in "/var/log/packages" and make sure not to remove the ones that are actually the newest version of a package!
Then run "slackpkg reinstall name_of_the_package" for every package that is affected to make sure that you have the latest files and libraries.
 
Old 07-14-2015, 11:27 AM   #14
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,639

Rep: Reputation: Disabled
Another note: If you choose the option to Remove the conflicting packages it will present you a list of all the various versions which are duplicated and you can select which ones you want to remove, therefor you can leave the most recent version installed and only remove the old ones. One of the nice things about slackpkg is that it does not do anything automatically but always presents you with a list of options and you choose exactly what you want to do.

Brian
 
Old 07-18-2015, 03:25 PM   #15
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,904

Original Poster
Rep: Reputation: 147Reputation: 147
Alien Bob: useful information! I tried `removepkg mozilla-firefox-24.7.0esr-x86_64-1_slack14.1` (one of the packages in my posted list) and it worked. When I went to upgrade, that package was no longer in my "(B)lacklist, (R)emove or (I)gnore list". So, do you recommend that I do this removepkg one-by-one on the older packages to give me a clean list?

Quote:
Obviously you have been using "installpkg" instead of "upgradepkg" when installing the Slackware 14.1 patches
I assume that these are commands run by `slackpkg install` and `slackpkg upgrade`, respectively? I've never actually run installpkg and upgradepkg by hand.

BCarey:
Quote:
If you choose the option to Remove the conflicting packages it will present you a list of all the various versions which are duplicated and you can select which ones you want to remove
So, I can un-check the most recent ones and only remove the older versions? I'll experiment with that and post back.
 
  


Reply

Tags
slackpkg


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
Upgrading via slackpkg mattca Slackware 9 11-10-2013 12:16 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

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation

All times are GMT -5. The time now is 08:06 AM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration