LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
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 05-14-2018, 07:16 AM   #1
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 522

Rep: Reputation: 55
Installed duplicate packages with slackpkg+


I've started to use slackpkg+ and need some advice on how to proceed. I've

I installed current in virtualbox with multilib.

Followed the instructions from AlienBob to install kde plasma including deleting the kde4 packages.

Installed slackpkg+
amended the configuration files

Ran

Code:
slackpkg update gpg
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system

I then ran slackpkg upgrade-all again it tells me that I need to upgrade these packages


Quote:
grantlee-5.1.0-x86_64-3alien
kaudiocreator-e64e16a_20171004git-x86_64-1alien
kdelibs-4.14.38-x86_64-1alien
kdevelop-pg-qt-2.1.0-x86_64-1alien
ktorrent-5.1.0-x86_64-1alien
kwebkitpart-cca571d_20171117git-x86_64-1alien
libktorrent-2.1-x86_64-1alien
oxygen-gtk2-1.4.6.1-x86_64-1alien
partitionmanager-3.3.1-x86_64-1alien
phonon-gstreamer-4.9.0-x86_64-1alien
qt-gstreamer-1.2.0-x86_64-6alien

When I look in /var/log/packages I see

Quote:
grantlee-0.5.1-x86_64-1
grantlee-5.1.0-x86_64-3alien

kaudiocreator-1.3-x86_64-2
kaudiocreator-e64e16a_20171004git-x86_64-1alien

kdelibs-4.14.38-x86_64-1
kdelibs-4.14.38-x86_64-1alien

kdevelop-pg-qt-1.0.0-x86_64-2
kdevelop-pg-qt-2.1.0-x86_64-1alien

ktorrent-4.3.1-x86_64-2
ktorrent-5.1.0-x86_64-1alien

libktorrent-1.3.1-x86_64-3
libktorrent-2.1-x86_64-1alien

oxygen-gtk2-1.4.6-x86_64-2
oxygen-gtk2-1.4.6.1-x86_64-1alien

partitionmanager-1.1.1-x86_64-2
partitionmanager-3.3.1-x86_64-1alien

phonon-gstreamer-4.8.2-x86_64-1
phonon-gstreamer-4.9.0-x86_64-1alien

qt-gstreamer-1.2.0-x86_64-1
qt-gstreamer-1.2.0-x86_64-6alien

It looks like I have duplicate packages. Should I be worried?
 
Old 05-14-2018, 07:38 AM   #2
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Slackware 14.2 / Slackware 14.2 current / Manjaro
Posts: 6,614

Rep: Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333
Worried? no,

Logically I'd say the system uses the last one installed, but it only needs one, so keep alien, or the other one added by the system.

I have never had an issue running anything with a situation like that, but when I do an upgrade and the system shows me i have dups, I remove one, and keep the other.

You might want to keep alien if it is for something he did to keep things tighter. Because he usually builds the software to curtail to the needs of what it is being used for, and not all willy nilly enable everything that can be. He also usually does a write up on what he has done, if you want to take a closer look at that.

Last edited by BW-userx; 05-14-2018 at 07:51 AM.
 
Old 05-14-2018, 08:27 AM   #3
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 522

Original Poster
Rep: Reputation: 55
I've always assumed that if I see a package in /var/log/packages it is actually installed.

I've added grantlee-0.5.1-x86_64-1 to /etc/slackpkg/blacklist.

When I run slackpkg upgrade-all I no longer see grantlee-5.1.0-x86_64-3alien as a candidate for upgrade. However, I still see in /var/log/packages

Quote:
-rw-r--r-- 1 root root 2750 Feb 15 15:57 grantlee-0.5.1-x86_64-1
-rw-r--r-- 1 root root 2688 Feb 16 19:22 grantlee-5.1.0-x86_64-3alien
Should I manually delete the package I don't want with removepkg?
 
Old 05-14-2018, 08:31 AM   #4
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,324

Rep: Reputation: Disabled
I would use removepkg on all the duplicate packages and then reinstall the intended package.
 
2 members found this post helpful.
Old 05-14-2018, 09:37 AM   #5
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Slackware 14.2 / Slackware 14.2 current / Manjaro
Posts: 6,614

Rep: Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333
in Slackware (stable) I updated/graded windowmaker, every time Slack gets an update, it says it has an upgrade to windowmaker, which in fact is the lesser version. ( that is the nature of the beast) to eliminate that message, I (finally) black listed windowmaker. So now it just leaves it alone. Giving the control of the piece of software to me.

