[SOLVED] slpkg issues

pisti · 02-06-2024, 10:41 AM

i simply want to update an old version of slpkg on my slack150 box(es) and that's when the update/upgrade nirwana begins. ultimately i just need a new version of signal_desktop i wanted to use slpkg for, but that's just on the side for now...

on a first slack150 machine with slpkg 4.2 i was able to upgrade to 4.9.7 (as required for the signal_desktop upgrade) - but then on my 2nd slack150 box with an even older slpkg version 3.9.1 that ipsigenic upgrade of slpkg itself does not work anymore. after updating or freshly installing half a dozen or so SBo packages i seem to be stuck with the following issues - mainly 'tomli' :

Code:

./python3-tomli_w.SlackBuild 
tomli_w-1.0.0/LICENSE
tomli_w-1.0.0/README.md
tomli_w-1.0.0/pyproject.toml
tomli_w-1.0.0/tomli_w/__init__.py
tomli_w-1.0.0/tomli_w/_writer.py
tomli_w-1.0.0/tomli_w/py.typed
tomli_w-1.0.0/PKG-INFO
Traceback (most recent call last):
  File "/usr/lib64/python3.7/runpy.py", line 183, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/usr/lib64/python3.7/runpy.py", line 142, in _get_module_details
    return _get_module_details(pkg_main_name, error)
  File "/usr/lib64/python3.7/runpy.py", line 109, in _get_module_details
    __import__(pkg_name)
  File "/usr/lib64/python3.7/site-packages/build/__init__.py", line 40, in <module>
    import tomli as tomllib
ModuleNotFoundError: No module named 'tomli'

Code:

pip3 install --upgrade tomli
Segmentation fault

Code:

./slpkg.SlackBuild 
slpkg-4.9.7/
slpkg-4.9.7/.gitignore
...
slpkg-4.9.7/tools/
slpkg-4.9.7/tools/gen_sbo_txt.sh
Traceback (most recent call last):
  File "/usr/lib64/python3.7/runpy.py", line 183, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/usr/lib64/python3.7/runpy.py", line 142, in _get_module_details
    return _get_module_details(pkg_main_name, error)
  File "/usr/lib64/python3.7/runpy.py", line 109, in _get_module_details
    __import__(pkg_name)
  File "/usr/lib64/python3.7/site-packages/build/__init__.py", line 40, in <module>
    import tomli as tomllib
ModuleNotFoundError: No module named 'tomli'

Code:

slpkg -h
Traceback (most recent call last):
  File "/usr/bin/slpkg", line 35, in <module>
    from slpkg.main import main
ModuleNotFoundError: No module named 'slpkg'

why does such a slpkg upgrade have to be so painfully complicated ??? i usually keep it simple and just use plain SBo scripts with install/removepkg - but occasionally i would want to enjoy the comfort of an automated slackware package manager, for example in the case of upgrading this signal_desktop package...

marav · 02-06-2024, 11:42 AM

Some new dependencies have emerged since 4.2
slpkg 4.9.x needs :

python3-build
SQLAlchemy
python3-pythondialog
python3-progress

fourtysixandtwo · 02-06-2024, 06:34 PM

I'm wondering why you have python3.7 on a slackware 15 box?

Code:

/usr/lib64/python3.7/

pisti · 02-06-2024, 10:59 PM

why python 3.7 - very very bizarr, very weird - i don't know the answer? all my other slack150 boxes run stock 3.9 ! thank you for pointing that out !

what i remember that when i tried to 'upgrade' slpkg 3.9 to something 4ish, than it took a long time to do that, with tons of packages modified...! perhaps by doing so it downgraded to python3.7 - although the slpkg version on the given machine is still 3.9 albeit dysfunctional !

on my home machine, also a slack150 box, the slpkg version was 4.1 something and now it's at 4.9.7. i don't know where this difference between slpkg versions comes from.

so, i mean, i will need to fix that production box' python3 version first, and then see what else went wrong. i hope we don't deal here with uglier things as the box is freely hanging out there on the wild web though access to it is (should be) pretty restricted...

pisti · 02-07-2024, 12:46 PM

so, i am not sure what happened during that slpkg-python3-downgrade-fiesta a few days ago - but i had to fix a few things till my algorithms & programs started to work again as before. i had to reinstall :

Code:

python3-3.9.10-x86_64-1
python3-pythondialog-3.5.3-x86_64-1_SBo
python3-flit_core-3.9.0-x86_64-1_SBo
python3-installer-0.7.0-x86_64-1_SBo
python3-pyproject-hooks-1.0.0-x86_64-1_SBo
python3-build-1.0.3-x86_64-1_SBo
greenlet-2.0.2-x86_64-1_SBo
SQLAlchemy-1.4.51-x86_64-1_SBo
python3-progress-1.6-x86_64-1_SBo
slpkg-4.9.7-x86_64-1_SBo

