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: From sbo at linuxgalaxy.org Mon May 18 18:10:56 2026 From: sbo at linuxgalaxy.org (KB_SBo) Date: Mon, 18 May 2026 18:10:56 +0000 Subject: [Slackbuilds-users] polychromatic (0.8.8) does not work with openrazer-daemon (3.12.1) Message-ID: <03aac1f5-0756-4f2a-a8b7-1e7cea82e898@linuxgalaxy.org> Hello, After upgrading stable kernel and rebuilding openrazer-kernel (3.12.1) and openrazer-daemon (3.12.1), polychromatic was no longer able to launch daemon backend: $ polychromatic-cli -l No backends available. The systray app can't find the backend: ------ $ python3 -c "import openrazer.client" Traceback (most recent call last): File "", line 1, in File "/usr/lib64/python3.9/site-packages/openrazer/client/__init__.py", line 4, in from openrazer.client.device_manager import DeviceManager as DeviceManager, DaemonNotFound as DaemonNotFound, __version__ as __version__ File "/usr/lib64/python3.9/site-packages/openrazer/client/device_manager.py", line 5, in from openrazer.client.device import RazerDeviceFactory as _RazerDeviceFactory File "/usr/lib64/python3.9/site-packages/openrazer/client/device.py", line 4, in from openrazer.client.devices import RazerDevice, BaseDeviceFactory File "/usr/lib64/python3.9/site-packages/openrazer/client/devices/__init__.py", line 5, in from openrazer.client.fx import RazerFX as _RazerFX File "/usr/lib64/python3.9/site-packages/openrazer/client/fx.py", line 122, in class RazerFX(BaseRazerFX): File "/usr/lib64/python3.9/site-packages/openrazer/client/fx.py", line 123, in RazerFX advanced: RazerAdvancedFX | None TypeError: unsupported operand type(s) for |: 'type' and 'NoneType' ------ I recompiled everything (all deps, etc) - no build errors. I also have RazerGenie installed (C++ code) which runs correctly with updated openrazer-3.12.1 with no issues. It looks like there was a syntax change incompatible with python3.9. I reverted to openrazer-daemon-3.10.3 which looks like the last version that works with polychromatic-0.8.8 (openrazer-kernel-3.12.1 works with the older daemon: ----- $ polychromatic-cli -l Connected Devices: Name (-n) Form Factor (-d) Serial (-s) Zones (-z) Razer DeathAdder V3 mouse 632343H26900786 main Razer Huntsman V2 keyboard PM2352F58400612 main $ polychromatic-cli --version Polychromatic 0.8.8 Python: 3.9.25 ----- -Ed From willysr at slackbuilds.org Wed May 20 13:24:21 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 20 May 2026 20:24:21 +0700 Subject: [Slackbuilds-users] CI bot access Message-ID: <20260520202421.2be3aa93@home.slackie.org> Hi all i sent a PR to Andrew to add some more active maintainers who are now given access to our CI bot: https://github.com/aclemons/sbo-bot/pull/1807 If your github handler is listed there, well, congrats!! you can now run "@sbo-bot: build category/script" command in the comment section to run the build yourself please don't abuse the CI :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From erich.public at protonmail.com Wed May 20 13:55:55 2026 From: erich.public at protonmail.com (Erich Ritz) Date: Wed, 20 May 2026 13:55:55 +0000 Subject: [Slackbuilds-users] CI bot access In-Reply-To: <20260520202421.2be3aa93@home.slackie.org> References: <20260520202421.2be3aa93@home.slackie.org> Message-ID: Hi Willy, Minor nitpick: rizitis is listed twice. (It already was previously; this MR is no impact on that.) Erich On Wednesday, May 20th, 2026 at 8:24 AM, Willy Sudiarto Raharjo wrote: > Hi all > > i sent a PR to Andrew to add some more active maintainers who are now given > access to our CI bot: https://github.com/aclemons/sbo-bot/pull/1807 > > If your github handler is listed there, well, congrats!! > you can now run "@sbo-bot: build category/script" command in the comment > section to run the build yourself > > please don't abuse the CI :) > > -- > 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 lists at osh.id.au Thu May 21 02:35:16 2026 From: lists at osh.id.au (David O'Shaughnessy) Date: Thu, 21 May 2026 10:35:16 +0800 Subject: [Slackbuilds-users] Slackware Community Forge Message-ID: <02302e54-c7d2-42f6-8751-036735b140a4@app.fastmail.com> Sorry if this has been discussed before, but has there been any talk of making use of the new Slackware Community Forge (some more info here )? I know some people would prefer not to use GitHub, and SCF looks like a great alternative. Any plans to make use of it for SBo? Thanks, -- Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Thu May 21 13:14:25 2026 From: dickson.tim at googlemail.com (Tim Dickson) Date: Thu, 21 May 2026 14:14:25 +0100 Subject: [Slackbuilds-users] Slackware Community Forge In-Reply-To: <02302e54-c7d2-42f6-8751-036735b140a4@app.fastmail.com> References: <02302e54-c7d2-42f6-8751-036735b140a4@app.fastmail.com> Message-ID: <7ff992d7-ef03-4424-88b2-cf13d68e65b0@googlemail.com> thanks for the heads up. I used to get email notifications of new posts on alien bob's blog, but it doesn't seem to be working so I missed that. regards, Tim From willysr at slackbuilds.org Sat May 23 11:09:27 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 23 May 2026 18:09:27 +0700 Subject: [Slackbuilds-users] Updates - 20260523.1 Message-ID: <20260523180927.70659292@home.slackie.org> Sat May 23 10:48:16 UTC 2026 academic/aeskulap: Trim README blank line. academic/dwave-greedy: Trim README blank line. academic/gaiasky: Trim README blank line. academic/gdstk: Trim README blank line. academic/gem5: Trim README blank line. academic/h5utils: Fix README. academic/harminv: Trim README blank line. academic/itex2mml: Trim README blank line. academic/maxima: Trim README blank line. academic/meep: Trim README blank line. academic/scilab: Trim README blank line. academic/suitesparse: Trim README blank line. academic/xschem: Updated for version 3.4.7. accessibility/blugon: Trim README blank line. audio/JDSP4Linux: Trim README blank line. audio/Luppp: Trim README blank line. audio/callaudiod: Trim README blank line. audio/gnome-music: Trim README blank line. audio/mp3wrap: Trim README blank line. audio/ncspot: Updated for version 1.3.4. audio/ntk: Trim README blank line. audio/ogmtools: Trim README blank line. audio/reaper: Updated for version 7.73 audio/retrovol: Trim README blank line. desktop/ComixCursors: Trim README blank line. desktop/ambiance-radiance-flat-colors-gtk-theme: Add "set -e". desktop/budgie-screensaver: Trim README blank line. desktop/calls: Trim README blank line. desktop/cutefish-core: Trim README blank line. desktop/cutefish-dock: Fix URL (double slash). desktop/cutefish-dock: Trim README blank line. desktop/cutefish-gtk-themes: Trim README blank line. desktop/cutefish-launcher: Trim README blank line. desktop/cutefish-screenlocker: Trim README blank line. desktop/cutefish-settings: Trim README blank line. desktop/cutefish-statusbar: Trim README blank line. desktop/cutefish-wallpapers: Trim README blank line. desktop/domterm: Trim README blank line. desktop/ee: update to 1.5.2 desktop/gdm: Trim README blank line. desktop/gnome-browser-connector: Trim README blank line. desktop/gnome-clocks: Trim README blank line. desktop/gnome-connections: Trim README blank line. desktop/gnome-contacts: Trim README blank line. desktop/gnome-font-viewer: Trim README blank line. desktop/gnome-shell-extension-appindicator: Trim README blank line. desktop/gnome-shell: Trim README blank line. desktop/gnome-tour: Trim README blank line. desktop/happy-hacking-gnu: Trim README blank line. desktop/herbe: Trim README blank line. desktop/i3ipc-glib: Fix README. desktop/kbdd: Trim README blank line. desktop/mint-themes: Trim README blank line. desktop/mugshot: Trim README blank line. desktop/nwg-displays: Updated for version 0.4.3. desktop/nwg-look: Updated for version 1.1.1. desktop/nwg-panel: Updated for version 0.10.15. desktop/progman: Trim README blank line. desktop/qtpass: Updated for version 1.7.0. desktop/river: Fix README. desktop/slstatus: Trim README blank line. desktop/slstatus: update to 1.1 desktop/sun: Trim README blank line. desktop/sushi: Trim README blank line. desktop/swayidle: Trim README blank line. desktop/vinagre: Trim README blank line. desktop/wbar: Trim README blank line. desktop/xapp-symbolic-icons: Updated for version 1.1.0 desktop/xfce4-battery-plugin: Trim README blank line. desktop/xfce4-i3-workspaces-plugin: Trim README blank line. desktop/xfdashboard: Trim README blank line. development/Kiro: Updated for version 0.12.200. development/android-studio: Trim README blank line. development/android-tools: Trim README blank line. development/apache-maven: Updated for version 3.9.16. development/aspnetcore-runtime-10.0: Updated for version 10.0.8. development/aspnetcore-runtime-8.0: Updated for version 8.0.27. development/aspnetcore-runtime-9.0: Updated for version 9.0.16. development/aws-cdk: Updated for version 2.1124.1. development/bcc: Trim README blank line. development/bluefish: Fix README. development/bun-bin: Trim README blank line. development/bun-bin:update to version 1.3.14 development/casperjs: Fix URL (double slash). development/cim: Trim README blank line. development/critcl: Trim README blank line. development/cudatoolkit_12.6: Removed (at maintainer's request). development/cudatoolkit_12: Remove gcc14 dependence. Fix pkgconfig development/cudatoolkit_13: Fix pkgconfig entries development/cudnn: New maintainer. Add samples & pkgconfig file. development/datagrip: Trim README blank line. development/deno-bin: Trim README blank line. development/diffoscope: updated for version 318 development/dkms: Trim README blank line. development/dotnet-runtime-10.0: Updated for version 10.0.8. development/dotnet-runtime-8.0: Updated for version 8.0.27. development/dotnet-runtime-9.0: Updated for version 9.0.16. development/dotnet-sdk-10.0: Updated for version 10.0.300. development/dotnet-sdk-8.0: Updated for version 8.0.421. development/dotnet-sdk-9.0: Updated for version 9.0.314. development/dub: Updated for version 1.41.0. development/eisl: Fix README. development/electron-bin: Updated for version 42.1.0 development/fortitude-bin: Updated for version 0.9.0. development/gedit: Fix README. development/gerbil: Trim README blank line. development/ghidra: Updated for version 12.1 development/gnome-builder: Trim README blank line. development/gopls: Updated for version 0.22.0. development/gputils: Trim README blank line. development/hoppscotch: Updated for version 26.4.1. development/icecream-sundae: Trim README blank line. development/lm-studio-bin: Trim README blank line. development/lm-studio-bin: Updated for version 0.4.14.4. development/meld: Add missing "set -e". development/metakit: Trim README blank line. development/newlisp: Trim README blank line. development/nodeenv: Fix README. development/nodejs24-bin: Trim README blank line. development/notepad++: Updated for version 8.9.6 development/p4: Fix md5sums. development/p4d: Fix md5sums. development/p4v: Trim README blank line. development/polyml: Trim README blank line. development/pulsar: Trim README blank line. development/python3-hylang: Trim README blank line. development/python3-numpy-legacy: Trim README blank line. development/python3-numpy: Trim README blank line. development/python3-numpy: Updated README development/quickjs: Trim README blank line. development/rebar3: Trim README blank line. development/sccache: Added (shared compilation cache). development/schroot: Trim README blank line. development/sourcegit: Updated for version 2026.11 development/sysprof: Trim README blank line. development/terraform: Updated for version 1.15.4 development/tkcon: Trim README blank line. development/ttk-themes: Trim README blank line. development/vala-language-server: Trim README blank line. development/valgrind: Updated for version 3.27.1. development/vscode-bin: Updated for version 1.121.0. development/vstudio: Updated for version 17.4.1 development/xmake: Updated for version 3.0.9. development/zed-editor-bin: Updated for version 1.3.5. development/zed-editor-bin: Updated for version 1.3.6. development/zile: Trim README blank line. development/zizmor: Updated for version 1.25.2. development/zope.sqlalchemy: Trim README blank line. games/bluemoon: Trim README blank line. games/dfarc: Trim README blank line. games/endgame-singularity: Trim README blank line. games/fheroes2: Updated for version 1.1.16. games/fillets-ng-data: Trim README blank line. games/firestorm-opensim: Trim README blank line. games/fortune-dharma: Trim README blank line. games/freedink: Trim README blank line. games/gnugo: Trim README blank line. games/hnefatafl: Trim README blank line. games/ppsspp: Updated for version 1.20.4. games/protonup: Trim README blank line. games/puzzles: Updated for version 20260410.06e37f1. games/rocksndiamonds: Trim README blank line. games/vegastrike: Trim README blank line. games/vkBasalt: Trim README blank line. games/yamagi-quake2: Updated for version 8.70. gis/python3-netcdf4-python: Trim README blank line. graphics/Blender: Improved CUDA support graphics/OpenCASCADE: Fix 32bit build graphics/OpenSubdiv: Trim README blank line. graphics/amide: Fix README. graphics/converseen: Updated for version 0.15.2.4. graphics/dblatex: Trim README blank line. graphics/libplacebo: Trim README blank line. graphics/pdfsyntax: Trim README blank line. graphics/posterazor: Fix README. graphics/scrot: Clean up build. graphics/ueberzugpp: Updated for version 2.9.10. graphics/veles: Removed (Upstream archived) graphics/xfishtank: Trim README blank line. graphics/xnap: Trim README blank line. ham/js8call: Trim README blank line. ham/sdrangel: Updated for version 7.25.1. ham/sdrplay_apiService: Trim README blank line. haskell/cabal-install: Trim README blank line. libraries/OpenSceneGraph: Trim README blank line. libraries/PrettyTable: Trim README blank line. libraries/VTK: Trim README blank line. libraries/bsddialog: Trim README blank line. libraries/ceres-solver: Fix README. libraries/cppzmq: Trim README blank line. libraries/cutefish-kwin-plugins: Trim README blank line. libraries/cyrus-timezones: Trim README blank line. libraries/geshi: Trim README blank line. libraries/gom: Trim README blank line. libraries/grilo-plugins: Trim README blank line. libraries/grilo: Trim README blank line. libraries/grpc: Add abseil-cpp as dep. libraries/grpc: Update for 1.80.0 libraries/gupnp-av: Trim README blank line. libraries/gupnp-dlna: Trim README blank line. libraries/highway: Trim README blank line. libraries/jsonrpc-glib: Trim README blank line. libraries/lib3mf: Trim README blank line. libraries/libavif:update to version 1.4.1 libraries/libctl: Trim README blank line. libraries/libcurl-gnutls: Fix README. libraries/libevtx: Trim README blank line. libraries/libfprint: Trim README blank line. libraries/libgedit-amtk: Trim README blank line. libraries/libgit2: Updated for version 1.9.4 libraries/libgnomekbd: Trim README blank line. libraries/libgrss: Trim README blank line. libraries/libldm: Fix README. libraries/libmediaart: Trim README blank line. libraries/librdkafka: Added (Standalone C Library). libraries/librime: Trim README blank line. libraries/librist:update to version 0.2.15 libraries/libspiro: Trim README blank line. libraries/libticalcs2: Trim README blank line. libraries/libxc: Trim README blank line. libraries/libxdg-basedir: Trim README blank line. libraries/libxmlb: Updated for version 0.3.27. libraries/libzia: Trim README blank line. libraries/microsoft-gsl: Updated for version 4.2.2. libraries/mlt-bindings: Trim README blank line. libraries/nDPI: Fix README. libraries/nvidia-vaapi-driver: Trim README blank line. libraries/openimagedenoise: Trim README blank line. libraries/pam_usb: Updated for version 0.9.0 libraries/posixsignalmanager: Trim README blank line. libraries/ptex: Trim README blank line. libraries/pylibpcap: Trim README blank line. libraries/qwt: Trim README blank line. libraries/simdjson: Trim README blank line. libraries/simdjson:update to version 4.6.4 libraries/simdutf: Trim README blank line. libraries/sofia-sip: Trim README blank line. libraries/srt: Trim README blank line. libraries/tclsoap: Trim README blank line. libraries/template-glib: Trim README blank line. libraries/tepl: Trim README blank line. libraries/tksvg: Fix README. libraries/totem-pl-parser: Trim README blank line. libraries/tree-sitter: Updated for version 0.26.9 libraries/tuiwidgets: Trim README blank line. misc/cups-pk-helper: Trim README blank line. misc/exploitdb: Trim README blank line. misc/fcitx5-gtk: Trim README blank line. misc/fcitx5-mozc: Trim README blank line. misc/fcitx5: Trim README blank line. misc/gnome-user-docs: Trim README blank line. misc/ibus-rime: Trim README blank line. misc/libime: Trim README blank line. misc/moodbar: Trim README blank line. misc/nuclei: Trim README blank line. misc/ollama: Updated for version 0.24.0. misc/pam-u2f: Trim README blank line. misc/rmlint: Trim README blank line. misc/xhidecursor: Trim README blank line. multimedia/MuseScore: Updated for version 4.7.1 multimedia/RenameMyTVSeries: Trim README blank line. multimedia/amarok: Trim README blank line. multimedia/droidcam: Trim README blank line. multimedia/ffmpegfs: Trim README blank line. multimedia/gnome-video-effects: Trim README blank line. multimedia/gstreamer-vaapi: Trim README blank line. multimedia/haruna: Trim README blank line. multimedia/mpv: Trim README blank line. multimedia/nrg2iso: Trim README blank line. multimedia/plexmediaserver: Updated for version 1.43.2.10687_563d026ea. multimedia/pocketsphinx:update to version 5.1.0 multimedia/qprompt: Trim README blank line. multimedia/rygel: Trim README blank line. multimedia/svt-av1:update to version 4.1.0 multimedia/totem: Trim README blank line. multimedia/tsduck: Updated for version 3.40.4165. multimedia/uavs3e: Trim README blank line. multimedia/vokoscreenNG-QT5: Trim README blank line. network/AdGuardHome: Updated for version 0.107.76. network/DownTube: Trim README blank line. network/acme.sh: Trim README blank line. network/asuka: Trim README blank line. network/brave-browser: update 1.90.122 network/castor: Trim README blank line. network/chawan: updated for version 0.4.0 network/cloudflared-bin: Updated for version 2026.5.0. network/cmst: Trim README blank line. network/copyparty: updated for version 1.20.14 network/curl-quic: Trim README blank line. network/darkhttpd: Trim README blank line. network/ddclient: Trim README blank line. network/deskflow: Trim README blank line. network/dino: Trim README blank line. network/dnsproxy-bin: Updated for version 0.81.4. network/dooble: Updated for version 2026.05.15 network/dropbox: Updated for version 252.4.3485. network/epiphany: Trim README blank line. network/fdns: Trim README blank line. network/firehol: Trim README blank line. network/floorp-bin: Trim README blank line. network/floorp-bin: Updated for version 12.14.2. network/gnome-remote-desktop: Trim README blank line. network/gnome-user-share: Trim README blank line. network/haproxy: Updated for version 3.2.19. network/helium-browser: Updated for version 0.12.3.1 network/ipvsadm: Trim README blank line. network/landrun: Trim README blank line. network/librewolf: Updated for version 151.0_1 network/mblaze: update to 1.4 network/memcached: Updated for version 1.6.42. network/microsoft-edge: Updated for version 148.0.3967.70. network/mullvad-browser: Updated for version 15.0.14 network/mumble: Trim README blank line. network/ngrok: Updated for version 3.39.2 network/nordvpn-gui: Updated for version 4.6.0. network/nordvpn: Updated for version 4.6.0. network/opera: Updated for version 131.0.5877.55 network/putty: Updated for version 0.84. network/rclone: update 1.74.1 network/repology-cli: Updated for version 20260520. network/signal-desktop: Updated for version 8.11.0. network/snac2: Trim README blank line. network/syncthingtray-bin: Updated for version 2.1.0. network/tailscale: update 1.98.2 network/tixati: Trim README blank line. network/tor-browser: Updated for version 15.0.14. network/unbound: Updated for version 1.25.1. network/urlwatch: Trim README blank line. network/vivaldi: Updated for version 8.0.4033.28. network/waterfox: Updated for version 6.6.13 network/wireshark: Updated for version 4.6.6. network/xmrig: Trim README blank line. network/zabbix_frontend: Trim README blank line. network/zen-browser: Updated for version 1.19.13b network/zoom-linux: Updated for version 7.0.5.3034 office/PortfolioPerformance-bin: Trim README blank line. office/batdoc-bin: Updated for version 1.4.0. office/catdvi: Trim README blank line. office/csbooks-bin: Updated for version 9.0.0. office/ding: Trim README blank line. office/hebcal: Trim README blank line. office/hunspell-russian-aot: Trim README blank line. office/hunspell-russian-kliukvin: Fix README. office/ispell-dict-russian-lebedev: Trim README blank line. office/ledger-live: Updated for version 4.4.0 office/notes: Trim README blank line. office/onlyoffice-desktopeditors: Updated for version 9.4.0 office/openoffice.org: Trim README blank line. office/qownnotes: Updated for version 26.5.14. office/tnote: Trim README blank line. office/vzic: Trim README blank line. office/wps-office-dicts: Updated for version 26.2.4.1 office/zk: Trim README blank line. perl/perl-Archive-Zip: Trim README blank line. perl/perl-Class-Factory-Util: Trim README blank line. perl/perl-DBD-Pg: Updated for version 3.20.2. perl/perl-Digest-SHA-PurePerl: Trim README blank line. perl/perl-File-Download: Trim README blank line. perl/perl-Getopt-Long-Descriptive: Trim README blank line. perl/perl-Git-Sub: Trim README blank line. perl/perl-IO-Multiplex: Trim README blank line. perl/perl-IPC-DirQueue: Trim README blank line. perl/perl-Image-Size: Trim README blank line. perl/perl-Log-Log4perl: Trim README blank line. perl/perl-Module-Build-XSUtil: Trim README blank line. perl/perl-Mojolicious: Updated for version 9.43. perl/perl-Net-SSH: Trim README blank line. perl/perl-PPI: Trim README blank line. perl/perl-Proc-ProcessTable: Trim README blank line. perl/perl-Regexp-Common: Trim README blank line. perl/perl-Role-Tiny: Updated for version 2.002005. perl/perl-System-Command: Trim README blank line. perl/perl-System-Sub: Trim README blank line. perl/perl-Task-Weaken: Trim README blank line. perl/perl-UUID: Trim README blank line. perl/perl-gstreamer: Trim README blank line. perl/perl-html-tagset: Trim README blank line. perl/perl-net-ip: Trim README blank line. python/buildbot-badges: Trim README blank line. python/dpkt: Trim README blank line. python/feedparser: Trim README blank line. python/flake8: Trim README blank line. python/holidays: Trim README blank line. python/homebase: Trim README blank line. python/humanize: Trim README blank line. python/insipid-sphinx-theme: Trim README blank line. python/internetarchive: Updated for version 5.8.0. python/pyatspi: Trim README blank line. python/pycodestyle: Trim README blank line. python/pyfiglet: Trim README blank line. python/python-debian: Trim README blank line. python/python2-lockfile: Trim README blank line. python/python2-morbid: Trim README blank line. python/python2-pathlib2: Trim README blank line. python/python2-uuid: Fix README. python/python3-application: Fix README. python/python3-authheaders: Trim README blank line. python/python3-cachetools: Trim README blank line. python/python3-cffsubr:update to version 0.4.0 python/python3-compreffor:update to version 0.6.0 python/python3-desktop-notify: Trim README blank line. python/python3-dotenv: Trim README blank line. python/python3-filelock: Trim README blank line. python/python3-fontmake:update to version 3.11.1 python/python3-fonttools:update to version 4.63.0 python/python3-glad: Trim README blank line. python/python3-glyphslib:update to version 6.13.1 python/python3-gnutls: Trim README blank line. python/python3-grpcio: Update for 1.80.0 python/python3-h11: Trim README blank line. python/python3-jaconv:update to version 0.5.0 python/python3-json5: Updated for version 0.14.0. python/python3-klepto: Trim README blank line. python/python3-klepto:update to version 0.2.8 python/python3-langcodes: Trim README blank line. python/python3-langcodes:update to version 3.5.1 python/python3-language-data: update to version 1.4.0 python/python3-lockfile: Trim README blank line. python/python3-marisa-trie: Trim README blank line. python/python3-marisa_trie:update to version 1.4.1 python/python3-mat2: Trim README blank line. python/python3-multivolumefile: Trim README blank line. python/python3-narwhals: Update README python/python3-opencv: Trim README blank line. python/python3-openstep-plist:update to version 0.5.2 python/python3-otr: Trim README blank line. python/python3-outcome: Trim README blank line. python/python3-pathlib2: Trim README blank line. python/python3-pipx:update to version 1.11.1 python/python3-pmw: Trim README blank line. python/python3-pox: Trim README blank line. python/python3-pox:update to version 0.3.7 python/python3-progress: Trim README blank line. python/python3-pyflakes: Trim README blank line. python/python3-pypdf: Updated for version 6.12.0 python/python3-pytest-cov: Trim README blank line. python/python3-pytube: Trim README blank line. python/python3-reportlab:update to version 4.5.1 python/python3-rfc3986: Trim README blank line. python/python3-schedule: Trim README blank line, fix .info. python/python3-setuptools-git-versioning: Trim README blank line. python/python3-simple-term-menu: Trim README blank line. python/python3-sipclients3: Fix README. python/python3-tinydb: Trim README blank line. python/python3-trio: Trim README blank line. python/python3-trove-classifiers: Updated for version 2026.5.22.10. python/python3-ufo2ft:update to version 3.7.3 python/python3-ujson: Trim README blank line. python/python3-userpath: Trim README blank line. python/python3-xapp: Updated for version 3.0.3 python/python3-zeroconf: Change source download to pypi, fix MD5SUM python/python3-zeroconf: Fix rdlength overrun security vulnerability python/python3-zeroconf: Update README python/scikit-umfpack: Clean up build. python/sphinx-autobuild: Trim README blank line. python/sphinxcontrib-asyncio: Trim README blank line. python/sphinxcontrib-fulltoc: Trim README blank line. python/termcolor: Trim README blank line. ruby/wisper: Trim README blank line. system/B-em: Updated for version 20260521_05e762b system/Iosevka-aile: Updated for version 34.6.0. system/Iosevka-core: Trim README blank line. system/Iosevka-etoile: Updated for version 34.6.0. system/IoskeleyMono: Added (Monospace Font). system/Lmod: Updated for version 9.2.2. system/PeaZip: Updated for version 11.1.0. system/android-udev-rules: Updated for version 2026.04.23. system/blocaled: Trim README blank line. system/brother-hll2400d-cups: Trim README blank line. system/bzip3: Fix README. system/corectrl: Trim README blank line. system/cpuinfo: Trim README blank line. system/daemonize: Trim README blank line. system/docker-buildx: Updated for version 0.34.0. system/docker-buildx: Updated for version 0.34.1. system/dracut: updated for version 111 system/eaglemode: Trim README blank line. system/em: Trim README blank line. system/epson-printer-utility: Trim README blank line. system/extundelete: Trim README blank line. system/flexbackup: Trim README blank line. system/fq-bin: Added (Binary data decoders). system/fr: Trim README blank line. system/fzf-bin: Trim README blank line. system/gnome-color-manager: Trim README blank line. system/gyre-fonts: Trim README blank line. system/heatshrink: Trim README blank line. system/ibus-typing-booster: Trim README blank line. system/libcloudproviders: Trim README blank line. system/libertinus-fonts: Fix README. system/mbuffer: updated for version 20260511 system/memory-editor: Trim README blank line. system/memuse: Trim README blank line. system/mtm: Trim README blank line. system/mucommander: Trim README blank line. system/openrazer-daemon: Updated for version 3.12.2. system/openrazer-kernel: Updated for version 3.12.2. system/openzfs: upgraded for version 2.4.2 system/otf-ibm-plex: Fix URL (double slash). system/oxker-bin: Updated for version 0.13.2. system/pass-otp: fix mandir system/pcp: Trim README blank line. system/pipes.sh: Trim README blank line. system/polychromatic: Trim README blank line. system/qemu-static: Trim README blank line. system/ranger: Fix DOWNLOAD & MD5SUM. system/ranger: Trim README blank line. system/rhvoice: Trim README blank line. system/sbo-create: Updated for version 2.3.1. system/sbo-maintainer-tools: Updated for version 0.9.5. system/sbpkg: Updated for version 2.0.1. system/sensord: Trim README blank line. system/set_rlimits: Trim README blank line. system/slackpkg-update-notify: Updated for version 1.0. system/slackrepo-hints: Updated for version 20260523. system/slackrepo: Updated for version 20260523. system/sleepd: Trim README blank line. system/slpkg: Updated for version 6.1.6. system/ttf-babelstone-latin: Trim README blank line. system/ttf-babelstone-tibetan: Trim README blank line. system/ttf-ibm-plex: Fix URL (double slash). system/ttf-sakalbharati: Trim README blank line. system/ttygif: Trim README blank line. system/unigine-heaven-benchmark: Trim README blank line. system/update-initrd: Trim README blank line. system/volatility3: Trim README blank line. system/watch-fs: Trim README blank line. system/waydroid: Trim README blank line. system/witr: Updated for version 0.3.2. system/xbattmon: Trim README blank line. system/xdg-desktop-portal-gnome: Trim README blank line. system/xosview: Fix README. system/yaze-ag: Trim README blank line. system/yelp: Trim README blank line. +--------------------------+ -- 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 bdiego at pm.me Sat May 23 15:51:40 2026 From: bdiego at pm.me (Diego Borghetti) Date: Sat, 23 May 2026 15:51:40 +0000 Subject: [Slackbuilds-users] Remove pending neovim.tar.gz Message-ID: Hi, Can the pending neovim.tar.gz be remove/cancel please? I forgot to update one of the files during the process. I have another .tar.gz ready for submission. Cheers, Diego From urchlay at slackware.uk Sat May 23 17:37:41 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 23 May 2026 13:37:41 -0400 (EDT) Subject: [Slackbuilds-users] Remove pending neovim.tar.gz In-Reply-To: References: Message-ID: <9ab5cd7-7765-991e-b657-952c6dca19a@slackware.uk> On Sat, 23 May 2026, Diego Borghetti via SlackBuilds-users wrote: > Can the pending neovim.tar.gz be remove/cancel please? Would that be the "Updated for version 0.12.0." one, dated April 17? It's already been merged. Although it doesn't pass sbolint, so I'm not sure why it was merged... From bdiego at pm.me Sat May 23 17:52:44 2026 From: bdiego at pm.me (Diego Borghetti) Date: Sat, 23 May 2026 17:52:44 +0000 Subject: [Slackbuilds-users] Remove pending neovim.tar.gz In-Reply-To: <9ab5cd7-7765-991e-b657-952c6dca19a@slackware.uk> References: <9ab5cd7-7765-991e-b657-952c6dca19a@slackware.uk> Message-ID: No, it was today upload 0.12.2. It's in the pending queue at the moment. I just spot and fixed the issue with sbolint (url for luajit), so just need that pending remove to submit again. Cheers, Diego On Saturday, May 23rd, 2026 at 6:37 PM, B. Watson wrote: > > > On Sat, 23 May 2026, Diego Borghetti via SlackBuilds-users wrote: > > > Can the pending neovim.tar.gz be remove/cancel please? > > Would that be the "Updated for version 0.12.0." one, dated > April 17? It's already been merged. > > Although it doesn't pass sbolint, so I'm not sure why it > was merged... > From urchlay at slackware.uk Sat May 23 18:20:15 2026 From: urchlay at slackware.uk (B. Watson) Date: Sat, 23 May 2026 14:20:15 -0400 (EDT) Subject: [Slackbuilds-users] Remove pending neovim.tar.gz In-Reply-To: References: <9ab5cd7-7765-991e-b657-952c6dca19a@slackware.uk> Message-ID: On Sat, 23 May 2026, Diego Borghetti wrote: > No, it was today upload 0.12.2. It's in the pending queue at the moment. > > I just spot and fixed the issue with sbolint (url for luajit), so just need that pending remove to submit again. OK, removed from pending. From milgram at cgpp.com Sun May 24 22:40:48 2026 From: milgram at cgpp.com (J. Milgram) Date: Sun, 24 May 2026 18:40:48 -0400 Subject: [Slackbuilds-users] sbotools: multiline build options Message-ID: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> Dumb question. Where I see something like this in a Slackbuild README: ========= Add the following before the python3 build commands in your Slackbuild to use this version over the stock one in 15.0: PYVER=$(python3 -c 'import sys; print("%d.%d" % sys.version_info[:2])') export PYTHONPATH=/opt/python$PYVER/site-packages ========= ... sboinstall and sboupgrade will say "It looks like python3-setuptools-opt has options; would you like to set any when the slackbuild is run?" All good. I say "y" and then the question is how to type this in. First, I presume it's entered without the "export" builtin: PYVER= PYTHONPATH=/opt/python$PYVER/site-packages ... Else I get a "not a valid identifier" bash error apparently due to the script attempting: "export PYTHONPATH= foo.Slackbuild" and there's no "foo.Slackbuild" to export. Other question is, how to enter the lines at the sboinstall prompt: one at a time, separated by , or both in one line, separated by a semicolon? I've been "cheating" and entering only the second line, as PYTHONPATH=/opt/python3.9/site-packages, because I know I'm running 3.9. However, still curious how multiline input is envisioned to work. thanks! Judah ===== milgram at cgpp.com 301-257-7069 From fourtysixandtwo at sliderr.net Sun May 24 22:47:48 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sun, 24 May 2026 16:47:48 -0600 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> Message-ID: Those instructions are only for use in another slackbuild, they are not build options for python3-setuptools-opt so you can just ignore them. Cheers On Sun, May 24, 2026 at 4:41?PM J. Milgram via SlackBuilds-users wrote: > > > > Dumb question. Where I see something like this in a Slackbuild README: > > ========= > Add the following before the python3 build commands in your > Slackbuild to use this version over the stock one in 15.0: > > PYVER=$(python3 -c 'import sys; print("%d.%d" % sys.version_info[:2])') > export PYTHONPATH=/opt/python$PYVER/site-packages > ========= > > ... sboinstall and sboupgrade will say "It looks like python3-setuptools-opt has options; would you like to set > any when the slackbuild is run?" > > All good. I say "y" and then the question is how to type this in. > > First, I presume it's entered without the "export" builtin: > > PYVER= > PYTHONPATH=/opt/python$PYVER/site-packages > > ... Else I get a "not a valid identifier" bash error apparently due to the script attempting: "export PYTHONPATH= foo.Slackbuild" and there's no "foo.Slackbuild" to export. > > Other question is, how to enter the lines at the sboinstall prompt: one at a time, separated by , or both in one line, separated by a semicolon? > > I've been "cheating" and entering only the second line, as PYTHONPATH=/opt/python3.9/site-packages, because I know I'm running 3.9. However, still curious how multiline input is envisioned to work. > > thanks! > > Judah > > ===== > milgram at cgpp.com > 301-257-7069 > > > _______________________________________________ > 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 milgram at cgpp.com Mon May 25 06:51:03 2026 From: milgram at cgpp.com (J. Milgram) Date: Mon, 25 May 2026 02:51:03 -0400 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> Message-ID: OK, makes sense, thanks. Now for the problem that led to the question: I'm getting an error upgrading python3-setuptools-opt. Per advice, ignoring the build options. The? build attempt goes roughly like this: ========== :~: sudo /usr/sbin/sboupgrade python3-setuptools-opt CHECKSUMS.md5.asc verified. See /usr/sbo/gpg.log. ... Setuptools is a fully-featured, actively-maintained, and stable library designed to facilitate packaging Python projects. Installs to /opt/python$PYVER/site-packages. ... It looks like python3-setuptools-opt has options; would you like to set any when the slackbuild is run? [n] Proceed with python3-setuptools-opt? [y] setuptools-80.10.2/ setuptools-80.10.2/LICENSE setuptools-80.10.2/MANIFEST.in ...? < unpacks many files, applies patches > ... * Getting build dependencies for sdist... Traceback (most recent call last): ...? < long traceback, culminating in? > ... File "/usr/lib64/python3.9/site-packages/importlib_metadata/_itertools.py", line 16, in unique_everseen ? ?k = key(element) AttributeError: 'PathDistribution' object has no attribute '_normalized_name' ERROR Backend subprocess exited when trying to invoke get_requires_for_build_sdist =========== For quite a while I suspected it had to do with the PYTHONPATH build option but that now seems not to be the case. So I'm guessing I have a package version mismatch of some sort, but can't figure out what it might be. Does anyone recognize this error? Any tips on running it to ground? FWIW this is an up-to-date Slack64-15.0 system. Some SBo's are a minor number or two behind but I'm already running into SBo packages that fail to upgrade because sbotools tries first to upgrade python3-setuptools-opt, which build fails. grateful for any ideas! Judah On 5/24/26 18:47, fourtysixandtwo wrote: > Those instructions are only for use in another slackbuild, they are > not build options for python3-setuptools-opt so you can just ignore > them. > > Cheers > > On Sun, May 24, 2026 at 4:41?PM J. Milgram via SlackBuilds-users > wrote: >> >> >> Dumb question. Where I see something like this in a Slackbuild README: >> >> ========= >> Add the following before the python3 build commands in your >> Slackbuild to use this version over the stock one in 15.0: >> >> PYVER=$(python3 -c 'import sys; print("%d.%d" % sys.version_info[:2])') >> export PYTHONPATH=/opt/python$PYVER/site-packages >> ========= >> >> ... sboinstall and sboupgrade will say "It looks like python3-setuptools-opt has options; would you like to set >> any when the slackbuild is run?" >> >> All good. I say "y" and then the question is how to type this in. >> >> First, I presume it's entered without the "export" builtin: >> >> PYVER= >> PYTHONPATH=/opt/python$PYVER/site-packages >> >> ... Else I get a "not a valid identifier" bash error apparently due to the script attempting: "export PYTHONPATH= foo.Slackbuild" and there's no "foo.Slackbuild" to export. >> >> Other question is, how to enter the lines at the sboinstall prompt: one at a time, separated by , or both in one line, separated by a semicolon? >> >> I've been "cheating" and entering only the second line, as PYTHONPATH=/opt/python3.9/site-packages, because I know I'm running 3.9. However, still curious how multiline input is envisioned to work. >> >> thanks! >> >> Judah >> >> ===== >> milgram at cgpp.com >> 301-257-7069 >> >> >> _______________________________________________ >> 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/ > -- ===== milgram at cgpp.com 301-257-7069 From chris.willing at linux.com Mon May 25 07:25:27 2026 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 25 May 2026 17:25:27 +1000 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> Message-ID: On 25/5/26 16:51, J. Milgram via SlackBuilds-users wrote: [snip] > So I'm guessing I have a package version mismatch of some sort, but > can't figure out what it might be. > > Does anyone recognize this error? Any tips on running it to ground? > FWIW this is an up-to-date Slack64-15.0 system. Some SBo's are a minor > number or two behind but I'm already running into SBo packages that > fail to upgrade because sbotools tries first to upgrade > python3-setuptools-opt, which build fails. > > grateful for any ideas! If you suspect package mismatch somewhere, I recommend you first remove setuptools-opt and its dependants and dependants of dependants etc. and build _new_ packages for _all_ of them (don't assume any existing packages are OK). Fortunately the dependency chain is not too long e.g. python/python3-flit_core python/python3-installer python/python3-wheel python/python3-pyproject-hooks python/python3-build python/python3-packaging-opt python/python3-setuptools-opt chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From fourtysixandtwo at sliderr.net Mon May 25 07:45:00 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Mon, 25 May 2026 01:45:00 -0600 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> Message-ID: Try what Chris said. If that fails, check your python version, and share the output of "pip3 check" # python3 --version Python 3.9.25 On Mon, May 25, 2026 at 1:25?AM Christoph Willing wrote: > > On 25/5/26 16:51, J. Milgram via SlackBuilds-users wrote: > [snip] > > So I'm guessing I have a package version mismatch of some sort, but can't figure out what it might be. > > Does anyone recognize this error? Any tips on running it to ground? FWIW this is an up-to-date Slack64-15.0 system. Some SBo's are a minor number or two behind but I'm already running into SBo packages that fail to upgrade because sbotools tries first to upgrade python3-setuptools-opt, which build fails. > > grateful for any ideas! > > > If you suspect package mismatch somewhere, I recommend you first remove setuptools-opt and its dependants and dependants of dependants etc. and build new packages for all of them (don't assume any existing packages are OK). Fortunately the dependency chain is not too long e.g. > > python/python3-flit_core > python/python3-installer > python/python3-wheel > python/python3-pyproject-hooks > python/python3-build > python/python3-packaging-opt > python/python3-setuptools-opt > > 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 milgram at cgpp.com Mon May 25 16:17:02 2026 From: milgram at cgpp.com (J. Milgram) Date: Mon, 25 May 2026 12:17:02 -0400 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> Message-ID: <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> OK, thanks. sboremove -a python3-setuptools-opt ... came up with the seven packages you suggest and removed them. (Just out of curiosity, what's the easy way? to generate the dependency chain?) Then, to make sure I was in step with the stock distro: slackpkg update slackpkg upgrade-all slackpkg install-new slackpkg clean-system ... no packages were removed or installed. (SBo packages being blacklisted.) Then sboinstall python3-setuptools-opt ... and ignored offers to set build options (python3-setuptools-opt only). Confirmed the install queue: Install queue: python3-flit_core python3-installer python3-pyproject-hooks python3-build python3-packaging-opt python3-wheel python3-setuptools-opt and let it do its thing. Looks like it successfully built and installed six of the seven packages, but failed again on python3-setuptools-opt with: ? File "/usr/lib64/python3.9/site-packages/importlib_metadata/_itertools.py", line 16, in unique_everseen ? ? k = key(element) AttributeError: 'PathDistribution' object has no attribute '_normalized_name' (I can provide the whole? traceback if it's of any use.) To fourtysixandtwo's question: python3 --version Python 3.9.25 myhost:~: pip3 check meson-python 0.18.0 has requirement meson>=0.64.0; python_version < "3.12", but you have meson 0.59.4. meson-python 0.18.0 has requirement packaging>=23.2, but you have packaging 21.3 Well, that's interesting. Then did: ls /var/log/packages/*meson*? ... var/log/packages/meson-0.59.4-x86_64-1 /var/log/packages/python3-meson-opt-1.10.2-noarch-1_SBo /var/log/packages/python3-mesonpy-0.18.0-x86_64-1_SBo meson-0.59.4 seems to be from the stock Slack 15.0 package. "slackpkg upgrade meson" didn't find any? new packages. So i tried: sboupgrade python3-meson-opt ... and it built python3-meson-opt-1.11.1 successfully, but didn't solve the python3-setuptools-opt problem. Could it be that I need to? do something more to cause the? build to pick up meson and packaging from /opt/python3.9/site-packages? I note that PYTHONPATH=/opt/python3.9/site-packages pip3 check ... tells me: No broken requirements found. I thought the next? logical thing to try would be: PYTHONPATH=/opt/python3.9/site-packages sboinstall python3-setuptools-opt ... but this yielded same error as above. PS thanks again ... r/ Judah On 5/25/26 03:25, Christoph Willing wrote: > On 25/5/26 16:51, J. Milgram via SlackBuilds-users wrote: > [snip] >> So I'm guessing I have a package version mismatch of some sort, but >> can't figure out what it might be. >> >> Does anyone recognize this error? Any tips on running it to ground? >> FWIW this is an up-to-date Slack64-15.0 system. Some SBo's are a >> minor number or two behind but I'm already running into SBo packages >> that fail to upgrade because sbotools tries first to upgrade >> python3-setuptools-opt, which build fails. >> >> grateful for any ideas! > > If you suspect package mismatch somewhere, I recommend you first > remove setuptools-opt and its dependants and dependants of dependants > etc. and build _new_ packages for _all_ of them (don't assume any > existing packages are OK). Fortunately the dependency chain is not too > long e.g. > > python/python3-flit_core > python/python3-installer > python/python3-wheel > python/python3-pyproject-hooks > python/python3-build > python/python3-packaging-opt > python/python3-setuptools-opt > > 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/ > -- ===== milgram at cgpp.com 301-257-7069 From 414N at slacky.it Mon May 25 17:02:49 2026 From: 414N at slacky.it (414N) Date: Mon, 25 May 2026 19:02:49 +0200 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> Message-ID: Il 25/05/26 18:17, J. Milgram via SlackBuilds-users ha scritto: > > and let it do its thing. Looks like it successfully built and installed > six of the seven packages, but failed again on python3-setuptools-opt with: > > ? File "/usr/lib64/python3.9/site-packages/importlib_metadata/ > _itertools.py", line 16, in unique_everseen > ? ? k = key(element) > AttributeError: 'PathDistribution' object has no attribute > '_normalized_name' Could it be that you need to upgrade the 'python-importlib_metadata' package before trying the build of the python3-setuptools-opt one? -- Alan Alberghini SBo clone: https://github.com/414n/slackbuilds From milgram at cgpp.com Mon May 25 17:28:32 2026 From: milgram at cgpp.com (J. Milgram) Date: Mon, 25 May 2026 13:28:32 -0400 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> Message-ID: Thanks. It was worth a try. Turns out it needed to upgrade python3-setuptools-opt first, so failed right out of the gate. JM On 5/25/26 13:02, 414N wrote: > > Il 25/05/26 18:17, J. Milgram via SlackBuilds-users ha scritto: >> >> and let it do its thing. Looks like it successfully built and >> installed six of the seven packages, but failed again on >> python3-setuptools-opt with: >> >> ?? File "/usr/lib64/python3.9/site-packages/importlib_metadata/ >> _itertools.py", line 16, in unique_everseen >> ?? ? k = key(element) >> AttributeError: 'PathDistribution' object has no attribute >> '_normalized_name' > > Could it be that you need to upgrade the 'python-importlib_metadata' > package before trying the build of the python3-setuptools-opt one? > -- ===== milgram at cgpp.com 301-257-7069 From fourtysixandtwo at sliderr.net Mon May 25 19:25:54 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Mon, 25 May 2026 13:25:54 -0600 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> Message-ID: I just wanted to see the output of pip3 check, those are normal unless you run it as "PYTHONPATH=/opt/python3.9/site-packages pip3 check" so it can see the "-opt" packages which are primarily needed only at build time. Does sbocheck list any other builds that need updating? Can you share the output of "pip3 list" and "ls -l /opt/python3.9/site-packages/"? On Mon, May 25, 2026 at 10:17?AM J. Milgram via SlackBuilds-users wrote: > > > OK, thanks. > > sboremove -a python3-setuptools-opt > > ... came up with the seven packages you suggest and removed them. (Just > out of curiosity, what's the easy way to generate the dependency chain?) > > Then, to make sure I was in step with the stock distro: > > slackpkg update > slackpkg upgrade-all > slackpkg install-new > slackpkg clean-system > > ... no packages were removed or installed. (SBo packages being blacklisted.) > > Then sboinstall python3-setuptools-opt > > ... and ignored offers to set build options (python3-setuptools-opt > only). Confirmed the install queue: > > Install queue: python3-flit_core python3-installer > python3-pyproject-hooks python3-build python3-packaging-opt > python3-wheel python3-setuptools-opt > > and let it do its thing. Looks like it successfully built and installed > six of the seven packages, but failed again on python3-setuptools-opt with: > > File > "/usr/lib64/python3.9/site-packages/importlib_metadata/_itertools.py", > line 16, in unique_everseen > k = key(element) > AttributeError: 'PathDistribution' object has no attribute > '_normalized_name' > > (I can provide the whole traceback if it's of any use.) > > To fourtysixandtwo's question: > > python3 --version > Python 3.9.25 > > myhost:~: pip3 check > meson-python 0.18.0 has requirement meson>=0.64.0; python_version < > "3.12", but you have meson 0.59.4. > meson-python 0.18.0 has requirement packaging>=23.2, but you have > packaging 21.3 > > Well, that's interesting. Then did: > > ls /var/log/packages/*meson* ... > var/log/packages/meson-0.59.4-x86_64-1 > /var/log/packages/python3-meson-opt-1.10.2-noarch-1_SBo > /var/log/packages/python3-mesonpy-0.18.0-x86_64-1_SBo > > meson-0.59.4 seems to be from the stock Slack 15.0 package. "slackpkg > upgrade meson" didn't find any new packages. So i tried: > > sboupgrade python3-meson-opt > > ... and it built python3-meson-opt-1.11.1 successfully, but didn't solve > the python3-setuptools-opt problem. > > Could it be that I need to do something more to cause the build to > pick up meson and packaging from /opt/python3.9/site-packages? I note that > > PYTHONPATH=/opt/python3.9/site-packages pip3 check > ... tells me: > No broken requirements found. > > I thought the next logical thing to try would be: > > PYTHONPATH=/opt/python3.9/site-packages sboinstall python3-setuptools-opt > > ... but this yielded same error as above. > > PS thanks again ... > > r/ > Judah > > > > > On 5/25/26 03:25, Christoph Willing wrote: > > On 25/5/26 16:51, J. Milgram via SlackBuilds-users wrote: > > [snip] > >> So I'm guessing I have a package version mismatch of some sort, but > >> can't figure out what it might be. > >> > >> Does anyone recognize this error? Any tips on running it to ground? > >> FWIW this is an up-to-date Slack64-15.0 system. Some SBo's are a > >> minor number or two behind but I'm already running into SBo packages > >> that fail to upgrade because sbotools tries first to upgrade > >> python3-setuptools-opt, which build fails. > >> > >> grateful for any ideas! > > > > If you suspect package mismatch somewhere, I recommend you first > > remove setuptools-opt and its dependants and dependants of dependants > > etc. and build _new_ packages for _all_ of them (don't assume any > > existing packages are OK). Fortunately the dependency chain is not too > > long e.g. > > > > python/python3-flit_core > > python/python3-installer > > python/python3-wheel > > python/python3-pyproject-hooks > > python/python3-build > > python/python3-packaging-opt > > python/python3-setuptools-opt > > > > 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/ > > > > -- > ===== > milgram at cgpp.com > 301-257-7069 > > > > _______________________________________________ > 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 414N at slacky.it Mon May 25 20:20:03 2026 From: 414N at slacky.it (414N) Date: Mon, 25 May 2026 22:20:03 +0200 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> Message-ID: Il 25/05/26 19:28, J. Milgram via SlackBuilds-users ha scritto: > > Thanks. It was worth a try. Turns out it needed to upgrade python3- > setuptools-opt first, so failed right out of the gate. > > JM Can you try rebuilding it alone (even manually outside sbotools), ignoring the dependency chain for a moment? Judging from the stacktrace you reported it seems to me that setuptools-opt (or something running during its build) uses code from importlib_metadata, so there appears to be an implicit circular dependency between the two: importlib_metadata -> zipp -> setuptools-opt -> importlib_metadata -- Alan Alberghini SBo clone: https://github.com/414n/slackbuilds From milgram at cgpp.com Tue May 26 01:30:12 2026 From: milgram at cgpp.com (J. Milgram) Date: Mon, 25 May 2026 21:30:12 -0400 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> Message-ID: <5606b970-c7cb-47a8-beb9-a1226e00064c@cgpp.com> Yes, I have many packages that are behind per sbocheck. My next thing to try would be to bring them all up to date but I'm not optimistic, based on what little I know about what the build needs (which is admittedly very little.) I'll spare you the long list. Is it worth rebuilding the ones tagged as "bumped"? Here's output of "pip3 list" Package? ? ? ? ? ? ? ? ? ? Version -------------------------- ---------- appdirs? ? ? ? ? ? ? ? ? ? 1.4.4 atomicwrites? ? ? ? ? ? ? ?1.3.0 attrs? ? ? ? ? ? ? ? ? ? ? 21.4.0 beautifulsoup4? ? ? ? ? ? ?4.12.3 beniget? ? ? ? ? ? ? ? ? ? 0.4.1 Brotli? ? ? ? ? ? ? ? ? ? ?1.0.9 bsddb3? ? ? ? ? ? ? ? ? ? ?6.2.6 build? ? ? ? ? ? ? ? ? ? ? 1.3.0 caca? ? ? ? ? ? ? ? ? ? ? ?0.99b19 calver? ? ? ? ? ? ? ? ? ? ?2022.6.26 certifi? ? ? ? ? ? ? ? ? ? 2021.10.8 cffi? ? ? ? ? ? ? ? ? ? ? ?1.15.0 chardet? ? ? ? ? ? ? ? ? ? 4.0.0 charset-normalizer? ? ? ? ?2.0.10 cppy? ? ? ? ? ? ? ? ? ? ? ?1.2.0 cssselect? ? ? ? ? ? ? ? ? 1.2.0 cupshelpers? ? ? ? ? ? ? ? 1.0 cycler? ? ? ? ? ? ? ? ? ? ?0.11.0 Cython? ? ? ? ? ? ? ? ? ? ?0.29.36 deprecation? ? ? ? ? ? ? ? 2.1.0 distro? ? ? ? ? ? ? ? ? ? ?1.6.0 dnspython? ? ? ? ? ? ? ? ? 2.1.0 docutils? ? ? ? ? ? ? ? ? ?0.17.1 doxypypy? ? ? ? ? ? ? ? ? ?0.8.8.6 doxyqml? ? ? ? ? ? ? ? ? ? 0.5.1 editables? ? ? ? ? ? ? ? ? 0.6 et-xmlfile? ? ? ? ? ? ? ? ?2.0.0 exceptiongroup? ? ? ? ? ? ?1.2.0 flit_core? ? ? ? ? ? ? ? ? 3.12.0 flit_scm? ? ? ? ? ? ? ? ? ?1.7.0 future? ? ? ? ? ? ? ? ? ? ?0.18.2 gast? ? ? ? ? ? ? ? ? ? ? ?0.5.4 getmail6? ? ? ? ? ? ? ? ? ?6.18.6 gi-docgen? ? ? ? ? ? ? ? ? 2023.1 gpg? ? ? ? ? ? ? ? ? ? ? ? 1.16.0 gramps? ? ? ? ? ? ? ? ? ? ?5.1.2 gyp? ? ? ? ? ? ? ? ? ? ? ? 0.1 hatch-vcs? ? ? ? ? ? ? ? ? 0.3.0 hatchling? ? ? ? ? ? ? ? ? 1.18.0 html5lib? ? ? ? ? ? ? ? ? ?1.1 idna? ? ? ? ? ? ? ? ? ? ? ?3.3 imageio? ? ? ? ? ? ? ? ? ? 2.34.1 img2pdf? ? ? ? ? ? ? ? ? ? 0.4.0 importlib-metadata? ? ? ? ?4.10.1 include_server? ? ? ? ? ? ?3.4 iniconfig? ? ? ? ? ? ? ? ? 2.0.0 installer? ? ? ? ? ? ? ? ? 0.7.0 Jinja2? ? ? ? ? ? ? ? ? ? ?3.0.3 kapidox? ? ? ? ? ? ? ? ? ? 5.90.0 kiwisolver? ? ? ? ? ? ? ? ?1.4.1 lensfun? ? ? ? ? ? ? ? ? ? 0.3.95 libtorrent? ? ? ? ? ? ? ? ?2.0.10 libwebp? ? ? ? ? ? ? ? ? ? 0.0 lxml? ? ? ? ? ? ? ? ? ? ? ?5.2.1 M2Crypto? ? ? ? ? ? ? ? ? ?0.38.0 Mako? ? ? ? ? ? ? ? ? ? ? ?1.1.6 Markdown? ? ? ? ? ? ? ? ? ?3.3.4 MarkupSafe? ? ? ? ? ? ? ? ?2.0.1 matplotlib? ? ? ? ? ? ? ? ?3.4.3 mercurial? ? ? ? ? ? ? ? ? 6.0.1 meson? ? ? ? ? ? ? ? ? ? ? 0.59.4 meson-python? ? ? ? ? ? ? ?0.18.0 more-itertools? ? ? ? ? ? ?4.1.0 mpmath? ? ? ? ? ? ? ? ? ? ?1.3.0 netsnmp-python? ? ? ? ? ? ?1.0a1 networkx? ? ? ? ? ? ? ? ? ?2.8.8 nftables? ? ? ? ? ? ? ? ? ?0.1 notify2? ? ? ? ? ? ? ? ? ? 0.3.1 numpy? ? ? ? ? ? ? ? ? ? ? 1.26.3 opencv-python? ? ? ? ? ? ? 4.8.0.76 openpyxl? ? ? ? ? ? ? ? ? ?3.1.5 packaging? ? ? ? ? ? ? ? ? 21.3 pathlib2? ? ? ? ? ? ? ? ? ?2.3.2 pathspec? ? ? ? ? ? ? ? ? ?1.1.1 pbr? ? ? ? ? ? ? ? ? ? ? ? 5.8.0 pdfarranger? ? ? ? ? ? ? ? 1.10.1 pep517? ? ? ? ? ? ? ? ? ? ?0.12.0 pikepdf? ? ? ? ? ? ? ? ? ? 5.3.2 Pillow? ? ? ? ? ? ? ? ? ? ?8.4.0 pip? ? ? ? ? ? ? ? ? ? ? ? 21.3.1 pluggy? ? ? ? ? ? ? ? ? ? ?1.3.0 ply? ? ? ? ? ? ? ? ? ? ? ? 3.11 protobuf? ? ? ? ? ? ? ? ? ?3.20.1 pssh? ? ? ? ? ? ? ? ? ? ? ?2.3.4 pwquality? ? ? ? ? ? ? ? ? 1.4.4 py? ? ? ? ? ? ? ? ? ? ? ? ?1.11.0 pybind11? ? ? ? ? ? ? ? ? ?2.11.1 pycairo? ? ? ? ? ? ? ? ? ? 1.20.1 pycparser? ? ? ? ? ? ? ? ? 2.21 pycups? ? ? ? ? ? ? ? ? ? ?2.0.1 pycurl? ? ? ? ? ? ? ? ? ? ?7.44.1 Pygments? ? ? ? ? ? ? ? ? ?2.10.0 PyGObject? ? ? ? ? ? ? ? ? 3.42.0 PyICU? ? ? ? ? ? ? ? ? ? ? 2.8 pyparsing? ? ? ? ? ? ? ? ? 2.4.7 pyproject_hooks? ? ? ? ? ? 1.2.0 pyproject-metadata? ? ? ? ?0.9.1 PyQt5? ? ? ? ? ? ? ? ? ? ? 5.15.2 PyQt5_sip? ? ? ? ? ? ? ? ? 4.19.25 pysol-cards? ? ? ? ? ? ? ? 0.12.0 pytaglib? ? ? ? ? ? ? ? ? ?1.4.6 pytesseract? ? ? ? ? ? ? ? 0.3.10 pytest? ? ? ? ? ? ? ? ? ? ?7.4.3 pytest-runner? ? ? ? ? ? ? 6.0.0 python-dateutil? ? ? ? ? ? 2.8.2 python-sane? ? ? ? ? ? ? ? 2.9.1 pythran? ? ? ? ? ? ? ? ? ? 0.15.0 pytz? ? ? ? ? ? ? ? ? ? ? ?2021.3 pyxdg? ? ? ? ? ? ? ? ? ? ? 0.27 PyYAML? ? ? ? ? ? ? ? ? ? ?6.0 QScintilla? ? ? ? ? ? ? ? ?2.11.6 random2? ? ? ? ? ? ? ? ? ? 1.0.1 requests? ? ? ? ? ? ? ? ? ?2.26.0 rpm? ? ? ? ? ? ? ? ? ? ? ? 4.16.1.3 scipy? ? ? ? ? ? ? ? ? ? ? 1.12.0 SCons? ? ? ? ? ? ? ? ? ? ? 4.2.0 setuptools? ? ? ? ? ? ? ? ?57.5.0 setuptools-scm? ? ? ? ? ? ?6.3.2 setuptools-scm-git-archive 1.4.1 sip? ? ? ? ? ? ? ? ? ? ? ? 4.19.25 six? ? ? ? ? ? ? ? ? ? ? ? 1.16.0 smartypants? ? ? ? ? ? ? ? 2.0.1 soupsieve? ? ? ? ? ? ? ? ? 2.5 sympy? ? ? ? ? ? ? ? ? ? ? 1.11.1 toml? ? ? ? ? ? ? ? ? ? ? ?0.10.2 tomli? ? ? ? ? ? ? ? ? ? ? 1.2.2 tornado? ? ? ? ? ? ? ? ? ? 6.1 trove-classifiers? ? ? ? ? 2023.11.14 typing_extensions? ? ? ? ? 4.15.0 typogrify? ? ? ? ? ? ? ? ? 2.0.7 undervolt? ? ? ? ? ? ? ? ? 0.3.0 Unidecode? ? ? ? ? ? ? ? ? 1.3.8 urllib3? ? ? ? ? ? ? ? ? ? 1.26.8 webencodings? ? ? ? ? ? ? ?0.5.1 wheel? ? ? ? ? ? ? ? ? ? ? 0.45.1 zipp? ? ? ? ? ? ? ? ? ? ? ?3.8.0 Finally, "ls? -l /opt/python3.9/site-packages/": drwxr-xr-x? 2 root root 4096 May 25 11:40 meson-1.11.1.dist-info/ drwxr-xr-x 17 root root 4096 May 25 11:40 mesonbuild/ drwxr-xr-x? 4 root root 4096 May 25 11:25 packaging/ drwxr-xr-x? 3 root root 4096 May 25 11:25 packaging-26.2.dist-info/ drwxr-xr-x? 5 root root 4096 Jul? 4? 2025 setuptools_scm/ drwxr-xr-x? 2 root root 4096 Jul? 4? 2025 setuptools_scm-8.3.1.dist-info/ I'll report back after I upgrade my SBo packages. thanks, Judah On 5/25/26 15:25, fourtysixandtwo wrote: > I just wanted to see the output of pip3 check, those are normal unless > you run it as "PYTHONPATH=/opt/python3.9/site-packages pip3 check" so > it can see the "-opt" packages which are primarily needed only at > build time. > > Does sbocheck list any other builds that need updating? > > Can you share the output of "pip3 list" and "ls -l > /opt/python3.9/site-packages/"? > > On Mon, May 25, 2026 at 10:17?AM J. Milgram via SlackBuilds-users > wrote: >> >> OK, thanks. >> >> sboremove -a python3-setuptools-opt >> >> ... came up with the seven packages you suggest and removed them. (Just >> out of curiosity, what's the easy way to generate the dependency chain?) >> >> Then, to make sure I was in step with the stock distro: >> >> slackpkg update >> slackpkg upgrade-all >> slackpkg install-new >> slackpkg clean-system >> >> ... no packages were removed or installed. (SBo packages being blacklisted.) >> >> Then sboinstall python3-setuptools-opt >> >> ... and ignored offers to set build options (python3-setuptools-opt >> only). Confirmed the install queue: >> >> Install queue: python3-flit_core python3-installer >> python3-pyproject-hooks python3-build python3-packaging-opt >> python3-wheel python3-setuptools-opt >> >> and let it do its thing. Looks like it successfully built and installed >> six of the seven packages, but failed again on python3-setuptools-opt with: >> >> File >> "/usr/lib64/python3.9/site-packages/importlib_metadata/_itertools.py", >> line 16, in unique_everseen >> k = key(element) >> AttributeError: 'PathDistribution' object has no attribute >> '_normalized_name' >> >> (I can provide the whole traceback if it's of any use.) >> >> To fourtysixandtwo's question: >> >> python3 --version >> Python 3.9.25 >> >> myhost:~: pip3 check >> meson-python 0.18.0 has requirement meson>=0.64.0; python_version < >> "3.12", but you have meson 0.59.4. >> meson-python 0.18.0 has requirement packaging>=23.2, but you have >> packaging 21.3 >> >> Well, that's interesting. Then did: >> >> ls /var/log/packages/*meson* ... >> var/log/packages/meson-0.59.4-x86_64-1 >> /var/log/packages/python3-meson-opt-1.10.2-noarch-1_SBo >> /var/log/packages/python3-mesonpy-0.18.0-x86_64-1_SBo >> >> meson-0.59.4 seems to be from the stock Slack 15.0 package. "slackpkg >> upgrade meson" didn't find any new packages. So i tried: >> >> sboupgrade python3-meson-opt >> >> ... and it built python3-meson-opt-1.11.1 successfully, but didn't solve >> the python3-setuptools-opt problem. >> >> Could it be that I need to do something more to cause the build to >> pick up meson and packaging from /opt/python3.9/site-packages? I note that >> >> PYTHONPATH=/opt/python3.9/site-packages pip3 check >> ... tells me: >> No broken requirements found. >> >> I thought the next logical thing to try would be: >> >> PYTHONPATH=/opt/python3.9/site-packages sboinstall python3-setuptools-opt >> >> ... but this yielded same error as above. >> >> PS thanks again ... >> >> r/ >> Judah >> >> >> >> >> On 5/25/26 03:25, Christoph Willing wrote: >>> On 25/5/26 16:51, J. Milgram via SlackBuilds-users wrote: >>> [snip] >>>> So I'm guessing I have a package version mismatch of some sort, but >>>> can't figure out what it might be. >>>> >>>> Does anyone recognize this error? Any tips on running it to ground? >>>> FWIW this is an up-to-date Slack64-15.0 system. Some SBo's are a >>>> minor number or two behind but I'm already running into SBo packages >>>> that fail to upgrade because sbotools tries first to upgrade >>>> python3-setuptools-opt, which build fails. >>>> >>>> grateful for any ideas! >>> If you suspect package mismatch somewhere, I recommend you first >>> remove setuptools-opt and its dependants and dependants of dependants >>> etc. and build _new_ packages for _all_ of them (don't assume any >>> existing packages are OK). Fortunately the dependency chain is not too >>> long e.g. >>> >>> python/python3-flit_core >>> python/python3-installer >>> python/python3-wheel >>> python/python3-pyproject-hooks >>> python/python3-build >>> python/python3-packaging-opt >>> python/python3-setuptools-opt >>> >>> 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/ >>> >> -- >> ===== >> milgram at cgpp.com >> 301-257-7069 >> >> >> >> _______________________________________________ >> 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/ > -- ===== milgram at cgpp.com 301-257-7069 From milgram at cgpp.com Tue May 26 01:38:10 2026 From: milgram at cgpp.com (J. Milgram) Date: Mon, 25 May 2026 21:38:10 -0400 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> Message-ID: <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> I tried building it as a standalone, manually with "sh python3-setuptools-opt.SlackBuild". Same result. But good idea to try it. Thanks, and I'll report back after my SBo upgrade campaign. Judah On 5/25/26 16:20, 414N wrote: > > Il 25/05/26 19:28, J. Milgram via SlackBuilds-users ha scritto: >> >> Thanks. It was worth a try. Turns out it needed to upgrade python3- >> setuptools-opt first, so failed right out of the gate. >> >> JM > > Can you try rebuilding it alone (even manually outside sbotools), > ignoring the dependency chain for a moment? > Judging from the stacktrace you reported it seems to me that > setuptools-opt (or something running during its build) uses code from > importlib_metadata, so there appears to be an implicit circular > dependency between the two: > > ?importlib_metadata -> zipp -> setuptools-opt -> importlib_metadata > > -- ===== milgram at cgpp.com 301-257-7069 From fourtysixandtwo at sliderr.net Tue May 26 01:44:07 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Mon, 25 May 2026 19:44:07 -0600 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> Message-ID: Ya, remove python-importlib_metadata and try again. The version you have is ancient and most likely the problem. You are so behind on updates there might be a few other builds that will cause issues. -- On Mon, May 25, 2026, 7:38?p.m. J. Milgram via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > > I tried building it as a standalone, manually with "sh > python3-setuptools-opt.SlackBuild". Same result. > > But good idea to try it. Thanks, and I'll report back after my SBo > upgrade campaign. > > Judah > > On 5/25/26 16:20, 414N wrote: > > > > Il 25/05/26 19:28, J. Milgram via SlackBuilds-users ha scritto: > >> > >> Thanks. It was worth a try. Turns out it needed to upgrade python3- > >> setuptools-opt first, so failed right out of the gate. > >> > >> JM > > > > Can you try rebuilding it alone (even manually outside sbotools), > > ignoring the dependency chain for a moment? > > Judging from the stacktrace you reported it seems to me that > > setuptools-opt (or something running during its build) uses code from > > importlib_metadata, so there appears to be an implicit circular > > dependency between the two: > > > > importlib_metadata -> zipp -> setuptools-opt -> importlib_metadata > > > > > > -- > ===== > milgram at cgpp.com > 301-257-7069 > > > > _______________________________________________ > 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 414N at slacky.it Tue May 26 08:53:01 2026 From: 414N at slacky.it (414N) Date: Tue, 26 May 2026 10:53:01 +0200 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> Message-ID: <1092fe0a-bcd6-46a7-afd1-3741e4896aa9@slacky.it> Il 26/05/26 03:38, J. Milgram via SlackBuilds-users ha scritto: > > I tried building it as a standalone, manually with "sh python3- > setuptools-opt.SlackBuild". Same result. > > But good idea to try it. Thanks, and I'll report back after my SBo > upgrade campaign. > > Judah Sorry I was not more explicit about it: what I meant was to rebuild/upgrade manually the importlib-metadata package, not the setuptools-opt one. Your "pip3 list" output reports a version that is far behind the current one on SBo (4.10.1 vs 8.7.0). Updating this first might fix your issues with setuptools-opt. -- Alan Alberghini SBo clone: https://github.com/414n/slackbuilds From milgram at cgpp.com Tue May 26 14:16:56 2026 From: milgram at cgpp.com (J. Milgram) Date: Tue, 26 May 2026 10:16:56 -0400 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: <1092fe0a-bcd6-46a7-afd1-3741e4896aa9@slacky.it> References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> <1092fe0a-bcd6-46a7-afd1-3741e4896aa9@slacky.it> Message-ID: <26f00add-96bb-4c82-8891-892c0a55a68e@cgpp.com> All good. Let's give it a go: The python-importlib_metadata manual build fails with: ERROR Missing dependencies: ? ? ? ? setuptools>=61.2 ? ? ? ? setuptools_scm[toml]>=3.4.1 ? ? ? ? importlib-metadata>=4.6 -> zipp>=3.20 So right there I have a circular dependency: python-importlib_metadata: python3-setuptools_scm: (per the error message, though not the SlackBuild info file) python3-setuptools_scm: python-importlib_metadata (per the info file) BTW attempt to build python3-setuptools_scm manually fails with the same error (I think) I see when building python3-setuptools-opt: === AttributeError: 'PathDistribution' object has no attribute '_normalized_name' ERROR Backend subprocess exited when trying to invoke get_requires_for_build_sdist === More to follow ... (am still upgrading packages ... I obviously let things go too long!) JM On 5/26/26 04:53, 414N wrote: > > Il 26/05/26 03:38, J. Milgram via SlackBuilds-users ha scritto: >> >> I tried building it as a standalone, manually with "sh python3- >> setuptools-opt.SlackBuild". Same result. >> >> But good idea to try it. Thanks, and I'll report back after my SBo >> upgrade campaign. >> >> Judah > > Sorry I was not more explicit about it: what I meant was to > rebuild/upgrade manually the importlib-metadata package, not the > setuptools-opt one. > > Your "pip3 list" output reports a version that is far behind the > current one on SBo (4.10.1 vs 8.7.0). > > Updating this first might fix your issues with setuptools-opt. > > -- ===== milgram at cgpp.com 301-257-7069 From willysr at slackbuilds.org Wed May 27 00:14:04 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 27 May 2026 07:14:04 +0700 Subject: [Slackbuilds-users] Early notice: removing nodejs Message-ID: <20260527071404.466353bb@home.slackie.org> Hi since nodejs 20.x branch has been considered EOL by upstream, and the only script that depends on this version of nodejs has been switched to nodejs22, i'm planning to remove nodejs by this week's public update. If you still need this version of nodejs, please let us know before it will be removed from master branch soon. It's suggested to use nodejs22 for 22.x branch or nodejs24-bin for 24.x branch which is still supported upstream Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From fourtysixandtwo at sliderr.net Wed May 27 05:15:09 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Tue, 26 May 2026 23:15:09 -0600 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: <26f00add-96bb-4c82-8891-892c0a55a68e@cgpp.com> References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> <1092fe0a-bcd6-46a7-afd1-3741e4896aa9@slacky.it> <26f00add-96bb-4c82-8891-892c0a55a68e@cgpp.com> Message-ID: Have you removed "python-importlib_metadata" and tried building python3-setuptools-opt yet? On Tue, May 26, 2026 at 8:17?AM J. Milgram via SlackBuilds-users wrote: > > > All good. Let's give it a go: > > The python-importlib_metadata manual build fails with: > > ERROR Missing dependencies: > setuptools>=61.2 > setuptools_scm[toml]>=3.4.1 > importlib-metadata>=4.6 -> zipp>=3.20 > > So right there I have a circular dependency: > > python-importlib_metadata: python3-setuptools_scm: (per the error > message, though not the SlackBuild info file) > > python3-setuptools_scm: python-importlib_metadata (per the info file) > > BTW attempt to build python3-setuptools_scm manually fails with the same > error (I think) I see when building python3-setuptools-opt: > > === > AttributeError: 'PathDistribution' object has no attribute > '_normalized_name' > > ERROR Backend subprocess exited when trying to invoke > get_requires_for_build_sdist > === > > More to follow ... (am still upgrading packages ... I obviously let > things go too long!) > > JM > > > > > On 5/26/26 04:53, 414N wrote: > > > > Il 26/05/26 03:38, J. Milgram via SlackBuilds-users ha scritto: > >> > >> I tried building it as a standalone, manually with "sh python3- > >> setuptools-opt.SlackBuild". Same result. > >> > >> But good idea to try it. Thanks, and I'll report back after my SBo > >> upgrade campaign. > >> > >> Judah > > > > Sorry I was not more explicit about it: what I meant was to > > rebuild/upgrade manually the importlib-metadata package, not the > > setuptools-opt one. > > > > Your "pip3 list" output reports a version that is far behind the > > current one on SBo (4.10.1 vs 8.7.0). > > > > Updating this first might fix your issues with setuptools-opt. > > > > > > -- > ===== > milgram at cgpp.com > 301-257-7069 > > > > _______________________________________________ > 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 milgram at cgpp.com Wed May 27 06:10:08 2026 From: milgram at cgpp.com (J. Milgram) Date: Wed, 27 May 2026 02:10:08 -0400 Subject: [Slackbuilds-users] sbotools: multiline build options In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> <1092fe0a-bcd6-46a7-afd1-3741e4896aa9@slacky.it> <26f00add-96bb-4c82-8891-892c0a55a68e@cgpp.com> Message-ID: <39ddbc8d-203d-49c6-b5b6-3ef25b2e6329@cgpp.com> Actually, I had already tried that without success. Am trying again, having done this: python3 -m pip uninstall importlib-metadata importlib_metadata ... suspecting I had mixed pip-installed and SBo packages (and it seems this is a bad thing to do and I have no memory of doing it.). This let me build/install python3-setuptools-opt-80.10.2-x86_64-1_SBo (without reinstalling python-importlib_metadata) Yay. Very encouraging, however: still can't build python-importlib_metadata, because: python-importlib_metadata build fails? with a complaint about not finding zipp => 3.20. But I had it installed ... !?? So I removed python-zipp, but then it wouldn't build again, because ... python-importlib_metadata is missing. In other words, a circular dependency. Attempt to build python-zipp manually failed in the same way as sboinstall. BTW both zipp and python-importlib_metadata builds are complaining about missing? setuptools_scm[toml]>=3.4.1 however I do have python3-setuptools-scm-opt-8.3.1-noarch-1_SBo installed, so I don't? understand what the problem is. So I'm making progress but not there yet and out of ideas. Anyway I need to set it aside until tomorrow. Thanks again for the help and wisdom. Judah On 5/27/26 01:15, fourtysixandtwo wrote: > Have you removed "python-importlib_metadata" and tried building > python3-setuptools-opt yet? > > On Tue, May 26, 2026 at 8:17?AM J. Milgram via SlackBuilds-users > wrote: >> >> All good. Let's give it a go: >> >> The python-importlib_metadata manual build fails with: >> >> ERROR Missing dependencies: >> setuptools>=61.2 >> setuptools_scm[toml]>=3.4.1 >> importlib-metadata>=4.6 -> zipp>=3.20 >> >> So right there I have a circular dependency: >> >> python-importlib_metadata: python3-setuptools_scm: (per the error >> message, though not the SlackBuild info file) >> >> python3-setuptools_scm: python-importlib_metadata (per the info file) >> >> BTW attempt to build python3-setuptools_scm manually fails with the same >> error (I think) I see when building python3-setuptools-opt: >> >> === >> AttributeError: 'PathDistribution' object has no attribute >> '_normalized_name' >> >> ERROR Backend subprocess exited when trying to invoke >> get_requires_for_build_sdist >> === >> >> More to follow ... (am still upgrading packages ... I obviously let >> things go too long!) >> >> JM >> >> >> >> >> On 5/26/26 04:53, 414N wrote: >>> Il 26/05/26 03:38, J. Milgram via SlackBuilds-users ha scritto: >>>> I tried building it as a standalone, manually with "sh python3- >>>> setuptools-opt.SlackBuild". Same result. >>>> >>>> But good idea to try it. Thanks, and I'll report back after my SBo >>>> upgrade campaign. >>>> >>>> Judah >>> Sorry I was not more explicit about it: what I meant was to >>> rebuild/upgrade manually the importlib-metadata package, not the >>> setuptools-opt one. >>> >>> Your "pip3 list" output reports a version that is far behind the >>> current one on SBo (4.10.1 vs 8.7.0). >>> >>> Updating this first might fix your issues with setuptools-opt. >>> >>> >> -- >> ===== >> milgram at cgpp.com >> 301-257-7069 >> >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> -- ===== milgram at cgpp.com 301-257-7069 From chris.willing at linux.com Wed May 27 13:10:45 2026 From: chris.willing at linux.com (Christoph Willing) Date: Wed, 27 May 2026 23:10:45 +1000 Subject: [Slackbuilds-users] SlackBuilds up for grabs Message-ID: <64f41803-d84a-4dc1-bdb9-969fd6e68836@linux.com> I recently emailed the maintainer of some SlackBuilds I wanted to use to request updated versions. Alternatively, I asked to take them over. Since the maintainer hasn't been active since 2017, I also asked whether I could announce their remaining SlackBuilds as "up for grabs", to which he replied "Yes, please do". The resulting list of "up for grabs" SlackBuilds are (I've already grabbed libraries/{rocksdb,gflags}): ./multimedia/subtitleripper ./python/cfgparse ./python/pyjwt ./python/pluginbase ./python/monotonic ./python/node-semver ./python/sk1libs ./python/python2-patch ./python/fasteners ./graphics/uniconvertor ./system/fxload ./system/zookeeper ./system/rabbitmq-server ./system/kafka ./system/evdi ./system/evdi-kernel ./system/displaylink ./development/xsp ./development/reckless ./development/libxbgi ./development/gplcver ./development/mstch ./development/cim ./development/g3log ./development/libcutl ./development/sauce ./development/mono-addins ./development/boost-di ./academic/abntex ./libraries/cpprestsdk ./libraries/dlib ./libraries/libr3 ./libraries/sqlpp11 ./libraries/gperftools ./libraries/gnome-sharp ./libraries/RxCpp ./libraries/google-fruit ./libraries/restbed ./libraries/Hypodermic ./libraries/capnproto ./libraries/kashmir ./libraries/libgraphqlparser ./libraries/cpp-netlib ./libraries/glog chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From milgram at cgpp.com Wed May 27 14:17:09 2026 From: milgram at cgpp.com (J. Milgram) Date: Wed, 27 May 2026 10:17:09 -0400 Subject: [Slackbuilds-users] mutual dependency? [was: sbotools: multiline build options] In-Reply-To: <39ddbc8d-203d-49c6-b5b6-3ef25b2e6329@cgpp.com> References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <751c7bea-6ccb-446b-83ba-58b14dfeb4d4@cgpp.com> <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> <1092fe0a-bcd6-46a7-afd1-3741e4896aa9@slacky.it> <26f00add-96bb-4c82-8891-892c0a55a68e@cgpp.com> <39ddbc8d-203d-49c6-b5b6-3ef25b2e6329@cgpp.com> Message-ID: python-importlib_metadata and python-zipp really do seem to be pointing at each other: After? removing both packages, and attempting to re-install (with sboinstall or manually): The python-zipp build bombs with: ERROR Missing dependencies: ? ? ? ? setuptools_scm[toml]>=3.4.1 ? ? ? ? importlib-metadata>=4.6 while python-importlib_metadata seems to need python-zipp,? bombing with: ERROR Missing dependencies: ? ? ? ? setuptools_scm[toml]>=3.4.1 ? ? ? ? importlib-metadata>=4.6 -> zipp>=3.20 I? don't understand why? it's complaining about setuptools_scm ... I seem to have it: /var/log/packages/python3-setuptools-scm-opt-8.3.1-noarch-1_SBo /var/log/packages/python-setuptools_scm-6.3.2-x86_64-1 /var/log/packages/python3-setuptools_scm_git_archive-1.4.1-x86_64-1_SBo ... though not sure which (if? any) of these packages is the one it wants. So I'm stuck? again.? Anyone have a next step? to suggest? At least I got python3-setuptools-opt installed. thanks! Judah On 5/27/26 02:10, J. Milgram wrote: > > Actually, I had already tried that without success. Am trying again, > having done this: > > python3 -m pip uninstall importlib-metadata importlib_metadata > > ... suspecting I had mixed pip-installed and SBo packages (and it > seems this is a bad thing to do and I have no memory of doing it.). > > This let me build/install python3-setuptools-opt-80.10.2-x86_64-1_SBo > (without reinstalling python-importlib_metadata) > > Yay. Very encouraging, however: still can't build > python-importlib_metadata, because: > > python-importlib_metadata build fails? with a complaint about not > finding zipp => 3.20. But I had it installed ... !?? > > So I removed python-zipp, but then it wouldn't build again, because > ... python-importlib_metadata is missing. > > In other words, a circular dependency. > > Attempt to build python-zipp manually failed in the same way as > sboinstall. > > BTW both zipp and python-importlib_metadata builds are complaining > about missing? setuptools_scm[toml]>=3.4.1 however I do have > python3-setuptools-scm-opt-8.3.1-noarch-1_SBo installed, so I don't? > understand what the problem is. > > So I'm making progress but not there yet and out of ideas. Anyway I > need to set it aside until tomorrow. > > Thanks again for the help and wisdom. > > Judah > > > > On 5/27/26 01:15, fourtysixandtwo wrote: >> Have you removed "python-importlib_metadata" and tried building >> python3-setuptools-opt yet? >> >> On Tue, May 26, 2026 at 8:17?AM J. Milgram via SlackBuilds-users >> wrote: >>> >>> All good. Let's give it a go: >>> >>> The python-importlib_metadata manual build fails with: >>> >>> ERROR Missing dependencies: >>> ????????? setuptools>=61.2 >>> ????????? setuptools_scm[toml]>=3.4.1 >>> ????????? importlib-metadata>=4.6 -> zipp>=3.20 >>> >>> So right there I have a circular dependency: >>> >>> python-importlib_metadata: python3-setuptools_scm: (per the error >>> message, though not the SlackBuild info file) >>> >>> python3-setuptools_scm: python-importlib_metadata (per the info file) >>> >>> BTW attempt to build python3-setuptools_scm manually fails with the >>> same >>> error (I think) I see when building python3-setuptools-opt: >>> >>> === >>> AttributeError: 'PathDistribution' object has no attribute >>> '_normalized_name' >>> >>> ERROR Backend subprocess exited when trying to invoke >>> get_requires_for_build_sdist >>> === >>> >>> More to follow ... (am still upgrading packages ... I obviously let >>> things go too long!) >>> >>> JM >>> >>> >>> >>> >>> On 5/26/26 04:53, 414N wrote: >>>> Il 26/05/26 03:38, J. Milgram via SlackBuilds-users ha scritto: >>>>> I tried building it as a standalone, manually with "sh python3- >>>>> setuptools-opt.SlackBuild". Same result. >>>>> >>>>> But good idea to try it. Thanks, and I'll report back after my SBo >>>>> upgrade campaign. >>>>> >>>>> Judah >>>> Sorry I was not more explicit about it: what I meant was to >>>> rebuild/upgrade manually the importlib-metadata package, not the >>>> setuptools-opt one. >>>> >>>> Your "pip3 list" output reports a version that is far behind the >>>> current one on SBo (4.10.1 vs 8.7.0). >>>> >>>> Updating this first might fix your issues with setuptools-opt. >>>> >>>> >>> -- >>> ===== >>> milgram at cgpp.com >>> 301-257-7069 >>> >>> >>> >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> > -- ===== milgram at cgpp.com 301-257-7069 From erich.public at protonmail.com Wed May 27 14:33:40 2026 From: erich.public at protonmail.com (Erich Ritz) Date: Wed, 27 May 2026 14:33:40 +0000 Subject: [Slackbuilds-users] mutual dependency? [was: sbotools: multiline build options] In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> <1092fe0a-bcd6-46a7-afd1-3741e4896aa9@slacky.it> <26f00add-96bb-4c82-8891-892c0a55a68e@cgpp.com> <39ddbc8d-203d-49c6-b5b6-3ef25b2e6329@cgpp.com> Message-ID: On Wednesday, May 27th, 2026 at 9:17 AM, J. Milgram via SlackBuilds-users wrote: > > python-importlib_metadata and python-zipp really do seem to be pointing > at each other: > > After removing both packages, and attempting to re-install (with > sboinstall or manually): > > The python-zipp build bombs with: > > ERROR Missing dependencies: > setuptools_scm[toml]>=3.4.1 > importlib-metadata>=4.6 > > while python-importlib_metadata seems to need python-zipp, bombing with: > > ERROR Missing dependencies: > setuptools_scm[toml]>=3.4.1 > importlib-metadata>=4.6 -> zipp>=3.20 > > I don't understand why it's complaining about setuptools_scm ... I > seem to have it: > > /var/log/packages/python3-setuptools-scm-opt-8.3.1-noarch-1_SBo > /var/log/packages/python-setuptools_scm-6.3.2-x86_64-1 > /var/log/packages/python3-setuptools_scm_git_archive-1.4.1-x86_64-1_SBo > > ... though not sure which (if any) of these packages is the one it wants. > > So I'm stuck again. Anyone have a next step to suggest? > > At least I got python3-setuptools-opt installed. > > thanks! > > Judah > Hi Judah, This is the full dependency list required for python-zipp, from my local build log (I use slackrepo to build in a clean chroot): Building python/python-zipp (rebuild for updated deps) 2026-02-03 15:47:51 Verifying source files ... Installing dependencies ... python3-flit_core-3.12.0-x86_64-1_SBo: Simplified pkging of Python modules, core b [ 180K] python3-installer-0.7.0-x86_64-6_SBo: Library for installing Python packages from [ 1.1M] python3-pyproject-hooks-1.2.0-x86_64-1_SBo: Wrappers to call PEP 517 build backend [ 120K] python3-build-1.3.0-x86_64-1_SBo: a simple, correct PEP517 package builder ....... [ 230K] python3-packaging-opt-26.0-noarch-1_SBo: Install packaging in /opt ............... [ 740K] python3-wheel-0.45.1-x86_64-1_SBo: A built-package format for Python ............. [ 650K] python3-setuptools-opt-80.10.2-x86_64-1_SBo: Install setuptools from -current in / [ 9.6M] Running python-zipp.SlackBuild ... ETA 15:48:?? ... Built ok: python-zipp-3.21.0-x86_64-11_SBo.txz 15:47:53 Unmounting chroot ... Backed up: python-zipp-3.21.0-x86_64-10_SBo.txz :-) python/python-zipp Rebuilt for updated deps (-: Erich From rizitis at gmail.com Wed May 27 16:53:52 2026 From: rizitis at gmail.com (=?UTF-8?B?zpnPic6szr3Ovc63z4I=?=) Date: Wed, 27 May 2026 19:53:52 +0300 Subject: [Slackbuilds-users] capstone don`t build shared library Message-ID: Hello! In capstone 5.0 the cmake flags changed. SlackBuild need this patch else it not building shared the library. Thank you! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: capstone-SlackBuild.patch Type: text/x-patch Size: 480 bytes Desc: not available URL: From fourtysixandtwo at sliderr.net Wed May 27 20:20:51 2026 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Wed, 27 May 2026 14:20:51 -0600 Subject: [Slackbuilds-users] mutual dependency? [was: sbotools: multiline build options] In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> <1092fe0a-bcd6-46a7-afd1-3741e4896aa9@slacky.it> <26f00add-96bb-4c82-8891-892c0a55a68e@cgpp.com> <39ddbc8d-203d-49c6-b5b6-3ef25b2e6329@cgpp.com> Message-ID: If you've been using pip to install and uninstall...that's certainly not helping the situation and is not recommended as root as it cannot be trusted to apply the proper permissions. When I previously suggested removing python-importlib_metadata, I was talking about removing the slackware SBo package. I would start with cleaning up any python stuff not properly installed via slackware packaging. # as root get a list of anything pip installed and uninstall them. (If you have had pip install anything as your regular user, that can cause problems too, but is out of scope for the moment) pip3 list --user pip3 uninstall # sbocheck has a list of "out-of-tree builds...", remove those packages # one example I know is installed, added zipp and importlib just in case... removepkg python3-pep517 python-zipp python-importlib_metadata # another old build that might cause issues removepkg python3-pyproject-metadata Try to build python3-setuptools-opt again and let us know. On Wed, May 27, 2026 at 8:33?AM Erich Ritz wrote: > > On Wednesday, May 27th, 2026 at 9:17 AM, J. Milgram via SlackBuilds-users wrote: > > > > > python-importlib_metadata and python-zipp really do seem to be pointing > > at each other: > > > > After removing both packages, and attempting to re-install (with > > sboinstall or manually): > > > > The python-zipp build bombs with: > > > > ERROR Missing dependencies: > > setuptools_scm[toml]>=3.4.1 > > importlib-metadata>=4.6 > > > > while python-importlib_metadata seems to need python-zipp, bombing with: > > > > ERROR Missing dependencies: > > setuptools_scm[toml]>=3.4.1 > > importlib-metadata>=4.6 -> zipp>=3.20 > > > > I don't understand why it's complaining about setuptools_scm ... I > > seem to have it: > > > > /var/log/packages/python3-setuptools-scm-opt-8.3.1-noarch-1_SBo > > /var/log/packages/python-setuptools_scm-6.3.2-x86_64-1 > > /var/log/packages/python3-setuptools_scm_git_archive-1.4.1-x86_64-1_SBo > > > > ... though not sure which (if any) of these packages is the one it wants. > > > > So I'm stuck again. Anyone have a next step to suggest? > > > > At least I got python3-setuptools-opt installed. > > > > thanks! > > > > Judah > > > > Hi Judah, > > This is the full dependency list required for python-zipp, from my local build log (I use slackrepo to build in a clean chroot): > > Building python/python-zipp (rebuild for updated deps) 2026-02-03 15:47:51 > Verifying source files ... > Installing dependencies ... > python3-flit_core-3.12.0-x86_64-1_SBo: Simplified pkging of Python modules, core b [ 180K] > python3-installer-0.7.0-x86_64-6_SBo: Library for installing Python packages from [ 1.1M] > python3-pyproject-hooks-1.2.0-x86_64-1_SBo: Wrappers to call PEP 517 build backend [ 120K] > python3-build-1.3.0-x86_64-1_SBo: a simple, correct PEP517 package builder ....... [ 230K] > python3-packaging-opt-26.0-noarch-1_SBo: Install packaging in /opt ............... [ 740K] > python3-wheel-0.45.1-x86_64-1_SBo: A built-package format for Python ............. [ 650K] > python3-setuptools-opt-80.10.2-x86_64-1_SBo: Install setuptools from -current in / [ 9.6M] > Running python-zipp.SlackBuild ... ETA 15:48:?? > > ... > > Built ok: python-zipp-3.21.0-x86_64-11_SBo.txz 15:47:53 > Unmounting chroot ... > Backed up: python-zipp-3.21.0-x86_64-10_SBo.txz > :-) python/python-zipp Rebuilt for updated deps (-: > > > > > Erich From milgram at cgpp.com Thu May 28 01:20:48 2026 From: milgram at cgpp.com (J. Milgram) Date: Wed, 27 May 2026 21:20:48 -0400 Subject: [Slackbuilds-users] mutual dependency? [was: sbotools: multiline build options] In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> <1092fe0a-bcd6-46a7-afd1-3741e4896aa9@slacky.it> <26f00add-96bb-4c82-8891-892c0a55a68e@cgpp.com> <39ddbc8d-203d-49c6-b5b6-3ef25b2e6329@cgpp.com> Message-ID: On 5/27/26 10:33, Erich Ritz wrote: > This is the full dependency list required for python-zipp, from my local build log (I use slackrepo to build in a clean chroot): Thank you Erich. Not sure what to do with it, though. There was never any suspicion that there was an actual circular dependency coming from the SBo .info files. I only see it when I try to build python-zipp and python-importlib_metadata packages manually. (See error messages below). FWIW, I have recently rebuilt every one of those dependencies in versions you list. Is there any diagnostic value in running slackrepo on my system to build python-zipp? Not been a slackrepo user, I'd need to figure out how to do the clean chroot bit, so any tips appreciated! thanks Judah On 5/27/26 10:33, Erich Ritz wrote: > On Wednesday, May 27th, 2026 at 9:17 AM, J. Milgram via SlackBuilds-users wrote: > >> python-importlib_metadata and python-zipp really do seem to be pointing >> at each other: >> >> After removing both packages, and attempting to re-install (with >> sboinstall or manually): >> >> The python-zipp build bombs with: >> >> ERROR Missing dependencies: >> setuptools_scm[toml]>=3.4.1 >> importlib-metadata>=4.6 >> >> while python-importlib_metadata seems to need python-zipp, bombing with: >> >> ERROR Missing dependencies: >> setuptools_scm[toml]>=3.4.1 >> importlib-metadata>=4.6 -> zipp>=3.20 >> >> I don't understand why it's complaining about setuptools_scm ... I >> seem to have it: >> >> /var/log/packages/python3-setuptools-scm-opt-8.3.1-noarch-1_SBo >> /var/log/packages/python-setuptools_scm-6.3.2-x86_64-1 >> /var/log/packages/python3-setuptools_scm_git_archive-1.4.1-x86_64-1_SBo >> >> ... though not sure which (if any) of these packages is the one it wants. >> >> So I'm stuck again. Anyone have a next step to suggest? >> >> At least I got python3-setuptools-opt installed. >> >> thanks! >> >> Judah >> > Hi Judah, > > This is the full dependency list required for python-zipp, from my local build log (I use slackrepo to build in a clean chroot): > > Building python/python-zipp (rebuild for updated deps) 2026-02-03 15:47:51 > Verifying source files ... > Installing dependencies ... > python3-flit_core-3.12.0-x86_64-1_SBo: Simplified pkging of Python modules, core b [ 180K] > python3-installer-0.7.0-x86_64-6_SBo: Library for installing Python packages from [ 1.1M] > python3-pyproject-hooks-1.2.0-x86_64-1_SBo: Wrappers to call PEP 517 build backend [ 120K] > python3-build-1.3.0-x86_64-1_SBo: a simple, correct PEP517 package builder ....... [ 230K] > python3-packaging-opt-26.0-noarch-1_SBo: Install packaging in /opt ............... [ 740K] > python3-wheel-0.45.1-x86_64-1_SBo: A built-package format for Python ............. [ 650K] > python3-setuptools-opt-80.10.2-x86_64-1_SBo: Install setuptools from -current in / [ 9.6M] > Running python-zipp.SlackBuild ... ETA 15:48:?? > > ... > > Built ok: python-zipp-3.21.0-x86_64-11_SBo.txz 15:47:53 > Unmounting chroot ... > Backed up: python-zipp-3.21.0-x86_64-10_SBo.txz > :-) python/python-zipp Rebuilt for updated deps (-: > > > > > Erich > -- ===== milgram at cgpp.com 301-257-7069 From milgram at cgpp.com Thu May 28 03:25:10 2026 From: milgram at cgpp.com (J. Milgram) Date: Wed, 27 May 2026 23:25:10 -0400 Subject: [Slackbuilds-users] mutual dependency? [was: sbotools: multiline build options] In-Reply-To: References: <36186d35-1fbe-4fe1-877d-33eface6b8e6@cgpp.com> <70eade69-5d3b-4326-a79b-97ea80e515b7@cgpp.com> <1092fe0a-bcd6-46a7-afd1-3741e4896aa9@slacky.it> <26f00add-96bb-4c82-8891-892c0a55a68e@cgpp.com> <39ddbc8d-203d-49c6-b5b6-3ef25b2e6329@cgpp.com> Message-ID: <3374b373-bd7c-4038-a585-44eaa910b8ce@cgpp.com> On 5/27/26 16:20, fourtysixandtwo wrote: > If you've been using pip to install and uninstall...that's certainly > not helping the situation and is not recommended as root as it cannot > be trusted to apply the proper permissions. Unfortunately I didn't realize this was the case.? Up to now, if I found no Slackbuild,? I'd install with pip. "Don't do that", I guess. > When I previously > suggested removing python-importlib_metadata, I was talking about > removing the slackware SBo package. Understood, and I did exactly that a couple of tries ago. No luck. "pip3 uninstall" was a subsequent act of desperation. > I would start with cleaning up any python stuff not properly installed > via slackware packaging. OK... pip3 list & compare with /var/log/packages -> quite a few pip3-installed packages found and removed. I? shudder to? think what I may have broken along the way... > # as root get a list of anything pip installed and uninstall them. > (If you have had pip install anything as your regular user, that can > cause problems too, but is out of scope for the moment) > pip3 list --user > pip3 uninstall pip3 list --user -> reported two packages, removed both > # sbocheck has a list of "out-of-tree builds...", remove those packages sbocheck tells me: Checking for bumped SlackBuilds...? ? ? No build numbers differ. Checking for out-of-tree builds...? ? ? No out-of-tree _SBo builds. > # one example I know is installed, added zipp and importlib just in case... > removepkg python3-pep517 python-zipp python-importlib_metadata all of these were already? gone > # another old build that might cause issues > removepkg python3-pyproject-metadata done. > > Try to build python3-setuptools-opt again and let us know. I? had already managed to build? it but? just to? make sure: sboinstall --reinstall python3-setuptools-opt Built: python3-flit_core python3-installer python3-pyproject-hooks python3-build python3-packaging-opt python3-wheel python3-setuptools-opt Good. But still same issue with python-zipp and python-importlib_metadata Sleep first, then regroup and try again. thanks! Judah -- ===== milgram at cgpp.com 301-257-7069 From dickson.tim at googlemail.com Thu May 28 07:52:28 2026 From: dickson.tim at googlemail.com (Tim Dickson) Date: Thu, 28 May 2026 08:52:28 +0100 Subject: [Slackbuilds-users] tag query on new project Message-ID: <31ece4d8-94d2-45fc-8566-dbd11f7b24cf@googlemail.com> hi all, I'm working on a new bootloader called elilong, which has a similar conf format as elilo, but (for me at least) manages to boot with "above 4g decoding" and "resize-bar" enabled in the bios, something that elilo on my hardware fails to do. https://www.elilong.sourceforge.io Currently I provide a versioned projectname-version-slackbuild.tar.gz and the versioned source projectname-version.tar.gz (so people don't get confused and download the slackbuild instead of the source.) is there a standard for? the TAG=${TAG:-_SBo}? line when a project provides it's own slackbuild, as well as submitting one to sbo?. thanks, Tim From willysr at slackbuilds.org Fri May 29 14:27:36 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 29 May 2026 21:27:36 +0700 Subject: [Slackbuilds-users] tag query on new project In-Reply-To: <31ece4d8-94d2-45fc-8566-dbd11f7b24cf@googlemail.com> References: <31ece4d8-94d2-45fc-8566-dbd11f7b24cf@googlemail.com> Message-ID: <20260529212736.2d5fd26c@home.slackie.org> >hi all, I'm working on a new bootloader called elilong, which has a >similar conf format as elilo, but (for me at least) manages to boot with >"above 4g decoding" and "resize-bar" enabled in the bios, something that >elilo on my hardware fails to do. >https://www.elilong.sourceforge.io > >Currently I provide a versioned projectname-version-slackbuild.tar.gz >and the versioned source projectname-version.tar.gz (so people don't get >confused and download the slackbuild instead of the source.) >is there a standard for? the TAG=${TAG:-_SBo}? line when a project >provides it's own slackbuild, as well as submitting one to sbo?. >thanks, Tim We don't have standard for TAG besides _SBo, except when you publish a binary packages https://slackbuilds.org/faq/ -- 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 30 12:46:19 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 30 May 2026 19:46:19 +0700 Subject: [Slackbuilds-users] Updates - 20260530.1 Message-ID: <20260530194619.7468c5f4@home.slackie.org> Hi everyone This week, it was planned to remove nodejs (which i did on my branch), but then i didn't realize that forgejo requires it since it was tested on CI against master branch (which still has nodejs before public update). So if you are planning to build forgejo on your machine, please make sure to install nodejs22 or nodejs24-bin first. I will update forgejo on my branch after the public update to reflect the available nodejs version on our repository That's for the bad news, now into the good news :) We are happy to announce that Christoph Willing and 46and2 will be joining us as SBo admins starting this week. They have contributed a lot during in the past few years and we are happy they are onboard with us now. We hope that for next SBo repo version (which we still don't know, don't ask us), the transition should be faster than before. That's all for this week's update, until next week! Happy weekend Sat May 30 12:17:03 UTC 2026 academic/maxima: Trim README blank line. academic/pari-elldata: Fix slack-desc. academic/scidavis: Add set -e, fix qt6 conflict. academic/umfpack: Fix includes. audio/libation-bin: Updated for version 13.4.4 audio/spettro: Added (Music Player). desktop/ClamAV-GUI: Updated for version 1.3.9 desktop/cde: Fix README. desktop/dwm: Updated for version 6.8 (+ new maint). desktop/mimi: Fix download URL. desktop/sun: Update .desktop. desktop/sun: Updated for version 2.5.2. desktop/tty-clock: Bump `BUILD`. desktop/tty-clock: Updated build (+ new maintainer). desktop/ttyplot: Added (Plotting Utility). desktop/wmsysmon: Fix URLs (https). development/Kiro: Updated for version 0.12.224. development/Kiro: Updated for version 0.12.263. development/bruno: Updated for version 3.4.1. development/buf: Updated for version 1.70.0. development/cargo-auditable: Updated for version 0.7.5 development/cbmc: Fix download URLs. development/composer: Updated for version 2.10.0 development/creduce: Fix download URL. development/cudnn: Updated for version 9.22.0.52_13 development/deno-bin:update to version 2.8.0 development/electron-bin: Updated for version 42.2.0 development/f2c: Trim README blank line. development/forgejo: Added (Software Forge). development/gcc14: Handle language selection correctly development/github-desktop: Trim README blank line. development/godot: Updated for version 4.5.2 development/goland: Updated for version 2026.1.2. development/got: update to 0.126 development/idea: Updated for version 2026.1.2. development/jupyter_server: Update README. development/lua-language-server: Trim README blank line. development/meld: Fix to python2. development/meld: Remove unused directory. development/mongodb-compass: Updated for version 1.49.8. development/nodejs18: Update README development/nodejs24-bin:update to version 24.16.0 development/nodejs: Removed (EOL). development/notepad++: Updated for version 8.9.6.1 development/nwjs: Update README development/open-inventor: Apply upstream manpage patch development/openjdk8: Fix README, .info. development/pinner: Trim README blank line. development/pnpm: Update REQUIRES for nodejs22. development/rider: Updated for version 2026.1.2. development/rust-opt: Updated for version 1.95.0. development/sccache: fix build for i686 target development/vscode-bin: Updated for version 1.122.1. development/vscodium: Updated for version 1.121.03429. development/vstudio: Updated for version 17.4.2 development/witsy: Fix README. development/zed-editor-bin: Updated for version 1.4.2. development/zed-editor-bin: Updated for version 1.4.4. games/crispy-doom: Fix download URL. games/supertux: Add new dep. games/supertux: Updated for version 0.7.0. games/wesnoth: Fix sbolint nitpick. games/wings2: Added (Network Game). games/xconq: Trim README blank line. git/ci: Update CI dependencies. graphics/Blender: Updated for version 5.1.2 graphics/paraview: Updated for version 6.1.1 graphics/scantailor-advanced: Updated for version 1.2.1. graphics/weasis-bin: Fix sbolint nitpick. ham/Xastir: Trim README blank line. ham/fbb: Trim README blank line. ham/hamclock: Trim README blank line. ham/tqsl: Updated for version 2.8.5. libraries/OpenSceneGraph: Additional requirements gdal, libgta and open-inventor libraries/VTK: Updated for version 9.6.2 libraries/VulkanSceneGraph: Added (Scene Graph Library). libraries/fzssh: Updated for version 1.3.0. libraries/gflags: New maintainer. Updated for version 2.3.0 libraries/grpc: Update README, mark as x86_64 only libraries/gssdp: Updated for version 1.6.5. libraries/gupnp: Updated for version 1.6.10. libraries/libfilezilla: Updated for version 0.56.0. libraries/libgta: Remove obsolete doxyfile tags. libraries/libslirp:updated to version 4.9.2 libraries/pam_usb: Updated for version 0.9.2 libraries/qt6: Update README libraries/rocksdb: New maintainer. Updated for version 7.10.2 Changed to Cmake build system. libraries/vmaf: Slackbuild script update libraries/zxing-cpp: Updated for version 2.3.0. misc/html2ps: Fix runtime bug. misc/ollama: Updated for version 0.24.0. multimedia/MuseScore: Updated for version 4.7.2 multimedia/kaffeine-mozilla: Clean up build. multimedia/lightspark: Updated for version 0.9.0. multimedia/rtmpdump: Fix homepage URL. network/DownTube: Add a needed patch network/bitcoin-knots: Updated for version 20260508. network/chawan: updated for version 0.4.1 network/choqok: Trim README blank line. network/cisco-secure-client-vpn: Fix README, slack-desc. network/copyparty: updated for version 1.20.16 network/electrs: Updated for version 0.11.1. network/element-desktop-bin: Updated for version 1.12.20. network/element-desktop: Updated for version 1.12.20. network/helium-browser: Updated for version 0.12.4.1 network/libressl: update to 4.3.2 network/librewolf: Updated for version 151.0.1_2 network/libtls: update to 4.3.2 network/modemu2k: Updated for version 0.2.1. network/msmtp: update to 1.8.32 network/nginx: Updated for version 1.30.2 network/ngrok: Fix MD5SUM. network/opera: Updated for version 131.0.5877.97 network/palemoon-bin: Fix download URL. network/palemoon: Fix sbolint TAG nitpick. network/pounce: update to 3.2 network/pound: No tabs in README. network/purple-gowhatsapp: Stop writing to $CWD, add set -e. network/rclone-src: Updated for version 1.74.2 network/repo: Clean up slack-desc. network/sfeed: update to 2.4 network/syncthingtray-bin: Updated for version 2.1.1. network/vivaldi: Updated for version 8.0.4033.35. network/warpinator: Update for 2.0.4 network/xmrig: Updated for version 6.26.0. network/zdns: Updated for version 2.1.1. network/zen-browser: Updated for version 1.20b network/zmap: Updated for version 4.4.0. office/Joplin: Updated for version 3.6.14. office/gmdb2: Trim README blank line. office/hebcal: Updated for version 5.9.8. office/ledger-live: Updated for version 4.6.0. office/lyx: Updated for version 2.5.1. office/python3-mintotp: Added (TOTP Implementation). office/qownnotes: Updated for version 26.5.17. office/xed: Added (Text Editor). office/xreader: Update for 4.6.5 perl/MoarVM: Updated for version 2026.05 perl/nqp: Updated for version 2026.05 perl/perl-Pod-POM-View-Restructured: Fix slack-desc, make noarch. perl/perl-http-daemon: Updated for version 6.17 perl/rakudo: Updated for version 2026.05 perl/zef: Updated for version 1.1.3 python/Kallithea: Update README. python/kallithea-frontend: Update README. python/python2-nuitka: Updated for version 4.1.1 python/python3-capstone: Updated for version 5.0.9 python/python3-grpcio: Update README. python/python3-nuitka: Updated for version 4.1.1 python/python3-pint: Trim README blank line. python/python3-pipx: Trim README blank line. python/python3-pypdf: Updated for version 6.12.1 python/python3-zeroconf: Backport other security fixes ruby/ruby-build: Updated for version 20260520. system/7zip: Updated to 26.01 system/B-em: Updated for version 20260527_dc65698 system/Iosevka-aile: Updated for version 34.6.1. system/Iosevka-core: update to 34.6.0 system/Iosevka-core: update to 34.6.1 system/Iosevka-etoile: Updated for version 34.6.1. system/Iosevka-slab: Updated for version 34.6.1 system/Iosevka: Updated for version 34.6.1 system/brother-hll2400d-cups: Trim README blank line. system/dfm: Update script system/fzf: Updated for version 0.73.1. system/goaccess: Updated for version 1.10.2. system/incus: Updated for version 7.1 system/lxcfs:updated to version 4.0.12 system/nerdctl: Updated for version 2.3.1 system/netdata: Update README. system/nvidia-driver: Updated for version 595.80. system/nvidia-kernel: Updated for version 595.80. system/nvidia-legacy580-driver: Updated for version 580.159.04. system/nvidia-legacy580-kernel: Updated for version 580.159.04. system/openrazer-daemon: Updated for version 3.12.3. system/openrazer-kernel: Updated for version 3.12.3. system/pkg: Updated for version v0.9.0. system/sarasa-gothic: Updated for version 1.0.39. system/sbpkg: Updated for version 2.0.2. system/xfile: Updated for version 1.2.0. system/zellij-bin: Updated for version 0.44.3. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 870 bytes Desc: OpenPGP digital signature URL: From mab974 at misouk.com Sat May 30 16:27:39 2026 From: mab974 at misouk.com (Mab974) Date: Sat, 30 May 2026 20:27:39 +0400 Subject: [Slackbuilds-users] perl-http-daemon not built Message-ID: <20260530202739.2eb609e8b750d753fb09e726@misouk.com> Hi, Source file (6.17) does not contain the required Makefile.PL file. Build.PL present. Regards -*- From mrvladislavovich at gmail.com Sun May 31 04:59:41 2026 From: mrvladislavovich at gmail.com (=?UTF-8?B?0K7RgNC40Lkg0KHQvtGA0L7QutC40L0=?=) Date: Sun, 31 May 2026 08:59:41 +0400 Subject: [Slackbuilds-users] perl-http-daemon: fix build failure (migration from Makefile.PL to Build.PL) Message-ID: Hi, The perl-http-daemon package has been updated upstream, and they switched their build system from Makefile.PL to Build.PL (specifically using Module::Build::Tiny). Because of this, the current SlackBuild fails to build. Here is the corrected build block for the .SlackBuild script that fixes the issue: echo "y" | CFLAGS="$SLKCFLAGS" perl Build.PL \ --prefix=/usr \ --installdirs=vendor \ --install_path libdoc=/usr/man/man3 ./Build ./Build install --destdir="${PKG}" -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrvladislavovich at gmail.com Sun May 31 05:00:23 2026 From: mrvladislavovich at gmail.com (=?UTF-8?B?0K7RgNC40Lkg0KHQvtGA0L7QutC40L0=?=) Date: Sun, 31 May 2026 09:00:23 +0400 Subject: [Slackbuilds-users] perl-http-daemon not built In-Reply-To: <20260530202739.2eb609e8b750d753fb09e726@misouk.com> References: <20260530202739.2eb609e8b750d753fb09e726@misouk.com> Message-ID: Hi, echo "y" | CFLAGS="$SLKCFLAGS" perl Build.PL \ --prefix=/usr \ --installdirs=vendor \ --install_path libdoc=/usr/man/man3 ./Build ./Build install --destdir="${PKG}" ??, 30 ??? 2026??. ? 20:27, Mab974 : > Hi, > > Source file (6.17) does not contain the required Makefile.PL file. > Build.PL present. > > Regards > > -*- > _______________________________________________ > 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 31 09:43:26 2026 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 31 May 2026 16:43:26 +0700 Subject: [Slackbuilds-users] perl-http-daemon not built In-Reply-To: References: <20260530202739.2eb609e8b750d753fb09e726@misouk.com> Message-ID: <20260531164326.1a26e09c@home.slackie.org> >Hi, >echo "y" | CFLAGS="$SLKCFLAGS" perl Build.PL \ >--prefix=/usr \ > --installdirs=vendor \ > --install_path libdoc=/usr/man/man3 >./Build >./Build install --destdir="${PKG}" > >??, 30 ??? 2026??. ? 20:27, Mab974 : > >> Hi, >> >> Source file (6.17) does not contain the required Makefile.PL file. >> Build.PL present. Already fixed on my branch https://git.slackbuilds.org/slackbuilds/commit/?id=374c4d6b0 -- 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 dickson.tim at googlemail.com Sun May 31 20:36:14 2026 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sun, 31 May 2026 21:36:14 +0100 Subject: [Slackbuilds-users] issue submitting new slackbuild Message-ID: <139461f6-ea9b-40ec-953b-34c4886a6c3b@googlemail.com> I just tried to submit a new slackbuild (elilong.tar.gz) via the web form and got the error message Submission failed: Could not find elilong/elilong.info Could not find elilong/README Could not find elilong/elilong.SlackBuild however, running tar -xzf elilong.tar.gz cd elilong ls -l gives -rw-r--r-- 1 root root? 410 May 17 21:37 README -rw-r--r-- 1 root root? 287 May? 3 14:16 doinst.sh -rwxr-xr-x 1 root root 2904 May 31 19:57 elilong.SlackBuild* -rw-r--r-- 1 root root? 307 May 31 19:57 elilong.info -rw-r--r-- 1 root root? 917 May 30 14:48 slack-desc i did try a couple of times just in case it was me. is the submission form broken at the moment? regards, Tim From arnaud.garcia-fernandez at laposte.net Sun May 31 20:54:15 2026 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Sun, 31 May 2026 20:54:15 +0000 Subject: [Slackbuilds-users] issue submitting new slackbuild In-Reply-To: <139461f6-ea9b-40ec-953b-34c4886a6c3b@googlemail.com> References: <139461f6-ea9b-40ec-953b-34c4886a6c3b@googlemail.com> Message-ID: The files needs to be inside a directory named by the name of the package, here : elilong/elilong.info etc. - Yth. Le 31 mai 2026 20:36:14 UTC, Tim Dickson via SlackBuilds-users a ?crit : >I just tried to submit a new slackbuild (elilong.tar.gz) via the web form >and got the error message > >Submission failed: >Could not find elilong/elilong.info >Could not find elilong/README >Could not find elilong/elilong.SlackBuild > >however, >running >tar -xzf elilong.tar.gz >cd elilong >ls -l >gives >-rw-r--r-- 1 root root? 410 May 17 21:37 README >-rw-r--r-- 1 root root? 287 May? 3 14:16 doinst.sh >-rwxr-xr-x 1 root root 2904 May 31 19:57 elilong.SlackBuild* >-rw-r--r-- 1 root root? 307 May 31 19:57 elilong.info >-rw-r--r-- 1 root root? 917 May 30 14:48 slack-desc > >i did try a couple of times just in case it was me. >is the submission form broken at the moment? >regards, Tim >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - https://slackbuilds.org/faq/ > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: