LinuxQuestions.org
Review your favorite Linux distribution.
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 07-28-2020, 05:10 AM   #1
rdx
Member
 
Registered: Apr 2007
Location: Dallas
Distribution: Slackware64 14.2
Posts: 274

Rep: Reputation: 25
What is the deal with "slackpkg"? A mixed blessing?


A while back I installed Slackware64 14.2. I discovered that several browsers, eg, Opera, Chromium, didn't work. Firefox and Seamonkey did work so I used them. Other programs, such as audacity worked nicely and others. Then I ran slackpkg for the first time (to get discord to work). After that, the browsers worked but other programs like audacity are now broken. This is not really helpful, honestly I need audacity more than chromium.

I have been told to bow down to the computer god and serve it, that my problems are due to my neglect of service to the machine. My POV is that the computer is here to serve me, not I it. All of this seems to have begun with Slackware 14.2 and I have been using previous releases without incident for many years. So what happened? Why did the Windoz virus of constant updates infect Slackware?
 
Old 07-28-2020, 05:35 AM   #2
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,502

Rep: Reputation: 801Reputation: 801Reputation: 801Reputation: 801Reputation: 801Reputation: 801Reputation: 801
Did you run slackpkg install-new
 
Old 07-28-2020, 05:47 AM   #3
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,242

Rep: Reputation: 518Reputation: 518Reputation: 518Reputation: 518Reputation: 518Reputation: 518
What mirror did you select in /etc/slackpkg/mirrors?
 
Old 07-28-2020, 06:37 AM   #4
Gerard Lally
Senior Member
 
Registered: Sep 2009
Location: Brú na Bóinne, IE
Distribution: Slackware, NetBSD
Posts: 1,758

Rep: Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266
Quote:
Originally Posted by rdx View Post
A while back I installed Slackware64 14.2. I discovered that several browsers, eg, Opera, Chromium, didn't work. Firefox and Seamonkey did work so I used them. Other programs, such as audacity worked nicely and others. Then I ran slackpkg for the first time (to get discord to work). After that, the browsers worked but other programs like audacity are now broken. This is not really helpful, honestly I need audacity more than chromium.

I have been told to bow down to the computer god and serve it, that my problems are due to my neglect of service to the machine. My POV is that the computer is here to serve me, not I it. All of this seems to have begun with Slackware 14.2 and I have been using previous releases without incident for many years. So what happened? Why did the Windoz virus of constant updates infect Slackware?
It depends how you installed audacity, discord and the other third-party software. Since they're not included with Slackware it's unlikely you used slackpkg to install them, unless you are using slackpkg+ and they're available as binaries at Eric's repo.

sbopkg and sbotools are available for building the software you have listed; slackpkg without the plus extension looks after packages included with Slackware, and has nothing to do with audacity, discord and chromium; with the plus extension slackpkg can be configured to install some or all of the third-party software you need.

But until you clear up which slackpkg you are using, and how you install third-party software, nobody can really help you.

Last edited by Gerard Lally; 07-28-2020 at 06:41 AM.
 
1 members found this post helpful.
Old 07-28-2020, 07:06 AM   #5
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,777

Rep: Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364
Is this a support request or a rant? You certainly didn't just run slackpkg, since it requires a secondary command to do anything. You gave far too little information for anyone to help you.
 
1 members found this post helpful.
Old 07-28-2020, 07:17 AM   #6
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 526

Rep: Reputation: 333Reputation: 333Reputation: 333Reputation: 333
It seems this started here https://www.linuxquestions.org/quest...-a-4175675470/
 
Old 07-28-2020, 10:09 AM   #7
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 581

Rep: Reputation: 273Reputation: 273Reputation: 273
So a few tips with slackpkg.


slackpkg update
slackpkg upgrade-all
slackpkg install-new (Paranoid, but I do this every update.)
(slackpkg install multilib, if you're using multilib.)

Make certain your kernel and modules are blacklisted. These should be installed manually, so you don't ever overwrite your working kernel.

slackpkg clean-system will remove all 3rd party applications installed as slackware packages. It will break things, if you have things compiled against them. (Like other 3rd party software.)

All of Alien Bob's packages, for instance, require an updated Slackware, too. (His packages are nice because they always work and always build, if you're using his slackbuilds.)

Last edited by garpu; 07-28-2020 at 09:30 PM. Reason: changed line about gpg.
 
Old 07-28-2020, 10:20 AM   #8
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,243

Rep: Reputation: 4933Reputation: 4933Reputation: 4933Reputation: 4933Reputation: 4933Reputation: 4933Reputation: 4933Reputation: 4933Reputation: 4933Reputation: 4933Reputation: 4933
Packages are built against libraries on your system. When the system is updated, if those libraries are updated to binary incompatible versions of their older selves, the packages that depended on them will need to be rebuilt.

Newer versions of Chromium based browsers were likely using newer libraries that didn't exist on your stock 14.2 and you built audacity against the stock versions of libraries on your 14.2. When you updated, it brought in new programs that broke audacity. Generally, this doesn't happen frequently when running a stable release (as Pat tries to minimize breakage unless absolutely necessary due to a severe bug), but if you're running -current, updates can and do break 3rd-party packages as the core of the OS is updated.

If you accidentally selected a "current" mirror instead of a 14.2 mirror in /etc/slackpkg/mirrors, then this is likely what caused the breakage. A simple rebuild of audacity and its dependencies should fix the issue. Coincidentally, this is why *I* don't run -current. I don't have the time to fix programs when they occasionally break.

