Package list generated to upgrade does not seem to match with installed packages?
Slpkg is a user-friendly package manager for Slackware installations
Brought to you by:
dslackw
Was going to try this... I am running Slackware64 current. But I noticed something curious. I installed it, and ran "slpkg -c slack upgrade " If I am reading man correctly this should check my slackware for upgrades? It returned list of packages that need upgrading...
[ upgrade ] --> samba-4.1.11-x86_64-1_slack14.1.txz
[ upgrade ] --> seamonkey-2.26.1-x86_64-1_slack14.1.txz
[ upgrade ] --> seamonkey-solibs-2.26.1-x86_64-1_slack14.1.txz
[ upgrade ] --> sendmail-8.14.9-x86_64-1_slack14.1.txz
But some of the packages it lists are not installed on my system ? If I run pkgtool, remove installed packages.. this is the list where seamonkey would be: ( I only have the solibs installed for chrome.. )
│ │[ ] sdparm-1.08-x86_64-1 sdparm (fetch and change SCSI attribu│
│ │[ ] seamonkey-solibs-2.26.1-x86_seamonkey-solibs (Shared libraries fr│
│ │[ ] sed-4.2.2-x86_64-1 sed (stream editor)
It also showed mozilla firefox and thunderbird which are not installed either. I am using slackpkg now and it seems to do well... I am afraid that this will break my system if I run it to upgrade....Seems like it must be getting package list from my initial install of 14.1 ..before I upgraded to current through slackpkg... not the list of what is actually on my system now, which is what pkgtool and slackpkg show?
Ok, after our discussion on FB I looked a little closer at the code:
1. I misunderstood the purpose of the function, which was to update packages in the patches dir of a release version. Since I am running the current version things work a little differently I think.
2.The program is pulling the version as it was intended to, since I upgraded from 14.1 to current through slackpkg the slackware-version file still showed 14.1, and it was showing me the packages available in that release's patches.
Thanks for your time, and Have a Great Day!
Last edit: Dave Reese 2014-08-15
Feel free to delete the posts above to clean this up ...since it was never a "bug" just a misunderstanding on my part. I would have deleted them myself but I couldn't find any way to do it.
Thanks!