and with that also the newly upgraded slpkg finally began to work as expected :

Code:

slpkg -h
slpkg - version 4.9.7

USAGE:
  slpkg [COMMAND] [OPTIONS] [FILELIST|PACKAGES...]

DESCRIPTION:
  Package manager utility for Slackware.

COMMANDS:
  -u, update                    Update the package lists.
  -U, upgrade                   Upgrade all the packages.
  -c, check-updates             Check for news on ChangeLog.txt.
  -I, repo-info                 Prints the repositories information.
  -g, configs                   Edit the configuration file.
  -L, clean-logs                Clean all logging files.
  -T, clean-data                Clean all the repositories data.
  -D, clean-tmp                 Delete all the downloaded sources.
  -b, build [PACKAGES...]       Build only the packages.
  -i, install [PACKAGES...]     Build and install the packages.
  -R, remove [PACKAGES...]      Remove installed packages.
  -d, download [PACKAGES...]    Download only the scripts and sources.
  -f, find [PACKAGES...]        Find installed packages.
  -w, view [PACKAGES...]        View packages from the repository.
  -s, search [PACKAGES...]      Search packages from the repository.
  -e, dependees [PACKAGES...]   Show which packages depend on.
  -t, tracking [PACKAGES...]    Tracking the packages dependencies.

OPTIONS:
  -y, --yes                     Answer Yes to all questions.
  -j, --jobs                    Set it for multicore systems.
  -O, --resolve-off             Turns off dependency resolving.
  -r, --reinstall               Upgrade packages of the same version.
  -k, --skip-installed          Skip installed packages.
  -a, --install-data            Install data into the database only.
  -E, --full-reverse            Full reverse dependency.
  -S, --search                  Search packages from the repository.
  -n, --no-silent               Disable silent mode.
  -p, --pkg-version             Print the repository package version.
  -P, --parallel                Download files in parallel.
  -m, --no-case                 Case-insensitive pattern matching.
  -o, --repository=NAME         Change repository you want to work.
  -z, --directory=PATH          Download files to a specific path.

  -h, --help                    Show this message and exit.
  -v, --version                 Print version and exit.

If you need more information try to use slpkg manpage.
Extra help for the commands, use: 'slpkg help [COMMAND]'.
Edit the config file in the /etc/slpkg/slpkg.toml or 'slpkg configs'.

uff, ende gut, alles gut...
with that i marked this as [SOLVED]

fourtysixandtwo · 02-07-2024, 01:56 PM

Was the box upgraded from 14.2 by any chance? python 3.7 was available from the 14.2 SBo branch. slpkg 3.9.1 is also the last version available from the 14.2 branch.

I would check all installed packages are from slackware 15.0 (plus patches) and the 15.0 slackbuilds branch, but I'm guessing that's already your plan.

Here's a bash function to check for any installed _SBo tagged packages that no longer exist in the repo. (it's expected that an "slpkg update" has been run recently and is pointed at the correct branch)

Code:

PKGDIR="/var/lib/pkgtools/packages"

# get list of installed slackbuilds (_SBo tag) that no longer exist in repo
SLACKBUILDS=/var/lib/slpkg/repositories/sbo/SLACKBUILDS.TXT
sbremoved () {
  for i in `( cd $PKGDIR ; ls *_SBo ) | rev |cut -d- -f4-|rev`
  do
    echo -n "$i "
    grep -c "SLACKBUILD NAME: $i$" $SLACKBUILDS
  done | grep 0$
}

pisti · 02-07-2024, 07:50 PM

nop, no slackware upgrade from v142 to v150 - i usually do a full install. as said i had python3.9 installed but somehow on that day (yesterday) happened somehow that downgrading (i am sure there are better ways explaining this). i believe the slpkg v3.9 is the culprit - and me who invoked some silly option with it (without reading the rtfm...).

regarding your function (and thank you for providing the script), here the output on given problem machine (now fixed) :

Code:

source shellfiles/bashfx
sbremoved 
libxkbcommon 0
ninja 0

pretty dry - is that what you would expect under the current circumstances ? (both libxkbcommon and ninja i need by the way in a script that help me locate that tiny mouse cursor in X on my 4K/43inch screen

fourtysixandtwo · 02-07-2024, 08:16 PM

Reading your first post again, my best guess is the slpkg 3.9.1 you had installed was still pointed at the 14.2 SBo repo or some bug to that effect.

Those two should be removed and the versions shipped/patched with 15.0 should be reinstalled. But yes, shouldn't be anything listed normally.