[SOLVED] weird behaviour of slackpkg (slackpkgplus?) compared to slapt-get
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.
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Rep:
weird behaviour of slackpkg (slackpkgplus?) compared to slapt-get
While I was trying the package slapt-get and tested it, I was surprised to see that:
- slapt-get showed me python-docutils to upgrade from 0.16 to 0.17 version
- I looked at /var/log/packages to see if python-docutils was really 0.16, and it was
- "slackpkg upgrade-all" didn't show me python-docutils to upgrade
I have no package of that sort in blacklist of greylist of slackpkg.
I have the same mirror for slackpkg and SOURCE for slapt-get.
Can someone make the same test as me?
Is it a corner case?
I always use "slackpkg update && slackpkg upgrade-all", so I was suprised when I used "slapt-get --upgrade" to see there was a package which was not updated.
So I re-ran "slackpkg update && slackpkg upgrade-all" and nothing was to upgrade.
Then I listed the packages installed:
# ls /var/log/packages/python-docutils*
it was version 0.16 of the package:
- so "slapt-get --upgrade" was right
- "slackpkg upgrade-all" was wrong.
it was version 0.16 of the package:
- so "slapt-get --upgrade" was right
- "slackpkg upgrade-all" was wrong.
I don't really know much about how slackpkg works, but I would assume that "slackpkg upgrade-all" works totally correctly, but "slackpkg update" checked a mirror that hadn't been synchronised with the authoritative source. My humble understanding is that "slackpkg update" creates a list of things to be updated, and "slackpkg upgrade-all" reads that list and upgrades what's listed.
I just considered the idea to enhance "slackpkg update" for a function to check all available mirrors for the most recent version, and then create the update list from that mirror, BUT I don't think it would be a great idea, because
(1) Whenever the original Slackware server gets some updates it would be overrun, because it always will take the mirrors a while to get sync'ed
(2) The first mirrors updated will share that fate, and mirror operators won't be too happy about that
(3) It would take a while to scan all the mirrors, so I would expect a noticeable decrease of slackpkg performance
So if, and only if, slackpkg would be extended in that way, it should be possible to invoke it with that function alone, independent of update, upgrade-all etc., and it would have to be possible to exclude the original Slackware server and some authoritative mirrors from the list of mirrors to be scanned in order to ensure smooth and scalable mirror operation.
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Original Poster
Rep:
the mirror site is exactliy the same, and before upgrade I checked on the mirror the presence of the package: it was there!
- "slackpkg upgrade-all" didn't see it
- "slapt-get --upgrade" saw it
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Original Poster
Rep:
Exactly the same result after downgrade:
- slackpkg upgrade-all: nothing
- slapt-get --upgrade : python-docutils
I enclosed my slackpkgplus.conf and slapt-getrc files, if someone can do the same thing I did: downgrade to 0.16 from cumulative mirror (http://slackware.uk/cumulative/slack.../slackware64/l) and use the same mirror. Tell me what's the result on your side.
You can search specific files using "slackpkg file-search file".
---------------------------------------
Either the problem is in slackpkgplus or in my slackpkgplus.conf?
Any idea?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.