[SOLVED] Slackpkg+: searching for current packages at cgit.ponce.cc not working (slackpkg+-1.7.9-noarch-1mt)

chrisretusn · 12-06-2021, 07:29 AM

Quote:

Originally Posted by drew_gui

No need to guess

it's mentioned in the original post you quoted

HeHe, yeah I figured that, just do like the word assume so I use guess.

Strange. It's working here no issues. I don't normally enable this. I even enabled the 14.2 SBo and all is working as expected.

Here is a copy of my slackpkgplus.conf as it is right now: The red comments I added to the code block

Code:

SLACKPKGPLUS=on
VERBOSE=0
USETERSE=off
TERSESEARCH=on # My default is off.
ALLOW32BIT=on
USEBL=on
LEGACYBL=off
WGETOPTS="--timeout=20 --tries=2"
SEARCH_CLOG_INPARENT=on
CACHEUPDATE=on
ENABLENOTIFY=on
GREYLIST=on
SENSITIVE_SEARCH=off
WW_FILE_SEARCH=off
SHOWORDER=package
DETAILED_INFO=basic
STRICTGPG=on
PKGS_PRIORITY=( slackware64:gcc ) # 2020-09-17 override multilib.
PKGS_PRIORITY+=( justpkgs )
PKGS_PRIORITY+=( nonslack )
PKGS_PRIORITY+=( slackpkgplus )
PKGS_PRIORITY+=( multilib restricted alienbob )
TAG_PRIORITY=off
REPOPLUS=( justpkgs )
REPOPLUS+=( nonslack )
REPOPLUS+=( slackpkgplus )
REPOPLUS+=( multilib restricted alienbob )
MIRRORPLUS['justpkgs']=dir://home/non-slack/justpkgs/
MIRRORPLUS['nonslack']=file://home/non-slack/slackbuilds/
MIRRORPLUS['slackpkgplus']=https://slakfinder.org/slackpkg+dev/
MIRRORPLUS['multilib']=file://home/non-slack/multilib/current/
MIRRORPLUS['restricted']=file://home/non-slack/alienbob_restricted/current/x86_64/
MIRRORPLUS['alienbob']=file://home/non-slack/alienbob/current/x86_64/
SBO['14.2']=https://www.slackbuilds.org/slackbuilds/14.2/ # My default is commented out.
SBO['current']=https://cgit.ponce.cc/slackbuilds # My default is commented out.

Here is the output:

Code:

~# slackpkg search ffmpeg

Looking for ffmpeg in package list. Please wait... DONE

The list below shows all packages with name matching "ffmpeg".

[inst] nonslack    : ffmpeg-compat32-4.4-x86_64-2aliencompat32
[inst] restricted  : ffmpeg-4.4.1-x86_64-1alien
[inst] slackware64 : ffmpegthumbnailer-2.2.2-x86_64-3
[inst] slackware64 : ffmpegthumbs-21.08.3-x86_64-1
[unin] alienbob    : ffmpeg3-compat-3.4.6-x86_64-1alien
[unin] alienbob    : gst-plugins-ffmpeg0-0.10.13-x86_64-2alien
[mask] alienbob    : ffmpeg-4.4.1-x86_64-1alien
[mask] multilib    : ffmpeg-compat32-4.4.1-x86_64-2compat32
[mask] slackware64 : ffmpeg-4.4.1-x86_64-2

You can search specific files using "slackpkg file-search file".


Also found in SBo (download it with 'slackpkg download <package>'):

[ package ]
  alsa-plugin-ffmpeg-1.1.1-sbo-14.2
  audacious-ffmpeg-3.7.2-sbo-14.2
  ffmpegthumbnailer-2.2.0-sbo-14.2
  ffmpeg-3.2.4-sbo-14.2
  ffmpeg2theora-0.30-sbo-14.2
  ffmpeg4-4.3.2-sbo-14.2
  gst0-ffmpeg-0.10.13-sbo-14.2
  opera-developer-ffmpeg-codecs-0.44.1-sbo-14.2
  opera-ffmpeg-codecs-0.44.1-sbo-14.2
  ffmpeg2theora-0.30-sbo-current
  gst0-ffmpeg-0.10.13-sbo-current
  opera-developer-ffmpeg-codecs-0.44.1-sbo-current
  opera-ffmpeg-codecs-0.44.1-sbo-current

For what is worth, I don't see much use in having both of the SBO lines uncommented, since one would be using one or the other not both on the machine you are using slackpkg.

You could try removing '/var/cache/packages' and '/var/lib/slackpkg/'; then run:

Code:

slackpkg update gpg
slackpkg update

