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.
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.
Last edited by lostintime; 04-06-2024 at 07:44 PM.
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.)
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:
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.
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.
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).
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.
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.
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.
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)...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.