From jebrhansen+SBo at gmail.com Thu Oct 1 12:19:49 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Thu, 1 Oct 2026 05:19:49 -0700 Subject: [Slackbuilds-users] Updates - 20260919.1 In-Reply-To: <356d54b4-dd9c-45b3-aa1c-f2f1f74a9bc8@slacky.it> References: <20260919090616.5d0e5449@home.slackie.org> <20260930213301.5da0a79e@home.slackie.org> <356d54b4-dd9c-45b3-aa1c-f2f1f74a9bc8@slacky.it> Message-ID: Yep! I realized it wouldn't work, added the remarks to the README, but forgot to revert the actual version bump before committing. The revert is awaiting the next public update. https://git.slackbuilds.org/slackbuilds/commit/?h=user/bassmadrigal/updates&id=c8742d69232eaa9d45e53cfa63b0d409d0ee5861 Apologies for the churn! Jeremy On Wed, Sep 30, 2026, 7:36?AM 414N <414N at slacky.it> wrote: > Il 30/09/26 16:33, Willy Sudiarto Raharjo ha scritto: > > maybe he forgot to revert the changes > > i will revert it back to 1.9.3 > > I already notified the maintainer (Jeremy Hansen) for this. > > He said that he reverted the change on his branch, I guess we'll see a > version downgrade for the python3-evdev package soon. > > > -- > Alan Alberghini > > SBo clone: https://github.com/414n/slackbuilds > > _______________________________________________ > 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 rizitis at gmail.com Thu Oct 1 18:48:04 2026 From: rizitis at gmail.com (Yiannis) Date: Thu, 1 Oct 2026 21:48:04 +0300 Subject: [Slackbuilds-users] REQUEST for removal Message-ID: Please on next updates remove from SBo development/gum which I'm the maintainer until now. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Oct 1 23:53:09 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 2 Oct 2026 06:53:09 +0700 Subject: [Slackbuilds-users] REQUEST for removal In-Reply-To: References: Message-ID: <20261002065309.24a73384@home.slackie.org> >Please on next updates remove from SBo development/gum which I'm the >maintainer until now. >Thank you. done on my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Oct 3 02:02:32 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 3 Oct 2026 09:02:32 +0700 Subject: [Slackbuilds-users] Updates - 20261003.1 Message-ID: <20261003090232.6a7bbef8@home.slackie.org> Sat Oct 3 01:47:31 UTC 2026 academic/AstroImageJ: Orphaned (unmaintained). academic/OpenFOAM: Updated for version 14. academic/geomview: Orphaned (unmaintained). academic/irsim: Orphaned (unmaintained). academic/magic: Orphaned (unmaintained). academic/python2-scipy: New maintainer. academic/sage: Orphaned (unmaintained). academic/xsimd: Make BUILD_TESTS optional academic/zotero: update to 10.0.5 accessibility/easystroke: Updated script + new maintainer. audio/JDSP4Linux: Orphaned (unmaintained). audio/SongRec: Orphaned (unmaintained). audio/fmit: Add no-update note to README. audio/jalv: Add no-update note to README. audio/jamulus: Updated for version 3.12.5. audio/ncmpcpp: Updated for version 0.10.1 audio/ocp: Drop gnu-unifont dep, various fixes. audio/reaper: Updated for version 7.81 audio/transcribe: Updated for version 9.70.0. desktop/AppStream: Updated for version 1.1.6. desktop/ClamAV-GUI: Updated for version 1.4.7 desktop/TriliumNotes: Added (Note taker & organizer). desktop/aweather: Orphaned (unmaintained). desktop/grits: Orphaned (unmaintained). desktop/lumina: Orphaned (unmaintained). desktop/rsl: Orphaned (unmaintained). desktop/standard-notes-bin: Updated for version 3.202.7 desktop/wmbattery: Updated for version 2.56, new maintainer. development/Digital: Added (Digital logic designer). development/Kiro: Updated for version 1.2.4. development/OpenHantek6022: Orphaned (unmaintained). development/antigravity-cli: Updated for version 1.2.12 development/antigravity: Updated for version 2.17.0 development/apache-maven: Updated for version 3.10.0. development/arduino-cli: Updated script development/asl: Updated for version 142_bld313. development/bbcsdl: Updated for version 20260929_2bbe729 development/bfg: Orphaned (unmaintained). development/cproc: Updated for version 20260601_d1c53dd. development/cursor: Updated for version 3.22.7 development/cxxtools: Updated for version 4.2 + new maintainer development/diffoscope: Updated for version 332 development/eh: Updated for version 1.9.0 development/electron-bin: Updated for version 44.4.5 development/elixir: Updated for version 1.14.5 development/gauche: Updated for version 0.9.15. development/gengetopt: Updated for version 2.23.1. development/ghidra: Updated for version 12.1.4 development/go-term: Added (Go terminal/console support). development/got: update to 0.129 development/gum: Removed (Maintainer's request). development/jupyterlab_server: Update README development/mads: Updated for version 2.1.8. development/mcu8051ide: Fix build with new tkimg. development/minipro: Updated script. development/mongodb-compass: Fix MD5SUM. development/nccl: Fix MD5SUM. development/nodejs22: Updated for version 22.23.3. development/python2-numpy: New maintainer. development/python3-cycler: New maintainer development/python3-matplotlib: New maintainer development/qb64pe: Updated for version 4.7.0_GLFW development/rgbds: Updated for version 1.0.4. development/rider: Updated for version 2026.2.3. development/sbcl: Updated for version 2.6.9 development/smalltalk: Orphaned (unmaintained). development/smartgit: Updated for version 26.1.056 development/staruml: Updated for version 7.1.0. development/swi-prolog: Updated for version 10.0.2. development/uemacs: Orphaned (unmaintained). development/unifdef: Fix -current FTBFS, fix "make test". development/vscode-bin: Updated for version 1.140.0 development/vstudio: Updated for version 18.2.1 games/PrismLauncher: Updated for version 11.1.1. games/atari800: Updated for version 7.2.1. games/boosteroid: Orphaned (unmaintained). games/cataclysmdda: Updated for version 0.I-1. games/commandergenius: Updated for version 3.6.4. games/crrcsim: Updated REQUIRES. games/ds-models: Removed (unmaintained). games/enigma-marbles: Orphaned (unmaintained). games/ffgo: Orphaned (unmaintained). games/fgo: Orphaned (unmaintained). games/immortal-barons: Updated for version 0.2.1 games/jg-bsnes: Updated for version 2.1.2. games/jg-cega: Updated for version 0.6.3. games/jg-geolith: Updated for version 0.5.0. games/jg-jollycv: Updated for version 2.1.0. games/jg-nestopia: Updated for version 2.0.0. games/odamex: Updated for version 12.3.0. games/openjazz: Updated for version 20260301. games/opentyrian: Updated for version 2.1.20260913. games/puzzles: Updated for version 20260923.616da16. games/quackle: Updated for version 1.1.0. games/rottexpr: Orphaned (unmaintained). games/skulltag: Removed (unmaintained). games/x16emu: Orphaned (unmaintained). games/zsnes: Updated for version 2.3.6, now with 64-bit support. gis/GMT: Mark x86_64 only. gis/OWSLib: Updated README. gis/routino: New maintainer. graphics/FreeCAD: Patched intrusive_ptr error graphics/apitrace: Orphaned (unmaintained). graphics/dia: New maintainer graphics/entangle: Orphaned (unmaintained). graphics/paraview: Updated for version 6.2.0 graphics/plotutils: Orphaned (unmaintained). graphics/ralcgm: Use working homepage URL. graphics/renderdoc: Updated for version 1.19 graphics/shutter: Version bump to 0.99.7 graphics/vips: Updated for version 8.18.7. ham/Xastir: Orphaned (unmaintained). ham/codec2: New maintainer. ham/fbb: Orphaned (unmaintained). ham/gridtracker2: Updated for version 2.260925.2. ham/libax25: Orphaned (unmaintained). libraries/CGAL5: Updated for version 6.2.1. libraries/CondConfigParser: Orphaned (unmaintained). libraries/GeographicLib: Orphaned (unmaintained). libraries/PyOpenGL: New maintainer. libraries/batinfo: Orphaned (unmaintained). libraries/camlpdf: Updated for version 2.9.2. libraries/ftplib: Orphaned (unmaintained). libraries/go-gdamore-encoding: Added (Character map encodings). libraries/go-uniseg: Updated README. libraries/gumbo-parser: Updated for version 0.14.1. libraries/libdispatch: Updated for version 6.4.0. libraries/libindi-drivers: Updated for version 2.2.4.1 libraries/libindi-libraries: Updated for version 2.2.4.1 libraries/libindi: Updated for version 2.2.4.2 libraries/libmpu: Updated for version 1.0.25. libraries/libnova: New maintainer libraries/libnova: Updated for version 0.16.0 libraries/libopenshot-audio: Updated for version 1.0.1 libraries/libopenshot: Updated for version 1.0.1 libraries/libscfg: Updated for version 0.2.0 libraries/libsoup3: Update README. libraries/libucil: Orphaned (unmaintained). libraries/libunibreak: Add note to self. libraries/libunicapgtk: Orphaned (unmaintained). libraries/libxml++3: Updated for version 3.2.5, new maintainer. libraries/logilab-astng: Orphaned (unmaintained). libraries/logilab-common: Orphaned (unmaintained). libraries/opencl-amd: Removed (broken, unmaintained). libraries/python3-contourpy: New maintainer libraries/qt-avif-image-plugin: Updated for version 0.10.6. libraries/qt-jpegxl-image-plugin: Updated for version 0.9.0. libraries/sqliteodbc: Orphaned (unmaintained). libraries/ucl: Orphaned (unmaintained). misc/asterixInspector: Orphaned (unmaintained). misc/discount: Updated for version 3.0.2.0. misc/es40: Updated for version 0.88 misc/exploitdb: Updated for version 2026_10_02. misc/ollama: Updated for version 0.35.0. misc/u8strings: Added (strings(1) with UTF-8 support). misc/weather: Orphaned (unmaintained). misc/xcape: Orphaned (unmaintained). misc/xdelta3: Updated for version 3.2.1. multimedia/LBRY: Orphaned (unmaintained). multimedia/coriander: Orphaned (unmaintained). multimedia/devedeng: Updated for version 4.21.3.1 multimedia/inputstream.adaptive: Version bump to 21.5.25 multimedia/musique: Orphaned (unmaintained). multimedia/openshot: Updated for version 4.0.1 multimedia/qdvdauthor: Orphaned (unmaintained). multimedia/ucview: Orphaned (unmaintained). multimedia/vvdec: Updated for version 3.2.0 + new maintainer multimedia/vvenc: Updated for version 1.14.0 + new maintainer multimedia/w_scan: Orphaned (unmaintained). multimedia/webvfx: Orphaned (unmaintained). network/NetworkManager-strongswan: Updated for version 1.6.6 network/armcord: Orphaned (unmaintained). network/arno-iptables-firewall: Orphaned (unmaintained). network/beegfs: Orphaned (unmaintained). network/bmon: Updated for version 5.0. network/bottle: Orphaned (unmaintained). network/brave-browser: update to 1.96.60 network/brave-origin: update to 1.96.60 network/choqok: Orphaned (unmaintained). network/discord: Version bump to 1.0.159 network/discord: Version bump to 1.0.160 network/dnsproxy-bin: Updated for version 0.86.0. network/dropbox: Updated for version 273.4.4708. network/element-desktop: Updated for version 1.12.30. network/exim: Updated for version 4.100.1. network/felinks: Updated for version 0.20.0. network/franz: Updated for version 6.9.0. network/gallery-dl: Updated for version 1.32.14 network/helium-browser: Updated for version 0.18.1.1 network/ip2location-c: Orphaned (unmaintained). network/ipv6calc: Orphaned (unmaintained). network/knock: Updated for version 0.8.2 + new maintainer network/librewolf: Updated for version 157.0_1 network/libvma: Orphaned (unmaintained). network/mstflint: New maintainer network/mullvad-browser: Updated for version 15.0.24 network/newsraft: Updated for version 0.38 network/node_exporter: Orphaned (unmaintained). network/opensm: New maintainer network/opera: Updated for version 136.0.6008.80 network/protonmail-bridge: Updated for version 3.27.0. network/rdma-core: New maintainer. network/repology-cli: Removed patch network/rspamd: Updated for version 4.2.0 network/rtorrent: Updated for version 0.16.24. network/scrcpy: Updated for version 4.1. network/thorium-browser: Orphaned (unmaintained). network/tntnet: Updated for version 4.2 + new maintainer network/tor-browser: Updated for version 15.0.24. network/tunctl: Updated script + new maintainer. network/vivaldi: Updated for version 8.2.4133.80. network/waterfox: Updated for version 6.7.5 network/zen-browser: Updated for version 1.22.3b office/1password: Orphaned (unmaintained). office/cpdf: Updated for version 2.9.2. office/djvusmooth: Orphaned (nobody wants it). office/epdfview: New maintainer. office/hebcal: Updated for version 5.16.0. office/lumina-calculator: Orphaned (unmaintained). office/lumina-pdf: Orphaned (unmaintained). office/lyx: Updated for version 2.5.3. office/mupdf: Updated for version 1.28.5. office/pandoc: update to 3.12 office/qownnotes: Updated for version 26.10.0. office/qtrans: Orphaned (unmaintained). office/smoffice2026: Updated for version 2026_1504 office/timew: Updated for version 1.10.0 + new maintainer office/vit: Updated REQUIRES. office/xpad: Updated for version 5.4.0 perl/perl-Cpanel-JSON-XS: Version bump to 4.53 perl/perl-Email-Sender: Updated for version 2.603. perl/perl-MooX-Types-MooseLike: Updated REQUIRES perl/perl-Throwable: Updated REQUIRES and changed to noarch. python/asgiref: Removed (renamed to python3-asgiref) python/functools-lru-cache: New maintainer. python/python2-lxml: Orphaned (unmaintained). python/python2-sympy: Orphaned (unmaintained). python/python3-argon2-cffi-bindings: Update README python/python3-caldav: Version bump to 3.3.1 python/python3-configargparse: Updated for version 1.8.0. python/python3-cython-opt: updated for version 3.3.0 python/python3-debugpy: Update README python/python3-deprecated: Note on why we can't update python/python3-discovery: Version bump to 1.6.1 python/python3-evdev: Revert back to 1.9.3 python/python3-freezegun: Added (Time manipulation in python tests). python/python3-geventhttpclient: Updated for version 2.4.0. python/python3-hatch_jupyter_builder: Update README python/python3-icalendar-searcher: Note on why we can't update python/python3-jh2: Version bump to 5.0.15 python/python3-jinxed: Added (Subset of curses library). python/python3-knowit: Note on why we can't update python/python3-lazy_loader: Version bump to 0.6 python/python3-levenshtein: Allow building with newer Cython python/python3-lupa: Added (Integrate Lua with Python) python/python3-msal: Version bump to 1.39.0 python/python3-niquests: Version bump to 3.21.2 python/python3-nvchecker: Added (New version checker). python/python3-payload_dumper: Added (Dump Android payload.bin). python/python3-propcache: Allow building with newer Cython python/python3-pytz: Version bump to 2026.4 python/python3-qh3: Version bump to 2.0.4 python/python3-rapidfuzz: Allow building with newer Cython python/python3-sentry_sdk: Updated for version 2.71.0 python/python3-setproctitle: Update for 1.3.8 python/python3-setuptools-gettext: Updated for version 0.1.19 python/python3-slugify: Version bump to 9.1.2 python/python3-soupsieve: Version bump to 2.8.4 python/python3-statsmodels: Update README python/python3-structlog: Added (Structured logging for Python). python/python3-sympy: New maintainer python/python3-threadpoolctl: Version bump to 3.7.0 python/python3-tornado: Version bump to 6.5.10 python/python3-trakit: Note on why we can't update python/python3-urllib3-future: Version bump to 2.25.901 python/sqlparse: Removed (renamed to python3-sqlparse) python/subprocess32: Orphaned (unmaintained). python/traitlets: Version bump to 5.15.1 python/uv-bin: Updated for version 0.12.20. python/uv-bin: Updated for version 0.12.21. system/EpsonTMXCUPS: Orphaned (unmaintained). system/Iosevka-slab: Updated for version 34.9.0 system/Iosevka: Updated for version 34.9.0 system/PeaZip: Updated for version 11.3.0. system/PrintNode: Orphaned (unmaintained). system/archivemount: Updated for version 1c. system/aufs-dir-tools: Updated for version 0.1.1. system/augeas: Updated for version 1.15.0. system/cantarell-fonts: New Maintainer and updated to version 0.311 system/ccid: Updated for version 1.8.4. system/chronograf: Updated for version 1.11.5 system/conky: Updated for version 1.25.1. system/corectrl: Orphaned (unmaintained). system/cwtex-q-fonts-TTFs: New Maintainer system/davfs2: Orphaned (unmaintained). system/dool: Orphaned (unmaintained). system/doublecmd-qt5: Updated for version 1.2.9 system/duf: Added (Disk usage/free utility). system/efitools: Orphaned (unmaintained). system/fuse-archive: Updated for version 1.24. system/gnsu: Updated for version 0.4.0. system/incus: Updated for version 7.5 system/limine: Updated for version 12.9.1 system/lirc: Don't clobber the system lirc.4 manpage system/lshw: Orphaned (unmaintained). system/mbuffer: Updated for version 20260926 system/mongodb: Updated for version 8.3.11. system/mpich: Updated for version 5.0.2 system/netdata: Updated for version 2.12.0. system/nvidia-driver: Updated for version 595.104.02. system/nvidia-fabricmanager: Orphaned (unmaintained). system/nvidia-kernel: Updated for version 595.104.02. system/nvidia-legacy390-driver: Updated script. system/nvidia-legacy470-driver: Updated script. system/openzfs: updated for version 2.4.4 system/otf-ebgaramond-fonts: Added (Garamond font). system/pax-utils: Updated for version 1.3.11. system/pcsc-perl: Version bump to 1.4.16 system/pcsc-tools: Version bump to 1.7.5 system/peektea: Added (Terminal file browser). system/powerpanel: Orphaned (unmaintained). system/prometheus: Updated for version 3.15.0 system/pueue: Added (Task management tool). system/radeon-profile: Orphaned (unmaintained). system/s6-rc: Fix default boot database path. system/sbsigntools: Orphaned (unmaintained). system/slpkg: Updated for version 6.1.7. system/srm: Orphaned (unmaintained). system/superfile: Added (File manager). system/terminalia-fonts: Updated for version 1.020 system/trash-cli: Update for 0.26.9.29 system/ttf-aller: New maintainer system/ttf-caladea: Updated to version 20200211 system/ttf-carlito: Updated to version 20230309 system/ttf-coda: New Maintainer system/ttf-crosscorefonts: Updated to version 20260427 system/ttf-monaco: New Maintainer system/ttf-nerd-fonts-jetbrains-mono: Added (JetBrains Mono Font). system/ttf-nerd-fonts-monoid: Added (Monoid Nerd Font). system/ttf-open-sans: Updated to version 3.003 system/ttf-roboto: Updated for version 3.016 + new maintainer system/ttf-zekton: New maintainer system/x86_energy_perf_policy: Updated for version 5.15.209. system/xchm: Updated for version 1.40. system/yabsm: Removed (Maintainer's request). system/yelp: Use meson setup. system/zramen: Updated for version 1.0.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From ozan.turkyilmaz at gmail.com Sat Oct 3 06:50:50 2026 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 3 Oct 2026 09:50:50 +0300 Subject: [Slackbuilds-users] Back from hiatus Message-ID: Hello All, I am back from hiatus on limited bases. Regards, Ozan -------------- next part -------------- An HTML attachment was scrubbed... URL: From duncan_roe at optusnet.com.au Sat Oct 3 10:18:49 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sat, 3 Oct 2026 20:18:49 +1000 Subject: [Slackbuilds-users] Back from hiatus In-Reply-To: References: Message-ID: Hi all, Sorry about this but I couldn't resist On Sat, Oct 03, 2026 at 09:50:50AM +0300, Ozan T?rky?lmaz wrote: > Hello All, > > I am back from hiatus on limited bases. Cut out the ryhme you're wasting time > > Regards, > Ozan Cheers ... Duncan. From zsd+slackbuilds at jdvb.ca Sat Oct 3 13:46:52 2026 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Sat, 3 Oct 2026 10:46:52 -0300 Subject: [Slackbuilds-users] pstoedit In-Reply-To: <20261003090232.6a7bbef8@home.slackie.org> References: <20261003090232.6a7bbef8@home.slackie.org> Message-ID: <20261003.134652.GA28620@x360.localdomain> Hi, Trying to update pstoedit: ... make[2]: Leaving directory '/usr/local/SBo/pstoedit-4.3/src' make[1]: Leaving directory '/usr/local/SBo/pstoedit-4.3/src' Making all in doc make[1]: *** No rule to make target 'pstoedit.1', needed by 'all-am'. Stop. make[1]: Entering directory '/usr/local/SBo/pstoedit-4.3/doc' make[1]: Leaving directory '/usr/local/SBo/pstoedit-4.3/doc' make: *** [Makefile:415: all-recursive] Error 1 Package: 0:00:30 Failures: pstoedit: pstoedit.SlackBuild returned non-zero. Is this a "me" problem? Or are other people having this issue? Thanks. Jim From jebrhansen+SBo at gmail.com Sat Oct 3 16:29:12 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 3 Oct 2026 09:29:12 -0700 Subject: [Slackbuilds-users] pstoedit In-Reply-To: <20261003.134652.GA28620@x360.localdomain> References: <20261003090232.6a7bbef8@home.slackie.org> <20261003.134652.GA28620@x360.localdomain> Message-ID: It built fine for me on my main machine and on a clean chroot: +++++++++++++++++++++++++++++++++++++++++++ SUMMARY LOG Using the SBo repository for Slackware 15.0 Queue Process: Download, build, and install pstoedit: MD5SUM check for pstoedit-4.3.tar.gz ... OK Building package pstoedit-4.3-x86_64-1_SBo.tgz ... OK Installing package pstoedit-4.3-x86_64-1_SBo.tgz ... OK +++++++++++++++++++++++++++++++++++++++++++ ########################################### Queue process complete! ########################################### root at chroot.eEVj6:/$ Jeremy On Sat, Oct 3, 2026, 6:47?AM Jim via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hi, > > Trying to update pstoedit: > > ... > make[2]: Leaving directory '/usr/local/SBo/pstoedit-4.3/src' > make[1]: Leaving directory '/usr/local/SBo/pstoedit-4.3/src' > Making all in doc > make[1]: *** No rule to make target 'pstoedit.1', needed by 'all-am'. > Stop. > make[1]: Entering directory '/usr/local/SBo/pstoedit-4.3/doc' > make[1]: Leaving directory '/usr/local/SBo/pstoedit-4.3/doc' > make: *** [Makefile:415: all-recursive] Error 1 > > Package: 0:00:30 > > Failures: > pstoedit: pstoedit.SlackBuild returned non-zero. > > > Is this a "me" problem? Or are other people having this issue? > > Thanks. > > Jim > > _______________________________________________ > 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 zsd+slackbuilds at jdvb.ca Sat Oct 3 17:54:33 2026 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Sat, 3 Oct 2026 14:54:33 -0300 Subject: [Slackbuilds-users] pstoedit In-Reply-To: References: <20261003090232.6a7bbef8@home.slackie.org> <20261003.134652.GA28620@x360.localdomain> Message-ID: <20261003.175433.GA30471@x360.localdomain> Jeremy, thanks. Please see below. On Sat, Oct 3, 2026 at 09:29 (-0700), Jeremy Hansen wrote: > It built fine for me on my main machine and on a clean chroot: > +++++++++++++++++++++++++++++++++++++++++++ > SUMMARY LOG > Using the SBo repository for Slackware 15.0 > Queue Process: Download, build, and install > pstoedit: > MD5SUM check for pstoedit-4.3.tar.gz ... OK > Building package pstoedit-4.3-x86_64-1_SBo.tgz ... OK > Installing package pstoedit-4.3-x86_64-1_SBo.tgz ... OK > +++++++++++++++++++++++++++++++++++++++++++ Thanks very much for responding. If, by "clean chroot", you mean no SBo packages at all, I guess I must have broken something, somewhere, somehow on my system. I see in 4.01 the pstoedit.1 file is in the distfile, but in 4.3 the pstoedit.1 file is not in the distfile. Are you able to tell me what Makefile rule your system used to create pstoedit.1 ? Thanks. Jim > On Sat, Oct 3, 2026, 6:47?AM Jim via SlackBuilds-users < > slackbuilds-users at slackbuilds.org> wrote: >> Hi, >> Trying to update pstoedit: >> ... >> make[2]: Leaving directory '/usr/local/SBo/pstoedit-4.3/src' >> make[1]: Leaving directory '/usr/local/SBo/pstoedit-4.3/src' >> Making all in doc >> make[1]: *** No rule to make target 'pstoedit.1', needed by 'all-am'. >> Stop. >> make[1]: Entering directory '/usr/local/SBo/pstoedit-4.3/doc' >> make[1]: Leaving directory '/usr/local/SBo/pstoedit-4.3/doc' >> make: *** [Makefile:415: all-recursive] Error 1 >> Package: 0:00:30 >> Failures: >> pstoedit: pstoedit.SlackBuild returned non-zero. >> Is this a "me" problem? Or are other people having this issue? >> Thanks. >> Jim >> _______________________________________________ >> 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 daniel.stolarski at gmail.com Sat Oct 3 18:34:03 2026 From: daniel.stolarski at gmail.com (Daniel Stolarski) Date: Sat, 3 Oct 2026 20:34:03 +0200 Subject: [Slackbuilds-users] swig 4.5.x on -current breaking builds Message-ID: This is just FYI: swig 4.5.x no longer supports the python2 api, so e.g. gdal will not build any longer. For details, see https://www.swig.org/Doc4.5/Python.html#Python_nn53 (at the bottom of section 33.8). Renaming the function calls (e.g. s/PyOld/PyNew/) in the source fixes the issue. regards, d.s. From urchlay at slackware.uk Sat Oct 3 22:50:41 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 3 Oct 2026 18:50:41 -0400 (EDT) Subject: [Slackbuilds-users] pstoedit In-Reply-To: <20261003.134652.GA28620@x360.localdomain> References: <20261003090232.6a7bbef8@home.slackie.org> <20261003.134652.GA28620@x360.localdomain> Message-ID: <6625a28b-f087-85f4-3e8-15f2eb85257@slackware.uk> On Sat, 3 Oct 2026, Jim via SlackBuilds-users wrote: > make[2]: Leaving directory '/usr/local/SBo/pstoedit-4.3/src' > make[1]: Leaving directory '/usr/local/SBo/pstoedit-4.3/src' > Making all in doc > make[1]: *** No rule to make target 'pstoedit.1', needed by 'all-am'. Stop. > make[1]: Entering directory '/usr/local/SBo/pstoedit-4.3/doc' > make[1]: Leaving directory '/usr/local/SBo/pstoedit-4.3/doc' > make: *** [Makefile:415: all-recursive] Error 1 > > Is this a "me" problem? Or are other people having this issue? Did you skip the T series when installing Slackware? It looks like it's using texlive to generate the man page. From zsd+slackbuilds at jdvb.ca Sun Oct 4 00:01:30 2026 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Sat, 3 Oct 2026 21:01:30 -0300 Subject: [Slackbuilds-users] pstoedit In-Reply-To: <6625a28b-f087-85f4-3e8-15f2eb85257@slackware.uk> References: <20261003090232.6a7bbef8@home.slackie.org> <20261003.134652.GA28620@x360.localdomain> <6625a28b-f087-85f4-3e8-15f2eb85257@slackware.uk> Message-ID: <20261004.000130.GG30471@x360.localdomain> On Sat, Oct 3, 2026 at 18:50 (-0400), B. Watson wrote: > On Sat, 3 Oct 2026, Jim via SlackBuilds-users wrote: >> make[2]: Leaving directory '/usr/local/SBo/pstoedit-4.3/src' >> make[1]: Leaving directory '/usr/local/SBo/pstoedit-4.3/src' >> Making all in doc >> make[1]: *** No rule to make target 'pstoedit.1', needed by 'all-am'. Stop. >> make[1]: Entering directory '/usr/local/SBo/pstoedit-4.3/doc' >> make[1]: Leaving directory '/usr/local/SBo/pstoedit-4.3/doc' >> make: *** [Makefile:415: all-recursive] Error 1 >> Is this a "me" problem? Or are other people having this issue? > Did you skip the T series when installing Slackware? It looks > like it's using texlive to generate the man page. Thanks for that. I wish I had read your email 10 minutes earlier before I figured it out myself. No, I don't have the T series installed. Instead, I have TeXlive installed, so the T series is mostly(!) redundant. And TL is not in root's PATH, thus pdflatex is not found when configure is configuring. [[ Yes, I know I am supposed to have everything installed for Slackbuilds to work, but this is the first time I've ever run into this problem. ]] Having said that, I see that if configure doesn't find pdflatex, in the generated doc/Makefile it comments out the part which creates the man page from the LaTeX source (this makes sense). However, the doc/Makefile nonetheless cheerfully insists that pstoedit.1 must exist. This was OK in the previous version, where a pstoedit.1 file was included in the dist file, but it isn't really so good without it, as in the current version. I could argue that this is a bug in the pstoedit source package, but I'm not sure I want to spend time convincing someone that this is a problem. I thought I'd send this explanation to this list in case there is some other person in the world who didn't install the T series. Cheers. Jim From duncan_roe at optusnet.com.au Sun Oct 4 03:24:15 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sun, 4 Oct 2026 14:24:15 +1100 Subject: [Slackbuilds-users] cinelerra 5.1.20260531 only builds under current Message-ID: Hi all, ffmpeg-4.4.7 in 15.0 is too old for cinelerra to build now - gets errors from undeclared items in not ffmpeg's header files. Cheers ... Duncan. From willysr at slackbuilds.org Sun Oct 4 03:44:00 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 4 Oct 2026 10:44:00 +0700 Subject: [Slackbuilds-users] cinelerra 5.1.20260531 only builds under current In-Reply-To: References: Message-ID: <20261004104400.7eae4f2b@home.slackie.org> >ffmpeg-4.4.7 in 15.0 is too old for cinelerra to build now - gets errors from >undeclared items in not ffmpeg's header files. it builds just fine on our CI https://gitlab.com/SlackBuilds.org/slackbuilds/-/merge_requests/915 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From urchlay at slackware.uk Sun Oct 4 08:51:23 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 4 Oct 2026 04:51:23 -0400 (EDT) Subject: [Slackbuilds-users] Template updates, 20261004 Message-ID: <1a41afe2-7afc-ac68-45bc-819cb36b23cf@slackware.uk> Announcing: New updates to the SBo build templates. We thought about holding this back until the Slackware 16.0 release, but we decided it's useful for whatever remaining time 15.0 has, too. As always, you can get the templates here: https://slackbuilds.org/templates/ ...or by doing this: git clone git://git.slackbuilds.org/templates.git What does this mean for your SlackBuild scripts? For existing scripts, nothing yet. As you update your scripts, we encourage you to modify them to align with the new template, but we don't expect everyone to update all their scripts *just* to make them match the new stuff. For totally new scripts that aren't updates of existing ones, please base them on the new template. For now, we're not actually going to enforce this, but eventually (probably after the Slackware 16.0 release), we will add new checks to sbolint to make it complain about outdated template code. The most important changes: - We now have not one but two rust templates. One for builds that will list dozens of .crate files in DOWNLOAD, and a rust-vendored template (with support scripts) for those who prefer to "vendor" the required sources and have the ability to host a tarball on some web server. The support scripts are cargo-mkvendored.sh for rust-vendored-template, and gen_crate_dependencies.sh for rust-template. - The new find/chmod template that was discussed on this list a while back is finally implemented. It's faster than the old template, and also more accurate (doesn't trip over broken symlinks, and catches "weird" permissions like 501 or 701). - No more "chown -R root:root ." after tarball extraction. Instead, the tarball is extracted with --no-same-owner, which creates the files as root:root in the first place. - rubygem-template no longer installs file in /usr/doc/$PRGNAM-$VERSION with incorrect permissions/ownership. It also now uses the SLKCFLAGS, instead of setting them and then not passing them to 'gem install'. - All the templates now use a new variable PKGDOC, to help avoid repetitious code. What used to be written as this: mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cp -a \ \ $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild is now written: PKGDOC=$PKG/usr/doc/$PRGNAM-$VERSION mkdir -p $PKGDOC cp -a \ \ $PKGDOC cat $CWD/$PRGNAM.SlackBuild > $PKGDOC/$PRGNAM.SlackBuild ...which is more maintainable (see "DRY Principle"). - In the same vein, the section that sets SLKCFLAGS based on ARCH has been condensed. - Some extra commentary, e.g. a section explaining "make -j1". From 1.41421 at gmail.com Sun Oct 4 17:22:08 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 4 Oct 2026 11:22:08 -0600 Subject: [Slackbuilds-users] libopenshot not building Message-ID: For a few weeks now libopenshot has been refusing to build for me: -- The following features have been disabled: * Coverage, analyze test coverage and generate report * IWYU (include-what-you-use), Scan all source files with 'iwyu' * Wayland screen capture, Use the optional xdg-desktop-portal and PipeWire capture module -- The following OPTIONAL packages have not been found: * Resvg -- Configuring done -- Generating done -- Build files have been written to: /tmp/SBo/libopenshot-1.0.1/build [ 1%] Running cpp protocol buffer compiler on trackerdata.proto /usr/bin/protoc: error while loading shared libraries: libabsl_die_if_null.so.2508.0.0: cannot open shared object file: No such file or directory make[2]: *** [src/CMakeFiles/openshot_autogen.dir/build.make:97: src/trackerdata.pb.h] Error 127 make[1]: *** [CMakeFiles/Makefile2:2929: src/CMakeFiles/openshot_autogen.dir/all] Error 2 make: *** [Makefile:166: all] Error 2 I have all the required packages installed, and there is no libasl* shared library in any of them, or anywhere else in the system, at that. -------------- next part -------------- An HTML attachment was scrubbed... URL: From heiko.rosemann at web.de Sun Oct 4 17:37:17 2026 From: heiko.rosemann at web.de (Heiko Rosemann) Date: Sun, 4 Oct 2026 19:37:17 +0200 Subject: [Slackbuilds-users] libopenshot not building In-Reply-To: References: Message-ID: <7b07146b-319d-4174-a91e-18e81c8b5d61@web.de> On 10/4/26 7:22 PM, Luveh Keraph wrote: > For a few weeks now libopenshot has been refusing to build for me: > [...] > I have all the required packages installed, and there is no libasl* > shared library in any of them, or anywhere else in the system, at > that. libabsl* (not libasl*, note the b in there) comes from abseil-cpp. For 15.0 that's a SlackBuild from SlackBuilds.org, for -current it's part of Slackware. And it's a dependency of protobuf, for which the same is true (protobuf3 on SlackBuilds.org for 15.0). That's why /usr/bin/protoc can't run without it. 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.asc Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From jebrhansen+SBo at gmail.com Sun Oct 4 18:04:12 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 4 Oct 2026 11:04:12 -0700 Subject: [Slackbuilds-users] libopenshot not building In-Reply-To: References: Message-ID: On Sun, Oct 4, 2026, 10:22?AM Luveh Keraph <1.41421 at gmail.com> wrote: > For a few weeks now libopenshot has been refusing to build for me: > > -- The following features have been disabled: > > * Coverage, analyze test coverage and generate report > * IWYU (include-what-you-use), Scan all source files with 'iwyu' > * Wayland screen capture, Use the optional xdg-desktop-portal and > PipeWire capture module > > -- The following OPTIONAL packages have not been found: > > * Resvg > > -- Configuring done > -- Generating done > -- Build files have been written to: /tmp/SBo/libopenshot-1.0.1/build > [ 1%] Running cpp protocol buffer compiler on trackerdata.proto > /usr/bin/protoc: error while loading shared libraries: > libabsl_die_if_null.so.2508.0.0: cannot open shared object file: No such > file or directory > make[2]: *** [src/CMakeFiles/openshot_autogen.dir/build.make:97: > src/trackerdata.pb.h] Error 127 > make[1]: *** [CMakeFiles/Makefile2:2929: > 127 errors are usually due to mismatched APIs. This probably means something was upgraded that broke existing compatibility without rebuilding the packages that rely on it. protoc is from the protobuf3 package and it refers to libabsl_die_if_null.so.2508.0.0 from the absel-cpp package. However, the 2508.0.0 in the filename tells me it is trying to reference the 20250814.0 version from August of 2025. It's now on 20260817.0 from August 2026. You should just need to rebuild protobuf3 (so it can properly link to the newer absel-cpp) to get the protoc command to work. Hopefully that will be enough to get the build to complete. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sun Oct 4 18:27:45 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 4 Oct 2026 12:27:45 -0600 Subject: [Slackbuilds-users] libopenshot not building In-Reply-To: References: Message-ID: Thanks. I rebuilt protobuf3 (and absel-cpp, for good measure) and after doing so the libopenshot build process is ongoing without choking as I described. On Sun, Oct 4, 2026 at 12:04?PM Jeremy Hansen wrote: > On Sun, Oct 4, 2026, 10:22?AM Luveh Keraph <1.41421 at gmail.com> wrote: > >> For a few weeks now libopenshot has been refusing to build for me: >> >> -- The following features have been disabled: >> >> * Coverage, analyze test coverage and generate report >> * IWYU (include-what-you-use), Scan all source files with 'iwyu' >> * Wayland screen capture, Use the optional xdg-desktop-portal and >> PipeWire capture module >> >> -- The following OPTIONAL packages have not been found: >> >> * Resvg >> >> -- Configuring done >> -- Generating done >> -- Build files have been written to: /tmp/SBo/libopenshot-1.0.1/build >> [ 1%] Running cpp protocol buffer compiler on trackerdata.proto >> /usr/bin/protoc: error while loading shared libraries: >> libabsl_die_if_null.so.2508.0.0: cannot open shared object file: No such >> file or directory >> make[2]: *** [src/CMakeFiles/openshot_autogen.dir/build.make:97: >> src/trackerdata.pb.h] Error 127 >> make[1]: *** [CMakeFiles/Makefile2:2929: >> > > 127 errors are usually due to mismatched APIs. This probably means > something was upgraded that broke existing compatibility without rebuilding > the packages that rely on it. > > protoc is from the protobuf3 package and it refers to > libabsl_die_if_null.so.2508.0.0 from the absel-cpp package. However, > the 2508.0.0 in the filename tells me it is trying to reference the > 20250814.0 version from August of 2025. It's now on 20260817.0 from August > 2026. > > You should just need to rebuild protobuf3 (so it can properly link to the > newer absel-cpp) to get the protoc command to work. Hopefully that will be > enough to get the build to complete. > > Jeremy > _______________________________________________ > 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 urchlay at slackware.uk Sun Oct 4 21:05:53 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 4 Oct 2026 17:05:53 -0400 (EDT) Subject: [Slackbuilds-users] libopenshot not building In-Reply-To: References: Message-ID: <7bb71c48-e69b-851e-c8ab-5b4f24e3ec6f@slackware.uk> On Sun, 4 Oct 2026, Luveh Keraph wrote: > /usr/bin/protoc: error while loading shared libraries: libabsl_die_if_null.so.2508.0.0: cannot open shared object file: No such file or directory > I have all the required packages installed, and there is no libasl* shared library in any of them, or anywhere else in the system, at that. There should be, the libasl_*.so stuff is part of the protobuf3 package. So is the protoc command (which is what failed, above). Probably you can fix this by rebuilding and reinstalling protobuf3. From phalange at komputermatrix.com Mon Oct 5 00:56:14 2026 From: phalange at komputermatrix.com (phalange at komputermatrix.com) Date: Sun, 04 Oct 2026 20:56:14 -0400 Subject: [Slackbuilds-users] Template updates, 20261004 In-Reply-To: <1a41afe2-7afc-ac68-45bc-819cb36b23cf@slackware.uk> References: <1a41afe2-7afc-ac68-45bc-819cb36b23cf@slackware.uk> Message-ID: These are nice improvements, much appreciated. On 2026-10-04 04:51, B. Watson wrote: > Announcing: New updates to the SBo build templates. > > We thought about holding this back until the Slackware 16.0 release, > but we decided it's useful for whatever remaining time 15.0 has, too. > > As always, you can get the templates here: > > https://slackbuilds.org/templates/ > > ...or by doing this: > > git clone git://git.slackbuilds.org/templates.git > > What does this mean for your SlackBuild scripts? For existing scripts, > nothing yet. As you update your scripts, we encourage you to modify > them > to align with the new template, but we don't expect everyone to update > all their scripts *just* to make them match the new stuff. > > For totally new scripts that aren't updates of existing ones, please > base them on the new template. For now, we're not actually going > to enforce this, but eventually (probably after the Slackware 16.0 > release), we will add new checks to sbolint to make it complain about > outdated template code. > > The most important changes: > > - We now have not one but two rust templates. One for builds that > will list dozens of .crate files in DOWNLOAD, and a rust-vendored > template (with support scripts) for those who prefer to "vendor" > the required sources and have the ability to host a tarball on > some web server. The support scripts are cargo-mkvendored.sh > for rust-vendored-template, and gen_crate_dependencies.sh > for rust-template. > > - The new find/chmod template that was discussed on this list a > while back is finally implemented. It's faster than the old > template, and also more accurate (doesn't trip over broken > symlinks, and catches "weird" permissions like 501 or 701). > > - No more "chown -R root:root ." after tarball extraction. > Instead, the tarball is extracted with --no-same-owner, which > creates the files as root:root in the first place. > > - rubygem-template no longer installs file in /usr/doc/$PRGNAM-$VERSION > with incorrect permissions/ownership. It also now uses the SLKCFLAGS, > instead of setting them and then not passing them to 'gem install'. > > - All the templates now use a new variable PKGDOC, to help avoid > repetitious code. What used to be written as this: > > mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION > cp -a \ > \ > $PKG/usr/doc/$PRGNAM-$VERSION > cat $CWD/$PRGNAM.SlackBuild > > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild > > is now written: > > PKGDOC=$PKG/usr/doc/$PRGNAM-$VERSION > mkdir -p $PKGDOC > cp -a \ > \ > $PKGDOC > cat $CWD/$PRGNAM.SlackBuild > $PKGDOC/$PRGNAM.SlackBuild > > ...which is more maintainable (see "DRY Principle"). > > - In the same vein, the section that sets SLKCFLAGS based on ARCH > has been condensed. > > - Some extra commentary, e.g. a section explaining "make -j1". > _______________________________________________ > 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 duncan_roe at optusnet.com.au Mon Oct 5 05:03:48 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Mon, 5 Oct 2026 16:03:48 +1100 Subject: [Slackbuilds-users] Template updates, 20261004 In-Reply-To: <1a41afe2-7afc-ac68-45bc-819cb36b23cf@slackware.uk> References: <1a41afe2-7afc-ac68-45bc-819cb36b23cf@slackware.uk> Message-ID: On Sun, Oct 04, 2026 at 04:51:23AM -0400, B. Watson wrote: > > Announcing: New updates to the SBo build templates. > w.r.t. make, I was going to suggest `make || make -j1 V=1` Like Pat does in his SBs, except add V=1. Whether or not you're using MAKEFLAGS=-j, this reduces the log file size (if you keep logs) and gives you diagnostics when you want them. Ah well, maybe next time... Cheers ... Duncan. From urchlay at slackware.uk Mon Oct 5 06:16:09 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 5 Oct 2026 02:16:09 -0400 (EDT) Subject: [Slackbuilds-users] Template updates, 20261004 In-Reply-To: References: <1a41afe2-7afc-ac68-45bc-819cb36b23cf@slackware.uk> Message-ID: On Mon, 5 Oct 2026, Duncan Roe via SlackBuilds-users wrote: > w.r.t. make, I was going to suggest > > `make || make -j1 V=1` > > Like Pat does in his SBs, except add V=1. > > Whether or not you're using MAKEFLAGS=-j, this reduces the log file size (if > you keep logs) and gives you diagnostics when you want them. Well, I'd want that to be written: make V=1 || make -j1 V=1 I don't want to only see the verbose make output if make fails the first time around. The diagnostics I want to see include the actual compiler flags, to verify that SLKCFLAGS are actually getting passed properly, and not being overridden later on the command line. For instance, if the compile command looks like: gcc -g -Dwhatever=1 -I./include -O0 -c foo.c ...then I know SLKCFLAGS aren't being passed (because I don't see -O2 -fPIC, or the --march=i586 stuff if I'm on 32-bit). Another example: gcc -O2 -fPIC -Dwhatever=1 -I./include -O3 -c foo.c ...the "-O2 -fPIC" came from SLKCFLAGS. But, following that there's a -O3. The -O options are taken in order, and the last one wins, so that means it's being built with -O3. In a case like that, there are 2 choices: 1. Let upstream win. Get rid of SLKCFLAGS entirely, let them use the flags they want. 2. Patch or sed the Makefile (or configure, meson, cmake, etc script) to get rid of the offending -O3. For most stuff, I tend to choose the 2nd option. But for anything that really needs performance (emulators, realtime audio processing), I might leave upstream's flags in place. A few builds, I've even gone to the trouble of making the flags user-selectable, controlled with e.g. FORCE_SLACK_CFLAGS=yes in the environment. Not sure anyone (including me) ever actually cared enough to set that variable though. The disadvantage of "make || make -j1" (with or without V=1) is, I might not notice that the initial make fails... if I know "make -j9" will fail, I might actually be able to fix it by patching the Makefile. Which will benefit everyone (or at least everyone who sets MAKEFLAGS). From erich.public at protonmail.com Mon Oct 5 15:37:52 2026 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 05 Oct 2026 15:37:52 +0000 Subject: [Slackbuilds-users] libopenshot not building In-Reply-To: References: Message-ID: On Sunday, October 4th, 2026 at 1:28 PM, Luveh Keraph <1.41421 at gmail.com> wrote: > Thanks. I rebuilt protobuf3 (and absel-cpp, for good measure) and after doing so the libopenshot build process is ongoing without choking as I described. > If you're using slackrepo the permanent fix is to add this to protobuf-c.hint (in /var/lib/slackrepo//hintfiles/protobuf-c.hint): ADDREQUIRES="abseil-cpp" That will force protobuf-c to be rebuilt whenever abseil-cpp is upgraded. slackrepo doesn't rebuild packages when a dep of a dep gets upgraded; it only rebuilds when direct dependencies get upgraded. Erich From slack at giand.it Mon Oct 5 20:43:09 2026 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Mon, 5 Oct 2026 22:43:09 +0200 Subject: [Slackbuilds-users] sbolint error Message-ID: <62ff277f-4f97-4ba2-9b74-b7d0b6390ebf@giand.it> sbolint reports an error about the installation of douninst.sh, but the package includes this file. This is the end of the stream of the slackbuild script and the result of sbolint [cut] Creating Slackware package:? /tmp/postgis-3.6.4-x86_64-1_SBo.tgz ./ install/ install/doinst.sh install/douninst.sh install/slack-desc usr/ usr/bin/ [cut] Slackware package /tmp/postgis-3.6.4-x86_64-1_SBo.tgz created. [cut] root at giand:/packages/sbo/org/tarball/postgis# sbolint postgis: ERR: postgis.SlackBuild: douninst.sh exists, but the script doesn't install it sbolint: postgis: errors 1, warnings 0 root at giand:/packages/sbo/org/tarball/postgis# The code of the slackbuild script includes these lines: mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc cat $CWD/doinst.sh > $PKG/install/doinst.sh cat $CWD/douninst.sh > $PKG/install/douninst.sh Where am I going wrong? -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From slack at giand.it Mon Oct 5 20:51:59 2026 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Mon, 5 Oct 2026 22:51:59 +0200 Subject: [Slackbuilds-users] sbolint error In-Reply-To: <62ff277f-4f97-4ba2-9b74-b7d0b6390ebf@giand.it> References: <62ff277f-4f97-4ba2-9b74-b7d0b6390ebf@giand.it> Message-ID: Il 05/10/26 22:43, Giancarlo Dess? ha scritto: > > > Where am I going wrong? > Sorry, please ignore this message, due main brain corrupted: the directory was updated with the new douninstall.sh file but not the other files (including the slackbuild script) -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From urchlay at slackware.uk Mon Oct 5 21:41:22 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 5 Oct 2026 17:41:22 -0400 (EDT) Subject: [Slackbuilds-users] sbolint error In-Reply-To: <62ff277f-4f97-4ba2-9b74-b7d0b6390ebf@giand.it> References: <62ff277f-4f97-4ba2-9b74-b7d0b6390ebf@giand.it> Message-ID: <75b05c94-d3e1-2c4f-3a67-4a9b5c1577@slackware.uk> On Mon, 5 Oct 2026, Giancarlo Dess? wrote: > sbolint reports an error about the installation of douninst.sh, but the > package includes this file. > postgis: ERR: postgis.SlackBuild: douninst.sh exists, but the script > doesn't install it > sbolint: postgis: errors 1, warnings 0 > root at giand:/packages/sbo/org/tarball/postgis# > > The code of the slackbuild script includes these lines: > > mkdir -p $PKG/install > cat $CWD/slack-desc > $PKG/install/slack-desc > cat $CWD/doinst.sh > $PKG/install/doinst.sh > cat $CWD/douninst.sh > $PKG/install/douninst.sh > > Where am I going wrong? It's not obvious from what you sent me... The postgis that's in the repo now doesn't have douninst.sh, so this is something you're working on currently. Is there any way you can tar up the slackbuild dir that causes the error, and email it to me? From dchmelik at gmail.com Tue Oct 6 00:52:28 2026 From: dchmelik at gmail.com (David Chmelik) Date: Mon, 5 Oct 2026 17:52:28 -0700 Subject: [Slackbuilds-users] txz? Message-ID: When it's Slackware v16, SBo could maybe upgrade to txz by default, right?? It's been Slackware standard for many years--if not 10+--and there are a few newer types.? One was maybe tlz which was tried briefly but maybe only better for text and not great for binaries, There's now a newer one I expect might be tried, that might be called zstd or something but I expect will have its own shorter extension or maybe is an upgrade/improvement to txz. -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Tue Oct 6 01:19:56 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 5 Oct 2026 21:19:56 -0400 (EDT) Subject: [Slackbuilds-users] txz? In-Reply-To: References: Message-ID: <5ebb66f7-4a4f-f824-d456-ff5d2a915f4c@slackware.uk> On Mon, 5 Oct 2026, David Chmelik wrote: > When it's Slackware v16, SBo could maybe upgrade to txz by default, right? You can make this the default already on your own Slackware box by putting "export PKGTYPE=txz" in the environment (like, in /root/.bashrc or such). > It's been Slackware standard for many years Slackware packages are generally built once (by Pat) and downloaded many times (by everyone else). So it makes sense for him to save a slight bit of bandwidth by using XZ compression. Built SBo packages are generally built on the system they're going to be installed on, or anyway aren't distributed over the Internet. The typical use case is to build the package (compressing it), then *immediately* install it (aka uncompressing it). The amount of local storage saved by using XZ might not outweigh the extra time spent on the better-but-slower XZ compression and decompression. My gut instinct is that using .txz by default isn't worth the extra time spent in compression, but that's not science... Hard numbers would be good. Maybe you (and me, and a few others) could actually benchmark it on real-world systems we actually use, with SBo packages of various sizes, and see what the results look like? I did just time "gz -9" vs. "xz -9" for a 99MB font package, and the results were that xz took almost 3x as long to compress it (16.7 sec vs. 6.5)... but the resulting compressed file was 3.2MB (the .gz one was 55MB). That's a single data point, can't extrapolate from it really. Hopefully others weigh in with their own opinions. Anyone? From ricardsonwilliams at gmail.com Tue Oct 6 01:57:19 2026 From: ricardsonwilliams at gmail.com (Ricardson) Date: Mon, 5 Oct 2026 22:57:19 -0300 Subject: [Slackbuilds-users] txz? In-Reply-To: References: Message-ID: I would also suggest considering .tlz packages using plzip. Slackware?s makepkg already supports the .tlz format, and automatically uses plzip for multithreaded compression when it is available. The number of threads can also be selected with --threads. The lzip format was designed with a strong focus on data integrity and recovery from corruption. Antonio D?az D?az, the author of lzip and plzip (and also ed), has written an interesting article about some of the design and reliability issues surrounding xz: https://www.nongnu.org/lzip/xz_inadequate.html .txz is certainly the safest default for compatibility, but .tlz could be a valuable alternative for Slackware users who prioritize robustness and parallel compression. On Mon, Oct 5, 2026 at 9:52?PM David Chmelik wrote: > > When it's Slackware v16, SBo could maybe upgrade to txz by default, right? It's been Slackware standard for many years--if not 10+--and there are a few newer types. One was maybe tlz which was tried briefly but maybe only better for text and not great for binaries, There's now a newer one I expect might be tried, that might be called zstd or something but I expect will have its own shorter extension or maybe is an upgrade/improvement to txz. > _______________________________________________ > 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 willysr at slackbuilds.org Tue Oct 6 02:17:24 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 6 Oct 2026 09:17:24 +0700 Subject: [Slackbuilds-users] txz? In-Reply-To: References: Message-ID: <20261006091724.202c1853@office64.slackie.org> >I would also suggest considering .tlz packages using plzip. > >Slackware?s makepkg already supports the .tlz format, and >automatically uses plzip for multithreaded compression when it is >available. > >The number of threads can also be selected with --threads. > >The lzip format was designed with a strong focus on data integrity and >recovery from corruption. Antonio D?az D?az, the author of lzip and >plzip (and also ed), has written an interesting article about some of >the design and reliability issues surrounding xz: > >https://www.nongnu.org/lzip/xz_inadequate.html > >.txz is certainly the safest default for compatibility, but .tlz could >be a valuable alternative for Slackware users who prioritize >robustness and parallel compression. Again, there's no stopping you to do that :) This is what i have on my /etc/profile export PKGTYPE="txz" you can change that to any type you prefer that works best on your environment -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From dchmelik at gmail.com Tue Oct 6 02:23:30 2026 From: dchmelik at gmail.com (David Chmelik) Date: Mon, 5 Oct 2026 19:23:30 -0700 Subject: [Slackbuilds-users] txz? In-Reply-To: <5ebb66f7-4a4f-f824-d456-ff5d2a915f4c@slackware.uk> References: <5ebb66f7-4a4f-f824-d456-ff5d2a915f4c@slackware.uk> Message-ID: On 10/5/26 6:19 PM, B. Watson wrote: > On Mon, 5 Oct 2026, David Chmelik wrote: > >> When it's Slackware v16, SBo could maybe upgrade to txz by default, >> right? > > You can make this the default already on your own Slackware box > by putting "export PKGTYPE=txz" in the environment (like, in > /root/.bashrc or such). > I did years ago but SBo .SlackBuild files still use tgz and I run many (not most) manually so end up redoing. >> It's been Slackware standard for many years > > Slackware packages are generally built once (by Pat) and downloaded > many times (by everyone else). So it makes sense for him to save a > slight bit of bandwidth by using XZ compression. > > Built SBo packages are generally built on the system they're going to > be installed on, or anyway aren't distributed over the Internet. The > typical use case is to build the package (compressing it), then > *immediately* install it (aka uncompressing it). The amount of local > storage saved by using XZ might not outweigh the extra time spent on > the better-but-slower XZ compression and decompression. > > My gut instinct is that using .txz by default isn't worth the extra > time spent in compression, but that's not science... > > Hard numbers would be good. Maybe you (and me, and a few others) could > actually benchmark it on real-world systems we actually use, with SBo > packages of various sizes, and see what the results look like? > > I did just time "gz -9" vs. "xz -9" for a 99MB font package, and > the results were that xz took almost 3x as long to compress it (16.7 > sec vs. 6.5)... but the resulting compressed file was 3.2MB (the .gz > one was 55MB). That's a single data point, can't extrapolate from it > really. > You have some major point.? I think I'd still use txz for fonts and some things to save space, but it sounds like for other things I might want to save time and not upgrade yet. > Hopefully others weigh in with their own opinions. Anyone? > I would also suggest considering .tlz packages using plzip. > > Slackware?s makepkg already supports the .tlz format, and > automatically uses plzip for multithreaded compression when it is > available. > > The number of threads can also be selected with --threads. > > The lzip format was designed with a strong focus on data integrity and > recovery from corruption. Antonio D?az D?az, the author of lzip and > plzip (and also ed), has written an interesting article about some of > the design and reliability issues surrounding xz: > > https://www.nongnu.org/lzip/xz_inadequate.html > > .txz is certainly the safest default for compatibility, but .tlz could > be a valuable alternative for Slackware users who prioritize > robustness and parallel compression. That all sounds good, and might partly solve the time issue?? I've definitely had txz packages been called corrupt several times, but haven't seen it for tgz.? How is tlz for saving space with binaries though? > On Mon, Oct 5, 2026 at 9:52?PM David Chmelik wrote: >> When it's Slackware v16, SBo could maybe upgrade to txz by default, right? It's been Slackware standard for many years--if not 10+--and there are a few newer types. One was maybe tlz which was tried briefly but maybe only better for text and not great for binaries, There's now a newer one I expect might be tried, that might be called zstd or something but I expect will have its own shorter extension or maybe is an upgrade/improvement to txz. From slack at giand.it Tue Oct 6 04:38:50 2026 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Tue, 6 Oct 2026 06:38:50 +0200 Subject: [Slackbuilds-users] sbolint error In-Reply-To: <75b05c94-d3e1-2c4f-3a67-4a9b5c1577@slackware.uk> References: <62ff277f-4f97-4ba2-9b74-b7d0b6390ebf@giand.it> <75b05c94-d3e1-2c4f-3a67-4a9b5c1577@slackware.uk> Message-ID: Il 05/10/26 23:41, B. Watson ha scritto: > > > On Mon, 5 Oct 2026, Giancarlo Dess? wrote: > >> sbolint reports an error about the installation of douninst.sh, but >> the package includes this file. > >> postgis: ERR: postgis.SlackBuild: douninst.sh exists, but the script >> doesn't install it >> sbolint: postgis: errors 1, warnings 0 >> root at giand:/packages/sbo/org/tarball/postgis# >> >> The code of the slackbuild script includes these lines: >> >> mkdir -p $PKG/install >> cat $CWD/slack-desc > $PKG/install/slack-desc >> cat $CWD/doinst.sh > $PKG/install/doinst.sh >> cat $CWD/douninst.sh > $PKG/install/douninst.sh >> >> Where am I going wrong? > > It's not obvious from what you sent me... > > The postgis that's in the repo now doesn't have douninst.sh, so this > is something you're working on currently. Is there any way you can tar > up the slackbuild dir that causes the error, and email it to me? Sorry, please ignore my message: I messed up. Usually I have a directory that stores the slackbuilds' files cleaned of any files I use for testing. Before the submission of a tarball I check with sbolint the package's directory. After testing the update for postgis, I copied into its directory the new file douninst.sh but not the slackbuild script, so sbolint has returned the error ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From yth at ythogtha.org Tue Oct 6 14:02:25 2026 From: yth at ythogtha.org (Yth =?UTF-8?B?T+KAmUd0aGE=?=) Date: Tue, 6 Oct 2026 16:02:25 +0200 Subject: [Slackbuilds-users] txz? In-Reply-To: <5ebb66f7-4a4f-f824-d456-ff5d2a915f4c@slackware.uk> References: <5ebb66f7-4a4f-f824-d456-ff5d2a915f4c@slackware.uk> Message-ID: <20261006160225.b3e255981a7e55c9499ccac7@ythogtha.org> > > When it's Slackware v16, SBo could maybe upgrade to txz by default, right? > > You can make this the default already on your own Slackware box > by putting "export PKGTYPE=txz" in the environment (like, in > /root/.bashrc or such). > > > It's been Slackware standard for many years > > Slackware packages are generally built once (by Pat) and downloaded > many times (by everyone else). So it makes sense for him to save a > slight bit of bandwidth by using XZ compression. > > Built SBo packages are generally built on the system they're going to > be installed on, or anyway aren't distributed over the Internet. The > typical use case is to build the package (compressing it), then > *immediately* install it (aka uncompressing it). The amount of local > storage saved by using XZ might not outweigh the extra time spent on > the better-but-slower XZ compression and decompression. > > My gut instinct is that using .txz by default isn't worth the extra > time spent in compression, but that's not science... > > Hard numbers would be good. Maybe you (and me, and a few others) could > actually benchmark it on real-world systems we actually use, with SBo > packages of various sizes, and see what the results look like? > > I did just time "gz -9" vs. "xz -9" for a 99MB font package, and > the results were that xz took almost 3x as long to compress it (16.7 > sec vs. 6.5)... but the resulting compressed file was 3.2MB (the .gz > one was 55MB). That's a single data point, can't extrapolate from it > really. > > Hopefully others weigh in with their own opinions. Anyone? It really depends on the data. I've been faced with having to fetch various data, logs and binary files, from a distant virtual machine, without much power (only 2 cores, not a lot of memory), repeatedly, for tests. And bzip2 was my choice, de/compressing is almost as fast as with gzip, while compression ratio was half-way to xz. My requirement here was the total time spent for compression + transmission + decompression, and it was the best using bzip2. bzip2 is often overlooked because it is neither the faster, nor the best, but the compromise is pretty strong. Today I've benchmarked makepkg on texlive-extras, my biggest package. I `explodepkg`, then `time makepkg`. On a ramdisk, so no disk I/O perturbations. .tbz uses lbzip2, available on -15.0 and -current, which is a threaded bzip2, hence removing the major old flaw of bzip2. lzma is for .tar.lzma packages, no short extension, looks like mono-threaded xz. # texlive-extra-2024.240409 | real | user | sys | size | tgz | 5m16 | 5m07 | 11s | 3.0G | tbz | 1m15 | 6m47 | 17s | 2.8G | txz | 4m29 | 36m30 | 20s | 2.3G | tlz | 4m14 | 47m31 | 23s | 2.4G | lzma | 29m16 | 28m29 | 24s | 2.3G | gzip being mono-thread, bzip2 is way faster on my box, but the box is quite strong with 8-cores, it'd still take way less time on a 2-core box. Even txz/tlz are faster than tgz because of the 8 cores used... Here, the better compromise still is bzip2. And for large-scale distribution, like official repositories, xz is the best, achieving better compression ratio, hence less network usage, and bzip2 makes too big packages. A switch to .tbz-by-default could be discussed, with strong arguments. I'd advocate against .txz and .tlz, and I'd be ok with sticking to .tgz. I've benchmarked enlightenment too, which is quite a big software package also, with mixed data. # enlightenment-0.27.1 | real | user | sys | size | tgz | 11s30 | 10s59 | 1s | 390M | tbz | 3s47 | 36s93 | 1s | 383G | txz | 1m50 | 3m32 | 3s | 385G | tlz | 37s | 3m32 | 3s | 385G | lzma | 3m44 | 3m37 | 3s | 384G | And lbzip2 is just the best, but I'm surprised, usually, compression ratio is between tgz and txz (eg GraphicsMagick : txz:2.5M / tbz:3.1M / tgz:3.6M, with tbz being the fastest). - Yth. From urchlay at slackware.uk Tue Oct 6 21:23:38 2026 From: urchlay at slackware.uk (B. Watson) Date: Tue, 6 Oct 2026 17:23:38 -0400 (EDT) Subject: [Slackbuilds-users] txz? In-Reply-To: <20261006160225.b3e255981a7e55c9499ccac7@ythogtha.org> References: <5ebb66f7-4a4f-f824-d456-ff5d2a915f4c@slackware.uk> <20261006160225.b3e255981a7e55c9499ccac7@ythogtha.org> Message-ID: On Tue, 6 Oct 2026, Yth O?Gtha wrote: > It really depends on the data. > I've been faced with having to fetch various data, logs and binary files, from a > distant virtual machine, without much power (only 2 cores, not a lot of memory), > repeatedly, for tests. > And bzip2 was my choice, de/compressing is almost as fast as with gzip, > while compression ratio was half-way to xz. Interesting. I wouldn't have even thought of trying bzip2. I discovered something about xz. Its man page says: -0 ... -3 These are somewhat fast presets. -0 is sometimes faster than gzip -9 while compressing much better. The higher ones often have speed comparable to bzip2(1) with compa? rable or better compression ratio, although the results depend a lot on the type of data being compressed ...and for the font 99MB font package I was playing with, that turned out to be true. I added --compress -0 to the makepkg line in the SlackBuild (also tried -3 and -6). Looking at /sbin/makepkg... the default compression level is -9, and it doesn't inherit from the environment. So if we wanted to make the compression level user-selectable in the environment for our SlackBuilds, we'd have to change the makepkg line in all 10,000 scripts... something like: /sbin/makepkg --compress ${COMPRESS_OPTION:-9} -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE I wonder if someone could talk Pat into making a one-line change to makepkg? Replace this: COMPRESS_OPTION="-9" ...with this: COMPRESS_OPTION="${COMPRESS_OPTION:-9}" If so, SBo users would be able to set the compression level without us editing 10,000 scripts (and GPG signing them, which is the real time-consuming part). From ricardsonwilliams at gmail.com Wed Oct 7 00:22:00 2026 From: ricardsonwilliams at gmail.com (Ricardson) Date: Tue, 6 Oct 2026 21:22:00 -0300 Subject: [Slackbuilds-users] txz? In-Reply-To: References: <5ebb66f7-4a4f-f824-d456-ff5d2a915f4c@slackware.uk> <20261006160225.b3e255981a7e55c9499ccac7@ythogtha.org> Message-ID: a/pkgtools-16.0-noarch-2.txz: Rebuilt. makepkg: allow setting COMPRESS_OPTION for xz as an environment variable. Thanks to B. Watson. On Tue, Oct 6, 2026 at 6:29?PM B. Watson wrote: > > > > On Tue, 6 Oct 2026, Yth O?Gtha wrote: > > > It really depends on the data. > > I've been faced with having to fetch various data, logs and binary files, from a > > distant virtual machine, without much power (only 2 cores, not a lot of memory), > > repeatedly, for tests. > > And bzip2 was my choice, de/compressing is almost as fast as with gzip, > > while compression ratio was half-way to xz. > > Interesting. I wouldn't have even thought of trying bzip2. > > I discovered something about xz. Its man page says: > > -0 ... -3 > These are somewhat fast presets. -0 is sometimes faster > than gzip -9 while compressing much better. The higher > ones often have speed comparable to bzip2(1) with compa? > rable or better compression ratio, although the results > depend a lot on the type of data being compressed > > ...and for the font 99MB font package I was playing with, that turned > out to be true. I added --compress -0 to the makepkg line in the > SlackBuild (also tried -3 and -6). > > Looking at /sbin/makepkg... the default compression level is -9, > and it doesn't inherit from the environment. So if we wanted to > make the compression level user-selectable in the environment for > our SlackBuilds, we'd have to change the makepkg line in all 10,000 > scripts... something like: > > /sbin/makepkg --compress ${COMPRESS_OPTION:-9} -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE > > I wonder if someone could talk Pat into making a one-line change to > makepkg? Replace this: > > COMPRESS_OPTION="-9" > > ...with this: > > COMPRESS_OPTION="${COMPRESS_OPTION:-9}" > > If so, SBo users would be able to set the compression level without > us editing 10,000 scripts (and GPG signing them, which is the real > time-consuming part)._______________________________________________ > 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 slack at giand.it Wed Oct 7 18:36:48 2026 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Wed, 7 Oct 2026 20:36:48 +0200 Subject: [Slackbuilds-users] build of Vigra fails against HDF5 Message-ID: <36fd82e3-a447-4c29-aae5-b76192bf80fd@giand.it> Hi, I'm trying to test Vigra as optional dependency of saga-gis but the build of current version available on SBo fails due the current version of HDF5. This issue can be solved with a greater version of Vigra ( https://github.com/ukoethe/vigra/issues/556 ). I tried with the lastest release (1.12.4) and it builds fine. The slackbuild script requires some adjustments because the source's tarball is named vigra-Version-1-12-4.tar.gz instead of vigra-1.12.4.tar.gz. At the moment I'll disable the support of vigra in the saga-gis update I will submit soon. -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From ricardsonwilliams at gmail.com Wed Oct 7 21:21:39 2026 From: ricardsonwilliams at gmail.com (Ricardson) Date: Wed, 7 Oct 2026 18:21:39 -0300 Subject: [Slackbuilds-users] Fwd: lowdown SlackBuild update In-Reply-To: References: Message-ID: Hi, I contacted the current maintainer of lowdown a week ago about updating the SlackBuild from 1.3.2 to 3.2.1, but haven't received a response. I'd be happy to take over maintenance and submit the update if that's OK. Regards, r1w1s1 ---------- Forwarded message --------- From: Ricardson Date: Wed, Sep 30, 2026 at 4:34?PM Subject: lowdown SlackBuild update To: Hi Pouria, I noticed that the lowdown SlackBuild is currently at version 1.3.2, while upstream has released version 3.2.1. Are you still maintaining this SlackBuild and planning to update it? If you're no longer maintaining it, I'd be happy to take it over and submit an updated version. -- Regards r1w1s1 From slack at giand.it Thu Oct 8 02:44:56 2026 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Thu, 8 Oct 2026 04:44:56 +0200 Subject: [Slackbuilds-users] build of Vigra fails against HDF5 In-Reply-To: <36fd82e3-a447-4c29-aae5-b76192bf80fd@giand.it> References: <36fd82e3-a447-4c29-aae5-b76192bf80fd@giand.it> Message-ID: <8557dbeb-ed66-4296-98d1-ce97c4d0305c@giand.it> Il 07/10/26 20:36, Giancarlo Dess? ha scritto: > Hi, I'm trying to test Vigra as optional dependency of saga-gis but > the build of current version available on SBo fails due the current > version of HDF5. > This issue can be solved with a greater version of Vigra ( > https://github.com/ukoethe/vigra/issues/556 ). I tried with the > lastest release (1.12.4) and it > builds fine. The slackbuild script requires some adjustments because > the source's tarball is named vigra-Version-1-12-4.tar.gz instead of > vigra-1.12.4.tar.gz. > > At the moment I'll disable the support of vigra in the saga-gis update > I will submit soon. > Unfortunately the build with support to Vigra fails even with the lastest release if HDF5 is also installed, so the build with Vigra tools will be disabled anyway. -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From willysr at slackbuilds.org Thu Oct 8 05:05:56 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 8 Oct 2026 12:05:56 +0700 Subject: [Slackbuilds-users] Fwd: lowdown SlackBuild update In-Reply-To: References: Message-ID: <20261008120556.469577c0@office64.slackie.org> >I contacted the current maintainer of lowdown a week ago about >updating the SlackBuild from 1.3.2 to 3.2.1, but haven't received a >response. sure, go ahead -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From urchlay at slackware.uk Thu Oct 8 06:08:45 2026 From: urchlay at slackware.uk (B. Watson) Date: Thu, 8 Oct 2026 02:08:45 -0400 (EDT) Subject: [Slackbuilds-users] Fwd: lowdown SlackBuild update In-Reply-To: References: Message-ID: <60d348bc-146e-c486-f856-5de9459ba42b@slackware.uk> On Wed, 7 Oct 2026, Ricardson wrote: > Hi, > > I contacted the current maintainer of lowdown a week ago about > updating the SlackBuild from 1.3.2 to 3.2.1, but haven't received a > response. > > I'd be happy to take over maintenance and submit the update if that's OK. Have you looked at the git log for office/lowdown? I see this: commit 89eb9b87cf52637dd0846488b66fc92929631781 Author: Pouria Rezaei Date: Tue Jan 28 14:10:23 2025 +0330 office/lowdown: Revert to 1.3.2. Last commit broken nix, so I'll downgrade this. ...and Pouria Rezaei is also the maintainer of nix. Sounds like there's a good reason for lowdown staying at an older version. I suggest waiting a little longer for Pouria to respond. Say, another week. If you still don't hear back, mention it again on the mailing list. From urchlay at slackware.uk Thu Oct 8 06:09:54 2026 From: urchlay at slackware.uk (B. Watson) Date: Thu, 8 Oct 2026 02:09:54 -0400 (EDT) Subject: [Slackbuilds-users] Fwd: lowdown SlackBuild update In-Reply-To: <20261008120556.469577c0@office64.slackie.org> References: <20261008120556.469577c0@office64.slackie.org> Message-ID: <182de4a9-5cda-92f-22c6-44908aca88e0@slackware.uk> On Thu, 8 Oct 2026, Willy Sudiarto Raharjo wrote: >> I contacted the current maintainer of lowdown a week ago about >> updating the SlackBuild from 1.3.2 to 3.2.1, but haven't received a >> response. > > sure, go ahead OK, this will almost certainly break nix. Should it be orphaned, then? From yth at ythogtha.org Thu Oct 8 16:22:22 2026 From: yth at ythogtha.org (Yth =?UTF-8?B?T+KAmUd0aGE=?=) Date: Thu, 8 Oct 2026 18:22:22 +0200 Subject: [Slackbuilds-users] txz? In-Reply-To: References: <5ebb66f7-4a4f-f824-d456-ff5d2a915f4c@slackware.uk> <20261006160225.b3e255981a7e55c9499ccac7@ythogtha.org> Message-ID: <20261008182222.23269bca75628d8e2f6ef873@ythogtha.org> > a/pkgtools-16.0-noarch-2.txz: Rebuilt. > makepkg: allow setting COMPRESS_OPTION for xz as an environment variable. > Thanks to B. Watson. > That was pretty efficient ! For comparison, I tried re-makepkg-ing using xz -0, and here are the results: # texlive-extra-2024.240409 | real | user | sys | size | tgz | 5m16 | 5m07 | 11s | 3.0G | tbz | 1m15 | 6m47 | 17s | 2.8G | txz | 4m29 | 36m30 | 20s | 2.3G | 0txz | 1m27 | 10m03 | 13s | 2.8G | # enlightenment-0.27.1 | real | user | sys | size | tgz | 11s30 | 10s59 | 1s | 390M | tbz | 3s47 | 36s93 | 1s | 383G | txz | 1m50 | 3m32 | 3s | 385G | 0txz | 6s02 | 1m20 | 1s | 390G | It feels there should broader testing to have a better picture. Here although lbzip2 is still looking like the best compromise. And I know a lot of peaople (myself from some years ago being one of them) ? wouldn't have even thought of trying bzip2. ? but it is clearly neither a bad nor an outdated tool. Cheers ;) - Yth. From urchlay at slackware.uk Thu Oct 8 21:15:19 2026 From: urchlay at slackware.uk (B. Watson) Date: Thu, 8 Oct 2026 17:15:19 -0400 (EDT) Subject: [Slackbuilds-users] txz? In-Reply-To: <20261008182222.23269bca75628d8e2f6ef873@ythogtha.org> References: <5ebb66f7-4a4f-f824-d456-ff5d2a915f4c@slackware.uk> <20261006160225.b3e255981a7e55c9499ccac7@ythogtha.org> <20261008182222.23269bca75628d8e2f6ef873@ythogtha.org> Message-ID: On Thu, 8 Oct 2026, Yth O?Gtha wrote: >> a/pkgtools-16.0-noarch-2.txz: Rebuilt. >> makepkg: allow setting COMPRESS_OPTION for xz as an environment variable. >> Thanks to B. Watson. >> > > That was pretty efficient ! I wish I knew how I did that :) > It feels there should broader testing to have a better picture. Yeah. I've got to write myself a little test script that generates reports like yours, and I'll let run on a few hundred packages while I'm at work. Probably should pick packages for different criteria. Like, ones with *lots* of small files (icon themes), ones with large but compressible files, ones with large already-compressed files (game data might have lots of .mp3 or .ogg files, .jpeg images, compressed video...) So our numbers will describe the same thing... you're *just* testing compression speed, not the entire process of running the SlackBuild, right? I was thinking, my script would build a package as a .tgz, then un-gzip it to a .tar file, then time how long it takes to compress that file with the various compressors. That's basically what you're doing, right? > Here although lbzip2 is still looking like the best compromise. Yeah. > And I know a lot of peaople (myself from some years ago being one of them) > ? wouldn't have even thought of trying bzip2. ? but it is clearly neither a bad > nor an outdated tool. You ever look at pbzip2? Parallel implementation, might be faster... though makepkg can't use it unless it becomes part of core Slackware. There's also a bzip3, apparently (I just found it on SBo, know nothing about it). From yth at ythogtha.org Thu Oct 8 22:04:00 2026 From: yth at ythogtha.org (Yth) Date: Thu, 08 Oct 2026 22:04:00 +0000 Subject: [Slackbuilds-users] txz? In-Reply-To: References: <5ebb66f7-4a4f-f824-d456-ff5d2a915f4c@slackware.uk> <20261006160225.b3e255981a7e55c9499ccac7@ythogtha.org> <20261008182222.23269bca75628d8e2f6ef873@ythogtha.org> Message-ID: >>> a/pkgtools-16.0-noarch-2.txz: Rebuilt. >>> makepkg: allow setting COMPRESS_OPTION for xz as an environment variable. >>> Thanks to B. Watson. >>> >> That was pretty efficient ! >I wish I knew how I did that :) Don't sell yourself short ?? >So our numbers will describe the same thing... you're *just* testing >compression speed, not the entire process of running the SlackBuild, >right? >I was thinking, my script would build a package as a .tgz, then >un-gzip it to a .tar file, then time how long it takes to compress >that file with the various compressors. That's basically what you're >doing, right? I'm sticking with pkgtools, so I have a prebuilt package from my own collection, I explodepkg in a ramdisk, then makepkg with usual options from SlackBuilds, only changing the extension of the package. So I'm testing as much as possible what people would experience when slackbuilding, for the package creation itself only. >You ever look at pbzip2? >Parallel implementation, might be faster... >though makepkg can't use it unless it becomes part of core Slackware. I did find out Slackware ships lbzip2, and pkgtools uses it if available, which is also a parallel bzip2, which renders it extremely fast on my 8-cores computer. I don't know the differences with pbzip2, or even bzip3, whose existence I'm discovering right now! -- - Yth. From ricardsonwilliams at gmail.com Fri Oct 9 14:48:04 2026 From: ricardsonwilliams at gmail.com (Ricardson) Date: Fri, 9 Oct 2026 11:48:04 -0300 Subject: [Slackbuilds-users] Fwd: lowdown SlackBuild update In-Reply-To: <182de4a9-5cda-92f-22c6-44908aca88e0@slackware.uk> References: <20261008120556.469577c0@office64.slackie.org> <182de4a9-5cda-92f-22c6-44908aca88e0@slackware.uk> Message-ID: I think it's better we orphan Nix and update Lowdown, okay? See the attached email from the maintainer I received today. On Thu, Oct 8, 2026 at 3:10?AM B. Watson wrote: > > > > On Thu, 8 Oct 2026, Willy Sudiarto Raharjo wrote: > > >> I contacted the current maintainer of lowdown a week ago about > >> updating the SlackBuild from 1.3.2 to 3.2.1, but haven't received a > >> response. > > > > sure, go ahead > > OK, this will almost certainly break nix. Should it be orphaned, then? -------------- next part -------------- An embedded message was scrubbed... From: Pouria Rezaei Subject: Re: lowdown SlackBuild update Date: Fri, 9 Oct 2026 13:58:06 +0000 Size: 12844 URL: From yth at ythogtha.org Fri Oct 9 20:51:51 2026 From: yth at ythogtha.org (Yth =?UTF-8?B?T+KAmUd0aGE=?=) Date: Fri, 9 Oct 2026 22:51:51 +0200 Subject: [Slackbuilds-users] txz? In-Reply-To: <20261008182222.23269bca75628d8e2f6ef873@ythogtha.org> References: <5ebb66f7-4a4f-f824-d456-ff5d2a915f4c@slackware.uk> <20261006160225.b3e255981a7e55c9499ccac7@ythogtha.org> <20261008182222.23269bca75628d8e2f6ef873@ythogtha.org> Message-ID: <20261009225151.69fb48489448efd82ffa44b8@ythogtha.org> So, for the sake of gathering more data, I repackaged all my current slackbuilds, added times, and got global size. This is for 293 packages, and "txz0" stands for `xz -0` `memory` column is a bit devious: it is the sum of resident memory usage for all runs. Correlated with the maximum usage `maxmem` it can give a global feeling about whether a compressor requires a lot of memory, or not. `mean` is just `memory/293` so an average per build, for what its worth. And I added a line for tar.bz3, doing `tar | bzip3 -j 8`, for 8 cores It isn't handled by pkgtools, hence it is only for getting some insight into this new compressor, which proves quite interesting. Documentation doesn't show a way to ? just use as many threads as available cores ?, and there is a block parameter which adds more memory, more time, and reduces size, and alas more decompression memory required, so it may not be interesting to try to maximize that. Results are shown on the second tbz3 line, using maximum of `-b 511`, and I'm not convinced, contrary to eg `xv -9`. | | real | user | sys | size | memory | maxmem | mean | | tgz | 1316s | 1265s | 72s | 8620M | 6G | 37M | 22M | | tbz | 239s | 1202s | 89s | 8007M | 12G | 148M | 43M | | txz | 2843s | 6456s | 139s | 6580M | 104G | 12G | 364M | | txz0 | 278s | 1654s | 83s | 7886M | 10G | 91M | 34M | | tbz3 | 310s | 1510s | 30s | 7135M | 29G | 881M | 103M | | tbz3 | 904s | 1307s | 53s | 7008M | 79G | 19G | 273M | I am overall pretty impressed with lbzip2, though `xz -0` looks slightly better, a tad bit less memory, a tad bit more cpu and time, and a tad bit less space. And there is no question that standard xz is best for large-scale distribution. -- Arnaud From sb at rbn.im Fri Oct 9 21:33:49 2026 From: sb at rbn.im (Ruben Schuller) Date: Fri, 9 Oct 2026 23:33:49 +0200 Subject: [Slackbuilds-users] bwidget Message-ID: <20261009233349.225f7583@banane.kuchen> Hi, (CC-ing the list because gmail probably does throw away my mail..) are you still interested in maintaining the bwidget SlackBuild? The version listed on SBo is 1.9.8 from 2015, the latest is 1.10.1 from 2024 [1]. The new version also builds with the new Tcl 9.x release, which I hope will be included in the next Slackware release. Kind Regards Ruben [1] https://sourceforge.net/projects/tcllib/files/BWidget/ From willysr at slackbuilds.org Sat Oct 10 03:35:11 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 10 Oct 2026 10:35:11 +0700 Subject: [Slackbuilds-users] Updates - 20261010.1 Message-ID: <20261010103511.6774a7f3@home.slackie.org> Sat Oct 10 03:18:58 UTC 2026 academic/ViennaRNA: Updated script academic/gri: Updated script academic/ktikz: Fixed compilation error in stable and current. academic/locarna: Updated script academic/ngspice-jit: Updated for version 46.10. academic/parmetis: Removed (Unmaintained and 404). academic/pspp: Updated for version 2.1.2. academic/python3-scipy: Allow it to work with newer pythran academic/stellarium: Updated for version v26.3 academic/xcircuit: orphaned - no maintainer. audio/acousticbrainz-music-extractor: Fix homepage. audio/alsacap: Align to template. audio/aseqview: Updated for version 0.3.1. audio/drumkv1: Updated for version 1.5.0. audio/hydrogen: Updated for version 1.2.7. audio/jack-rack: Fix build on -current. audio/jalv: Fix build. audio/kew: Added (Music Player). audio/mac: Updated for version 13.27. audio/ncspot: Updated for version 1.5.0. audio/padthv1: Updated for version 1.5.0. audio/reaper: Updated for version 7.82 audio/samplv1: Updated for version 1.5.0. audio/setBfree: Updated for version 0.8.17. audio/synthv1: Updated for version 1.5.0. audio/transcribe: Fix download. audio/tta: orphaned - no maintainer. audio/xmms-jack: Align to template. desktop/ClamAV-GUI: Updated for version 1.4.8 desktop/faba-icon-theme: Orphaned (abandoned 2023/12 on ML). desktop/marco: Updated for version 1.28.2. desktop/mate-control-center: Updated for version 1.28.2. desktop/mate-screensaver: Updated for version 1.28.1. desktop/moka-icon-theme: Orphaned (abandoned 2023/12 on ML). desktop/naps2: Updated for version 8.4.1 desktop/nwg-look: Updated for version 1.1.2. desktop/razercfg: Version bump to 0.44 desktop/trayer-srg: Fix build on -current. desktop/wayfire: New maintainer. desktop/wcm: New maintainer. desktop/wdisplays: Updated for version 1.3.0. desktop/wf-config: New maintainer. desktop/wf-shell: New maintainer. development/Catch2: Updated for version 3.16.1 development/HeidiSQL: Updated for version 12.21. development/Kiro: Updated for version 1.2.56. development/OpenCL-CLHPP: orphaned - no maintainer. development/age: Added (File encryption tool). development/antigravity-cli: Updated for version 1.3.0 development/antigravity: Updated for version 2.19.1 development/astyle: Updated for version 3.6.19. development/aws-cdk: Updated for version 2.1144.0. development/bbcsdl: Updated for version 20261005_2ef1c00 development/bun-bin:updated to version 1.4.2 development/cargo-auditable: Updated for version 0.7.7. development/cargo-vendor-filterer: Align with template fixes. development/chatgpt: Updated for version 26.930.31730. development/clion: Updated for version 2026.2.3.1. development/cppcheck: Updated for version 2.22.0 development/deno-bin:updated to version 2.9.7 development/dkms: Updated for version 3.4.4 development/electron-bin: Updated for version 44.5.1 development/elixir: updated for version 1.18.5. development/erlang-otp: Updated for version 27.3.4.18 development/github-cli: Updated for version 2.102.0 development/gitui: Added (Terminal UI for GIT). development/heroku-cli: Updated for version 11.11.0. development/ieee-pilot: Fix build on -current. development/jupyter_server: Fix for python3-tornado v6.5.9+ development/jupyterlab_server: Patched for python3-tornado v6.5.9+ development/kotlin: Updated for version 2.4.21. development/mads: Updated for version 2.1.9. development/meld3: Updated for version 3.24.1. development/mongodb-compass: Updated for version 1.52.0. development/mongodb-shell: Updated for version 2.13.0. development/nodejs24-bin:updated to version 24.21.0 development/prek: Updated for version 0.5.5. development/pycharm: Updated for version 2026.2.3 development/reuse-tool: Update readme development/rider: Updated for version 2026.2.3.1. development/robotframework: Updated for version 7.5. development/smartgit: Updated for version 26.1.057 development/sops: Added (Encrypted file editor). development/srcML: Updated for version 1.1.0. development/unmake: Updated for version 0.0.27, new maintainer. development/vscode-bin: Updated for version 1.141.0. development/whisper.cpp: Updated for version 1.7.1. development/zed-editor-bin: Updated for version 1.21.0. development/zulu-openjdk8: Fix for ARCH=i586 in env. games/Lac: Added (Linux air combat). games/VASSAL: Updated for version 3.7.29 games/alephone: Updated for version 20260930. games/domination: Updated for version 1.3.5. games/immortal-barons: Updated for version 0.2.3 games/iortcw: New maintainer. games/lmarbles: Updated for version 1.2. games/marathon-data: Updated for version 20260930. games/marathon-infinity-data: Updated for version 20260930. games/marathon2-data: Updated for version 20260930. games/micropolis: Fix build on -current. games/odamex: Fix build if UID 1001 doesn't exist. games/opensurge: Updated for version 0.6.1.3. games/protontricks: Version bump to 1.15.0 games/shattered-pixel-dungeon: Updated for version 4.0.2. games/torcs: Updated for version 1.3.10. games/zaz: Updated for version 1.0.1. games/zsnes: Fix build when ARCH is exported. gis/SFCGAL: Updated for version 2.3.0. gis/google-earth: Updated for version 7.3.7.1327. gis/ossim: Updated script. gis/pdal: Updated for version 2.10.2. gis/postgis: Updated for version 3.6.4. gis/saga-gis: Updated for version 9.13.1. graphics/GraphicsMagick: Align with template (fixes aarch64). graphics/chafa:remove /sbin/ldconfig line from slackbuild graphics/chafa:updated to version 1.18.3 graphics/converseen: Updated for version 0.15.2.9. graphics/makehuman: Updated for version 1.3.0. graphics/mcomix: Updated for version 3.2.0. graphics/renderdoc: Updated for version 1.20 graphics/white_dune: Updated for version 1.930 graphics/zbar: Updated for version 0.23.93 + new maintainer ham/codec2: Updated scripts. libraries/SDL3: Updated for version 3.4.18 libraries/dietlibc: Fix build on -current. libraries/flint: New maintainer. libraries/ilo: Added (Helper Libraries). libraries/libb64: New maintainer. libraries/libe-book: Updated for version 0.1.4 libraries/libfabric:updated to version 2.7.0 libraries/libindi-drivers: Fix extension type. libraries/libmediainfo: Version bump to 26.10 libraries/libmpuio: Updated for version 1.0.4. libraries/libslirp:updated to version 4.9.5 libraries/libuninameslist:updated to version 20260918 libraries/mmtisobmff: Added (ISOBMFF library). libraries/mpeghdec: Added (MPEG-H Decoder). libraries/openapv: Updated for version 1.1.2.0 libraries/simdjson: Updated for version 5.0.1 libraries/simdutf: Updated for version 9.2.1 libraries/tinygltf: Updated for version 3.0.1. libraries/vali: Updated for version 20260317_cfc9abf4 libraries/vcglib: new maintainer libraries/vmaf: Updated for version 3.2.1 misc/OSCAR: Updated for version 2.1.0 misc/bdfresize: Fix homepage. misc/ollama: Updated for version 0.40.2. misc/xdelta3: Updated for version 3.2.2. multimedia/aegisub: Update README. multimedia/devedeng: Updated for version 4.22.0 multimedia/mediainfo: Version bump to 26.10 multimedia/picard: Note on why we can't update + minor cleanup multimedia/pocketsphinx: Updated for version 5.1.1 multimedia/strawberry: Updated for version 1.2.31. multimedia/svt-jpeg-xs: Added (ISO/IEC 21122 Library). network/ani-cli:updated to version 5.1 network/anydesk: Updated for version 8.1.0. network/brave-browser: Updated for version 1.97.56 network/brave-origin: Updated for version 1.97.56 network/caddy: Updated for version 2.11.7. network/cisco-secure-client-vpn: Updated for version 5.1.20.333. network/clipgrab: New maintainer network/cloudflared-bin: Updated for version 2026.10.0. network/feather: Orphaned (unmaintained). network/ferdium: Updated for version 7.2.3. network/floorp-bin: Updated for version 12.20.1. network/gallery-dl: Updated for version 1.32.15 network/grafana: Updated for version 13.2.3. network/halloy: Updated for version 2026.9 network/helium-browser: Updated for version 0.18.3.1 network/ipcalc-ng: Updated for version 1.1.0. network/libressl: update to 4.3.3 network/librewolf: Updated for version 157.0.1_1 network/microsoft-edge: Updated for version 154.0.4258.53. network/nessus: Updated for version 10.12.5. network/netavark: Updated for version 2.1.0 network/nyxt: Removed (FTBFS and unmaintained). network/rclone-src: Updated for version 1.75.2 network/rdma-core: Updated for version 65.0 network/rspamd: Updated for version 4.2.1 network/rtorrent: Updated for version 0.16.25. network/rustdesk: Updated for version 1.5.0. network/static-web-server: Updated for version 2.44.1 network/tailscale: Updated for version 1.104.1 network/telegram: Updated for versin 7.3.0. network/twinkle: Updated for version 1.11.0. network/ungoogled-chromium-bin: Added (Chromium without Google). network/vivaldi: Updated for version 8.2.4133.84. network/zen-browser: Updated for version 1.23b office/FreeOffice: Updated for version 2024_1238 office/LibreOffice: Updated for version 26.8.1.1 office/ccal: New maintainer. office/csvlens: Added (Terminal CVS viewer). office/cups-pdf: New maintainer office/ledger-live: Updated for version 4.23.0 office/mu: Updated for version 1.12.15 + new maintainer office/pandoc-bin: Updated for version 3.12.1 office/paps: Updated for version 0.8.1. office/pdfsam-basic: update to v. 6.0.6 office/qownnotes: Updated for version 26.10.3. office/smoffice2024: Updated for version 2024_1238 office/wps-office: Updated for version 11.1.0.11733.XA office/xpad: Updated for version 5.5.0 perl/MoarVM: Updated for version 2026.09 perl/nqp: Updated for version 2026.09 perl/perl-CPAN-Perl-Releases: Updated for version 5.20260924. perl/perl-Clone: Updated for version 0.51. perl/perl-Exception-Class: Updated for version 1.46. perl/perl-Package-Stash-XS: Updated for version 0.32. perl/perl-Test-Differences: Updated for version 0.73. perl/perl-Test-Trap: Updated for version 0.3.5. perl/perl-gtk2: Fix build on -current. perl/rakudo: Updated for version 2026.09 perl/zef: Updated for version 1.1.4 python/python-debian: Updated to version 1.1.1 python/python3-argcomplete: Updated README python/python3-fonttools: Updated README python/python3-fqdn: Update for 1.6.0 python/python3-gast: Version bump to 0.7.0 python/python3-glyphslib: Updated README python/python3-gmpy2: Updated for version 2.3.2 python/python3-gnupg: Update for 0.5.7 python/python3-pycryptodomex: Updated for version 3.24.0. python/python3-pypdf: Updated for version 6.20.0 python/python3-pythran: Version bump to 0.19.0 python/python3-pyudev: Update README python/python3-reportlab: Updated for version 5.0.1 python/python3-rope: Updated README python/python3-soupsieve: Updated script. python/python3-ufo2ft: update readme python/tzdata: Updated for version 2026.5. python/uv-bin: Updated for version 0.12.22. python/uv-bin: Updated for version 0.12.24. python/uv-bin: Updated for version 0.13.0. ruby/rubygem-rubyzip: Added (Ruby Library). system/7zip: Updated for version 26.04 system/Iosevka-aile: Updated for version 34.9.0. system/Iosevka-etoile: Updated for version 34.9.0. system/android-udev-rules: Deleted 51-android.rules system/ansifilter: Updated for version 2.24. system/apache-activemq: New maintainer. system/aterm: Align with new template. system/ck4up: Updated for version 1.5. system/cpufetch: Added (CPU information). system/csh: Fix build on -current. system/dump: Updated for version 0.4b56. system/freeipmi: Updated for version 1.6.20. system/fzf-bin:updated to version 0.74.4 system/gdu: Updated for version 5.38.0 system/geoclue2: New maintainer. system/gpufetch: Added (GPU detection). system/hyperfine: Updated for version 1.21.0. system/kapacitor: Updated for version 1.8.7 system/lazydocker: Added (Manage Docker). system/limine: Updated for version 12.9.3 system/mongo-tools: Updated for version 100.19.1. system/mrxvt: Fix build on -current. system/nerdctl: Updated for version 2.4.1 system/netdata: Updated for version 2.12.1. system/onefetch: Updated for version 3.0.0. system/otf-nerd-fonts-hermit: Added (Nerdfonts hermit). system/pause: New maintainer. system/peektea: Updated README. system/postgresql18: Fix authentication method in setup script. system/rabbitmq-server: Updated for version 4.3.6 system/runit: New maintainer. system/rxvt: Fix build on -current. system/sarasa-gothic: Updated for version 1.0.42. system/slkstore: Mark as x86_64 only. system/socklog: Orphaned (abandoned 2023/12 on ML). system/superfile: Updated README. system/telegraf: Updated for version 1.40.1 system/terminalia-fonts: Clean up script. system/ttf-nerd-fonts-firacode: Added (Nerdfonts firacode). system/ttf-nerd-fonts-martian-mono: Added (Nerdfonts martian mono). system/ttf-nerd-fonts-mononoki: Added (Nerdfonts mononoki). system/ttf-nerd-fonts-saucecodepro: Added (OpenType Fonts). system/ttf-nerd-fonts-ubuntu-mono: Added (Nerdfonts ubuntu mono). system/ucs-miscfixed-opentype-fonts: Clean up script. system/ventoy: Updated for version 1.1.18 system/xosd-xft: Added (On Screen Display for X11). system/yazi: Added (File Manager). system/yeahconsole: Align to template. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From promano7 at hotmail.com Sun Oct 11 20:35:49 2026 From: promano7 at hotmail.com (Pablo Romano) Date: Sun, 11 Oct 2026 22:35:49 +0200 Subject: [Slackbuilds-users] Fwd: gnome-terminal SlackBuild In-Reply-To: References: Message-ID: Hello, I contacted the maintainer of gnome-terminal on September 27 to ask for permission to take over maintenance of the package, but I have not received a reply after two weeks. I would therefore like to ask SBo for permission to take over the package from the current maintainer. The current version of gnome-terminal cannot be updated further due to the limitations of Slackware 15.0. However, the SlackBuild itself can be improved considerably. At present, it declares gnome-shell and nautilus as dependencies, which makes building the package take a very long time. Neither of them is actually required for the core gnome-terminal application; they are only needed for the optional GNOME Shell search provider and Nautilus extension. I have prepared and tested an alternative SlackBuild that disables those two optional integrations by default, removing gnome-shell and nautilus as mandatory dependencies and greatly reducing the overall build time. The SlackBuild still allows either integration to be enabled optionally at build time for users who have gnome-shell and/or nautilus installed. The resulting package builds and works correctly on Slackware 15.0 without either dependency installed, and it passes both sbolint and sbopkglint. I am forwarding below the message I originally sent to the current gnome-terminal maintainer. Thank you. -------- Mensaje reenviado -------- Asunto: gnome-terminal SlackBuild Fecha: Sun, 27 Sep 2026 18:07:31 +0200 De: Pablo Romano Para: bobfunk11 at gmail.com Hi Bob, I'm writing about the gnome-terminal SlackBuild in SlackBuilds.org. I've been testing the current 3.43.90 build on an up-to-date Slackware 15.0 system. I found that the gnome-shell and nautilus dependencies are only needed for the optional GNOME Shell search provider and Nautilus extension. I have prepared and tested a small revision that disables those two optional integrations by default, removes gnome-shell and nautilus from REQUIRES, and still allows users to enable them at build time with NAUTILUS=yes and/or SEARCH_PROVIDER=yes. The resulting package builds and installs successfully without either gnome-shell or nautilus installed, passes both sbolint and sbopkglint, and works correctly with Slackware 15.0's stock VTE 0.66.2. I would also like to maintain gnome-terminal going forward. In addition to keeping the Slackware 15.0 SlackBuild maintained, I plan to prepare a SlackBuild for the current stable gnome-terminal 3.60 release for Slackware-current and contribute the necessary version to Ponce's slackbuilds repository. I need to be the maintainer on SBo to submit a pull request to Ponce's repository. Would you be OK with me taking over maintainership of gnome-terminal on SlackBuilds.org? Of course, I would retain your existing copyright notice in the SlackBuild. Thanks for your work maintaining the package and the other GNOME components in SBo. Best regards, Pablo -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Sun Oct 11 21:04:15 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 11 Oct 2026 17:04:15 -0400 (EDT) Subject: [Slackbuilds-users] Fwd: gnome-terminal SlackBuild In-Reply-To: References: Message-ID: On Sun, 11 Oct 2026, Pablo Romano wrote: > > Hello, > > I contacted the maintainer of gnome-terminal on September 27 to ask for permission to take over maintenance of the package, but I have not received a > reply after two weeks. I would therefore like to ask SBo for permission to take over the package from the current maintainer. The current maintainer is Bob Funk. He's an active maintainer, last activity September 16, 2026, and he's responded to several emails from me over the last 2 or 3 months. He maintains most of the GNOME builds on SBo, and I don't feel good about giving one of his builds to another maintainer without talking to him myself, or seeing a reply from him on this mailing list. > The current version of gnome-terminal cannot be updated further due to the limitations of Slackware 15.0. However, the SlackBuild itself can be > improved considerably. > > At present, it declares gnome-shell and nautilus as dependencies, which makes building the package take a very long time. Neither of them is actually > required for the core gnome-terminal application; they are only needed for the optional GNOME Shell search provider and Nautilus extension. That seems like a good idea to me. Bob, you listening? From bobfunk11 at gmail.com Mon Oct 12 12:16:18 2026 From: bobfunk11 at gmail.com (Bob Funk) Date: Mon, 12 Oct 2026 07:16:18 -0500 Subject: [Slackbuilds-users] Fwd: gnome-terminal SlackBuild In-Reply-To: References: Message-ID: Hey, thanks for dropping me a line here. It looks like the "Sept 27 email" went to my spam and unnoticed by me until prompted by this email. I can get the gnome-terminal slackbuild script tweaked to build without nautilus and get the changes in for next weeks update. It's been on my todo list with changes when I update it, but I might as well do it now. Regarding your request to take over: I'd still prefer to maintain it and use it as my primary terminal emulator. You mentioned wanting to take it over so you can submit an updated slackbuild to ponce's slackware current repo. I was unaware this is something we can do, but I can certainly do that as well, if ponce is okay with me making pull requests to his repo. Regards, Bob On Sun, Oct 11, 2026 at 4:04?PM B. Watson wrote: > > > On Sun, 11 Oct 2026, Pablo Romano wrote: > > > > > Hello, > > > > I contacted the maintainer of gnome-terminal on September 27 to ask for > permission to take over maintenance of the package, but I have not received > a > > reply after two weeks. I would therefore like to ask SBo for permission > to take over the package from the current maintainer. > > The current maintainer is Bob Funk. He's an active maintainer, last > activity September 16, 2026, and he's responded to several emails > from me over the last 2 or 3 months. He maintains most of the GNOME > builds on SBo, and I don't feel good about giving one of his builds to > another maintainer without talking to him myself, or seeing a reply > from him on this mailing list. > > > The current version of gnome-terminal cannot be updated further due to > the limitations of Slackware 15.0. However, the SlackBuild itself can be > > improved considerably. > > > > At present, it declares gnome-shell and nautilus as dependencies, which > makes building the package take a very long time. Neither of them is > actually > > required for the core gnome-terminal application; they are only needed > for the optional GNOME Shell search provider and Nautilus extension. > > That seems like a good idea to me. Bob, you listening? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Mon Oct 12 13:36:45 2026 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 12 Oct 2026 15:36:45 +0200 Subject: [Slackbuilds-users] Fwd: gnome-terminal SlackBuild In-Reply-To: References: Message-ID: the unofficial repository for current is there mainly to host fixes to let SBo stuff build on current so parallel maintaining scripts that are on SBo with newer versions for current with frequent updates is outside its scope (I already have 774 branches to rebase every week)... that said if some maintainer has an occasional update that better fits current for ${good_reasons} I'll gladly accept it! BTW thanks for letting me clarify this! Matteo Il giorno lun 12 ott 2026 alle ore 14:17 Bob Funk ha scritto: > Hey, > > thanks for dropping me a line here. It looks like the "Sept 27 email" went > to my spam and unnoticed by me until prompted by this email. > > I can get the gnome-terminal slackbuild script tweaked to build without > nautilus and get the changes in for next weeks update. It's been on my todo > list with changes when I update it, but I might as well do it now. > > Regarding your request to take over: I'd still prefer to maintain it and > use it as my primary terminal emulator. You mentioned wanting to take it > over so you can submit an updated slackbuild to ponce's slackware current > repo. I was unaware this is something we can do, but I can certainly do > that as well, if ponce is okay with me making pull requests to his repo. > > Regards, > > Bob > > > > > > On Sun, Oct 11, 2026 at 4:04?PM B. Watson wrote: > >> >> >> On Sun, 11 Oct 2026, Pablo Romano wrote: >> >> > >> > Hello, >> > >> > I contacted the maintainer of gnome-terminal on September 27 to ask for >> permission to take over maintenance of the package, but I have not received >> a >> > reply after two weeks. I would therefore like to ask SBo for permission >> to take over the package from the current maintainer. >> >> The current maintainer is Bob Funk. He's an active maintainer, last >> activity September 16, 2026, and he's responded to several emails >> from me over the last 2 or 3 months. He maintains most of the GNOME >> builds on SBo, and I don't feel good about giving one of his builds to >> another maintainer without talking to him myself, or seeing a reply >> from him on this mailing list. >> >> > The current version of gnome-terminal cannot be updated further due to >> the limitations of Slackware 15.0. However, the SlackBuild itself can be >> > improved considerably. >> > >> > At present, it declares gnome-shell and nautilus as dependencies, which >> makes building the package take a very long time. Neither of them is >> actually >> > required for the core gnome-terminal application; they are only needed >> for the optional GNOME Shell search provider and Nautilus extension. >> >> That seems like a good idea to me. Bob, you listening? >> > _______________________________________________ > 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 promano7 at hotmail.com Mon Oct 12 17:01:29 2026 From: promano7 at hotmail.com (Pablo Romano) Date: Mon, 12 Oct 2026 19:01:29 +0200 Subject: [Slackbuilds-users] Fwd: gnome-terminal SlackBuild In-Reply-To: References: Message-ID: Hi Bob, I'm sending you by email the SlackBuild I have prepared. This version: 1. Does not require gnome-shell or nautilus to be installed, while still keeping both as optional dependencies. 2. Conforms to the new SBo templates published on October 6. 3. Also builds successfully on Slackware-current, whereas the current SlackBuild does not. Thanks. El 12/10/26 a las 14:16, Bob Funk escribi?: > Hey, > > thanks for dropping me a line here. It looks like the "Sept 27 email" > went to my spam and unnoticed by me until prompted by this email. > > I can get the gnome-terminal slackbuild script tweaked to build > without nautilus and get the changes in for next weeks update. It's > been on my todo list with changes when I update it, but I might as > well do it now. > > Regarding your request to take over: I'd still prefer to maintain it > and use it as my primary terminal emulator. You mentioned wanting to > take it over so you can submit an updated slackbuild to ponce's > slackware current repo. I was unaware this is something we can do, but > I can certainly do that as well, if ponce is okay with me making pull > requests to his repo. > > Regards, > > Bob > > > > > > On Sun, Oct 11, 2026 at 4:04?PM B. Watson wrote: > > > > On Sun, 11 Oct 2026, Pablo Romano wrote: > > > > > Hello, > > > > I contacted the maintainer of gnome-terminal on September 27 to > ask for permission to take over maintenance of the package, but I > have not received a > > reply after two weeks. I would therefore like to ask SBo for > permission to take over the package from the current maintainer. > > The current maintainer is Bob Funk. He's an active maintainer, last > activity September 16, 2026, and he's responded to several emails > from me over the last 2 or 3 months. He maintains most of the GNOME > builds on SBo, and I don't feel good about giving one of his builds to > another maintainer without talking to him myself, or seeing a reply > from him on this mailing list. > > > The current version of gnome-terminal cannot be updated further > due to the limitations of Slackware 15.0. However, the SlackBuild > itself can be > > improved considerably. > > > > At present, it declares gnome-shell and nautilus as > dependencies, which makes building the package take a very long > time. Neither of them is actually > > required for the core gnome-terminal application; they are only > needed for the optional GNOME Shell search provider and Nautilus > extension. > > That seems like a good idea to me. Bob, you listening? > > > _______________________________________________ > 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 promano7 at hotmail.com Mon Oct 12 17:17:26 2026 From: promano7 at hotmail.com (Pablo Romano) Date: Mon, 12 Oct 2026 19:17:26 +0200 Subject: [Slackbuilds-users] Fwd: gnome-terminal SlackBuild In-Reply-To: References: Message-ID: Hi Matteo, First of all, thank you for the time and effort you put into maintaining the repository for Slackware-current. I understand your policy regarding the repository, but I have a question about the gnome-terminal package. The version currently available in SBo is 3.43.90, which is kept there because of the dependency limitations of Slackware 15.0. However, the current upstream stable release is 3.60.0, and Slackware-current already provides a sufficiently recent dependency stack to build it. So, in this particular case, the old version in SBo is not really a limitation of Slackware-current itself, but rather a consequence of SBo having to remain compatible with Slackware 15.0. Would you consider accepting a current-specific version bump to gnome-terminal 3.60.0 as an exception to the usual policy? Thanks again. El 12/10/26 a las 15:36, Matteo Bernardini escribi?: > the unofficial repository for current is there mainly to host fixes to > let SBo stuff build on current so parallel maintaining scripts that > are on SBo with newer versions for current with frequent updates is > outside its scope (I already have 774 branches to rebase every week)... > > that said if some maintainer has an occasional update that better fits > current for ${good_reasons} I'll gladly accept it! > > BTW thanks for letting me clarify this! > > Matteo > > Il giorno lun 12 ott 2026 alle ore 14:17 Bob Funk > ha scritto: > > Hey, > > thanks for dropping me a line here. It looks like the "Sept 27 > email" went to my spam and unnoticed by me until prompted by this > email. > > I can get the gnome-terminal slackbuild script tweaked to build > without nautilus and get the changes in for next weeks update. > It's been on my todo list with changes when I update it, but I > might as well do it now. > > Regarding your request to take over: I'd still prefer to maintain > it and use it as my primary terminal emulator. You mentioned > wanting to take it over so you can submit an updated slackbuild to > ponce's slackware current repo. I was unaware this is something we > can do, but I can certainly do that as well, if ponce is okay with > me making pull requests to his repo. > > Regards, > > Bob > > > > > > On Sun, Oct 11, 2026 at 4:04?PM B. Watson > wrote: > > > > On Sun, 11 Oct 2026, Pablo Romano wrote: > > > > > Hello, > > > > I contacted the maintainer of gnome-terminal on September 27 > to ask for permission to take over maintenance of the package, > but I have not received a > > reply after two weeks. I would therefore like to ask SBo for > permission to take over the package from the current maintainer. > > The current maintainer is Bob Funk. He's an active maintainer, > last > activity September 16, 2026, and he's responded to several emails > from me over the last 2 or 3 months. He maintains most of the > GNOME > builds on SBo, and I don't feel good about giving one of his > builds to > another maintainer without talking to him myself, or seeing a > reply > from him on this mailing list. > > > The current version of gnome-terminal cannot be updated > further due to the limitations of Slackware 15.0. However, the > SlackBuild itself can be > > improved considerably. > > > > At present, it declares gnome-shell and nautilus as > dependencies, which makes building the package take a very > long time. Neither of them is actually > > required for the core gnome-terminal application; they are > only needed for the optional GNOME Shell search provider and > Nautilus extension. > > That seems like a good idea to me. Bob, you listening? > > _______________________________________________ > 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 Oct 12 18:39:45 2026 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 12 Oct 2026 20:39:45 +0200 Subject: [Slackbuilds-users] Fwd: gnome-terminal SlackBuild In-Reply-To: References: Message-ID: Il giorno lun 12 ott 2026 alle ore 19:17 Pablo Romano ha scritto: > Hi Matteo, > > First of all, thank you for the time and effort you put into maintaining > the repository for Slackware-current. > > I understand your policy regarding the repository, but I have a question > about the gnome-terminal package. > > The version currently available in SBo is 3.43.90, which is kept there > because of the dependency limitations of Slackware 15.0. However, the > current upstream stable release is 3.60.0, and Slackware-current already > provides a sufficiently recent dependency stack to build it. > > So, in this particular case, the old version in SBo is not really a > limitation of Slackware-current itself, but rather a consequence of SBo > having to remain compatible with Slackware 15.0. > this could also be true for everything else that cannot be upgraded because libraries in 15.0 are too old, right? like all the other gnome scripts, for example, but probably also thousands other ones... > Would you consider accepting a current-specific version bump to > gnome-terminal 3.60.0 as an exception to the usual policy? > like I said if it's something that has some added value (the ${good_reasons} indicated before) and the maintainer agrees then it's ok for me... Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From promano7 at hotmail.com Mon Oct 12 19:14:22 2026 From: promano7 at hotmail.com (Pablo Romano) Date: Mon, 12 Oct 2026 21:14:22 +0200 Subject: [Slackbuilds-users] Fwd: gnome-terminal SlackBuild In-Reply-To: References: Message-ID: Understood, Matteo. If I can't find a good reason to update gnome-terminal to 3.60.0, we'll keep the current version as it is. The current SlackBuild I sent Bob works on Slackware-current. Thanks. El 12/10/26 a las 20:39, Matteo Bernardini escribi?: > Il giorno lun 12 ott 2026 alle ore 19:17 Pablo Romano > ha scritto: > > Hi Matteo, > > First of all, thank you for the time and effort you put into > maintaining the repository for Slackware-current. > > I understand your policy regarding the repository, but I have a > question about the gnome-terminal package. > > The version currently available in SBo is 3.43.90, which is kept > there because of the dependency limitations of Slackware 15.0. > However, the current upstream stable release is 3.60.0, and > Slackware-current already provides a sufficiently recent > dependency stack to build it. > > So, in this particular case, the old version in SBo is not really > a limitation of Slackware-current itself, but rather a consequence > of SBo having to remain compatible with Slackware 15.0. > > > this could also be true for everything else that cannot be upgraded > because libraries in 15.0 are too old, right? like all the other gnome > scripts, for example, but probably also thousands other ones... > > Would you consider accepting a current-specific version bump to > gnome-terminal 3.60.0 as an exception to the usual policy? > > > like I said if it's something that has some added value (the > ${good_reasons} indicated before) and the maintainer agrees then it's > ok for me... > > 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bobfunk11 at gmail.com Tue Oct 13 14:05:45 2026 From: bobfunk11 at gmail.com (Bob Funk) Date: Tue, 13 Oct 2026 09:05:45 -0500 Subject: [Slackbuilds-users] Fwd: gnome-terminal SlackBuild In-Reply-To: References: Message-ID: @Pablo - I already submitted a slackbuild update yesterday morning which switched off nautilus and search_provider by default, with variables to enable it again. I also tested it against my Slackware current box and it built fine there too. cwilling already merged the update so it should be in the repo next Saturday. Regarding ponce's repo - I'll leave things as they are as it seems he doesn't want any more weekly churn in that repo. I do have an entire backlog of packages that need to be updated for next Slackware release that build on current but not on 15.0. While I'd be willing to upload to a public repo, I'll follow his preferences and avoid making pull requests. Regards, Bob On Mon, Oct 12, 2026 at 2:14?PM Pablo Romano wrote: > Understood, Matteo. If I can't find a good reason to update gnome-terminal > to 3.60.0, we'll keep the current version as it is. The current SlackBuild > I sent Bob works on Slackware-current. > > Thanks. > > > El 12/10/26 a las 20:39, Matteo Bernardini escribi?: > > Il giorno lun 12 ott 2026 alle ore 19:17 Pablo Romano < > promano7 at hotmail.com> ha scritto: > >> Hi Matteo, >> >> First of all, thank you for the time and effort you put into maintaining >> the repository for Slackware-current. >> >> I understand your policy regarding the repository, but I have a question >> about the gnome-terminal package. >> >> The version currently available in SBo is 3.43.90, which is kept there >> because of the dependency limitations of Slackware 15.0. However, the >> current upstream stable release is 3.60.0, and Slackware-current already >> provides a sufficiently recent dependency stack to build it. >> >> So, in this particular case, the old version in SBo is not really a >> limitation of Slackware-current itself, but rather a consequence of SBo >> having to remain compatible with Slackware 15.0. >> > > this could also be true for everything else that cannot be upgraded > because libraries in 15.0 are too old, right? like all the other gnome > scripts, for example, but probably also thousands other ones... > > >> Would you consider accepting a current-specific version bump to >> gnome-terminal 3.60.0 as an exception to the usual policy? >> > > like I said if it's something that has some added value (the > ${good_reasons} indicated before) and the maintainer agrees then it's ok > for me... > > Matteo > > _______________________________________________ > SlackBuilds-users mailing listSlackBuilds-users at slackbuilds.orghttps://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 mm at dorfdsl.de Wed Oct 14 14:45:00 2026 From: mm at dorfdsl.de (Marco Moock) Date: Wed, 14 Oct 2026 16:45:00 +0200 Subject: [Slackbuilds-users] ripe-atlas-tools Message-ID: Hello! I've created some Slackbuilds for ripe-atlas-tools (the CLI tools to create network measurements). They are my first ones where Python is involved. Is the usage of setup.py right here? The tools need some extra Python modules that are hosted in a separate git repo. Is it right to have multiple Slackbuilds here? I've attached them to the mail, feel free to give suggestions for improvement. -- kind regards Marco Muell und Spam bitte an abfalleimer2002 at stinkedores.dorfdsl.de -------------- next part -------------- A non-text attachment was scrubbed... Name: ripe-atlas-cousteau.tar Type: application/x-tar Size: 10240 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ripe-atlas-sagan.tar Type: application/x-tar Size: 10240 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ripe-atlas-tools.tar Type: application/x-tar Size: 10240 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 665 bytes Desc: OpenPGP digital signature URL: From nomnombtc at arcor.de Wed Oct 14 20:10:02 2026 From: nomnombtc at arcor.de (nnb) Date: Wed, 14 Oct 2026 22:10:02 +0200 Subject: [Slackbuilds-users] ripe-atlas-tools In-Reply-To: References: Message-ID: <600acd90-ed9e-4f4f-897a-aa6b3205644e@arcor.de> Hello :) Am 14.10.26 um 16:45 schrieb Marco Moock: > Hello! > > I've created some Slackbuilds for ripe-atlas-tools (the CLI tools to > create network measurements). > > They are my first ones where Python is involved. > > Is the usage of setup.py right here? Seems fine, but all three tools mention Python 3.10 and upwards in setup.py. You need to make sure they really work fine on stable with the old outdated Python 3.9. > The tools need some extra Python modules that are hosted in a separate > git repo. > > Is it right to have multiple Slackbuilds here? I think this is correct. I noticed ripe-atlas-cousteau and ripe-atlas- sagan have no dependencies listed in the .info file. It looks like they won't work without ripe-atlas-tools, so I would just list this as REQUIRES="ripe-atlas-tools". Then if it gets installed via automated tools it will pull in all the main dependencies anyway (assuming it doesn't need additional ones). > I've attached them to the mail, feel free to give suggestions for > improvement. Maybe just nitpicking, but the template for python has been updated mainly the find and chmod part. Might be better to have this included for new submits. https://slackbuilds.org/templates/python-template.SlackBuild Best regards, -- nnb From fourtysixandtwo at sliderr.net Wed Oct 14 21:31:04 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Wed, 14 Oct 2026 15:31:04 -0600 Subject: [Slackbuilds-users] ripe-atlas-tools In-Reply-To: <600acd90-ed9e-4f4f-897a-aa6b3205644e@arcor.de> References: <600acd90-ed9e-4f4f-897a-aa6b3205644e@arcor.de> Message-ID: nnb mentioned most of what I was going to say already except there's a few more fixes coming to the templates that we overlooked previously. Here's the fixed slackbuilds matching the templates and a few missing deps mentioned in setup.py for ripe-atlas-tools. I did test and they work despite saying 3.10 is minimum required version. Cheers. On Wed, 14 Oct 2026 at 14:10, nnb via SlackBuilds-users wrote: > > Hello :) > > Am 14.10.26 um 16:45 schrieb Marco Moock: > > Hello! > > > > I've created some Slackbuilds for ripe-atlas-tools (the CLI tools to > > create network measurements). > > > > They are my first ones where Python is involved. > > > > Is the usage of setup.py right here? > > Seems fine, but all three tools mention Python 3.10 and upwards in > setup.py. You need to make sure they really work fine on stable with > the old outdated Python 3.9. > > > The tools need some extra Python modules that are hosted in a separate > > git repo. > > > > Is it right to have multiple Slackbuilds here? > > I think this is correct. I noticed ripe-atlas-cousteau and ripe-atlas- > sagan have no dependencies listed in the .info file. It looks like > they won't work without ripe-atlas-tools, so I would just list this > as REQUIRES="ripe-atlas-tools". Then if it gets installed via automated > tools it will pull in all the main dependencies anyway (assuming it > doesn't need additional ones). > > > I've attached them to the mail, feel free to give suggestions for > > improvement. > > Maybe just nitpicking, but the template for python has been updated > mainly the find and chmod part. Might be better to have this included > for new submits. > https://slackbuilds.org/templates/python-template.SlackBuild > > > Best regards, > -- > nnb > > _______________________________________________ > 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 -------------- A non-text attachment was scrubbed... Name: ripe-atlas-slackbuilds.tar.gz Type: application/gzip Size: 2851 bytes Desc: not available URL: From jebrhansen+SBo at gmail.com Fri Oct 16 06:54:48 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Thu, 15 Oct 2026 23:54:48 -0700 Subject: [Slackbuilds-users] ripe-atlas-tools In-Reply-To: References: <600acd90-ed9e-4f4f-897a-aa6b3205644e@arcor.de> Message-ID: On Wed, Oct 14, 2026 at 2:31?PM fourtysixandtwo wrote: > nnb mentioned most of what I was going to say already except there's a > few more fixes coming to the templates that we overlooked previously. > Were there discussions about potential template changes that I missed (besides the find command that was brought to this list by B. Watson)? I had ideas I wanted to share, and I imagine others have ideas that might be worth considering before pushing big changes. However, I assumed there wouldn't be massive template changes before the attempt to get the repo ready for 16.0, which is why I kept them to myself for now. It seemed reasonable that these discussions would've happened on the mailing list before making changes to the stable templates, which is why I didn't create a thread about my handling of crate files and the resulting SlackBuild (my script also needed some refinement, which I hadn't felt rushed to do since I assumed big template changes would've only occurred once SBo went into development mode for the 16.0 release). My implementation might not be the best, but maybe the one in the templates isn't the best either and pushing it out to the community might've resulted in an even better implementation. However, adding the version to the templates that was added without discussion shoehorns us into that implementation when better options might exist. The fact there are additional changes needed to these templates for fixes that were overlooked further solidifies that big changes like these should be sent out to the masses for review before implementation. The issues might've been caught before there were official template updates. I didn't reply to the email about the changes to the templates (even though I was really frustated when I saw it) simply because it seemed like it had already been decided by the admins, but knowing there are addtional "fixes" that need to be made, it reinvigorated my desire to vent my frustration that the majority of these changes were made without community involvement. None of this criticism is directed specifically towards fourtysixandtwo, it was simply the email I replied to after finding out there were going to be additional changes to fix the changes to the templates. Jeremy, aka bassmadrigal -------------- next part -------------- An HTML attachment was scrubbed... URL: From fourtysixandtwo at sliderr.net Fri Oct 16 17:08:29 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Fri, 16 Oct 2026 11:08:29 -0600 Subject: [Slackbuilds-users] ripe-atlas-tools In-Reply-To: References: <600acd90-ed9e-4f4f-897a-aa6b3205644e@arcor.de> Message-ID: Hey Jeremy, Sorry for the confusion, the "fixes" I was referring to in that email were the ones already discussed, but not yet applied to all the templates (the intended but overlooked part). Specifically the minor find and PKGDOC changes. Adding the rust templates was long overdue and we needed a starting point. Good/better ideas are always welcome for discussion, the templates are not set in stone. Start a new email thread about them when you are ready. Cheers. fourtysixandtwo On Fri, 16 Oct 2026 at 00:55, Jeremy Hansen wrote: > > On Wed, Oct 14, 2026 at 2:31?PM fourtysixandtwo wrote: >> >> nnb mentioned most of what I was going to say already except there's a >> few more fixes coming to the templates that we overlooked previously. > > > Were there discussions about potential template changes that I missed (besides the find command that was brought to this list by B. Watson)? I had ideas I wanted to share, and I imagine others have ideas that might be worth considering before pushing big changes. However, I assumed there wouldn't be massive template changes before the attempt to get the repo ready for 16.0, which is why I kept them to myself for now. > > It seemed reasonable that these discussions would've happened on the mailing list before making changes to the stable templates, which is why I didn't create a thread about my handling of crate files and the resulting SlackBuild (my script also needed some refinement, which I hadn't felt rushed to do since I assumed big template changes would've only occurred once SBo went into development mode for the 16.0 release). My implementation might not be the best, but maybe the one in the templates isn't the best either and pushing it out to the community might've resulted in an even better implementation. However, adding the version to the templates that was added without discussion shoehorns us into that implementation when better options might exist. > > The fact there are additional changes needed to these templates for fixes that were overlooked further solidifies that big changes like these should be sent out to the masses for review before implementation. The issues might've been caught before there were official template updates. I didn't reply to the email about the changes to the templates (even though I was really frustated when I saw it) simply because it seemed like it had already been decided by the admins, but knowing there are addtional "fixes" that need to be made, it reinvigorated my desire to vent my frustration that the majority of these changes were made without community involvement. > > None of this criticism is directed specifically towards fourtysixandtwo, it was simply the email I replied to after finding out there were going to be additional changes to fix the changes to the templates. > > Jeremy, aka bassmadrigal > _______________________________________________ > 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 promano7 at hotmail.com Fri Oct 16 18:14:03 2026 From: promano7 at hotmail.com (Pablo Romano) Date: Fri, 16 Oct 2026 20:14:03 +0200 Subject: [Slackbuilds-users] Fwd: gnome-terminal SlackBuild In-Reply-To: References: Message-ID: Hello @Bob, That seems fine to me, thank you. El 13/10/26 a las 16:05, Bob Funk escribi?: > @Pablo - I already submitted a slackbuild update yesterday morning > which switched off nautilus and search_provider by default, with > variables to enable it again. I also tested it against my Slackware > current box and it built fine there too. cwilling already merged the > update so it should be in the repo next Saturday. > > Regarding ponce's repo - I'll leave things as they are as it seems he > doesn't want any more weekly churn in that repo. I do have an entire > backlog of packages that need to be updated for next Slackware release > that build on current but not on 15.0. While I'd be willing to upload > to a public repo, I'll follow his preferences and avoid making pull > requests. > > Regards, > Bob > > On Mon, Oct 12, 2026 at 2:14?PM Pablo Romano wrote: > > Understood, Matteo. If I can't find a good reason to update > gnome-terminal to 3.60.0, we'll keep the current version as it is. > The current SlackBuild I sent Bob works on Slackware-current. > > Thanks. > > > El 12/10/26 a las 20:39, Matteo Bernardini escribi?: >> Il giorno lun 12 ott 2026 alle ore 19:17 Pablo Romano >> ha scritto: >> >> Hi Matteo, >> >> First of all, thank you for the time and effort you put into >> maintaining the repository for Slackware-current. >> >> I understand your policy regarding the repository, but I have >> a question about the gnome-terminal package. >> >> The version currently available in SBo is 3.43.90, which is >> kept there because of the dependency limitations of Slackware >> 15.0. However, the current upstream stable release is 3.60.0, >> and Slackware-current already provides a sufficiently recent >> dependency stack to build it. >> >> So, in this particular case, the old version in SBo is not >> really a limitation of Slackware-current itself, but rather a >> consequence of SBo having to remain compatible with Slackware >> 15.0. >> >> >> this could also be true for everything else that cannot be >> upgraded because libraries in 15.0 are too old, right? like all >> the other gnome scripts, for example, but probably also thousands >> other ones... >> >> Would you consider accepting a current-specific version bump >> to gnome-terminal 3.60.0 as an exception to the usual policy? >> >> >> like I said if it's something that has some added value (the >> ${good_reasons} indicated before) and the maintainer agrees then >> it's ok for me... >> >> 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at dorfdsl.de Fri Oct 16 18:26:39 2026 From: mm at dorfdsl.de (Marco Moock) Date: Fri, 16 Oct 2026 20:26:39 +0200 Subject: [Slackbuilds-users] ripe-atlas-tools In-Reply-To: <600acd90-ed9e-4f4f-897a-aa6b3205644e@arcor.de> References: <600acd90-ed9e-4f4f-897a-aa6b3205644e@arcor.de> Message-ID: <3940aca8-af3f-476f-b998-abe2d4f01343@dorfdsl.de> Am 14.10.26 um 22:10 schrieb nnb via SlackBuilds-users: > Hello :) > > Am 14.10.26 um 16:45 schrieb Marco Moock: >> Hello! >> >> I've created some Slackbuilds for ripe-atlas-tools (the CLI tools to >> create network measurements). >> >> They are my first ones where Python is involved. >> >> Is the usage of setup.py right here? > > Seems fine, but all three tools mention Python 3.10 and upwards in > setup.py. You need to make sure they really work fine on stable with > the old outdated Python 3.9. I cannot guarantee that. Although, is it enough to mention that in README? Maybe people want to use it on current... >> The tools need some extra Python modules that are hosted in a separate >> git repo. >> >> Is it right to have multiple Slackbuilds here? > > I think this is correct. I noticed ripe-atlas-cousteau and ripe-atlas- > sagan have no dependencies listed in the .info file. It looks like > they won't work without ripe-atlas-tools, so I would just list this > as REQUIRES="ripe-atlas-tools". Then if it gets installed via automated > tools it will pull in all the main dependencies anyway (assuming it > doesn't need additional ones). Doesn't that create a never-ending circle? >> I've attached them to the mail, feel free to give suggestions for >> improvement. > > Maybe just nitpicking, but the template for python has been updated > mainly the find and chmod part. Might be better to have this included > for new submits. > https://slackbuilds.org/templates/python-template.SlackBuild Thanks! I will have a look. -- Gru? Marco Muell und Spam bitte an abfalleimer2002 at stinkedores.dorfdsl.de -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 665 bytes Desc: OpenPGP digital signature URL: From slack at giand.it Fri Oct 16 20:23:09 2026 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Fri, 16 Oct 2026 22:23:09 +0200 Subject: [Slackbuilds-users] bwidget In-Reply-To: <20261009233349.225f7583@banane.kuchen> References: <20261009233349.225f7583@banane.kuchen> Message-ID: <1dcba5c9-3885-408f-bc53-a80cc7b4a7a3@giand.it> Il 09/10/26 23:33, Ruben Schuller ha scritto: > Hi, > > (CC-ing the list because gmail probably does throw away my mail..) > > are you still interested in maintaining the bwidget SlackBuild? The > version listed on SBo is 1.9.8 from 2015, the latest is 1.10.1 from > 2024 [1]. The new version also builds with the new Tcl 9.x release, > which I hope will be included in the next Slackware release. > > Kind Regards > Ruben > > [1] https://sourceforge.net/projects/tcllib/files/BWidget/ > _______________________________________________ > 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/ bwidget is required as dependency by two packages: mcu8051ide (with the same maintainer of bwidget) and therion, maintained by me. Until now, therion didn't require any update of bwidget and probably also mcu8041ide, so I think that the maintainer does not consider the update essential. It may also be the case that he is no longer interested in maintaining this package. I don't know -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From willysr at slackbuilds.org Sat Oct 17 02:47:03 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 17 Oct 2026 09:47:03 +0700 Subject: [Slackbuilds-users] Updates - 20261017.1 Message-ID: <20261017094703.5a30afff@home.slackie.org> Sat Oct 17 02:36:38 UTC 2026 academic/free42: Updated for version 3.4 academic/ngspice-jit: Updated for version 46.12. academic/ngspice-wave: Updated for version 0.1.2. academic/plus42: Updated for version 1.4 academic/zotero: update to 10.0.6 audio/kew: Updated for version 4.4.1. audio/linuxsampler: New maintainer. desktop/ClamAV-GUI: Updated for version 1.5.0 desktop/cbatticon: update maintainer email desktop/dwm: update maintainer email desktop/evilwm: update maintainer email desktop/fbpanel: update maintainer email desktop/gromit-mpx: Update README. desktop/gsimplecal: Updated for version 2.5.4 desktop/herbe: update maintainer email desktop/hsetroot: update maintainer email desktop/i3lock: update maintainer email desktop/icewm-themes: update maintainer email desktop/pfetch: update maintainer email desktop/polybar: update maintainer email desktop/slstatus: update maintainer email desktop/sxhkd: update maintainer email desktop/sxwm: Added (X11 Tiling WM). desktop/sxwm: Fix permission. desktop/vdesk: update maintainer email desktop/wl-mirror: Updated for version 0.18.5 desktop/xmenu: update maintainer email development/Kiro: Updated for version 1.3.0. development/Kiro: Updated for version 1.3.11. development/a68g: Updated for version 3.13.4 development/air: Added (Live reload for Go applications). development/antigravity-cli: Updated for version 1.3.4 development/antigravity: Updated for version 2.22.0 development/aspnetcore-runtime-10.0: Updated for version 10.0.13. development/aspnetcore-runtime-8.0: Updated for version 8.0.32. development/aspnetcore-runtime-9.0: Updated for version 9.0.21. development/aws-cdk: Updated for version 2.1145.0. development/bbcsdl: Updated for version 20261009_5b62c85 development/buf: Updated for version 1.74.0. development/cargo-c: Updated for version 0.10.26 development/chatgpt: Updated for version 26.1007.71326. development/clion: Update DOWNLOAD. development/dotnet-runtime-10.0: Updated for version 10.0.13. development/dotnet-runtime-8.0: Updated for version 8.0.32. development/dotnet-runtime-9.0: Updated for version 9.0.21. development/dotnet-sdk-10.0: Updated for version 10.0.402. development/dotnet-sdk-8.0: Updated for version 8.0.426. development/dotnet-sdk-9.0: Updated for version 9.0.319. development/eisl: Updated for version 5.69 development/electron-bin: Updated for version 44.7.1 development/ggml: Added (Tensor Library for ML). development/gitleaks: Added (Secrets detection tool). development/goland: Fix DOWNLOAD. development/goland: Updated for version 2026.2.3. development/jupyter-nbconvert: Updated for version 7.17.2 development/just: Added (Project-specific command runner). development/kube-linter: Added (Kubernetes file linter). development/kubeconform: Added (Kubernetes Validator). development/lazygit: Updated for version 0.66.1 + new maintainer development/lefthook: Added (Git hooks manager). development/libmcpu: Added (Software CPU and toolchain). development/lua-language-server: Updated for version 3.19.2. development/mcpu-cpp: Added (MCPU languages preprocessor). development/mle: update maintainer email development/mongodb-compass: Updated for version 1.53.0. development/nedit: update maintainer email development/osv-scanner: Added (Vulnerability checker). development/poedit: Updated for version 3.10. development/revive: Added (Configurable Go linter). development/rider: Update DOWNLOAD. development/scala: Updated for version 2.13.18. development/source-highlight: update maintainer email development/sourcegit: Updated for version 2026.22 development/srcML: Updated script. development/stagit: Updated for version 1.3 development/syft: Added (Bills of materials generator). development/tcc: Updated for version 0.9.28rc+20261003_43c7708b. development/vscode-bin: Updated for version 1.141.1. development/vscode-bin: Updated for version 1.142.0. development/xmake: Updated for version 3.1.2. development/zig-bin: update to 0.9.1 development/zig: update to 0.17.0 development/zubr: Added (Parser Generator). games/crispy-doom: Updated for version 7.2. games/domination: Updated for version 1.3.6. games/etlegacy: Updated for version 2.86.2. games/icebreaker: Updated for version 2.2.2+20241204_6f9fd2a. games/immortal-barons: Updated for version 0.2.6 games/redeclipse: Fix download links to use full commit ID games/sameboy: Updated for version 1.0.4. games/stockfish: Updated for version 19. games/zork-mit: Add fixes from upstream git. games/zsnes: Updated for version 2.3.7. gis/libspatialindex: Updated for version 2.0.0. gis/proj-data: Updated for version 1.25. gis/proj: Updated for version 9.9.0. gis/qgis: Updated for version 3.44.15. gis/saga-gis: Updated MD5SUM graphics/OpenCASCADE: Check ffmpeg version graphics/gifsicle: Updated for version 1.97. graphics/pencil3: Updated for version 3.1.1 + new maintainer graphics/xnap: update maintainer email ham/gridtracker2: Updated for version 2.261011.2. libraries/activemq-cpp: New maintainer. libraries/bsddialog: update maintainer email libraries/dovi_tool: Added (Tool for working with Dolby Vision). libraries/flatbuffers: Version bump to 25.12.19 libraries/flint: Update DOWNLOAD. libraries/fstrcmp: Change to correct email libraries/imath: Added (C++ Library). libraries/jbigkit: Updated for version 2.2. libraries/libayatana-appindicator: Updated for version 0.6.1. libraries/libb64: Updated for version 2.0.0.1. libraries/libcec: Version bump to 8.1.7 libraries/libcurl-gnutls: Updated for version 8.23.0. libraries/libdraco: Updated REQUIRES. libraries/libgig: New maintainer. libraries/libgrapheme: update maintainer email libraries/libmpu: Updated for version 1.0.28. libraries/libmpuio: Updated for version 1.0.8. libraries/libunique: Change to correct email libraries/libxnvctrl: Updated for version 595.104.02. libraries/lua-posix: Updated for version 37.0. libraries/minizip-ng: Added (C Library). libraries/mygpoclient: Updated for version 1.10. libraries/oath-toolkit: Updated for version 2.6.15. libraries/podcastparser: Updated for version 0.6.11. libraries/tinygltf: Updated README. libraries/wxWidgets: Updated for version 3.2.12. libraries/xmpppy: Removed (Unmaintained). libraries/yaz: Updated for version 5.38.0 + new maintainer misc/birthday: Removed (unmaintained and upstream is 404. misc/es40: Updated for version 0.91.1 misc/recode: Version bump to 3.7.13 multimedia/minidlna: Fix SlackBuild to patch when ffmpeg is greater or equal 7 (not only 7). multimedia/systran-faster-whisper-xxl-bin: Added (Whisper). network/3proxy: Updated for version 1.0.1. network/amavisd-new: Updated for version 2.15.0. network/brave-browser: update to 1.97.57 network/brave-origin: update to 1.97.57 network/cloudflared-bin: Updated for version 2026.10.1. network/deltachat-desktop: Updated for version 2.62.0. network/discord: Version bump to 1.0.161 network/discord: Version bump to 1.0.162 network/dma: update maintainer email network/dokuwiki: Updated for version 20260714c. network/dropbox: Updated for version 275.4.3565. network/element-desktop: Updated for version 1.12.32. network/franz: Updated for version 6.9.2. network/gallery-dl: Updated for version 1.32.16 network/helium-browser: Updated for version 0.19.2.1 network/helm: Updated for version 4.3.1 network/ii: update maintainer email network/ipxnet: Updated for version 20241125.a1c36e4. network/k9s: update maintainer email network/lchat: update maintainer email network/libressl: update maintainer email network/librewolf: Updated for version 158.0_1 network/libtls: update maintainer email network/maildrop: Updated for version 4.0.5 network/mblaze: update maintainer email network/microsoft-edge: Updated for version 155.0.4283.45. network/mullvad-browser: Updated for version 15.0.25 network/ocserv: Updated for version 1.6.0. network/piavpn-app: Updated for version 3.8_08539. network/rclone: update to 1.75.2 network/senpai: update maintainer email network/sfeed: update maintainer email network/shibboleth-sp: Updated for version 3.6.0. network/signal-desktop: Updated for version 8.31.0. network/snac2: Updated for version 2.95. network/ssmtp: Updated for version 2.66. network/syncthingtray-bin: Updated for version 2.1.8. network/teams-for-linux: Updated for version 2.24.0. network/telegram: Updated for version 7.3.1. network/tnfsd: Updated for version 26.0915.1+20261003_4aab910. network/tor-browser: Updated for version 15.0.25. network/urlscan: Updated for version 1.2.0 + new maintainer. network/vivaldi: Updated for version 8.2.4133.89. network/waterfox: Updated for version 6.7.6 network/wifitui: update maintainer email network/zen-browser: Updated for version 1.23.2b office/Joplin: Fix permission. office/Joplin: Updated for version 3.7.21. office/antixls: Added (XLS file processing). office/ccal: Update DOWNLOAD. office/hebcal: Updated for version 5.17.0. office/jsignpdf: Added (PDF digital signing tool). office/ledger-live: Updated for version 4.24.0 office/minidjvu: Make VERSION shorter (same version). office/onlyoffice-desktopeditors: Updated for version 10.0.0 office/openoffice-langpack: Updated for version 4.1.17 office/openoffice.org: Updated for version 4.1.17 office/paps: Fix typo. office/qownnotes: Updated for version 26.10.7. office/sent: update maintainer email office/slides: Added (Presentation tool). office/timetrap: Update dep. office/treesheets: New maintainer perl/perl-Clone-Choose: Added (Choose appropriate clone utility). perl/perl-Cpanel-JSON-XS: Version bump to 4.80 perl/perl-Crypt-RC4: Added (RC4 encryption algorithm). perl/perl-DBD-Pg: Updated for version 3.21.2. perl/perl-Data-OptList: Updated for version 0.115. perl/perl-Digest-Perl-MD5: Added (Ron Rivest's MD5 Algorithm). perl/perl-Encode-IMAPUTF7: Added (Modify UTF-7 encoding for IMAP). perl/perl-File-Finder: Updated for version 1.01 perl/perl-Hash-Merge: Added (Merges arbitrarily deep hashes into a single hash). perl/perl-IO-Tee: Added (Multiplex output to multiple outputs) perl/perl-MIME-tools: Updated for version 5.519. perl/perl-Mail-IMAPClient: Added (IMAP Client API). perl/perl-OLE-Storage_Lite: Added (OLE document interface class) perl/perl-Params-SomeUtil: Added (Functions for paramater checking). perl/perl-Spreadsheet-ParseExcel: Added (Excel file interface). perl/perl-Sub-Exporter: Updated for version 0.992. perl/perl-Test-Without-Module: Added (Testing fallback behaviour). perl/perl-Text-CSV_XS: Updated for version 1.65 perl/perl-X11-Protocol-Other: Updated for version 31 perl/perl-html-parser: Updated for version 3.86. perl/perl-lwp-mediatypes: Updated for version 6.05. perl/perl-net-dbus: Change to correct email python/python2-nuitka: Updated for version 4.3.1 python/python3-discovery: Version bump to 1.6.2 python/python3-dunamai: Updated for version 1.26.3. python/python3-executing: Version bump to 2.3.0 python/python3-jsonpatch: Updated README python/python3-matplotlib-inline: Version bump to 0.2.2 python/python3-nuitka: Updated for version 4.3.1 python/python3-pdm-backend: Version bump to 2.5.0 python/python3-pdm-build-locked: Version bump to 0.3.8 python/python3-pluggy: Note on why we can't update python/python3-poetry-dynamic-versioning: Updated for v 1.10.1. python/python3-pure_eval: Version bump to 0.2.4 python/python3-pycryptodomex: Updated for version 3.24.1. python/python3-pypdf: Updated for version 6.20.1 python/python3-pytz: Version bump to 2026.5 python/python3-sentry_sdk: Updated for version 2.72.0 python/python3-slugify: Version bump to 9.1.3 python/python3-tomlkit: Version bump to 0.15.2 python/python3-urllib3-future: Version bump to 2.25.902 python/python3-validators: Version bump to 0.36.0 python/python3-virtualenv: Version bump to 21.14.8 python/uv-bin: Updated for version 0.13.1. ruby/rubygem-sqlite3: Added (Interface to sqlite3 DB). ruby/sqlite3: Removed (renamed to rubygem-sqlite3). system/0xproto-fonts: Added (programming font). system/CPU-X: Updated for version 5.4.1. system/FreeFileSync: Updated for version 14.13 system/Lmod: Updated for version 9.4.5. system/TLP: update maintainer email system/android-udev-rules: Updated for version 2026.09.22. system/bfs: update maintainer email system/csv2sql: Update REQUIRES, sqlite3 => rubygem-sqlite3. system/csv2sql: Update dep. system/davfs2: Updated for version 1.7.3 + new maintainer system/dfm: update maintainer email system/docker-compose: Updated for version 5.6.0 system/fff: update maintainer email system/game-devices-udev: Version bump to 1.1 system/gnome-terminal: Updated script and added build options. system/intel-microcode: Updated for version 20260925 system/jenkins: Updated for version 2.580.1. system/keyd: update maintainer email system/llama.cpp: Added (LLM inference in C/C++). system/lshw: Updated for version B.02.20 + new maintainer. system/man-pages-fr: Updated for version 3.70_8. system/man-pages-ja: Updated for version 20260815. system/mongodb: Updated for version 8.3.13. system/mtm: update maintainer email system/multitail: Updated for version 7.1.6. system/nvidia-legacy390-kernel: Patched for 7.3 kernel. system/nvidia-legacy470-driver: Fixed 10-nvidia.conf. system/nvidia-legacy470-kernel: Patched for kernel 7.3. system/nvtop: Updated for version 3.3.2. system/passwordsafe: Updated for version 3.72.2 + new maintainer system/pipes.sh: update maintainer email system/powerkit: New maintainer. system/powershell: Updated for version 7.6.7. system/rover: update maintainer email system/sbo-create: Updated for version 2.3.2. system/spacefm: New maintainer. system/veracrypt: Updated for version 1.26.29 + new maintainer system/wmconfig: Updated for version 1.5.3 system/xbattmon: update maintainer email system/xosview: update maintainer email system/zsh-completions: Updated for version 0.36.0 + new maintainer. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From nomnombtc at arcor.de Sat Oct 17 18:58:39 2026 From: nomnombtc at arcor.de (nnb) Date: Sat, 17 Oct 2026 20:58:39 +0200 Subject: [Slackbuilds-users] ripe-atlas-tools In-Reply-To: <3940aca8-af3f-476f-b998-abe2d4f01343@dorfdsl.de> References: <600acd90-ed9e-4f4f-897a-aa6b3205644e@arcor.de> <3940aca8-af3f-476f-b998-abe2d4f01343@dorfdsl.de> Message-ID: Hello! Am 16.10.26 um 20:26 schrieb Marco Moock: > Am 14.10.26 um 22:10 schrieb nnb via SlackBuilds-users: [...] >> Seems fine, but all three tools mention Python 3.10 and upwards in >> setup.py. You need to make sure they really work fine on stable with >> the old outdated Python 3.9. > > I cannot guarantee that. Although, is it enough to mention that in README? > > Maybe people want to use it on current... All scripts on SBo must work correctly on stable, so you have to test the runtime functions (e.g., in a VM). fourtysixandtwo confirmed that he tested the script and that it works, despite the 3.10 minimum version. It is just not officially supported anymore and could break with future releases. >>> The tools need some extra Python modules that are hosted in a >>> separate git repo. >>> >>> Is it right to have multiple Slackbuilds here? >> >> I think this is correct. I noticed ripe-atlas-cousteau and ripe-atlas- >> sagan have no dependencies listed in the .info file. It looks like >> they won't work without ripe-atlas-tools, so I would just list this >> as REQUIRES="ripe-atlas-tools". Then if it gets installed via automated >> tools it will pull in all the main dependencies anyway (assuming it >> doesn't need additional ones). > > Doesn't that create a never-ending circle? Not really, but my suggestion wasn't ideal anyway. Sometimes it works, but fourtysixandtwo's handling of the REQUIRES in his email attachment "ripe-atlas-slackbuilds.tar.gz" is way better and more correct. regards, -- nnb