To recreate those directories.

The VEBOSE=3 will keep the /tmp/slackpkg.* directories, what's inside that directory is what is use to help debug.

You are using the correct version:

Code:

~# slackpkg help | grep ^slackpkg
slackpkg - version 15.0.8 / slackpkg+ 1.7.9

You are aware that downloading from those two does not download a package, only the SlackBuild and associated files and does not include the source tarballs.

Edit: You might want to drop a link to this thread in slackpkg+ 1.8, as the slackpkg+ developer monitors that one.

drew_gui · 12-06-2021, 07:04 PM

Quote:

Originally Posted by chrisretusn

You could try removing '/var/cache/packages' and '/var/lib/slackpkg/'; then run:

Code:

slackpkg update gpg
slackpkg update

To recreate those directories.

Thank you! I cleared both of those out, and now I have maybe an interesting development...

Code:

root@slackpad:~# slackpkg update gpg

You have selected a mirror for Slackware -current in /etc/slackpkg/mirrors,
but Slackware version 15.0 appears to be installed.

Slackware -current is the development (i.e. unstable) tree.

Is this really what you want?

To confirm your choice, press Y, else press N. Then, press Enter:

I wonder if maybe my system is seen as 15 instead of -current, and it's causing issues? This essentially a fresh install, and it's entirely possible I haven't upgraded to current correctly. Or are we just close enough to 15.0 that current is now calling itself 15

Code:

root@slackpad:~# grep -v ^# /etc/slackpkg/mirrors
https://mirrors.slackware.com/slackware/slackware64-current/

Code:

root@slackpad:~# cat /etc/os-release 
NAME=Slackware
VERSION="15.0"
ID=slackware
VERSION_ID=15.0
PRETTY_NAME="Slackware 15.0 x86_64"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:slackware:slackware_linux:15.0"
HOME_URL="http://slackware.com/"
SUPPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"
BUG_REPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"
VERSION_CODENAME=stable
root@slackpad:~#

Quote:

Originally Posted by chrisretusn

You are aware that downloading from those two does not download a package, only the SlackBuild and associated files and does not include the source tarballs.

Yes, completely my fault for using incorrect terminology. I should have titled the thread "searching for current slackbuilds not working" rather than "searching for current packages not working"

Quote:

Originally Posted by chrisretusn

Edit: You might want to drop a link to this thread in slackpkg+ 1.8, as the slackpkg+ developer monitors that one.

Nice thank you, I don't know how I missed that thread before I posted

drew_gui · 12-06-2021, 07:12 PM

Actually it looks like that fixed it, something in either /var/lib/slackpkg or /var/cache/packages was causing the issue

After deleting those directories, the fresh slackpkg update reports:

Code:

...
2021-12-06 20:08:16 URL:https://cgit.ponce.cc/slackbuilds/snapshot/slackbuilds-current-20211204.1.tar.gz [17849847] -> "/tmp/slackpkg.eJnYDh/slackbuilds-current-20211204.1.tar.gz" [1]
...

and I can search ponce for current slackbuilds without issue:

Code:

root@slackpad:~# slackpkg search xmonad

Looking for xmonad in package list. Please wait... DONE

No package name matches the pattern.

Also found in SBo (download it with 'slackpkg download <package>'):

[ package ]
  xmonad-0.15-sbo-current
  xmonad-contrib-0.15-sbo-current


root@slackpad:~#

Thank you for your time everyone

marking this thread solved

chrisretusn · 12-07-2021, 02:56 AM

Glad you got it figured out.

I get the same results.

Code:

~# slackpkg search xmonad

Looking for xmonad in package list. Please wait... DONE

No package name matches the pattern.

Also found in SBo (download it with 'slackpkg download <package>'):

[ package ]
  xmonad-contrib-0.15-sbo-current
  xmonad-0.15-sbo-current

Quote:

Originally Posted by drew_gui

Thank you! I cleared both of those out, and now I have maybe an interesting development...

Code:

root@slackpad:~# slackpkg update gpg

You have selected a mirror for Slackware -current in /etc/slackpkg/mirrors,
but Slackware version 15.0 appears to be installed.

Slackware -current is the development (i.e. unstable) tree.

Is this really what you want?

To confirm your choice, press Y, else press N. Then, press Enter:

I wonder if maybe my system is seen as 15 instead of -current, and it's causing issues? This essentially a fresh install, and it's entirely possible I haven't upgraded to current correctly. Or are we just close enough to 15.0 that current is now calling itself 15

That happened because you wiped out /var/lib/slackpkg/, that is were the file "current" is stored that lets slackpkg now you are on -current.