SBo scripts not building on current (read 1st post, pls)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,070
Rep:
Quote:
Originally Posted by Bouboulov
libiptcdata won't build on version 1.0.4 anymore.
Confirmed. Python2-related error:
Code:
checking for python... /usr/bin/python
checking for a version of Python >= '2.1.0'... File "<string>", line 1
import sys, string; ver = string.split(sys.version)[0]; print ver >= '2.1.0'
^
SyntaxError: invalid syntax
no
configure: error: in `/tmp/SBo/libiptcdata-1.0.4':
configure: error:
This version of the AC_PYTHON_DEVEL macro
doesn't work properly with versions of Python before
2.1.0. You may need to re-run configure, setting the
variables PYTHON_CPPFLAGS, PYTHON_LDFLAGS, PYTHON_SITE_PKG,
PYTHON_EXTRA_LIBS and PYTHON_EXTRA_LDFLAGS by hand.
Moreover, to disable this check, set PYTHON_NOVERSIONCHECK
to something else than an empty string.
I tested on -current and works with python pointing to python3.
The seebang on the file is for "python" ... on 15.0 are python2 pointing and works, but on -current points to python3 and need the file updated to support python3.
Thanks!
As i say , no need touch nothing, only push an updated python file.
Last edited by USUARIONUEVO; 03-25-2024 at 05:07 PM.
I tested on -current and works with python pointing to python3.
The seebang on the file is for "python" ... on 15.0 are python2 pointing and works, but on -current points to python3 and need the file updated to support python3.
Thanks!
As i say , no need touch nothing, only push an updated python file.
unfortunately looks like the maintainer of the nvidia-firmware script abandoned all of its scripts, this specifically hadn't been updated in 6 years: you could write to him to take care of this or you could step in as a maintainer but, I'm sorry, I won't touch this neither with a long pole.
unfortunately looks like the maintainer of the nvidia-firmware script abandoned all of its scripts, this specifically hadn't been updated in 6 years: you could write to him to take care of this or you could step in as a maintainer but, I'm sorry, I won't touch this neither with a long pole.
Thanks! , you make me laungh.
No mantainer ,but contact the mantainer ..hahaha.
In the case he contact me, can say do nothing , cause 15.0 no have problems.
Is a -current problem.
Last edited by USUARIONUEVO; 03-26-2024 at 01:05 PM.
In the case he contact me, can say do nothing , cause 15.0 no have problems.
Is a -current problem.
ok, so as it doesn't have a maintainer and nobody seems interested (you too) I'll remove it from the current repository (I won't maintain myself abandoned and non-working scripts, I hope you understand).
The file /tmp/SBo/libpst-0.6.76/.libs/libpst.so is present as a symlink, and points to libpst.so.4.1.18 in the same directory.
There's code in the SlackBuild meant to ignore Python2 if it isn't present. Perhaps it's detecting an incomplete installation of Python2?
I don't have need for libpst, as I've been retired for over two years and no longer have any need to import a PST file, but I just wanted to raise a flag.
The file /tmp/SBo/libpst-0.6.76/.libs/libpst.so is present as a symlink, and points to libpst.so.4.1.18 in the same directory.
There's code in the SlackBuild meant to ignore Python2 if it isn't present. Perhaps it's detecting an incomplete installation of Python2?
I don't have need for libpst, as I've been retired for over two years and no longer have any need to import a PST file, but I just wanted to raise a flag.
Thanks.
just delete these lines from the SlackBuild and you should be good to go
Code:
--- ./libpst.SlackBuild.orig 2024-03-23 15:52:42.265158000 +0100
+++ ./libpst.SlackBuild 2024-03-26 22:54:42.286158000 +0100
@@ -128,29 +128,8 @@
# first build). autotools doesn't make it easy or even necessarily
# possible to build only part of a project :(
-# Python 2 build. If python2 ever really does go away, this code will
-# silently omit python2 support from the package.
-if type -p python2 &>/dev/null; then
- PY2VER="$( python2 --version 2>&1 | cut -d' ' -f2 | cut -d. -f1,2 )"
-
- # ./configure --help claims that I can set PYTHON_VERSION in the environment
- # and it'll use that, but it doesn't work. So I have to use this abomination:
- sed -i.bak 's,\<python3\..\>,python'$PY2VER',g' m4/ax_python.m4
-
- buildit
-
- mv $PKG/usr/lib$LIBDIRSUFFIX/python$PY2VER $PKG/.keep.python2
- rm -rf $PKG/*
-
- # put everything back the way it was.
- make distclean
- mv m4/ax_python.m4.bak m4/ax_python.m4
-fi
-
# Python 3 build
buildit
-[ -e $PKG/.keep.python2 ] && \
- mv $PKG/.keep.python2 $PKG/usr/lib$LIBDIRSUFFIX/python$PY2VER
gzip -9 $PKG/usr/man/man?/*.?
just delete these lines from the SlackBuild and you should be good to go
Code:
--- ./libpst.SlackBuild.orig 2024-03-23 15:52:42.265158000 +0100
+++ ./libpst.SlackBuild 2024-03-26 22:54:42.286158000 +0100
@@ -128,29 +128,8 @@
# first build). autotools doesn't make it easy or even necessarily
# possible to build only part of a project :(
-# Python 2 build. If python2 ever really does go away, this code will
-# silently omit python2 support from the package.
-if type -p python2 &>/dev/null; then
- PY2VER="$( python2 --version 2>&1 | cut -d' ' -f2 | cut -d. -f1,2 )"
-
- # ./configure --help claims that I can set PYTHON_VERSION in the environment
- # and it'll use that, but it doesn't work. So I have to use this abomination:
- sed -i.bak 's,\<python3\..\>,python'$PY2VER',g' m4/ax_python.m4
-
- buildit
-
- mv $PKG/usr/lib$LIBDIRSUFFIX/python$PY2VER $PKG/.keep.python2
- rm -rf $PKG/*
-
- # put everything back the way it was.
- make distclean
- mv m4/ax_python.m4.bak m4/ax_python.m4
-fi
-
# Python 3 build
buildit
-[ -e $PKG/.keep.python2 ] && \
- mv $PKG/.keep.python2 $PKG/usr/lib$LIBDIRSUFFIX/python$PY2VER
gzip -9 $PKG/usr/man/man?/*.?
Thanks! That did the trick. Hopefully, this will help someone else.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,646
Rep:
puddletag needs two patches because of recent changes to pyparsing. The issue will be solved when pyparsing will have got an update to 3.1.3 from what I've read.
Without the patches puddletag compiled but would throw an error (when started from command line) and deny to start. It starts with only the first patch applied, but I have not tested if I would get an error on any tagging operation.
python-colour is failing on -current after the python-3.11 upgrade. I maintain this package since it is a dependency of Polychromatic. I am working on it, but if anyone wants to tag in or has any ideas on how to fix please let me know.
Code:
Building package for python-colour...
colour-0.1.5/.package
Missing version information: running './autogen.sh'...
/usr/lib/python3.11/site-packages/setuptools/dist.py:476: SetuptoolsDeprecationWarning: Invalid dash-separated options
!!
********************************************************************************
Usage of dash-separated 'description-file' will not be supported in future
versions. Please use the underscore name 'description_file' instead.
By 2024-Sep-26, you need to update your project and remove deprecated calls
or your builds will no longer be supported.
See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
********************************************************************************
!!
opt = self.warn_dash_deprecation(opt, section)
/usr/lib/python3.11/site-packages/setuptools/dist.py:476: SetuptoolsDeprecationWarning: Invalid dash-separated options
!!
********************************************************************************
Usage of dash-separated 'requires-dist' will not be supported in future
versions. Please use the underscore name 'requires_dist' instead.
By 2024-Sep-26, you need to update your project and remove deprecated calls
or your builds will no longer be supported.
See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
********************************************************************************
!!
opt = self.warn_dash_deprecation(opt, section)
/usr/lib/python3.11/site-packages/setuptools/__init__.py:81: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!
********************************************************************************
Requirements should be satisfied by a PEP 517 installer.
If you are using pip, you can try `pip install --use-pep517`.
********************************************************************************
!!
dist.fetch_build_eggs(dist.setup_requires)
Traceback (most recent call last):
File "/tmp/SBo/colour-0.1.5/setup.py", line 61, in <module>
setup(
File "/usr/lib/python3.11/site-packages/setuptools/__init__.py", line 104, in setup
return distutils.core.setup(**attrs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 147, in setup
_setup_distribution = dist = klass(attrs)
^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/setuptools/dist.py", line 307, in __init__
_Distribution.__init__(self, dist_attrs)
File "/usr/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 283, in __init__
self.finalize_options()
File "/usr/lib/python3.11/site-packages/setuptools/dist.py", line 658, in finalize_options
ep(self)
File "/usr/lib/python3.11/site-packages/setuptools/dist.py", line 678, in _finalize_setup_keywords
ep.load()(self, ep.name, value)
File "/usr/lib/python3.11/site-packages/d2to1/core.py", line 30, in d2to1
from setuptools.dist import _get_unpatched
ImportError: cannot import name '_get_unpatched' from 'setuptools.dist' (/usr/lib/python3.11/site-packages/setuptools/dist.py)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.