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 01-08-2018, 08:49 AM   #1
ubiloo
LQ Newbie
 
Registered: Sep 2017
Posts: 10

Rep: Reputation: Disabled
Slackware-current unmet dependancies + how to report?


Hi all, I happily run Slackware-current on one of my hosts but, though rarely, I find missing dependencies. For instance, today I fixed:

1 - Apache module for PHP7 prevents HTTPD from starting, because libsodium is missing
(just do slackpkg install libsodium)

2 - nslookup command needs missing libedit
(just do slackpkg install libedit)

Whom shoud I write to, of the Slackware addresses, if I want to report such small issues?
 
Old 01-08-2018, 09:02 AM   #2
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 5,066

Rep: Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864
Quote:
Originally Posted by ubiloo View Post
Hi all, I happily run Slackware-current on one of my hosts but, though rarely, I find missing dependencies. For instance, today I fixed:

1 - Apache module for PHP7 prevents HTTPD from starting, because libsodium is missing
(just do slackpkg install libsodium)

2 - nslookup command needs missing libedit
(just do slackpkg install libedit)

Whom shoud I write to, of the Slackware addresses, if I want to report such small issues?
If you were able to install them with slackpkg, it means they exist in the distribution, but they were missing in your install. This most likely occurred because you forgot to run slackpkg install-new before you ran slackpkg upgrade-all.

Running upgrade-all will only update the existing packages if any newer versions are present. install-new will add any new programs, and clean-system will uninstall any programs that were removed (be sure to blacklist your 3rd-party packages from slackpkg so clean-system doesn't remove them). All should be a part of your upgrade process when running -current.

I'd highly recommend running slackpkg install-new now to see what other programs you might be missing, and slackpkg clean-system to get rid of all the packages that are no longer a part of Slackware.
 
2 members found this post helpful.
Old 01-08-2018, 09:03 AM   #3
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,198

Rep: Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137
that most probably happens because you usually don't install the new packages added to the current tree but you just upgrade the existing ones: if you use slackpkg, the correct set of commands to use at every update is
Code:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system
you are probably missing the second one.
the last should be issued with great care because, with the default configuration, it will remove every third party package you have installed (thing that maybe you don't want), but it's used commonly to uninstall packages removed from the slackware tree (like "man", that has been recently substituted by man-db).

EDIT: bassmadrigal has been faster!

Last edited by ponce; 01-08-2018 at 09:54 AM. Reason: forgot a dash
 
3 members found this post helpful.
Old 01-08-2018, 09:28 AM   #4
hitest
LQ Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 5,380

Rep: Reputation: 1381Reputation: 1381Reputation: 1381Reputation: 1381Reputation: 1381Reputation: 1381Reputation: 1381Reputation: 1381Reputation: 1381Reputation: 1381
Further to the excellent, previous posts I like to run this command the first time I'm updating -current then follow with the other commands in order.

Code:
slackpkg update gpg
 
2 members found this post helpful.
Old 01-08-2018, 12:32 PM   #5
ubiloo
LQ Newbie
 
Registered: Sep 2017
Posts: 10

Original Poster
Rep: Reputation: Disabled
Thanks everybody

Thanks for the replies, I always installaed packages on a per-need basis and missed this apparently obvious fact!
 
Old 01-08-2018, 06:34 PM   #6
slackb0t
Member
 
Registered: Apr 2005
Location: Canada
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 258

Rep: Reputation: 62
Quote:
Originally Posted by ponce View Post
that most probably happens because you usually don't install the new packages added to the current tree but you just upgrade the existing ones: if you use slackpkg, the correct set of commands to use at every update is
Code:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system
you are probably missing the second one.
the last should be issued with great care because, with the default configuration, it will remove every third party package you have installed (thing that maybe you don't want), but it's used commonly to uninstall packages removed from the slackware tree (like "man", that has been recently substituted by man-db).

EDIT: bassmadrigal has been faster!
hmmm.. I have never run clean-system. How important is that step? Is it just to keep things neat or is not doing so possibly going to cause an issue?

edit: I just searched and there seem to be mixed opinions on how often to run clean-system.

Last edited by slackb0t; 01-08-2018 at 06:45 PM.
 
Old 01-08-2018, 06:43 PM   #7
montagdude
Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 946

Rep: Reputation: 670Reputation: 670Reputation: 670Reputation: 670Reputation: 670Reputation: 670
Quote:
Originally Posted by slackb0t View Post
hmmm.. I have never run clean-system. How important is that step? Is it just to keep things neat or is not doing so possibly going to cause an issue?
It probably depends on the reason why Pat removed the package(s) in the first place. Usually, it probably doesn't hurt to keep them, but I'm sure there are exceptions.

As a note of caution, clean-system will also select any third-party packages you have installed, unless you have blacklisted them, so be careful.
 
2 members found this post helpful.
Old 01-08-2018, 06:53 PM   #8
slackb0t
Member
 
Registered: Apr 2005
Location: Canada
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 258

Rep: Reputation: 62
Thanks.

I wonder if someone has created a script to add all 3rd party packages directly to the blacklist? I tried a search but didn't come up with anything. That would be handy.

edit: Doh.. I just realized I added the following to blacklist to take care of the problem lol

Code:
[0-9]+_SBo
[0-9]+alien
I normally install most 3rd party packages from SBo or alien so I should be safe to run clean-system.

I just did a trial run and it didn't want to remove the SBo or Alien packages but there were quite a few official packages that it wanted to delete. Probably 25 or so...

Last edited by slackb0t; 01-08-2018 at 07:04 PM.
 
Old 01-08-2018, 08:51 PM   #9
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 5,066

Rep: Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864
Quote:
Originally Posted by slackb0t View Post
I just did a trial run and it didn't want to remove the SBo or Alien packages but there were quite a few official packages that it wanted to delete. Probably 25 or so...
Basically, this will remove any packages not in the official tree (unless it is blacklisted). This could be packages that were removed (no longer needed, replaced by a different program, consolidated into another program, no longer works, etc) or 3rd-party packages that aren't blacklisted. You could search the changelog and see if there were any notes on the removal. That could give insight on why it was removed.

While it isn't always important to remove programs that have been removed from Slackware, sometimes it's very important, like in the 14.2 development when we moved from udev to eudev. Had you left udev in the system, it probably would've conflicted with eudev and caused you problems. Also, if the switch gets thrown on KDE5/Plasma5, you'll want to clean the system of any KDE4 remnants to prevent conflicts (I don't think they coexist together anymore).

Just find the 3rd-party packages you use and ensure you blacklist the tags (most people just need SBo and alien tags), then you should be good to go to run clean-system without issue
 
1 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
[SOLVED] Unmet Dependancies KelsoJIm Linux - Newbie 20 09-13-2017 11:06 AM
[SOLVED] Slackware-Current on a MacBook Pro 2015 Report dugan Slackware 15 01-31-2016 05:59 PM
[Slackware-64 current] Issue with LILO (Bug Report?) metalforever Slackware 4 09-17-2015 01:55 PM
Unmet Dependancies/Broken Packages - Can't apt-get Build-Install??? Xenoman1 Ubuntu 3 08-07-2006 03:38 AM
unmet dependancies upgrading to SID MaTrIx709 Debian 6 08-03-2005 01:17 AM

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

All times are GMT -5. The time now is 08:18 PM.

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