From willysr at slackbuilds.org Sat Apr 1 02:32:51 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 1 Apr 2023 09:32:51 +0700 Subject: [Slackbuilds-users] Updates - 20230401.1 Message-ID: This is not an April Fool Prank :) Sat Apr 1 02:16:01 UTC 2023 academic/R: Updated for version 4.2.3 + fix build with curl 8. academic/gaw3: Updated for version 20220315. academic/gcompris-qt: Updated for version 3.2. academic/plus42: Updated for version 1.0.16. academic/root: Updated for version 6.28.02. academic/zotero: Updated for version 6.0.23. accessibility/blugon: Added (simple Blue Light Filter for X) audio/JDSP4Linux: Updated for version 2.4. audio/cubeb: Updated for version 0.2.1572. audio/qpwgraph: Updated for version 0.4.1. desktop/BlockstreamGreen: Updated for version 1.1.8. desktop/dunst: Updated for version 1.9.1. desktop/rss-guard: Updated for version 4.3.3. desktop/xfce4-mailwatch-plugin: Update EMAIL. development/Catch2: Added (Unit testing framework for C++) development/Catch: Updated for version 2.13.10. New maintainer. development/PhpStorm: Updated for version 2022.3.3. development/dpkg: Updated for version 1.21.21. development/dynarmic: Updated for version 6.4.5. development/eclipse-cpp: Updated for version 4.27. development/eclipse-java: Updated for version 4.27. development/eclipse-jee: Updated for version 4.27. development/eclipse-php: Updated for version 4.27. development/github-cli: Updated for version 2.24.3. development/jupyter-ipykernel: Updated for version 6.22.0. development/jupyter-nbconvert: Updated for version 7.2.10. development/jupyter-nbformat: Updated for version 5.8.0. development/jupyter_core: Updated for version 5.3.0. development/jupyter_server: Updated for version 2.5.0. development/kForth-32: Fix /etc/profile.d/ file. development/kForth-64: Fix /etc/profile.d file. development/mle: Added (flexible terminal-based text editor) development/mongodb-compass: Updated for version 1.36.2. development/mono: Updated for version 6.12.0.182. New maintainer. development/pycharm: Updated for version 2023.1.231.8109.197. development/rizin: Updated for version 0.5.2. development/rstudio-desktop: Updated for version 2023.03.0+386. development/terraform: Updated for version 1.4.2. development/universal-ctags: Updated for version p6.0.20230326.0 development/vscode-bin: Updated for version 1.77. games/ags: Updated for version 3.5.1.27. games/boosteroid: Added (Boosteroid Cloud Gaming Platform) games/dolphin-emu: Updated for version 5.0.19115. games/duckstation: Updated for version 0.1.6051. games/frotz: Fix md5sum. games/lbreakouthd: Updated for version 1.1.2. games/lgogdownloader: Updated for version 3.11. games/mesen-x: Updated for version 0.9.9.3363. games/rpcs3: Updated for version 0.0.27. games/warzone2100: Updated for version 4.3.4. games/xemu: Updated for version 0.7.86. Remove static license. graphics/Blender: Adapt for -current graphics/brlcad: Updated MD5SUM. graphics/gallery-dl: Moved to network. graphics/vuecan: Updated MD5SUMs. graphics/vuescan: Updated MD5SUMs. libraries/cpp-httplib: Updated for version 0.12.2. libraries/double-conversion: Updated for v 3.2.1. New maintainer. libraries/exiftool: Updated for version 12.59. libraries/fast_float: Updated for version 3.11.0. libraries/flatbuffers: Updated for version 23.3.3. libraries/imgui: Updated for version 1.89.4. libraries/libcurl-gnutls: Updated for version 8.0.1. libraries/libgdiplus: Updated for version 6.1. New maintainer. libraries/libheif: Updated for version 1.15.2. libraries/libmediainfo: Updated for version 23.03. libraries/libtraceevent: Added (Linux kernel trace event library) libraries/qt-avif-image-plugin: Added (Qt plug-in for AVIF) libraries/qt-heif-image-plugin: Added (Qt plug-in for HEIF/HEIC) libraries/qt-jpegxl-image-plugin: Added (Qt plug-in for JPEG XL/JXL) libraries/qt6: Updated for version 6.4.3. libraries/tclsoap: Added (SOAP client/server for Tcl) libraries/tclxml: Added (XML support for Tcl) libraries/webkit2gtk4.1: Fix build. libraries/webkit2gtk: Fix build. libraries/xbyak: Updated for version 6.69.1. misc/bitwarden-desktop: Updated for version 2023.3.1. multimedia/ccextractor: Switch to cmake. multimedia/gtick: Updated for version 0.5.5. multimedia/inputstream.adaptive: Updated for version 20.3.5. multimedia/jellyfin-media-player: Updated for version 1.9.0. multimedia/kodi: Updated for version 20.1. multimedia/makemkv: Updated for version 1.17.3. New maintainer. multimedia/mediainfo: Updated for version 23.03. multimedia/spotify: Updated for version 1.2.8.923. multimedia/strawberry: Updated for version 1.0.17. network/MEGAcmd: Updated for version 1.6.1. network/brave-browser: Updated for version 1.49.128. network/element-desktop: Updated for version 1.11.26. network/gallery-dl: Updated for version 1.25.1. network/haproxy: Updated for version 2.7.5. network/ngrok: Updated for version 3.2.1. network/phodav: Add the dependency libsoup3. network/prosody-mod-vcard-muc: Updated for version hg5290. network/protonmail-bridge: Updated for version 3.0.21. network/qutebrowser: Change licence. Change perms on README.md. network/rclone: Updated for version 1.62.2. network/rspamd: Updated for version 3.5. network/signal-desktop: Updated for version 6.11.0. network/sslscan: Bump bundled openssl version. network/teamviewer: Updated for version 15.40.8. network/transgui: Fix duplicate object status error. network/vivaldi: Updated for version 5.7.2921.65. network/whalebird: Updated for version 5.0.2, binary repackaging. network/zoom-linux: Updated for version 5.14.0.1720. office/LibreOffice: Updated for version 7.5.2.2 office/antiword: Update DOWNLOAD. office/homebank: Updated for version 5.6.3. office/libreoffice-helppack: Updated for version 7.5.2. office/libreoffice-langpack: Updated for version 7.5.2. office/libreoffice: Updated for version 7.5.2. perl/perl-Glib-Object-Introspection: Updated for version 0.050. perl/perl-Math-BigInt: Updated for version 1.999838. ARCH=noarch. perl/perl-Schedule-Cron: Updated for version 1.05. python/cairocffi: Update README and Homepage. python/certbot-dns-cloudflare: Updated for version 2.4.0. python/ipython: Updated for version 8.12.0. python/python3-aiofiles: Updated for version 23.1.0. python/python3-boto3: Added (Python API for AWS) python/python3-comm: Updated for version 0.1.3. python/python3-gensim: Added (Topic Modelling in Python) python/python3-json5: Updated for version 0.9.13. python/python3-jsonlines: Updated dependencies. python/python3-regex: Updated for version 2023.3.22. python/python3-regex: Updated for version 2023.3.23. python/python3-smart_open: Added (utils for streaming large files) python/python3-tomlkit: Updated for version 0.11.7. python/python3-watchdog: Updated for version 3.0.0. python/python3-webcolors: Update README. system/Iosevka-aile: Updated for version 21.1.1. system/Iosevka-etoile: Updated for version 21.1.1. system/arqiver: Updated for version 0.11.0. system/bat: Updated for version 0.23.0. system/bbf: Added (bad block finder) system/chronograf: Updated for version 1.10.1. system/dosbox-dev: Updated for version 0.75_pre4482. system/fish: Updated for version 3.6.1. New maintainer. system/hyperfine: Updated for version 1.16.1. system/lolcat: Updated for version 1.4. system/osquery-bin: Updated for version 5.8.1. system/pgbadger: Updated for version 12.1. system/prometheus: Updated for version 2.43.0. system/redis-py: Updated for version 4.5.3. system/redis-py: Updated for version 4.5.4. system/redis: Updated for version 7.0.10. system/sarasa-gothic: Updated for version 0.40.4. system/sbo-maintainer-tools: Updated for version 0.7.0. system/slackroll: Updated for version v51. system/telegraf: Updated for version 1.26.0. system/wine: Revert back to stable 7.0.2. system/yabsm: Added (yet another btrfs snapshot manager) +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From didier at slint.fr Sat Apr 1 08:10:25 2023 From: didier at slint.fr (Didier Spaier) Date: Sat, 1 Apr 2023 10:10:25 +0200 Subject: [Slackbuilds-users] Updates - 20230401.1 In-Reply-To: References: Message-ID: <1bd9797c-170f-707a-101c-aafe54ba7e7d@slint.fr> Hello, Le 01/04/2023 ? 04:32, Willy Sudiarto Raharjo a ?crit?: > system/yabsm: Added (yet another btrfs snapshot manager) Maybe there will also be a volunteer to write a SlackBuild absm ;) https://github.com/DidierSpaier/absm Cheers, Didier From droidbittin at gmail.com Sat Apr 1 08:38:01 2023 From: droidbittin at gmail.com (Luna Jernberg) Date: Sat, 1 Apr 2023 10:38:01 +0200 Subject: [Slackbuilds-users] Fwd: [Fish-users] fish 3.6.1 released In-Reply-To: References: <8672f8da-3bf6-6572-f17a-cdf68ab9d156@slackware.uk> Message-ID: Not a joke but the latest fish is now Slackbuilded for Slackware 15 and current: https://slackbuilds.org/repository/15.0/system/fish/ https://git.slackbuilds.org/slackbuilds/commit/system/fish?h=15.0&id=bf2e135cd95a09201732889c065410a760f49e6c On 3/26/23, Luna Jernberg wrote: > Attaching an updated working Slackbuild package :) > > Might need some of you more advance Slackbuilders to mentor me, for > bigger changes however and read the Wiki pages that Dave linked me > (will take care of that when i have more energy having a cold at the > moment, but this one works for me on current and should work on 15.0 i > hope > > On 3/25/23, B. Watson wrote: >> >> >> On Sat, 25 Mar 2023, Luna Jernberg wrote: >> >>> Alright, have to learn more about how Slackbuilds work but maybe i >>> will after that, not exactly sure how doinst.sh scripts and all works >>> yet, should think about it, or maybe someone else thats more >>> experienced and have time can take it over? >> >> Actually, I just tried building fish-3.6.1 with the existing >> SlackBuild (with 'export VERSION=3.6.1' in the environment) and it >> builds fine and seems to create a working package. >> >> So if you're considering taking over this build, it should be a >> minimal amount of work for you: you'd just update VERSION and BUILD in >> the script, and VERSION, DOWNLOAD, MD5SUM in the .info file. >> >> After doing that, you'd want to actually install and run the new >> version of fish and make sure it works correctly. I don't use fish, >> so I don't know all of what constitures "correctly"... but it at least >> seems to give me a shell where I can type commands, and "help" brings >> up a browser (which was highly unexpected by me, I thought it'd just >> print some information to the terminal, like bash does). So it passes >> at least 'basic functionality' tests. >> > From fellype at gmail.com Sat Apr 1 13:11:35 2023 From: fellype at gmail.com (Fellype) Date: Sat, 1 Apr 2023 10:11:35 -0300 Subject: [Slackbuilds-users] Some abandoned SlackBuilds In-Reply-To: References: Message-ID: > abntex > > I guess abntex can be removed since it is part of texlive-extra as abntex2. Unless someone is still using tetex in Slackware 15.0 :) Cheers, Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: From fellype at gmail.com Sat Apr 1 19:14:58 2023 From: fellype at gmail.com (Fellype) Date: Sat, 1 Apr 2023 16:14:58 -0300 Subject: [Slackbuilds-users] Updates - 20230401.1 In-Reply-To: References: Message-ID: multimedia/strawberry: Updated for version 1.0.17. > I've got wrong md5sum for strawberry: For the file downloaded from https://files.strawberrymusicplayer.org/strawberry-1.0.17.tar.xz fellype at plasma:~$ md5sum strawberry-1.0.17.tar.xz 1af7513c187e3055163076207fc878d1 strawberry-1.0.17.tar.xz from strawberry.info: fellype at plasma:~$ less /usr/sbo/repo/multimedia/strawberry/strawberry.info | grep MD5 MD5SUM="d7cb3bab452e594824989527736b249f" Regards, Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Sat Apr 1 19:59:07 2023 From: dave at slackbuilds.org (Dave) Date: Sat, 1 Apr 2023 20:59:07 +0100 Subject: [Slackbuilds-users] Updates - 20230401.1 In-Reply-To: References: Message-ID: 01/04/23 16:14, Fellype : > multimedia/strawberry: Updated for version 1.0.17. > > > > I've got wrong md5sum for strawberry: > > For the file downloaded from > https://files.strawberrymusicplayer.org/strawberry-1.0.17.tar.xz > fellype at plasma:~$ md5sum strawberry-1.0.17.tar.xz > 1af7513c187e3055163076207fc878d1 strawberry-1.0.17.tar.xz > > from strawberry.info: > fellype at plasma:~$ less /usr/sbo/repo/multimedia/strawberry/strawberry.info > | grep MD5 > MD5SUM="d7cb3bab452e594824989527736b249f" Thanks. Fixed in my branch and also emailed maintainer. Dave From didier at slint.fr Sat Apr 1 20:12:29 2023 From: didier at slint.fr (Didier Spaier) Date: Sat, 1 Apr 2023 22:12:29 +0200 Subject: [Slackbuilds-users] fim, wrong md5sum Message-ID: Hi, in fim.info: MD5SUM="96492d5c53f806ebdf6d624e73360bdd" But: md5sum fim-0.6-trunk.tar.gz gives: 116d513030ef26cd4dff9aada2bea77a Also, In the .info: DOWNLOAD="http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz" However the link works with the https so I suggest indtead: DOWNLOAD="https://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz" Cheers, Didier From didier at slint.fr Sat Apr 1 20:22:34 2023 From: didier at slint.fr (Didier Spaier) Date: Sat, 1 Apr 2023 22:22:34 +0200 Subject: [Slackbuilds-users] fim, wrong md5sum In-Reply-To: References: Message-ID: <25db2770-528a-1b94-07fb-fa7d2d2c522c@slint.fr> Now that I do wget http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz md5sum fim-0.6-trunk.tar.gz > a rm fim-0.6-trunk.tar.gz wget http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz md5sum fim-0.6-trunk.tar.gz > a I get: cat a 05398df089bcc847e2995db121fa98df fim-0.6-trunk.tar.gz cat b 116d513030ef26cd4dff9aada2bea77a fim-0.6-trunk.tar.gz Is this an issue on my end ??? Didier Le 01/04/2023 ? 22:12, Didier Spaier a ?crit?: > Hi, > > in fim.info: > MD5SUM="96492d5c53f806ebdf6d624e73360bdd" > But: > md5sum fim-0.6-trunk.tar.gz gives: > 116d513030ef26cd4dff9aada2bea77a > > Also, In the .info: > DOWNLOAD="http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz" > However the link works with the https so I suggest indtead: > DOWNLOAD="https://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz" > > Cheers, > Didier From dave at slackbuilds.org Sat Apr 1 20:26:02 2023 From: dave at slackbuilds.org (Dave) Date: Sat, 1 Apr 2023 21:26:02 +0100 Subject: [Slackbuilds-users] fim, wrong md5sum In-Reply-To: <25db2770-528a-1b94-07fb-fa7d2d2c522c@slint.fr> References: <25db2770-528a-1b94-07fb-fa7d2d2c522c@slint.fr> Message-ID: 01/04/23 22:22, Didier Spaier : > Now that I do > wget http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz > md5sum fim-0.6-trunk.tar.gz > a > rm fim-0.6-trunk.tar.gz > wget http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz > md5sum fim-0.6-trunk.tar.gz > a > I get: > cat a > 05398df089bcc847e2995db121fa98df fim-0.6-trunk.tar.gz > cat b > 116d513030ef26cd4dff9aada2bea77a fim-0.6-trunk.tar.gz > > Is this an issue on my end ??? > > Didier I don't think it's just you - I tried with curl and elinks and they both gave the wrong md5sum. Dave > Le 01/04/2023 ? 22:12, Didier Spaier a ?crit?: > > Hi, > > > > in fim.info: > > MD5SUM="96492d5c53f806ebdf6d624e73360bdd" > > But: > > md5sum fim-0.6-trunk.tar.gz gives: > > 116d513030ef26cd4dff9aada2bea77a > > > > Also, In the .info: > > DOWNLOAD="http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz" > > However the link works with the https so I suggest indtead: > > DOWNLOAD="https://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz" > > > > Cheers, > > Didier > From artourter at gmail.com Sat Apr 1 21:33:10 2023 From: artourter at gmail.com (Greg Tourte) Date: Sat, 1 Apr 2023 22:33:10 +0100 Subject: [Slackbuilds-users] Updates - 20230401.1 In-Reply-To: References: Message-ID: One of the source files for rstudio-desktop points to the head release in the git repo which has already been updated since the update has been submitted so the checksum fails: https://github.com/quarto-dev/quarto/archive/refs/heads/release/rstudio-cherry-blossom.zip It would be best to point the source file to a specific commit. However, since when you do that the commit hash becomes part of the source tree, I have not been able to find the commit that matches the checksum. I have not tried to use the current version and see if it compiles with it yet. Cheers Greg On Sat, 1 Apr 2023 at 20:59, Dave wrote: > > 01/04/23 16:14, > Fellype : > > multimedia/strawberry: Updated for version 1.0.17. > > > > > > > I've got wrong md5sum for strawberry: > > > > For the file downloaded from > > https://files.strawberrymusicplayer.org/strawberry-1.0.17.tar.xz > > fellype at plasma:~$ md5sum strawberry-1.0.17.tar.xz > > 1af7513c187e3055163076207fc878d1 strawberry-1.0.17.tar.xz > > > > from strawberry.info: > > fellype at plasma:~$ less /usr/sbo/repo/multimedia/strawberry/ > strawberry.info > > | grep MD5 > > MD5SUM="d7cb3bab452e594824989527736b249f" > > Thanks. > > Fixed in my branch and also emailed maintainer. > > Dave > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From isaacyu1 at isaacyu1.com Sun Apr 2 04:05:05 2023 From: isaacyu1 at isaacyu1.com (=?utf-8?q?isaacyu1=40isaacyu1.com?=) Date: Sun, 02 Apr 2023 06:05:05 +0200 Subject: [Slackbuilds-users] =?utf-8?q?Updates_-_20230401=2E1?= In-Reply-To: Message-ID: <333e-6428ff00-1fd-60ea5c00@134329894> Hi Greg, How about this: I change the rstudio-cherry-blossom link to: https://github.com/quarto-dev/quarto/archive/23d8720/rstudio-cherry-blossom.zip I also changed the MD5SUM of the zip file accordingly. My changes to my own SlackBuild are available at the following link: https://github.com/isaackwy/slackbuilds-15.0/commit/25db4fe8977027e7833053013c6db1228058bf57 Please note that I derived the SlackBuild from the Arch Linux AUR PKGBUILD. I didn't know that the AUR PKGBUILD skipped checking checksums (in its case, SHA256SUM rather than MD5SUM): https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=rstudio-desktop - Isaac On Saturday, April 01, 2023 14:33 PDT, Greg Tourte wrote: ?One of the source files for rstudio-desktop points to the head release in the git repo which has already been updated since the update has been submitted so the checksum fails:?https://github.com/quarto-dev/quarto/archive/refs/heads/release/rstudio-cherry-blossom.zip?It would be best to point the source file to a specific commit. However, since when you do that the commit hash becomes part of the source tree, I have not been able to find the commit that matches the checksum. I have not tried to use the current version and see if it compiles with it yet.?Cheers?Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From alik at ejik.org Mon Apr 3 19:34:05 2023 From: alik at ejik.org (Alexander Verbovetsky) Date: Mon, 3 Apr 2023 22:34:05 +0300 Subject: [Slackbuilds-users] uid/gid for _dkimsign Message-ID: Hello, I'm writing a SlackBuild for opensmtpd-filter-dkimsign, and I'd like to ask for a UID/GID for the user/group "_dkimsign". Best regards, Alexander From arnaud.garcia-fernandez at laposte.net Wed Apr 5 08:33:30 2023 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Wed, 5 Apr 2023 10:33:30 +0200 Subject: [Slackbuilds-users] Gitlab download filename changed In-Reply-To: <1982629135.173182.1680108514175@nm53.abv.bg> References: <20230328192628.5b04136482ae524b725b8779@laposte.net> <1982629135.173182.1680108514175@nm53.abv.bg> Message-ID: <20230405103330.e1e5919ed9e1a01d948c8d25@laposte.net> >>> it seems that gitlab download filenames changed very recently. >>> For example when downloading the new graphviz-8.0.1.tar.bz2 I get a file >>> named : >>> graphviz-8cd5300e2e31c80dbbfcdd65aad697187e5ac0b0.tar.bz2 >> >> This is what I get clicking on the link in firefox. >> However wget works as usual. >> Didier > > No matter whether content disposition or not, the tar contains the following > dir for 7.1.0: 'graphviz-e650d3ba65f6d672a1fe09505bb576d4fed320bc'. That's not > the expect $VERSION naming. What the actual fuck... > That was the main problem, true. Fortunaltely, it turns out this was probably a mistake on gitlab part, and things are now working as usual again ! So Graphviz will be updated this week... Cheers ! - Yth. From willysr at slackbuilds.org Fri Apr 7 12:51:19 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 7 Apr 2023 19:51:19 +0700 Subject: [Slackbuilds-users] uid/gid for _dkimsign In-Reply-To: References: Message-ID: <92d22a37-353a-168d-f601-d2c689ecc6a9@slackbuilds.org> > I'm writing a SlackBuild for opensmtpd-filter-dkimsign, and I'd like to > ask for a UID/GID for the user/group "_dkimsign". use 376 for dkimsign -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Apr 8 02:28:58 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 8 Apr 2023 09:28:58 +0700 Subject: [Slackbuilds-users] Updates - 20230408.1 Message-ID: <13be03d7-c2de-18c9-d95f-8076e741ee22@slackbuilds.org> Sat Apr 8 02:17:09 UTC 2023 academic/fityk: Updated for version 1.3.2. academic/gaiasky: Added (3D universe simulator for desktop and VR) academic/root: do not download and use gtest audio/cubeb: Updated for version 20230321_2071354. audio/ncspot: Updated for version 0.13.1. desktop/Matcha-gtk-theme: Update for 2023_04_03 desktop/azote: Updated for version 1.11.0. desktop/hyfetch: Updated for version 1.4.8. desktop/nwg-bar: Updated for version 0.1.2. desktop/nwg-displays: Updated for version 0.3.0. desktop/nwg-panel: Updated for version 0.8.2. desktop/xfce4-docklike-plugin: Updated for version 0.4.1. development/bazel: Updated for version 5.4.0. development/colm: Updated for version 0.14.7. development/dynarmic: Updated for version 6.4.6. development/github-cli: Updated for version 2.25.1. development/guile2.2: Use https for DOWNLOAD development/jupyter-nbclassic: Updated for version 0.5.4. development/jupyter-notebook: Updated for version 6.5.4. development/mle: Updated for version 1.5.0. development/python3-spyder-kernels: Update for 2.4.3 development/ragel: Updated for version 7.0.4. development/rstudio-desktop: Fix MD5SUM development/sbcl: Updated for version 2.3.3. development/tiled: updated for version 1.10.1 development/universal-ctags: Updated for version p6.0.20230402.0 development/vscode-bin: Updated for version 1.77.1. development/xmake: Updated for version 2.7.8. games/boosteroid: Updated for version 1.5.3. games/jg-bsnes: Updated for version 1.1.2. games/jg-prosystem: Updated for version 1.5.2. games/jollygood: Updated for version 1.0.1. games/zork-mit: Added (PDP/10 Zork from MIT, circa 1981) graphics/FreeCAD: Updated for version 0.20.2 graphics/OpenCASCADE: Updated for version 7.7.0 graphics/fim: Fix source md5sum. graphics/graphviz: updated for version 8.0.1 graphics/tuxpaint-stamps: Updated for version 2023.04.02. graphics/tuxpaint: Updated for version 0.9.29. graphics/vuescan: Updated MD5SUMs. libraries/VTK: Updated for version 9.2.6 libraries/exiftool: Updated for version 12.60. libraries/fast_float: Updated for version 4.0.0. libraries/gloox: Updated for version 1.0.26. libraries/libopensmtpd: Added (library for OpenSMTPD filters) libraries/qt6: Updated for version 6.5.0. misc/bitwarden-desktop: Updated for version 2023.3.2. misc/fcitx-mozc: Remove template comment. misc/flips: Added (Rom patching utility) multimedia/FFaudioConverter: Added (Graphical audio converter) multimedia/flowblade: Add python3-numpy dependency multimedia/plexmediaserver: Updated for V. 1.31.3.6868_28fc46b27. multimedia/strawberry: Fix source md5sum. network/AdGuardHome: Updated for version 0.107.27. network/dropbox: Updated for version 171.4.6182. network/element-desktop: Updated for version 1.11.28. network/haproxy: Updated for version 2.7.6. network/limnoria: Updated for version 2023_02_11. network/opensmtpd-filter-dkimsign: Added (OpenSMTPD filter for DKIM) network/opensmtpd: Fix pkill, add testconf, to rc init file. network/plastid: Fix github tarball handling. network/qutebrowser-bin: Updated for version 2.5.4. network/signal-desktop: Updated for version 6.13.0. network/webex: Updated for version 43.4.0.25788 network/yt-dlp: Updated for version 2023.03.04. network/zoom-linux: Updated for version 5.14.2.2046 office/calibre-bin: Updated for version 6.15.0. office/kbibtex: Updated for version 0.10.0 python/defusedxml: Removed (Use python3-defusedxml). python/mini-amf: Switch dep. python/pyamf: Switch dep. python/pygsl: Updated for version 2.3.3. python/python-socks: Update for 2.2.0 python/python3-debugpy: Update for 1.6.7 python/python3-h5py: Updated for version 3.8.0. python/python3-hupper: updated for version 1.12 python/python3-psycopg2: updated for version 2.9.6 python/python3-shtab: Update for 1.6.1 system/Iosevka-aile: Updated for version 22.0.0. system/Iosevka-etoile: Updated for version 22.0.0. system/ciderpress-tools: Added (tools for Apple II disk images) system/conky: Updated for version 1.19.0. system/gnome-online-accounts: Fix configure flag. system/letsencrypt: Updated for version 2.5.0. system/mlterm: Updated for version 3.9.3. system/slpkg: Updated for version 4.7.6. system/wine-staging: Updated for version 8.5. system/wine: Make tests for lowercase options. No BUILD bump. system/winetricks: Update for 20230212 +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From dchmelik at gmail.com Sat Apr 8 03:50:06 2023 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Fri, 7 Apr 2023 20:50:06 -0700 Subject: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) Message-ID: It's confusing there's both LibreOffice and libreoffice packages when one is basically a binary repackaging.? As such, why wasn't package naming format followed like the different calibre, calibre-bin, palemoon, palemoon-bin, etc.? From chris.willing at linux.com Sat Apr 8 05:13:09 2023 From: chris.willing at linux.com (Christoph Willing) Date: Sat, 8 Apr 2023 15:13:09 +1000 Subject: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) In-Reply-To: References: Message-ID: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> On 8/4/23 13:50, dchmelik at gmail.com wrote: > It's confusing there's both LibreOffice and libreoffice packages when > one is basically a binary repackaging.? As such, why wasn't package > naming format followed like the different calibre, calibre-bin, > palemoon, palemoon-bin, etc.? I don't know if there's any particular reason for not following that format. Similarly, no particular reason to follow that format either. I'm not aware of any rule or convention to use that format. I can see the attraction of adding "-bin"; nevertheless the README of LibreOffice very clearly states that it builds from source; the README of libreoffice very clearly states that it repackages official binaries. We all read the READMEs don't we? Historically, when LibreOffice was added to the repo, libreoffice had already existed for some time. To follow the *-bin format, we would have had to rename libreoffice as libreoffice-bin and then add libreoffice. Of course that could have been done if there was an established convention to do so, but there was no such convention back then in Jan 2016. As for palemoon, a binary repacking named palemoon already existed for some time before being renamed to palemoon-bin in May 2018, shortly before a build from source palemoon was added in Jun 2018. I believe this was the first[1] SlackBuild to use the "-bin" suffix to denote a binary repackaging, so impossible to use as an exemplar for LibreOffice/libreoffice in 2016. The calibre SlackBuild was added in 2010 with calibre-bin added in Jul 2019 - again too late to use as an examplar for LibreOffice. Perhaps those *-bin SlackBuilds should have followed the existing convention provided 2 years earlier by Libreoffice/libreoffice - also Blender/blender 3 years earlier in Aug 2015. chris [1] there was actually a "haskell-binary" that was removed in 2012. From urchlay at slackware.uk Sat Apr 8 06:53:55 2023 From: urchlay at slackware.uk (B. Watson) Date: Sat, 8 Apr 2023 02:53:55 -0400 (EDT) Subject: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) In-Reply-To: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> References: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> Message-ID: <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> On Sat, 8 Apr 2023, Christoph Willing wrote: > Perhaps those *-bin SlackBuilds should have followed the existing > convention provided 2 years earlier by Libreoffice/libreoffice - also > Blender/blender 3 years earlier in Aug 2015. Gods, no. We'd have had even more confusion. Just because it was done doesn't make it a good idea to keep doing... I think having 2 builds with names that only differ in capitalization is a horrible idea. I'd even say it'd be a good idea to rename LibreOffice to libreoffice-bin and Blender to blender-bin. From lists at osh.id.au Sat Apr 8 08:56:23 2023 From: lists at osh.id.au (David O'Shaughnessy) Date: Sat, 08 Apr 2023 16:56:23 +0800 Subject: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) In-Reply-To: <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> References: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> Message-ID: <8ef2f2ee-cc49-4b1b-8e2e-5d83283aa334@app.fastmail.com> I wouldn't mind seeing binary repacks with -bin appended. I'd have to rename some of my own builds, but at least there's some information in the title. Differentiating by capitalization seems very arbitrary. On Sat, 8 Apr 2023, at 2:53 PM, B. Watson wrote: > On Sat, 8 Apr 2023, Christoph Willing wrote: > >> Perhaps those *-bin SlackBuilds should have followed the existing >> convention provided 2 years earlier by Libreoffice/libreoffice - also >> Blender/blender 3 years earlier in Aug 2015. > > Gods, no. We'd have had even more confusion. Just because it was done > doesn't make it a good idea to keep doing... > > I think having 2 builds with names that only differ in capitalization > is a horrible idea. I'd even say it'd be a good idea to rename > LibreOffice to libreoffice-bin and Blender to blender-bin. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ From chris.willing at linux.com Sat Apr 8 09:29:21 2023 From: chris.willing at linux.com (Christoph Willing) Date: Sat, 8 Apr 2023 19:29:21 +1000 Subject: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) In-Reply-To: <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> References: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> Message-ID: On 8/4/23 16:53, B. Watson wrote: > > > On Sat, 8 Apr 2023, Christoph Willing wrote: > >> Perhaps those *-bin SlackBuilds should have followed the existing >> convention provided 2 years earlier by Libreoffice/libreoffice - also >> Blender/blender 3 years earlier in Aug 2015. > > Gods, no. We'd have had even more confusion. Just because it was done > doesn't make it a good idea to keep doing... > > I think having 2 builds with names that only differ in capitalization > is a horrible idea. I'd even say it'd be a good idea to rename > LibreOffice to libreoffice-bin and Blender to blender-bin. It was a joke. However the change would be: libreoffice -> libreoffice-bin and LibreOffice -> libreoffice blender -> blender-bin and Blender -> blender since the currently capitalized versions build from source and uncapitalized versions repackage binaries. chris From marav8 at free.fr Sat Apr 8 09:53:48 2023 From: marav8 at free.fr (marav) Date: Sat, 8 Apr 2023 11:53:48 +0200 Subject: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) In-Reply-To: References: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> Message-ID: <3b18c4ca-3621-12c6-868c-60ae05544f8a@free.fr> Le 08/04/2023 ? 11:29, Christoph Willing a ?crit?: > On 8/4/23 16:53, B. Watson wrote: >> >> >> On Sat, 8 Apr 2023, Christoph Willing wrote: >> >>> Perhaps those *-bin SlackBuilds should have followed the existing >>> convention provided 2 years earlier by Libreoffice/libreoffice - >>> also Blender/blender 3 years earlier in Aug 2015. >> >> Gods, no. We'd have had even more confusion. Just because it was done >> doesn't make it a good idea to keep doing... >> >> I think having 2 builds with names that only differ in capitalization >> is a horrible idea. I'd even say it'd be a good idea to rename >> LibreOffice to libreoffice-bin and Blender to blender-bin. > > It was a joke. > > However the change would be: > ??? libreoffice -> libreoffice-bin and LibreOffice -> libreoffice > ??? blender -> blender-bin???????? and Blender -> blender > > since the currently capitalized versions build from source and > uncapitalized versions repackage binaries. > > chris > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > I for one, I think all binary packages should be renamed with *-bin It gives the most important information that the slackbuild is not a compiled version, directly in the name No matter if there is a compiled version or not -------------- next part -------------- An HTML attachment was scrubbed... URL: From dchmelik at gmail.com Sat Apr 8 10:10:25 2023 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Sat, 8 Apr 2023 03:10:25 -0700 Subject: [Slackbuilds-users] naming conventions (compiled & binary) (was Re: LibreOffice vs libreoffice (confusing, too vague)) In-Reply-To: References: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> Message-ID: On 4/8/23 2:29 AM, Christoph Willing wrote: > On 8/4/23 16:53, B. Watson wrote: >> >> >> On Sat, 8 Apr 2023, Christoph Willing wrote: >> >>> Perhaps those *-bin SlackBuilds should have followed the existing >>> convention provided 2 years earlier by Libreoffice/libreoffice - >>> also Blender/blender 3 years earlier in Aug 2015. >> >> Gods, no. We'd have had even more confusion. Just because it was done >> doesn't make it a good idea to keep doing... >> >> I think having 2 builds with names that only differ in capitalization >> is a horrible idea. I'd even say it'd be a good idea to rename >> LibreOffice to libreoffice-bin and Blender to blender-bin. > > It was a joke. > > However the change would be: > ?? libreoffice -> libreoffice-bin and LibreOffice -> libreoffice > ?? blender -> blender-bin???????? and Blender -> blender > > since the currently capitalized versions build from source and > uncapitalized versions repackage binaries. Aren't there still many capitalized SlackBuilds that build from source without each matching a SlackBuild that does a binary?? I thought it'd be up to upstream and maintainers what capitalization to use... not that I do any that use binaries. From tonus1 at free.fr Sat Apr 8 11:23:01 2023 From: tonus1 at free.fr (Tonus) Date: Sat, 8 Apr 2023 13:23:01 +0200 Subject: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) In-Reply-To: <3b18c4ca-3621-12c6-868c-60ae05544f8a@free.fr> References: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> <3b18c4ca-3621-12c6-868c-60ae05544f8a@free.fr> Message-ID: <20230408112301.e2zqvfhaml42rmaf@Baldr.vingolf.info> On Sat, Apr 08, 2023 at 11:53:48AM +0200, marav wrote: >Le 08/04/2023 ? 11:29, Christoph Willing a ?crit?: >>On 8/4/23 16:53, B. Watson wrote: >>> >>> >>>On Sat, 8 Apr 2023, Christoph Willing wrote: >>> >>>>Perhaps those *-bin SlackBuilds should have followed the >>>>existing convention provided 2 years earlier by >>>>Libreoffice/libreoffice - also Blender/blender 3 years earlier >>>>in Aug 2015. >>> >>>Gods, no. We'd have had even more confusion. Just because it was done >>>doesn't make it a good idea to keep doing... >>> >>>I think having 2 builds with names that only differ in capitalization >>>is a horrible idea. I'd even say it'd be a good idea to rename >>>LibreOffice to libreoffice-bin and Blender to blender-bin. >> >>It was a joke. >> >>However the change would be: >>??? libreoffice -> libreoffice-bin and LibreOffice -> libreoffice >>??? blender -> blender-bin???????? and Blender -> blender >> >>since the currently capitalized versions build from source and >>uncapitalized versions repackage binaries. >> >>chris >> >I for one, I think all binary packages should be renamed with *-bin > >It gives the most important information that the slackbuild is not a >compiled version, directly in the name >No matter if there is a compiled version or not > > I agree with marav. Best to see at first sight what's the diff. Perhaps shall we do the same with .deb repack. -- Regards, Tonus From chris.willing at linux.com Sat Apr 8 10:48:39 2023 From: chris.willing at linux.com (Christoph Willing) Date: Sat, 8 Apr 2023 20:48:39 +1000 Subject: [Slackbuilds-users] naming conventions (compiled & binary) (was Re: LibreOffice vs libreoffice (confusing, too vague)) In-Reply-To: References: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> Message-ID: On 8/4/23 20:10, dchmelik at gmail.com wrote: > On 4/8/23 2:29 AM, Christoph Willing wrote: >> On 8/4/23 16:53, B. Watson wrote: >>> >>> >>> On Sat, 8 Apr 2023, Christoph Willing wrote: >>> >>>> Perhaps those *-bin SlackBuilds should have followed the existing >>>> convention provided 2 years earlier by Libreoffice/libreoffice - >>>> also Blender/blender 3 years earlier in Aug 2015. >>> >>> Gods, no. We'd have had even more confusion. Just because it was done >>> doesn't make it a good idea to keep doing... >>> >>> I think having 2 builds with names that only differ in capitalization >>> is a horrible idea. I'd even say it'd be a good idea to rename >>> LibreOffice to libreoffice-bin and Blender to blender-bin. >> >> It was a joke. >> >> However the change would be: >> ?? libreoffice -> libreoffice-bin and LibreOffice -> libreoffice >> ?? blender -> blender-bin???????? and Blender -> blender >> >> since the currently capitalized versions build from source and >> uncapitalized versions repackage binaries. > > Aren't there still many capitalized SlackBuilds that build from source > without each matching a SlackBuild that does a binary?? I thought it'd > be up to upstream and maintainers what capitalization to use... not that > I do any that use binaries. Yes there may be many SlackBuilds like that. As you say, it's up to upstream and maintainers what capitalization to use. I was referring only to the LibreOffice and Blender SlackBuilds which I maintain. chris From kjhambrick at gmail.com Sat Apr 8 10:56:19 2023 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 8 Apr 2023 05:56:19 -0500 Subject: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) In-Reply-To: <3b18c4ca-3621-12c6-868c-60ae05544f8a@free.fr> References: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> <3b18c4ca-3621-12c6-868c-60ae05544f8a@free.fr> Message-ID: On Sat, Apr 8, 2023 at 4:54?AM marav wrote: > I for one, I think all binary packages should be renamed with *-bin > > It gives the most important information that the slackbuild is not a > compiled version, directly in the name > No matter if there is a compiled version or not > All -- Thinking out loud here ... I agree with marav but would there not need to be special, one-time instructions to `removepkg old-package-without-dash-bin` before doing an `upgradepkg --install-nre new-package-with-bin` ? Othewise, wouldn't upgradepkg be confused ? And would /var/log/packages/ be 'corrupted' ? -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: From kjhambrick at gmail.com Sat Apr 8 11:20:35 2023 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 8 Apr 2023 06:20:35 -0500 Subject: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) In-Reply-To: References: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> <3b18c4ca-3621-12c6-868c-60ae05544f8a@free.fr> Message-ID: On Sat, Apr 8, 2023 at 5:56?AM Konrad J Hambrick wrote: > On Sat, Apr 8, 2023 at 4:54?AM marav wrote: > >> I for one, I think all binary packages should be renamed with *-bin >> >> It gives the most important information that the slackbuild is not a >> compiled version, directly in the name >> No matter if there is a compiled version or not >> > All -- > > Thinking out loud here ... > > I agree with marav but would there not need to be special, one-time > instructions to `removepkg old-package-without-dash-bin` before doing an > `upgradepkg --install-nre new-package-with-bin` ? > <> Dang ! I said: --install-nre I meant: --install-new -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrzej at telszewski.com Sat Apr 8 11:57:15 2023 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Sat, 8 Apr 2023 13:57:15 +0200 (GMT+02:00) Subject: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) In-Reply-To: References: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> <3b18c4ca-3621-12c6-868c-60ae05544f8a@free.fr> Message-ID: <65097d81-1f76-4769-a3bd-c37c3f46a47e@telszewski.com> *From: *Konrad J Hambrick *To: *SlackBuilds.org Users List *Date: *8 Apr 2023 12:56:36 *Subject: *Re: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) > On Sat, Apr 8, 2023 at 4:54?AM marav wrote: >> >> I for one, I think all binary packages should be renamed with *-bin >> >> It gives the most important information that the slackbuild is not a compiled version, directly in the name >> No matter if there is a compiled version or not >> > All -- > > Thinking out loud here ... > > I agree with marav but would there not need to be special, one-time instructions to `removepkg old-package-without-dash-bin` before doing an `upgradepkg --install-nre new-package-with-bin` ? > > Othewise, wouldn't upgradepkg be confused ?? > > And?would /var/log/packages/ be 'corrupted' ? > > -- kjh `pkgtools` are (specifically) designed in a way that if one package over-installs another, there is no corruption in the database. You just need to uninstall the old package, which can be safely done after the new package is installed. Actually, this is how the `upgradepkg` works under the hood. It over-installs one package on the other, then removes the old one. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 691 bytes Desc: not available URL: From kjhambrick at gmail.com Sat Apr 8 12:10:50 2023 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 8 Apr 2023 07:10:50 -0500 Subject: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague) In-Reply-To: <65097d81-1f76-4769-a3bd-c37c3f46a47e@telszewski.com> References: <5a09860c-43df-8fe3-8b3f-bac246cba013@linux.com> <51bd7f9f-7ef-5832-c77a-878d418285de@slackware.uk> <3b18c4ca-3621-12c6-868c-60ae05544f8a@free.fr> <65097d81-1f76-4769-a3bd-c37c3f46a47e@telszewski.com> Message-ID: On Sat, Apr 8, 2023 at 6:57?AM Andrzej Telszewski wrote: > `pkgtools` are (specifically) designed in a way that if one package > over-installs another, there is no corruption in the database. > > You just need to uninstall the old package, which can be safely done after > the new package is installed. > > Actually, this is how the `upgradepkg` works under the hood. > It over-installs one package on the other, then removes the old one. > Thanks for the info Andrzej ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: From fellype at gmail.com Mon Apr 10 13:23:18 2023 From: fellype at gmail.com (Fellype) Date: Mon, 10 Apr 2023 10:23:18 -0300 Subject: [Slackbuilds-users] Scripts for grab In-Reply-To: <3f81017f-2042-449a-a610-6781053c1ba0@jaxartes.net> References: <3f81017f-2042-449a-a610-6781053c1ba0@jaxartes.net> Message-ID: Hi guys, Em qui., 6 de abr. de 2023 ?s 12:53, Benjamin Trigona-Harany < slackbuilds at jaxartes.net> escreveu: > I stopped maintaining my builds a couple of years ago. Feel free to take > them over. Best, Ben > > > Maybe I've missed some past email in the list... Benjamin Trigona-Harany is not maintaining his build scripts anymore. So, they are up for grab but he is still listed as maintainer of the scripts listed below. I'll not take any of them because none is in my "profile" (sorry!!). If someone has plans to take over gis/OTB, please, test it against the muParser v2.3.4 (build script attached). I'm planning to update muParser, but OTB is the only dependee that does not build with the new version. Regards, Fellype academic/ITK academic/Shark academic/cld2 audio/minimodem desktop/kwalletcli desktop/screenkey desktop/vim-qt development/Sphinx development/cunit development/eovim development/neovim-qt games/VASSAL gis/Fiona gis/Geohash gis/OTB gis/OWSLib gis/SFCGAL gis/cligj gis/geographiclib-python gis/geojson gis/geopandas gis/geopy gis/gj2ascii gis/laszip gis/mapnik gis/merkaartor gis/osm2pgrouting gis/osm2pgsql gis/ossim gis/pdal gis/pgrouting gis/pgsql-ogr-fdw gis/pktools gis/pointcloud gis/polyline gis/postgis gis/python-mapnik gis/qgis gis/rasterio gis/saga-gis gis/whitebox-tools gis/xplanet graphics/exact-image libraries/hdf libraries/libkml libraries/libpqxx libraries/libversion libraries/stfl multimedia/xawtv network/megatools network/tornado office/basket office/tellico python/affine python/async_generator python/backcall python/backports-abc python/munch python/numexpr python/pycld2 python/python-emoji python/python3-gitdb2 python/python3-pexpect python/python3-ptyprocess python/python3-smmap2 python/simplegeneric python/snuggs python/sphinxcontrib-applehelp python/sphinxcontrib-devhelp python/sphinxcontrib-htmlhelp python/sphinxcontrib-jsmath python/sphinxcontrib-qthelp python/sphinxcontrib-serializinghtml python/sphinxcontrib-websupport python/timehash system/pspg system/skim system/thinkfan system/vagrant -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: muParser.tar.gz Type: application/gzip Size: 2600 bytes Desc: not available URL: From slackbuilds at schoepfer.info Wed Apr 12 12:27:17 2023 From: slackbuilds at schoepfer.info (Franzen) Date: Wed, 12 Apr 2023 14:27:17 +0200 Subject: [Slackbuilds-users] Fwd: ngspice on SBo In-Reply-To: <4309a711c4b15f9511424da9941239c1@schoepfer.info> References: <4309a711c4b15f9511424da9941239c1@schoepfer.info> Message-ID: <470edd1289ef224560dcd770b720eada@schoepfer.info> I forward to this list, as i got no reply from Rsamurti(maybe landed in the spam-folder) -------- Originalnachricht -------- Betreff: ngspice on SBo Datum: 2023-04-08 07:55 Von: Franzen An: rsamurti at gmail.com Hi, it seems openmpi is no hard requirement for ngspice, your buildscript builds with and without openmpi, and i can happily user ngspice without openmpi. So i propose to mark openmpi as optional. Cheers, Johannes From dhalliwe at rogers.com Wed Apr 12 22:21:19 2023 From: dhalliwe at rogers.com (David Halliwell) Date: Wed, 12 Apr 2023 18:21:19 -0400 Subject: [Slackbuilds-users] Problem/fix for SlackBuild for MP3Diags References: <98df2c0e-420e-5df7-c5b6-e4e89cdd54db.ref@rogers.com> Message-ID: <98df2c0e-420e-5df7-c5b6-e4e89cdd54db@rogers.com> ?? Hello. A long-time Slackware user here, but relatively new to using SlackBuilds. Sending this email without subscribing to the mailing list. ?? Today, I wanted to build/install the MP3Diags software (https://slackbuilds.org/repository/15.0/audio/MP3Diags/?search=mp3diag). It would not build, exiting with a message about not finding Qwidget. I had seen the qt4 dependency, and had downloaded, built, and installed qt4 using he Slackbuild, but MP3Diags would not build on my Slackware 15.0 system (upgraded last year from 14.2). I also tried building it on a fairly clean Slackware 15.0 VM, but had the same error. ?? Looking closely at the SlackBuild script and the errors messages on the terminal window, I was able to determine that the build script was finding and using qmake from the standard qt5 installation, not the qt4 version. I manged to work around this by changing line 83 from 'qmake' to '/usr/lib64/qt4/bin/qmake', and then I also needed to change line 88 from 'lrelease' to '/usr/lib64/qt4/bin/lrelease'. After those changes, MP3Diags built, installed, and ran successfully. ?? I have contacted Dominik Drobek (the listed maintainer) about this. He is still on 14.2, and he mentioned that there is a newer version of MP3Diags available upstream that uses qt5, but he does not have time to do any updates now. He suggested that I take over - but I also do not have time, and do not feel I have the necessary skills to be able to revise the script for a new version. ?? I don't know if my fix is the best way, or whether there is something odd about my system with leftover cruft from previous Slackware versions, but I thought I'd take the time to send in the information on the fix I have found, in case someone can make the changes - or has a better solution. ?? Thanks for having this resource available. -- David Halliwell -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Thu Apr 13 05:52:34 2023 From: urchlay at slackware.uk (B. Watson) Date: Thu, 13 Apr 2023 01:52:34 -0400 (EDT) Subject: [Slackbuilds-users] Problem/fix for SlackBuild for MP3Diags In-Reply-To: <98df2c0e-420e-5df7-c5b6-e4e89cdd54db@rogers.com> References: <98df2c0e-420e-5df7-c5b6-e4e89cdd54db.ref@rogers.com> <98df2c0e-420e-5df7-c5b6-e4e89cdd54db@rogers.com> Message-ID: <47caa25c-63be-ea39-40e3-9251d63028ae@slackware.uk> Replying directly to the poster, plus to the list. On Wed, 12 Apr 2023, David Halliwell wrote: > ?? Today, I wanted to build/install the MP3Diags software (https://slackbuilds.org/repository/15.0/audio/MP3Diags/?search=mp3diag). It would not > build, exiting with a message about not finding Qwidget. I had seen the qt4 dependency, and had downloaded, built, and installed qt4 using he > Slackbuild, but MP3Diags would not build on my Slackware 15.0 system (upgraded last year from 14.2). I also tried building it on a fairly clean > Slackware 15.0 VM, but had the same error. The probable reason for a SlackBuild not picking up your qt4 is that qt4 installs a script that sets some environment variables, in /etc/profile.d/. If you didn't have qt4 already installed, and you install it, then try to build something that expects those variables to already be set... you get the exact issue you were having. The easiest thing to do is install qt4, then log out & back in. Your new login will have the environment variables set correctly. The qt4 README doesn't actually mention this (though it should). It's possible to write a SlackBuild that will source the profile script itself, avoiding this problem, but not all qt4-using scripts do this. You've found one that doesn't, apparently. So yeah, the MP3Diags SlackBuild needs attention. And so does the README for qt4. Thanks for pointing it out. From urchlay at slackware.uk Thu Apr 13 05:55:38 2023 From: urchlay at slackware.uk (B. Watson) Date: Thu, 13 Apr 2023 01:55:38 -0400 (EDT) Subject: [Slackbuilds-users] system76-power In-Reply-To: <0c8e1e69-a918-636f-7984-4935368ebc4a@ptd.net> References: <0c8e1e69-a918-636f-7984-4935368ebc4a@ptd.net> Message-ID: <24e5f20-b56a-9f8-b2d3-9ae3658f970@slackware.uk> On Sat, 28 Jan 2023, John via SlackBuilds-users wrote: > namespaced features with the `dep:` prefix are only allowed on the nightly > channel and requires the `-Z namespaced-features` flag on the command-line > make: *** [Makefile:62: target/release/system76-power] Error 101 >From the README for system76-power: NOTE: The directions in rustup's README must be followed so that the rust installed by rustup is preferred over the system rust. Maybe you didn't follow those directions? Just a guess, because of the word "nightly" in the error message. From dave at slackbuilds.org Thu Apr 13 09:54:42 2023 From: dave at slackbuilds.org (Dave) Date: Thu, 13 Apr 2023 10:54:42 +0100 Subject: [Slackbuilds-users] libreoffice-7.4.3.2 Slackbuild In-Reply-To: <32128fd9-d077-fcce-ca63-c141843935f4@gmail.com> References: <32128fd9-d077-fcce-ca63-c141843935f4@gmail.com> Message-ID: Wayne Smith : > I think this email id for Chris Willing . Never done this before > installed this LibreOffice-7.4.3.2-x86_64-1_SBo yesterday > had to uninstall jdk8 then reinstall jdk8 > also had to reboot a couple of times > not much fun. You didn't need to reboot. A logout/login or source /etc/profile should have been enough. If you have more than one jdk installed, you'll need to make their /etc/profile.d/ scripts non-executable and manually source the one you need for the application you want to run that uses it: . /etc/profile.d/zulu-openjdk11.sh > libreOffice is running now and I'm happy > don't understand why I need both jdk8 and jdk11 installed to make the slack > build happy. > looking into javajdk problems with LibreOffice-7.4.3.2 SBo install .. needed > both jdk8 and jdk11 installed > post install > both jdk8.sh and jdk11.sh are in /etc/profile.d .. and they both are > executable ????? > env says JAVA_HOME=/usr/lib64/zulu-openjdk11 > so I guess /etc/profile.d/zulu-openjdk11.sh runs after > /etc/profile.d/zulu-openjdk8.sh It would have been the other way around, because 8 comes after 1. > not to predictable > checking sboui today I see version 7.4.5.1 is available now. > has the jdk wars been settled in this version ? The /etc/profile.d/zulu-openjdk11.sh script ought to be sourced before starting the build, or all other jdks uninstalled, logout and login again. Check $JAVA_HOME before building to be sure. You could test if whatever applications need the older jdk versions will work with version 11. If they do, simply uninstall the older versions and keep the latest. Dave -- sbo-maintainer-tools (sbolint, sbopkglint): https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt From chris.willing at linux.com Thu Apr 13 10:25:05 2023 From: chris.willing at linux.com (Christoph Willing) Date: Thu, 13 Apr 2023 20:25:05 +1000 Subject: [Slackbuilds-users] libreoffice-7.4.3.2 Slackbuild In-Reply-To: References: <32128fd9-d077-fcce-ca63-c141843935f4@gmail.com> Message-ID: <00a4ee7c-d4a9-5254-c0dc-b6837606e72a@linux.com> On 13/4/23 19:54, Dave wrote: > Wayne Smith : >> I think this email id for Chris Willing . Never done this before >> installed this LibreOffice-7.4.3.2-x86_64-1_SBo yesterday >> had to uninstall jdk8 then reinstall jdk8 >> also had to reboot a couple of times >> not much fun. > > You didn't need to reboot. A logout/login or source /etc/profile > should have been enough. If you have more than one jdk installed, > you'll need to make their /etc/profile.d/ scripts non-executable and > manually source the one you need for the application you want to run > that uses it: > > . /etc/profile.d/zulu-openjdk11.sh > >> libreOffice is running now and I'm happy >> don't understand why I need both jdk8 and jdk11 installed to make the slack >> build happy. >> looking into javajdk problems with LibreOffice-7.4.3.2 SBo install .. needed >> both jdk8 and jdk11 installed >> post install >> both jdk8.sh and jdk11.sh are in /etc/profile.d .. and they both are >> executable ????? >> env says JAVA_HOME=/usr/lib64/zulu-openjdk11 >> so I guess /etc/profile.d/zulu-openjdk11.sh runs after >> /etc/profile.d/zulu-openjdk8.sh > > It would have been the other way around, because 8 comes after 1. > >> not to predictable >> checking sboui today I see version 7.4.5.1 is available now. >> has the jdk wars been settled in this version ? > > The /etc/profile.d/zulu-openjdk11.sh script ought to be sourced > before starting the build, or all other jdks uninstalled, logout and > login again. > > Check $JAVA_HOME before building to be sure. > > You could test if whatever applications need the older jdk versions > will work with version 11. If they do, simply uninstall the older > versions and keep the latest. > Although zulu-openjdk11 is specified in the .info file, just about any of the multitude of JDKs will work OK to build/run LibreOffice. Provided $JAVA_HOME exists and points to something valid, the SlackBuild should work. Dave offers good advice about removing older versions and keeping the latest. However if the old version really is required for some other SLackBuild, I'm pretty sure LibreOffice will still build/run with the older JDK. Again, ensure $JAVA_HOME is valid. The latest version LibreOffice version is 7.5.2.2. chris From erich.public at protonmail.com Thu Apr 13 13:23:12 2023 From: erich.public at protonmail.com (Erich Ritz) Date: Thu, 13 Apr 2023 13:23:12 +0000 Subject: [Slackbuilds-users] system76-power In-Reply-To: <24e5f20-b56a-9f8-b2d3-9ae3658f970@slackware.uk> References: <0c8e1e69-a918-636f-7984-4935368ebc4a@ptd.net> <24e5f20-b56a-9f8-b2d3-9ae3658f970@slackware.uk> Message-ID: <0wbAt0tvf1GoDs4XH26TFS53iu0TOFwA_W2WtXLiLk1dQBDc8dLYMPW8SuDl0WaVhYNuMmilUfhpi4ata9irG5d3z7p6BKxhWIBBdOnB9Xk=@protonmail.com> ------- Original Message ------- On Thursday, April 13th, 2023 at 12:55 AM, B. Watson wrote: > > > > > > On Sat, 28 Jan 2023, John via SlackBuilds-users wrote: > > > namespaced features with the `dep:` prefix are only allowed on the nightly > > channel and requires the `-Z namespaced-features` flag on the command-line > > make: *** [Makefile:62: target/release/system76-power] Error 101 > > > From the README for system76-power: > > NOTE: The directions in rustup's README must be followed so that the > rust installed by rustup is preferred over the system rust. > > Maybe you didn't follow those directions? Just a guess, because of the > word "nightly" in the error message. Maintainer here, Yes, I think that's the reason. If I remember correctly I can't use SBo's rust16 because the project wants exactly rust version 1.61.0. Erich From dhalliwe at rogers.com Thu Apr 13 14:50:40 2023 From: dhalliwe at rogers.com (David Halliwell) Date: Thu, 13 Apr 2023 10:50:40 -0400 Subject: [Slackbuilds-users] Problem/fix for SlackBuild for MP3Diags In-Reply-To: <47caa25c-63be-ea39-40e3-9251d63028ae@slackware.uk> References: <98df2c0e-420e-5df7-c5b6-e4e89cdd54db.ref@rogers.com> <98df2c0e-420e-5df7-c5b6-e4e89cdd54db@rogers.com> <47caa25c-63be-ea39-40e3-9251d63028ae@slackware.uk> Message-ID: ?? Subscribing to the list, so I can see any other responses... ?? Thanks for this advice. When trying the original compile, I was pretty sure that is was something like this - and I had tried going out of X to a level 3 prompt and logging in as root, to get a full root environment. ?? I took a look this morning (which is after a reboot). I see the .qt4.sh and qt4.csh files in /etc/profile.d, but it seems that they are not having any effect on modifying my $PATH in either my real system or my VM. /usr/lib64/qt5/bin is there, and 'which qmake' gives me the qt5 version (either as a regular user or as root). Must be something about how I have set up my machine - which is not a SlackBuild problem, AFAIK. I use bash, and the default /etc/profile does run .sh files in profile.d - but only if they are set executable (and qt4.sh is not). The qt4.sh script itself says to NOT make it executable. ?? Again, thanks for the work everyone does in making the SlackBuilds resource available, and glad I could help in a small way.. Dave On 2023-04-13 01:52, B. Watson wrote: > > > Replying directly to the poster, plus to the list. > > On Wed, 12 Apr 2023, David Halliwell wrote: > >> ?? Today, I wanted to build/install the MP3Diags software >> (https://slackbuilds.org/repository/15.0/audio/MP3Diags/?search=mp3diag). >> It would not >> build, exiting with a message about not finding Qwidget. I had seen >> the qt4 dependency, and had downloaded, built, and installed qt4 >> using he >> Slackbuild, but MP3Diags would not build on my Slackware 15.0 system >> (upgraded last year from 14.2). I also tried building it on a fairly >> clean >> Slackware 15.0 VM, but had the same error. > > The probable reason for a SlackBuild not picking up your qt4 is > that qt4 installs a script that sets some environment variables, in > /etc/profile.d/. If you didn't have qt4 already installed, and you > install it, then try to build something that expects those variables > to already be set... you get the exact issue you were having. > > The easiest thing to do is install qt4, then log out & back in. Your > new login will have the environment variables set correctly. The qt4 > README doesn't actually mention this (though it should). > > It's possible to write a SlackBuild that will source the profile > script itself, avoiding this problem, but not all qt4-using scripts do > this. You've found one that doesn't, apparently. > > So yeah, the MP3Diags SlackBuild needs attention. And so does the > README for qt4. Thanks for pointing it out. -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Thu Apr 13 18:43:13 2023 From: urchlay at slackware.uk (B. Watson) Date: Thu, 13 Apr 2023 14:43:13 -0400 (EDT) Subject: [Slackbuilds-users] Problem/fix for SlackBuild for MP3Diags In-Reply-To: References: <98df2c0e-420e-5df7-c5b6-e4e89cdd54db.ref@rogers.com> <98df2c0e-420e-5df7-c5b6-e4e89cdd54db@rogers.com> <47caa25c-63be-ea39-40e3-9251d63028ae@slackware.uk> Message-ID: <5880f7a-4282-18f5-81b7-64d4b579fa0@slackware.uk> On Thu, 13 Apr 2023, David Halliwell wrote: > bash, and the default /etc/profile does run .sh files in profile.d - but only if they are set executable (and qt4.sh is not). The qt4.sh script > itself says to NOT make it executable. Right, it does. It's been a year since I looked at this... so ignore what I said about logging out and back in. I should have actually built/installed qt4 instead of working from my faulty memory. Looks like what's needed is for MP3Diags to source the qt4.sh script itself, before running qmake. Doing that makes it build. So I'll make that change (I'm not the maintainer, but we haven't got a response from the maintainer yet...) Sorry for the confusion. From dominik.drobek at o2.pl Thu Apr 13 19:00:55 2023 From: dominik.drobek at o2.pl (Dominik Drobek) Date: Thu, 13 Apr 2023 21:00:55 +0200 Subject: [Slackbuilds-users] Problem/fix for SlackBuild for MP3Diags In-Reply-To: <5880f7a-4282-18f5-81b7-64d4b579fa0@slackware.uk> References: <98df2c0e-420e-5df7-c5b6-e4e89cdd54db.ref@rogers.com> <98df2c0e-420e-5df7-c5b6-e4e89cdd54db@rogers.com> <47caa25c-63be-ea39-40e3-9251d63028ae@slackware.uk> <5880f7a-4282-18f5-81b7-64d4b579fa0@slackware.uk> Message-ID: <222cdffc-4114-c74b-74c6-c18fdf2a8fde@o2.pl> W dniu 13.04.2023 o?20:43, B. Watson pisze: > Looks like what's needed is for MP3Diags to source the qt4.sh script > itself, before running qmake. Doing that makes it build. So I'll make > that change (I'm not the maintainer, but we haven't got a response > from the maintainer yet...) Hi, Maintainer here. Please go ahead and make that change. The long-term solution is to update to version ported to Qt5 and to drop Qt4 dependency, but your fix can be applied quickly. I need more time to make a proper update, because I don't have Slackware 15 installed at the moment. Thanks, Dominik From urchlay at slackware.uk Thu Apr 13 19:24:45 2023 From: urchlay at slackware.uk (B. Watson) Date: Thu, 13 Apr 2023 15:24:45 -0400 (EDT) Subject: [Slackbuilds-users] Problem/fix for SlackBuild for MP3Diags In-Reply-To: <222cdffc-4114-c74b-74c6-c18fdf2a8fde@o2.pl> References: <98df2c0e-420e-5df7-c5b6-e4e89cdd54db.ref@rogers.com> <98df2c0e-420e-5df7-c5b6-e4e89cdd54db@rogers.com> <47caa25c-63be-ea39-40e3-9251d63028ae@slackware.uk> <5880f7a-4282-18f5-81b7-64d4b579fa0@slackware.uk> <222cdffc-4114-c74b-74c6-c18fdf2a8fde@o2.pl> Message-ID: On Thu, 13 Apr 2023, Dominik Drobek wrote: > Maintainer here. Please go ahead and make that change. The long-term > solution is to update to version ported to Qt5 and to drop Qt4 > dependency, but your fix can be applied quickly. OK, done. You're right, if there's a qt5 version, that'd be better. From urchlay at slackware.uk Thu Apr 13 22:00:28 2023 From: urchlay at slackware.uk (B. Watson) Date: Thu, 13 Apr 2023 18:00:28 -0400 (EDT) Subject: [Slackbuilds-users] Submission error In-Reply-To: <44-63ff0780-3-14ad5f00@41677159> References: <44-63ff0780-3-14ad5f00@41677159> Message-ID: <245e97d-4799-2d4b-e37b-b3ccc79a7fd7@slackware.uk> On Wed, 1 Mar 2023, Ivan Kovmir via SlackBuilds-users wrote: > I have tried to submit a new slackbuild, but the submission form says there is an error (does not say which one) and asks me to send the archive > to this email address. You included the source tarball inside your submission tarball. You might want to install sbo-maintainer-tools and use sbolint to check your submission tarballs before uploading them. I ran it on the tarball you posted to the list, and got: $ sbolint limine.tar.gz limine: WARN: limine.tar.gz is larger than 1048576 bytes, upload may be rejected limine: ERR: source archive found: limine-4.20230227.0.tar.gz sbolint: limine: errors 1, warnings 1 ...which pretty much tells you what to do to fix it. From dickson.tim at googlemail.com Fri Apr 14 15:14:44 2023 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 14 Apr 2023 16:14:44 +0100 Subject: [Slackbuilds-users] OpenSubdiv linking issue Message-ID: hi all, I'm attempting to build OpenSubdiv with optional deps tbb and glfw3 and am getting a linking error [ 33%] Linking CXX executable ../../bin/glViewer /usr/bin/ld: ../common/CMakeFiles/examples_common_gl_obj.dir/clDeviceContext.cpp.o: in function `CLDeviceContext::Initialize()': clDeviceContext.cpp:(.text+0x1b3): undefined reference to `glXGetCurrentContext' /usr/bin/ld: clDeviceContext.cpp:(.text+0x1bd): undefined reference to `glXGetCurrentDisplay' collect2: error: ld returned 1 exit status make[2]: *** [examples/glViewer/CMakeFiles/glViewer.dir/build.make:149: bin/glViewer] Error 1 make[1]: *** [CMakeFiles/Makefile2:4055: examples/glViewer/CMakeFiles/glViewer.dir/all] Error 2 make: *** [Makefile:146: all] Error 2 any ideas? thanks, Tim From marav8 at free.fr Fri Apr 14 15:31:58 2023 From: marav8 at free.fr (marav) Date: Fri, 14 Apr 2023 17:31:58 +0200 Subject: [Slackbuilds-users] OpenSubdiv linking issue In-Reply-To: References: Message-ID: <3b0615ca-debc-688d-ff9c-5b31571f3a25@free.fr> Le 14/04/2023 ? 17:14, Tim Dickson via SlackBuilds-users a ?crit?: > hi all, I'm attempting to build OpenSubdiv with optional deps tbb and > glfw3 and am getting a linking error > > [ 33%] Linking CXX executable ../../bin/glViewer > /usr/bin/ld: > ../common/CMakeFiles/examples_common_gl_obj.dir/clDeviceContext.cpp.o: > in function `CLDeviceContext::Initialize()': > clDeviceContext.cpp:(.text+0x1b3): undefined reference to > `glXGetCurrentContext' > /usr/bin/ld: clDeviceContext.cpp:(.text+0x1bd): undefined reference to > `glXGetCurrentDisplay' > collect2: error: ld returned 1 exit status > make[2]: *** > [examples/glViewer/CMakeFiles/glViewer.dir/build.make:149: > bin/glViewer] Error 1 > make[1]: *** [CMakeFiles/Makefile2:4055: > examples/glViewer/CMakeFiles/glViewer.dir/all] Error 2 > make: *** [Makefile:146: all] Error 2 > > any ideas? > thanks, Tim > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > Hi, Maybe this one https://github.com/PixarAnimationStudios/OpenSubdiv/commit/9079a517.patch -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Fri Apr 14 17:27:46 2023 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 14 Apr 2023 18:27:46 +0100 Subject: [Slackbuilds-users] OpenSubdiv linking issue In-Reply-To: <3b0615ca-debc-688d-ff9c-5b31571f3a25@free.fr> References: <3b0615ca-debc-688d-ff9c-5b31571f3a25@free.fr> Message-ID: <0239b3b4-6f77-e857-09e7-26ec3dc5ebdc@googlemail.com> thanks for the pointer. unfortunately applying that patch doesn't fix the problem. I assume Chris got it working when he updated it, as both it and blender are his. On 14/04/2023 16:31, marav wrote: > Le 14/04/2023 ? 17:14, Tim Dickson via SlackBuilds-users a ?crit?: >> hi all, I'm attempting to build OpenSubdiv with optional deps tbb and >> glfw3 and am getting a linking error >> >> [ 33%] Linking CXX executable ../../bin/glViewer >> /usr/bin/ld: >> ../common/CMakeFiles/examples_common_gl_obj.dir/clDeviceContext.cpp.o: >> in function `CLDeviceContext::Initialize()': >> clDeviceContext.cpp:(.text+0x1b3): undefined reference to >> `glXGetCurrentContext' >> /usr/bin/ld: clDeviceContext.cpp:(.text+0x1bd): undefined reference >> to `glXGetCurrentDisplay' >> collect2: error: ld returned 1 exit status >> make[2]: *** >> [examples/glViewer/CMakeFiles/glViewer.dir/build.make:149: >> bin/glViewer] Error 1 >> make[1]: *** [CMakeFiles/Makefile2:4055: >> examples/glViewer/CMakeFiles/glViewer.dir/all] Error 2 >> make: *** [Makefile:146: all] Error 2 >> >> any ideas? >> thanks, Tim >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > Hi, > > Maybe this one > > https://github.com/PixarAnimationStudios/OpenSubdiv/commit/9079a517.patch > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ -https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Fri Apr 14 18:26:36 2023 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 14 Apr 2023 19:26:36 +0100 Subject: [Slackbuilds-users] VTK Message-ID: 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 From matteo.bernardini at gmail.com Fri Apr 14 18:59:35 2023 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 14 Apr 2023 20:59:35 +0200 Subject: [Slackbuilds-users] VTK In-Reply-To: References: Message-ID: 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 at 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 at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Apr 15 00:55:03 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Apr 2023 07:55:03 +0700 Subject: [Slackbuilds-users] Updates - 20230415.1 Message-ID: Sat Apr 15 00:16:13 UTC 2023 academic/avogadrolibs: Add VTK as optional dependency. academic/bcftools: Updated for version 1.17. academic/bowtie2: Updated for version 2.5.1. academic/fastqc: Updated for version 0.12.1. academic/ngspice: Updated for version 40. academic/pyCRAC: Updated to version 1.5.2; crac_pipeline no longer included (see README) academic/pysam: Updated for version 0.21.0. academic/rpy2: Updated for version 3.5.10. academic/samtools: Updated for version 1.17. audio/MP3Diags: Fix build (qt4.sh). audio/gnome-music: Added (GNOME Music) audio/musikcube: Updated for version 0.99.8. audio/ncmpc: Updated for version 0.48. desktop/gnome-characters: Added (Character map application) desktop/gnome-contacts: Added (Manage your contacts in GNOME) desktop/gnome-font-viewer: Added (GNOME Fonts) desktop/nautilus: Add patch for newer libportal. desktop/nwg-bar: Updated for version 0.1.3. desktop/nwg-displays: Updated for version 0.3.2. desktop/nwg-panel: Updated for version 0.8.4. desktop/nwg-shell-config: Update .info file. development/Bear: Added (gen compilation database for clang tooling) development/MinForth: Added (Transpile Forth to C) development/avrdude: Updated for version 7.1. development/github-cli: Updated for version 2.27.0 development/jupyter-nbclassic: Updated for version 0.5.5. development/jupyter-nbclient: Updated for version 0.7.3. development/jupyter-nbconvert: Updated for version 7.3.1. development/kotlin: Updated for version 1.8.20. development/nodejs: Updated for version 19.9.0. development/php82: Updated for version 8.2.5 development/postman: Updated for version 10.12.13. development/rarian: Updated for version 0.8.2. development/universal-ctags: Updated for version p6.0.20230409.0 development/vscode-bin: Updated for version 1.77.3. development/zulu-openjdk11: Fix build for -current. development/zulu-openjdk17: Fix build for -current. development/zulu-openjdk8: Bump BUILD. games/FlightGear-data: Updated for version 2020.3.18. games/FlightGear: Updated for version 2020.3.18. games/ags: Updated for version 3.6.0.47. games/boosteroid: Updated for version 1.5.4. games/freeciv: Updated for version 3.0.7. games/snes9x: Updated for version 1.62.3. games/wolfmame: Updated for version 0.253. graphics/ART: Updated for version 1.19.3. graphics/catimg: Added (Insanely fast image printing in your term) graphics/eog: Add patch for newer libportal. graphics/graphviz: Updated for version 8.0.2. graphics/mangohud: Updated for version 0.6.9. libraries/SDL2_sound: Added (a sound library add-on for SDL2) libraries/SimGear: Updated for version 2020.3.18. libraries/aqbanking: Updated for version 6.5.4. libraries/glfw3: Updated for version 3.3.8. libraries/grilo-plugins: Added (Plugins using Grilo's API) libraries/grilo: Updated for version 0.3.15. libraries/gwenhywfar: Updated for version 5.10.1. libraries/htslib: Updated for version 1.17. libraries/libcpuid: Updated for version 0.6.3. libraries/libgnomekbd: Added (GNOME keyboard library) libraries/libjodycode: Added (library for tools like jdupes) libraries/libmediaart: Added (Media art extraction library) libraries/python3-rpyc: Updated for version 5.3.1. libraries/python3-zc.lockfile: Updated for version 3.0.post1. libraries/totem-pl-parser: Updated for v 3.26.6. New Maintainer. libraries/tree-sitter: Updated for version 0.20.8. libraries/xmlsec: Updated for version 1.3.0. misc/floating-IPS: Removed. Replaced by fips. multimedia/gnome-video-effects: Added (Video FX for GNOME Cheese) multimedia/munt: Updated for version 2.7.0, new maintainer. multimedia/plexmediaserver: Updated for V. 1.32.0.6918_6f393eda1. multimedia/stremio: Added (The Next Generation Media Center) multimedia/totem: Added (GNOME Videos) multimedia/vlc: Updated for version 3.0.18. New maintainer. network/AdGuardHome: Updated for version 0.107.28. network/brave-browser: update 1.50.114 network/coturn: Updated for version 4.6.2. network/librewolf: Updated for version 111.0. network/neomutt: Updated for version 20230407. network/newsboat: Updated for version 2.31. network/nextcloud-desktop: update 3.8.0 network/ngrok: Fix md5sums. network/onedrive: Updated for version 2.4.23. network/sslscan: Updated for version 2.0.16. network/tailscale: Added (vpn service) network/viber: Updated for version 18.2.0.2. Add snappy to REQUIRES. network/whalebird: Updated for version 5.0.3. network/wireshark: Updated for version 4.0.5. office/LibreOffice: Handle incompatible system boost office/calibre-bin: Updated for version 6.15.1. office/pandoc-bin: update 3.1.2 python/mypy: Updated for version 1.2.0. python/pyelftools: Added (python library for examining ELF files) python/python-mysql-replication: Updated for version 0.31. python/python3-APScheduler: Updated for version 3.10.1. python/python3-Flask-RESTX: Updated for version 1.1.0. python/python3-alembic: Updated for version 1.10.3. python/python3-calver: Added (setuptools ext. for CalVer pkg ver's) python/python3-cattrs: Added (Composable complex class support) python/python3-confuse: Updated for version 2.0.1. python/python3-dotenv: Updated for version 1.0.0. python/python3-exceptiongroup: Added (PEP 654 exception groups) python/python3-flit_scm: Added (PEP 518 build backend library) python/python3-guessit: Updated for version 3.7.1. python/python3-hatchling: Updated for version 1.14.0. python/python3-httpcore: Updated for version 0.17.0. python/python3-inflect: Updated for version 6.0.4. python/python3-jaraco.collections: Updated for version 4.1.0. python/python3-jaraco.functools: Updated for version 3.6.0. python/python3-jaraco.text: Updated for version 3.11.1. python/python3-libtmux: Updated for version 0.21.1. python/python3-markdown-it-py: Updated for version 2.2.0. python/python3-more-itertools: Updated for version 9.1.0. python/python3-nltk: Updated for version 3.8.1. python/python3-pathspec: Updated for version 0.11.1. python/python3-poetry-core: Updated for version 1.5.2. python/python3-pydantic: Updated for version 1.10.7. python/python3-pytube: Updated for version 12.1.3. python/python3-rebulk: Updated for version 3.2.0. python/python3-requests-cache: Added (Persistent cache for requests) python/python3-rich: Updated for version 13.3.3. python/python3-teletype: Added (A cross platform tty library) python/python3-trove-classifiers: Added (PyPI classifier validation) python/python3-url-normalize: Added (URL normalization for Python) python/python3-websocket-client: Updated for version 1.5.1. python/python3-xcffib: Update for 1.3.0 python/tzdata: Updated for version 2023.3. ruby/ruby-build: Updated for version 20230330. system/CPU-X: Updated for version 4.5.3. system/alacritty: Updated for version 0.12.0. system/cdemu-daemon: Fix cdemu-daemon udev rule system/conky: Updated for version 1.19.1. system/epson-inkjet-printer-escpr2: Updated for version 1.1.62. system/fzf: Updated for version 0.39.0. system/gnome-color-manager: Added (GNOME Color Profile Manager) system/gsplus: Added (Apple IIgs emulator) system/ibus-typing-booster: Added (completion input method) system/jdupes: Updated for version 1.22.0. system/jenkins: Updated for version 2.387.2. system/nnn: Updated for version 4.8. system/pax-utils: Added (security audit tools for ELF binaries) system/postgresql: Switch to python3. system/rasdaemon: Added (RAS logging tool) system/slpkg: Updated for version 4.7.8. system/tmuxp: Updated for version 1.27.1. system/xdg-desktop-portal-gnome: Added (GNOME's xdg-desktop-portal) +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From chris.willing at linux.com Sat Apr 15 01:06:06 2023 From: chris.willing at linux.com (Christoph Willing) Date: Sat, 15 Apr 2023 11:06:06 +1000 Subject: [Slackbuilds-users] OpenSubdiv linking issue In-Reply-To: References: Message-ID: <0813c9a2-8d68-7f14-7157-1b0c3f8ae1f7@linux.com> On 15/4/23 01:14, Tim Dickson via SlackBuilds-users wrote: > hi all, I'm attempting to build OpenSubdiv with optional deps tbb and > glfw3 and am getting a linking error > > [ 33%] Linking CXX executable ../../bin/glViewer > /usr/bin/ld: > ../common/CMakeFiles/examples_common_gl_obj.dir/clDeviceContext.cpp.o: > in function `CLDeviceContext::Initialize()': > clDeviceContext.cpp:(.text+0x1b3): undefined reference to > `glXGetCurrentContext' > /usr/bin/ld: clDeviceContext.cpp:(.text+0x1bd): undefined reference to > `glXGetCurrentDisplay' > collect2: error: ld returned 1 exit status > make[2]: *** [examples/glViewer/CMakeFiles/glViewer.dir/build.make:149: > bin/glViewer] Error 1 > make[1]: *** [CMakeFiles/Makefile2:4055: > examples/glViewer/CMakeFiles/glViewer.dir/all] Error 2 > make: *** [Makefile:146: all] Error 2 > > any ideas? > thanks, Tim I have a fix - unfortunately I just missed the cutoff time to submit it for latest SBo updates today :( The fix is to add the line: sed -i -e '/${OPENGL_gl_LIBRARY}/a${OPENGL_glx_LIBRARY}' CMakeLists.txt between the lines: cd $PRGNAM-$SRCVER and: chown -R root:root . chris From chris.willing at linux.com Sat Apr 15 01:46:50 2023 From: chris.willing at linux.com (Christoph Willing) Date: Sat, 15 Apr 2023 11:46:50 +1000 Subject: [Slackbuilds-users] VTK In-Reply-To: References: Message-ID: <0bb53447-b522-705f-570f-99ee026c828d@linux.com> On 15/4/23 04:26, Tim Dickson via SlackBuilds-users wrote: > 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 Interestingly, this exact problem has been raised recently on LQ in the "SBo scripts not building on current" thread. Therefore first question regards whether you're seeing this problem in Slackware-stable or -current? Unfortunately I have tried all combinations (I think) of build flags in clean -stable & -current VMs and have not been able to replicate the problem. I just built it again now without incident in -stable using IMAGING=yes and MPI=yes flags. Therefore the next question is whether you're building in a VM or normal environment. If the latter, how clean is it? chris From dickson.tim at googlemail.com Sat Apr 15 07:13:34 2023 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sat, 15 Apr 2023 08:13:34 +0100 Subject: [Slackbuilds-users] VTK In-Reply-To: <0bb53447-b522-705f-570f-99ee026c828d@linux.com> References: <0bb53447-b522-705f-570f-99ee026c828d@linux.com> Message-ID: <4bc70622-aa7e-bb00-1aef-e093cf1295e4@googlemail.com> On 15/04/2023 02:46, Christoph Willing wrote: > On 15/4/23 04:26, Tim Dickson via SlackBuilds-users wrote: >> 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 > > Interestingly, this exact problem has been raised recently on LQ in > the "SBo scripts not building on current" thread. Therefore first > question regards whether you're seeing this problem in > Slackware-stable or -current? > > Unfortunately I have tried all combinations (I think) of build flags > in clean -stable & -current VMs and have not been able to replicate > the problem. I just built it again now without incident in -stable > using IMAGING=yes and MPI=yes flags. Therefore the next question is > whether you're building in a VM or normal environment. If the latter, > how clean is it? > > > chris > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > I'm running on stable (15.0 64bit) Thanks for looking at this Chris. I have managed to get VTK to build now. My solution was to uninstall the existing (older) version of VTK before creating the newer package. If someone wants to confirm this as a repeatable solution then it may be worth adding a comment to that effect to the readme. regards, Tim From chris.willing at linux.com Sat Apr 15 09:11:49 2023 From: chris.willing at linux.com (Christoph Willing) Date: Sat, 15 Apr 2023 19:11:49 +1000 Subject: [Slackbuilds-users] VTK In-Reply-To: <4bc70622-aa7e-bb00-1aef-e093cf1295e4@googlemail.com> References: <0bb53447-b522-705f-570f-99ee026c828d@linux.com> <4bc70622-aa7e-bb00-1aef-e093cf1295e4@googlemail.com> Message-ID: On 15/4/23 17:13, Tim Dickson via SlackBuilds-users wrote: > I'm running on stable (15.0 64bit) > > Thanks for looking at this Chris. I have managed to get VTK to build now. > My solution was to uninstall the existing (older) version of VTK before > creating the newer package. If someone wants to confirm this as a > repeatable solution then it may be worth adding a comment to that effect > to the readme. > regards, Tim Thanks for finding that Tim. I was able to replicate the problem in a VM with previous VTK installed. I've also posted to LQ requesting your solution be tried. If it works, as seems probable, I'll add it to the README. chris From dhalliwe at rogers.com Sat Apr 15 15:11:55 2023 From: dhalliwe at rogers.com (David Halliwell) Date: Sat, 15 Apr 2023 11:11:55 -0400 Subject: [Slackbuilds-users] Problem/fix for SlackBuild for MP3Diags References: Message-ID: On Thu, 13 Apr 2023, B. Watson wrote: >OK, done. You're right, if there's a qt5 version, that'd be better. ?? I see your changes have gone live. ?? Again, not offering to take over maintenance, but I did decide to look at the upstream revisions Dominik mentioned. There is an MP3Diags-unstable-1.5.02 version available. I was able to modify the previous SlackBuild by changing the package name to MP3Diags-unstable, the version number to 1.5.02, changing qmake to qmake-qt5, lrelease to lrelease-qt5, and finally in the copying stage changing README.TXT to README.md. At that point, the new version built, installed, and ran - and I uninstalled qt-4 to make sure. ?? The MP3Diags-unstable name is hard-coded into the source, so my simple changes needed to use that for the package name. That meant 'upgradepkg' did not recognize it as a replacement for the earlier install of MP3Diags, so I did a removepkg followed by an upgradepkg --install-new. ?? There is probably a better way to handle the odd '-unstable' package name in the source, but at least this indicates that the basic source code is manageable. -- Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From dominik.drobek at o2.pl Sat Apr 15 16:30:53 2023 From: dominik.drobek at o2.pl (Dominik Drobek) Date: Sat, 15 Apr 2023 18:30:53 +0200 Subject: [Slackbuilds-users] Problem/fix for SlackBuild for MP3Diags In-Reply-To: References: Message-ID: <6dd99d46-3dba-a279-1e11-b6c3db309188@o2.pl> W dniu 15.04.2023 o?17:11, David Halliwell pisze: > ?? The MP3Diags-unstable name is hard-coded into the source, so my > simple changes needed to use that for the package name. That meant > 'upgradepkg' did not recognize it as a replacement for the earlier > install of MP3Diags, so I did a removepkg followed by an upgradepkg > --install-new. Yes, the version ported to Qt5 is "unstable". There is no "stable" Qt5 version at the moment - I guess that would be version 1.6.x. And this is problematic, because the "-unstable" suffix is not only hardcoded in the source package, binary name, icons, etc., but also deeper in the source code. For example, "unstable" version is reading configuration from $HOME/.config/Ciobi/Mp3Diags-unstable.conf. This means upgrading from "stable" to "unstable" version (and vice versa) requires manual intervention by the user - otherwise the user settings will be lost. This should be at least mentioned in the README. Handling package name change in the SlackBuild is possible. So all in all, the update is manageable, just not as straightforward as it seems at first glance. Regards, Dominik From slack at giand.it Sat Apr 15 17:47:43 2023 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=) Date: Sat, 15 Apr 2023 19:47:43 +0200 Subject: [Slackbuilds-users] VTK In-Reply-To: References: <0bb53447-b522-705f-570f-99ee026c828d@linux.com> <4bc70622-aa7e-bb00-1aef-e093cf1295e4@googlemail.com> Message-ID: <7bbeb1df-5fd8-2708-019f-1295e3a06bd3@giand.it> Il 15/04/23 11:11, Christoph Willing ha scritto: > On 15/4/23 17:13, Tim Dickson via SlackBuilds-users wrote: > >> I'm running on stable (15.0 64bit) >> >> Thanks for looking at this Chris. I have managed to get VTK to build >> now. >> My solution was to uninstall the existing (older) version of VTK >> before creating the newer package. If someone wants to confirm this >> as a repeatable solution then it may be worth adding a comment to >> that effect to the readme. >> regards, Tim > > Thanks for finding that Tim. > > I was able to replicate the problem in a VM with previous VTK > installed. I've also posted to LQ requesting your solution be tried. > If it works, as seems probable, I'll add it to the README. > > chris > Hi, I use current as default OS, so some days ago I first posted the question in the Ponce's thread in LQ about the same error, that occurred enabling all optional features (IMAGING, MPI, VIEWS, ecc.). I temporary "solved" disabling MPI. This happened always trying to build the new version with previous VTK 9.0.3 installed Following the suggestion given by Chris, today I rebuilt VTK with all features enabled after uninstalling the previous version and I confirm that the build ends successfully. At this point it appears obvious that extended settings require the removal of previous installation. Thanks for these reports! greetings gian -- ********************************************************* Giancarlo Dess? https://www.giand.it Slackware Linux... because it works! ********************************************************* From lramos.prof at yahoo.com.br Sat Apr 15 18:16:47 2023 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Sat, 15 Apr 2023 15:16:47 -0300 Subject: [Slackbuilds-users] VTK In-Reply-To: <7bbeb1df-5fd8-2708-019f-1295e3a06bd3@giand.it> References: <0bb53447-b522-705f-570f-99ee026c828d@linux.com> <4bc70622-aa7e-bb00-1aef-e093cf1295e4@googlemail.com> <7bbeb1df-5fd8-2708-019f-1295e3a06bd3@giand.it> Message-ID: Hi all, confirmed here. First trial gave the error mentioned in the first post, but now, rebuilding the package without VTK installed, then worked perfectly. Options selected in both cases: export IMAGING=yes export MPI=yes export VIEWS=yes I would second vote for including some remark in the README file, as suggested above by a colleague. Only my 2 cents, Luiz Ramos Sao Paulo - Brazil lramos dot prof at yahoo dot com dot br On Sat, Apr 15, 2023 at 07:47:43PM +0200, Giancarlo Dess? wrote: > Il 15/04/23 11:11, Christoph Willing ha scritto: > > On 15/4/23 17:13, Tim Dickson via SlackBuilds-users wrote: > > > > > I'm running on stable (15.0 64bit) > > > > > > Thanks for looking at this Chris. I have managed to get VTK to build > > > now. > > > My solution was to uninstall the existing (older) version of VTK > > > before creating the newer package. If someone wants to confirm this > > > as a repeatable solution then it may be worth adding a comment to > > > that effect to the readme. > > > regards, Tim > > > > Thanks for finding that Tim. > > > > I was able to replicate the problem in a VM with previous VTK installed. > > I've also posted to LQ requesting your solution be tried. If it works, > > as seems probable, I'll add it to the README. > > > > chris > > > Hi, > > I use current as default OS, so some days ago I first posted the question in > the Ponce's thread in LQ about the same error, that occurred enabling all > optional features (IMAGING, MPI, VIEWS, ecc.). I temporary "solved" > disabling MPI. This happened always trying to build the new version with > previous VTK 9.0.3 installed > > Following the suggestion given by Chris, today I rebuilt VTK with all > features enabled after uninstalling the previous version and I confirm that > the build ends successfully. At this point it appears obvious that extended > settings require the removal of previous installation. > > Thanks for these reports! > > greetings > > gian > > -- > ********************************************************* > Giancarlo Dess? > https://www.giand.it > > Slackware Linux... because it works! > ********************************************************* > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From urchlay at slackware.uk Sat Apr 15 19:47:54 2023 From: urchlay at slackware.uk (B. Watson) Date: Sat, 15 Apr 2023 15:47:54 -0400 (EDT) Subject: [Slackbuilds-users] Problem/fix for SlackBuild for MP3Diags In-Reply-To: References: Message-ID: On Sat, 15 Apr 2023, David Halliwell wrote: > ?? There is probably a better way to handle the odd '-unstable' package name in the source, but at least this indicates that the basic source code > is manageable. Separate variables for PRGNAM (the name of the package created) and the the source name (usually we use SRCNAM for this). In the part of the script that extracts the source and cd's into it, use SRCNAM instead of PRGNAM. From heiko.rosemann at web.de Sat Apr 15 21:29:43 2023 From: heiko.rosemann at web.de (Heiko Rosemann) Date: Sat, 15 Apr 2023 23:29:43 +0200 Subject: [Slackbuilds-users] Your avr-libc Slackbuild - I updated it for 2.1.0 plus x Message-ID: Hello Thorsten, Thank You for providing that avr-libc SlackBuild in the first place. I needed support for attiny816/attiny1616, so I put some work into updating avr-libc to 2.1.0 and integrating a couple of (huge: 1 Mio lines...) patches that hit upstream after 2.1.0. My changes are here: https://github.com/SlackBuildsOrg/slackbuilds/compare/master...newHeiko:slackbuilds:avr-libc - builds and runs fine on my Slackware 15.0. Feel free to ignore them or take over whatever you can use. Greetings from the North Sea shore, Heiko -- eMails verschl?sseln mit PGP - privacy is your right! Mein PGP-Key zur Verifizierung: http://pgp.mit.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From chris.willing at linux.com Sat Apr 15 23:54:26 2023 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 16 Apr 2023 09:54:26 +1000 Subject: [Slackbuilds-users] VTK In-Reply-To: References: <0bb53447-b522-705f-570f-99ee026c828d@linux.com> <4bc70622-aa7e-bb00-1aef-e093cf1295e4@googlemail.com> <7bbeb1df-5fd8-2708-019f-1295e3a06bd3@giand.it> Message-ID: <0680e0f9-bc97-b819-c33a-94649d9c63ef@linux.com> Thanks everyone for your inputs. I've submitted an update which contains the relevant warning in the README. I also enabled the IMAGING & VIEWS options by default since they involve no additional dependencies. In fact the IMAGING option was already enabled in the SlackBuild despite the README stating it was off by default. chris From sbo at linuxgalaxy.org Sun Apr 16 21:46:10 2023 From: sbo at linuxgalaxy.org (KB_SBo) Date: Sun, 16 Apr 2023 21:46:10 +0000 Subject: [Slackbuilds-users] Updates - 20230415.1 In-Reply-To: References: Message-ID: <77892c04-c6d1-7fcb-dffb-e1edab796217@linuxgalaxy.org> On 4/14/23 17:55, Willy Sudiarto Raharjo wrote: > system/slpkg: Updated for version 4.7.8. There appears to be a wee typo in slpkg.SlackBuild: root at gandalf:/library/slackware/builds/15.0/system/slpkg# ls -l total 104 -rw-r--r-- 1 beowulf users 301 Jul 4 2022 README -rw-r--r-- 1 beowulf users 432 Apr 9 09:35 doinst.sh -rw-r--r-- 1 beowulf users 939 Jul 4 2022 slack-desc -rw-r--r-- 1 beowulf users 83774 Apr 16 14:21 slpkg-4.7.8.tar.gz -rwxr-xr-x 1 beowulf users 3841 Apr 15 18:33 slpkg.SlackBuild* -rw-r--r-- 1 beowulf users 355 Apr 15 18:33 slpkg.info root at gandalf:/library/slackware/builds/15.0/system/slpkg# ./slpkg.SlackBuild tar: /library/slackware/builds/15.0/system/slpkg/slpkg-.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now The fix: --- /library/slackware/SBo_repository/SBo/system/slpkg/slpkg.SlackBuild 2023-04-15 18:33:27.743134305 -0700 +++ /library/slackware/builds/15.0/system/slpkg/slpkg.SlackBuild 2023-04-16 14:30:34.708134406 -0700 @@ -25,7 +25,7 @@ cd $(dirname $0) ; CWD=$(pwd) PRGNAM=slpkg -ERSION=${VERSION:-4.7.8} +VERSION=${VERSION:-4.7.8} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} -kb From dave at slackbuilds.org Sun Apr 16 22:15:42 2023 From: dave at slackbuilds.org (Dave) Date: Sun, 16 Apr 2023 23:15:42 +0100 Subject: [Slackbuilds-users] Updates - 20230415.1 In-Reply-To: <77892c04-c6d1-7fcb-dffb-e1edab796217@linuxgalaxy.org> References: <77892c04-c6d1-7fcb-dffb-e1edab796217@linuxgalaxy.org> Message-ID: 16/04/23 21:46, KB_SBo : > On 4/14/23 17:55, Willy Sudiarto Raharjo wrote: > > system/slpkg: Updated for version 4.7.8. > > There appears to be a wee typo in slpkg.SlackBuild: > > root at gandalf:/library/slackware/builds/15.0/system/slpkg# ls -l > total 104 > -rw-r--r-- 1 beowulf users 301 Jul 4 2022 README > -rw-r--r-- 1 beowulf users 432 Apr 9 09:35 doinst.sh > -rw-r--r-- 1 beowulf users 939 Jul 4 2022 slack-desc > -rw-r--r-- 1 beowulf users 83774 Apr 16 14:21 slpkg-4.7.8.tar.gz > -rwxr-xr-x 1 beowulf users 3841 Apr 15 18:33 slpkg.SlackBuild* > -rw-r--r-- 1 beowulf users 355 Apr 15 18:33 slpkg.info > root at gandalf:/library/slackware/builds/15.0/system/slpkg# ./slpkg.SlackBuild > tar: /library/slackware/builds/15.0/system/slpkg/slpkg-.tar.gz: Cannot > open: No such file or directory > tar: Error is not recoverable: exiting now > > The fix: > > --- /library/slackware/SBo_repository/SBo/system/slpkg/slpkg.SlackBuild > 2023-04-15 18:33:27.743134305 -0700 > +++ /library/slackware/builds/15.0/system/slpkg/slpkg.SlackBuild > 2023-04-16 14:30:34.708134406 -0700 > @@ -25,7 +25,7 @@ > cd $(dirname $0) ; CWD=$(pwd) > > PRGNAM=slpkg > -ERSION=${VERSION:-4.7.8} > +VERSION=${VERSION:-4.7.8} > BUILD=${BUILD:-1} > TAG=${TAG:-_SBo} > PKGTYPE=${PKGTYPE:-tgz} > > -kb Fixed in my branch. Thanks Dave -- sbo-maintainer-tools (sbolint, sbopkglint): https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt From marav8 at free.fr Sun Apr 16 22:15:44 2023 From: marav8 at free.fr (marav) Date: Mon, 17 Apr 2023 00:15:44 +0200 Subject: [Slackbuilds-users] Updates - 20230415.1 In-Reply-To: <77892c04-c6d1-7fcb-dffb-e1edab796217@linuxgalaxy.org> References: <77892c04-c6d1-7fcb-dffb-e1edab796217@linuxgalaxy.org> Message-ID: <573396c5-62ad-3b1f-039e-8ded8922fa3c@free.fr> Le 16/04/2023 ? 23:46, KB_SBo a ?crit?: > On 4/14/23 17:55, Willy Sudiarto Raharjo wrote: >> system/slpkg: Updated for version 4.7.8. > There appears to be a wee typo in slpkg.SlackBuild: > > root at gandalf:/library/slackware/builds/15.0/system/slpkg# ls -l > total 104 > -rw-r--r-- 1 beowulf users 301 Jul 4 2022 README > -rw-r--r-- 1 beowulf users 432 Apr 9 09:35 doinst.sh > -rw-r--r-- 1 beowulf users 939 Jul 4 2022 slack-desc > -rw-r--r-- 1 beowulf users 83774 Apr 16 14:21 slpkg-4.7.8.tar.gz > -rwxr-xr-x 1 beowulf users 3841 Apr 15 18:33 slpkg.SlackBuild* > -rw-r--r-- 1 beowulf users 355 Apr 15 18:33 slpkg.info > root at gandalf:/library/slackware/builds/15.0/system/slpkg# ./slpkg.SlackBuild > tar: /library/slackware/builds/15.0/system/slpkg/slpkg-.tar.gz: Cannot > open: No such file or directory > tar: Error is not recoverable: exiting now > > The fix: > > --- /library/slackware/SBo_repository/SBo/system/slpkg/slpkg.SlackBuild > 2023-04-15 18:33:27.743134305 -0700 > +++ /library/slackware/builds/15.0/system/slpkg/slpkg.SlackBuild > 2023-04-16 14:30:34.708134406 -0700 > @@ -25,7 +25,7 @@ > cd $(dirname $0) ; CWD=$(pwd) > > PRGNAM=slpkg > -ERSION=${VERSION:-4.7.8} > +VERSION=${VERSION:-4.7.8} > BUILD=${BUILD:-1} > TAG=${TAG:-_SBo} > PKGTYPE=${PKGTYPE:-tgz} > > -kb > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ -https://slackbuilds.org/faq/ > Thx Willy for the fix It was already corrected upstream as I reported it to Dimitris -------------- next part -------------- An HTML attachment was scrubbed... URL: From slack at giand.it Mon Apr 17 16:39:11 2023 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=) Date: Mon, 17 Apr 2023 18:39:11 +0200 Subject: [Slackbuilds-users] Fix a submission in ready queue (therion) Message-ID: Hi, Dave contacted me about an issue occurring in the slackbuild of a new package (therion). I fixed it but I cannot submit the new tarball because it is already in the approved queue. Is it possible to remove it so that it can send the correct version? Thanks Giancarlo -- ********************************************************* Giancarlo Dess? https://www.giand.it Slackware Linux... because it works! ********************************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Mon Apr 17 16:56:31 2023 From: dave at slackbuilds.org (Dave) Date: Mon, 17 Apr 2023 17:56:31 +0100 Subject: [Slackbuilds-users] Fix a submission in ready queue (therion) In-Reply-To: References: Message-ID: 17/04/23 18:39, Giancarlo Dess? : > Hi, > > Dave contacted me about an issue occurring in the slackbuild of a new > package (therion). > > I fixed it but I cannot submit the new tarball because it is already in the > approved queue. Is it possible to remove it so that it can send the correct > version? > > Thanks > > Giancarlo I've now removed it from pending. Dave From slack at giand.it Mon Apr 17 17:11:23 2023 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=) Date: Mon, 17 Apr 2023 19:11:23 +0200 Subject: [Slackbuilds-users] Fix a submission in ready queue (therion) In-Reply-To: References: Message-ID: Il 17/04/23 18:56, Dave ha scritto: > 17/04/23 18:39, > Giancarlo Dess? : >> Hi, >> >> Dave contacted me about an issue occurring in the slackbuild of a new >> package (therion). >> >> I fixed it but I cannot submit the new tarball because it is already in the >> approved queue. Is it possible to remove it so that it can send the correct >> version? >> >> Thanks >> >> Giancarlo > I've now removed it from pending. > > Dave Thanks -- ********************************************************* Giancarlo Dess? https://www.giand.it Slackware Linux... because it works! ********************************************************* From erich.public at protonmail.com Mon Apr 17 17:41:26 2023 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 17 Apr 2023 17:41:26 +0000 Subject: [Slackbuilds-users] games/snes9x requires portaudio? Message-ID: Hello B. Watson, I think snes9x now requires portaudio. Here is a portion of my log without portaudio installed: -- Checking for module 'libpulse' -- Found libpulse, version 15.0 -- Checking for module 'portaudio-2.0' -- No package 'portaudio-2.0' found CMake Error at /usr/share/cmake-3.21/Modules/FindPkgConfig.cmake:562 (message): A required package was not found Call Stack (most recent call first): /usr/share/cmake-3.21/Modules/FindPkgConfig.cmake:784 (_pkg_check_modules_internal) CMakeLists.txt:172 (pkg_check_modules) -- Configuring incomplete, errors occurred! See also "/tmp/slackrepo/etr/slackrepo.NXJvkg/build_snes9x/snes9x-1.62.3/gtk/build/CMakeFiles/CMakeOutput.log". See also "/tmp/slackrepo/etr/slackrepo.NXJvkg/build_snes9x/snes9x-1.62.3/gtk/build/CMakeFiles/CMakeError.log". games/snes9x: snes9x.SlackBuild failed (status 1) 16:26:34 Unmounting chroot ... :-( games/snes9x FAILED )-: After adding portaudio as a dependency, it builds successfully. (My portaudio adds jack as an option dependency - not sure if that matters.) I also build snes9x with option "RETROARCH=no", although I don't have retroarch installed. Erich From urchlay at slackware.uk Tue Apr 18 01:47:55 2023 From: urchlay at slackware.uk (B. Watson) Date: Mon, 17 Apr 2023 21:47:55 -0400 (EDT) Subject: [Slackbuilds-users] games/snes9x requires portaudio? In-Reply-To: References: Message-ID: <63878825-9d3-7051-887d-91c6bdf9aa18@slackware.uk> On Mon, 17 Apr 2023, Erich Ritz wrote: > Hello B. Watson, > > I think snes9x now requires portaudio. Here is a portion of my log without portaudio installed: Ugh. I thought I'd built it at least once without portaudio. Apparently not. > After adding portaudio as a dependency, it builds successfully. (My portaudio adds jack as an option dependency - not sure if that matters.) Probably not. I'll test with portaudio built with & without jack, to make sure. > I also build snes9x with option "RETROARCH=no", although I don't have retroarch installed. I wish someone who does use retroarch would chime in and let me know if the retroarch core even works. It build OK... From urchlay at slackware.uk Tue Apr 18 04:22:14 2023 From: urchlay at slackware.uk (B. Watson) Date: Tue, 18 Apr 2023 00:22:14 -0400 (EDT) Subject: [Slackbuilds-users] games/snes9x requires portaudio? In-Reply-To: References: Message-ID: <9bd6c386-2eea-eab5-73f-bf467f10cefd@slackware.uk> On Mon, 17 Apr 2023, Erich Ritz wrote: > I think snes9x now requires portaudio. Here is a portion of my log without portaudio installed: OK, it doesn't actually require portaudio, but it defaults to building with it and doesn't autodetect when it's missing. I can't see any possible use for portaudio with snes9x on Linux (it might be useful on other platforms)... but I went ahead and made it autodetect, disable if not found. My git branch: https://git.slackbuilds.org/slackbuilds/commit/?h=urchlay&id=b6be393d0d2fd0935a6f28e8b68d82a61ff04196 Thanks for the bug report, BTW. I dunno how that got past me... From dickson.tim at googlemail.com Wed Apr 19 19:57:30 2023 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 19 Apr 2023 20:57:30 +0100 Subject: [Slackbuilds-users] kicade build issue Message-ID: <1abc9b5a-928d-5e80-6cd8-eb857d6a2d82@googlemail.com> I am getting the following error building kicad on vanilla slackware 15.0 64bit (no multilib) [ 92%] Building CXX object plugins/3d/oce/CMakeFiles/s3d_plugin_oce.dir/loadmodel.cpp.o cd /tmp/SBo/kicad-5.1.9/build/plugins/3d/oce && /usr/bin/c++ -DGLM_FORCE_CTOR_INIT -DHAVE_STDINT_H -DKICAD_SCRIPTING -DKICAD_SCRIPTING_ACTION_MENU -DKICAD_SCRIPTING_MODULES -DKICAD_SCRIPTING_WXPYTHON -DKICAD_SPICE -DKICAD_USE_OCC -DUSE_WX_OVERLAY -DWXUSINGDLL -DWX_COMPATIBILITY -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -Ds3d_plugin_oce_EXPORTS -I/tmp/SBo/kicad-5.1.9/include -I/tmp/SBo/kicad-5.1.9/3d-viewer -isystem /usr/include/opencascade -isystem /usr/lib64/wx/include/gtk3-unicode-3.0 -isystem /usr/include/wx-3.0 -Wall -O2 -fPIC -std=c++11 -Wsuggest-override -Werror=vla -pthread -Wshadow -O3 -DNDEBUG -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -std=gnu++11 -MD -MT plugins/3d/oce/CMakeFiles/s3d_plugin_oce.dir/loadmodel.cpp.o -MF CMakeFiles/s3d_plugin_oce.dir/loadmodel.cpp.o.d -o CMakeFiles/s3d_plugin_oce.dir/loadmodel.cpp.o -c /tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp /tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp: In function ?bool processFace(const TopoDS_Face&, DATA&, SGNODE*, std::vector*, Quantity_Color*)?: /tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp:868:64: error: ?class Poly_Triangulation? has no member named ?Nodes?; did you mean ?Node?? ? 868 |???? const TColgp_Array1OfPnt&??? arrPolyNodes = triangulation->Nodes(); | ^~~~~ | Node /tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp:869:73: warning: ?const Poly_Array1OfTriangle& Poly_Triangulation::Triangles() const? is deprecated: Deprecated method, Triangle() should be used instead [-Wdeprecated-declarations] ? 869 |???? const Poly_Array1OfTriangle& arrTriangles = triangulation->Triangles(); ????? | ~~~~~~~~~~~~~~~~~~~~~~~~^~ In file included from /usr/include/opencascade/Poly_ListOfTriangulation.hxx:19, ???????????????? from /usr/include/opencascade/BRep_Tool.hxx:30, ???????????????? from /tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp:57: /usr/include/opencascade/Poly_Triangulation.hxx:330:32: note: declared here ? 330 |?? const Poly_Array1OfTriangle& Triangles() const { return myTriangles; } ????? |??????????????????????????????? ^~~~~~~~~ make[2]: *** [plugins/3d/oce/CMakeFiles/s3d_plugin_oce.dir/build.make:90: plugins/3d/oce/CMakeFiles/s3d_plugin_oce.dir/loadmodel.cpp.o] Error 1 make[2]: Leaving directory '/tmp/SBo/kicad-5.1.9/build' make[1]: *** [CMakeFiles/Makefile2:2328: plugins/3d/oce/CMakeFiles/s3d_plugin_oce.dir/all] Error 2 make[1]: Leaving directory '/tmp/SBo/kicad-5.1.9/build' make: *** [Makefile:166: all] Error 2 All deps are up to date: using build tree as below. kicad 5.1.9-1 k zzzzzzz ( electronic pcb circuit design/layout etc) - temporarily remove wxWidgets and reinstall wxGTK3 then wxPython3 before building. (reinstall wxWidgets after installing) -requires ?wxPython3 3.0.2.0-4 k zzzzzz ?-requires ? wxGTK3 3.0.5-4 k zzzzz ? -requires ?? webkit2gtk 2.40.0-2 k zzzz ?? -requires ??? bubblewrap 0.4.0-1 -no deps k z ??? geoclue2 2.6.0-1 k zzz ??? AVAHI=yes ??? -optional ???? avahi 0.8-7 k zz ???? -requires ? ? ? libdaemon 0.14-1 -no deps k z ??? wpebackend-fdo 1.8.3-1 k zz ??? -requires ???? libwpe 1.14.1-1 -no deps k z ??? xdg-dbus-proxy 0.1.2-1 -no deps k z ??? unifdef 2.12-1 -no deps k z ?ngspice-40-1 k zz ?-requires ? openmpi 4.1.4-1 -no deps? (optional deps not used (slurm)) k z ?OpenCASCADE 7.7.0-2 k zzz ?FFMPEG=yes ?FREEIMAGE=yes ?TBB=yes ?GL2PS=yes ?-requires ? VTK 9.2.6-1 k zz (uninstall previous version before creating package) ? IMAGING=yes ? MPI=yes ? -requires ?? openmpi k z ? FreeImage 3.18.0-1 -no deps k z ? tbb 2020u2-1 -no deps k z ? gl2ps 1.3.7-1 -no deps k z ?glm 0.9.9.5-1 -no deps k z any ideas? regards, Tim From urchlay at slackware.uk Wed Apr 19 20:55:36 2023 From: urchlay at slackware.uk (B. Watson) Date: Wed, 19 Apr 2023 16:55:36 -0400 (EDT) Subject: [Slackbuilds-users] kicade build issue In-Reply-To: <1abc9b5a-928d-5e80-6cd8-eb857d6a2d82@googlemail.com> References: <1abc9b5a-928d-5e80-6cd8-eb857d6a2d82@googlemail.com> Message-ID: On Wed, 19 Apr 2023, Tim Dickson via SlackBuilds-users wrote: > /tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp:868:64: error: 'class > Poly_Triangulation' has no member named 'Nodes'; did you mean 'Node'? > ? 868 |???? const TColgp_Array1OfPnt&??? arrPolyNodes = > triangulation->Nodes(); > | ^~~~~ > | Node Confirmed, I got the same error. In my case I built everything without any extra build options (FFMPEG=yes or such). From erich.public at protonmail.com Thu Apr 20 11:48:03 2023 From: erich.public at protonmail.com (Erich Ritz) Date: Thu, 20 Apr 2023 11:48:03 +0000 Subject: [Slackbuilds-users] kicade build issue In-Reply-To: References: <1abc9b5a-928d-5e80-6cd8-eb857d6a2d82@googlemail.com> Message-ID: ------- Original Message ------- On Wednesday, April 19th, 2023 at 3:55 PM, B. Watson wrote: > > > > > > On Wed, 19 Apr 2023, Tim Dickson via SlackBuilds-users wrote: > > > /tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp:868:64: error: 'class > > Poly_Triangulation' has no member named 'Nodes'; did you mean 'Node'? > > 868 | const TColgp_Array1OfPnt& arrPolyNodes = > > triangulation->Nodes(); > > | ^~~~~ > > | Node > > > Confirmed, I got the same error. In my case I built everything without > any extra build options (FFMPEG=yes or such). Version 5.1.9 is 2 years old. Latest is 7.0.2. Additionally the homepage needs to be updated to https://www.kicad.org/ Perhaps it's been abandoned on SBo? Erich From dave at slackbuilds.org Thu Apr 20 13:04:23 2023 From: dave at slackbuilds.org (Dave) Date: Thu, 20 Apr 2023 14:04:23 +0100 Subject: [Slackbuilds-users] kicade build issue In-Reply-To: References: <1abc9b5a-928d-5e80-6cd8-eb857d6a2d82@googlemail.com> Message-ID: 20/04/23 11:48, Erich Ritz via SlackBuilds-users : > ------- Original Message ------- > On Wednesday, April 19th, 2023 at 3:55 PM, B. Watson wrote: > > > > > > > > > > > > > On Wed, 19 Apr 2023, Tim Dickson via SlackBuilds-users wrote: > > > > > /tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp:868:64: error: 'class > > > Poly_Triangulation' has no member named 'Nodes'; did you mean 'Node'? > > > 868 | const TColgp_Array1OfPnt& arrPolyNodes = > > > triangulation->Nodes(); > > > | ^~~~~ > > > | Node > > > > > > Confirmed, I got the same error. In my case I built everything without > > any extra build options (FFMPEG=yes or such). > > Version 5.1.9 is 2 years old. Latest is 7.0.2. Additionally the homepage needs to be updated to https://www.kicad.org/ > > Perhaps it's been abandoned on SBo? > > Erich > After chatting to the maintainer on IRC, he's agreed to let someone submit an update on his behalf, while he's unable to. Dave From willysr at slackbuilds.org Sat Apr 22 05:01:56 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 22 Apr 2023 12:01:56 +0700 Subject: [Slackbuilds-users] Updates - 20230422.1 Message-ID: <869ebceb-d680-21b7-077a-ee98c58e6d9b@slackbuilds.org> Sat Apr 22 04:39:39 UTC 2023 academic/IGV: Updated for version 2.16.1. academic/R: update 4.3.0 academic/biopython: Updated for version 1.81. academic/calc: Updated for version 2.14.1.3. academic/fet: Updated for version 6.9.0. academic/fiji: Updated for version 20221201_1017. academic/gelemental: Updated for version 2.0.2. academic/hyphy: Updated for version 2.5.49. academic/iqtree: Updated for version 2.2.2.4. academic/jalview: Updated for version 2.11.2.5. academic/labplot2: Updated for version 2.10.0. academic/nco: Updated for version 5.1.5. academic/paml: Updated for version 4.10.6. academic/pamlX: Fix paml docs dir. academic/seaview: treerecs added to REQUIRES. academic/seqkit: Updated for version 2.4.0. academic/spades: Updated for version 3.15.5. academic/treerecs: Added (Treerecs: a tree reconciliation tool) academic/ugene: Updated for version 46.0. audio/DPF-Plugins: Updated for version 1.7. audio/pavucontrol-qt: Added (Qt port of pavucontrol) audio/qpwgraph: Updated for version 0.4.2. audio/rack: Updated for version 2.3.0. audio/sunvox: Updated for version 2.1c. desktop/amiwm: Added (Amiga lookalike X window manager) desktop/dwmblocks: Update README desktop/i3ipc-glib: Added (GLib bindings for i3.) desktop/libqtxdg: Updated for version 3.11.0. desktop/lxqt-panel: Updated for version 1.3.0. desktop/lxqt-themes: Updated for version 1.3.0. desktop/rofi-emoji: Updated for version 3.2.0. desktop/rss-guard: updated for version 4.3.4 development/MinForth: Fix README to pass sbolint. development/ShellCheck-bin: Updated for version 0.9.0. development/android-tools: Updated for version 34.0.0. development/gambas3: Updated for version 3.18.2. development/kicad: Updated for version 7.0.2. development/liberica-jdk-bin: Added (JDK distribution) development/lua-language-server: Updated for version 3.6.18. development/mg-troglobit: Updated for version 3.6. development/mongodb-compass: Updated for version 1.36.3. development/nodejs: Updated for version 20.0.0. development/ophis: Added (cross assembler for 6502) development/postman: Updated for version 10.13.0. development/rust16: Update README. development/universal-ctags: Updated for version p6.0.20230416.0 development/uz80as: Updated for version 2.01. games/minetest: Updated for version 5.7.0. games/minetest_game: Updated for version 5.7.0. games/neverball: Make flags added. Make patch removed. games/openttd: Updated for version 13.1. games/puzzles: Updated for version 20230421.20606f0. games/pychess: Updated for version 1.0.4. games/snes9x: Fix build without portaudio. games/vcmi: Updated for version 1.2.0. games/warzone2100: updated for version 4.3.5 gis/gdal: Update for version 3.6.4. gis/therion: Added (Cave surveying software) graphics/OpenSubdiv: Fix build with glfw3 graphics/gpaint: Updated for version 0.3.4. graphics/grafx2: Updated for version 2.8.3091. graphics/graphviz: Updated for version 8.0.3. graphics/mangohud: Updated for version 0.6.9.1. graphics/qcomicbook: New maintainer. graphics/screengrab: Updated for version 2.6.0. graphics/vuescan: Updated MD5SUMs. libraries/VTK: Update README & options libraries/irrlichtmt: Updated for version 1.9.0mt10. libraries/libfm-qt: Updated for version 1.3.0. libraries/libjodycode: Updated for version 1.1. libraries/liblxqt: Updated for version 1.3.0. libraries/libsoup3: Updated for version 3.4.1. libraries/libzen: Version bump to 0.4.41 libraries/lxqt-build-tools: Update for 0.13.0 libraries/lxqt-notificationd: Updated for version 1.3.0. libraries/lxqt-qtplugin: Updated for version 1.3.0. libraries/lxqt-sudo: Updated for version 1.3.0. libraries/netcdf: Updated for version 4.9.2. libraries/spdlog: Updated for version 1.11.0. libraries/webkit2gtk4.1: Updated for version 2.40.1. libraries/webkit2gtk: Updated for version 2.40.1. multimedia/inputstream.adaptive: Version bump to 20.3.6 multimedia/mpv: Update README multimedia/plexmediaserver: Updated for V. 1.32.0.6973_a787c5a8e. network/AdGuardHome: Updated for version 0.107.29. network/brave-browser: update 1.50.121 network/cmst: Added (Qt frontend for Connman) network/connman: Added (Connection management daemon) network/discord: Version bump to 0.0.26 network/ejabberd: Updated for version 23.04. network/element-desktop: Updated for version 1.11.29. network/gallery-dl: Updated for version 1.25.2. network/nextcloud-desktop: Updated for version 3.8.1. network/signal-desktop: Updated for version 6.15.0. network/slack: Updated for version 4.31.155. network/tor-browser: Updated for version 12.0.5. network/vivaldi: Updated for version 6.0.2979.15. network/yle-dl: Add python3-installer dependency. office/LaTeXML: Added (LaTeX to XML/HTML) office/Logseq: Updated for version 0.9.2. office/calibre-bin: Updated for version 6.16.0. perl/perl-Text-Unidecode: Added (Perl Text::Unidecode module) python/argon2-cffi: Add python3-installer dependency. python/buildbot-badges: Updated for version 3.8.0. python/buildbot-worker: Updated for version 3.8.0. python/buildbot: Updated for version 3.8.0. python/certbot-dns-cloudflare: Updated for version 2.5.0. python/python-jeepney: Add python3-installer dependency. python/python3-Flask-Dance: Add python3-installer dependency. python/python3-flit_core: Remove DEPS, bootstrap process changed. python/python3-flit_scm: Add python3-installer dependency. python/python3-hatch_jupyter_builder: Updated for version 0.8.3. python/python3-mdurl: Add python3-installer dependency. python/python3-pathspec: Add python3-installer dependency. python/python3-seaborn: Add python3-installer dependency. python/python3-threadpoolctl: Add python3-installer dependency. python/python3-tomli_w: Add python3-installer dependency. python/python3-tornado: Updated for version 6.3.0. python/python3-wheel: Added (A built-package format for Python) python/testpath: Add python3-installer dependency. python/typing-extensions: Add python3-installer dependency. system/Iosevka-aile: Updated for version 22.0.2. system/Iosevka-etoile: Updated for version 22.0.2. system/acefile: Added (extract ACE 1.0 and 2.0 archives) system/alacritty: Fix 64bit build. system/borgbackup: Updated for version 1.2.4. system/inotify-info: Added (Linux inotify info reporting app) system/joyce: Updated for version 2.4.1. system/lxqt-config: Updated for version 1.3.0. system/lxqt-globalkeys: Updated for version 1.3.0. system/lxqt-policykit: Updated for version 1.3.0. system/lxqt-session: Updated for version 1.3.0. system/numlockx: New maintainer. system/openzfs: Updated for version 2.1.10. system/osquery-bin: Updated for version 5.8.2. system/pcmanfm-qt: Updated for version 1.3.0. system/qps: Update for version 2.7.0. system/qtxdg-tools: Updated for version 3.11.0. system/redis: Updated for version 7.0.11. system/sarasa-gothic: Updated for version 0.40.5. system/sdltrs: Updated for version 1.2.27, new maintainer. system/slpkg: Fixed typo for version. system/slpkg: Updated for version 4.8.0. system/telegraf: Updated for version 1.26.1. system/torrent-file-editor: Added (Torrent files management). system/trs80-roms: Added (ROM images for use with sdltrs and xtrs) system/xtrs: New maintainer, many changes. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From kjhambrick at gmail.com Sat Apr 22 13:11:52 2023 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 22 Apr 2023 08:11:52 -0500 Subject: [Slackbuilds-users] Some abandoned SlackBuilds In-Reply-To: References: Message-ID: All -- I have successfully built rabbitmq-server-3.11.13 and rabbitmq-c-0.13.0 All I had to do was bump the versions in the .info and .SlackBuild files and make minor adjustments to the files copied to /usr/doc/ However, rabbitmq-server-3.11.13 and rabbitmq-c-0.13.0 require erlang-otp-25.3 and elixir-1.14.4 to build. The erlang-otp and elixr SlackBuilds are maintained by Ryan S. Northrup ( copied here ). The rabbitmq-server.SlackBuild is ( was ) maintained by Andre Barboza ( copied here ) And then ejabberd depends on erlang-otp which is maintained by Alexander Verbovetsky ( also copied here ). Are there any issues with the erlang-otp and elixr updates ? I have just started testing rabbitmq-server and the rabbitmq-c library and won't finish for a week or two, given my home and work duties. I can provide my unmanicured SlackBuilds if they would be helpful but I wanted to check before going down a Rabbit Hole ( pun intended :) Thanks. -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: From alik at ejik.org Sat Apr 22 13:50:52 2023 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 22 Apr 2023 16:50:52 +0300 Subject: [Slackbuilds-users] Some abandoned SlackBuilds In-Reply-To: References: Message-ID: On Sat, Apr 22, 2023 at 08:11:52AM -0500, Konrad J Hambrick wrote: > However, rabbitmq-server-3.11.13 and rabbitmq-c-0.13.0 require > erlang-otp-25.3 and elixir-1.14.4 to build. > And then ejabberd depends on erlang-otp which is maintained by > Alexander Verbovetsky ( also copied here ). > Are there any issues with the erlang-otp and elixr updates ? Ejabberd will be happy with this update. Best regards, Alexander From kjhambrick at gmail.com Sat Apr 22 14:33:58 2023 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 22 Apr 2023 09:33:58 -0500 Subject: [Slackbuilds-users] Some abandoned SlackBuilds In-Reply-To: References: Message-ID: On Sat, Apr 22, 2023 at 8:50?AM Alexander Verbovetsky wrote: > On Sat, Apr 22, 2023 at 08:11:52AM -0500, Konrad J Hambrick wrote: > > > However, rabbitmq-server-3.11.13 and rabbitmq-c-0.13.0 require > > erlang-otp-25.3 and elixir-1.14.4 to build. > > > And then ejabberd depends on erlang-otp which is maintained by > > Alexander Verbovetsky ( also copied here ). > > Are there any issues with the erlang-otp and elixr updates ? > > Ejabberd will be happy with this update. > Thanks Alexander. I'll continue testing and let the list know when I have something :) -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: From lramos.prof at yahoo.com.br Sat Apr 22 23:58:45 2023 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Sat, 22 Apr 2023 20:58:45 -0300 Subject: [Slackbuilds-users] Updates - 20230422.1 In-Reply-To: <869ebceb-d680-21b7-077a-ee98c58e6d9b@slackbuilds.org> References: <869ebceb-d680-21b7-077a-ee98c58e6d9b@slackbuilds.org> Message-ID: Hello, don't know if happens only here, but after spdlog was upgraded (from 1.10.0 to 1.11.0), one program stopped to run, namely, gqrx (from gqrx-sdr). It was a very strange thing because except by a mistake of myself, it seems not to be a dependency of gqrx-sdr, even indirect. Tracing what was happening, what I could find is that a library link, libspdlog.so.1, was missing in the new version. After managing to create one such link, by hand, gqrx worked again. So it seems to be a tricky thing with the new spdlog package. A first file to be checked, I thought, would be doinst.sh, but in a first view, it is autogenerated by makepkg and so there is nothing to fix there. Hope it helps someway, Luiz Ramos Sao Paulo - Brazil lramos dot prof at yahoo dot com dot br On Sat, Apr 22, 2023 at 12:01:56PM +0700, Willy Sudiarto Raharjo wrote: > Sat Apr 22 04:39:39 UTC 2023 > academic/IGV: Updated for version 2.16.1. > academic/R: update 4.3.0 > academic/biopython: Updated for version 1.81. > academic/calc: Updated for version 2.14.1.3. > academic/fet: Updated for version 6.9.0. > academic/fiji: Updated for version 20221201_1017. > academic/gelemental: Updated for version 2.0.2. > academic/hyphy: Updated for version 2.5.49. > academic/iqtree: Updated for version 2.2.2.4. > academic/jalview: Updated for version 2.11.2.5. > academic/labplot2: Updated for version 2.10.0. > academic/nco: Updated for version 5.1.5. > academic/paml: Updated for version 4.10.6. > academic/pamlX: Fix paml docs dir. > academic/seaview: treerecs added to REQUIRES. > academic/seqkit: Updated for version 2.4.0. > academic/spades: Updated for version 3.15.5. > academic/treerecs: Added (Treerecs: a tree reconciliation tool) > academic/ugene: Updated for version 46.0. > audio/DPF-Plugins: Updated for version 1.7. > audio/pavucontrol-qt: Added (Qt port of pavucontrol) > audio/qpwgraph: Updated for version 0.4.2. > audio/rack: Updated for version 2.3.0. > audio/sunvox: Updated for version 2.1c. > desktop/amiwm: Added (Amiga lookalike X window manager) > desktop/dwmblocks: Update README > desktop/i3ipc-glib: Added (GLib bindings for i3.) > desktop/libqtxdg: Updated for version 3.11.0. > desktop/lxqt-panel: Updated for version 1.3.0. > desktop/lxqt-themes: Updated for version 1.3.0. > desktop/rofi-emoji: Updated for version 3.2.0. > desktop/rss-guard: updated for version 4.3.4 > development/MinForth: Fix README to pass sbolint. > development/ShellCheck-bin: Updated for version 0.9.0. > development/android-tools: Updated for version 34.0.0. > development/gambas3: Updated for version 3.18.2. > development/kicad: Updated for version 7.0.2. > development/liberica-jdk-bin: Added (JDK distribution) > development/lua-language-server: Updated for version 3.6.18. > development/mg-troglobit: Updated for version 3.6. > development/mongodb-compass: Updated for version 1.36.3. > development/nodejs: Updated for version 20.0.0. > development/ophis: Added (cross assembler for 6502) > development/postman: Updated for version 10.13.0. > development/rust16: Update README. > development/universal-ctags: Updated for version p6.0.20230416.0 > development/uz80as: Updated for version 2.01. > games/minetest: Updated for version 5.7.0. > games/minetest_game: Updated for version 5.7.0. > games/neverball: Make flags added. Make patch removed. > games/openttd: Updated for version 13.1. > games/puzzles: Updated for version 20230421.20606f0. > games/pychess: Updated for version 1.0.4. > games/snes9x: Fix build without portaudio. > games/vcmi: Updated for version 1.2.0. > games/warzone2100: updated for version 4.3.5 > gis/gdal: Update for version 3.6.4. > gis/therion: Added (Cave surveying software) > graphics/OpenSubdiv: Fix build with glfw3 > graphics/gpaint: Updated for version 0.3.4. > graphics/grafx2: Updated for version 2.8.3091. > graphics/graphviz: Updated for version 8.0.3. > graphics/mangohud: Updated for version 0.6.9.1. > graphics/qcomicbook: New maintainer. > graphics/screengrab: Updated for version 2.6.0. > graphics/vuescan: Updated MD5SUMs. > libraries/VTK: Update README & options > libraries/irrlichtmt: Updated for version 1.9.0mt10. > libraries/libfm-qt: Updated for version 1.3.0. > libraries/libjodycode: Updated for version 1.1. > libraries/liblxqt: Updated for version 1.3.0. > libraries/libsoup3: Updated for version 3.4.1. > libraries/libzen: Version bump to 0.4.41 > libraries/lxqt-build-tools: Update for 0.13.0 > libraries/lxqt-notificationd: Updated for version 1.3.0. > libraries/lxqt-qtplugin: Updated for version 1.3.0. > libraries/lxqt-sudo: Updated for version 1.3.0. > libraries/netcdf: Updated for version 4.9.2. > libraries/spdlog: Updated for version 1.11.0. > libraries/webkit2gtk4.1: Updated for version 2.40.1. > libraries/webkit2gtk: Updated for version 2.40.1. > multimedia/inputstream.adaptive: Version bump to 20.3.6 > multimedia/mpv: Update README > multimedia/plexmediaserver: Updated for V. 1.32.0.6973_a787c5a8e. > network/AdGuardHome: Updated for version 0.107.29. > network/brave-browser: update 1.50.121 > network/cmst: Added (Qt frontend for Connman) > network/connman: Added (Connection management daemon) > network/discord: Version bump to 0.0.26 > network/ejabberd: Updated for version 23.04. > network/element-desktop: Updated for version 1.11.29. > network/gallery-dl: Updated for version 1.25.2. > network/nextcloud-desktop: Updated for version 3.8.1. > network/signal-desktop: Updated for version 6.15.0. > network/slack: Updated for version 4.31.155. > network/tor-browser: Updated for version 12.0.5. > network/vivaldi: Updated for version 6.0.2979.15. > network/yle-dl: Add python3-installer dependency. > office/LaTeXML: Added (LaTeX to XML/HTML) > office/Logseq: Updated for version 0.9.2. > office/calibre-bin: Updated for version 6.16.0. > perl/perl-Text-Unidecode: Added (Perl Text::Unidecode module) > python/argon2-cffi: Add python3-installer dependency. > python/buildbot-badges: Updated for version 3.8.0. > python/buildbot-worker: Updated for version 3.8.0. > python/buildbot: Updated for version 3.8.0. > python/certbot-dns-cloudflare: Updated for version 2.5.0. > python/python-jeepney: Add python3-installer dependency. > python/python3-Flask-Dance: Add python3-installer dependency. > python/python3-flit_core: Remove DEPS, bootstrap process changed. > python/python3-flit_scm: Add python3-installer dependency. > python/python3-hatch_jupyter_builder: Updated for version 0.8.3. > python/python3-mdurl: Add python3-installer dependency. > python/python3-pathspec: Add python3-installer dependency. > python/python3-seaborn: Add python3-installer dependency. > python/python3-threadpoolctl: Add python3-installer dependency. > python/python3-tomli_w: Add python3-installer dependency. > python/python3-tornado: Updated for version 6.3.0. > python/python3-wheel: Added (A built-package format for Python) > python/testpath: Add python3-installer dependency. > python/typing-extensions: Add python3-installer dependency. > system/Iosevka-aile: Updated for version 22.0.2. > system/Iosevka-etoile: Updated for version 22.0.2. > system/acefile: Added (extract ACE 1.0 and 2.0 archives) > system/alacritty: Fix 64bit build. > system/borgbackup: Updated for version 1.2.4. > system/inotify-info: Added (Linux inotify info reporting app) > system/joyce: Updated for version 2.4.1. > system/lxqt-config: Updated for version 1.3.0. > system/lxqt-globalkeys: Updated for version 1.3.0. > system/lxqt-policykit: Updated for version 1.3.0. > system/lxqt-session: Updated for version 1.3.0. > system/numlockx: New maintainer. > system/openzfs: Updated for version 2.1.10. > system/osquery-bin: Updated for version 5.8.2. > system/pcmanfm-qt: Updated for version 1.3.0. > system/qps: Update for version 2.7.0. > system/qtxdg-tools: Updated for version 3.11.0. > system/redis: Updated for version 7.0.11. > system/sarasa-gothic: Updated for version 0.40.5. > system/sdltrs: Updated for version 1.2.27, new maintainer. > system/slpkg: Fixed typo for version. > system/slpkg: Updated for version 4.8.0. > system/telegraf: Updated for version 1.26.1. > system/torrent-file-editor: Added (Torrent files management). > system/trs80-roms: Added (ROM images for use with sdltrs and xtrs) > system/xtrs: New maintainer, many changes. > +--------------------------+ > > > -- > Willy Sudiarto Raharjo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From northrup at yellowapple.us Sun Apr 23 21:45:03 2023 From: northrup at yellowapple.us (Ryan S. Northrup ("RyNo")) Date: Sun, 23 Apr 2023 14:45:03 -0700 Subject: [Slackbuilds-users] Some abandoned SlackBuilds In-Reply-To: References: Message-ID: <5757e2b1-4302-517d-103c-3515ffc85cac@yellowapple.us> Howdy! No objections to updating erlang-otp or elixir; I hadn't gotten around to it only because I nowadays prefer version managers (like asdf) or Docker/Podman containers for my own Erlang/Elixir usage over installing them system-wide. If it's just a version bump, you've got a thumbs up from me (or I'll do it tonight). I also at one point maintained the couchdb Slackbuild, which was another reason for holding back the erlang Slackbuild (CouchDB likes to put hard caps on supported Erlang versions that require annoying patching to circumvent), but CouchDB itself never ended up with a 15.0 Slackbuild anyway (upstream packaging changes made that infeasible), so there's no blocker there anymore, either. Thanks, -- Ryan S. Northrup ("RyNo") northrup at yellowapple.us On 4/22/23 06:11, Konrad J Hambrick wrote: > All -- > > I have successfully built rabbitmq-server-3.11.13 and?rabbitmq-c-0.13.0 > > All I had to do was bump the?versions in the?.info and .SlackBuild files > and make minor adjustments to the files copied to /usr/doc/ > > However, rabbitmq-server-3.11.13 and rabbitmq-c-0.13.0 > require?erlang-otp-25.3 and?elixir-1.14.4 to build. > > The erlang-otp and elixr?SlackBuilds are maintained by?Ryan S. Northrup > ( copied here ). > > The rabbitmq-server.SlackBuild is ( was ) maintained by?Andre Barboza ( > copied here ) > > And then?ejabberd depends on erlang-otp which is maintained by Alexander > Verbovetsky ( also copied here ). > > Are there any issues with the erlang-otp and elixr updates ? > > I have just started testing rabbitmq-server and the rabbitmq-c library > and won't finish for a week or two, given my home and work duties. > > I can provide my?unmanicured SlackBuilds if they would be helpful but I > wanted?to?check before going down a?Rabbit Hole ( pun intended :) > Thanks. > > -- kjh > > > From sbo at linuxgalaxy.org Mon Apr 24 00:13:07 2023 From: sbo at linuxgalaxy.org (KB_SBo) Date: Mon, 24 Apr 2023 00:13:07 +0000 Subject: [Slackbuilds-users] qemu updates roadmap Message-ID: <6f165e62-f59a-0500-1e30-3be6ad9736f8@linuxgalaxy.org> 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 From sultmhoor at gmail.com Mon Apr 24 02:37:45 2023 From: sultmhoor at gmail.com (Kevin Bryant) Date: Sun, 23 Apr 2023 22:37:45 -0400 Subject: [Slackbuilds-users] Mojolicious slackbuild Message-ID: Hello all, The perl-Mojolicious slackbuild is kind of old, and I've emailed the maintainer a few times to perhaps update it without any response. Are they listening to this list? Thanks, Kevin Bryant From urchlay at slackware.uk Mon Apr 24 05:37:30 2023 From: urchlay at slackware.uk (B. Watson) Date: Mon, 24 Apr 2023 01:37:30 -0400 (EDT) Subject: [Slackbuilds-users] Mojolicious slackbuild In-Reply-To: References: Message-ID: <8cb3725-799-e98b-39f5-ceac52d3ea9b@slackware.uk> On Sun, 23 Apr 2023, Kevin Bryant wrote: > Hello all, > The perl-Mojolicious slackbuild is kind of old, and I've emailed the > maintainer a few times to perhaps update it without any response. Are > they listening to this list? FWIW, the maintainer (Andreas Guldstrand) hasn't been active on SBo in several years. Last activity from the git log: commit 430be129a69575eeaf2177f63cc9c012704eed1b Author: Andreas Guldstrand Date: Sat Apr 27 15:56:10 2019 +0200 system/sbotools: Updated for version 2.7. That was 4 years ago. If you've sent email and not gotten a response after a week or two, feel free to take over the build. Unless Andreas Guldstrand sees this message and responds... From kjhambrick at gmail.com Mon Apr 24 09:56:24 2023 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Mon, 24 Apr 2023 04:56:24 -0500 Subject: [Slackbuilds-users] Some abandoned SlackBuilds In-Reply-To: <5757e2b1-4302-517d-103c-3515ffc85cac@yellowapple.us> References: <5757e2b1-4302-517d-103c-3515ffc85cac@yellowapple.us> Message-ID: On Sun, Apr 23, 2023 at 4:45?PM Ryan S. Northrup ("RyNo") < northrup at yellowapple.us> wrote: > Howdy! > > No objections to updating erlang-otp or elixir; I hadn't gotten around > to it only because I nowadays prefer version managers (like asdf) or > Docker/Podman containers for my own Erlang/Elixir usage over installing > them system-wide. If it's just a version bump, you've got a thumbs up > from me (or I'll do it tonight). > > I also at one point maintained the couchdb Slackbuild, which was another > reason for holding back the erlang Slackbuild (CouchDB likes to put hard > caps on supported Erlang versions that require annoying patching to > circumvent), but CouchDB itself never ended up with a 15.0 Slackbuild > anyway (upstream packaging changes made that infeasible), so there's no > blocker there anymore, either. > > Thanks, > -- > Ryan S. Northrup ("RyNo") > northrup at yellowapple.us RyNo -- To create new .SlackBuild and .info files, I copied the original files to *.SlackBuild-${OLD_VERSION} and *.info-${OLD_VERSION} and edited the original files. Not sure it will be helpful but attached are diffs for {erlang-otp,elixir}.{info,SlackBuild} Don't trust my MD5SUMS. I updated them but did not really do anything beyond regenerating the CheckSums on the DOWNLOADs. HTH and Thanks ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- --- erlang-otp.info-23.2 2023-01-01 06:49:43.243486293 -0600 +++ erlang-otp.info 2023-04-17 16:08:06.796813607 -0500 @@ -1,10 +1,10 @@ PRGNAM="erlang-otp" -VERSION="23.2" +VERSION="25.3" HOMEPAGE="https://www.erlang.org" -DOWNLOAD="https://erlang.org/download/otp_src_23.2.tar.gz \ - https://erlang.org/download/otp_doc_man_23.2.tar.gz" -MD5SUM="e315f59eb9e420a0e469c09649f4303f \ - cfef029c3d4d6acf2cc04f8589002ecd" +DOWNLOAD="https://erlang.org/download/otp_src_25.3.tar.gz \ + https://erlang.org/download/otp_doc_man_25.3.tar.gz" +MD5SUM="0bd0f04da31ce22248edfd7f7cc09cde \ + 8426ad3182c14322a2f6d116250bf368" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -------------- next part -------------- --- erlang-otp.SlackBuild-23.2 2023-01-01 06:49:43.243486293 -0600 +++ erlang-otp.SlackBuild 2023-04-17 16:34:36.493725676 -0500 @@ -26,7 +26,7 @@ cd $(dirname $0) ; CWD=$(pwd) PRGNAM=erlang-otp -VERSION=${VERSION:-23.2} +VERSION=${VERSION:-25.3} BUILD=${BUILD:-2} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} @@ -104,9 +104,23 @@ chown -R root:root $PKG/usr/lib${LIBDIRSUFFIX}/erlang chmod -R u+w,go+r-w,a-s $PKG/usr/lib${LIBDIRSUFFIX}/erlang +# kjh was here +# +# mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION +# ( cd $PKG/usr/lib${LIBDIRSUFFIX}/erlang +# mv COPYRIGHT README.md $PKG/usr/doc/$PRGNAM-$VERSION ) + mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION -( cd $PKG/usr/lib${LIBDIRSUFFIX}/erlang - mv COPYRIGHT README.md $PKG/usr/doc/$PRGNAM-$VERSION ) +( cd $TMP/$SRC_NAME_VERSION + cp -va AUTHORS \ + CONTRIBUTING.md \ + HOWTO \ + LICENSE.txt \ + OTP_VERSION \ + README.md $PKG/usr/doc/$PRGNAM-$VERSION/ +) +# kjh was there +# cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \ -------------- next part -------------- --- elixir.SlackBuild-1.11.3 2022-03-11 15:05:40.815890711 -0600 +++ elixir.SlackBuild 2023-04-17 16:54:09.448660796 -0500 @@ -29,7 +29,7 @@ cd $(dirname $0) ; CWD=$(pwd) PRGNAM=elixir -VERSION=${VERSION:-1.11.3} +VERSION=${VERSION:-1.14.4} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} -------------- next part -------------- --- elixir.info-1.11.3 2022-03-11 15:05:40.815890711 -0600 +++ elixir.info 2023-04-17 16:56:51.506651832 -0500 @@ -1,8 +1,8 @@ PRGNAM="elixir" -VERSION="1.11.3" +VERSION="1.14.4" HOMEPAGE="https://elixir-lang.org" -DOWNLOAD="https://github.com/elixir-lang/elixir/archive/v1.11.3/elixir-1.11.3.tar.gz" -MD5SUM="0319a8428c647cdbc373312a5c25fb5e" +DOWNLOAD="https://github.com/elixir-lang/elixir/archive/v1.14.4/elixir-1.14.4.tar.gz" +MD5SUM="ab180ed84351af44ba1454fdda5d4424" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="erlang-otp" From northrup at yellowapple.us Mon Apr 24 10:27:38 2023 From: northrup at yellowapple.us (Ryan S. Northrup ("RyNo")) Date: Mon, 24 Apr 2023 03:27:38 -0700 Subject: [Slackbuilds-users] Some abandoned SlackBuilds In-Reply-To: References: <5757e2b1-4302-517d-103c-3515ffc85cac@yellowapple.us> Message-ID: On 4/24/23 02:56, Konrad J Hambrick wrote: > RyNo -- > > To create new .SlackBuild and .info files, I copied the original files > to *.SlackBuild-${OLD_VERSION} and *.info-${OLD_VERSION} and edited > the?original files. > > Not sure it will be helpful but attached are diffs for > {erlang-otp,elixir}.{info,SlackBuild} > > Don't trust my MD5SUMS. > > I updated them but did not really do anything beyond regenerating the > CheckSums on the DOWNLOADs. > > HTH and Thanks ! > > -- kjh Received, and thank *you*! I'll test and submit 'em as soon as I've got a moment. Thanks, -- Ryan S. Northrup ("RyNo") northrup at yellowapple.us From slackalaxy at gmail.com Mon Apr 24 13:18:55 2023 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 24 Apr 2023 16:18:55 +0300 Subject: [Slackbuilds-users] Microsoft fonts Message-ID: 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 From matteo.bernardini at gmail.com Mon Apr 24 13:24:20 2023 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 24 Apr 2023 15:24:20 +0200 Subject: [Slackbuilds-users] Microsoft fonts In-Reply-To: References: Message-ID: 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 at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marav8 at free.fr Mon Apr 24 13:50:22 2023 From: marav8 at free.fr (marav) Date: Mon, 24 Apr 2023 15:50:22 +0200 Subject: [Slackbuilds-users] Microsoft fonts In-Reply-To: References: Message-ID: <6C485958-85A6-4311-8BCE-E0ED325B97F2@free.fr> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo-ms-social.png Type: image/png Size: 449 bytes Desc: not available URL: From slackalaxy at gmail.com Mon Apr 24 13:52:50 2023 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 24 Apr 2023 16:52:50 +0300 Subject: [Slackbuilds-users] Microsoft fonts In-Reply-To: References: Message-ID: hi, there's a license.rtf file in the Windows 11 ISO, which I uploaded with the slackbuild: https://github.com/slackalaxy/misc/tree/master/preliminary/microsoft-fonts-win11 That script is pretty much inspired by what Arch linux does: https://aur.archlinux.org/packages/ttf-ms-win11-auto I even played with httpdirfs to mount the ISO remotely, but decided it would be too much... about the Office ones, I need to search. -petar On Mon, 24 Apr 2023 at 16:24, Matteo Bernardini wrote: > > 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 at 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 at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From slackalaxy at gmail.com Mon Apr 24 14:01:20 2023 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 24 Apr 2023 17:01:20 +0300 Subject: [Slackbuilds-users] Microsoft fonts In-Reply-To: <6C485958-85A6-4311-8BCE-E0ED325B97F2@free.fr> References: <6C485958-85A6-4311-8BCE-E0ED325B97F2@free.fr> Message-ID: yep, I also just found this. However, the script does not redistribute them -- I do not intent to host them anywhere. Also, there's a clause there about converting to different formats, being prohibited. The webcore fonts are Microsoft's fonts, right? And its slackbuild does this, if fontforge is installed, isn't it so? For cambria? -p On Mon, 24 Apr 2023 at 16:50, marav wrote: > Redistribution and extended rights > > Apart from the document embedding rights described previously, you may not > redistribute the Windows fonts. You may not copy them to other computers or > servers, and you may not convert them to other formats, including bitmap > formats, or modify them. > > > Font redistribution FAQ - Typography > > learn.microsoft.com > > [image: logo-ms-social.png] > > > > > Le 24 avr. 2023 ? 15:24, Matteo Bernardini > a ?crit : > > ? > 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 < > slackalaxy at gmail.com> 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 at 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 at 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 at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo-ms-social.png Type: image/png Size: 449 bytes Desc: not available URL: From matteo.bernardini at gmail.com Mon Apr 24 14:41:47 2023 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 24 Apr 2023 16:41:47 +0200 Subject: [Slackbuilds-users] Microsoft fonts In-Reply-To: References: <6C485958-85A6-4311-8BCE-E0ED325B97F2@free.fr> Message-ID: 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackalaxy at gmail.com Mon Apr 24 14:46:15 2023 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 24 Apr 2023 17:46:15 +0300 Subject: [Slackbuilds-users] Microsoft fonts In-Reply-To: References: <6C485958-85A6-4311-8BCE-E0ED325B97F2@free.fr> Message-ID: 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 at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From matteo.bernardini at gmail.com Mon Apr 24 14:49:15 2023 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 24 Apr 2023 16:49:15 +0200 Subject: [Slackbuilds-users] Microsoft fonts In-Reply-To: References: <6C485958-85A6-4311-8BCE-E0ED325B97F2@free.fr> Message-ID: 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 at 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 at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackalaxy at gmail.com Mon Apr 24 14:54:40 2023 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 24 Apr 2023 17:54:40 +0300 Subject: [Slackbuilds-users] Microsoft fonts In-Reply-To: References: <6C485958-85A6-4311-8BCE-E0ED325B97F2@free.fr> Message-ID: ok, fair enough. That's why I asked -p 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 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 at 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 at 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 at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From slackalaxy at gmail.com Mon Apr 24 14:56:28 2023 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 24 Apr 2023 17:56:28 +0300 Subject: [Slackbuilds-users] Microsoft fonts In-Reply-To: References: <6C485958-85A6-4311-8BCE-E0ED325B97F2@free.fr> Message-ID: 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 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 at 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 at 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 at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From matteo.bernardini at gmail.com Mon Apr 24 15:23:00 2023 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 24 Apr 2023 17:23:00 +0200 Subject: [Slackbuilds-users] Microsoft fonts In-Reply-To: References: <6C485958-85A6-4311-8BCE-E0ED325B97F2@free.fr> Message-ID: 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 < > slackalaxy at 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 at 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 at 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 at 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 at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Mon Apr 24 18:07:59 2023 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 24 Apr 2023 20:07:59 +0200 Subject: [Slackbuilds-users] Microsoft fonts In-Reply-To: References: <6C485958-85A6-4311-8BCE-E0ED325B97F2@free.fr> Message-ID: Il giorno lun 24 apr 2023 alle ore 17:23 Matteo Bernardini < matteo.bernardini at gmail.com> ha scritto: > keeped > BTW, sorry for my terrible english... Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From ml at mareichelt.com Mon Apr 24 18:26:29 2023 From: ml at mareichelt.com (Markus Reichelt) Date: Mon, 24 Apr 2023 20:26:29 +0200 Subject: [Slackbuilds-users] Updates - 20230422.1 In-Reply-To: <869ebceb-d680-21b7-077a-ee98c58e6d9b@slackbuilds.org> References: <869ebceb-d680-21b7-077a-ee98c58e6d9b@slackbuilds.org> Message-ID: <20230424182629.GB3798@pc21.mareichelt.com> * Willy Sudiarto Raharjo wrote: > system/openzfs: Updated for version 2.1.10. heads up, openzfs-2.1.11 has been released to fix a possible data corruption bug, see https://github.com/openzfs/zfs/issues/14753 I'll submit an update soon-ish. Markus From sultmhoor at gmail.com Mon Apr 24 21:05:14 2023 From: sultmhoor at gmail.com (Kevin Bryant) Date: Mon, 24 Apr 2023 17:05:14 -0400 Subject: [Slackbuilds-users] Mojolicious slackbuild In-Reply-To: <8cb3725-799-e98b-39f5-ceac52d3ea9b@slackware.uk> References: <8cb3725-799-e98b-39f5-ceac52d3ea9b@slackware.uk> Message-ID: Thanks! I've updated it to 9.31 and sent it in. That kind of clears up the logjam for a few other mojolicious plugins and minion that I'll be uploading soon. Kevin Bryant On Mon, Apr 24, 2023 at 1:37?AM B. Watson wrote: > > > > On Sun, 23 Apr 2023, Kevin Bryant wrote: > > > Hello all, > > The perl-Mojolicious slackbuild is kind of old, and I've emailed the > > maintainer a few times to perhaps update it without any response. Are > > they listening to this list? > > FWIW, the maintainer (Andreas Guldstrand) hasn't been active on SBo in > several years. Last activity from the git log: > > commit 430be129a69575eeaf2177f63cc9c012704eed1b > Author: Andreas Guldstrand > Date: Sat Apr 27 15:56:10 2019 +0200 > > system/sbotools: Updated for version 2.7. > > That was 4 years ago. > > If you've sent email and not gotten a response after a week or two, > feel free to take over the build. Unless Andreas Guldstrand sees this > message and responds... > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From dev at iotib.net Tue Apr 25 11:56:18 2023 From: dev at iotib.net (Charadon) Date: Tue, 25 Apr 2023 07:56:18 -0400 Subject: [Slackbuilds-users] Including runit script with slackbuild? Message-ID: Hey all, I want to include runit scripts with my earlyoom slackbuild. What's the policy with it? Do I have to include an environment variable like RUNIT=YES so the user can choose if they want it, or can I just include it? - Charadon From kristofru at gmail.com Thu Apr 27 06:39:14 2023 From: kristofru at gmail.com (Chris Abela) Date: Thu, 27 Apr 2023 08:39:14 +0200 Subject: [Slackbuilds-users] Including runit script with slackbuild? In-Reply-To: References: Message-ID: <49280c73-7381-86c8-1b58-ffbb7cea1e7a@gmail.com> Hi, I suggest setting up or updating a separate repository of runit scripts, as I suspect that only a handful of us use runit. This is my modest contribution: https://gitlab.com/chrisabela/runit_scripts_for_slackware. Feel free to take the lead, fork, follow, copy, contribute or whatever. Then you can refer to a runit script repository in the docs, say as comment in the slackbuild or in the README file. We all like comprehensive documentation. Chris On 25/04/2023 13:56, Charadon via SlackBuilds-users wrote: > Hey all, > > I want to include runit scripts with my earlyoom slackbuild. What's > the policy with it? Do I have to include an environment variable like > RUNIT=YES so the user can choose if they want it, or can I just > include it? > > - Charadon > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From slackbuilds at schoepfer.info Fri Apr 28 08:16:12 2023 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 28 Apr 2023 10:16:12 +0200 Subject: [Slackbuilds-users] ngspice does not depend on openmpi In-Reply-To: <4309a711c4b15f9511424da9941239c1@schoepfer.info> References: <4309a711c4b15f9511424da9941239c1@schoepfer.info> Message-ID: <689d362df4413772786a7faa6ea28022@schoepfer.info> Hi, mainterner cc'ed, openmpi is no hard dependency of ngspice, the buildscript builds with and without installed openmpi, and i can happily user ngspice without installed openmpi. Please remove openmpi from ngspice.info:required. Cheers, Johannes From chris.willing at linux.com Fri Apr 28 11:32:05 2023 From: chris.willing at linux.com (Christoph Willing) Date: Fri, 28 Apr 2023 21:32:05 +1000 Subject: [Slackbuilds-users] ngspice does not depend on openmpi In-Reply-To: <689d362df4413772786a7faa6ea28022@schoepfer.info> References: <4309a711c4b15f9511424da9941239c1@schoepfer.info> <689d362df4413772786a7faa6ea28022@schoepfer.info> Message-ID: <69d314b7-5370-f7af-e3e6-ea96eeaeb657@linux.com> On 28/4/23 18:16, Franzen via SlackBuilds-users wrote: > Hi, > > mainterner cc'ed, > openmpi is no hard dependency of ngspice, the buildscript > builds with and without installed openmpi, and i can happily user > ngspice without installed openmpi. > Please remove openmpi from ngspice.info:required. > > I don't use ngspice, so have no special interest in it (and no knowledge about its prerequisites). However, as a general principle, I don't think that just because a SlackBuild will complete without some other SlackBuild as dependency (here openmpi), that the "dependency" should be precluded. Who knows what functionality it provides when it is included? Maybe that functionality is not useful to everyone but it may be useful to some. I don't believe we should be generating minimalist libraries or applications, rather products containing as many features as possible which the authors have made possible. End users should be able to expect whatever functionality the product is able to provide, not some subset of the possible functionality. People who know what they're doing and who want some minimalist build are free to leave out whatever they want and edit their personal versions of SlackBuilds accordingly. Please don't insist that everyone is bound by the same idea. chris From slackbuilds at schoepfer.info Fri Apr 28 12:51:57 2023 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 28 Apr 2023 14:51:57 +0200 Subject: [Slackbuilds-users] ngspice does not depend on openmpi In-Reply-To: <69d314b7-5370-f7af-e3e6-ea96eeaeb657@linux.com> References: <4309a711c4b15f9511424da9941239c1@schoepfer.info> <689d362df4413772786a7faa6ea28022@schoepfer.info> <69d314b7-5370-f7af-e3e6-ea96eeaeb657@linux.com> Message-ID: > I don't use ngspice, so have no special interest in it (and no > knowledge about its prerequisites). > > However, as a general principle, I don't think that just because a > SlackBuild will complete without some other SlackBuild as dependency > (here openmpi), that the "dependency" should be precluded. Who knows > what functionality it provides when it is included? Maybe that > functionality is not useful to everyone but it may be useful to some. > > I don't believe we should be generating minimalist libraries or > applications, rather products containing as many features as possible > which the authors have made possible. End users should be able to > expect whatever functionality the product is able to provide, not some > subset of the possible functionality. > > People who know what they're doing and who want some minimalist build > are free to leave out whatever they want and edit their personal > versions of SlackBuilds accordingly. Please don't insist that everyone > is bound by the same idea. Thanks for your feedback. In this case, openmpi doesn't even change the binary, it does nothing at compile-time. It also does nothing if available on a single device. Ngspice might use openmpi if it's available and configured to use multiple devices in a network. Despite i lean towards minimal dependencies, this dependency feels just wrong, it feels like e.g. a dependency on one more display as it might be a comfortable feature. I would mention openmpi in the README anyway, i hope the maintainer gives some feedback too. Johannes From fellype at gmail.com Fri Apr 28 13:14:00 2023 From: fellype at gmail.com (Fellype) Date: Fri, 28 Apr 2023 10:14:00 -0300 Subject: [Slackbuilds-users] ngspice does not depend on openmpi In-Reply-To: References: <4309a711c4b15f9511424da9941239c1@schoepfer.info> <689d362df4413772786a7faa6ea28022@schoepfer.info> <69d314b7-5370-f7af-e3e6-ea96eeaeb657@linux.com> Message-ID: Em sex., 28 de abr. de 2023 ?s 09:52, Franzen via SlackBuilds-users < slackbuilds-users at slackbuilds.org> escreveu: > > I don't use ngspice, so have no special interest in it (and no > > knowledge about its prerequisites). > > > > However, as a general principle, I don't think that just because a > > SlackBuild will complete without some other SlackBuild as dependency > > (here openmpi), that the "dependency" should be precluded. Who knows > > what functionality it provides when it is included? Maybe that > > functionality is not useful to everyone but it may be useful to some. > > > > I don't believe we should be generating minimalist libraries or > > applications, rather products containing as many features as possible > > which the authors have made possible. End users should be able to > > expect whatever functionality the product is able to provide, not some > > subset of the possible functionality. > > > > People who know what they're doing and who want some minimalist build > > are free to leave out whatever they want and edit their personal > > versions of SlackBuilds accordingly. Please don't insist that everyone > > is bound by the same idea. > > Thanks for your feedback. > In this case, openmpi doesn't even change the binary, it does nothing at > compile-time. > It also does nothing if available on a single device. > Ngspice might use openmpi if it's available and configured to use > multiple devices in a network. > > Despite i lean towards minimal dependencies, this dependency feels just > wrong, it feels like e.g. a dependency on one more display as it might > be a > comfortable feature. > I would mention openmpi in the README anyway, i hope the maintainer > gives some feedback too. > > Johannes > > Just as a reference, the ngspice package on Arch Linux enables the option --enable-openmp in the make flags but openmpi is not listed as a dependency (see https://github.com/archlinux/svntogit-community/blob/packages/ngspice/trunk/PKGBUILD ) By the way, openmpi is in the 'extra' repository of Arch Linux ( https://archlinux.org/packages/extra/x86_64/openmpi/) Regards, Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Fri Apr 28 13:20:18 2023 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 28 Apr 2023 06:20:18 -0700 Subject: [Slackbuilds-users] Including runit script with slackbuild? In-Reply-To: References: Message-ID: On Tue, Apr 25, 2023, 4:56 AM Charadon via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hey all, > > I want to include runit scripts with my earlyoom slackbuild. What's the > policy with it? Do I have to include an environment variable like > RUNIT=YES so the user can choose if they want it, or can I just include it? > > - Charadon > If it's part of the program, I'd probably include it in the default location. Pat does the same thing with systemd scripts.? He won't modify a package to remove functionality that others might choose to later use simply to save a few KB. If it isn't included with the program by default, that is more up to you. It may not be a bad idea to include it in the doc directory with a note in the README that it's available if someone wants to incorporate it, or using Chris's idea of keeping scripts in a separate repo. Jeremy ? https://www.linuxquestions.org/questions/slackware-14/systemd-creeping-into-slackware-4175614385/#post5762104 -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Fri Apr 28 18:56:56 2023 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 28 Apr 2023 20:56:56 +0200 Subject: [Slackbuilds-users] ngspice does not depend on openmpi In-Reply-To: References: <4309a711c4b15f9511424da9941239c1@schoepfer.info> <689d362df4413772786a7faa6ea28022@schoepfer.info> <69d314b7-5370-f7af-e3e6-ea96eeaeb657@linux.com> Message-ID: <3d7e45ce3a895265179ca9a1d3921fa6@schoepfer.info> Am 2023-04-28 15:14, schrieb Fellype: > Em sex., 28 de abr. de 2023 ?s 09:52, Franzen via SlackBuilds-users > escreveu: > >>> I don't use ngspice, so have no special interest in it (and no >>> knowledge about its prerequisites). >>> >>> However, as a general principle, I don't think that just because a >>> SlackBuild will complete without some other SlackBuild as >> dependency >>> (here openmpi), that the "dependency" should be precluded. Who >> knows >>> what functionality it provides when it is included? Maybe that >>> functionality is not useful to everyone but it may be useful to >> some. >>> >>> I don't believe we should be generating minimalist libraries or >>> applications, rather products containing as many features as >> possible >>> which the authors have made possible. End users should be able to >>> expect whatever functionality the product is able to provide, not >> some >>> subset of the possible functionality. >>> >>> People who know what they're doing and who want some minimalist >> build >>> are free to leave out whatever they want and edit their personal >>> versions of SlackBuilds accordingly. Please don't insist that >> everyone >>> is bound by the same idea. >> >> Thanks for your feedback. >> In this case, openmpi doesn't even change the binary, it does >> nothing at >> compile-time. >> It also does nothing if available on a single device. >> Ngspice might use openmpi if it's available and configured to use >> multiple devices in a network. >> >> Despite i lean towards minimal dependencies, this dependency feels >> just >> wrong, it feels like e.g. a dependency on one more display as it >> might >> be a >> comfortable feature. >> I would mention openmpi in the README anyway, i hope the maintainer >> gives some feedback too. >> >> Johannes > > Just as a reference, the ngspice package on Arch Linux enables the > option --enable-openmp in the make flags but openmpi is not listed as > a dependency (see > https://github.com/archlinux/svntogit-community/blob/packages/ngspice/trunk/PKGBUILD > ) Thanks for your feedback. openmpi has nothing to do with openmp, openmp is built into some ngspice-engines when enabled at builttime via --enable-openmp(this is the case here, the openmp-part is already included in the ngspice-source, no dependencyy/requirement needed), see https://ngspice.sourceforge.io/docs/ngspice-manual.pdf chapter 16.10. The documentation doesn't mention openmpi at all. Maybe this was confused by the maintainer, feedback appreciated. Johannes From zhu.qunying at gmail.com Fri Apr 28 23:46:43 2023 From: zhu.qunying at gmail.com (Qun-Ying) Date: Fri, 28 Apr 2023 16:46:43 -0700 Subject: [Slackbuilds-users] ngspice does not depend on openmpi In-Reply-To: <3d7e45ce3a895265179ca9a1d3921fa6@schoepfer.info> References: <4309a711c4b15f9511424da9941239c1@schoepfer.info> <689d362df4413772786a7faa6ea28022@schoepfer.info> <69d314b7-5370-f7af-e3e6-ea96eeaeb657@linux.com> <3d7e45ce3a895265179ca9a1d3921fa6@schoepfer.info> Message-ID: I just do a search under ngspice-40 source with "find -type f | xargs grep -i openmpi", no a single mention of it. Maybe just confuse with openmp. -- Qun-Ying From willysr at slackbuilds.org Sat Apr 29 11:29:47 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 29 Apr 2023 18:29:47 +0700 Subject: [Slackbuilds-users] Updates - 20230429.1 Message-ID: <61cc06c1-e4c6-7388-778f-940e5f0cf134@slackbuilds.org> Hi all as discussed in the mailing list, we are pushing the python2/3 splits to make it easier in the future if one day Slackware decided to remove Python2 support. For future submission, please use python3- for python3 spesific packages Sat Apr 29 11:12:43 UTC 2023 academic/Gridcoin-Research: Updated for version 5.4.5.0 academic/boinc: Updated for version 7.22.7 academic/cadabra2: Update REQUIRES. academic/dwave-neal: Update DEP. academic/fastqc: Remove .svn folders that were causing java-errors. academic/plus42: Updated for version 1.0.18. academic/qucs-s: Updated for version 1.0.2. academic/xsimd: Updated for version 11.0.0. audio/musikcube: Updated for version 3.0.0. audio/pavucontrol-qt: Updated for version 1.3.0. audio/pulsemixer: Added (CLI and curses mixer for PulseAudio) audio/volctl: Update EMAIL. desktop/LX-Colors-Revival: Updated for version 20160602. desktop/amiwm: Updated for version 0.22pl2. desktop/caffeine-ng: Update DEP. desktop/dunst: Updated for version 1.9.2. desktop/dwm: Updated for version 6.4. desktop/gnome-icon-theme-stock: Added (Gnome 2 stock icons subset) desktop/gnome-icon-theme: Added (default icons used by GTK+) desktop/gtk-xfce-engine: Added (Xfce Gtk+ engines) desktop/nwg-panel: Update DEP. desktop/nwg-shell-config: Update DEP. desktop/nwg-wrapper: Update DEP. desktop/python3-autotiling: Update DEP. desktop/xfwm4-themes: Added (themes for the Xfce window manager) desktop/zenity: Update for 3.44.1 development/QtPy: Updated for version 2.3.1. development/bas55: Updated for version 1.19, fix completion. development/codespell: Update DEP. development/focal: Added (FOCAL language interpreter) development/ghex: Update for 44.1 development/github-cli: Updated for version 2.28.0. development/goland: Updated for version 2023.1. development/idea: Updated for version 2023.1. development/jupyter-nbclassic: Updated for version 0.5.6. development/jupyter-nbclient: Updated for version 0.7.4. development/jupyter-notebook_shim: Updated for version 0.2.3. development/jupyter_packaging: Update DEP. development/kotlin: Updated for version 1.8.21. development/liberica-jdk-bin: Updated for version 17.0.7+7. development/lua-language-server: Updated for version 3.6.19. development/minimal-basic: Added (ECMA-55 Minimal BASIC compiler) development/mongodb-compass: Updated for version 1.36.4. development/msbasic2ascii: Added (detokenizers for MS BASIC) development/mutagen: Update DEP. development/pycharm: Updated for version 2023.1.1.231.8770.66. development/terraform: Updated for version 1.4.6. development/universal-ctags: Updated for version p6.0.20230423.0 development/valgrind: Updated for version 3.21.0. development/zulu-openjdk11: Updated for version 11.0.19. development/zulu-openjdk17: Updated for version 17.0.7. games/ezquake: Updated for version 3.6.2. games/mame: Updated for version 0.254. games/scid_vs_pc: Updated for version 4.24. games/wesnoth: Updated for version 1.16.9 games/xonotic: Update EMAIL. gis/proj-data: Updated for version 1.13. gis/proj: Updated for version 9.2.0. gis/python3-pyproj: Updated for version 3.5.0. gis/therion: Nitpick: tab => space in README. graphics/OpenCASCADE: Fix perms for files in DOCS dir. graphics/aaphoto: Change DOWNLOAD. graphics/graphviz: Updated for version 8.0.4. graphics/inkscape-gtk2: Added (Open Source vector graphics editor) graphics/tesseract: Update for 5.3.1 graphics/yacreader: Updated for version 9.12.0.2304234. graphics/yed: Updated for version 2.23.1. libraries/CLI11: Added (a command line parser for C++11 and beyond) libraries/VTK: Disable execute permission on git. libraries/gloox: Updated for version 1.0.27. libraries/libadwaita: Update for 1.2.4 libraries/libfilezilla: Updated for version 0.42.2. libraries/libjodycode: updated for version 1.2 libraries/liboauth: Update EMAIL. libraries/libportal: Updated for version 0.6. libraries/libsixel: Added (DEC SIXEL graphics en/decoder + tools) libraries/mimalloc: Updated for version 2.1.2 misc/bitwarden-desktop: Updated for version 2023.4.0. misc/pinfo: Fix keybinds, man page. multimedia/jellyfin-media-player: Updated for version 1.9.1. multimedia/obs-studio: Updated for version 29.0.2 multimedia/pocketsphinx: Update DEP. multimedia/totem: Update REQUIRES. network/Electrum-DASH: updated pyasn1-modules requirement network/Electrum: Updated for version 4.4.1. network/addrwatch: Added (arp traffic montor). network/dropbox: Updated for version 172.4.7555. network/element-desktop: Updated for version 1.11.30. network/enet: Update EMAIL. network/feather: Added (Monero Wallet Client) network/filezilla: Updated for version 3.64.0. network/microsoft-edge: Updated to version 112.0.1722.64 network/radicale: Update DEP. network/sfeed: Updated for version 1.8. network/tailscale: update 1.40.0 network/telegram: Updated for version 4.8.1. network/zoom-linux: Updated for version 5.14.5.2430 office/calibre-bin: Updated for version 6.17.0. office/evince-gtk2: Added (a simple gnome-based document viewer) office/gcalctool-gtk2: Added (a graphical UNIX calculator) office/gnumeric-gtk2: Added (GNOME spreadsheet app) office/khal: Updated for version 0.11.1. office/openoffice.org: Add theme option. office/osmo-gtk2: Added (Handy Personal Organizer) perl/perl-Mojolicious: Updated for version 9.31. New maintainer. python/asttokens: Update DEP. python/cryptography: Update DEP. python/humanize: Update DEP. python/ics: Update DEP. python/iniconfig: Remove Python 2 support python/ipython: Updated for version 8.13.0. python/pelican: Update DEP. python/pyasn1-modules: Removing, replaced by python2-pyasn1-modules and python3-pyasn1-modules python/pygsl: Update DEP. python/pynacl: Update DEP. python/python-gssapi: Added (Python Bindings for GSSAPI) python/python-jeepney: Update DEP. python/python-krb5: Added (Python Kerberos 5 Library) python/python2-asn1crypto: Added (Fast ASN.1 parser and serializer) python/python2-automat: Update DEP. python/python2-cryptography: Update DEP. python/python2-gmpy2: Added (multi-precision arithmetic for python) python/python2-ldap: updated pyasn1-modules requirement python/python2-py: Added (library with cross-python path) python/python2-pyasn1-modules: Added (ASN.1-based protocol modules.) python/python2-pyasn1: Added (ASN.1 types and codecs in Python) python/python3-alembic: Updated for version 1.10.4. python/python3-asn1crypto: Added (Fast ASN.1 parser and serializer) python/python3-attrdict: Update DEP. python/python3-automat: Update DEP. python/python3-booleanOperations: Update DEP. python/python3-calver: Update DEP. python/python3-cloudflare: Update EMAIL. python/python3-distlib: Update DEP. python/python3-docker: Update DEP. python/python3-editables: Update DEP. python/python3-gensim: Update DEP. python/python3-gmpy2: Added (multi-precision arithmetic for python) python/python3-isoduration: Update DEP. python/python3-jaraco.classes: Update DEP. python/python3-jaraco.context: Update DEP. python/python3-jaraco.functools: Update DEP. python/python3-jsonlines: Update EMAIL. python/python3-kiwisolver: Update DEP. python/python3-klein: Update DEP. python/python3-ldap: updated pyasn1-modules requirement python/python3-lsp-server: Update DEP. python/python3-lz4: Update DEP. python/python3-nltk: Update DEP. python/python3-psutil: Update DEP. python/python3-py-cpuinfo: Update DEP. python/python3-py: Added (library with cross-python path) python/python3-pyasn1-modules: Added (ASN.1-based protocol modules.) python/python3-pyasn1: Added (ASN.1 types and codecs in Python) python/python3-pydantic: Update DEP. python/python3-pylint-venv: Update DEP. python/python3-pypandoc: Update DEP. python/python3-pypng: Update DEP. python/python3-pyproject-hooks: Added (call PEP517 backend hooks) python/python3-pytest-runner: Update DEP. python/python3-requests-cache: Update DEP. python/python3-rtree: Update DEP. python/python3-service-identity: updated pyasn1-modules requirement python/python3-shtab: Update DEP. python/python3-teletype: Update DEP. python/python3-tomlkit: Updated for version 0.11.8. python/python3-tornado: Updated for version 6.3.1. python/python3-ujson: Update DEP. python/pyudev: Updated for version 0.24.1. python/rencode: Update DEP. python/service_identity: updated pyasn1-modules requirement python/tzdata: Update DEP. ruby/ruby-build: Updated for version 20230428. system/Iosevka-aile: Updated for version 22.1.0. system/Iosevka-etoile: Updated for version 22.1.0. system/Iosevka-slab: Updated for version 22.1.0 system/Iosevka: Updated for version 22.1.0 system/afdko: Update DEP. system/apple-emoji: Added (Apple Color Emoji) system/apple-fonts-Garamond: Added (Apple fonts Garamond) system/apple-fonts-NY: Added (Apple New York fonts) system/apple-fonts-SF: Added (Apple San Francisco fonts) system/file-roller-gtk2: Added (an archive manager for GNOME) system/fuse-overlayfs: README is text, not Markdown. system/kitty-bin: Added (featureful, GPU-based terminal emulator) system/loggedfs: Added (filesystem monitoring with FUSE) system/noto-extra-ttf: Added (extra Noto fonts) system/openzfs: Updated for version 2.1.11. system/qemu: Updated for version 7.2.1 system/restic: Updated for version 0.15.2. system/rhash: Update EMAIL. system/sarasa-gothic: Updated for version 0.40.6. system/slpkg: Updated for version 4.8.2. system/sst: Updated for version 1.7. system/vhba-module: Allow building with custom kernel versions +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From bobfunk11 at gmail.com Sat Apr 29 12:44:08 2023 From: bobfunk11 at gmail.com (Bob Funk) Date: Sat, 29 Apr 2023 07:44:08 -0500 Subject: [Slackbuilds-users] Does colord-gtk have an active maintainer? Message-ID: Hi, I had emailed the listed maintainer for colord-gtk a week ago proposing an update to the latest colord-gtk version (0.3.0), to get gtk4 support as well (older 0.2.0 version is only up to gtk3). I haven't heard back from him yet, and looking at the slackbuilds git log, his last commit was in 2018, with the later commits all done by admin. Made me think that this one might not be actively maintained anymore so I thought I'd email the user list and ask to be sure. I'd happily take over maintaining that one if it needs a maintainer, since it's a dep for my gnome-control-center slackbuild (and nothing else AFAICT). Cheers, Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Sat Apr 29 12:53:52 2023 From: dave at slackbuilds.org (Dave) Date: Sat, 29 Apr 2023 13:53:52 +0100 Subject: [Slackbuilds-users] Does colord-gtk have an active maintainer? In-Reply-To: References: Message-ID: 29/04/23 07:44, Bob Funk : > Hi, > > I had emailed the listed maintainer for colord-gtk a week ago proposing an > update to the latest colord-gtk version (0.3.0), to get gtk4 support as > well (older 0.2.0 version is only up to gtk3). > > I haven't heard back from him yet, and looking at the slackbuilds git log, > his last commit was in 2018, with the later commits all done by admin. Made > me think that this one might not be actively maintained anymore so I > thought I'd email the user list and ask to be sure. > > I'd happily take over maintaining that one if it needs a maintainer, since > it's a dep for my gnome-control-center slackbuild (and nothing else AFAICT). > > Cheers, > Bob It should be OK. He doesn't seem to be around much any more. Dave -- sbo-maintainer-tools (sbolint, sbopkglint): https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt From spaceman at antispaceman.com Sat Apr 29 21:14:27 2023 From: spaceman at antispaceman.com (spaceman) Date: Sat, 29 Apr 2023 21:14:27 +0000 Subject: [Slackbuilds-users] mpop (https://marlam.de/mpop) Message-ID: <202304292115.33TLF9AX020981@mail.authsmtp.com> Both mpop (1.2.6 --> 1.4.18) and evilwm (1.1.1 --> 1.4.2) are out of date. The maintainers email address bounced for me. They should probably be removed or updated. Regards, spaceman From fourtysixandtwo at sliderr.net Sat Apr 29 21:20:01 2023 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sat, 29 Apr 2023 15:20:01 -0600 Subject: [Slackbuilds-users] remove wheel slackbuild Message-ID: With everything switched to python3-wheel, the wheel slackbuild can now be removed. Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Sat Apr 29 22:00:23 2023 From: urchlay at slackware.uk (B. Watson) Date: Sat, 29 Apr 2023 18:00:23 -0400 (EDT) Subject: [Slackbuilds-users] mpop (https://marlam.de/mpop) In-Reply-To: <202304292115.33TLF9AX020981@mail.authsmtp.com> References: <202304292115.33TLF9AX020981@mail.authsmtp.com> Message-ID: <6d84a385-0e-30a9-cdab-468a2f3c03c@slackware.uk> On Sat, 29 Apr 2023, spaceman via SlackBuilds-users wrote: > Both mpop (1.2.6 --> 1.4.18) and evilwm (1.1.1 --> 1.4.2) are out of > date. > > The maintainers email address bounced for me. > > They should probably be removed or updated. Are you interested in taking them over as maintainer? Marek Buras hasn't been active since November 2017. If you want them, they're yours. From willysr at slackbuilds.org Sun Apr 30 03:30:04 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 30 Apr 2023 10:30:04 +0700 Subject: [Slackbuilds-users] remove wheel slackbuild In-Reply-To: References: Message-ID: <632475ba-4c79-462a-03ef-3c034c7753bc@slackbuilds.org> > With everything switched to python3-wheel, the wheel slackbuild can now be > removed. i'll keep them for a week and remove them if no reports of scripts broken -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From s.arcus at open-t.co.uk Sun Apr 30 11:20:32 2023 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 30 Apr 2023 12:20:32 +0100 Subject: [Slackbuilds-users] Burp version upgrade Message-ID: Just a little note that Burp could do with a little version bump from 2.1.32 to 2.4.0 - if possible. I'm happy to give a hand if it helps :-) From arnaud.garcia-fernandez at laposte.net Sun Apr 30 16:40:54 2023 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Sun, 30 Apr 2023 18:40:54 +0200 Subject: [Slackbuilds-users] remove wheel slackbuild In-Reply-To: <632475ba-4c79-462a-03ef-3c034c7753bc@slackbuilds.org> References: <632475ba-4c79-462a-03ef-3c034c7753bc@slackbuilds.org> Message-ID: <20230430184054.461f595c5de6920ee72dd88f@laposte.net> > > With everything switched to python3-wheel, the wheel slackbuild can now be > > removed. > > i'll keep them for a week and remove them if no reports of scripts broken > > -- > Willy Sudiarto Raharjo > Well, there's no python2-wheel. It looks fine because it seems it mostly is an shell executable, so whatever Python version is used should be ok. But... python2-automat builds with python3-wheel with this message : WARNING: The wheel package is not available. DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support Which looks like its making a call to pip, but not installing wheel, and not seeming to do much. The package builds fine. Keeping the old wheel package there removes the warning, and the python2-Automat package builds... well exactly the same. Removing all wheel packages, old and python3-wheel, well, doesn't change anything, the warning is there, the package builds fine. Anyway, this does not seem that big a problem, but I guess we could just drop the python3-wheel requirement altogether, since it builds the same. My whole not very useful point being that we might see some problems with the removal of python2 version of wheel. But... I don't care, and all python2 packages should be removed, or presenting themselves at the morgue soon ^^ But... (again, I know) A package like python2-automat is used by python2-twisted, itself used by : Nevow TaskCoach python2-txaio Parsley txi2p Scrapy python2-orbited sslstrip python2-klein txrequests txsocksx graphite-carbon foolscap Most of which are probable outdated, not really maintained, and might not work at all, but will require some work to know what's what, ask for people to update and step up as maintainers, or be removed (then I may at last kill python2-twisted and be rid of that old stuff). Cheers :) - Yth / Arnaud. PS : on a side note, problems might appear at a very late time, because the old wheel package is not removed by the name change, therefore the python2 wheel will stay in many slackware box used by real people, masking any problem that might arise. So things will break, but I think those things are either already broken, or needs to be updated. From arnaud.garcia-fernandez at laposte.net Sun Apr 30 18:17:09 2023 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Sun, 30 Apr 2023 20:17:09 +0200 Subject: [Slackbuilds-users] Python2 packages in need of action Message-ID: <20230430201709.0f11a1bb2bee6b7c54c5413d@laposte.net> Hi everybody. Taking another look at my python2 packages, they are requirements of some other stuff, most of which is unmaintained. Amongst those there are packages very outdated, building for python2, no python3 version available on SBo, and the upstream newer versions are python3 only. Most of them probable aren't working at all, probably build fine, but short of really using it, with python packages, you can't know if they work. Mosty of the one I've tested don't, they have broken dependencies, or rely on Great Old Stuff from Way Before Slackware 15.0. Hence those packages are in dire need of either : - someone to step up as maintainer, pushing an update to later version, using python3 ; - be removed as nobody seems to use them, because they'd have complained about their situation. Here is a short list of the ones I've found, which are related to the python2 package I really want not to maintain anymore. * To be updated or dropped | | version | date | newest | | salt | 2018.3.3 | 2018 | 3008 | | tahoe-lafs | 1.12.1 | 2017 | 1.18.0 | | Scrapy | 1.7.3 | 2019 | 2.8.0 | | graphite-carbon | 0.9.15 | 2015 | 1.1.10 | | graphite-web | 0.9.15 | 2015 | 1.1.10 | | txtorcon | 0.19.3 | 2017 | 23.0.0 | | foolscap | 0.13.1 | 2017 | 23.3.0 | * To be removed because very obsolete, and often an old requirement of tahoe-lafs or Scrapy, and not required by newer version. Upstream has *not* been updated for years. | | version | date | newest | | python2-orbited | 0.7.10 | 2009 | yes | | TaskCoach | 1.4.3 | 2016 | 1.4.4 | | Nevow | 0.14.4 | 2018 | 0.14.5 | | sslstrip | 0.9 | 2013 | 0.9.2 | | Parsley | 1.3 | 2015 | yes | | txsocksx | 1.15.0.2 | 2015 | yes | | txi2p | 0.3.2 | 2017 | yes | | txrequests | 0.9.6 | 2018 | yes | | Electrum-DASH | 2.4.1 | 2015 | 2.8.3 | * Other packages for which there is already a python3 package : - service_identity as a requirement of Scrapy and tahoe-lafs should be removed after dealing with them, as a python3-service-identity already exists. - python2-klein -> python3-klein exists and is uptodate. - python2-ldap - > python3-ldap exists and is uptodate. * Needing split : - python-m2r, for which python2 support could be dropped. -> I will split python-m2r, taking python3-m2r, because it is an optional dependency of python3-automat, which I maintain already. The old python-m2r could then be removed, unneeded as I plan on removing python2-automat soon enough. I have absolutely no use of any of the packages I marked as needed to be updated or removed, I have no wish to take over them. They probably simply don't work at all, because some requirements are python3, and other are python2, just look at Scrapy requirement tree, I can't see how it would work. Which means that nobody uses them. My advice would be to remove them. That means removing : salt , tahoe-lafs, Scrapy, graphite-carbon, graphite-web, txtorcon , foolscap, python2-orbited, TaskCoach, Nevow, sslstrip, Parsley, txsocksx, txi2p, txrequests, Electrum-DASH, service_identity, python2-klein, python2-ldap. And replacing python-m2r with a python3-m2r (which I'm willing to do). That would lead to the removal of my packages : python2-attrs, python2-automat, python2-mistune, python2-pyhamcrest, python2-pyzmq, python2-twisted, python2-txaio. All available for python3. And probably some more, which I don't maintain, but we may see clearer after that big operation. Cheers, and sorry for the very long message :) - Yth / Arnaud. From ml at mareichelt.com Sun Apr 30 19:30:42 2023 From: ml at mareichelt.com (Markus Reichelt) Date: Sun, 30 Apr 2023 21:30:42 +0200 Subject: [Slackbuilds-users] Botan 3.0.0 support Message-ID: <20230430193042.GG3369@pc21.mareichelt.com> Hi, just wanted to drop this info in here: Botan 3.0.0 has been released https://github.com/randombit/botan/tags the Botan devel & announce mailinglists are still nonfunctional. Jack has other priorities, and will fix this eventually (=don't hold your breath). keepassxc & CoreCtrl both depend on Botan2 and fail to compile with Botan3. I've contacted keepassxc folks in their libera dev chan & the CoreCtrl coder per email. Respective maintainers are encouraged to check on progress :-) fwiw, the Botan buildscript also works with Botan 3.0.0 as-is (use VERSION=) Regards, Markus From ml at mareichelt.com Sun Apr 30 20:08:56 2023 From: ml at mareichelt.com (Markus Reichelt) Date: Sun, 30 Apr 2023 22:08:56 +0200 Subject: [Slackbuilds-users] Python2 packages in need of action In-Reply-To: <20230430201709.0f11a1bb2bee6b7c54c5413d@laposte.net> References: <20230430201709.0f11a1bb2bee6b7c54c5413d@laposte.net> Message-ID: <20230430200856.GH3369@pc21.mareichelt.com> * Arnaud via SlackBuilds-users wrote: > Amongst those there are packages very outdated, building for > python2, no python3 version available on SBo, and the upstream > newer versions are python3 only. Most of them probable aren't > working at all, probably build fine, but short of really using it, > with python packages, you can't know if they work. Mosty of the > one I've tested don't, they have broken dependencies, or rely on > Great Old Stuff from Way Before Slackware 15.0. Let's not forget what magic mess the superlong release timeframe of Slackware 15.0 caused for all involved; I had tahoe-lafs working on then-at-a-time-current including 1.16.0, with added deps. But the number of python deps kept increasing and tahoe-lafs changed their release procedure/mantra, in addition to the established mess. I used to maintain some of the patients you mention, and have already informed about their situation on this list. I can say that to date nobody contacted me in that regard whatsoever - so let's remove old cruft that you mention and where I am still listed as maintainer. But maybe this thread sparks someone into action taking over maintenance. Regards, Markus From artourter at gmail.com Sun Apr 30 22:03:09 2023 From: artourter at gmail.com (Greg Tourte) Date: Sun, 30 Apr 2023 23:03:09 +0100 Subject: [Slackbuilds-users] Botan 3.0.0 support In-Reply-To: <20230430193042.GG3369@pc21.mareichelt.com> References: <20230430193042.GG3369@pc21.mareichelt.com> Message-ID: Looks like upstream have started adding support to botan3 for keepasscx in the main branch on github. I will play around, see how well it works and report back. Thanks for the heads up. Cheers Greg On Sun, 30 Apr 2023 at 20:30, Markus Reichelt wrote: > Hi, > > just wanted to drop this info in here: > > Botan 3.0.0 has been released https://github.com/randombit/botan/tags > > the Botan devel & announce mailinglists are still nonfunctional. Jack > has other priorities, and will fix this eventually (=don't hold your > breath). > > keepassxc & CoreCtrl both depend on Botan2 and fail to compile with > Botan3. I've contacted keepassxc folks in their libera dev chan & > the CoreCtrl coder per email. > > Respective maintainers are encouraged to check on progress :-) > > fwiw, the Botan buildscript also works with Botan 3.0.0 as-is (use > VERSION=) > > Regards, > Markus > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fourtysixandtwo at sliderr.net Sun Apr 30 22:16:57 2023 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sun, 30 Apr 2023 16:16:57 -0600 Subject: [Slackbuilds-users] remove wheel slackbuild In-Reply-To: <20230430184054.461f595c5de6920ee72dd88f@laposte.net> References: <632475ba-4c79-462a-03ef-3c034c7753bc@slackbuilds.org> <20230430184054.461f595c5de6920ee72dd88f@laposte.net> Message-ID: Arnaud's tests backup my findings and why I didn't create a python2-wheel and suggest the removal of the old wheel slackbuild sooner rather than later. It's just not needed and would only cause a conflict (/usr/bin/wheel) with python3-wheel. And we don't need more wxPython-like conflicts! The other two builds (rencode and pynacl) that have those same warnings need to be split/renamed, but also build just fine despite the wheel missing warning. (as mentioned in my PR) My testing included comparing the build log and packages between no wheel , old wheel slackbuild, and just python3-wheel installed. There is no difference except the warning and functionality tests are successful. (except for python2-automat which seems to be broken and more testing would be moot given Arnaud planning it's removal) So I suggest removing the 3 commits to "fix wheel dependency" sitting in Andrew's branch and we remove the old wheel slackbuild. Cheers On Sun, Apr 30, 2023 at 10:41?AM Arnaud via SlackBuilds-users wrote: > > > > With everything switched to python3-wheel, the wheel slackbuild can now be > > > removed. > > > > i'll keep them for a week and remove them if no reports of scripts broken > > > > -- > > Willy Sudiarto Raharjo > > > > Well, there's no python2-wheel. > It looks fine because it seems it mostly is an shell executable, so whatever > Python version is used should be ok. > > But... > > python2-automat builds with python3-wheel with this message : > > WARNING: The wheel package is not available. > DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please > upgrade your Python as Python 2.7 is no longer maintained. A future version of > pip will drop support for Python 2.7. More details about Python 2 support in > pip, can be found at > https://pip.pypa.io/en/latest/development/release-process/#python-2-support > > Which looks like its making a call to pip, but not installing wheel, and not > seeming to do much. > The package builds fine. > Keeping the old wheel package there removes the warning, and the > python2-Automat package builds... well exactly the same. > Removing all wheel packages, old and python3-wheel, well, doesn't change > anything, the warning is there, the package builds fine. > > Anyway, this does not seem that big a problem, but I guess we could just drop > the python3-wheel requirement altogether, since it builds the same. > > My whole not very useful point being that we might see some problems with the > removal of python2 version of wheel. > > But... > > I don't care, and all python2 packages should be removed, or presenting > themselves at the morgue soon ^^ > > But... (again, I know) > > A package like python2-automat is used by python2-twisted, itself used by : > Nevow TaskCoach python2-txaio Parsley txi2p Scrapy python2-orbited sslstrip > python2-klein txrequests txsocksx graphite-carbon foolscap > > Most of which are probable outdated, not really maintained, and might not work > at all, but will require some work to know what's what, ask for people to update > and step up as maintainers, or be removed (then I may at last kill > python2-twisted and be rid of that old stuff). > > Cheers :) > > - Yth / Arnaud. > > PS : on a side note, problems might appear at a very late time, because the old > wheel package is not removed by the name change, therefore the python2 wheel > will stay in many slackware box used by real people, masking any problem that > might arise. > So things will break, but I think those things are either already broken, or > needs to be updated. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ >