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

lostintime · 04-06-2024, 07:41 PM

Seem unable to run or build meld 1.8.6 any longer. The errors:

Code:

File "/usr/bin/meld", line 107
print "Couldn't bind the translation domain. Some translations won't work."
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?

Reading around the web indicates this means Python 3 expectations of using parentheses in print statements.

I'm hoping 1.8.6 can be salvaged. Not much enthused about Meld 3. If only Kompare supported inline editing. Oh well.

Thanks.

willysr · 04-07-2024, 12:54 AM

You just need to use python2.7 instead of calling python since probably asking for python 2 instead of python 3

Brent S · 04-07-2024, 05:52 AM

Quote:

Originally Posted by sombragris

Yes I did. In fact, initially ipykernel reported only jupyter_client as a missing dependency. After building jupyter_client, I tried to build and it gave a me an even bigger list of unmet dependencies, I rebuilt them one by one and only these two left. I rebuilt them against Python 3.11 several times, had no trouble doing so, but even then ipykernel complains about this.

I had something similar after the upgrade to 3.11; I think it was resolved when I rebuilt ipython, then jupyter_client, then jupyter-ipykernel. I also noticed (by accident) that jupyter_client can be built without complaint even before some of its first-level dependencies are rebuilt, but of course they can't be found at runtime since the actual libraries are still under the python3.9 site-packages. So, if you're still having problems, double-check that you truly rebuilt and installed each of the jupyter_client dependencies before jupyter_client itself.

(Note to self to contribute a "topologically sort the queue" feature to sbopkg.)

fourtysixandtwo · 04-07-2024, 12:14 PM

To show any installed python3.9 packages to be rebuilt.

Code:

grep -l -m 1 python3.9 /var/log/packages/*|cut -d/ -f5|rev |cut -d- -f 4- |rev

After rebuilding have a look in /usr/lib{,64}/python3.9/site-packages/ and then rm the python3.9 directory once happy.

Daedra · 04-07-2024, 12:21 PM

Quote:

Originally Posted by fourtysixandtwo

To show any installed python3.9 packages to be rebuilt.

Code:

grep -l -m 1 python3.9 /var/log/packages/*|cut -d/ -f5|rev |cut -d- -f 4- |rev

After rebuilding have a look in /usr/lib{,64}/python3.9/site-packages/ and then rm the python3.9 directory once happy.

I was using a similar script. I finally got all my 3.9 SBo packages updated. python3-setuptools-rust-opt was giving me a false positive but that is only because of the slack-desc file.

Code:

python3-setuptools-rust-opt: python3-setuptools-rust-opt (setuptools-rust installed to /opt)
python3-setuptools-rust-opt:
python3-setuptools-rust-opt: setuptools-rust is a plugin for setuptools to build Rust Python
python3-setuptools-rust-opt: extensions implemented with PyO3 or rust-cpython.
python3-setuptools-rust-opt:
python3-setuptools-rust-opt: Installs to /opt/python3.9/site-packages
python3-setuptools-rust-opt:
python3-setuptools-rust-opt:
python3-setuptools-rust-opt: Project URL: https://github.com/PyO3/setuptools-rust/
python3-setuptools-rust-opt:
python3-setuptools-rust-opt:

fourtysixandtwo · 04-07-2024, 12:54 PM

Quote:

Originally Posted by Daedra

I was using a similar script. I finally got all my 3.9 SBo packages updated. python3-setuptools-rust-opt was giving me a false positive but that is only because of the slack-desc file.

Code:

python3-setuptools-rust-opt: python3-setuptools-rust-opt (setuptools-rust installed to /opt)
python3-setuptools-rust-opt:
python3-setuptools-rust-opt: setuptools-rust is a plugin for setuptools to build Rust Python
python3-setuptools-rust-opt: extensions implemented with PyO3 or rust-cpython.
python3-setuptools-rust-opt:
python3-setuptools-rust-opt: Installs to /opt/python3.9/site-packages
python3-setuptools-rust-opt:
python3-setuptools-rust-opt:
python3-setuptools-rust-opt: Project URL: https://github.com/PyO3/setuptools-rust/
python3-setuptools-rust-opt:
python3-setuptools-rust-opt:

Thanks for pointing that out, I'll get that fixed.

lostintime · 04-07-2024, 03:53 PM

Quote:

You just need to use python2.7 instead of calling python since probably asking for python 2 instead of python 3

I don't know if this is correct but the following patch worked for me to build and use meld 1.8.6:

Code:

--- meld.SlackBuild     2024-04-07 15:50:28.531533750 -0500
+++ meld.SlackBuild.new 2024-04-07 15:50:56.630193590 -0500
@@ -79,6 +79,8 @@
\( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
-o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

+export PYTHON=python2
+sed -i 's|/usr/bin/env python|/usr/bin/env python2|' bin/meld
make prefix=/usr libdir=/usr/lib${LIBDIRSUFFIX} docdir=/usr/doc/$PRGNAM-$VERSION DESTDIR=$PKG install

mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION

Back to wishing Kompare had inline editing or meld could be adopted to a Qt/KDE GUI.

Brent S · 04-08-2024, 02:22 PM

I noticed that graphviz 10.0.1 (and probably other SBos) now throws a "CPU you selected does not support x86-64 instruction set" error when building the gvedit tool under slackware64-current. The issue is that the newest qt6-6.6.3_20240319_c2516323-x86_64-1 package sets up qmake6 to generate Makefiles for the 586/686 architecture by default; just remove the "-march=i586 -mtune=i686" flags from two lines in /usr/lib/qt6/mkspecs/common/gcc-base.conf.

qt6 package regression reported to Pat.

Bouboulov · 04-09-2024, 09:23 AM

Hello, python3-PyQtWebEngine won't build. Just posting this to make it updated.

[edit] I used it before to get polychromatic for Razer but it has built without the python3-PyQtWebEngine. It is obsolete ?

ponce · 04-09-2024, 10:32 AM

Quote:

Originally Posted by Bouboulov

Hello, python3-PyQtWebEngine won't build. Just posting this to make it updated.

hi Bouboulov,

I'm not sure what's happening there but FWIW I just built polychromatic together with all of its dependencies (python3-PyQtWebEngine included) from scratch on a fresh install of slackware64-current here.

Quote:

Originally Posted by Bouboulov

[edit] I used it before to get polychromatic for Razer but it has built without the python3-PyQtWebEngine. It is obsolete ?

I don't know the specific of polychromatic, these are actually questions that you should ask to its maintainer (his mail address is listed in the polychromatic.info file).

Daedra · 04-09-2024, 12:29 PM

Quote:

Originally Posted by ponce

hi Bouboulov,

I'm not sure what's happening there but FWIW I just built polychromatic together with all of its dependencies (python3-PyQtWebEngine included) from scratch on a fresh install of slackware64-current here.

I don't know the specific of polychromatic, these are actually questions that you should ask to its maintainer (his mail address is listed in the polychromatic.info file).

I maintain polychromatic and after last weeks SBo update all the required packages and polychrmatic compile on -current. I have tested this on two bare metal machines and a VM.

sombragris · 04-09-2024, 05:19 PM

I don't know whether this is the place or not for this. Apologies in advance.

Pat upgraded texlive to 2024 today. @franzen already has texlive 2024 tarballs for extra and docs, for which I am grateful.

However, biber seems to be missing from both the standard and -extra packages. Is biber to be included in texlive-extra? Thanks in advance.

EDITED: Clarified a mistake in package labels.

J_W · 04-09-2024, 05:33 PM

Hi,
I tried to install vvdec-2.2.0 on my slackware64-current environment.
However, the default slackbuild of vvdec did not install "vvdecapp" binary into /usr/bin directory.

By adding an option "-DVVDEC_INSTALL_VVDECAPP=on" fixed this issue.

diff -Nru vvdec.SlackBuild vvdec.SlackBuild.new

Code:

--- vvdec.SlackBuild	2024-04-10 06:54:43.953357451 +0900
+++ vvdec.SlackBuild.new	2024-04-10 06:51:30.791990703 +0900
@@ -26,7 +26,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=vvdec
-VERSION=${VERSION:-1.6.1}
+VERSION=${VERSION:-2.2.0}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -86,6 +86,7 @@
     -DCMAKE_INSTALL_LIBDIR:PATH=lib${LIBDIRSUFFIX} \
     -DCMAKE_INSTALL_INCLUDEDIR:PATH=include \
     -DBUILD_SHARED_LIBS=1 \
+    -DVVDEC_INSTALL_VVDECAPP=on \
     -DCMAKE_BUILD_TYPE=Release ..
   make
   make install DESTDIR=$PKG

diff -Nru vvdec.info vvdec.info.new

Code:

--- vvdec.info	2023-03-12 10:52:47.000000000 +0900
+++ vvdec.info.new	2024-04-10 06:54:06.089285620 +0900
@@ -1,8 +1,8 @@
 PRGNAM="vvdec"
-VERSION="1.6.1"
+VERSION="2.22.0"
 HOMEPAGE="https://github.com/fraunhoferhhi/vvdec"
-DOWNLOAD="https://github.com/fraunhoferhhi/vvdec/archive/v1.6.1/vvdec-1.6.1.tar.gz"
-MD5SUM="be71114991acce321869abf44c2b72ef"
+DOWNLOAD="https://github.com/fraunhoferhhi/vvdec/archive/v2.2.0/vvdec-2.2.0.tar.gz"
+MD5SUM="6f1cd609e3a656ea66643762fa8399a3"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""

[NOTE] A similar phenomenon occurred in case of vvenc-1.11.1. I will post this in another new post.

J_W · 04-09-2024, 05:51 PM

Hi,
The default slackbuild of vvenc did not install "vvencFFapp" binary from vvenc-1.11.1.
This is a workaround of vvenc-1.11.1 similar to the case of vvdec-2.2.0.
By adding an option "-DVVENC_INSTALL_FULLFEATURE_APP=on" fixed this issue.

diff -Nru vvenc.SlackBuild vvenc.SlackBuild.new

Code:

--- vvenc.SlackBuild	2024-04-10 07:05:22.413504229 +0900
+++ vvenc.SlackBuild.new	2024-04-10 07:03:09.412266978 +0900
@@ -26,7 +26,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=vvenc
-VERSION=${VERSION:-1.7.0}
+VERSION=${VERSION:-1.11.1}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -86,6 +86,7 @@
     -DCMAKE_INSTALL_LIBDIR:PATH=lib${LIBDIRSUFFIX} \
     -DCMAKE_INSTALL_INCLUDEDIR:PATH=include \
     -DBUILD_SHARED_LIBS=1 \
+    -DVVENC_INSTALL_FULLFEATURE_APP=on \
     -DCMAKE_BUILD_TYPE=Release ..
   make
   make install DESTDIR=$PKG

diff -Nru vvenc.info vvenc.info.new

Code:

--- vvenc.info	2023-03-12 10:52:47.000000000 +0900
+++ vvenc.info.new	2024-04-10 07:46:24.483414609 +0900
@@ -1,10 +1,10 @@
 PRGNAM="vvenc"
-VERSION="1.7.0"
+VERSION="1.11.1"
 HOMEPAGE="https://github.com/fraunhoferhhi/vvenc"
 DOWNLOAD="UNSUPPORTED"
 MD5SUM=""
-DOWNLOAD_x86_64="https://github.com/fraunhoferhhi/vvenc/archive/v1.7.0/vvenc-1.7.0.tar.gz"
-MD5SUM_x86_64="bd14534787f4180cd5bebb248b27285f"
+DOWNLOAD_x86_64="https://github.com/fraunhoferhhi/vvenc/archive/v1.11.1/vvenc-1.11.1.tar.gz"
+MD5SUM_x86_64="c3267221f7d0f74fe58d751188c2efbb"
 REQUIRES=""
 MAINTAINER="Andrew Strong"
 EMAIL="andrew.david.strong@gmail.com"

ponce · 04-10-2024, 08:02 AM

hi J_W,

if you wish vvdec and vvenc to be updated (the version we have ATM build fine also on current) your best option is to write to the maintainer proposing him these patches (they should probably be ok also on 15.0)...