[SOLVED] Installed duplicate packages with slackpkg+
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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?
that is not me, it is you. if you cannot gather from what I just said if I am agreeing with you or not. or that I am just trying to make a point, it is not me that is the cause of your dilemma.
I am just pointing out the process of thought along with gathered knowledge and using that together in determining what to do next. Therefore eliminating a ridged way of thinking. Which removes ones options in what he or she can do. Because it is of ridge thinking.
the options here where.
remove both then install one again.
or
just remove the first one and leave the second one alone. because as even you stated the second one has already taken precedence within the operating system by the very same method you described.
Quote:
Originally Posted by montagdude
then the second one you install will overwrite any common files from the first one,...
if I was to write anything more on the process of what can take place due to the possible variables to show cause and effects I fear I will only confuse you.
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
ls -l /var/log/packages/grantlee*
-rw-r--r-- 1 root root 2750 Feb 15 15:57 /var/log/packages/grantlee-0.5.1-x86_64-1
-rw-r--r-- 1 root root 2688 Feb 16 19:22 /var/log/packages/grantlee-5.1.0-x86_64-3alien
-rw-r--r-- 1 root root 14972 Feb 16 19:28 /var/log/packages/grantlee-editor-17.12.2-x86_64-1alien
-rw-r--r-- 1 root root 3300 Feb 16 19:22 /var/log/packages/grantlee-qt4-0.5.1-x86_64-1alien
-rw-r--r-- 1 root root 6719 Feb 16 19:28 /var/log/packages/grantleetheme-17.12.2-x86_64-1alien
So perhaps along with the original instructions I followed and before installing plasma I should have removed the package grantlee-0.5.1 and any of the other packages that I would have ended up duplicating.
Or maybe if I'd started using slackpkg earlier I could have simply used
I suspect that there's a lot wrong with these configuration files. Though I do think the PKGS_PRIORITY line is correct. I'd hope that someone will speak up if it isn't!
So to extend my knowledge I will reinstall from the beginning and go down the slackpkg route and see what happens!
Under normal circumstances I would have just waited for next stable release of Slackware 14.3, 15.0 or whatever it's going to be. What I was wanting to achieve is a Slackware platform with plasma that I can use to chase libreoffice bugs. My production platform will remain on 14.2 for some time.
that is not me, it is you. if you cannot gather from what I just said if I am agreeing with you or not. or that I am just trying to make a point, it is not me that is the cause of your dilemma.
hehehe
reminds me of this: https://www.xkcd.com/1860/
If it is still unclear, just hover the mouse pointer over the image and read further.
Location: Geneva - Switzerland ( Bordeaux - France / Montreal - QC - Canada)
Distribution: Slackware 14.2 - 32/64bit
Posts: 609
Rep:
Quote:
Originally Posted by BW-userx
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...
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.
Wrong: it would remove common files, so the one from the latest too...
It's strange to give presumptuous advises while it seems that you don't understand how things work...
A "removepkg" command will not remove files that belong to another package. The 'removepkg' script checks all entries in /var/log/packages when removing a particular package, to find the files which are not unique to this package.
hehehe
reminds me of this: https://www.xkcd.com/1860/
If it is still unclear, just hover the mouse pointer over the image and read further.
where do you find this stuff? you got it stashed in your back pocket just waiting to use it?
fails to understand how to reason and discern what is being said?
"just hover the mouse pointer over the image and read further"
to a point yes it does, when one comes in the middle of a conversation he or she needs to use the brain in there head to try and piece together what is being said in order to understand what is being said.
when some other is in a frantic state yes one does need to try and figure out what they are talknig about. many incidences where that can apply.
if one cannot take from experience and use that to try and understand what is going on around them. instead reliving on someone else to tell them. where does that leave that person?
it is too lengthy to type out all of the variables .. he was looking for a yes or a no, where one was not being given by me, nor did I indicate that I was. When even by his own understanding that he showed he could have deduced the answer for himself. I'll leave it at that. ...
I installed two same programs, I changed the version number, but the program name executable is the exact same.
ver 1.7 installed first
ver 1.8 installed second
Code:
root@slackcurr:/media/projects/Slackbuild.apps/wmimagedock
# ls /var/log/packages | grep wmimagedock
wmimagedock-1.7-x86_64-1_SBo.userxbw
wmimagedock-1.8-x86_64-1_SBo.userxbw
root@slackcurr:/media/projects/Slackbuild.apps/wmimagedock
# removepkg wmimagedock-1.7-x86_64-1_SBo.userxbw
Removing package /var/log/packages/wmimagedock-1.7-x86_64-1_SBo.userxbw...
Removing files:
--> /usr/bin/wmimagedock was found in another package. Skipping.
--> Deleting /usr/doc/wmimagedock-1.7/COPYING
WARNING: /usr/doc/wmimagedock-1.7/ChangeLog changed after package installation.
--> Deleting /usr/doc/wmimagedock-1.7/ChangeLog
--> Deleting /usr/doc/wmimagedock-1.7/INSTALL
--> Deleting /usr/doc/wmimagedock-1.7/README
--> Deleting /usr/doc/wmimagedock-1.7/wmimagedock.SlackBuild
--> Deleting empty directory /usr/doc/wmimagedock-1.7/
root@slackcurr:/media/projects/Slackbuild.apps/wmimagedock
# wmimagedock
wmimagedock 1.5 (c) 2018 Michael Heras
wmimagedock -e : either path to directory of images,
or a file containing a list with absoloute path and images name of images.
wmimagedock -t : delay time in seconds.
wmimagedock -r : display images in random order.
wmimagedock -o : display images in ordered list.
wmimagedock -t 30 -r -e /path/to/image directory
Can have multiple instances of this app running at same time.
( yes I know I am in root, current, thanks for noticing. )
I think it is saver to say if the version is different, then it is safe to uninstall one and keep the other. Because I did it this way too, same version, same program the only difference is the naming of the package.
that is something I failed to point out, and got caught up in the logic not applying the versioning properly. in the later, but noticing it in the OP posting the versions are different.
more experimentation,
Code:
k
# ls /tmp
SBo pulse-R91CaowslLOk wmimagedock-1.7-x86_64-1_SBo.tgz
kde-root slackpkg.YyMqkR wmimagedock-1.7-x86_64-1_SBo.userxbw.tgz
ksocket-root slackpkg.rThgCS wmimagedock-1.8-x86_64-1_SBo.userxbw.tgz
root@slackcurr:/media/projects/Slackbuild.apps/wmimagedock
# installpkg /tmp/wmimage*
# ls /var/log/packages | grep wmimagedock
wmimagedock-1.7-x86_64-1_SBo
wmimagedock-1.7-x86_64-1_SBo.userxbw
wmimagedock-1.8-x86_64-1_SBo.userxbw
# removepkg wmimagedock-1.7-x86_64-1_SBo
Removing package /var/log/packages/wmimagedock-1.7-x86_64-1_SBo...
Removing files:
--> /usr/bin/wmimagedock was found in another package. Skipping.
--> Deleting /usr/doc/wmimagedock-1.7/COPYING
WARNING: /usr/doc/wmimagedock-1.7/ChangeLog changed after package installation.
--> Deleting /usr/doc/wmimagedock-1.7/ChangeLog
--> Deleting /usr/doc/wmimagedock-1.7/INSTALL
--> Deleting /usr/doc/wmimagedock-1.7/README
--> Deleting /usr/doc/wmimagedock-1.7/wmimagedock.SlackBuild
--> Deleting empty directory /usr/doc/wmimagedock-1.7/
# wmimagedock
wmimagedock 1.5 (c) 2018 Michael Heras
wmimagedock -e : either path to directory of images,
or a file containing a list with absoloute path and images name of images.
wmimagedock -t : delay time in seconds.
wmimagedock -r : display images in random order.
wmimagedock -o : display images in ordered list.
wmimagedock -t 30 -r -e /path/to/image directory
Can have multiple instances of this app running at same time.
it is still there. they all have the same executable name in /usr/bin/wmimagedock
wit is too lengthy to type out all of the variables .. he was looking for a yes or a no, where one was not being given by me, nor did I indicate that I was. When even by his own understanding that he showed he could have deduced the answer for himself. I'll leave it at that. ...
Or, your posts ramble on with no apparent point, are full of run-on sentences, inappropriate verb tenses, and wrong or missing punctuation. I don't normally point out such things, but in your case it is to the point that your posts are often not comprehensible. I'm sure they make sense to you, but they don't make sense to anyone else. You might consider spending some time focusing on that when you post if you want people to actually read and understand them. I will leave it at that.
Last edited by montagdude; 05-15-2018 at 12:25 PM.
the removepkg script checks all files listed in /var/log/packages/wmimagedock-1.7-x86_64-1_SBo.userxbw and only removes them if they are not listed in another package's record in /var/log/packages.
So as
/usr/bin/wmimagedock is listed in /var/log/pacakageswmimagedock-1.8-x86_64-1_SBo.userxbw is not removed and also lists this file removepkg informs you: --> /usr/bin/wmimagedock was found in another package. Skipping.
Removepkg doesn't check that the files are identical or differ in both packages' records (and it has no way to do that, as the packages' records in /var/log/packages don't include each listed file's checksum).
When you remove the second package there is no remaining package's record in /var/log/packages that lists /usr/bin/wmimagedock so this file gets removed.
That this file be an executable doesn't matter at all.
Simple as that, and this logic has worked well for decades.
Last edited by Didier Spaier; 05-15-2018 at 12:45 PM.
Or, your posts ramble on with no apparent point, are full of run-on sentences, inappropriate verb tenses, and wrong or missing punctuation. I don't normally point out such things, but in your case it is to the point that your posts are often not comprehensible. I'm sure they make sense to you, but they don't make sense to anyone else. You might consider spending some time focusing on that when you post if you want people to actually read and understand them. I will leave it at that.
well punctuation was invented 100's years after the written word and they got along fine without it what is the problem
can you discern where the one thought ends and a question starts without the use of punctuation
did you recognize that last line of text as a question or statement after you read it
I do suppose you will not be able to answer any of this because I put no ? to tell you that I even posed a question.
the removepkg script checks all files listed in /var/log/packages/wmimagedock-1.7-x86_64-1_SBo.userxbw and only removes them if they are not listed in another package's record in /var/log/packages.
So as
/usr/bin/wmimagedock is listed in /var/log/pacakageswmimagedock-1.8-x86_64-1_SBo.userxbw it is not removed and removepkg informs you: --> /usr/bin/wmimagedock was found in another package. Skipping.
Removepkg doesn't check that the files are identical or differ in both packages' records (and it has no way to do that, as the pacakages' records in /var/log/packages don't include each listed file's checksum).
When you remove the second package there is no remaining package's record in /var/log/packages that lists /usr/bin/wmimagedock so this file gets removed.
That this file be an executable doesn't matter at all.
Simple as that, and this logic has worked well for decades.
so you're saying it is safe to remove the one version and leave the other?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
)