The reason you are seeing the both of them popping up is because their is a difference in the files, one has alien tack on it, whereas the other ones does not, therefore, they both can (be installed, and) coexist in the system side by side.

but only one is being used. as suggest you can use removepkg, or when you run your update / upgrade-all and the message pops up, you can opt to select which one to keep, and which one to remove. Either way the end result is the same, you're back to only having one installed. Because having two installed, is redundant.

Last edited by BW-userx; 05-14-2018 at 09:39 AM.
 
Old 05-14-2018, 09:46 AM   #6
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 815

Rep: Reputation: 295Reputation: 295Reputation: 295
Did you follow the ktown README to the letter. Specifically "upgradepkg --install-new --reinstall" very important. You shouldn't have two versions. I am also suspecting something may not be right in your slackpkgplus.conf file.

Adding these to your blacklist is not the solution. Of course you won't see grantlee-0.5.1-x86_64-1 when running slackpkg upgrade-all because it's blacklisted.

Try running slackpkg search grantlee. Search will show all, including blacklisted. This is what I see.
Code:
[ Status           ] [ Repository               ] [ Package                                  ]
   installed               ktown                        grantlee-5.1.0-x86_64-3alien              
   installed               ktown                        grantlee-editor-18.04.0-x86_64-1alien     
   installed               ktown                        grantlee-qt4-0.5.1-x86_64-1alien          
   installed               ktown                        grantleetheme-18.04.0-x86_64-1alien       
  uninstalled(masked)      slackware64                  grantlee-0.5.1-x86_64-2
What do you see?
 
1 members found this post helpful.
Old 05-14-2018, 09:51 AM   #7
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,214

Rep: Reputation: 5219Reputation: 5219Reputation: 5219Reputation: 5219Reputation: 5219Reputation: 5219Reputation: 5219Reputation: 5219Reputation: 5219Reputation: 5219Reputation: 5219
Quote:
Originally Posted by aikempshall View Post
It looks like I have duplicate packages. Should I be worried?
Yes.

You should not end up with my packages alongside the Slackware versions. You did not follow all the instructions somehow, or you do not yet grasp the effects of what you put into slackpkgplus.conf. Perhaps you forgot to define "PKGS_PRIORITY". It's well-documented, for instance here: http://slakfinder.org/slackpkg+/src/README

Quote:
Originally Posted by aikempshall View Post
I've added grantlee-0.5.1-x86_64-1 to /etc/slackpkg/blacklist.
When I run slackpkg upgrade-all I no longer see grantlee-5.1.0-x86_64-3alien as a candidate for upgrade.
This is wrong. You should look at fixing this with "PKGS_PRIORITY".

Quote:
Should I manually delete the package I don't want with removepkg?
Yes, that is what you should do because this cannot be resolved otherwise. And pray that the other package was installed last, or else you end up with a mix of files and will have a future of pain.

Quote:
Originally Posted by orbea View Post
I would use removepkg on all the duplicate packages and then reinstall the intended package.
Like that, exactly.

Quote:
Originally Posted by BW-userx View Post
in Slackware (stable) I updated/graded windowmaker, every time Slack gets an update, it says it has an upgrade to windowmaker, which in fact is the lesser version. ( that is the nature of the beast) to eliminate that message, I (finally) black listed windowmaker. So now it just leaves it alone. Giving the control of the piece of software to me.
This too should not be 'fixed' with a blacklist entry but with proper use of "PKGS_PRIORITY".

Quote:
The reason you are seeing the both of them popping up is because their is a difference in the files, one has alien tack on it, whereas the other ones does not, therefore, they both can (be installed, and) coexist in the system side by side.
Absolutely not! Only one, the correct one, should be installed. IF I have another version of a Slackware package, that is for a good reason: add functionality that e.g. Plasma5 requires. If you configure slackpkg+ correctly then these issues do not occur.
 
3 members found this post helpful.
Old 05-14-2018, 10:07 AM   #8
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Slackware 14.2 / Slackware 14.2 current / Manjaro
Posts: 6,614

Rep: Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333
Quote:
Originally Posted by Alien Bob View Post
Yes.

You should not end up with my packages alongside the Slackware versions. You did not follow all the instructions somehow, or you do not yet grasp the effects of what you put into slackpkgplus.conf. Perhaps you forgot to define "PKGS_PRIORITY". It's well-documented, for instance here: http://slakfinder.org/slackpkg+/src/README


This is wrong. You should look at fixing this with "PKGS_PRIORITY".


Yes, that is what you should do because this cannot be resolved otherwise. And pray that the other package was installed last, or else you end up with a mix of files and will have a future of pain.


Like that, exactly.


This too should not be 'fixed' with a blacklist entry but with proper use of "PKGS_PRIORITY".


Absolutely not! Only one, the correct one, should be installed. IF I have another version of a Slackware package, that is for a good reason: add functionality that e.g. Plasma5 requires. If you configure slackpkg+ correctly then these issues do not occur.
if you look I have already addressed that issue in using your packages as apposed to the other ones in post #2 about the importance of using your packages.

as far as windowmaker black list that was a general example as I am not using slackpkg+ . if I am still wrong then thanks for the update information between blacklisting and "PKGS_PRIORITY". which I think is a slackpkg+ thing.

worried about it, I said no, you said yes,

I'd just fix it by whatever means necessary then that worry part is not there, so no, I'd not worry about it, because I'd fix it. I guess it is just a matter of perspective.

Last edited by BW-userx; 05-14-2018 at 10:26 AM.
 
Old 05-14-2018, 10:22 AM   #9
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,114

Rep: Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825
Quote:
Originally Posted by BW-userx View Post
if that is causing a conflict now with the slackpkg+ whereas you have to only use removepkg, then what is to be said of that. Because that would mean that is is not complementing the system.
slackpkg+ is not to blame for the OP's situation. It happened, presumably, because he did not properly remove the existing packages before installing the new ones with installpkg / upgradepkg. Or possibly he has a screwed up slackpkgplus.conf. Or maybe both.
 
1 members found this post helpful.
Old 05-14-2018, 10:28 AM   #10
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Slackware 14.2 / Slackware 14.2 current / Manjaro
Posts: 6,614

Rep: Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333
Quote:
Originally Posted by montagdude View Post
slackpkg+ is not to blame for the OP's situation. It happened, presumably, because he did not properly remove the existing packages before installing the new ones with installpkg / upgradepkg. Or possibly he has a screwed up slackpkgplus.conf. Or maybe both.
notice the use of the leading word 'if'

I never said it was. it was putting to question the why only using removepkg and not let the system remove it when it gives the opportunity? of course that would put to use the assumption that the person using that later method, by allowing the system to remove it in lue of killing the process of upgrade-all then using removepkg instead.

that the one being removed is the one that is suppose to be removed. instead of removing both of them then reinstalling one of them.

logic states the the one that is not alien would be the first one installed, because it is installed by the system at installation of the system, and any updates by the system to it.

Then if the next one being installed is the alien one. then that would be the one taking precedence and being put to use,therefore it should be safe to say to just remove the first one, not being alien and everything will be ok. if in fact no other one was installed to over take its precedence within the system.

if someone screwed up that logic, or is not using it, then problems will arise.

I was addressing the removing of a duplicate package, not the usage of slackpkg+ two different things entirely.

Last edited by BW-userx; 05-14-2018 at 10:49 AM.
 
Old 05-14-2018, 10:53 AM   #11
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,114

Rep: Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825
I don't know, I can hardly understand your posts.
 
1 members found this post helpful.
Old 05-14-2018, 11:06 AM   #12
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Slackware 14.2 / Slackware 14.2 current / Manjaro
Posts: 6,614

Rep: Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333
Quote:
Originally Posted by montagdude View Post
I don't know, I can hardly understand your posts.
what do you know? let me check.

you have two installed packages. they are the same packages, because they are the same software and have the the same version of the software. Yet they too can be two completely different packages even though the version number is the same.

how and why?

what gives indication they are different even though they have the same name and version number?

when both are installed because of the reason for the difference so they can be installed side by side on the system. Which one is being used by the system and how does the system know which one to use when they are both installed at the same time?


then you have to take that and apply it in knowing which one to remove and which one to leave alone.

installing software by using a make file,as apposed to slackpkg or installpkg .
a make file install does not care about what version you are installing.
slack packaging system does not care up to a point. it will prevent installing the same version again. but when using upgradepkg it does not care about the number. only the name.

why do these events take place and how?

