From willysr at slackbuilds.org Sat Aug 1 00:55:04 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 1 Aug 2026 07:55:04 +0700 Subject: [Slackbuilds-users] Updates - 20260801.1 Message-ID: <20260801075504.2a70efb1@home.slackie.org> Sat Aug 1 00:40:47 UTC 2026 academic/geda-gaf: New maintainer. academic/gtkwave: New maintainer. academic/latex2html: New maintainer. academic/ncview: new maintainer academic/ngspice: Updated for version 46. academic/verilog: Orphaned (unmaintained). academic/yices2: New maintainer. accessibility/jpilot: Updated for version 2.0.3. audio/SuperCollider: Fix MD5SUM. audio/SuperCollider: Updated for version 3.13.1. audio/acousticbrainz-music-extractor: Tweak README. audio/alsa-tools: Updated for version 1.2.15. audio/amSynth: Updated for version 2.0.0. audio/calf: Updated for version 0.90.9. audio/cava: Updated for version 1.0.0 + new maintainer. audio/faust: New maintainer. audio/id3tool: Fix homepage/download. audio/linuxsampler: Updated for version 2.4.2. audio/pianobar: Updated for version 2022.04.01. audio/pmidi: Updated for version 1.7.1 audio/qjackctl: Updated for version 1.0.6. audio/sayonara-player: Updated for version 1.12.0_stable1. audio/soundconverter: New maintainer. desktop/NsCDE: Updated for version 2.3 desktop/ansiweather:Updated to version 1.19.1 desktop/bspwm: update to 0.9.12 desktop/catfish: New maintainer. desktop/cwm: update desktop/emwm: update to 2.0 desktop/engrampa: Updated for version 1.28.3. desktop/grun: New maintainer; patch build for newer GCC. desktop/herbstluftwm: Updated for version 0.9.6. desktop/lemonbar: update to 1.5 desktop/mate-terminal: Updated for version 1.28.3. desktop/materia-theme: New maintainer. desktop/mcwm: Fix homepage/download URLs. desktop/mwm-utils: update to 2.0 desktop/slock: update to 1.7 desktop/wmii: New maintainer desktop/xfce4-cpugraph-plugin: New maintainer. desktop/xfce4-datetime-plugin: Update download URL. desktop/xfce4-wavelan-plugin: New maintainer. development/Bear: Updated for version 4.1.5. development/GHDL: New maintainer. development/Kiro: Updated for version 1.0.212. development/Kiro: Updated for version 1.0.242. development/ShellCheck-bin: Updated man page; new maintainer. development/Xdialog: New maintainer. development/antigravity2: Updated for version 2.4.2 development/astyle: Updated for version 3.6.17. development/aws-cdk: Updated for version 2.1133.0. development/aws-cdk: Updated for version 2.1134.0. development/bazel: Updated for version 9.2.0; new maintainer. development/codespell: Updated for version 2.4.3. development/cpan2tgz: New maintainer. development/cproto: Updated for version 4.8a. development/csmith: Fix homepage. development/deno-bin:Updated to version 2.9.4 development/edwood: Updated for version 0.4.0. development/electron-bin: Updated for version 43.2.0 development/es-shell: Updated for version 0.10.0. development/fpc-mingw-w64: Added (Pascal Cross Compilers). development/gdb-dashboard: New maintainer. development/git-cola: added dependencies development/git-cola: update to 4.19.0 and new maintainer development/github-cli: Updated for version 2.97.0 development/julia: Updated for version 1.10.11. development/ldns: Fix MD5SUM. development/mawk: Updated for version 1.3.4_20260302. development/mingw-w64-binutils: Added (Build utilities). development/mlton: New maintainer. development/neatvi: Updated for version 19. development/nextvi: Updated for version 7.0. development/nodejs22: Updated for version 22.23.2. development/nodejs24-bin:Updated to version 24.18.1 development/notepadqq: Updated for version 20260727_132ac0a development/opencomal: Use https URLs. development/openocd: Updated for version 0.12.0 + new maintainer development/pasdoc: Updated for version 1.0.4 development/pcbasic: Updated for version 2.0.8. development/pcc: Updated for version 1.2.0.DEVEL+20260727_08c57ee. development/php82: Updated for version 8.2.33 development/php84: Updated for version 8.4.24 development/qb64pe: Updated for version 4.6.0 development/ratfor: Updated for version 1.07. development/reflex: Updated for version 2.5.4.20260131. development/rgbds: Add note to self. development/sbt: Updated for version 2.0.4 development/sourcegit: Updated for version 2026.16 development/spin: New maintainer. development/vasm: Updated for version 2.0f. development/vscode-bin: Updated for version 1.131.0. development/xtruss: Updated for version 20260410.f723509. development/xxd-standalone: Updated for version 9.2.0658. development/zig-bin: Added (Programming language). development/zig: update to 0.16.0 games/KoboDeluxe: Fix download. games/OpenSD: Added (Userspace Driver). games/VASSAL: Updated for version 3.7.26 games/burgerspace: Fix download. games/cosmosmash: Fix download. games/eduke32_hires_pack: Fix download. games/eduke32_shareware_data: Fix homepage/download. games/fortune_doctor_who: Updated for version 20230720. games/fs-uae-arcade: Removed (use fs-uae-launcher --arcade) games/fs-uae-launcher: Updated for version 3.2.35, New maintainer. games/fs-uae: Updated for version 3.2.35 + new maintainer games/jfsw_demo_data: Fix homepage/download. games/jg-bsnes: Updated for version 2.1.1. games/jg-cega: Updated for version 0.6.2. games/jg-gambatte: Updated for version 0.6.1. games/jg-genplus: Updated for version 1.7.6.6. games/jg-geolith: Updated for version 0.4.2. games/jg-jollycv: Updated for version 2.0.1. games/jg-mednafen: Updated for version 1.32.1.2. games/jg-melonds: Updated for version 1.1.0.1. games/jg-mgba: Updated for version 0.10.5.1. games/jg-nestopia: Updated for version 1.54.0. games/jg-picodrive: Updated for version 1.93.2. games/jg-prosystem: Updated for version 1.5.4. games/jg-sameboy: Updated for version 1.0.3.1. games/jg-vecx: Updated for version 1.2.4. games/jollygood: Updated for version 2.0.1. games/lmarbles: Updated for version 1.1.2. games/maelstrom-mods: Added (Add-on for Maelstrom). games/maelstrom: Updated for version 4.0.2. games/nbsdgames: Updated for version 6.0.2. games/open-adventure: Updated for version 1.22. games/principia: Updated for version 2026.07.15. games/skulltag: Fix downloads. games/sl: new maintainer games/solarus-quest-editor: Removed (FTBFS and archived upstream). games/solarus: Updated for version 2.1.0 games/trigger-rally: Updated for version 0.6.7. games/zdbsp: Fix download. gis/foxtrotgps: New maintainer. graphics/GraphicsMagick: Updated for version 1.3.48. graphics/fbv: Fix homepage. graphics/libfpx: Updated for version 1.3.1_20260725_bb28e42. graphics/meshlab: New maintainer. graphics/tesseract: Updated for version 5.5.3. libraries/agar: Add note to self. libraries/boolstuff: Fix download/homepage. libraries/fcft: update to 3.3.3 libraries/flatzebra: Fix download. libraries/gl2ps: Updated for version 1.4.2 libraries/grpc: Allow building on 32-bit systems libraries/libaribcaption:Updated to version 1.1.2 libraries/libcapsimage: Add note to self. libraries/libdeflate: Added (Compression library). libraries/libgig: Updated for version 4.5.2. libraries/libjxl:Updated to version 0.12.0 libraries/liblogging: Updated for version 1.0.8. libraries/libmateweather: Updated for version 1.28.2. libraries/libmpd: New maintainer. libraries/libmseed: Updated for version 3.4.0. libraries/libmysofa:Updated to version 1.3.5 libraries/libnet: Remove extraneous docs only if they exist. libraries/librist:Updated to version 0.2.20 libraries/libspf2: New maintainer. libraries/libtorrent: Updated for version 0.16.18. libraries/libvterm: Add conflict note. libraries/mpir: Fix compilation on -current (new maint). libraries/openapv:Updated to version 0.3.0.0 libraries/pangox-compat: New maintainer. libraries/ptex: Update MD5SUM. libraries/python3-PyQtWebEngine: New maintainer. libraries/qt3: Use https homepage. libraries/qt4: Use https homepage. libraries/simdjson:Updated to version 4.6.6 libraries/tsocks: New maintainer. libraries/utfcpp: Updated for version 4.1.1. misc/ascii: Fix download. misc/asr-manpages: Use working homepage. misc/axpbox: Added (AXPbox Alpha emulator). misc/doclifter: Fix download. misc/es40: Added (DEC ES40 simulator). misc/figlet: New maintainer. misc/ollama: Updated for version 0.32.5. misc/rsnapshot: New maintainer. misc/tinytldr: Updated for version 1.2.2 misc/wcd: Updated for version 6.0.7. multimedia/AtomicParsley: Updated for version 20240608.083822.1ed9031. multimedia/HandBrake: Version bump to 1.11.2 multimedia/devedeng: Updated for version 4.17.0 multimedia/ffmpeg2theora: Updated for version 0.30 multimedia/strawberry: Updated for version 1.2.26. multimedia/vapoursynth-mvtools: Updated for version 25 multimedia/vapoursynth: Updated for version R71 multimedia/whistle: Orphaned (unmaintained). network/aerc: update to 0.22.0 network/amneziawg-go: Updated for version 3.0.2. network/amneziawg-go: Updated to version 3.0.1. network/amneziawg-kernel: Updated to version 1.0.20260725. network/ani-cli:updated to version 4.15 network/atftp: Updated for version 0.8.1. network/awstats: Updated for version 8.0. network/bozohttpd: Updated for version 20260503. network/brave-browser: Updated for version 1.93.129. network/brave-origin: Updated for version 1.93.129. network/cicb: Updated for version 5.1.3b4+git20251030. network/ckermit: Updated for version 9.0.304.24 network/deluge: Updated for version 2.2.0. network/dnsproxy-bin: Updated for version 0.83.1. network/edbrowse: Updated for version 3.8.17. network/ejabberd: New maintainer. network/filen-desktop-bin: Updated for version 3.0.53 network/franz: Updated for version 6.5.2. network/gallery-dl: Updated for version 1.32.8 network/geomyidae: New naintainer network/glusterfs: New maintainer. network/halloy: Fix permission. network/halloy: Updated for version 2026.8 network/haproxy: Updated for version 3.4.3. network/helium-browser: Updated for version 0.14.9.1 network/hostapd: New maintainer. network/icbm: Updated for version 1.7. network/iperf: New maintainer. network/irc.c: Updated for version 20240412_587e1fd. network/js185: New maintainer. network/ldapvi: New maintainer. network/libdnet: Updated for version 1.18.2. network/librewolf: Updated for version 153.0_3 network/llhttp: Updated for version 9.4.3. network/maildrop: Updated for version 4.0.4. network/metasploit-framework-bin: Updated for version 6.4.147. network/milter-greylist: New maintainer. network/mod_evasive: Updated for version 2.4.0. network/msmtp: update network/ncp: Use working homepage/download. network/opera: Updated for version 133.0.5932.85 network/pfqueue: New maintainer. network/pgbouncer: New maintainer. network/proxychains: Update for version 4.17. network/psi: New maintainer. network/purple-facebook: Removed (non-functional). network/purple-plugin-pack: New maintainer. network/qutebrowser: New maintainer. network/rclone: Updated for version 1.75.0. network/rspamd: Updated for version 4.1.3 network/rtorrent: Updated for version 0.16.18. network/signal-desktop: Updated for version 8.21.0. network/slack: Updated for version 4.51.180. network/squirrelmail: New maintainer. network/static-web-server: Updated for version 2.44.0. network/sylpheed: new maintainer network/tailscale: Updated for version 1.98.10. network/telegram: Updated for version 7.0.6. network/tor: Updated for version 0.4.9.11 network/uget: Fix homepage. network/vivaldi: Updated for version 8.1.4087.61. network/w3m: Updated for version 0.5.6. network/weechat: Updated for version 4.9.5. network/wifi-radar: New maintainer. network/wrk: update to 4.2.0 and new maintainer network/zen-browser: Updated for version 1.21.9b network/zerotier-one: new maintainer office/FreeOffice: Removed unused .desktop files office/LibreOffice: Updated for version 26.2.5.2 office/atril: Updated for version 1.28.6. office/calcurse: Updated for version 4.8.2; new maintainer. office/dictd: New maintainer. office/docx2txt: Fix URLs. office/elyxer: New maintainer. office/freemind: New maintainer (actually, original one). office/jpilot: Moved from accessibility. office/keepnote: New maintainer. office/ledger-live: Updated for version 4.13.0 office/nb: Updated for version 7.25.4. office/openoffice-langpack: Updated for version 4.1.16 office/pandoc-bin: Updated for version 3.10.1. office/qownnotes: Updated for version 26.7.10. office/texstudio: Update version to 4.9.6 office/vit: Updated for version 2.3.4. office/wordtsar: Add note to self. perl/MoarVM: Updated for version 2026.07. perl/nqp: Updated for version 2026.07. perl/perl-Audio-FLAC-Header: Orphaned (unmaintained). perl/perl-B-Hooks-EndOfScope: New maintainer. perl/perl-Bit-Vector: Updated for version 7.4. perl/perl-CPAN-Perl-Releases: Updated for version 5.20260703; new maintainer. perl/perl-Crypt-Eksblowfish: New maintainer. perl/perl-Data-Validate-IP: New maintainer. perl/perl-Devel-PatchPerl: Updated for version 2.14; new maintainer. perl/perl-File-pushd: noarch; new maintainer. perl/perl-GD: Updated for version 2.86. perl/perl-Gnome2-Vte: Updated for version 0.12. perl/perl-IO-Stty: Updated for version 0.08. perl/perl-IPC-Run3: New maintainer. perl/perl-MIME-Types: New maintainer. perl/perl-MP3-Info: Orphaned (unmaintained). perl/perl-Math-BigInt: New maintainer. perl/perl-Module-Pluggable: Updated for version 6.4. perl/perl-Net-IPv4Addr: New maintainer. perl/perl-Net-IPv6Addr: New maintainer. perl/perl-Net-Libdnet: Updated for version 0.99. perl/perl-Ogg-Vorbis-Header-PurePerl: Orphaned (unmaintained). perl/perl-Package-Stash-XS: Updated for version 0.30; new maintainer. perl/perl-Package-Stash: Updated for version 0.40; new maintainer. perl/perl-Pegex: Updated for version 0.75. perl/perl-Probe-Perl: New maintainer. perl/perl-Socket6: Updated for version 0.29. perl/perl-String-Random: Updated for version 0.32. perl/perl-Test-Class: New maintainer. perl/perl-Test-Spec: noarch; new maintainer. perl/perl-Test-TempDir-Tiny: Remove obsolete patch; new maintainer. perl/perl-Text-CSV: Updated for version 2.06 perl/perl-Text-CSV_XS: New maintainer. perl/perl-Tie-IxHash: noarch; new maintainer. perl/perl-Unicode-Map8: Orphaned (unmaintained). perl/perl-Unicode-String: Orphaned (unmaintained). perl/perl-WebService-MusicBrainz: New maintainer. perl/perl-html-form: Remove test. perl/perl-http-cookies: Updated for version 6.12. perl/perl-http-message: Updated for version 7.04. perl/perl-namespace-clean: New maintainer. perl/perlbrew: Updated for version 1.02; new maintainer. perl/rakudo: Updated for version 2026.07. python/PyStemmer: Removed (renamed python3-PyStemmer). python/alabaster: Removed (renamed python3-alabaster). python/hgsubversion: New maintainer. python/imagesize: Removed (renamed python3-imagesize). python/importlib-resources: Note reasons for not updating and fixes. python/pyelftools: Add note to self. python/pygsl: Updated for version 2.6.5. python/python2-pydns: New maintainer. python/python2-pypolicyd-spf: New maintainer. python/python2-pyspf: New maintainer. python/python3-attrs: Updated for version 26.1.0. python/python3-bitarray: Updated for version 3.9.2. python/python3-casttube: Added (YouTube Chromecast API). python/python3-cinemagoer: Version bump to 2026.06.27 python/python3-colorlog:Updated to version 6.12.0 python/python3-dep-logic: Version bump to 0.6.0 python/python3-fastjsonschema: Update README python/python3-lhafile: Updated for version 0.3.1 + new maintainer python/python3-msal: Version bump to 1.37.0 python/python3-odfdo: Updated for version 3.23.1 python/python3-pint: Add numpy 2.0 fix python/python3-prometheus_client: Update for 0.26.0 python/python3-proton-core: Added (Proton components core logic) python/python3-proton-vpn-api-core: Added (Proton VPN services API). python/python3-pychromecast: Added (python chromecast library). python/python3-sentry_sdk: Added (Error and performance monitoring). python/python3-typeguard: Update README about python3.9 support. python/snowballstemmer: Removed (renamed python3-snowballstemmer). system/Iosevka-aile: Updated for version 34.8.0. system/Iosevka-core: Updated for version 34.8.0 system/Iosevka-etoile: Updated for version 34.8.0. system/Iosevka-slab: Updated for version 34.8.0 system/Iosevka: Updated for version 34.8.0. system/Lmod: Updated for version 9.2.10. system/acefile: Updated for version 0.6.14. system/agedu: Updated for version 20260410.3622eda. system/apache-tomcat: Updated for version 10.1.57. system/audit: New maintainer. system/bottom: Updated for version 0.14.7. system/cbmbasic: Updated for version 1.0+20260403_3b9e48d. system/colorize: Updated for version 0.67. system/conspy: Updated for version 1.17. system/dar: Updated for version 2.8.5. system/doas: update system/dtach: New maintainer. system/elasticsearch: New maintainer. system/firmware-gobi-2000: New maintainer. system/fzf-bin:Updated to version 0.74.1 system/goaccess: Updated for version 1.11. system/grub2-splashimages:Updated to version 1.1.1 system/hwloc: Updated for version 2.14.0. system/ifuse: New maintainer. system/info2man: Fix download. system/irqbalance: Updated for version 1.9.5. system/isomd5sum: Tweak README. system/lf: update to r42 system/limine: Updated for version 12.5.2 system/lv: Updated for version 4.51_10. system/man-pages-ru: Fix homepage/download. system/mksh: Fix homepage. system/multipath-tools: New maintainer. system/nomarch: Fix download URL. system/numlockx: Use github download. system/open-vm-tools: Update script. system/oxker-bin: Updated for version 0.13.3 system/pause-nosignal: Added (Signal aware pause command). system/pdsh: update to 2.36 system/ph: New maintainer system/phpsysinfo: New maintainer. system/physlock: New maintainer. system/posh: Updated for version 0.14.5. system/postgresql: New maintainer. system/prometheus: Updated for version 3.13.2. system/pw: Upstream site now has CAPTCHA; I refuse. system/qtfm: update to 6.2.1 and new maintainer system/read-edid: Fix download. system/rename.pl: Updated for version 1.16.3. system/rmw: Update for version 0.10.0 system/roxterm: Updated for version 3.18.2. system/rsyslog: Updated for version 8.2606.0. system/rtirq: Updated for version 20240905_9945bcd. system/sbotest: Updated for version 1.2.3. system/sbotools: Updated for version 4.3; new SBO_HOME default. system/scdoc: Updated for version 1.11.5. system/seahorse: New maintainer. system/set_rlimits: Use working homepage. system/slim: Tweak README. system/stress-ng: update to 0.21.04 and new maintainer system/usermin: Updated for version 2.552. system/vagrant: New maintainer. system/ventoy: Removed unused patch file system/virt-viewer: New maintainer. system/vwm: Updated for version 4.9.6+20260709_8631057. system/webmin: Updated for version 2.653. system/wterm: Fix build on -current. system/xautolock: update system/yank: Updated for version 1.4.0. +--------------------------+ -- 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 Sat Aug 1 01:16:45 2026 From: urchlay at slackware.uk (B. Watson) Date: Fri, 31 Jul 2026 21:16:45 -0400 (EDT) Subject: [Slackbuilds-users] probably time to remove zotero-gtk2 In-Reply-To: <8089e339c0fb6cf385dd3cf5fa937732@komputermatrix.com> References: <8089e339c0fb6cf385dd3cf5fa937732@komputermatrix.com> Message-ID: <73dc97d9-731-2f2a-929f-9d3851c9d6d9@slackware.uk> On Fri, 31 Jul 2026, phalange at komputermatrix.com wrote: > I think this variant was created to accommodate users who postponed GTK3 > adoption, but Zotero long ago retired 4 (we're on 9.0.6). The build is > orphaned and IMO not of enough value to preserve. OK, removed, will be in next week's update. From urchlay at slackware.uk Sat Aug 1 07:05:17 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 1 Aug 2026 03:05:17 -0400 (EDT) Subject: [Slackbuilds-users] teighafileconverter Message-ID: <0e9d61-181-93b7-9ecc-868a2e1c04c@slackware.uk> Does anyone use teighafileconverter, or use AutoCAD or similar and need a utility like this to convert between .dwg and .dxf files? I have no idea why I took over maintenance of this (in 2018; who knows what I was thinking then?) but it's disappeared upstream, or perhaps been renamed to "ODA file converter". Would anyone like to take over this build? I've got too many and this one is useless to me... From urchlay at slackware.uk Sat Aug 1 21:59:00 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 1 Aug 2026 17:59:00 -0400 (EDT) Subject: [Slackbuilds-users] D Woodfall's remaining builds Message-ID: If anyone wants to take any of these over, please do. Anything not taken by Friday, August 7, will be orphaned. addrwatch (arp traffic montor) aiksaurus (CLI/GTK thesaurus) atheme (Atheme IRC Services) audioconvert (Audio Sync and Conversion Utility) calc (C-style arbitrary precision calculator) driconf (DRI Configuration Applet) farsight2 (Audio/Video Communications Framework) gcal (Gnu terminal calendar application) gofiche (fork of fiche, the termbin.com pastebin server) imwheel (a mouse wheel and stick interpreter for X Windows) ink (printer ink level monitor) libinklevel (library to check printer ink levels) libxlsxwriter (C library for creating Excel XLSX files) lomoco (Logitech Mouse Control for Linux) nas (Network Audio System) nspluginwrapper (proxy plugin) nweb (A tiny web server in C) oinkmaster (update and manage snort and suricata rules) perl-Algorithm-Combinatorics (generation of combinatorial sequences) perl-Algorithm-Loops (Looping constructs) perl-IO-Interface (access to network card configuration information) perl-Math-Prime-Util (Utilities related to prime numbers) perl-Math-Prime-Util-GMP (module for number theory in Perl using GMP) perl-Sidef (A modern object-oriented programming language) persepolis (Persepolis Download Manager is a GUI for aria2) powernowd (a cpu frequency daemon) pudb (A console-based Python debugger) pyNeighborhood (A windows share browser) pyPEG2 (plain and simple intrinsic parser interpreter for Python) python-urwid_readline (readline text edit for urwid) python2-demjson (Encoder, decoder, and lint/validator for JSON) python2-elementtree (Python library wrapper for XML) python2-morbid (messaging server) python2-stomper (client implementation of the STOMP protocol) python2-uuid (UUID object and generation functions) regionset (set dvd drive region) retrovol (Volume and mixer control for alsa) smstools3 (SMS Server Tools) tta (TTA lossless audio codec written in C) upass (Console UI for pass) xcfa (Powerful Audio Converter & Splitter for Linux) xforge (a graphical wave editor for UNIX systems with X11 and Motif) xonclock (a skinable X on-screen analog clock) From urchlay at slackware.uk Sat Aug 1 22:27:45 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 1 Aug 2026 18:27:45 -0400 (EDT) Subject: [Slackbuilds-users] portmidi about to update Message-ID: I'm about to update portmidi to v2.0.8. I've built everything against the new version and everything builds fine, but it would be good if the maintainers could check that everything runs correctly. If your build is listed here, you should check it against the new portmidi: https://slackbuilds.org/advsearch.php?stype=revdep&q=portmidi To get the new portmidi, check out my branch (urchlay), commit 11fc417c. From sbo at linuxgalaxy.org Sun Aug 2 00:47:55 2026 From: sbo at linuxgalaxy.org (KB_SBo) Date: Sun, 02 Aug 2026 00:47:55 +0000 Subject: [Slackbuilds-users] D Woodfall's remaining builds In-Reply-To: References: Message-ID: On 8/1/26 14:59, B. Watson wrote: > driconf (DRI Configuration Applet) I'll grab this one. -kb From urchlay at slackware.uk Sun Aug 2 00:54:57 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 1 Aug 2026 20:54:57 -0400 (EDT) Subject: [Slackbuilds-users] D Woodfall's remaining builds In-Reply-To: References: Message-ID: <61287ba-7139-ced0-71b9-7ecec18786@slackware.uk> On Sun, 2 Aug 2026, KB_SBo wrote: > On 8/1/26 14:59, B. Watson wrote: >> driconf (DRI Configuration Applet) > > I'll grab this one. It's yours, thanks. I tried it, and it didn't work for me ("count not detect any devices"), using the nvidia proprietary driver. IIRC you use AMD/ATI these days so you might have better luck. From sbo at linuxgalaxy.org Sun Aug 2 01:03:15 2026 From: sbo at linuxgalaxy.org (KB_SBo) Date: Sun, 02 Aug 2026 01:03:15 +0000 Subject: [Slackbuilds-users] Warning from openssh regarding key exchange Message-ID: Admins, When I 'git push' an update to the SBo git, this warning pops up: $ git push --set-upstream origin user/kingbeowulf/updates ** WARNING: connection is not using a post-quantum key exchange algorithm. ** This session may be vulnerable to "store now, decrypt later" attacks. ** The server may need to be upgraded. See https://openssh.com/pq.html I do not recall this warning last week or so. Slackware64-15.0 multilib and testing/graphics-updates openssh-10.4p1 -kb From sbo at linuxgalaxy.org Sun Aug 2 01:12:44 2026 From: sbo at linuxgalaxy.org (KB_SBo) Date: Sun, 02 Aug 2026 01:12:44 +0000 Subject: [Slackbuilds-users] dmg2img slackbuild Message-ID: Admins, Pablo is now new anointed maintainer of dmg2img. Long may he reign! -kb -------- Forwarded Message -------- Subject: dmg2img slackbuild Date: Wed, 29 Jul 2026 15:05:25 +0000 From: Pablo Romano Reply-To: Pablo Romano To: kingbeowulf at linuxgalaxy.org Hi Edward. The SlackBuild for dmg2img package does not work anymore, I've just made a new SlackBuild using ubuntu archive as source, it works without the need of a patch. I'm ready to upload it to slackbuilds.org but I need your permission to take over you as new mantainer. Thank You. From urchlay at slackware.uk Sun Aug 2 01:17:28 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 1 Aug 2026 21:17:28 -0400 (EDT) Subject: [Slackbuilds-users] txr Message-ID: Anyone ever even look at development/txr? It's a "pattern-based text extraction language", I thought I might use it, but I have too much inertia, and perl is too familiar. Anyone want it? From sbo at linuxgalaxy.org Sun Aug 2 01:30:59 2026 From: sbo at linuxgalaxy.org (KB_SBo) Date: Sun, 02 Aug 2026 01:30:59 +0000 Subject: [Slackbuilds-users] D Woodfall's remaining builds In-Reply-To: <61287ba-7139-ced0-71b9-7ecec18786@slackware.uk> References: <61287ba-7139-ced0-71b9-7ecec18786@slackware.uk> Message-ID: <87fe78cc-411a-499c-836b-8d248e432248@linuxgalaxy.org> On 8/1/26 17:54, B. Watson wrote: > > > On Sun, 2 Aug 2026, KB_SBo wrote: > >> On 8/1/26 14:59, B. Watson wrote: >>> driconf (DRI Configuration Applet) >> >> I'll grab this one. > > It's yours, thanks. > > I tried it, and it didn't work for me ("count not detect any > devices"), using the nvidia proprietary driver. IIRC you use AMD/ATI > these days so you might have better luck. I'll have to test some more, but it look like it has problems with newer radionsi and amdgpu as well. I may just replace it with the newer 'adriconf' -kb From willysr at slackbuilds.org Sun Aug 2 02:00:59 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 2 Aug 2026 09:00:59 +0700 Subject: [Slackbuilds-users] Warning from openssh regarding key exchange In-Reply-To: References: Message-ID: <20260802090059.47ce9976@home.slackie.org> >Admins, > >When I 'git push' an update to the SBo git, this warning pops up: > >$ git push --set-upstream origin user/kingbeowulf/updates >** WARNING: connection is not using a post-quantum key exchange algorithm. >** This session may be vulnerable to "store now, decrypt later" attacks. >** The server may need to be upgraded. See https://openssh.com/pq.html > >I do not recall this warning last week or so. > >Slackware64-15.0 multilib and testing/graphics-updates >openssh-10.4p1 you can ignore this warning it's part of openssh's warning which is harmless -- 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 fredg at zaclys.net Sun Aug 2 05:48:57 2026 From: fredg at zaclys.net (Fred. Galusik) Date: Sun, 2 Aug 2026 07:48:57 +0200 Subject: [Slackbuilds-users] D Woodfall's remaining builds In-Reply-To: References: Message-ID: Le samedi 01 ao?t 2026 ? 17:59 (-0400), B. Watson a ?crit : > > If anyone wants to take any of these over, please do. Anything not > taken by Friday, August 7, will be orphaned. > Hi, Those for me please: > calc (C-style arbitrary precision calculator) > nweb (A tiny web server in C) > pudb (A console-based Python debugger) Cheers, -fredg From fredg at zaclys.net Sun Aug 2 05:27:21 2026 From: fredg at zaclys.net (Fred. Galusik) Date: Sun, 2 Aug 2026 07:27:21 +0200 Subject: [Slackbuilds-users] txr In-Reply-To: References: Message-ID: Le samedi 01 ao?t 2026 ? 21:17 (-0400), B. Watson a ?crit : > > Anyone ever even look at development/txr? It's a "pattern-based text > extraction language", I thought I might use it, but I have too much > inertia, and perl is too familiar. > > Anyone want it? Hi, Sounds interesting. I can take it. Have a nice day :) -fredg From urchlay at slackware.uk Sun Aug 2 08:42:08 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 2 Aug 2026 04:42:08 -0400 (EDT) Subject: [Slackbuilds-users] D Woodfall's remaining builds In-Reply-To: References: Message-ID: <5db5e48b-db27-c472-a3ca-da918abf8a36@slackware.uk> On Sun, 2 Aug 2026, Fred. Galusik via SlackBuilds-users wrote: > Those for me please: >> calc (C-style arbitrary precision calculator) >> nweb (A tiny web server in C) >> pudb (A console-based Python debugger) Are you going to submit/push updates, or should I change the .info files in my git branch? Either way is good. From urchlay at slackware.uk Sun Aug 2 08:48:51 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 2 Aug 2026 04:48:51 -0400 (EDT) Subject: [Slackbuilds-users] txr In-Reply-To: References: Message-ID: <74c749d1-f8da-8914-383e-f8c3191f878b@slackware.uk> On Sun, 2 Aug 2026, Fred. Galusik via SlackBuilds-users wrote: > Sounds interesting. I can take it. Same question for you: should I update the .info file, or will you? From mm at dorfdsl.de Sun Aug 2 09:17:02 2026 From: mm at dorfdsl.de (Marco Moock) Date: Sun, 2 Aug 2026 11:17:02 +0200 Subject: [Slackbuilds-users] using archive.org download links In-Reply-To: References: <7604f2c1-0ba4-4f68-ade9-fad43e7a9584@dorfdsl.de> Message-ID: <245ab237-895e-4e76-8ca9-23abfc64d7ca@dorfdsl.de> Am 29.07.26 um 23:25 schrieb B. Watson: > > Usually what I do is use the archive.org link for HOMEPAGE, and > try to find another location for the download file(s)... like, > Debian or FreeBSD's archives. You can search for the package name on > repology.org to see if other distros package it. I noticed that archive.org unpacks gz archives if certain HTTP headers are not present in the HTTP client. I will look for another place. -- Gru? Marco Junk-Mail bitte an trashcan 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 urchlay at slackware.uk Sun Aug 2 09:27:56 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 2 Aug 2026 05:27:56 -0400 (EDT) Subject: [Slackbuilds-users] using archive.org download links In-Reply-To: <245ab237-895e-4e76-8ca9-23abfc64d7ca@dorfdsl.de> References: <7604f2c1-0ba4-4f68-ade9-fad43e7a9584@dorfdsl.de> <245ab237-895e-4e76-8ca9-23abfc64d7ca@dorfdsl.de> Message-ID: On Sun, 2 Aug 2026, Marco Moock wrote: > I noticed that archive.org unpacks gz archives if certain HTTP headers are > not present in the HTTP client. Yuck! > I will look for another place. If all else fails, you can ask on this list for your source(s) to be hosted on the slackbuildsdirectlinks sourceforge page. I can't remember who's in charge of that (Willy, maybe?) From mm at dorfdsl.de Sun Aug 2 09:43:47 2026 From: mm at dorfdsl.de (Marco Moock) Date: Sun, 2 Aug 2026 11:43:47 +0200 Subject: [Slackbuilds-users] request for hosting xskat sources Message-ID: <809c9868-c06b-4ce0-a9c2-54d104aa6099@dorfdsl.de> Hello! I am currently updating the xskat slackbuild. The upstream website does not exist anymore and web.archive.org modifies the tar.gz file in case wget is being used. Can it be hosted on the slackbuildsdirectlinks sourceforge page? https://web.archive.org/web/20220331112433/http://www.xskat.de/xskat-4.0.tar.gz md5 6744cea48a890771736b75083e7ea2b5 -- kind regards Marco Junk-Mail bitte an trashcan 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 willysr at slackbuilds.org Sun Aug 2 13:24:03 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 2 Aug 2026 20:24:03 +0700 Subject: [Slackbuilds-users] request for hosting xskat sources In-Reply-To: <809c9868-c06b-4ce0-a9c2-54d104aa6099@dorfdsl.de> References: <809c9868-c06b-4ce0-a9c2-54d104aa6099@dorfdsl.de> Message-ID: <20260802202403.505995f8@home.slackie.org> >Hello! > >I am currently updating the xskat slackbuild. The upstream website does >not exist anymore and web.archive.org modifies the tar.gz file in case >wget is being used. > >Can it be hosted on the slackbuildsdirectlinks sourceforge page? > >https://web.archive.org/web/20220331112433/http://www.xskat.de/xskat-4.0.tar.gz >md5 6744cea48a890771736b75083e7ea2b5 send us your SF username, and i will add you as devs there so you can upload yourself -- 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 Aug 2 22:43:28 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 2 Aug 2026 18:43:28 -0400 (EDT) Subject: [Slackbuilds-users] template find/chmod RFC Message-ID: RFC for new find/chmod in the SBo templates =========================================== Please respond to this, if you have any opinion at all (for or against the proposed change). The existing template code: ---------------------------------------------------------------------- find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ -o -perm 511 \) -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; ---------------------------------------------------------------------- The proposed replacement code: ---------------------------------------------------------------------- find . ! -type l -a \ \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) ---------------------------------------------------------------------- English translation: For all files or dirs under the current directory: ...if it's a symlink, ignore it completely. ...if any of the +x bits are set (owner group other), but the mode is not already 755, set the mode to 755 (-rwxr-xr-x). ...else, if no +x bits are set, but the mode is not already 644, set the mode to 644 (-rw-r--r--). ...else, the mode was already 644 or 755, so don't change anything. Explanation and notes: Because of the + in the -exec, the filenames are all passed as arguments to the same instance(s) of chmod, rather than executing a separate chmod for each file. This is faster and less resource-intensive: we only spawn 0, 1, or 2 chmod commands, no matter how many files need changing. We don't want to use -L (follow symlinks), because what if someone creates a tarball with a symlink to /etc/shadow or /root? The old template would 'chmod 644 /etc/shadow' or 'chmod 755 /root'! Using "! -type l" omits symlinks entirely, which makes more sense and is safer. Plus, symlinks' permissions aren't even used by the OS (or changeable); the permissions of the symlink *target* are used. The -f in the chmod command is probably redundant: it tells chmod to always return success status, even if it failed to change the permissions of one or more files. This is to avoid the script dying due to "set -e". In my experience, chmod when run as root normally only fails if it's passed a broken (dangling) symlink... which will not happen here because of the "! -type l". All the -a's are actually redundant: find assumes assumes -a (logical AND) by default. I left them in because I think it's more readable that way. Overall, I think this is more readable and easier to understand than the old template. This also is more reliable than the old template, which listed explicit permissions (-perm 777 -o -perm 775 -o -perm 750, etc) but the lists were incomplete. Files with mode 710, 510, 500, or 751 wouldn't get their permissions changed, for example. I've been using this new find/chmod template for my own SlackBuilds for about a year now, to test the waters, and I've had no problems. From zsd+slackbuilds at jdvb.ca Mon Aug 3 00:12:34 2026 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Sun, 2 Aug 2026 21:12:34 -0300 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: References: Message-ID: <20260803.001234.GA26979@x360.localdomain> On Sun, Aug 2, 2026 at 18:43 (-0400), B. Watson wrote: > RFC for new find/chmod in the SBo templates > =========================================== > Please respond to this, if you have any opinion at all (for or > against the proposed change). > The existing template code: > ---------------------------------------------------------------------- > find -L . \ > \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > -o -perm 511 \) -exec chmod 755 {} \; -o \ > \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; > ---------------------------------------------------------------------- I've long thought that code was a bit painful to read. FWIW, I support changing it. > The proposed replacement code: > ---------------------------------------------------------------------- > find . ! -type l -a \ > \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ > \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) > ---------------------------------------------------------------------- I know it is redundant to chmod a file to the perms it already has, but at the cost of a few redundant chmod operations, would the clarity gained by removing the " -a ! -perm 644 " clause (and the 755 one) be worth those extra few chmods? Jim From duncan_roe at optusnet.com.au Mon Aug 3 01:52:37 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Mon, 3 Aug 2026 11:52:37 +1000 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <20260803.001234.GA26979@x360.localdomain> References: <20260803.001234.GA26979@x360.localdomain> Message-ID: On Sun, Aug 02, 2026 at 09:12:34PM -0300, SlackBuilds wrote: > On Sun, Aug 2, 2026 at 18:43 (-0400), B. Watson wrote: > > > > RFC for new find/chmod in the SBo templates > > =========================================== > > > Please respond to this, if you have any opinion at all (for or > > against the proposed change). > > > The existing template code: > > > ---------------------------------------------------------------------- > > find -L . \ > > \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > > -o -perm 511 \) -exec chmod 755 {} \; -o \ > > \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > > -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; > > ---------------------------------------------------------------------- > > I've long thought that code was a bit painful to read. FWIW, I support > changing it. > > > The proposed replacement code: > > > ---------------------------------------------------------------------- > > find . ! -type l -a \ > > \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ > > \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) > > ---------------------------------------------------------------------- > > I know it is redundant to chmod a file to the perms it already has, but at > the cost of a few redundant chmod operations, would the clarity gained by > removing the " -a ! -perm 644 " clause (and the 755 one) be worth those > extra few chmods? > > Jim > I think either way is a lot better than what we have now. My preference is to avoid unnecessary writes to the file system, so I would leave it as originally proposed. Cheers ... Duncan. From urchlay at slackware.uk Mon Aug 3 01:53:30 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 2 Aug 2026 21:53:30 -0400 (EDT) Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <20260803.001234.GA26979@x360.localdomain> References: <20260803.001234.GA26979@x360.localdomain> Message-ID: <32f0c68-5c3f-f9e7-4310-e955b43494e@slackware.uk> On Sun, 2 Aug 2026, Jim via SlackBuilds-users wrote: >> ---------------------------------------------------------------------- >> find . ! -type l -a \ >> \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ >> \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) >> ---------------------------------------------------------------------- > > I know it is redundant to chmod a file to the perms it already has, but at > the cost of a few redundant chmod operations, would the clarity gained by > removing the " -a ! -perm 644 " clause (and the 755 one) be worth those > extra few chmods? It's not necessily a "few". If you have 10,000 files with correct permissions and only a few (or only one, or none at all) that need changing, your chmod commands will take 10,000 times as long as they need to. Part of my goal in changing the template is to avoid the long delay caused by the old find/chmod code. From elyk03 at gmail.com Mon Aug 3 05:26:54 2026 From: elyk03 at gmail.com (Kyle Guinn) Date: Mon, 3 Aug 2026 00:26:54 -0500 Subject: [Slackbuilds-users] Attn: R. S. Ananda Murthy In-Reply-To: <9b9f33d1-469c-4faa-90de-79e74b95eac6@slackware.uk> References: <7b2dee9-4b9a-e4d6-d934-52b0635e3c66@slackware.uk> <9114b491-9562-22d1-3a74-ec151648b7f3@slackware.uk> <65a3d404-71c4-4655-b6d1-37390ec59a63@app.fastmail.com> <549c6556-8e97-42db-9c9b-1687c2e190d1@app.fastmail.com> <9b9f33d1-469c-4faa-90de-79e74b95eac6@slackware.uk> Message-ID: If it's not too late to jump on the bandwagon, may I take smlnj off your hands? -Kyle On Mon, Jul 27, 2026 at 2:13?AM B. Watson wrote: > > > > On Sun, 26 Jul 2026, Nick Smallbone wrote: > > > I got the OK from Anand to take over mlton. B. Watson, please could you put me as maintainer in the .info file? > > Yep. Thanks for taking it. > _______________________________________________ > 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 dickson.tim at googlemail.com Mon Aug 3 10:10:45 2026 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 3 Aug 2026 11:10:45 +0100 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <32f0c68-5c3f-f9e7-4310-e955b43494e@slackware.uk> References: <20260803.001234.GA26979@x360.localdomain> <32f0c68-5c3f-f9e7-4310-e955b43494e@slackware.uk> Message-ID: great idea. anything script/code that is easier to read/understand and faster with no extra deps is a win in my book :-) thanks B. Watson From tonus1 at free.fr Mon Aug 3 10:51:13 2026 From: tonus1 at free.fr (Tonus) Date: Mon, 03 Aug 2026 12:51:13 +0200 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <32f0c68-5c3f-f9e7-4310-e955b43494e@slackware.uk> (B. Watson's message of "Sun, 2 Aug 2026 21:53:30 -0400 (EDT)") References: <20260803.001234.GA26979@x360.localdomain> <32f0c68-5c3f-f9e7-4310-e955b43494e@slackware.uk> Message-ID: <87jyq7lboe.fsf@Baldr.vingolf.info> "B. Watson" writes: > On Sun, 2 Aug 2026, Jim via SlackBuilds-users wrote: > >>> ---------------------------------------------------------------------- >>> find . ! -type l -a \ >>> \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ >>> \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) >>> ---------------------------------------------------------------------- >> >> I know it is redundant to chmod a file to the perms it already has, but at >> the cost of a few redundant chmod operations, would the clarity gained by >> removing the " -a ! -perm 644 " clause (and the 755 one) be worth those >> extra few chmods? > > It's not necessily a "few". If you have 10,000 files with correct > permissions and only a few (or only one, or none at all) that need > changing, your chmod commands will take 10,000 times as long as they > need to. > > Part of my goal in changing the template is to avoid the long delay > caused by the old find/chmod code. > _______________________________________________ > 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/ Great changes and very clear explanation. For the initial change, for the sake of technique and beauty ! Regards, -- Regards, Tonus. From rsamurti at gmail.com Mon Aug 3 11:21:04 2026 From: rsamurti at gmail.com (Ananda Murthy) Date: Mon, 3 Aug 2026 16:51:04 +0530 Subject: [Slackbuilds-users] Attn: R. S. Ananda Murthy In-Reply-To: References: <7b2dee9-4b9a-e4d6-d934-52b0635e3c66@slackware.uk> <9114b491-9562-22d1-3a74-ec151648b7f3@slackware.uk> <65a3d404-71c4-4655-b6d1-37390ec59a63@app.fastmail.com> <549c6556-8e97-42db-9c9b-1687c2e190d1@app.fastmail.com> <9b9f33d1-469c-4faa-90de-79e74b95eac6@slackware.uk> Message-ID: Of course you can! On Mon, Aug 3, 2026 at 10:57?AM Kyle Guinn wrote: > If it's not too late to jump on the bandwagon, may I take smlnj off your > hands? > > -Kyle > > On Mon, Jul 27, 2026 at 2:13?AM B. Watson wrote: > > > > > > > > On Sun, 26 Jul 2026, Nick Smallbone wrote: > > > > > I got the OK from Anand to take over mlton. B. Watson, please could > you put me as maintainer in the .info file? > > > > Yep. Thanks for taking it. > > _______________________________________________ > > 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/ > > > -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From tonus1 at free.fr Mon Aug 3 12:07:07 2026 From: tonus1 at free.fr (Tonus) Date: Mon, 03 Aug 2026 14:07:07 +0200 Subject: [Slackbuilds-users] OfflineIMAP Message-ID: <87ecgfl85w.fsf@Baldr.vingolf.info> Hi all Just noticed that OfflineIMAP was marked as orphaned. I took it since I use it every day, even if it's only in maintenance mode. Since it is replaced with a Python 3 version, I might submit a SlackBuild for this one. I could : - submit a new offlineimap-legacy and update offlineimap to Python 3 - submit a offlineimap3 What would be best ? -- Regards, Tonus. From slackbuilds at schoepfer.info Mon Aug 3 11:57:19 2026 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 03 Aug 2026 13:57:19 +0200 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: References: Message-ID: <3c567ed61afcd4136e595fc305656610@schoepfer.info> Am 2026-08-03 00:43, schrieb B. Watson: > RFC for new find/chmod in the SBo templates > =========================================== > > Please respond to this, if you have any opinion at all (for or > against the proposed change). > > The existing template code: > > ---------------------------------------------------------------------- > find -L . \ > \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > -o -perm 511 \) -exec chmod 755 {} \; -o \ > \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; > ---------------------------------------------------------------------- > > The proposed replacement code: > > ---------------------------------------------------------------------- > find . ! -type l -a \ > \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ > \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) > ---------------------------------------------------------------------- This is for sure an improvement! I personally like the following(already well known i think) solution the most, which i believe does the same. It's super fast and doesn't follow symlinks: chmod -R u+w,go-w,a+rX-st . From slackbuilds at schoepfer.info Mon Aug 3 12:31:36 2026 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 03 Aug 2026 14:31:36 +0200 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <3c567ed61afcd4136e595fc305656610@schoepfer.info> References: <3c567ed61afcd4136e595fc305656610@schoepfer.info> Message-ID: <823f2f0223fe42fdc90dc06c67d94726@schoepfer.info> > chmod -R u+w,go-w,a+rX-st . Here is an explanation why my proposal might not be that good. It's 13 years old, maybe chmod has changed to the better: https://unix.stackexchange.com/a/79874 From erich.public at protonmail.com Mon Aug 3 13:11:25 2026 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 03 Aug 2026 13:11:25 +0000 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: References: Message-ID: <3KvigM_5921aGEN7Gh4ES-ppkrhy23AHE4Sd8LnOu8IHJj-6tAtUdUPSBeCTEtE6dC4XuOmnHBlWhUO1vSZP0Ti8wRMs0nfW9CPYA5mBiEE=@protonmail.com> On Sunday, August 2nd, 2026 at 5:48 PM, B. Watson wrote: > > RFC for new find/chmod in the SBo templates > =========================================== > > Please respond to this, if you have any opinion at all (for or > against the proposed change). > > The existing template code: > > ---------------------------------------------------------------------- > find -L . \ > \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > -o -perm 511 \) -exec chmod 755 {} \; -o \ > \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; > ---------------------------------------------------------------------- > > The proposed replacement code: > > ---------------------------------------------------------------------- > find . ! -type l -a \ > \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ > \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) > ---------------------------------------------------------------------- > > English translation: > > For all files or dirs under the current directory: > > ...if it's a symlink, ignore it completely. > > ...if any of the +x bits are set (owner group other), but the mode > is not already 755, set the mode to 755 (-rwxr-xr-x). > > ...else, if no +x bits are set, but the mode is not already 644, > set the mode to 644 (-rw-r--r--). > > ...else, the mode was already 644 or 755, so don't change anything. > > Explanation and notes: > > Because of the + in the -exec, the filenames are all passed > as arguments to the same instance(s) of chmod, rather than > executing a separate chmod for each file. This is faster and less > resource-intensive: we only spawn 0, 1, or 2 chmod commands, no > matter how many files need changing. > > We don't want to use -L (follow symlinks), because what if someone > creates a tarball with a symlink to /etc/shadow or /root? The > old template would 'chmod 644 /etc/shadow' or 'chmod 755 /root'! > Using "! -type l" omits symlinks entirely, which makes more sense > and is safer. Plus, symlinks' permissions aren't even used by the OS > (or changeable); the permissions of the symlink *target* are used. > > The -f in the chmod command is probably redundant: it tells chmod > to always return success status, even if it failed to change the > permissions of one or more files. This is to avoid the script dying > due to "set -e". In my experience, chmod when run as root normally > only fails if it's passed a broken (dangling) symlink... which will > not happen here because of the "! -type l". > > All the -a's are actually redundant: find assumes assumes -a (logical > AND) by default. I left them in because I think it's more readable > that way. Overall, I think this is more readable and easier to > understand than the old template. > > This also is more reliable than the old template, which listed > explicit permissions (-perm 777 -o -perm 775 -o -perm 750, etc) > but the lists were incomplete. Files with mode 710, 510, 500, or 751 > wouldn't get their permissions changed, for example. > > I've been using this new find/chmod template for my own SlackBuilds > for about a year now, to test the waters, and I've had no problems. My only suggestion would be IF this change is made to also update all builds that exactly match the old style to the new style. From what I remember we are encouraged to use the templates in case changes like this are made then we can easily be updated to the new style. The assumption here is that if an existing build uses exactly the same lines in the template then the script maintainer is saying "I'm following the spirit of the template and just want done what the template is doing here" and therefore would want any improvements to the template applied. If an existing build does not exactly match the template, then that indicates a conscious effort on the script writer to deviate away from the template for some reason, and therefore a conscious effort must be applied (if desired) to update to the new style. Erich From mm at dorfdsl.de Mon Aug 3 13:41:56 2026 From: mm at dorfdsl.de (Marco Moock) Date: Mon, 3 Aug 2026 15:41:56 +0200 Subject: [Slackbuilds-users] OfflineIMAP In-Reply-To: <87ecgfl85w.fsf@Baldr.vingolf.info> References: <87ecgfl85w.fsf@Baldr.vingolf.info> Message-ID: <98e6ad64-2b21-4dd8-bfb5-bab114ff9f17@dorfdsl.de> Am 03.08.26 um 14:07 schrieb Tonus via SlackBuilds-users: > - submit a new offlineimap-legacy and update offlineimap to Python 3 Python 2 is EoL for a long time and 3 is widely available. Is there a reason to keep a version for 2? -- Gru? Marco Junk-Mail bitte an trashcan 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 matteo.bernardini at gmail.com Mon Aug 3 13:59:57 2026 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 3 Aug 2026 15:59:57 +0200 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <3KvigM_5921aGEN7Gh4ES-ppkrhy23AHE4Sd8LnOu8IHJj-6tAtUdUPSBeCTEtE6dC4XuOmnHBlWhUO1vSZP0Ti8wRMs0nfW9CPYA5mBiEE=@protonmail.com> References: <3KvigM_5921aGEN7Gh4ES-ppkrhy23AHE4Sd8LnOu8IHJj-6tAtUdUPSBeCTEtE6dC4XuOmnHBlWhUO1vSZP0Ti8wRMs0nfW9CPYA5mBiEE=@protonmail.com> Message-ID: Il giorno lun 3 ago 2026 alle ore 15:11 Erich Ritz via SlackBuilds-users < slackbuilds-users at slackbuilds.org> ha scritto: > On Sunday, August 2nd, 2026 at 5:48 PM, B. Watson > wrote: > > > > > RFC for new find/chmod in the SBo templates > > =========================================== > > > > Please respond to this, if you have any opinion at all (for or > > against the proposed change). > > > > The existing template code: > > > > ---------------------------------------------------------------------- > > find -L . \ > > \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > > -o -perm 511 \) -exec chmod 755 {} \; -o \ > > \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > > -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; > > ---------------------------------------------------------------------- > > > > The proposed replacement code: > > > > ---------------------------------------------------------------------- > > find . ! -type l -a \ > > \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ > > \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) > > ---------------------------------------------------------------------- > > > > English translation: > > > > For all files or dirs under the current directory: > > > > ...if it's a symlink, ignore it completely. > > > > ...if any of the +x bits are set (owner group other), but the mode > > is not already 755, set the mode to 755 (-rwxr-xr-x). > > > > ...else, if no +x bits are set, but the mode is not already 644, > > set the mode to 644 (-rw-r--r--). > > > > ...else, the mode was already 644 or 755, so don't change anything. > > > > Explanation and notes: > > > > Because of the + in the -exec, the filenames are all passed > > as arguments to the same instance(s) of chmod, rather than > > executing a separate chmod for each file. This is faster and less > > resource-intensive: we only spawn 0, 1, or 2 chmod commands, no > > matter how many files need changing. > > > > We don't want to use -L (follow symlinks), because what if someone > > creates a tarball with a symlink to /etc/shadow or /root? The > > old template would 'chmod 644 /etc/shadow' or 'chmod 755 /root'! > > Using "! -type l" omits symlinks entirely, which makes more sense > > and is safer. Plus, symlinks' permissions aren't even used by the OS > > (or changeable); the permissions of the symlink *target* are used. > > > > The -f in the chmod command is probably redundant: it tells chmod > > to always return success status, even if it failed to change the > > permissions of one or more files. This is to avoid the script dying > > due to "set -e". In my experience, chmod when run as root normally > > only fails if it's passed a broken (dangling) symlink... which will > > not happen here because of the "! -type l". > > > > All the -a's are actually redundant: find assumes assumes -a (logical > > AND) by default. I left them in because I think it's more readable > > that way. Overall, I think this is more readable and easier to > > understand than the old template. > > > > This also is more reliable than the old template, which listed > > explicit permissions (-perm 777 -o -perm 775 -o -perm 750, etc) > > but the lists were incomplete. Files with mode 710, 510, 500, or 751 > > wouldn't get their permissions changed, for example. > > > > I've been using this new find/chmod template for my own SlackBuilds > > for about a year now, to test the waters, and I've had no problems. > > My only suggestion would be IF this change is made to also update all > builds that exactly match the old style to the new style. From what I > remember we are encouraged to use the templates in case changes like this > are made then we can easily be updated to the new style. > > The assumption here is that if an existing build uses exactly the same > lines in the template then the script maintainer is saying "I'm following > the spirit of the template and just want done what the template is doing > here" and therefore would want any improvements to the template applied. > If an existing build does not exactly match the template, then that > indicates a conscious effort on the script writer to deviate away from the > template for some reason, and therefore a conscious effort must be applied > (if desired) to update to the new style. > > Erich if we decide to intervene on all the scripts we shouldn't do massive changes like this during the normal update cycle or we break every existing fork (like mine, for example). the moment to intervene in this cleanly is when we move to a different version of Slackware and submissions are closed and external branches merged: only then we should also adapt existing scripts to eventual new templates, not before. Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From tonus1 at free.fr Mon Aug 3 14:21:27 2026 From: tonus1 at free.fr (Tonus) Date: Mon, 03 Aug 2026 16:21:27 +0200 Subject: [Slackbuilds-users] OfflineIMAP In-Reply-To: <98e6ad64-2b21-4dd8-bfb5-bab114ff9f17@dorfdsl.de> (Marco Moock's message of "Mon, 3 Aug 2026 15:41:56 +0200") References: <87ecgfl85w.fsf@Baldr.vingolf.info> <98e6ad64-2b21-4dd8-bfb5-bab114ff9f17@dorfdsl.de> Message-ID: <878q6nl1y0.fsf@Baldr.vingolf.info> Marco Moock writes: > Am 03.08.26 um 14:07 schrieb Tonus via SlackBuilds-users: >> - submit a new offlineimap-legacy and update offlineimap to Python 3 > > Python 2 is EoL for a long time and 3 is widely available. > > Is there a reason to keep a version for 2? There's a new compile dependency for python3-setuptools-opt at least. Whatever the naming, the Python 2 SlackBuild could be dropped at next Slackware release. -- Regards, Tonus. From zsd+slackbuilds at jdvb.ca Mon Aug 3 15:25:42 2026 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Mon, 3 Aug 2026 12:25:42 -0300 Subject: [Slackbuilds-users] template find/chmod RFC Message-ID: <20260803.152542.GC13439@x360.localdomain> On Sun, Aug 2, 2026 at 21:53 (-0400), B. Watson wrote: > On Sun, 2 Aug 2026, Jim via SlackBuilds-users wrote: >>> ---------------------------------------------------------------------- >>> find . ! -type l -a \ >>> \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ >>> \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) >>> ---------------------------------------------------------------------- >> I know it is redundant to chmod a file to the perms it already has, but at >> the cost of a few redundant chmod operations, would the clarity gained by >> removing the " -a ! -perm 644 " clause (and the 755 one) be worth those >> extra few chmods? > It's not necessily a "few". If you have 10,000 files with correct > permissions and only a few (or only one, or none at all) that need > changing, your chmod commands will take 10,000 times as long as they > need to. That's a big package. Of the 512 (huh!) SBos I have on my system, the average number of lines in /var/log/packages/ is 384.xxx. (And that includes the blurb at the top.) > Part of my goal in changing the template is to avoid the long delay > caused by the old find/chmod code. My biggest SBo is qt6-6.8.3 (wc of /var/log/packages/qt6-6.8.3-x86_64-2_SBo gives 18299). After untarring it into a scratch directory, I ran time find . ! -type l -a \( -perm /111 -a -exec chmod -f 755 {} + \) -o \( ! -perm /111 -a -exec chmod -f 644 {} + \) which reported .06s user 0.23s system 99% cpu 0.285 total This is on a 6 year old laptop (with a Ryzen 4700U CPU). I don't really think that amount of time is significant (especially in light of the fact that compiling Qt6 took hours), but YMMV. Anyway, you asked for "any opinion at all", and so I gave it. If you want to keep the optimizing test, that's fine. But I don't think it is much of a time saver. Cheers. Jim From zsd+slackbuilds at jdvb.ca Mon Aug 3 15:47:44 2026 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Mon, 3 Aug 2026 12:47:44 -0300 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <823f2f0223fe42fdc90dc06c67d94726@schoepfer.info> References: <3c567ed61afcd4136e595fc305656610@schoepfer.info> <823f2f0223fe42fdc90dc06c67d94726@schoepfer.info> Message-ID: <20260803.154744.GE13439@x360.localdomain> On Mon, Aug 3, 2026 at 14:31 (+0200), Franzen via SlackBuilds-users wrote: >> chmod -R u+w,go-w,a+rX-st . > Here is an explanation why my proposal might not be that good. It's 13 years > old, maybe chmod has changed to the better: > https://unix.stackexchange.com/a/79874 Since I already timed the other replacement options, here is that one as well (again, on qt6-6.8.3-x86_64-2_SBo.tgz, where find . | wc -l outputs 18282, which is a lot of files and directories). $ time find . ! -type l -a \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) 0.03s user 0.06s system 99% cpu 0.086 total $ time find . ! -type l -a \( -perm /111 -a -exec chmod -f 755 {} + \) -o \( ! -perm /111 -a -exec chmod -f 644 {} + \) 0.07s user 0.22s system 99% cpu 0.285 total $ time chmod -R u+w,go-w,a+rX-st . 0.03s user 0.21s system 99% cpu 0.244 total Certainly the one with ! -perm is the fastest. Whether brevity is worth two tenths of a second or not is probably a personal opinion. Cheers. Jim From andrzej at telszewski.com Mon Aug 3 17:52:27 2026 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Mon, 3 Aug 2026 19:52:27 +0200 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <823f2f0223fe42fdc90dc06c67d94726@schoepfer.info> References: <3c567ed61afcd4136e595fc305656610@schoepfer.info> <823f2f0223fe42fdc90dc06c67d94726@schoepfer.info> Message-ID: <135d225f-7807-4543-aa66-679e086a6eb6@telszewski.com> On 03/08/2026 14:31, Franzen via SlackBuilds-users wrote: > >> chmod -R u+w,go-w,a+rX-st . > > Here is an explanation why my proposal might not be that good. It's 13 > years old, maybe chmod has changed to the better: > https://unix.stackexchange.com/a/79874 Unless enforced by SBo rules, I'll prefer `chmod -R` variant over `find` variant, for its compactness. Now, it's not strictly important how much time changing the permissions takes, but how much time does it take compared to the build time as a whole. -- Best regards, Andrzej Telszewski From rizitis at gmail.com Mon Aug 3 18:34:18 2026 From: rizitis at gmail.com (Yiannis) Date: Mon, 3 Aug 2026 21:34:18 +0300 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <135d225f-7807-4543-aa66-679e086a6eb6@telszewski.com> References: <3c567ed61afcd4136e595fc305656610@schoepfer.info> <823f2f0223fe42fdc90dc06c67d94726@schoepfer.info> <135d225f-7807-4543-aa66-679e086a6eb6@telszewski.com> Message-ID: One small thing before someday it becomes a template. As written: find . ! -type l -a \ \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) -a binds tighter than -o, so this parses as ( ! -type l AND first-group ) OR ( second-group ) and the "! -type l" never applies to the second branch. It is still safe on Linux, but incidentally rather than by design: the kernel forces mode 0777 on symlinks (umask is ignored, there is no lchmod, and even tar cannot restore a different mode), so "! -perm /111" is false for them and the 644 branch never fires. That is a property of Linux symlink modes, not of the guard - and it stops being true on an NFS or FUSE mount from a host where symlinks do carry real modes. One outer group fixes it: find . ! -type l -a \( \ \( -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) \ \) Same behaviour, same timing, two extra characters - but now the code stays more correct if either branch is ever edited. ???? ??? 3 ??? 2026 ???? 8:52??.?., ?/? Andrzej Telszewski < andrzej at telszewski.com> ??????: > On 03/08/2026 14:31, Franzen via SlackBuilds-users wrote: > > > >> chmod -R u+w,go-w,a+rX-st . > > > > Here is an explanation why my proposal might not be that good. It's 13 > > years old, maybe chmod has changed to the better: > > https://unix.stackexchange.com/a/79874 > > Unless enforced by SBo rules, I'll prefer `chmod -R` variant over `find` > variant, > for its compactness. > > Now, it's not strictly important how much time changing the permissions > takes, > but how much time does it take compared to the build time as a whole. > > -- > Best regards, > Andrzej Telszewski > > _______________________________________________ > 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 jebrhansen+SBo at gmail.com Mon Aug 3 18:38:36 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Mon, 3 Aug 2026 11:38:36 -0700 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <20260803.154744.GE13439@x360.localdomain> References: <3c567ed61afcd4136e595fc305656610@schoepfer.info> <823f2f0223fe42fdc90dc06c67d94726@schoepfer.info> <20260803.154744.GE13439@x360.localdomain> Message-ID: On Mon, Aug 3, 2026, 8:47?AM Jim via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > On Mon, Aug 3, 2026 at 14:31 (+0200), Franzen via SlackBuilds-users wrote: > > >> chmod -R u+w,go-w,a+rX-st . > > > Here is an explanation why my proposal might not be that good. It's 13 > years > > old, maybe chmod has changed to the better: > > https://unix.stackexchange.com/a/79874 > > Since I already timed the other replacement options, here is that one as > well (again, on qt6-6.8.3-x86_64-2_SBo.tgz, where find . | wc -l > outputs 18282, which is a lot of files and directories). > > $ time find . ! -type l -a \( -perm /111 -a ! -perm 755 -a -exec chmod -f > 755 {} + \) -o \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) > 0.03s user 0.06s system 99% cpu 0.086 total > > $ time find . ! -type l -a \( -perm /111 -a -exec chmod -f 755 {} + \) -o > \( ! -perm /111 -a -exec chmod -f 644 {} + \) > 0.07s user 0.22s system 99% cpu 0.285 total > > $ time chmod -R u+w,go-w,a+rX-st . > 0.03s user 0.21s system 99% cpu 0.244 total > > Certainly the one with ! -perm is the fastest. Whether brevity is worth > two tenths of a second or not is probably a personal opinion. > I'm not sure why you're seeing such a minimal amount of time with the original command. That's always been a bottleneck when compiling SlackBuilds between the visible extraction and the visible compilation. It just sits there on big builds while find does its thing silently. I just tested my Kodi SlackBuild by adding time in front of the find command and that took: real 0m15.603s user 0m10.402s sys 0m5.215s The chmod was incredibly fast: real 0m0.076s user 0m0.003s sys 0m0.073s As was the new find: real 0m0.079s user 0m0.016s sys 0m0.062s The amount of files in the Kodi source is around 33% smaller compared to your qt6 example: jbhansen at craven-moorhead:~/sbo-git/multimedia/kodi$ find /tmp/SBo/xbmc-21.3-Omega/ | wc -l 11697 This is all done on a Ryzen 9 5950X with a 2TB Samsung 980 Pro NVMe and 64GB of RAM. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Mon Aug 3 21:09:02 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 3 Aug 2026 17:09:02 -0400 (EDT) Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <3KvigM_5921aGEN7Gh4ES-ppkrhy23AHE4Sd8LnOu8IHJj-6tAtUdUPSBeCTEtE6dC4XuOmnHBlWhUO1vSZP0Ti8wRMs0nfW9CPYA5mBiEE=@protonmail.com> References: <3KvigM_5921aGEN7Gh4ES-ppkrhy23AHE4Sd8LnOu8IHJj-6tAtUdUPSBeCTEtE6dC4XuOmnHBlWhUO1vSZP0Ti8wRMs0nfW9CPYA5mBiEE=@protonmail.com> Message-ID: On Mon, 3 Aug 2026, Erich Ritz via SlackBuilds-users wrote: > My only suggestion would be IF this change is made to also update all builds that exactly match the old style to the new style. From what I remember we are encouraged to use the templates in case changes like this are made then we can easily be updated to the new style. That's something we'd do during a "development cycle", which is what we call the time when submissions are closed following a Slackware release. During the dev cycle, we don't do site updates, which means that changing several hundred (or thousand) builds in one commit is allowed. Normally we avoid this because of the overhead of generating the site tarballs and their GPG signatures. Until then, maintainers are free to update their builds to use the new template, but doing a bunch of updates *just* to change the template (for builds that already work) isn't something we're expecting everyone to do. You can if you want to, of course. > The assumption here is that if an existing build uses exactly the same lines in the template then the script maintainer is saying "I'm following the spirit of the template and just want done what the template is doing here" and therefore would want any improvements to the template applied. If an existing build does not exactly match the template, then that indicates a conscious effort on the script writer to deviate away from the template for some reason, and therefore a conscious effort must be applied (if desired) to update to the new style. Yes. If the script doesn't match the template, there's probably a good reason for it. Unfortunately, for whatever reason, explanatory comments in code have gone out of style... so we're left wondering "does this deviate for a reason? Is it a reason that still applies after a version update?" Example from odamex: # Every file in 0.9.5 is +x, and none of them need to be! # Do not revert to template. find . -type f -exec chmod 644 {} \+ find . -type d -exec chmod 755 {} \+ I've always believed comments shouldn't say *what* the code does (since the code already says it), they should say *why* the code does what it does. From antonioleal at yahoo.com Mon Aug 3 20:25:54 2026 From: antonioleal at yahoo.com (Antonio Leal) Date: Mon, 3 Aug 2026 21:25:54 +0100 Subject: [Slackbuilds-users] package rename References: Message-ID: Hello Admins Google has change the names of their antigravity packages. I want also realign the 2 SlackBuilds to the new names. Should I do it with a PR or through the site? tks - Ant?nio From urchlay at slackware.uk Mon Aug 3 21:40:38 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 3 Aug 2026 17:40:38 -0400 (EDT) Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <135d225f-7807-4543-aa66-679e086a6eb6@telszewski.com> References: <3c567ed61afcd4136e595fc305656610@schoepfer.info> <823f2f0223fe42fdc90dc06c67d94726@schoepfer.info> <135d225f-7807-4543-aa66-679e086a6eb6@telszewski.com> Message-ID: <3e8cf22-aa98-48c8-6bfa-ff01fa897@slackware.uk> On Mon, 3 Aug 2026, Andrzej Telszewski wrote: > Unless enforced by SBo rules, I'll prefer `chmod -R` variant over `find` > variant, > for its compactness. We're not going to force you to follow the template. We might like it if you'd put a comment, like maybe: # This is simpler than using find/chmod: From urchlay at slackware.uk Mon Aug 3 21:45:02 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 3 Aug 2026 17:45:02 -0400 (EDT) Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: References: <3c567ed61afcd4136e595fc305656610@schoepfer.info> <823f2f0223fe42fdc90dc06c67d94726@schoepfer.info> <135d225f-7807-4543-aa66-679e086a6eb6@telszewski.com> Message-ID: <458da26-2cf3-839e-68c1-2a77e4d4102c@slackware.uk> On Mon, 3 Aug 2026, Yiannis wrote: > One outer group fixes it: > > ? find . ! -type l -a \( \ > ? ? \( ? -perm /111 -a ! -perm 755 -a -exec chmod -f 755 {} + \) -o \ > ? ? \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) \ > ? \) > > Same behaviour, same timing, two extra characters - but now the code stays more correct if either branch > is ever edited. Nice catch! You're absolutely right, and I'm going to replace my original code with your version (well, test it first, of course, but it looks obviously correct to me). From milgram at cgpp.com Mon Aug 3 22:12:25 2026 From: milgram at cgpp.com (J. Milgram) Date: Mon, 3 Aug 2026 18:12:25 -0400 Subject: [Slackbuilds-users] jpilot category In-Reply-To: <20260731084558.6f0abc07@office64.slackie.org> References: <90c2f541-ca55-42ed-839e-1d3e97b15cf6@cgpp.com> <20260731084558.6f0abc07@office64.slackie.org> Message-ID: <4537ecd0-a0c3-4f61-9569-b193a4c234ce@cgpp.com> Thank you! JM On 7/30/26 21:46, Willy Sudiarto Raharjo wrote: >> I see my updated jpilot package in the ready queue. Thanks. >> >> I wanted to upload it marked as category "office" but see it in the >> queue as "accessibility."? Perhaps I got? sloppy with the form when I >> submitted it, or maybe there's some subtlety about changing categories >> that? I'm not aware of. >> >> In any event, the consensus on the jpilot list is that it's definitely >> "office." I? wonder how it ever got binned as "accessibility" in the >> first place (would? have been? years ago) but no matter. >> >> Can we change it to "office"? > > let me see if i can move it for this week's public update > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -- ===== milgram at cgpp.com 301-257-7069 From duncan_roe at optusnet.com.au Tue Aug 4 00:04:42 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Tue, 4 Aug 2026 10:04:42 +1000 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: References: <3KvigM_5921aGEN7Gh4ES-ppkrhy23AHE4Sd8LnOu8IHJj-6tAtUdUPSBeCTEtE6dC4XuOmnHBlWhUO1vSZP0Ti8wRMs0nfW9CPYA5mBiEE=@protonmail.com> Message-ID: On Mon, Aug 03, 2026 at 05:09:02PM -0400, B. Watson wrote: > > I've always believed comments shouldn't say *what* the code does > (since the code already says it), they should say *why* the code does > what it does. Excellent! My feelings exactly, Cheers ... Duncan. From willysr at slackbuilds.org Tue Aug 4 01:18:35 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 4 Aug 2026 08:18:35 +0700 Subject: [Slackbuilds-users] package rename In-Reply-To: References: Message-ID: <20260804081835.7a583825@office64.slackie.org> >Hello Admins > >Google has change the names of their antigravity packages. I want also >realign the 2 SlackBuilds to the new names. > >Should I do it with a PR or through the site? you need to do it via submission site once approved, you can ask for removal for the old one or you can just mention it on the README or just simply make a symlink without making changes this way, users do not need to install new script and remove the old one That's what i did with letsencrypt which upstream rename it to certbot To provide compatibility, i just made a symlink letsencrypt to certbot every scripts used to renew certs no longer needed to be replaced -- 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 jim at jdvb.ca Tue Aug 4 01:50:27 2026 From: jim at jdvb.ca (Jim Diamond) Date: Mon, 3 Aug 2026 22:50:27 -0300 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: References: <3c567ed61afcd4136e595fc305656610@schoepfer.info> <823f2f0223fe42fdc90dc06c67d94726@schoepfer.info> <20260803.154744.GE13439@x360.localdomain> Message-ID: <20260804.015027.GA14339@x360.localdomain> ZOn Mon, Aug 3, 2026 at 11:38 (-0700), Jeremy Hansen wrote: > On Mon, Aug 3, 2026, 8:47?AM Jim via SlackBuilds-users < > slackbuilds-users at slackbuilds.org> wrote: >> On Mon, Aug 3, 2026 at 14:31 (+0200), Franzen via SlackBuilds-users wrote: >>>> chmod -R u+w,go-w,a+rX-st . >>> Here is an explanation why my proposal might not be that good. It's 13 >> years >>> old, maybe chmod has changed to the better: >>> https://unix.stackexchange.com/a/79874 >> Since I already timed the other replacement options, here is that one as >> well (again, on qt6-6.8.3-x86_64-2_SBo.tgz, where find . | wc -l >> outputs 18282, which is a lot of files and directories). >> $ time find . ! -type l -a \( -perm /111 -a ! -perm 755 -a -exec chmod -f >> 755 {} + \) -o \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) >> 0.03s user 0.06s system 99% cpu 0.086 total >> $ time find . ! -type l -a \( -perm /111 -a -exec chmod -f 755 {} + \) -o >> \( ! -perm /111 -a -exec chmod -f 644 {} + \) >> 0.07s user 0.22s system 99% cpu 0.285 total >> $ time chmod -R u+w,go-w,a+rX-st . >> 0.03s user 0.21s system 99% cpu 0.244 total >> Certainly the one with ! -perm is the fastest. Whether brevity is worth >> two tenths of a second or not is probably a personal opinion. > I'm not sure why you're seeing such a minimal amount of time with the > original command. Me neither (but see below). > That's always been a bottleneck when compiling SlackBuilds between the > visible extraction and the visible compilation. It just sits there on big > builds while find does its thing silently. I can't say I've noticed that, but often I let a SlackBuild chug away in one window and look at something else. The next time I build something I'll have to see if thee is something weird about my tests today. > I just tested my Kodi SlackBuild by adding time in front of the find > command and that took: > real 0m15.603s > user 0m10.402s > sys 0m5.215s That seems very slow, especially in light of the machine you describe below. Astonishing, in fact. Given that the find comes right after untarring and chowning, I would think that all of the directory structure should be cached in pages lounging around in your 64 GB memory, unless you have a bunch of VMs running which have been allocated 60 or 62 GB of your RAM. > The chmod was incredibly fast: > real 0m0.076s > user 0m0.003s > sys 0m0.073s > As was the new find: > real 0m0.079s > user 0m0.016s > sys 0m0.062s Did you run the old stinky find again just to see how it went on second try? > The amount of files in the Kodi source is around 33% smaller compared to > your qt6 example: > jbhansen at craven-moorhead:~/sbo-git/multimedia/kodi$ find > /tmp/SBo/xbmc-21.3-Omega/ | wc -l > 11697 > This is all done on a Ryzen 9 5950X with a 2TB Samsung 980 Pro NVMe and > 64GB of RAM. If I had a desktop I'd probably have major hardware jealousy at this point. :-) Jim From zsd+slackbuilds at jdvb.ca Tue Aug 4 02:01:27 2026 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Mon, 3 Aug 2026 23:01:27 -0300 Subject: [Slackbuilds-users] template find/chmod RFC Message-ID: <20260804.020127.GC14339@x360.localdomain> On Mon, Aug 3, 2026 at 11:38 (-0700), Jeremy Hansen wrote: > On Mon, Aug 3, 2026, 8:47?AM Jim via SlackBuilds-users < > slackbuilds-users at slackbuilds.org> wrote: >> On Mon, Aug 3, 2026 at 14:31 (+0200), Franzen via SlackBuilds-users wrote: >>>> chmod -R u+w,go-w,a+rX-st . >>> Here is an explanation why my proposal might not be that good. It's 13 >> years >>> old, maybe chmod has changed to the better: >>> https://unix.stackexchange.com/a/79874 >> Since I already timed the other replacement options, here is that one as >> well (again, on qt6-6.8.3-x86_64-2_SBo.tgz, where find . | wc -l >> outputs 18282, which is a lot of files and directories). >> $ time find . ! -type l -a \( -perm /111 -a ! -perm 755 -a -exec chmod -f >> 755 {} + \) -o \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} + \) >> 0.03s user 0.06s system 99% cpu 0.086 total >> $ time find . ! -type l -a \( -perm /111 -a -exec chmod -f 755 {} + \) -o >> \( ! -perm /111 -a -exec chmod -f 644 {} + \) >> 0.07s user 0.22s system 99% cpu 0.285 total >> $ time chmod -R u+w,go-w,a+rX-st . >> 0.03s user 0.21s system 99% cpu 0.244 total >> Certainly the one with ! -perm is the fastest. Whether brevity is worth >> two tenths of a second or not is probably a personal opinion. > I'm not sure why you're seeing such a minimal amount of time with the > original command. Me neither (but see below). > That's always been a bottleneck when compiling SlackBuilds between the > visible extraction and the visible compilation. It just sits there on big > builds while find does its thing silently. I can't say I've noticed that, but often I let a SlackBuild chug away in one window and look at something else. The next time I build something I'll have to see if thee is something weird about my tests today. > I just tested my Kodi SlackBuild by adding time in front of the find > command and that took: > real 0m15.603s > user 0m10.402s > sys 0m5.215s That seems very slow, especially in light of the machine you describe below. Astonishing, in fact. Given that the find comes right after untarring and chowning, I would think that all of the directory structure should be cached in pages lounging around in your 64 GB memory, unless you have a bunch of VMs running which have been allocated 60 or 62 GB of your RAM. > The chmod was incredibly fast: > real 0m0.076s > user 0m0.003s > sys 0m0.073s > As was the new find: > real 0m0.079s > user 0m0.016s > sys 0m0.062s Did you run the old stinky find again just to see how it went on second try? > The amount of files in the Kodi source is around 33% smaller compared to > your qt6 example: > jbhansen at craven-moorhead:~/sbo-git/multimedia/kodi$ find > /tmp/SBo/xbmc-21.3-Omega/ | wc -l > 11697 > This is all done on a Ryzen 9 5950X with a 2TB Samsung 980 Pro NVMe and > 64GB of RAM. If I had a desktop I'd probably have major hardware jealousy at this point. :-) Jim From jebrhansen+SBo at gmail.com Tue Aug 4 02:26:13 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Mon, 3 Aug 2026 19:26:13 -0700 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <20260804.020127.GC14339@x360.localdomain> References: <20260804.020127.GC14339@x360.localdomain> Message-ID: On Mon, Aug 3, 2026, 7:01?PM Jim via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > On Mon, Aug 3, 2026 at 11:38 (-0700), Jeremy Hansen wrote: > > > On Mon, Aug 3, 2026, 8:47?AM Jim via SlackBuilds-users < > > slackbuilds-users at slackbuilds.org> wrote: > > >> On Mon, Aug 3, 2026 at 14:31 (+0200), Franzen via SlackBuilds-users > wrote: > > >>>> chmod -R u+w,go-w,a+rX-st . > > >>> Here is an explanation why my proposal might not be that good. It's 13 > >> years > >>> old, maybe chmod has changed to the better: > >>> https://unix.stackexchange.com/a/79874 > > >> Since I already timed the other replacement options, here is that one as > >> well (again, on qt6-6.8.3-x86_64-2_SBo.tgz, where find . | wc -l > >> outputs 18282, which is a lot of files and directories). > > >> $ time find . ! -type l -a \( -perm /111 -a ! -perm 755 -a -exec chmod > -f > >> 755 {} + \) -o \( ! -perm /111 -a ! -perm 644 -a -exec chmod -f 644 {} > + \) > >> 0.03s user 0.06s system 99% cpu 0.086 total > > >> $ time find . ! -type l -a \( -perm /111 -a -exec chmod -f 755 {} + \) > -o > >> \( ! -perm /111 -a -exec chmod -f 644 {} + \) > >> 0.07s user 0.22s system 99% cpu 0.285 total > > >> $ time chmod -R u+w,go-w,a+rX-st . > >> 0.03s user 0.21s system 99% cpu 0.244 total > > >> Certainly the one with ! -perm is the fastest. Whether brevity is worth > >> two tenths of a second or not is probably a personal opinion. > > > I'm not sure why you're seeing such a minimal amount of time with the > > original command. > > Me neither (but see below). > > > That's always been a bottleneck when compiling SlackBuilds between the > > visible extraction and the visible compilation. It just sits there on big > > builds while find does its thing silently. > > I can't say I've noticed that, but often I let a SlackBuild chug away in > one window and look at something else. The next time I build something > I'll have to see if thee is something weird about my tests today. > > > I just tested my Kodi SlackBuild by adding time in front of the find > > command and that took: > > > real 0m15.603s > > user 0m10.402s > > sys 0m5.215s > > That seems very slow, especially in light of the machine you describe > below. > > Astonishing, in fact. Given that the find comes right after untarring and > chowning, I would think that all of the directory structure should be > cached in pages lounging around in your 64 GB memory, unless you have a > bunch of VMs running which have been allocated 60 or 62 GB of your RAM. > I have no VMs and only 3 relatively small containers running. Only using about 5GB total. jbhansen at craven-moorhead:~/sbo-git/multimedia/kodi$ free -h total used free shared buff/cache available Mem: 62Gi 4.8Gi 1.8Gi 112Mi 56Gi 57Gi Swap: 15Gi 1.1Gi 14Gi > The chmod was incredibly fast: > > > real 0m0.076s > > user 0m0.003s > > sys 0m0.073s > > > As was the new find: > > > real 0m0.079s > > user 0m0.016s > > sys 0m0.062s > > Did you run the old stinky find again just to see how it went on second > try? > Just tried it again. Left the chmod initially and then commented that out and uncommented the original find with time in front of it and reran the SlackBuild. It resulted in similar times: real 0m15.079s user 0m9.920s sys 0m5.185s > The amount of files in the Kodi source is around 33% smaller compared to > > your qt6 example: > > > jbhansen at craven-moorhead:~/sbo-git/multimedia/kodi$ find > > /tmp/SBo/xbmc-21.3-Omega/ | wc -l > > 11697 > > > This is all done on a Ryzen 9 5950X with a 2TB Samsung 980 Pro NVMe and > > 64GB of RAM. > > If I had a desktop I'd probably have major hardware jealousy at this > point. :-) I've definitely been lucky, but I tend to buy big and then wait a long time before replacing. I'm hoping to get close to a decade with this set up. -------------- next part -------------- An HTML attachment was scrubbed... URL: From list+sbo at vahedi.org Mon Aug 3 15:29:04 2026 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Mon, 03 Aug 2026 15:29:04 +0000 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: References: Message-ID: <7b78a8321f2c3cfc972a97124b6684c8bcf56561@vahedi.org> This definitely looks better. Just as a reminder though: it's not POSIX. -Shahab From urchlay at slackware.uk Tue Aug 4 04:21:26 2026 From: urchlay at slackware.uk (B. Watson) Date: Tue, 4 Aug 2026 00:21:26 -0400 (EDT) Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: <7b78a8321f2c3cfc972a97124b6684c8bcf56561@vahedi.org> References: <7b78a8321f2c3cfc972a97124b6684c8bcf56561@vahedi.org> Message-ID: On Mon, 3 Aug 2026, Shahab Vahedi via SlackBuilds-users wrote: > This definitely looks better. > Just as a reminder though: it's not POSIX. Noted. But... You mean, the find extensions it uses? And/or the bash syntax? It doesn't have to be POSIX, it has to work on a full install of Slackware, where /usr/bin/find is the GNU one (if it's not, you have broken a lot more than just this). And the shebang line is #!/bin/bash, meaning SlackBuilds are explicitly bash scripts, not intended to be portable to other shells. This has been discussed to death already in the past (on this list, in private emails, and on IRC)... Even if someday Pat changes the default /bin/sh by symlinking it to something other than /bin/bash (unlikely but I suppose possible), I doubt he'll remove bash from the distro. From list+sbo at vahedi.org Tue Aug 4 11:13:42 2026 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Tue, 04 Aug 2026 11:13:42 +0000 Subject: [Slackbuilds-users] template find/chmod RFC In-Reply-To: References: <7b78a8321f2c3cfc972a97124b6684c8bcf56561@vahedi.org> Message-ID: <3f0bd516d2d02985bfb25f1f60ac381f3d353b00@vahedi.org> August 4, 2026, "B. Watson" wrote: > You mean, the find extensions it uses? And/or the bash syntax? The "-perm /111" part of the "find" command. >? > It doesn't have to be POSIX, it has to work on a full install of > Slackware, where /usr/bin/find is the GNU one... Agreed. I was just stating a fact. > And the shebang line is #!/bin/bash... No argument there. -Shahab From nick at smallbone.se Tue Aug 4 15:17:50 2026 From: nick at smallbone.se (Nick Smallbone) Date: Tue, 04 Aug 2026 16:17:50 +0100 Subject: [Slackbuilds-users] Remove office/elyxer Message-ID: <26fe2860-dca7-4869-b7fe-699c01a3750d@app.fastmail.com> Hi, I recently offered to take over office/elyxer (a LyX-to-HTML converter), but now I see that it's unmaintained upstream, its last release was in 2013, and it doesn't work well with modern versions of LyX. Probably we should just remove it from the repo? Nick From nick at smallbone.se Tue Aug 4 16:04:17 2026 From: nick at smallbone.se (Nick Smallbone) Date: Tue, 04 Aug 2026 17:04:17 +0100 Subject: [Slackbuilds-users] Remove python/hgsubversion too Message-ID: <7342c695-4da4-4f9b-9ac1-2472748cba39@app.fastmail.com> Hi, Sorry for the spam, looks like python/hgsubversion is also unmaintained upstream and not working any more, could we remove it too? Nick From willysr at slackbuilds.org Tue Aug 4 23:59:14 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 5 Aug 2026 06:59:14 +0700 Subject: [Slackbuilds-users] Remove office/elyxer In-Reply-To: <26fe2860-dca7-4869-b7fe-699c01a3750d@app.fastmail.com> References: <26fe2860-dca7-4869-b7fe-699c01a3750d@app.fastmail.com> Message-ID: <20260805065914.6dbe3c76@office64.slackie.org> >Hi, > >I recently offered to take over office/elyxer (a LyX-to-HTML >converter), but now I see that it's unmaintained upstream, its last >release was in 2013, and it doesn't work well with modern versions of >LyX. > >Probably we should just remove it from the repo? done, also with hgsubversion -- 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 Wed Aug 5 09:13:18 2026 From: urchlay at slackware.uk (B. Watson) Date: Wed, 5 Aug 2026 05:13:18 -0400 (EDT) Subject: [Slackbuilds-users] templates/ proposed updates Message-ID: <1f43a3b-71bd-1713-a35a-3472669dfb1b@slackware.uk> I'm planning to update the templates... proposed changes so far are here: https://git.slackbuilds.org/templates/log/?h=urchlay ...or clone the templates/ repo and check out the origin/urchlay branch. This is a request for comments. If you see anything that's questionable, confusing, or looks just plain wrong, let me know. And yes, I left TODO comments in rubygem-template.SlackBuild. Will address this in a separate thread. From pyllyukko at maimed.org Wed Aug 5 09:34:10 2026 From: pyllyukko at maimed.org (pyllyukko) Date: Wed, 5 Aug 2026 12:34:10 +0300 Subject: [Slackbuilds-users] New orphans In-Reply-To: <7b9fa5dd-6e1e-8cfb-8b3f-4f7cd72fc8c@slackware.uk> References: <7b9fa5dd-6e1e-8cfb-8b3f-4f7cd72fc8c@slackware.uk> Message-ID: Ehlo. On Sat, Jul 25, 2026 at 06:11:55AM -0400, B. Watson wrote: > > At this point, as of the update a few minutes ago, we have 10170 > SlackBuilds in the repo. And 1665 of them are orphaned due to being > unmaintained. That's 16% (or 1/6th) of the repo... > > I encourage everyone to look through the list of orphaned builds and > see if there's anything there that looks interesting and/or useful. > Anything you find, you can take maintenance of without even asking or > telling anyone. > > The list: > > https://slackbuilds.org/advsearch.php?stype=maint&q=NOEMAIL I'll take amavisd-new. -- pyllyukko email: PGP: https://keybase.io/pyllyukko From urchlay at slackware.uk Wed Aug 5 09:45:09 2026 From: urchlay at slackware.uk (B. Watson) Date: Wed, 5 Aug 2026 05:45:09 -0400 (EDT) Subject: [Slackbuilds-users] templates/ proposed updates In-Reply-To: <1f43a3b-71bd-1713-a35a-3472669dfb1b@slackware.uk> References: <1f43a3b-71bd-1713-a35a-3472669dfb1b@slackware.uk> Message-ID: <1b09a8-5b42-d919-6379-ebad7bb92723@slackware.uk> On Wed, 5 Aug 2026, B. Watson wrote: > And yes, I left TODO comments in rubygem-template.SlackBuild. Will > address this in a separate thread. Well, no, I won't. I figured out what I was doing wrong. The correct way is to add '-- --with-cflags="$SLKCFLAGS"' to the end of the 'gem install' command. I kept leaving off the --, which gives an 'invalid option' error. Putting the -- in, I get a nice message: Building native extensions with: '--with-cflags=-O2 -fPIC' ...and strace shows that, yes, gcc is being executed with these flags. From urchlay at slackware.uk Wed Aug 5 10:02:30 2026 From: urchlay at slackware.uk (B. Watson) Date: Wed, 5 Aug 2026 06:02:30 -0400 (EDT) Subject: [Slackbuilds-users] New orphans In-Reply-To: References: <7b9fa5dd-6e1e-8cfb-8b3f-4f7cd72fc8c@slackware.uk> Message-ID: On Wed, 5 Aug 2026, pyllyukko wrote: > I'll take amavisd-new. amavisd-new.info in my branch now: MAINTAINER="pyllyukko" EMAIL="pyllyukko at maimed.org" From kvngncrlsn at gmail.com Wed Aug 5 15:38:22 2026 From: kvngncrlsn at gmail.com (K. Eugene Carlson) Date: Thu, 6 Aug 2026 00:38:22 +0900 Subject: [Slackbuilds-users] templates/ proposed updates In-Reply-To: <1b09a8-5b42-d919-6379-ebad7bb92723@slackware.uk> References: <1f43a3b-71bd-1713-a35a-3472669dfb1b@slackware.uk> <1b09a8-5b42-d919-6379-ebad7bb92723@slackware.uk> Message-ID: If you're open to suggestions, maybe some kind of reminder about noarch for the perl template would be appropriate. I did a test run, and almost 300 packages in the perl series triggered the "good candidate for noarch" sbopkglint message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From poprocks at gmail.com Wed Aug 5 18:45:12 2026 From: poprocks at gmail.com (Logan Rathbone) Date: Wed, 5 Aug 2026 14:45:12 -0400 Subject: [Slackbuilds-users] templates/ proposed updates In-Reply-To: References: <1f43a3b-71bd-1713-a35a-3472669dfb1b@slackware.uk> <1b09a8-5b42-d919-6379-ebad7bb92723@slackware.uk> Message-ID: I have a few thoughts on the meson template. The current meson template runs the initial setup operation (equivalent to ./configure) by running entering into the build directory and running `meson` without argument on the parent directory. This is deprecated - `meson setup` is the command that is supposed to be run these days. No warning message is printed with the version of meson that ships with 15.0, but in newer versions such as -current, we're going to start seeing lots of annoying warning messages once 15.1 is released. The version shipped with 15.0 also supports `meson setup`, so there is no harm in migrating the template now. Also, the creation and chdir's to and from $CWD/build are unnecessary, since meson will handle this on its own via the `setup` command as well as via the `-C` option. Attached please find a diff with proposed changes to the meson template. Regards, L.A. Rathbone (poprocks) On Wed, Aug 5, 2026 at 11:38?AM K. Eugene Carlson wrote: > > If you're open to suggestions, maybe some kind of reminder about noarch for the perl template would be appropriate. > > I did a test run, and almost 300 packages in the perl series triggered the "good candidate for noarch" sbopkglint message. > _______________________________________________ > 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: 20260805-proposed-meson-template-change.diff Type: text/x-patch Size: 1102 bytes Desc: not available URL: From urchlay at slackware.uk Wed Aug 5 21:10:50 2026 From: urchlay at slackware.uk (B. Watson) Date: Wed, 5 Aug 2026 17:10:50 -0400 (EDT) Subject: [Slackbuilds-users] templates/ proposed updates In-Reply-To: References: <1f43a3b-71bd-1713-a35a-3472669dfb1b@slackware.uk> <1b09a8-5b42-d919-6379-ebad7bb92723@slackware.uk> Message-ID: <2317a16b-e6a5-7db0-954c-684f9b755de5@slackware.uk> On Wed, 5 Aug 2026, Logan Rathbone wrote: > The version shipped with 15.0 also supports `meson setup`, so there is > no harm in migrating the template now. Yeah, we get the warnings for anything using python3-meson-opt on 15.0, too. > Attached please find a diff with proposed changes to the meson template. Looks good. Will do some testing but I don't expect problems. A question... does it really make sense to call ninja as "${NINJA:=ninja}" instead of just saying "ninja"? It exists to support samu (from the samurai build). But why does anyone care whether a build uses regular ninja or samu? Is samu faster? If there are builds that don't work with regular ninja, that need samu, we'd just write "samu" in their SlackBuilds... it doesn't look like anyone's ever done this, though. I mean, we have an alternate implementation of meson called "muon", but nobody's proposed supporting it via "${MESON:=meson}" in the template. If someone *really* wants to use samu, wouldn't it make more sense to have a profile.d script that sets up PATH so it has a directory with a symlink samu => ninja, and let the user source that script? This is how e.g. cmake-opt works. From urchlay at slackware.uk Wed Aug 5 21:16:07 2026 From: urchlay at slackware.uk (B. Watson) Date: Wed, 5 Aug 2026 17:16:07 -0400 (EDT) Subject: [Slackbuilds-users] templates/ proposed updates In-Reply-To: References: <1f43a3b-71bd-1713-a35a-3472669dfb1b@slackware.uk> <1b09a8-5b42-d919-6379-ebad7bb92723@slackware.uk> Message-ID: <31aadf9c-9184-1a41-1966-a96811fc6e6@slackware.uk> On Thu, 6 Aug 2026, K. Eugene Carlson wrote: > If you're open to suggestions, maybe some kind of reminder about noarch for the perl template would be appropriate. > I did a test run, and almost 300 packages in the perl series triggered the "good candidate for noarch" sbopkglint message. Good idea. I just took over a few perl builds and had to noarch-ify them. Also the perl template sets, but never uses, both SLKCFLAGS and LIBDIRSUFFIX. To me, that smacks of cargo-cult programming... From poprocks at gmail.com Wed Aug 5 22:35:34 2026 From: poprocks at gmail.com (Logan Rathbone) Date: Wed, 5 Aug 2026 18:35:34 -0400 Subject: [Slackbuilds-users] templates/ proposed updates In-Reply-To: <2317a16b-e6a5-7db0-954c-684f9b755de5@slackware.uk> References: <1f43a3b-71bd-1713-a35a-3472669dfb1b@slackware.uk> <1b09a8-5b42-d919-6379-ebad7bb92723@slackware.uk> <2317a16b-e6a5-7db0-954c-684f9b755de5@slackware.uk> Message-ID: On Wed, Aug 5, 2026 at 5:16?PM B. Watson wrote: > A question... does it really make sense to call ninja as "${NINJA:=ninja}" > instead of just saying "ninja"? Personally I'd have no problem just saying "ninja". I always just assumed there was some reason it was done like this, for the benefit of *someone*, *somewhere*. I believe I have a couple of my own builds where I just use "ninja" and go on with my life. > It exists to support samu (from the samurai build). But why does > anyone care whether a build uses regular ninja or samu? Is samu > faster? > > If there are builds that don't work with regular ninja, that need > samu, we'd just write "samu" in their SlackBuilds... it doesn't look > like anyone's ever done this, though. > > I mean, we have an alternate implementation of meson called "muon", > but nobody's proposed supporting it via "${MESON:=meson}" in the > template. > > If someone *really* wants to use samu, wouldn't it make more sense to > have a profile.d script that sets up PATH so it has a directory with > a symlink samu => ninja, and let the user source that script? This is > how e.g. cmake-opt works. I don't have an opinion on this, but I think you make some good points! From pyllyukko at maimed.org Thu Aug 6 04:12:05 2026 From: pyllyukko at maimed.org (pyllyukko) Date: Thu, 6 Aug 2026 07:12:05 +0300 Subject: [Slackbuilds-users] New orphans In-Reply-To: References: <7b9fa5dd-6e1e-8cfb-8b3f-4f7cd72fc8c@slackware.uk> Message-ID: On Wed, Aug 05, 2026 at 06:02:30AM -0400, B. Watson wrote: > > > On Wed, 5 Aug 2026, pyllyukko wrote: > > > I'll take amavisd-new. > > amavisd-new.info in my branch now: > > MAINTAINER="pyllyukko" > EMAIL="pyllyukko at maimed.org" Also merged here: https://github.com/SlackBuildsOrg/slackbuilds/pull/16977 -- pyllyukko email: PGP: https://keybase.io/pyllyukko -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From urchlay at slackware.uk Thu Aug 6 04:58:04 2026 From: urchlay at slackware.uk (B. Watson) Date: Thu, 6 Aug 2026 00:58:04 -0400 (EDT) Subject: [Slackbuilds-users] New orphans In-Reply-To: References: <7b9fa5dd-6e1e-8cfb-8b3f-4f7cd72fc8c@slackware.uk> Message-ID: <67d93930-10a8-d952-60f1-b9889934bd2a@slackware.uk> On Thu, 6 Aug 2026, pyllyukko wrote: > Also merged here: > https://github.com/SlackBuildsOrg/slackbuilds/pull/16977 OK, removed my commit. Basically I've been doing the "update the .info" thing locally for my own purposes (keep track of who's taking over a build). From pyllyukko at maimed.org Thu Aug 6 08:25:22 2026 From: pyllyukko at maimed.org (pyllyukko) Date: Thu, 6 Aug 2026 11:25:22 +0300 Subject: [Slackbuilds-users] Requesting UID for p0f Message-ID: Ehlo. I took over maintainership of p0f[1]. I would need an UID assigned for it, as instructed in the README[2]? 1: https://github.com/SlackBuildsOrg/slackbuilds/pull/16992 2: https://lcamtuf.coredump.cx/p0f3/README -- pyllyukko email: PGP: https://keybase.io/pyllyukko From willysr at slackbuilds.org Thu Aug 6 14:57:00 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 6 Aug 2026 21:57:00 +0700 Subject: [Slackbuilds-users] Requesting UID for p0f In-Reply-To: References: Message-ID: <20260806215700.7c2e3d7e@home.slackie.org> >Ehlo. > >I took over maintainership of p0f[1]. I would need an UID assigned for >it, as instructed in the README[2]? > >1: https://github.com/SlackBuildsOrg/slackbuilds/pull/16992 >2: https://lcamtuf.coredump.cx/p0f3/README let us know what user/group you want to be assigned? -- 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 duncan_roe at optusnet.com.au Fri Aug 7 05:22:20 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Fri, 7 Aug 2026 15:22:20 +1000 Subject: [Slackbuilds-users] Regarding "make V=1" in the autotools template Message-ID: Hi, Can I suggest a simplification? Instead of the proposed:- | # If the compile fails and you're using MAKEFLAGS=-j, try adding | # -j1 to the make command: | #make -j1 V=1 put something like:- | # To aid debugging of possible compile failures, | #make || make -j1 V=1 | # This can be left in. Cheers ... Duncan. From urchlay at slackware.uk Fri Aug 7 05:27:49 2026 From: urchlay at slackware.uk (B. Watson) Date: Fri, 7 Aug 2026 01:27:49 -0400 (EDT) Subject: [Slackbuilds-users] Regarding "make V=1" in the autotools template In-Reply-To: References: Message-ID: <51a84af8-618-ff6b-b29d-275ae22b41ee@slackware.uk> On Fri, 7 Aug 2026, Duncan Roe wrote: > Hi, > > Can I suggest a simplification? Instead of the proposed:- > > | # If the compile fails and you're using MAKEFLAGS=-j, try adding > | # -j1 to the make command: > | #make -j1 V=1 > > put something like:- > > | # To aid debugging of possible compile failures, > | #make || make -j1 V=1 > | # This can be left in. Ought to be: make V=1 || make -j1 V=1 ...the point being, we always want to see the compile commands. Not just if the compile fails, but always. It lets us catch things like, ignoring our SLKCFLAGS, or overriding them (we put "-O2 -fPIC", but the Makefile adds a -O3 after our flags, whoops). I'm not sure how others feel about the "make || make -j1" thing. I know PV's SlackBuilds do it. I've never tested it so I don't know if it always works or not... From julian at dotcore.co.il Fri Aug 7 06:13:06 2026 From: julian at dotcore.co.il (Julian Grinblat) Date: Fri, 7 Aug 2026 15:13:06 +0900 Subject: [Slackbuilds-users] =?utf-8?q?=5Bqemu-static=5D_update-binfmts_-?= =?utf-8?q?-import_=E2=80=94_intended_manual_step=3F?= In-Reply-To: <87o6gdithp.fsf@laptop.lockywolf.net> References: <87ech9kdxr.fsf@laptop.lockywolf.net> <87o6gdithp.fsf@laptop.lockywolf.net> Message-ID: thanks! Yeah the 7.1.x issue I was just bringing to your attention, maybe by the time we upgrade it will be solved :) On Tue, Aug 4, 2026 at 11:01?AM Lockywolf Laptop wrote: > > > Julian Grinblat writes: > > > patch below, which I think will be useful for newcomers: > > You can see the merge progress at the link below: > > https://gitlab.com/SlackBuilds.org/slackbuilds/-/merge_requests/977 > > > As an aside, not part of this patch: I hit a build failure worth > > flagging if you're aware of it - the bundled static glibc fails with > > `OPEN_TREE_CLONE redefined [-Werror]` when built against the > > experimental linux-7.1.x testing kernel line (kernel-headers-7.1.x) > > rather than mainline -current. kernel-headers-7.1.x reformats some > > mount.h flags to bit-shift notation, which collides with glibc's own > > bundled definition of the same constant - harmless (same value), but > > fatal since glibc's build enables -Werror. Slackware's own official > > glibc build doesn't hit this, since it's built against mainline > > kernel-headers, not the testing branch. --disable-werror on the > > bundled glibc's configure works around it, in case it's useful to know > > about even without a formal patch. > > I am afraid it's not really worth fixing at the moment, because kernel, > glibc, qemu, everything might change by the time 7.1.x gets into > -current, so rather than patching the existing version it might be worth > updating the glibc instead. > > I think Ponce might be interested in knowing this, though, he has his > own branch dedicated to -current (see > https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/page507.html) > But I suspect he will also say "when 7.1.x (or even something newer) > gets into -current." > > -- > Your sincerely, > Vladimir Nikishkin (MiEr, lockywolf) > (Laptop) > _______________________________________________ > 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 pyllyukko at maimed.org Fri Aug 7 06:34:03 2026 From: pyllyukko at maimed.org (pyllyukko) Date: Fri, 7 Aug 2026 09:34:03 +0300 Subject: [Slackbuilds-users] Requesting UID for p0f In-Reply-To: <20260806215700.7c2e3d7e@home.slackie.org> References: <20260806215700.7c2e3d7e@home.slackie.org> Message-ID: Ehlo. On Thu, Aug 06, 2026 at 09:57:00PM +0700, Willy Sudiarto Raharjo wrote: > >Ehlo. > > > >I took over maintainership of p0f[1]. I would need an UID assigned for > >it, as instructed in the README[2]? > > > >1: https://github.com/SlackBuildsOrg/slackbuilds/pull/16992 > >2: https://lcamtuf.coredump.cx/p0f3/README > > > let us know what user/group you want to be assigned? User "p0f-user" as in the README. Thanks. -- pyllyukko email: PGP: https://keybase.io/pyllyukko From jebrhansen+SBo at gmail.com Fri Aug 7 06:51:41 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Thu, 6 Aug 2026 23:51:41 -0700 Subject: [Slackbuilds-users] Requesting UID for p0f In-Reply-To: References: <20260806215700.7c2e3d7e@home.slackie.org> Message-ID: On Thu, Aug 6, 2026, 11:34?PM pyllyukko wrote: > Ehlo. > > On Thu, Aug 06, 2026 at 09:57:00PM +0700, Willy Sudiarto Raharjo wrote: > > >Ehlo. > > > > > >I took over maintainership of p0f[1]. I would need an UID assigned for > > >it, as instructed in the README[2]? > > > > > >1: https://github.com/SlackBuildsOrg/slackbuilds/pull/16992 > > >2: https://lcamtuf.coredump.cx/p0f3/README > > > > > > let us know what user/group you want to be assigned? > > User "p0f-user" as in the README. Thanks. > In fairness to the SBo admins, this was a 900+ line README with only a single line stating this could be ran with a unique user (and actually suggesting earlier it probably needs to be ran as root [1]). Whatever user OP is requesting should've been specified in the original email. Jeremy [1] "You probably need to run the tool as root." > -------------- next part -------------- An HTML attachment was scrubbed... URL: From duncan_roe at optusnet.com.au Fri Aug 7 07:06:19 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Fri, 7 Aug 2026 17:06:19 +1000 Subject: [Slackbuilds-users] Regarding "make V=1" in the autotools template In-Reply-To: <51a84af8-618-ff6b-b29d-275ae22b41ee@slackware.uk> References: <51a84af8-618-ff6b-b29d-275ae22b41ee@slackware.uk> Message-ID: On Fri, Aug 07, 2026 at 01:27:49AM -0400, B. Watson wrote: > > > On Fri, 7 Aug 2026, Duncan Roe wrote: > > > Hi, > > > > Can I suggest a simplification? Instead of the proposed:- > > > > | # If the compile fails and you're using MAKEFLAGS=-j, try adding > > | # -j1 to the make command: > > | #make -j1 V=1 > > > > put something like:- > > > > | # To aid debugging of possible compile failures, > > | #make || make -j1 V=1 > > | # This can be left in. > > Ought to be: > > make V=1 || make -j1 V=1 > > ...the point being, we always want to see the compile commands. Not > just if the compile fails, but always. It lets us catch things like, > ignoring our SLKCFLAGS, or overriding them (we put "-O2 -fPIC", but > the Makefile adds a -O3 after our flags, whoops). > > I'm not sure how others feel about the "make || make -j1" thing. I > know PV's SlackBuilds do it. I've never tested it so I don't know if > it always works or not... If you get compiler errors (say when upgrading) then it's definitely much easier to find the error message with -j1. I don't bother with MAKEFLAGS, just run `make -j$(($(nproc)+1))". (Automated edit, will be small part of a new SB I hope to submit later this year). Cheers .... Duncan. From urchlay at slackware.uk Fri Aug 7 07:13:51 2026 From: urchlay at slackware.uk (B. Watson) Date: Fri, 7 Aug 2026 03:13:51 -0400 (EDT) Subject: [Slackbuilds-users] Regarding "make V=1" in the autotools template In-Reply-To: References: <51a84af8-618-ff6b-b29d-275ae22b41ee@slackware.uk> Message-ID: <5d64d455-c5dd-5431-8ff1-58e9d3832ac1@slackware.uk> On Fri, 7 Aug 2026, Duncan Roe wrote: > If you get compiler errors (say when upgrading) then it's definitely much easier > to find the error message with -j1. True. I just meant, both branches (make with & without the -j1) should have V=1. Even then, when using plain make (without autoconf/cmake/etc), some upstream devs put @ in front of the compile commands: %.o %.c: @$(CC) $(CFLAGS) ... I'll go so far as to use sed to get rid of the @'s. From willysr at slackbuilds.org Fri Aug 7 08:09:43 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 7 Aug 2026 15:09:43 +0700 Subject: [Slackbuilds-users] Regarding "make V=1" in the autotools template In-Reply-To: References: <51a84af8-618-ff6b-b29d-275ae22b41ee@slackware.uk> Message-ID: <20260807150943.5eb1291e@office64.slackie.org> >I don't bother with MAKEFLAGS, just run `make -j$(($(nproc)+1))". >(Automated edit, will be small part of a new SB I hope to submit later >this year). no, please don't use -j $(nproc) we only allow -j1 for scripts that doesn't support multicore builds if you wish to utilize your number of cores, please adjust with MAKEFLAGS on your own machine -- 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 Fri Aug 7 08:13:37 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 7 Aug 2026 15:13:37 +0700 Subject: [Slackbuilds-users] Requesting UID for p0f In-Reply-To: References: <20260806215700.7c2e3d7e@home.slackie.org> Message-ID: <20260807151337.0c3b46f6@office64.slackie.org> >> let us know what user/group you want to be assigned? > >User "p0f-user" as in the README. Thanks. That's just an example, but i put p0f in the uid_gid -- 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 glenn_e_becker at protonmail.com Fri Aug 7 11:52:39 2026 From: glenn_e_becker at protonmail.com (glenn_e_becker) Date: Fri, 07 Aug 2026 11:52:39 +0000 Subject: [Slackbuilds-users] anki Slackbuild Message-ID: Good morning, Yesterday I tried installing the anki Slackbuild via sbopkg on a new (stable) 15.0 laptop. The build completed but anki fails with bash-5.1$ anki anki: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by anki)anki: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by anki) This makes sense since stable is using glibc 2.33. glibc 2.42 is in testing of course. I tried emailing the maintainer but the email has so far failed to go through (Proton Mail reports that it is 'still being retried'). I notice some messages from the list regarding whether this maintainer (Caterino Tommaso) is still active. It looks like the answer is a maybe ...? Thanks, Glenn Becker (I used to maintain some packages but haven't had a Slack box for a while) ===================================== Rain comes down through the alders, Its low conducive voices Mutter about let-downs and erosions And yet each drop recalls The diamond absolutes. -- Seamus Heaney Sent with [Proton Mail](https://proton.me/mail/home) secure email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Aug 7 12:14:49 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 7 Aug 2026 19:14:49 +0700 Subject: [Slackbuilds-users] anki Slackbuild In-Reply-To: References: Message-ID: <20260807191449.04bb057e@home.slackie.org> >Good morning, > >Yesterday I tried installing the anki Slackbuild via sbopkg on a new (stable) >15.0 laptop. > >The build completed but anki fails with > >bash-5.1$ anki >anki: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by anki)anki: >/lib64/libc.so.6: version `GLIBC_2.34' not found (required by anki) > >This makes sense since stable is using glibc 2.33. > >glibc 2.42 is in testing of course. > >I tried emailing the maintainer but the email has so far failed to go through >(Proton Mail reports that it is 'still being retried'). I notice some messages >from the list regarding whether this maintainer (Caterino Tommaso) is still >active. It looks like the answer is a maybe ...? Caterino Tommaso is the maintainer but the one who posted an update since last year was Alan and i think he is using -current on his test. Since CI only test for build stage and not runtime, this kind of issue was not detected properly. I think we need to revert it to the version that works for -stable If you can test which version works, please let us know by sending PR -- 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 glenn_e_becker at protonmail.com Fri Aug 7 12:18:55 2026 From: glenn_e_becker at protonmail.com (glenn_e_becker) Date: Fri, 07 Aug 2026 12:18:55 +0000 Subject: [Slackbuilds-users] anki Slackbuild In-Reply-To: <20260807191449.04bb057e@home.slackie.org> References: <20260807191449.04bb057e@home.slackie.org> Message-ID: Hi Willy - I used the email for Alan, but I perhaps got it wrong ... Will try building earlier versions and will report back. Thanks. GB ===================================== Rain comes down through the alders, Its low conducive voices Mutter about let-downs and erosions And yet each drop recalls The diamond absolutes. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- Seamus Heaney Sent with Proton Mail secure email. On Friday, August 7th, 2026 at 8:15 AM, Willy Sudiarto Raharjo wrote: > >Good morning, > > > >Yesterday I tried installing the anki Slackbuild via sbopkg on a new (stable) > >15.0 laptop. > > > >The build completed but anki fails with > > > >bash-5.1$ anki > >anki: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by anki)anki: > >/lib64/libc.so.6: version `GLIBC_2.34' not found (required by anki) > > > >This makes sense since stable is using glibc 2.33. > > > >glibc 2.42 is in testing of course. > > > >I tried emailing the maintainer but the email has so far failed to go through > >(Proton Mail reports that it is 'still being retried'). I notice some messages > >from the list regarding whether this maintainer (Caterino Tommaso) is still > >active. It looks like the answer is a maybe ...? > > Caterino Tommaso is the maintainer but the one who posted an update since last > year was Alan and i think he is using -current on his test. > Since CI only test for build stage and not runtime, this kind of issue was not > detected properly. > > I think we need to revert it to the version that works for -stable > If you can test which version works, please let us know by sending PR > > > -- > Willy Sudiarto Raharjo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > From glenn_e_becker at protonmail.com Fri Aug 7 13:11:44 2026 From: glenn_e_becker at protonmail.com (glenn_e_becker) Date: Fri, 07 Aug 2026 13:11:44 +0000 Subject: [Slackbuilds-users] anki Slackbuild In-Reply-To: References: <20260807191449.04bb057e@home.slackie.org> Message-ID: Hi - If I'm reading the changelogs correctly, v. 24.11 of Anki is the last version before the glibc dependency went to 2.35+ (but >2.31). I built 24.11 successfully and it works well on my stable box. Re: a PR, I will open myself to ridicule by saying I've never done one. Happily I'm now retired and have plenty of time to figure it out (if folks are willing to wait). Thx, Glenn ===================================== Rain comes down through the alders, Its low conducive voices Mutter about let-downs and erosions And yet each drop recalls The diamond absolutes. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- Seamus Heaney Sent with Proton Mail secure email. On Friday, August 7th, 2026 at 8:19 AM, glenn_e_becker via SlackBuilds-users wrote: > Hi Willy - > > I used the email for Alan, but I perhaps got it wrong ... > > Will try building earlier versions and will report back. Thanks. > > GB > > ===================================== > Rain comes down through the alders, > Its low conducive voices > Mutter about let-downs and erosions > And yet each drop recalls > > The diamond absolutes. > -- Seamus Heaney > > Sent with Proton Mail secure email. > > On Friday, August 7th, 2026 at 8:15 AM, Willy Sudiarto Raharjo wrote: > > > >Good morning, > > > > > >Yesterday I tried installing the anki Slackbuild via sbopkg on a new (stable) > > >15.0 laptop. > > > > > >The build completed but anki fails with > > > > > >bash-5.1$ anki > > >anki: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by anki)anki: > > >/lib64/libc.so.6: version `GLIBC_2.34' not found (required by anki) > > > > > >This makes sense since stable is using glibc 2.33. > > > > > >glibc 2.42 is in testing of course. > > > > > >I tried emailing the maintainer but the email has so far failed to go through > > >(Proton Mail reports that it is 'still being retried'). I notice some messages > > >from the list regarding whether this maintainer (Caterino Tommaso) is still > > >active. It looks like the answer is a maybe ...? > > > > Caterino Tommaso is the maintainer but the one who posted an update since last > > year was Alan and i think he is using -current on his test. > > Since CI only test for build stage and not runtime, this kind of issue was not > > detected properly. > > > > I think we need to revert it to the version that works for -stable > > If you can test which version works, please let us know by sending PR > > > > > > -- > > Willy Sudiarto Raharjo > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > > _______________________________________________ > 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 poprocks at gmail.com Fri Aug 7 13:14:53 2026 From: poprocks at gmail.com (Logan Rathbone) Date: Fri, 7 Aug 2026 09:14:53 -0400 Subject: [Slackbuilds-users] Regarding "make V=1" in the autotools template In-Reply-To: <51a84af8-618-ff6b-b29d-275ae22b41ee@slackware.uk> References: <51a84af8-618-ff6b-b29d-275ae22b41ee@slackware.uk> Message-ID: On Fri, Aug 7, 2026 at 1:33?AM B. Watson wrote: [snip] > ...the point being, we always want to see the compile commands. Not > just if the compile fails, but always. It lets us catch things like, > ignoring our SLKCFLAGS, or overriding them (we put "-O2 -fPIC", but > the Makefile adds a -O3 after our flags, whoops). On that note - on the subject of the meson template, I'd also recommend adding `-v` to the ninja options. I've done that in a couple of my slackbuilds and it works well to catch similar issues on the meson end of things. From k.venken at online.be Fri Aug 7 17:11:40 2026 From: k.venken at online.be (Karel Venken) Date: Fri, 7 Aug 2026 19:11:40 +0200 Subject: [Slackbuilds-users] Warning from openssh regarding key exchange In-Reply-To: <20260802090059.47ce9976@home.slackie.org> References: <20260802090059.47ce9976@home.slackie.org> Message-ID: Willy Sudiarto Raharjo wrote: >> Admins, >> >> When I 'git push' an update to the SBo git, this warning pops up: >> >> $ git push --set-upstream origin user/kingbeowulf/updates >> ** WARNING: connection is not using a post-quantum key exchange algorithm. >> ** This session may be vulnerable to "store now, decrypt later" attacks. >> ** The server may need to be upgraded. See https://openssh.com/pq.html >> >> I do not recall this warning last week or so. >> >> Slackware64-15.0 multilib and testing/graphics-updates >> openssh-10.4p1 > > you can ignore this warning > it's part of openssh's warning which is harmless > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > For whats worth. I noticed the same message when connecting to my cluster. I have difference versions of slackware on different systems. It typically appears when a recent ssh client connects to an older ssh server. I found following explanation, it may be helpful. == quote == The warning refers to the SSH key exchange algorithm, not to the host key itself. Current SSH key exchanges such as ECDH or Curve25519 are secure against today's computers, but a sufficiently powerful quantum computer could theoretically recover the exchanged session key from a recorded handshake. An attacker could therefore record encrypted traffic today and decrypt it years later ("store now, decrypt later"). Post-quantum key exchange algorithms are designed to prevent exactly this scenario. The warning simply indicates that the server does not yet support a post-quantum key exchange. For most day-to-day Git operations this is not an immediate security issue, but upgrading OpenSSH on the server side will remove the warning and provide protection against future quantum attacks. == unquote == Just notice, Slackware itself is not the issue here. The warning depends on the OpenSSH version and configuration of the remote server you're connecting to. As said. It is harmless unless working in certain conditions. From jebrhansen+SBo at gmail.com Fri Aug 7 17:49:45 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 7 Aug 2026 10:49:45 -0700 Subject: [Slackbuilds-users] anki Slackbuild In-Reply-To: References: <20260807191449.04bb057e@home.slackie.org> Message-ID: On Fri, Aug 7, 2026, 6:11?AM glenn_e_becker via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hi - > > If I'm reading the changelogs correctly, v. 24.11 of Anki is the last > version before the glibc dependency went to 2.35+ (but >2.31). > > I built 24.11 successfully and it works well on my stable box. > > Re: a PR, I will open myself to ridicule by saying I've never done one. > Happily I'm now retired and have plenty of time to figure it out (if folks > are willing to wait). > I had emailed out a git guide to the mailing list a few years back that the SBo admins tweaked and added to SBo itself. You can view it below: https://slackbuilds.org/SBo-Github-Workflows.txt Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn_e_becker at protonmail.com Fri Aug 7 18:13:16 2026 From: glenn_e_becker at protonmail.com (glenn_e_becker) Date: Fri, 07 Aug 2026 18:13:16 +0000 Subject: [Slackbuilds-users] anki Slackbuild In-Reply-To: References: <20260807191449.04bb057e@home.slackie.org> Message-ID: <2rOHfj8BRSqQUakLbfYBgVicfnZYnBlYdPRfxEgxQvDdshzypsO-Prje2eOD8kPxfegb-i8QxcbFp8AFN-sv-tFyn6k-SPAX0U3kbAM8y14=@protonmail.com> Thanks! I'm following it now. Very helpful. G ===================================== Rain comes down through the alders, Its low conducive voices Mutter about let-downs and erosions And yet each drop recalls The diamond absolutes. -- Seamus Heaney Sent with [Proton Mail](https://proton.me/mail/home) secure email. On Friday, August 7th, 2026 at 1:49 PM, Jeremy Hansen wrote: > On Fri, Aug 7, 2026, 6:11?AM glenn_e_becker via SlackBuilds-users wrote: > >> Hi - >> >> If I'm reading the changelogs correctly, v. 24.11 of Anki is the last version before the glibc dependency went to 2.35+ (but >2.31). >> >> I built 24.11 successfully and it works well on my stable box. >> >> Re: a PR, I will open myself to ridicule by saying I've never done one. Happily I'm now retired and have plenty of time to figure it out (if folks are willing to wait). > > I had emailed out a git guide to the mailing list a few years back that the SBo admins tweaked and added to SBo itself. You can view it below: > > https://slackbuilds.org/SBo-Github-Workflows.txt > > Jeremy > >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn_e_becker at protonmail.com Fri Aug 7 22:18:58 2026 From: glenn_e_becker at protonmail.com (glenn_e_becker) Date: Fri, 07 Aug 2026 22:18:58 +0000 Subject: [Slackbuilds-users] anki Slackbuild In-Reply-To: <2rOHfj8BRSqQUakLbfYBgVicfnZYnBlYdPRfxEgxQvDdshzypsO-Prje2eOD8kPxfegb-i8QxcbFp8AFN-sv-tFyn6k-SPAX0U3kbAM8y14=@protonmail.com> References: <20260807191449.04bb057e@home.slackie.org> <2rOHfj8BRSqQUakLbfYBgVicfnZYnBlYdPRfxEgxQvDdshzypsO-Prje2eOD8kPxfegb-i8QxcbFp8AFN-sv-tFyn6k-SPAX0U3kbAM8y14=@protonmail.com> Message-ID: I've submitted a PR. Hope it's okay. This was fun. Thanks to everyone who helped. G ===================================== Rain comes down through the alders, Its low conducive voices Mutter about let-downs and erosions And yet each drop recalls The diamond absolutes. -- Seamus Heaney Sent with [Proton Mail](https://proton.me/mail/home) secure email. On Friday, August 7th, 2026 at 2:13 PM, glenn_e_becker via SlackBuilds-users wrote: > Thanks! I'm following it now. Very helpful. G > > ===================================== > Rain comes down through the alders, > Its low conducive voices > Mutter about let-downs and erosions > And yet each drop recalls > > The diamond absolutes. > -- Seamus Heaney > > Sent with [Proton Mail](https://proton.me/mail/home) secure email. > > On Friday, August 7th, 2026 at 1:49 PM, Jeremy Hansen wrote: > >> On Fri, Aug 7, 2026, 6:11?AM glenn_e_becker via SlackBuilds-users wrote: >> >>> Hi - >>> >>> If I'm reading the changelogs correctly, v. 24.11 of Anki is the last version before the glibc dependency went to 2.35+ (but >2.31). >>> >>> I built 24.11 successfully and it works well on my stable box. >>> >>> Re: a PR, I will open myself to ridicule by saying I've never done one. Happily I'm now retired and have plenty of time to figure it out (if folks are willing to wait). >> >> I had emailed out a git guide to the mailing list a few years back that the SBo admins tweaked and added to SBo itself. You can view it below: >> >> https://slackbuilds.org/SBo-Github-Workflows.txt >> >> Jeremy >> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Aug 8 02:30:44 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 8 Aug 2026 09:30:44 +0700 Subject: [Slackbuilds-users] Updates - 20260808.1 Message-ID: <20260808093044.7a6cbaf9@home.slackie.org> Sat Aug 8 02:13:27 UTC 2026 academic/calc: Updated for version 2.17.0.0, new maint. academic/gtkwave: Updated for version 3.3.128. academic/ngspice-jit: Updated for version 46.7. academic/octave: Update URL. academic/suitesparse: Updated for version 7.12.3 academic/yices2: Updated for version 2.7.0. academic/zotero-gtk2: Removed (obsolescent, unmaintained). audio/asap: Updated for version 8.0.0. audio/audacity: Always use wxWidgets-3.2. audio/caps: Fix homepage/download. audio/drumkv1: Updated for version 1.4.2. audio/faust: Updated for version 2.85.9. audio/guitarix: Updated for version 0.47.0. audio/id3tool: Use correct debian homepage. audio/lv2-mda-metapiano: Fix homepage/download URLs. audio/mda-lv2: Updated for version 1.2.12. audio/muse: New Maintainer audio/padthv1: Updated for version 1.4.2. audio/portmidi: Updated for version 2.0.8. audio/qm-vamp-plugins: Fix download. audio/samplv1: Updated for version 1.4.2. audio/soundconverter: Updated for version 4.1.3. audio/synthv1: Updated for version 1.4.2. audio/transcribe: Updated for version 9.60.3. audio/tta: New maintainer. audio/vmpk: Updated for version 0.9.2. audio/wmusic-xmms: Add no-conflict note. audio/wmusic: Updated for version 2.1.1. desktop/anki: Reverted to version 24.11 to allow building on stable. desktop/catfish: Updated for version 4.20.1. desktop/devilspie: New maintainer desktop/joystickwake: Updated for version 1.0 desktop/noice: fix download URL desktop/papirus-icon-theme: Updated for version 20260801. desktop/river: Update dep. desktop/x2x: Updated for version 1.30_beta+20250217_0884251. desktop/xfce-hkmon: New maintainer desktop/xfce4-datetime-plugin: Updated for version 0.8.3. desktop/xfce4-wavelan-plugin: Updated for version 0.7.0. development/Catch2: Updated for version 3.15.3 development/GHDL: Updated for version 6.0.0. development/Kiro: Updated for version 1.0.288. development/antigravity-cli: Added (Antigravity CLI). development/antigravity-ide: Added (Antigravity CLI). development/antigravity2: Updated for version 2.4.3 development/asl: Updated for version 142_bld311. development/aws-cdk: Updated for version 2.1135.0. development/bacon: Updated for version 5.0.4. development/bbcsdl: Updated for version 20260801_6c30298 development/bmake: Updated for version 20260714. development/bruno: Updated for version 4.0.0. development/cargo-c: Updated for version 0.10.24 + new maintainer development/d-tools: Updated for version 2.112.1 development/ddisasm: Fix ccache incompatibility development/dkms: Updated for version 3.4.2 development/ecl: New Maintainer development/electron-bin: Updated for version 43.3.0 development/fasm: Updated for version 1.73.35. development/gcli: Updated for version 2.13.0. development/gitlab-cli: Updated for version 1.111.0. development/gitlab-cli: Updated for version 1.112.0. development/gnustep-base: Updated for version 1.31.1. development/gnustep-make: Updated for version 2.9.3. development/hadolint-bin: Updated for version 2.15.1. development/hexinator: Add note to self. development/hoppscotch: Updated for version 26.7.0. development/ieee-pilot: Updated for version 1.12. development/jujutsu: Updated for version 0.44.0 development/letos: Updated for version 4.0.2 development/mlton: Updated for version 20241230. development/mongodb-compass: Updated for version 1.49.14. development/notepadqq: Updated for version 20260802_37652c5 development/nvidia-container-toolkit: Updated for version 1.19.1. development/pnpm: Updated for version 11.19.0. development/pnpm: Updated for version 11.20.0. development/prek: Updated for version 0.4.11. development/prek: Updated for version 0.4.12. development/rider: Updated for version 2026.2.0.1. development/rider: Updated for version 2026.2.0.2. development/rust-opt: Add aarch64. development/sasm: Updated for version 3.16.0. development/sbcl: Updated for version 2.6.7 development/sbt: Updated for version 2.0.6 development/smartgit: Updated for version 26.1.051 development/souffle: improve README development/sourcegit: Updated for version 2026.17 development/tcc: Updated for version 0.9.28rc+20260730_2be0218b. development/tweak: Updated for version 3.02+20251018_29ce537. development/typos-lsp: Updated for version 0.1.54. development/typos-lsp: Updated for version 0.1.55. development/typos: Updated for version 1.49.0. development/vif: Fix homepage. development/vscode-bin: Updated for version 1.132.0. development/vstudio: Updated for version 17.5.3 development/zig-bin: Update README. development/zig-bin: Updated for version 0.9.1. development/zizmor: Updated for version 1.29.0. development/zxbasic: Updated for version 1.19.0 games/CorsixTH: Updated for version 0.70.0. games/OpenRA: Updated for version 20250330 games/PrismLauncher-Unlocked: Update MD5SUM. games/asteroidsinfinity: Updated for version 1.3. games/commandergenius: Updated for version 3.6.3. games/cosmic_assault: Fix homepage. games/doomseeker: Updated for version 1.5.3. games/lmpc: Updated for version 3.5.1. games/openyahtzee: Updated for version 1.10. games/pentagram: Removed (folded into scummvm). games/puzzles: Updated for version 20260720.3c36322. games/solarus: Updated for version 2.1.1 games/solarwolf: Updated for version 1.6.0. games/tint: Updated for version 0.11. games/torcs: Updated for version 1.3.9. games/trs80gp: Updated for version 2.5.7. games/xroar: Updated for version 1.12.1. games/xskat: New Source URL. games/zork-mit: Add note to self. graphics/GraphicsMagick: Fix build w/old version installed. graphics/OpenCASCADE: Orphaned (unmaintained). graphics/flpsed: Fix download. graphics/fontforge: Updated for version 20251009. graphics/openscad: Orphaned (unmaintained). graphics/psftools: Updated for version 1.1.3. graphics/raw-thumbnailer: New maintainer. graphics/vips: Updated for version 8.18.5. ham/SoapyRemote: Updated for version 0.5.2. ham/SoapySDRPlay: New source. ham/liquid-dsp: Updated for version 1.8.1. libraries/CGAL: Orphaned (unmaintained). libraries/CLI11: Updated for version 2.7.1. libraries/OpenCSG: Orphaned (unmaintained). libraries/SDL3: Updated for version 3.4.14 libraries/SOPE: Updated for version 5.12.9. libraries/appstream-glib: Updated for version 0.8.4. libraries/fcft: update to 3.1.6 libraries/fcgi: Orphaned (unmaintained). libraries/kddockwidgets: Updated for version 2.4.1. libraries/levmar: Orphaned (unmaintained). libraries/libcdaudio: New maintainer libraries/libdaemon: Orphaned (unmaintained). libraries/libfabric: Updated for version 2.6.0 libraries/libfprint: New maintainer libraries/libopenraw: New maintainer. libraries/libxmlb: Updated for version 0.3.29. libraries/libyuv: Updated for version 0.0.1949.20260706 libraries/onevpl: Version bump to 2.17.0 libraries/pjsip: Updated for version 2.17. libraries/qt-avif-image-plugin: Updated for version 0.10.4. libraries/qt-jpegxl-image-plugin: Updated for version 0.8.4. libraries/tclap: Orphaned (unmaintained). libraries/vmaf: Updated for version 3.2.0 misc/ascii: Updated for version 3.32. misc/birthday: Restore old maintainer. misc/dejsonlz4: Added (Mozilla bookmarks backup decompressor). misc/dmg2img: Update maintainer. misc/es40: Updated for version 0.79.5 misc/figlet: Fix comment. misc/font-unscii: Add -j1 to make. misc/modprobed-db: Updated for version 2.50. misc/rsnapshot: Updated for version 1.5.1. misc/tinytldr: Updated for version 2.0.0 multimedia/cfourcc: Updated for version 0.1.5. multimedia/devedeng: Updated for version 4.18.0 multimedia/gst-plugins-bad-nonfree: Fix spandsp conflict. multimedia/opera-ffmpeg-codecs: Updated for version 43.3.0 multimedia/rav1e: Updated to version 0.8.1 multimedia/svt-av1: Updated for version 4.2.0 multimedia/vapoursynth-mvtools: orphaned multimedia/vapoursynth: orphaned multimedia/vobcopy: New maintainer multimedia/x265: Updated for version 4.3. multimedia/xawtv: New maintainer network/3proxy: Updated for version 0.9.8. network/GeoIP: Orphaned (unmaintained). network/amavisd-new: New maintainer. network/amneziawg-go: Updated for version 3.0.20260805. network/amneziawg-kernel: Updated for version 3.0.20260805. network/amneziawg-tools: Updated for version 3.0.20260805. network/ani-cli: Updated for version 5.0 network/asterisk: Updated for version 22.10.1. network/basilisk-bin: Updated for version 2026.06.12 network/bitlbee: Updated for version 3.6 network/brave-browser: Updated for version 1.93.134 network/brave-origin: Updated for version 1.93.134 network/clamav-unofficial-sigs: New maintainer. network/dropbox: Updated for version 264.4.3385. network/element-desktop-bin: Updated for version 1.12.25. network/element-desktop: Updated for version 1.12.25. network/franz: Updated for version 6.5.3. network/gallery-dl: Updated for version 1.32.9 network/helium-browser: Updated for version 0.15.1.1 network/httping: Updated for version 1.4.4, new maintainer. network/hylafax+: Updated for version 7.0.11. network/jitsi-meet-desktop: Updated for version 2026.8.0 network/keepalived: Updated for version 2.4.3. network/librewolf: Updated for version 153.0.1_1 network/memcached: Updated for version 1.6.45. network/metasploit-framework-bin: Updated for version 6.5.1. network/microsoft-edge: Updated for version 151.0.4129.59. network/milter-greylist: Updated for version 4.6.4. network/mpop: Updated for version 1.4.23 network/msmtp: Updated for version 1.8.34 network/netavark: Updated for version 2.0.0 network/newsraft: Updated for version 0.37 network/noip2: New maintainer network/offlineimap: New maintainer network/openconnect: Updated for version 9.21. network/opera: Updated for version 134.0.5954.31 network/p0f: New maintainer. network/palemoon-bin: Updated for version 34.3.2 network/palemoon: Updated for version 34.3.2 network/profanity: Updated for version 0.18.2. network/proton-vpn-cli: Added (Proton VPN CLI). network/python3-offlineimap: Added (Sync remote IMAP). network/radvd: New maintainer network/rclone-src: Updated for version 1.75.0 network/s: Updated for version 0.8.1 network/slakfinder-app: Added (Package explorer). network/spamassassin: Updated optional dependencies in the README. network/syncterm: Updated for version 1.8. network/tailscale: Updated for version 1.102.2 network/telegram: Updated for version 7.0.7. network/telegram: Updated for version 7.0.9. network/tnftp: Updated for version 20260211. network/vivaldi: Updated for version 8.1.4087.62. network/webex: Updated for version 46.8.0.33593 network/zen-browser: Updated for version 1.21.10b office/SOGo: Updated for version 5.12.9. office/elyxer: Removed (Unmaintained upstream). office/fbpdf: Updated for version 20250124_6a0d77f. office/ledger-live: Updated for version 4.13.1 office/mupdf: Updated for version 1.28.1. office/qownnotes: Updated for version 26.8.2. office/wps-office-dicts: Updated for version 26.8.0.2 office/zettlr: Updated for version 4.7.0. perl/cpanminus: Updated for version 1.7049; new maintainer. perl/perl-B-COW: Updated for version 0.007. perl/perl-B-Hooks-EndOfScope: Updated for version 0.28 perl/perl-BerkeleyDB: Updated for version 0.67. perl/perl-CGI: Orphaned (unmaintained). perl/perl-CPAN-Perl-Releases: Updated for version 20260803. perl/perl-Data-UUID: Updated for version 1.227. perl/perl-Data-Validate-IP: Updated for version 0.31 perl/perl-File-ShareDir-Install: Updated for version 0.14. perl/perl-IO-Tty: Updated for version 1.31. perl/perl-IP-Geolocation-MMDB: Added (Geolocation maxmind). perl/perl-IPC-Run3: Updated for version 0.049 perl/perl-Inline-C: Updated for version 0.82. perl/perl-Inline: Updated for version 0.87. perl/perl-JSON: Updated for version 4.11. perl/perl-LWP-Protocol-https: Updated for version 6.17. perl/perl-MIME-Types: Updated for version 2.30 and changed ARCH to noarch. perl/perl-Mail-DKIM: Added perl-CryptX as a dependency. perl/perl-MailTools: Updated for version 2.22. perl/perl-Math-BigInt-GMP: Updated for version 1.7003. perl/perl-Math-BigInt: Updated for version 2.005003. perl/perl-Math-GMPq: Updated for version 0.70. perl/perl-Math-GMPz: Updated for version 0.69. perl/perl-Math-MPC: Updated for version 1.43. perl/perl-Math-MPFR: Updated for version 4.47. perl/perl-Minion: Added (Job Queue). perl/perl-Minion: Update dep. perl/perl-Mozilla-CA: Updated for version 20250602. perl/perl-Net-IPv6Addr: Updated for version 1.02 perl/perl-Net-LDAP: Updated for version 0.68. perl/perl-Net-Server: Updated for version 2.018. perl/perl-Net-Write: Fix linter. perl/perl-NetAddr-IP: Added documentation. perl/perl-Socket6: Fix linter. perl/perl-Test-Class: Updated for version 0.52 perl/perl-Test-Fatal: Updated for version 0.018. perl/perl-Test-File: Updated for version 1.995. perl/perl-Test-NoWarnings: Updated for version 1.06. perl/perl-Test-Requires: Updated for version 0.11. perl/perl-Test-Warnings: Updated for version 0.038. perl/perl-Test-utf8: Updated for version 1.03. perl/perl-Text-CSV_XS: Updated for version 1.64 perl/perl-TimeDate: Updated for version 2.35. perl/perl-Try-Tiny: Updated for version 0.32. perl/perl-XML-SAX-Writer: Updated for version 0.57. perl/perl-YAML-LibYAML: Updated for version 0.910.0. perl/perl-io-uncompress-brotli: Updated for version 0.022. perl/perl-test-warn: Updated for version 0.37. python/feedparser: Updated for version 6.0.14 python/hgsubversion: Removed (Unmaintained upstream). python/mock: Orphaned (unmaintained). python/numexpr: Updated for version 2.14.2 python/pyOpenSSL: Updated for version 26.4.0. python/python2-authres: Updated for version 1.2.0. python/python2-pygame: Fix homepage/download. python/python2-pytest-runner: Orphaned (unmaintained). python/python3-argcomplete: Updated for version 3.7.0 python/python3-cffi: Updated for version 2.1.1. python/python3-dunamai: Updated for version 1.26.2. python/python3-fontmake: Updated for version 3.12.1 python/python3-glyphslib: Updated for version 6.14.0 python/python3-imaplib2: Added (Python module). python/python3-json5: Updated for version 0.15.0. python/python3-keyring: Update dependencies python/python3-llvmlite: Fix running on llvm13-compat python/python3-odfdo: Updated for version 3.24.0 python/python3-proton-keyring-linux: Added (Python proton keyring). python/python3-pycrypto: Use SLKCFLAGS. python/python3-pygame: Fix homepage/download. python/python3-pypdf: Updated for version 6.15.0 python/python3-reportlab: Updated for version 5.0.0 python/python3-secretstorage: Added (Python module). python/python3-shtab: Update for 1.9.3 python/python3-telethon: Added (Telegram Client Library). python/python3-ufo2ft: Updated for version 3.9.0 python/python3-xmldiff: Updated for version 3.0 python/sqlparse: Orphaned (unmaintained). system/Lmod: Updated for version 9.3. system/backintime: New Maintainer system/basu: Added (sd-bus library). system/cfengine: Updated for version 3.27.1. system/cpuid: Fix permissions; new maintainer. system/dateutils: update to 0.4.11 system/docker-buildx: Updated for version 0.36.0. system/docker-buildx: Updated for version 0.36.1. system/docker-compose: Updated for version 5.4.0 system/driconf: New maintainer system/dump: Updated for version 0.4b55. system/dvdisaster: New maintainer system/fastfetch: Explain the stopped updates in README. system/fprintd: New maintainer system/fswatch: update to 1.22.0 system/fwupd: Updated for version 2.1.7. system/fxload: New maintainer system/fzf: Updated for version 0.74.2. system/hw-probe: Reworked pacman patch; new maintainer. system/incus: Updated for version 7.3 system/jenkins: Updated for version 2.568.2. system/phpsysinfo: Updated for version 3.4.6 system/physlock: Updated for version 13. system/recoverdm: Fix homepage. system/rng-tools: New maintainer. system/sbotest: Updated for version 1.3. system/sbotools: Updated for version 4.4. system/sdl-jstest: Updated for version 0.2.2+20260729_cf4fab3. system/sdl2trs: Updated for version 1.2.35+20260517_96d531a4. system/sdltrs: Updated for version 1.2.35. system/smbldap-tools: Updated for version 0.9.11. system/symbola-font-ttf: Avoid writes to /root. system/targetcli-fb: Updated for version 3.0.2. system/ttf-nerd-fonts-symbols: Updated for version 3.5.0 system/uae: New maintainer system/uhubctl: Updated for version 2.6.0. system/vagrant: Updated for version 2.4.9 +--------------------------+ -- 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 mm at dorfdsl.de Sat Aug 8 12:51:58 2026 From: mm at dorfdsl.de (Marco Moock) Date: Sat, 8 Aug 2026 14:51:58 +0200 Subject: [Slackbuilds-users] firewalld maintainer Message-ID: <4c3f1e64-1234-4c58-a893-61b394c033d3@dorfdsl.de> Hello! I mailed the maintainer (didn't receive a bounce) of firewalld on 12th July regarding a package description that includes outdated things. There was also no update in the last 2 years - despite new upstream versions. Is there anyone who knows other contact addresses? -- kind regards Marco Junk-Mail bitte an trashcan 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 willysr at slackbuilds.org Sat Aug 8 14:44:49 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 8 Aug 2026 21:44:49 +0700 Subject: [Slackbuilds-users] firewalld maintainer In-Reply-To: <4c3f1e64-1234-4c58-a893-61b394c033d3@dorfdsl.de> References: <4c3f1e64-1234-4c58-a893-61b394c033d3@dorfdsl.de> Message-ID: <20260808214449.2e6c6de7@home.slackie.org> >I mailed the maintainer (didn't receive a bounce) of firewalld on 12th >July regarding a package description that includes outdated things. > >There was also no update in the last 2 years - despite new upstream >versions. > >Is there anyone who knows other contact addresses? feel free to take over -- 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 1.41421 at gmail.com Sat Aug 8 16:37:15 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 8 Aug 2026 10:37:15 -0600 Subject: [Slackbuilds-users] Updates - 20260808.1 In-Reply-To: <20260808093044.7a6cbaf9@home.slackie.org> References: <20260808093044.7a6cbaf9@home.slackie.org> Message-ID: proton-vpn-cli is not working for me: $ protonvpn-cli connect Traceback (most recent call last): File "/usr/bin/protonvpn-cli", line 6, in from pkg_resources import load_entry_point File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 3243, in def _initialize_master_working_set(): File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 3226, in _call_aside f(*args, **kwargs) File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 3255, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 568, in _build_master ws.require(__requires__) File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 886, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 772, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'protonvpn-cli==3.13.0' distribution was not found and is required by the application On Fri, Aug 7, 2026 at 8:30?PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Sat Aug 8 02:13:27 UTC 2026 > academic/calc: Updated for version 2.17.0.0, new maint. > academic/gtkwave: Updated for version 3.3.128. > academic/ngspice-jit: Updated for version 46.7. > academic/octave: Update URL. > academic/suitesparse: Updated for version 7.12.3 > academic/yices2: Updated for version 2.7.0. > academic/zotero-gtk2: Removed (obsolescent, unmaintained). > audio/asap: Updated for version 8.0.0. > audio/audacity: Always use wxWidgets-3.2. > audio/caps: Fix homepage/download. > audio/drumkv1: Updated for version 1.4.2. > audio/faust: Updated for version 2.85.9. > audio/guitarix: Updated for version 0.47.0. > audio/id3tool: Use correct debian homepage. > audio/lv2-mda-metapiano: Fix homepage/download URLs. > audio/mda-lv2: Updated for version 1.2.12. > audio/muse: New Maintainer > audio/padthv1: Updated for version 1.4.2. > audio/portmidi: Updated for version 2.0.8. > audio/qm-vamp-plugins: Fix download. > audio/samplv1: Updated for version 1.4.2. > audio/soundconverter: Updated for version 4.1.3. > audio/synthv1: Updated for version 1.4.2. > audio/transcribe: Updated for version 9.60.3. > audio/tta: New maintainer. > audio/vmpk: Updated for version 0.9.2. > audio/wmusic-xmms: Add no-conflict note. > audio/wmusic: Updated for version 2.1.1. > desktop/anki: Reverted to version 24.11 to allow building on stable. > desktop/catfish: Updated for version 4.20.1. > desktop/devilspie: New maintainer > desktop/joystickwake: Updated for version 1.0 > desktop/noice: fix download URL > desktop/papirus-icon-theme: Updated for version 20260801. > desktop/river: Update dep. > desktop/x2x: Updated for version 1.30_beta+20250217_0884251. > desktop/xfce-hkmon: New maintainer > desktop/xfce4-datetime-plugin: Updated for version 0.8.3. > desktop/xfce4-wavelan-plugin: Updated for version 0.7.0. > development/Catch2: Updated for version 3.15.3 > development/GHDL: Updated for version 6.0.0. > development/Kiro: Updated for version 1.0.288. > development/antigravity-cli: Added (Antigravity CLI). > development/antigravity-ide: Added (Antigravity CLI). > development/antigravity2: Updated for version 2.4.3 > development/asl: Updated for version 142_bld311. > development/aws-cdk: Updated for version 2.1135.0. > development/bacon: Updated for version 5.0.4. > development/bbcsdl: Updated for version 20260801_6c30298 > development/bmake: Updated for version 20260714. > development/bruno: Updated for version 4.0.0. > development/cargo-c: Updated for version 0.10.24 + new maintainer > development/d-tools: Updated for version 2.112.1 > development/ddisasm: Fix ccache incompatibility > development/dkms: Updated for version 3.4.2 > development/ecl: New Maintainer > development/electron-bin: Updated for version 43.3.0 > development/fasm: Updated for version 1.73.35. > development/gcli: Updated for version 2.13.0. > development/gitlab-cli: Updated for version 1.111.0. > development/gitlab-cli: Updated for version 1.112.0. > development/gnustep-base: Updated for version 1.31.1. > development/gnustep-make: Updated for version 2.9.3. > development/hadolint-bin: Updated for version 2.15.1. > development/hexinator: Add note to self. > development/hoppscotch: Updated for version 26.7.0. > development/ieee-pilot: Updated for version 1.12. > development/jujutsu: Updated for version 0.44.0 > development/letos: Updated for version 4.0.2 > development/mlton: Updated for version 20241230. > development/mongodb-compass: Updated for version 1.49.14. > development/notepadqq: Updated for version 20260802_37652c5 > development/nvidia-container-toolkit: Updated for version 1.19.1. > development/pnpm: Updated for version 11.19.0. > development/pnpm: Updated for version 11.20.0. > development/prek: Updated for version 0.4.11. > development/prek: Updated for version 0.4.12. > development/rider: Updated for version 2026.2.0.1. > development/rider: Updated for version 2026.2.0.2. > development/rust-opt: Add aarch64. > development/sasm: Updated for version 3.16.0. > development/sbcl: Updated for version 2.6.7 > development/sbt: Updated for version 2.0.6 > development/smartgit: Updated for version 26.1.051 > development/souffle: improve README > development/sourcegit: Updated for version 2026.17 > development/tcc: Updated for version 0.9.28rc+20260730_2be0218b. > development/tweak: Updated for version 3.02+20251018_29ce537. > development/typos-lsp: Updated for version 0.1.54. > development/typos-lsp: Updated for version 0.1.55. > development/typos: Updated for version 1.49.0. > development/vif: Fix homepage. > development/vscode-bin: Updated for version 1.132.0. > development/vstudio: Updated for version 17.5.3 > development/zig-bin: Update README. > development/zig-bin: Updated for version 0.9.1. > development/zizmor: Updated for version 1.29.0. > development/zxbasic: Updated for version 1.19.0 > games/CorsixTH: Updated for version 0.70.0. > games/OpenRA: Updated for version 20250330 > games/PrismLauncher-Unlocked: Update MD5SUM. > games/asteroidsinfinity: Updated for version 1.3. > games/commandergenius: Updated for version 3.6.3. > games/cosmic_assault: Fix homepage. > games/doomseeker: Updated for version 1.5.3. > games/lmpc: Updated for version 3.5.1. > games/openyahtzee: Updated for version 1.10. > games/pentagram: Removed (folded into scummvm). > games/puzzles: Updated for version 20260720.3c36322. > games/solarus: Updated for version 2.1.1 > games/solarwolf: Updated for version 1.6.0. > games/tint: Updated for version 0.11. > games/torcs: Updated for version 1.3.9. > games/trs80gp: Updated for version 2.5.7. > games/xroar: Updated for version 1.12.1. > games/xskat: New Source URL. > games/zork-mit: Add note to self. > graphics/GraphicsMagick: Fix build w/old version installed. > graphics/OpenCASCADE: Orphaned (unmaintained). > graphics/flpsed: Fix download. > graphics/fontforge: Updated for version 20251009. > graphics/openscad: Orphaned (unmaintained). > graphics/psftools: Updated for version 1.1.3. > graphics/raw-thumbnailer: New maintainer. > graphics/vips: Updated for version 8.18.5. > ham/SoapyRemote: Updated for version 0.5.2. > ham/SoapySDRPlay: New source. > ham/liquid-dsp: Updated for version 1.8.1. > libraries/CGAL: Orphaned (unmaintained). > libraries/CLI11: Updated for version 2.7.1. > libraries/OpenCSG: Orphaned (unmaintained). > libraries/SDL3: Updated for version 3.4.14 > libraries/SOPE: Updated for version 5.12.9. > libraries/appstream-glib: Updated for version 0.8.4. > libraries/fcft: update to 3.1.6 > libraries/fcgi: Orphaned (unmaintained). > libraries/kddockwidgets: Updated for version 2.4.1. > libraries/levmar: Orphaned (unmaintained). > libraries/libcdaudio: New maintainer > libraries/libdaemon: Orphaned (unmaintained). > libraries/libfabric: Updated for version 2.6.0 > libraries/libfprint: New maintainer > libraries/libopenraw: New maintainer. > libraries/libxmlb: Updated for version 0.3.29. > libraries/libyuv: Updated for version 0.0.1949.20260706 > libraries/onevpl: Version bump to 2.17.0 > libraries/pjsip: Updated for version 2.17. > libraries/qt-avif-image-plugin: Updated for version 0.10.4. > libraries/qt-jpegxl-image-plugin: Updated for version 0.8.4. > libraries/tclap: Orphaned (unmaintained). > libraries/vmaf: Updated for version 3.2.0 > misc/ascii: Updated for version 3.32. > misc/birthday: Restore old maintainer. > misc/dejsonlz4: Added (Mozilla bookmarks backup decompressor). > misc/dmg2img: Update maintainer. > misc/es40: Updated for version 0.79.5 > misc/figlet: Fix comment. > misc/font-unscii: Add -j1 to make. > misc/modprobed-db: Updated for version 2.50. > misc/rsnapshot: Updated for version 1.5.1. > misc/tinytldr: Updated for version 2.0.0 > multimedia/cfourcc: Updated for version 0.1.5. > multimedia/devedeng: Updated for version 4.18.0 > multimedia/gst-plugins-bad-nonfree: Fix spandsp conflict. > multimedia/opera-ffmpeg-codecs: Updated for version 43.3.0 > multimedia/rav1e: Updated to version 0.8.1 > multimedia/svt-av1: Updated for version 4.2.0 > multimedia/vapoursynth-mvtools: orphaned > multimedia/vapoursynth: orphaned > multimedia/vobcopy: New maintainer > multimedia/x265: Updated for version 4.3. > multimedia/xawtv: New maintainer > network/3proxy: Updated for version 0.9.8. > network/GeoIP: Orphaned (unmaintained). > network/amavisd-new: New maintainer. > network/amneziawg-go: Updated for version 3.0.20260805. > network/amneziawg-kernel: Updated for version 3.0.20260805. > network/amneziawg-tools: Updated for version 3.0.20260805. > network/ani-cli: Updated for version 5.0 > network/asterisk: Updated for version 22.10.1. > network/basilisk-bin: Updated for version 2026.06.12 > network/bitlbee: Updated for version 3.6 > network/brave-browser: Updated for version 1.93.134 > network/brave-origin: Updated for version 1.93.134 > network/clamav-unofficial-sigs: New maintainer. > network/dropbox: Updated for version 264.4.3385. > network/element-desktop-bin: Updated for version 1.12.25. > network/element-desktop: Updated for version 1.12.25. > network/franz: Updated for version 6.5.3. > network/gallery-dl: Updated for version 1.32.9 > network/helium-browser: Updated for version 0.15.1.1 > network/httping: Updated for version 1.4.4, new maintainer. > network/hylafax+: Updated for version 7.0.11. > network/jitsi-meet-desktop: Updated for version 2026.8.0 > network/keepalived: Updated for version 2.4.3. > network/librewolf: Updated for version 153.0.1_1 > network/memcached: Updated for version 1.6.45. > network/metasploit-framework-bin: Updated for version 6.5.1. > network/microsoft-edge: Updated for version 151.0.4129.59. > network/milter-greylist: Updated for version 4.6.4. > network/mpop: Updated for version 1.4.23 > network/msmtp: Updated for version 1.8.34 > network/netavark: Updated for version 2.0.0 > network/newsraft: Updated for version 0.37 > network/noip2: New maintainer > network/offlineimap: New maintainer > network/openconnect: Updated for version 9.21. > network/opera: Updated for version 134.0.5954.31 > network/p0f: New maintainer. > network/palemoon-bin: Updated for version 34.3.2 > network/palemoon: Updated for version 34.3.2 > network/profanity: Updated for version 0.18.2. > network/proton-vpn-cli: Added (Proton VPN CLI). > network/python3-offlineimap: Added (Sync remote IMAP). > network/radvd: New maintainer > network/rclone-src: Updated for version 1.75.0 > network/s: Updated for version 0.8.1 > network/slakfinder-app: Added (Package explorer). > network/spamassassin: Updated optional dependencies in the README. > network/syncterm: Updated for version 1.8. > network/tailscale: Updated for version 1.102.2 > network/telegram: Updated for version 7.0.7. > network/telegram: Updated for version 7.0.9. > network/tnftp: Updated for version 20260211. > network/vivaldi: Updated for version 8.1.4087.62. > network/webex: Updated for version 46.8.0.33593 > network/zen-browser: Updated for version 1.21.10b > office/SOGo: Updated for version 5.12.9. > office/elyxer: Removed (Unmaintained upstream). > office/fbpdf: Updated for version 20250124_6a0d77f. > office/ledger-live: Updated for version 4.13.1 > office/mupdf: Updated for version 1.28.1. > office/qownnotes: Updated for version 26.8.2. > office/wps-office-dicts: Updated for version 26.8.0.2 > office/zettlr: Updated for version 4.7.0. > perl/cpanminus: Updated for version 1.7049; new maintainer. > perl/perl-B-COW: Updated for version 0.007. > perl/perl-B-Hooks-EndOfScope: Updated for version 0.28 > perl/perl-BerkeleyDB: Updated for version 0.67. > perl/perl-CGI: Orphaned (unmaintained). > perl/perl-CPAN-Perl-Releases: Updated for version 20260803. > perl/perl-Data-UUID: Updated for version 1.227. > perl/perl-Data-Validate-IP: Updated for version 0.31 > perl/perl-File-ShareDir-Install: Updated for version 0.14. > perl/perl-IO-Tty: Updated for version 1.31. > perl/perl-IP-Geolocation-MMDB: Added (Geolocation maxmind). > perl/perl-IPC-Run3: Updated for version 0.049 > perl/perl-Inline-C: Updated for version 0.82. > perl/perl-Inline: Updated for version 0.87. > perl/perl-JSON: Updated for version 4.11. > perl/perl-LWP-Protocol-https: Updated for version 6.17. > perl/perl-MIME-Types: Updated for version 2.30 and changed ARCH to noarch. > perl/perl-Mail-DKIM: Added perl-CryptX as a dependency. > perl/perl-MailTools: Updated for version 2.22. > perl/perl-Math-BigInt-GMP: Updated for version 1.7003. > perl/perl-Math-BigInt: Updated for version 2.005003. > perl/perl-Math-GMPq: Updated for version 0.70. > perl/perl-Math-GMPz: Updated for version 0.69. > perl/perl-Math-MPC: Updated for version 1.43. > perl/perl-Math-MPFR: Updated for version 4.47. > perl/perl-Minion: Added (Job Queue). > perl/perl-Minion: Update dep. > perl/perl-Mozilla-CA: Updated for version 20250602. > perl/perl-Net-IPv6Addr: Updated for version 1.02 > perl/perl-Net-LDAP: Updated for version 0.68. > perl/perl-Net-Server: Updated for version 2.018. > perl/perl-Net-Write: Fix linter. > perl/perl-NetAddr-IP: Added documentation. > perl/perl-Socket6: Fix linter. > perl/perl-Test-Class: Updated for version 0.52 > perl/perl-Test-Fatal: Updated for version 0.018. > perl/perl-Test-File: Updated for version 1.995. > perl/perl-Test-NoWarnings: Updated for version 1.06. > perl/perl-Test-Requires: Updated for version 0.11. > perl/perl-Test-Warnings: Updated for version 0.038. > perl/perl-Test-utf8: Updated for version 1.03. > perl/perl-Text-CSV_XS: Updated for version 1.64 > perl/perl-TimeDate: Updated for version 2.35. > perl/perl-Try-Tiny: Updated for version 0.32. > perl/perl-XML-SAX-Writer: Updated for version 0.57. > perl/perl-YAML-LibYAML: Updated for version 0.910.0. > perl/perl-io-uncompress-brotli: Updated for version 0.022. > perl/perl-test-warn: Updated for version 0.37. > python/feedparser: Updated for version 6.0.14 > python/hgsubversion: Removed (Unmaintained upstream). > python/mock: Orphaned (unmaintained). > python/numexpr: Updated for version 2.14.2 > python/pyOpenSSL: Updated for version 26.4.0. > python/python2-authres: Updated for version 1.2.0. > python/python2-pygame: Fix homepage/download. > python/python2-pytest-runner: Orphaned (unmaintained). > python/python3-argcomplete: Updated for version 3.7.0 > python/python3-cffi: Updated for version 2.1.1. > python/python3-dunamai: Updated for version 1.26.2. > python/python3-fontmake: Updated for version 3.12.1 > python/python3-glyphslib: Updated for version 6.14.0 > python/python3-imaplib2: Added (Python module). > python/python3-json5: Updated for version 0.15.0. > python/python3-keyring: Update dependencies > python/python3-llvmlite: Fix running on llvm13-compat > python/python3-odfdo: Updated for version 3.24.0 > python/python3-proton-keyring-linux: Added (Python proton keyring). > python/python3-pycrypto: Use SLKCFLAGS. > python/python3-pygame: Fix homepage/download. > python/python3-pypdf: Updated for version 6.15.0 > python/python3-reportlab: Updated for version 5.0.0 > python/python3-secretstorage: Added (Python module). > python/python3-shtab: Update for 1.9.3 > python/python3-telethon: Added (Telegram Client Library). > python/python3-ufo2ft: Updated for version 3.9.0 > python/python3-xmldiff: Updated for version 3.0 > python/sqlparse: Orphaned (unmaintained). > system/Lmod: Updated for version 9.3. > system/backintime: New Maintainer > system/basu: Added (sd-bus library). > system/cfengine: Updated for version 3.27.1. > system/cpuid: Fix permissions; new maintainer. > system/dateutils: update to 0.4.11 > system/docker-buildx: Updated for version 0.36.0. > system/docker-buildx: Updated for version 0.36.1. > system/docker-compose: Updated for version 5.4.0 > system/driconf: New maintainer > system/dump: Updated for version 0.4b55. > system/dvdisaster: New maintainer > system/fastfetch: Explain the stopped updates in README. > system/fprintd: New maintainer > system/fswatch: update to 1.22.0 > system/fwupd: Updated for version 2.1.7. > system/fxload: New maintainer > system/fzf: Updated for version 0.74.2. > system/hw-probe: Reworked pacman patch; new maintainer. > system/incus: Updated for version 7.3 > system/jenkins: Updated for version 2.568.2. > system/phpsysinfo: Updated for version 3.4.6 > system/physlock: Updated for version 13. > system/recoverdm: Fix homepage. > system/rng-tools: New maintainer. > system/sbotest: Updated for version 1.3. > system/sbotools: Updated for version 4.4. > system/sdl-jstest: Updated for version 0.2.2+20260729_cf4fab3. > system/sdl2trs: Updated for version 1.2.35+20260517_96d531a4. > system/sdltrs: Updated for version 1.2.35. > system/smbldap-tools: Updated for version 0.9.11. > system/symbola-font-ttf: Avoid writes to /root. > system/targetcli-fb: Updated for version 3.0.2. > system/ttf-nerd-fonts-symbols: Updated for version 3.5.0 > system/uae: New maintainer > system/uhubctl: Updated for version 2.6.0. > system/vagrant: Updated for version 2.4.9 > +--------------------------+ > > > -- > Willy Sudiarto Raharjo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pgcswiss at yandex.com Sat Aug 8 17:15:33 2026 From: pgcswiss at yandex.com (Patrice Coni) Date: Sat, 08 Aug 2026 19:15:33 +0200 Subject: [Slackbuilds-users] SlackBuild - pdfsam-basic Message-ID: <2349383.vFx2qVVIhK@penguin.imac> Dear all I maintained the SlackBuild of pdfsam-basic from December 2024 to present. My circumstances have been changed and i would like to give this package to a new maintainer. Link: https://slackbuilds.org/repository/15.0/office/pdfsam-basic/?search=pdfsam[1] Best regards. -------- [1] https://slackbuilds.org/repository/15.0/office/pdfsam-basic/?search=pdfsam -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Sat Aug 8 17:18:03 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 8 Aug 2026 10:18:03 -0700 Subject: [Slackbuilds-users] Updates - 20260808.1 In-Reply-To: References: <20260808093044.7a6cbaf9@home.slackie.org> Message-ID: Looks like you might have an old version installed along with a newer one. The current proton-vpn-cli version on SBo includes the /usr/bin/protonvpn launcher script, which replaced the older protonvpn-cli script. Try running `protonvpn connect` instead. To figure out what happened, you might want to check what proton packages you have installed or dig to see if you installed any python packages via pip. Jeremy On Sat, Aug 8, 2026, 9:37?AM Luveh Keraph <1.41421 at gmail.com> wrote: > proton-vpn-cli is not working for me: > > $ protonvpn-cli connect > Traceback (most recent call last): > File "/usr/bin/protonvpn-cli", line 6, in > from pkg_resources import load_entry_point > File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", > line 3243, in > def _initialize_master_working_set(): > File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", > line 3226, in _call_aside > f(*args, **kwargs) > File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", > line 3255, in _initialize_master_working_set > working_set = WorkingSet._build_master() > File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", > line 568, in _build_master > ws.require(__requires__) > File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", > line 886, in require > needed = self.resolve(parse_requirements(requirements)) > File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", > line 772, in resolve > raise DistributionNotFound(req, requirers) > pkg_resources.DistributionNotFound: The 'protonvpn-cli==3.13.0' > distribution was not found and is required by the application > > On Fri, Aug 7, 2026 at 8:30?PM Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> Sat Aug 8 02:13:27 UTC 2026 >> academic/calc: Updated for version 2.17.0.0, new maint. >> academic/gtkwave: Updated for version 3.3.128. >> academic/ngspice-jit: Updated for version 46.7. >> academic/octave: Update URL. >> academic/suitesparse: Updated for version 7.12.3 >> academic/yices2: Updated for version 2.7.0. >> academic/zotero-gtk2: Removed (obsolescent, unmaintained). >> audio/asap: Updated for version 8.0.0. >> audio/audacity: Always use wxWidgets-3.2. >> audio/caps: Fix homepage/download. >> audio/drumkv1: Updated for version 1.4.2. >> audio/faust: Updated for version 2.85.9. >> audio/guitarix: Updated for version 0.47.0. >> audio/id3tool: Use correct debian homepage. >> audio/lv2-mda-metapiano: Fix homepage/download URLs. >> audio/mda-lv2: Updated for version 1.2.12. >> audio/muse: New Maintainer >> audio/padthv1: Updated for version 1.4.2. >> audio/portmidi: Updated for version 2.0.8. >> audio/qm-vamp-plugins: Fix download. >> audio/samplv1: Updated for version 1.4.2. >> audio/soundconverter: Updated for version 4.1.3. >> audio/synthv1: Updated for version 1.4.2. >> audio/transcribe: Updated for version 9.60.3. >> audio/tta: New maintainer. >> audio/vmpk: Updated for version 0.9.2. >> audio/wmusic-xmms: Add no-conflict note. >> audio/wmusic: Updated for version 2.1.1. >> desktop/anki: Reverted to version 24.11 to allow building on stable. >> desktop/catfish: Updated for version 4.20.1. >> desktop/devilspie: New maintainer >> desktop/joystickwake: Updated for version 1.0 >> desktop/noice: fix download URL >> desktop/papirus-icon-theme: Updated for version 20260801. >> desktop/river: Update dep. >> desktop/x2x: Updated for version 1.30_beta+20250217_0884251. >> desktop/xfce-hkmon: New maintainer >> desktop/xfce4-datetime-plugin: Updated for version 0.8.3. >> desktop/xfce4-wavelan-plugin: Updated for version 0.7.0. >> development/Catch2: Updated for version 3.15.3 >> development/GHDL: Updated for version 6.0.0. >> development/Kiro: Updated for version 1.0.288. >> development/antigravity-cli: Added (Antigravity CLI). >> development/antigravity-ide: Added (Antigravity CLI). >> development/antigravity2: Updated for version 2.4.3 >> development/asl: Updated for version 142_bld311. >> development/aws-cdk: Updated for version 2.1135.0. >> development/bacon: Updated for version 5.0.4. >> development/bbcsdl: Updated for version 20260801_6c30298 >> development/bmake: Updated for version 20260714. >> development/bruno: Updated for version 4.0.0. >> development/cargo-c: Updated for version 0.10.24 + new maintainer >> development/d-tools: Updated for version 2.112.1 >> development/ddisasm: Fix ccache incompatibility >> development/dkms: Updated for version 3.4.2 >> development/ecl: New Maintainer >> development/electron-bin: Updated for version 43.3.0 >> development/fasm: Updated for version 1.73.35. >> development/gcli: Updated for version 2.13.0. >> development/gitlab-cli: Updated for version 1.111.0. >> development/gitlab-cli: Updated for version 1.112.0. >> development/gnustep-base: Updated for version 1.31.1. >> development/gnustep-make: Updated for version 2.9.3. >> development/hadolint-bin: Updated for version 2.15.1. >> development/hexinator: Add note to self. >> development/hoppscotch: Updated for version 26.7.0. >> development/ieee-pilot: Updated for version 1.12. >> development/jujutsu: Updated for version 0.44.0 >> development/letos: Updated for version 4.0.2 >> development/mlton: Updated for version 20241230. >> development/mongodb-compass: Updated for version 1.49.14. >> development/notepadqq: Updated for version 20260802_37652c5 >> development/nvidia-container-toolkit: Updated for version 1.19.1. >> development/pnpm: Updated for version 11.19.0. >> development/pnpm: Updated for version 11.20.0. >> development/prek: Updated for version 0.4.11. >> development/prek: Updated for version 0.4.12. >> development/rider: Updated for version 2026.2.0.1. >> development/rider: Updated for version 2026.2.0.2. >> development/rust-opt: Add aarch64. >> development/sasm: Updated for version 3.16.0. >> development/sbcl: Updated for version 2.6.7 >> development/sbt: Updated for version 2.0.6 >> development/smartgit: Updated for version 26.1.051 >> development/souffle: improve README >> development/sourcegit: Updated for version 2026.17 >> development/tcc: Updated for version 0.9.28rc+20260730_2be0218b. >> development/tweak: Updated for version 3.02+20251018_29ce537. >> development/typos-lsp: Updated for version 0.1.54. >> development/typos-lsp: Updated for version 0.1.55. >> development/typos: Updated for version 1.49.0. >> development/vif: Fix homepage. >> development/vscode-bin: Updated for version 1.132.0. >> development/vstudio: Updated for version 17.5.3 >> development/zig-bin: Update README. >> development/zig-bin: Updated for version 0.9.1. >> development/zizmor: Updated for version 1.29.0. >> development/zxbasic: Updated for version 1.19.0 >> games/CorsixTH: Updated for version 0.70.0. >> games/OpenRA: Updated for version 20250330 >> games/PrismLauncher-Unlocked: Update MD5SUM. >> games/asteroidsinfinity: Updated for version 1.3. >> games/commandergenius: Updated for version 3.6.3. >> games/cosmic_assault: Fix homepage. >> games/doomseeker: Updated for version 1.5.3. >> games/lmpc: Updated for version 3.5.1. >> games/openyahtzee: Updated for version 1.10. >> games/pentagram: Removed (folded into scummvm). >> games/puzzles: Updated for version 20260720.3c36322. >> games/solarus: Updated for version 2.1.1 >> games/solarwolf: Updated for version 1.6.0. >> games/tint: Updated for version 0.11. >> games/torcs: Updated for version 1.3.9. >> games/trs80gp: Updated for version 2.5.7. >> games/xroar: Updated for version 1.12.1. >> games/xskat: New Source URL. >> games/zork-mit: Add note to self. >> graphics/GraphicsMagick: Fix build w/old version installed. >> graphics/OpenCASCADE: Orphaned (unmaintained). >> graphics/flpsed: Fix download. >> graphics/fontforge: Updated for version 20251009. >> graphics/openscad: Orphaned (unmaintained). >> graphics/psftools: Updated for version 1.1.3. >> graphics/raw-thumbnailer: New maintainer. >> graphics/vips: Updated for version 8.18.5. >> ham/SoapyRemote: Updated for version 0.5.2. >> ham/SoapySDRPlay: New source. >> ham/liquid-dsp: Updated for version 1.8.1. >> libraries/CGAL: Orphaned (unmaintained). >> libraries/CLI11: Updated for version 2.7.1. >> libraries/OpenCSG: Orphaned (unmaintained). >> libraries/SDL3: Updated for version 3.4.14 >> libraries/SOPE: Updated for version 5.12.9. >> libraries/appstream-glib: Updated for version 0.8.4. >> libraries/fcft: update to 3.1.6 >> libraries/fcgi: Orphaned (unmaintained). >> libraries/kddockwidgets: Updated for version 2.4.1. >> libraries/levmar: Orphaned (unmaintained). >> libraries/libcdaudio: New maintainer >> libraries/libdaemon: Orphaned (unmaintained). >> libraries/libfabric: Updated for version 2.6.0 >> libraries/libfprint: New maintainer >> libraries/libopenraw: New maintainer. >> libraries/libxmlb: Updated for version 0.3.29. >> libraries/libyuv: Updated for version 0.0.1949.20260706 >> libraries/onevpl: Version bump to 2.17.0 >> libraries/pjsip: Updated for version 2.17. >> libraries/qt-avif-image-plugin: Updated for version 0.10.4. >> libraries/qt-jpegxl-image-plugin: Updated for version 0.8.4. >> libraries/tclap: Orphaned (unmaintained). >> libraries/vmaf: Updated for version 3.2.0 >> misc/ascii: Updated for version 3.32. >> misc/birthday: Restore old maintainer. >> misc/dejsonlz4: Added (Mozilla bookmarks backup decompressor). >> misc/dmg2img: Update maintainer. >> misc/es40: Updated for version 0.79.5 >> misc/figlet: Fix comment. >> misc/font-unscii: Add -j1 to make. >> misc/modprobed-db: Updated for version 2.50. >> misc/rsnapshot: Updated for version 1.5.1. >> misc/tinytldr: Updated for version 2.0.0 >> multimedia/cfourcc: Updated for version 0.1.5. >> multimedia/devedeng: Updated for version 4.18.0 >> multimedia/gst-plugins-bad-nonfree: Fix spandsp conflict. >> multimedia/opera-ffmpeg-codecs: Updated for version 43.3.0 >> multimedia/rav1e: Updated to version 0.8.1 >> multimedia/svt-av1: Updated for version 4.2.0 >> multimedia/vapoursynth-mvtools: orphaned >> multimedia/vapoursynth: orphaned >> multimedia/vobcopy: New maintainer >> multimedia/x265: Updated for version 4.3. >> multimedia/xawtv: New maintainer >> network/3proxy: Updated for version 0.9.8. >> network/GeoIP: Orphaned (unmaintained). >> network/amavisd-new: New maintainer. >> network/amneziawg-go: Updated for version 3.0.20260805. >> network/amneziawg-kernel: Updated for version 3.0.20260805. >> network/amneziawg-tools: Updated for version 3.0.20260805. >> network/ani-cli: Updated for version 5.0 >> network/asterisk: Updated for version 22.10.1. >> network/basilisk-bin: Updated for version 2026.06.12 >> network/bitlbee: Updated for version 3.6 >> network/brave-browser: Updated for version 1.93.134 >> network/brave-origin: Updated for version 1.93.134 >> network/clamav-unofficial-sigs: New maintainer. >> network/dropbox: Updated for version 264.4.3385. >> network/element-desktop-bin: Updated for version 1.12.25. >> network/element-desktop: Updated for version 1.12.25. >> network/franz: Updated for version 6.5.3. >> network/gallery-dl: Updated for version 1.32.9 >> network/helium-browser: Updated for version 0.15.1.1 >> network/httping: Updated for version 1.4.4, new maintainer. >> network/hylafax+: Updated for version 7.0.11. >> network/jitsi-meet-desktop: Updated for version 2026.8.0 >> network/keepalived: Updated for version 2.4.3. >> network/librewolf: Updated for version 153.0.1_1 >> network/memcached: Updated for version 1.6.45. >> network/metasploit-framework-bin: Updated for version 6.5.1. >> network/microsoft-edge: Updated for version 151.0.4129.59. >> network/milter-greylist: Updated for version 4.6.4. >> network/mpop: Updated for version 1.4.23 >> network/msmtp: Updated for version 1.8.34 >> network/netavark: Updated for version 2.0.0 >> network/newsraft: Updated for version 0.37 >> network/noip2: New maintainer >> network/offlineimap: New maintainer >> network/openconnect: Updated for version 9.21. >> network/opera: Updated for version 134.0.5954.31 >> network/p0f: New maintainer. >> network/palemoon-bin: Updated for version 34.3.2 >> network/palemoon: Updated for version 34.3.2 >> network/profanity: Updated for version 0.18.2. >> network/proton-vpn-cli: Added (Proton VPN CLI). >> network/python3-offlineimap: Added (Sync remote IMAP). >> network/radvd: New maintainer >> network/rclone-src: Updated for version 1.75.0 >> network/s: Updated for version 0.8.1 >> network/slakfinder-app: Added (Package explorer). >> network/spamassassin: Updated optional dependencies in the README. >> network/syncterm: Updated for version 1.8. >> network/tailscale: Updated for version 1.102.2 >> network/telegram: Updated for version 7.0.7. >> network/telegram: Updated for version 7.0.9. >> network/tnftp: Updated for version 20260211. >> network/vivaldi: Updated for version 8.1.4087.62. >> network/webex: Updated for version 46.8.0.33593 >> network/zen-browser: Updated for version 1.21.10b >> office/SOGo: Updated for version 5.12.9. >> office/elyxer: Removed (Unmaintained upstream). >> office/fbpdf: Updated for version 20250124_6a0d77f. >> office/ledger-live: Updated for version 4.13.1 >> office/mupdf: Updated for version 1.28.1. >> office/qownnotes: Updated for version 26.8.2. >> office/wps-office-dicts: Updated for version 26.8.0.2 >> office/zettlr: Updated for version 4.7.0. >> perl/cpanminus: Updated for version 1.7049; new maintainer. >> perl/perl-B-COW: Updated for version 0.007. >> perl/perl-B-Hooks-EndOfScope: Updated for version 0.28 >> perl/perl-BerkeleyDB: Updated for version 0.67. >> perl/perl-CGI: Orphaned (unmaintained). >> perl/perl-CPAN-Perl-Releases: Updated for version 20260803. >> perl/perl-Data-UUID: Updated for version 1.227. >> perl/perl-Data-Validate-IP: Updated for version 0.31 >> perl/perl-File-ShareDir-Install: Updated for version 0.14. >> perl/perl-IO-Tty: Updated for version 1.31. >> perl/perl-IP-Geolocation-MMDB: Added (Geolocation maxmind). >> perl/perl-IPC-Run3: Updated for version 0.049 >> perl/perl-Inline-C: Updated for version 0.82. >> perl/perl-Inline: Updated for version 0.87. >> perl/perl-JSON: Updated for version 4.11. >> perl/perl-LWP-Protocol-https: Updated for version 6.17. >> perl/perl-MIME-Types: Updated for version 2.30 and changed ARCH to noarch. >> perl/perl-Mail-DKIM: Added perl-CryptX as a dependency. >> perl/perl-MailTools: Updated for version 2.22. >> perl/perl-Math-BigInt-GMP: Updated for version 1.7003. >> perl/perl-Math-BigInt: Updated for version 2.005003. >> perl/perl-Math-GMPq: Updated for version 0.70. >> perl/perl-Math-GMPz: Updated for version 0.69. >> perl/perl-Math-MPC: Updated for version 1.43. >> perl/perl-Math-MPFR: Updated for version 4.47. >> perl/perl-Minion: Added (Job Queue). >> perl/perl-Minion: Update dep. >> perl/perl-Mozilla-CA: Updated for version 20250602. >> perl/perl-Net-IPv6Addr: Updated for version 1.02 >> perl/perl-Net-LDAP: Updated for version 0.68. >> perl/perl-Net-Server: Updated for version 2.018. >> perl/perl-Net-Write: Fix linter. >> perl/perl-NetAddr-IP: Added documentation. >> perl/perl-Socket6: Fix linter. >> perl/perl-Test-Class: Updated for version 0.52 >> perl/perl-Test-Fatal: Updated for version 0.018. >> perl/perl-Test-File: Updated for version 1.995. >> perl/perl-Test-NoWarnings: Updated for version 1.06. >> perl/perl-Test-Requires: Updated for version 0.11. >> perl/perl-Test-Warnings: Updated for version 0.038. >> perl/perl-Test-utf8: Updated for version 1.03. >> perl/perl-Text-CSV_XS: Updated for version 1.64 >> perl/perl-TimeDate: Updated for version 2.35. >> perl/perl-Try-Tiny: Updated for version 0.32. >> perl/perl-XML-SAX-Writer: Updated for version 0.57. >> perl/perl-YAML-LibYAML: Updated for version 0.910.0. >> perl/perl-io-uncompress-brotli: Updated for version 0.022. >> perl/perl-test-warn: Updated for version 0.37. >> python/feedparser: Updated for version 6.0.14 >> python/hgsubversion: Removed (Unmaintained upstream). >> python/mock: Orphaned (unmaintained). >> python/numexpr: Updated for version 2.14.2 >> python/pyOpenSSL: Updated for version 26.4.0. >> python/python2-authres: Updated for version 1.2.0. >> python/python2-pygame: Fix homepage/download. >> python/python2-pytest-runner: Orphaned (unmaintained). >> python/python3-argcomplete: Updated for version 3.7.0 >> python/python3-cffi: Updated for version 2.1.1. >> python/python3-dunamai: Updated for version 1.26.2. >> python/python3-fontmake: Updated for version 3.12.1 >> python/python3-glyphslib: Updated for version 6.14.0 >> python/python3-imaplib2: Added (Python module). >> python/python3-json5: Updated for version 0.15.0. >> python/python3-keyring: Update dependencies >> python/python3-llvmlite: Fix running on llvm13-compat >> python/python3-odfdo: Updated for version 3.24.0 >> python/python3-proton-keyring-linux: Added (Python proton keyring). >> python/python3-pycrypto: Use SLKCFLAGS. >> python/python3-pygame: Fix homepage/download. >> python/python3-pypdf: Updated for version 6.15.0 >> python/python3-reportlab: Updated for version 5.0.0 >> python/python3-secretstorage: Added (Python module). >> python/python3-shtab: Update for 1.9.3 >> python/python3-telethon: Added (Telegram Client Library). >> python/python3-ufo2ft: Updated for version 3.9.0 >> python/python3-xmldiff: Updated for version 3.0 >> python/sqlparse: Orphaned (unmaintained). >> system/Lmod: Updated for version 9.3. >> system/backintime: New Maintainer >> system/basu: Added (sd-bus library). >> system/cfengine: Updated for version 3.27.1. >> system/cpuid: Fix permissions; new maintainer. >> system/dateutils: update to 0.4.11 >> system/docker-buildx: Updated for version 0.36.0. >> system/docker-buildx: Updated for version 0.36.1. >> system/docker-compose: Updated for version 5.4.0 >> system/driconf: New maintainer >> system/dump: Updated for version 0.4b55. >> system/dvdisaster: New maintainer >> system/fastfetch: Explain the stopped updates in README. >> system/fprintd: New maintainer >> system/fswatch: update to 1.22.0 >> system/fwupd: Updated for version 2.1.7. >> system/fxload: New maintainer >> system/fzf: Updated for version 0.74.2. >> system/hw-probe: Reworked pacman patch; new maintainer. >> system/incus: Updated for version 7.3 >> system/jenkins: Updated for version 2.568.2. >> system/phpsysinfo: Updated for version 3.4.6 >> system/physlock: Updated for version 13. >> system/recoverdm: Fix homepage. >> system/rng-tools: New maintainer. >> system/sbotest: Updated for version 1.3. >> system/sbotools: Updated for version 4.4. >> system/sdl-jstest: Updated for version 0.2.2+20260729_cf4fab3. >> system/sdl2trs: Updated for version 1.2.35+20260517_96d531a4. >> system/sdltrs: Updated for version 1.2.35. >> system/smbldap-tools: Updated for version 0.9.11. >> system/symbola-font-ttf: Avoid writes to /root. >> system/targetcli-fb: Updated for version 3.0.2. >> system/ttf-nerd-fonts-symbols: Updated for version 3.5.0 >> system/uae: New maintainer >> system/uhubctl: Updated for version 2.6.0. >> system/vagrant: Updated for version 2.4.9 >> +--------------------------+ >> >> >> -- >> Willy Sudiarto Raharjo >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> _______________________________________________ > 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 roberto.puzzanghera at sagredo.eu Sat Aug 8 19:27:13 2026 From: roberto.puzzanghera at sagredo.eu (Roberto Puzzanghera) Date: Sat, 8 Aug 2026 21:27:13 +0200 Subject: [Slackbuilds-users] SlackBuild - pdfsam-basic In-Reply-To: <2349383.vFx2qVVIhK@penguin.imac> References: <2349383.vFx2qVVIhK@penguin.imac> Message-ID: <76970cce-dbeb-4d91-8702-0cbfdd4efc52@sagredo.eu> I can take it -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sat Aug 8 20:03:27 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 8 Aug 2026 14:03:27 -0600 Subject: [Slackbuilds-users] Updates - 20260808.1 In-Reply-To: References: <20260808093044.7a6cbaf9@home.slackie.org> Message-ID: I had indeed an older version installed. I removed it, and also the protonvpn packages resulting from building proton-vpn-cli, and still no cigar. To make sure that nothing to do with ProtonVPN was messing with me, I installed proton-vpn-cli in a different 15.0 system in which there was no ProtonVPN stuff already installed (I triple checked that) using sbopkg -ki proton-vpn-cli.sqf. As before, this installed a bunch of Python 3-related packages, plus the ProtonVPN packages explicitly to do with ProtonVPN. Here's what I am getting now: $ protonvpn connect \Traceback (most recent call last): File "/usr/bin/protonvpn", line 33, in sys.exit(load_entry_point('proton-vpn-cli==1.0.2', 'console_scripts', 'protonvpn')()) File "/usr/bin/protonvpn", line 25, in importlib_load_entry_point return next(matches).load() File "/usr/lib64/python3.9/importlib/metadata.py", line 86, in load module = import_module(match.group('module')) File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 850, in exec_module File "", line 228, in _call_with_frames_removed File "/usr/lib64/python3.9/site-packages/proton/vpn/cli/__init__.py", line 31, in from proton.vpn.cli._cli_constants import \ File "/usr/lib64/python3.9/site-packages/proton/vpn/cli/_cli_constants.py", line 29, in LOGGING_DIR_PATH = os.path.join(VPNExecutionEnvironment().path_cache, "logs") File "/usr/lib64/python3.9/site-packages/proton/utils/metaclasses.py", line 25, in __call__ cls._instances[cls] = super(Singleton, cls).__call__(*args, **kwargs) File "/usr/lib64/python3.9/site-packages/proton/utils/environment.py", line 116, in __init__ super().__init__() File "/usr/lib64/python3.9/site-packages/proton/utils/environment.py", line 38, in __init__ self._setup_as_regular_user() File "/usr/lib64/python3.9/site-packages/proton/utils/environment.py", line 78, in _setup_as_regular_user config_home, cache_home, runtime_dir = self._get_dir_paths() File "/usr/lib64/python3.9/site-packages/proton/utils/environment.py", line 91, in _get_dir_paths runtime_dir = BaseDirectory.get_runtime_dir() File "/usr/lib64/python3.9/site-packages/xdg/BaseDirectory.py", line 127, in get_runtime_dir return os.environ['XDG_RUNTIME_DIR'] File "/usr/lib64/python3.9/os.py", line 679, in __getitem__ raise KeyError(key) from None KeyError: 'XDG_RUNTIME_DIR' That from my own account. As root: # protonvpn connect An unexpected error occurred. Please try again. If the error persists please contact customer support: https://protonvpn.com/support/contact?subject=%5BCLI%5D&os=Linux&platform=VPN%20for%20Linux Traceback (most recent call last): File "/usr/bin/protonvpn", line 33, in sys.exit(load_entry_point('proton-vpn-cli==1.0.2', 'console_scripts', 'protonvpn')()) File "/usr/lib64/python3.9/site-packages/proton/vpn/cli/__init__.py", line 170, in main app( File "/usr/lib64/python3.9/site-packages/click/core.py", line 1161, in __call__ return self.main(*args, **kwargs) File "/usr/lib64/python3.9/site-packages/click/core.py", line 1082, in main rv = self.invoke(ctx) File "/usr/lib64/python3.9/site-packages/click/core.py", line 1694, in invoke super().invoke(ctx) File "/usr/lib64/python3.9/site-packages/click/core.py", line 1443, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib64/python3.9/site-packages/click/core.py", line 788, in invoke return __callback(*args, **kwargs) File "/usr/lib64/python3.9/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/lib64/python3.9/site-packages/proton/vpn/cli/core/run_async.py", line 31, in wrapper return asyncio.run(func(*args, **kwargs)) File "/usr/lib64/python3.9/asyncio/runners.py", line 44, in run return loop.run_until_complete(main) File "/usr/lib64/python3.9/asyncio/base_events.py", line 647, in run_until_complete return future.result() File "/usr/lib64/python3.9/site-packages/proton/vpn/cli/__init__.py", line 135, in app vpn_gui_running = await _vpn_gui_running() File "/usr/lib64/python3.9/site-packages/proton/vpn/cli/__init__.py", line 63, in _vpn_gui_running bus = await MessageBus(bus_type=BusType.SESSION).connect() File "/usr/lib64/python3.9/site-packages/dbus_fast/aio/message_bus.py", line 206, in __init__ super().__init__(bus_address, bus_type, ProxyObject, negotiate_unix_fd) File "/usr/lib64/python3.9/site-packages/dbus_fast/message_bus.py", line 171, in __init__ self._setup_socket() File "/usr/lib64/python3.9/site-packages/dbus_fast/message_bus.py", line 725, in _setup_socket raise err File "/usr/lib64/python3.9/site-packages/dbus_fast/message_bus.py", line 698, in _setup_socket self._sock.connect(filename) ConnectionRefusedError: [Errno 111] Connection refused On Sat, Aug 8, 2026 at 11:18?AM Jeremy Hansen wrote: > Looks like you might have an old version installed along with a newer one. > > The current proton-vpn-cli version on SBo includes the /usr/bin/protonvpn > launcher script, which replaced the older protonvpn-cli script. > > Try running `protonvpn connect` instead. > > To figure out what happened, you might want to check what proton packages > you have installed or dig to see if you installed any python packages via > pip. > > Jeremy > > On Sat, Aug 8, 2026, 9:37?AM Luveh Keraph <1.41421 at gmail.com> wrote: > >> proton-vpn-cli is not working for me: >> >> $ protonvpn-cli connect >> Traceback (most recent call last): >> File "/usr/bin/protonvpn-cli", line 6, in >> from pkg_resources import load_entry_point >> File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", >> line 3243, in >> def _initialize_master_working_set(): >> File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", >> line 3226, in _call_aside >> f(*args, **kwargs) >> File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", >> line 3255, in _initialize_master_working_set >> working_set = WorkingSet._build_master() >> File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", >> line 568, in _build_master >> ws.require(__requires__) >> File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", >> line 886, in require >> needed = self.resolve(parse_requirements(requirements)) >> File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", >> line 772, in resolve >> raise DistributionNotFound(req, requirers) >> pkg_resources.DistributionNotFound: The 'protonvpn-cli==3.13.0' >> distribution was not found and is required by the application >> >> On Fri, Aug 7, 2026 at 8:30?PM Willy Sudiarto Raharjo < >> willysr at slackbuilds.org> wrote: >> >>> Sat Aug 8 02:13:27 UTC 2026 >>> academic/calc: Updated for version 2.17.0.0, new maint. >>> academic/gtkwave: Updated for version 3.3.128. >>> academic/ngspice-jit: Updated for version 46.7. >>> academic/octave: Update URL. >>> academic/suitesparse: Updated for version 7.12.3 >>> academic/yices2: Updated for version 2.7.0. >>> academic/zotero-gtk2: Removed (obsolescent, unmaintained). >>> audio/asap: Updated for version 8.0.0. >>> audio/audacity: Always use wxWidgets-3.2. >>> audio/caps: Fix homepage/download. >>> audio/drumkv1: Updated for version 1.4.2. >>> audio/faust: Updated for version 2.85.9. >>> audio/guitarix: Updated for version 0.47.0. >>> audio/id3tool: Use correct debian homepage. >>> audio/lv2-mda-metapiano: Fix homepage/download URLs. >>> audio/mda-lv2: Updated for version 1.2.12. >>> audio/muse: New Maintainer >>> audio/padthv1: Updated for version 1.4.2. >>> audio/portmidi: Updated for version 2.0.8. >>> audio/qm-vamp-plugins: Fix download. >>> audio/samplv1: Updated for version 1.4.2. >>> audio/soundconverter: Updated for version 4.1.3. >>> audio/synthv1: Updated for version 1.4.2. >>> audio/transcribe: Updated for version 9.60.3. >>> audio/tta: New maintainer. >>> audio/vmpk: Updated for version 0.9.2. >>> audio/wmusic-xmms: Add no-conflict note. >>> audio/wmusic: Updated for version 2.1.1. >>> desktop/anki: Reverted to version 24.11 to allow building on stable. >>> desktop/catfish: Updated for version 4.20.1. >>> desktop/devilspie: New maintainer >>> desktop/joystickwake: Updated for version 1.0 >>> desktop/noice: fix download URL >>> desktop/papirus-icon-theme: Updated for version 20260801. >>> desktop/river: Update dep. >>> desktop/x2x: Updated for version 1.30_beta+20250217_0884251. >>> desktop/xfce-hkmon: New maintainer >>> desktop/xfce4-datetime-plugin: Updated for version 0.8.3. >>> desktop/xfce4-wavelan-plugin: Updated for version 0.7.0. >>> development/Catch2: Updated for version 3.15.3 >>> development/GHDL: Updated for version 6.0.0. >>> development/Kiro: Updated for version 1.0.288. >>> development/antigravity-cli: Added (Antigravity CLI). >>> development/antigravity-ide: Added (Antigravity CLI). >>> development/antigravity2: Updated for version 2.4.3 >>> development/asl: Updated for version 142_bld311. >>> development/aws-cdk: Updated for version 2.1135.0. >>> development/bacon: Updated for version 5.0.4. >>> development/bbcsdl: Updated for version 20260801_6c30298 >>> development/bmake: Updated for version 20260714. >>> development/bruno: Updated for version 4.0.0. >>> development/cargo-c: Updated for version 0.10.24 + new maintainer >>> development/d-tools: Updated for version 2.112.1 >>> development/ddisasm: Fix ccache incompatibility >>> development/dkms: Updated for version 3.4.2 >>> development/ecl: New Maintainer >>> development/electron-bin: Updated for version 43.3.0 >>> development/fasm: Updated for version 1.73.35. >>> development/gcli: Updated for version 2.13.0. >>> development/gitlab-cli: Updated for version 1.111.0. >>> development/gitlab-cli: Updated for version 1.112.0. >>> development/gnustep-base: Updated for version 1.31.1. >>> development/gnustep-make: Updated for version 2.9.3. >>> development/hadolint-bin: Updated for version 2.15.1. >>> development/hexinator: Add note to self. >>> development/hoppscotch: Updated for version 26.7.0. >>> development/ieee-pilot: Updated for version 1.12. >>> development/jujutsu: Updated for version 0.44.0 >>> development/letos: Updated for version 4.0.2 >>> development/mlton: Updated for version 20241230. >>> development/mongodb-compass: Updated for version 1.49.14. >>> development/notepadqq: Updated for version 20260802_37652c5 >>> development/nvidia-container-toolkit: Updated for version 1.19.1. >>> development/pnpm: Updated for version 11.19.0. >>> development/pnpm: Updated for version 11.20.0. >>> development/prek: Updated for version 0.4.11. >>> development/prek: Updated for version 0.4.12. >>> development/rider: Updated for version 2026.2.0.1. >>> development/rider: Updated for version 2026.2.0.2. >>> development/rust-opt: Add aarch64. >>> development/sasm: Updated for version 3.16.0. >>> development/sbcl: Updated for version 2.6.7 >>> development/sbt: Updated for version 2.0.6 >>> development/smartgit: Updated for version 26.1.051 >>> development/souffle: improve README >>> development/sourcegit: Updated for version 2026.17 >>> development/tcc: Updated for version 0.9.28rc+20260730_2be0218b. >>> development/tweak: Updated for version 3.02+20251018_29ce537. >>> development/typos-lsp: Updated for version 0.1.54. >>> development/typos-lsp: Updated for version 0.1.55. >>> development/typos: Updated for version 1.49.0. >>> development/vif: Fix homepage. >>> development/vscode-bin: Updated for version 1.132.0. >>> development/vstudio: Updated for version 17.5.3 >>> development/zig-bin: Update README. >>> development/zig-bin: Updated for version 0.9.1. >>> development/zizmor: Updated for version 1.29.0. >>> development/zxbasic: Updated for version 1.19.0 >>> games/CorsixTH: Updated for version 0.70.0. >>> games/OpenRA: Updated for version 20250330 >>> games/PrismLauncher-Unlocked: Update MD5SUM. >>> games/asteroidsinfinity: Updated for version 1.3. >>> games/commandergenius: Updated for version 3.6.3. >>> games/cosmic_assault: Fix homepage. >>> games/doomseeker: Updated for version 1.5.3. >>> games/lmpc: Updated for version 3.5.1. >>> games/openyahtzee: Updated for version 1.10. >>> games/pentagram: Removed (folded into scummvm). >>> games/puzzles: Updated for version 20260720.3c36322. >>> games/solarus: Updated for version 2.1.1 >>> games/solarwolf: Updated for version 1.6.0. >>> games/tint: Updated for version 0.11. >>> games/torcs: Updated for version 1.3.9. >>> games/trs80gp: Updated for version 2.5.7. >>> games/xroar: Updated for version 1.12.1. >>> games/xskat: New Source URL. >>> games/zork-mit: Add note to self. >>> graphics/GraphicsMagick: Fix build w/old version installed. >>> graphics/OpenCASCADE: Orphaned (unmaintained). >>> graphics/flpsed: Fix download. >>> graphics/fontforge: Updated for version 20251009. >>> graphics/openscad: Orphaned (unmaintained). >>> graphics/psftools: Updated for version 1.1.3. >>> graphics/raw-thumbnailer: New maintainer. >>> graphics/vips: Updated for version 8.18.5. >>> ham/SoapyRemote: Updated for version 0.5.2. >>> ham/SoapySDRPlay: New source. >>> ham/liquid-dsp: Updated for version 1.8.1. >>> libraries/CGAL: Orphaned (unmaintained). >>> libraries/CLI11: Updated for version 2.7.1. >>> libraries/OpenCSG: Orphaned (unmaintained). >>> libraries/SDL3: Updated for version 3.4.14 >>> libraries/SOPE: Updated for version 5.12.9. >>> libraries/appstream-glib: Updated for version 0.8.4. >>> libraries/fcft: update to 3.1.6 >>> libraries/fcgi: Orphaned (unmaintained). >>> libraries/kddockwidgets: Updated for version 2.4.1. >>> libraries/levmar: Orphaned (unmaintained). >>> libraries/libcdaudio: New maintainer >>> libraries/libdaemon: Orphaned (unmaintained). >>> libraries/libfabric: Updated for version 2.6.0 >>> libraries/libfprint: New maintainer >>> libraries/libopenraw: New maintainer. >>> libraries/libxmlb: Updated for version 0.3.29. >>> libraries/libyuv: Updated for version 0.0.1949.20260706 >>> libraries/onevpl: Version bump to 2.17.0 >>> libraries/pjsip: Updated for version 2.17. >>> libraries/qt-avif-image-plugin: Updated for version 0.10.4. >>> libraries/qt-jpegxl-image-plugin: Updated for version 0.8.4. >>> libraries/tclap: Orphaned (unmaintained). >>> libraries/vmaf: Updated for version 3.2.0 >>> misc/ascii: Updated for version 3.32. >>> misc/birthday: Restore old maintainer. >>> misc/dejsonlz4: Added (Mozilla bookmarks backup decompressor). >>> misc/dmg2img: Update maintainer. >>> misc/es40: Updated for version 0.79.5 >>> misc/figlet: Fix comment. >>> misc/font-unscii: Add -j1 to make. >>> misc/modprobed-db: Updated for version 2.50. >>> misc/rsnapshot: Updated for version 1.5.1. >>> misc/tinytldr: Updated for version 2.0.0 >>> multimedia/cfourcc: Updated for version 0.1.5. >>> multimedia/devedeng: Updated for version 4.18.0 >>> multimedia/gst-plugins-bad-nonfree: Fix spandsp conflict. >>> multimedia/opera-ffmpeg-codecs: Updated for version 43.3.0 >>> multimedia/rav1e: Updated to version 0.8.1 >>> multimedia/svt-av1: Updated for version 4.2.0 >>> multimedia/vapoursynth-mvtools: orphaned >>> multimedia/vapoursynth: orphaned >>> multimedia/vobcopy: New maintainer >>> multimedia/x265: Updated for version 4.3. >>> multimedia/xawtv: New maintainer >>> network/3proxy: Updated for version 0.9.8. >>> network/GeoIP: Orphaned (unmaintained). >>> network/amavisd-new: New maintainer. >>> network/amneziawg-go: Updated for version 3.0.20260805. >>> network/amneziawg-kernel: Updated for version 3.0.20260805. >>> network/amneziawg-tools: Updated for version 3.0.20260805. >>> network/ani-cli: Updated for version 5.0 >>> network/asterisk: Updated for version 22.10.1. >>> network/basilisk-bin: Updated for version 2026.06.12 >>> network/bitlbee: Updated for version 3.6 >>> network/brave-browser: Updated for version 1.93.134 >>> network/brave-origin: Updated for version 1.93.134 >>> network/clamav-unofficial-sigs: New maintainer. >>> network/dropbox: Updated for version 264.4.3385. >>> network/element-desktop-bin: Updated for version 1.12.25. >>> network/element-desktop: Updated for version 1.12.25. >>> network/franz: Updated for version 6.5.3. >>> network/gallery-dl: Updated for version 1.32.9 >>> network/helium-browser: Updated for version 0.15.1.1 >>> network/httping: Updated for version 1.4.4, new maintainer. >>> network/hylafax+: Updated for version 7.0.11. >>> network/jitsi-meet-desktop: Updated for version 2026.8.0 >>> network/keepalived: Updated for version 2.4.3. >>> network/librewolf: Updated for version 153.0.1_1 >>> network/memcached: Updated for version 1.6.45. >>> network/metasploit-framework-bin: Updated for version 6.5.1. >>> network/microsoft-edge: Updated for version 151.0.4129.59. >>> network/milter-greylist: Updated for version 4.6.4. >>> network/mpop: Updated for version 1.4.23 >>> network/msmtp: Updated for version 1.8.34 >>> network/netavark: Updated for version 2.0.0 >>> network/newsraft: Updated for version 0.37 >>> network/noip2: New maintainer >>> network/offlineimap: New maintainer >>> network/openconnect: Updated for version 9.21. >>> network/opera: Updated for version 134.0.5954.31 >>> network/p0f: New maintainer. >>> network/palemoon-bin: Updated for version 34.3.2 >>> network/palemoon: Updated for version 34.3.2 >>> network/profanity: Updated for version 0.18.2. >>> network/proton-vpn-cli: Added (Proton VPN CLI). >>> network/python3-offlineimap: Added (Sync remote IMAP). >>> network/radvd: New maintainer >>> network/rclone-src: Updated for version 1.75.0 >>> network/s: Updated for version 0.8.1 >>> network/slakfinder-app: Added (Package explorer). >>> network/spamassassin: Updated optional dependencies in the README. >>> network/syncterm: Updated for version 1.8. >>> network/tailscale: Updated for version 1.102.2 >>> network/telegram: Updated for version 7.0.7. >>> network/telegram: Updated for version 7.0.9. >>> network/tnftp: Updated for version 20260211. >>> network/vivaldi: Updated for version 8.1.4087.62. >>> network/webex: Updated for version 46.8.0.33593 >>> network/zen-browser: Updated for version 1.21.10b >>> office/SOGo: Updated for version 5.12.9. >>> office/elyxer: Removed (Unmaintained upstream). >>> office/fbpdf: Updated for version 20250124_6a0d77f. >>> office/ledger-live: Updated for version 4.13.1 >>> office/mupdf: Updated for version 1.28.1. >>> office/qownnotes: Updated for version 26.8.2. >>> office/wps-office-dicts: Updated for version 26.8.0.2 >>> office/zettlr: Updated for version 4.7.0. >>> perl/cpanminus: Updated for version 1.7049; new maintainer. >>> perl/perl-B-COW: Updated for version 0.007. >>> perl/perl-B-Hooks-EndOfScope: Updated for version 0.28 >>> perl/perl-BerkeleyDB: Updated for version 0.67. >>> perl/perl-CGI: Orphaned (unmaintained). >>> perl/perl-CPAN-Perl-Releases: Updated for version 20260803. >>> perl/perl-Data-UUID: Updated for version 1.227. >>> perl/perl-Data-Validate-IP: Updated for version 0.31 >>> perl/perl-File-ShareDir-Install: Updated for version 0.14. >>> perl/perl-IO-Tty: Updated for version 1.31. >>> perl/perl-IP-Geolocation-MMDB: Added (Geolocation maxmind). >>> perl/perl-IPC-Run3: Updated for version 0.049 >>> perl/perl-Inline-C: Updated for version 0.82. >>> perl/perl-Inline: Updated for version 0.87. >>> perl/perl-JSON: Updated for version 4.11. >>> perl/perl-LWP-Protocol-https: Updated for version 6.17. >>> perl/perl-MIME-Types: Updated for version 2.30 and changed ARCH to >>> noarch. >>> perl/perl-Mail-DKIM: Added perl-CryptX as a dependency. >>> perl/perl-MailTools: Updated for version 2.22. >>> perl/perl-Math-BigInt-GMP: Updated for version 1.7003. >>> perl/perl-Math-BigInt: Updated for version 2.005003. >>> perl/perl-Math-GMPq: Updated for version 0.70. >>> perl/perl-Math-GMPz: Updated for version 0.69. >>> perl/perl-Math-MPC: Updated for version 1.43. >>> perl/perl-Math-MPFR: Updated for version 4.47. >>> perl/perl-Minion: Added (Job Queue). >>> perl/perl-Minion: Update dep. >>> perl/perl-Mozilla-CA: Updated for version 20250602. >>> perl/perl-Net-IPv6Addr: Updated for version 1.02 >>> perl/perl-Net-LDAP: Updated for version 0.68. >>> perl/perl-Net-Server: Updated for version 2.018. >>> perl/perl-Net-Write: Fix linter. >>> perl/perl-NetAddr-IP: Added documentation. >>> perl/perl-Socket6: Fix linter. >>> perl/perl-Test-Class: Updated for version 0.52 >>> perl/perl-Test-Fatal: Updated for version 0.018. >>> perl/perl-Test-File: Updated for version 1.995. >>> perl/perl-Test-NoWarnings: Updated for version 1.06. >>> perl/perl-Test-Requires: Updated for version 0.11. >>> perl/perl-Test-Warnings: Updated for version 0.038. >>> perl/perl-Test-utf8: Updated for version 1.03. >>> perl/perl-Text-CSV_XS: Updated for version 1.64 >>> perl/perl-TimeDate: Updated for version 2.35. >>> perl/perl-Try-Tiny: Updated for version 0.32. >>> perl/perl-XML-SAX-Writer: Updated for version 0.57. >>> perl/perl-YAML-LibYAML: Updated for version 0.910.0. >>> perl/perl-io-uncompress-brotli: Updated for version 0.022. >>> perl/perl-test-warn: Updated for version 0.37. >>> python/feedparser: Updated for version 6.0.14 >>> python/hgsubversion: Removed (Unmaintained upstream). >>> python/mock: Orphaned (unmaintained). >>> python/numexpr: Updated for version 2.14.2 >>> python/pyOpenSSL: Updated for version 26.4.0. >>> python/python2-authres: Updated for version 1.2.0. >>> python/python2-pygame: Fix homepage/download. >>> python/python2-pytest-runner: Orphaned (unmaintained). >>> python/python3-argcomplete: Updated for version 3.7.0 >>> python/python3-cffi: Updated for version 2.1.1. >>> python/python3-dunamai: Updated for version 1.26.2. >>> python/python3-fontmake: Updated for version 3.12.1 >>> python/python3-glyphslib: Updated for version 6.14.0 >>> python/python3-imaplib2: Added (Python module). >>> python/python3-json5: Updated for version 0.15.0. >>> python/python3-keyring: Update dependencies >>> python/python3-llvmlite: Fix running on llvm13-compat >>> python/python3-odfdo: Updated for version 3.24.0 >>> python/python3-proton-keyring-linux: Added (Python proton keyring). >>> python/python3-pycrypto: Use SLKCFLAGS. >>> python/python3-pygame: Fix homepage/download. >>> python/python3-pypdf: Updated for version 6.15.0 >>> python/python3-reportlab: Updated for version 5.0.0 >>> python/python3-secretstorage: Added (Python module). >>> python/python3-shtab: Update for 1.9.3 >>> python/python3-telethon: Added (Telegram Client Library). >>> python/python3-ufo2ft: Updated for version 3.9.0 >>> python/python3-xmldiff: Updated for version 3.0 >>> python/sqlparse: Orphaned (unmaintained). >>> system/Lmod: Updated for version 9.3. >>> system/backintime: New Maintainer >>> system/basu: Added (sd-bus library). >>> system/cfengine: Updated for version 3.27.1. >>> system/cpuid: Fix permissions; new maintainer. >>> system/dateutils: update to 0.4.11 >>> system/docker-buildx: Updated for version 0.36.0. >>> system/docker-buildx: Updated for version 0.36.1. >>> system/docker-compose: Updated for version 5.4.0 >>> system/driconf: New maintainer >>> system/dump: Updated for version 0.4b55. >>> system/dvdisaster: New maintainer >>> system/fastfetch: Explain the stopped updates in README. >>> system/fprintd: New maintainer >>> system/fswatch: update to 1.22.0 >>> system/fwupd: Updated for version 2.1.7. >>> system/fxload: New maintainer >>> system/fzf: Updated for version 0.74.2. >>> system/hw-probe: Reworked pacman patch; new maintainer. >>> system/incus: Updated for version 7.3 >>> system/jenkins: Updated for version 2.568.2. >>> system/phpsysinfo: Updated for version 3.4.6 >>> system/physlock: Updated for version 13. >>> system/recoverdm: Fix homepage. >>> system/rng-tools: New maintainer. >>> system/sbotest: Updated for version 1.3. >>> system/sbotools: Updated for version 4.4. >>> system/sdl-jstest: Updated for version 0.2.2+20260729_cf4fab3. >>> system/sdl2trs: Updated for version 1.2.35+20260517_96d531a4. >>> system/sdltrs: Updated for version 1.2.35. >>> system/smbldap-tools: Updated for version 0.9.11. >>> system/symbola-font-ttf: Avoid writes to /root. >>> system/targetcli-fb: Updated for version 3.0.2. >>> system/ttf-nerd-fonts-symbols: Updated for version 3.5.0 >>> system/uae: New maintainer >>> system/uhubctl: Updated for version 2.6.0. >>> system/vagrant: Updated for version 2.4.9 >>> +--------------------------+ >>> >>> >>> -- >>> Willy Sudiarto Raharjo >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> >>> _______________________________________________ >> 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 pgcswiss at yandex.com Sat Aug 8 20:21:13 2026 From: pgcswiss at yandex.com (Patrice Coni) Date: Sat, 08 Aug 2026 22:21:13 +0200 Subject: [Slackbuilds-users] SlackBuild - pdfsam-basic In-Reply-To: <76970cce-dbeb-4d91-8702-0cbfdd4efc52@sagredo.eu> References: <2349383.vFx2qVVIhK@penguin.imac> <76970cce-dbeb-4d91-8702-0cbfdd4efc52@sagredo.eu> Message-ID: <2801709.vuYhMxLoTh@penguin.slackpengi> Hello Roberto Thank you for your reply. Okay, you have my approval. Please replace my name with your name in the SlackBuild of pdfsam-basic. Best regards, Patrice Coni Am Samstag, 8. August 2026, 21:27:13 CEST schrieb Roberto Puzzanghera via SlackBuilds-users: > I can take it From urchlay at slackware.uk Sun Aug 9 03:06:46 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 8 Aug 2026 23:06:46 -0400 (EDT) Subject: [Slackbuilds-users] github homepages Message-ID: I'm thinking about adding a check to sbolint. It would look at HOMEPAGE in the .info file, and give a warning for github links that aren't the project page. Examples: # homepage is the wiki, not the project page: HOMEPAGE="https://github.com/OpenSC/libp11/wiki" # homepage is the releases page, not the project page: HOMEPAGE="https://github.com/nemtrif/utfcpp/releases" # homepage is the tags page, not the project page: HOMEPAGE="https://github.com/Thomas-Tsai/partclone/tags" # homepage gives a 404 error! HOMEPAGE="https://github.com/googleapis/google-api-python-client/archive/" Seems to me that the 'canonical' home page of a github project is the base project page. Or if there's a non-github homepage, or a project.github.io page, that would be OK, too. I just think the tags/ or releases/ or wiki/ shouldn't be considered the homepage. To me this falls under "principle of least surprise": https://en.wikipedia.org/wiki/Principle_of_least_surprise Does anyone else have an opinion about this, one way or the other? It's not something set in stone, just a thought I had. From mm at dorfdsl.de Sun Aug 9 09:47:02 2026 From: mm at dorfdsl.de (Marco Moock) Date: Sun, 9 Aug 2026 11:47:02 +0200 Subject: [Slackbuilds-users] github release URLs Message-ID: <1802ecc4-ecf8-45be-9e1d-780f16e50078@dorfdsl.de> Hello! https://github.com/firewalld/firewalld/releases/download/v2.5.1/firewalld-2.5.1.tar.bz2 Are such addresses acceptable? https://github.com/firewalld/firewalld/archive/2.5.1/firewalld-2.5.1.tar.bz2 does not work, even when version begins with v. -- Gru? Marco Junk-Mail bitte an trashcan 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 matteo.bernardini at gmail.com Sun Aug 9 09:51:36 2026 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 9 Aug 2026 11:51:36 +0200 Subject: [Slackbuilds-users] github release URLs In-Reply-To: <1802ecc4-ecf8-45be-9e1d-780f16e50078@dorfdsl.de> References: <1802ecc4-ecf8-45be-9e1d-780f16e50078@dorfdsl.de> Message-ID: Il giorno dom 9 ago 2026 alle ore 11:47 Marco Moock ha scritto: > Hello! > > > https://github.com/firewalld/firewalld/releases/download/v2.5.1/firewalld-2.5.1.tar.bz2 > > Are such addresses acceptable? > > > https://github.com/firewalld/firewalld/archive/2.5.1/firewalld-2.5.1.tar.bz2 > does not work, even when version begins with v. hi Marco, the links from the release pages are perfectly fine. Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Sun Aug 9 09:57:41 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 9 Aug 2026 05:57:41 -0400 (EDT) Subject: [Slackbuilds-users] github release URLs In-Reply-To: References: <1802ecc4-ecf8-45be-9e1d-780f16e50078@dorfdsl.de> Message-ID: On Sun, 9 Aug 2026, Matteo Bernardini wrote: > https://github.com/firewalld/firewalld/releases/download/v2.5.1/firewalld-2.5.1.tar.bz2 > > Are such addresses acceptable? Yes. sbolint won't ever complain about a github URL with /releases/ in it, and there's no weirdness about some browsers/clients renaming the file and others not. Plus... it's better to use a /releases/ URL anyway (if available), because sometimes the /tags/ one doesn't include everything needed to build & run the software. E.g. a game that includes assets (graphics, sound), sometimes the release tarball has these, but the auto-generated /tags/ one doesn't. Another possibility is git submodules. From urchlay at slackware.uk Sun Aug 9 10:19:48 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 9 Aug 2026 06:19:48 -0400 (EDT) Subject: [Slackbuilds-users] github release URLs In-Reply-To: References: <1802ecc4-ecf8-45be-9e1d-780f16e50078@dorfdsl.de> Message-ID: <9e74b071-61be-d633-82bc-ddbe879f4657@slackware.uk> On Sun, 9 Aug 2026, Matteo Bernardini wrote: > https://github.com/firewalld/firewalld/archive/2.5.1/firewalld-2.5.1.tar.bz2 > does not work, even when version begins with v. Also, github doesn't do .tar.bz2 autogenerated tarballs. If you *really* wanted to use a URL like this, you'd use .tar.gz... but see my previous email about why you're better off with the /releases/ one. From urchlay at slackware.uk Sun Aug 9 21:28:13 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 9 Aug 2026 17:28:13 -0400 (EDT) Subject: [Slackbuilds-users] template idea: --no-same-owner Message-ID: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> So the templates all do this: rm -rf $PRGNAM-$VERSION tar xvf $CWD/$PRGNAM-$VERSION.tar.gz cd $PRGNAM-$VERSION chown -R root:root . ...but looking at the tar man page, there's this: --no-same-owner Extract files as yourself (default for ordinary users). ...which would extract the tarball and set the ownership to root:root in one step. I don't know when this option got added to tar, but it seems like using it would simplify things (do the same job in less code). So the template would look something like: rm -rf $PRGNAM-$VERSION tar xvf $CWD/$PRGNAM-$VERSION.tar.gz --no-same-owner cd $PRGNAM-$VERSION There's also this: --no-same-permissions Apply the user's umask when extracting permissions from the archive (default for or? dinary users). ...which might substitute for (or at least simplify) the find/chmod stuff. Thoughts? From chris.willing at linux.com Sun Aug 9 23:43:59 2026 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 10 Aug 2026 09:43:59 +1000 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> Message-ID: On 10/8/26 07:28, B. Watson wrote: > > So the templates all do this: > > rm -rf $PRGNAM-$VERSION > tar xvf $CWD/$PRGNAM-$VERSION.tar.gz > cd $PRGNAM-$VERSION > chown -R root:root . > > ...but looking at the tar man page, there's this: > > ? --no-same-owner > ???????? Extract files as yourself (default for ordinary users). > > ...which would extract the tarball and set the ownership to root:root > in one step. I don't know when this option got added to tar, but it > seems like using it would simplify things (do the same job in less > code). > > So the template would look something like: > > rm -rf $PRGNAM-$VERSION > tar xvf $CWD/$PRGNAM-$VERSION.tar.gz --no-same-owner > cd $PRGNAM-$VERSION > > There's also this: > > --no-same-permissions > ?????? Apply the user's umask when extracting permissions from the > archive (default for or? > ?????? dinary users). > > ...which might substitute for (or at least simplify) the find/chmod > stuff. > > Thoughts? Good idea. I tried the --no-same-owner thing on some of the SlackBuilds I use a while back and the only reason I didn't persist was the need to update them all after each weekly SBo update. The main reason I was playing with it at all was that, when using a docker container for building, tar extraction would sometimes fail because files would be extracted to illegal uid or gid. In reality, that could have been due to faulty /etc/sub{git,uid} settings but using --no-same-owner overcame the problem for me. chris From isaacyu at protonmail.com Mon Aug 10 06:15:05 2026 From: isaacyu at protonmail.com (Isaac Yu) Date: Mon, 10 Aug 2026 06:15:05 +0000 Subject: [Slackbuilds-users] I will no longer maintain SlackBuilds from Aug 15 onwards Message-ID: <1YJ3SC0PayeJy1wzNgiqY32N2M0anMDUR8t1twRshWHhhszkFvXB6gLmH89AzzPp8xOG7Ia9zkRVcgREMAbZVLfIyroz5uMu5HJcNB1II3Y=@protonmail.com> Hi everyone, This is the last weekly cycle in which I will maintain/update SlackBuilds. I will no longer do so from Aug 15 onwards. I previously said that I would no longer maintain SlackBuilds last Christmas, but I kept continuing to do so. Sorry about that - the main reason was that getting LXQt to v2 was less stressful than I initially thought (which prompted me to make that claim last Christmas). I mean it this time. Software (and by extension SlackBuilds) are getting more and more complicated to maintain. My main motivation recently has been to prepare for a new release of Slackware (ex. 15.1, 16.0, etc.) I'm actually using Linux Mint Debian right now as my main day-to-day operating system. I've been testing updates through Slackware virtual machines. I might return when the first alpha of the next Slackware version gets released (ex. 15.1-alpha1.) To the SlackBuilds.org team: My suggestion is to orphan my SlackBuilds only when the next version of Slackware is about to get released. I might make a hotfix SlackBuild update even during the Slackware 15.0 cycle (ex. protobuf gets updated, making python3-grpcio unable to build.) However, you may orphan them next week if you like. - Isaac -------------- next part -------------- An HTML attachment was scrubbed... URL: From rizitis at gmail.com Mon Aug 10 09:20:46 2026 From: rizitis at gmail.com (Yiannis) Date: Mon, 10 Aug 2026 12:20:46 +0300 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> Message-ID: --no-same-owner: yes, this works. It does exactly what "chown -R root:root ." does, symlinks included. Both leave every entry root:root, and both leave the symlink's target outside the tree untouched -- chown -R defaults to -P, so it lchown()s the link rather than following it. I could not find a case where they differ. The option predates any Slackware we still support, so its age isn't a concern. One place where --no-same-owner is a bug fix, not a simplification ruby/ as example look here: https://git.slackbuilds.org/slackbuilds/tree/ruby/rubygem-parallel/rubygem-parallel.SlackBuild?h=15.0&id=608168806da9306799ec6aec884828f38a85e8d4 rubygem-template has no chown/find pass at all, but it does this: tar -x -O --file=$CWD/$SRCNAM-$VERSION.gem data.tar.gz \ | tar -xz -C $PKGDOC --file=- That second tar runs as root with --same-owner in effect, writes straight into $PKG, and nothing corrects it afterwards. If built a synthetic gem to check: the doc file landed in $PKGDOC owned by the upstream packager's uid, and that's what makepkg ships. Adding --no-same-owner to that second tar fixes it. Worth doing regardless of what happens to the rest of this. --no-same-permissions: no! this one doesn't hold up. umask can only clear bits, never set them, so it can't do the job the find/chmod block exists for. The question is, is it worth the effort to change a few thousand SlackBuilds for no real reason? I mean, if it's just to change `chown -R root:root .` with `tar --no-same-owner -xvf ...` I would suggest you focus on SBo/ruby/* for that alone. thanks ???? ??? 10 ??? 2026 ???? 2:44??.?., ?/? Christoph Willing < chris.willing at linux.com> ??????: > On 10/8/26 07:28, B. Watson wrote: > > > > So the templates all do this: > > > > rm -rf $PRGNAM-$VERSION > > tar xvf $CWD/$PRGNAM-$VERSION.tar.gz > > cd $PRGNAM-$VERSION > > chown -R root:root . > > > > ...but looking at the tar man page, there's this: > > > > --no-same-owner > > Extract files as yourself (default for ordinary users). > > > > ...which would extract the tarball and set the ownership to root:root > > in one step. I don't know when this option got added to tar, but it > > seems like using it would simplify things (do the same job in less > > code). > > > > So the template would look something like: > > > > rm -rf $PRGNAM-$VERSION > > tar xvf $CWD/$PRGNAM-$VERSION.tar.gz --no-same-owner > > cd $PRGNAM-$VERSION > > > > There's also this: > > > > --no-same-permissions > > Apply the user's umask when extracting permissions from the > > archive (default for or? > > dinary users). > > > > ...which might substitute for (or at least simplify) the find/chmod > > stuff. > > > > Thoughts? > > > Good idea. > > I tried the --no-same-owner thing on some of the SlackBuilds I use a > while back and the only reason I didn't persist was the need to update > them all after each weekly SBo update. > > The main reason I was playing with it at all was that, when using a > docker container for building, tar extraction would sometimes fail > because files would be extracted to illegal uid or gid. In reality, that > could have been due to faulty /etc/sub{git,uid} settings but using > --no-same-owner overcame the problem for me. > > chris > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Mon Aug 10 09:32:04 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 10 Aug 2026 05:32:04 -0400 (EDT) Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> Message-ID: <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> On Mon, 10 Aug 2026, Yiannis wrote: > --no-same-owner: yes, this works. > It does exactly what "chown -R root:root ." does, symlinks included. > Both leave every entry root:root, and both leave the symlink's target > outside the tree untouched -- chown -R defaults to -P, so it lchown()s > the link rather than following it. I could not find a case where they > differ. The option predates any Slackware we still support, so its age > isn't a concern. Thanks for this analysis. > One place where --no-same-owner is a bug fix, not a simplification ruby/ as example look here: > https://git.slackbuilds.org/slackbuilds/tree/ruby/rubygem-parallel/rubygem-parallel.SlackBuild?h=15.0&id=608168806da9306799ec6aec884828f38a85e8d4 > > rubygem-template has no chown/find pass at all, but it does this: > ? tar -x -O --file=$CWD/$SRCNAM-$VERSION.gem data.tar.gz \ > ? ? | tar -xz -C $PKGDOC --file=- > > That second tar runs as root with --same-owner in effect, writes > straight into $PKG, and nothing corrects it afterwards. If built a > synthetic gem to check: the doc file landed in $PKGDOC owned by the > upstream packager's uid, and that's what makepkg ships. Adding > --no-same-owner to that second tar fixes it. Worth doing regardless of > what happens to the rest of this. Interesting. So we have a bunch of ruby/ packages that fail sbopkglint? It really should complain about those... bug or just an oversight, maybe. > --no-same-permissions: no! this one doesn't hold up. > umask can only clear bits, never set them, so it can't do the job the > find/chmod block exists for. Right. I looked into it and found the same thing. > The question is, is it worth the effort to change a few thousand SlackBuilds for no real reason? > ?I mean, if it's just to change `chown -R root:root .` with `tar --no-same-owner -xvf ...` No, I'm not talking about changing every existing script. I'm talking about changing the template. New builds will be based on the new template, but we're not going to change existing (working!) builds just to update to the new template. You're right, it wouldn't be worth the effort. If this becomes the new template, we'll encourage maintainers to make this change in their scripts, when they're already in the process of updating them (e.g. a version update, editing the script anyway, might as well align it with the latest template), but we won't *require* it. > I would suggest you focus on SBo/ruby/* for that alone. I'll have a look. From willysr at slackbuilds.org Mon Aug 10 14:22:56 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 10 Aug 2026 21:22:56 +0700 Subject: [Slackbuilds-users] Build Environment Reminder Message-ID: <20260810212256.7ec41764@home.slackie.org> Hi all We noticed that some applications require newer version of libraries or modules that is already provided by Slackware core packages. This is normal as Slackware 15.0 is now 4 years old and upstream are bumping requirements as they develop new version with more features. Patrick has been kind enough to provide some new version of some packages into testing/ which helps people to keep updating to the latest version of the software they often use daily. We just to want to remind everyone that SBo is designed to be tested against latest Slackware Stable releases with latest patches. It doesn't include extra/ or testing/ which requires manual intervention and not part of the full installation. Our CI is NOT designed to test against custom installation, which includes packages from extra or testing. That said, moving forward, we will start scanning our repository for scripts that requires newer libraries/packages, such as GLIBC and start removing them. Urchlay will add GLIBC detection at sbo-maintainer-tools package soon, which will help CI to test against new PR that requires newer GLIBC. Maintainers, please ensure that your scripts are tested against clean environment of Slackware 15.0, not -current or custom installation. Our FAQ is also updated to clarify this issue https://slackbuilds.org/faq/#full -- 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 mm at dorfdsl.de Mon Aug 10 15:29:25 2026 From: mm at dorfdsl.de (Marco Moock) Date: Mon, 10 Aug 2026 17:29:25 +0200 Subject: [Slackbuilds-users] modifying pending uploads Message-ID: <7aeb5eff-450a-489a-8de4-0a4994fd1e98@dorfdsl.de> Hello! I uploaded a firewalld update, but missed a description file. If I try to upload the new one, it says it is in pending, but already committed for the next update. How can I handle that situation? -- kind regards Marco Junk-Mail bitte an trashcan 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 artourter at gmail.com Mon Aug 10 21:38:53 2026 From: artourter at gmail.com (Greg Tourte) Date: Mon, 10 Aug 2026 22:38:53 +0100 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: <20260810212256.7ec41764@home.slackie.org> References: <20260810212256.7ec41764@home.slackie.org> Message-ID: Willy, does that include package which explicitly state in the README that the package require the newer GLIBC? I maintain one such script (signal-desktop) and it would be a shame to see it removed from the repo. Cheers Greg On Mon, 10 Aug 2026 at 15:23, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Hi all > > We noticed that some applications require newer version of libraries or > modules > that is already provided by Slackware core packages. This is normal as > Slackware 15.0 is now 4 years old and upstream are bumping requirements as > they > develop new version with more features. Patrick has been kind enough to > provide > some new version of some packages into testing/ which helps people to keep > updating to the latest version of the software they often use daily. > > We just to want to remind everyone that SBo is designed to be tested > against > latest Slackware Stable releases with latest patches. It doesn't include > extra/ > or testing/ which requires manual intervention and not part of the full > installation. Our CI is NOT designed to test against custom installation, > which > includes packages from extra or testing. > > That said, moving forward, we will start scanning our repository for > scripts > that requires newer libraries/packages, such as GLIBC and start > removing them. Urchlay will add GLIBC detection at sbo-maintainer-tools > package > soon, which will help CI to test against new PR that requires newer GLIBC. > > Maintainers, please ensure that your scripts are tested against clean > environment of Slackware 15.0, not -current or custom installation. > Our FAQ is also updated to clarify this issue > https://slackbuilds.org/faq/#full > > > -- > Willy Sudiarto Raharjo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Mon Aug 10 21:43:28 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 10 Aug 2026 15:43:28 -0600 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> Message-ID: Indeed. Especially after somebody (maybe yourself) shared a simple hack to get it to work under Slackware 15.0. On Mon, Aug 10, 2026 at 3:39?PM Greg Tourte wrote: > Willy, > > does that include package which explicitly state in the README that the > package require the newer GLIBC? > > I maintain one such script (signal-desktop) and it would be a shame to see > it removed from the repo. > > Cheers > > Greg > > On Mon, 10 Aug 2026 at 15:23, Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> Hi all >> >> We noticed that some applications require newer version of libraries or >> modules >> that is already provided by Slackware core packages. This is normal as >> Slackware 15.0 is now 4 years old and upstream are bumping requirements >> as they >> develop new version with more features. Patrick has been kind enough to >> provide >> some new version of some packages into testing/ which helps people to keep >> updating to the latest version of the software they often use daily. >> >> We just to want to remind everyone that SBo is designed to be tested >> against >> latest Slackware Stable releases with latest patches. It doesn't include >> extra/ >> or testing/ which requires manual intervention and not part of the full >> installation. Our CI is NOT designed to test against custom installation, >> which >> includes packages from extra or testing. >> >> That said, moving forward, we will start scanning our repository for >> scripts >> that requires newer libraries/packages, such as GLIBC and start >> removing them. Urchlay will add GLIBC detection at sbo-maintainer-tools >> package >> soon, which will help CI to test against new PR that requires newer GLIBC. >> >> Maintainers, please ensure that your scripts are tested against clean >> environment of Slackware 15.0, not -current or custom installation. >> Our FAQ is also updated to clarify this issue >> https://slackbuilds.org/faq/#full >> >> >> -- >> Willy Sudiarto Raharjo >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Aug 11 00:02:11 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 11 Aug 2026 07:02:11 +0700 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> Message-ID: <20260811070211.1136be77@home.slackie.org> >does that include package which explicitly state in the README that the >package require the newer GLIBC? > >I maintain one such script (signal-desktop) and it would be a shame to see >it removed from the repo. Unfortunately yes -- 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 lumin+slackbuilds at etherlight.link Tue Aug 11 04:50:46 2026 From: lumin+slackbuilds at etherlight.link (Lumin Etherlight) Date: Tue, 11 Aug 2026 07:50:46 +0300 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: <20260811070211.1136be77@home.slackie.org> (Willy Sudiarto Raharjo's message of "Tue, 11 Aug 2026 07:02:11 +0700") References: <20260810212256.7ec41764@home.slackie.org> <20260811070211.1136be77@home.slackie.org> Message-ID: >> does that include package which explicitly state >> in the README that the package require the newer >> GLIBC? >> >> I maintain one such script (signal-desktop) and >> it would be a shame to see it removed from the >> repo. >> >>> Indeed. Especially after somebody shared a >>> simple hack to get it to work under Slackware >>> 15.0. Willy Sudiarto Raharjo writes: > Unfortunately yes Signal is an important package, so perhaps we can make the SlackBuild patch the binary itself and thus it would work on Slackware 15.0 without user intervention. I wrote some instructions[1] on my website, and wrote a script[2] to automate the patching process. The patch forces Signal to use a glibc install in /opt using rpath. Perhaps we can provide a simple glibc-opt-bin SlackBuild which would install glibc from /testing into /opt to support the installation of Signal (and perhaps other packages that may follow the same pattern). I've been using Signal on 15.0 for more than two months in this manner; it's stable and works well. [1]: https://lumin.etherlight.link/c/2C2606/mf3gC [2]: https://lumin.etherlight.link/s/2C2606/saNeW/slackware-signal-glibc-workaround.sh Best Regards, Lumin Etherlight From willysr at slackbuilds.org Tue Aug 11 05:31:57 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 11 Aug 2026 12:31:57 +0700 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> <20260811070211.1136be77@home.slackie.org> Message-ID: <20260811123157.04ee9756@office64.slackie.org> > Signal is an important package, so perhaps > we can make the SlackBuild patch the binary itself > and thus it would work on Slackware 15.0 without > user intervention. I wrote some instructions[1] > on my website, and wrote a script[2] to automate > the patching process. The patch forces Signal to > use a glibc install in /opt using rpath. Perhaps > we can provide a simple glibc-opt-bin SlackBuild > which would install glibc from /testing into /opt > to support the installation of Signal (and perhaps > other packages that may follow the same pattern). > I've been using Signal on 15.0 for more than two > months in this manner; it's stable and works well. For library as important as glibc, i am not recommending to have multiple installation and push it to SBo. That would be much more complicated for us to maintain in the future. Best to stick with the current glibc we have in stable -- 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 Tue Aug 11 05:38:40 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 11 Aug 2026 12:38:40 +0700 Subject: [Slackbuilds-users] modifying pending uploads In-Reply-To: <7aeb5eff-450a-489a-8de4-0a4994fd1e98@dorfdsl.de> References: <7aeb5eff-450a-489a-8de4-0a4994fd1e98@dorfdsl.de> Message-ID: <20260811123840.143c1acb@office64.slackie.org> >I uploaded a firewalld update, but missed a description file. > >If I try to upload the new one, it says it is in pending, but already >committed for the next update. > >How can I handle that situation? I think Chris is the one approved your script, so you should contact him to remove it from his branch and from DB so you can reupload -- 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 chris.willing at linux.com Tue Aug 11 05:46:53 2026 From: chris.willing at linux.com (Christoph Willing) Date: Tue, 11 Aug 2026 15:46:53 +1000 Subject: [Slackbuilds-users] modifying pending uploads In-Reply-To: <20260811123840.143c1acb@office64.slackie.org> References: <7aeb5eff-450a-489a-8de4-0a4994fd1e98@dorfdsl.de> <20260811123840.143c1acb@office64.slackie.org> Message-ID: <733f4913-7e8f-40c6-9be6-cdee62a976ac@linux.com> On 11/8/26 15:38, Willy Sudiarto Raharjo wrote: >> I uploaded a firewalld update, but missed a description file. >> >> If I try to upload the new one, it says it is in pending, but already >> committed for the next update. >> >> How can I handle that situation? > > I think Chris is the one approved your script, so you should contact > him to remove it from his branch and from DB so you can reupload It should be clear to try again now. chris From urchlay at slackware.uk Tue Aug 11 06:15:00 2026 From: urchlay at slackware.uk (B. Watson) Date: Tue, 11 Aug 2026 02:15:00 -0400 (EDT) Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> <20260811070211.1136be77@home.slackie.org> Message-ID: <79dcc629-5271-eb43-cc7a-a8c761ec62dc@slackware.uk> On Tue, 11 Aug 2026, Lumin Etherlight via SlackBuilds-users wrote: > Perhaps we can provide a simple glibc-opt-bin SlackBuild > which would install glibc from /testing into /opt to support the > installation of Signal (and perhaps other packages that may follow > the same pattern). I've actually got a glibc-opt build I've been working on, including a script to patch binaries... side project, not submitted to SBo, not even sure it's a good idea. What I found is, I could get C programs working without too much trouble, but anything that links with libstdc++ gave trouble. From rizitis at gmail.com Tue Aug 11 07:15:51 2026 From: rizitis at gmail.com (Yiannis) Date: Tue, 11 Aug 2026 10:15:51 +0300 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> Message-ID: sbopkglint is fine -- it complains exactly as it should. I built rubygem-ast (orphaned, no deps, unmodified doc pipeline) and linted it: Running test: 10-docs... --- ERR: bad ownership (should be root:root) in doc dir: -rw-r--r-- 1 root wheel 1089 Jan 23 2021 usr/doc/rubygem-ast-2.4.2/LICENSE.MIT -rw-r--r-- 1 root wheel 482 Jan 23 2021 usr/doc/rubygem-ast-2.4.2/ README.YARD.md FAILED So a new rubygem submission written to the current template fails the lint we tell submitters to run. That's the whole of the problem. I need to correct my own explanation, though: it's not the packager's uid, it's the group, and it's hardcoded. Every entry in a gem is recorded with the *name* wheel: $ tar -x -O --file=ast-2.4.2.gem data.tar.gz | tar -tvz -rw-r--r-- wheel/wheel 1089 2021-01-23 20:56 LICENSE.MIT -rw-r--r-- wheel/wheel 482 2021-01-23 20:56 README.YARD.md -rw-r--r-- wheel/wheel 586 2021-01-23 20:56 lib/ast.rb [...] RubyGems' tar_header.rb defaults uname and gname to "wheel" and never sets uid/gid, so gems carry uid 0 / gid 0 / uname wheel / gname wheel. GNU tar as root resolves the names before the numbers unless you give it --numeric-owner. There's no wheel user, so uid falls back to 0 -> root. There is a wheel group -> root:wheel. What makes it unambiguous is that the gem records wheel/wheel for *every* file, including lib/*.rb -- but those come out root:root in the package, because gem install writes them itself. Only the files that go through tar are affected. Same build, same source archive: drwxr-xr-x root/root usr/doc/rubygem-ast-2.4.2/ -rw-r--r-- root/wheel usr/doc/rubygem-ast-2.4.2/LICENSE.MIT -rw-r--r-- root/wheel usr/doc/rubygem-ast-2.4.2/README.YARD.md -rw-r--r-- root/root usr/doc/rubygem-ast-2.4.2/rubygem-ast.SlackBuild The SlackBuild in that same directory is root:root because it's written with cat. 2 offending entries out of 73. rubygem-template is the only template with no "chown -R root:root ." anywhere, and that second tar is the one place in it where ownership is restored from an archive rather than created by the process doing the writing. --no-same-owner (or --numeric-owner) on that line fixes it. ps. I used a translation tool and hope everything is ok now :) ???? ??? 10 ??? 2026 ???? 12:37??.?., ?/? B. Watson ??????: > > > On Mon, 10 Aug 2026, Yiannis wrote: > > > --no-same-owner: yes, this works. > > It does exactly what "chown -R root:root ." does, symlinks included. > > Both leave every entry root:root, and both leave the symlink's target > > outside the tree untouched -- chown -R defaults to -P, so it lchown()s > > the link rather than following it. I could not find a case where they > > differ. The option predates any Slackware we still support, so its age > > isn't a concern. > > Thanks for this analysis. > > > One place where --no-same-owner is a bug fix, not a simplification ruby/ > as example look here: > > > https://git.slackbuilds.org/slackbuilds/tree/ruby/rubygem-parallel/rubygem-parallel.SlackBuild?h=15.0&id=608168806da9306799ec6aec884828f38a85e8d4 > > > > rubygem-template has no chown/find pass at all, but it does this: > > tar -x -O --file=$CWD/$SRCNAM-$VERSION.gem data.tar.gz \ > > | tar -xz -C $PKGDOC --file=- > > > > That second tar runs as root with --same-owner in effect, writes > > straight into $PKG, and nothing corrects it afterwards. If built a > > synthetic gem to check: the doc file landed in $PKGDOC owned by the > > upstream packager's uid, and that's what makepkg ships. Adding > > --no-same-owner to that second tar fixes it. Worth doing regardless of > > what happens to the rest of this. > > Interesting. So we have a bunch of ruby/ packages that fail > sbopkglint? It really should complain about those... bug or just an > oversight, maybe. > > > --no-same-permissions: no! this one doesn't hold up. > > umask can only clear bits, never set them, so it can't do the job the > > find/chmod block exists for. > > Right. I looked into it and found the same thing. > > > The question is, is it worth the effort to change a few thousand > SlackBuilds for no real reason? > > I mean, if it's just to change `chown -R root:root .` with `tar > --no-same-owner -xvf ...` > > No, I'm not talking about changing every existing script. > > I'm talking about changing the template. New builds will be > based on the new template, but we're not going to change existing > (working!) builds just to update to the new template. You're right, > it wouldn't be worth the effort. > > If this becomes the new template, we'll encourage maintainers to make > this change in their scripts, when they're already in the process of > updating them (e.g. a version update, editing the script anyway, might > as well align it with the latest template), but we won't *require* it. > > > I would suggest you focus on SBo/ruby/* for that alone. > > I'll have a look._______________________________________________ > 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 Tue Aug 11 08:50:00 2026 From: urchlay at slackware.uk (B. Watson) Date: Tue, 11 Aug 2026 04:50:00 -0400 (EDT) Subject: [Slackbuilds-users] Anyone playing Warcraft II with wargus and stratagus? Message-ID: <82d9a641-36d4-de29-7c17-88d16e10b2a2@slackware.uk> I've attempted to update wargus and stratagus for the *last* time. The versions we have in our repo are really old, because I couldn't get any newer versons to work with the verson of Warcraft II that I actually own (the original MS-DOS CD release, before Battle.Net and before GoG). I've updated the builds for the latest versions (3.2.2 for both), but the game still won't start. So I rebuilt/reinstalled the old versions of stratagus and wargus and *they* no longer work: Invalid graphic (width, height) /usr/share/games/stratagus/wargus/graphics/ui/fonts/game.png Expected: (14,14) Found: (195,196) So I'm done. I haven't played Warcraft II in ages, anyway. If I want to play it again someday, I'll play it in DOSBox, which actually works fine. Does anyone want to take over these builds, and maybe update them to their latest versions? The new versions require the Battle.Net or GoG data files, but probably that's not a problem for most people. If anyone wants to take them over, please do. If not, they'll be orphaned in the next update (this weekend). From urchlay at slackware.uk Tue Aug 11 11:49:07 2026 From: urchlay at slackware.uk (B. Watson) Date: Tue, 11 Aug 2026 07:49:07 -0400 (EDT) Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> Message-ID: <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> On Tue, 11 Aug 2026, Yiannis wrote: > sbopkglint is fine -- it complains exactly as it should. I built > rubygem-ast (orphaned, no deps, unmodified doc pipeline) and linted it: > > ? Running test: 10-docs... > ? --- ERR: bad ownership (should be root:root) in doc dir: > ? -rw-r--r-- 1 root wheel 1089 Jan 23 ?2021 usr/doc/rubygem-ast-2.4.2/LICENSE.MIT > ? -rw-r--r-- 1 root wheel ?482 Jan 23 ?2021 usr/doc/rubygem-ast-2.4.2/README.YARD.md > ? FAILED > > So a new rubygem submission written to the current template fails the > lint we tell submitters to run. That's the whole of the problem. Yes, that's a serious problem. I am at a loss to understand how these builds ever got approved, or how the template was left in that state. Thanks for pointing it out. Looks we have 93 builds that need attention. Sigh. From willysr at slackbuilds.org Tue Aug 11 13:12:35 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 11 Aug 2026 20:12:35 +0700 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> Message-ID: <20260811201235.55d02b4d@home.slackie.org> > > >On Tue, 11 Aug 2026, Yiannis wrote: > >> sbopkglint is fine -- it complains exactly as it should. I built >> rubygem-ast (orphaned, no deps, unmodified doc pipeline) and linted it: >> >> ? Running test: 10-docs... >> ? --- ERR: bad ownership (should be root:root) in doc dir: >> ? -rw-r--r-- 1 root wheel 1089 Jan 23 ?2021 >> usr/doc/rubygem-ast-2.4.2/LICENSE.MIT -rw-r--r-- 1 root wheel ?482 Jan 23 >> 2021 usr/doc/rubygem-ast-2.4.2/README.YARD.md FAILED >> >> So a new rubygem submission written to the current template fails the >> lint we tell submitters to run. That's the whole of the problem. > >Yes, that's a serious problem. > >I am at a loss to understand how these builds ever got approved, or how >the template was left in that state. Thanks for pointing it out. > >Looks we have 93 builds that need attention. Sigh. It was approved back in 2018 where we didn't have any linter, so as long as the build process works, it got accepted. We didn't have time to check for every files inside. That's why having our current CI + linter are very valuable :) -- 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 tonus1 at free.fr Tue Aug 11 14:23:55 2026 From: tonus1 at free.fr (Tonus) Date: Tue, 11 Aug 2026 16:23:55 +0200 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: (Lumin Etherlight via SlackBuilds-users's message of "Tue, 11 Aug 2026 07:50:46 +0300") References: <20260810212256.7ec41764@home.slackie.org> <20260811070211.1136be77@home.slackie.org> Message-ID: <87zeysburo.fsf@odin.vingolf.org> Lumin Etherlight via SlackBuilds-users writes: >>> does that include package which explicitly state >>> in the README that the package require the newer >>> GLIBC? >>> >>> I maintain one such script (signal-desktop) and >>> it would be a shame to see it removed from the >>> repo. >>> >>>> Indeed. Especially after somebody shared a >>>> simple hack to get it to work under Slackware >>>> 15.0. > > Willy Sudiarto Raharjo writes: > >> Unfortunately yes > > Signal is an important package, so perhaps > we can make the SlackBuild patch the binary itself > and thus it would work on Slackware 15.0 without > user intervention. I wrote some instructions[1] > on my website, and wrote a script[2] to automate > the patching process. The patch forces Signal to > use a glibc install in /opt using rpath. Perhaps > we can provide a simple glibc-opt-bin SlackBuild > which would install glibc from /testing into /opt > to support the installation of Signal (and perhaps > other packages that may follow the same pattern). > I've been using Signal on 15.0 for more than two > months in this manner; it's stable and works well. > > [1]: https://lumin.etherlight.link/c/2C2606/mf3gC > [2]: https://lumin.etherlight.link/s/2C2606/saNeW/slackware-signal-glibc-workaround.sh > > > Best Regards, > Lumin Etherlight Hi all, I agree that Signal is a must have. I've been using the workaround from Lumin for weeks on at least 2 devices running stable 15.0. This seems quite stable enough. I suggest the SlackBuild stays with a %README% in the REQUIRES line of the .info file. This could explain the needs of the testing glibc package and link to the maintainer website for those that wouldn't go this path. -- Regards, Tonus. From willysr at slackbuilds.org Tue Aug 11 15:41:46 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 11 Aug 2026 22:41:46 +0700 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: <87zeysburo.fsf@odin.vingolf.org> References: <20260810212256.7ec41764@home.slackie.org> <20260811070211.1136be77@home.slackie.org> <87zeysburo.fsf@odin.vingolf.org> Message-ID: <20260811224146.237a2f57@home.slackie.org> >I agree that Signal is a must have. I've been using the workaround from >Lumin for weeks on at least 2 devices running stable 15.0. > >This seems quite stable enough. I suggest the SlackBuild stays with a >%README% in the REQUIRES line of the .info file. > >This could explain the needs of the testing glibc package and link to >the maintainer website for those that wouldn't go this path. again, testing/ is *testing*, it's not yet approved for core packages We can't approve one script only because it's a must have app for some people, since it's a all or nothing situation. Unless Patrick move those packages in testing to main categories (which i highly doubt), glibc requirement will stick to 2.33 for SBo 15.0 repository -- 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 roberto.puzzanghera at sagredo.eu Tue Aug 11 16:56:04 2026 From: roberto.puzzanghera at sagredo.eu (Roberto Puzzanghera) Date: Tue, 11 Aug 2026 18:56:04 +0200 Subject: [Slackbuilds-users] SlackBuild - pdfsam-basic In-Reply-To: <2801709.vuYhMxLoTh@penguin.slackpengi> References: <2349383.vFx2qVVIhK@penguin.imac> <76970cce-dbeb-4d91-8702-0cbfdd4efc52@sagredo.eu> <2801709.vuYhMxLoTh@penguin.slackpengi> Message-ID: <8b5951a3a4e8d618c29851559d00accf@sagredo.eu> I tried to submit my slackbuild with the new maintainer and new version, but it was rejected because there was already a submission sent by you two days ago. I'll try again next week. Il 08-08-2026 22:21 Patrice Coni ha scritto: > Hello Roberto > > Thank you for your reply. > Okay, you have my approval. > Please replace my name with your name in the SlackBuild of > pdfsam-basic. > > Best regards, > Patrice Coni > > Am Samstag, 8. August 2026, 21:27:13 CEST schrieb Roberto Puzzanghera > via > SlackBuilds-users: >> I can take it From willysr at slackbuilds.org Tue Aug 11 17:12:40 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 12 Aug 2026 00:12:40 +0700 Subject: [Slackbuilds-users] SlackBuild - pdfsam-basic In-Reply-To: <8b5951a3a4e8d618c29851559d00accf@sagredo.eu> References: <2349383.vFx2qVVIhK@penguin.imac> <76970cce-dbeb-4d91-8702-0cbfdd4efc52@sagredo.eu> <2801709.vuYhMxLoTh@penguin.slackpengi> <8b5951a3a4e8d618c29851559d00accf@sagredo.eu> Message-ID: <20260812001240.51e1fdc4@home.slackie.org> >I tried to submit my slackbuild with the new maintainer and new version, >but it was rejected because there was already a submission sent by you >two days ago. >I'll try again next week. I have changed it on my branch under your name now https://git.slackbuilds.org/slackbuilds/commit/?id=9aa5340e2 -- 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 pgcswiss at yandex.com Tue Aug 11 17:33:57 2026 From: pgcswiss at yandex.com (Patrice Coni) Date: Tue, 11 Aug 2026 19:33:57 +0200 Subject: [Slackbuilds-users] SlackBuild - pdfsam-basic In-Reply-To: <20260812001240.51e1fdc4@home.slackie.org> References: <2349383.vFx2qVVIhK@penguin.imac> <8b5951a3a4e8d618c29851559d00accf@sagredo.eu> <20260812001240.51e1fdc4@home.slackie.org> Message-ID: @Roberto: Yes. Bevore i write in this mailinglist for a maintainer-change of pdfsam-basic, i uploaded an updated slackbuild for pdfsam-basic v6.0.5 (my last one). @Willy Sudiarto Raharjo: Thank you. Best regards, Patrice Coni Am Dienstag, 11. August 2026, 19:12:40 Mitteleurop?ische Sommerzeit schrieb Willy Sudiarto Raharjo: > >I tried to submit my slackbuild with the new maintainer and new version, > >but it was rejected because there was already a submission sent by you > >two days ago. > >I'll try again next week. > > I have changed it on my branch under your name now > https://git.slackbuilds.org/slackbuilds/commit/?id=9aa5340e2 > > > -- > Willy Sudiarto Raharjo From khronosschoty at posteo.org Tue Aug 11 17:34:49 2026 From: khronosschoty at posteo.org (Vasily Sora) Date: Tue, 11 Aug 2026 17:34:49 +0000 Subject: [Slackbuilds-users] Anyone playing Warcraft II with wargus and stratagus? Message-ID: > Does anyone want to take over these builds, and > maybe update them to their latest versions? I?m interested. From roberto.puzzanghera at sagredo.eu Tue Aug 11 17:53:34 2026 From: roberto.puzzanghera at sagredo.eu (Roberto Puzzanghera) Date: Tue, 11 Aug 2026 19:53:34 +0200 Subject: [Slackbuilds-users] SlackBuild - pdfsam-basic In-Reply-To: <20260812001240.51e1fdc4@home.slackie.org> References: <2349383.vFx2qVVIhK@penguin.imac> <76970cce-dbeb-4d91-8702-0cbfdd4efc52@sagredo.eu> <2801709.vuYhMxLoTh@penguin.slackpengi> <8b5951a3a4e8d618c29851559d00accf@sagredo.eu> <20260812001240.51e1fdc4@home.slackie.org> Message-ID: <4e34e380ebb3f9027904001ea2516974@sagredo.eu> Thank you Willy and Patrice Il 11-08-2026 19:12 Willy Sudiarto Raharjo ha scritto: >> I tried to submit my slackbuild with the new maintainer and new >> version, >> but it was rejected because there was already a submission sent by you >> two days ago. >> I'll try again next week. > > > I have changed it on my branch under your name now > https://git.slackbuilds.org/slackbuilds/commit/?id=9aa5340e2 > > > -- > Willy Sudiarto Raharjo From urchlay at slackware.uk Tue Aug 11 20:32:02 2026 From: urchlay at slackware.uk (B. Watson) Date: Tue, 11 Aug 2026 16:32:02 -0400 (EDT) Subject: [Slackbuilds-users] Anyone playing Warcraft II with wargus and stratagus? In-Reply-To: References: Message-ID: <77529f78-23f3-202e-65cc-f14a047cc22@slackware.uk> On Tue, 11 Aug 2026, Vasily Sora wrote: >> Does anyone want to take over these builds, and > maybe update them to their latest versions? > I?m interested. They're yours. I can change the maintainer in the .info files for you, or you can submit updates in the usual way, if you're ready to. From milgram at cgpp.com Wed Aug 12 01:47:05 2026 From: milgram at cgpp.com (J. Milgram) Date: Tue, 11 Aug 2026 21:47:05 -0400 Subject: [Slackbuilds-users] Easy typo Message-ID: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> All, I noticed in a SlackBuild I was working on that I misspelled SLKCFLAGS as SLCKFLAGS, as in SLCKFLAGS= ... so setting CFLAGS="$SLKCFLAGS" ... wasn't doing anything. My eye wanted to see "SLCK" as in "Slack" so it's an easy typo to make and not notice. Out of curiosity, I ran find /usr/sbo/repo? -name \*.SlackBuild -exec grep SLCK \{\} \; -print and similar issues turned? up? in ./office/qpdfview/qpdfview.SlackBuild ("SLCKCFLAGS=...") ./office/cups-pdf/cups-pdf.SlackBuild ("gcc $SLCKFLAGS...") ./development/regina-rexx/regina-rexx.SlackBuild (in a comment) ./development/sqlitebrowser/sqlitebrowser.SlackBuild ("SLCKCFLAGS=...") ... and maybe there are others. I wonder if? this wouldn't be a good thing to append as a test in sbopkglint? ... if the SlackBuild sets any variables named SLCK... could be worth a closer look. Just a thought! respectfully, Judah -- ===== milgram at cgpp.com 301-257-7069 From willysr at slackbuilds.org Wed Aug 12 02:09:34 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 12 Aug 2026 09:09:34 +0700 Subject: [Slackbuilds-users] Easy typo In-Reply-To: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> Message-ID: <20260812090934.5d80e4f7@office64.slackie.org> >I noticed in a SlackBuild I was working on that I misspelled SLKCFLAGS >as SLCKFLAGS, as in > >SLCKFLAGS= ... > >so setting CFLAGS="$SLKCFLAGS" ... > >wasn't doing anything. > >My eye wanted to see "SLCK" as in "Slack" so it's an easy typo to make >and not notice. > >Out of curiosity, I ran >find /usr/sbo/repo? -name \*.SlackBuild -exec grep SLCK \{\} \; -print > >and similar issues turned? up? in > >./office/qpdfview/qpdfview.SlackBuild ("SLCKCFLAGS=...") >./office/cups-pdf/cups-pdf.SlackBuild ("gcc $SLCKFLAGS...") >./development/regina-rexx/regina-rexx.SlackBuild (in a comment) >./development/sqlitebrowser/sqlitebrowser.SlackBuild ("SLCKCFLAGS=...") Thanks for spotting it all fixed in 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 urchlay at slackware.uk Wed Aug 12 03:24:21 2026 From: urchlay at slackware.uk (B. Watson) Date: Tue, 11 Aug 2026 23:24:21 -0400 (EDT) Subject: [Slackbuilds-users] Easy typo In-Reply-To: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> Message-ID: On Tue, 11 Aug 2026, J. Milgram via SlackBuilds-users wrote: > I wonder if? this wouldn't be a good thing to append as a test > in sbopkglint? ... if the SlackBuild sets any variables named > SLCK... could be worth a closer look. That's a very good idea. Another one would be PKGNAM. If you have both PKGNAM and PRGNAM in the same script... well, in my font, they only differ by a couple of pixels. And I've seen a build that was screwed up by that. Another one would be PRGMAN (I dunno how many times I've typed that). From rizitis at gmail.com Wed Aug 12 08:39:58 2026 From: rizitis at gmail.com (Yiannis) Date: Wed, 12 Aug 2026 11:39:58 +0300 Subject: [Slackbuilds-users] Easy typo In-Reply-To: References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> Message-ID: If you add a check for both PKGNAM and PRGNAM if exist, please add it as a warning not error! I know that I have scripts that both of them used in the same script for a reason! thanks. ???? ??? 12 ??? 2026 ???? 6:29??.?., ?/? B. Watson ??????: > > > On Tue, 11 Aug 2026, J. Milgram via SlackBuilds-users wrote: > > > I wonder if this wouldn't be a good thing to append as a test > > in sbopkglint ... if the SlackBuild sets any variables named > > SLCK... could be worth a closer look. > > That's a very good idea. > > Another one would be PKGNAM. If you have both PKGNAM and PRGNAM in > the same script... well, in my font, they only differ by a couple of > pixels. And I've seen a build that was screwed up by that. > > Another one would be PRGMAN (I dunno how many times I've typed > that)._______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Aug 12 08:54:26 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 12 Aug 2026 15:54:26 +0700 Subject: [Slackbuilds-users] Easy typo In-Reply-To: References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> Message-ID: <20260812155426.4a47cc5d@office64.slackie.org> >If you add a check for both PKGNAM and PRGNAM if exist, please add it >as a warning not error! >I know that I have scripts that both of them used in the same script >for a reason! >thanks. yes, that's usually common name used when the program name and source is different -- 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 Wed Aug 12 09:32:29 2026 From: urchlay at slackware.uk (B. Watson) Date: Wed, 12 Aug 2026 05:32:29 -0400 (EDT) Subject: [Slackbuilds-users] Easy typo In-Reply-To: <20260812155426.4a47cc5d@office64.slackie.org> References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> <20260812155426.4a47cc5d@office64.slackie.org> Message-ID: <23d131cd-7fd1-5dea-407c-eef0d9e0a5c1@slackware.uk> On Wed, 12 Aug 2026, Willy Sudiarto Raharjo wrote: > yes, that's usually common name used when the program name and source > is different That's a terrible idea! I use SRCNAM for the source... it's the name of the source. PKGNAM would be "name of the package", but we're already using PRGNAM to mean the name of the Slackware package we're building. So it's kinda ambiguous. PRGNAM and PKGNAM look too similar IMO. I didn't think anyone would choose to deliberately use both, but apparently I'm wrong. However, a thought: if PKGNAM is never assigned to, *then* it's a typo if it's referenced... most likely if you never assigned anything to PKGNAM, then it's a typo for PRGNAM (same as PRGMAN would be). I haven't added any code to sbolint to do anything about this. Just kicking ideas around. I think we can all agree that SLCKFLAGS is always a typo though. Or PRGMAN. Or PGK. I made that typo myself last week, I wrote: gzip -9 $PGK/usr/man/man*/* Oh, what fun... fortunately gzip won't re-gzip a file that's already gzipped, so no real harm done, just a minor freak-out as a ton of "gzip: blah.gz already has .gz suffix" warnings spewed out. From rizitis at gmail.com Wed Aug 12 10:10:17 2026 From: rizitis at gmail.com (Yiannis) Date: Wed, 12 Aug 2026 13:10:17 +0300 Subject: [Slackbuilds-users] Easy typo In-Reply-To: <23d131cd-7fd1-5dea-407c-eef0d9e0a5c1@slackware.uk> References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> <20260812155426.4a47cc5d@office64.slackie.org> <23d131cd-7fd1-5dea-407c-eef0d9e0a5c1@slackware.uk> Message-ID: There are few scripts that use PRGNAM+PGKNAM in SBo and from what I saw in 3 I am the creator. In my case this happens because SRCNAM has also taken a value :D example: PRGNAM="abdownloadmanager-bin" VERSION=${VERSION:-1.8.7} SRCNAM=ABDownloadManager_"$VERSION"_linux_x64 PKGNAM=ABDownloadManager After all, we have to put something in these cases too and PRGNAM+SRCNAM+PKGNAM was convenient! BUT What I really want to inform you is this: recently I uploaded the slakfinder-app to SBo and I had this issue with the .desktop https://forge.slackware.nl/rizitis/slakfinder-app/src/branch/main/SBo.txt And since it doesn't throw an error but a hint, I left it as is. But I would like you to know this as information for sbopkglint and your opinion in general is of course welcome. ???? ??? 12 ??? 2026 ???? 12:37??.?., ?/? B. Watson ??????: > > > On Wed, 12 Aug 2026, Willy Sudiarto Raharjo wrote: > > > yes, that's usually common name used when the program name and source > > is different > > That's a terrible idea! > > I use SRCNAM for the source... it's the name of the source. PKGNAM > would be "name of the package", but we're already using PRGNAM to > mean the name of the Slackware package we're building. So it's kinda > ambiguous. > > PRGNAM and PKGNAM look too similar IMO. I didn't think anyone would > choose to deliberately use both, but apparently I'm wrong. > > However, a thought: if PKGNAM is never assigned to, *then* it's a typo > if it's referenced... most likely if you never assigned anything to > PKGNAM, then it's a typo for PRGNAM (same as PRGMAN would be). > > I haven't added any code to sbolint to do anything about this. > Just kicking ideas around. > > I think we can all agree that SLCKFLAGS is always a typo though. Or > PRGMAN. Or PGK. I made that typo myself last week, I wrote: > > gzip -9 $PGK/usr/man/man*/* > > Oh, what fun... fortunately gzip won't re-gzip a file that's already > gzipped, so no real harm done, just a minor freak-out as a ton of > "gzip: blah.gz already has .gz suffix" warnings spewed out. > _______________________________________________ > 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 Wed Aug 12 10:40:16 2026 From: urchlay at slackware.uk (B. Watson) Date: Wed, 12 Aug 2026 06:40:16 -0400 (EDT) Subject: [Slackbuilds-users] Easy typo In-Reply-To: References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> <20260812155426.4a47cc5d@office64.slackie.org> <23d131cd-7fd1-5dea-407c-eef0d9e0a5c1@slackware.uk> Message-ID: On Wed, 12 Aug 2026, Yiannis wrote: > BUT What I really want to inform you is this: > recently I uploaded the slakfinder-app to SBo and I had this issue with the .desktop https://forge.slackware.nl/rizitis/slakfinder-app/src/branch/main/SBo.txt For the record, here's the important part of SBo.txt: >> sbopkglint complain: >> Running test: 35-desktop...usr/share/applications/slakfinder.desktop: >> hint: value item "PackageManager" in key "Categories" >> in group "Desktop Entry" can be extended with another >> category among the following categories: Settings >> usr/share/applications/slakfinder.desktop: hint: value >> "Utility;PackageManager;System;" for key "Categories" in group >> "Desktop Entry" contains more than one main category; application >> might appear more than once in the application menu >> BUT the only way to turn it off is Settings;PackageManager; and >> Settings in Plasma 6 means "System Settings", which is clearly the >> wrong name for a search tool. So let it whine; it's a hint. :) > And since it doesn't throw an error but a hint, I left it as is. > But I would like you to know this as information for sbopkglint and your opinion in general is of course welcome. Yes, "let it whine" is likely the correct answer here. I've found that sometimes it's impossible to satisfy desktop-file-validate *and* make logical sense. sbopkglint just runs desktop-file-validate, which is supposed to check that a .desktop file conforms to the FreeDesktop.org standards for desktop files and categories: https://specifications.freedesktop.org/desktop-entry/latest/ https://specifications.freedesktop.org/menu/latest/category-registry.html [note: These are the latest versions of the spec; Slackware 15.0 supports slightly outdated specs. You're talking about Plasma 6 so you're on -current though] The standards are not 100% perfect or consistent. Also, desktop envronment implementors (like the KDE project) might not interpret them exactly as intended. It looks like the FDo standard intended "Settings" to be a catch-all for any kind of "settings" (not just "System Settings" as Plasma6 uses it). Who's right? Who's wrong? Who knows? Does an OS package manager count as "System Settings"? It looks like "System" would make more sense than "Settings", for slakfinder-app. Actually. Is slakfinder-app even a "Package Manager"? For slakfinder-app-6.0/README I see: Search packages in https://slakfinder.slackware.nl/index.php database. Click on package url and: read-explore-download package from your web browser. ...which *doesn't* sound like it actually "manages" packages (in the sense that, e.g. slackpkg or sbotools does, or something like aptitude on That Other OS). The description doesn't say anything about installing or upgrading packages. My opinion would be, if it doesn't install/remove/upgrade OS packages, it's not a package manager. Maybe it really should be a single category, "System" only? I probably spent too much time writing this, and I apologize for it taking too long to read... but hopefully this is more than just an email to you, it could end up as part of a "Maintainer FAQ" or "Maintainer Tips" page on the SBo site. From rizitis at gmail.com Wed Aug 12 10:57:16 2026 From: rizitis at gmail.com (Yiannis) Date: Wed, 12 Aug 2026 13:57:16 +0300 Subject: [Slackbuilds-users] Easy typo In-Reply-To: References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> <20260812155426.4a47cc5d@office64.slackie.org> <23d131cd-7fd1-5dea-407c-eef0d9e0a5c1@slackware.uk> Message-ID: Thank you for the answer. In fact I have my answer now, because it is not a real package manager as we know and probably since it only search for packages + download them I think Categories=Network;FileTransfer; is the correct? In any case a HOWTO for .desktop entries is worth it!! thank you. ???? ??? 12 ??? 2026 ???? 1:45??.?., ?/? B. Watson ??????: > > > On Wed, 12 Aug 2026, Yiannis wrote: > > > BUT What I really want to inform you is this: > > recently I uploaded the slakfinder-app to SBo and I had this issue with > the .desktop > https://forge.slackware.nl/rizitis/slakfinder-app/src/branch/main/SBo.txt > > For the record, here's the important part of SBo.txt: > > >> sbopkglint complain: > > >> Running test: 35-desktop...usr/share/applications/slakfinder.desktop: > >> hint: value item "PackageManager" in key "Categories" > >> in group "Desktop Entry" can be extended with another > >> category among the following categories: Settings > >> usr/share/applications/slakfinder.desktop: hint: value > >> "Utility;PackageManager;System;" for key "Categories" in group > >> "Desktop Entry" contains more than one main category; application > >> might appear more than once in the application menu > > >> BUT the only way to turn it off is Settings;PackageManager; and > >> Settings in Plasma 6 means "System Settings", which is clearly the > >> wrong name for a search tool. So let it whine; it's a hint. :) > > > And since it doesn't throw an error but a hint, I left it as is. > > But I would like you to know this as information for sbopkglint and your > opinion in general is of course welcome. > > Yes, "let it whine" is likely the correct answer here. I've found that > sometimes it's impossible to satisfy desktop-file-validate *and* make > logical sense. > > sbopkglint just runs desktop-file-validate, which is supposed to check that > a .desktop file conforms to the FreeDesktop.org standards for desktop files > and categories: > > https://specifications.freedesktop.org/desktop-entry/latest/ > > https://specifications.freedesktop.org/menu/latest/category-registry.html > > [note: These are the latest versions of the spec; Slackware 15.0 > supports slightly outdated specs. You're talking about Plasma 6 so > you're on -current though] > > The standards are not 100% perfect or consistent. Also, desktop > envronment implementors (like the KDE project) might not interpret > them exactly as intended. It looks like the FDo standard intended > "Settings" to be a catch-all for any kind of "settings" (not just > "System Settings" as Plasma6 uses it). Who's right? Who's wrong? Who > knows? Does an OS package manager count as "System Settings"? > > It looks like "System" would make more sense than "Settings", for > slakfinder-app. > > Actually. Is slakfinder-app even a "Package Manager"? For > slakfinder-app-6.0/README I see: > > Search packages in https://slakfinder.slackware.nl/index.php database. > Click on package url and: > read-explore-download package from your web browser. > > ...which *doesn't* sound like it actually "manages" packages (in > the sense that, e.g. slackpkg or sbotools does, or something like > aptitude on That Other OS). The description doesn't say anything about > installing or upgrading packages. My opinion would be, if it doesn't > install/remove/upgrade OS packages, it's not a package manager. > > Maybe it really should be a single category, "System" only? > > I probably spent too much time writing this, and I apologize for > it taking too long to read... but hopefully this is more than just > an email to you, it could end up as part of a "Maintainer FAQ" or > "Maintainer Tips" page on the SBo site. > _______________________________________________ > 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 Wed Aug 12 11:02:59 2026 From: urchlay at slackware.uk (B. Watson) Date: Wed, 12 Aug 2026 07:02:59 -0400 (EDT) Subject: [Slackbuilds-users] Easy typo In-Reply-To: References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> <20260812155426.4a47cc5d@office64.slackie.org> <23d131cd-7fd1-5dea-407c-eef0d9e0a5c1@slackware.uk> Message-ID: <979b582e-36eb-445-7fab-4a2fde69681@slackware.uk> On Wed, 12 Aug 2026, Yiannis wrote: > Thank you for the answer.? > In fact I have my answer now, because it is not a real package manager as we know? > and probably since it only search for packages + download them? > I think Categories=Network;FileTransfer; is the correct? That makes sense. And it's more specific than "System", which tends to be a catch-all category when people don't put much thought into picking a category... > In any case a HOWTO for .desktop entries is worth it!! Yeah. Maybe a whole new "Maintainer HOWTOs" section on the site. If I'm doing the writing, I tend to be long-winded, so it's better not to just jam all the unrelated stuff (.desktop files, cmake variable overrides, icons, using the correct -std= for CFLAGS, etc) into one long page. It'd be better if I wasn't the only one doing the writing. But a lot of this stuff never gets discussed, so I have no idea what other people do or don't know about it. From tonus1 at free.fr Wed Aug 12 11:12:54 2026 From: tonus1 at free.fr (Tonus) Date: Wed, 12 Aug 2026 13:12:54 +0200 Subject: [Slackbuilds-users] Python naming and sources Message-ID: <875x1f4mo9.fsf@Baldr.vingolf.info> Hi all While updating a few python related slackbuilds, I was wondering about source links. For sources from https://files.pythonhosted.org/, I thought we recommanded this kind of URL https://files.pythonhosted.org/packages/source/$PKG_INITIAL_LETTER/$PKG_NAME/$PKG_NAME-$$VERSION.tar.gz Could it land in the ressources page ? -- Regards, Tonus. From urchlay at slackware.uk Wed Aug 12 11:37:01 2026 From: urchlay at slackware.uk (B. Watson) Date: Wed, 12 Aug 2026 07:37:01 -0400 (EDT) Subject: [Slackbuilds-users] Python naming and sources In-Reply-To: <875x1f4mo9.fsf@Baldr.vingolf.info> References: <875x1f4mo9.fsf@Baldr.vingolf.info> Message-ID: <907ad2f9-e6fd-add6-8a8e-f13b277b835c@slackware.uk> On Wed, 12 Aug 2026, Tonus via SlackBuilds-users wrote: > Hi all > > While updating a few python related slackbuilds, I was wondering about > source links. > > For sources from https://files.pythonhosted.org/, I thought we > recommanded this kind of URL > https://files.pythonhosted.org/packages/source/$PKG_INITIAL_LETTER/$PKG_NAME/$PKG_NAME-$$VERSION.tar.gz > Could it land in the ressources page ? Yeah. We do prefer that. But nobody ever put it in a FAQ or anything, which we should. Noted. From rizitis at gmail.com Wed Aug 12 12:02:53 2026 From: rizitis at gmail.com (Yiannis) Date: Wed, 12 Aug 2026 15:02:53 +0300 Subject: [Slackbuilds-users] Easy typo In-Reply-To: <979b582e-36eb-445-7fab-4a2fde69681@slackware.uk> References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> <20260812155426.4a47cc5d@office64.slackie.org> <23d131cd-7fd1-5dea-407c-eef0d9e0a5c1@slackware.uk> <979b582e-36eb-445-7fab-4a2fde69681@slackware.uk> Message-ID: Please when you have free time read attachment. You will save a lot of time just to correct it than to create it from scratch ???? ??? 12 ??? 2026 ???? 2:08??.?., ?/? B. Watson ??????: > > > On Wed, 12 Aug 2026, Yiannis wrote: > > > Thank you for the answer. > > In fact I have my answer now, because it is not a real package manager > as we know > > and probably since it only search for packages + download them > > I think Categories=Network;FileTransfer; is the correct? > > That makes sense. And it's more specific than "System", which tends > to be a catch-all category when people don't put much thought into > picking a category... > > > In any case a HOWTO for .desktop entries is worth it!! > > Yeah. Maybe a whole new "Maintainer HOWTOs" section on the site. If > I'm doing the writing, I tend to be long-winded, so it's better not > to just jam all the unrelated stuff (.desktop files, cmake variable > overrides, icons, using the correct -std= for CFLAGS, etc) into one > long page. > > It'd be better if I wasn't the only one doing the writing. But a > lot of this stuff never gets discussed, so I have no idea what other > people do or don't know about > it._______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- ====================================================================== .desktop FILES FOR SLACKBUILDS - A SHORT GUIDE ====================================================================== If your package installs a .desktop file, this is what you need to get right. Everything here was tested with desktop-file-validate 0.27. ---------------------------------------------------------------------- THE LINE ---------------------------------------------------------------------- Categories=Network;WebBrowser;ConsoleOnly; Rules: - At least one MAIN category (the list below). Without it your program lands in a catch-all menu. - Additional categories are optional and make placement precise. - Case-sensitive. "network" is not "Network". - Anything not in the lists must start with X- -> X-Slackware - End with a semicolon. Technically optional, but everyone does it. ---------------------------------------------------------------------- MAIN CATEGORIES - pick one ---------------------------------------------------------------------- AudioVideo multimedia, audio and/or video Audio audio only (must also include AudioVideo) Video video only (must also include AudioVideo) Development programming tools Education educational software Game games Graphics images, drawing, 3D Network anything that talks over a network Office documents, mail, calendars Science scientific software Settings changes the USER'S desktop (theme, keyboard) System inspects or administers the MACHINE (logs, disks) Utility small tools that fit nowhere else Two main categories means the entry shows up in two menus. Rarely what you want. Do NOT use HealthFitness. It is in the newest spec draft but desktop-file-validate rejects it, so sbopkglint fails your package. ---------------------------------------------------------------------- ADDITIONAL CATEGORIES - the ones you will actually use ---------------------------------------------------------------------- Network WebBrowser Email Chat IRCClient FileTransfer P2P News Feed RemoteAccess Telephony Monitor Development Building Debugger IDE RevisionControl Profiling Translation WebDevelopment Office WordProcessor Spreadsheet Presentation Calendar Database Chart Finance Viewer Publishing Graphics 2DGraphics 3DGraphics RasterGraphics VectorGraphics Photography Scanning OCR Viewer AudioVideo Player Recorder Mixer Sequencer Midi Tuner TV AudioVideoEditing DiscBurning System Monitor Security FileTools FileManager Filesystem TerminalEmulator Emulator PackageManager Settings DesktopSettings HardwareSettings Printing Security Accessibility Utility Calculator Clock TextEditor TextTools Archiving Compression FileTools Game ActionGame AdventureGame ArcadeGame BoardGame BlocksGame CardGame KidsGame LogicGame RolePlaying Shooter Simulation SportsGame StrategyGame Emulator Science Astronomy Biology Chemistry Physics Math Robotics Education Geography Geology History Languages Literature ComputerScience MedicalSoftware DataVisualization Any ConsoleOnly Documentation Amusement Engineering Electronics GTK Qt If nothing matches exactly, add nothing. An approximate additional category is worse than none. ---------------------------------------------------------------------- SOME NEED A COMPANION ---------------------------------------------------------------------- A few additional categories expect a second one alongside them. Leave it out and the entry gets filed badly: RasterGraphics needs Graphics;2DGraphics VectorGraphics needs Graphics;2DGraphics OCR needs Graphics;Scanning FileManager needs System;FileTools Compression needs Utility;Archiving Printing needs HardwareSettings;Settings Mixer, Midi, Sequencer, Tuner need AudioVideo;Audio TV needs AudioVideo;Video Example: Categories=Graphics;RasterGraphics; wrong Categories=Graphics;2DGraphics;RasterGraphics; right ---------------------------------------------------------------------- HOW TO PICK ---------------------------------------------------------------------- Finish this sentence: "This program lets the user ______." Then match the verb to one main category, and add one additional category if a precise one exists. browses the web in a terminal Categories=Network;WebBrowser;ConsoleOnly; Terminal=true edits photographs Categories=Graphics;2DGraphics;RasterGraphics;Photography; sets volume and picks an output device Categories=AudioVideo;Audio;Mixer; watches CPU and memory Categories=System;Monitor; manages files Categories=System;FileTools;FileManager; takes notes Categories=Utility;TextEditor; plays a Tetris clone Categories=Game;BlocksGame; is Slackware-specific with no good fit Categories=System;X-Slackware; ---------------------------------------------------------------------- THE OTHER KEYS ---------------------------------------------------------------------- Terminal=true Required for any console program. Forget it and clicking the menu entry appears to do nothing at all. Version=1.0 Version of the SPECIFICATION, not of your program. Accepted values are 1.0 to 1.5. This trips up nearly everyone once. Icon=foo A name from the icon theme - no path, no extension. Ship the icon upstream provides: mkdir -p $PKG/usr/share/icons/hicolor/48x48/apps cat $CWD/$PRGNAM.png \ > $PKG/usr/share/icons/hicolor/48x48/apps/$PRGNAM.png and use Icon=$PRGNAM. The Icon Naming Specification says an application must either install an icon named after its executable, or use one of the generic APPLICATION names - and it explicitly says application icons must not fall back to generic mimetype icons. NO ICON AT ALL? Leave the Icon= line out entirely. It is not a required key, the file validates clean without it, and the desktop then picks its own fallback - which is guaranteed to exist. Do not borrow a mimetype name like package-x-generic: it is the wrong context, and whether it exists depends on the user's theme. Nothing checks that the icon exists. A wrong name passes every test and gives the user a blank square. Keywords=archive;download;fetch; Extra menu search terms. Semicolons, never commas - the comma form is old KDE syntax, nothing flags it, and it collapses into one useless keyword. NoDisplay=true Valid entry, hidden from menus. For MIME-handler helpers. Encoding=UTF-8 Obsolete. Delete the line if upstream ships it. ---------------------------------------------------------------------- WHAT SBOPKGLINT CHECKS ---------------------------------------------------------------------- Build the package, then run sbopkglint. Its desktop test wants: 1. desktop-file-validate must exit 0. Only errors matter. Hints and warnings are printed but do not fail the test - so read the log even when it says OK. 2. Mode 644, owner root:root. Add an explicit chmod 644 in the SlackBuild; nothing else guarantees it. 3. Only .desktop files in /usr/share/applications (plus *-mimeapps.list, which is allowed). 4. doinst.sh MUST run update-desktop-database: if [ -x /usr/bin/update-desktop-database ]; then /usr/bin/update-desktop-database -q usr/share/applications \ >/dev/null 2>&1 fi Ship icons too? Then it also wants gtk-update-icon-cache. To check one file without rebuilding: desktop-file-validate foo.desktop Silence means clean. ---------------------------------------------------------------------- A COMPLETE EXAMPLE ---------------------------------------------------------------------- [Desktop Entry] Type=Application Version=1.0 Name=foo GenericName=Remote Archive Fetcher Comment=Download files from a remote archive Exec=foo Icon=foo Terminal=true Categories=Network;FileTransfer;ConsoleOnly; Keywords=archive;download;fetch; Icon=foo assumes the package installs its own icon as /usr/share/icons/hicolor/48x48/apps/foo.png. If it has no icon, delete the Icon= line - do not substitute a stock mimetype name. In the SlackBuild: mkdir -p $PKG/usr/share/applications cat $CWD/$PRGNAM.desktop \ > $PKG/usr/share/applications/$PRGNAM.desktop chmod 644 $PKG/usr/share/applications/$PRGNAM.desktop ---------------------------------------------------------------------- WHEN IN DOUBT ---------------------------------------------------------------------- See what real packages already do: grep -h ^Categories= /usr/share/applications/*.desktop \ | sort | uniq -c | sort -rn | head -20 Full category lists: https://specifications.freedesktop.org/menu/latest/ ====================================================================== From jebrhansen+SBo at gmail.com Wed Aug 12 12:15:03 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 12 Aug 2026 05:15:03 -0700 Subject: [Slackbuilds-users] Python naming and sources In-Reply-To: <907ad2f9-e6fd-add6-8a8e-f13b277b835c@slackware.uk> References: <875x1f4mo9.fsf@Baldr.vingolf.info> <907ad2f9-e6fd-add6-8a8e-f13b277b835c@slackware.uk> Message-ID: On Wed, Aug 12, 2026, 4:42?AM B. Watson wrote: > > > On Wed, 12 Aug 2026, Tonus via SlackBuilds-users wrote: > > > Hi all > > > > While updating a few python related slackbuilds, I was wondering about > > source links. > > > > For sources from https://files.pythonhosted.org/, I thought we > > recommanded this kind of URL > > > https://files.pythonhosted.org/packages/source/$PKG_INITIAL_LETTER/$PKG_NAME/$PKG_NAME-$$VERSION.tar.gz > > Could it land in the ressources page ? > > Yeah. We do prefer that. But nobody ever put it in a FAQ or anything, > which we should. Noted. > I did write a helper function/script that will auto correct github and pythonhosted source URLs to a working format... in case anyone is interested: https://github.com/bassmadrigal/scripts/blob/master/check-source-download.sh I've been using the basis of it for years in my sbgen.sh script and haven't found any issues. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Wed Aug 12 18:34:07 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 12 Aug 2026 11:34:07 -0700 Subject: [Slackbuilds-users] I will no longer maintain SlackBuilds from Aug 15 onwards In-Reply-To: <1YJ3SC0PayeJy1wzNgiqY32N2M0anMDUR8t1twRshWHhhszkFvXB6gLmH89AzzPp8xOG7Ia9zkRVcgREMAbZVLfIyroz5uMu5HJcNB1II3Y=@protonmail.com> References: <1YJ3SC0PayeJy1wzNgiqY32N2M0anMDUR8t1twRshWHhhszkFvXB6gLmH89AzzPp8xOG7Ia9zkRVcgREMAbZVLfIyroz5uMu5HJcNB1II3Y=@protonmail.com> Message-ID: Isaac, Thanks for all your years of service to SBo and best of luck to your future! I can take the following as dependencies for the packages I currently maintain: network/tut python/python3-defusedxml python/python3-pynacl I've already pushed the maintainer changes to my branch. If you do ever come back and want any of these back, I'm happy to give them back to you. Again, best of luck! Jeremy PS Here are the remaining SlackBuilds from Isaac that are up for grabs: academic/mathjax2 audio/Ymuse audio/mpd audio/pavucontrol-qt desktop/Matcha-gtk-theme desktop/SysTray-X desktop/bemenu desktop/bibata-cursor-theme desktop/birdtray desktop/cinnamon-desktop desktop/dwmblocks desktop/flat-remix desktop/gsimplecal desktop/libqt6xdg desktop/libqtxdg desktop/lightdm-slick-greeter desktop/lxqt-menu-data desktop/lxqt-panel desktop/lxqt-runner desktop/lxqt-themes desktop/naps2 desktop/qtile desktop/qtile-extras desktop/xsecurelock desktop/yaru-icon-theme development/extra-cmake-modules-opt development/jupyter-ipykernel development/jupyter-nbclient development/jupyter-nbconvert development/jupyter-nbformat development/jupyter-notebook development/jupyter-notebook_shim development/jupyter-qtconsole development/jupyter_client development/jupyter_console development/jupyter_core development/jupyter_events development/jupyter_packaging development/jupyter_server development/jupyter_server_terminals development/jupyterlab development/jupyterlab_pygments development/jupyterlab_server development/protoc-gen-go development/protoc-gen-go-grpc development/python3-spyder-kernels development/rstudio-desktop development/rstudio-desktop-legacy development/spyder graphics/ctpv graphics/lximage-qt graphics/screengrab graphics/vimiv-qt graphics/xviewer libraries/grpc libraries/kidletime6 libraries/kwindowsystem6 libraries/layer-shell-qt6 libraries/libdbusmenu-lxqt libraries/libfm-qt libraries/libfm-qt6 libraries/libkscreen6 libraries/liblxqt libraries/libminizip libraries/libsysstat libraries/lxqt-build-tools libraries/lxqt-build-tools-qt6 libraries/lxqt-notificationd libraries/lxqt-qt6plugin libraries/lxqt-qtplugin libraries/lxqt-sudo libraries/plasma-wayland-protocols-opt libraries/polkit-qt6-1 libraries/python3-PyQtWebEngine libraries/qt5gtk2 libraries/qt6gtk2 libraries/re2 libraries/solid6 network/proton-vpn-cli network/proton-vpn-local-agent network/warpinator network/wego office/hunspell-en office/xed office/xreader python/python2-asn1crypto python/python2-atomicwrites python/python2-pluggy python/python2-py python/python3-argon2-cffi python/python3-argon2-cffi-bindings python/python3-arrow python/python3-async-lru python/python3-comm python/python3-construct python/python3-cookiecutter python/python3-dbus-fast python/python3-dbus-next python/python3-debugpy python/python3-diff-match-patch python/python3-docstring-to-markdown python/python3-entrypoints python/python3-et_xmlfile python/python3-exiv2 python/python3-fastjsonschema python/python3-fqdn python/python3-gensim python/python3-gnupg python/python3-grpcio python/python3-hatch-nodejs-version python/python3-hatch_jupyter_builder python/python3-inflection python/python3-intervaltree python/python3-ipython-pygments-lexers python/python3-ipython-sql python/python3-ipython_genutils python/python3-isoduration python/python3-jinja2-time python/python3-json-logger python/python3-jsonpatch python/python3-jsonpointer python/python3-lsp-black python/python3-lsp-jsonrpc python/python3-lsp-server python/python3-mistune python/python3-narwhals python/python3-nest_asyncio python/python3-numpydoc python/python3-openpyxl python/python3-overrides python/python3-pandocfilters python/python3-patsy python/python3-plotly python/python3-prometheus_client python/python3-proton-core python/python3-proton-keyring-linux python/python3-proton-vpn-api-core python/python3-pulsectl-asyncio python/python3-pydocstyle python/python3-pyinotify python/python3-pykeepass python/python3-pylint-venv python/python3-pyls-spyder python/python3-pyrsistent python/python3-pytoolconfig python/python3-pyudev python/python3-qstylizer python/python3-qtawesome python/python3-regex python/python3-requests-unixsocket python/python3-rfc3339_validator python/python3-rfc3986_validator python/python3-rope python/python3-rtree python/python3-seaborn python/python3-secretstorage python/python3-sentry_sdk python/python3-setproctitle python/python3-shtab python/python3-smart_open python/python3-sortedcontainers python/python3-statsmodels python/python3-tabulate python/python3-tenacity python/python3-terminado python/python3-testpath python/python3-textdistance python/python3-three-merge python/python3-tinycss2 python/python3-uri_template python/python3-watchdog python/python3-webcolors python/python3-whatthepatch python/python3-wurlitzer python/python3-xcffib python/python3-zeroconf system/FontAwesome system/OpenSnitch system/file-roller system/fscrypt system/grub2-theme-mint system/libtrash system/lightdm system/lightdm-settings system/lxqt-about system/lxqt-admin system/lxqt-archiver system/lxqt-config system/lxqt-globalkeys system/lxqt-openssh-askpass system/lxqt-policykit system/lxqt-powermanagement system/lxqt-session system/nemo system/nemo-fileroller system/pass-import system/pcmanfm-qt system/powerline-fonts system/qps system/qtxdg-tools system/tbsm system/trash-cli system/ttf-ubuntu-font-family On Sun, Aug 9, 2026 at 11:15?PM Isaac Yu via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hi everyone, > > This is the last weekly cycle in which I will maintain/update SlackBuilds. > I will no longer do so from Aug 15 onwards. > > I previously said that I would no longer maintain SlackBuilds last > Christmas, but I kept continuing to do so. > Sorry about that - the main reason was that getting LXQt to v2 was less > stressful than I initially thought (which prompted me to make that claim > last Christmas). > > I mean it this time. > Software (and by extension SlackBuilds) are getting more and more > complicated to maintain. > > My main motivation recently has been to prepare for a new release of > Slackware (ex. 15.1, 16.0, etc.) > I'm actually using Linux Mint Debian right now as my main day-to-day > operating system. > I've been testing updates through Slackware virtual machines. > > I might return when the first alpha of the next Slackware version gets > released (ex. 15.1-alpha1.) > > To the SlackBuilds.org team: > My suggestion is to orphan my SlackBuilds only when the next version of > Slackware is about to get released. > I might make a hotfix SlackBuild update even during the Slackware 15.0 > cycle (ex. protobuf gets updated, making python3-grpcio unable to build.) > However, you may orphan them next week if you like. > > - Isaac > _______________________________________________ > 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 Wed Aug 12 20:29:45 2026 From: urchlay at slackware.uk (B. Watson) Date: Wed, 12 Aug 2026 16:29:45 -0400 (EDT) Subject: [Slackbuilds-users] Easy typo In-Reply-To: References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> <20260812155426.4a47cc5d@office64.slackie.org> <23d131cd-7fd1-5dea-407c-eef0d9e0a5c1@slackware.uk> <979b582e-36eb-445-7fab-4a2fde69681@slackware.uk> Message-ID: <681bbd5-5a20-7693-82e3-e1f4a8817bfd@slackware.uk> On Wed, 12 Aug 2026, Yiannis wrote: > Please when you have free time read attachment. > You will save a lot of time just to correct it than to create it from > scratch That's *nice*! It won't need much correction. I might add a few things to it, but what you wrote will need very few changes. Thanks for doing this. From urchlay at slackware.uk Wed Aug 12 20:38:15 2026 From: urchlay at slackware.uk (B. Watson) Date: Wed, 12 Aug 2026 16:38:15 -0400 (EDT) Subject: [Slackbuilds-users] Python naming and sources In-Reply-To: References: <875x1f4mo9.fsf@Baldr.vingolf.info> <907ad2f9-e6fd-add6-8a8e-f13b277b835c@slackware.uk> Message-ID: <4de04a23-1e31-fa8-9a2b-669f85861518@slackware.uk> On Wed, 12 Aug 2026, Jeremy Hansen wrote: > I did write a helper function/script that will auto correct github and > pythonhosted source URLs to a working format... in case anyone is > interested:? > > https://github.com/bassmadrigal/scripts/blob/master/check-source-download.s > h > > I've been using the basis of it for years in my sbgen.sh script and haven't > found any issues. I would add the python URL part of this to sbolint, except it's in bash and sbolint is in perl. sbolint already canonicalizes github URLs, I'll add a perl version of your logic. From lumin+slackbuilds at etherlight.link Wed Aug 12 23:15:12 2026 From: lumin+slackbuilds at etherlight.link (Lumin Etherlight) Date: Thu, 13 Aug 2026 02:15:12 +0300 Subject: [Slackbuilds-users] Easy typo In-Reply-To: <23d131cd-7fd1-5dea-407c-eef0d9e0a5c1@slackware.uk> (B. Watson's message of "Wed, 12 Aug 2026 05:32:29 -0400 (EDT)") References: <26db56c5-ea44-4ba4-9990-1110666661d1@cgpp.com> <20260812155426.4a47cc5d@office64.slackie.org> <23d131cd-7fd1-5dea-407c-eef0d9e0a5c1@slackware.uk> Message-ID: "B. Watson" writes: > However, a thought: if PKGNAM is never assigned > to, *then* it's a typo if it's referenced... most > likely if you never assigned anything to PKGNAM, > then it's a typo for PRGNAM (same as PRGMAN would > be). I suggest using ShellCheck (ShellCheck-bin), as it catches such errors, and more. I use it in all my bash & POSIX shell scripting. The typical SlackBuild template shows a lot of warnings about quoting, which you can easily ignore by running it like this: shellcheck -e SC2086,SC2046 *.SlackBuild This preserves its ability to detected other errors, such as the use of a variable without any assignment to it, while not flooding your terminal with dozens of "Double quote to prevent globbing and word splitting." warnings. Best Wishes, Lumin Etherlight From willysr at slackbuilds.org Wed Aug 12 23:35:30 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 13 Aug 2026 06:35:30 +0700 Subject: [Slackbuilds-users] Python naming and sources In-Reply-To: References: <875x1f4mo9.fsf@Baldr.vingolf.info> <907ad2f9-e6fd-add6-8a8e-f13b277b835c@slackware.uk> Message-ID: <20260813063530.5e542726@home.slackie.org> >> > While updating a few python related slackbuilds, I was wondering about >> > source links. >> > >> > For sources from https://files.pythonhosted.org/, I thought we >> > recommanded this kind of URL >> > >> https://files.pythonhosted.org/packages/source/$PKG_INITIAL_LETTER/$PKG_NAME/$PKG_NAME-$$VERSION.tar.gz >> > Could it land in the ressources page ? For now https://slackbuilds.org/PYPI_URLs.txt i will add it to resources page later -- 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 chris.willing at linux.com Thu Aug 13 01:47:05 2026 From: chris.willing at linux.com (Christoph Willing) Date: Thu, 13 Aug 2026 11:47:05 +1000 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> Message-ID: <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> On 11/8/26 07:38, Greg Tourte wrote: > Willy, > > does that include package which explicitly state in the README that > the package require the newer GLIBC? > > I maintain one such script (signal-desktop) and it would be a shame to > see it removed from the repo. I suggest reverting the VERSION to the last one that worked without newer GLIBC - I guess 8.1.0 (as for signal-desktop-legacy, which could then be removed). The README could then be expanded to mention that later versions would require the newer GLIBC but could still be "built" by setting the VERSION appropriately in the environment e.g. ? ? VERSION=8.21.0 bash signal-desktop.SlackBuild Whenever a new version is released, the README could be updated acccordingly rather than updating signal-desktop.{info,SlackBuild} as would normally be the case This way a user would always be able to run the latest version provided they install the newer GLIBC (which they already need to do at the moment anyway). chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Aug 13 02:29:50 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 13 Aug 2026 09:29:50 +0700 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> Message-ID: <20260813092950.30a8f4c2@office64.slackie.org> >I suggest reverting the VERSION to the last one that worked without >newer GLIBC - I guess 8.1.0 (as for signal-desktop-legacy, which could >then be removed). The README could then be expanded to mention that >later versions would require the newer GLIBC but could still be >"built" by setting the VERSION appropriately in the environment e.g. > ? ? VERSION=8.21.0 bash signal-desktop.SlackBuild > >Whenever a new version is released, the README could be updated >acccordingly rather than updating signal-desktop.{info,SlackBuild} as >would normally be the case > >This way a user would always be able to run the latest version >provided they install the newer GLIBC (which they already need to do >at the moment anyway). This is the same thing that i did with libreoffice (binary repack) https://slackbuilds.org/repository/15.0/office/libreoffice/ it stuck at 25.8.x branch due to GLIBC -- 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 Thu Aug 13 02:40:13 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 13 Aug 2026 09:40:13 +0700 Subject: [Slackbuilds-users] Python naming and sources In-Reply-To: <20260813063530.5e542726@home.slackie.org> References: <875x1f4mo9.fsf@Baldr.vingolf.info> <907ad2f9-e6fd-add6-8a8e-f13b277b835c@slackware.uk> <20260813063530.5e542726@home.slackie.org> Message-ID: <20260813094013.20282f0c@office64.slackie.org> >>> https://files.pythonhosted.org/packages/source/$PKG_INITIAL_LETTER/$PKG_NAME/$PKG_NAME-$$VERSION.tar.gz >>> > Could it land in the ressources page ? > >For now >https://slackbuilds.org/PYPI_URLs.txt > >i will add it to resources page later It's added now -- 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 lumin+slackbuilds at etherlight.link Thu Aug 13 03:58:39 2026 From: lumin+slackbuilds at etherlight.link (Lumin Etherlight) Date: Thu, 13 Aug 2026 06:58:39 +0300 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: <20260813092950.30a8f4c2@office64.slackie.org> (Willy Sudiarto Raharjo's message of "Thu, 13 Aug 2026 09:29:50 +0700") References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> <20260813092950.30a8f4c2@office64.slackie.org> Message-ID: Willy Sudiarto Raharjo writes: > Christoph Willing writes: >> >> I suggest reverting the VERSION to the last one >> that worked without newer GLIBC - I guess 8.1.0 > > This is the same thing that i did with libreoffice Signal blocks old versions of their software from connecting to the network. I had to figure out the binary patching thing because the last 15.0 glibc-compatible version I had was finally blocked from connecting to the Signal network. If patching the rpath to use an isolated new glibc-opt without migrating the whole OS is not an acceptable solution for the SlackBuilds.org repo, then removing the Signal SlackBuild is the option that makes sense, in my opinion. People who still want to use Signal will have to install it from a different 3rd party. If that happens, I might end up packaging the patched version myself, and then redistribute it on my site for others to use. Thank you all for your meticulous work, pretty active here recently :) Best Wishes, Lumin Etherlight From willysr at slackbuilds.org Thu Aug 13 04:12:55 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 13 Aug 2026 11:12:55 +0700 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> <20260813092950.30a8f4c2@office64.slackie.org> Message-ID: <20260813111255.07bda649@office64.slackie.org> > Signal blocks old versions of their software > from connecting to the network. I had to figure > out the binary patching thing because the last > 15.0 glibc-compatible version I had was finally > blocked from connecting to the Signal network. > > If patching the rpath to use an isolated new > glibc-opt without migrating the whole OS is not an > acceptable solution for the SlackBuilds.org repo, > then removing the Signal SlackBuild is the option > that makes sense, in my opinion. People who still > want to use Signal will have to install it from a > different 3rd party. If that happens, I might end > up packaging the patched version myself, and then > redistribute it on my site for others to use. What about the AppImage format? will that work? i assume it's all contained in a single package, so no link to system-based GLIBC -- 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 rizitis at gmail.com Thu Aug 13 09:05:03 2026 From: rizitis at gmail.com (Yiannis) Date: Thu, 13 Aug 2026 12:05:03 +0300 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: <20260813111255.07bda649@office64.slackie.org> References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> <20260813092950.30a8f4c2@office64.slackie.org> <20260813111255.07bda649@office64.slackie.org> Message-ID: Please give me some time, I have an idea and it looks that works! When I finish and be sure I will upload it here and IF maintainer and SBo admins agree you can adopt it. ???? ??? 13 ??? 2026 ???? 7:13??.?., ?/? Willy Sudiarto Raharjo < willysr at slackbuilds.org> ??????: > > Signal blocks old versions of their software > > from connecting to the network. I had to figure > > out the binary patching thing because the last > > 15.0 glibc-compatible version I had was finally > > blocked from connecting to the Signal network. > > > > If patching the rpath to use an isolated new > > glibc-opt without migrating the whole OS is not an > > acceptable solution for the SlackBuilds.org repo, > > then removing the Signal SlackBuild is the option > > that makes sense, in my opinion. People who still > > want to use Signal will have to install it from a > > different 3rd party. If that happens, I might end > > up packaging the patched version myself, and then > > redistribute it on my site for others to use. > > > What about the AppImage format? > will that work? > i assume it's all contained in a single package, so no link to > system-based GLIBC > > > -- > Willy Sudiarto Raharjo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lumin+slackbuilds at etherlight.link Thu Aug 13 10:57:23 2026 From: lumin+slackbuilds at etherlight.link (Lumin Etherlight) Date: Thu, 13 Aug 2026 13:57:23 +0300 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: <20260813111255.07bda649@office64.slackie.org> (Willy Sudiarto Raharjo's message of "Thu, 13 Aug 2026 11:12:55 +0700") References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> <20260813092950.30a8f4c2@office64.slackie.org> <20260813111255.07bda649@office64.slackie.org> Message-ID: Willy Sudiarto Raharjo writes: >> Lumin Etherlight writes: >> >> Signal blocks old versions of their software >> from connecting to the network. I had to figure >> out the binary patching thing because the last >> 15.0 glibc-compatible version I had was finally >> blocked from connecting to the Signal network. >> >> If patching the rpath to use an isolated new >> glibc-opt without migrating the whole OS is not an >> acceptable solution for the SlackBuilds.org repo, >> then removing the Signal SlackBuild is the option >> that makes sense, in my opinion. People who still >> want to use Signal will have to install it from a >> different 3rd party. If that happens, I might end >> up packaging the patched version myself, and then >> redistribute it on my site for others to use. > > What about the AppImage format? will that work? > i assume it's all contained in a single package, > so no link to system-based GLIBC No, the AppImage links against the system's glibc, not a bundled glibc. I just tested it on a 15.0 system with the stable glibc version, it did not work, with the usual errors. Upgrading to the testing glibc libraries allows the AppImage to run as expected. So, no, this will not help us. Best Regards, Lumin Etherlight From rizitis at gmail.com Thu Aug 13 11:06:30 2026 From: rizitis at gmail.com (Yiannis) Date: Thu, 13 Aug 2026 14:06:30 +0300 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> <20260813092950.30a8f4c2@office64.slackie.org> <20260813111255.07bda649@office64.slackie.org> Message-ID: Just to be clear, this is not the same as installing the testing glibc. Nothing on the system changes. System glibc stays 2.33. No upgradepkg of a core package, no ld.so.conf, no ldconfig. What the script does: - unpacks the snap into /opt/Signal/signal-desktop - unpacks aaa_glibc-solibs-2.42 into the same prefix, as a build source like any tarball - patchelf on the Electron binary so its PT_INTERP and DT_RPATH point there So those .so files are reachable by exactly one binary. Nothing else on the machine can see them, and removepkg takes them all with it. Checked: /proc/PID/maps across all 7 Signal processes shows only the bundled libc, never the host 2.33. QR link, full history sync, send and receive all work. sbopkglint passes. Attached if anyone wants to look. IF admins and the maintainer agree with that then a desktop entry and an icon needed, now run only from the terminal. Thank you. ???? ??? 13 ??? 2026 ???? 12:05??.?., ?/? Yiannis ??????: > Please give me some time, I have an idea and it looks that works! > When I finish and be sure I will upload it here and IF maintainer and SBo > admins agree you can adopt it. > > > ???? ??? 13 ??? 2026 ???? 7:13??.?., ?/? Willy Sudiarto Raharjo < > willysr at slackbuilds.org> ??????: > >> > Signal blocks old versions of their software >> > from connecting to the network. I had to figure >> > out the binary patching thing because the last >> > 15.0 glibc-compatible version I had was finally >> > blocked from connecting to the Signal network. >> > >> > If patching the rpath to use an isolated new >> > glibc-opt without migrating the whole OS is not an >> > acceptable solution for the SlackBuilds.org repo, >> > then removing the Signal SlackBuild is the option >> > that makes sense, in my opinion. People who still >> > want to use Signal will have to install it from a >> > different 3rd party. If that happens, I might end >> > up packaging the patched version myself, and then >> > redistribute it on my site for others to use. >> >> >> What about the AppImage format? >> will that work? >> i assume it's all contained in a single package, so no link to >> system-based GLIBC >> >> >> -- >> Willy Sudiarto Raharjo >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signal-desktop.tar.gz Type: application/gzip Size: 2723 bytes Desc: not available URL: From chris.willing at linux.com Thu Aug 13 13:30:36 2026 From: chris.willing at linux.com (Christoph Willing) Date: Thu, 13 Aug 2026 23:30:36 +1000 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> <20260813092950.30a8f4c2@office64.slackie.org> <20260813111255.07bda649@office64.slackie.org> Message-ID: <5732a108-3c03-48f8-b47b-ac1c005783ba@linux.com> I've never use signal before so can't check history but QR link & sync seem to work OK here. I'm not sure if it meets all other admins requirements but if put to a vote my vote would be "aye" if only because it's such a cute solution. chris On 13/8/26 21:06, Yiannis wrote: > Just to be clear, this is not the same as installing the testing glibc. > > Nothing on the system changes. System glibc stays 2.33. No upgradepkg > of a core package, no ld.so.conf, no ldconfig. > > What the script does: > > - unpacks the snap into /opt/Signal/signal-desktop > - unpacks aaa_glibc-solibs-2.42 into the same prefix, as a build > source like any tarball > - patchelf on the Electron binary so its PT_INTERP and DT_RPATH point > there > > So those .so files are reachable by exactly one binary. Nothing else > on the machine can see them, and removepkg takes them all with it. > > Checked: /proc/PID/maps across all 7 Signal processes shows only the > bundled libc, never the host 2.33. QR link, full history sync, send > and receive all work. sbopkglint passes. > > Attached if anyone wants to look. > > IF admins and the maintainer agree with that then a desktop entry and > an icon needed, now run only from the terminal. > > Thank you. > > ???? ??? 13 ??? 2026 ???? 12:05??.?., ?/? Yiannis > ??????: > > Please give me some time, I have an idea and it looks that works! > When I finish and be sure I will upload it here and IF maintainer > and SBo admins agree you can adopt it. > > > ???? ??? 13 ??? 2026 ???? 7:13??.?., ?/? Willy Sudiarto Raharjo > ??????: > > > ? ? ? Signal blocks old versions of their software > >? from connecting? to the network.? I? had to figure > >? out? the binary? patching thing? because the? last > >? 15.0? glibc-compatible version? I had? was finally > >? blocked from connecting to the Signal network. > > > >? ? ? ? If patching the rpath to use an isolated new > >? glibc-opt without migrating the whole OS is not an > >? acceptable solution for? the SlackBuilds.org repo, > >? then removing the Signal? SlackBuild is the option > >? that makes sense, in my opinion.? People who still > >? want to use Signal will? have to install it from a > >? different 3rd party.? If that happens, I might end > >? up packaging the patched? version myself, and then > >? redistribute it on my site for others to use. > > > What about the AppImage format? > will that work? > i assume it's all contained in a single package, so no link to > system-based GLIBC > > > -- > Willy Sudiarto Raharjo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > _______________________________________________ > 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 lumin+slackbuilds at etherlight.link Thu Aug 13 16:26:32 2026 From: lumin+slackbuilds at etherlight.link (Lumin Etherlight) Date: Thu, 13 Aug 2026 19:26:32 +0300 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: (Yiannis's message of "Thu, 13 Aug 2026 14:06:30 +0300") References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> <20260813092950.30a8f4c2@office64.slackie.org> <20260813111255.07bda649@office64.slackie.org> Message-ID: Yiannis writes: > Just to be clear, this is not the same as > installing the testing glibc. Nothing on the > system changes. System glibc stays 2.33. No > upgradepkg of a core package, no ld.so.conf, no > ldconfig. > > What the script does: > > - unpacks the snap into /opt/Signal/signal-desktop > - unpacks aaa_glibc-solibs-2.42 into the same > prefix, as a build source like any tarball > - patchelf on the Electron binary so its PT_INTERP > and DT_RPATH point there I don't see how this differs in a meaningful way from the existing solution that was refused by the SBo admins. The only minor difference is that you're extracting Signal from a snap instead of a .deb archive. The testing glibc is installed into /opt, and Signal binaries are patched to point to that glibc instead of the system one. If there's some other important difference here, please do explain it a bit more. Best Regards, Lumin Etherlight From tonus1 at free.fr Thu Aug 13 16:46:34 2026 From: tonus1 at free.fr (Tonus) Date: Thu, 13 Aug 2026 18:46:34 +0200 Subject: [Slackbuilds-users] I will no longer maintain SlackBuilds from Aug 15 onwards In-Reply-To: (Jeremy Hansen's message of "Wed, 12 Aug 2026 11:34:07 -0700") References: <1YJ3SC0PayeJy1wzNgiqY32N2M0anMDUR8t1twRshWHhhszkFvXB6gLmH89AzzPp8xOG7Ia9zkRVcgREMAbZVLfIyroz5uMu5HJcNB1II3Y=@protonmail.com> Message-ID: <87o6f62ck5.fsf@Baldr.vingolf.info> Jeremy Hansen writes: > Isaac, > > Thanks for all your years of service to SBo and best of luck to > your future! > > I can take the following as dependencies for the packages I > currently maintain: > > network/tut > python/python3-defusedxml > python/python3-pynacl > > I've already pushed the maintainer changes to my branch. > > If you do ever come back and want any of these back, I'm happy to > give them back to you. > > Again, best of luck! > Jeremy > > PS Here are the remaining SlackBuilds from Isaac that are up for > grabs: > Hi, If needed I could upgrade these since they are deps of mine (calcure, todoman). > python/python3-tabulate > python/python3-arrow These I can't find any reason I have them (no deps/rdeps) but still... Might figure out sometime. (If someone could have a clue...) > python/python3-tenacity > python/python3-exiv2 (optional for gramps ?) I use these and could take care of them if needed. > audio/mpd > system/FontAwesome > system/pass-import Let me know if I have to write a note for my future self to pay attention when the freeze will happen or anything else. -- Regards, Tonus. From rizitis at gmail.com Thu Aug 13 17:36:38 2026 From: rizitis at gmail.com (Yiannis) Date: Thu, 13 Aug 2026 20:36:38 +0300 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> <20260813092950.30a8f4c2@office64.slackie.org> <20260813111255.07bda649@office64.slackie.org> Message-ID: You're right that the technique is the same -- bundled glibc, patched interpreter and rpath. I took $ORIGIN and the patch-everything loop from your script. The difference isn't technical, it's what each one asks the repo for. Yours needs a second thing to exist: either a glibc-opt-bin SlackBuild in the repo, or the user runs your apply script by hand. That's what Willy refused -- not the patching, but adding a shared glibc to SBo that other scripts could then depend on. He called it all or nothing, and he was right about that: once glibc-opt-bin exists in the repo, it's a package the admins have to maintain, and your own message anticipated other packages following the same pattern. Now doesn't create anything shared. The .txz is a build-time source, extracted into the package payload the same way any tarball is. What gets installed is a set of .so files under /opt/Signal/signal-desktop/lib64/, reachable only through one binary's PT_INTERP and DT_RPATH. No second package, no REQUIRES, nothing on the system another script could ever link against. It's vendored libraries in one package, which SBo already accepts elsewhere. Concretely, from a user's point of view: - installpkg and it works; no apply step - removepkg takes all of it, including the glibc; no revert step, no /opt/glibc left behind - survives upgradepkg, because the patching is in the SlackBuild rather than something to re-run afterwards - the source has an md5sum in the .info, instead of required a glibc package - system glibc stays 2.33 and no other package sees 2.42 So the question for the admins stops being "can SBo ship a glibc" and becomes "can one package carry private libraries under /opt", which is a much smaller question. Its like you run an independent signal-desktop.AppImage with the required glibc included :) ???? ??? 13 ??? 2026 ???? 7:26??.?., ?/? Lumin Etherlight via SlackBuilds-users ??????: > Yiannis writes: > > > Just to be clear, this is not the same as > > installing the testing glibc. Nothing on the > > system changes. System glibc stays 2.33. No > > upgradepkg of a core package, no ld.so.conf, no > > ldconfig. > > > > What the script does: > > > > - unpacks the snap into /opt/Signal/signal-desktop > > - unpacks aaa_glibc-solibs-2.42 into the same > > prefix, as a build source like any tarball > > - patchelf on the Electron binary so its PT_INTERP > > and DT_RPATH point there > > I don't see how this differs in a meaningful > way from the existing solution that was refused by > the SBo admins. The only minor difference is that > you're extracting Signal from a snap instead of a > .deb archive. The testing glibc is installed into > /opt, and Signal binaries are patched to point to > that glibc instead of the system one. If there's > some other important difference here, please do > explain it a bit more. > > Best Regards, > Lumin Etherlight > _______________________________________________ > 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 Aug 13 18:05:25 2026 From: rizitis at gmail.com (Yiannis) Date: Thu, 13 Aug 2026 21:05:25 +0300 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> <20260813092950.30a8f4c2@office64.slackie.org> <20260813111255.07bda649@office64.slackie.org> Message-ID: Ah there is an email I sent before 2-3 hours that everything was explained also new slackbuild.tar.gz was attached that by mistake was sent directly to *Christoph Willing but ont in the list!* *Please * *Christoph Willing can you cc it to list?* *thank you!* ???? ??? 13 ??? 2026 ???? 8:36??.?., ?/? Yiannis ??????: > You're right that the technique is the same -- bundled glibc, patched > interpreter and rpath. > I took $ORIGIN and the patch-everything loop from your script. > The difference isn't technical, it's what each one asks the repo for. > > Yours needs a second thing to exist: either a glibc-opt-bin SlackBuild in > the repo, or the user runs your apply script by hand. > That's what Willy refused -- not the patching, but adding a shared glibc > to SBo that other scripts could then depend on. > He called it all or nothing, and he was right about that: > once glibc-opt-bin exists in the repo, it's a package the admins have to > maintain, and your own message anticipated other packages following the > same pattern. > > Now doesn't create anything shared. The .txz is a build-time source, > extracted into the package payload the same way any tarball is. > What gets installed is a set of .so files under > /opt/Signal/signal-desktop/lib64/, reachable only through one binary's > PT_INTERP and DT_RPATH. > No second package, no REQUIRES, nothing on the system another script could > ever link against. > It's vendored libraries in one package, which SBo already accepts > elsewhere. > > Concretely, from a user's point of view: > > - installpkg and it works; no apply step > - removepkg takes all of it, including the glibc; no revert step, no > /opt/glibc left behind > - survives upgradepkg, because the patching is in the SlackBuild rather > than something to re-run afterwards > - the source has an md5sum in the .info, instead of required a glibc > package > - system glibc stays 2.33 and no other package sees 2.42 > > So the question for the admins stops being "can SBo ship a glibc" and > becomes "can one package carry private libraries under /opt", which is a > much smaller question. > > Its like you run an independent signal-desktop.AppImage with the required > glibc included :) > > ???? ??? 13 ??? 2026 ???? 7:26??.?., ?/? Lumin Etherlight via > SlackBuilds-users ??????: > >> Yiannis writes: >> >> > Just to be clear, this is not the same as >> > installing the testing glibc. Nothing on the >> > system changes. System glibc stays 2.33. No >> > upgradepkg of a core package, no ld.so.conf, no >> > ldconfig. >> > >> > What the script does: >> > >> > - unpacks the snap into /opt/Signal/signal-desktop >> > - unpacks aaa_glibc-solibs-2.42 into the same >> > prefix, as a build source like any tarball >> > - patchelf on the Electron binary so its PT_INTERP >> > and DT_RPATH point there >> >> I don't see how this differs in a meaningful >> way from the existing solution that was refused by >> the SBo admins. The only minor difference is that >> you're extracting Signal from a snap instead of a >> .deb archive. The testing glibc is installed into >> /opt, and Signal binaries are patched to point to >> that glibc instead of the system one. If there's >> some other important difference here, please do >> explain it a bit more. >> >> Best Regards, >> Lumin Etherlight >> _______________________________________________ >> 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 chris.willing at linux.com Thu Aug 13 21:57:08 2026 From: chris.willing at linux.com (Christoph Willing) Date: Fri, 14 Aug 2026 07:57:08 +1000 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> <20260813092950.30a8f4c2@office64.slackie.org> <20260813111255.07bda649@office64.slackie.org> <5732a108-3c03-48f8-b47b-ac1c005783ba@linux.com> Message-ID: I see from Yiannis' earlier email to me directly that he fully credits Lumin for the main idea. One more possibility would be to use the built source code rather than an appImage. In this case it is almost the same as Lumin's original proposal but with the advantage of keeping the updated glibc relatively private. chris On 14/8/26 01:31, Yiannis wrote: > Thanks! but the main idea was Lumin`s script :) > > So looking better Lumin`s [1] script caught something I had missed -- I was only patching the signal-desktop binary. > Lumin patch every executable in the directory, and that turned out to matter: > chrome_crashpad_handler is exec'd separately, so it kept its own PT_INTERP and would have started against the system 2.33 > while inspecting a 2.42 process. Only shows up when something else has already gone wrong, so I would never have caught it in testing. > > Also took $ORIGIN in the rpath from him -- more robust than the absolute path I had. > > for b in signal-desktop chrome_crashpad_handler; do > ? printf '== %s\n' "$b" > ? readelf -d /opt/Signal/signal-desktop/opt/Signal/$b | grep -E 'RPATH|RUNPATH' > done > == signal-desktop > ?0x000000000000000f (RPATH) ? ? ? ? ? ? ?Library rpath: [$ORIGIN:/opt/Signal/signal-desktop/lib64/incoming] > == chrome_crashpad_handler > ?0x000000000000000f (RPATH) ? ? ? ? ? ? ?Library rpath: [$ORIGIN:/opt/Signal/signal-desktop/lib64/incoming] > > Both binaries now resolve to the bundled loader, RPATH not RUNPATH, single libc across all processes per /proc/PID/maps. > > PS. in tar.gz included a python3 script I use to find snap package`s url for download. (python3 snap-info.py ) > [1]:https://lumin.etherlight.link/s/2C2606/saNeW/slackware-signal-glibc-workaround.sh > > > ???? ??? 13 ??? 2026 ???? 4:30??.?., ?/? Christoph Willing > ??????: > > I've never use signal before so can't check history but QR link & > sync seem to work OK here. > > I'm not sure if it meets all other admins requirements but if put > to a vote my vote would be "aye" if only because it's such a cute > solution. > > chris > > > On 13/8/26 21:06, Yiannis wrote: >> Just to be clear, this is not the same as installing the testing >> glibc. >> >> Nothing on the system changes. System glibc stays 2.33. No >> upgradepkg of a core package, no ld.so.conf, no ldconfig. >> >> What the script does: >> >> - unpacks the snap into /opt/Signal/signal-desktop >> - unpacks aaa_glibc-solibs-2.42 into the same prefix, as a build >> source like any tarball >> - patchelf on the Electron binary so its PT_INTERP and DT_RPATH >> point there >> >> So those .so files are reachable by exactly one binary. Nothing >> else on the machine can see them, and removepkg takes them all >> with it. >> >> Checked: /proc/PID/maps across all 7 Signal processes shows only >> the bundled libc, never the host 2.33. QR link, full history >> sync, send and receive all work. sbopkglint passes. >> >> Attached if anyone wants to look. >> >> IF admins and the maintainer agree with that then a desktop entry >> and an icon needed, now run only from the terminal. >> >> Thank you. >> >> ???? ??? 13 ??? 2026 ???? 12:05??.?., ?/? Yiannis >> ??????: >> >> Please give me some time, I have an idea and it looks that >> works! >> When I finish and be sure I will upload it here and IF >> maintainer and SBo admins agree you can adopt it. >> >> >> ???? ??? 13 ??? 2026 ???? 7:13??.?., ?/? Willy Sudiarto >> Raharjo ??????: >> >> > ? ? ? Signal blocks old versions of their software >> >? from connecting? to the network.? I? had to figure >> >? out? the binary? patching thing? because the? last >> >? 15.0? glibc-compatible version? I had? was finally >> >? blocked from connecting to the Signal network. >> > >> >? ? ? ? If patching the rpath to use an isolated new >> >? glibc-opt without migrating the whole OS is not an >> >? acceptable solution for? the SlackBuilds.org repo, >> >? then removing the Signal? SlackBuild is the option >> >? that makes sense, in my opinion.? People who still >> >? want to use Signal will? have to install it from a >> >? different 3rd party.? If that happens, I might end >> >? up packaging the patched? version myself, and then >> >? redistribute it on my site for others to use. >> >> >> What about the AppImage format? >> will that work? >> i assume it's all contained in a single package, so no >> link to >> system-based GLIBC >> >> >> -- >> Willy Sudiarto Raharjo >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - >> https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ -https://slackbuilds.org/faq/ >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Aug 14 01:14:30 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 14 Aug 2026 08:14:30 +0700 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> <7a7592f9-5bf8-4287-ad88-9ac4d64bcc0d@linux.com> <20260813092950.30a8f4c2@office64.slackie.org> <20260813111255.07bda649@office64.slackie.org> Message-ID: <20260814081430.3ea20eb9@office64.slackie.org> >You're right that the technique is the same -- bundled glibc, patched >interpreter and rpath. >I took $ORIGIN and the patch-everything loop from your script. >The difference isn't technical, it's what each one asks the repo for. > >Yours needs a second thing to exist: either a glibc-opt-bin SlackBuild >in the repo, or the user runs your apply script by hand. >That's what Willy refused -- not the patching, but adding a shared >glibc to SBo that other scripts could then depend on. > He called it all or nothing, and he was right about that: >once glibc-opt-bin exists in the repo, it's a package the admins have >to maintain, and your own message anticipated other packages following >the same pattern. > >Now doesn't create anything shared. The .txz is a build-time source, >extracted into the package payload the same way any tarball is. >What gets installed is a set of .so files under >/opt/Signal/signal-desktop/lib64/, reachable only through one binary's >PT_INTERP and DT_RPATH. >No second package, no REQUIRES, nothing on the system another script >could ever link against. > It's vendored libraries in one package, which SBo already accepts >elsewhere. > >Concretely, from a user's point of view: > >- installpkg and it works; no apply step >- removepkg takes all of it, including the glibc; no revert step, no >/opt/glibc left behind >- survives upgradepkg, because the patching is in the SlackBuild rather >than something to re-run afterwards >- the source has an md5sum in the .info, instead of required a glibc >package >- system glibc stays 2.33 and no other package sees 2.42 > >So the question for the admins stops being "can SBo ship a glibc" and >becomes "can one package carry private libraries under /opt", which is >a much smaller question. > >Its like you run an independent signal-desktop.AppImage with the >required glibc included :) From my *personal perspective*, this approach is fine since it's contained *only* for this spesific package, so we can keep using the original GLIBC from Slackware 15.0. It's like how alienBOB provide some of his package where all modules/dependencies are linked statically into his single package without linking to outside libraries. the disadvantages of this approach is that the output package will be slightly bigger in size -- 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 phalange at komputermatrix.com Fri Aug 14 21:11:18 2026 From: phalange at komputermatrix.com (phalange at komputermatrix.com) Date: Fri, 14 Aug 2026 17:11:18 -0400 Subject: [Slackbuilds-users] I will no longer maintain SlackBuilds from Aug 15 onwards In-Reply-To: References: <1YJ3SC0PayeJy1wzNgiqY32N2M0anMDUR8t1twRshWHhhszkFvXB6gLmH89AzzPp8xOG7Ia9zkRVcgREMAbZVLfIyroz5uMu5HJcNB1II3Y=@protonmail.com> Message-ID: <6f5d152380ec29c89131106ca2339a03@komputermatrix.com> I'll take this > development/rstudio-desktop On 2026-08-12 14:34, Jeremy Hansen wrote: > Isaac, > > Thanks for all your years of service to SBo and best of luck to your > future! > > I can take the following as dependencies for the packages I currently > maintain: > > network/tut > python/python3-defusedxml > python/python3-pynacl > > I've already pushed the maintainer changes to my branch. > > If you do ever come back and want any of these back, I'm happy to give > them back to you. > > Again, best of luck! > Jeremy > > PS Here are the remaining SlackBuilds from Isaac that are up for > grabs: > > academic/mathjax2 > audio/Ymuse > audio/mpd > audio/pavucontrol-qt > desktop/Matcha-gtk-theme > desktop/SysTray-X > desktop/bemenu > desktop/bibata-cursor-theme > desktop/birdtray > desktop/cinnamon-desktop > desktop/dwmblocks > desktop/flat-remix > desktop/gsimplecal > desktop/libqt6xdg > desktop/libqtxdg > desktop/lightdm-slick-greeter > desktop/lxqt-menu-data > desktop/lxqt-panel > desktop/lxqt-runner > desktop/lxqt-themes > desktop/naps2 > desktop/qtile > desktop/qtile-extras > desktop/xsecurelock > desktop/yaru-icon-theme > development/extra-cmake-modules-opt > development/jupyter-ipykernel > development/jupyter-nbclient > development/jupyter-nbconvert > development/jupyter-nbformat > development/jupyter-notebook > development/jupyter-notebook_shim > development/jupyter-qtconsole > development/jupyter_client > development/jupyter_console > development/jupyter_core > development/jupyter_events > development/jupyter_packaging > development/jupyter_server > development/jupyter_server_terminals > development/jupyterlab > development/jupyterlab_pygments > development/jupyterlab_server > development/protoc-gen-go > development/protoc-gen-go-grpc > development/python3-spyder-kernels > development/rstudio-desktop > development/rstudio-desktop-legacy > development/spyder > graphics/ctpv > graphics/lximage-qt > graphics/screengrab > graphics/vimiv-qt > graphics/xviewer > libraries/grpc > libraries/kidletime6 > libraries/kwindowsystem6 > libraries/layer-shell-qt6 > libraries/libdbusmenu-lxqt > libraries/libfm-qt > libraries/libfm-qt6 > libraries/libkscreen6 > libraries/liblxqt > libraries/libminizip > libraries/libsysstat > libraries/lxqt-build-tools > libraries/lxqt-build-tools-qt6 > libraries/lxqt-notificationd > libraries/lxqt-qt6plugin > libraries/lxqt-qtplugin > libraries/lxqt-sudo > libraries/plasma-wayland-protocols-opt > libraries/polkit-qt6-1 > libraries/python3-PyQtWebEngine > libraries/qt5gtk2 > libraries/qt6gtk2 > libraries/re2 > libraries/solid6 > network/proton-vpn-cli > network/proton-vpn-local-agent > network/warpinator > network/wego > office/hunspell-en > office/xed > office/xreader > python/python2-asn1crypto > python/python2-atomicwrites > python/python2-pluggy > python/python2-py > python/python3-argon2-cffi > python/python3-argon2-cffi-bindings > python/python3-arrow > python/python3-async-lru > python/python3-comm > python/python3-construct > python/python3-cookiecutter > python/python3-dbus-fast > python/python3-dbus-next > python/python3-debugpy > python/python3-diff-match-patch > python/python3-docstring-to-markdown > python/python3-entrypoints > python/python3-et_xmlfile > python/python3-exiv2 > python/python3-fastjsonschema > python/python3-fqdn > python/python3-gensim > python/python3-gnupg > python/python3-grpcio > python/python3-hatch-nodejs-version > python/python3-hatch_jupyter_builder > python/python3-inflection > python/python3-intervaltree > python/python3-ipython-pygments-lexers > python/python3-ipython-sql > python/python3-ipython_genutils > python/python3-isoduration > python/python3-jinja2-time > python/python3-json-logger > python/python3-jsonpatch > python/python3-jsonpointer > python/python3-lsp-black > python/python3-lsp-jsonrpc > python/python3-lsp-server > python/python3-mistune > python/python3-narwhals > python/python3-nest_asyncio > python/python3-numpydoc > python/python3-openpyxl > python/python3-overrides > python/python3-pandocfilters > python/python3-patsy > python/python3-plotly > python/python3-prometheus_client > python/python3-proton-core > python/python3-proton-keyring-linux > python/python3-proton-vpn-api-core > python/python3-pulsectl-asyncio > python/python3-pydocstyle > python/python3-pyinotify > python/python3-pykeepass > python/python3-pylint-venv > python/python3-pyls-spyder > python/python3-pyrsistent > python/python3-pytoolconfig > python/python3-pyudev > python/python3-qstylizer > python/python3-qtawesome > python/python3-regex > python/python3-requests-unixsocket > python/python3-rfc3339_validator > python/python3-rfc3986_validator > python/python3-rope > python/python3-rtree > python/python3-seaborn > python/python3-secretstorage > python/python3-sentry_sdk > python/python3-setproctitle > python/python3-shtab > python/python3-smart_open > python/python3-sortedcontainers > python/python3-statsmodels > python/python3-tabulate > python/python3-tenacity > python/python3-terminado > python/python3-testpath > python/python3-textdistance > python/python3-three-merge > python/python3-tinycss2 > python/python3-uri_template > python/python3-watchdog > python/python3-webcolors > python/python3-whatthepatch > python/python3-wurlitzer > python/python3-xcffib > python/python3-zeroconf > system/FontAwesome > system/OpenSnitch > system/file-roller > system/fscrypt > system/grub2-theme-mint > system/libtrash > system/lightdm > system/lightdm-settings > system/lxqt-about > system/lxqt-admin > system/lxqt-archiver > system/lxqt-config > system/lxqt-globalkeys > system/lxqt-openssh-askpass > system/lxqt-policykit > system/lxqt-powermanagement > system/lxqt-session > system/nemo > system/nemo-fileroller > system/pass-import > system/pcmanfm-qt > system/powerline-fonts > system/qps > system/qtxdg-tools > system/tbsm > system/trash-cli > system/ttf-ubuntu-font-family > > On Sun, Aug 9, 2026 at 11:15?PM Isaac Yu via SlackBuilds-users > wrote: > >> Hi everyone, >> >> This is the last weekly cycle in which I will maintain/update >> SlackBuilds. >> I will no longer do so from Aug 15 onwards. >> >> I previously said that I would no longer maintain SlackBuilds last >> Christmas, but I kept continuing to do so. >> Sorry about that - the main reason was that getting LXQt to v2 was >> less stressful than I initially thought (which prompted me to make >> that claim last Christmas). >> >> I mean it this time. >> Software (and by extension SlackBuilds) are getting more and more >> complicated to maintain. >> >> My main motivation recently has been to prepare for a new release of >> Slackware (ex. 15.1, 16.0, etc.) >> I'm actually using Linux Mint Debian right now as my main day-to-day >> operating system. >> I've been testing updates through Slackware virtual machines. >> >> I might return when the first alpha of the next Slackware version >> gets released (ex. 15.1-alpha1.) >> >> To the SlackBuilds.org team: >> My suggestion is to orphan my SlackBuilds only when the next version >> of Slackware is about to get released. >> I might make a hotfix SlackBuild update even during the Slackware >> 15.0 cycle (ex. protobuf gets updated, making python3-grpcio unable >> to build.) >> However, you may orphan them next week if you like. >> >> - Isaac >> >> _______________________________________________ >> 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 duncan_roe at optusnet.com.au Sat Aug 15 02:53:24 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sat, 15 Aug 2026 12:53:24 +1000 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> Message-ID: Hi B. Watson, On Tue, Aug 11, 2026 at 07:49:07AM -0400, B. Watson wrote: > > Looks we have 93 builds that need attention. Sigh. Could I please have a stab at fixing these? I plan to submit a SlackBuild for the Q editor once upstream gets the next release out (long overdue). Q advertises itself to be good at bulk edits so these 93 would be an interesting test. Reply off-list to duncan_roe at optusnet.com.au if you like, Cheers ... Duncan. From urchlay at slackware.uk Sat Aug 15 03:10:18 2026 From: urchlay at slackware.uk (B. Watson) Date: Fri, 14 Aug 2026 23:10:18 -0400 (EDT) Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> Message-ID: On Sat, 15 Aug 2026, Duncan Roe via SlackBuilds-users wrote: > Hi B. Watson, > > On Tue, Aug 11, 2026 at 07:49:07AM -0400, B. Watson wrote: >> >> Looks we have 93 builds that need attention. Sigh. > > Could I please have a stab at fixing these? Uh, I wish you'd asked me that 24 hours ago... I've already fixed 'em. > I plan to submit a SlackBuild for the Q editor once upstream gets the next > release out (long overdue). Q advertises itself to be good at bulk edits so > these 93 would be an interesting test. Hm. Well I can think of other 'bulk edit' stuff you could use it for. If you have a full SBo tree (git or rsync), try "sbolint -a". You'll get tons of "NOTE: blah.SlackBuild:XX: LIBDIRSUFFIX gets set, but never used" warnings in the log... you could try using Q to delete the assignments to LIBDIRSUFFIX in those builds. From willysr at slackbuilds.org Sat Aug 15 09:17:59 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Aug 2026 16:17:59 +0700 Subject: [Slackbuilds-users] Updates - 20260815.1 Message-ID: <20260815161759.15955d67@home.slackie.org> We added glibc-detection into sbo-maintainer-tools and our CI for this week's update, so we will see more warnings if there's a submission that requires newer glibc than what we have in Slackware 15.0. Credit goes to Andrew and Urchlay for this feature If you wish to see the complete changelog for this tool, please visit https://slackware.uk/~urchlay/repos/sbo-maintainer-tools/plain/NEWS Sat Aug 15 09:03:02 UTC 2026 academic/ngspice-jit: Updated for version 46.9. academic/ngspice-wave: Added (analog waveform viewer). academic/verilator: Updated for version 5.050 + new maintainer academic/verilog: Updated for version 13.0 + new maintainer audio/acxi: Updated for version 3.6.03. audio/caps: Fix homepage/download for real. audio/dopamine-bin: Updated for version 3.0.8 audio/libation-bin: Updated for version 13.7.5 audio/mac: Updated for version 13.25. audio/ocenaudio-bin: Updated for version 3.20.2 audio/openvino-plugins-ai-audacity: Removed (Sources are missing). desktop/XDecorations: Updated to version 0.1.10 + new maintainer desktop/alacarte: Updated for version 3.44.3 + new maintainer desktop/catclock: Script updates desktop/claude-desktop: Updated for version 1.25927.0 desktop/cwm: update SlackBuild desktop/fvwm3: fvwm3-menu-desktop fixes. desktop/xfce4-timer-plugin: Updated for version 1.8.0. development/Kiro: Updated for version 1.0.293. development/SQLAlchemy: Updated for version 2.0.52. development/SystemC: Updated for version 3.0.2 + new maintainer development/a68g: Updated for version 3.13.2 development/antigravity-cli: Updated for version 1.1.13 development/antigravity-ide: Updated for version 2.5.5 development/antigravity2: Removed (use antigravity) development/antigravity: Updated for version 2.6.0 development/aspnetcore-runtime-10.0: Updated for version 10.0.11. development/aspnetcore-runtime-8.0: Updated for version 8.0.30. development/aspnetcore-runtime-9.0: Updated for version 9.0.19. development/avrdude: Updated for version 8.2. development/aws-cdk: Updated for version 2.1135.1. development/cargo-c: Don't use BUILD. development/deno: Updated for version 2.9.5. development/difftastic: Updated for version 0.70.0 development/dotnet-runtime-10.0: Updated for version 10.0.11. development/dotnet-runtime-8.0: Updated for version 8.0.30. development/dotnet-runtime-9.0: Updated for version 9.0.19. development/dotnet-sdk-10.0: Updated for version 10.0.400. development/dotnet-sdk-8.0: Updated for version 8.0.424. development/dotnet-sdk-9.0: Updated for version 9.0.317. development/dub: Updated for version 1.42.0 development/ecl: Updated for version 26.5.5 development/electron-bin: Updated for version 43.4.0 development/fortitude-bin: Updated for version 0.9.2 development/gitify-bin: Updated for version 7.3.1 development/gitlab-cli: Updated for version 1.113.0. development/gnustep-base: Fix build for -current. development/got: update SlackBuild development/gtkdialog: Updated for version 0.8.5e + new maintainer development/haxe-bin: Updated for version 4.3.6. development/hexnet: Use flags, strip binary. development/inform: Updated for version 6.44_r7. development/jupyter-nbformat: Update README development/letos: Updated for version 4.0.3 development/lua-language-server: Updated for version 3.19.0. development/mold: Updated for version 2.42.0. development/muon: Orphaned (unmaintained). development/mysql-workbench: Update components. development/nim: Updated for version 2.2.10. development/pnpm: Updated for version 11.21.0. development/positron: Updated for version 2026.08.0_331. development/prek: Updated for version 0.4.13. development/regina-rexx: Fix comment. development/smartgit: Updated for version 26.1.052 development/sqlitebrowser: Fix variable. development/squeak-vm: Updated for version 4.21.3.3840. development/tup: Orphaned (unmaintained). development/txr: New maintainer. development/vscode-bin: Updated for version 1.132.1. development/vscode-bin: Updated for version 1.33.0. development/vstudio: downgraded upstream to version 17.5.1 development/xmake: Updated for version 3.1.0. games/PrismLauncher-Unlocked: Compress man pages. games/gnugo: new maintainer games/nestopia: Add fltk to REQUIRES, fix README. games/nsudoku: Script updates + new maintainer. games/openyahtzee: Fix requires. games/stratagus: Orphaned (unmaintained). games/wargus: Orphaned (unmaintained). git/ci: Update CI dependencies. graphics/FreeCAD: Fixed URL graphics/dia: Make lint-clean, fix .desktop. graphics/fbgrab: Updated for version 1.5 + new maintainer. graphics/jp2-pixbuf-loader: Fix homepage. graphics/openscad: new maintainer graphics/renderdoc: Updated for version 1.12 graphics/teighafileconverter: Orphaned (unmaintained). graphics/ueberzugpp: Update script. ham/CubicSDR: Update script. ham/SDRPlay: Update script. ham/gridtracker2: Updated for version 2.260808.2. libraries/CGAL: new maintainer libraries/CLI11: Updated for version 2.7.2. libraries/MuseScore-Libraries: Updated for version 6.10.2 libraries/OpenCSG: new maintainer libraries/aqbanking: Updated for version 6.9.2. libraries/avr-libc: Correct github canonical name libraries/avr-libc: Updated for version 2.3.2. libraries/ell: Updated for version 0.83. libraries/fcgi: New maintainer. libraries/libgit2: Updated for version 1.9.7 libraries/libmpdclient: Updated for version 2.27 libraries/libtomcrypt: Fix .pc, use flags. libraries/lttng-ust: Updated for version 2.15.1 libraries/python2-PyYAML: Updated for version 5.3. libraries/qt6: Updated for version 6.8.4. libraries/vst3sdk: Updated for version 3.8.1 misc/SecLists: Updated for version 2026.1. misc/axpbox: Removed unused file misc/bdf2psf: Updated for version 1.249. misc/es40: Updated for version 0.80 misc/exploitdb: Updated for version 2026_08_12. misc/gxmessage: Updated to version 3.4.3 + new maintainer misc/jmri: Updated for version 5.16. misc/nuclei: Updated for version 3.11.1. misc/ollama: Updated for version 0.32.11. misc/par2cmdline-turbo: Updated for version 1.4.0. misc/xhidecursor: update SlackBuild multimedia/MuseScore: Updated for version 4.7.3 multimedia/opera-ffmpeg-codecs: Updated for version 0.102.1 multimedia/plexmediaserver: Fix script. multimedia/plexmediaserver: Updated for version 1.43.3.10861_07dfddaeb. multimedia/sfnt2woff: Add LICENSE and README to pkg; use flags. multimedia/sickchill: Fix tvdb and cinemagoer issues + updated rc.sickchill multimedia/strawberry: Updated for version 1.2.27. multimedia/ucview: Fix .desktop and doc dir. network/amavisd-new: Updated dependencies. network/amneziawg-go: Updated for version 3.1.20260814. network/amneziawg-kernel: Updated for version 3.1.20260812. network/amneziawg-tools: Updated for version 3.1.20260812. network/arno-iptables-firewall: Make lint-clean. network/brave-browser: Updated for version 1.93.136 network/brave-origin: Updated for version 1.93.136 network/cisco-secure-client-vpn: Updated for version 5.1.19.1862. network/clamav-unofficial-sigs: Updated for version 8.0.0. network/discord: Version bump to 1.0.151 network/dnsproxy-bin: Updated for version 0.84.0. network/dropbox: Updated for version 264.4.3421. network/firewalld: Updated for version 2.5.1. network/franz: Updated for version 6.6.0. network/helium-browser: Updated for version 0.15.3.1 network/ldapvi: Updated for version 1.8 network/librewolf: Updated for version 153.0.3_1 network/metasploit-framework-bin: Updated for version 6.5.2. network/microsoft-edge: Updated for version 151.0.4129.86. network/mptcpd: Updated for version 0.14. network/nextcloud-server: Updated dep and README. network/opera: Reverted to version 133.0.5932.85 network/pilot-link: Added (PalmOS toolkit and library). network/proton-vpn-cli: Removed (unable to login, unable to use) network/roundcubemail: Update dep. network/roundcubemail: Updated for version 1.6.18. network/rspamd: Updated for version 4.1.4 network/spamassassin: Updated dependencies and improved documentation. network/sshamble: Updated for version 0.3.10. network/syncthingtray-bin: Updated for version 2.1.4. network/tut: New maintainer network/vivaldi: Updated for version 8.1.4087.66. network/wireshark: Updated for version 4.6.8. network/yt-dlp-bin: Updated for version 2026.08.04.234419. network/zen-browser: Updated for version 1.21.13b office/MasterPDFEditor: Updated for version 5.9.99. office/OpenAudible-bin: Updated for version 4.8.7 office/cups-pdf: Use flags. office/jpilot: Updated for version 2_1_0. office/keepnote: Updated for version 0.7.8 office/ledger-live: Updated for version 4.15.0 office/pandoc-bin: update to 3.10.2 office/pdfsam-basic: New maintainer. office/pdfsam-basic: Updated for version 6.0.5. office/qownnotes: Updated for version 26.8.3. office/qpdfview: Fix variable. perl/perl-Class-Std: Added (Perl Module). perl/perl-Sys-Mmap: Updated for version 0.21. python/internetarchive: Add missing python3-jsonpatch dep. python/python3-aiohttp-socks: Updated for version 0.12.0. python/python3-bitarray: Updated for version 3.10.1. python/python3-construct: New Maintainer. python/python3-defusedxml: New maintainer python/python3-dunamai: Use consistent URL. python/python3-hatchling: Updated for version 1.32.0. python/python3-hatchling: Updated for version 1.32.0. python/python3-odfdo: Updated for version 3.22.2 python/python3-packaging-opt: Updated for version 26.3. python/python3-proton-core: Update for 0.7.4 python/python3-pykeepass: Update for 4.2.0 python/python3-pynacl: New maintainer python/python3-pypdf: Updated for version 6.16.0 python/python3-pypng: Updated for version 0.20250521.0. python/python3-secretstorage: Fix README python/python3-sentry_sdk: Updated for version 2.67.1 python/python3-setuptools-gettext: Added (Plugin for gettext). python/python3-shtab: Updated for version 1.10.0 python/python3-socks: Updated for version 3.0.0. python/python3-typogrify: Use correct pypi URL, simplify script. python/secretstorage: Removed (renamed to python3-secretstorage) python/subliminal: Version bump to 2.7.1 + add missing defusedxml dep python/uv-bin: Updated for version 0.12.3. ruby/ncurses-ruby: Fix doc perms, apply flags. ruby/passenger: Fix doc perms, apply flags. ruby/rubygem-activesupport: Fix doc permissions. ruby/rubygem-atk: Fix doc perms. ruby/rubygem-cairo-gobject: Fix doc perms, apply flags. ruby/rubygem-cairo: Fix doc perms, apply flags. ruby/rubygem-concurrent-ruby: Fix doc permissions. ruby/rubygem-daemons: Fix doc permissions. ruby/rubygem-diff-lcs: Fix doc permissions. ruby/rubygem-file-tail: Fix doc permissions. ruby/rubygem-gdk3: Fix doc perms. ruby/rubygem-gdk_pixbuf2: Fix doc perms, apply flags. ruby/rubygem-gio2: Fix doc perms, apply flags. ruby/rubygem-glib2: Fix doc perms, apply flags. ruby/rubygem-gobject-introspection: Fix doc perms, apply flags. ruby/rubygem-gtk2: Fix doc perms, apply flags. ruby/rubygem-gtk3: Fix doc perms, apply flags. ruby/rubygem-hpricot: Fix doc perms, apply flags. ruby/rubygem-httparty: Fix doc permissions. ruby/rubygem-i18n: Fix doc permissions. ruby/rubygem-lolcat: Fix doc permissions. ruby/rubygem-mail: Fix doc permissions. ruby/rubygem-manpages: Fix doc permissions. ruby/rubygem-matrix: Fix doc permissions. ruby/rubygem-mime-types-data: Fix doc permissions. ruby/rubygem-mime-types: Fix doc permissions. ruby/rubygem-mini_mime: Fix doc permissions. ruby/rubygem-multi_json: Fix doc permissions. ruby/rubygem-multi_xml: Fix doc permissions. ruby/rubygem-mustache: Fix doc permissions. ruby/rubygem-net-scp: Fix doc permissions. ruby/rubygem-net-sftp: Fix doc permissions. ruby/rubygem-net-ssh: Fix doc permissions. ruby/rubygem-optimist: Fix doc permissions. ruby/rubygem-paint: Fix doc permissions. ruby/rubygem-pango: Fix doc perms, apply flags. ruby/rubygem-pkg-config: Fix doc permissions. ruby/rubygem-pygments: Fix doc permissions. ruby/rubygem-rack: Fix doc permissions. ruby/rubygem-rdiscount: Fix doc perms, apply flags. ruby/rubygem-red-colors: Fix doc permissions. ruby/rubygem-ronn: Fix doc permissions. ruby/rubygem-rspec-core: Fix doc permissions. ruby/rubygem-rspec-expectations: Fix doc permissions. ruby/rubygem-rspec-mocks: Fix doc permissions. ruby/rubygem-rspec-support: Fix doc permissions. ruby/rubygem-rspec: Fix doc permissions. ruby/rubygem-ruby2ruby: Fix doc permissions. ruby/rubygem-ruby_parser: Fix doc permissions. ruby/rubygem-sexp_processor: Fix doc permissions. ruby/rubygem-sourcify: Fix doc permissions. ruby/rubygem-sync: Fix doc permissions. ruby/rubygem-term-ansicolor: Fix doc permissions. ruby/rubygem-tins: Fix doc permissions. ruby/rubygem-trogdoro-el4r: Fix doc permissions. ruby/rubygem-trollop: Fix doc permissions. ruby/rubygem-xiki: Fix doc permissions. ruby/sequel4: Fix doc permissions. system/FreeFileSync: Updated for version 14.11 system/bottom: Updated for version 0.14.8. system/clamav: Updated for version 1.5.4. system/cmdline-tools-bin: Added (Android SDK Command line tools). system/containerd: Updated for veresion 1.7.34. system/doas: update SlackBuild system/docker-buildx: Fix moby download URL. system/docker-cli: Updated for version 28.7.2. system/docker: Updated for version 28.7.2. system/doublecmd-qt5: Updated for version 1.2.8 system/fdclone: Fix homepage/download. system/fish: Updated URLs & maintainer email system/lightdm: Updated for version 1.33.0 system/nanum-coding-fonts-ttf: Updated for version 2.5 system/nanum-fonts-ttf: Updated to version 20250212 + new maintainer system/netdata: Updated for version 2.11.0. system/nvidia-legacy390-driver: Update script. system/open-vm-tools: Updated for version 13.1.0_25218885. system/physlock: Pass SLKCFLAGS correctly. system/pkg: Updated for version v0.11.0. system/postgresql15: Updated for version 15.19. system/postgresql16: Updated for version 16.15. system/postgresql17: Updated for version 17.11. system/postgresql18: Updated for version 18.6. system/postgresql: Updated for version 14.24. system/powershell: Updated for version 7.6.5. system/qdirstat: Fix README. system/sbo-maintainer-tools: Updated for version 0.9.6.2. system/sbotest: Updated for version 1.3.1. system/sbotools: Updated for version 4.4.2. system/sbozyp: Updated for version 1.8.0 system/srm: Fix var names, doc dir. system/ttf-arphic-uming: New maintainer system/un-fonts-core: Updated for version 1.0.2.080608 system/uptimed: Fix .new config handling. system/uw-ttyp0: Added (Monospace bitmap fonts). system/wdiff: Updated for version 1.2.3. system/zopfli: Updated for version 1.0.3. +--------------------------+ -- 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 antonioleal at yahoo.com Sat Aug 15 12:51:11 2026 From: antonioleal at yahoo.com (Antonio Leal) Date: Sat, 15 Aug 2026 13:51:11 +0100 Subject: [Slackbuilds-users] =?utf-8?q?pilot-link_doppelg=C3=A4nger?= References: <32c8320c-69d1-4a37-b9b1-62588dcc3c6d.ref@yahoo.com> Message-ID: <32c8320c-69d1-4a37-b9b1-62588dcc3c6d@yahoo.com> pilot-link which is stock on slackware64/l has just been overrun by https://slackbuilds.org/repository/15.0/network/pilot-link/?search=pilot-link From willysr at slackbuilds.org Sat Aug 15 13:36:51 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Aug 2026 20:36:51 +0700 Subject: [Slackbuilds-users] =?utf-8?q?pilot-link_doppelg=C3=A4nger?= In-Reply-To: <32c8320c-69d1-4a37-b9b1-62588dcc3c6d@yahoo.com> References: <32c8320c-69d1-4a37-b9b1-62588dcc3c6d.ref@yahoo.com> <32c8320c-69d1-4a37-b9b1-62588dcc3c6d@yahoo.com> Message-ID: <4A35CDFE-904C-459B-B631-05E415BE8648@slackbuilds.org> >pilot-link which is stock on slackware64/l has just been overrun by https://slackbuilds.org/repository/15.0/ Oh right That should have not been added to SBo -- Willy Sudiarto Raharjo From lists at osh.id.au Sat Aug 15 14:53:41 2026 From: lists at osh.id.au (David O'Shaughnessy) Date: Sat, 15 Aug 2026 22:53:41 +0800 Subject: [Slackbuilds-users] Build Environment Reminder In-Reply-To: References: <20260810212256.7ec41764@home.slackie.org> Message-ID: <0f3b2169-c8e1-4e44-82b8-5019c6f70eb6@app.fastmail.com> Just in case it gets removed, I do keep signal-desktop mostly up to date in my (very) modest Slackware repo, basically made for my own convenience: https://slack.osh.id.au/ It does a binary repack of signal-desktop (checks the signatures first though, so it's not a blind download/repackage). -- Dave On Tue, 11 Aug 2026, at 5:38 AM, Greg Tourte wrote: > Willy, > > does that include package which explicitly state in the README that the package require the newer GLIBC? > > I maintain one such script (signal-desktop) and it would be a shame to see it removed from the repo. > > Cheers > > Greg > > On Mon, 10 Aug 2026 at 15:23, Willy Sudiarto Raharjo wrote: >> Hi all >> >> We noticed that some applications require newer version of libraries or modules >> that is already provided by Slackware core packages. This is normal as >> Slackware 15.0 is now 4 years old and upstream are bumping requirements as they >> develop new version with more features. Patrick has been kind enough to provide >> some new version of some packages into testing/ which helps people to keep >> updating to the latest version of the software they often use daily. >> >> We just to want to remind everyone that SBo is designed to be tested against >> latest Slackware Stable releases with latest patches. It doesn't include extra/ >> or testing/ which requires manual intervention and not part of the full >> installation. Our CI is NOT designed to test against custom installation, which >> includes packages from extra or testing. >> >> That said, moving forward, we will start scanning our repository for scripts >> that requires newer libraries/packages, such as GLIBC and start >> removing them. Urchlay will add GLIBC detection at sbo-maintainer-tools package >> soon, which will help CI to test against new PR that requires newer GLIBC. >> >> Maintainers, please ensure that your scripts are tested against clean >> environment of Slackware 15.0, not -current or custom installation. >> Our FAQ is also updated to clarify this issue >> https://slackbuilds.org/faq/#full >> >> >> -- >> Willy Sudiarto Raharjo >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ > _______________________________________________ > 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 fourtysixandtwo at sliderr.net Sat Aug 15 21:54:06 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sat, 15 Aug 2026 15:54:06 -0600 Subject: [Slackbuilds-users] uid/gid conflict for pcp Message-ID: Found a conflict with sickchill for uid/gid 377. Next available is 402. I've updated uid_gid.txt Anyone using pcp may want to make the change as well. https://git.slackbuilds.org/slackbuilds/diff/?h=user/46and2/updates&id2=bdd859cef4d6d63f4d1e00cd2b4139b94630283e Cheers -- _______________________________________________ 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 emmanueln at gmail.com Sun Aug 16 01:30:05 2026 From: emmanueln at gmail.com (Emmanuel) Date: Sat, 15 Aug 2026 22:30:05 -0300 Subject: [Slackbuilds-users] SlackBuilds in search of better maintainers In-Reply-To: <20241002004639.76f79bfb@kiwi.kuchen> References: <20241001115554.0652ad61@kiwi.kuchen> <20241002004639.76f79bfb@kiwi.kuchen> Message-ID: Hi Ruben, I noticed that you haven't been able to update vis since 2022. Is it still available for me to take over and maintain it? Best regards. On Tue, Oct 1, 2024 at 7:46?PM Ruben Schuller wrote: > 2024-10-01 "Nick Smallbone" : > > > I can take nim. > > Great :) > > Ruben > _______________________________________________ > 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/ > > -- ***************** Emmanuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Aug 16 01:47:36 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 16 Aug 2026 08:47:36 +0700 Subject: [Slackbuilds-users] uid/gid conflict for pcp In-Reply-To: References: Message-ID: <20260816084736.24b3ab66@home.slackie.org> >Found a conflict with sickchill for uid/gid 377. Next available is >402. I've updated uid_gid.txt > >Anyone using pcp may want to make the change as well. > >https://git.slackbuilds.org/slackbuilds/diff/?h=user/46and2/updates&id2=bdd859cef4d6d63f4d1e00cd2b4139b94630283e Thanks updated the hints as well for our CI -- 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 Aug 16 01:59:30 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 15 Aug 2026 21:59:30 -0400 (EDT) Subject: [Slackbuilds-users] Last call for gst0-ffmpeg and gst0-plugins-ugly Message-ID: <257b1aab-7fe0-f841-34bc-3eea6137e490@slackware.uk> Andrey Maraev, I have been trying to reach you via email for 3 weeks. Hopefully you'll see this and respond to it... Your build radiotray is the only thing in the repo that depends on gst0-ffmpeg and gst0-plugins-ugly, which have become unmaintained and really need someone to take them over. Since radiotray requires these builds, it makes sense for you to take them over. Please let me know if you're willing to do this. From duncan_roe at optusnet.com.au Sun Aug 16 02:14:33 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sun, 16 Aug 2026 12:14:33 +1000 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> Message-ID: On Fri, Aug 14, 2026 at 11:10:18PM -0400, B. Watson wrote: > > If you have a full SBo tree (git or rsync), try "sbolint -a". You'll > get tons of "NOTE: blah.SlackBuild:XX: LIBDIRSUFFIX gets set, but > never used" warnings in the log... you could try using Q to delete the > assignments to LIBDIRSUFFIX in those builds. I see almost as many warnings for SLKCFLAGS. Should I do them as well? In same commit? Cheers ... Duncan. From milgram at cgpp.com Sun Aug 16 02:26:24 2026 From: milgram at cgpp.com (J. Milgram) Date: Sat, 15 Aug 2026 22:26:24 -0400 Subject: [Slackbuilds-users] =?utf-8?q?pilot-link_doppelg=C3=A4nger?= In-Reply-To: <32c8320c-69d1-4a37-b9b1-62588dcc3c6d@yahoo.com> References: <32c8320c-69d1-4a37-b9b1-62588dcc3c6d.ref@yahoo.com> <32c8320c-69d1-4a37-b9b1-62588dcc3c6d@yahoo.com> Message-ID: eek! My bad. I just didn't notice it. The new jpilot won't build with the stock pilot-link. So I guess we remove both pilot-link and jpilot from SBo. Sorry about that. On 8/15/26 08:51, Antonio Leal via SlackBuilds-users wrote: > pilot-link which is stock on slackware64/l has just been overrun by > https://slackbuilds.org/repository/15.0/network/pilot-link/?search=pilot-link > > _______________________________________________ > 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/ > > -- ===== milgram at cgpp.com 301-257-7069 From fourtysixandtwo at sliderr.net Sun Aug 16 02:32:03 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sat, 15 Aug 2026 20:32:03 -0600 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> Message-ID: I only remove the ARCH if/elif section if sbolint complains about both not being used. Not sure it's worth worrying about otherwise. For example, this would be a good candidate: sun: NOTE: sun.SlackBuild:60: SLKCFLAGS gets set, but never used. sun: NOTE: sun.SlackBuild:61: LIBDIRSUFFIX gets set, but never used. On Sat, 15 Aug 2026 at 20:14, Duncan Roe via SlackBuilds-users wrote: > > On Fri, Aug 14, 2026 at 11:10:18PM -0400, B. Watson wrote: > > > > If you have a full SBo tree (git or rsync), try "sbolint -a". You'll > > get tons of "NOTE: blah.SlackBuild:XX: LIBDIRSUFFIX gets set, but > > never used" warnings in the log... you could try using Q to delete the > > assignments to LIBDIRSUFFIX in those builds. > > I see almost as many warnings for SLKCFLAGS. Should I do them as well? > In same commit? > > Cheers ... Duncan. > _______________________________________________ > 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 willysr at slackbuilds.org Sun Aug 16 02:44:49 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 16 Aug 2026 09:44:49 +0700 Subject: [Slackbuilds-users] =?utf-8?q?pilot-link_doppelg=C3=A4nger?= In-Reply-To: References: <32c8320c-69d1-4a37-b9b1-62588dcc3c6d.ref@yahoo.com> <32c8320c-69d1-4a37-b9b1-62588dcc3c6d@yahoo.com> Message-ID: <20260816094449.3d3050bf@home.slackie.org> >eek! My bad. I just didn't notice it. > >The new jpilot won't build with the stock pilot-link. So I guess we >remove both pilot-link and jpilot from SBo. can you modify pilot-link to install everything into /opt? that should work since jpilot is the only one that need this -- 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 Aug 16 02:40:32 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 15 Aug 2026 22:40:32 -0400 (EDT) Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> Message-ID: <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> On Sun, 16 Aug 2026, Duncan Roe wrote: > I see almost as many warnings for SLKCFLAGS. Should I do them as well? > In same commit? Yes, feel free. If you're getting rid of both SLKCFLAGS and LIBDIRSUFFIX in the same build, just delete the entire block that begins with: if [ "$ARCH" = "i586" ]; then ...up to & including the "fi" at the end. And hopefully the blank line after it, too. Also note that your commits have to be one per build, not one giant commit that alters multiple builds. I know it's annoying but that's how we keep track of things... From lumin+slackbuilds at etherlight.link Sun Aug 16 09:23:49 2026 From: lumin+slackbuilds at etherlight.link (Lumin Etherlight) Date: Sun, 16 Aug 2026 12:23:49 +0300 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> (B. Watson's message of "Sat, 15 Aug 2026 22:40:32 -0400 (EDT)") References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> Message-ID: "B. Watson" writes: > Also note that your commits have to be one per > build, not one giant commit that alters multiple > builds. I know it's annoying but that's how we > keep track of things... Just to note, this will mean /thousands/ of git commits just removing unused variables. Best Regards, Lumin Etherlight From urchlay at slackware.uk Sun Aug 16 09:31:36 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 16 Aug 2026 05:31:36 -0400 (EDT) Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> Message-ID: <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> On Sun, 16 Aug 2026, Lumin Etherlight via SlackBuilds-users wrote: > "B. Watson" writes: > >> Also note that your commits have to be one per >> build, not one giant commit that alters multiple >> builds. I know it's annoying but that's how we >> keep track of things... > > Just to note, this will mean /thousands/ of > git commits just removing unused variables. Yeah. It's actually why it hasn't already been done. The extra unused variables don't actually do any harm... The best time to do this would be during 'development cycle', when a new Slackware stable has just been released, and the repo is closed while we port all the builds over (fix compile errors, remove builds that were included in the new Slackware, etc). Unfortunately that means, no time soon. We all have our guesses of when we expect a new Slackware, but nobody knows... From willysr at slackbuilds.org Sun Aug 16 10:35:03 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 16 Aug 2026 17:35:03 +0700 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> Message-ID: <20260816173503.1c44855e@home.slackie.org> >The best time to do this would be during 'development cycle', >when a new Slackware stable has just been released, and the repo >is closed while we port all the builds over (fix compile errors, >remove builds that were included in the new Slackware, etc). Minor correction: development cycle starts when ALPHA/BETA label is announced by Patrick, not when a new version is released. It could be some time before a new version is released, but also gives us time to clear all scripts in SBo to be compatible with next Slackware version We want to achieve same day release for Slackware version and SBo repo -- 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 glenn_e_becker at protonmail.com Sun Aug 16 12:47:14 2026 From: glenn_e_becker at protonmail.com (glenn_e_becker) Date: Sun, 16 Aug 2026 12:47:14 +0000 Subject: [Slackbuilds-users] sbopkglint test failure (tasksh) Message-ID: Hi - I've been working on an update (really just maintainer identity for now) to the tasksh package, which offers an interface to task[warrior]. sbopkglint throws the following error on the built package: Running test: 05-basic-sanity... --- ERR: forbidden directory exists: usr/share/doc FAILED ... this is the only failure. I've been poking around in the tasksh source code and so far the only occurrence of the string "/usr/share/doc" I've found is in the file install_manifest.txt,which contains lines like /usr/share/doc/tasksh/NEWS Is there a way around or a way to fix this? I would like to be a better maintainer, and want to do things right. Thx, Glenn Becker ===================================== Rain comes down through the alders, Its low conducive voices Mutter about let-downs and erosions And yet each drop recalls The diamond absolutes. -- Seamus Heaney Sent with [Proton Mail](https://proton.me/mail/home) secure email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Aug 16 13:29:41 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 16 Aug 2026 20:29:41 +0700 Subject: [Slackbuilds-users] sbopkglint test failure (tasksh) In-Reply-To: References: Message-ID: <20260816202941.79c2fe39@home.slackie.org> >sbopkglint throws the following error on the built package: > >Running test: 05-basic-sanity... >--- ERR: forbidden directory exists: usr/share/doc >FAILED > >... this is the only failure. I've been poking around in the tasksh source >code and so far the only occurrence of the string "/usr/share/doc" I've found >is in the file install_manifest.txt,which contains lines like > >/usr/share/doc/tasksh/NEWS > >Is there a way around or a way to fix this? I would like to be a better >maintainer, and want to do things right. move it to /usr/doc/$PRGNAM-$VERSION and remove /usr/share/doc directory -- 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 nick at smallbone.se Sun Aug 16 14:00:34 2026 From: nick at smallbone.se (Nick Smallbone) Date: Sun, 16 Aug 2026 16:00:34 +0200 Subject: [Slackbuilds-users] sbopkglint test failure (tasksh) In-Reply-To: References: Message-ID: Hi Glenn, On Sun, 16 Aug 2026, at 2:47 PM, glenn_e_becker via SlackBuilds-users wrote: > *sbopkglint* throws the following error on the built package: > > Running test: 05-basic-sanity... > --- ERR: forbidden directory exists: usr/share/doc > FAILED To add to what Willy said, this is caused by this line in CMakeLists.txt: SET (TASKSH_DOCDIR share/doc/tasksh CACHE STRING "Installation directory for doc files") so in this case it can also be solved by adding -DTASKSH_DOCDIR=doc/$PRGNAM-$VERSION when you run cmake. Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at dorfdsl.de Sun Aug 16 14:43:26 2026 From: mm at dorfdsl.de (Marco Moock) Date: Sun, 16 Aug 2026 16:43:26 +0200 Subject: [Slackbuilds-users] Oracle Java Message-ID: Hello! SBo currently provides jdk11 jdk19 jdk23 I found that 19 and 23 are non-LTS and are already out of support. Java.com points users (not developers) to the JRE 8. Is that still supported and is it reasonable to provide a Slackbuild for it (it is the latest LTS that supports Java WebStart)? -- kind regards Marco Junk-Mail bitte an trashcan 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 glenn_e_becker at protonmail.com Sun Aug 16 15:02:33 2026 From: glenn_e_becker at protonmail.com (glenn_e_becker) Date: Sun, 16 Aug 2026 15:02:33 +0000 Subject: [Slackbuilds-users] sbopkglint test failure (tasksh) In-Reply-To: References: Message-ID: <_qbqTMJfkyYedWdQW7BXL0TXTxA-9yNzUoS3kwwzBMDcOhwKG1ombOHLf3Hu-JxqUmgUiJwxvxxoYCnft1JOydePVK4oNdPJ7hEsiQCjyJg=@protonmail.com> Thanks, now passing all sbopkglint tests. :^) ===================================== Rain comes down through the alders, Its low conducive voices Mutter about let-downs and erosions And yet each drop recalls The diamond absolutes. -- Seamus Heaney Sent with [Proton Mail](https://proton.me/mail/home) secure email. On Sunday, August 16th, 2026 at 10:01 AM, Nick Smallbone wrote: > Hi Glenn, > > On Sun, 16 Aug 2026, at 2:47 PM, glenn_e_becker via SlackBuilds-users wrote: > >> sbopkglint throws the following error on the built package: >> >> Running test: 05-basic-sanity... >> --- ERR: forbidden directory exists: usr/share/doc >> FAILED > > To add to what Willy said, this is caused by this line in CMakeLists.txt: > > SET (TASKSH_DOCDIR share/doc/tasksh CACHE STRING "Installation directory for doc files") > > so in this case it can also be solved by adding -DTASKSH_DOCDIR=doc/$PRGNAM-$VERSION when you run cmake. > > Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From emmanueln at gmail.com Sun Aug 16 21:29:33 2026 From: emmanueln at gmail.com (Emmanuel) Date: Sun, 16 Aug 2026 18:29:33 -0300 Subject: [Slackbuilds-users] Updates on OpenMPI Message-ID: Hi everyone, I maintain the openmpi package. It is currently at version 4, and I would like to update it to version 5. I have run into some issues with OpenMPI 5 when using the CESM software, but it works well with others like LAMMPS and GROMACS. Would it be possible to upload a new version and keep both versions available in the repository? What do you think is the best approach? - Should I update openmpi to version 5 and create a new package for openmpi4 ? - Or should I keep openmpi at version 4 and create a new package for openmpi5? Thanks and best regards -- ***************** Emmanuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From duncan_roe at optusnet.com.au Mon Aug 17 01:32:37 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Mon, 17 Aug 2026 11:32:37 +1000 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> Message-ID: On Sat, Aug 15, 2026 at 08:32:03PM -0600, fourtysixandtwo wrote: > I only remove the ARCH if/elif section if sbolint complains about both > not being used. Not sure it's worth worrying about otherwise. > You *have* to remove it - `if; then; elif` is a bash syntax error From willysr at slackbuilds.org Mon Aug 17 01:43:24 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 17 Aug 2026 08:43:24 +0700 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: References: Message-ID: <20260817084324.5e3d634c@office64.slackie.org> >SBo currently provides > >jdk11 >jdk19 >jdk23 > >I found that 19 and 23 are non-LTS and are already out of support. > >Java.com points users (not developers) to the JRE 8. > >Is that still supported and is it reasonable to provide a Slackbuild >for it (it is the latest LTS that supports Java WebStart)? I removed jdk11 on my branch already mysql-workbench is still using jdk19, but i will try to submit newer jdk and change it jdk19 and 23 still have active maintainer (Eben), so i will let him decide -- 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 fourtysixandtwo at sliderr.net Mon Aug 17 01:47:37 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sun, 16 Aug 2026 19:47:37 -0600 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <967a9c6c-ad1e-288b-dcaf-2a237e6fa9@slackware.uk> <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> Message-ID: Yes, I assumed that it was clear I meant the following given the sbolint example I used: -if [ "$ARCH" = "i586" ]; then - SLKCFLAGS="-O2 -march=i586 -mtune=i686" - LIBDIRSUFFIX="" -elif [ "$ARCH" = "i686" ]; then - SLKCFLAGS="-O2 -march=i686 -mtune=i686" - LIBDIRSUFFIX="" -elif [ "$ARCH" = "x86_64" ]; then - SLKCFLAGS="-O2 -fPIC" - LIBDIRSUFFIX="64" -elif [ "$ARCH" = "aarch64" ]; then - SLKCFLAGS="-O2 -fPIC" - LIBDIRSUFFIX="64" -else - SLKCFLAGS="-O2" - LIBDIRSUFFIX="" -fi - On Sun, 16 Aug 2026 at 19:32, Duncan Roe wrote: > > On Sat, Aug 15, 2026 at 08:32:03PM -0600, fourtysixandtwo wrote: > > I only remove the ARCH if/elif section if sbolint complains about both > > not being used. Not sure it's worth worrying about otherwise. > > > You *have* to remove it - `if; then; elif` is a bash syntax error -- _______________________________________________ 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 davidnchmelik at gmail.com Mon Aug 17 01:59:19 2026 From: davidnchmelik at gmail.com (David Chmelik) Date: Sun, 16 Aug 2026 18:59:19 -0700 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: References: Message-ID: On 8/16/26 7:43 AM, Marco Moock wrote: > [...] SBo currently provides > > jdk11 > jdk19 > jdk23 and jdk, which is only jdk8... is that for some reason: shouldn't it be updated to most standard stable version?? It's hundreds minor versions behind. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Aug 17 02:08:06 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 17 Aug 2026 09:08:06 +0700 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: References: Message-ID: <20260817090806.05ab755d@office64.slackie.org> >> [...] SBo currently provides >> >> jdk11 >> jdk19 >> jdk23 >and jdk, which is only jdk8... is that for some reason: shouldn't it >be updated to most standard stable version?? It's hundreds minor >versions behind. believe it or not, jdk8 is still supported until today -- 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 davidnchmelik at gmail.com Mon Aug 17 02:46:25 2026 From: davidnchmelik at gmail.com (David Chmelik) Date: Sun, 16 Aug 2026 19:46:25 -0700 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: <20260817090806.05ab755d@office64.slackie.org> References: <20260817090806.05ab755d@office64.slackie.org> Message-ID: On 8/16/26 7:08 PM, Willy Sudiarto Raharjo wrote: >>> [...] SBo currently provides >>> >>> jdk11 >>> jdk19 >>> jdk23 >> and jdk, which is only jdk8... is that for some reason: shouldn't it >> be updated to most standard stable version?? It's hundreds minor >> versions behind. > believe it or not, jdk8 is still supported until today Except jdk SlackBuild hasn't been updated since 2024; now 80 minor versions behind jdk8u501 and no longer needs login to download (outdated README).? I don't know why java.com links one this old, or what depends on it, but if SlackBuilds.org has builds depending on it, they may want update. -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Mon Aug 17 02:55:42 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 16 Aug 2026 22:55:42 -0400 (EDT) Subject: [Slackbuilds-users] Oracle Java In-Reply-To: References: <20260817090806.05ab755d@office64.slackie.org> Message-ID: <86c9ac0-2a4f-1183-f837-1e23c9fc7947@slackware.uk> On Sun, 16 Aug 2026, David Chmelik wrote: > Except jdk SlackBuild hasn't been updated since 2024; now 80 minor versions behind jdk8u501 and no longer needs login to download (outdated README).? I don't know why > java.com links one this old, or what depends on it, but if SlackBuilds.org has builds depending on it, they may want update. By policy, nothing on SBo depends jdk or any of the other Oracle jdk's. We settled on the various zulu-openjdk* as the dependency for anything that requires Java. This policy came into existence precisely because of the Oracle "no direct download link; must register" policy. None of the admins wanted the hassle of registering with Oracle, and to 100% comply with their license, we each would have had to have a separate login (due to their "no redistribution"; I couldn't download it and give a copy to Willy, for instance). And even if you registered, there was no direct download link, you'd *have* to use a JS-capable browser (hard to automate, more hassle). If Oracle's gotten rid of this, maybe we could rethink it, but I'm against that. Things work the way they are now. I don't see any benefit to switching working builds that use zulu-openjdk to using oracle's jdk instead. Plus, who's to say Oracle won't change their minds again and go back to the restrictive registration process? From willysr at slackbuilds.org Mon Aug 17 03:01:05 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 17 Aug 2026 10:01:05 +0700 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: References: <20260817090806.05ab755d@office64.slackie.org> Message-ID: <20260817100105.3949ed28@office64.slackie.org> >On 8/16/26 7:08 PM, Willy Sudiarto Raharjo wrote: >>>> [...] SBo currently provides >>>> >>>> jdk11 >>>> jdk19 >>>> jdk23 >>> and jdk, which is only jdk8... is that for some reason: shouldn't it >>> be updated to most standard stable version?? It's hundreds minor >>> versions behind. >> believe it or not, jdk8 is still supported until today >Except jdk SlackBuild hasn't been updated since 2024; now 80 minor >versions behind jdk8u501 and no longer needs login to download >(outdated README).? I don't know why java.com links one this old, or >what depends on it, but if SlackBuilds.org has builds depending on it, >they may want update. You still need to login to download i was the one updating jdk for the last few years but yeah, it's hard to keep up with all the updates since it's not my script at the first place. -- 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 davidnchmelik at gmail.com Mon Aug 17 03:07:56 2026 From: davidnchmelik at gmail.com (David Chmelik) Date: Sun, 16 Aug 2026 20:07:56 -0700 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: <20260817100105.3949ed28@office64.slackie.org> References: <20260817090806.05ab755d@office64.slackie.org> <20260817100105.3949ed28@office64.slackie.org> Message-ID: <2cace1fd-ea88-4cd8-b0b8-ee27b51b5f5e@gmail.com> On 8/16/26 8:01 PM, Willy Sudiarto Raharjo wrote: >> On 8/16/26 7:08 PM, Willy Sudiarto Raharjo wrote: >>>>> [...] SBo currently provides >>>>> >>>>> jdk11 >>>>> jdk19 >>>>> jdk23 >>>> and jdk, which is only jdk8... is that for some reason: shouldn't it >>>> be updated to most standard stable version?? It's hundreds minor >>>> versions behind. >>> believe it or not, jdk8 is still supported until today >> Except jdk SlackBuild hasn't been updated since 2024; now 80 minor >> versions behind jdk8u501 and no longer needs login to download >> (outdated README).? I don't know why java.com links one this old, or >> what depends on it, but if SlackBuilds.org has builds depending on it, >> they may want update. > You still need to login to download You don't on java.com. > i was the one updating jdk for the last few years but yeah, it's hard > to keep up with all the updates since it's not my script at the first > place. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Aug 17 03:16:08 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 17 Aug 2026 10:16:08 +0700 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: <2cace1fd-ea88-4cd8-b0b8-ee27b51b5f5e@gmail.com> References: <20260817090806.05ab755d@office64.slackie.org> <20260817100105.3949ed28@office64.slackie.org> <2cace1fd-ea88-4cd8-b0b8-ee27b51b5f5e@gmail.com> Message-ID: <20260817101608.1fe73ceb@office64.slackie.org> >>> Except jdk SlackBuild hasn't been updated since 2024; now 80 minor >>> versions behind jdk8u501 and no longer needs login to download >>> (outdated README).? I don't know why java.com links one this old, or >>> what depends on it, but if SlackBuilds.org has builds depending on >>> it, they may want update. >> You still need to login to download >You don't on java.com. That's JRE, not JDK -- 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 Mon Aug 17 03:19:25 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 17 Aug 2026 10:19:25 +0700 Subject: [Slackbuilds-users] Updates on OpenMPI In-Reply-To: References: Message-ID: <20260817101925.26a447a1@office64.slackie.org> >Hi everyone, > >I maintain the openmpi package. It is currently at version 4, and I >would like to update it to version 5. > >I have run into some issues with OpenMPI 5 when using the CESM >software, but it works well with others like LAMMPS and GROMACS. Would >it be possible to upload a new version and keep both versions >available in the repository? What do you think is the best approach? > >- Should I update openmpi to version 5 and create a new package for >openmpi4 ? > >- Or should I keep openmpi at version 4 and create a new package for >openmpi5? Basically it's up to maintainers on how to handle this if all the other software that depends on openmpi is working fine with version 5, i would suggest to update it to version 5 instead But as you mentioned there was some issue with version 5, you can upload openmpi-legacy or openmpi4 and push the updates in openmpi to version 5. We will change the requirement of those who need the version 4 (please make a note when submitting a new version). -- 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 Mon Aug 17 03:24:48 2026 From: dchmelik at gmail.com (David Chmelik) Date: Sun, 16 Aug 2026 20:24:48 -0700 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: <20260817101608.1fe73ceb@office64.slackie.org> References: <20260817090806.05ab755d@office64.slackie.org> <20260817100105.3949ed28@office64.slackie.org> <2cace1fd-ea88-4cd8-b0b8-ee27b51b5f5e@gmail.com> <20260817101608.1fe73ceb@office64.slackie.org> Message-ID: <42f1519b-4826-4bd8-b690-31bb40e9b15c@gmail.com> On 8/16/26 7:55 PM, B. Watson wrote: > On Sun, 16 Aug 2026, David Chmelik wrote: > >> Except jdk SlackBuild hasn't been updated since 2024; now 80 minor >> versions behind jdk8u501 and no longer needs login to download >> (outdated README).? I don't know why >> java.com links one this old, or what depends on it, but if >> SlackBuilds.org has builds depending on it, they may want update. > > By policy, nothing on SBo depends jdk or any of the other Oracle > jdk's. We settled on the various zulu-openjdk* as the dependency for > anything that requires Java. Good. > This policy came into existence precisely because of the Oracle > "no direct download link; must register" policy. None of the admins > wanted the hassle of registering with Oracle, and to 100% comply > with their license, we each would have had to have a separate login > (due to their "no redistribution"; I couldn't download it and give a > copy to Willy, for instance). And even if you registered, there was no > direct download link, you'd *have* to use a JS-capable browser (hard > to automate, more hassle). yes.? It had also been possible to get elsewhere, even some sites that had it legally, such as Adobe, but Oracle made a serious mistake if they want a lot of people to use this. > If Oracle's gotten rid of this [...] I was mistaken. On 8/16/26 8:16 PM, Willy Sudiarto Raharjo wrote: On 8/16/26 8:16 PM, Willy Sudiarto Raharjo wrote: >>>> Except jdk SlackBuild hasn't been updated since 2024; now 80 minor >>>> versions behind jdk8u501 and no longer needs login to download >>>> (outdated README).? I don't know why java.com links one this old, or >>>> what depends on it, but if SlackBuilds.org has builds depending on >>>> it, they may want update. >>> You still need to login to download >> You don't on java.com. > That's JRE, not JDK I stand corrected. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at dorfdsl.de Mon Aug 17 05:22:15 2026 From: mm at dorfdsl.de (Marco Moock) Date: Mon, 17 Aug 2026 07:22:15 +0200 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: References: Message-ID: Am 17.08.26 um 03:59 schrieb David Chmelik: > On 8/16/26 7:43 AM, Marco Moock wrote: >> [...] SBo currently provides >> >> jdk11 >> jdk19 >> jdk23 > and jdk, which is only jdk8... is that for some reason: shouldn't it be > updated to most standard stable version?? It's hundreds minor versions > behind. Dunno about JDK8 (that is not shown on the developer website), but JRE8 is the default that is being shipped to end users. -- Gru? Marco Junk-Mail bitte an trashcan 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 willysr at slackbuilds.org Mon Aug 17 05:58:07 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 17 Aug 2026 12:58:07 +0700 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: References: Message-ID: <20260817125807.55bf5f18@home.slackie.org> >> and jdk, which is only jdk8... is that for some reason: shouldn't it be >> updated to most standard stable version?? It's hundreds minor versions >> behind. > >Dunno about JDK8 (that is not shown on the developer website), but JRE8 >is the default that is being shipped to end users. it's still shown on the developer page you just need to scroll down a bit to find JDK 8 links -- 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 korgie at gmail.com Mon Aug 17 07:55:25 2026 From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=) Date: Mon, 17 Aug 2026 10:55:25 +0300 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: References: Message-ID: <42EBB04E-8A8E-4002-AAEC-AC06C1751302@gmail.com> > 17 ??? 2026, 05:46, ? ??????? ?David Chmelik ? ??????: > > Except jdk SlackBuild hasn't been updated since 2024; now 80 minor versions behind jdk8u501 I think this is not a issue. You can change the $VERSION variable before start the SlackBuild with VERSION=type_version jdk8.SlackBuild From mm at dorfdsl.de Mon Aug 17 18:13:23 2026 From: mm at dorfdsl.de (Marco Moock) Date: Mon, 17 Aug 2026 20:13:23 +0200 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: <20260817125807.55bf5f18@home.slackie.org> References: <20260817125807.55bf5f18@home.slackie.org> Message-ID: <040f83bb-3dfd-447b-b6a5-4f3b6e252aff@dorfdsl.de> Am 17.08.26 um 07:58 schrieb Willy Sudiarto Raharjo: > it's still shown on the developer page > you just need to scroll down a bit to find JDK 8 links Would it be reasonable to add a JRE 8 slackbuild? -- Gru? Marco Junk-Mail bitte an trashcan 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 urchlay at slackware.uk Mon Aug 17 20:54:39 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 17 Aug 2026 16:54:39 -0400 (EDT) Subject: [Slackbuilds-users] Oracle Java In-Reply-To: <040f83bb-3dfd-447b-b6a5-4f3b6e252aff@dorfdsl.de> References: <20260817125807.55bf5f18@home.slackie.org> <040f83bb-3dfd-447b-b6a5-4f3b6e252aff@dorfdsl.de> Message-ID: <96ce9d9-c815-aca5-c4d9-113d2de29af3@slackware.uk> On Mon, 17 Aug 2026, Marco Moock wrote: > Would it be reasonable to add a JRE 8 slackbuild? What would we use it for? All the builds in our repo that require Java already work with whichever zulu-openjdk* version they need... and possibly with newer versions of zulu, as well (the .info file is supposed to list the minimum required version). It would only make sense to have an oracle JRE 8 build if someone wants to add a slackbuild for something that really actually needs oracle's java, and wouldn't work with any of the zulu-openjdk* or openjdk* we already have. Unlike the JDK, the JRE is useless by itself. From willysr at slackbuilds.org Mon Aug 17 23:11:20 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 18 Aug 2026 06:11:20 +0700 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: <040f83bb-3dfd-447b-b6a5-4f3b6e252aff@dorfdsl.de> References: <20260817125807.55bf5f18@home.slackie.org> <040f83bb-3dfd-447b-b6a5-4f3b6e252aff@dorfdsl.de> Message-ID: <20260818061120.5c9069e4@home.slackie.org> >Would it be reasonable to add a JRE 8 slackbuild? no, since JDK already includes JRE -- 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 duncan_roe at optusnet.com.au Tue Aug 18 02:39:15 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Tue, 18 Aug 2026 12:39:15 +1000 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> References: <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> Message-ID: Hi Urchlay, On Sun, Aug 16, 2026 at 05:31:36AM -0400, B. Watson wrote: > > > On Sun, 16 Aug 2026, Lumin Etherlight via SlackBuilds-users wrote: > > > "B. Watson" writes: > > > > > Also note that your commits have to be one per > > > build, not one giant commit that alters multiple > > > builds. I know it's annoying but that's how we > > > keep track of things... > > > > Just to note, this will mean /thousands/ of > > git commits just removing unused variables. 2777 commits of which I have so far pushed 2. > > Yeah. It's actually why it hasn't already been done. The extra > unused variables don't actually do any harm... They blow out the output from sbolint -a to over 5000 lines (nice new log feature BTW). With this bulk change it gets down below 1000. You can start to see other candidate patterns e.g.:- | suggest replacing 'python' with 'python2' for future-proofing My thinking was that fixing these now would make the admins' job easier at the next stable. > > The best time to do this would be during 'development cycle', > when a new Slackware stable has just been released, and the repo > is closed while we port all the builds over (fix compile errors, > remove builds that were included in the new Slackware, etc). I thouhght PRs were blocked during the freeze. Are they not? > > Unfortunately that means, no time soon. We all have our guesses of > when we expect a new Slackware, but nobody knows... I had the idea that I would script the PR process using githup-cli to make the PR. That's nearly done. Then I would put it in a cron job to send a constant trickle until they were all done. The constant trickle is to ensure servers don't get swamped. Also gives time to delete branches when PRs are closed. What would you like me to do? Cheers ... Duncan. From urchlay at slackware.uk Tue Aug 18 02:54:14 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 17 Aug 2026 22:54:14 -0400 (EDT) Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> Message-ID: <28741a74-5347-3ff6-249e-a464aa4c52e@slackware.uk> On Tue, 18 Aug 2026, Duncan Roe wrote: > They blow out the output from sbolint -a to over 5000 lines (nice new log > feature BTW). With this bulk change it gets down below 1000. You can start to > see other candidate patterns e.g.:- > | suggest replacing 'python' with 'python2' for future-proofing > My thinking was that fixing these now would make the admins' job easier at the > next stable. Yes, it would... > I thouhght PRs were blocked during the freeze. Are they not? No idea, I'm not involved with the github/lab/etc end of things. > I had the idea that I would script the PR process using githup-cli to make the > PR. That's nearly done. Then I would put it in a cron job to send a constant > trickle until they were all done. The constant trickle is to ensure servers > don't get swamped. Also gives time to delete branches when PRs are closed. > > What would you like me to do? The above looks good: a few at a time. Maybe as many as 100 per weekly update. I mean I've pushed 100 commits in a week lots of times without swamping anything... You said 2777 commits, that'll take 28 weeks or 7 months. Possibly the next Slackware alpha/beta/RC will happen within those 7 months, or possibly not (I lean toward the latter, but I'm a congenital pessimist). From mm at dorfdsl.de Tue Aug 18 04:22:42 2026 From: mm at dorfdsl.de (Marco Moock) Date: Tue, 18 Aug 2026 06:22:42 +0200 Subject: [Slackbuilds-users] Oracle Java In-Reply-To: <96ce9d9-c815-aca5-c4d9-113d2de29af3@slackware.uk> References: <20260817125807.55bf5f18@home.slackie.org> <040f83bb-3dfd-447b-b6a5-4f3b6e252aff@dorfdsl.de> <96ce9d9-c815-aca5-c4d9-113d2de29af3@slackware.uk> Message-ID: Am 17.08.26 um 22:54 schrieb B. Watson: > > All the builds in our repo that require Java already work with > whichever zulu-openjdk* version they need... and possibly with newer > versions of zulu, as well (the .info file is supposed to list the > minimum required version). I have some applications that use Java Web Start that either need Oracle JRE 8 (as this got removed in later versions) or IcedTea. -- Gru? Marco Junk-Mail bitte an trashcan 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 willysr at slackbuilds.org Tue Aug 18 04:30:48 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 18 Aug 2026 11:30:48 +0700 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> Message-ID: <20260818113048.56421cdf@office64.slackie.org> >I thouhght PRs were blocked during the freeze. Are they not? yes, but we are not there yet -- 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 lumin+slackbuilds at etherlight.link Tue Aug 18 10:19:11 2026 From: lumin+slackbuilds at etherlight.link (Lumin Etherlight) Date: Tue, 18 Aug 2026 13:19:11 +0300 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: <28741a74-5347-3ff6-249e-a464aa4c52e@slackware.uk> (B. Watson's message of "Mon, 17 Aug 2026 22:54:14 -0400 (EDT)") References: <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> <28741a74-5347-3ff6-249e-a464aa4c52e@slackware.uk> Message-ID: <3JeTQjwWg6YuxcNcJ0soLfgXe2oevnmi@etherlight.link> "B. Watson" writes: > On Tue, 18 Aug 2026, Duncan Roe wrote: > >> I had the idea that I would script the PR process >> using githup-cli to make the PR. That's nearly >> done. Then I would put it in a cron job to send a >> constant trickle until they were all done. The >> constant trickle is to ensure servers don't get >> swamped. Also gives time to delete branches when >> PRs are closed. >> >> What would you like me to do? > > The above looks good: a few at a time. Maybe as > many as 100 per weekly update. I mean I've pushed > 100 commits in a week lots of times without > swamping anything... You said 2777 commits, > that'll take 28 weeks or 7 months. If the git history is inevitably going to have thousands of commits changing little script compliance things, then I would suggest they're all made in one go. Instead of having hundreds of noise commits in little chunks clustered over many months, we'd just have them all in one chunk, where someone can skip over them when reading the history. Pushing thousands of commits in one go is not an issue for git, in my experience. Unless you have an expensive automation system that will have to run once for each commit, of course. Best Regards, Lumin Etherlight From willysr at slackbuilds.org Tue Aug 18 13:29:05 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 18 Aug 2026 20:29:05 +0700 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: <3JeTQjwWg6YuxcNcJ0soLfgXe2oevnmi@etherlight.link> References: <2fc3c38-695-3e3d-e367-b9fbef8b690@slackware.uk> <583d45f5-738-eb97-9c1-d054a8b72ac@slackware.uk> <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> <28741a74-5347-3ff6-249e-a464aa4c52e@slackware.uk> <3JeTQjwWg6YuxcNcJ0soLfgXe2oevnmi@etherlight.link> Message-ID: <20260818202905.12547da0@home.slackie.org> > If the git history is inevitably going to > have thousands of commits changing little script > compliance things, then I would suggest they're > all made in one go. Instead of having hundreds of > noise commits in little chunks clustered over many > months, we'd just have them all in one chunk, > where someone can skip over them when reading the > history. Pushing thousands of commits in one go > is not an issue for git, in my experience. Unless > you have an expensive automation system that will > have to run once for each commit, of course. This kind of situation is fine during development cycle, not during normal cycle where each commits will be listed in /ready and used as reference to know which script need to be updated and tarball creations during public update. In development cycle, all hell breaks loose :) You can add, remove, change, update, patch, anything -- 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 duncan_roe at optusnet.com.au Tue Aug 18 23:15:10 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Wed, 19 Aug 2026 09:15:10 +1000 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: <20260818202905.12547da0@home.slackie.org> References: <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> <28741a74-5347-3ff6-249e-a464aa4c52e@slackware.uk> <3JeTQjwWg6YuxcNcJ0soLfgXe2oevnmi@etherlight.link> <20260818202905.12547da0@home.slackie.org> Message-ID: Hi Willy, On Tue, Aug 18, 2026 at 08:29:05PM +0700, Willy Sudiarto Raharjo wrote: > > If the git history is inevitably going to > > have thousands of commits changing little script > > compliance things, then I would suggest they're > > all made in one go. Instead of having hundreds of > > noise commits in little chunks clustered over many > > months, we'd just have them all in one chunk, > > where someone can skip over them when reading the > > history. Pushing thousands of commits in one go > > is not an issue for git, in my experience. Unless > > you have an expensive automation system that will > > have to run once for each commit, of course. > > > This kind of situation is fine during development cycle, not during normal > cycle where each commits will be listed in /ready and used as reference to know > which script need to be updated and tarball creations during public update. > > In development cycle, all hell breaks loose :) > You can add, remove, change, update, patch, anything > I'd prefer to do it that way too. But, as a non-admin, would I be able to? If not, I see 2 alternatives:- 1. Make me an admin 2. I post the Q macros that do the job and an admin runs them. Needs the Q editor to be in the repo but it should be by then In the meantime I'll finish testing the trickle system but won't start cron job, Cheers ... Duncan. From willysr at slackbuilds.org Tue Aug 18 23:35:35 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 19 Aug 2026 06:35:35 +0700 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> <28741a74-5347-3ff6-249e-a464aa4c52e@slackware.uk> <3JeTQjwWg6YuxcNcJ0soLfgXe2oevnmi@etherlight.link> <20260818202905.12547da0@home.slackie.org> Message-ID: <20260819063535.41a10192@home.slackie.org> >> In development cycle, all hell breaks loose :) >> You can add, remove, change, update, patch, anything >> >I'd prefer to do it that way too. But, as a non-admin, would I be able to? >If not, I see 2 alternatives:- > >1. Make me an admin > >2. I post the Q macros that do the job and an admin runs them. > Needs the Q editor to be in the repo but it should be by then > >In the meantime I'll finish testing the trickle system but won't start cron >job, either you can send us PR for this (one commit per script) or wait until development cycle starts :) -- 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 duncan_roe at optusnet.com.au Wed Aug 19 01:12:56 2026 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Wed, 19 Aug 2026 11:12:56 +1000 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: <20260819063535.41a10192@home.slackie.org> References: <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> <28741a74-5347-3ff6-249e-a464aa4c52e@slackware.uk> <3JeTQjwWg6YuxcNcJ0soLfgXe2oevnmi@etherlight.link> <20260818202905.12547da0@home.slackie.org> <20260819063535.41a10192@home.slackie.org> Message-ID: Hi Willy, On Wed, Aug 19, 2026 at 06:35:35AM +0700, Willy Sudiarto Raharjo wrote: > >> In development cycle, all hell breaks loose :) > >> You can add, remove, change, update, patch, anything > >> > >I'd prefer to do it that way too. But, as a non-admin, would I be able to? > > >If not, I see 2 alternatives:- > > > >1. Make me an admin > > > >2. I post the Q macros that do the job and an admin runs them. > > Needs the Q editor to be in the repo but it should be by then > > > >In the meantime I'll finish testing the trickle system but won't start cron > >job, > > either you can send us PR for this (one commit per script) or > wait until development cycle starts :) > I'm fine with waiting until development cycle starts. Once it does start, how do I make the changes? Alternative 2, create a branch for me or what? Cheers ... Duncan. From willysr at slackbuilds.org Wed Aug 19 01:27:38 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 19 Aug 2026 08:27:38 +0700 Subject: [Slackbuilds-users] template idea: --no-same-owner In-Reply-To: References: <2d636de6-7e45-bfa-5fb6-793fafba736b@slackware.uk> <1b7a5fd7-b32c-27ce-3668-34a91bca2d4d@slackware.uk> <28741a74-5347-3ff6-249e-a464aa4c52e@slackware.uk> <3JeTQjwWg6YuxcNcJ0soLfgXe2oevnmi@etherlight.link> <20260818202905.12547da0@home.slackie.org> <20260819063535.41a10192@home.slackie.org> Message-ID: <20260819082738.25a421db@office64.slackie.org> >I'm fine with waiting until development cycle starts. Once it does >start, how do I make the changes? Alternative 2, create a branch for >me or what? you can send PR to github/gitlab/codeberg :) -- 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 tonus1 at free.fr Wed Aug 19 21:54:01 2026 From: tonus1 at free.fr (Tonus) Date: Wed, 19 Aug 2026 23:54:01 +0200 Subject: [Slackbuilds-users] Upgrade and split package python-urwid Message-ID: <87pkzdkc92.fsf@Baldr.vingolf.info> Hi all I just pushed 2 packages to upgrade python-urwid, for Python2 and Python3. Python2 version is unchanged and Python3 latest available. I also updated my scripts that depends now on python3-urwid. Dear maintainers (copy of this message to prevent if some are not on the list) of - pudb (D Woodfall) - python-urwid_readline (D Woodfall) - s-tui (M.Dinslage) - speedometer (Edinaldo P. Silva) - toot (Kevin Bryant) - upass (D Woodfall) - urlscan (abooksigun) - vit (Dan-Simon Myrland) Does anyone wants to keep the Python2 version ? The agnostic version ? I then suggest the candidates grab the maintainership for those 0:-) Otherwise, thanks to upgrade your scripts and let admins delete the unused version(s). -- Regards, Tonus. From willysr at slackbuilds.org Thu Aug 20 03:50:12 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 20 Aug 2026 10:50:12 +0700 Subject: [Slackbuilds-users] signal-desktop updates Message-ID: <20260820105012.7a957496@office64.slackie.org> Hi all Please note that we reverted signal-desktop back to version 8.1.0, the last version that is known to be running well with standard GLIBC in Slackware 15.0. We also removed signal-desktop-legacy since it's no longer useful. If you wish to upgrade to newer version, you need to upgrade the GLIBC packages from /testing by yourself, put them in /etc/slackpkg/blacklist so that it will not get reverted to the default stock version, and build the newer signal-desktop manually. We are looking for other scripts that depends on newer GLIBC in the repo as now we have GLIBC detection on our CI tools, thanks to Urchlay. -- 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 Thu Aug 20 05:20:02 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 20 Aug 2026 12:20:02 +0700 Subject: [Slackbuilds-users] Upgrade and split package python-urwid In-Reply-To: <87pkzdkc92.fsf@Baldr.vingolf.info> References: <87pkzdkc92.fsf@Baldr.vingolf.info> Message-ID: <20260820122002.456096d7@office64.slackie.org> >I just pushed 2 packages to upgrade python-urwid, for Python2 and >Python3. Python2 version is unchanged and Python3 latest available. > >I also updated my scripts that depends now on python3-urwid. > >Dear maintainers (copy of this message to prevent if some are not on >the list) of >- pudb (D Woodfall) >- python-urwid_readline (D Woodfall) >- s-tui (M.Dinslage) >- speedometer (Edinaldo P. Silva) >- toot (Kevin Bryant) >- upass (D Woodfall) >- urlscan (abooksigun) >- vit (Dan-Simon Myrland) >Does anyone wants to keep the Python2 version ? The agnostic version ? > >I then suggest the candidates grab the maintainership for those 0:-) > >Otherwise, thanks to upgrade your scripts and let admins delete the >unused version(s). i hope i already covered it all here https://github.com/SlackBuildsOrg/slackbuilds/pull/17306 -- 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 artourter at gmail.com Thu Aug 20 18:53:00 2026 From: artourter at gmail.com (Greg Tourte) Date: Thu, 20 Aug 2026 20:53:00 +0200 Subject: [Slackbuilds-users] signal-desktop updates In-Reply-To: <20260820105012.7a957496@office64.slackie.org> References: <20260820105012.7a957496@office64.slackie.org> Message-ID: I am on holidays at the moment so cannot really update my packages but i have followed the thread and if the sollution propose is acceptable, I will update the script so that we can have the latest version for slackware. However, distributing 8.1 in sbo is not a good idea as it will not work. Signal somehow block old version of the clients from connecting. So we can definitely remove the legacy package, but if you can wait a couple of weeks we can have a fully working version in the repo. That is of course unless sbo admin have decided that the proposed solution is not something we should do with pur packages. Sorry for being out of contact for a while. Cheers Greg On Thu, 20 Aug 2026, 05:50 Willy Sudiarto Raharjo, wrote: > Hi all > > Please note that we reverted signal-desktop back to version > 8.1.0, the last version that is known to be running well with standard > GLIBC in Slackware 15.0. We also removed signal-desktop-legacy since > it's no longer useful. > > If you wish to upgrade to newer version, you need to upgrade the GLIBC > packages from /testing by yourself, put them in /etc/slackpkg/blacklist > so that it will not get reverted to the default stock version, and > build the newer signal-desktop manually. > > We are looking for other scripts that depends on newer GLIBC in the > repo as now we have GLIBC detection on our CI tools, thanks to Urchlay. > > > > -- > Willy Sudiarto Raharjo > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Aug 21 01:00:05 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 21 Aug 2026 08:00:05 +0700 Subject: [Slackbuilds-users] signal-desktop updates In-Reply-To: References: <20260820105012.7a957496@office64.slackie.org> Message-ID: <20260821080005.7821866d@office64.slackie.org> >I am on holidays at the moment so cannot really update my packages but >i have followed the thread and if the sollution propose is acceptable, >I will update the script so that we can have the latest version for >slackware. > >However, distributing 8.1 in sbo is not a good idea as it will not >work. Signal somehow block old version of the clients from connecting. > >So we can definitely remove the legacy package, but if you can wait a >couple of weeks we can have a fully working version in the repo. That >is of course unless sbo admin have decided that the proposed solution >is not something we should do with pur packages. > >Sorry for being out of contact for a while. No problem, enjoy your holiday I updated the README in signal-desktop on how to build newer version assuming users have used new glibc in testing, so they should be able to update signal-desktop manually. -- 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 fredg at zaclys.net Fri Aug 21 04:48:09 2026 From: fredg at zaclys.net (Fred. Galusik) Date: Fri, 21 Aug 2026 06:48:09 +0200 Subject: [Slackbuilds-users] Upgrade and split package python-urwid In-Reply-To: <20260820122002.456096d7@office64.slackie.org> References: <87pkzdkc92.fsf@Baldr.vingolf.info> <20260820122002.456096d7@office64.slackie.org> Message-ID: Hi, Le jeudi 20 ao?t 2026 ? 12:20 (+0700), Willy Sudiarto Raharjo a ?crit : > i hope i already covered it all here > https://github.com/SlackBuildsOrg/slackbuilds/pull/17306 Thank you very much (as the new maintainer of pudb). Best regards. -fredg > _______________________________________________ > 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 davidnchmelik at gmail.com Fri Aug 21 20:56:59 2026 From: davidnchmelik at gmail.com (David Chmelik) Date: Fri, 21 Aug 2026 13:56:59 -0700 Subject: [Slackbuilds-users] KuickShow-stable Message-ID: I know this mailing list isn't officially about Slackware-current, but since a few years after Slackware 14.2, many users just switched to Slackware-current for servers (needing some upgrades) and even for desktop (needing some new drivers).? This is just to let people know that I've tested my KuickShow SlackBuild on Slackware-current and it seems to work fine, and I'm willing to help with any problems.? Ponce can/should go ahead and increment the Slackware-current SBo-git to KuickShow v0.11.0 (don't think it needs any other changes, but double-check) and if there's a Slackware-stable release in the lately average release schedule (five years) that may be the version of KuickShow it gets.? That won't work on Slackware-stable unless you install alienBOB's KDE6 (ktown) if it has it, and any dependencies (QT6, etc.) but may be worth testing because the last Slackware-stable KuickShow on SBo was unfortunately a git commit, and I don't know how good that was, but the previous stable was many years ago, though if you still use KDE5 and prefer stable, I think you can still actually decrement the version to 0.10.0. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dchmelik at gmail.com Fri Aug 21 20:57:18 2026 From: dchmelik at gmail.com (David Chmelik) Date: Fri, 21 Aug 2026 13:57:18 -0700 Subject: [Slackbuilds-users] KuickShow-stable Message-ID: <2efe0027-75cf-4ec9-ad25-a3df1a0f631b@gmail.com> I know this mailing list isn't officially about Slackware-current, but since a few years after Slackware 14.2, many users just switched to Slackware-current for servers (needing some upgrades) and even for desktop (needing some new drivers).? This is just to let people know that I've tested my KuickShow SlackBuild on Slackware-current and it seems to work fine, and I'm willing to help with any problems.? Ponce can/should go ahead and increment the Slackware-current SBo-git to KuickShow v0.11.0 (don't think it needs any other changes, but double-check) and if there's a Slackware-stable release in the lately average release schedule (five years) that may be the version of KuickShow it gets.? That won't work on Slackware-stable unless you install alienBOB's KDE6 (ktown) if it has it, and any dependencies (QT6, etc.) but may be worth testing because the last Slackware-stable KuickShow on SBo was unfortunately a git commit, and I don't know how good that was, but the previous stable was many years ago, though if you still use KDE5 and prefer stable, I think you can still actually decrement the version to 0.10.0. From willysr at slackbuilds.org Sat Aug 22 06:59:59 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 22 Aug 2026 13:59:59 +0700 Subject: [Slackbuilds-users] Updates - 20260822.1 Message-ID: <20260822135959.75d1d6ee@home.slackie.org> Hi we just found out that there are multiple scripts that were submitted and tested under -current environment and passed our CI. Some of them are -bin so it's binary repackaging so it's not detected by our CI. We will do further examination on these scripts and we will tell the results soon. In the meantime, some scripts that are using new GLIBC completely are being tracked and removed starting from this batch of updates, except when there's a situation like what happened in positron. It's an IDE, and the main application works fine, but there are some files that requires newer GLIBC to work. For now, we allow this to pass since i personally test this on clean Slackware 15.0 VM, but we can't do this on every scripts out there. Maintainers, please make sure you test all the scripts you submitted on Slackware 15.0 machines, either in bare metals or inside a VM or chroot environment to make sure it works for Slackware 15.0. Thank you Sat Aug 22 06:40:58 UTC 2026 academic/AlphaPlot: Removed unused LIBDIRSUFFIX and SLKCFLAGS academic/DendroPy: Removed unused LIBDIRSUFFIX & SLKCFLAGS academic/FreeFem: Removed unused SLKCFLAGS academic/Gabedit: Remove unused LIBDIRSUFFIX and SLKCFLAGS academic/GeoGebra: Removed unused LIBDIRSUFFIX and SLKCFLAGS academic/MetaPhlAn2: Use 7-digit commit hash in URL. academic/R: Updated for version 4.6.1. academic/chartgeany: Orphaned (unmaintained). academic/copasi: Updated for version 4.47.309. academic/eprover: Updated for version 3.5.1. academic/gpredict: Updated for version 2.6 academic/hp-prime: Updated for version 2.3.1 academic/mathics: Updated for version 4.0.0 + new maintainer academic/plus42: fixed source md5 academic/speedcrunch: Orphaned (unmaintained). academic/tuxmath: Orphaned (unmaintained). academic/wxMaxima: Orphaned (unmaintained). academic/xsimd: Version bump to 14.3.0 academic/zotero: update to 10.0 academinc/acl2: Fix path in starter script accessibility/easystroke: Orphaned (unmaintained). audio/audioconvert: Orphaned (unmaintained). audio/eyeD3: Orphaned (unmaintained). audio/kradio: Orphaned (unmaintained). audio/nas: Orphaned (unmaintained). audio/ncspot: Updated for version 1.4.0. audio/reaper: Updated for version 7.79 audio/retrovol: Orphaned (unmaintained). audio/xcfa: Orphaned (unmaintained). audio/xforge: Orphaned (unmaintained). desktop/ClamAV-GUI: Updated for version 1.4.4 desktop/calcure: Updated for version 3.3. desktop/clipit: Orphaned (unmaintained). desktop/copyq: Orphaned (unmaintained). desktop/cwm: revert patch and build desktop/notification-daemon: Orphaned (unmaintained). desktop/s1kls: Orphaned (unmaintained). desktop/sdorfehs: Updated for version 1.7 + new maintainer desktop/standard-notes-bin: Updated for version 3.202.0 desktop/xonclock: Orphaned (unmaintained). development/OpenJDK17: Update README. development/OpenJDK21: Update README. development/a68g: Updated for version 3.13.3 development/android-tools: Version bump to 37.0.0 development/antigravity-cli: Updated for version 1.1.14 development/antigravity: Updated for version 2.8.1 development/aws-cdk: Updated for version 2.1137.0. development/chicken: Updated for version 6.0.0. development/diffuse: Fix doinst.sh (icon cache). development/electron-bin: Updated for version 43.4.1 development/github-cli: Updated for version 2.98.0 development/goland: Updated for version 2026.2.1. development/idea: Updated for version 2026.2.1. development/jdk11: Removed (EOL and unmaintained). development/jdk: New maintainer. development/jdk: Updated for version 8u501. development/ldns: Fix lint issues, orphan. development/mongodb-shell: Updated for version 2.10.0. development/mysql-workbench: Use zulu-openjdk25 development/pd-psql: Removed (source 404 and unmaintained). development/pnpm: Updated for version 11.22.0. development/positron: Updated for version 2026.08.1_2. development/prek: Updated for version 0.4.14. development/pudb: New maintainer. development/pudb: Updated for version 2025.1.5. development/pycharm: Updated for version 2026.2.1 development/python3-numpy-legacy: Fix README warning. development/regexxer: Orphaned (unmaintained). development/rider: Updated for version 2026.2.1. development/rstudio-desktop: new maintainer development/rustc-demangle: Fix README warning. development/smlnj: Updated for version 110.99.9 + new maintainer development/sourcegit: Updated for version 2026.18 development/tracy: Updated for version 0.14.0 development/vis: Updated for version 0.9 + new maintainer development/vscode-bin: Updated for version 1.134.0. development/vstudio: Updated for version 17.5.3 development/xmlcopyeditor: Orphaned (unmaintained). development/zig: Fix README warning. development/zope.interface: updated for version 8.5 development/zope.testing: updated for version 6.2 games/Mindustry: Updated for version 159.7 games/ags: Updated for version 3.6.2.20 games/chroma: Version bump to 1.21 games/crrcsim: Fix desktop ownership. games/dealers-choice: Fix doinst.sh (icon cache). games/enigma-marbles: Use correct maintainer name. games/freeciv: Updated for version 3.2.5 games/kmuddy: Fix doinst.sh (icon cache). games/oolite: Removed (FTBFS). games/openmsx-catapult: New maintainer games/openmsx-debugger: New maintainer games/openmsx: New maintainer games/solarus: Updated for version 2.1.2 games/xmoto: Version bump to 0.6.3 gis/osm-gps-map: Updated for version 1.2.1. git/ci: Update CI dependencies. graphics/Blender: Updated for version 5.2.0 graphics/HotShots: Orphaned (unmaintained). graphics/drawio: Updated for version 31.1.8. graphics/graphviz: updated for version 16.0.0 graphics/qcad: Orphaned (unmaintained). graphics/renderdoc: Updated for version 1.13 graphics/yagf: Orphaned (unmaintained). ham/SDRPlay: Update source. ham/SoapyFobosSDR: Updated for version 20260820.aa8d486c. ham/gridtracker2: Fix doinst.sh (icon cache). ham/libfobos-sdr-agile: Updated for version 3.3.0. ham/liquid-dsp: Updated for version 1.8.2. ham/qlog: Updated for version 0.52.0. ham/sdrangel: Updated for version 7.27.2. ham/sdrpp: Updated for version 20260820.8c9f5ee8. ham/sgp4: Updated for version 20260820.661e057a. libraries/SDL2_sound: updated for version 2.0.6 libraries/bitstream: Updated for version 1.6 + new maintainer libraries/cdk: Orphaned (unmaintained). libraries/chess-library: Added (chess library). libraries/cuneiform: Orphaned (unmaintained). libraries/dcadec: Orphaned (unmaintained). libraries/enca: Orphaned (unmaintained). libraries/fpconst: Orphaned (unmaintained). libraries/fzssh: Updated for version 1.4.0. libraries/gdata: Orphaned (unmaintained). libraries/gtkimageview: New maintainer libraries/http-parser: Orphaned (unmaintained). libraries/libb64: Orphaned (unmaintained). libraries/libbgcode: Fix README warning. libraries/libdaemon: New maintainer libraries/libdivecomputer: Orphaned (unmaintained). libraries/libdvbcsa: New maintainer. libraries/libfilezilla: Updated for version 0.57.0. libraries/libinklevel: Orphaned (unmaintained). libraries/libmodplug: New maintainer. libraries/libmusicbrainz3: Orphaned (unmaintained). libraries/libotf: Orphaned (unmaintained). libraries/libqxt: Orphaned (unmaintained). libraries/libunique: New maintainer. libraries/libxlsxwriter: Orphaned (unmaintained). libraries/lockdev: Orphaned (unmaintained). libraries/logilinux: Added (Logitech MX Creative Console library). libraries/mini18n: Orphaned (unmaintained). libraries/nspluginwrapper: Orphaned (unmaintained). libraries/ois: Orphaned (unmaintained). libraries/pilot-link-opt: Added (Palm Handheld Glue). libraries/pyPEG2: Orphaned (unmaintained). libraries/soil: Orphaned (unmaintained). libraries/spandsp: Use 7-digit commit hash i URL. libraries/t4k_common: Orphaned (unmaintained). libraries/vali: Fix README warning. libraries/webrtc-audio-processing: Use 7-digit commit hash i URL. misc/autofirma: Use zulu-openjdk25. misc/es40: Updated for version 0.81 misc/exploitdb: Updated for version 2026_08_19. misc/ollama: Updated for version 0.32.15. misc/par2cmdline: Updated for version 1.3.0. misc/subsurface: Orphaned (unmaintained). multimedia/audiopreview: Orphaned (unmaintained). multimedia/devedeng: Updated for version 4.19.0 multimedia/dvblast: New maintainer multimedia/farsight2: Orphaned (unmaintained). multimedia/flowblade: Use 7-digit commit hash i URL. multimedia/freetube: Fix permission. multimedia/freetube: Updated for version 0.25.2. multimedia/gst0-ffmpeg: Orphaned (unmaintained). multimedia/gst0-plugins-ugly: Orphaned (unmaintained). multimedia/inputstream.adaptive: Version bump to 21.5.23 multimedia/opera-ffmpeg-codecs: Updated for version 43.0.0_b8 multimedia/plexmediaserver: Updated for 1.43.3.10896_cb3ebc72d. multimedia/radiotray: Orphaned (unmaintained). multimedia/shotcut: Orphaned (unmaintained). multimedia/w_scan_cpp: Updated for vdr version 2.8.2. multimedia/xvst: Orphaned (unmaintained). network/3proxy: Updated for version 0.9.9. network/AdGuardHome: Updated for version 0.107.79. network/Electrum-bin: Added (Bitcoin Client). network/Electrum: Update README network/addrwatch: Orphaned (unmaintained). network/atheme: Orphaned (unmaintained). network/brave-browser: update to 1.93.137 network/brave-origin: update to 1.93.137 network/csync: Updated requirements + new maintainer network/discord: Version bump to 1.0.154 network/dnsproxy-bin: Updated for version 0.84.1. network/dropbox: Updated for version 266.4.3911. network/element-desktop-bin: Updated for version 1.12.26. network/element-desktop: Updated for version 1.12.26. network/filezilla: Updated for version 3.71.0. network/flvstreamer: Orphaned (unmaintained). network/franz: Updated for version 6.7.1. network/gofiche: Orphaned (unmaintained). network/grafana: Updated for version 13.2.0. network/helium-browser: Updated for version 0.15.5.1 network/kubectl-bin: Updated for version 1.36.4. network/kubectl: update to 1.36.4 network/librespeed-cli: Updated for version 1.0.14 network/librewolf: Updated for version 153.0.4_1 network/metasploit-framework-bin: Updated for version 6.5.3. network/microsoft-edge: Updated for version 151.0.4129.93. network/mullvad-browser: Updated for version 15.0.20 network/mullvadvpn-app: Updated for version 2026.4. network/nweb: New maintainer. network/oinkmaster: Orphaned (unmaintained). network/opera: Updated for version 134.0.5954.56 network/persepolis: Orphaned (unmaintained). network/phppgadmin: Updated for version 7.14.8 network/pidgin-toobars: Orphaned (unmaintained). network/putty: Updated for version 0.85. network/pyNeighborhood: Orphaned (unmaintained). network/signal-desktop-legacy: Removed. network/signal-desktop: Reverted back to 8.1.0 and update README. network/smstools3: Orphaned (unmaintained). network/speedometer: Change to python3-urwid. network/tailscale: update to 1.102.3 network/toot: Change to python3-urwid. network/tor-browser: Updated for version 15.0.20. network/urlscan: Updated for version 1.1.2. network/vdirsyncer: Updated for version 0.20.0. network/vivaldi: Updated for version 8.1.4087.70. network/waterfox: Updated for version 6.7.0 network/webex: Updated for version 46.8.0.35631 network/wifi-radar: Updated upstream details network/zen-browser: Updated for version 1.21.14b office/aiksaurus: Orphaned (unmaintained). office/gcal: Orphaned (unmaintained). office/jpilot: Require pilot-link-opt. office/krop: Fix doinst.sh (icon cache). office/ledger-live: Updated for version 4.17.0 office/msee: Orphaned office/mytetra: Orphaned (unmaintained). office/pdfshuffler: Removed at maintainer's request. office/qownnotes: Updated for version 26.8.6. office/tasksh: Fix documentation directory + new maintainer office/texstudio: Updated for version 4.9.7 office/vit: Change to python3-urwid. office/wps-office-dicts: Updated for version 26.8.0.3 office/xpad: New maintainer perl/perl-Algorithm-Combinatorics: Orphaned (unmaintained). perl/perl-Algorithm-Loops: Orphaned (unmaintained). perl/perl-CPAN-Perl-Releases: Updated for version 5.20260820. perl/perl-Class-Std-Fast: Added (Fast implementation of Class::Std). perl/perl-CryptX: Updated for version 0.091. perl/perl-Cstools: Orphaned (unmaintained). perl/perl-Data-Float: Added (Details of floating point data). perl/perl-HTTP-Lite: Added (Lightweight HTTP implementation). perl/perl-IO-CaptureOutput: Orphaned (unmaintained). perl/perl-IO-Interface: Orphaned (unmaintained). perl/perl-Log-Log4perl: Updated for version 1.58 perl/perl-Math-Prime-Util-GMP: Orphaned (unmaintained). perl/perl-Math-Prime-Util: Orphaned (unmaintained). perl/perl-Mojo-SQL: Added (Mojo::SQL for perl). perl/perl-Mojolicious: Updated for version 9.49. perl/perl-Sidef: Orphaned (unmaintained). perl/perl-Unicode-Map: Orphaned (unmaintained). perl/perl-trayicon: Orphaned (unmaintained). python/PyPy3: updated for version 7.3.23 python/PyPy: updated for version 7.3.23 python/css-parser: New maintainer. python/cssutils: Orphaned (unmaintained). python/drawille: Use canonical pypi URL. python/dukpy: Orphaned (unmaintained). python/feedparser: Reverted to version 6.0.12 python/filechunkio: Orphaned (unmaintained). python/gst0-python: Orphaned (unmaintained). python/html5-parser: Orphaned (unmaintained). python/mechanize: New maintainer. python/pydf: Orphaned (unmaintained). python/pymysql: Orphaned (unmaintained). python/pypoppler: Orphaned (unmaintained). python/pypy3: updated for version 7.3.23 python/pypy: updated for version 7.3.23 python/python-libnacl: Orphaned (unmaintained). python/python-musicbrainz2: Orphaned (unmaintained). python/python-mysql-replication: Orphaned (unmaintained). python/python-sh: Orphaned (unmaintained). python/python-urwid_readline: Orphaned (unmaintained). python/python-urwid_readline: Updated for version 0.15.1. python/python2-demjson: Orphaned (unmaintained). python/python2-distutils-extra: Orphaned (unmaintained). python/python2-elementtree: Orphaned (unmaintained). python/python2-keyczar: Orphaned (unmaintained). python/python2-morbid: Orphaned (unmaintained). python/python2-nuitka: Updated for version 4.2 python/python2-stomper: Orphaned (unmaintained). python/python2-uuid: Orphaned (unmaintained). python/python3-aiostream: Updated for version 0.7.1. python/python3-brotlicffi: Updated for version 1.2.0.2. python/python3-distutils-extra: New maintainer. python/python3-falcon: updated for version 4.3.1 python/python3-holidays: Added (Python library). python/python3-knowit: Version bump to 0.6.1 python/python3-korean-lunar-calendar: Added (Python module). python/python3-nuitka: Updated for version 4.2 python/python3-persistent: updated for version 6.7 python/python3-pypdf: Updated for version 6.16.1 python/python3-trakit: Version bump to 0.3.0 python/python3-typing-extensions: Version bump to 4.16.0 python/python3-unearth: Version bump to 0.18.3 python/rope: Orphaned (unmaintained). python/s3cmd: Orphaned (unmaintained). python/unrardll: Orphaned (unmaintained). python/uv-bin: Updated for version 0.12.5. ruby/pastel: Orphaned ruby/tty-color: Orphaned ruby/tty-cursor: Orphaned ruby/tty-reader: Orphaned ruby/tty-screen: Orphaned system/FreeFileSync: Moved src to sourceforge.net system/IoskeleyMono: Updated for version 2.1.0 system/cpulimit: Orphaned (unmaintained). system/dfm: Patched for SIXEL preview system/diskscan: Orphaned (unmaintained). system/dosbox-x: Updated for version 2026.08.02 system/dosemu: Orphaned (unmaintained). system/dust: Updated for version 1.2.5. system/fantasque-sans-mono: New maintainer system/fzf: Updated for version 0.74.3. system/imwheel: Orphaned (unmaintained). system/ink: Orphaned (unmaintained). system/intel-microcode: Updated for version 20260812 system/kopia: Added (Backup system). system/lightdm: Update for 1.33.1 (which fixes user switching) system/limine: Updated for version 12.6.0 system/lomoco: Orphaned (unmaintained). system/nnn: Updated for version 5.3 + new maintainer system/nvidia-legacy390-driver: Updated script. system/nvidia-legacy390-kernel: Updated script. system/partclone: Updated for version 0.3.48 system/pcp: Fix uid/gid conflict with sickchill. system/pkg: Updated for version v0.12.0. system/powernowd: Orphaned (unmaintained). system/procs: Fix permission. system/procs: update to 0.14.12 system/pv: Updated for version 1.11.0 system/python2-urwid: Added (Python library). system/python3-urwid: Added (Python library). system/python3-urwid: Update dependencies. system/readpe: Updated for version 20260708_967ab57 system/redis-py: Updated for version 8.1.0 system/regionset: Orphaned (unmaintained). system/s-tui: Change to python3-urwid. system/sbo-maintainer-tools: Updated for version 0.9.7. system/sbozyp: Updated for version 1.9.0 system/sleuthkit: Updated for version 4.15.0. system/swtpm: Updated for version 0.10.2. system/sysdig: Orphaned (unmaintained). system/upass: Orphaned (unmaintained). system/upass: REQUIRES =~ s,python-urwid,python3-urwid. system/uw-ttyp0: update to readme and slackbuild comment system/xrdp: Version bump to 0.10.6.1 system/yq: Updated for version 4.53.6. system/zoxide: Updated for version 0.10.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 urchlay at slackware.uk Sat Aug 22 07:27:18 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 22 Aug 2026 03:27:18 -0400 (EDT) Subject: [Slackbuilds-users] Updates - 20260822.1 In-Reply-To: <20260822135959.75d1d6ee@home.slackie.org> References: <20260822135959.75d1d6ee@home.slackie.org> Message-ID: <8e4a37d1-36b9-56ba-e147-b04bb7bc70e6@slackware.uk> On Sat, 22 Aug 2026, Willy Sudiarto Raharjo wrote: > Maintainers, please make sure you test all the scripts you submitted on > Slackware 15.0 machines, either in bare metals or inside a VM or chroot > environment to make sure it works for Slackware 15.0. Addendum: by "15.0", we mean: 1. 15.0 (NOT -current) 2. with all patches applied from patches/ (e.g. via "slackpkg upgrade-all") 3. *WITHOUT* anything from testing/ In particular, this means you CAN'T use the new glibc, binutils, gcc[*], etc from testing, when you're testing your scripts for 15.0 compliance. If you're not already using sbo-maintainer-tools to check your builds and built packages, I strongly recommend that you start using it. In particular, sbopkglint now (as of last week) checks for bad glibc requirements and emits an error. We run sbolint and sbopkglint on all submissions (including ones made via PR/MR), and anything that fails the checks will be rejected. It's possible to convince us that your build should be accepted (e.g. that the checks are too strict), but that will be considered on a case-by-case basis, and will require human interaction (you, the maintainer, are going to have to explain and justify it to the admins). It's not as scary as it sounds, we don't bite... [*] If you really do need a newer gcc, you can use REQUIRES="gcc14" (since we have that in our repo already). Don't do this lightly though: please try to find a way to patch the code to compile on 15.0's stock gcc (11.2.0) or clang (13.0.0), and only resort to gcc14 if it's *really* required. It should be the last resort, not the first thing you try. From fernando.lopezjr at gmail.com Sat Aug 22 10:05:59 2026 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 22 Aug 2026 04:05:59 -0600 Subject: [Slackbuilds-users] ngspice bad download URL. Message-ID: ngspice bad download URL. -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alik at ejik.org Sat Aug 22 10:25:25 2026 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 22 Aug 2026 13:25:25 +0300 Subject: [Slackbuilds-users] Updates - 20260822.1 In-Reply-To: <20260822135959.75d1d6ee@home.slackie.org> References: <20260822135959.75d1d6ee@home.slackie.org> Message-ID: > development/android-tools: Version bump to 37.0.0 It yields: --------------- CMake Error at vendor/boringssl/CMakeLists.txt:15 (cmake_minimum_required): CMake 3.22 or higher is required. You are running version 3.21.4 --------------- With cmake-opt, the build succeeds. Best regards, Alexander From willysr at slackbuilds.org Sat Aug 22 14:15:32 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 22 Aug 2026 21:15:32 +0700 Subject: [Slackbuilds-users] ngspice bad download URL. In-Reply-To: References: Message-ID: <20260822211532.0cf1a15f@home.slackie.org> >ngspice bad download URL. Fixed on my branch and also in SBo server thanks -- 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 Aug 22 14:17:24 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 22 Aug 2026 21:17:24 +0700 Subject: [Slackbuilds-users] Updates - 20260822.1 In-Reply-To: References: <20260822135959.75d1d6ee@home.slackie.org> Message-ID: <20260822211724.7e3eb405@home.slackie.org> >> development/android-tools: Version bump to 37.0.0 > >It yields: > >--------------- >CMake Error at vendor/boringssl/CMakeLists.txt:15 (cmake_minimum_required): > CMake 3.22 or higher is required. You are running version 3.21.4 >--------------- > >With cmake-opt, the build succeeds. Jeremy did you test this on -current ? -- 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 Aug 22 14:18:03 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 22 Aug 2026 21:18:03 +0700 Subject: [Slackbuilds-users] ngspice bad download URL. In-Reply-To: References: Message-ID: <20260822211803.7c17cdf1@home.slackie.org> >ngspice bad download URL. Fixed on my branch and also in SBo server thank -- 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 jebrhansen+SBo at gmail.com Sat Aug 22 14:25:38 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 22 Aug 2026 07:25:38 -0700 Subject: [Slackbuilds-users] Updates - 20260822.1 In-Reply-To: References: <20260822135959.75d1d6ee@home.slackie.org> Message-ID: On Sat, Aug 22, 2026, 3:32?AM Alexander Verbovetsky wrote: > > development/android-tools: Version bump to 37.0.0 > > It yields: > > --------------- > CMake Error at vendor/boringssl/CMakeLists.txt:15 (cmake_minimum_required): > CMake 3.22 or higher is required. You are running version 3.21.4 > --------------- > > With cmake-opt, the build succeeds. > Shoot, I must've missed that. I'll get it corrected for next week. Thanks! Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From emmanueln at gmail.com Sat Aug 22 15:34:19 2026 From: emmanueln at gmail.com (Emmanuel) Date: Sat, 22 Aug 2026 12:34:19 -0300 Subject: [Slackbuilds-users] Vinyl cache new package Message-ID: Hi, I just submitted a new vinyl cache package to replace varnish. Could you please remove the varnish package from the repository Best Regards. -- ***************** Emmanuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From khronosschoty at posteo.org Sat Aug 22 16:21:37 2026 From: khronosschoty at posteo.org (Vasily Sora) Date: Sat, 22 Aug 2026 16:21:37 +0000 Subject: [Slackbuilds-users] mupen64plus SlackBuild Message-ID: Greetings, I noticed after successfully compiling, installing and using the mupen64plus package produced by your SlackBuild that mupen64plus complains that it can not find its corelib in /usr/local/lib. The reason being is that, mupen64plus was compiled with its defaults, and then installed with 'PREFIX=/usr LIBDIR=/usr/lib${LIBDIRSUFFIX} MANDIR=/usr/man DESTDIR=$PKG'. The fix, is to compile and install with the same parameters. (see the attached diff). -------------- next part -------------- A non-text attachment was scrubbed... Name: mupen64plus.SlackBuild.diff Type: text/x-patch Size: 633 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x0423ECCC94BFCD0B.asc Type: application/pgp-keys Size: 3988 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From milgram at cgpp.com Sun Aug 23 14:04:56 2026 From: milgram at cgpp.com (J. Milgram) Date: Sun, 23 Aug 2026 10:04:56 -0400 Subject: [Slackbuilds-users] Updates - 20260822.1 In-Reply-To: <20260822135959.75d1d6ee@home.slackie.org> References: <20260822135959.75d1d6ee@home.slackie.org> Message-ID: <6e5feb23-9196-48e7-9039-3ba31eae8a55@cgpp.com> pilot-link should be removed. (1) steps on Slack 15 package of same name (2) has been superseded by the new pilot-link-opt SlackBuild. I see it still on slackbuilds.org: https://slackbuilds.org/repository/15.0/network/pilot-link/ thx JM Sat Aug 22 06:40:58 UTC 2026 -- ===== milgram at cgpp.com 301-257-7069 From willysr at slackbuilds.org Sun Aug 23 14:26:25 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 23 Aug 2026 21:26:25 +0700 Subject: [Slackbuilds-users] Updates - 20260822.1 In-Reply-To: <6e5feb23-9196-48e7-9039-3ba31eae8a55@cgpp.com> References: <20260822135959.75d1d6ee@home.slackie.org> <6e5feb23-9196-48e7-9039-3ba31eae8a55@cgpp.com> Message-ID: <20260823212625.291d061f@home.slackie.org> >pilot-link should be removed. (1) steps on Slack 15 package of same name >(2) has been superseded by the new pilot-link-opt SlackBuild. > >I see it still on slackbuilds.org: > >https://slackbuilds.org/repository/15.0/network/pilot-link/ Thanks for reminder i want to make sure everything in place before removing it it's now removed in 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 milgram at cgpp.com Sun Aug 23 14:28:49 2026 From: milgram at cgpp.com (J. Milgram) Date: Sun, 23 Aug 2026 10:28:49 -0400 Subject: [Slackbuilds-users] Updates - 20260822.1 In-Reply-To: <20260823212625.291d061f@home.slackie.org> References: <20260822135959.75d1d6ee@home.slackie.org> <6e5feb23-9196-48e7-9039-3ba31eae8a55@cgpp.com> <20260823212625.291d061f@home.slackie.org> Message-ID: Thanks.? I do believe the dust is settling :) r/ JM On 8/23/26 10:26, Willy Sudiarto Raharjo wrote: >> pilot-link should be removed. (1) steps on Slack 15 package of same name >> (2) has been superseded by the new pilot-link-opt SlackBuild. >> >> I see it still on slackbuilds.org: >> >> https://slackbuilds.org/repository/15.0/network/pilot-link/ > > Thanks for reminder > i want to make sure everything in place before removing it > it's now removed in my branch > > -- > Willy Sudiarto Raharjo -- ===== milgram at cgpp.com 301-257-7069 From urchlay at slackware.uk Mon Aug 24 07:59:16 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 24 Aug 2026 03:59:16 -0400 (EDT) Subject: [Slackbuilds-users] Alan Aversa (aka Caterino Tommaso, T.O.P.) Message-ID: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> This is unpleasant, but the SBo admin team has come to a decision about Alan Aversa (also known as Caterino Tommaso, T.O.P.). We've tried to reach this maintainer via email several times over the past few weeks, including posting to the mailing list. We have also tried sending messages on LQ. This person has been breaking two of the rules: - Submitting updates for other peoples' builds without permission. - Not basing his updates on our changes, when we have to change something in one of his builds. E.g. anki does not require Markdown, and we removed it from REQUIRES, but every time he updates anki, he re-adds Markdown to REQUIRES. Since this has been going on for a while now, and we can't reach him to explain why this isn't allowed, we're giving up. If anyone would like to take over any of these builds, please send an update (submission form or PR/MR) setting yourself as maintainer, and whatever other changes you'd like to make. Most of them need version updates. Anything that hasn't been taken by the next weekly update will be orphaned. We don't like to do this, but the bogus updates have caused us headaches and extra work. We're done. The lists are at these 2 URLs: https://slackbuilds.org/advsearch.php?stype=maint&q=Alan%20Aversa https://slackbuilds.org/advsearch.php?stype=maint&q=Caterino%20Tommaso ...or here: CubicSDR SDRPlay SoapyRemote SoapySDR SoapySDRPlay WolframEngine anki bsddb3 btrbk cbmc contextlib2 cryptominisat diffuse google-images-download gramps ibus-typing-booster img2pdf internetarchive jpdfbookmarks jupyter-ipywidgets jupyter-widgetsnbextension kissat krop liquid-dsp louvain-community plover purple-gowhatsapp qdirstat retroshare scantailor-advanced schema simplex-desktop waydroid From bgrundy at linuxleo.com Mon Aug 24 16:59:36 2026 From: bgrundy at linuxleo.com (Barry J. Grundy) Date: Mon, 24 Aug 2026 12:59:36 -0400 Subject: [Slackbuilds-users] libregf - force fuse2? Message-ID: Good Morning, I recently submitted an update to libregf. It builds fine on both current and 15.0, but the regfmount command is broken. My apologies. It wasn't until I tried a local mount that I found the issue. The strange thing is that when I build the version that's currently on SBo, it is also broken, though I used it often in the past. The issue is that regfmount is fuse based and it's being compiled with fuse3. Is there a way in the slackbuild to force it to use fuse (2) instead? I can't see an option for that in ./configure --help. In the meantime, can libregf be removed from the upcoming update until I get this sorted? Again, my apologies. Barry Grundy bgrundy at linuxleo.com From bgrundy at linuxleo.com Mon Aug 24 20:54:04 2026 From: bgrundy at linuxleo.com (Barry J. Grundy) Date: Mon, 24 Aug 2026 16:54:04 -0400 Subject: [Slackbuilds-users] libregf - force fuse2? In-Reply-To: References: Message-ID: On 26/08/24 12:59PM, Barry J. Grundy wrote: > Good Morning, > > I recently submitted an update to libregf. It builds fine on both > current and 15.0, but the regfmount command is broken. My apologies. It > wasn't until I tried a local mount that I found the issue. The strange > thing is that when I build the version that's currently on SBo, it is also > broken, though I used it often in the past. > > The issue is that regfmount is fuse based and it's being compiled with > fuse3. Is there a way in the slackbuild to force it to use fuse (2) > instead? I can't see an option for that in ./configure --help. > > In the meantime, can libregf be removed from the upcoming update until I > get this sorted? > > Again, my apologies. > > Barry Grundy > bgrundy at linuxleo.com Responding to my own message here... Belay the above. I tested version 20260526 and it works. I was avoiding that version because I'm usually required to track the "release" versions in the GIFT PPA (incident response tools). I'll submit libregf-20260526 and be done with it. From urchlay at slackware.uk Mon Aug 24 21:29:02 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 24 Aug 2026 17:29:02 -0400 (EDT) Subject: [Slackbuilds-users] libregf - force fuse2? In-Reply-To: References: Message-ID: <60485b4d-e76d-114f-71f1-9ff89c75c335@slackware.uk> On Mon, 24 Aug 2026, Barry J. Grundy wrote: > The issue is that regfmount is fuse based and it's being compiled with > fuse3. Is there a way in the slackbuild to force it to use fuse (2) > instead? I can't see an option for that in ./configure --help. I didn't see a way to do it without patching, so I patched it. Patch is attached to this email (gzipped). Put the un-gzipped file in the SlackBuild dir, then in the script, before the configure command, add: patch -p1 < $CWD/libregf-remove-fuse3.diff autoreconf -if After running the build: $ ldd /tmp/SBo/package-libregf/usr/bin/regfmount | grep fuse libfuse.so.2 => /lib64/libfuse.so.2 (0x00007f1e67872000) I have no way to test it, since it's for Windows registry files and I don't run Windows. While messing with this, I noticed there's a newer release of libregf on the github releases page. https://github.com/libyal/libregf/releases shows a 20260526 release. I tried building that, with the above patch, and it builds fine. So you might want to update to 20260526 insteaad of 20240421... unless you already tried it and found a showstopper bug in 20260526, of course. If you go with the older one, it's a good idea to put a comment in the SlackBuild explaining why (so maybe you don't get emailed by people "helping" you by pointing out that there's a new release). Also, whichever version you decide on, I recommend using the github releases/ URL for the source, rather than the linuxleo.com ones. These are: https://github.com/libyal/libregf/releases/download/20240421/libregf-alpha-20240421.tar.gz https://github.com/libyal/libregf/releases/download/20260526/libregf-alpha-20260526.tar.gz > In the meantime, can libregf be removed from the upcoming update until I > get this sorted? It's already in ready/ so yes, but it'll have to wait for Willy to be awake (it's the middle of the night where he is). -------------- next part -------------- A non-text attachment was scrubbed... Name: libregf-remove-fuse3.diff.gz Type: application/octet-stream Size: 526 bytes Desc: URL: From urchlay at slackware.uk Mon Aug 24 21:32:25 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 24 Aug 2026 17:32:25 -0400 (EDT) Subject: [Slackbuilds-users] libregf - force fuse2? In-Reply-To: References: Message-ID: <56554df2-ca10-2757-c33-2f1795771938@slackware.uk> On Mon, 24 Aug 2026, Barry J. Grundy wrote: > Responding to my own message here... Belay the above. I tested version > 20260526 and it works. I was avoiding that version because I'm usually > required to track the "release" versions in the GIFT PPA (incident response > tools). > > I'll submit libregf-20260526 and be done with it. Well damn. If I were better at multitasking, I might have seen this email while working on the patch for 20240421 :) The patch from the previous email will still apply to 20260526, if you find out you need it. But it sounds like it works without patching, so you shouldnt't need it. From lists at osh.id.au Tue Aug 25 06:54:08 2026 From: lists at osh.id.au (David O'Shaughnessy) Date: Tue, 25 Aug 2026 14:54:08 +0800 Subject: [Slackbuilds-users] Alan Aversa (aka Caterino Tommaso, T.O.P.) In-Reply-To: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> References: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> Message-ID: On Mon, 24 Aug 2026, at 3:59 PM, B. Watson wrote: > - Submitting updates for other peoples' builds without permission. Given the nature of the form at https://slackbuilds.org/submit/ (no authentication or submission email verification), can't the practice of submitting updates without permission still continue though? From urchlay at slackware.uk Tue Aug 25 07:20:41 2026 From: urchlay at slackware.uk (B. Watson) Date: Tue, 25 Aug 2026 03:20:41 -0400 (EDT) Subject: [Slackbuilds-users] Alan Aversa (aka Caterino Tommaso, T.O.P.) In-Reply-To: References: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> Message-ID: On Tue, 25 Aug 2026, David O'Shaughnessy wrote: > On Mon, 24 Aug 2026, at 3:59 PM, B. Watson wrote: >> - Submitting updates for other peoples' builds without permission. > > Given the nature of the form at https://slackbuilds.org/submit/ (no authentication or submission email verification) Well, there's no authentication, but there is submission email verification: the form verifies that the email address exists, and can be reached via SMTP (does a "RCPT TO"). You're right in that it doesn't verify that the user's email address matches the .info file's maintainer email: there's no rule that says you have to use the same email address for both. This is a feature... Example: My primary email address is on a domain (slackware.uk) that does greylisting. On the rare occasions I use the submit form, I use a different email address (which doesn't do greylisting), to avoid the greylist delay of 5 minutes. This means the email in my .info file doesn't match the email I entered into the submission form. And I know I'm not the only one who does this regularly. > can't the practice of submitting updates without permission still continue though? Yes, it can. Which is why, when it happens, we contact the person who did it, explain the situation, and ask them nicely to stop. When it's happened in the past, the updaters have responded positively for the most part. "Sorry, I didn't know it wasn't allowed", etc. The only reason Aversa/Caterino is getting singled out is that he hasn't responded to our attempts to contact him, for over a month now (and actually, it goes back further than that, we just didn't start documenting it until a month ago). In the past few days, I've given some thought to the idea of having all maintainers create user accounts, and log in before they're allowed to submit a build... and prevent anyone from updating anyone else's build unless they have permission (the one giving permission would log in and have some kind of UI for giving permission). Having maintainer user accounts and requiring browser logins would be a pain in everyone's ass. Maintainers would have extra hoops to jump through, and someone from the SBo admin team (probably me) would have to write all the code (in PHP, SQL, and maybe JavaScript). Plus, this still wouldn't stop unauthorized updates: users can update builds via PR/MR on github, gitlab, and codeberg. I don't think we can do anything there beyond what we're already doing: look at the user who sent the update, see if it's the same as the maintainer. From urchlay at slackware.uk Tue Aug 25 10:20:25 2026 From: urchlay at slackware.uk (B. Watson) Date: Tue, 25 Aug 2026 06:20:25 -0400 (EDT) Subject: [Slackbuilds-users] btrbk needs a maintainer Message-ID: <43392016-f7af-be1f-3d1d-67bf0e89824@slackware.uk> Any btrfs users here? btrbk looks useful and maybe important, and it needs a maintainer. Any takers? From nick at smallbone.se Tue Aug 25 10:31:38 2026 From: nick at smallbone.se (Nick Smallbone) Date: Tue, 25 Aug 2026 12:31:38 +0200 Subject: [Slackbuilds-users] btrbk needs a maintainer In-Reply-To: <43392016-f7af-be1f-3d1d-67bf0e89824@slackware.uk> References: <43392016-f7af-be1f-3d1d-67bf0e89824@slackware.uk> Message-ID: I can take it. I can also take (if they are still orphaned) cbmc, kissat, cryptominisat, and shotcut. Nick On Tue, 25 Aug 2026, at 12:20 PM, B. Watson wrote: > Any btrfs users here? btrbk looks useful and maybe important, and it > needs a maintainer. > > Any takers? > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ From urchlay at slackware.uk Tue Aug 25 10:54:48 2026 From: urchlay at slackware.uk (B. Watson) Date: Tue, 25 Aug 2026 06:54:48 -0400 (EDT) Subject: [Slackbuilds-users] btrbk needs a maintainer In-Reply-To: References: <43392016-f7af-be1f-3d1d-67bf0e89824@slackware.uk> Message-ID: On Tue, 25 Aug 2026, Nick Smallbone wrote: > I can take it. I can also take (if they are still orphaned) cbmc, kissat, cryptominisat, and shotcut. Thanks! They're yours. Do you want me to update the .info files, or wait for your updates? From glenn_e_becker at protonmail.com Tue Aug 25 11:01:12 2026 From: glenn_e_becker at protonmail.com (glenn_e_becker) Date: Tue, 25 Aug 2026 11:01:12 +0000 Subject: [Slackbuilds-users] Alan Aversa (aka Caterino Tommaso, T.O.P.) In-Reply-To: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> References: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> Message-ID: I can take anki, since I've already done a 'backtracking' to an earlier version, and I do use it. Glenn Becker ===================================== Rain comes down through the alders, Its low conducive voices Mutter about let-downs and erosions And yet each drop recalls The diamond absolutes. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- Seamus Heaney Sent from Proton Mail for Android. -------- Original Message -------- On Monday, 08/24/26 at 04:04 B. Watson wrote: This is unpleasant, but the SBo admin team has come to a decision about Alan Aversa (also known as Caterino Tommaso, T.O.P.). We've tried to reach this maintainer via email several times over the past few weeks, including posting to the mailing list. We have also tried sending messages on LQ. This person has been breaking two of the rules: - Submitting updates for other peoples' builds without permission. - Not basing his updates on our changes, when we have to change something in one of his builds. E.g. anki does not require Markdown, and we removed it from REQUIRES, but every time he updates anki, he re-adds Markdown to REQUIRES. Since this has been going on for a while now, and we can't reach him to explain why this isn't allowed, we're giving up. If anyone would like to take over any of these builds, please send an update (submission form or PR/MR) setting yourself as maintainer, and whatever other changes you'd like to make. Most of them need version updates. Anything that hasn't been taken by the next weekly update will be orphaned. We don't like to do this, but the bogus updates have caused us headaches and extra work. We're done. The lists are at these 2 URLs: https://slackbuilds.org/advsearch.php?stype=maint&q=Alan%20Aversa https://slackbuilds.org/advsearch.php?stype=maint&q=Caterino%20Tommaso ...or here: CubicSDR SDRPlay SoapyRemote SoapySDR SoapySDRPlay WolframEngine anki bsddb3 btrbk cbmc contextlib2 cryptominisat diffuse google-images-download gramps ibus-typing-booster img2pdf internetarchive jpdfbookmarks jupyter-ipywidgets jupyter-widgetsnbextension kissat krop liquid-dsp louvain-community plover purple-gowhatsapp qdirstat retroshare scantailor-advanced schema simplex-desktop waydroid _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/ From urchlay at slackware.uk Tue Aug 25 11:03:44 2026 From: urchlay at slackware.uk (B. Watson) Date: Tue, 25 Aug 2026 07:03:44 -0400 (EDT) Subject: [Slackbuilds-users] Alan Aversa (aka Caterino Tommaso, T.O.P.) In-Reply-To: References: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> Message-ID: <7fae7d1c-cfde-efda-c8e3-6ef0e465159@slackware.uk> On Tue, 25 Aug 2026, glenn_e_becker via SlackBuilds-users wrote: > I can take anki, since I've already done a 'backtracking' to an earlier version, and I do use it. All yours. Want me to update .info, or you got it? If you don't think you'll have time to get your update in by this weekend's update, I should update the .info for you (it's how I keep track of all these takeovers). From chris.willing at linux.com Tue Aug 25 11:19:16 2026 From: chris.willing at linux.com (Christoph Willing) Date: Tue, 25 Aug 2026 21:19:16 +1000 Subject: [Slackbuilds-users] btrbk needs a maintainer In-Reply-To: References: <43392016-f7af-be1f-3d1d-67bf0e89824@slackware.uk> Message-ID: <5f64f3f4-40c4-4a48-929d-d82d6e15cca2@linux.com> On 25/8/26 20:54, B. Watson wrote: > > > On Tue, 25 Aug 2026, Nick Smallbone wrote: > >> I can take it. I can also take (if they are still orphaned) cbmc, >> kissat, cryptominisat, and shotcut. > multimedia/shotcut has already been claimed by Eugene Wissner chris From nick at smallbone.se Tue Aug 25 12:11:55 2026 From: nick at smallbone.se (Nick Smallbone) Date: Tue, 25 Aug 2026 14:11:55 +0200 Subject: [Slackbuilds-users] btrbk needs a maintainer In-Reply-To: References: <43392016-f7af-be1f-3d1d-67bf0e89824@slackware.uk> Message-ID: On Tue, 25 Aug 2026, at 12:54 PM, B. Watson wrote: > On Tue, 25 Aug 2026, Nick Smallbone wrote: > >> I can take it. I can also take (if they are still orphaned) cbmc, kissat, cryptominisat, and shotcut. > > Thanks! > > They're yours. Do you want me to update the .info files, or wait for > your updates? I'll try and bring the packages up to date this week, so it's fine with me if you wait. Nick From willysr at slackbuilds.org Sat Aug 29 00:39:01 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 29 Aug 2026 07:39:01 +0700 Subject: [Slackbuilds-users] Updates - 20260829.1 Message-ID: <20260829073901.3e1a367a@home.slackie.org> Sat Aug 29 00:29:05 UTC 2026 academic/R: Fix pkgconfig entry academic/arpack: Update HOMEPAGE, DOWNLOADS. academic/cryptominisat: Updated for version 5.14.7 + new maintainer academic/grpn: Fix slack-desc. academic/kissat: Updated for version 4.0.4 + new maintainer. academic/ngspice: Update DOWNLOAD. academic/siril: New maintainer academic/zotero: Updated for version 10.0.1 audio/gogglesmm: Updated for version 1.3.1 + new maintainer audio/rhythmbox: Updated for version 3.4.8 + new maintainer desktop/anki: New maintainer desktop/emwm: Updated for version 2.1 desktop/notification-daemon: Updated for version 3.20.0 desktop/nwg-displays: Updated for version 0.4.4. desktop/todoman: Use python3-urwid. desktop/xpra: Fix initscript location development/Kiro: Updated for version 1.0.337. development/Kiro: Updated for version 1.0.395. development/LLgen: Fix slack-desc. development/abseil-cpp: Version bump to 20260817.0 development/android-tools: Add missed cmake-opt dependency development/antigravity-cli: Updated for version 1.1.20 development/antigravity: Updated for version 2.10.0 development/aws-cdk: Updated for version 2.1139.0. development/bun-bin: Updated for version 1.4.0 development/cbmc: Updated for version 6.11.0 + new maintainer. development/composer: Updated for version 2.10.3 development/d-tools: Updated for version 2.113.0 development/deno-bin:Updated for version 2.9.6 development/deno: Updated for version 2.9.6. development/diffuse: New maintainer development/dmd: Updated for version 2.113.0 development/eh: Added (Minimal Vi-like Editor). development/electron-bin: Updated for version 44.0.0 development/ghidra: Updated for version 12.1.3 development/git-lfs: Updated for version 3.8.0. development/gitlab-cli: Updated for version 1.115.0. development/gnu-apl: Updated for version 2.0 + new maintainer development/got: Updated REQUIRES development/jdk: Fix slack-desc. development/jdk: Updated for version 8u503. development/lua-language-server: Updated for version 3.19.1. development/mongodb-compass: Updated for version 1.49.15. development/nodejs24-bin: Updated for version 24.20.0 development/notepad++: Updated for version 8.9.8 development/php84: Updated for version 8.4.25 development/pnpm: Updated for version 11.24.0. development/rmlmmc: Fix slack-desc. development/rust-opt: Updated for version 1.98.0. development/sbt: Reverted to version 1.11.4 development/terraform: Updated for version 1.16.0 development/typescript: Updated for version 7.0.2 development/velero-bin: Added (Backup and Restore Tool). development/velero: Updated for version 1.18.2 development/vscode-bin: Updated for version 1.135.0. development/vstudio: Updated for version 17.5.4 development/xmake: Updated for version 3.1.1. development/zulu-openjdk11: Updated for version 11.0.32.1. development/zulu-openjdk17: Updated for version 17.0.20.1. development/zulu-openjdk21: Updated for version 21.0.12.1. development/zulu-openjdk25: Updated for version 25.0.4.1. development/zulu-openjdk8: Updated for version 8.0.54. games/mame: Updated for version 0.289. games/mupen64plus: Fix corelib path. games/solarus: Updated for version 2.1.3 games/yetris: Fix slack-desc. graphics/gimp-feca_hdr-plugin: Fix slack-desc. graphics/img2pdf: New maintainer graphics/qcad: Updated for version 3.32.9.0 + new maintainer graphics/renderdoc: Updated for version 1.14 graphics/vips: Updated for version 8.18.6. ham/libosmocore: Updated for version 1.14.2. haskell/haskell-idna: Fix slack-desc. libraries/Ipopt: Updated for version 3.14.20 libraries/backports-ssl-match-hostname: Fix slack-desc. libraries/dragonbox: Added (C++ dragonbox implementation). libraries/freealut: Fix slack-desc. libraries/libaosd: Updated for 0.2.7+20141127_8a0d0d7, new maint. libraries/libkqueue: Fix slack-desc. libraries/libqtpas: Updated for version 4.8 libraries/libregf: Updated for version 20240421. libraries/libscca: Updated for version 20250915. libraries/libscrypt: Fix slack-desc. libraries/libslirp: Updated for version 4.9.4 libraries/log4cplus: Updated for version 2.2.0.1. libraries/logilinux: Reverted to version 20260516_d621d56 libraries/logilinux: Update permission. libraries/microsoft-gsl: Updated for version 5.0.0. libraries/nextaw: Fix slack-desc. libraries/pilot-link-opt: Update script. libraries/pysendfile: Fix slack-desc. libraries/pytorch: Fix build with latest openssl patch. libraries/simdjson: Updated for version 4.6.9 libraries/simdutf: Updated for version 9.1.0 libraries/utfcpp: Updated for version 4.2.0. misc/es40: Updated for version 0.82 misc/gramps: Orphaned (unmaintained). misc/ollama: Updated for version 0.33.1. multimedia/devedeng: Updated for version 4.20.0 multimedia/dvblast: Updated for version 3.5 multimedia/shotcut: New maintainer. multimedia/strawberry: Updated for version 1.2.28. network/3proxy: Updated for version 1.0.0. network/amneziawg-go: Updated for version 3.1.20260828. network/amneziawg-kernel: Updated for version 3.1.20260828. network/bitcoin-knots: Updated for version 29.4.20260508. network/brave-browser: Updated for version 1.94.117 network/brave-origin: Updated for version 1.94.117 network/bsflite: Fix slack-desc. network/catgirl: update deps and email. network/exim: Updated for version 4.100. network/filezilla: Updated for version 3.71.1. network/ftp-cloudfs: Fix slack-desc. network/helium-browser: Updated for version 0.15.7.1 network/kea: Updated for version 3.2.0. network/librewolf: Updated for version 154.0_2 network/mod_evasive: Patched to fix mailer usage network/opera: Updated for version 135.0.5973.41 network/pidgin-otr: Fix slack-desc. network/pilot-link: Removed (use pilot-link-opt). network/pounce: Updated REQUIRES network/purple-gowhatsapp: Orphaned (unmaintained). network/putty: Update MD5SUM. network/putty: Use permanent link. network/retroshare: Orphaned (unmaintained). network/rspamd: Updated for version 4.1.5 network/rssh: New maintainer network/sftp-cloudfs: Fix slack-desc. network/shadowsocks-rust: Updated for version 1.25.0. network/telegram: Updated for version 7.1.1. network/telegram: Updated for version 7.1.3. network/varnish: Removed - replaced by network/vinyl network/vblade: Fix slack-desc. network/vinyl: Added (caching HTTP reverse proxy). network/vivaldi: Updated for version 8.1.4087.75. network/waterfox: Updated for version 6.7.1.1 network/yt-dlp-bin: Updated for version 2026.08.19. network/zen-browser: Updated for version 1.21.15b office/Joplin: Updated for version 3.6.16. office/flowkeeper: Fix slack-desc. office/glow: Updated for version 3.0.0 office/krop: New maintainer office/ledger-live: Updated for version 4.17.1 office/plover: Orphaned (unmaintained). office/qownnotes: Updated for version 26.8.11. office/xpad: Updated for version 4.9.0 perl/MoarVM: Updated for version 2026.08 perl/nqp: Updated for version 2026.08 perl/perl-Danga-Socket: Fix slack-desc. perl/perl-File-Finder: Fix slack-desc. perl/perl-Meta-Requirements-Range: Update script. perl/perl-Net-IDN-Encode: Updated for version 2.502. perl/perl-Net-Pcap: Fix slack-desc. perl/perl-Text-Iconv: Fix slack-desc. perl/perl-XML-Filter-BufferText: Fix slack-desc. perl/rakudo: Updated for version 2026.08 python/apsw: New maintainer. python/bsddb3: Orphaned (unmaintained). python/contextlib2: Removed (no dependees, no maintainer). python/google-images-download: Orphaned (unmaintained). python/internetarchive: Updated for version 5.10.1, new maintainer. python/monotonic: Fix slack-desc. python/python3-entrypoints: Removed (no longer needed). python/python3-imagesize: Updated for version 2.0.1. python/python3-maturin: Updated for version 1.15.0. python/python3-monotonic: Fix slack-desc. python/python3-pypdf: Updated for version 6.16.2 python/schema: Removed (no dependees, no maintainer). python/uv-bin: Updated for version 0.12.7. python/wsgiref: Fix slack-desc. system/Iosevka-aile: Updated for version 34.8.1. system/Iosevka-core: update to 34.8.1 system/Iosevka-etoile: Updated for version 34.8.1. system/acopw-cli: Updated for version 1.0.1 system/brother-brscan4: Update script. system/brother-dcp8410-cups: Update script. system/brother-dcp8410-lpr: Update script. system/btrbk: Updated for version 0.32.7 + new maintainer. system/bulk_extractor: Updated for version 2.2.0. system/edk2-ovmf: Updated for version 202608. system/elasticsearch: Orphaned. system/fd: Updated for version 10.5.0. system/fonts-IoskeleyMono: Added (Ioskeleymono font). system/fonts-agave: Added (Programming Font). system/fonts-uw-ttyp0: Added (Screen Fonts). system/fzf-bin: Updated for version 0.74.3 system/hntool: Fix slack-desc. system/limine: Updated for version 12.6.1 system/mongo-tools: Updated for version 100.18.0. system/msitools: Fix slack-desc. system/openmpi4: Added (MPI-2 Implementation). system/openmpi: Updated for version 5.0.10 system/prometheus: Updated for version 3.14.0 system/python-urwid: Removed (Split into 2 packages). system/qdirstat: New maintainer system/rhash: Fix slack-desc. system/sarasa-gothic: Updated for version 1.0.41. system/snooze: Added (Cron Replacement). system/squashfuse: Updated for version 0.6.3. system/stress-ng: Updated for version 0.22.00 system/ttf-nerd-fonts-symbols: Updated for version 3.5.1 system/usermin: Updated for version 2.560. system/uw-ttyp0: Removed (renamed to fonts-uw-ttyp0). system/webmin: Updated for version 2.660. system/xosd: New maintainer, update for v2.2.15, xmms plugin. system/yepstat: Added (Terminal status display). system/zellij-bin: Updated for version 0.45.0. +--------------------------+ -- 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 Sat Aug 29 05:25:22 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 29 Aug 2026 01:25:22 -0400 (EDT) Subject: [Slackbuilds-users] nvidia-legacy340-driver and nvidia-legacy340-kernel on the chopping block Message-ID: <6662fa42-f1c6-f1af-a5e0-beca78dca3d@slackware.uk> Is anyone still using nvidia-legacy340-driver and nvidia-legacy340-kernel? They've both been orphaned for almost a year. If nobody wants to take them over, they will be removed soon. I'm not sure how old an NVidia GPU has to be to require this driver, but if you need it to support your hardware, *please* take over maintenance. From 414N at slacky.it Sat Aug 29 10:21:46 2026 From: 414N at slacky.it (414N) Date: Sat, 29 Aug 2026 12:21:46 +0200 Subject: [Slackbuilds-users] Alan Aversa (aka Caterino Tommaso, T.O.P.) In-Reply-To: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> References: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> Message-ID: Il 24/08/26 09:59, B. Watson ha scritto: > scantailor-advanced I'll gladly take it. I'll send a PR in the next few days on github -- Alan Alberghini SBo clone: https://github.com/414n/slackbuilds From tonus1 at free.fr Sat Aug 29 16:46:07 2026 From: tonus1 at free.fr (Tonus) Date: Sat, 29 Aug 2026 18:46:07 +0200 Subject: [Slackbuilds-users] Alan Aversa (aka Caterino Tommaso, T.O.P.) In-Reply-To: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> References: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> Message-ID: <87ecfgkh80.fsf@Baldr.vingolf.info> "B. Watson" writes: > bsddb3 > gramps Hi I could take these 2 since I use it. Nothing to do with it for now though, it's already the last gramps version for Python >= 3.9. -- Regards, Tonus. From urchlay at slackware.uk Sat Aug 29 21:15:56 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 29 Aug 2026 17:15:56 -0400 (EDT) Subject: [Slackbuilds-users] Alan Aversa (aka Caterino Tommaso, T.O.P.) In-Reply-To: <87ecfgkh80.fsf@Baldr.vingolf.info> References: <27c5b52-41af-d658-f6c6-1a5ec9f12c4@slackware.uk> <87ecfgkh80.fsf@Baldr.vingolf.info> Message-ID: <73d45c90-1a7c-2bc-9472-cac221e7e6cf@slackware.uk> On Sat, 29 Aug 2026, Tonus via SlackBuilds-users wrote: > "B. Watson" writes: >> bsddb3 >> gramps > > Hi > > I could take these 2 since I use it. Nothing to do with it for now though, it's > already the last gramps version for Python >= 3.9. bsddb3 and gramps are yours. Thanks. From belka at caraus.de Sun Aug 30 15:30:07 2026 From: belka at caraus.de (Eugen Wissner) Date: Sun, 30 Aug 2026 17:30:07 +0200 Subject: [Slackbuilds-users] btrbk needs a maintainer In-Reply-To: <5f64f3f4-40c4-4a48-929d-d82d6e15cca2@linux.com> References: <43392016-f7af-be1f-3d1d-67bf0e89824@slackware.uk> <5f64f3f4-40c4-4a48-929d-d82d6e15cca2@linux.com> Message-ID: Updating shotcut will take some time (if possible). I updated the script locally to work on current. But it requires Qt6 as far as I know. So I need first to make my Slackware stable VMs capable to build Qt6, check what else is needed and test it. On Tue Aug 25, 2026 at 1:19 PM CEST, Christoph Willing wrote: > On 25/8/26 20:54, B. Watson wrote: >> >> >> On Tue, 25 Aug 2026, Nick Smallbone wrote: >> >>> I can take it. I can also take (if they are still orphaned) cbmc, >>> kissat, cryptominisat, and shotcut. >> > > multimedia/shotcut has already been claimed by Eugene Wissner > > chris > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ From davidnchmelik at gmail.com Mon Aug 31 01:27:56 2026 From: davidnchmelik at gmail.com (David Chmelik) Date: Sun, 30 Aug 2026 18:27:56 -0700 Subject: [Slackbuilds-users] lirc breaks udev Message-ID: <9316548a-112e-454e-aba6-9168fa69dbdf@gmail.com> The lirc.SlackBuild doesn't do the standard thing to ask to install its group, but installs a file expecting a group, which apparently breaks udev for other things, and definitely for lirc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Mon Aug 31 01:44:08 2026 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 30 Aug 2026 18:44:08 -0700 Subject: [Slackbuilds-users] lirc breaks udev In-Reply-To: <9316548a-112e-454e-aba6-9168fa69dbdf@gmail.com> References: <9316548a-112e-454e-aba6-9168fa69dbdf@gmail.com> Message-ID: Could you maybe give me a bit more to go off of? The udev rule has no user or group in it. What file is expecting a group? Do you have any errors you can provide? If a group is specified and created, do the errors go away? Also, because this was an issue last time, you're talking about running 0.9.3a from SBo on 15.0, right? Last time you complained it was broken on this list, you were running a newer version than what was on SBo and were also on -current (which this list is not used for either purpose). https://lists.slackbuilds.org/pipermail/slackbuilds-users/2025-December/030731.html Jeremy On Sun, Aug 30, 2026, 6:28?PM David Chmelik wrote: > The lirc.SlackBuild doesn't do the standard thing to ask to install its > group, but installs a file expecting a group, which apparently breaks udev > for other things, and definitely for lirc. > _______________________________________________ > 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: