Created a test branch on github to experiment that patches
https://raw.githubusercontent.com/zu...lackpkgplus.sh |
1 Attachment(s)
Hello,
Quote:
Code:
--- slackpkgplus.sh.orig 2020-02-17 10:52:12.134150217 +0100 Code:
$ ls /var/log/packages/ffmpeg-4*
-- SeB |
pushed on test branch
@all, ask for tests Code:
wget -O /usr/libexec/slackpkg/functions.d/slackpkgplus.sh https://raw.githubusercontent.com/zuno/slackpkgplus/test/src/slackpkgplus.sh |
Quote:
Code:
The list below shows all packages with name matching "ffmpeg-4". I installed the slackwre64 version "ffmpeg-4.2.2-x86_64-1" again here is the result of a search after that. This is a correct listing based on my PKGS_PRIORITY settings. Telling me that the installed ffmpeg-4.2.2 slackware64 package needs an upgrade to the restricted package ffmpeg-4.4.1 which is what my PKGS_PRIORITY setting are telling it to do. Code:
The list below shows all packages with name matching "ffmpeg-4". Code:
The list below shows all packages with name matching "ffmpeg-4"; which I consider correct. |
Quote:
Are you trying latest commit from test branch? Code:
wget -O /usr/libexec/slackpkg/functions.d/slackpkgplus.sh https://raw.githubusercontent.com/zuno/slackpkgplus/test/src/slackpkgplus.sh |
Quote:
I downloaded the version you just gave me. It works as well. Listing with slackware64 installed and having version priority. Code:
PKGS_PRIORITY=( nonslack slackpkgplus multilib ktown testing slackware64:ffmpeg restricted slackware64:id3lib alienbob ) Code:
PKGS_PRIORITY=( nonslack slackpkgplus multilib ktown testing restricted slackware64:id3lib alienbob ) Code:
upgrade restricted ffmpeg-4.2.2-x86_64-1 --> ffmpeg-4.2.1-x86_64-1alien When running 'slackpkg -dialog=off upgrade ffmpeg' I get the following, which is the desired result based on my PKGS_PRIORITY setting. Code:
Checking local integrity... DONE Code:
The list below shows all packages with name matching "ffmpeg-4". |
Thankyou
|
pushed on master branch
|
Pushed in 'test' a version to manage
Code:
# Enable TERSE to use a smaller output in installpkg/upgradepkg |
slackpkg+-1.7.0d1-noarch-7mt released
Code:
Tue Feb 18 08:30:10 CET 2020 https://www.linuxquestions.org/quest...ed-4175643527/ https://slackpkg.org/beta/slackpkg-2...arch-1_rlw.txz |
Quote:
slackpkg - version 2.84.0_beta6 / slackpkg+ 1.7.0 When I run 'slackpkg search kernel' I get the following list: Code:
[ Status ] [ Repository ] [ Package ] With these vesions: slackpkg - version 2.84.0_beta6 / slackpkg+ 1.7.0d1 When I run 'slackpkg search kernel' I get the following list: Code:
[ Status ] [ Repository ] [ Package ] |
Hello,
Quote:
Code:
$ USEBL=off slackpkg search kernel SeB |
Yes I know that. It worked before without doing that. So I'm guessing the answer to my question is no?
|
Hello,
Quote:
-- SeB |
slackpkg+ 1.7.0 ignore the blacklist due a bug (introduced 4 years ago), not as a feature.
starts from commit e2a831b918b62ad27bc8cd91ba679f27d8bde6f2 (slackpkg+-search-duplicate-packages-fix-V7.patch.txt) Code:
@@ -1127,7 +1128,7 @@ if [ "$SLACKPKGPLUS" = "on" ];then (try SLACKPKGPLUS=off slackpkg search kernel) slackpkg+ 1.7 did search in ${WORKDIR}/pkglist that means "before blacklist" starting from commit 904088459ab6a238e6c230b5f60afd55259e2a32 (slackpkg 1.7.beta1) In effect was a bug, not a feature :) slackpkg+ now does search in ${WORKDIR}/pkglist that means "after blacklist" I think this is most correct and aligned with slackpkg. So I will add a note in changelog marking it as a fix or alignment with slackpkg or so on, since mentioned patch incidentally also fix it. If you want to skip blacklist use USEBL=0 this is the output of slackpkg+ 1.7.alpha6 and slackpkg+ 1.6 Code:
root@beelink:/etc/slackpkg# slackpkg search kernel |
All times are GMT -5. The time now is 06:20 PM. |