OK, makes sense, thanks.
Now for the problem that led to the question:
I'm getting an error upgrading python3-setuptools-opt. Per advice,
ignoring the build options.
The build attempt goes roughly like this:
==========
:~: sudo /usr/sbin/sboupgrade python3-setuptools-opt
CHECKSUMS.md5.asc verified. See /usr/sbo/gpg.log.
...
Setuptools is a fully-featured, actively-maintained, and stable
library designed to facilitate packaging Python projects.
Installs to /opt/python$PYVER/site-packages.
...
It looks like python3-setuptools-opt has options; would you like to set
any when the slackbuild is run? [n]
Proceed with python3-setuptools-opt? [y]
setuptools-80.10.2/
setuptools-80.10.2/LICENSE
setuptools-80.10.2/MANIFEST.in
... < unpacks many files, applies patches > ...
* Getting build dependencies for sdist...
Traceback (most recent call last):
... < long traceback, culminating in > ...
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'
ERROR Backend subprocess exited when trying to invoke
get_requires_for_build_sdist
===========
For quite a while I suspected it had to do with the PYTHONPATH build
option but that now seems not to be the case.
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!
Judah
On 5/24/26 18:47, fourtysixandtwo wrote:
Those instructions are only for use in another slackbuild, they are
not build options for python3-setuptools-opt so you can just ignore
them.
Cheers
On Sun, May 24, 2026 at 4:41 PM J. Milgram via SlackBuilds-users
<[email protected]> wrote:
Dumb question. Where I see something like this in a Slackbuild README:
=========
Add the following before the python3 build commands in your
Slackbuild to use this version over the stock one in 15.0:
PYVER=$(python3 -c 'import sys; print("%d.%d" % sys.version_info[:2])')
export PYTHONPATH=/opt/python$PYVER/site-packages
=========
... sboinstall and sboupgrade will say "It looks like python3-setuptools-opt
has options; would you like to set
any when the slackbuild is run?"
All good. I say "y" and then the question is how to type this in.
First, I presume it's entered without the "export" builtin:
PYVER=<whatever>
PYTHONPATH=/opt/python$PYVER/site-packages
... Else I get a "not a valid identifier" bash error apparently due to the script attempting:
"export PYTHONPATH=<path> foo.Slackbuild" and there's no "foo.Slackbuild" to export.
Other question is, how to enter the lines at the sboinstall prompt: one at a time,
separated by <return>, or both in one line, separated by a semicolon?
I've been "cheating" and entering only the second line, as
PYTHONPATH=/opt/python3.9/site-packages, because I know I'm running 3.9. However, still
curious how multiline input is envisioned to work.
thanks!
Judah
=====
[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/