If this happened with a 14.2 mirror selected, then it is extremely rare (and I'd be very interested to know your error message). However, again, a simple rebuild of audacity and its dependencies should fix the problem.

This is why some prefer distros that offer binary based repos, because when the OS is updated, all packages on the binary repo should be updated, so when you update the system, everything still works. When you're working with a non-binary repo (like Slackware's SBo, Arch's AUR, Gentoo's ebuilds, etc), if the OS is updated, it might require recompiling programs against the new libraries in the core OS. Is does take more work, but it does give you more flexibility when compiling those programs (enabling/disabling optional features).
 
Old 07-28-2020, 10:48 AM   #9
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 526

Rep: Reputation: 333Reputation: 333Reputation: 333Reputation: 333
Quote:
Originally Posted by garpu View Post
slackpkg update gpg (if you haven't already, or anytime you change mirrors.)
This is not true. The GPG key doesn't change, so if you already have it in your keyring, don't fetch it again.

As a matter of fact, I would consider it suspicious to update the key using a file downloaded from the same mirror whose files you want to check for authenticity. A perpetrator who controls the mirror could compromise the packages, sign the packages with their own key, and put the corresponding public GPG key to be downloaded from the mirror. "slackpkg update gpg" would first delete the previous key and then import the compromised key.

I would prefer to download the GPG key from a key server, like this:
Code:
gpg --keyserver keys.gnupg.net --recv-key 40102233
or
Code:
gpg --keyserver keys.gnupg.net --search-keys "Slackware Linux Project <security@slackware.com>"

Last edited by Petri Kaukasoina; 07-28-2020 at 10:50 AM.
 
1 members found this post helpful.
Old 07-28-2020, 01:28 PM   #10
rdx
Member
 
Registered: Apr 2007
Location: Dallas
Distribution: Slackware64 14.2
Posts: 274

Original Poster
Rep: Reputation: 25
Thank you all for your inputs. It's a lot to digest and I will have to study on it a while. It was meant as a question but I don't know enough to formulate a question. Hopefully I will be able to pose a good question soon.
 
Old 07-28-2020, 02:08 PM   #11
drgibbon
Member
 
Registered: Nov 2014
Distribution: Slackware64 -current
Posts: 713

Rep: Reputation: 457Reputation: 457Reputation: 457Reputation: 457Reputation: 457
You definitely do not want to be updating the GPG key every time you change mirrors! The whole point is that you have the real public key from the project, and that in general doesn't change. If a mirror was compromised and files altered, for sure a new (evil) keypair would be generated and your `update gpg` would set your system to trust it. Anyway, Petri Kaukasoina laid it out nicely.

Quote:
Originally Posted by rdx View Post
A while back I installed Slackware64 14.2. I discovered that several browsers, eg, Opera, Chromium, didn't work. Firefox and Seamonkey did work so I used them. Other programs, such as audacity worked nicely and others. Then I ran slackpkg for the first time (to get discord to work). After that, the browsers worked but other programs like audacity are now broken. This is not really helpful, honestly I need audacity more than chromium.
Hmm, I don't know what's up with your system, but I run Firefox, Chromium (slackpkg+ / alien repo), Vivaldi (SBo), Falkon (slackpkg+ / ktown), and Audacity (SBo) on both stable and -current. So yeah, there are no inherent problems with it all. Hopefully you can get it sorted out.
 
Old 07-28-2020, 02:48 PM   #12
hitest
Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD, Debian
Posts: 6,304

Rep: Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549
Quote:
Originally Posted by rdx View Post
Thank you all for your inputs. It's a lot to digest and I will have to study on it a while. It was meant as a question but I don't know enough to formulate a question. Hopefully I will be able to pose a good question soon.
https://slackpkg.org/documentation.html

Here's some documentation about slackpkg so that you may better understand how it works.
 
1 members found this post helpful.
Old 07-28-2020, 09:37 PM   #13
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 581

Rep: Reputation: 273Reputation: 273Reputation: 273
I stand corrected and edited accordingly. It's one of those things I only do once every seven years or so, and couldn't remember what best practice was.
 
Old 07-29-2020, 06:01 AM   #14
poke.peek
LQ Newbie
 
Registered: Jul 2020
Distribution: Slackware
Posts: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by garpu View Post
slackpkg update
slackpkg upgrade-all
slackpkg install-new (Paranoid, but I do this every update.)

Hi. I think it's better to run 'slackpkg install-new' first, in case of some of the upgraded packages not working because of the missing dependencies (happened to me few times in past ).

I usually do this:

Code:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
 
5 members found this post helpful.
Old 07-29-2020, 07:29 AM   #15
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 581

Rep: Reputation: 273Reputation: 273Reputation: 273
OK. More coffee needed.
 
  


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] [ENCHANCEMENT] slackpkg+: do not show the notices "pkglist is older than 24h..." and "remember to re-run 'slackpkg update''..."... yars Slackware 1 01-09-2016 09:56 AM
LXer: Java crowd has mixed views on potential Sun-IBM deal LXer Syndicated Linux News 0 03-19-2009 07:50 AM
LXer: Review: Ubuntu Popularity: Blessing or Curse? LXer Syndicated Linux News 2 09-25-2007 09:41 AM
LXer: Open-source ID project awaits Microsoft's blessing LXer Syndicated Linux News 0 03-10-2007 03:16 PM
Blessing for a new computer? kkathman Linux - Hardware 15 10-28-2003 06:00 PM

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

All times are GMT -5. The time now is 11:59 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
Open Source Consulting | Domain Registration