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.
Have you closed slackpkg with ctrl+C ?
the trace does not tell me that you reply with I at the question "Select your action (R/I)". (Yes, you had not the question since it was hidden)
you have to rerun the test, then press I to ignore, then press N to not upgrade. Even if you do not see the question.
The trace may not show the response but I did respond "i" then enter. Dropped right to bash prompt after that. Just did it again to confirm and compare files.
The blacklist is used in two part of slackpkg/slackpkg+
The first is when slackpkg starts searching the duplicated packages.
In that moment the blacklist is used strictly as EXACT MATCH.
so if you have
kernel-modules-5.10.13-x86_64-1
kernel-modules-5.10.14-x86_64-1
in packages, it will find in blacklist the presence of "kernel-modules", not "kernel.*" nor "kernel-modules.*"
so if you put 'kernel-modules' in blacklist you will no longer have the warning of duplicated packages.
This is indipendent from slackpkg+ since is slackpkg code.
the second is when you search for packages to install/upgrade.
Here you can find the difference from slackpkg and slackpkg+, and the difference from a slackpkg+ with slackpkg on 14.2, on 15.0, on current prior last update, and beta.
To save backward compatibility slackpkg+ (both stable and dev) use a legacy blacklist method.
Now that slackpkg 15 was released, may be possible to develop something, but I don't know exactly what I will do.
The confusion is increased from the bug of slackpkg+1.7d1-12 that did not know slackpkg-15
I hope I explained all
if you want to be sure put "kernel-modules" without .* and you will solve all.
... in packages, it will find in blacklist the presence of "kernel-modules", not "kernel.*" nor "kernel-modules.*"
so if you put 'kernel-modules' in blacklist you will no longer have the warning of duplicated packages...
It works! That fixes my multiple kernel issue. Thanks zerouno!
Try that:
edit /usr/libexec/slackpkg/functions.d/slackpkgplus.sh
at line 1735 replace "2.84" with "15.0"
So that it's not using the legacy blacklist, which I note that the code now checks for "15.0" in -13mt.
"slackpkg update-all"
"slackpkg upgrade-kernel"
Work as expected.
Code:
slackpkg upgrade-all
Checking local integrity... DONE
Looking for packages to upgrade. Please wait... DONE
No packages match the pattern for upgrade. Try:
/usr/sbin/slackpkg install|reinstall
However, changing "kernel-source" to "kernel-source.*" produces:
Code:
slackpkg upgrade kernel
Checking local integrity... DONE
You have a broken /var/log/packages/ - with two versions of the same package.
The list of packages duplicated in your machine is shown below, but don't
worry about this list - when you select your action, slackpkg will show a
better list:
kernel-source-5.10.13-noarch-1
kernel-source-5.10.14-noarch-1
You can (R)emove, or (I)gnore these packages.
Select your action (R/I): i
Is there a reason that kernel-source treated differently that the other kernel-* packages?
All in all, everything looks good in all of my testing with slackpkg - version 15.0 / slackpkg+ 1.7.0d1 -13mt
Pat just pushed out the patch (by PiterPUNK, original slackpkg author!) from slackpkg git to fixup the new-config usage after upgrade. As far as I know, the only other issue that's surfaced is the duplicate kernel packages (but it could be *any* dupe packages) being blacklisted but still showing up in results. I'm open to suggestions (more open to patches) on exactly how to fix that.
I upgraded to the dev version (slackpkg+-1.7.0d1-noarch-13mt on -current), no blacklist problems, but I notice that `slackpkg update` now always results in a full download (even when there aren't any ChangeLog differences):
Code:
# slackpkg update
Updating the package lists...
Downloading...
force to download ChangeLog
ChangeLogs
2021-02-10 13:16:36 URL:http://mirrors.us.kernel.org/slackware/slackware64-current/ChangeLog.txt [1295130/1295130] -> "/tmp/slackpkg.7Otyb3/ChangeLog.txt" [1]
2021-02-10 13:16:51 URL:http://slakfinder.org/slackpkg+dev/CHECKSUMS.md5 [1592/1592] -> "/tmp/slackpkg.7Otyb3/CHECKSUMS.md5-slackpkgplus" [1]
2021-02-10 13:17:17 URL:https://slackware.nl/people/alien/sbrepos/current/x86_64/CHECKSUMS.md5 [232240/232240] -> "/tmp/slackpkg.7Otyb3/CHECKSUMS.md5-alienbob" [1]
Files //var/lib/slackpkg/CHECKSUMS.md5.asc and /tmp/slackpkg.7Otyb3/CHECKSUMS.md5.asc differ
Also, with VERBOSE=3, it seems that with slackpkg+ `slackpkg check-updates` is grabbing the full ChangeLog; shouldn't it only compare the CHECKSUMS.md5.asc files like slackpkg does?
slackpkg 15 introduce a new way to check if there are news on changelog.
Unfortunately this is incompatible with slackpkg prior 15.0, and unfortunately slackpkg+ have to work both with slackware current and slackware 14.2
So it use an ibrid way to check it.
My suggest is to use CACHEUPDATE=on in slackpkgplus.conf, so it will not really redownload all files any time.
I hope to find a solution to fix that saving the compatibility with slackware 14.2.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
