From kev4321 at fastmail.fm Fri May 1 16:20:34 2026 From: kev4321 at fastmail.fm (Kevin McCormick) Date: Fri, 1 May 2026 11:20:34 -0500 Subject: [Slackbuilds-users] request for QPrompt package Message-ID: <938d44e7-28c5-4036-aee1-a3920a957e1d@fastmail.fm> I am looking at a program called QPrompt, which is a teleprompt program useful for video presenters or people doing public presentations. The program is at https://github.com/Cuperino/QPrompt-Teleprompter The build instructions are at: https://github.com/Cuperino/QPrompt-Teleprompter/blob/main/BUILD.md According to the build instructions, it appears all except one dependencies are already in Slackware 15.0. The dependency not in Slackware 15.0 is "QHotKey" at: https://github.com/Skycoder42/QHotkey It turns out that QHotKey needs "qpmx" for installation: ?https://github.com/Skycoder42/qpmx#installation Thanks, Kevin McCormick I also received this email from the QPrompt developer: Cuperino? left a comment (Cuperino/QPrompt-Teleprompter#462) Hi Kevin, I appreciate you trying to build a Slackware package. QHotkey The use of QHotkey is very minor if you try to build the QPrompt 2.0.1 or 2.0.0. There it's used to provide one shortcut that toggles window transparency (not to be confused with the background transparency that is controlled by a slider). You can remove it from 2.0.x and no one will notice. Feel free to do so, but only for the 2.0 branch. That is no longer the case for 2.1.0 branch, which is currently in development under the main and 2.1 branches. There, QHotkey takes a prominent role alongside a new dependency called KGlobalAccel. These two dependencies together add support for global hotkeys in both X11 (QHotkey) and Plasma Wayland (KGlobalAccel). KGlobalAccel could also add support for hotkeys under X11 but, I have programmed it for GlobalHotkey to take precedence because I find it to provide a better user experience, as it is less invasive. KGlobalAccel shortcuts remain in operation across sessions because it sets the shortcuts at the Plasma Desktop level. A user of X11 who is not expecting this find themselves frustrated if we only used KGlobalAccel. Since it will be a while before 2.1 is released next year I can make QHotkey completely optional in the 2.0 branch, so you could make the Slackware package without it. This would be a temporary measure, because it would have to be present for QPrompt 2.1. qpmx Sometimes dependencies introduce dependencies that weren't there before. This is probably the case with qpmx and it was probably either KDE's KCoreAddons or KDE's Kirigami that introduced it, both KDE dependencies. Neither of these dependencies can be made optional. Kirigami is an integral part of QPrompt's DNA. KCoreAddons could be replaced with a bit of reverse engineering or creating a stripped down fork of it, but I'm not willing to do either of those things, as that would move us away from my goal to have QPrompt join KDE someday. I ship older versions of KDE Frameworks on my Windows and macOS builds, so I haven't had to deal with this sub-dependency yet. For my Deb package I just use the packages shipped by the distribution, and that works for every Linux dependency except for QHotkey, which isn't shipped by Debian. That includes optional dependencies like KCrash, which I don't include on Windows and macOS because it has a ton of sub-dependencies and it is non-essential. KCrash is only used to restart the app automatically in the event of a crash. Memory leak bug There is a bug in Qt 6.10 and later that causes a memory leak when Screen > Projections is checked. It's already been fixed but the fix hasn't made it out to a release yet. For that reason we removed the Screen Projections feature from the official Ubuntu package. A variation of QPrompt 2.0.1 with the feature removed is found in the v2.0.1-no-screens tag. That's what was used to create the Ubuntu package. You should use it too if Slackware happens to be shipping Qt 6.10. From fsleg at t-rg.ws Fri May 1 16:43:05 2026 From: fsleg at t-rg.ws (fsLeg) Date: Fri, 1 May 2026 19:43:05 +0300 Subject: [Slackbuilds-users] request for QPrompt package In-Reply-To: <938d44e7-28c5-4036-aee1-a3920a957e1d@fastmail.fm> References: <938d44e7-28c5-4036-aee1-a3920a957e1d@fastmail.fm> Message-ID: <9dbad382-399d-47e6-82e6-096dbd314473@t-rg.ws> I just tried building QPrompt, and version 2.x requires KDE6 (or, more specifically, KF6-6.9.0). Even -current doesn't have KDE6 (yet, but still). Version 1.2.0, however, builds and runs fine as is with no extra dependencies (or maybe I just have enough extra packages installed). It's not difficult to write a SlackBuild for it, especially since it'll be stuck at that version until Slackware 15.1 with KDE6 releases. But who's gonna maintain it? On 5/1/26 19:20, Kevin McCormick wrote: > I am looking at a program called QPrompt, which is a teleprompt program > useful for video presenters or people doing public presentations. > > The program is at https://github.com/Cuperino/QPrompt-Teleprompter > > The build instructions are at: https://github.com/Cuperino/QPrompt- > Teleprompter/blob/main/BUILD.md > > According to the build instructions, it appears all except one > dependencies are already in Slackware 15.0. From chris.willing at linux.com Sat May 2 04:44:10 2026 From: chris.willing at linux.com (Christoph Willing) Date: Sat, 2 May 2026 14:44:10 +1000 Subject: [Slackbuilds-users] request for QPrompt package In-Reply-To: <9dbad382-399d-47e6-82e6-096dbd314473@t-rg.ws> References: <938d44e7-28c5-4036-aee1-a3920a957e1d@fastmail.fm> <9dbad382-399d-47e6-82e6-096dbd314473@t-rg.ws> Message-ID: <3c470539-eeb1-459d-a8d9-daf298b0332e@linux.com> On 2/5/26 02:43, fsLeg via SlackBuilds-users wrote: > I just tried building QPrompt, and version 2.x requires KDE6 (or, more > specifically, KF6-6.9.0). Even -current doesn't have KDE6 (yet, but > still). > > Version 1.2.0, however, builds and runs fine as is with no extra > dependencies (or maybe I just have enough extra packages installed). > It's not difficult to write a SlackBuild for it, especially since > it'll be stuck at that version until Slackware 15.1 with KDE6 > releases. But who's gonna maintain it? Having once worked in the broadcast TV industry, I like the idea of this software and just now took the liberty of submitting a SlackBuild for it (version 1.2.0 as fsLeg already mentioned). If anyone else wants to claim it, I'm happy to pass it on to them. chris From nalumc at gmail.com Sat May 2 10:14:01 2026 From: nalumc at gmail.com (Andrew Conway) Date: Sat, 2 May 2026 11:14:01 +0100 Subject: [Slackbuilds-users] udev rule clash Message-ID: I'm writing a slackbuild for FireCapture (https://www.firecapture.de/). It ships with udev rules for various astronomical cameras but these udev rules already exist on my system from libindi packages, and are likely to for other astro minded folk too. My first thought is to exclude these udev rules in the FireCapture package unless the user has set an environment variable to explicitly say they want them included, and note that in the README. Is that OK? Is there a convention for how slackbuilds should handle such udev rules? Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sat May 2 10:55:54 2026 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 2 May 2026 12:55:54 +0200 Subject: [Slackbuilds-users] udev rule clash In-Reply-To: References: Message-ID: Il giorno sab 2 mag 2026 alle ore 12:22 Andrew Conway ha scritto: > I'm writing a slackbuild for FireCapture (https://www.firecapture.de/). > It ships with udev rules for various astronomical cameras but these udev > rules already exist on my system from libindi packages, and are likely to > for other astro minded folk too. > > My first thought is to exclude these udev rules in the FireCapture package > unless the user has set an environment variable to explicitly say they want > them included, and note that in the README. > > Is that OK? Is there a convention for how slackbuilds should handle such > udev rules? > hi Andrew, usually you can install them, if they don't overlap with something else... in this case and considered also that libindi is part of Slackware since this iteration of current (so it will be in the next stable release), IMHO, you could let the SlackBuild install them and then, still in the SlackBuild, move them away in the /usr/doc/firecapture-$VERSION directory, adding a note in the README that one has to manually copy the udev rule for his own hardware in the /etc/udev/rules.d directory. Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat May 2 17:51:55 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 3 May 2026 00:51:55 +0700 Subject: [Slackbuilds-users] Updates - 20260502.1 Message-ID: <20260503005155.5c9c9b9c@home.slackie.org> Sat May 2 17:43:25 UTC 2026 academic/R: Updated for version 4.6.0. academic/zotero: Updated for version 9.0.1. accessibility/xdotool: Updated for version 4.20260303.1. audio/ocenaudio-bin: Updated for version 3.18.2. audio/reaper: Updated for version 7.70. desktop/catclock: Added (X11 xclock). desktop/sxhkd: Updated for version 0.6.3. development/HeidiSQL: Updated for version 12.17. development/aws-cdk: Updated for version 2.1120.0. development/buf: Updated for version 1.69.0. development/bun-bin: Updated for version 1.3.13. development/cmake-opt: Updated for version 3.31.12. development/cudatoolkit_12: Don't hard code compiler version development/cudatoolkit_13: Don't hard code compiler version development/deno-bin: Updated for version 2.7.14. development/deno: Updated for version 2.7.14. development/difftastic: Updated for version 0.69.0. development/dub: Added (package manager). development/electron-bin: Updated for version 41.3.0 development/github-cli: Updated for version 2.92.0. development/gitify-bin: Updated for version 6.20.0. development/jupyter-notebook: Updated for version 7.5.6. development/jupyterlab: Updated for version 4.5.7. development/mongodb-shell: Updated for version 2.8.3. development/nodejs24-bin: Updated for version 24.15.0. development/notepad++: Updated for version 8.9.4 development/positron: Updated for version 2026.04.1_10. development/python3-numpy-legacy: Updated for version 1.26.3 development/python3-numpy: Updated for version 2.0.2 development/qb64pe: Updated for version 4.5.0 development/rider: Updated for version 2026.1.1. development/sbt: Updated for version 1.12.10 development/terraform: Updated for version 1.15.0. development/tfenv: Updated for version 3.2.2. development/vscodium: Updated for version 1.116.02821. development/vstudio: Updated for version 17.3.1. development/zed-editor-bin: Updated for version 0.233.10. development/zed-editor-bin: Updated for version 1.0.0. ham/SoapyFobosSDR: Update script. ham/qlog: Updated for version 0.50.0. libraries/KDSingleApplication: Updated for version 1.2.1. libraries/SDL3: Updated for version 3.4.6. libraries/nx-libs: Updated for version 3.5.99.27. libraries/plastid: Patch for updated python3-numpy-legacy libraries/uriparser: Updated for version 1.0.1. misc/open-simh: Updated for version 20260430_45f1ce7. misc/yara: Updated for version 4.5.5. multimedia/plexmediaserver: Updated for version 1.43.1.10611_1e34174b1. multimedia/qprompt: Added (teleprompter). multimedia/w_scan_cpp: Update dependencies. multimedia/x265: Updated for version 4.2. network/brave-browser: Updated for version 1.89.143. network/dillo: Updated for version 3.3.0. network/discord: Version bump to 0.0.134 network/discord: Version bump to 0.0.135 network/dnsproxy-bin: Updated for version 0.81.2. network/dropbox: Updated for version 250.4.3245. network/element-desktop-bin: Updated for version 1.12.17. network/element-desktop: Updated for version 1.12.17. network/exim: Updated for version 4.99.2. network/filen-desktop-bin: Added (cloud storage). network/grafana: Updated for version 13.0.1. network/helium-browser: Updated for version 0.11.5.1 network/librespeed-cli: Updated for version 1.0.13. network/librewolf: Updated for version 150.0.1_1. network/llhttp: Updated for version 9.4.1. network/localsend-bin: Added (Secure Communication). network/mullvad-browser: Updated for version 15.0.11 network/opera: Updated for version 130.0.5847.92 network/qodem: Update download. network/r8125: Added (Network driver). network/repology-cli: Added (cli for repology). network/rustdesk-opt: Removed (FTBFS). network/senpai: update to 0.4.1 network/slack: Updated for version 4.47.69. network/tor-browser: Updated for version 15.0.11. network/vivaldi: Updated for version 7.9.3970.60. network/wego: Update for 2.4 network/wireshark: Updated for version 4.6.5. network/x2goserver: Updated for version 20201227_08aa5e6. network/zen-browser: Updated for version 1.19.10b office/LibreOffice: Updated for version 26.2.3.2 office/homebank: Updated for version 5.10. office/ledger-live: Updated for version 4.0.0 office/qownnotes: Updated for version 26.5.0. office/sent: update to 1 office/wps-office-dicts: Updated for version 26.2.3.2 perl/MoarVM: Updated for version 2026.04. perl/nqp: Updated for version 2026.04. perl/perl-Crypt-URandom: Added (Perl Module). perl/perl-CryptX: Updated for version 0.088. perl/perl-File-Find-Rule: Updated for version 0.35. perl/perl-Net-CIDR-Lite: Updated for version 0.23. perl/perl-Net-CIDR: Updated for version 0.27. perl/rakudo: Updated for version 2026.04. python/numexpr: Updated for version VERSION:-2.10.0 python/python3-boto3: Updated for version 1.42.97 python/python3-meson-opt: Updated for version 1.11.1. python/python3-numba: Updated for version 0.60.0 python/python3-opencv: Require python3-numpy-legacy python/python3-packaging-opt: Updated for version 26.2. python/python3-pathspec: Updated for version 1.1.1. python/python3-pdm: Version bump to 2.26.8 python/python3-pydantic-core: Updated for version 2.46.3. python/python3-pydantic: Updated for version 2.13.3. python/python3-pypandoc: Update for 1.17 (+orphan maintenance) python/python3-pyzmq: Updated for version 27.1.0 python/python3-setuptools-scm-opt: README updated. python/python3-trove-classifiers: Updated for version 2026.4.28.13. python/tzdata: Updated for version 2026.2. ruby/ruby-build: Updated for version 20260501. system/aufs-dir-tools: Added (AUFS File Management). system/bfs: Added (breadth-first find command). system/containerd: Updated for version 1.7.31. system/distrobox: Updated for version 1.8.2.5. system/docker-cli: Updated for version 29.4.2. system/docker: Strip binaries. system/docker: Updated for version 29.4.2. system/fzf-bin: Updated from version 0.72.0. system/fzf: Updated for version 0.72.0. system/mongo-tools: Updated for version 100.16.1. system/nerdctl: Updated for version 2.2.2 system/netdata: Updated for version 2.10.3. system/plymouth-slackware-theme: Update script. system/prometheus: Updated for version 3.11.2 system/qdirstat: Updated for version 2.0. system/sbo-maintainer-tools: Updated for version 0.9.4. system/sbozyp: Updated for version 1.7.2 system/slackrepo-hints: Updated for version 20260502. system/slackrepo: Updated for version 20260502. system/ventoy: Fix permission. system/ventoy: Updated for version 1.1.12 +--------------------------+ -- 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 sbo at linuxgalaxy.org Sun May 3 04:27:44 2026 From: sbo at linuxgalaxy.org (KB_SBo) Date: Sun, 03 May 2026 04:27:44 +0000 Subject: [Slackbuilds-users] udev rule clash In-Reply-To: References: Message-ID: On 5/2/26 03:55, Matteo Bernardini wrote: > Il giorno sab 2 mag 2026 alle ore 12:22 Andrew Conway > ha scritto: > > I'm writing a slackbuild for FireCapture (https:// > www.firecapture.de/ ). It ships with > udev rules for various astronomical cameras but these udev rules > already exist on my system from libindi packages, and are likely to > for other astro minded folk too. > > My first thought is to exclude these udev rules in the FireCapture > package unless the user has set an environment?variable to > explicitly say they want them included, and note that in the README. > > Is that OK? Is there a convention for how slackbuilds should handle > such udev rules? > > > hi Andrew, > > usually you can install them, if they don't overlap with something else... > > in this case and considered also that libindi is part of Slackware since > this iteration of current (so it will be in the next stable release), > IMHO, you could let the SlackBuild install them and then, still in the > SlackBuild, move them away in the /usr/doc/firecapture-$VERSION > directory, adding a note in the README that one has to manually copy the > udev rule for his own hardware in the /etc/udev/rules.d directory. > > Matteo Yes, I concur that plopping the udev rules into /usr/doc/... might be best now that INDI is in Slackware-Current. While libindi has a bunch of driver and undev rules included, I will still be maintaining the additional 3rd party drivers and libraries. I might need to do something similar. libindi-drivers libindi-libraries Looking at firecapture, there may be some camera library conflicts (ZWO ASI for example), so you may need to reference and itemize in your README. https://drivers.indilib.org/cameras/ I was not aware of firecapture. Looks nifty. -Ed From dimitar at nikov.net Sun May 3 11:24:03 2026 From: dimitar at nikov.net (dimitar at nikov.net) Date: Sun, 03 May 2026 12:24:03 +0100 Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts Message-ID: Hi everyone, I am writing to inform the community that I will be stepping down as the maintainer of the following SlackBuild scripts, which I would like to mark as orphaned: - diff-so-fancy - hw-probe - perl-Digest-SHA - warp-terminal Due to current constraints, I am no longer in a position to continue maintaining these scripts, including performing the necessary testing and updates. I believe it is best to step aside at this point so that others in the community may take over maintenance if they wish. I would also like to note that I intend to continue distributing these scripts independently. I would like to thank the SBo team and the wider community for their support during this time. I hope the scripts remain useful and continue to be maintained going forward. Best regards, Dimitar Nikov From rizitis at gmail.com Sun May 3 15:08:54 2026 From: rizitis at gmail.com (=?UTF-8?B?zpnPic6szr3Ovc63z4I=?=) Date: Sun, 3 May 2026 18:08:54 +0300 Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: References: Message-ID: I can take hw-probe if you agree I will use AppImage that has no requires and run fine in slackware-15.0 ???? ??? 3 ??? 2026 ???? 2:24??.?., ?/? Dimitar Nikov via SlackBuilds-users ??????: > > Hi everyone, > > I am writing to inform the community that I will be stepping down as the > maintainer of the following SlackBuild scripts, which I would like to > mark as orphaned: > > - diff-so-fancy > - hw-probe > - perl-Digest-SHA > - warp-terminal > > Due to current constraints, I am no longer in a position to continue > maintaining these scripts, including performing the necessary testing > and updates. I believe it is best to step aside at this point so that > others in the community may take over maintenance if they wish. > > I would also like to note that I intend to continue distributing these > scripts independently. > > I would like to thank the SBo team and the wider community for their > support during this time. I hope the scripts remain useful and continue > to be maintained going forward. > > Best regards, > Dimitar Nikov > _______________________________________________ > 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 Sun May 3 19:54:33 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 3 May 2026 15:54:33 -0400 (EDT) Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: References: Message-ID: <6913a01e-b013-8585-88a1-244d207f8fc0@slackware.uk> On Sun, 3 May 2026, Dimitar Nikov via SlackBuilds-users wrote: > - perl-Digest-SHA Slackware's perl package already contains this perl module. It's a slightly older version (Slackware has 6.02, you packaged 6.04). Do we really need it? Your hw-probe depends on it, but it seems to run fine without it... and we do have a policy of not including anything in SBo that's already included in Slackware. One amusing thing: hw-probe runs "pacman", I suppose it's trying to run the Arch package tool, but here I have the SBo games/pacman package installed, and so running hw-probe actually runs the game. It should probably be patched to look in /sbin or wherever Arch keeps its pacman package manager (the game is installed as /usr/games/pacman)... or just patch it to skip pacman entirely, since we're making a Slackware package, and we know we're not running on Arch. This would be something for the new maintainer to look into, since you're abandoning it. From urchlay at slackware.uk Sun May 3 20:05:08 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 3 May 2026 16:05:08 -0400 (EDT) Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: References: Message-ID: On Sun, 3 May 2026, ??????? wrote: > I can take hw-probe if you agree > I will use AppImage that has no requires and run fine in slackware-15.0 Please don't use an AppImage. hw-probe is written in Perl, and Perl isn't a "moving target". This is a tiny perl script with no support files needed at runtime. If you do take hw-probe over, can I suggest adding some of its documentation to the /usr/doc/hw-probe-$VERSION dir? LICENSE.md, README.md, NEWS.md, and the 2 licenses in the LICENSES/ dir should be in the package IMO. If you absolutely *insist* on using an AppImage, please submit it as a new build called hw-probe-bin. Repackaging a binary should be a last resort, when it's the only way to get something to work on Slackware. That's not the case with hw-probe. I updated it locally to the latest release (1.6.6) and it works fine. From lenardrspencer at gmail.com Sun May 3 22:43:52 2026 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Sun, 3 May 2026 18:43:52 -0400 Subject: [Slackbuilds-users] My OpenJDK{11,17,21} SBo scripts Message-ID: The latest AlienBOB slackbuilds of these packages leave my SBo scripts redundant and not really necessary anymore, so if nobody wants to take them over, they can probably be removed in the next update. -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Sun May 3 22:53:34 2026 From: urchlay at slackware.uk (B. Watson) Date: Sun, 3 May 2026 18:53:34 -0400 (EDT) Subject: [Slackbuilds-users] My OpenJDK{11,17,21} SBo scripts In-Reply-To: References: Message-ID: <3beaa559-9ecf-bb91-62f2-52a8437d235@slackware.uk> On Sun, 3 May 2026, Lenard Spencer wrote: > The latest AlienBOB slackbuilds of these packages leave my SBo scripts redundant and not really necessary anymore, so if nobody wants to take them over, they can > probably be removed in the next update. OpenJDK11 and OpenJDK17 are listed as dependencies for other builds. We don't have a way to specify an AlienBOB package as a dependency. If you remove OpenJDK11 and OpenJDK17, you break autofirma, PrismLauncher, PrismLauncher-Unlocked, and sonarqube. From dimitar at nikov.net Mon May 4 08:40:42 2026 From: dimitar at nikov.net (dimitar at nikov.net) Date: Mon, 04 May 2026 09:40:42 +0100 Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: <6913a01e-b013-8585-88a1-244d207f8fc0@slackware.uk> References: <6913a01e-b013-8585-88a1-244d207f8fc0@slackware.uk> Message-ID: <249619185dddf90627c265ea0794cadb@nikov.net> Hi, On 2026-05-03 20:54, B. Watson wrote: > On Sun, 3 May 2026, Dimitar Nikov via SlackBuilds-users wrote: > >> - perl-Digest-SHA > > Slackware's perl package already contains this perl module. It's a > slightly older version (Slackware has 6.02, you packaged 6.04). > > Do we really need it? Your hw-probe depends on it, but it seems to run > fine without it... and we do have a policy of not including anything > in SBo that's already included in Slackware. > Then this script could be removed from the repository. I have no idea how this package slipped through submission form in this case. > One amusing thing: hw-probe runs "pacman", I suppose it's trying > to run the Arch package tool, but here I have the SBo games/pacman > package installed, and so running hw-probe actually runs the game. It > should probably be patched to look in /sbin or wherever Arch keeps its > pacman package manager (the game is installed as /usr/games/pacman)... > or just patch it to skip pacman entirely, since we're making a > Slackware package, and we know we're not running on Arch. > I am not playing any games, hence I don't have that package installed. Also, that command check comes form the upstream. It does checks for some more package managers/OS-specific binaries too. Should they be patched too? > This would be something for the new maintainer to look into, since > you're abandoning it. I'll do the requested patch before handing over the package. Cheers, Dimitar From dimitar at nikov.net Mon May 4 09:13:49 2026 From: dimitar at nikov.net (dimitar at nikov.net) Date: Mon, 04 May 2026 10:13:49 +0100 Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: References: Message-ID: Hi, On 2026-05-03 21:05, B. Watson wrote: > On Sun, 3 May 2026, ??????? wrote: > >> I can take hw-probe if you agree Yes, ???????, please do. I have no objection who the next maintainer will be. I could send you my latest slackbuild script with update to 1.6.6 and patch for removing pacman invocation if you want. Please drop me a message if you do. >> I will use AppImage that has no requires and run fine in >> slackware-15.0 > > Please don't use an AppImage. hw-probe is written in Perl, and Perl > isn't a "moving target". This is a tiny perl script with no support > files needed at runtime. > > If you do take hw-probe over, can I suggest adding some of its > documentation > to the /usr/doc/hw-probe-$VERSION dir? LICENSE.md, README.md, NEWS.md, > and > the 2 licenses in the LICENSES/ dir should be in the package IMO. > Those were added to my latest submisison alongisde with the version update and patcing the script to avoid running pacman. > If you absolutely *insist* on using an AppImage, please submit it as a > new build called hw-probe-bin. > > Repackaging a binary should be a last resort, when it's the only way > to get something to work on Slackware. That's not the case with > hw-probe. > I updated it locally to the latest release (1.6.6) and it works fine. > _______________________________________________ > 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/ Cheers, Dimitar From urchlay at slackware.uk Mon May 4 09:10:08 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 4 May 2026 05:10:08 -0400 (EDT) Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: <249619185dddf90627c265ea0794cadb@nikov.net> References: <6913a01e-b013-8585-88a1-244d207f8fc0@slackware.uk> <249619185dddf90627c265ea0794cadb@nikov.net> Message-ID: On Mon, 4 May 2026, dimitar at nikov.net wrote: > Then this script could be removed from the repository. > I have no idea how this package slipped through submission form in this case. Probably because it doesn't actually overwrite any of Slackware's files. It installs the module to /usr/lib(64)?/perl5/vendor_perl/, and the one in Slackware is installed in /usr/lib(64)?/perl5/ (without the vendor_perl). > I am not playing any games, hence I don't have that package installed. Right, you didn't know there was a conflict. Now you know... that's how a lot of conflicts are discovered: software works fine on your system, but someone else has problems with it, and it turns out to be because of some unrelated package. At least in this case it was *very* obvious what was happening. > Also, that command check comes form the upstream. Yes. But upstream aren't superhuman. You're packaging this thing *for Slackware*, which upstream probably doesn't run and has never even thought about. More specifically, you're packaging it for SBo, which has a known conflict... > It does checks for some more package managers/OS-specific binaries > too. Should they be patched too? Possibly, but probably not. It's unlikely there will ever be a binary called e.g. "rpm" or "dpkg" that is anything other than the actual rpm or dpkg (nobody's ever likely to name a game or unrelated program that). pacman is a special case because the Arch developers thought it would be cute to choose a name that already means something else... The fact that it tries to run rpm, dpkg, etc isn't a problem. If you don't use these package managers, it won't find any packages installed by them. If you do, then it's *useful* to have hw-probe list them. I can think of 2 good ways to patch it: either remove the whole "if(checkCmd("pacman"))" paragraph beginning with line 15948, or modify the checkCmd subroutine (starting on line 16887) so it removes /usr/games from the PATH. It looks like you should be able to change line 16900 to: my @Paths = grep { !m{/games} } split(/:/, $ENV{"PATH"}); ...which would remove any path including /games (including /usr/games and also e.g. /usr/local/games). This would allow for the (highly unlikely) possibility that someone's actually running Arch's pacman on Slackware. > I'll do the requested patch before handing over the package. Thanks. I'm sorta curious if Arch (or AUR) packages up the same pacman game as we do, and if so what do they call the executable? pac-man, pacman-game, something like that... I guess I don't care enough, spent 10 mins searching for it, failed to find, and that's 10 minutes of my life I'll never get back. From dimitar at nikov.net Mon May 4 09:34:51 2026 From: dimitar at nikov.net (dimitar at nikov.net) Date: Mon, 04 May 2026 10:34:51 +0100 Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: References: <6913a01e-b013-8585-88a1-244d207f8fc0@slackware.uk> <249619185dddf90627c265ea0794cadb@nikov.net> Message-ID: <9ad73d5a8df468677dcaaa0c911cf85e@nikov.net> On 2026-05-04 10:10, B. Watson wrote: > On Mon, 4 May 2026, dimitar at nikov.net wrote: > >> Then this script could be removed from the repository. >> I have no idea how this package slipped through submission form in >> this case. > > Probably because it doesn't actually overwrite any of Slackware's > files. It installs the module to /usr/lib(64)?/perl5/vendor_perl/, and > the one in Slackware is installed in /usr/lib(64)?/perl5/ (without the > vendor_perl). > >> I am not playing any games, hence I don't have that package installed. > > Right, you didn't know there was a conflict. Now you know... that's > how a lot of conflicts are discovered: software works fine on your > system, but someone else has problems with it, and it turns out to > be because of some unrelated package. At least in this case it was > *very* obvious what was happening. > >> Also, that command check comes form the upstream. > > Yes. But upstream aren't superhuman. You're packaging this thing *for > Slackware*, which upstream probably doesn't run and has never even > thought about. > > More specifically, you're packaging it for SBo, which has a known > conflict... > Thanks for the suggestions and explanations. However, I don?t appreciate the lecturing tone. I already said I?ll apply the requested patch before handing over the package, and I?ve now done that. I understand how software conflicts are found, so the extra commentary was unnecessary. I also don?t think it matters whether the pacman game has not changed in 10 years, or whether only a handful of people have it installed. That is not relevant to the fix. The issue was reported, I acknowledged it, and it has been patched. Let?s leave it at that. >> It does checks for some more package managers/OS-specific binaries >> too. Should they be patched too? > > Possibly, but probably not. It's unlikely there will ever be a binary > called e.g. "rpm" or "dpkg" that is anything other than the actual > rpm or dpkg (nobody's ever likely to name a game or unrelated program > that). pacman is a special case because the Arch developers thought it > would be cute to choose a name that already means something else... > > The fact that it tries to run rpm, dpkg, etc isn't a problem. If you > don't use these package managers, it won't find any packages installed > by them. If you do, then it's *useful* to have hw-probe list them. > > I can think of 2 good ways to patch it: either remove the whole > "if(checkCmd("pacman"))" paragraph beginning with line 15948, or > modify the checkCmd subroutine (starting on line 16887) so it > removes /usr/games from the PATH. It looks like you should be > able to change line 16900 to: > > my @Paths = grep { !m{/games} } split(/:/, $ENV{"PATH"}); > > ...which would remove any path including /games (including /usr/games > and also e.g. /usr/local/games). This would allow for the (highly > unlikely) possibility that someone's actually running Arch's pacman > on Slackware. > >> I'll do the requested patch before handing over the package. > > Thanks. > > I'm sorta curious if Arch (or AUR) packages up the same pacman > game as we do, and if so what do they call the executable? pac-man, > pacman-game, something like that... I guess I don't care enough, spent > 10 mins searching for it, failed to find, and that's 10 minutes of my > life I'll never get back. As for the ?10 minutes of my life I?ll never get back? comment: that was entirely your choice. I didn?t ask you to look into it, so please don?t frame it as if I wasted your time. Cheers, Dimitar From urchlay at slackware.uk Mon May 4 09:56:23 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 4 May 2026 05:56:23 -0400 (EDT) Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: <9ad73d5a8df468677dcaaa0c911cf85e@nikov.net> References: <6913a01e-b013-8585-88a1-244d207f8fc0@slackware.uk> <249619185dddf90627c265ea0794cadb@nikov.net> <9ad73d5a8df468677dcaaa0c911cf85e@nikov.net> Message-ID: On Mon, 4 May 2026, dimitar at nikov.net wrote: > Thanks for the suggestions and explanations. > > However, I don?t appreciate the lecturing tone. I already said I?ll apply the > requested patch before handing over the package, and I?ve now done that. > > I understand how software conflicts are found, so the extra commentary was > unnecessary. Sorry, didn't intend to lecture or sound condescending. I'm writing for everyone on the mailing list. You might already know everything I say, but others reading this might not. The idea is that folks might read it and learn something. Also, when I was writing the email, I didn't know you had (or were in the process of) already sent a patch. I was trying to suggest useful ways to patch it. From dimitar at nikov.net Mon May 4 10:38:57 2026 From: dimitar at nikov.net (dimitar at nikov.net) Date: Mon, 04 May 2026 11:38:57 +0100 Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: References: <6913a01e-b013-8585-88a1-244d207f8fc0@slackware.uk> <249619185dddf90627c265ea0794cadb@nikov.net> <9ad73d5a8df468677dcaaa0c911cf85e@nikov.net> Message-ID: On 2026-05-04 10:56, B. Watson wrote: > On Mon, 4 May 2026, dimitar at nikov.net wrote: > >> Thanks for the suggestions and explanations. >> >> However, I don?t appreciate the lecturing tone. I already said I?ll >> apply the >> requested patch before handing over the package, and I?ve now done >> that. >> >> I understand how software conflicts are found, so the extra commentary >> was unnecessary. > > Sorry, didn't intend to lecture or sound condescending. > > I'm writing for everyone on the mailing list. You might already know > everything I say, but others reading this might not. The idea is > that folks might read it and learn something. > > Also, when I was writing the email, I didn't know you had (or were in > the process of) already sent a patch. I was trying to suggest useful > ways to patch it. Please accept my sincere apologies for misunderstanding that part of your reply. I appreciate the clarification. I think I misread the intent behind your message, especially given the mailing list context. To avoid further confusion or unnecessary friction, I?m going to unsubscribe from the list for now. Best regards, Dimitar From zsd+slackbuilds at jdvb.ca Mon May 4 14:25:59 2026 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Mon, 4 May 2026 11:25:59 -0300 Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: References: <6913a01e-b013-8585-88a1-244d207f8fc0@slackware.uk> <249619185dddf90627c265ea0794cadb@nikov.net> Message-ID: On Mon, May 4, 2026 at 05:10 (-0400), B. Watson wrote: > I'm sorta curious if Arch (or AUR) packages up the same pacman > game as we do, and if so what do they call the executable? pac-man, > pacman-game, something like that... I guess I don't care enough, spent > 10 mins searching for it, failed to find, and that's 10 minutes of my > life I'll never get back. Yes, but you fought the good fight. Jim From list+sbo at vahedi.org Mon May 4 22:18:01 2026 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Tue, 5 May 2026 00:18:01 +0200 Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: References: <6913a01e-b013-8585-88a1-244d207f8fc0@slackware.uk> <249619185dddf90627c265ea0794cadb@nikov.net> Message-ID: <83708965-80f3-4350-9a92-19e3e2e45cfa@vahedi.org> Archlinux package of the game: https://aur.archlinux.org/packages/pacman_sdl-ebuc99-git Someone already beaten by the collision: https://blog.stackademic.com/installing-pacman-in-arch-linux-when-you-blow-it-up-aa40778aa237 -Shahab From urchlay at slackware.uk Mon May 4 23:05:06 2026 From: urchlay at slackware.uk (B. Watson) Date: Mon, 4 May 2026 19:05:06 -0400 (EDT) Subject: [Slackbuilds-users] Orphaning SlackBuild Scripts In-Reply-To: <83708965-80f3-4350-9a92-19e3e2e45cfa@vahedi.org> References: <6913a01e-b013-8585-88a1-244d207f8fc0@slackware.uk> <249619185dddf90627c265ea0794cadb@nikov.net> <83708965-80f3-4350-9a92-19e3e2e45cfa@vahedi.org> Message-ID: <3a62c143-3be3-8e66-35aa-be80c2e59254@slackware.uk> On Tue, 5 May 2026, Shahab Vahedi via SlackBuilds-users wrote: > Archlinux package of the game: > > https://aur.archlinux.org/packages/pacman_sdl-ebuc99-git Well-spotted, thanks. > Someone already beaten by the collision: > > https://blog.stackademic.com/installing-pacman-in-arch-linux-when-you-blow-it-up-aa40778aa237 Wow. That recovery procedure is pretty complex... if you blow up pkgtools on Slackware you can just untar the pkgtools package in / to get it reinstalled. From rizitis at gmail.com Tue May 5 19:02:12 2026 From: rizitis at gmail.com (=?UTF-8?B?zpnPic6szr3Ovc63z4I=?=) Date: Tue, 5 May 2026 22:02:12 +0300 Subject: [Slackbuilds-users] Request for the SlackBuilds Upload Form Message-ID: Hello, I have a request, I don't know if it is easily accepted and technically feasible: Is there a possibility that in the case that a package fails to pass the submit form/ the failure message can be made in red font or even just a single "failed" red? So that it irritates the eyes of the elderly and we don't pass by the message essentially unread, thinking that everything is fine? I understand that this need doesn't make much sense for normal people, but it will help some, maybe a few, as stupid as it may seem... I just want to submit it as a suggestion for the admins to consider, even if it is not accepted, which I will also understand. Thank you. rizitis. From willysr at slackbuilds.org Wed May 6 09:12:05 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 6 May 2026 16:12:05 +0700 Subject: [Slackbuilds-users] Request for the SlackBuilds Upload Form In-Reply-To: References: Message-ID: <20260506161205.4fc97318@tuf15.slackie.org> >Hello, I have a request, I don't know if it is easily accepted and >technically feasible: >Is there a possibility that in the case that a package fails to pass >the submit form/ the failure message can be made in red font or even >just a single "failed" red? >So that it irritates the eyes of the elderly and we don't pass by the >message essentially unread, thinking that everything is fine? > >I understand that this need doesn't make much sense for normal people, >but it will help some, maybe a few, as stupid as it may seem... > >I just want to submit it as a suggestion for the admins to consider, >even if it is not accepted, which I will also understand. AFAIK the submit page already has some checks and it will display bold text instead of red. perhaps you can define what kind of failed situation you are referring to? -- 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 nalumc at gmail.com Wed May 6 13:08:30 2026 From: nalumc at gmail.com (Andrew Conway) Date: Wed, 6 May 2026 14:08:30 +0100 Subject: [Slackbuilds-users] udev rule clash In-Reply-To: References: Message-ID: > > > > hi Andrew, > > > > usually you can install them, if they don't overlap with something > else... > > > > in this case and considered also that libindi is part of Slackware since > > this iteration of current (so it will be in the next stable release), > > IMHO, you could let the SlackBuild install them and then, still in the > > SlackBuild, move them away in the /usr/doc/firecapture-$VERSION > > directory, adding a note in the README that one has to manually copy the > > udev rule for his own hardware in the /etc/udev/rules.d directory. > > > > Matteo > > Yes, I concur that plopping the udev rules into /usr/doc/... might be > best now that INDI is in Slackware-Current. While libindi has a bunch > of driver and undev rules included, I will still be maintaining the > additional 3rd party drivers and libraries. I might need to do something > similar. > > libindi-drivers > libindi-libraries > > Looking at firecapture, there may be some camera library conflicts (ZWO > ASI for example), so you may need to reference and itemize in your README. > > https://drivers.indilib.org/cameras/ > > I was not aware of firecapture. Looks nifty. > > > -Ed > > Thanks Matteo and Ed. I'll go with putting the rules in /usr/doc. Ed - I'll need to test the slackbuild on 15.0 in due course because I'm actually doing this on -current as it happens as it's on the laptop I use for astro stuff with kstars/ekos. Works very well. Thanks for your efforts getting that into slackware! I have noticed that the QHY libraries shipped with firecapture are slightly older than those in my libindi-libraries package, but I did adapt your slackbuilds for my needs as I needed the latest betas from QHY to support the minicam8. Again, I'll need to test this again on 15.0 with your vanilla slackbuilds. I'll report back if I learn anything from that. Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: From nalumc at gmail.com Wed May 6 13:08:30 2026 From: nalumc at gmail.com (Andrew Conway) Date: Wed, 6 May 2026 14:08:30 +0100 Subject: [Slackbuilds-users] udev rule clash In-Reply-To: References: Message-ID: > > > > hi Andrew, > > > > usually you can install them, if they don't overlap with something > else... > > > > in this case and considered also that libindi is part of Slackware since > > this iteration of current (so it will be in the next stable release), > > IMHO, you could let the SlackBuild install them and then, still in the > > SlackBuild, move them away in the /usr/doc/firecapture-$VERSION > > directory, adding a note in the README that one has to manually copy the > > udev rule for his own hardware in the /etc/udev/rules.d directory. > > > > Matteo > > Yes, I concur that plopping the udev rules into /usr/doc/... might be > best now that INDI is in Slackware-Current. While libindi has a bunch > of driver and undev rules included, I will still be maintaining the > additional 3rd party drivers and libraries. I might need to do something > similar. > > libindi-drivers > libindi-libraries > > Looking at firecapture, there may be some camera library conflicts (ZWO > ASI for example), so you may need to reference and itemize in your README. > > https://drivers.indilib.org/cameras/ > > I was not aware of firecapture. Looks nifty. > > > -Ed > > Thanks Matteo and Ed. I'll go with putting the rules in /usr/doc. Ed - I'll need to test the slackbuild on 15.0 in due course because I'm actually doing this on -current as it happens as it's on the laptop I use for astro stuff with kstars/ekos. Works very well. Thanks for your efforts getting that into slackware! I have noticed that the QHY libraries shipped with firecapture are slightly older than those in my libindi-libraries package, but I did adapt your slackbuilds for my needs as I needed the latest betas from QHY to support the minicam8. Again, I'll need to test this again on 15.0 with your vanilla slackbuilds. I'll report back if I learn anything from that. Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: From artourter at gmail.com Thu May 7 17:36:51 2026 From: artourter at gmail.com (Greg Tourte) Date: Thu, 7 May 2026 18:36:51 +0100 Subject: [Slackbuilds-users] updates to signal-desktop Message-ID: Hi, I am getting more and more uncomfortable with not being able to have signal-desktop updated. I realise that versions above 8.1 do not work with vanilla stable but they do work with the glibc in the testing folder in -stable (and of course they will work in -current). What I am proposing is to have a new signal-desktop-legacy package with the latest version working on -stable without the testing glibc and keep the signal-desktop package fully uptodate and a note in the README file. Does this sound acceptable? Cheers Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From fsleg at t-rg.ws Thu May 7 19:11:25 2026 From: fsleg at t-rg.ws (fsLeg) Date: Thu, 7 May 2026 22:11:25 +0300 Subject: [Slackbuilds-users] The state of development/google-go-lang Message-ID: A few days ago ollama released an update that requires google-go-lang 1.26. SBo only has version 1.25.9. I took a look at the SlackBuild and found that, first, it's not as trivial as changing VERSION for a new even major number, and second, the code is a mess. So I refactored it. Well, first I just wrote my own[1] code, then I combined it with the existing SlackBuild[2]. Key points: 1. Instead of having a section for every bootstrap version, I iterate through them as the steps are the same anyway. This also means that future updates are as easy as adjusting GO_BOOTSTRAP array and required versions below it. 2. I don't see a point in building the entire bootstrap chain from scratch every time. The first time? Sure, this ensures there were no blobs used. But afterwards? You've already done that, so why not just use the version you already have to build the next one? This significantly reduces build time when upgrading versions. So my script detects the available go version and adjusts the bootstrap chain as needed, even removing it completely if the previously installed version of google-go-lang is recent enough. My "detection" relies on the fact that Slackware's stock gcc-go package doesn't set GOROOT environment variable, while SBo's google-go-lang package does. Hopefully, it's enough. And if not, the script should still build the package using bootstrapping from scratch. 3. I removed some obsolete code. Also, what is the point of `go install` command? I don't think there's a use case for installing shared libraries of the toolchin itself. Arch doesn't do it, Google doesn't do it, everything still seems to just work if you don't do it. So I'm thinking about removing that too, it'll help save a lot of space. And about the SlackBuild's state. The currently listed maintainer is Vincent Batts. However, his last contribution was in 2023, and the script has been de-facto maintained by the admins ever since. To whom should I've written this whole passage of text? Since I don't know, I'm writing here. [1]: https://github.com/fsLeg/sb/blob/master/google-go-lang/google-go-lang.SlackBuild [2]: https://github.com/fsLeg/SlackBuilds/blob/master/google-go-lang/google-go-lang.SlackBuild From andrew.clemons at gmail.com Thu May 7 21:15:29 2026 From: andrew.clemons at gmail.com (Andrew Clemons) Date: Fri, 8 May 2026 06:15:29 +0900 Subject: [Slackbuilds-users] The state of development/google-go-lang In-Reply-To: References: Message-ID: Hello, On 2026-05-07 22:11:25 +0300, slackbuilds-users at slackbuilds.org wrote: > A few days ago ollama released an update that requires google-go-lang 1.26. > SBo only has version 1.25.9. I took a look at the SlackBuild and found that, > first, it's not as trivial as changing VERSION for a new even major number, > and second, the code is a mess. So I refactored it. > > Well, first I just wrote my own[1] code, then I combined it with the > existing SlackBuild[2]. Key points: > > 1. Instead of having a section for every bootstrap version, I iterate > through them as the steps are the same anyway. This also means that future > updates are as easy as adjusting GO_BOOTSTRAP array and required versions > below it. > > 2. I don't see a point in building the entire bootstrap chain from scratch > every time. The first time? Sure, this ensures there were no blobs used. But > afterwards? You've already done that, so why not just use the version you > already have to build the next one? This significantly reduces build time > when upgrading versions. So my script detects the available go version and > adjusts the bootstrap chain as needed, even removing it completely if the > previously installed version of google-go-lang is recent enough. > > My "detection" relies on the fact that Slackware's stock gcc-go package > doesn't set GOROOT environment variable, while SBo's google-go-lang package > does. Hopefully, it's enough. And if not, the script should still build the > package using bootstrapping from scratch. > > 3. I removed some obsolete code. Also, what is the point of `go install` > command? I don't think there's a use case for installing shared libraries of > the toolchin itself. Arch doesn't do it, Google doesn't do it, everything > still seems to just work if you don't do it. So I'm thinking about removing > that too, it'll help save a lot of space. > > And about the SlackBuild's state. The currently listed maintainer is Vincent > Batts. However, his last contribution was in 2023, and the script has been > de-facto maintained by the admins ever since. To whom should I've written > this whole passage of text? Since I don't know, I'm writing here. Regarding 1 and 2: This is mostly just a case of inertia - what started off a one bootstrap of 1.19 so we could build 1.20 slowly crept into multiple bootstrap versions as the months rolled by with no new stable and golang's 6 month release cycle. When I added the 1.19 bootstrap to build 1.20, I did not bother trying to detect if there was already a google-go-lang installed just always bootstrapped to keep things simple with the idea once the next stable was released, we'd just delete that block of the slackbuild again and there'd be no other changes to make. It was not my build, so I did not want to make sweeping changes. Now, as you've pointed out, with more time passing, it's a right mess with 3 bootstraps to get 1.25 built. I did consider some time along the way adjusting it, but had still hoped we could just snip out the bootstrap steps at the beginning and leave everything else the same when the next stable release came, but now that google-go-lang is in current, this script is only here to keep us covered until then. Which brings me to point 3 - I don't know the answer. It has been there since 4f1f5818531. But considering google-go-lang has been added to current, probably not worth changing this slackbuild here now. I have a few things that use google-go-lang, hence I have been bumping the version - I updated it for 1.26 last week, but I have not submitted it yet because its quite disruptive for the weekly update, but I will probably do it this week or next. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 870 bytes Desc: not available URL: From willysr at slackbuilds.org Fri May 8 03:57:21 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 8 May 2026 10:57:21 +0700 Subject: [Slackbuilds-users] The state of development/google-go-lang In-Reply-To: References: Message-ID: <20260508105721.293b17e4@office64.slackie.org> >I have a few things that use google-go-lang, hence I have been bumping >the version - I updated it for 1.26 last week, but I have not submitted >it yet because its quite disruptive for the weekly update, but I will >probably do it this week or next. We can do it in separate branch first and test other scripts that depends on it until we got most (if not all) of it, then we can merge it into master branch after. What do you think? -- 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 fsleg at t-rg.ws Fri May 8 13:57:34 2026 From: fsleg at t-rg.ws (fsLeg) Date: Fri, 8 May 2026 16:57:34 +0300 Subject: [Slackbuilds-users] The state of development/google-go-lang In-Reply-To: References: Message-ID: Hopefully, the next -stable releases in the foreseeable future. But the way -current is going, it might be anywhere between a year and a few more years before Pat announces a beta. While the future is bright, we live in the here and now, and, chances are, Google releases go-1.28 before Slackware-15.1, which would require yet another bootstrapping step. I'd choose maintainability even if it's temporary. But whatever works for you. If it ain't broken, don't fix it. I also looked at the SlackBuild Pat uses. He just took the one from SBo, except he replaced all bootstrapping steps with using a Google's pre-built binary release to build the needed version in just one step. Whatever works for him, I guess, the resulting packages are the same anyway. I looked at commit 4f1f5818531. It was 10 years ago. According to Google's published releases, they stopped bundling libraries since 1.20, which was 3 years ago. So the `go install` line really only consumes space with nothing actually using the built libraries. People will still be able to build shared libraries for their projects, they won't be linked to the toolchain anyway. On 5/8/26 00:15, Andrew Clemons wrote: > Regarding 1 and 2: > > This is mostly just a case of inertia - what started off a one bootstrap > of 1.19 so we could build 1.20 slowly crept into multiple bootstrap > versions as the months rolled by with no new stable and golang's 6 month > release cycle. When I added the 1.19 bootstrap to build 1.20, I did not > bother trying to detect if there was already a google-go-lang installed > just always bootstrapped to keep things simple with the idea once the > next stable was released, we'd just delete that block of the slackbuild > again and there'd be no other changes to make. It was not my build, so I > did not want to make sweeping changes. Now, as you've pointed out, with > more time passing, it's a right mess with 3 bootstraps to get 1.25 > built. I did consider some time along the way adjusting it, but had > still hoped we could just snip out the bootstrap steps at the beginning > and leave everything else the same when the next stable release came, > but now that google-go-lang is in current, this script is only here to > keep us covered until then. > > Which brings me to point 3 - I don't know the answer. It has been there > since 4f1f5818531. But considering google-go-lang has been added to > current, probably not worth changing this slackbuild here now. > > I have a few things that use google-go-lang, hence I have been bumping > the version - I updated it for 1.26 last week, but I have not submitted > it yet because its quite disruptive for the weekly update, but I will > probably do it this week or next. From willysr at slackbuilds.org Fri May 8 17:11:54 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 May 2026 00:11:54 +0700 Subject: [Slackbuilds-users] The state of development/google-go-lang In-Reply-To: References: Message-ID: <20260509001154.5964541f@home.slackie.org> >Hopefully, the next -stable releases in the foreseeable future. But the >way -current is going, it might be anywhere between a year and a few >more years before Pat announces a beta. While the future is bright, we >live in the here and now, and, chances are, Google releases go-1.28 >before Slackware-15.1, which would require yet another bootstrapping >step. I'd choose maintainability even if it's temporary. But whatever >works for you. If it ain't broken, don't fix it. let's start from here https://github.com/SlackBuildsOrg/slackbuilds/pull/15537 -- 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 May 9 14:03:45 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 May 2026 21:03:45 +0700 Subject: [Slackbuilds-users] Updates - 20260509.1 Message-ID: <20260509210345.5b6ccc38@home.slackie.org> Sat May 9 13:46:38 UTC 2026 academic/Graphic: Added (Graph Tool). academic/dwave-ocean-sdk: Fix DOWNLOAD for renamed project. academic/plus42: Updated for version 1.3.15. academic/suitesparse: Updated for version 7.12.2 academic/zotero: update 9.0.2 audio/libation-bin: Added (manage audiobooks). audio/nnls-chroma: Update download URL. audio/qtractor: Updated for version 1.6.0. audio/reaper: Updated for version 7.71 audio/vamp-plugin-sdk: Update download URL. desktop/ComixCursors: Updated for version 0.10.1. desktop/awf: Updated for version 4.1.0. desktop/human-gtk-theme: Updated for version 3.1.0. desktop/qhotkey: Added (Global Shortcut). development/aws-cdk: Updated for version 2.1121.0. development/diff-so-fancy: Orphaned development/eisl: Updated for version 5.63. development/electron-bin: Updated for version 41.5.0 development/google-go-lang: Updated for version 1.25.10. development/hoppscotch: Updated for version 26.4.0. development/jujutsu: Updated for version 0.41.0 development/jupyter_server: Update for 2.18.0 development/mongodb-compass: Updated for version 1.49.6. development/nexus: Updated DOWNLOAD. development/php82: Updated for version 8.2.31 development/php84: Updated for version 8.4.21 development/pnpm: Updated for version 10.33.4. development/positron: Updated for version 2026.05.0_179. development/python3-numpy-legacy: Fix PATH,PYTHONPATH development/python3-numpy: Update README development/ropgadget: Added (ROP Exploitation). development/sourcegit: Updated for version 2026.10. development/srcML: Updated DOWNLOAD. development/terraform: Updated for version 1.15.2. development/typescript:update to version 6.0.3 development/zed-editor-bin: Updated for version 1.0.1. development/zed-editor-bin: Updated for version 1.1.5. development/zed-editor-bin: Updated for version 1.1.6. git/ci: Update CI dependencies. graphics/chafa:update to version 1.18.2 graphics/zgrviewer: Fix sourceforge DOWNLOAD. ham/js8call: Update source URL. ham/wsjtz: Update source URL. libraries/Botan2: Added (Crypto Library for C++). libraries/Botan3: Removed (use Botan). libraries/SDL3: Updated for version 3.4.8 libraries/ceres-solver: Updated for version 2.2.0. libraries/fzssh: Updated for version 1.2.1. libraries/highway:update to version 1.4.0 libraries/libcamera: Added (camera stack and framework). libraries/libcurl-gnutls: Updated for version 8.20.0. libraries/libfabric:update to version 2.5.1 libraries/libfilezilla: Updated for version 0.55.5. libraries/librist:update to version 0.2.14 libraries/libshumate: Added (GTK4 Toolkit). libraries/lttng-ust: Added (Tracing Library). libraries/openapv:update to version 0.2.1.3 libraries/pam_usb: Updated for version 0.8.6 libraries/pcg-c: Added (random number generator). libraries/plastid: New maintainer libraries/qwt: Added support for Qt6. Thanks to Brent Spillner. libraries/simdjson:update to version 4.6.3 libraries/simdutf:update to version 9.0.0 libraries/vmaf:update to version 3.1.0 libraries/xeve: update to version 429c18a_20260224 libraries/xmlsec: Update source URL. library/Botan: Updated for version 3.12.0. misc/balena-etcher-bin: Updated for version 2.1.5. misc/open-simh: Updated for version 20260503_774a74f multimedia/ardour-harvid-bin: Added (Ardour Video Tools). multimedia/ffmpegfs: Updated for version 2.18. multimedia/obs-studio: Ensure cmake-opt is used multimedia/qprompt: Mention qhotkey in README multimedia/tvheadend: Updated DOWNLOAD. network/amneziawg-kernel: fix building for 5.15.204 kernel network/ani-cli:update to version 4.14 network/brave-browser: update 1.89.145 network/dnsproxy-bin: Updated for version 0.81.3. network/dropbear: Updated for version 2026.90. network/filezila: Updated for version 3.70.5. network/floorp-bin: Updated for version 12.13.0. network/floorp-bin: Updated for version 12.14.0. network/gallery-dl: Updated for version 1.32.1 network/helium-browser: Updated for version 0.11.7.1 network/librewolf: Updated for version 150.0.2_1. network/microsoft-edge: Updated for version 147.0.3912.98. network/mullvad-browser: Updated for version 15.0.12. network/mullvadvpn-app: Updated for version 2026.2. network/neomutt: Updated for version 20260504. network/opera: Updated for version 131.0.5877.5 network/protonmail-bridge: Updated for version 3.24.2. network/r8168: Updated for version 8.056.02. network/rclone-src: Updated for version 1.74.0 network/rclone: update 1.74.0 network/repology-cli: Updated for version 20260502. network/signal-desktop-legacy: Added (Signal for Desktop). network/signal-desktop: Updated for version 8.9.1. network/telegram: Updated for version 6.8.1. network/tor-browser: Updated for version 15.0.13. network/vivaldi: Updated for version 7.9.3970.64. network/whalebird: Updated for version 6.3.0 network/zen-browser: Updated for version 1.19.11b office/antiword-xp-rb: Added (Extract Text). office/glow:update to version 2.1.2 office/keepassxc: Updated to version 2.7.12. office/qownnotes: Update README. office/qownnotes: Updated for version 26.5.6. perl/perl-Digest-SHA: Orphaned. python/git-fame: Updated for version 3.1.2. python/numexpr: New maintainer python/pyOpenSSL: Updated for version 26.2.0. python/python3-WTForms: Updated for version 3.2.2. python/python3-boto3: Orphaned. python/python3-capstone: Added (Disassembler for Python3). python/python3-gensim: Fix build. python/python3-mistune: Update for 3.2.1 python/python3-narwhals: Updated for version 2.21.0. python/python3-numba: New maintainer python/python3-odfdo: Updated for version 3.22.7. python/python3-pandas: Fix dep. python/python3-pydantic-core: Updated for version 2.46.4. python/python3-pydantic: Updated for version 2.13.4. python/python3-trove-classifiers: Updated for version 2026.5.7.17. ruby/ruby-build: Updated for version 20260503. system/B-em: Updated for version 20260505_fb313c4. system/TLP: update to 1.10.1 system/apache-cassandra: Updated for version 4.1.11. system/apache-cassandra: Use permanent URL. system/bfs: update to 4.1.2 system/conky: Update script. system/corectrl: updated dependency to the new Botan2 package. system/distrobuilder:update to version 3.3.1 system/epson-inkjet-printer-escpr: Updated for version 1.8.8 system/fish: Updated for version 4.7.0. system/hw-probe: Updated for version 1.6.6. system/incus: Updated for version 7.0 system/lts: Added (File Time Data). system/nvidia-driver: Updated for version 595.71.05. system/nvidia-firmware: Updated for version 340.108. system/nvidia-kernel: Updated for version 595.71.05. system/nvidia-legacy580-driver: Updated for version 580.159.03. system/nvidia-legacy580-kernel: Updated for version 580.159.03. system/osquery-bin: Updated for version 5.23.0. system/powershell: Updated for version 7.6.1. system/prometheus: Updated for version 3.11.3 system/sbotest: Updated for version 1.2.2. system/sbotools: Updated for version 4.1.4. system/slackpkg-update-notify: Added (Notification for slackpkg). system/warp-terminal: Orphaned. system/xen: Updated for version 4.21.1. system/zellij-bin: Mark as x86_64 only. +--------------------------+ -- 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 May 9 16:20:47 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 9 May 2026 10:20:47 -0600 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: <20260509210345.5b6ccc38@home.slackie.org> References: <20260509210345.5b6ccc38@home.slackie.org> Message-ID: Botan is not building for me: cd . && ln -fs libbotan-3.so.12 libbotan-3.so.12.12.0 "/usr/bin/python3" "src/scripts/build_docs.py" --build-dir="build" INFO: Starting sphinx-build -q -c src/configs/sphinx -j auto -W --keep-going -b html doc build/docs/handbook Could not import furo theme; falling back to agago /tmp/SBo/Botan-3.12.0/doc/api_ref/pbkdf.rst:173: WARNING: Could not lex literal_block as "cpp". Highlighting skipped. ERROR: Error running sphinx-build -q -c src/configs/sphinx -j auto -W --keep-going -b html doc build/docs/handbook make: *** [Makefile:53: build/doc.stamp] Error 1 A failure occurred while building Botan: Botan.SlackBuild returned non-zero. On Sat, May 9, 2026 at 8:03?AM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Sat May 9 13:46:38 UTC 2026 > academic/Graphic: Added (Graph Tool). > academic/dwave-ocean-sdk: Fix DOWNLOAD for renamed project. > academic/plus42: Updated for version 1.3.15. > academic/suitesparse: Updated for version 7.12.2 > academic/zotero: update 9.0.2 > audio/libation-bin: Added (manage audiobooks). > audio/nnls-chroma: Update download URL. > audio/qtractor: Updated for version 1.6.0. > audio/reaper: Updated for version 7.71 > audio/vamp-plugin-sdk: Update download URL. > desktop/ComixCursors: Updated for version 0.10.1. > desktop/awf: Updated for version 4.1.0. > desktop/human-gtk-theme: Updated for version 3.1.0. > desktop/qhotkey: Added (Global Shortcut). > development/aws-cdk: Updated for version 2.1121.0. > development/diff-so-fancy: Orphaned > development/eisl: Updated for version 5.63. > development/electron-bin: Updated for version 41.5.0 > development/google-go-lang: Updated for version 1.25.10. > development/hoppscotch: Updated for version 26.4.0. > development/jujutsu: Updated for version 0.41.0 > development/jupyter_server: Update for 2.18.0 > development/mongodb-compass: Updated for version 1.49.6. > development/nexus: Updated DOWNLOAD. > development/php82: Updated for version 8.2.31 > development/php84: Updated for version 8.4.21 > development/pnpm: Updated for version 10.33.4. > development/positron: Updated for version 2026.05.0_179. > development/python3-numpy-legacy: Fix PATH,PYTHONPATH > development/python3-numpy: Update README > development/ropgadget: Added (ROP Exploitation). > development/sourcegit: Updated for version 2026.10. > development/srcML: Updated DOWNLOAD. > development/terraform: Updated for version 1.15.2. > development/typescript:update to version 6.0.3 > development/zed-editor-bin: Updated for version 1.0.1. > development/zed-editor-bin: Updated for version 1.1.5. > development/zed-editor-bin: Updated for version 1.1.6. > git/ci: Update CI dependencies. > graphics/chafa:update to version 1.18.2 > graphics/zgrviewer: Fix sourceforge DOWNLOAD. > ham/js8call: Update source URL. > ham/wsjtz: Update source URL. > libraries/Botan2: Added (Crypto Library for C++). > libraries/Botan3: Removed (use Botan). > libraries/SDL3: Updated for version 3.4.8 > libraries/ceres-solver: Updated for version 2.2.0. > libraries/fzssh: Updated for version 1.2.1. > libraries/highway:update to version 1.4.0 > libraries/libcamera: Added (camera stack and framework). > libraries/libcurl-gnutls: Updated for version 8.20.0. > libraries/libfabric:update to version 2.5.1 > libraries/libfilezilla: Updated for version 0.55.5. > libraries/librist:update to version 0.2.14 > libraries/libshumate: Added (GTK4 Toolkit). > libraries/lttng-ust: Added (Tracing Library). > libraries/openapv:update to version 0.2.1.3 > libraries/pam_usb: Updated for version 0.8.6 > libraries/pcg-c: Added (random number generator). > libraries/plastid: New maintainer > libraries/qwt: Added support for Qt6. Thanks to Brent Spillner. > libraries/simdjson:update to version 4.6.3 > libraries/simdutf:update to version 9.0.0 > libraries/vmaf:update to version 3.1.0 > libraries/xeve: update to version 429c18a_20260224 > libraries/xmlsec: Update source URL. > library/Botan: Updated for version 3.12.0. > misc/balena-etcher-bin: Updated for version 2.1.5. > misc/open-simh: Updated for version 20260503_774a74f > multimedia/ardour-harvid-bin: Added (Ardour Video Tools). > multimedia/ffmpegfs: Updated for version 2.18. > multimedia/obs-studio: Ensure cmake-opt is used > multimedia/qprompt: Mention qhotkey in README > multimedia/tvheadend: Updated DOWNLOAD. > network/amneziawg-kernel: fix building for 5.15.204 kernel > network/ani-cli:update to version 4.14 > network/brave-browser: update 1.89.145 > network/dnsproxy-bin: Updated for version 0.81.3. > network/dropbear: Updated for version 2026.90. > network/filezila: Updated for version 3.70.5. > network/floorp-bin: Updated for version 12.13.0. > network/floorp-bin: Updated for version 12.14.0. > network/gallery-dl: Updated for version 1.32.1 > network/helium-browser: Updated for version 0.11.7.1 > network/librewolf: Updated for version 150.0.2_1. > network/microsoft-edge: Updated for version 147.0.3912.98. > network/mullvad-browser: Updated for version 15.0.12. > network/mullvadvpn-app: Updated for version 2026.2. > network/neomutt: Updated for version 20260504. > network/opera: Updated for version 131.0.5877.5 > network/protonmail-bridge: Updated for version 3.24.2. > network/r8168: Updated for version 8.056.02. > network/rclone-src: Updated for version 1.74.0 > network/rclone: update 1.74.0 > network/repology-cli: Updated for version 20260502. > network/signal-desktop-legacy: Added (Signal for Desktop). > network/signal-desktop: Updated for version 8.9.1. > network/telegram: Updated for version 6.8.1. > network/tor-browser: Updated for version 15.0.13. > network/vivaldi: Updated for version 7.9.3970.64. > network/whalebird: Updated for version 6.3.0 > network/zen-browser: Updated for version 1.19.11b > office/antiword-xp-rb: Added (Extract Text). > office/glow:update to version 2.1.2 > office/keepassxc: Updated to version 2.7.12. > office/qownnotes: Update README. > office/qownnotes: Updated for version 26.5.6. > perl/perl-Digest-SHA: Orphaned. > python/git-fame: Updated for version 3.1.2. > python/numexpr: New maintainer > python/pyOpenSSL: Updated for version 26.2.0. > python/python3-WTForms: Updated for version 3.2.2. > python/python3-boto3: Orphaned. > python/python3-capstone: Added (Disassembler for Python3). > python/python3-gensim: Fix build. > python/python3-mistune: Update for 3.2.1 > python/python3-narwhals: Updated for version 2.21.0. > python/python3-numba: New maintainer > python/python3-odfdo: Updated for version 3.22.7. > python/python3-pandas: Fix dep. > python/python3-pydantic-core: Updated for version 2.46.4. > python/python3-pydantic: Updated for version 2.13.4. > python/python3-trove-classifiers: Updated for version 2026.5.7.17. > ruby/ruby-build: Updated for version 20260503. > system/B-em: Updated for version 20260505_fb313c4. > system/TLP: update to 1.10.1 > system/apache-cassandra: Updated for version 4.1.11. > system/apache-cassandra: Use permanent URL. > system/bfs: update to 4.1.2 > system/conky: Update script. > system/corectrl: updated dependency to the new Botan2 package. > system/distrobuilder:update to version 3.3.1 > system/epson-inkjet-printer-escpr: Updated for version 1.8.8 > system/fish: Updated for version 4.7.0. > system/hw-probe: Updated for version 1.6.6. > system/incus: Updated for version 7.0 > system/lts: Added (File Time Data). > system/nvidia-driver: Updated for version 595.71.05. > system/nvidia-firmware: Updated for version 340.108. > system/nvidia-kernel: Updated for version 595.71.05. > system/nvidia-legacy580-driver: Updated for version 580.159.03. > system/nvidia-legacy580-kernel: Updated for version 580.159.03. > system/osquery-bin: Updated for version 5.23.0. > system/powershell: Updated for version 7.6.1. > system/prometheus: Updated for version 3.11.3 > system/sbotest: Updated for version 1.2.2. > system/sbotools: Updated for version 4.1.4. > system/slackpkg-update-notify: Added (Notification for slackpkg). > system/warp-terminal: Orphaned. > system/xen: Updated for version 4.21.1. > system/zellij-bin: Mark as x86_64 only. > +--------------------------+ > > > -- > 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 willysr at slackbuilds.org Sat May 9 16:25:18 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 May 2026 23:25:18 +0700 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: References: <20260509210345.5b6ccc38@home.slackie.org> Message-ID: <20260509232518.7d06484a@home.slackie.org> >Botan is not building for me: > >cd . && ln -fs libbotan-3.so.12 libbotan-3.so.12.12.0 >"/usr/bin/python3" "src/scripts/build_docs.py" --build-dir="build" > INFO: Starting sphinx-build -q -c src/configs/sphinx -j auto -W >--keep-going -b html doc build/docs/handbook >Could not import furo theme; falling back to agago >/tmp/SBo/Botan-3.12.0/doc/api_ref/pbkdf.rst:173: WARNING: Could not lex >literal_block as "cpp". Highlighting skipped. > ERROR: Error running sphinx-build -q -c src/configs/sphinx -j auto -W >--keep-going -b html doc build/docs/handbook >make: *** [Makefile:53: build/doc.stamp] Error 1 >A failure occurred while building Botan: > Botan.SlackBuild returned non-zero. It built fine on our CI test https://github.com/SlackBuildsOrg/slackbuilds/pull/15546 did you test this on -current or -stable, just to make sure -- 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 May 9 16:29:23 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 May 2026 23:29:23 +0700 Subject: [Slackbuilds-users] The state of development/google-go-lang In-Reply-To: <20260509001154.5964541f@home.slackie.org> References: <20260509001154.5964541f@home.slackie.org> Message-ID: <20260509232923.0bdc27d6@home.slackie.org> >>Hopefully, the next -stable releases in the foreseeable future. But the >>way -current is going, it might be anywhere between a year and a few >>more years before Pat announces a beta. While the future is bright, we >>live in the here and now, and, chances are, Google releases go-1.28 >>before Slackware-15.1, which would require yet another bootstrapping >>step. I'd choose maintainability even if it's temporary. But whatever >>works for you. If it ain't broken, don't fix it. > >let's start from here >https://github.com/SlackBuildsOrg/slackbuilds/pull/15537 I bumped google go lang to 1.25.10 for this week because: 1. Andrew Clemons is still testing all scripts against 1.26.3 2. 1.25.10 and 1.26.3 fixed 11 security updates, so it should be addressed first -- 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 zsd+slackbuilds at jdvb.ca Sat May 9 16:42:09 2026 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Sat, 9 May 2026 13:42:09 -0300 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: References: <20260509210345.5b6ccc38@home.slackie.org> Message-ID: On Sat, May 9, 2026 at 10:20 (-0600), Luveh Keraph wrote: > Botan is not building for me: > cd . && ln -fs libbotan-3.so.12 libbotan-3.so.12.12.0 > "/usr/bin/python3" "src/scripts/build_docs.py" --build-dir="build" > INFO: Starting sphinx-build -q -c src/configs/sphinx -j auto -W > --keep-going -b html doc build/docs/handbook > Could not import furo theme; falling back to agago > /tmp/SBo/Botan-3.12.0/doc/api_ref/pbkdf.rst:173: WARNING: Could not lex > literal_block as "cpp". Highlighting skipped. > ERROR: Error running sphinx-build -q -c src/configs/sphinx -j auto -W > --keep-going -b html doc build/docs/handbook > make: *** [Makefile:53: build/doc.stamp] Error 1 > A failure occurred while building Botan: > Botan.SlackBuild returned non-zero. For what it's worth, it built for me with no problems. Jim From artourter at gmail.com Sat May 9 16:46:11 2026 From: artourter at gmail.com (Greg Tourte) Date: Sat, 9 May 2026 17:46:11 +0100 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: <20260509232518.7d06484a@home.slackie.org> References: <20260509210345.5b6ccc38@home.slackie.org> <20260509232518.7d06484a@home.slackie.org> Message-ID: I cannot reproduce this either, neither on -stable nor on -current. On Sat, 9 May 2026 at 17:25, Willy Sudiarto Raharjo wrote: > >Botan is not building for me: > > > >cd . && ln -fs libbotan-3.so.12 libbotan-3.so.12.12.0 > >"/usr/bin/python3" "src/scripts/build_docs.py" --build-dir="build" > > INFO: Starting sphinx-build -q -c src/configs/sphinx -j auto -W > >--keep-going -b html doc build/docs/handbook > >Could not import furo theme; falling back to agago > >/tmp/SBo/Botan-3.12.0/doc/api_ref/pbkdf.rst:173: WARNING: Could not lex > >literal_block as "cpp". Highlighting skipped. > > ERROR: Error running sphinx-build -q -c src/configs/sphinx -j auto -W > >--keep-going -b html doc build/docs/handbook > >make: *** [Makefile:53: build/doc.stamp] Error 1 > >A failure occurred while building Botan: > > Botan.SlackBuild returned non-zero. > > > It built fine on our CI test > https://github.com/SlackBuildsOrg/slackbuilds/pull/15546 > > did you test this on -current or -stable, just to make sure > > > -- > 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 Sat May 9 16:53:20 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 9 May 2026 10:53:20 -0600 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: References: <20260509210345.5b6ccc38@home.slackie.org> <20260509232518.7d06484a@home.slackie.org> Message-ID: It's in 15.0 with all the current patches. On Sat, May 9, 2026 at 10:46?AM Greg Tourte wrote: > I cannot reproduce this either, neither on -stable nor on -current. > > On Sat, 9 May 2026 at 17:25, Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> >Botan is not building for me: >> > >> >cd . && ln -fs libbotan-3.so.12 libbotan-3.so.12.12.0 >> >"/usr/bin/python3" "src/scripts/build_docs.py" --build-dir="build" >> > INFO: Starting sphinx-build -q -c src/configs/sphinx -j auto -W >> >--keep-going -b html doc build/docs/handbook >> >Could not import furo theme; falling back to agago >> >/tmp/SBo/Botan-3.12.0/doc/api_ref/pbkdf.rst:173: WARNING: Could not lex >> >literal_block as "cpp". Highlighting skipped. >> > ERROR: Error running sphinx-build -q -c src/configs/sphinx -j auto -W >> >--keep-going -b html doc build/docs/handbook >> >make: *** [Makefile:53: build/doc.stamp] Error 1 >> >A failure occurred while building Botan: >> > Botan.SlackBuild returned non-zero. >> >> >> It built fine on our CI test >> https://github.com/SlackBuildsOrg/slackbuilds/pull/15546 >> >> did you test this on -current or -stable, just to make sure >> >> >> -- >> 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 fsleg at t-rg.ws Sat May 9 17:16:45 2026 From: fsleg at t-rg.ws (fsLeg) Date: Sat, 09 May 2026 20:16:45 +0300 Subject: [Slackbuilds-users] The state of development/google-go-lang In-Reply-To: <20260509232923.0bdc27d6@home.slackie.org> References: <20260509001154.5964541f@home.slackie.org> <20260509232923.0bdc27d6@home.slackie.org> Message-ID: My original post was more about the script itself, Google's release of go-1.26 was just what prompted me to look into it in the first place. After I refactored the SlackBuild, it's now relatively trivial for me to build any version I want. Besides, nothing on SBo strictly requires go-1.26. Well, maybe except ollama, although its maintainer isn't very keen on providing latest and greatest, but they do chug out releases often enough to be annoying for package maintainers. But I have my own repository of build scripts, so it's not an issue for me. On May 9, 2026 19:29:23 GMT+03:00, Willy Sudiarto Raharjo wrote: >I bumped google go lang to 1.25.10 for this week because: >1. Andrew Clemons is still testing all scripts against 1.26.3 >2. 1.25.10 and 1.26.3 fixed 11 security updates, so it should be addressed first From artourter at gmail.com Sat May 9 17:57:06 2026 From: artourter at gmail.com (Greg Tourte) Date: Sat, 9 May 2026 18:57:06 +0100 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: References: <20260509210345.5b6ccc38@home.slackie.org> <20260509232518.7d06484a@home.slackie.org> Message-ID: I thought it was due to having Sphinx installed but even then It builds fine and doesn't try to use sphinx-build like your log indicate. Can you try adding --without-sphinx to the configure options to see if it helps. I would also be interested to know which sphinx related packages you have installed on your system to see which one triggers the failure. Greg On Sat, 9 May 2026 at 17:53, Luveh Keraph <1.41421 at gmail.com> wrote: > It's in 15.0 with all the current patches. > > > On Sat, May 9, 2026 at 10:46?AM Greg Tourte wrote: > >> I cannot reproduce this either, neither on -stable nor on -current. >> >> On Sat, 9 May 2026 at 17:25, Willy Sudiarto Raharjo < >> willysr at slackbuilds.org> wrote: >> >>> >Botan is not building for me: >>> > >>> >cd . && ln -fs libbotan-3.so.12 libbotan-3.so.12.12.0 >>> >"/usr/bin/python3" "src/scripts/build_docs.py" --build-dir="build" >>> > INFO: Starting sphinx-build -q -c src/configs/sphinx -j auto -W >>> >--keep-going -b html doc build/docs/handbook >>> >Could not import furo theme; falling back to agago >>> >/tmp/SBo/Botan-3.12.0/doc/api_ref/pbkdf.rst:173: WARNING: Could not lex >>> >literal_block as "cpp". Highlighting skipped. >>> > ERROR: Error running sphinx-build -q -c src/configs/sphinx -j auto -W >>> >--keep-going -b html doc build/docs/handbook >>> >make: *** [Makefile:53: build/doc.stamp] Error 1 >>> >A failure occurred while building Botan: >>> > Botan.SlackBuild returned non-zero. >>> >>> >>> It built fine on our CI test >>> https://github.com/SlackBuildsOrg/slackbuilds/pull/15546 >>> >>> did you test this on -current or -stable, just to make sure >>> >>> >>> -- >>> 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 1.41421 at gmail.com Sat May 9 20:31:07 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 9 May 2026 14:31:07 -0600 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: References: <20260509210345.5b6ccc38@home.slackie.org> <20260509232518.7d06484a@home.slackie.org> Message-ID: I am at a loss here, because of the following: I have three Slackware 15.0 systems. Systems 2 and 3 have no Sphinx packages installed, whereas in system 1 I have sphinx-2.2.11-x86_64-1_SBo sphinxcontrib-applehelp-2.0.0-x86_64-1_SBo sphinxcontrib-devhelp-2.0.0-x86_64-1_SBo sphinxcontrib-htmlhelp-2.1.0-x86_64-1_SBo sphinxcontrib-jsmath-1.0.1-x86_64-1_SBo sphinxcontrib-qthelp-2.0.0-x86_64-1_SBo sphinxcontrib-serializinghtml-2.0.0-x86_64-1_SBo Botan fails to build in 1 as indicated before. It also fails to build in 2, failing in exactly the same way as 1, but it builds on 3 without any issues. 2 and 3 do not have exactly the same packages installed, but, unlike 1, neither has anything obviously to do with Sphinx. I am flummoxed. Any suggestions as to what else to look for? On Sat, May 9, 2026 at 11:57?AM Greg Tourte wrote: > I thought it was due to having Sphinx installed but even then It builds > fine and doesn't try to use sphinx-build like your log indicate. Can you > try adding --without-sphinx to the configure options to see if it helps. > > I would also be interested to know which sphinx related packages you have > installed on your system to see which one triggers the failure. > > Greg > > On Sat, 9 May 2026 at 17:53, Luveh Keraph <1.41421 at gmail.com> wrote: > >> It's in 15.0 with all the current patches. >> >> >> On Sat, May 9, 2026 at 10:46?AM Greg Tourte wrote: >> >>> I cannot reproduce this either, neither on -stable nor on -current. >>> >>> On Sat, 9 May 2026 at 17:25, Willy Sudiarto Raharjo < >>> willysr at slackbuilds.org> wrote: >>> >>>> >Botan is not building for me: >>>> > >>>> >cd . && ln -fs libbotan-3.so.12 libbotan-3.so.12.12.0 >>>> >"/usr/bin/python3" "src/scripts/build_docs.py" --build-dir="build" >>>> > INFO: Starting sphinx-build -q -c src/configs/sphinx -j auto -W >>>> >--keep-going -b html doc build/docs/handbook >>>> >Could not import furo theme; falling back to agago >>>> >/tmp/SBo/Botan-3.12.0/doc/api_ref/pbkdf.rst:173: WARNING: Could not lex >>>> >literal_block as "cpp". Highlighting skipped. >>>> > ERROR: Error running sphinx-build -q -c src/configs/sphinx -j auto -W >>>> >--keep-going -b html doc build/docs/handbook >>>> >make: *** [Makefile:53: build/doc.stamp] Error 1 >>>> >A failure occurred while building Botan: >>>> > Botan.SlackBuild returned non-zero. >>>> >>>> >>>> It built fine on our CI test >>>> https://github.com/SlackBuildsOrg/slackbuilds/pull/15546 >>>> >>>> did you test this on -current or -stable, just to make sure >>>> >>>> >>>> -- >>>> 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/ >> >> _______________________________________________ > 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 fsleg at t-rg.ws Sat May 9 20:54:11 2026 From: fsleg at t-rg.ws (fsLeg) Date: Sat, 09 May 2026 23:54:11 +0300 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: References: <20260509210345.5b6ccc38@home.slackie.org> <20260509232518.7d06484a@home.slackie.org> Message-ID: That's the wrong Sphinx. You need Sphinx, not sphinx. Sphinx is version 5.3.0 and about generating docs, sphinx is version 2.2.11 and is a search engine for databases. On May 9, 2026 23:31:07 GMT+03:00, Luveh Keraph <1.41421 at gmail.com> wrote: >I am at a loss here, because of the following: > >I have three Slackware 15.0 systems. Systems 2 and 3 have no Sphinx >packages installed, whereas in system 1 I have > >sphinx-2.2.11-x86_64-1_SBo >sphinxcontrib-applehelp-2.0.0-x86_64-1_SBo >sphinxcontrib-devhelp-2.0.0-x86_64-1_SBo >sphinxcontrib-htmlhelp-2.1.0-x86_64-1_SBo >sphinxcontrib-jsmath-1.0.1-x86_64-1_SBo >sphinxcontrib-qthelp-2.0.0-x86_64-1_SBo >sphinxcontrib-serializinghtml-2.0.0-x86_64-1_SBo From artourter at gmail.com Sat May 9 21:01:10 2026 From: artourter at gmail.com (Greg Tourte) Date: Sat, 9 May 2026 22:01:10 +0100 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: References: <20260509210345.5b6ccc38@home.slackie.org> <20260509232518.7d06484a@home.slackie.org> Message-ID: Luveh, Does adding the --without-sphinx flag to the configure.py invocation help? Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sat May 9 22:51:46 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 9 May 2026 16:51:46 -0600 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: References: <20260509210345.5b6ccc38@home.slackie.org> <20260509232518.7d06484a@home.slackie.org> Message-ID: None of those systems have any Sphinx packages, with a capital S. On Sat, May 9, 2026 at 2:54?PM fsLeg via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > That's the wrong Sphinx. You need Sphinx, not sphinx. Sphinx is version > 5.3.0 and about generating docs, sphinx is version 2.2.11 and is a search > engine for databases. > > On May 9, 2026 23:31:07 GMT+03:00, Luveh Keraph <1.41421 at gmail.com> wrote: > >I am at a loss here, because of the following: > > > >I have three Slackware 15.0 systems. Systems 2 and 3 have no Sphinx > >packages installed, whereas in system 1 I have > > > >sphinx-2.2.11-x86_64-1_SBo > >sphinxcontrib-applehelp-2.0.0-x86_64-1_SBo > >sphinxcontrib-devhelp-2.0.0-x86_64-1_SBo > >sphinxcontrib-htmlhelp-2.1.0-x86_64-1_SBo > >sphinxcontrib-jsmath-1.0.1-x86_64-1_SBo > >sphinxcontrib-qthelp-2.0.0-x86_64-1_SBo > >sphinxcontrib-serializinghtml-2.0.0-x86_64-1_SBo > _______________________________________________ > 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 Sat May 9 23:50:59 2026 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 9 May 2026 17:50:59 -0600 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: References: <20260509210345.5b6ccc38@home.slackie.org> <20260509232518.7d06484a@home.slackie.org> Message-ID: With that option it builds all right. On Sat, May 9, 2026 at 3:01?PM Greg Tourte wrote: > Luveh, > > Does adding the --without-sphinx flag to the configure.py invocation help? > > Greg > > _______________________________________________ > 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 Sat May 9 23:58:43 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 9 May 2026 19:58:43 -0400 (EDT) Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: References: <20260509210345.5b6ccc38@home.slackie.org> <20260509232518.7d06484a@home.slackie.org> Message-ID: <3dc6389-4ca5-e09d-66a-7b1dc96fcf1c@slackware.uk> On Sat, 9 May 2026, Luveh Keraph wrote: > I am at a loss here, because of the following: > I have three Slackware 15.0 systems. Systems 2 and 3 have no Sphinx packages installed, whereas in system 1 I have? > > sphinx-2.2.11-x86_64-1_SBo > sphinxcontrib-applehelp-2.0.0-x86_64-1_SBo > sphinxcontrib-devhelp-2.0.0-x86_64-1_SBo > sphinxcontrib-htmlhelp-2.1.0-x86_64-1_SBo > sphinxcontrib-jsmath-1.0.1-x86_64-1_SBo > sphinxcontrib-qthelp-2.0.0-x86_64-1_SBo > sphinxcontrib-serializinghtml-2.0.0-x86_64-1_SBo The sphinxcontrib-* packages are Sphinx extensions, but you don't have the core Sphinx installed. That could be what's confusing the build. Try 'removepkg sphinxcontrib-*' and see if that un-confuses it? For some reason, the sphinxcontrib-* builds don't list Sphinx as a dependency... not sure why (since they're Sphinx extensions)? From fourtysixandtwo at sliderr.net Sun May 10 00:58:13 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sat, 9 May 2026 18:58:13 -0600 Subject: [Slackbuilds-users] Updates - 20260509.1 In-Reply-To: <3dc6389-4ca5-e09d-66a-7b1dc96fcf1c@slackware.uk> References: <20260509210345.5b6ccc38@home.slackie.org> <20260509232518.7d06484a@home.slackie.org> <3dc6389-4ca5-e09d-66a-7b1dc96fcf1c@slackware.uk> Message-ID: On Sat, May 9, 2026 at 6:04?PM B. Watson wrote: > > On Sat, 9 May 2026, Luveh Keraph wrote: > > > I am at a loss here, because of the following: > > I have three Slackware 15.0 systems. Systems 2 and 3 have no Sphinx packages installed, whereas in system 1 I have > > > > sphinx-2.2.11-x86_64-1_SBo > > sphinxcontrib-applehelp-2.0.0-x86_64-1_SBo > > sphinxcontrib-devhelp-2.0.0-x86_64-1_SBo > > sphinxcontrib-htmlhelp-2.1.0-x86_64-1_SBo > > sphinxcontrib-jsmath-1.0.1-x86_64-1_SBo > > sphinxcontrib-qthelp-2.0.0-x86_64-1_SBo > > sphinxcontrib-serializinghtml-2.0.0-x86_64-1_SBo > > The sphinxcontrib-* packages are Sphinx extensions, but you don't have > the core Sphinx installed. That could be what's confusing the build. > Try 'removepkg sphinxcontrib-*' and see if that un-confuses it? > > For some reason, the sphinxcontrib-* builds don't list Sphinx as a > dependency... not sure why (since they're Sphinx extensions)?_______________________________________________ Other way around...Sphinx depends on them. But still odd they were added without Sphinx being installed unless the package list above was grepped in a case sensitive way? From chris.willing at linux.com Sun May 10 06:17:30 2026 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 10 May 2026 16:17:30 +1000 Subject: [Slackbuilds-users] Coin, SoQt, Pivy Message-ID: <4ca421bd-8224-4718-90e9-11ab00533f7b@linux.com> The SlackBuilds at development/Coin, development/SoQt and development/Pivy are all required for graphics/FreeCAD (which I maintain). As far as I can tell, they are not directly required by any other SlackBuild. They have not been updated for some years; the current maintainer's most recent entry in the git log was in 2016. I received no reply to emails sent to the maintainer a few years ago about these SlackBuilds. If no one objects in the next few days, I intend to take over maintainership of these SlackBuilds and update them appropriately in time for the next SBo global update. chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at osh.id.au Wed May 13 01:35:07 2026 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 13 May 2026 09:35:07 +0800 Subject: [Slackbuilds-users] updates to signal-desktop In-Reply-To: References: Message-ID: <85bf14f2-5365-40a7-b800-5e3227cafe14@app.fastmail.com> That's been a problem for me too, but how does the glibc in testing actually work? I see from the changelog (2025/09/19) it's got a bunch of packages: testing/packages/binutils-gcc-glibc/aaa_glibc-solibs-2.42-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/binutils-2.45-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/gcc-15.2.0-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/gcc-g++-15.2.0-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/gcc-gcobol-15.2.0-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/gcc-gdc-15.2.0-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/gcc-gfortran-15.2.0-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/gcc-gm2-15.2.0-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/gcc-gnat-15.2.0-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/gcc-go-15.2.0-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/gcc-objc-15.2.0-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/gcc-rust-15.2.0-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/glibc-2.42-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/glibc-i18n-2.42-x86_64-1_slack15.0.txz: Added. testing/packages/binutils-gcc-glibc/glibc-profile-2.42-x86_64-1_slack15.0.txz: Added. Is it as simple as upgradepkg on all of those? No special upgrade order? Thanks, -- Dave On Fri, 8 May 2026, at 1:36 AM, Greg Tourte wrote: > Hi, > > I am getting more and more uncomfortable with not being able to have signal-desktop updated. > > I realise that versions above 8.1 do not work with vanilla stable but they do work with the glibc in the testing folder in -stable (and of course they will work in -current). > > What I am proposing is to have a new signal-desktop-legacy package with the latest version working on -stable without the testing glibc and keep the signal-desktop package fully uptodate and a note in the README file. > > Does this sound acceptable? > > Cheers > > Greg > _______________________________________________ > 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 May 13 02:07:59 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 13 May 2026 09:07:59 +0700 Subject: [Slackbuilds-users] updates to signal-desktop In-Reply-To: <85bf14f2-5365-40a7-b800-5e3227cafe14@app.fastmail.com> References: <85bf14f2-5365-40a7-b800-5e3227cafe14@app.fastmail.com> Message-ID: <20260513090759.231c3820@tuf15.slackie.org> >That's been a problem for me too, but how does the glibc in testing >actually work? I see from the changelog (2025/09/19) it's got a bunch >of packages: > >testing/packages/binutils-gcc-glibc/aaa_glibc-solibs-2.42-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/binutils-2.45-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/gcc-15.2.0-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/gcc-g++-15.2.0-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/gcc-gcobol-15.2.0-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/gcc-gdc-15.2.0-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/gcc-gfortran-15.2.0-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/gcc-gm2-15.2.0-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/gcc-gnat-15.2.0-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/gcc-go-15.2.0-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/gcc-objc-15.2.0-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/gcc-rust-15.2.0-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/glibc-2.42-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/glibc-i18n-2.42-x86_64-1_slack15.0.txz: >Added. >testing/packages/binutils-gcc-glibc/glibc-profile-2.42-x86_64-1_slack15.0.txz: >Added. > >Is it as simple as upgradepkg on all of those? No special upgrade >order? yes, simple upgradepkg but you need to blacklist them in order not to revert the process again if you wish to keep using the newer version otherwise, next time you run slackpkg upgrade-all, you will get the normal version in 15.0 patches, not from testing -- 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 slackbuilds at jerviss.org Wed May 13 13:25:07 2026 From: slackbuilds at jerviss.org (Kyle Jerviss) Date: Wed, 13 May 2026 08:25:07 -0500 Subject: [Slackbuilds-users] UID and GID for ceph package Message-ID: <6a2f108b38c8abd70932268c26703e5b@jerviss.org> I'm working on a package for ceph. ( https://ceph.io/ ) Although the main use of this package will probably be as a client for Slackware VMs connecting to their hosting ProxMox cluster's CephFSs, I'd like the package to be as complete as possible, including maybe the capability of running ceph nodes on Slackware. The various daemons need to run as a user named ceph, in a group named ceph. It looks like 399 is next. From willysr at slackbuilds.org Wed May 13 13:35:49 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 13 May 2026 20:35:49 +0700 Subject: [Slackbuilds-users] UID and GID for ceph package In-Reply-To: <6a2f108b38c8abd70932268c26703e5b@jerviss.org> References: <6a2f108b38c8abd70932268c26703e5b@jerviss.org> Message-ID: <20260513203549.11dc5784@home.slackie.org> >I'm working on a package for ceph. ( https://ceph.io/ ) Although the >main use of this package will probably be as a client for Slackware VMs >connecting to their hosting ProxMox cluster's CephFSs, I'd like the >package to be as complete as possible, including maybe the capability of >running ceph nodes on Slackware. The various daemons need to run as a >user named ceph, in a group named ceph. > >It looks like 399 is next. done -- 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 slackbuilds at jerviss.org Wed May 13 15:25:38 2026 From: slackbuilds at jerviss.org (Kyle Jerviss) Date: Wed, 13 May 2026 10:25:38 -0500 Subject: [Slackbuilds-users] ceph package git question In-Reply-To: <20260513203549.11dc5784@home.slackie.org> References: <6a2f108b38c8abd70932268c26703e5b@jerviss.org> <20260513203549.11dc5784@home.slackie.org> Message-ID: <3bbe9e845800766bd222318675fcdfa2@jerviss.org> While I've got this on my mind... The ceph source tree makes extensive use of git submodules. So much so that I've never managed to track down all of them and assemble them into a buildable source tree. git clone / git checkout handles it flawlessly. Is it allowed to have a package with no download URL and no MD5? On 2026-05-13 08:35, Willy Sudiarto Raharjo wrote: >> I'm working on a package for ceph. ( https://ceph.io/ ) Although the >> main use of this package will probably be as a client for Slackware >> VMs >> connecting to their hosting ProxMox cluster's CephFSs, I'd like the >> package to be as complete as possible, including maybe the capability >> of >> running ceph nodes on Slackware. The various daemons need to run as a >> user named ceph, in a group named ceph. >> >> It looks like 399 is next. > > > done > > > -- > 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 chris.willing at linux.com Wed May 13 23:31:29 2026 From: chris.willing at linux.com (Christoph Willing) Date: Thu, 14 May 2026 09:31:29 +1000 Subject: [Slackbuilds-users] ceph package git question In-Reply-To: <3bbe9e845800766bd222318675fcdfa2@jerviss.org> References: <6a2f108b38c8abd70932268c26703e5b@jerviss.org> <20260513203549.11dc5784@home.slackie.org> <3bbe9e845800766bd222318675fcdfa2@jerviss.org> Message-ID: On 14/5/26 01:25, Kyle Jerviss wrote: > While I've got this on my mind... > > The ceph source tree makes extensive use of git submodules.? So much > so that I've never managed to track down all of them and assemble them > into a buildable source tree.? git clone / git checkout handles it > flawlessly. Have a look at multimedia/obs-studio/get-obs-studio.sh which checks out a git repo, pulls in the submodules and generates a tarball. It specifies a particular git tag and uses that as the VERSION? for the tarball. If you just want the master branch (so no real version number), have a look at system/incus-ui/get-incus-ui.sh which uses the date of last commit and its abbreviated git hash to generate a usable version string. This is based on something I saw in one of Pat's scripts and it works very well. This one doesn't check out submodules but you easily add that like the get-obs-studio.sh script does. Once I have a full source tarball, I upload it to SlackBuildsDirectLinks repo at Sourceforge which can then become the DOWNLOAD url for your .info file. chris From slackbuilds at jerviss.org Thu May 14 00:55:19 2026 From: slackbuilds at jerviss.org (Kyle Jerviss) Date: Wed, 13 May 2026 19:55:19 -0500 Subject: [Slackbuilds-users] ceph package git question In-Reply-To: References: <6a2f108b38c8abd70932268c26703e5b@jerviss.org> <20260513203549.11dc5784@home.slackie.org> <3bbe9e845800766bd222318675fcdfa2@jerviss.org> Message-ID: <045be980206f6861aaffbbef942e2f2a@jerviss.org> I'll check those out. I think the main use will be Slackware VMs in ProxMox VE clusters, so I had intended to keep pace with the releases that ProxMox blesses for production use. 19.2.3 currently. On 2026-05-13 18:31, Christoph Willing wrote: > On 14/5/26 01:25, Kyle Jerviss wrote: >> While I've got this on my mind... >> >> The ceph source tree makes extensive use of git submodules.? So much >> so that I've never managed to track down all of them and assemble them >> into a buildable source tree.? git clone / git checkout handles it >> flawlessly. > > Have a look at multimedia/obs-studio/get-obs-studio.sh which checks out > a git repo, pulls in the submodules and generates a tarball. It > specifies a particular git tag and uses that as the VERSION? for the > tarball. > > If you just want the master branch (so no real version number), have a > look at system/incus-ui/get-incus-ui.sh which uses the date of last > commit and its abbreviated git hash to generate a usable version > string. This is based on something I saw in one of Pat's scripts and it > works very well. This one doesn't check out submodules but you easily > add that like the get-obs-studio.sh script does. > > Once I have a full source tarball, I upload it to > SlackBuildsDirectLinks repo at Sourceforge which can then become the > DOWNLOAD url for your .info file. > > 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 fsleg at t-rg.ws Thu May 14 03:30:13 2026 From: fsleg at t-rg.ws (fsLeg) Date: Thu, 14 May 2026 06:30:13 +0300 Subject: [Slackbuilds-users] ceph package git question In-Reply-To: References: <6a2f108b38c8abd70932268c26703e5b@jerviss.org> <20260513203549.11dc5784@home.slackie.org> <3bbe9e845800766bd222318675fcdfa2@jerviss.org> Message-ID: What about cases where the build process relies on the source tree being a proper git repo as it uses commit history? I have a couple of things (namely, dart-sdk and deltachat-desktop) I can't submit because of this, and I have no desire to tarball the entire git tree. On May 14, 2026 02:31:29 GMT+03:00, Christoph Willing wrote: >On 14/5/26 01:25, Kyle Jerviss wrote: >Have a look at multimedia/obs-studio/get-obs-studio.sh which checks out a git repo, pulls in the submodules and generates a tarball. It specifies a particular git tag and uses that as the VERSION? for the tarball. > >If you just want the master branch (so no real version number), have a look at system/incus-ui/get-incus-ui.sh which uses the date of last commit and its abbreviated git hash to generate a usable version string. This is based on something I saw in one of Pat's scripts and it works very well. This one doesn't check out submodules but you easily add that like the get-obs-studio.sh script does. From list+sbo at vahedi.org Thu May 14 07:00:27 2026 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Thu, 14 May 2026 09:00:27 +0200 Subject: [Slackbuilds-users] ceph package git question In-Reply-To: References: <6a2f108b38c8abd70932268c26703e5b@jerviss.org> <20260513203549.11dc5784@home.slackie.org> <3bbe9e845800766bd222318675fcdfa2@jerviss.org> Message-ID: <1f9993e4-40b5-45fa-af25-c153f87a5ee3@vahedi.org> May 14, 2026 fsLeg via SlackBuilds-users: > What about cases where the build process relies on the source tree being a proper git repo as it uses commit history? What if you have a `git` script that mocks the desired output and you put it in the PATH so it will take precedence over `/usr/bin/git`? Imagine the build process uses: ----------------------------- git rev-list --max-count=1 HEAD ----------------------------- then your got script would be: ----------------------------- cat /path/to/mocking/git #! /bin/sh echo ----------------------------- then, the SlackBuild would have: ----------------------------- export PATH=/path/to/mocking:$PATH ----------------------------- -Shahab From fsleg at t-rg.ws Thu May 14 09:05:56 2026 From: fsleg at t-rg.ws (fsLeg) Date: Thu, 14 May 2026 12:05:56 +0300 Subject: [Slackbuilds-users] ceph package git question In-Reply-To: <1f9993e4-40b5-45fa-af25-c153f87a5ee3@vahedi.org> References: <6a2f108b38c8abd70932268c26703e5b@jerviss.org> <20260513203549.11dc5784@home.slackie.org> <3bbe9e845800766bd222318675fcdfa2@jerviss.org> <1f9993e4-40b5-45fa-af25-c153f87a5ee3@vahedi.org> Message-ID: <339FA3A7-118F-4F0F-BB22-06242415B04E@t-rg.ws> Interesting. And really hacky. I feel like it goes against the principles of Slackware. Also, if the logic is complex enough, which seems to be the case for dart-sdk with several moving parts all of which rely on git, you might end up just reimplementing a rudimentary git. And maintainability is a potential nightmare. I'm not sure I have the skills to write something that wouldn't rely on manual hardcoding of the required values. And what about verifyability? Some random tarball with sources and even blobs (blame Google) from who knows where with no way of verifying its authenticity aside for the random maintainer's word. It's not like various mkvendor and create-tarball scripts work in a reproducible way. On May 14, 2026 10:00:27 GMT+03:00, Shahab Vahedi wrote: >May 14, 2026 fsLeg via SlackBuilds-users: > >> What about cases where the build process relies on the source tree being a proper git repo as it uses commit history? > >What if you have a `git` script that mocks the desired output and you put it in the PATH so it will take precedence over `/usr/bin/git`? From chris.willing at linux.com Thu May 14 10:13:43 2026 From: chris.willing at linux.com (Christoph Willing) Date: Thu, 14 May 2026 20:13:43 +1000 Subject: [Slackbuilds-users] ceph package git question In-Reply-To: <339FA3A7-118F-4F0F-BB22-06242415B04E@t-rg.ws> References: <6a2f108b38c8abd70932268c26703e5b@jerviss.org> <20260513203549.11dc5784@home.slackie.org> <3bbe9e845800766bd222318675fcdfa2@jerviss.org> <1f9993e4-40b5-45fa-af25-c153f87a5ee3@vahedi.org> <339FA3A7-118F-4F0F-BB22-06242415B04E@t-rg.ws> Message-ID: <732bee9a-eb14-4463-9cea-0ac823ec16a8@linux.com> On 14/5/26 19:05, fsLeg via SlackBuilds-users wrote: > Interesting. And really hacky. I feel like it goes against the principles of Slackware. Also, if the logic is complex enough, which seems to be the case for dart-sdk with several moving parts all of which rely on git, you might end up just reimplementing a rudimentary git. And maintainability is a potential nightmare. I'm not sure I have the skills to write something that wouldn't rely on manual hardcoding of the required values. > > And what about verifyability? Some random tarball with sources and even blobs (blame Google) from who knows where with no way of verifying its authenticity aside for the random maintainer's word. It's not like various mkvendor and create-tarball scripts work in a reproducible way. That's why whenever I use a get-*.sh script to generate a tarball to use in a SlackBuild, I keep the script as one of the files in that SlackBuild. Then in the README I mention that this "random maintainer" has used that script to generate the tarball and invite anyone who might think I'm too random to generate their own tarball using the same script. Of course they don't have to use that script; they can make their own arrangements. chris From fourtysixandtwo at sliderr.net Thu May 14 16:30:38 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Thu, 14 May 2026 10:30:38 -0600 Subject: [Slackbuilds-users] ceph package git question In-Reply-To: <732bee9a-eb14-4463-9cea-0ac823ec16a8@linux.com> References: <6a2f108b38c8abd70932268c26703e5b@jerviss.org> <20260513203549.11dc5784@home.slackie.org> <3bbe9e845800766bd222318675fcdfa2@jerviss.org> <1f9993e4-40b5-45fa-af25-c153f87a5ee3@vahedi.org> <339FA3A7-118F-4F0F-BB22-06242415B04E@t-rg.ws> <732bee9a-eb14-4463-9cea-0ac823ec16a8@linux.com> Message-ID: On Thu, May 14, 2026 at 4:13?AM Christoph Willing wrote: > That's why whenever I use a get-*.sh script to generate a tarball to use > in a SlackBuild, I keep the script as one of the files in that > SlackBuild. Then in the README I mention that this "random maintainer" > has used that script to generate the tarball and invite anyone who might > think I'm too random to generate their own tarball using the same > script. Of course they don't have to use that script; they can make > their own arrangements. I do the same as Chris with my rust mkvendored script. I've included it as cargo-mkvendored.sh in cargo-vendor-filterer, then as a stub file in the slackbuilds that use it. But I wasn't happy with that and as of last year, it creates reproducible tarballs with information from https://reproducible-builds.org. So feel free to have a look at it for your own scripts. Cheers From arnaud.garcia-fernandez at laposte.net Thu May 14 20:10:00 2026 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Thu, 14 May 2026 22:10:00 +0200 Subject: [Slackbuilds-users] [hplip-plugin] updated without my say-so, but someone who used my name and email. Message-ID: <20260514221000.7b4e445e7800a0b42416872e@laposte.net> Hi, there's recently been an update sent for hplip-plugin, using the web form, with the name and email I use for my slackbuilds (which are not exactly the ones I use for my pull requests...). I didn't send that update. That update was not warranted, as it effectively breaks hplip usage of its plugin, and printers/scanners will stop working. On a stable slackware-15.0. The update sent was to match the version of hplip used by -current. The main SBo repository is not for -current. Ponce maintains a secondary repository for -current, with updates there: https://github.com/Ponce/slackbuilds.git hplip-plugins needs to be the exact same version as hplip for it to work. I have tested it again before sending that email : a printer or scanner requiring the plugin (I have one at home) will not be installable using a wrong plugin, and will stop working if the plugin is updated (And work again without further ado when the plugin is reverted). Hence this slackbuild shouldn't see any update between releases, except if there is a security update for hplip on -stable branch. Also, after some careful thought, I find that I dislike profoundly that someone used my name and email for an unwarranted update. That is not the way to do things, and even as I know I've been slow lately, even being very (very) long to answer some emails, I have not received any email, request, or whatever, from the person who did that. I would have pointed him on the right direction. And I really hope the person responsible didn't push other unwarranted updates through the web form, which could be a way for a malevolent person to insert a security breach, completely anonymously. - A. From willysr at slackbuilds.org Fri May 15 03:40:36 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 15 May 2026 10:40:36 +0700 Subject: [Slackbuilds-users] [hplip-plugin] updated without my say-so, but someone who used my name and email. In-Reply-To: <20260514221000.7b4e445e7800a0b42416872e@laposte.net> References: <20260514221000.7b4e445e7800a0b42416872e@laposte.net> Message-ID: <20260515104036.53a617ad@home.slackie.org> >Hi, > > there's recently been an update sent for hplip-plugin, using the web >form, with the name and email I use for my slackbuilds (which are not exactly >the ones I use for my pull requests...). > > I didn't send that update. > > That update was not warranted, as it effectively breaks hplip usage of >its plugin, and printers/scanners will stop working. >On a stable slackware-15.0. > >The update sent was to match the version of hplip used by -current. >The main SBo repository is not for -current. >Ponce maintains a secondary repository for -current, with updates there: >https://github.com/Ponce/slackbuilds.git > > hplip-plugins needs to be the exact same version as hplip for it to > work. >I have tested it again before sending that email : a printer or scanner >requiring the plugin (I have one at home) will not be installable using a wrong >plugin, and will stop working if the plugin is updated (And work again without >further ado when the plugin is reverted). > Hence this slackbuild shouldn't see any update between releases, except >if there is a security update for hplip on -stable branch. > > > Also, after some careful thought, I find that I dislike profoundly that >someone used my name and email for an unwarranted update. > > > That is not the way to do things, and even as I know I've been slow >lately, even being very (very) long to answer some emails, I have not received >any email, request, or whatever, from the person who did that. >I would have pointed him on the right direction. >And I really hope the person responsible didn't push other unwarranted updates >through the web form, which could be a way for a malevolent person to insert a >security breach, completely anonymously. I will be more careful about this with the email notification is gone, i have to do things manually and this is why it slipped -- 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 arnaud.garcia-fernandez at laposte.net Fri May 15 18:30:07 2026 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Fri, 15 May 2026 20:30:07 +0200 Subject: [Slackbuilds-users] [hplip-plugin] updated without my say-so, by someone who used my name and email. In-Reply-To: <20260515104036.53a617ad@home.slackie.org> References: <20260514221000.7b4e445e7800a0b42416872e@laposte.net> <20260515104036.53a617ad@home.slackie.org> Message-ID: <20260515203007.805ec05130977ac62f8e7dd0@laposte.net> > I will be more careful about this > with the email notification is gone, i have to do things manually and this is > why it slipped > > -- > Willy Sudiarto Raharjo I am absolutely not blaming anyone here (except the person who impersonated me using the submission form), and you have a lot of work reviewing the submissions and PR, and I commend you for your continuous and efficient work. I am thinking about what could be done to our repository, changing a URL there under the pretense that its more stable, but is pointing to a modified version with security breaches. And all we'll see is that the official maintainer proposed the change and it was approved. Maybe there could be a group effort toward a few modernizations, a bit more security, a better submission process ? Is there any kind of access to a repository containing the website source code ? And could it be improved by the SBo community ? I'm not really pointing toward MFA, or complex overengineered systems, just making things a bit better, like making identity spoofing really difficult. All the while not relying solely on the same peoples. Yth. From lumin+slackbuilds at etherlight.link Fri May 15 22:35:40 2026 From: lumin+slackbuilds at etherlight.link (Lumin Etherlight) Date: Sat, 16 May 2026 01:35:40 +0300 Subject: [Slackbuilds-users] [hplip-plugin] updated without my say-so, by someone who used my name and email. In-Reply-To: <20260515203007.805ec05130977ac62f8e7dd0@laposte.net> (Arnaud via SlackBuilds-users's message of "Fri, 15 May 2026 20:30:07 +0200") References: <20260514221000.7b4e445e7800a0b42416872e@laposte.net> <20260515104036.53a617ad@home.slackie.org> <20260515203007.805ec05130977ac62f8e7dd0@laposte.net> Message-ID: Arnaud via SlackBuilds-users writes: > I am thinking about what could be done to > our repository, changing a URL there under the > pretense that its more stable, but is pointing to > a modified version with security breaches. And > all we'll see is that the official maintainer > proposed the change and it was approved. > > Maybe there could be a group effort toward a > few modernizations, a bit more security, a better > submission process ? I agree. If anyone can publish an update in my name, which may include "supply-chain" attacks, against other Slackware users, then I'd be really weary of having my name on SlackBuilds, lest I get falsely accused of doing the attacks myself. Cryptographic signatures by the private keys of the maintainer is the usual mitigation in other projects as far as I know. If a developer adopts a package, then their key is marked as the only one allowed to push updates to said package. If an admin needs to modify the uploaded update, then the administrator's signature has to be on that update instead. I wonder if current SlackBuild.org policy allows individual maintainers to sign their own updates, by optionally including a signature file in their upload, which gets published to the end users just like any file in the SlackBuild. Users who want to be extra cautious can then validate it to make sure nothing weird is happening. Would my updates be rejected if I do so? At minimum, we need email confirmation sent to the maintainers' address when they make uploads so that their identity is slightly confirmed. Simpler solutions are welcome, if anyone has any :-) Best Regard, Lumin Etherlight From dpross1100 at msn.com Sat May 16 00:46:41 2026 From: dpross1100 at msn.com (Daniel Prosser) Date: Fri, 15 May 2026 20:46:41 -0400 Subject: [Slackbuilds-users] [hplip-plugin] updated without my say-so, by someone who used my name and email. In-Reply-To: Message-ID: An HTML attachment was scrubbed... URL: From andrew.clemons at gmail.com Sat May 16 03:45:45 2026 From: andrew.clemons at gmail.com (Andrew Clemons) Date: Sat, 16 May 2026 12:45:45 +0900 Subject: [Slackbuilds-users] [hplip-plugin] updated without my say-so, by someone who used my name and email. In-Reply-To: References: <20260514221000.7b4e445e7800a0b42416872e@laposte.net> <20260515104036.53a617ad@home.slackie.org> <20260515203007.805ec05130977ac62f8e7dd0@laposte.net> Message-ID: On 2026-05-16 01:35:40 +0300, slackbuilds-users at slackbuilds.org wrote: > Arnaud via SlackBuilds-users > writes: > > > I am thinking about what could be done to > > our repository, changing a URL there under the > > pretense that its more stable, but is pointing to > > a modified version with security breaches. And > > all we'll see is that the official maintainer > > proposed the change and it was approved. > > > > Maybe there could be a group effort toward a > > few modernizations, a bit more security, a better > > submission process ? > > I agree. If anyone can publish an update in > my name, which may include "supply-chain" attacks, > against other Slackware users, then I'd be really > weary of having my name on SlackBuilds, lest I get > falsely accused of doing the attacks myself. > > Cryptographic signatures by the private keys > of the maintainer is the usual mitigation in other > projects as far as I know. If a developer adopts > a package, then their key is marked as the only > one allowed to push updates to said package. If > an admin needs to modify the uploaded update, then > the administrator's signature has to be on that > update instead. > > I wonder if current SlackBuild.org policy > allows individual maintainers to sign their own > updates, by optionally including a signature file > in their upload, which gets published to the end > users just like any file in the SlackBuild. Users > who want to be extra cautious can then validate it > to make sure nothing weird is happening. Would my > updates be rejected if I do so? > > At minimum, we need email confirmation sent > to the maintainers' address when they make uploads > so that their identity is slightly confirmed. > > Simpler solutions are welcome, > if anyone has any :-) Yes just to clarify how this is supposed to work at the moment - no suggestions for improvement right now. For maintainers who regularly submit updates through gitlab or github, the admins know your handles so we _should_ realise when someone else opens an MR or PR for your builds. For submissions through the web form, the email address entered in the form should receive an email and the admins should too. Currently this is not working - Willy has posted about this multiple times, but for whatever reason the people who have access have not been able to fix it. So the admins have the uploaded tarball and see the diff but we don't see the email from the submission form. We can see the details in the DB - Willy can correct me here if I am wrong, but the `sbodb` output contains just the details in the db from the info file (afaik). So when we create the diff, we can only make a commit based on the info file attributing it to the address and name there. This is the problem and the missing link of trust. For people who regularly submit MRs and PRs, if we get a file upload, it is unusual so Willy for example asked about in this case here: https://github.com/SlackBuildsOrg/slackbuilds/pull/15365#issuecomment-4317247780 As Willy mentioned at the start of this thread, it was a mistake not to wait for the answer here. There was nothing concerning in the update - still pointing to upstream etc, just unusual that it came through the submission form. As far supply-chain issues mentioned, the admins are humans so we could make mistakes, but if someone submits an update through the form or even an MR/PR for a build and DOWNLOAD no longer points to upstream, a version is rolled back or the script is doing things it should not, this is a major flag for us to follow up on. But agreed, we do need the emails from the submissions fixed - both for maintainers submitting updates and for the admins cross referencing the details during approval. For maintainers who have access to our git, Willy does final review of those branches when he merges them into his branch for publishing during the weekly update. Other than that approval, we do all our reviews and approvals in the open. You can see them here: https://gitlab.com/SlackBuilds.org/slackbuilds/-/merge_requests and here: https://github.com/SlackBuildsOrg/slackbuilds/pulls including the ones uploaded through the form: e.g: https://github.com/SlackBuildsOrg/slackbuilds/pull/15687 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 870 bytes Desc: not available URL: From andrew.clemons at gmail.com Sat May 16 03:54:16 2026 From: andrew.clemons at gmail.com (Andrew Clemons) Date: Sat, 16 May 2026 12:54:16 +0900 Subject: [Slackbuilds-users] [hplip-plugin] updated without my say-so, by someone who used my name and email. In-Reply-To: References: Message-ID: Daniel, On 2026-05-15 20:46:41 -0400, dpross1100 at msn.com wrote: > Yes, one of my Slackbuilds was apparently updated recently (by a bot or > something?) and it was said to be committed by my GitHub username even though I > had nothing to do with it. I don't have a problem with automatic updates in > some situations if this makes maintenance easier for Willy and team, but I am > not comfortable with being impersonated. It shouldn't have my username on it if > someone else did it. Could you send the sha for this change so we can follow up? I'm not aware of any bots doing updates anywhere. Thanks -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 870 bytes Desc: not available URL: From willysr at slackbuilds.org Sat May 16 04:33:54 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 16 May 2026 11:33:54 +0700 Subject: [Slackbuilds-users] [hplip-plugin] updated without my say-so, by someone who used my name and email. In-Reply-To: References: Message-ID: <20260516113354.6a3582d1@tuf15.slackie.org> >Yes, one of my Slackbuilds was apparently updated recently (by a bot >or something?) and it was said to be committed by my GitHub username >even though I had nothing to do with it. I don't have a problem with >automatic updates in some situations if this makes maintenance easier >for Willy and team, but I am not comfortable with being impersonated. >It shouldn't have my username on it if someone else did it. I sometimes makes a direct changes to some scripts (not particularly on yours Dan, but in general), when i saw some security updates needed or the maintainers is MIA and i know it won't break things. But there are times when i thought it was a minor changes and turns out upstream made a *major* changes and i missed the ChangeLog, so it broke some other scripts. At least we could catch most of build failures asap with our CI, thanks to Andrew's work. Some were not catched because it built fine on CI, especially those bugs that were occurring during runtime, but we could find out when users starts reporting. So my suggestions for those who have knowledge on how to submit an updates via github/gitlab, please do so. At least we can tag your handler directly without having to check the submitter's email. It's easier when everyone is doing updates via github/gitlab and leave the submission form *only* for new scripts. -- 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 May 16 10:01:16 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 16 May 2026 17:01:16 +0700 Subject: [Slackbuilds-users] Updates - 20260516.1 Message-ID: <20260516170116.1e7d4e35@home.slackie.org> Sat May 16 09:40:05 UTC 2026 academic/gpredict: updated for version 2.5.1 academic/nco: Updated for version 5.3.9. academic/python3-scipy: Update for 1.13.1 academic/suitesparse: Enable CUDA academic/units: Updated for version 2.27. audio/reaper: Updated for version 7.72 desktop/nwg-displays: Updated for version 0.4.2. desktop/nwg-hello: Updated for version 0.4.5. desktop/nwg-shell-config: Updated for version 0.5.65. development/Catch2: Updated for version 3.15.0 development/Coin: New maintainer. Updated for version 4.0.7 development/Pivy: New maintainer. Updated for version 0.6.11 development/SoQt: New maintainer. Updated for version 1.6.4 development/aws-cdk: Updated for version 2.1122.0. development/composer: Updated for version 2.9.8 development/dkms: Updated for version 3.4.1 development/efsextract: Added (extract files from SGI CD images). development/eisl: Updated for version 5.66 development/electron-bin: Updated for version 42.0.1 development/goland: Updated for version 2026.1.1. development/google-go-lang: Updated for version 1.26.3. development/got: update to 0.125 development/jupyter_server: Update for 2.18.2 development/mongodb-compass: Updated for version 1.49.7. development/nodejs22: Updated for version 22.22.3. development/nodejs: Updated for version 20.20.2. development/notepad++: Updated for version 8.9.5 development/open-inventor: Added (Scene Graph Library). development/positron: Updated for version 2026.05.2_3. development/sbcl: Updated for version 2.6.4 development/sbt: Updated for version 1.12.11 development/scite: Updated for version 5.6.2. development/terraform: Updated for version 1.15.3. development/tflint: Updated for version 0.62.1. development/tiled: updated for version 1.12.1 development/vstudio: Updated for version 17.4. development/zed-editor-bin: Updated for version 1.1.7. development/zed-editor-bin: Updated for version 1.2.5. development/zizmor: Updated for version 1.25.0. development/zizmor: Updated for version 1.25.1. development/zope.interface: updated for version 8.4 games/Mindustry: updated for version 157.4 games/ags: updated for version 3.6.2.19 games/flare-game: updated for version 1.15 games/flare: updated for version 1.15 games/freeciv: updated for version 3.2.4 gis/eccodes: Updated for version 2.47.0. gis/proj: Updated for version 9.8.1. git/ci: Adjust workflow for large PRs graphics/FreeCAD: Require graphviz, matplotlib ham/gridtracker2: Updated for version 2.260511.0. libraries/MuseScore-Libraries: Updated for version 6.9.3 libraries/canfigger: Updated for version 0.3.2. libraries/double-conversion: Updated for version 3.4.0. libraries/globalqss: Added (Qt Engine). libraries/libcbor: updated for version 0.14.0 libraries/libgit2: Updated for version 1.9.3 libraries/libkiwix: Updated for version 14.2.1. libraries/libzim: Updated for version 9.7.0. libraries/lttng-ust: Updated for version 2.15.0 libraries/md4c: Updated for version 0.5.3. libraries/pam_usb: Updated for version 0.8.7 libraries/pcg-c: Fixes SlackBuild script libraries/qt6: Security fixes for version 6.8.3. libraries/zope.configuration: updated for version 7.1 libraries/zope.event: updated for version 6.2 libraries/zope.proxy: updated for version 7.2 misc/balena-etcher-bin: Updated for version 2.1.6 misc/ollama: Updated for version 0.23.0. misc/open-simh: Updated for version 20260507_0dc9dec multimedia/MuseScore: Updated for version 4.7.0. multimedia/pipe-viewer: Updated for version 0.5.7. multimedia/qprompt: Update README multimedia/rtmpdump: Updated for version 2.6. multimedia/w_scan_cpp: Updated for version 20260515. multimedia/ytdlp-gui: Updated for version 3.3.0 network/NetworkManager-strongswan: Added (StrongSwan for NM). network/amavisd-new: Updated for version 2.14.0. network/amneziawg-go: Updated for version 0.2.18. network/brave-browser: update 1.90.121 network/dnsproxy-bin: Fix MD5SUM. network/dropbear: Updated for version 2026.91. network/element-desktop-bin: Updated for version 1.12.18. network/element-desktop: Updated for version 1.12.18. network/exim: Updated for version 4.99.3. network/helium-browser: Updated for version 0.12.1.1 network/jitsi-meet-desktop: Updated for version 2026.5.0 network/kubectl-bin: Updated for version 1.36.1. network/kubectl: update to 1.36.1 network/librewolf: Updated for version 150.0.3_1 network/opera: Updated for version 131.0.5877.24 network/pwntools: Added (CTF Framework). network/rclone-src: Updated for version 1.74.1 network/signal-desktop: Updated for version 8.10.0. network/slack: Updated for version 4.49.89. network/spamassassin: Updated for version 4.0.2. network/teams-for-linux: Updated for version 2.9.0. network/telegram: Restore telegram icon. network/telegram: Switch to github. network/telegram: Updated for version 6.8.2. network/vivaldi: Updated for version 7.9.3970.67. network/zabbix_agent2: Updated for version 7.0.26. network/zabbix_agentd: Updated for version 7.0.26. network/zabbix_frontend: Updated for version 7.0.26. network/zabbix_java_gateway: Updated for version 7.0.26. network/zabbix_proxy: Updated for version 7.0.26. network/zabbix_server: Updated for version 7.0.26. network/zen-browser: Updated for version 1.19.12b office/Joplin: Updated for version 3.6.13. office/ledger-live: Updated for version 4.2.2 office/miktex: Updated for version 26.5. office/pdfsam-basic: Updated for version 6.0.1. office/qownnotes: Updated for version 26.5.11. office/zk: Added (Note-Taking Assistant). perl/perl-Net-CIDR-Lite: Updated for version 0.24. perl/perl-xml-libxml: Updated for version 2.0210. python/PyPy3: updated for version 7.3.22 python/PyPy: updated for version 7.3.22 python/numexpr: Updated for version 2.14.1 python/pypy3: updated for version 7.3.22 python/pypy: updated for version 7.3.22 python/python2-nuitka: Updated for version 4.1 python/python3-BTrees: updated for version 6.4 python/python3-ZEO: updated for version 6.2 python/python3-ZODB: updated for version 6.3 python/python3-babel: fix when more than one cldr files are in the script directory python/python3-capstone: Fix permission. python/python3-capstone: Updated for version 5.0.7 python/python3-celery: updated for version 5.6.3 python/python3-croniter: updated for version 6.2.2 python/python3-flufl.lock: updated for version 9.1.0 python/python3-gast: Edit README python/python3-maturin: Updated for version 1.13.3. python/python3-nuitka: Updated for version 4.1 python/python3-numba: Updated README python/python3-odfdo: Updated for version 3.22.8 python/python3-pandas: Update for 2.3.3 python/python3-parso: updated for version 0.8.7 python/python3-persistent: updated for version 6.6 python/python3-psycopg2: updated for version 2.9.12 python/python3-pyasn1: updated for version 0.6.3 python/python3-pyjwt: updated for version 2.12.1 python/python3-pypdf: Updated for version 6.11.0 python/python3-pythran: Edit README python/python3-setuptools-git-versioning: Updated for version 3.1.0. python/python3-statsmodels: Update for 0.14.6 python/python3-transaction: updated for version 5.1 python/python3-twisted: updated for version 26.4.0 python/python3-typeguard: Updated for version 4.5.2. python/python3-unicorn: Added (Python Bindings). python/python3-wcwidth: updated for version 0.7.0 python/python3-zodbpickle: updated for version 4.4 ruby/ruby-build: Updated for version 20260512. system/Iosevka-aile: Updated for version 34.5.0. system/Iosevka-core: update to 34.5.0 system/Iosevka-etoile: Updated for version 34.5.0. system/Iosevka-slab: Updated for version 34.5.0 system/Iosevka: Updated for version 34.5.0 system/Lmod: Updated for version 9.2.1. system/apache-tomcat: Updated for version 10.1.55. system/bootterm: Added (Powerful Terminal). system/crun: Added (OCI Container Runtime). system/dosbox-x: updated for version 2026.05.02 system/golangci-lint: Updated for version 2.12.2. system/hplip-plugin: reverted to version 3.20.5 system/jenkins: Updated for version 2.555.2. system/jrnlc: Added (Command Line Journal). system/kbfs: Updated for version 6.6.2. system/kiwix-tools: Updated for version 3.8.2. system/logwatch: Updated for version 7.14. system/mongo-tools: Updated for version 100.17.0. system/nvidia-driver: Fix command. system/postgresql15: Updated for version 15.18. system/postgresql16: Updated for version 16.14. system/postgresql17: Updated for version 17.10. system/postgresql18: Updated for version 18.4. system/postgresql: Updated for version 14.23. system/pv: updated for version 1.10.5 system/redis-py: updated for version 7.4.0 system/sbpkg: Updated for version 2.0.0. system/slackpkg-update-notify: Updated for version 0.3 system/slackrepo-hints: Updated for version 20260515. system/slackrepo: Updated for version 20260516. system/spleen: Added (Bitmap Font). system/usermin: Updated for version 2.540. system/webmin: Updated for version 2.641. system/yelp: Fix security issue. system/ytree: Added (File Manager). system/zim-tools: Updated for version 3.7.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 slackcoder at server.ky Sat May 16 12:04:33 2026 From: slackcoder at server.ky (Slack Coder) Date: Sat, 16 May 2026 07:04:33 -0500 Subject: [Slackbuilds-users] [hplip-plugin] updated without my say-so, by someone who used my name and email. In-Reply-To: <20260516113354.6a3582d1@tuf15.slackie.org> References: <20260516113354.6a3582d1@tuf15.slackie.org> Message-ID: <7b719200-f508-4d31-abae-9dde81790597@server.ky> > It's easier when everyone is doing updates via github/gitlab and leave > the submission form *only* for new scripts. Would cryptographic signatures (GPG) be considered as mentioned earlier?? Its peer-to-peer and avoids adding third party gatekeepers. From willysr at slackbuilds.org Sat May 16 14:41:56 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 16 May 2026 21:41:56 +0700 Subject: [Slackbuilds-users] [hplip-plugin] updated without my say-so, by someone who used my name and email. In-Reply-To: References: <20260514221000.7b4e445e7800a0b42416872e@laposte.net> <20260515104036.53a617ad@home.slackie.org> <20260515203007.805ec05130977ac62f8e7dd0@laposte.net> Message-ID: <20260516214156.363f333f@home.slackie.org> > I wonder if current SlackBuild.org policy > allows individual maintainers to sign their own > updates, by optionally including a signature file > in their upload, which gets published to the end > users just like any file in the SlackBuild. Users > who want to be extra cautious can then validate it > to make sure nothing weird is happening. Would my > updates be rejected if I do so? During development cycle preparing for next SBo repo, we take everyone's work in order to make the script works with latest snapshot of -current changes. That will surely break the workflow if only certain people are allowed to update a script. > At minimum, we need email confirmation sent > to the maintainers' address when they make uploads > so that their identity is slightly confirmed. Yes, this is the easiest way actually, but for now, send updates via github/gitlab is the preferred solution without making any changes to the current workflow. You might be given privileges to run the CI to test your own scripts as well, so double benefits for active maintainers :) -- 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 May 16 15:01:39 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 16 May 2026 22:01:39 +0700 Subject: [Slackbuilds-users] Updates - 20260516.1 In-Reply-To: <20260516170116.1e7d4e35@home.slackie.org> References: <20260516170116.1e7d4e35@home.slackie.org> Message-ID: <20260516220139.4d0c4299@home.slackie.org> >Sat May 16 09:40:05 UTC 2026 I made a mistake during public update and some commits were not reflected on the website (Thanks to Ponce for catching it). I just redo the public update steps and it's on the final stage, so it should be updated by now. If you use git and have pulled from master branch, there's no changes at all. It's just on the web site side of our infrastructure that's changed. If you mirrored SBo repo, you might notice there's been some changes during syncronizing. That's considered normal as those files that were left behind are now properly updated on the website. -- 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 Sat May 16 16:13:28 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sat, 16 May 2026 10:13:28 -0600 Subject: [Slackbuilds-users] Updates - 20260516.1 In-Reply-To: <20260516220139.4d0c4299@home.slackie.org> References: <20260516170116.1e7d4e35@home.slackie.org> <20260516220139.4d0c4299@home.slackie.org> Message-ID: CHECKSUMS.md5.asc hasn't been produced yet...so still isn't done On Sat, May 16, 2026 at 9:01?AM Willy Sudiarto Raharjo wrote: > > >Sat May 16 09:40:05 UTC 2026 > > I made a mistake during public update and some commits were not reflected on > the website (Thanks to Ponce for catching it). > I just redo the public update steps and it's on the final stage, so it should > be updated by now. > > If you use git and have pulled from master branch, there's no changes at > all. It's just on the web site side of our infrastructure that's changed. > If you mirrored SBo repo, you might notice there's been some changes during > syncronizing. That's considered normal as those files that were left behind are > now properly updated on the website. > > -- > 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 rizitis at gmail.com Sun May 17 10:07:34 2026 From: rizitis at gmail.com (=?UTF-8?B?zpnPic6szr3Ovc63z4I=?=) Date: Sun, 17 May 2026 13:07:34 +0300 Subject: [Slackbuilds-users] notifications on mobile phone if submitted via the submission form. Message-ID: Hello, I had an idea about getting notifications on my mobile phone when one of the packages I maintain is submitted via the submission form. The main idea is described here https://gist.github.com/rizitis/37713e51864988f8d1f59ef44f322b9f I have already started implementing it and for this reason all my packages this week whether they are "Update for version" or "Added" will gradually go through the submission form. I will only need the following help from the admins. If there is a possibility this week to move the packages from "/pending/" to https://github.com/SlackBuildsOrg/slackbuilds/pulls a little more often than usual. For me, 1-2 times a day would be ideal, but I understand that this is not always possible... There is no need for anything more, everything else can continue to be done in the usual way and at the usual pace, just that the program to see a package and check if it is "mine" or not must see it /pulls with "label: submission-form" IF the idea works, I think it will be a very useful and free service for anyone interested. Thank you very much for your understanding. From korgie at gmail.com Sun May 17 14:46:46 2026 From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=) Date: Sun, 17 May 2026 17:46:46 +0300 Subject: [Slackbuilds-users] notifications on mobile phone if submitted via the submission form. In-Reply-To: References: Message-ID: 17 ??? 2026, 13:08, ? ??????? ???????? ? ??????: > > ?Hello, I had an idea about getting notifications on my mobile phone I think email notification is enough. 1. I don?t have mobile phone. 2. It?s against the anonymity in the palantir days. 3. Email notification is enough. From willysr at slackbuilds.org Sun May 17 14:57:00 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 May 2026 21:57:00 +0700 Subject: [Slackbuilds-users] Updates - 20260516.1 In-Reply-To: References: <20260516170116.1e7d4e35@home.slackie.org> <20260516220139.4d0c4299@home.slackie.org> Message-ID: <20260517215700.04c1b7ab@home.slackie.org> >CHECKSUMS.md5.asc hasn't been produced yet...so still isn't done Yeah, i left the house and forgot about it it's uploaded by 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 rizitis at gmail.com Sun May 17 15:36:41 2026 From: rizitis at gmail.com (=?UTF-8?B?zpnPic6szr3Ovc63z4I=?=) Date: Sun, 17 May 2026 18:36:41 +0300 Subject: [Slackbuilds-users] notifications on mobile phone if submitted via the submission form. In-Reply-To: References: Message-ID: 1. I don?t have mobile phone: If I could practically live without a cell phone, I would do the same. 2. It?s against the anonymity in the palantir days: Anonymity is not affected at all by using the application, no mobile phone number or any other personal data is needed. You just get a notification in the application in the channel that you have created. It's like having a channel on IRC where you are alone and a hidden repository that you have on github sends you a message there that the foo package that you maintain has just been added to the PR pull and that's it. 3. Email notification is enough. I completely agree. I didn't say that what I'm making should be made official by SBo or replace email. It's a personal effort and IF it works, anyone else can have it IF they want to. All I asked for was a little help from the admins to move the packages from pending to PR github every day so I can debug. IF they want to and if they can, that was all. ???? ??? 17 ??? 2026 ???? 5:46??.?., ?/? ??????? ?????????? ??????: > > > 17 ??? 2026, 13:08, ? ??????? ???????? ? ??????: > > > > ?Hello, I had an idea about getting notifications on my mobile phone > > I think email notification is enough. > > 1. I don?t have mobile phone. > 2. It?s against the anonymity in the palantir days. > 3. Email notification is enough. > _______________________________________________ > 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 lockywolf at lockywolf.net Sun May 17 15:43:59 2026 From: lockywolf at lockywolf.net (Lockywolf) Date: Sun, 17 May 2026 23:43:59 +0800 Subject: [Slackbuilds-users] notifications on mobile phone if submitted via the submission form. In-Reply-To: References: Message-ID: <891DF384-AE92-4469-82AD-A2146D5AD35D@lockywolf.net> I'm just using k9mail on my phone and get notifications via IMAP. On May 17, 2026 11:36:41 PM GMT+08:00, "???????" wrote: >1. I don?t have mobile phone: >If I could practically live without a cell phone, I would do the same. > >2. It?s against the anonymity in the palantir days: >Anonymity is not affected at all by using the application, no mobile >phone number or any other personal data is needed. You just get a >notification in the application in the channel that you have created. >It's like having a channel on IRC where you are alone and a hidden >repository that you have on github sends you a message there that the >foo package that you maintain has just been added to the PR pull and >that's it. > >3. Email notification is enough. >I completely agree. I didn't say that what I'm making should be made >official by SBo or replace email. It's a personal effort and IF it >works, anyone else can have it IF they want to. > > >All I asked for was a little help from the admins to move the packages >from pending to PR github every day so I can debug. >IF they want to and if they can, that was all. > >???? ??? 17 ??? 2026 ???? 5:46??.?., ?/? ??????? ?????????? > ??????: >> >> >> 17 ??? 2026, 13:08, ? ??????? ???????? ? ??????: >> > >> > ?Hello, I had an idea about getting notifications on my mobile phone >> >> I think email notification is enough. >> >> 1. I don?t have mobile phone. >> 2. It?s against the anonymity in the palantir days. >> 3. Email notification is enough. >> _______________________________________________ >> 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 Sun May 17 23:38:57 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 18 May 2026 06:38:57 +0700 Subject: [Slackbuilds-users] notifications on mobile phone if submitted via the submission form. In-Reply-To: References: Message-ID: <20260518063857.478126d2@home.slackie.org> >I will only need the following help from the admins. >If there is a possibility this week to move the packages from >"/pending/" to https://github.com/SlackBuildsOrg/slackbuilds/pulls a >little more often than usual. For me, 1-2 times a day would be ideal, >but I understand that this is not always possible... >There is no need for anything more, everything else can continue to be >done in the usual way and at the usual pace, just that the program to >see a package and check if it is "mine" or not must see it /pulls with >"label: submission-form" I can't really make a promise to do it twice a day Usually i do it on batches, so more like once every 2-3 days :) -- 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: