Re: [Slackbuilds-users] Issues with tkimg
Il giorno dom 18 ago 2024 alle ore 18:56 M Wedin ha scritto: > Den sön 18 aug. 2024 kl 18:18 skrev Richard Ellis via > SlackBuilds-users : > > > > On Sun, Aug 18, 2024 at 05:58:55PM +0200, M Wedin wrote: > > >I aim to install mcu8051ide > > > > > >These are the packages to be installed. Dependencies are indented > > > > > >mcu8051ide > > > bwidget > > > itcl > > >! tkimg > > >tcllib > > > tDOM > > >gumbo-parser > > > > > >There is no libtiff on SBo. > > > > That is because libtiff is part of Slackware. > > > > Look here, search for "libtiff" in the file list to find the entries: > > > > https://mirrors.slackware.com/slackware/slackware64-15.0/slackware64/l/ > > Found libtiff-4.3.0-x86_64-1.txz > > > Note that it has also been patched (again search for libtiff in the > > list here): > > > > > https://mirrors.slackware.com/slackware/slackware64-15.0/patches/packages/ > > libtiff-4.4.0-x86_64-1_slack15.0.txz > > From my /var/log/packages: > libtiff-4.4.0-x86_64-1_slack15.0 > > $ locate libtiff > /usr/lib64/libtiff.so > /usr/lib64/libtiff.so.5 > /usr/lib64/libtiff.so.5.7.0 > /usr/lib64/libtiff.so.5.8.0 > /usr/lib64/libtiffxx.so > /usr/lib64/libtiffxx.so.5 > /usr/lib64/libtiffxx.so.5.7.0 > /usr/lib64/libtiffxx.so.5.8.0 > /usr/lib64/pkgconfig/libtiff-4.pc > > > I just tested my tkimg slackbuild on my Slack 15 system (with the 4.3.0 > > libtiff). It built without error. > > > > I then upgraded my libtiff (as your question caused me to notice I was > > behind Slackware 15's patches on this one). The tklib slackbuild > > again built without error. > > > > I don't have anything extra to offer, but there are two questions you > > left open: > > > > Do you have Slackware's libtiff installed? > > Yes > > > What Slackware version are you trying to build upon? > > Bog standard 15 64-bit. No compatibility. > > Thanks for the reply > Wedin Hi Wedin, I'm not able to reproduce your error either... if you have already installed in your system jbig2dec, jbig2enc or jbigkit have you tried (temporarily) removing these packages and rebuilding both tcllib and tkimg? Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] bad permissions in /usr/share/mime
Il giorno mer 10 lug 2024 alle ore 10:35 Giancarlo Dessì
ha scritto:
> Il 10/07/24 10:31, Matteo Bernardini ha scritto:
>
> chmod 0644 usr/share/mime/{application,image}/*.xml || true
>
>
> thanks Matteo, I'll try it.
>
> but I'm not sure if I have to add the line after or within the block.
>
if you prefer you can modify the block like this
if [ -x /usr/bin/update-mime-database ]; then
/usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
/usr/bin/chmod 0644 usr/share/mime/{application,image}/*.xml >/dev/null
2>&1 || true
fi
Matteo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] bad permissions in /usr/share/mime
Il giorno mer 10 lug 2024 alle ore 10:20 Giancarlo Dessì
ha scritto:
> Il 10/07/24 10:14, Giancarlo Dessì ha scritto:
>
> Hi,
>
> I'm updating the slackbuild for new version of QGIS (3.38.0). Usually this
> package is not affected by issues, but for this version this failure of
> sbopkglint occurred:
>
> --- usr/share/mime should not contain files with executable permission:
> -rwxr-xr-x 1 root root 373 lug 10 09:27
> usr/share/mime/application/geopackage+sqlite3.xml
> -rwxr-xr-x 1 root root 383 lug 10 09:27
> usr/share/mime/application/vnd.google-earth.kml+xml.xml
> -rwxr-xr-x 1 root root 386 lug 10 09:27
> usr/share/mime/application/vnd.google-earth.kmz.xml
> -rwxr-xr-x 1 root root 347 lug 10 09:27
> usr/share/mime/application/x-adobe-mif.xml
> -rwxr-xr-x 1 root root 398 lug 10 09:27
> usr/share/mime/application/x-esri-crs.xml
> -rwxr-xr-x 1 root root 394 lug 10 09:27
> usr/share/mime/application/x-esri-shape.xml
> -rwxr-xr-x 1 root root 376 lug 10 09:27
> usr/share/mime/application/x-mapinfo-mif.xml
> -rwxr-xr-x 1 root root 446 lug 10 09:27
> usr/share/mime/application/x-qgis-composer-template.xml
> -rwxr-xr-x 1 root root 430 lug 10 09:27
> usr/share/mime/application/x-qgis-layer-definition.xml
> -rwxr-xr-x 1 root root 429 lug 10 09:27
> usr/share/mime/application/x-qgis-layer-settings.xml
> -rwxr-xr-x 1 root root 451 lug 10 09:27
> usr/share/mime/application/x-qgis-project-container.xml
> -rwxr-xr-x 1 root root 441 lug 10 09:27
> usr/share/mime/application/x-qgis-project.xml
> -rwxr-xr-x 1 root root 368 lug 10 09:27
> usr/share/mime/application/x-raster-aig.xml
> -rwxr-xr-x 1 root root 368 lug 10 09:27
> usr/share/mime/application/x-raster-ecw.xml
> -rwxr-xr-x 1 root root 374 lug 10 09:27
> usr/share/mime/application/x-raster-mrsid.xml
> -rwxr-xr-x 1 root root 389 lug 10 09:27 usr/share/mime/image/jp2.xml
> -rwxr-xr-x 1 root root 383 lug 10 09:27 usr/share/mime/image/jpeg.xml
> -rwxr-xr-x 1 root root 383 lug 10 09:27 usr/share/mime/image/tiff.xml
> FAILED
>
> These files don't appear in the package tree, so I think they are
> generated or modified during the installation by the following block of
> doinst.sh:
>
> if [ -x /usr/bin/update-mime-database ]; then
> /usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
> fi
>
> Since doint.sh is the same of current and previous versions of the
> slackbuild, something should be wrong in some files of source, but I don't
> know where I have to check.
>
> Can someone help me? Thanks in advance
>
>
> I verified just now that the issue occurs building the package in
> -current. In 15.0 stable sbopkglint doesn't report any error!
>
> :\
>
just add in the doinst.sh, after the block
if [ -x /usr/bin/update-mime-database ]; then
/usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
fi
another line with
chmod 0644 usr/share/mime/{application,image}/*.xml || true
it should be harmless on 15.0...
Matteo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20240525.1
Il giorno sab 25 mag 2024 alle ore 15:22 Luveh Keraph <1.41...@gmail.com> ha scritto: > fwupd is failing to build for me. It was failing last week already. > > [542/1098] Compiling C object > plugins/kinetic-dp/libfu_plugin_kinetic_dp.a.p/fu-kinetic-dp-secure-device.c.o > [543/1098] Generating from 'device_attestation.proto' > FAILED: > plugins/logitech-bulkcontroller/libfu_plugin_logitech_bulkcontroller.a.p/device_attestation.pb-c.c > plugins/logitech-bulkcontroller/libfu_plugin_logitech_bulkcontroller.a.p/device_attestation.pb-c.h > > /usr/bin/protoc --proto_path=../plugins/logitech-bulkcontroller/proto > --c_out=plugins/logitech-bulkcontroller/libfu_plugin_logitech_bulkcontroller.a.p > ../plugins/logitech-bulkcontroller/proto/device_attestation.proto > protoc-gen-c: error while loading shared libraries: > libabsl_log_internal_check_op.so.2308.0.0: cannot open shared object file: > No such file or directory > --c_out: protoc-gen-c: Plugin failed with status code 127. > [544/1098] Generating from 'fu-linux-lockdown.rs' > [545/1098] Compiling C object > plugins/hailuck/libfu_plugin_hailuck.a.p/meson-generated_fu-hailuck-struct.c.o > [546/1098] Generating from 'fu-igsc.rs' > [547/1098] Generating from 'fu-intel-usb4.rs' > [548/1098] Generating from 'fu-logitech-hidpp.rs' > [549/1098] Generating from 'fu-logitech-bulkcontroller.rs' > [550/1098] Linking target libfwupd/libfwupd.so.2.0.0 > [551/1098] Generating plugins/uefi-capsule/ux-capsule-tar with a custom > command > ninja: build stopped: subcommand failed. > FWIW I just built it fine from scratch, together with all of its dependencies on slackware64-15.0. glancing at the error it might be that rebuilding and reinstalling protobuf3 would be enough in your case, but YMMV... Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20240518.1
I think your issue is because /usr/lib64/librpmio.so.10 is part of the rpm package in current and there links to the system's lua (lua-5.4.x). Matteo Il giorno gio 23 mag 2024 alle ore 08:09 Diniz Bortolotto < diniz.bortolo...@gmail.com> ha scritto: > I've just updated *system/fastfetch* and I'm getting this error message: > fastfetch: symbol lookup error: /usr/lib64/librpmio.so.10: undefined > symbol: luaL_requiref > and requires says nothing: REQUIRES="" > > Maybe some new dependency? > > Atenciosamente, > > Diniz Bortolotto > > > > Em sex., 17 de mai. de 2024 às 21:35, Willy Sudiarto Raharjo < > will...@slackbuilds.org> escreveu: > >> During our weekly rebuild last week, we noticed some scripts failed to >> build only in i586 architecture. Most of us are now using x86_64 >> exclusively so if you didn't test the scripts in i586 VM, it's probably >> better to put UNSUPPORTED or UNTESTED in DOWNLOAD field. >> >> If anyone wants to help clearing the i586 FTBFS entries, you might find >> the list here: https://github.com/SlackBuildsOrg/slackbuilds/issues/5827 >> Any help is appreciated. >> >> There are a lot of removals in python category, but 1 script is still >> needed by other (python2-swiftclient) and it slipped from maintainer's >> check, so i reinstated the files in my branch and it will be restored by >> next week's public update. >> >> >> Sat May 18 00:00:04 UTC 2024 >> academic/fet: Updated for version 6.19.5. >> academic/plus42: Updated for version 1.1.10. >> audio/cmus: Updated for version 2.11.0. >> audio/mixxx: Updated for version 2.4.0. >> audio/ncspot: Updated for version 1.1.1. >> desktop/bibata-cursor-theme: Added (Bibata Cursor Theme). >> desktop/dolphin-megasync: Updated for version 5.2.1.0. >> desktop/fvwm3: Update script. >> desktop/gnome-shell: Disable building tests. >> desktop/ideviceinstaller: Updated for version 1.1.1. >> desktop/lxpanel: Updated for version 20230918_633a2d4. >> desktop/mint-l-icons: Updated for version 1.7.0. >> desktop/mint-themes: Update for 2.1.6 (+new maintainer) >> desktop/mint-x-icons: Updated for version 1.6.8. >> desktop/mint-y-icons: Update for 1.7.5 (+new maintainer) >> desktop/mousam: Update for 1.2.0 >> desktop/mutter: Disable building tests. >> desktop/river: Mark as x86_64. >> desktop/sun: Updated for version 1.6.2. >> desktop/thunar-megasync: Updated for version 5.2.1.0. >> development/Bottleneck: Removed unused. >> development/OpenJDK11: Updated for version 11.0.23. >> development/OpenJDK17: Updated for version 17.0.10. >> development/OpenJDK21: Added (Java Development Kit). >> development/aws-cdk: Updated for version 2.142.0. >> development/cargo-c: Updated for version 0.9.32. >> development/github-cli: Updated for version 2.49.2 >> development/gtest: Change the cmake file install routine. >> development/hugo: Updated for version 0.126.1. >> development/liberica-jdk-bin: Updated for version 21.0.3+12. >> development/neovim: Updated for version 0.10.0. >> development/poedit: Updated for version 3.4.4. >> development/postman: Updated for version 11.1.0. >> development/pre-commit: Updated for version 3.7.1. >> development/pyenchant: Updated for version 3.2.2. >> development/pyvim: Updated for version 3.0.3. >> development/qb64pe: Updated for version 3.13.0. >> development/rust16: Updated for version 1.78.0. >> development/tig: Updated for version 2.5.10. >> development/tkdiff: Updated for version 5.7 >> development/tstoolbox: Removed unused. >> development/xxd-standalone: Updated for version 9.1.0404. >> games/galaxyv2: Fix .info. >> games/term2048: Removed unused. >> games/xemu: Fix MD5SUM. >> graphics/CairoSVG: Updated for version 2.7.1. >> graphics/dblatex: Updated for version 0.3.12. >> ham/codec2: Updated for version 1.2.0. >> ham/freedv: Updated for version 1.9.9.1. >> ham/gridtracker: Updated for version 1.24.0504. >> ham/lpcnetfreedv: Added (Neural Network Plugin for freedv). >> ham/lpcnetfreedv: Updated README. >> ham/qlog: Updated for version 0.35.1. >> libraries/LucenePlusPlus: Updated for version 3.0.9. >> libraries/PrettyTable: Updated for version 3.10.0. >> libraries/libdisplay-info: Remove proper source folder on rebuild >> libraries/libslirp: Updated for version 4.8.0. >> libraries/libtorrent-rasterbar: Fix building on -current. >> libraries/libvterm: Update script. >> libraries/python-xlrd: Updated for version 2.0.1. >> libraries/qt5gtk2: Added (gtk2 integration plugin). >> libraries/qt6gtk2: Added (gtk2 integration plugin). >> libraries/webkit2gtk4.1: Updated for version 2.44.2. >> libraries/webkit2gtk: Updated for version 2.44.2. >> misc/bitwarden-desktop: updated for 2024.4.3 >> misc/open-simh: Fix permission. >> misc/open-simh: Updated for version 20240315_ffe537a. >> multimedia/MuseScore: Updated for version 4.3.0. >> multimedia/kodi: Forgot to bump BUILD number >> multimedia/obs-studio: Add patch to fix 32bit build >> multimedia/videomass: Updated for version 5.0.13. >> network/brave-browser: Updated for version 1.66.110. >>
Re: [Slackbuilds-users] gtest error
Hi Fernando, I just tried building gtest and I'm not able to reproduce your error... Have you tried that, like me, on a full installation of Slackware64-15.0? if it happens on current please report it in the dedicated thread on LQ, thanks! Matteo Il giorno dom 12 mag 2024 alle ore 14:04 Fernando Lopez < fernando.lope...@gmail.com> ha scritto: > [ 75%] Linking CXX shared library ../lib/libgmock_main.so > [ 75%] Built target gmock_main > [ 87%] Building CXX object > googletest/CMakeFiles/gtest_main.dir/src/gtest_main.cc.o > [100%] Linking CXX shared library ../lib/libgtest_main.so > [100%] Built target gtest_main > cp: cannot stat 'build/googletest/CMakeFiles/Export/lib64/cmake': No such > file or directory > > gtest: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. > > (Y)es to continue, (N)o to abort, (R)etry the build?: > > -- > > > Regards, > Fernando Lopez Jr. > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Audacity fails build (zip vs. tar.gz confusion)
ok, upstream just confirmed that in-app support for the offline manual is gone https://github.com/audacity/audacity/issues/6402 so I'll leave the option but will now be to put it as-is in /usr/doc/audacity-$VERSION/ Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Audacity fails build (zip vs. tar.gz confusion)
Il giorno mar 7 mag 2024 alle ore 22:22 Erich Ritz < erich.pub...@protonmail.com> ha scritto: > On Tuesday, May 7th, 2024 at 2:59 PM, Matteo Bernardini < > matteo.bernard...@gmail.com> wrote: > > > actually I was also considering about removing the manual build > completely because if you build it without it (the default), when you > select the manual on the menu, the online version gets opened in the > default browser: could that be an acceptable alternative, in your opinion? > > > > I prefer local documentation, but I won't complain which ever way you > decide :) > well, looking better at it it seems that, at the moment, the audacity devs f***ed up the manual installation routine (it happens very often) so, also if you install it, you still get redirected to the online documentation... I'll just note it and hope it gets fixed somehow (also hope to not get bored trying to make this work). Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Audacity fails build (zip vs. tar.gz confusion)
Il giorno mar 7 mag 2024 alle ore 18:46 Erich Ritz via SlackBuilds-users < slackbuilds-users@slackbuilds.org> ha scritto: > Hello Matteo, > > The latest audacity update fails to build for me: > > unzip: cannot find or open > /tmp/slackrepo/etr/slackrepo.JU0v3x/slackbuild_audacity/audacity-manual-3.5.1.zip, > /tmp/slackrepo/etr/slackrepo.JU0v3x/slackbuild_audacity/audacity-manual-3.5.1.zip.zip > or > /tmp/slackrepo/etr/slackrepo.JU0v3x/slackbuild_audacity/audacity-manual-3.5.1.zip.ZIP. > Build time 87 sec, peak load 32.79, peak memory 13033M, peak tmp 524M > audio/audacity: audacity.SlackBuild failed (status 9) > 14:16:54 > Unmounting chroot ... > :-( audio/audacity FAILED )-: > > Looks like audacity-manual changed from .zip to .tar.gz, but the > SlackBuild is still using "unzip" to extract it. > > Erich > Thanks Erich, I changed it locally but I forgot to change it when I moved the changes in the commit... actually I was also considering about removing the manual build completely because if you build it without it (the default), when you select the manual on the menu, the online version gets opened in the default browser: could that be an acceptable alternative, in your opinion? Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] LXDE on SBo switches to gtk+3
hi guys, an heads-up for the LXDE users: I think it's time to switch to the gtk+3 version of the components by default so I pushed the scripts that need to be modified for that in a dedicated branch and plan to push it in the main repository at the end of the week https://git.slackbuilds.org/slackbuilds/log/?h=lxde-gtk3 if someone is still interested I left the option to build the stuff against gtk+2 just exporting the environment variable GTK3=no during the build. take care! Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] avidemux missing patch file.
hi Fernando, that version of avidemux is not available in the SBo repository but only on the unofficial repository for current: I had to update to that because the one on SBo didn't build on current but I forgot to "git add" the patch. now it's fixed but please avoid reporting issues with that unofficial repository in this mailing list as that repo is not supported/endorsed by SBo, the proper place is the dedicated topic on LQ. thanks! Matteo Il giorno mar 23 apr 2024 alle ore 00:03 Fernando Lopez < fernando.lope...@gmail.com> ha scritto: > avidemux_20240417_ac7587b/myOwnPlugins/videoEncoder/vaenc_settings.conf > avidemux_20240417_ac7587b/myOwnPlugins/videoEncoder/libvaencPlugin.cpp > > avidemux_20240417_ac7587b/myOwnPlugins/videoEncoder/ADM_libVaEncodingContextH264.h > avidemux_20240417_ac7587b/myOwnPlugins/videoEncoder/readme.txt > > avidemux_20240417_ac7587b/myOwnPlugins/videoEncoder/ADM_libVaEncodingContextH264_misc.cpp > avidemux_20240417_ac7587b/bootStrapOsx_Sierra.bash > avidemux_20240417_ac7587b/bootStrapHaikuOS.bash > *cp: cannot stat > '/var/lib/sbopkg/SBo-git/multimedia/avidemux/0004-support-nv-codec-headers-12.2.patch': > No such file or directory* > > avidemux: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. > > (Y)es to continue, (N)o to abort, (R)etry the build?: > > -- > > > Regards, > Fernando Lopez Jr. > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] malloc runtime error, any suggestions?
...but SBo already ships 3.4.1... Matteo Il giorno mer 17 apr 2024 alle ore 15:14 ha scritto: > I guess that's promising, although my install is a full install of > slack15. Maybe it's something specific to the video driver. It's just > intel in a t470s. > > There's one bug report open for this issue from someone using debian. > That doesn't offer much. > > At any rate, do you want to move forward and distribute 3.5.1 or do you > want me to push 3.4.1 back to SBO? > > > On 2024-04-16 00:59, B. Watson wrote: > > On Mon, 15 Apr 2024, phala...@komputermatrix.com wrote: > > > >> It's version 3.5.1 -- it's pushed but not distributed yet. > > > > OK, I just built 3.5.1 with the existing script (VERSION=3.5.1 in the > > environment) and it starts up and seems to work OK. > > > > It does say this: > > > > spectrwm: Welcome to spectrwm V3.5.1 Build: 3.5.1 > > > > ...so I know I'm running the right version. > > > > So whatever's going on might be specific to your system... > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] ganglia is missing, is it not needed anymore?
if I recall correctly I think they were removed when the repository was migrating to 15.0 because they weren't building... sorry, what do you mean by "is it not needed anymore"? if someone still uses them I don't see any issues for them to be submitted back to the repo by whoever wishes to maintain them further. Matteo Il giorno mer 10 apr 2024 alle ore 15:29 Karel Venken via SlackBuilds-users ha scritto: > Hi, > > I am migrating some of my systems to 15.0 and I noted that ganglia, > ganglia-web was removed from SBo already some time ago. Is it not needed > anymore? > > kind regards. > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20240405.1
Hi Giancarlo, thanks for the report! I think Willy already realized about that and fixed it in git (it will go in at the next merge) https://git.slackbuilds.org/slackbuilds/commit/?id=3ac1326 Matteo Il giorno ven 5 apr 2024 alle ore 22:48 Giancarlo Dessì ha scritto: > Cmake configuration of x265 does not start: after uncompressing the > tarball an issue affects the path set in the slackbuild script: > > CMake Error: The source directory "/tmp/SBo/x265_3.6/source" does not > exist. > Specify --help for usage, or press the help button on the CMake GUI. > > This happens in Slackware64, is something lost in the conditions? I'm not > sure what and/or where I have to fix > > -- > * > Giancarlo Dessìhttps://www.giand.ithttps://github.com/giandex > > Slackware Linux... because it works! > * > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] jq fails to build
Il giorno mer 20 mar 2024 alle ore 18:50 Tonus ha scritto: > │ PASS: tests/mantest > │ FAIL: tests/jqtest > │ PASS: tests/shtest > │ PASS: tests/utf8test > │ PASS: tests/base64test > │ FAIL: tests/optionaltest > │ PASS: tests/onigtest > │ PASS: tests/manonigtest > │ > == > │ Testsuite summary for jq 1.7.1 > │ > == > │ # TOTAL: 8 > │ # PASS: 6 > │ # SKIP: 0 > │ # XFAIL: 0 > │ # FAIL: 2 > │ # XPASS: 0 > │ # ERROR: 0 > hi Tonus, jq seems to build fine here so I am inclined to think about a local issue: for hints maybe you can have a look in your /tmp/SBo/jq-1.7.1/tests directory, and in particular check the content of the jqtest.log and optionaltest.log diles that you can find there... Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] coeurl fails to build with new spdlog
Il giorno ven 15 mar 2024 alle ore 15:09 Vladimir Nikishkin <
for_slackbuilds-users_mlist_2023-04...@lockywolf.net> ha scritto:
> Hello, everyone.
>
> spdlog has been recently updated, and now my coeurl build fails to build
>
> Does anybody know how to overcome this?
>
> [1/2] ccache c++ -Ilibcoeurl.so.0.3.p -I. -I.. -I../include
> -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch
> -Wnon-virtual-dtor -Wextra -Wpedantic -std=c++17 -g -fPIC -pthread
> -DSPDLOG_SHARED_LIB -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -MD -MQ
> libcoeurl.so.0.3.p/lib_client.cpp.o -MF
> libcoeurl.so.0.3.p/lib_client.cpp.o.d -o
> libcoeurl.so.0.3.p/lib_client.cpp.o -c ../lib/client.cpp
> FAILED: libcoeurl.so.0.3.p/lib_client.cpp.o
> ccache c++ -Ilibcoeurl.so.0.3.p -I. -I.. -I../include
> -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch
> -Wnon-virtual-dtor -Wextra -Wpedantic -std=c++17 -g -fPIC -pthread
> -DSPDLOG_SHARED_LIB -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -MD -MQ
> libcoeurl.so.0.3.p/lib_client.cpp.o -MF
> libcoeurl.so.0.3.p/lib_client.cpp.o.d -o
> libcoeurl.so.0.3.p/lib_client.cpp.o -c ../lib/client.cpp
> In file included from /usr/include/fmt/format.h:49,
> from /usr/include/fmt/ostream.h:21,
> from /usr/include/spdlog/fmt/ostr.h:20,
> from ../lib/client.cpp:1:
> /usr/include/fmt/core.h: In instantiation of ‘constexpr
> fmt::v10::detail::value fmt::v10::detail::make_arg(T&) [with bool
> PACKED = true; Context = fmt::v10::basic_format_context char>; T = CURLcode; typename std::enable_if::type
> = 0]’:
> /usr/include/fmt/core.h:1842:51: required from ‘constexpr
> fmt::v10::format_arg_store::format_arg_store(T& ...) [with T
> = {std::__cxx11::basic_string,
> std::allocator >, CURLcode, char [256], long int}; Context =
> fmt::v10::basic_format_context; Args =
> {std::__cxx11::basic_string,
> std::allocator >, CURLcode, char [256], long int}]’
> /usr/include/fmt/core.h:1860:18: required from ‘constexpr
> fmt::v10::format_arg_store std::remove_reference::type>::type ...> fmt::v10::make_format_args(T&
> ...) [with Context = fmt::v10::basic_format_context char>; T = {std::__cxx11::basic_string,
> std::allocator >, CURLcode, char [256], long int}]’
> /usr/include/spdlog/logger.h:374:75: required from ‘void
> spdlog::logger::log_(spdlog::source_loc, spdlog::level::level_enum,
> spdlog::string_view_t, Args&& ...) [with Args =
> {std::__cxx11::basic_string,
> std::allocator >&, CURLcode&, char (&)[256], long int&};
> spdlog::string_view_t = fmt::v10::basic_string_view]’
> /usr/include/spdlog/logger.h:90:13: required from ‘void
> spdlog::logger::log(spdlog::source_loc, spdlog::level::level_enum,
> fmt::v10::format_string, Args&& ...) [with Args =
> {std::__cxx11::basic_string,
> std::allocator >&, CURLcode&, char (&)[256], long int&};
> fmt::v10::format_string = fmt::v10::basic_format_string std::__cxx11::basic_string,
> std::allocator >&, CURLcode&, char (&)[256], long int&>]’
> /usr/include/spdlog/logger.h:96:12: required from ‘void
> spdlog::logger::log(spdlog::level::level_enum, fmt::v10::format_string ...>, Args&& ...) [with Args = {std::__cxx11::basic_string std::char_traits, std::allocator >&, CURLcode&, char (&)[256],
> long int&}; fmt::v10::format_string =
> fmt::v10::basic_format_string std::char_traits, std::allocator >&, CURLcode&, char (&)[256],
> long int&>]’
> /usr/include/spdlog/logger.h:146:12: required from ‘void
> spdlog::logger::trace(fmt::v10::format_string, Args&& ...) [with
> Args = {std::__cxx11::basic_string,
> std::allocator >&, CURLcode&, char (&)[256], long int&};
> fmt::v10::format_string = fmt::v10::basic_format_string std::__cxx11::basic_string,
> std::allocator >&, CURLcode&, char (&)[256], long int&>]’
> ../lib/client.cpp:358:27: required from here
> /usr/include/fmt/core.h:1600:63: error:
> ‘fmt::v10::detail::type_is_unformattable_for _’ has
> incomplete type
> 1600 | type_is_unformattable_for _;
> | ^
> /usr/include/fmt/core.h:1604:7: error: static assertion failed: Cannot
> format an argument. To make type T formattable provide a formatter
> specialization: https://fmt.dev/latest/api.html#udt
> 1604 | formattable,
> | ^~~
> /usr/include/fmt/core.h:1604:7: note: ‘formattable’ evaluates to false
> ninja: build stopped: subcommand failed.
>
> --
> Your sincerely,
> Vladimir Nikishkin (MiEr, lockywolf)
> (Laptop)
>
>
Hi Vladimir,
that happens because spdlog has been build against fmt >= 10.x: I found
this patch in the archlinux repo that let coeurl build also in this
situation
https://nheko.im/nheko-reborn/coeurl/-/commit/831e2ee8e9cf08ea1ee9736cde8370f9d0312abc.patch
Matteo
P.S. please use sane email addresses when you write to the mailing list,
thanks in advance! ;-)
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://
Re: [Slackbuilds-users] qt6 build error with new protobuf3-25.3 (Slackware 15.0 x86_64)
Il giorno mar 12 mar 2024 alle ore 06:43 myrequiem < mrvladislavov...@gmail.com> ha scritto: > Hello. After updating protobuf3-25.3, building package qt6 gives an error. > The > old protobuf3 package had 17 header files, the new package has only 5, > which > are located in > /usr/include/google/protobuf/stubs/ > This is why the qt6 assembly complains that there are not enough headers: > > ERROR > qt-everywhere-src-6.5.2/qtgrpc/src/tools/qtprotoccommon/generatorbase.cpp: > fatal error: 'google/protobuf/stubs/logging.h' file not found > #include > > The same with the header google/protobuf/stubs/macros.h > > Even if you add these header files from the old protobuf3 package, the > build > still fails > it seems that a component, qtgrpc, added with qt6-6.5.x, uses some protobuf deprecated headers if it find this installed: there are some specific patches upstream fot qt-7.x (!!!) that I just backported to 6.5.2 https://git.slackbuilds.org/slackbuilds/commit/?id=87b5f24 Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] sbotools config issues
hi, just for testing I downloaded, packaged and installed sbotools from here https://slackbuilds.org/repository/15.0/system/sbotools/ following what's written on the documentation https://pink-mist.github.io/sbotools/documentation/ I run "sbosnap fetch" to download the repository and I saw that in /usr/sbo/repo what is downloaded by default the unofficial repository for current that I maintain (check /usr/sbo/repo/.git/config) that shouldn't be used for 15.0 (maybe some other default should be set in the package on SBo) but should help who's running current. the reason why it should help who's running current is that it contains patches for the broken scripts that don't build on current and that are reported to me through the dedicated stickied thread on LQ and, also, scripts that are added to current are removed from there to avoid risks of overlap with what is already in current, like Gene explained in another message of this thread. what I don't edit in my unofficial repository for current are the mentions of the removed scripts in the REQUIRED variables in the *.info files of what use these scripts as dependencies: that would be simply non maintenable because simple version changes of these scripts would result in a gazillion of conflicts in these git forks. users of current should learn to ignore these non existant scripts warning (and optionally refer to this list to check what has been removed and why https://cgit.ponce.cc/slackbuilds/refs/heads), still like Gene pointed out in the previous message this to say that the repository you were using as default should already had been probably ok and the "unable to locate" message were normal (I don't think you ever had a repository for 15.0 setup in sbotools). consider also that this mailing list is not actually the proper place to help you in your eventual issues with current as the developer's version of Slackware is not supported by SBo: if you find problems using this unofficial repository for current or any of the SBo's scripts with current, IMHO, the best option is to open a topic on LQ describing the issue and your setup. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] tracking down SBo "dependencies"
Il giorno gio 29 feb 2024 alle ore 17:12 Jim ha scritto: > I recently upgraded the SBo dav1d, which upgraded the library from > libdav1d.so.6 to libdav1d.so.7. > > Unfortunately, a couple of other SBo packages (libheif and vlc) had > references to (specifically) libdav1d.so.6, which caused them to whine a > bit. > > It was easy enough to recompile libheif and vlc after I found the problem, > but this got me wondering... > > Does anyone have an easy way of tracking down this sort of "breakage" which > might happen when upgrading an SBo package? > > Thanks. > Jim > > some time ago Pat shared one script he uses for this cases https://www.linuxquestions.org/questions/slackware-14/why-slackpkg-doesn%27t-resolve-dependencies-4175720632/#post6403575 Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Fwd: [PATCH] development/hexedit: Updated for version 1.6.
Forwarded for consideration to the hexedit maintainer
-- Forwarded message -
Da: Shahab Vahedi via SlackBuilds-users
Date: ven 16 feb 2024 alle ore 09:53
Subject: [Slackbuilds-users] [PATCH] development/hexedit: Updated for
version 1.6.
To:
Cc: Shahab Vahedi
The current version (1.2.12) cannot even be built anymore, because
that source version exists no more.
Tested on a Slackware64 15.0 with the latest patches in. The lint
results are OK both for the script and the package.
Signed-off-by: Shahab Vahedi
---
development/hexedit/hexedit.SlackBuild | 9 ++---
development/hexedit/hexedit.info | 8
2 files changed, 10 insertions(+), 7 deletions(-)
diff --git a/development/hexedit/hexedit.SlackBuild
b/development/hexedit/hexedit.SlackBuild
index 21381bcac0..33f3d82e5c 100644
--- a/development/hexedit/hexedit.SlackBuild
+++ b/development/hexedit/hexedit.SlackBuild
@@ -27,7 +27,7 @@
cd $(dirname $0) ; CWD=$(pwd)
PRGNAM=hexedit
-VERSION=${VERSION:-1.2.12}
+VERSION=${VERSION:-1.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}
PKGTYPE=${PKGTYPE:-tgz}
@@ -66,8 +66,8 @@ rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$VERSION
-tar xvf $CWD/$PRGNAM-$VERSION.src.tgz
-cd $PRGNAM
+tar xvf $CWD/$VERSION.tar.gz
+cd $PRGNAM-$VERSION
chown -R root:root .
find -L . \
\( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
@@ -75,6 +75,7 @@ find -L . \
\( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
-o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
+./autogen.sh
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
@@ -103,6 +104,8 @@ DOCS="COPYING Changes TODO"
mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a $DOCS $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/
$PRGNAM.SlackBuild
+# TODO file is empty in version 1.6
+test -s $PKG/usr/doc/$PRGNAM-$VERSION/TODO || rm
$PKG/usr/doc/$PRGNAM-$VERSION/TODO
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
diff --git a/development/hexedit/hexedit.info b/development/hexedit/
hexedit.info
index 111b69d3b3..c4cd5ac420 100644
--- a/development/hexedit/hexedit.info
+++ b/development/hexedit/hexedit.info
@@ -1,8 +1,8 @@
PRGNAM="hexedit"
-VERSION="1.2.12"
-HOMEPAGE="http://prigaux.chez.com/hexedit.html";
-DOWNLOAD="http://rigaux.org/hexedit-1.2.12.src.tgz";
-MD5SUM="0d2f48610006278cd93359fea9a06d5c"
+VERSION="1.6"
+HOMEPAGE="https://rigaux.org/hexedit.html";
+DOWNLOAD="https://github.com/pixel/hexedit/archive/1.6.tar.gz";
+MD5SUM="9b5849759dbda9ab25ec22818c16e970"
DOWNLOAD_x86_64=""
MD5SUM_x86_64=""
REQUIRES=""
--
2.35.8
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Bear missing libraries
hi Ruben, the error you are reporting is because you most probably built Bear or against older versions of fmt and/or grpc: try to rebuild Bear (and everything on which it depends which build scripts are hosted on SBo). when you do that you will discover that the version of Bear we have here (3.1.1) cannot be built because of the new fmt: just build version 3.1.3 and that will work ok (I'll push a fix in our git for that). Matteo Il giorno dom 11 feb 2024 alle ore 13:39 Ruben Carlo Benante via SlackBuilds-users ha scritto: > Hello there Ivan Kovmir, hello guys, > > The software Bear ( > https://slackbuilds.org/repository/15.0/development/Bear/ ) is > complaining about missing libraries in Slackware 15.0: > > * bear: error [...]: libgrpc++.so.1: cannot open shared object: No such > file or directory > * bear: error [...]: libgrpc.so.9: cannot open shared object: No such file > or directory > * bear: error [...]: libgpr.so.9: cannot open shared object: No such file > or directory > * bear: error [...]: libspdlog.so.1.11: cannot open shared object: No such > file or directory > * bear: error [...]: libfmt.so.9: cannot open shared object: No such file > or directory > > Could you take a peek at it, if you be kind? > > Thanks a bucket. > > Cordialmente, > > Ruben > > -- > Dr. Beco > AI Researcher > > > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] SFML update breaks extremetuxracer
Il giorno lun 5 feb 2024 alle ore 17:19 Erich Ritz < erich.pub...@protonmail.com> ha scritto: > On Monday, February 5th, 2024 at 9:37 AM, Matteo Bernardini < > matteo.bernard...@gmail.com> wrote: > > > Hi Erich, > > > > this happens because the new SFML installs its pkgconfi files in the > wrong location (/usr/pkgconfig): if you add the line > > > > -DSFML_PKGCONFIG_INSTALL_PREFIX=/usr/lib$LIBDIRSUFFIX/pkgconfig \ > > > > between the cmake options in the SlackBuild then stuff using pkgconfig > to locate SFML will find it again correctly. > > > > I'll push the change in our git, it will be fixed in the repository at > the next global update. > > > > Matteo > > > > Il giorno lun 5 feb 2024 alle ore 16:22 Erich Ritz via SlackBuilds-users > ha scritto: > > > > > It looks like the recent update to SFML breaks the extremetuxracer > build: > > > > > > Building games/extremetuxracer (rebuild for updated deps) 2024-02-05 > 14:42:12Verifying source files ... > > > Installing dependencies ... > > > SFML-2.6.1-x86_64-1_SBo: Simple and Fast Multimedia Library > .. [ 2.2M] > > > Running extremetuxracer.SlackBuild ... ETA 14:43:?? > > > env MAKEFLAGS='-j176 -l89' nice -n 5 bash ./extremetuxracer.SlackBuild > > > ... > > > checking pkg-config is at least version 0.9.0... yes > > > checking for sfml-system >= 2.4... no > > > configure: error: sfml-system not found > > > games/extremetuxracer: extremetuxracer.SlackBuild failed (status 1) > 14:42:19 > > > Unmounting chroot ... > > > :-( games/extremetuxracer FAILED )-: > > > ___ > > > SlackBuilds-users mailing list > > > SlackBuilds-users@slackbuilds.org > > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > > FAQ - https://slackbuilds.org/faq/ > > There is another problem as well highlighted by sbopkglint (forbidden > directory usr/share/doc): > > # sbopkglint /var/lib/slackrepo/etr/packages/15.0/x86_64/libraries/SFML/ > SFML-2.6.1-x86_64-1_SBo.txz > Using tests from /usr/share/sbo-maintainer-tools/sbopkglint.d > Exploding > /var/lib/slackrepo/etr/packages/15.0/x86_64/libraries/SFML/SFML-2.6.1-x86_64-1_SBo.txz > to /tmp/SBo/sbopkglint.QLp0Dt ...OK > Running pre-doinst test...OK > Installing > /var/lib/slackrepo/etr/packages/15.0/x86_64/libraries/SFML/SFML-2.6.1-x86_64-1_SBo.txz > to /tmp/SBo/sbopkglint.QLp0Dt ...OK > Running test: 05-basic-sanity... > --- nonstandard directory in /usr: usr/pkgconfig > --- forbidden directory exists: usr/share/doc > FAILED > Running test: 10-docs...OK > Running test: 15-noarch...OK > Running test: 20-arch...OK > Running test: 25-lafiles...OK > Running test: 30-manpages...OK > Running test: 35-desktop...OK > Running test: 40-newconfig...OK > Running test: 45-doinst...OK > Running test: 50-icons...OK > Running test: 60-usr_info...OK > Running test: 65-python...OK > Running test: 70-tmp_path...OK > Running test: 75-static_libs...OK > Running test: 85-perl...OK > !!! SFML-2.6.1-x86_64-1_SBo.txz: 2 failures > thanks for the heads-up, fixed that too! Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] SFML update breaks extremetuxracer
Hi Erich, this happens because the new SFML installs its pkgconfi files in the wrong location (/usr/pkgconfig): if you add the line -DSFML_PKGCONFIG_INSTALL_PREFIX=/usr/lib$LIBDIRSUFFIX/pkgconfig \ between the cmake options in the SlackBuild then stuff using pkgconfig to locate SFML will find it again correctly. I'll push the change in our git, it will be fixed in the repository at the next global update. Matteo Il giorno lun 5 feb 2024 alle ore 16:22 Erich Ritz via SlackBuilds-users < slackbuilds-users@slackbuilds.org> ha scritto: > It looks like the recent update to SFML breaks the extremetuxracer build: > > Building games/extremetuxracer (rebuild for updated deps) 2024-02-05 > 14:42:12Verifying source files ... > Installing dependencies ... > SFML-2.6.1-x86_64-1_SBo: Simple and Fast Multimedia Library > .. [ 2.2M] > Running extremetuxracer.SlackBuild ... ETA > 14:43:?? > env MAKEFLAGS='-j176 -l89' nice -n 5 bash ./extremetuxracer.SlackBuild > ... > checking pkg-config is at least version 0.9.0... yes > checking for sfml-system >= 2.4... no > configure: error: sfml-system not found > games/extremetuxracer: extremetuxracer.SlackBuild failed (status 1) > 14:42:19 > Unmounting chroot ... > :-( games/extremetuxracer FAILED )-: > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] ngspice42
Hi Ralph,
thanks for the report! actually there is an error in the SlackBuild but I
fixed it in out git, it will go in the repository next week
--- a/academic/ngspice/ngspice.SlackBuild
+++ b/academic/ngspice/ngspice.SlackBuild
@@ -134,7 +134,7 @@ ln -s "libngspice.so.0.0.9"
"$PKG/usr/lib${LIBDIRSUFFIX}/libngspice.so"
install -Dm644 ./src/include/ngspice/sharedspice.h
$PKG/usr/include/ngspice/sharedspice.h
# Move the configure output file.
mv $TMP/$PRGNAM-$VERSION/release/src/include/ngspice/config.h
$PKG/usr/include/ngspice/
-chmod 644
$PRGNAM-$VERSION/usr/doc/ngspice-42/examples/klu/Circuits/libraries/*.lib
+chmod 644 $PKG/usr/doc/ngspice-42/examples/klu/Circuits/libraries/*.lib
install -Dm644 $CWD/$PRGNAM.png
$PKG/usr/share/icons/hicolor/48x48/apps/$PRGNAM.png
if you edit it locally and change manually that line it should work.
Matteo
Il giorno sab 27 gen 2024 alle ore 17:23 Ralph Spitzner via
SlackBuilds-users ha scritto:
> gives me this:
> make[2]: Leaving directory '/tmp/SBo/ngspice-42/release'
> make[1]: Leaving directory '/tmp/SBo/ngspice-42/release'
> chmod: cannot access
> 'ngspice-42/usr/doc/ngspice-42/examples/klu/Circuits/libraries/*.lib':
> No such file or directory
>
>
>
> -rasp
>
> --
> Chaos ist die höchste form der Ordnung.
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> 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
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Qt6 and QTWEBENGINE_RESOURCES_PATH
Il giorno mar 9 gen 2024 alle ore 12:11 Arnaud via SlackBuilds-users < slackbuilds-users@slackbuilds.org> ha scritto: > > Qt should be able to find that directory by itself using > > |QLibraryInfo::DataPath.| > > Can you try to run this command and see what it returns? > > > > qtdiag6 --no-vulkan --no-rhi --no-gl | grep DataPath > > > > In my case it returns > > > > ArchDataPath: /usr/lib64/qt6 > > DataPath: /usr/share/qt6 > > > > So the chromium resource pack path should be discovered automatically. > > Well : > $ qtdiag6 --no-vulkan --no-rhi --no-gl | grep DataPath > ArchDataPath: /usr/lib64 > DataPath: /usr > > Even though I do have : > Environment: > QT5DIR="/usr/lib64/qt5" > QT6DIR="/usr/lib64/qt6" > > So I guess something is wrong on my box. > I think this actually happens because one of the cmake options in the qt6.SlackBuild is missing -DINSTALL_DATADIR=./share/qt6 if I add that between the others then the qtdiag6 output show the correct DataPath. I'll put the maintainer in cc. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20231216.1
Il giorno sab 16 dic 2023 alle ore 09:27 Fernando Lopez < fernando.lope...@gmail.com> ha scritto: > sorry, I can't maintain it but don't drop 'em. > I am sorry Fernando, but unfortunately without a maintainer there's no alternative: besides that I can't afford to maintain it occasionally, every script, especially a browser, needs an actual maintainer... so, if anybody doesn't step in soon, they will be removed with the next update. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20231216.1
Il giorno sab 16 dic 2023 alle ore 05:24 Fernando Lopez < fernando.lope...@gmail.com> ha scritto: > opera 404 > > Processing opera > > opera: > opera not found in /var/cache/sbopkg. > --2023-12-15 22:23:23-- > https://get.geo.opera.com/pub/opera/desktop/105.0.4970.29/linux/opera-stable_105.0.4970.29.deb > Resolving get.geo.opera.com (get.geo.opera.com)... 37.228.108.149, > 37.228.108.150, 2001:4c28:3000:622:37:228:108:150, ... > Connecting to get.geo.opera.com (get.geo.opera.com)|37.228.108.149|:443... > connected. > HTTP request sent, awaiting response... 404 Not Found > 2023-12-15 22:23:24 ERROR 404: Not Found. > Hi Fernando, I updated opera and opera-ffmpeg-codecs a couple of weeks ago because it had been abandoned since years asking if anybody was willing to step in as a maintainer or it would have been removed. as upstream seems inclined to also break download links IMHO, if nobody is interested yet (last call), it's time to drop it... Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] tepl
Hi David, I'm sorry but I don't have a solution for your tepl build issue (I looked around but hadn't found anything): as you can read in the first post of the dedicated LQ thread (where you have already posted lots of times) not everything will be fixed in the unofficial repository for current... but, differently for that dedicated LQ thread, this mailing list is not about that: Willy is right, you are reporting it in the wrong place as SBo supports only the latest stable Slackware release (that's also noted in the FAQ Willy pointed you to). I feel a bit strange saying it again because you should already know this as it has been said to you multiple times but, at this point, I guess you just don't care... feel free to look for help for your issues with current wherever you prefer, but not here, thanks. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] RFC updates for gdal slackbuild
IMHO specifying the needed dependencies for an optimal experience is the desired option: what we want is a well-tested base for people needing gdal (or whatever else) for any dependees, if the gdal dependencies of gdal are actually more than anyone may need it just won't hurt. what instead will hurt will be situations where someone may say "I've built gdal with these (reduced set of) dependencies and now my app won't work" and we have to debug and specify every subset of dependencies for gdal depending on any application needing it (just a nightmare). this to say that I'm perfectly fine with your resolution, Greg. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] no fet sourcecode
Il giorno ven 1 dic 2023 alle ore 03:30 ha scritto: > root@cosmos:~# sbopkg > > Processing fet > > fet: > fet not found in /var/cache/sbopkg. > --2023-11-30 18:28:59-- > https://www.lalescu.ro/liviu/fet/download/fet-6.13.0.tar.bz2 > Resolving www.lalescu.ro (www.lalescu.ro)... 77.81.240.93 > Connecting to www.lalescu.ro (www.lalescu.ro)|77.81.240.93|:443... > connected. > HTTP request sent, awaiting response... 404 Not Found > 2023-11-30 18:29:05 ERROR 404: Not Found. hi David, it seems upstream has the bad habit to remove the previous versions of the sources when a new one is out: it will be fixed but in the meantime, FWIW, you can also safely build it manually just version-bump it to 6.13.2. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] MPD needs an update
Il giorno ven 27 ott 2023 alle ore 20:01 Андрей Рабусов
ha scritto:
> Hi all,
>
> I think the mpd's slackbuild (and the corresponding info file) needs to be
> updated to match the latest mpd version, 0.23.14, due to the libfmt update
> to version 10. I didn't get a reply from the maintainer, so hopefully
> somebody else could quickly fix it.
>
> The build error with the current mpd version, 0.23.9, is as follows:
>
> [419/639] Compiling C++ object src/decoder/plugins/libdecoder_plugins.a.p/
> FfmpegDecoderPlugin.cxx.o
> FAILED: src/decoder/plugins/libdecoder_plugins.a.p/
> FfmpegDecoderPlugin.cxx.o
> ccache c++ -Isrc/decoder/plugins/libdecoder_plugins.a.p
> -Isrc/decoder/plugins -I../src/decoder/plugins -Isrc -I../src -I. -I..
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/opus
> -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/SDL2
> -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch
> -Wnon-virtual-dtor -Wextra -Wpedantic -std=c++17 -O3 -ffast-math
> -ftree-vectorize -Wcast-qual -Wdouble-promotion -Wmissing-declarations
> -Wshadow -Wunused -Wvla -Wwrite-strings -Wno-stringop-overflow
> -fno-threadsafe-statics -fmerge-all-constants -Wcomma-subscript
> -Wextra-semi -Wmismatched-tags -Woverloaded-virtual -Wsign-promo -Wvolatile
> -Wvirtual-inheritance -Wno-non-virtual-dtor -Wsuggest-override
> -fvisibility=hidden -ffunction-sections -fdata-sections -D_GNU_SOURCE -O2
> -fPIC -fPIC -DHAVE_UNIX -pthread -D_REENTRANT -D_DEFAULT_SOURCE
> -D_XOPEN_SOURCE=600 -MD -MQ
> src/decoder/plugins/libdecoder_plugins.a.p/FfmpegDecoderPlugin.cxx.o
> -MF src/decoder/plugins/libdecoder_plugins.a.p/FfmpegDecoderPlugin.cxx.o.d
> -o src/decoder/plugins/libdecoder_plugins.a.p/FfmpegDecoderPlugin.cxx.o
> -c ../src/decoder/plugins/FfmpegDecoderPlugin.cxx
> In file included from ../src/Log.hxx:25,
> from ../src/decoder/plugins/FfmpegDecoderPlugin.cxx:47:
> /usr/include/fmt/core.h: In instantiation of ‘constexpr
> fmt::v10::detail::value fmt::v10::detail::make_arg(T&) [with
> bool PACKED = true; Context =
> fmt::v10::basic_format_context char>; T = AVSampleFormat; typename std::enable_if::type
> = 0]’:
> /usr/include/fmt/core.h:1808:51: required from ‘constexpr
> fmt::v10::format_arg_store::format_arg_store(T& ...) [with
> T = {const char*, AVSampleFormat}; Context =
> fmt::v10::basic_format_context char>; Args = {const char*, AVSampleFormat}]’
> /usr/include/fmt/core.h:1826:18: required from ‘constexpr
> fmt::v10::format_arg_store std::remove_reference::type>::type ...> fmt::v10::make_format_args(T&
> ...) [with Context = fmt::v10::basic_format_context char>; T = {const char*, AVSampleFormat}]’
> ../src/Log.hxx:50:31: required from ‘void LogFmt(LogLevel, const
> Domain&, const S&, Args&& ...) [with S = char [51]; Args = {const char*&,
> AVSampleFormat&}]’
> ../src/Log.hxx:99:8: required from ‘void FmtError(const Domain&, const
> S&, Args&& ...) [with S = char [51]; Args = {const char*&,
> AVSampleFormat&}]’
> ../src/decoder/plugins/FfmpegDecoderPlugin.cxx:358:11: required from
> here
> /usr/include/fmt/core.h:1576:63: error: ‘fmt::v10::detail::type_is_
> unformattable_for _’ has incomplete type
> 1576 | type_is_unformattable_for _;
> | ^
> /usr/include/fmt/core.h:1580:7: error: static assertion failed: Cannot
> format an argument. To make type T formattable provide a formatter
> specialization: https://fmt.dev/latest/api.html#udt
> 1580 | formattable,
> | ^~~
> /usr/include/fmt/core.h:1580:7: note: formattable evaluates to false
>
> Regards
> Andrei
>
> thanks for the report, I version-bumped it to 0.23.14 so it should be ok
at the next global update.
Matteo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] khronosschoty's SlackBuilds
Il giorno gio 5 ott 2023 alle ore 07:43 ha scritto: > I emailed khronosschoty months ago about his palemoon SlackBuilds which > are approaching a year old if not already (many versions behind) but > never heard back, nor on IRC. I'm not prepared to take over any but > maybe a SlackBuilds staff member should try to contact him then decide > what to do next. > I've chatted with him on irc a few days ago so I think he's active... Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] new webkit2gtk{4.1}
Il giorno dom 17 set 2023 alle ore 06:33 Willy Sudiarto Raharjo < will...@slackbuilds.org> ha scritto: > Hi all, > > i pushed a new version of webkit2gtk and webkit2gtk4.1 in a separate > branch because this is a major release and i don't want to push things > before making sure every scripts that depends on it built on this new > version. > > it's on my webkit2gtk branch > (https://git.slackbuilds.org/slackbuilds/log/?h=webkit2gtk) and here are > the scripts that depends on both scripts: > > webkit2gtk > ├ badwolf > ├ birdfont > ├ bottles > ├ devhelp > ├ eclipse-platform > ├ gnome-boxes > ├ gnome-builder > ├ gnome-online-accounts > ├ gnucash > ├ gui-ufw > ├ liferea > ├ luakit > ├ lutris > ├ midori > ├ nyxt > ├ opencpn > ├ pdfpc > ├ poedit > ├ pytrainer > ├ shotwell > ├ surf > ├ sushi > ├ vimb > ├ wxHexEditor > ├ wxPython4 > └ yelp > midori works! if anybody needs already built packages for testing the one I used are here https://ponce.cc/slackware/testing/webkit2gtk-testing/ Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Packages Up for Grabs
sorry Johannes, I missed your mail... please go on, I'm sure you'll take a better care of it than me! Matteo Il giorno gio 14 set 2023 alle ore 15:03 Franzen via SlackBuilds-users < slackbuilds-users@slackbuilds.org> ha scritto: > I already did take leafpad some weeks ago, as i didn't hear back from the > maintainer. > > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2023-June/028349.html > > But you may have if you like. > > Johannes > > > Am 14. September 2023 07:05:26 MESZ schrieb Matteo Bernardini < > matteo.bernard...@gmail.com>: > >> I'll take leafpad! >> >> Matteo >> >> Il giorno gio 14 set 2023 alle ore 04:40 Brandon Pribula < >> wbprib...@gmail.com> ha scritto: >> >>> Hello, >>> >>> Unfortunately I don't have the time to maintain my slackbuilds. As a >>> result they are all up for grabs. >>> >>> misc/dos2unix >>> misc/discount >>> office/leafpad >>> office/anorack >>> office/featherpad >>> desktop/ufetch >>> desktop/xwallpaper >>> desktop/bashmount >>> development/micro >>> graphics/farbfeld >>> system/bitrot >>> >>> These packages haven't been updated for over a year. >>> >>> Thanks >>> >>> >>> ___ >>> SlackBuilds-users mailing list >>> SlackBuilds-users@slackbuilds.org >>> 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 > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Packages Up for Grabs
I'll take leafpad! Matteo Il giorno gio 14 set 2023 alle ore 04:40 Brandon Pribula < wbprib...@gmail.com> ha scritto: > Hello, > > Unfortunately I don't have the time to maintain my slackbuilds. As a > result they are all up for grabs. > > misc/dos2unix > misc/discount > office/leafpad > office/anorack > office/featherpad > desktop/ufetch > desktop/xwallpaper > desktop/bashmount > development/micro > graphics/farbfeld > system/bitrot > > These packages haven't been updated for over a year. > > Thanks > > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] codec2 1.0.3 Source No Longer Available
In the meantime I updated the download link in my git branch (it will go in the repo at the next merge)... Thanks for the report, Jeremy! Matteo Il giorno sab 9 set 2023 alle ore 12:26 Jeremy Hansen < jebrhansen+...@gmail.com> ha scritto: > Gustavo, > > In working on a project and testing possible dependencies, I came across > ham/codec2 on SBo. Unfortunately, it looks like the developer deleted the > 1.0.3 release when they added the 1.2.0 release in July. > > I see two ways forward, although, having not used it, I'm sure if one is > better than the other. > > 1. Find a saved copy of 1.0.3 and upload it somewhere else (sbodirectlinks > on sf.net or maybe ponce.cc, if he's willing). Then link SBo's source to > that copy. > 2. Update codec2 to 1.2.0, assuming it doesn't break anything that depends > on it, and hope the developer doesn't delete that release when they drop > the next version. > > I do not use this software, so if you no longer wish to maintain it, maybe > someone else can step in. > > Thanks! > Jeremy > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] abuse SBo fix for Slackware 15.0
I'll take yajl then, as I use it for libvirt... thanks, Ricardo! Matteo Il giorno sab 5 ago 2023 alle ore 03:35 Ricardo J. Barberis < ricardo.barbe...@gmail.com> ha scritto: > Hi! > > I thought I had already mentioned it on the list but let's make it > official: > > Since Im' not using Slackware anymore, I'm no longer maintaining my > slackbuilds, so feel free to grab them please. > > > They are: > > development/colordiff > development/git-cola > development/kdesvn > development/kdiff3 > development/zeal > games/abuse > games/smokin-guns > libraries/yajl > misc/grc > network/geoipupdate > network/pfqueue > network/urlgrabber > office/devtodo > office/vmd > system/acpitool > system/collectd > system/cronie > > Thannks! > > El viernes, 4 de agosto de 2023 14:34:26 -03 shelldweller escribió: > > Hello Ricardo, > > > >I have not been able to get your abuse SBo to run since 15.0 came > >out. I'm basically having the same problem noted here: > > > > https://bugs.archlinux.org/task/52915 > > > >I tried the fix mentioned in that thread, namely build with > > > > --enable-debug > > > >Then, I am no longer getting the error message: > > > > "Lisp: 527 symbols defined, 99 system functions, 319 pre-compiled > > functions (load "abuse.lsp") [..]Segmentation fault" > > > >and, instead, abuse launches like it used to on 14.2. > > > >I just wanted to mention that in case you'd like to update the > >SlackBuild on slackbuilds.org. > > > > thanks for maintaining a great package! > > > > - shelldweller > -- > Ricardo J. Barberis > SysAdmin & IT Architect > Cloud & IaaS > DonWeb.com > La actitud es todo > > > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] xfce4-docklike-plugin icon problem
Il giorno mar 1 ago 2023 alle ore 16:58 Alessandro Baggi < alessandro.ba...@gmail.com> ha scritto: > Hi, > I installed xfce4-docklike-plugin but I have problem with Firefox and > Thunderbird icons. I cannot pin them on the dock and when I launch them > I see a "gear" instead of relative icons. > > Anyone encountered this problem? > > Thank you in advance. > Hi Alessandro, maybe you better ask Marco, the maintainer of the package: I'll put him in cc. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Is the chromaprint SlackBuild failing for anyone else?
someone reported a similar error and it was because he was on Slackware 15.0 but he, for some reason, was using a repository of SlackBuild scripts for Slackware current. make sure you are using a repository of scripts for your version of Slackware (that includes checking the settings of any third party automated build tool you are using). Matteo Il giorno sab 8 lug 2023 alle ore 04:52 yabobay ha scritto: > On slackware64 15, it fails for me. I don't know if i should include > output, but here it is: > > /tmp/SBo/chromaprint-1.5.1/src/utils/base64.cpp: In function ‘void > chromaprint::Base64Encode(const string&, std::string&)’: > /tmp/SBo/chromaprint-1.5.1/src/utils/base64.cpp:12:20: warning: variable > ‘end’ set but not used [-Wunused-but-set-variable] > 12 | const auto end = Base64Encode(src.cbegin(), src.cend(), > dest.begin()); >|^~~ > /tmp/SBo/chromaprint-1.5.1/src/utils/base64.cpp: In function ‘void > chromaprint::Base64Decode(const string&, std::string&)’: > /tmp/SBo/chromaprint-1.5.1/src/utils/base64.cpp:26:20: warning: variable > ‘end’ set but not used [-Wunused-but-set-variable] > 26 | const auto end = Base64Decode(src.cbegin(), src.cend(), > dest.begin()); >|^~~ > [ 36%] Building C object > src/CMakeFiles/chromaprint_objs.dir/avresample/resample2.c.o > [ 36%] Built target chromaprint_objs > [ 38%] Building CXX object src/CMakeFiles/chromaprint.dir/chromaprint.cpp.o > [ 40%] Linking CXX shared library libchromaprint.so > [ 40%] Built target chromaprint > [ 42%] Building CXX object src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o > In file included from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7: > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h: In > constructor ‘chromaprint::FFmpegAudioReader::FFmpegAudioReader()’: > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:102:23: > warning: ‘void av_init_packet(AVPacket*)’ is deprecated > [-Wdeprecated-declarations] >102 | av_init_packet(&m_packet); >| ~~^~~ > In file included from /usr/include/libavcodec/bsf.h:30, > from /usr/include/libavcodec/avcodec.h:44, > from > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18, > from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7: > /usr/include/libavcodec/packet.h:488:6: note: declared here >488 | void av_init_packet(AVPacket *pkt); >| ^~ > In file included from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7: > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h: In member > function ‘bool chromaprint::FFmpegAudioReader::Open(const string&)’: > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:138:19: > warning: ‘void av_init_packet(AVPacket*)’ is deprecated > [-Wdeprecated-declarations] >138 | av_init_packet(&m_packet); >| ~~^~~ > In file included from /usr/include/libavcodec/bsf.h:30, > from /usr/include/libavcodec/avcodec.h:44, > from > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18, > from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7: > /usr/include/libavcodec/packet.h:488:6: note: declared here >488 | void av_init_packet(AVPacket *pkt); >| ^~ > In file included from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7: > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:144:69: > error: invalid conversion from ‘const AVInputFormat*’ to > ‘AVInputFormat*’ [-fpermissive] >144 | ret = avformat_open_input(&m_format_ctx, > file_name.c_str(), m_input_fmt, &m_input_opts); > | ^~~ > | | > | const AVInputFormat* > In file included from > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:19, > from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7: > /usr/include/libavformat/avformat.h:2226:90: note: initializing > argument 3 of ‘int avformat_open_input(AVFormatContext**, const char*, > AVInputFormat*, AVDictionary**)’ > 2226 | int avformat_open_input(AVFormatContext **ps, const char *url, > ff_const59 AVInputFormat *fmt, AVDictionary **options); > | ~~~^~~ > In file included from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7: > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:157:77: > error: invalid conversion from ‘const AVCodec**’ to ‘AVCodec**’ > [-fpermissive] >157 | ret = av_find_best_stream(m_format_ctx, > AVMEDIA_TYPE_AUDIO, -1, -1, &codec, 0); > | ^~ > | | > | const AVCodec** > In file included from > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:19, > from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7: > /usr/include/libavformat/avformat.h:2301:35: note: initializing > argument 5 of ‘int av_find_best_stream(AVFormatContext*, AVMediaType, > int, int, AVCodec**, int)’ > 2301 |
Re: [Slackbuilds-users] Updates - 20230617.1
I'll put the maintainer in cc, I think he forgot to update the MD5SUM... Matteo Il giorno lun 3 lug 2023 alle ore 16:33 414N <4...@slacky.it> ha scritto: > Il 17/06/23 12:38, Willy Sudiarto Raharjo ha scritto: > > office/LanguageTool: Updated for version 6.1. > > Using sbopkg I find a different MD5 than the expected one: > > Found LanguageTool-6.1.zip in /var/cache/sbopkg. > Checking MD5SUM: >MD5SUM check for LanguageTool-6.1.zip ... FAILED! > Expected: b750011ec97d2fd94e41fc37899844d3 > Found:fc4875d72950bb1302379559fc1168c5 > > I tried re-downloading the source package several times to no avail. > > Does anyone have the same issue? > > -- > Alan Alberghini > > SBo clone: https://github.com/414n/slackbuilds.org > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] sboinstall chromprint fails
Hi Ed,
I'm not sure where sbotools keeps the local copy of the repo, maybe
/usr/sbo or something similar.
The two SlackBuild you've found are the one in the working directory
generated when you built it manually and the one installed from the
generated package (so not the one in the local repo).
Matteo
Il sab 24 giu 2023, 08:49 Ed Fletcher ha scritto:
> Hi Matteo:
>
> Yes, but I was hoping that having a .current repo might explain my
> printer problem. Oh well.
>
> This might be a pointless exercise and I don't want to waste your time.
> VLC is working for me, which is what depends on chromaprint. Just had
> to install chromaprint the old way. I only posted this originally in
> case someone involved with sbotools might be interested.
>
> diff shows the two files to be identical. So I don't think the problem
> is here. Regardless, this is the file
>
> /tmp/SBo/package-chromaprint/usr/doc/chromaprint-1.5.1/chromaprint.SlackBuild
>
> #!/bin/bash
>
> # Slackware build script for chromaprint
>
> # Copyright 2012-2022 Matteo Bernardini , Pisa,
> Italy
> # All rights reserved.
> #
> # Redistribution and use of this script, with or without modification, is
> # permitted provided that the following conditions are met:
> #
> # 1. Redistributions of this script must retain the above copyright
> #notice, this list of conditions and the following disclaimer.
> #
> # THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR
> IMPLIED
> # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
> # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
> IN NO
> # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
> # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
> LIMITED TO,
> # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
> PROFITS;
> # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
> # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
> # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
> # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>
> cd $(dirname $0) ; CWD=$(pwd)
>
> PRGNAM=chromaprint
> VERSION=${VERSION:-1.5.1}
> BUILD=${BUILD:-1}
> TAG=${TAG:-_SBo}
> PKGTYPE=${PKGTYPE:-tgz}
>
> if [ -z "$ARCH" ]; then
>case "$( uname -m )" in
> i?86) ARCH=i586 ;;
> arm*) ARCH=arm ;;
> *) ARCH=$( uname -m ) ;;
>esac
> fi
>
> # If the variable PRINT_PACKAGE_NAME is set, then this script will
> report what
> # the name of the created package would be, and then exit. This information
> # could be useful to other scripts.
> if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
>echo "$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE"
>exit 0
> fi
>
> TMP=${TMP:-/tmp/SBo}
> PKG=$TMP/package-$PRGNAM
> OUTPUT=${OUTPUT:-/tmp}
>
> if [ "$ARCH" = "i586" ]; then
>SLKCFLAGS="-O2 -march=i586 -mtune=i686"
>LIBDIRSUFFIX=""
> elif [ "$ARCH" = "i686" ]; then
>SLKCFLAGS="-O2 -march=i686 -mtune=i686"
>LIBDIRSUFFIX=""
> elif [ "$ARCH" = "x86_64" ]; then
>SLKCFLAGS="-O2 -fPIC"
>LIBDIRSUFFIX="64"
> else
>SLKCFLAGS="-O2"
>LIBDIRSUFFIX=""
> fi
>
> if pkg-config --exists libavcodec; then tools="-DBUILD_TOOLS=ON"; else
> tools=""; fi
>
> DOCS="LICENSE.md NEWS.txt README.md"
>
> set -e
>
> rm -rf $PKG
> mkdir -p $TMP $PKG $OUTPUT
> cd $TMP
> rm -rf $PRGNAM-$VERSION
> tar xvf $CWD/$PRGNAM-$VERSION.tar.?z*
> cd $PRGNAM-$VERSION
> chown -R root:root .
> find -L . \
> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
> -o -perm 511 \) -exec chmod 755 {} \; -o \
> \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
> -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
>
> mkdir -p build
> cd build
>cmake \
> -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
> -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
> -DCMAKE_INSTALL_PREFIX=/usr \
> -DLIB_SUFFIX=${LIBDIRSUFFIX} \
> $tools \
> -DCMAKE_BUILD_TYPE=Release ..
>make
>make install DESTDIR=$PKG
> cd ..
>
> find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared
> object" | grep ELF \
>| cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
>
> mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
> cp -a $DOCS $PKG/usr/doc/$PRGNAM-$VERSION
> cat $CWD/
Re: [Slackbuilds-users] sboinstall chromprint fails
Hi Ed, I start by saying that I don't use sbotools so I don't know how it works. if you have the possibility to paste the content of chromaprint.SlackBuild as cointained in your local repository used by sbotools (not the one you downloaded manually) it might help. FWIW let me say that chromaprint has nothing to do with printers (please have a look at its README)... Matteo Il giorno sab 24 giu 2023 alle ore 02:43 Ed Fletcher ha scritto: > I don't think so. I've got sbotools v2.7 and didn't make any > configuration changes. My understanding is that sbo gets the version of > slackware from the system it's running on and uses that to get the > correct packages. Perhaps from /etc/slackware-version? Mine says > Slackware 15.0 and doesn't mention 64. > > The only place I can find current mentioned is in the README in > /usr/sbo/repo, which points to https://github.com/Ponce/slackbuilds/wiki > > That page mentions configuring the current repository with sbopkg in > /etc/sbopkg/sbopkg.conf but that page is old, from before 15.0. > > I don't have that directory in /etc so I don't see where to point > sbotools to current. > > Thanks for looking at this Matteo. I was hoping it was an easy fix. I > don't need it for chromaprint or vlc but I thought it might help me with > my printer. > > Ed > > On 6/22/23 23:35, Matteo Bernardini wrote: > > hi Ed, > > > > could it be that you have configured with sbotools a repository for > > Slackware current while you are running slackware 15.0? > > > > Matteo > > > > Il giorno gio 22 giu 2023 alle ore 23:59 Ed Fletcher > <mailto:e...@fletcher.ca>> ha scritto: > > > > While using sbo to put vlc on a freshly installed and updated > > Slackware64-15.0 (sboinstall vlc), the process failed on > > chromaprint. I > > tried chromaprint by itself (sboinstall chromaprint) but it failed > with > > the same error: > > > > In file included from > > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18, > >from > /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7: > > /usr/include/libavcodec/avcodec.h:3047:5: note: declared here > >3047 | int avcodec_decode_audio4(AVCodecContext *avctx, AVFrame > > *frame, > > | ^ > > make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/build.make:76: > > src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1 > > make[1]: *** [CMakeFiles/Makefile2:244: > > src/cmd/CMakeFiles/fpcalc.dir/all] Error 2 > > make: *** [Makefile:136: all] Error 2 > > Failures: > > chromaprint: chromaprint.SlackBuild return non-zero > > > > What I find strange is that downloading the source and the slackbuild > > let me install it successfully. This let sboinstall finish > installing > > vlc. So I have everything working, just left with a puzzle. > > > > Ed > > -- > > Ed Fletcher > > > > "When I became a man I put away childish things, including the fear > of > > childishness and the desire to be very grown up.” > > ― C.S. Lewis > > ___ > > SlackBuilds-users mailing list > > SlackBuilds-users@slackbuilds.org > > <mailto:SlackBuilds-users@slackbuilds.org> > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users> > > Archives - > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > <https://lists.slackbuilds.org/pipermail/slackbuilds-users/> > > FAQ - https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/> > > > > > > ___ > > SlackBuilds-users mailing list > > SlackBuilds-users@slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > -- > Ed Fletcher > > "When I became a man I put away childish things, including the fear of > childishness and the desire to be very grown up.” > ― C.S. Lewis > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] sboinstall chromprint fails
hi Ed, could it be that you have configured with sbotools a repository for Slackware current while you are running slackware 15.0? Matteo Il giorno gio 22 giu 2023 alle ore 23:59 Ed Fletcher ha scritto: > While using sbo to put vlc on a freshly installed and updated > Slackware64-15.0 (sboinstall vlc), the process failed on chromaprint. I > tried chromaprint by itself (sboinstall chromaprint) but it failed with > the same error: > > In file included from > /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18, > from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7: > /usr/include/libavcodec/avcodec.h:3047:5: note: declared here > 3047 | int avcodec_decode_audio4(AVCodecContext *avctx, AVFrame *frame, >| ^ > make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/build.make:76: > src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1 > make[1]: *** [CMakeFiles/Makefile2:244: > src/cmd/CMakeFiles/fpcalc.dir/all] Error 2 > make: *** [Makefile:136: all] Error 2 > Failures: >chromaprint: chromaprint.SlackBuild return non-zero > > What I find strange is that downloading the source and the slackbuild > let me install it successfully. This let sboinstall finish installing > vlc. So I have everything working, just left with a puzzle. > > Ed > -- > Ed Fletcher > > "When I became a man I put away childish things, including the fear of > childishness and the desire to be very grown up.” > ― C.S. Lewis > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] umask error on calcurse
Il giorno mer 31 mag 2023 alle ore 16:45 Ruben Carlo Benante via SlackBuilds-users ha scritto: > Dear Slackbuild maintainers, > > Sorry for the brief bug report, but here it is, hoping it will help track > the problem: > > If you use umask 007 (or other for that matter) and install the package > calcurse, > you end up with a /usr directory with wrong permissions. > > If you need any other information, I'll be glad to add to it on Friday. > hi Ruben, you should become root with "su -", so that you use a root login shell, before running any SlackBuild (it's explained at step 4 of the HOWTO https://slackbuilds.org/howto/ ). also, your root user shouldn't have a non-standard umask (0022) because things, as you saw, break (not just with SlackBuilds): that's just *NOT SUPPORTED*. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] qemu updates roadmap
Hi Edward, here I'm building qemu 8.0.0 and virtiofsd like this (actually I see no issue in using the bundled meson) https://ponce.cc/slackware/testing/virtiofsd/ https://ponce.cc/slackware/testing/qemu/ if you don't want it I'll submit virtiofsd to SBo. Matteo Il giorno lun 24 apr 2023 alle ore 02:13 KB_SBo ha scritto: > All, > > I'm going to hold off on qemu-8.0 for a bit and just bump to qemu-7.2.1 > > > 1. For 8.0, virtiofsd is now an external dependency. This built with > rust, of which I know absolutely nothing about. Since this may take me > awhile to do (wtf is a 'cargo'?), if anyone has a burning desire to add > virtiofsd to SBo, have at it! > > 2. Slackware 15.0 meson-0.59.4 is too old. qemu has an internal > meson-0.61.5 that is currently used for 7.2.x, but I think using the > system meson is better for consistency. > > 3. libslirp and a few others will be made hard dependencies to have > those handy features available by default. Also, libslirp could use bump > to version 4.7.0 (maintainer cc:'ed) > > > -Ed > > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Microsoft fonts
Il giorno lun 24 apr 2023 alle ore 17:23 Matteo Bernardini < matteo.bernard...@gmail.com> ha scritto: > keeped > BTW, sorry for my terrible english... Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Microsoft fonts
because Microsoft keeped distributing the webcore fonts until at least 2009, so they probably packaged vista fonts too... https://web.archive.org/web/20091208063245/http://www.microsoft.com/typography/fontpack/eula.htm the tarball we are using on SBo is the one redistributed by Avi Alkalay in 2007 https://avi.alkalay.net/articlefiles/linux/docs/font-howto/Font.html Matteo Il giorno lun 24 apr 2023 alle ore 16:55 Petar Petrov ha scritto: > for the record, the webcore fonts project was terminated in 2002, > right? So, how come we have Calibri and co, from Vista? I am not > arguing or being a dick, just wondering. > > -petar > > On Mon, 24 Apr 2023 at 17:49, Matteo Bernardini > wrote: > > > > if you ask me I don't think they can be repackaged (=> I don't think > that the AUR maintainer for those is not breaking any license). > > > > Matteo > > > > Il giorno lun 24 apr 2023 alle ore 16:45 Petar Petrov < > slackal...@gmail.com> ha scritto: > >> > >> Hi Matteo, > >> > >> thanks for the clarification. So, what shall we do about the fonts from > the ISO? > >> > >> -petar > >> > >> On Mon, 24 Apr 2023 at 17:41, Matteo Bernardini > >> wrote: > >> > > >> > hi Petar, > >> > > >> > the state of the webcore fonts is more permissive as they have been > already distributed in the past and they are packaged from their original > exes, please see > >> > > >> > https://en.wikipedia.org/wiki/Core_fonts_for_the_Web > >> > > >> > > https://en.wikipedia.org/wiki/Core_fonts_for_the_Web#Program_termination_and_software_license_agreement_issues > >> > (read the first paragraph of this bit carefully) > >> > > >> > I don't think that this licensing could be applied also to the fonts > found on a windows iso. > >> > > >> > Matteo > >> >> > >> >> > >> > ___ > >> > SlackBuilds-users mailing list > >> > SlackBuilds-users@slackbuilds.org > >> > 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 > >> SlackBuilds-users@slackbuilds.org > >> 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 > > SlackBuilds-users@slackbuilds.org > > 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 > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Microsoft fonts
if you ask me I don't think they can be repackaged (=> I don't think that the AUR maintainer for those is not breaking any license). Matteo Il giorno lun 24 apr 2023 alle ore 16:45 Petar Petrov ha scritto: > Hi Matteo, > > thanks for the clarification. So, what shall we do about the fonts from > the ISO? > > -petar > > On Mon, 24 Apr 2023 at 17:41, Matteo Bernardini > wrote: > > > > hi Petar, > > > > the state of the webcore fonts is more permissive as they have been > already distributed in the past and they are packaged from their original > exes, please see > > > > https://en.wikipedia.org/wiki/Core_fonts_for_the_Web > > > > > https://en.wikipedia.org/wiki/Core_fonts_for_the_Web#Program_termination_and_software_license_agreement_issues > > (read the first paragraph of this bit carefully) > > > > I don't think that this licensing could be applied also to the fonts > found on a windows iso. > > > > Matteo > >> > >> > > ___ > > SlackBuilds-users mailing list > > SlackBuilds-users@slackbuilds.org > > 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 > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Microsoft fonts
hi Petar, the state of the webcore fonts is more permissive as they have been already distributed in the past and they are packaged from their original exes, please see https://en.wikipedia.org/wiki/Core_fonts_for_the_Web https://en.wikipedia.org/wiki/Core_fonts_for_the_Web#Program_termination_and_software_license_agreement_issues (read the first paragraph of this bit carefully) I don't think that this licensing could be applied also to the fonts found on a windows iso. Matteo > > ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Microsoft fonts
can you put a link to these fonts' licenses? if they are not available as web pages could you please paste them somewhere (like pastebin or something) and put the link in a subsequent mail to this list? thanks in advance! Matteo Il giorno lun 24 apr 2023 alle ore 15:18 Petar Petrov ha scritto: > Hi guys, > > i'd like to hear your opinion (especially admins) on a couple of > SlackBuilds i've been working on. They extract MS Windows 11 fonts and > MS Office 2007 from the evaluation and web-archive ISOs, respectively: > > > https://github.com/slackalaxy/misc/tree/master/preliminary/microsoft-fonts-win11 > > https://github.com/slackalaxy/misc/tree/master/preliminary/microsoft-office-fonts > > Would SBo accept scripts that do that? > > We already have the webcore fonts, however these provide the latest > versions of Ariel, Calibri, etc, while the MS office ones make the > collection really complete. I was happily using the webcore fonts > until I needed to submit a paper, whose template required Palatino > Linotype and struggled with formatting in the very last minute... > > for the record, I also have a SlackBuild that does this for MathType fonts: > https://github.com/slackalaxy/misc/tree/master/preliminary/mathtype-fonts > > best, > > Petar > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] VTK
Hi Tim, I just tried to build it with your same options on a clean and full installation of slackware64-15.0 but everything went fine here... Matteo Il giorno ven 14 apr 2023 alle ore 20:26 Tim Dickson via SlackBuilds-users < slackbuilds-users@slackbuilds.org> ha scritto: > hi all, I'm getting the following error building VTK > > [ 99%] Linking CXX shared module > ../../../lib64/qml/VTK.9.2/libqmlvtkplugin.so > Generating qmltypes file using qmlplugindump > QQmlComponent: Component is not ready > make[2]: *** > [GUISupport/QtQuick/qml/CMakeFiles/qmlvtkplugin.dir/build.make:151: > lib64/qml/VTK.9.2/libqmlvtkplugin.so] Error 3 > make[2]: *** Deleting file 'lib64/qml/VTK.9.2/libqmlvtkplugin.so' > make[1]: *** [CMakeFiles/Makefile2:18427: > GUISupport/QtQuick/qml/CMakeFiles/qmlvtkplugin.dir/all] Error 2 > make: *** [Makefile:136: all] Error 2 > > I have IMAGING=yes and MPI=yes flags set. (and openmpi installed) > > Any ideas? > regards, Tim > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] fprintd & libfprint : pam module for elogind
if Terry is not active anymore then maybe Fabio, that maintains fprintd (that depends on libfprint) would like to step in as a maintainer? either he or someone else does or we will be forced to drop both the scripts... Matteo Il giorno mar 7 mar 2023 alle ore 16:02 marav ha scritto: > Le 07/03/2023 à 15:59, marav a écrit : > > Hi all, > > > > Could you have a look at : > > > > https://gitlab.com/maravtdm/fprint_all > > > > There are small modifications (for libfprint and fprintd) to have > > pam_fprintd.so without systemd (with elogind) > > > > It works well here, but probably needs more testing > > > > > > Thanks! > > > > > > ___ > > SlackBuilds-users mailing list > > SlackBuilds-users@slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > @ponce > > The email of Terry Laundos doesn't exists anymore ... > > _ > > This is the mail system at host smtp2-g21.free.fr. > > I'm sorry to have to inform you that your message could not > be delivered to one or more recipients. It's attached below. > > For further assistance, please send mail to postmaster. > > If you do so, please include this problem report. You can > delete your own text from the attached returned message. > > The mail system > > : host aspmx.l.google.com[66.102.1.27] said: > 550-5.1.1 > The email account that you tried to reach does not exist. Please try > 550-5.1.1 double-checking the recipient's email address for typos or > 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 > https://support.google.com/mail/?p=NoSuchUser > s10-20020a05600c384a00b003de6e4c8c58si12257974wmr.18 - gsmtp (in > reply to > RCPT TO command) > > > Reporting-MTA: dns; smtp2-g21.free.fr > X-Postfix-Queue-ID: B36AA2003EE > X-Postfix-Sender: rfc822; mar...@free.fr > Arrival-Date: Tue, 7 Mar 2023 15:59:20 +0100 (CET) > > Final-Recipient: rfc822; te...@s1solucoes.com.br > Original-Recipient: rfc822;te...@s1solucoes.com.br > Action: failed > Status: 5.1.1 > Remote-MTA: dns; aspmx.l.google.com > Diagnostic-Code: smtp; 550-5.1.1 The email account that you tried to > reach does > not exist. Please try 550-5.1.1 double-checking the recipient's email > address for typos or 550-5.1.1 unnecessary spaces. Learn more at > 550 5.1.1 > https://support.google.com/mail/?p=NoSuchUser > s10-20020a05600c384a00b003de6e4c8c58si12257974wmr.18 - gsmtp > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] proposal to enable building scripts on ARM
unfortunately they are painfully slow and we can't ask our maintainers to
support also those architectures.
Il giorno sab 4 mar 2023 alle ore 18:42 Fernando Lopez <
fernando.lope...@gmail.com> ha scritto:
> willy there are arm VM's.
>
> On Sat, Mar 4, 2023, 9:25 AM Willy Sudiarto Raharjo <
> will...@slackbuilds.org> wrote:
>
>> > ARM isn't going away, and slackbuilds.org supporting at least a subset
>> > of scripts to be build on ARM would be really nice to have. I'm not
>> > heavily invested in it, I just have some RPis with Slackware on it that
>> > I occasionally use. Just sharing my thoughts, as it's a semi-frequently
>> > discussed topic.
>> >
>> > The main problem with allowing support for ARM is that the layout of
>> > the info files would change, which could break tooling. I just had an
>> > idea which wouldn't break any existing tools, but could enable
>> > architecture specific information to be read by other tools (or
>> > humans):
>> >
>> > For each additional supported architecture other than x86 and x86_64 add
>> > a file named ${PRGNAM}.${ARCH}info which add/override values of the
>> > classic info file. The only additional change would be in the code to
>> > detect architectures in the SlackBuilds, but that should be of no
>> > relevance for tools.
>>
>> The problem is that we (admins) might not have a machine to test the ARM
>> architecture, so we can't validate the script.
>> Plus it adds more loads to the admins to validate over 8k scripts during
>> development cycle for next release of SlackBuild repository.
>>
>> We had issues with failing 32 bit builds for 15.0 since majority of
>> users here are using 64 bit machines only and didn't test on 32 bit
>> machines anymore so some goes undetected.
>>
>>
>> --
>> Willy Sudiarto Raharjo
>>
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> 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
> SlackBuilds-users@slackbuilds.org
> 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
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] conky compile error
Il giorno sab 25 feb 2023 alle ore 15:17 marav ha scritto:
> You should look on how Corrado builds lua, lua51 etc
> He adds this line, foro lua53 for example:
>
> # Fix lua 5.3
> sed -r -e "/^LUA_(SO|A|T)=/ s/lua/lua$MAINVERSION/" -e "/^LUAC_T=/
> s/luac/luac$MAINVERSION/" -i src/Makefile
>
>
> I have:
>
> # ls -lhC1 /var/lib/pkgtools/packages/ | grep lua
> lua51-5.1.5-x86_64-7cf
> lua53-5.3.6-x86_64-1cf
> lua54-5.4.4-x86_64-1_tdm
>
> And conly builds fine:
>
> usr/share/vim/vimfiles/ftdetect/conkyrc.vim
> usr/share/vim/vimfiles/syntax/
> usr/share/vim/vimfiles/syntax/conkyrc.vim
>
> Slackware package /tmp/conky-1.18.1-x86_64-1_SBo.tgz created.
>
unfortunately while that could be ok for conky I doubt it will work with
the other stuff that needs lua{,52,53} on SBo...
if someone has patches ready they are welcome!
Matteo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] conky compile error
Hi Tonus, I'm sorry, maybe I missed it or I just don't remember... could you please elaborate on your suggestion? It is something that you have already tested yourself locally? Matteo Il giorno sab 25 feb 2023 alle ore 13:06 Tonus ha scritto: > >>Il giorno sab 25 feb 2023 alle ore 11:35 Konrad J Hambrick < > >>kjhambr...@gmail.com> ha scritto: > >> > >> Matthew / all -- > >> > >> I am running an up-to-date Slackware64 15.0 + Multilib System > >> > >> I've got lua53 and imlib2 installed: > >> > >>lua53-5.3.4-x86_64-1_SBo > >>imlib2-1.10.0-x86_64-1_SBo_with-docs > >> > >> This morning's conky update failed to compile. > >> > >> Or, Is it just me ? > >> > >> Thanks > >> > >> -- kjh > >> > > On Sat, Feb 25, 2023 at 12:21:54PM +0100, Matteo Bernardini wrote: > >I think this happens because you have also lua installed: if you remove it > >conky should detect correctly lua53. > > > >Matteo > > > > Hi all > > It's a recurring problem. I had suggest a way to have all lua installed > side-by-side before the 15.0 rise IIRC. It was involving some changes to > the original lua pkg. > > Could it be something to be rework on ? (was not a wish on the list at > the time) > > -- > Regards, > > Tonus > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] conky compile error
I think this happens because you have also lua installed: if you remove it conky should detect correctly lua53. Matteo Il giorno sab 25 feb 2023 alle ore 11:35 Konrad J Hambrick < kjhambr...@gmail.com> ha scritto: > Matthew / all -- > > I am running an up-to-date Slackware64 15.0 + Multilib System > > I've got lua53 and imlib2 installed: > >lua53-5.3.4-x86_64-1_SBo >imlib2-1.10.0-x86_64-1_SBo_with-docs > > This morning's conky update failed to compile. > > Or, Is it just me ? > > Thanks > > -- kjh > > Tail of the build log: > > [ 10%] Running tolua++ on cairo_imlib2_helper.pkg > > ** tolua internal error: [string > "/tmp/SBo/conky-1.18.0/3rdparty/toluapp/src/..."]:337: bad argument #1 to > 'load' (function expected, got string) > stack traceback: > [C]: in function 'load' > [string "/tmp/SBo/conky-1.18.0/3rdparty/toluapp/src/..."]:337: in > function 'prep' > [string "/tmp/SBo/conky-1.18.0/3rdparty/toluapp/src/..."]:253: in > function 'Package' > [string "/tmp/SBo/conky-1.18.0/3rdparty/toluapp/src/..."]:54: in > function <[string "/tmp/SBo/conky-1.18.0/3rdparty/toluapp/src/..."]:27> > [C]: in function 'xpcall' > ...Bo/conky-1.18.0/3rdparty/toluapp/src/bin/lua/all.lua:25: in > main chunk. > > > [ 10%] Running tolua++ on cairo_imlib2_helper.pkg > > ** tolua internal error: [string > "/tmp/SBo/conky-1.18.0/3rdparty/toluapp/src/..."]:337: bad argument #1 to > 'load' (function expected, got string) > stack traceback: > [C]: in function 'load' > [string "/tmp/SBo/conky-1.18.0/3rdparty/toluapp/src/..."]:337: in > function 'prep' > [string "/tmp/SBo/conky-1.18.0/3rdparty/toluapp/src/..."]:253: in > function 'Package' > [string "/tmp/SBo/conky-1.18.0/3rdparty/toluapp/src/..."]:54: in > function <[string "/tmp/SBo/conky-1.18.0/3rdparty/toluapp/src/..."]:27> > [C]: in function 'xpcall' > ...Bo/conky-1.18.0/3rdparty/toluapp/src/bin/lua/all.lua:25: in > main chunk. > > > [ 11%] Building C object > lua/CMakeFiles/conky-cairo_imlib2_helper.dir/libcairo_imlib2_helper.c.o > cc1: fatal error: > /tmp/SBo/conky-1.18.0/build/lua/libcairo_imlib2_helper.c: No such file or > directory > compilation terminated. > make[2]: *** [lua/CMakeFiles/conky-cairo_imlib2_helper.dir/build.make:80: > lua/CMakeFiles/conky-cairo_imlib2_helper.dir/libcairo_imlib2_helper.c.o] > Error 1 > make[1]: *** [CMakeFiles/Makefile2:274: > lua/CMakeFiles/conky-cairo_imlib2_helper.dir/all] Error 2 > make: *** [Makefile:166: all] Error 2 > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] VLC maintainership
ok, you convinced me: if noone else wants them badly I'll take portaudio, libshout and libdca! Il giorno mar 7 feb 2023 alle ore 22:10 B. Watson ha scritto: > > > On Tue, 7 Feb 2023, Bill Kirkpatrick wrote: > > > This would include these five > > programs:live555, portaudio, zvbi, libdca, & libshout, which > > came to me with VLC & are not used anywhere else. > > portaudio is used by other stuff, see: > > https://slackbuilds.org/advsearch.php?stype=revdep&q=portaudio > > libshout is also used by others: > > https://slackbuilds.org/advsearch.php?stype=revdep&q=libshout > > libdca is used by avidemux, so maybe its maintainer could take that > one?___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Any issue with SBo
hi Dimitris, can you please make an example of a file that you are trying the download and it fails? Matteo Il giorno mer 25 gen 2023 alle ore 19:50 Dimitris Zlatanidis < d.zlatani...@gmail.com> ha scritto: > Hi to all, > > Is there any issue with the repository? I can't download from it with > wget command but only via the browser. > > Thanks > > -- > Dimitris Zlatanidis > https://dslackw.gitlab.io/slpkg/ > https://gitlab.com/dslackw > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] nodejs
Il giorno ven 20 gen 2023 alle ore 20:20 Matteo Bernardini < matteo.bernard...@gmail.com> ha scritto: > Judah, I never used sbotools but I'm pretty sure that if it doesn't find > nodejs in the repository it's not using the repository for 15.0. > > please check this message on the sbotools issue tracker > > https://github.com/pink-mist/sbotools/issues/86 > > the latest release has been done before 15.0 was out so it doesn't ship a > configuration pointing to our repository for 15.0. > FWIW, googling "sbotools" as a fourth result I also got this forum topic https://www.linuxquestions.org/questions/slackware-14/sbotools-patch-for-slackware-15-0-a-4175709648/ Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] nodejs
Il giorno ven 20 gen 2023 alle ore 19:56 J. Milgram ha scritto: > Matteo, > > Thanks, I hadn't thought to check this. > As near as I can tell, my sbotools points at Slackware 15.0, not -current: > > - I have no /etc/sbotools/sbotools.conf (not even an /etc/sbotools) > > - sboconfig -l tells me SLACKWARE_VERSION=FALSE and also REPO=FALSE > > - my /etc/slackware-version has: Slackware 15.0 > > I wonder... could there be another reason why sbocheck would fail to > make a local copy of something in the repo? > > Judah > Judah, I never used sbotools but I'm pretty sure that if it doesn't find nodejs in the repository it's not using the repository for 15.0. please check this message on the sbotools issue tracker https://github.com/pink-mist/sbotools/issues/86 the latest release has been done before 15.0 was out so it doesn't ship a configuration pointing to our repository for 15.0. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] nodejs
Judah, which repository are you using with sbotools? from the message it seems that you are using a repository for slackware current, but if you haven't nodejs already installed you most probably are on slackware 15.0, right? if this is the case you should be ok switching in sbotools to the stock slackbuilds.org repository, that is made for the latest stable Slackware, 15.0 ATM. Matteo Il giorno gio 19 gen 2023 alle ore 07:13 J. Milgram ha scritto: > > Trying to build rstudio-desktop. Requires yarn which in turn requires > nodejs. > > Searching at slackbuilds.org turns up a slackbuild for same (nodejs > 19.4.0). Good. > > But sbocheck (and sbosnap) don't seem to be downloading nodejs with the > rest of the repository, so when I try to build rstudio-desktop with > sboinstall, I get "Unable to locate nodejs in the SlackBuilds.org tree." > > Haven't run into this before. What am I doing wrong? I've got sbotools > 2.7. > > thanks! > > Judah > > > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Audacity issue
Il giorno dom 15 gen 2023 alle ore 11:55 Dimitris Zlatanidis < d.zlatani...@gmail.com> ha scritto: > Hi to all, > Is anyone who uses audacity and he has an issue with the track display > area not updating? Unexpectedly it stopped refreshing. I uninstalled the > package, the dependencies and all configs from my home directory, and I > updated to 3.2.3 but still not working. > > Any suggest? > something similar happened here (blank waveform display): I rebuilt everything (audacity and all the dependencies) on a full and up-to-date slackware64-15.0 installation (a virtual machine) with no other third party packages, and installing the new packages seems to have done the trick (now waveforms display again). while I was at it I also updated audacity to 3.2.3 in our git (thanks for the heads-up!). but I suspect (it's just a guess) that rebuilding wxWidgets was the culprit... Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] mkvtoolnix : FTBFS with latest ruby 3.2
thanks for the patch, marav, I'll put it in the unofficial repository for current if Ozan doesn't beat me with an update. but consider that SBo supports only the latest Slackware stable so also this kind of reports are actually a bit OT: if you want to keep report them in this mailing list be careful to specify always that they apply only to current (so that people that may want to skip them could), otherwise the best place for them, IMHO, besides writing directly to the maintainers, is the dedicated LQ topic. Matteo Il giorno mar 3 gen 2023 alle ore 12:01 marav ha scritto: > Hi Ozan, > > mkvtoolnix should be upgraded to 73.0 with this patch : > > > https://gitlab.com/mbunkus/mkvtoolnix/-/commit/ab6455f68c597ede3d6959597a38f2ecbc198011.patch > > in order to be built with ruby 3.2 > > > Cheers > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Nextcloud glibc build error
Hi phalange, happy new year to you too! FWIW I just tried building nextcloud-desktop on a pristine installation of slackware64-15.0 and on another pristine installation of slackware64-current and in both cases the build went fine with no error while linking that library providded by the samba package... if you are using stable have you got by any chance applied all the updates shipped for 15.0? frankly I cannot think of anything else that might cause similar errors besides partial updates or mixing packages with current... Matteo Il giorno dom 1 gen 2023 alle ore 22:04 ha scritto: > Happy new year, I am getting a fatal build error: > > /usr/bin/ld: /usr/lib64/libsys-rw-samba4.so: undefined reference to > `__steck_chk_fail@GLIBC_2.4' > collect2: error: ld returned 1 exit status > > Any ideas? > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Issues with new scripts for crelay
yes, you can use a patch or set PREFIX as null like sed -i "s|PREFIX=/local|PREFIX=|" src/Makefile both are fine, IMHO. Matteo Il giorno dom 20 nov 2022 alle ore 21:03 Sebastian Arcus < s.ar...@open-t.co.uk> ha scritto: > I am trying to make SBo scripts to build crelay > (https://github.com/ondrej1024/crelay) > > The sources come with a pre-made Makefile, which uses the path > /usr/local/bin for the binary. What is the accepted way to change this > using SBo scripts to /usr/bin? Do I make a patch for the Makefile and > apply it during the build? Or is there a better way? Thank you for any > hints > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20221105.1
hi Ruben, are you sure you are using the SBo repository? In the official SBo repository no patch is applied to claws-mail 4.1.1. In the unofficial repository for current instead I applied an additional patch for the newer perl in current since the beginning of july: it was needed for claws-mail version 4.1.0. it seems that this patch made into the upstream code and has been included with the update to 4.1.1 on SBo of a few hours ago so there should be no need of a patch with this version to build claws-mail on current, so I'll just delete my commit the next time I will release a new version of the unofficial repository. but what is really strange is that at the moment, in the unofficial repository for current claws-mail is still at version 4.1.0 (with the patch applied, and it applies cleanly), so it seems like you are not using any of the above repos... Matteo Il giorno lun 7 nov 2022 alle ore 11:25 Ruben Schuller ha scritto: > Hi Erik, hi list, > > I get this message while trying to compile the latest claws-mail update: > > [...] > claws-mail-4.1.1/manual/dtd/sdocbook.dtd > patching file src/plugins/perl/perl_plugin.c > Reversed (or previously applied) patch detected! Assume -R? [n] > > If I answer yes it continues for a while but then fails, with no it > breaks immediately. I think it might just be an old patch? > > Can anyone verify this? I tested it on -15.0 and -current, it breaks on > both for me. > > Cheers > Ruben > > 2022-11-05 Willy Sudiarto Raharjo : > > > Sat Nov 5 14:16:40 UTC 2022 > > academic/DRAMPower: Added (DRAM Power + Energy Estimation for DRAM) > > academic/DRAMsim3: Fix github tarball handling. > > academic/OpenMM: Fix github tarball handling. > > academic/SimEng: Added (cycle-accurate processor simulator) > > academic/elk: Added (Linearized augmented-plane-wave Software). > > academic/nco: Updated for version 5.1.1. > > academic/ngspice: Updated for version 38. > > academic/pgfplots: Added (Tex modules). > > academic/pyCRAC: Fix MD5SUM. > > academic/python2-kiwisolver: Added (Cassowary algorithm) > > academic/python2-scipy: Added (math, science, & engineering py2 lib) > > academic/python3-scipy: Added (py3 math, science, and engineering) > > academic/ramulator: Added (a fast and cycle-accurate DRAM simulator) > > academic/verilog: Fix download url. > > academic/yices2: Added (Satisfiability modulo theories solver). > > audio/google-musicmanager: Removed: Google Play Music is no more. > > audio/milkytracker: Update for version 1.03.00. > > audio/mpdscribble: Updated for version 0.24. > > audio/pasystray: Updated for version 0.8.0. > > audio/schismtracker: Updated for version 20221020. > > desktop/gtk-nodoka-engine: Removed: Retired. > > desktop/i3-gaps: Updated for version 4.21.1. > > development/SQLAlchemy: Updated for version 1.4.42. > > development/berkeley-abc: Added (binary sequential logic circuit) > > development/composer: Updated for version 2.4.4 > > development/dwz: Removed. > > development/ghidra: Updated for version 10.2. > > development/github-cli: Updated for version 2.19.0. > > development/jupyter-ipykernel: Updated for version 6.17.0. > > development/jupyter-nbclassic: Updated for version 0.4.7. > > development/jupyter-nbconvert: Updated for version 7.2.3. > > development/jupyter-notebook: Updated for version 6.5.2. > > development/jupyter-notebook_shim: Update for 0.2.2 > > development/nim: Updated for version 1.6.8, new maintainer. > > development/nodejs: Updated for version 19.0.1. > > development/php-apcu: Updated for version 5.1.22 > > development/python2-cycler: Added (composable cycles in python) > > development/python2-numpy: Added (Py2 extension for sci. computing) > > development/python3-cycler: Updated for version 0.11.0. > > development/python3-matplotlib: Update REQUIRES for python3-numpy. > > development/python3-numpy: Added (scientific computing Py3 exts) > > development/qbsolv: Added (A decomposing solver for QUBO) > > development/reuse-tool: Added (License Compliance Tool) > > development/sbcl: Updated for version 2.2.10. > > development/sbt: Updated for version 1.7.3. > > development/universal-ctags: Updated for version p5.9.20221030.0 > > development/vis: Updated for version 0.8 > > development/vscode-bin: Updated for version 1.73. > > development/yosys: Added (A framework for Verilog RTL synthesis) > > games/RetroArch: Updated for version 1.12.0. > > games/pcsx2: Updated for version 1.7.3526. > > gis/gdal: Updated for version 3.5.3. > > gis/python3-basemap: Updated for version 1.3.5. > > gis/python3-cftime: Fix github tarball handling. > > gis/python3-netcdf4-python: Fix github tarball handling. > > gis/python3-xarray: Updated for version 2022.11.0. > > graphics/birdfont: Updated for version 2.32.3. > > graphics/mtpaint: Fix github tarball handling. > > graphics/vuescan: Updated for version 9.7.95. > > libraries/appstream-glib: Updated for version 0.8.1. > > libraries/aribb25: Fix github tarball handling. > > libraries/confuse: Updated fo
Re: [Slackbuilds-users] Timeshift project
The maintainer should be notified: I'll put him CC Matteo Il giorno mar 25 ott 2022 alle ore 18:10 marav ha scritto: > Hi, > > FYI > > The timeshift project has been archived github and is now part of Linux > MINT > > The last archive tarball can be downloaded at: > > > https://github.com/linuxmint/timeshift/archive/22.06.5/timeshift-22.06.5.tar.gz > > > Cheers > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] python3-babel slackbuild needs update
works fine here: in doubt just use wget to download tarballs and if it doesn't work post wget's output. Matteo Il giorno mar 18 ott 2022 alle ore 17:21 Jude DaShiell ha scritto: > Fetching http://unicode.org/Public/cldr/41/cldr-common-41.0.zip...Failed > > > > Jude > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author, 1940) > > . > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] cryptography.slackbuild
it has already been fixed in our git, it will go in the main repository at the next global update. https://git.slackbuilds.org/slackbuilds/commit/?id=738d53 Il giorno mar 18 ott 2022 alle ore 17:04 Jude DaShiell ha scritto: > Needs an md5sum update, there's a mismatch with the sums for now. > > > > Jude > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author, 1940) > > . > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] BuildScripts up for grabs
Il giorno ven 14 ott 2022 alle ore 14:44 Markus Reichelt via SlackBuilds-users ha scritto: > Markdown: Also, there is the issue of Markdown; it's in stock > Slackware 15.0 by now. Dependees as shown on > > https://slackbuilds.org/advsearch.php?q=Markdown&stype=revdep1 > > should check if stuff works with the stock Slackware Markdown install > instead, and if so, let's remove the SBo legacy script. If not, > SBo's Markdown needs a new maintainer too. > Slackware provides python-markdown that is the python3 module while Markdown on SBo is the python2 version of the module. I had a look and Markdown is listed as used by the following SlackBuilds: - anki - apprise - diskscan - gmusicbrowser - pelican - vmd anki and vmd look python3-based now, so they should be ok with the python-markdown in Slackware (and Markdown should be removed from the dependencies). pelican, being built for python2, actually seems to use it as an optional dependency (but could be also been built for python3, together with his own dependencies, other distro do this). gmusicbrowser lists it between the dependencies but I'm not sure it's used https://aur.archlinux.org/packages/gmusicbrowser apprise needs a depper look by its maintainer because it's a mix of python2 and python3 dependencies at the moment (I doubt it works). the latest diskscan version (0.20) uses just python-PyYAML in Slackware and no other deps. I invite all the interested maintainers to please have a look and submit the needed changes, thanks in advance. Matteo Bernardini ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] mod_wsgi and mod_wsgi-metrics are available
On 04/10/22 12:18, Matteo Bernardini wrote: Hi Adis, sorry for bothering but someone reported that mod_wsgi won't work with python3 and mercurial in slackware 15.0 https://www.linuxquestions.org/questions/slackware-14/slackware-15-0-mod_wsgi-and-mercurial-problem-4175717396/ someone else proposed an update to a newer version that supports python3 and that seems to have fixed the issue. as I saw mod_wsgi has been updated on SBo last time more than 7 years ago I would like to ask if you are still feeling like maintaining it... take care! Matteo On 04/10/22 12:32, Adis Nezirovic wrote: Hi Matteo, I've been away from slackware for a quite while. You can consider all my packages orphaned, so if some brave soul wants to maintain them, all praise to them. Happy Slacking! Best regards, Adis that means, for whoever is interested, that mod_wsgi and mod_wsgi-metrics are up for grabs. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] xcb-imdkit redundant
Hi Linux Lite, the SlackBuilds.org repository is dedicated to the latest Slackware stable, that's 15.0, ATM: this doesn't include xcb-imdkit, only current (the development version, not supported by SBo) does, so xcb-imdkit is still ok here. if you want to report duplicate scripts in current please do it in the dedicated linuxquestions topic that tracks an unofficial fork of the SBo repository (thanks in advance!) https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/ Matteo Il giorno ven 30 set 2022 alle ore 08:50 Linux Lite ha scritto: > Hello, > > xcb-imdkit on SBo[1] was superceded by the official Slackware one. This > should be removed. > > Cheers, > ltlnx > > [1]: https://slackbuilds.org/repository/15.0/misc/xcb-imdkit/ > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Certbot failing + fix
FWIW pytz in the current (unofficial) branch has support for python3 enabled by default since january 2020 so I think the problem is that the repository doesn't update correctly (beside it being stuck on a specific branch). Matteo Il giorno sab 24 set 2022 alle ore 19:20 Slack Coder ha scritto: > Thanks Willy, you're right, the branch being used by two machines I have > is stuck on 'current'. > > Sbotools is unmaintained. It leaves its users now on a branch called > 'current'. I just discovered that the issue has been recently reported > on the project's github page. > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] OT qmake not found
Hi Peter, I might be wrong think Arnaud already gave you the right guess in his first answer Il giorno ven 23 set 2022 alle ore 11:27 Arnaud via SlackBuilds-users < slackbuilds-users@slackbuilds.org> ha scritto: > So either you're not in a full root shell (eg: use "su -", and not just > "su"), Matteo Il giorno sab 24 set 2022 alle ore 08:57 Peter Dambier < pe...@peter-dambier.de> ha scritto: > On Fri, 23 Sep 2022 18:05:08 -0600 > fourtysixandtwo wrote: > > > Hi Peter, > > > > I just tested on a 32bit 15.0 VM and am not seeing the same issue and > > qtmib starts normally as either a regular user or as root. > > > > Have you tried running it with a freshly created user to isolate > > whether it's your user level issue or a system level one? > > > > Cheers > > Hi fourtysixandtwo, > > I was downloading slackbuild, unpacking, downloading source as user and > running the slackbuild as root (su not sudo). > > Changing everything to owner root including my working directory before > running qtmib.SlackBuild fixed it. > > I am SlackBuilding on an external usb disk. May be my pwd is too long. > > /media/Charybdis/Slackware-15.0/SlackBuilds/Network/qtmib > > Cheers > Peter, DL2FBA > > > > > On Fri, Sep 23, 2022 at 11:15 AM Peter Dambier > > wrote: > > > > > On Fri, 23 Sep 2022 11:27:07 +0200 > > > Arnaud via SlackBuilds-users > > > wrote: > > > > > > > > Hello and have a nice weekend dear fellow Slack Builders, > > > > > > > > > > the trouble qtmib complained qmake missing > > > > > > > > > > "wich" finds "qmake" in "/usr/lib/qt5/bin". > > > > > > > > > > In "/usr/bin" I see "qmake-qt5 -> ../lib/qt5/bin/qmake". > > > > > > > > > > After > > > > > > > > > > ln -s /usr/lib/qt5/bin/qmake /usr/bin/qmake > > > > > > > > > > qtmib successfully built and I guess qtmib is not the only one. > > > > > > > > > > Kind regards and sorry for the noise > > > > > Peter Dambier, DL2FBA > > > > > > > > /usr/lib64/qt5/bin should be added to $PATH > > > > by /etc/profile.d/qt5.sh So either you're not in a full root > > > > shell (eg: use "su -", and not just "su"), or something else is > > > > wrong on your end. > > > > > > > > You should have : > > > > $ which qmake > > > > /usr/lib64/qt5/bin/qmake > > > > > > > > Cheers, > > > > > > > > - Yth. > > > > > > > Thankyou Arnaud, > > > > > > I have a 32 bit system but google ... this seems to be a recuring > > > Qt problem, not specific Qt-5 and agnostic of X84, AMD64, ... > > > > > > "which" did find it in the path so "make" and "qmake" might be part > > > of the party as well, automake spoiling the path or something. > > > > > > qt5.sh is there and did its work, adding "$QT5PATH" > > > > > > Google did not mention "qtmib" but others got bitten by a missing > > > "qmake" as well. > > > > > > Cheers > > > Peter Dambier, DL2FBA > > > > > > ___ > > > SlackBuilds-users mailing list > > > SlackBuilds-users@slackbuilds.org > > > 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 > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] [SlackBuilds] plan9port overwrites system defaults (and that isn't documented)
Hi David, not to be polemic and also I'm not a native speaker but you said just "replace" and, IMHO, "replace" means "replace" and the plan9port package doesn't seem to replace anything. as for the precedence plan9port installs a couple of /etc/profile.d files, plan9port.csh and plan9port.sh to let its own man page get loaded (the tools have the same names so there's no other way, short of renaming everything): if you wish to read the manpages of the other packages nstalled in your OS you can, in alternative: - remove the plan9port package - remove those files in /etc/profile.d/ - read the man pages you want specifying before the invocation of man an empty MANPATH variable, like "MANPATH= man whatever" Matteo Il giorno sab 27 ago 2022 alle ore 09:14 David Chmelik < davidnchme...@gmail.com> ha scritto: > I installed Slackware-stable in a chroot and kept standard > /etc/man_db.conf and /etc/profile, including $MANPATH except, made $PS1 > show I'm in chroot, and it still happens; plan9port installs manpages > which replace default system manpages in precedence order: I never said > 'gets installed in /usr/man' (did you actually type 'man mount' and see > default replaced in precedence order?). > > On 8/26/22 11:52 PM, Matteo Bernardini wrote: > > FWIW I tested building it on a freshly installed slackware64-15.0 and > > a freshly installed slackware64-current and from my test nothing gets > > installed in /usr/man neither during the build procedure or in the > > package contents causing overwrites when the package gets installed, > > so I'm, again, not able to reproduce what you are reporting. > > I suggest you, again, to test in a freshly installed environment (with > > even no custom environment variables or aliases) before reporting. > > > > Matteo > > > > Il giorno sab 27 ago 2022 alle ore 08:23 Matteo Bernardini > > mailto:matteo.bernard...@gmail.com>> ha > > scritto: > > > > Hi David, > > > > I'll report this to the maintainer > > > > Matteo > > > > Il giorno sab 27 ago 2022 alle ore 08:12 > <mailto:dchme...@gmail.com>> ha scritto: > > > > I installed plan9port but it replaced defaults of many UNIX-type > > manpages such as util-linux's 'mount'... how do I get those > > back? I > > only wanted to try Plan 9 stuff, not have it replace default > > Slackware > > system/configuration! Please make plan9port not do that > > without user > > consent to options. > > > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] [SlackBuilds] plan9port overwrites system defualts (and that isn't documented)
FWIW I tested building it on a freshly installed slackware64-15.0 and a freshly installed slackware64-current and from my test nothing gets installed in /usr/man neither during the build procedure or in the package contents causing overwrites when the package gets installed, so I'm, again, not able to reproduce what you are reporting. I suggest you, again, to test in a freshly installed environment (with even no custom environment variables or aliases) before reporting. Matteo Il giorno sab 27 ago 2022 alle ore 08:23 Matteo Bernardini < matteo.bernard...@gmail.com> ha scritto: > Hi David, > > I'll report this to the maintainer > > Matteo > > Il giorno sab 27 ago 2022 alle ore 08:12 ha scritto: > >> I installed plan9port but it replaced defaults of many UNIX-type >> manpages such as util-linux's 'mount'... how do I get those back? I >> only wanted to try Plan 9 stuff, not have it replace default Slackware >> system/configuration! Please make plan9port not do that without user >> consent to options. >> ___ >> SlackBuilds-users mailing list >> SlackBuilds-users@slackbuilds.org >> 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] [SlackBuilds] plan9port overwrites system defualts (and that isn't documented)
Hi David, I'll report this to the maintainer Matteo Il giorno sab 27 ago 2022 alle ore 08:12 ha scritto: > I installed plan9port but it replaced defaults of many UNIX-type > manpages such as util-linux's 'mount'... how do I get those back? I > only wanted to try Plan 9 stuff, not have it replace default Slackware > system/configuration! Please make plan9port not do that without user > consent to options. > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Maintain libcurl-gnutls
ok, I'll wait a week to let Edinaldo catch up in case he wishes to maintain it (as apparently is needed by spotify) and then I'll remove it from the repo. Matteo Il giorno ven 19 ago 2022 alle ore 19:42 marav ha scritto: > Le 19/08/2022 à 19:39, Matteo Bernardini a écrit : > > you say here on the list that you don't want to maintain it anymore and if > nobody steps in as a maintainer it get removed from the repository. > > Matteo > > Il giorno ven 19 ago 2022 alle ore 19:23 marav ha > scritto: > >> Le 19/08/2022 à 19:19, Matteo Bernardini a écrit : >> >> I don't use spotify but if libcurl-tls is actually a dependency of the >> newer version it could be easier for him, yes, but ultimately it's his >> call... >> if you instead wish not to maintain it anymore you could also drop it and >> if he needs it for spotify he will have to maintain it (no other things in >> the repository depend on it) or it will be removed from the repository. >> >> Matteo >> >> Il giorno ven 19 ago 2022 alle ore 19:04 marav ha >> scritto: >> >>> Hi, >>> >>> Since E.P. Silva now maintains Spotify, I think it would be better if he >>> also maintained libcurl-gnutls (as a dependency) >>> >>> What do you think about it? >>> >>> Cheers >>> ___ >>> SlackBuilds-users mailing list >>> SlackBuilds-users@slackbuilds.org >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> >>> >> ___ >> SlackBuilds-users mailing >> listSlackBuilds-users@slackbuilds.orghttps://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> Thanks Matteo >> >> I had proposed it in anticipation of maintaining Spotify >> Since it's not the case, I won't keep it >> >> And how exactly do you "drop" a slackbuild? >> ___ >> SlackBuilds-users mailing list >> SlackBuilds-users@slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> > ___ > SlackBuilds-users mailing > listSlackBuilds-users@slackbuilds.orghttps://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > Ok > > I don't want to maintain libcurl-gnutls anymore, if someone wants to take > it over, it is free > > Thanks again Matteo > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Maintain libcurl-gnutls
you say here on the list that you don't want to maintain it anymore and if nobody steps in as a maintainer it get removed from the repository. Matteo Il giorno ven 19 ago 2022 alle ore 19:23 marav ha scritto: > Le 19/08/2022 à 19:19, Matteo Bernardini a écrit : > > I don't use spotify but if libcurl-tls is actually a dependency of the > newer version it could be easier for him, yes, but ultimately it's his > call... > if you instead wish not to maintain it anymore you could also drop it and > if he needs it for spotify he will have to maintain it (no other things in > the repository depend on it) or it will be removed from the repository. > > Matteo > > Il giorno ven 19 ago 2022 alle ore 19:04 marav ha > scritto: > >> Hi, >> >> Since E.P. Silva now maintains Spotify, I think it would be better if he >> also maintained libcurl-gnutls (as a dependency) >> >> What do you think about it? >> >> Cheers >> ___ >> SlackBuilds-users mailing list >> SlackBuilds-users@slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> > ___ > SlackBuilds-users mailing > listSlackBuilds-users@slackbuilds.orghttps://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > Thanks Matteo > > I had proposed it in anticipation of maintaining Spotify > Since it's not the case, I won't keep it > > And how exactly do you "drop" a slackbuild? > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Maintain libcurl-gnutls
I don't use spotify but if libcurl-tls is actually a dependency of the newer version it could be easier for him, yes, but ultimately it's his call... if you instead wish not to maintain it anymore you could also drop it and if he needs it for spotify he will have to maintain it (no other things in the repository depend on it) or it will be removed from the repository. Matteo Il giorno ven 19 ago 2022 alle ore 19:04 marav ha scritto: > Hi, > > Since E.P. Silva now maintains Spotify, I think it would be better if he > also maintained libcurl-gnutls (as a dependency) > > What do you think about it? > > Cheers > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] New policy or poor advice?
Hi David, the case you describe is substantially different: in april 2021 SBo closed submissions and start adapting things to build on current to start getting ready for the soon-to-come 15.0 (rc1 had been already released). When we close submissions, differently from the normal developmrnt cycle, we admins patch everything needed without getting in touch with the single maintainers (accepting patches from maintainers and third parties) because it's not possibile to get in touch with everybody for every script with thousands of scripts to fix moving from one stable release of Slackware to another so the goal is to handle at least the build process for most of them so that at least they can be tested for functionality by the respective maintainers (we also accept patches from them at some point). That's the reason why rogue has been patched in may 2021. Matteo Il ven 3 giu 2022, 12:09 David Chmelik ha scritto: > Someone pushed a patch for previous rogue.tar.gz version on GitHub.com, > which I don't (and won't) even use for my SlackBuilds. I only found out > when sbopkg & sbotools said Rogue was already updated on SBo without me > having updated Rogue. I didn't obscure/anti-spam my email in rogue.info > nor was inactive--in fact was aware of the problem because of testing my > builds on Slackware-current--perhaps people were just catching up after > Slackware 15. I thanked the person for patch but asked them in future > to email first. > > On 6/3/22 1:20 AM, Matteo Bernardini wrote: > > hi David, > > > > could you please detail when and how this happened so we could try to > > give an answer? > > > > Matteo > > > > Il giorno ven 3 giu 2022 alle ore 10:08 David Chmelik > > mailto:davidnchme...@gmail.com>> ha scritto: > > > > It happened to me once also. A patch was needed, but the person who > > submitted it didn't even try to contact me, so didn't know I was also > > updating to newer source code that didn't need the patch. > > > > On 6/3/22 12:59 AM, Matteo Bernardini wrote: > > > hi Chris, > > > > > > I suppose there has been a misunderstanding as nothing changed > > in our > > > general policy. > > > > > > Matteo > > > > > > > > > Il giorno ven 3 giu 2022 alle ore 01:19 Christoph Willing > > > mailto:chris.will...@linux.com> > > <mailto:chris.will...@linux.com <mailto:chris.will...@linux.com>>> > > ha scritto: > > > > > > I just noticed one of the SlackBuilds that I maintain > > sitting in the > > > pending queue even though I'd made no changes. > > > > > > When discussing this with the person who made the > > submission, pointing > > > out the need to first contact the maintainer, they said that: > > > "I've gotten some different advice from one of the > > admins > > > for certain > > > situations" > > > > > > Is this a new policy - that "for certain situations" anyone can > > > arbitrarily submit changes for a SlackBuild? > > > > > > > > > chris > > > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] New policy or poor advice?
hi Chris, I suppose there has been a misunderstanding as nothing changed in our general policy. Matteo Il giorno ven 3 giu 2022 alle ore 01:19 Christoph Willing < chris.will...@linux.com> ha scritto: > I just noticed one of the SlackBuilds that I maintain sitting in the > pending queue even though I'd made no changes. > > When discussing this with the person who made the submission, pointing > out the need to first contact the maintainer, they said that: > "I've gotten some different advice from one of the admins for > certain > situations" > > Is this a new policy - that "for certain situations" anyone can > arbitrarily submit changes for a SlackBuild? > > > chris > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] runc slackbuild failed to build
hi Dimitris, I think you haven't logged out and logged back in from your root session after having installed google-go-lang because from your output it seems you are still using go from gcc. Matteo Il giorno ven 6 mag 2022 alle ore 09:22 Dimitris Zlatanidis < d.zlatani...@gmail.com> ha scritto: > go build -trimpath "-mod=vendor" "-buildmode=pie" -tags "seccomp" > -ldflags "-X main.gitCommit=12644e614e25b05da6fd08a38ffa0cfe1903fdec -X > main.version=1.0.2 " -o runc . > go build: when using gccgo toolchain, please pass linker flags using > -gccgoflags, not -ldflags > # github.com/opencontainers/runc > /usr/bin/ld: $WORK/b001/_pkg1_.a(_cgo_defun.o): relocation R_X86_64_32 > against `.rodata' can not be used when making a PIE object; recompile > with -fPIE > /usr/bin/ld: $WORK/b001/_pkg2_.a(_cgo_defun.o): relocation R_X86_64_32 > against `.rodata' can not be used when making a PIE object; recompile > with -fPIE > /usr/bin/ld: $WORK/b001/_pkg3_.a(_cgo_defun.o): relocation R_X86_64_32 > against `.rodata' can not be used when making a PIE object; recompile > with -fPIE > collect2: error: ld returned 1 exit status > make: *** [Makefile:34: runc] Error 2 > > Anyone who knows? > > Cheers, > Dimitris > > -- > Dimitris Zlatanidis > https://dslackw.gitlab.io/slpkg/ > https://gitlab.com/dslackw > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7
can you send a patch for it so I can test it? Il giorno gio 7 apr 2022 alle ore 04:25 Lenard Spencer < lenardrspen...@gmail.com> ha scritto: > Since openjdk6 and 7 can no longer be built at this time, I would have to > say drop them for now. openjdk8 can be built if you have zulu-openjdk7 > installed and adjust BOOT_JAVA to point to /usr/lib(64)/zulu-openjdk7 in > the script. > > > On Wed, Apr 6, 2022, 10:54 Luc Van Rompaey > wrote: > >> >> >> Op wo 6 apr. 2022 14:49 schreef Habs : >> >>> On Wed, 6 Apr 2022, Luc Van Rompaey wrote: >>> >>> > Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users < >>> > slackbuilds-users@slackbuilds.org>: >>> > >>> > java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 >>> but >>> > got 0xc7a06d31) >>> >>> This looks like you're inadvertently using the wrong set of source >>> files. Each new openjdk version has a new set of source files, many >>> of >>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) >>> so >>> your build system can easily pick up the wrong source file. >>> >>> chris >>> >>> >>> >>> Good morning all >>> >>> >>> >>> I do not doubt the comment above, but in this case, how could it be >>> >> unless >>> >>> the slackbuild source links are out of step/compromised/whatever. >>> >>> >>> >>> As I mentioned, it is a clean physical machine freshly installed and >>> >> then >>> >>> updated - no other [java related or other slackbuild addons etc] >>> >> downloads >>> >>> prior - and simply the source files linked in the slackbuild info. >>> Each >>> >>> slackbuild individually run using 'su -' (rather than using sbotools >>> or >>> >>> similar) as required. I don't even get to try openjdk8 (or download >>> >>> anything for it) as apache-ant, gcc5 and openjdk7 are listed as >>> required >>> >>> first. It is openjdk7 that is failing in that chain as such. >>> >>> >>> >>> That all said, I will go back and check the sources, though I think >>> that >>> >>> has been done by Matteo. >>> >>> >>> >>> Regards >>> >>> Habs >>> >> >>> >> My comment will not add much to the problem, but my several tries are >>> all >>> >> failing at the same place (ie: invalid entry CRC). >>> >> Be it on my master very unclean multilib box, a chroot, multilib or >>> not, >>> >> updated and clean, or some other cleaner boxes, VMs, not multilib, I >>> can't >>> >> make it build, and it always fails on the same place... >>> >> >>> >> But unlike others here, I don't pretend doing it on perfectly clean >>> >> installations (though always without any other java installed). >>> >> Although I am really sure my source packages are the right ones, >>> MD5SUM >>> >> checked and all. >>> >> >>> >> -- >>> >> Arnaud >>> >> >>> >> Let me first tell you all that I have been out of the Slackware loop >>> for a >>> > while and that I'm only just getting ready to install Slackware 15.0 >>> on my >>> > new computer. >>> > Thus, for now, I cannot do any tests involving Slackware myself. >>> > >>> > Anyway, I remember looking into the different Apache Ant releases just >>> > before life interfered, and I was about to try and figure out how the >>> Ant >>> > releases and the (Open)JDK version did and did not go together. I >>> hadn't >>> > gotten far enough to draw any final conclusions, though, and I hadn't >>> taken >>> > any meaningful notes yet. >>> >> ___ >>> >> SlackBuilds-users mailing list >>> >> SlackBuilds-users@slackbuilds.org >>> >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> >> FAQ - https://slackbuilds.org/faq/ >>> > >>> > This ongoing discussion reminded me that I had sent in an update to the >>> > apache-ant slackbuild when I took it over. According to the SlackBuilds >>> > history, it had been at Ant version 1.9.9 until then, and I updated it >>> to >>> > 1.9.14. Now, if I remember correctly, I had successfully compiled >>> OpenJDK 7 >>> > (and subsequently 8) before I took over the apache-ant slackbuild, and >>> I >>> > don't believe that I have ever recompiled them since then. >>> > >>> > Anyway, to cut a long story short, I'm now wondering if, perhaps, the >>> > problem may have anything to do with the Apache Ant version. In other >>> > words, the build fails with Ant 1.9.14, but it may still complete >>> > successfully with Ant 1.9.9. May be worth a try. Then, if that works, >>> I may >>> > attempt a build with the latest Ant 1.9.x revision (currently 1.9.16) >>> and >>> > see what gives. In any case, there's no point in trying the build with >>> Ant >>> > 1.10.x, since that cannot make sense of any Java run-time environment >>> older >>> > than, I think, Java version 8 (and, consequently, the Java environment >>> > provided by gcc5). >>> > >>> > If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 >>> while >>> > I'm getting ready for Slackware 15.0,
Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7
Il giorno mer 6 apr 2022 alle ore 07:25 Matteo Bernardini < matteo.bernard...@gmail.com> ha scritto: > Il giorno mar 5 apr 2022 alle ore 22:39 Christoph Willing < > chris.will...@linux.com> ha scritto: > >> On 6/4/22 06:00, Habs wrote: >> > java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but >> > got 0xc7a06d31) >> >> This looks like you're inadvertently using the wrong set of source >> files. Each new openjdk version has a new set of source files, many of >> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so >> your build system can easily pick up the wrong source file. >> > > could be we are still missing something but unfortunately I tried multiple > times manually to verify I hadn't got anything wrong (I also reinstalled a > vm from scratch) and redownloaded the sources too but still got the same > error. > Lenard, can you try building again openjdk7 (not openjdk8) from scratch > locally and verify that everything is building ok for you? > Note that the environment where you should try this *must* contain the latest updates to slackware 15.0. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7
Il giorno mar 5 apr 2022 alle ore 22:39 Christoph Willing < chris.will...@linux.com> ha scritto: > On 6/4/22 06:00, Habs wrote: > > java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but > > got 0xc7a06d31) > > This looks like you're inadvertently using the wrong set of source > files. Each new openjdk version has a new set of source files, many of > which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so > your build system can easily pick up the wrong source file. > could be we are still missing something but unfortunately I tried multiple times manually to verify I hadn't got anything wrong (I also reinstalled a vm from scratch) and redownloaded the sources too but still got the same error. Lenard, can you try building again openjdk7 (not openjdk8) from scratch locally and verify that everything is building ok for you? Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7
Hi Lenard, please have a look at openjdk7 too: from my test it doesn't build on 64bit. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7
Il giorno lun 4 apr 2022 alle ore 16:29 Lenard Spencer < lenardrspen...@gmail.com> ha scritto: > openjdk8 now also requires gcc5, and will build with zulu-openjdk7 with a > minor script edit (BOOT_JAVA to point to zulu-openjdk7). If the maintainer > approves I can send the patch. > > I also have an SBo script that builds OpenJDK8 without using icedtea, > using zulu-openjdk7 (a repackaged binary). If there is interest I can > submit it. > > > On Mon, Apr 4, 2022, 09:10 Habs wrote: > >> Hello everyone, good day >> >> Slackware 15, clean, fully updated >> >> The build either manually or via sbotools fails at the same place at the >> openjdk7 part. >> >> (part of the buildlog is below up until it bails out). >> >> Is it something I'm doing or something in the slackbuild and associate >> files and is there a quick 'fix' to try please ? >> >> Regards >> Habs >> >> >> >> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf >> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar >> >> -C >> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/ >> >> . >> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf >> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar >> >> -C >> /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes >> META-INF/services/com.sun.jdi.connect.Connector >> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but >> got >> 0xc7a06d31) >> at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413) >> at java.util.zip.ZipInputStream.read(ZipInputStream.java:195) >> at java.io.FilterInputStream.read(FilterInputStream.java:107) >> at sun.tools.jar.Main.copy(Main.java:822) >> at sun.tools.jar.Main.update(Main.java:584) >> at sun.tools.jar.Main.run(Main.java:224) >> at sun.tools.jar.Main.main(Main.java:1231) >> gmake[8]: *** >> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86: >> >> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar] >> >> Error 1 >> gmake[8]: Leaving directory >> >> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product' >> gmake[7]: *** >> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64: >> >> all] Error 2 >> gmake[7]: Leaving directory >> >> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product' >> gmake[6]: *** >> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103: >> >> sa_stuff] Error 2 >> gmake[6]: Leaving directory >> >> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product' >> gmake[5]: *** >> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323: >> product] Error 2 >> gmake[5]: Leaving directory >> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir' >> gmake[4]: *** [Makefile:203: generic_build2] Error 2 >> gmake[4]: Leaving directory >> '/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make' >> gmake[3]: *** [Makefile:158: product] Error 2 >> gmake[3]: Leaving directory >> '/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make' >> gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2 >> gmake[2]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk' >> gmake[1]: *** [Makefile:251: build_product_image] Error 2 >> gmake[1]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk' >> make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2 >> > Hi Lenard, yes, and please have a look at openjdk7 too because here, testing the build locally, I got the same error as Habs: cp /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes/sun/jvm/hotspot/ui/resources/*.png /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/sun/jvm/hotspot/ui/resources/ cp -r /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes/images/* /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/ /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar -C /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/ . /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar -C /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/ope
Re: [Slackbuilds-users] make -j${NUMJOBS} discussion
Il giorno dom 3 apr 2022 alle ore 20:59 Slackbuilds
ha scritto:
> Most of my testing for submission is in a VM (either 2, 4 or 6 cores,
> depending on how many I fire up on the Ryzen 9). Settings MAKEFLAGS
> will hide NUMJOBS and is not appropriate since it obscures what was
> used. My VMs may not have the expected cores. It's better to have this
> available to explicitly set in the script as needed. Having
> NUMJOBS=${NUMJOBS:-1} as the default provides a suitable fallback.
>
like netrixtrardis wrote you can use a dynamic setting also for MAKEFLAGS:
on my systems I have
export MAKEFLAGS=${MAKEFLAGS:--j$(expr $(nproc) + 1)}
this way you can use it on every machine regardless of their resources.
Il giorno dom 3 apr 2022 alle ore 21:19 Ozan Türkyılmaz <
ozan.turkyil...@gmail.com> ha scritto:
> Don't do that. MAKEFLAGS is for passing command line arguments to
> submake processes [1]. I dont know if MAKEFLAGS="-j2" sh configure
> would do any problem or even make would get it.
>
> Regards,
> Ozan
>
> [1] There's some long talk abut it
> here:
> https://www.gnu.org/software/make/manual/html_node/Options_002fRecursion.html
> Also here: https://stackoverflow.com/a/19622824/7247759
>
Hi Ozan,
the first link you cite contains a couple of paragraphs that say that is
perfectly legit to use MAKEFLAGS to set parallel make jobs, the second
discussion on stackoverflow is only about the opportunity to set MAKEFLAGS
inside a Makefile.
Matteo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Name clash
Robby removed it ;-) Il lun 28 mar 2022, 12:31 Willy Sudiarto Raharjo ha scritto: > > Since I maintain the existing SlackBuild dcmtk and I didn't submit a > > change, I presume the dcmtk.tar.gz in the pending queue is a new > > submission (which would result in a name clash). > > > > BTW I'm not sure if this is actually a rule, but we generally don't top > > post in this list. > > I don't see any dcmtk in pending (https://slackbuilds.org/pending/) nor > in ready (https://slackbuilds.org/ready/) > > > -- > Willy Sudiarto Raharjo > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updated ftbfs list
Il giorno dom 27 mar 2022 alle ore 20:07 Jeremy Hansen < jebrhansen+...@gmail.com> ha scritto: > Where do you go to find how Debian builds its packages? I know about the > AUR for Arch and Gentoo's gitweb. > there's also https://sources.debian.org there search for handbrake, click on the package name, then on the latest version (usually sid is ok) and then on the "debian folder" with the build stuff. there you will have the "rules" file with the build rules and the "patches" folder with the patches used (there's also usually a "series" file with the patching order). Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] fcron for 15.0
Il giorno ven 25 mar 2022 alle ore 18:33 mab974 ha scritto: > Selon mab974 : > > Selon Richard Narron : > > > On Tue, 22 Mar 2022, Michel BEGUE wrote: > > > > > > > fcron does not build. > > > > just a line to add to ./configure > > > > " --with-sendmail=/usr/sbin/postfix " > > > > > > I do not get any errors in building 3.3.0 > > > > > > With postfix installed, the fcron 3.3.0 build finds sendmail at > > > /usr/sbin/sendmail. > > > > > > What error did you get building fcron 3.3.0? > > > > > > > and maybe get to v3.3.1. > > > > > > This is a good idea. I am waiting to be able to update my > scripts... > > > > > > Richard Narron > > > > Sorry, I’m trying to find the exact build conditions. > > I’m not near my computer right now. > > > > Michel > > Sorry. > I have run 'sudo ./fcron.SlackBuild' and postfix is not accessible. > 'su -c ./fcron.SlackBuild' is better. > > my apologies to Richard and Dave. > > Michel > -*- > Hi Michel, please have a look at the HOWTO https://slackbuilds.org/howto/ the last paragraph of "Step 4" in particular Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] qemu build issue
well, to be fair that shouldn't actually be a problem in a Slackware stable setup because libraries' versions should be the same... that should only happens when you are using current or upgrading between Slackware versions (but in that case many other things could happen). Matteo Il giorno lun 21 mar 2022 alle ore 13:48 Tim Dickson via SlackBuilds-users < slackbuilds-users@slackbuilds.org> ha scritto: > thanks Matteo, that did the trick. It looks like part of the build process > uses already created binaries to process files, and when older binaries are > already in the path they are used instead, giving the error. > > It may be worth adding a comment to remove existing version of qemu before > installing a newer one into the README. > > regards, Tim > > On 20/03/2022 18:31, Matteo Bernardini wrote: > > have you tried removing the already installed qemu package first? > > Il giorno dom 20 mar 2022 alle ore 19:29 Tim Dickson via SlackBuilds-users > ha scritto: > >> I am getting the following error when attempting to create qemu package. >> >> /usr/bin/qemu-keymap: error while loading shared libraries: >> libjemalloc.so.1: cannot open shared object file: No such file or >> directory >> >> /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there >> is a libjemalloc installed (part of slackware 15.0). >> It seems that the build script is looking for the wrong version of the >> lib. Ideally it would try libjemalloc.so and thus pick up whichever >> version was installed. >> Is there a quick fix. (if it involves a sim-link would that have to be >> done on target computers as well?) >> regards, Tim >> > > ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] qemu build issue
have you tried removing the already installed qemu package first? Il giorno dom 20 mar 2022 alle ore 19:29 Tim Dickson via SlackBuilds-users < slackbuilds-users@slackbuilds.org> ha scritto: > I am getting the following error when attempting to create qemu package. > > /usr/bin/qemu-keymap: error while loading shared libraries: > libjemalloc.so.1: cannot open shared object file: No such file or directory > > /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there > is a libjemalloc installed (part of slackware 15.0). > It seems that the build script is looking for the wrong version of the > lib. Ideally it would try libjemalloc.so and thus pick up whichever > version was installed. > Is there a quick fix. (if it involves a sim-link would that have to be > done on target computers as well?) > regards, Tim > > > -- > This email has been checked for viruses by AVG. > https://www.avg.com > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] numpy builds w/problems
before reporting issues you should build the problematic packages from
scratch, together with all their dependencies, on a clean and full
installation (no other third party packages or customizations): I suggest
you to use virtual machines for the task (that's what most people do).
Matteo
Il giorno dom 20 mar 2022 alle ore 09:07 David Chmelik
ha scritto:
> Apparently; I reinstalled saved packages: now mathics 4 works on
> Slackware64 15.1+current w/earlier numpy & OpenBLAS. However beforehand
> I removed numpy3 and now was trying to rebuild because no longer could:
> something else happens with that which I'm waiting on another attempt to
> save output to a TXT...
>
> On 3/20/22 12:51 AM, Matteo Bernardini wrote:
> > maybe you just built numpy3 against OpenBLAS and then removed OpenBLAS
> > from your system?
> >
> > Matteo
> >
> > Il giorno dom 20 mar 2022 alle ore 08:47 David Chmelik
> > mailto:dchme...@gmail.com>> ha scritto:
> >
> > Some days/weeks ago I mentioned a build not working on Slackware64
> > 15.1+current and Urchlay said we're not worrying about SBo-git
> > until 15
> > is ready (ready now except submissions I guess) so I resorted to
> > report
> > another SBo-git problem on LinuxQuestions.com (LQ) then ponce said
> > post
> > here...
> > Built numpy3-1.21.2-x86_64-1ponce but some/most/all packages
> > depending on it don't build right. One I maintain, mathics.SlackBuild
> > (updated for Slackware 15 at
> > http://davidchmelik.com/math/slackbuilds/academic/mathics.tar.gz
> > <http://davidchmelik.com/math/slackbuilds/academic/mathics.tar.gz>
> > but not
> > updated on SBo[-git] yet) which I reported on
> > http://GitHub.com/mathics <http://GitHub.com/mathics>
> > who said I have a broken numpy... despite that built, something went
> > wrong. I don't recall what others didn't build but don't need any
> > these
> > urgently unless anyone needs Slackware-current Mathics 4...
> > Mathics 4 builds but crashes on run...
> >
> > d@cosmos:~$ mathics
> > Traceback (most recent call last):
> >File "/usr/lib64/python3.9/site-packages/numpy/core/__init__.py",
> > line 22, in
> > from . import multiarray
> >File
> > "/usr/lib64/python3.9/site-packages/numpy/core/multiarray.py",
> > line 12, in
> > from . import overrides
> >File "/usr/lib64/python3.9/site-packages/numpy/core/overrides.py",
> > line 7, in
> > from numpy.core._multiarray_umath import (
> > ImportError: libopenblas.so.0: cannot open shared object file: No
> > such
> > file or directory
> >
> > During handling of the above exception, another exception occurred:
> >
> > Traceback (most recent call last):
> >File "/usr/bin/mathics", line 33, in
> > sys.exit(load_entry_point('Mathics3==4.0.0', 'console_scripts',
> > 'mathics')())
> >File "/usr/bin/mathics", line 25, in importlib_load_entry_point
> > return next(matches).load()
> >File "/usr/lib64/python3.9/importlib/metadata.py", line 77, in
> load
> > module = import_module(match.group('module'))
> >File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in
> > import_module
> > return _bootstrap._gcd_import(name[level:], package, level)
> >File "", line 1030, in _gcd_import
> >File "", line 1007, in _find_and_load
> >File "", line 972, in
> > _find_and_load_unlocked
> >File "", line 228, in
> > _call_with_frames_removed
> >File "", line 1030, in _gcd_import
> >File "", line 1007, in _find_and_load
> >File "", line 986, in
> > _find_and_load_unlocked
> >File "", line 680, in _load_unlocked
> >File "", line 850, in
> > exec_module
> >File "", line 228, in
> > _call_with_frames_removed
> >File "/usr/lib64/python3.9/site-packages/mathics/__init__.py",
> > line
> > 8, in
> > import numpy
> >File "/usr/lib64/python3.9/site-packages/numpy/__init__.py", line
> > 150, in
> > from . import core
>
Re: [Slackbuilds-users] numpy builds w/problems
maybe you just built numpy3 against OpenBLAS and then removed OpenBLAS from
your system?
Matteo
Il giorno dom 20 mar 2022 alle ore 08:47 David Chmelik
ha scritto:
> Some days/weeks ago I mentioned a build not working on Slackware64
> 15.1+current and Urchlay said we're not worrying about SBo-git until 15
> is ready (ready now except submissions I guess) so I resorted to report
> another SBo-git problem on LinuxQuestions.com (LQ) then ponce said post
> here...
> Built numpy3-1.21.2-x86_64-1ponce but some/most/all packages
> depending on it don't build right. One I maintain, mathics.SlackBuild
> (updated for Slackware 15 at
> http://davidchmelik.com/math/slackbuilds/academic/mathics.tar.gz but not
> updated on SBo[-git] yet) which I reported on http://GitHub.com/mathics
> who said I have a broken numpy... despite that built, something went
> wrong. I don't recall what others didn't build but don't need any these
> urgently unless anyone needs Slackware-current Mathics 4...
> Mathics 4 builds but crashes on run...
>
> d@cosmos:~$ mathics
> Traceback (most recent call last):
>File "/usr/lib64/python3.9/site-packages/numpy/core/__init__.py",
> line 22, in
> from . import multiarray
>File "/usr/lib64/python3.9/site-packages/numpy/core/multiarray.py",
> line 12, in
> from . import overrides
>File "/usr/lib64/python3.9/site-packages/numpy/core/overrides.py",
> line 7, in
> from numpy.core._multiarray_umath import (
> ImportError: libopenblas.so.0: cannot open shared object file: No such
> file or directory
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>File "/usr/bin/mathics", line 33, in
> sys.exit(load_entry_point('Mathics3==4.0.0', 'console_scripts',
> 'mathics')())
>File "/usr/bin/mathics", line 25, in importlib_load_entry_point
> return next(matches).load()
>File "/usr/lib64/python3.9/importlib/metadata.py", line 77, in load
> module = import_module(match.group('module'))
>File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in
> import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>File "", line 1030, in _gcd_import
>File "", line 1007, in _find_and_load
>File "", line 972, in
> _find_and_load_unlocked
>File "", line 228, in
> _call_with_frames_removed
>File "", line 1030, in _gcd_import
>File "", line 1007, in _find_and_load
>File "", line 986, in
> _find_and_load_unlocked
>File "", line 680, in _load_unlocked
>File "", line 850, in exec_module
>File "", line 228, in
> _call_with_frames_removed
>File "/usr/lib64/python3.9/site-packages/mathics/__init__.py", line
> 8, in
> import numpy
>File "/usr/lib64/python3.9/site-packages/numpy/__init__.py", line
> 150, in
> from . import core
>File "/usr/lib64/python3.9/site-packages/numpy/core/__init__.py",
> line 48, in
> raise ImportError(msg)
> ImportError:
>
> IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
>
> Importing the numpy C-extensions failed. This error can happen for
> many reasons, often due to issues with your setup or how NumPy was
> installed.
>
> We have compiled some common reasons and troubleshooting tips at:
>
> https://numpy.org/devdocs/user/troubleshooting-importerror.html
>
> Please note and check the following:
>
>* The Python version is: Python3.9 from "/usr/bin/python3"
>* The NumPy version is: "1.21.2"
>
> and make sure that they are the versions you expect.
> Please carefully study the documentation linked above for further help.
>
> Original error was: libopenblas.so.0: cannot open shared object file: No
> such file or directory
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> 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
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Mathics 4 SlackBuild out
New SlackBuilds must go through the submissions form once submissions will reopen... Matteo Il sab 19 mar 2022, 12:48 David Neil Chmelik ha scritto: > On Sat, 19 Mar 2022 04:35:28 -0700, David Chmelik wrote: > > > Mathics 4 SlackBuilds is out (can add to SBo-git: ) > > http://davidchmelik.com/slackbuilds/academic/mathics.tar.gz > > Oops; https://davidchmelik.com/math/slackbuilds/academic/mathics.tar.gz > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20220317.1
Hi Qun-Ying, actually stuff in /extra, not being part of a Slackware full installation, is provided also here if being a dependency of something else: this is the case, for example, for fltk or the various java implementations... Matteo Il giorno ven 18 mar 2022 alle ore 20:21 Qun-Ying ha scritto: > Hi, > > fltk is provided from extra in official release, should be removed > from SlackBuild. > ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] lxml SlackBuild needs to be newer version
just be sure that the newer lxml doesn't break anything depending on lxml... Matteo Il giorno lun 7 mar 2022 alle ore 01:06 Duncan Roe ha scritto: > > Hi Larry, > > Your lxml SB is the only one left in the repo for which Type1_to_OTF needs a > newer version. > > Would it be OK with you if I pushed a rev bump? > > Cheers ... Duncan. > > On Sun, Feb 27, 2022 at 12:24:37PM +1100, Duncan Roe wrote: > > On Sun, Feb 27, 2022 at 12:15:27PM +1100, Duncan Roe wrote: > > > Hi Larry, > > > > > > lxml SB is at version 4.6.3 but PyPi has 4.8.0. > > > > > > afdko (that I maintain) requires at least 4.7.1. > > > > > > For now, I built afdko using pip2tgz to get an up-to-date lxml, > > > but could you update your SB please? > > > > Some clarification: lxml is a *runtime* dependency of afdko. afdko *builds* > > w/out lxml. > > > > Type1_to_OTF uses afdko to build: I should have posted "I built Type1_to_OTF > > using pip2tgz to get an up-to-date lxml". > > > > Cheers ... Duncan. > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] New Templates and 15.0 Repository Progress
I agree with Erich considerations: just follow Pat's instructions and
don't remove *.la files outside of LD_LIBRARY_PATH.
Matteo
Il giorno dom 6 mar 2022 alle ore 03:24 Erich Ritz via
SlackBuilds-users ha scritto:
>
> --- Original Message ---
>
> On Saturday, March 5th, 2022 at 7:36 PM, Willy Sudiarto Raharjo
> wrote:
>
> > > According to the new templates, .la files are not included
> > > in the package to be built as follows:
> > >
> > > # Don't ship .la files:
> > > rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la
> > >
> > > But some packages (for example geany) put .la files in subfolders too,
> > > say as
> > >
> > > /usr/lib${LIBDIRSUFFIX}/$PRGNAM/*.la
> > >
> > > Are maintainers supposed to make sure that these are omitted as
> > > well?
> >
> > Yes please
> >
> > --
> >
> > Willy Sudiarto Raharjo
> >
>
> Doesn't it depend? From the Slackware ChangeLog entry from Thu Apr 19 2018:
>
> > The .la files that are outside of
> > the LD_LIBRARY_PATH were not removed (and shouldn't be) - those ones are
> > often used by the lt_dlopen() function to load plugins and removing those
> > ones can break things. But those ones don't cause problems... they aren't
> > likely to try to infect .la files produced by other packages.
>
> And on 64-bit Slackware 15.0 the contents of /etc/ld.so.conf are:
>
> include /etc/ld.so.conf.d/*.conf
> /lib64
> /usr/lib64
> /usr/local/lib64
> /usr/x86_64-slackware-linux/lib64
>
> So if I understand correctly there should be no .la files in those
> directories. But /usr/lib${LIBDIRSUFFIX}/$PRGNAM/*.la may very well be
> necessary for a program to operate correctly, and won't adversely affect the
> system. In fact several stock Slackware packages contain these files (do a
> "find /usr/lib64 -name "*.la" to see them).
>
> On the other hand, there are a few offending SBo packages in /usr/lib64 on my
> system (apologies if any of these have been fixed recently):
>
> # ls -l /usr/lib64/*.la
> -rwxr-xr-x 1 root root 1172 Feb 16 08:08 /usr/lib64/libflatpak.la*
> (flatpak-1.10.2-x86_64-2_SBo)
> -rwxr-xr-x 1 root root 980 Mar 3 12:10 /usr/lib64/libgeotiff.la*
> (libgeotiff-1.5.1-x86_64-1_SBo)
> -rwxr-xr-x 1 root root 910 Feb 7 10:46 /usr/lib64/libglpk.la*
> (glpk-4.61-x86_64-1_SBo)
> -rwxr-xr-x 1 root root 916 Feb 7 12:16 /usr/lib64/liblaszip.la*
> (laszip-2.2.0-x86_64-1_SBo)
>
> Erich
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> 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
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
