Yes, I have many packages that are behind per sbocheck. My next thing to
try would be to bring them all up to date but I'm not optimistic, based
on what little I know about what the build needs (which is admittedly
very little.)
I'll spare you the long list. Is it worth rebuilding the ones tagged as
"bumped"?
Here's output of "pip3 list"
Package Version
-------------------------- ----------
appdirs 1.4.4
atomicwrites 1.3.0
attrs 21.4.0
beautifulsoup4 4.12.3
beniget 0.4.1
Brotli 1.0.9
bsddb3 6.2.6
build 1.3.0
caca 0.99b19
calver 2022.6.26
certifi 2021.10.8
cffi 1.15.0
chardet 4.0.0
charset-normalizer 2.0.10
cppy 1.2.0
cssselect 1.2.0
cupshelpers 1.0
cycler 0.11.0
Cython 0.29.36
deprecation 2.1.0
distro 1.6.0
dnspython 2.1.0
docutils 0.17.1
doxypypy 0.8.8.6
doxyqml 0.5.1
editables 0.6
et-xmlfile 2.0.0
exceptiongroup 1.2.0
flit_core 3.12.0
flit_scm 1.7.0
future 0.18.2
gast 0.5.4
getmail6 6.18.6
gi-docgen 2023.1
gpg 1.16.0
gramps 5.1.2
gyp 0.1
hatch-vcs 0.3.0
hatchling 1.18.0
html5lib 1.1
idna 3.3
imageio 2.34.1
img2pdf 0.4.0
importlib-metadata 4.10.1
include_server 3.4
iniconfig 2.0.0
installer 0.7.0
Jinja2 3.0.3
kapidox 5.90.0
kiwisolver 1.4.1
lensfun 0.3.95
libtorrent 2.0.10
libwebp 0.0
lxml 5.2.1
M2Crypto 0.38.0
Mako 1.1.6
Markdown 3.3.4
MarkupSafe 2.0.1
matplotlib 3.4.3
mercurial 6.0.1
meson 0.59.4
meson-python 0.18.0
more-itertools 4.1.0
mpmath 1.3.0
netsnmp-python 1.0a1
networkx 2.8.8
nftables 0.1
notify2 0.3.1
numpy 1.26.3
opencv-python 4.8.0.76
openpyxl 3.1.5
packaging 21.3
pathlib2 2.3.2
pathspec 1.1.1
pbr 5.8.0
pdfarranger 1.10.1
pep517 0.12.0
pikepdf 5.3.2
Pillow 8.4.0
pip 21.3.1
pluggy 1.3.0
ply 3.11
protobuf 3.20.1
pssh 2.3.4
pwquality 1.4.4
py 1.11.0
pybind11 2.11.1
pycairo 1.20.1
pycparser 2.21
pycups 2.0.1
pycurl 7.44.1
Pygments 2.10.0
PyGObject 3.42.0
PyICU 2.8
pyparsing 2.4.7
pyproject_hooks 1.2.0
pyproject-metadata 0.9.1
PyQt5 5.15.2
PyQt5_sip 4.19.25
pysol-cards 0.12.0
pytaglib 1.4.6
pytesseract 0.3.10
pytest 7.4.3
pytest-runner 6.0.0
python-dateutil 2.8.2
python-sane 2.9.1
pythran 0.15.0
pytz 2021.3
pyxdg 0.27
PyYAML 6.0
QScintilla 2.11.6
random2 1.0.1
requests 2.26.0
rpm 4.16.1.3
scipy 1.12.0
SCons 4.2.0
setuptools 57.5.0
setuptools-scm 6.3.2
setuptools-scm-git-archive 1.4.1
sip 4.19.25
six 1.16.0
smartypants 2.0.1
soupsieve 2.5
sympy 1.11.1
toml 0.10.2
tomli 1.2.2
tornado 6.1
trove-classifiers 2023.11.14
typing_extensions 4.15.0
typogrify 2.0.7
undervolt 0.3.0
Unidecode 1.3.8
urllib3 1.26.8
webencodings 0.5.1
wheel 0.45.1
zipp 3.8.0
Finally, "ls -l /opt/python3.9/site-packages/":
drwxr-xr-x 2 root root 4096 May 25 11:40 meson-1.11.1.dist-info/
drwxr-xr-x 17 root root 4096 May 25 11:40 mesonbuild/
drwxr-xr-x 4 root root 4096 May 25 11:25 packaging/
drwxr-xr-x 3 root root 4096 May 25 11:25 packaging-26.2.dist-info/
drwxr-xr-x 5 root root 4096 Jul 4 2025 setuptools_scm/
drwxr-xr-x 2 root root 4096 Jul 4 2025 setuptools_scm-8.3.1.dist-info/
I'll report back after I upgrade my SBo packages.
thanks,
Judah
On 5/25/26 15:25, fourtysixandtwo wrote:
I just wanted to see the output of pip3 check, those are normal unless
you run it as "PYTHONPATH=/opt/python3.9/site-packages pip3 check" so
it can see the "-opt" packages which are primarily needed only at
build time.
Does sbocheck list any other builds that need updating?
Can you share the output of "pip3 list" and "ls -l
/opt/python3.9/site-packages/"?
On Mon, May 25, 2026 at 10:17 AM J. Milgram via SlackBuilds-users
<[email protected]> wrote:
OK, thanks.
sboremove -a python3-setuptools-opt
... came up with the seven packages you suggest and removed them. (Just
out of curiosity, what's the easy way to generate the dependency chain?)
Then, to make sure I was in step with the stock distro:
slackpkg update
slackpkg upgrade-all
slackpkg install-new
slackpkg clean-system
... no packages were removed or installed. (SBo packages being blacklisted.)
Then sboinstall python3-setuptools-opt
... and ignored offers to set build options (python3-setuptools-opt
only). Confirmed the install queue:
Install queue: python3-flit_core python3-installer
python3-pyproject-hooks python3-build python3-packaging-opt
python3-wheel python3-setuptools-opt
and let it do its thing. Looks like it successfully built and installed
six of the seven packages, but failed again on python3-setuptools-opt with:
File
"/usr/lib64/python3.9/site-packages/importlib_metadata/_itertools.py",
line 16, in unique_everseen
k = key(element)
AttributeError: 'PathDistribution' object has no attribute
'_normalized_name'
(I can provide the whole traceback if it's of any use.)
To fourtysixandtwo's question:
python3 --version
Python 3.9.25
myhost:~: pip3 check
meson-python 0.18.0 has requirement meson>=0.64.0; python_version <
"3.12", but you have meson 0.59.4.
meson-python 0.18.0 has requirement packaging>=23.2, but you have
packaging 21.3
Well, that's interesting. Then did:
ls /var/log/packages/*meson* ...
var/log/packages/meson-0.59.4-x86_64-1
/var/log/packages/python3-meson-opt-1.10.2-noarch-1_SBo
/var/log/packages/python3-mesonpy-0.18.0-x86_64-1_SBo
meson-0.59.4 seems to be from the stock Slack 15.0 package. "slackpkg
upgrade meson" didn't find any new packages. So i tried:
sboupgrade python3-meson-opt
... and it built python3-meson-opt-1.11.1 successfully, but didn't solve
the python3-setuptools-opt problem.
Could it be that I need to do something more to cause the build to
pick up meson and packaging from /opt/python3.9/site-packages? I note that
PYTHONPATH=/opt/python3.9/site-packages pip3 check
... tells me:
No broken requirements found.
I thought the next logical thing to try would be:
PYTHONPATH=/opt/python3.9/site-packages sboinstall python3-setuptools-opt
... but this yielded same error as above.
PS thanks again ...
r/
Judah
On 5/25/26 03:25, Christoph Willing wrote:
On 25/5/26 16:51, J. Milgram via SlackBuilds-users wrote:
[snip]
So I'm guessing I have a package version mismatch of some sort, but
can't figure out what it might be.
Does anyone recognize this error? Any tips on running it to ground?
FWIW this is an up-to-date Slack64-15.0 system. Some SBo's are a
minor number or two behind but I'm already running into SBo packages
that fail to upgrade because sbotools tries first to upgrade
python3-setuptools-opt, which build fails.
grateful for any ideas!
If you suspect package mismatch somewhere, I recommend you first
remove setuptools-opt and its dependants and dependants of dependants
etc. and build _new_ packages for _all_ of them (don't assume any
existing packages are OK). Fortunately the dependency chain is not too
long e.g.
python/python3-flit_core
python/python3-installer
python/python3-wheel
python/python3-pyproject-hooks
python/python3-build
python/python3-packaging-opt
python/python3-setuptools-opt
chris
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
--
=====
[email protected]
301-257-7069
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
--
=====
[email protected]
301-257-7069
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
