[SOLVED] Packfile does not match index

mfoley · 10-17-2021, 10:45 AM

I just attempted to update my sbopkg repository index. I got a bunch (hundreds?) of "Packfile does not match index" messages. Then another bunch of messages like:

Code:

:
system/yeahconsole/yeahconsole.SlackBuild                                                           |   20 +-
 system/yeahconsole/yeahconsole.xml                                                                  |   19 +-
 1794 files changed, 17701 insertions(+), 15047 deletions(-)
 create mode 100644 academic/equalx/qt5fix.diff.gz
 delete mode 100644 accessibility/flite/flite-ldflags-fix.patch
 rename accessibility/flite/{ => man}/flite.1 (100%)
 create mode 100644 accessibility/flite/man/flite_time.1
 create mode 100644 accessibility/flite/man/t2p.1
 delete mode 100644 accessibility/svkbd/old_fontconfig.diff
:
Removing development/CImg/CImg_2.9.8.zip
Removing development/portaudio/portaudit-19.7.0.tar.gz
:
HEAD is now at f4150bb99d2 development/systemtap: Updated for version 4.5.

Repository update complete.

Doing 'man sbopkg' gave:

Code:

# man sbopkg
man: warning: /usr/man/man8/sbopkg.8.tmp.gz: ignoring bogus filename

and then did bring up the man page for section 8. When I went to list potential updates I got:

Code:

# sbopkg -c
[ Checking for potential updates ]
This may take a few moments. Press <ESC> to abort.
100%
Listing installed SBo master git branch packages and flagging potential
updates...

  Note: repo version not obtainable by standard method, may be inaccurate.
portaudio:
  INSTALLED PACKAGE IS NEWER THAN REPO
  Installed version:  portaudio-v190600_20161030-x86_64-1_SBo
  Repo version:  portaudio-19.7.0-x86_64-1_SBo
xvidcore:
  POTENTIAL UPDATE
  Installed version:  xvidcore-1.3.5-x86_64-1_SBo
  Repo version:  xvidcore-1.3.7-x86_64-1_SBo

Potential update list complete.

Note that the portaudio installed version is more recent than the repo.

What's up? I've never seen this before. The sbopkg version is 0.38.2. My previous version was 0.38.1 which is what I used on 14.2. I did upgrade for Slackware-Current, but this is not the first time using sbopkg since that upgrade. Do I need to remove sbopkg and reinstall?

ctrlaltca · 10-18-2021, 04:53 AM

Portaudio 19.7 was released on 20210406, so it's more recent than the version v190600_20161030 you currently have installed.
My guess is that you were using the slackbuild repo for 14.2 (that right now is still at version v190600_20161030) and with the new version of sbopkg you switched to the -current slackbuild repo (that has been updated for portaudio 19.7 on aug. 24).

This would probably explain all the strange messages you got while syncing the repo.
I'd try to clean the sbopkg dir (/var/lib/sbopkg) and re-start with a clean repo.

mfoley · 10-21-2021, 11:41 AM

Quote:

Originally Posted by ctrlaltca

I'd try to clean the sbopkg dir (/var/lib/sbopkg) and re-start with a clean repo.

I did as you suggested and things seem to work. I do get a lot more messages than I used to:

Code:

# sbopkg -r
Syncing with the remote repository into /var/lib/sbopkg/SBo.
From git://git.slackbuilds.org/slackbuilds
 * branch                  master     -> FETCH_HEAD
Already up to date.
Removing office/lyx/lyx-2.3.6.1.tar.xz
HEAD is now at d21008ba05 libraries/lua-lpeg: Fix quote.

Repository update complete.

This is for version 0.38.2. 0.38.1 didn't give all that "branch ..." stuff. Likewise with other sbo command. But, it does appears things are working, so I guess the new messages are just part of the new version.