SBo scripts not building on current (read 1st post, pls)

willysr · 10-10-2021, 10:40 PM

Some scripts still need Python 2.7 and some no longer ported for 3.x but they are still working just fine. That's why Python 2.7 is still being kept by Patrick in core tree.

willysr · 10-10-2021, 10:57 PM

Quote:

Originally Posted by brobr

Catfish needs version 4.16.3 to work with python3.10
http://https://github.com/xfce-mirro...catfish-4.16.3

pushed

USUARIONUEVO · 10-11-2021, 09:15 AM

Hi , kodi not build

Quote:

Player.h:616:45: error: ISO C++17 does not allow dynamic exception specifications

I test c++11 and c++14

But new problems appers around "limits are not memeber of std" ... we need patch , sed , or upgrade version.

brobr · 10-11-2021, 10:17 AM

Quote:

Originally Posted by willysr

Some scripts still need Python 2.7 and some no longer ported for 3.x but they are still working just fine. That's why Python 2.7 is still being kept by Patrick in core tree.

Yes, agreed. But the question is, would it not be KISS to keep the scripts for python2 and python3 separate for the same python module/programX? The problems arise when

Code:

python2 setup.py install
python3 setup.py install

are run in the same script (on the same version for the module). Often, for python3 a version is required that no longer builds on python2. This alone makes separation essential (otherwise we're stuck on outdated versions), which will help in solving problems. Yesterday, when compiling inkscape, the sqg -p generator gave a lot of python2 modules which only were needed to compile lxml or beautifulsoup4 (their scripts were mixing python2 with python3 builds). When erasing the python2 bits from these build scripts and the queue, all went well. The mix caused the problems.

Note, also, that some pip-blinded developers are opting to ditch even the good old 'setup.py', not having our model of distributing compiled packages in mind (all should happen automatically on the box). After a lengthy discussion in the case of leo, this is now also on the go with twine https://github.com/pypa/twine/pull/757.

Maybe this cannot be stopped and we should opt for a kind of system where slackware packages are generated after building using pip. Something along the line what @bifferos once proposed with his afterpkg-python. So that individual python-buildscripts could be bypassed, which would remove a layer of maintance (on SBo) for python stuff..... just an (old) idea.

richarson · 10-11-2021, 10:39 AM

Quote:

Originally Posted by USUARIONUEVO

Hi again.

lxml ,not build part of python3 ,

we need jump to --> lxml-4.6.3

Thanks USUARIONUEVO!

Also not compiling with python 3.10 is BeautifulSoup4, haven't tried bumping the version yet.

USUARIONUEVO · 10-11-2021, 10:51 AM

Quote:

Originally Posted by richarson

Thanks USUARIONUEVO!

Also not compiling with python 3.10 is BeautifulSoup4, haven't tried bumping the version yet.

BeautifulSoup4 builds fine here , you see the README ?

python3-soupsieve is required.

richarson · 10-11-2021, 10:56 AM

Quote:

Originally Posted by USUARIONUEVO

BeautifulSoup4 builds fine here , you see the README ?

python3-soupsieve is required.

I'm using ponce's branch of SBo and the README doesn't say much.
I have both python2-soupsieve and python3-soupsieve installed.

My build stops with:

Code:

Ran 372 tests in 0.242s

OK
error in beautifulsoup4 setup command: use_2to3 is invalid.

I saw something related on this thread but haven't investigated yet.

richarson · 10-11-2021, 11:00 AM

OK, I read the older posts and I see the problem now, what a mess...

richarson · 10-11-2021, 11:04 AM

I also had issues generating docs with Sphinx when building git-cola 3.10.1.

I have bumped the versions like this:

- Sphinx 4.2.0
- sphinxcontrib-htmlhelp 2.0.0
- sphinxcontrib-serializinghtml 1.1.5

After that, git-cola builds fine.

brobr · 10-11-2021, 04:43 PM

Quote:

Originally Posted by richarson

I'm using ponce's branch of SBo ..
My build stops with:

Code:

error in beautifulsoup4 setup command: use_2to3 is invalid.

Yes, this popped up for me as well. Removing all python2 related stuff from the build-script made it all work at my end.

Quote:

Originally Posted by brobr

Note, also, that some pip-blinded developers are opting to ditch even the good old 'setup.py', not having our model of distributing compiled packages in mind (all should happen automatically on the box). After a lengthy discussion in the case of leo, this is now also on the go with twine https://github.com/pypa/twine/pull/757.

We might have to resort to a 3-line as this in Slackbuilds to replace the commented line we normally use:

Code:

#python3 setup.py install --root=$PKG
python3 -m pip install \
    --no-warn-script-location \
    --use-feature=in-tree-build \
    . --root=$PKG

A pythonic improvement ;-?

USUARIONUEVO · 10-11-2021, 06:45 PM

Hi , secretstorage , cant import the new cryptography , need jump to new version

secretstorage --> 3.3.1

easy check , install secretstorage and cryptography , and use pip3 check to see.

USUARIONUEVO · 10-11-2021, 08:09 PM

Problems in nodejs ...

Quote:

Please use python3.9 or python3.8 or python3.7 or python3.6 or python3.5 or python2.7.
/usr/bin/python2.7 ./configure
Node.js configure: Found Python 3.10.0...

Lockywolf · 10-11-2021, 09:39 PM

audit seems to be at DOWNLOAD="https://people.redhat.com/sgrubb/audit/audit-3.0.1.tar.gz" instead of DOWNLOAD="http://people.redhat.com/sgrubb/audit/audit-3.0.1.tar.gz"

I think they turned off plain http altogether.

willysr · 10-11-2021, 09:51 PM

Quote:

Originally Posted by USUARIONUEVO

Hi , secretstorage , cant import the new cryptography , need jump to new version

secretstorage --> 3.3.1

easy check , install secretstorage and cryptography , and use pip3 check to see.

Pushed

willysr · 10-11-2021, 09:52 PM

Quote:

Originally Posted by Lockywolf

audit seems to be at DOWNLOAD="https://people.redhat.com/sgrubb/audit/audit-3.0.1.tar.gz" instead of DOWNLOAD="http://people.redhat.com/sgrubb/audit/audit-3.0.1.tar.gz"

I think they turned off plain http altogether.

Fixed