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/