Last edited by BW-userx; 05-14-2018 at 11:14 AM.
 
Old 05-14-2018, 11:36 AM   #13
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,114

Rep: Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825
Quote:
Originally Posted by BW-userx View Post
what do you know? let me check.

you have two installed packages. they are the same packages, because they are the same software and have the the same version of the software. Yet they too can be two completely different packages even though the version number is the same.

how and why?
Because any Joe Schmoe can create a Slackware package and call it anything they want. It's up to you, the user, to determine what the package contains and whether you want to install it on your system.

Quote:
Originally Posted by BW-userx View Post
what gives indication they are different even though they have the same name and version number?
For starters, the tag at the end of the package name. You can also compare the contents of the files /var/log/packages/pkg1 and /var/log/packages/pkg2 to see where they differ.

Quote:
Originally Posted by BW-userx View Post
when both are installed because of the reason for the difference so they can be installed side by side on the system. Which one is being used by the system and how does the system know which one to use when they are both installed at the same time?
If you use installpkg to install them both, then the second one you install will overwrite any common files from the first one, with the exception of configuration files that are given the .new treatment. The system doesn't "know" that you have two packages with the same name and version number installed; it just uses whatever files are in /usr/lib, /usr/bin, /etc, etc.

Figuring out which one to remove is the system administrator's job, since he/she is the one who installed them. Again, you can use the package naming information and the contents of the files in /var/log/packages to inform your decision, or, as someone else said, just removepkg them both and install the correct one again (assuming it's not a critical system component that will break stuff by being removed).

Last edited by montagdude; 05-14-2018 at 11:42 AM.
 
1 members found this post helpful.
Old 05-14-2018, 12:51 PM   #14
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Slackware 14.2 / Slackware 14.2 current / Manjaro
Posts: 6,614

Rep: Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333Reputation: 1333
Quote:
Originally Posted by montagdude View Post
Because any Joe Schmoe can create a Slackware package and call it anything they want. It's up to you, the user, to determine what the package contains and whether you want to install it on your system.
you took it outside the realm of trust.

because the software can have options too at compile time to give or take away. so it is the same software same version, one with and the other without an option(s), etc...


Quote:
Originally Posted by montagdude View Post

For starters, the tag at the end of the package name. You can also compare the contents of the files /var/log/packages/pkg1 and /var/log/packages/pkg2 to see where they differ.

If you use installpkg to install them both, then the second one you install will overwrite any common files from the first one, with the exception of configuration files that are given the .new treatment. The system doesn't "know" that you have two packages with the same name and version number installed; it just uses whatever files are in /usr/lib, /usr/bin, /etc, etc.
therefore it is now safe to say to just uninstall the prior package, by your own logic and understanding of what takes place during an install.

the only thing that does tell slack that their are two same pakages is the naming convention of the packages of the same software. the version number plays no real part in it.

Quote:
Originally Posted by montagdude View Post
Figuring out which one to remove is the system administrator's job, since he/she is the one who installed them. Again, you can use the package naming information and the contents of the files in /var/log/packages to inform your decision, or, as someone else said, just removepkg them both and install the correct one again (assuming it's not a critical system component that will break stuff by being removed).
exactly, as stated the system administrator because he or she is the one that only can install and remove, therefore should not the system administrator know which one was installed first then next, because he or she is the system administrator, therefore even by your stated logic and understanding of what takes place during an install, then use that knowledge to determining which one should be removed?

Last edited by BW-userx; 05-14-2018 at 12:54 PM.
 
Old 05-14-2018, 01:03 PM   #15
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,114

Rep: Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825
Yes. I don't know what you are getting at, and your posts are really hard to follow. I can't even tell if you are agreeing with me or not. I was just trying to answer your questions. If you have a point, can you try to state it in one or two complete sentences?
 
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] Duplicate packages dr.s Slackware 1 09-27-2015 05:26 PM
[SOLVED] Stale/duplicate packages in 14.1 patches/packages/ GazL Slackware 3 06-17-2015 09:06 AM
Duplicate packages in Aptitude wearetheborg Debian 2 06-02-2007 05:36 PM
Sort installed packages by # of dependant packages installed brianez21 Debian 1 01-18-2006 05:06 PM
Duplicate packages-rpm jerrymei Linux - Software 2 10-07-2005 02:33 PM

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

All times are GMT -5. The time now is 12:12 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration