From slackbuilds at ldsp.nl  Fri Apr  4 09:04:22 2025
From: slackbuilds at ldsp.nl (slackbuilds at ldsp.nl)
Date: Fri, 4 Apr 2025 11:04:22 +0200
Subject: [Slackbuilds-users] Audacity?
Message-ID: <da9ee771-aba4-4a26-b499-4fd54ffdd3ec@ldsp.nl>

Hello,

The current Slackbuild is for Audacity 3: 
https://slackbuilds.org/repository/15.0/audio/audacity/
But in each upgrade, more and more functions of the program stop working.
The latest official version is Audacity 3.7, but there are already lots 
of complaints: 
https://forum.audacityteam.org/t/audacity-3-7-is-out-now/122046

The latest Audacity 2 version in the Slackbuild is 2.4.1 . There is a 
2.4.2 version (https://github.com/audacity/audacity/releases?page=5)
Trying to build?2.4.1 and 2.4.2 both give errors related to wxWidgets.

Is it possible to bring back the Audacity 2 Slackbuild, maybe as a 
separate "audacity2" Slackbuild (if it's possible to get it to build)?

Or, does anyone know a good audio editing alternative that would be 
usable on Slackware?

Regards,
LDSP


From urchlay at slackware.uk  Fri Apr  4 09:15:11 2025
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 4 Apr 2025 05:15:11 -0400 (EDT)
Subject: [Slackbuilds-users] Audacity?
In-Reply-To: <da9ee771-aba4-4a26-b499-4fd54ffdd3ec@ldsp.nl>
References: <da9ee771-aba4-4a26-b499-4fd54ffdd3ec@ldsp.nl>
Message-ID: <5fd52e8-54b8-f365-aea0-bf7fe341356d@slackware.uk>



On Fri, 4 Apr 2025, slackbuilds--- via SlackBuilds-users wrote:

> The latest Audacity 2 version in the Slackbuild is 2.4.1 . There is a 
> 2.4.2 version (https://github.com/audacity/audacity/releases?page=5)
> Trying to build?2.4.1 and 2.4.2 both give errors related to wxWidgets.
>
> Is it possible to bring back the Audacity 2 Slackbuild, maybe as a 
> separate "audacity2" Slackbuild (if it's possible to get it to build)?

If you can get it to build, you're welcome to submit an audacity2
SlackBuild. Maybe name it "audacity-legacy2" or "audacity2-legacy",
to make it obvious that it's an older version.

> Or, does anyone know a good audio editing alternative that would be 
> usable on Slackware?

You could try ardour. It might be a bit "heavy" if you're used to
audacity, but it's highly functional.

From rizitis at gmail.com  Fri Apr  4 11:53:27 2025
From: rizitis at gmail.com (=?UTF-8?B?zpnPic6szr3Ovc63z4I=?=)
Date: Fri, 4 Apr 2025 14:53:27 +0300
Subject: [Slackbuilds-users] Audacity?
In-Reply-To: <5fd52e8-54b8-f365-aea0-bf7fe341356d@slackware.uk>
References: <da9ee771-aba4-4a26-b499-4fd54ffdd3ec@ldsp.nl>
 <5fd52e8-54b8-f365-aea0-bf7fe341356d@slackware.uk>
Message-ID: <CADV5w3wb_yMB0bXOji13s0yA-sO74goiSobBxL1g8hyTLSSgbA@mail.gmail.com>

ocenaudio might be a good alternative for a bin slackbuild, this app
is what most users use nowadays...
DownloadPage: https://www.ocenaudio.com/download
version i tested is 13.14.10 looks ok in 15.0 and current, but not hard tested.
it might be problem the source download
I found this link working with wget  :
https://www.ocenaudio.com/downloads/index.php/ocenaudio_debian10.deb
required:"jack"


???? ??? 4 ??? 2025 ???? 12:15??.?., ?/? B. Watson
<urchlay at slackware.uk> ??????:
>
>
>
> On Fri, 4 Apr 2025, slackbuilds--- via SlackBuilds-users wrote:
>
> > The latest Audacity 2 version in the Slackbuild is 2.4.1 . There is a
> > 2.4.2 version (https://github.com/audacity/audacity/releases?page=5)
> > Trying to build 2.4.1 and 2.4.2 both give errors related to wxWidgets.
> >
> > Is it possible to bring back the Audacity 2 Slackbuild, maybe as a
> > separate "audacity2" Slackbuild (if it's possible to get it to build)?
>
> If you can get it to build, you're welcome to submit an audacity2
> SlackBuild. Maybe name it "audacity-legacy2" or "audacity2-legacy",
> to make it obvious that it's an older version.
>
> > Or, does anyone know a good audio editing alternative that would be
> > usable on Slackware?
>
> You could try ardour. It might be a bit "heavy" if you're used to
> audacity, but it's highly functional._______________________________________________
> 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  Fri Apr  4 12:58:01 2025
From: rizitis at gmail.com (=?UTF-8?B?zpnPic6szr3Ovc63z4I=?=)
Date: Fri, 4 Apr 2025 15:58:01 +0300
Subject: [Slackbuilds-users] Audacity?
In-Reply-To: <CADV5w3wb_yMB0bXOji13s0yA-sO74goiSobBxL1g8hyTLSSgbA@mail.gmail.com>
References: <da9ee771-aba4-4a26-b499-4fd54ffdd3ec@ldsp.nl>
 <5fd52e8-54b8-f365-aea0-bf7fe341356d@slackware.uk>
 <CADV5w3wb_yMB0bXOji13s0yA-sO74goiSobBxL1g8hyTLSSgbA@mail.gmail.com>
Message-ID: <CADV5w3xY+p8YhMyfHCx6e-qG-Aa=wYHb2pTTG4Jzqxr_qLRWww@mail.gmail.com>

https://www.ocenaudio.com/downloads/index.php/ocenaudio_debian10_3_14_10.deb

This is the best link which work fine and include version also.

???? ??? 4 ??? 2025 ???? 2:53??.?., ?/? ??????? <rizitis at gmail.com> ??????:
>
> ocenaudio might be a good alternative for a bin slackbuild, this app
> is what most users use nowadays...
> DownloadPage: https://www.ocenaudio.com/download
> version i tested is 13.14.10 looks ok in 15.0 and current, but not hard tested.
> it might be problem the source download
> I found this link working with wget  :
> https://www.ocenaudio.com/downloads/index.php/ocenaudio_debian10.deb
> required:"jack"
>
>
> ???? ??? 4 ??? 2025 ???? 12:15??.?., ?/? B. Watson
> <urchlay at slackware.uk> ??????:
> >
> >
> >
> > On Fri, 4 Apr 2025, slackbuilds--- via SlackBuilds-users wrote:
> >
> > > The latest Audacity 2 version in the Slackbuild is 2.4.1 . There is a
> > > 2.4.2 version (https://github.com/audacity/audacity/releases?page=5)
> > > Trying to build 2.4.1 and 2.4.2 both give errors related to wxWidgets.
> > >
> > > Is it possible to bring back the Audacity 2 Slackbuild, maybe as a
> > > separate "audacity2" Slackbuild (if it's possible to get it to build)?
> >
> > If you can get it to build, you're welcome to submit an audacity2
> > SlackBuild. Maybe name it "audacity-legacy2" or "audacity2-legacy",
> > to make it obvious that it's an older version.
> >
> > > Or, does anyone know a good audio editing alternative that would be
> > > usable on Slackware?
> >
> > You could try ardour. It might be a bit "heavy" if you're used to
> > audacity, but it's highly functional._______________________________________________
> > 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  Fri Apr  4 13:00:32 2025
From: rizitis at gmail.com (=?UTF-8?B?zpnPic6szr3Ovc63z4I=?=)
Date: Fri, 4 Apr 2025 16:00:32 +0300
Subject: [Slackbuilds-users] Audacity?
In-Reply-To: <CADV5w3xY+p8YhMyfHCx6e-qG-Aa=wYHb2pTTG4Jzqxr_qLRWww@mail.gmail.com>
References: <da9ee771-aba4-4a26-b499-4fd54ffdd3ec@ldsp.nl>
 <5fd52e8-54b8-f365-aea0-bf7fe341356d@slackware.uk>
 <CADV5w3wb_yMB0bXOji13s0yA-sO74goiSobBxL1g8hyTLSSgbA@mail.gmail.com>
 <CADV5w3xY+p8YhMyfHCx6e-qG-Aa=wYHb2pTTG4Jzqxr_qLRWww@mail.gmail.com>
Message-ID: <CADV5w3w8badWk3_=RDCPb3zFarihNEB9cV7HgNCoOwtYnPGxdw@mail.gmail.com>

sorry ignore previous mail

???? ??? 4 ??? 2025 ???? 3:58??.?., ?/? ??????? <rizitis at gmail.com> ??????:
>
> https://www.ocenaudio.com/downloads/index.php/ocenaudio_debian10_3_14_10.deb
>
> This is the best link which work fine and include version also.
>
> ???? ??? 4 ??? 2025 ???? 2:53??.?., ?/? ??????? <rizitis at gmail.com> ??????:
> >
> > ocenaudio might be a good alternative for a bin slackbuild, this app
> > is what most users use nowadays...
> > DownloadPage: https://www.ocenaudio.com/download
> > version i tested is 13.14.10 looks ok in 15.0 and current, but not hard tested.
> > it might be problem the source download
> > I found this link working with wget  :
> > https://www.ocenaudio.com/downloads/index.php/ocenaudio_debian10.deb
> > required:"jack"
> >
> >
> > ???? ??? 4 ??? 2025 ???? 12:15??.?., ?/? B. Watson
> > <urchlay at slackware.uk> ??????:
> > >
> > >
> > >
> > > On Fri, 4 Apr 2025, slackbuilds--- via SlackBuilds-users wrote:
> > >
> > > > The latest Audacity 2 version in the Slackbuild is 2.4.1 . There is a
> > > > 2.4.2 version (https://github.com/audacity/audacity/releases?page=5)
> > > > Trying to build 2.4.1 and 2.4.2 both give errors related to wxWidgets.
> > > >
> > > > Is it possible to bring back the Audacity 2 Slackbuild, maybe as a
> > > > separate "audacity2" Slackbuild (if it's possible to get it to build)?
> > >
> > > If you can get it to build, you're welcome to submit an audacity2
> > > SlackBuild. Maybe name it "audacity-legacy2" or "audacity2-legacy",
> > > to make it obvious that it's an older version.
> > >
> > > > Or, does anyone know a good audio editing alternative that would be
> > > > usable on Slackware?
> > >
> > > You could try ardour. It might be a bit "heavy" if you're used to
> > > audacity, but it's highly functional._______________________________________________
> > > 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 phalange at komputermatrix.com  Fri Apr  4 15:01:39 2025
From: phalange at komputermatrix.com (phalange at komputermatrix.com)
Date: Fri, 04 Apr 2025 11:01:39 -0400
Subject: [Slackbuilds-users] Audacity?
In-Reply-To: <5fd52e8-54b8-f365-aea0-bf7fe341356d@slackware.uk>
References: <da9ee771-aba4-4a26-b499-4fd54ffdd3ec@ldsp.nl>
 <5fd52e8-54b8-f365-aea0-bf7fe341356d@slackware.uk>
Message-ID: <9c56c66bd2b9566350dc23208b345ba0@komputermatrix.com>

On 2025-04-04 05:15, B. Watson wrote:
> On Fri, 4 Apr 2025, slackbuilds--- via SlackBuilds-users wrote:
> 
>> The latest Audacity 2 version in the Slackbuild is 2.4.1 . There is a 
>> 2.4.2 version (https://github.com/audacity/audacity/releases?page=5)
>> Trying to build?2.4.1 and 2.4.2 both give errors related to wxWidgets.
>> 
>> Is it possible to bring back the Audacity 2 Slackbuild, maybe as a 
>> separate "audacity2" Slackbuild (if it's possible to get it to build)?
> 
> If you can get it to build, you're welcome to submit an audacity2
> SlackBuild. Maybe name it "audacity-legacy2" or "audacity2-legacy",
> to make it obvious that it's an older version.
> 
>> Or, does anyone know a good audio editing alternative that would be 
>> usable on Slackware?
> 
> You could try ardour. It might be a bit "heavy" if you're used to
> audacity, but it's highly functional.
> _______________________________________________
> 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/

The AppImage for v3.7.3 works on Slack15, but you have to download the 
AppImage for Ubuntu 20.04, NOT the one for 22.04.

https://www.audacityteam.org/download/linux/

-AP

From willysr at slackbuilds.org  Sat Apr  5 02:52:55 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 5 Apr 2025 09:52:55 +0700
Subject: [Slackbuilds-users] Updates - 20250405.1
Message-ID: <4370fc07-e4f3-44c6-b9ec-e8b69d2a791b@slackbuilds.org>

Sat Apr  5 02:45:44 UTC 2025
academic/pysam: upgraded to version 0.23.0.
audio/dopamine-bin: Added (Audio Player).
audio/volctl: Updated for version 0.9.5
desktop/awf: Updated for version 2.9.0.
desktop/dunst: Updated for version 1.12.2
desktop/flat-remix: Added (Icon Theme).
desktop/flat-remix: Fix script.
desktop/gammastep: Updated for version 2.0.11.
desktop/human-gtk-theme: Updated for version 2.3.0.
desktop/icewm: Updated for version 3.7.3.
desktop/vdesk: Added (Virtual Desktop Manager).
develop/pnpm: Updated for version 10.7.1.
development/amazon-corretto: Updated for version 17.0.14.7.1.
development/apache-ivy: Update script.
development/aws-cdk: Updated for version 2.1007.0.
development/composer: Updated for version 2.8.7
development/d-tools: Updated for version 2.111.0
development/dmd: Updated for version 2.111.0
development/gambas3: Updated for version 3.20.2.
development/geany-themes: Added (Color Scheme).
development/gnuradio: Updated for version 3.10.12.0.
development/jenv: Updated for version 0.5.7.
development/mongodb-compass: Updated for version 1.46.0.
development/netbeans: Updated for version 25.
development/nodejs: Updated for version 20.19.0.
development/poedit: Updated for version 3.6.
development/postman: Revert to 11.28.4.
development/protobuf3: Updated for version 30.2.
development/sbcl: Updated for version 2.5.3
development/scala3: Added (Object-oriented Programming Language).
development/sourcegit: Updated for version 2025.11
development/tflint: Updated for version 0.56.0.
development/vscode-bin: Updated for version 1.99.0.
development/witsy: Updated for version 2.4.3
games/ddnet: Updated for version 19.1
games/gzdoom: Updated for version 4.14.1.
games/pysolfc: Updated for version 3.2.0.
games/scid_vs_pc: Fix MD5SUM.
games/stockfish: Updated for version 17.1.
games/yamagi-quake2: Updated for version 8.50
graphics/fstl: Added (STL Viewer).
graphics/yed: Updated for version 3.25.1.
ham/dab_lib: Updated for version 20250329.dfacdcd3.
ham/gqrx-sdr: Updated for version 2.17.6.
ham/gridtracker2: Updated for version 2.250402.0.
ham/qlog: Updated for version 0.43.0.
libraries/LucenePlusPlus: Fix build with newer cmake and boost.
libraries/afflib: Updated for version 3.7.21.
libraries/digimend-kernel-drivers: Updated to newer source commits.
libraries/libqcow: Updated for version 20240308.
libraries/libvhdi: Updated for version 20240509.
libraries/libvmdk: Updated for version 20240510.
misc/autofirma: Use zulu-openjdk8.
misc/yara: Updated for version 4.5.2.
network/abdownloadmanager-bin: Added (Download Manager).
network/brave-browser: updated for version 1.77.95
network/cinny-desktop: Updated for version 4.6.0.
network/discord: Fix MD5SUM.
network/dooble: Added (Web Browser).
network/dooble: Fix 32bit build
network/dropbox: Updated for version 221.4.5365.
network/exim: Updated for version 4.98.2.
network/floorp-bin: Updated for version 11.25.0.
network/fwknop: Updated for version 2.6.11.
network/gallery-dl: Updated for version 1.29.3.
network/newsboat: Updated for version 2.39.
network/onedrive:upgraded to version 2.5.5
network/onionshare: Fix MD5SUM.
network/signal-desktop: Updated for version 7.49.0.
network/slack: Updated for version 4.43.51.
network/syncthingtray-bin: Updated for version 1.7.4.
network/tixati: Updated for version 3.33_1.
network/tor-browser: Updated for version 14.0.9.
network/vivaldi: updated for version 7.3.3635.7
network/yt-dlp: Updated for version 2025.03.31.
office/LibreOffice: Updated for version 25.2.2.2
office/MasterPDFEditor: Updated for version 5.9.89.
office/OpenAudible-bin: Added (Audible audiobook Application).
office/ishmael: Updated for version 1.04.
python/certbot-dns-cloudflare: Updated for version 3.3.0
python/nanobind: Added (Binding Library).
python/pefile: Updated for version 2024.8.26.
python/python-debian: Fix MD5SUM.
python/python-qrcode: Updated for version 8.1.
python/python3-aiohttp: Updated for version 3.11.16.
python/python3-grpcio: Revert workaround for building the 
python3-grpcio-tools module
python/python3-lazy_loader: Fix MD5SUM and script.
python/python3-lazy_loader: Fix github URL.
python/python3-multidict: Updated for version 6.3.2.
python/yara-python: Removed (use python2/3-yara).
system/CNS11643-kai-font: Fix MD5SUM.
system/CNS11643-sung-font: Fix MD5SUM.
system/CPU-X: Updated for version 5.2.0.
system/Iosevka-aile: Updated for version 33.2.0.
system/Iosevka-etoile: Updated for version 33.2.0.
system/Iosevka-slab: Updated for version 33.2.0
system/Iosevka: Updated for version 33.2.0
system/OpenSnitch: Edit README
system/apple-fonts-NY: Updated for version 2025.
system/apple-fonts-SF: Updated for version 2025.
system/atop: Updated for version 2.11.1.
system/bulk_extractor: Updated for version 2.1.1.
system/docker-buildx: Updated for version 0.22.0.
system/fastfetch: Updated for version 2.40.2.
system/fio: Fix MD5SUM.
system/fzf: Updated for version 0.61.0.
system/jenkins: Updated for version 2.492.3.
system/jnv-bin: Added (Interactive JSON Viewer).
system/netdata: Make sure needed dirs are present at runtime
system/netdata: Switch to cmake to build.
system/netdata: Updated for versin 2.3.2.
system/netdata: clean up dupe operation in rc.netdata
system/netdata: have logrotate su to specific user/group to rotate
system/nvidia-legacy470-kernel: Update script.
system/sff: Added (File Finder).
system/volatility3: Updated for version 2.11.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250405/a40f9112/attachment-0001.asc>

From willysr at slackbuilds.org  Mon Apr  7 08:29:06 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 7 Apr 2025 15:29:06 +0700
Subject: [Slackbuilds-users] Scripts up for grabs
Message-ID: <859b9f88-ce2e-4781-bf26-210abb41cc5b@slackbuilds.org>

Due to some reasons, these scripts are now up for grab as the maintainer 
is no longer available to maintain this scripts.

fzy
gem
gemget
gmi100
grb
instaloader
kiwix-tools-bin
kjv
sent
translate-shell
vul
xmouseless
xwallpaper
yt-dlp-bin
fish

Let us know if anyone is interested taking over maintainership

thank you


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250407/7b81dc87/attachment.asc>

From willysr at slackbuilds.org  Mon Apr  7 08:32:23 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 7 Apr 2025 15:32:23 +0700
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <859b9f88-ce2e-4781-bf26-210abb41cc5b@slackbuilds.org>
References: <859b9f88-ce2e-4781-bf26-210abb41cc5b@slackbuilds.org>
Message-ID: <bc2b8d6e-2fe7-43d4-b37d-98fb4b60bc30@slackbuilds.org>

> Due to some reasons, these scripts are now up for grab as the maintainer 
> is no longer available to maintain this scripts.
> 
> fzy
> gem
> gemget
> gmi100
> grb
> instaloader
> kiwix-tools-bin
> kjv
> sent
> translate-shell
> vul
> xmouseless
> xwallpaper
> yt-dlp-bin
> fish

oh, i missed one

stardict

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250407/c8321988/attachment.asc>

From rizitis at gmail.com  Mon Apr  7 08:39:34 2025
From: rizitis at gmail.com (=?UTF-8?B?zpnPic6szr3Ovc63z4I=?=)
Date: Mon, 7 Apr 2025 11:39:34 +0300
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <bc2b8d6e-2fe7-43d4-b37d-98fb4b60bc30@slackbuilds.org>
References: <859b9f88-ce2e-4781-bf26-210abb41cc5b@slackbuilds.org>
 <bc2b8d6e-2fe7-43d4-b37d-98fb4b60bc30@slackbuilds.org>
Message-ID: <CADV5w3y3dT1GxRiDCJZO5iyF=rXt4q6vN+g+SWAGS5274vNGrw@mail.gmail.com>

I want grb for sure, and late this week i will answer for others if left.

???? ??? 7 ??? 2025, 11:32??.?. ? ??????? Willy Sudiarto Raharjo <
willysr at slackbuilds.org> ??????:

> > Due to some reasons, these scripts are now up for grab as the maintainer
> > is no longer available to maintain this scripts.
> >
> > fzy
> > gem
> > gemget
> > gmi100
> > grb
> > instaloader
> > kiwix-tools-bin
> > kjv
> > sent
> > translate-shell
> > vul
> > xmouseless
> > xwallpaper
> > yt-dlp-bin
> > fish
>
> oh, i missed one
>
> stardict
>
> --
> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250407/81b50b27/attachment.htm>

From rizitis at gmail.com  Mon Apr  7 09:15:54 2025
From: rizitis at gmail.com (=?UTF-8?B?zpnPic6szr3Ovc63z4I=?=)
Date: Mon, 7 Apr 2025 12:15:54 +0300
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <CADV5w3y3dT1GxRiDCJZO5iyF=rXt4q6vN+g+SWAGS5274vNGrw@mail.gmail.com>
References: <859b9f88-ce2e-4781-bf26-210abb41cc5b@slackbuilds.org>
 <bc2b8d6e-2fe7-43d4-b37d-98fb4b60bc30@slackbuilds.org>
 <CADV5w3y3dT1GxRiDCJZO5iyF=rXt4q6vN+g+SWAGS5274vNGrw@mail.gmail.com>
Message-ID: <CADV5w3zezspGpMSVkOsOCCAkXNb_JnmJ=SckXh9RkT1PDzCdtw@mail.gmail.com>

These packages is what I can have if you agree:
grb
jkv
stardict
fzy
sent
translate-shell

???? ??? 7 ??? 2025 ???? 11:39??.?., ?/? ??????? <rizitis at gmail.com> ??????:
>
> I want grb for sure, and late this week i will answer for others if left.
>
> ???? ??? 7 ??? 2025, 11:32??.?. ? ??????? Willy Sudiarto Raharjo <willysr at slackbuilds.org> ??????:
>>
>> > Due to some reasons, these scripts are now up for grab as the maintainer
>> > is no longer available to maintain this scripts.
>> >
>> > fzy
>> > gem
>> > gemget
>> > gmi100
>> > grb
>> > instaloader
>> > kiwix-tools-bin
>> > kjv
>> > sent
>> > translate-shell
>> > vul
>> > xmouseless
>> > xwallpaper
>> > yt-dlp-bin
>> > fish
>>
>> oh, i missed one
>>
>> stardict
>>
>> --
>> 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 willysr at slackbuilds.org  Mon Apr  7 13:43:39 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 7 Apr 2025 20:43:39 +0700
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <CADV5w3zezspGpMSVkOsOCCAkXNb_JnmJ=SckXh9RkT1PDzCdtw@mail.gmail.com>
References: <859b9f88-ce2e-4781-bf26-210abb41cc5b@slackbuilds.org>
 <bc2b8d6e-2fe7-43d4-b37d-98fb4b60bc30@slackbuilds.org>
 <CADV5w3y3dT1GxRiDCJZO5iyF=rXt4q6vN+g+SWAGS5274vNGrw@mail.gmail.com>
 <CADV5w3zezspGpMSVkOsOCCAkXNb_JnmJ=SckXh9RkT1PDzCdtw@mail.gmail.com>
Message-ID: <837cd54f-e230-438f-ad02-9e9bc2bbddbe@slackbuilds.org>

> These packages is what I can have if you agree:
> grb
> jkv
> stardict
> fzy
> sent
> translate-shell

Yeah, go for it


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250407/264eb077/attachment-0001.asc>

From rizitis at gmail.com  Tue Apr  8 10:32:00 2025
From: rizitis at gmail.com (=?UTF-8?B?zpnPic6szr3Ovc63z4I=?=)
Date: Tue, 8 Apr 2025 13:32:00 +0300
Subject: [Slackbuilds-users] About aarch64 support support in TEMPLATE.info
Message-ID: <CADV5w3xTy6COYCgbTDUy5XfDScM1UrSh_5aPPvPoz_9vZ88bjg@mail.gmail.com>

Hello, this is just an information post if you want to discuss-test it.
Personally I dont have aarch64 but almost in every of my
package-bin.SlackBuilds there are
available packages for arm64(aarch64).
Also most projects can be compiled in aarch64 nowadays.
For now there is no option in TEMPLATE.info to support arm64.tarball
for download.
A solution to add them in info file like this:

DOWNLOAD_x86_64="url/amd64.deb \
 url/arm64.deb"
MD5SUM_x86_64="efgh5678_amd64 \
1234abcd_arm64"

works because SlackBuild script picks the correct tarball for compile
or repackage but we still have to download both files locally.

I did tried an TEMPLATE.info like this:
https://github.com/rizitis/sbopkg_hacks/blob/aarch64/template.info

and worked fine with 2 package managers I test (sbopkg,slpkg) in my
x86_64 system, didnt tried sbotools* so far but I dont think it will
have problems also.

I mean if we don't create conflicts for package managers then it wont
be so hard to appears in SlackBuilds.org Web page
Source Downloads:
link/tarbal-i?86
link/tarbal.x86_64
link/tarbal.arm64

For sbopkg specific I made a fork with a small patch and it seems to
work and support this TEMPLATE.info
https://github.com/rizitis/sbopkg_hacks/tree/aarch64

I m sure that for sbotools*, slpkg etc... maintainers will  easy fix
what needed in future (if you adopt this TEMPLATE.info future)

What will probably be hard sbobot, that is something I have no idea
how easy will be or if arm64 tarball will stay as UNTESTED as this is
already happening now.
For me that will be fair enough, but that's me...

Any way this email is just some test i did and one idea for the
future, nothing more.
Thats why i didnt even made PR in sbopkg master branch for my patch.
I have the idea and my knowledge stop here.
The rest (if any) are for more experts!

regards.

From an9wer at SDF.ORG  Tue Apr  8 13:34:04 2025
From: an9wer at SDF.ORG (an9wer at SDF.ORG)
Date: Tue, 8 Apr 2025 13:34:04 +0000
Subject: [Slackbuilds-users] cmake-template.SlackBuild: LIB_SUFFIX or
 CMAKE_INSTALL_LIBDIR for specifying the lib directory
Message-ID: <Z_UlzPl7I_BAHtoD@SDF.ORG>

Hi,

In cmake-template.SlackBuild, the lib directory is specified using 
"-DLIB_SUFFIX=${LIBDIRSUFFIX}":

	https://git.slackbuilds.org/templates/tree/cmake-template.SlackBuild#n121

However, it seems that LIB_SUFFIX is not a standard cmake cache 
variable. Instead, CMAKE_INSTALL_LIBDIR is documented officially:

	https://cmake.org/cmake/help/latest/module/GNUInstallDirs.html

I have noticed some packages, like libgme, only accept LIB_SUFFIX, while 
others, such as librime, only recognize CMAKE_INSTALL_LIBDIR.

I think using both of them would improve compatibility. As evidence, I 
found both are used in Gentoo's cmake.eclass:

	https://github.com/gentoo/gentoo/blob/7d691b86d7c351651aaea129332ccb309d9dd196/eclass/cmake.eclass#L536-L537

-- 
an9wer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cmake-template.SlackBuild.patch
Type: text/x-diff
Size: 432 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250408/12f918c0/attachment.bin>

From willysr at slackbuilds.org  Sat Apr 12 01:53:54 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 12 Apr 2025 08:53:54 +0700
Subject: [Slackbuilds-users] Updates - 20250412.1
Message-ID: <d4720914-fba9-4673-ba0c-0ed35758ac3c@slackbuilds.org>

Sat Apr 12 01:44:31 UTC 2025
academic/bibletime: Updated for version 3.1.1.
academic/grb: Fix permission.
academic/grb: New maintainer
academic/kjv: Fix permission.
academic/kjv: New maintainer
academic/pyCRAC: Fix script.
academic/xiphos: Updated for version 4.3.1.
audio/ocenaudio-bin: Added (Audio Editor).
desktop/ClamAV-GUI: Updated for version 1.1.2
desktop/e16: Fix ownership.
desktop/flat-remix: Change ARCH to noarch, fix broken relative symlink
desktop/hsetroot: Fix source.
desktop/rofi-emoji: Updated for version 3.5.0.
desktop/variety: Updated for version 0.8.13.
development/SQLAlchemy: Updated for version 2.0.40.
development/asar: Added (SNES Assembler).
development/composer: Updated for version 2.8.8
development/dart-sass: Updated for version 1.86.3.
development/fortitude-bin: Fix permission.
development/fortitude-bin: Updated for version 0.7.2
development/golangci-lint: Updated for version 2.0.2.
development/kicad: Updated for version 9.0.1.
development/lm-studio-bin: Added (Run LLM locally).
development/lua-language-server: Updated for version 3.14.0.
development/php84: Updated for version 8.4.6
development/pnpm: Updated for version 10.8.0.
development/regina-rexx: Updated for version 3.9.7.
development/rstudio-desktop: Update for 2024.12.1+563 (+remove 
postgresql dependency)
development/rust-opt: Updated for version 1.86.0.
development/sourcegit: Fix permission.
development/sourcegit: Updated for version 2025.12
development/tofuenv: Updated for version 1.0.7.
development/vscode-bin: Updated for version 1.99.2.
development/witsy: Updated for version 2.4.6
development/wla-dx: Added (Assembler).
development/xmake: Updated for version 2.9.9.
games/PrismLauncher: Updated for version 9.3.
games/mame: Updated for version 0.276.
gis/grass: Remove INSTALL.
gis/librttopo: Fix source.
graphics/xviewer: Update for 3.4.8
ham/SoapyRTLSDR: Updated for version 20250408.bb2d1511.
ham/serialDV: Updated for version 1.1.5.
libraries/dbus-cpp: Version bump to 5.0.4
libraries/eb: Added (C Library).
libraries/gtk-fortran: Fix permission.
libraries/gtk-fortran: Updated for version 4.7.1
libraries/imlib2: Updated for version 1.12.5.
libraries/protobuf-c: Updated for version 1.5.2.
libraries/pylast: Updated for version 5.5.0.
libraries/robin-map: Added -DCMAKE_POLICY_VERSION_MINIMUM for current
libraries/wxPython4: Updated for version 4.2.3.
libraries/wxWidgets: Updated for version 3.2.7.1.
misc/balena-etcher-bin: Added (Flash OS Images).
misc/stardict: Updated for version 3.0.6.2 + new maintainer
multimedia/inputstream.adaptive: Version bump to 21.5.10
multimedia/plexmediaserver: Updated for v 1.41.6.9685_d301f511a.
network/AdGuardHome: Updated for version 0.107.59.
network/abdownloadmanager-bin: Fix script.
network/betterbird-bin: Update script.
network/brave-browser: updated for version 1.77.97
network/discord: Version bump to 0.0.90
network/dnsproxy-bin: Updated for version 0.75.0.
network/dooble: Fix permission.
network/dooble: Updated for version 2025.04.05
network/franz: Updated for version 5.11.0.
network/rustdesk-opt: Updated for version 1.3.9.
network/senpai: Updated for version 0.4.0.
network/signal-desktop: Updated for version 7.50.0.
network/syncthingtray-bin: Fix strip code.
network/syncthingtray-bin: Updated for version 1.7.5.
network/translate-shell: New maintainer
network/udsclient3: Updated for version 4.0.0.
network/vivaldi: updated for version 7.3.3635.9
office/ishmael: Updated for version 1.05.
office/sent: New maintainer
perl/perl-CPAN-Requirements-Dynamic: Updated for version 0.002.
python/jellyfish: Updated for version 1.2.0.
python/mypy: Updated for version 1.15.0.
python/parsel: Removed unused.
python/python3-Flask-Cors: Updated for version 5.0.1.
python/python3-Flask-Security-Too: Updated for version 5.6.1.
python/python3-calver: Updated for version 2025.4.2.
python/python3-cattrs: Updated for version 24.1.3.
python/python3-cython-opt: updated for version 3.0.12
python/python3-dotenv: Updated for version 1.1.0.
python/python3-flit: Updated for version 3.12.0.
python/python3-flit_core: Updated for version 3.12.0.
python/python3-glances: Updated for version 4.3.1.
python/python3-libtmux: Updated for version 0.46.1.
python/python3-maturin: Updated for version 1.8.3.
python/python3-meson-opt: Updated for version 1.7.2.
python/python3-orjson: Updated for version 3.10.16.
python/python3-pdfminer.six: Updated for version 20250327.
python/python3-poetry-core: Updated for version 2.1.2.
python/python3-pydantic-core: Updated for version 2.33.1.
python/python3-pykeepass: Update for 4.1.1.post1
python/python3-pytz: Version bump to 2025.2
python/python3-rich: Updated for version 14.0.0.
python/python3-setuptools-opt: Updated for version 78.1.0.
python/python3-setuptools-rust-opt: Updated for version 1.11.1.
python/python3-tox: Version bump to 4.25.0
python/python3-trove-classifiers: Updated for version 2025.3.19.19.
python/python3-typing-extensions: Version bump to 4.13.1
python/python3-typing-inspection: Added (Runtime typing introspection 
tools).
python/python3-url-normalize: Updated for version 2.2.0.
python/python3-virtualenv: Version bump to 20.30.0
python/tzdata: Updated for version 2025.2.
python/w3lib: Removed unused.
system/c-lcrypt: added to CXXFLAGS -fopenmp needed for OpenMP
system/fonts-mpluscode: Added (Collection of fonts).
system/fzf: Updated for version 0.61.1.
system/fzy: New maintainer
system/google-chrome-the-latest: Updated for version 4.2
system/letsencrypt: Updated for version 4.0.0.
system/nemo: Update for 6.4.5
system/nnn: Update for 5.1
system/sbotools2: Updated for version 2.9.1.
system/slpkg: Updated for version 5.2.2.
system/slpkg: Updated for version 5.2.3.
system/tmuxp: Updated for version 1.55.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250412/c13879ff/attachment.asc>

From mrvladislavovich at gmail.com  Sat Apr 12 16:04:19 2025
From: mrvladislavovich at gmail.com (myrequiem)
Date: Sat, 12 Apr 2025 20:04:19 +0400
Subject: [Slackbuilds-users] SLACKBUILDS.TXT
Message-ID: <6f7db037-257b-43a2-895b-b253d3667e23@gmail.com>

Hello.
Why hasn't https://slackbuilds.org/slackbuilds/15.0/SLACKBUILDS.TXT been
updated?

SLACKBUILDS.TXT 2025-04-04 22:12 is the version from April 4th, but it 
should
be April 11th (In this case ChangeLog.txt 2025-04-11)

For example:
SLACKBUILD NAME: imlib2
SLACKBUILD VERSION: 1.12.4
SLACKBUILD DOWNLOAD: 
https://sourceforge.net/projects/enlightenment/files/imlib2-src/1.12.4/imlib2-1.12.4.tar.xz

But this package was updated to version 1.12.5
Same with other packages that were updated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250412/b6f0773a/attachment.htm>

From fourtysixandtwo at sliderr.net  Sat Apr 12 17:30:53 2025
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Sat, 12 Apr 2025 11:30:53 -0600
Subject: [Slackbuilds-users] SLACKBUILDS.TXT
In-Reply-To: <6f7db037-257b-43a2-895b-b253d3667e23@gmail.com>
References: <6f7db037-257b-43a2-895b-b253d3667e23@gmail.com>
Message-ID: <CAKCXYDFR7WNZqhKFAcgfq42r9GV+Jmt80QSKx6t4v7OCSrqONg@mail.gmail.com>

Looks like they are there now.

CHECKSUMS.md5.asc is the very last file to get updated and just rsync'd for me.

From willysr at slackbuilds.org  Wed Apr 16 01:49:51 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 16 Apr 2025 08:49:51 +0700
Subject: [Slackbuilds-users] About aarch64 support support in
 TEMPLATE.info
In-Reply-To: <CADV5w3xTy6COYCgbTDUy5XfDScM1UrSh_5aPPvPoz_9vZ88bjg@mail.gmail.com>
References: <CADV5w3xTy6COYCgbTDUy5XfDScM1UrSh_5aPPvPoz_9vZ88bjg@mail.gmail.com>
Message-ID: <932b25d1-d41c-4fa4-8364-c78bd6cdc125@slackbuilds.org>

> Hello, this is just an information post if you want to discuss-test it.
> Personally I dont have aarch64 but almost in every of my
> package-bin.SlackBuilds there are
> available packages for arm64(aarch64).
> Also most projects can be compiled in aarch64 nowadays.
> For now there is no option in TEMPLATE.info to support arm64.tarball
> for download.
> A solution to add them in info file like this:
> 
> DOWNLOAD_x86_64="url/amd64.deb \
>   url/arm64.deb"
> MD5SUM_x86_64="efgh5678_amd64 \
> 1234abcd_arm64"
> 
> works because SlackBuild script picks the correct tarball for compile
> or repackage but we still have to download both files locally.
> 
> I did tried an TEMPLATE.info like this:
> https://github.com/rizitis/sbopkg_hacks/blob/aarch64/template.info
> 
> and worked fine with 2 package managers I test (sbopkg,slpkg) in my
> x86_64 system, didnt tried sbotools* so far but I dont think it will
> have problems also.
> 
> I mean if we don't create conflicts for package managers then it wont
> be so hard to appears in SlackBuilds.org Web page
> Source Downloads:
> link/tarbal-i?86
> link/tarbal.x86_64
> link/tarbal.arm64
> 
> For sbopkg specific I made a fork with a small patch and it seems to
> work and support this TEMPLATE.info
> https://github.com/rizitis/sbopkg_hacks/tree/aarch64
> 
> I m sure that for sbotools*, slpkg etc... maintainers will  easy fix
> what needed in future (if you adopt this TEMPLATE.info future)
> 
> What will probably be hard sbobot, that is something I have no idea
> how easy will be or if arm64 tarball will stay as UNTESTED as this is
> already happening now.
> For me that will be fair enough, but that's me...
> 
> Any way this email is just some test i did and one idea for the
> future, nothing more.
> Thats why i didnt even made PR in sbopkg master branch for my patch.
> I have the idea and my knowledge stop here.
> The rest (if any) are for more experts!

This is my *personal* opinion, so other admins might have different idea

1. This is not the official Slackware project although it shares most of 
the basic scripts.
2. Not all of the admins/maintainers have or plans to use this 
architecture on their machines.
3. More burden for maintainers and admins if this is added into the 
template since they need to test more
4. We don't have the CI support as of now for AARCH64, only relies to 
the current maintainer that they test it.
5. Changes needed in our backend infrastructure (website, database, etc) 
and so far no one is interested to take this work.

So i'm not really sure if this is going to work (at least for now until 
most of those points are resolved).


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250416/81558345/attachment.asc>

From urchlay at slackware.uk  Wed Apr 16 03:08:47 2025
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 15 Apr 2025 23:08:47 -0400 (EDT)
Subject: [Slackbuilds-users] About aarch64 support support in
 TEMPLATE.info
In-Reply-To: <932b25d1-d41c-4fa4-8364-c78bd6cdc125@slackbuilds.org>
References: <CADV5w3xTy6COYCgbTDUy5XfDScM1UrSh_5aPPvPoz_9vZ88bjg@mail.gmail.com>
 <932b25d1-d41c-4fa4-8364-c78bd6cdc125@slackbuilds.org>
Message-ID: <5d35a851-db71-fb90-86d9-b3154598321@slackware.uk>



On Wed, 16 Apr 2025, Willy Sudiarto Raharjo wrote:

> 3. More burden for maintainers and admins if this is added into the template 
> since they need to test more
> 4. We don't have the CI support as of now for AARCH64, only relies to the 
> current maintainer that they test it.

These could be addressed like so, in the site FAQ:

"aarch64 is unsupported by the SBo team, though it may be supported
by individual maintainers. Please contact the maintainer if you have
problems with a build on aarch64."

When a maintainer gets contacted, it's up to him to either fix the
problem for the aarch64 user, or say "Sorry, I don't have time to
support aarch64, could you send me a patch?"... and if the user
sends a patch, the maintainer can add it to the build. If not, the
maintainer can at least put "This doesn't work on aarch64" in his
README, to save other aarch64 users from wasting time.

This isn't ideal for aarch64 users (it makes aarch64 a "second class"
architecture), but it's better than not being supported at all.

Point 4 (the CI thing) could exist someday, even though it doesn't now.

> 5. Changes needed in our backend infrastructure (website, database, etc) and 
> so far no one is interested to take this work.

This could be simpler than you think. Basically, all that's needed for
*minimal* aarch64 support would be to allow the DOWNLOAD_aarch64 and
MD5SUM_aarch64 keys in the .info file... and *ignore* them. The script
that reads .info files and populates the database would just have to
allow these keys to exist in the file, but not do anything with them.

The rest of the site wouldn't need changing, and neither would the
database.

The end result would be, aarch64 download URLs wouldn't be shown
on the site, but they would be in the .info files. If you went to
http://slackbuilds.org/repository/15.0/<category>/<build>/ in a
browser, you would only see the x86 and x86_64 downloads listed
"Source Downloads". You could click on the .info file under
"Individual Files" to see the aarch64 download/md5.

I could make this change without too much trouble (it's just
scripting, not rocket science). DOWNLOAD_aarch64 and MD5SUM_aarch64
would be optional (the database script wouldn't require them to be
present even if empty).

Tools like sbopkg and sbotools don't use the website. They just look
at the .info file. They'd just have to be modified to look in the
.info file for the aarch64 URL and md5sum, when running on aarch64.
Someone who isn't me is welcome to do that part.

From dchmelik at gmail.com  Wed Apr 16 05:42:05 2025
From: dchmelik at gmail.com (David Chmelik)
Date: Tue, 15 Apr 2025 22:42:05 -0700
Subject: [Slackbuilds-users] About aarch64 support support in
 TEMPLATE.info
In-Reply-To: <5d35a851-db71-fb90-86d9-b3154598321@slackware.uk>
References: <CADV5w3xTy6COYCgbTDUy5XfDScM1UrSh_5aPPvPoz_9vZ88bjg@mail.gmail.com>
 <932b25d1-d41c-4fa4-8364-c78bd6cdc125@slackbuilds.org>
 <5d35a851-db71-fb90-86d9-b3154598321@slackware.uk>
Message-ID: <2ab5149c-56f0-6743-f486-7d6ab820bf50@gmail.com>

On 4/15/25 8:08 PM, B. Watson wrote:
> On Wed, 16 Apr 2025, Willy Sudiarto Raharjo wrote:
>> 3. More burden for maintainers and admins if this is added into the 
>> template since they need to test more
>> 4. We don't have the CI support as of now for AARCH64, only relies to 
>> the current maintainer that they test it.
>
> These could be addressed like so, in the site FAQ:
exactly

> "aarch64 is unsupported by the SBo team, though it may be supported
> by individual maintainers. Please contact the maintainer if you have
> problems with a build on aarch64."
>
> When a maintainer gets contacted, it's up to him to either fix the
> problem for the aarch64 user, or say "Sorry, I don't have time to
> support aarch64, could you send me a patch?"... and if the user
> sends a patch, the maintainer can add it to the build. If not, the
> maintainer can at least put "This doesn't work on aarch64" in his
> README, to save other aarch64 users from wasting time.
sounds good

> This isn't ideal for aarch64 users (it makes aarch64 a "second class"
> architecture), but it's better than not being supported at all.
That's what *BSD UNIX does: NetBSD even has 50 'tier 2' architectures 
(FreeBSD has over 10 tier 2, and one tier 3) and I think it works fine.

> Point 4 (the CI thing) could exist someday, even though it doesn't now.
>
>> 5. Changes needed in our backend infrastructure (website, database, 
>> etc) and so far no one is interested to take this work.
>
> This could be simpler than you think. Basically, all that's needed for
> *minimal* aarch64 support would be to allow the DOWNLOAD_aarch64 and
> MD5SUM_aarch64 keys in the .info file... and *ignore* them. The script
> that reads .info files and populates the database would just have to
> allow these keys to exist in the file, but not do anything with them.
>
> The rest of the site wouldn't need changing, and neither would the
> database.
>
> The end result would be, aarch64 download URLs wouldn't be shown
> on the site, but they would be in the .info files. If you went to
> http://slackbuilds.org/repository/15.0/<category>/<build>/ in a
> browser, you would only see the x86 and x86_64 downloads listed
> "Source Downloads". You could click on the .info file under
> "Individual Files" to see the aarch64 download/md5.
Is it possible to put DOWNLOAD_aarch64 & MD5SUM_aarch64 on-site but not 
officially test build until enough team members are involved?? Often I 
search website for download URLs, though I only have two older Raspberry 
Pi (RPi) Slackware servers, I'm reorganizing---not currently using--but 
maybe this or next decade I'll have a Slackware ARM laptop.

> I could make this change without too much trouble (it's just
> scripting, not rocket science). DOWNLOAD_aarch64 and MD5SUM_aarch64
> would be optional (the database script wouldn't require them to be
> present even if empty).
>
> Tools like sbopkg and sbotools don't use the website. They just look
> at the .info file. They'd just have to be modified to look in the
> .info file for the aarch64 URL and md5sum, when running on aarch64.
> Someone who isn't me is welcome to do that part.
On that topic, sbopkg should be on website, because sbotools, etc., are, 
and the rest can self-update from it, so sbopkg should, especially since 
sbopkg isn't truly 'third-party' for some years rather than being 
maintained by a SlackBuilds.org team member.

From urchlay at slackware.uk  Wed Apr 16 06:55:27 2025
From: urchlay at slackware.uk (B. Watson)
Date: Wed, 16 Apr 2025 02:55:27 -0400 (EDT)
Subject: [Slackbuilds-users] About aarch64 support support in
 TEMPLATE.info
In-Reply-To: <2ab5149c-56f0-6743-f486-7d6ab820bf50@gmail.com>
References: <CADV5w3xTy6COYCgbTDUy5XfDScM1UrSh_5aPPvPoz_9vZ88bjg@mail.gmail.com>
 <932b25d1-d41c-4fa4-8364-c78bd6cdc125@slackbuilds.org>
 <5d35a851-db71-fb90-86d9-b3154598321@slackware.uk>
 <2ab5149c-56f0-6743-f486-7d6ab820bf50@gmail.com>
Message-ID: <c3269e21-5c46-7237-b76d-c73e467b534b@slackware.uk>



On Tue, 15 Apr 2025, David Chmelik wrote:

> Is it possible to put DOWNLOAD_aarch64 & MD5SUM_aarch64 on-site

No, not any time soon, because it would require major database and
site surgery. My compromise from the last email is basically "allow
them in .info files but don't store them in the database".

It's also a simple code change, to one script, and doesn't require
any database changes at all. It's low-impact. In other words it's
something I could do *right now* if the other admins agree that it's a
good idea.

Doing the "full support" you're asking for would require a lot more
work, and probably would have to wait until a "development cycle"
(when a new Slackware gets released and our submissions are closed).
No idea when the next release will be... and, don't misread this
paragraph: I'm not saying "we will fully support aarch64 after the
next Slackware release". I'm saying "**IF** we decide to fully support
aarch64, it wouldn't happen until the next Slackware release".

> but not officially test build until enough team members are involved?

What would be needed for "official test builds" would be a CI
system that can be triggered by git commits, like we have for x86
and x86_64. I'm not sure how involved that would be, but it would
at minimum require buying a fast aarch64 server (if such a thing
exists). Emulating aarch64 on x86_64 is just too slow to be practical.

Note that the .info file stuff really only matters for builds that are
binary repacks. When building from source, normally the same source
works on x86, x86_64, and aarch64.

> Often I search website for download URLs, though I only have two
> older Raspberry Pi (RPi) Slackware servers, I'm reorganizing---not
> currently using--but maybe this or next decade I'll have a Slackware
> ARM laptop.

OK, you'd have one extra click (click on the .info file on the build
page). Depending on your browser, you might have to copy/paste the
aarch64 URL, or the browser might helpfully present it as a link (even
though .info files are plain text, not HTML).

> On that topic, sbopkg should be on website, because sbotools, etc., are, 
> and the rest can self-update from it, so sbopkg should, especially since 
> sbopkg isn't truly 'third-party' for some years rather than being 
> maintained by a SlackBuilds.org team member.

sbopkg is maintained by an individual SBo team member, with occasional
contributions from other SBo team members, and from people who aren't
on the SBo team.

sbopkg isn't required, to use SBo. One reason it's third-party is that
multiple tools exist (sbopkg, sbotools, sborepo) and we don't want to
support (read: *endorse*) one but not the others (and we don't want to
support all of them).

It's also third-party partly because the rest of the SBo team is *not*
interested in being responsible for it. Right now, if you say to me
"thus and such doesn't work in sbopkg", I can decide I'm too busy to
deal with sbopkg issues (because they're not SBo issues), and point
you towards the *separate* maintainer, mailing list, github repo, LQ
threads, etc.

I know that makes me sound horrible, or horribly lazy, but life
is short and I already have 900+ SlackBuilds to maintain, plus the
sbo-maintainer-tools, plus the SBo source archive... and a real life
outside the SBo world.

From sb at rbn.im  Wed Apr 16 23:25:43 2025
From: sb at rbn.im (Ruben Schuller)
Date: Thu, 17 Apr 2025 01:25:43 +0200
Subject: [Slackbuilds-users] About aarch64 support support in
 TEMPLATE.info
In-Reply-To: <5d35a851-db71-fb90-86d9-b3154598321@slackware.uk>
References: <CADV5w3xTy6COYCgbTDUy5XfDScM1UrSh_5aPPvPoz_9vZ88bjg@mail.gmail.com>
 <932b25d1-d41c-4fa4-8364-c78bd6cdc125@slackbuilds.org>
 <5d35a851-db71-fb90-86d9-b3154598321@slackware.uk>
Message-ID: <20250417012543.0f51bbb7@banane.kuchen>

Hi!

2025-04-15 "B. Watson" <urchlay at slackware.uk>:

> This could be simpler than you think. Basically, all that's needed for
> *minimal* aarch64 support would be to allow the DOWNLOAD_aarch64 and
> MD5SUM_aarch64 keys in the .info file... and *ignore* them. The script
> that reads .info files and populates the database would just have to
> allow these keys to exist in the file, but not do anything with them.

Just my 2 cents on this: Why not add a file "$PRGNAM.$arch.info"
or something like this to scripts which are supported for the
respective architecture by their maintainers? These files would contain
the DOWNLOAD_$arch and MD5SUM_$arch lines (or maybe even REQUIRES in
case they differ?) for the respective architecture, just read this file
after the normal info file. No tool could break because the info files
suddenly contain new lines.

Cheers
Ruben

From dchmelik at gmail.com  Thu Apr 17 03:28:18 2025
From: dchmelik at gmail.com (David Chmelik)
Date: Wed, 16 Apr 2025 20:28:18 -0700
Subject: [Slackbuilds-users] inactive maintainer (was: Fwd: CCL?)
In-Reply-To: <1589447984.2580984.1744828586887@mail.yahoo.com>
References: <1589447984.2580984.1744828586887@mail.yahoo.com>
Message-ID: <75248b2f-fca4-8798-bdc0-81310ff87f7f@gmail.com>

-------- Forwarded Message -------
Date: 	Wed, 16 Apr 2025 18:36:26 +0000 (UTC)
From: 	Omer Yilmaz <mr1yh1 at yahoo.com>
To: 	David Chmelik <davidnchmelik at gmail.com>
Subject: 	Re: CCL?

Hello David,

I assume you mentioned the slackware package i prepared years ago.
For a long time i am not using slackware and ccl,
also as i remember ccl changed distribution format so script may be 
needed to be modified a bit more.

I don't know your experience with common lisp, but you should not use 
their default REPL (shell),
people mostly use EMACS or something more like an IDE.
Only exception could be clisp which has a better shell,
but still i would advice otherwise.

Maybe i will fix the script to update the version of CCL and include 
some docs in future,
if you don't have a specific need,
better try out SBCL in linux, CCL is better in MACOS (Cacoa support).

My regards.

On Sunday, April 13, 2025 at 01:56:01 AM GMT-5, David Chmelik wrote:

[...] I installed ccl, which is similar to a shell alias, so I 
accidentally typed, but can't exit/quit, and documentation is excluded. 
[...]

From willysr at slackbuilds.org  Thu Apr 17 06:37:28 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 17 Apr 2025 13:37:28 +0700
Subject: [Slackbuilds-users] About aarch64 support support in
 TEMPLATE.info
In-Reply-To: <2ab5149c-56f0-6743-f486-7d6ab820bf50@gmail.com>
References: <CADV5w3xTy6COYCgbTDUy5XfDScM1UrSh_5aPPvPoz_9vZ88bjg@mail.gmail.com>
 <932b25d1-d41c-4fa4-8364-c78bd6cdc125@slackbuilds.org>
 <5d35a851-db71-fb90-86d9-b3154598321@slackware.uk>
 <2ab5149c-56f0-6743-f486-7d6ab820bf50@gmail.com>
Message-ID: <59f1e702-8352-45ba-aa53-e4b954d78282@slackbuilds.org>

>> This isn't ideal for aarch64 users (it makes aarch64 a "second class"
>> architecture), but it's better than not being supported at all.
> That's what *BSD UNIX does: NetBSD even has 50 'tier 2' architectures 
> (FreeBSD has over 10 tier 2, and one tier 3) and I think it works fine.

They have the Foundation that support their work financially
See this page: https://freebsdfoundation.org/our-donors/donors/
Most of the admins work on SBo on our free time and even Andrew Clemons 
used his own infractructure for the CI.

> On that topic, sbopkg should be on website, because sbotools, etc., are, 
> and the rest can self-update from it, so sbopkg should, especially since 
> sbopkg isn't truly 'third-party' for some years rather than being 
> maintained by a SlackBuilds.org team member.

Well, it's a third party since it's not endorsed.
It was originally made by other people outside of SBo admins (Chess, 
Mauro, and slakmagik), i just continued to maintain it since i used it 
and found it useful and it worked for me.


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250417/b8ddfba8/attachment.asc>

From willysr at slackbuilds.org  Sat Apr 19 16:26:14 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 19 Apr 2025 23:26:14 +0700
Subject: [Slackbuilds-users] Updates - 20250419.1
Message-ID: <62a1aaf9-0fdb-4f06-8f7c-1636538fbb00@slackbuilds.org>

Hi

Sorry for the late public update this week
I also found that i missed one small typo during merging a PR and 
discovered it very late when i ran the public update process.

If you happen to use python3-docstring-to-markdown, it requires a new 
dependency of python-importlib_metadata but it was written as 
python3-importlib_metadata. It has been fixed in the tarball, but not in 
the script itself. It has been fixed on my branch but the actual changes 
will be merged next public update.


Sat Apr 19 16:09:18 UTC 2025
academic/plus42: Updated for version 1.2.7.
academic/root: Updated for version 6.34.08
audio/audacity: Updated for version 3.7.3.
audio/noisetorch-bin: Update noisetorch-bin.info
desktop/ClamAV-GUI: Updated for version 1.1.3.
desktop/Matcha-gtk-theme: Update for 2025_04_11
desktop/anki: Updated for version 25.02.1.
desktop/lightdm-slick-greeter: Added (LightDM greeter).
desktop/nwg-panel: Updated for version 0.10.1.
development/aws-cdk: Updated for version 2.1010.0.
development/bbcsdl: Updated for version 1.41b.
development/golangci-lint: Updated for version 2.1.2.
development/google-go-lang: Updated for version 1.24.2.
development/hugo: Updated for version 0.146.5.
development/idea: Updated for version 2024.3.5.
development/jupyter-nbclassic: Update for 1.2.0
development/jupyter-nbconvert: Update for 7.16.6
development/pnpm: Updated for version 10.8.1.
development/poedit: Updated for version 3.6.1.
development/pycharm: Updated for version 2024.3.5.
development/pycharm: Updated for version 2025.1.251.23774.444.
development/qbs: Updated for version 2.6.1
development/sourcegit: Updated for version 2025.13
development/vscode-bin: Updated for version 1.99.3.
development/vstudio: Updated for version 15.1.5.
development/witsy: Updated for version 2.4.7
games/0ad-data: Updated for version 0.27.0.
games/0ad: Updated for version 0.27.0.
games/pychess: Updated for version 1.0.5.
graphics/blender: Version bump to 4.4.1
ham/redsea: Updated for version 1.2.0.
libraries/Botan: Updated for version 2.19.5.
libraries/gtk-fortran: Update gtk-fortran.info
libraries/libavif: Updated for version 1.2.1.
libraries/libfabric: Updated for version 2.1.0.
libraries/libfilezilla: Updated for version 0.50.0.
libraries/libmygpo-qt: Updated for version 1.2.0.
libraries/libomemo-c: Add back dependency.
libraries/libomemo-c: Updated for version 0.5.1.
libraries/liburcu: Updated for versio 0.15.2.
libraries/libyuv: Updated for version 0.0.1904.20250204.
libraries/libzim: Updated for version 9.3.0.
libraries/microsoft-gsl: Updated for version 4.2.0.
libraries/onevpl: Version bump to 2.15.0
misc/bitwarden-desktop: updated for version 2025.3.1
multimedia/AviSynthPlus: Updated for version 3.7.4.
multimedia/beets: Updated for version 2.2.0.
multimedia/inputstream.adaptive: Version bump to 21.5.11
multimedia/svt-av1: Updated for version 3.0.2.
network/AdGuardHome: Updated for version 0.107.60.
network/betterbird-bin: Updated DOWNLOAD_x86_64.
network/bitcoin: Updated for version 29.0.
network/brave-browser: Updated for version 1.77.100.
network/connman: Updated for version 1.44.
network/dino: Add missing dependency.
network/dino: Updated for version 0.5.0.
network/discord: Version bump to 0.0.91
network/dnsproxy-bin: Updated for version 0.75.2.
network/dnsproxy-bin: Updated for version 0.75.3.
network/dooble: Updated for version 2025.04.07
network/dropbox: Updated for version 222.4.5042.
network/dstp: Update dstp.info
network/filezilla: Updated for version 0.50.0.
network/jitsi-meet-desktop: Updated for version 2025.4.0
network/lighttpd: Updated for version 1.4.79.
network/nchat: Updated for version 5.6.7.
network/nextcloud-server: Updated for version 29.0.15.
network/rustdesk: Updated for version 1.3.9.
network/signal-desktop: Updated for version 7.51.0.
network/tailscale: Updated for version 1.82.5.
network/teamviewer: Updated for version 15.64.3.
network/tor-browser: Updated for version 14.5.
network/turbo-attack: Update turbo-attack.info
network/turbo-scanner: Update turbo-scanner.info
network/vivaldi: Updated for version 7.3.3635.11.
network/wireshark: Updated for version 4.4.6.
network/zdns: Updated for version 2.0.4.
office/hunspell-gr: Update info file for maintainer name
office/ishmael: Updated for version 1.06.
office/onlyoffice-desktopeditors: Updated for version 8.3.3.
office/pdfsam-basic: Updated for version 5.3.1.
office/star-tex: Added (TeX engine in Go).
perl/MoarVM: Updated for version 2025.03
perl/nqp: Fix MD5SUM.
perl/nqp: Updated for version 2025.03
perl/perl-Linux-FD: Updated for version 0.017.
perl/rakudo: Updated for version 2025.03
python/cppy: Version bump to 1.3.1
python/python-debian: Updated for version 1.0.1.
python/python3-argcomplete: Updated for version 3.6.2.
python/python3-async-lru: Update for 2.0.5
python/python3-calver: Updated for version 2025.4.17.
python/python3-click-option-group: Version bump to 0.5.7
python/python3-debugpy: Update for 1.6.14
python/python3-dep-logic: Version bump to 0.5.0
python/python3-docstring-to-markdown: Update for 0.16
python/python3-fonttools: Updated for version 4.57.0.
python/python3-hishel: Version bump to 0.1.2
python/python3-httpcore: Updated for version 1.0.8.
python/python3-id: Added (Generate OIDC identities).
python/python3-json-logger: Update for 3.3.0
python/python3-jsonschema-specifications: Added (JSON support files).
python/python3-jsonschema: Updated for version 4.23.0.
python/python3-keyring: Update for 25.6.0 (+add shell completions)
python/python3-klepto: Updated for version 0.2.7.
python/python3-lxml: Version bump to 5.3.2
python/python3-multidict: Updated for version 6.4.3.
python/python3-pdfminer.six: Updated for version 20250416.
python/python3-pdm-backend: Version bump to 2.4.4
python/python3-pdm: Version bump to 2.24.0
python/python3-pox: Updated for version 0.3.6.
python/python3-propcache: Updated for version 0.3.1.
python/python3-propcache: Updated for version 0.3.1.
python/python3-pydantic: Updated for version 2.11.3.
python/python3-qtawesome: Update for 1.4.0
python/python3-referencing: Added (JSON Referencing + Python).
python/python3-rpds-py: Added (Python binding to Rust).
python/python3-rtree: Update for 1.4.0
python/python3-smart_open: Update for 7.2.0
python/python3-tenacity: Update for 9.1.2
python/python3-trove-classifiers: Updated for version 2025.4.11.15.
python/python3-typing-extensions: Version bump to 4.13.2
python/python3-unearth: Version bump to 0.17.5
python/python3-yarl: Updated for version 1.20.0.
ruby/ruby-build: Updated for version 20250418.
system/Iosevka-aile: Updated for version 33.2.1.
system/Iosevka-etoile: Updated for version 33.2.1.
system/SavvyCAN: Updated for version 213.
system/apparmor: Updated for version 4.1.0.
system/borgmatic: Updated for version 2.0.3.
system/cpuinfo: Added (CPU INFOrmation library).
system/docker-buildx: Updated for version 0.23.0.
system/forkstat: Updated for version 0.04.00.
system/gslapt: Updated for version 0.5.11.
system/lightdm-settings: Added (GUI for lightdm-slick-greeter).
system/lightdm: Added (Display Manager).
system/mlterm: Updated for version 3.9.4.
system/mongodb: Updated for version 8.0.8.
system/netdata: Updated for version 2.4.0.
system/onefetch: Updated for version 2.24.0.
system/pmdk: Updated for version 2.1.1.
system/sarasa-gothic: Updated for version 1.0.30.
system/slapt-get: Updated for version 0.11.11.
system/slapt-src: Updated for version 0.3.9.
system/slapt-update-service: Updated for version 0.5.4.
system/slpkg: Updated for version 5.2.4.
system/tio: Updated for version 3.9
system/trash-cli: Edit README
system/zim-tools: Updated for version 3.6.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250419/6de21505/attachment-0001.asc>

From didier at slint.fr  Mon Apr 21 17:22:23 2025
From: didier at slint.fr (Didier Spaier)
Date: Mon, 21 Apr 2025 19:22:23 +0200
Subject: [Slackbuilds-users] Please patch yelp and yelp-xsl to overcome a
 security flaw
Message-ID: <28f5695c-1c49-49c9-b39d-b51a17bde635@slint.fr>

Hello,

as recommended by Michael Catanzaro:
https://blogs.gnome.org/mcatanzaro/2025/04/15/dangerous-arbitrary-file-read-vulnerability-in-yelp-cve-2025-3155/
I have patched locally yelp and yelp-xsl using these patches (also attached):
https://gitlab.gnome.org/GNOME/yelp/-/issues/221#note_2359937
against yelp-42.2 and yel-xsl-42.1 respectively

I suggest that they be applied to the SlackBuilds @ SBo.

Cheers,
Didier

PS while I was at it I wanted to upgrade webkit2gtk to the last version as
recommended by upstream for security reasons but could not because icu4c shipped
in Slackware 15.0 is too old. I have posted about that on LQ:
https://www.linuxquestions.org/questions/slackware-14/how-do-i-package-a-newer-icu4c-to-allow-upgrading-webkit2gtk-without-rebuilding-other-dependees-4175749884/
Suggestions are gladly welcome.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: yelp.patch
Type: text/x-patch
Size: 4347 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250421/c158081d/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: yelp-xsl.patch
Type: text/x-patch
Size: 3319 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250421/c158081d/attachment-0001.bin>

From willysr at slackbuilds.org  Tue Apr 22 01:10:49 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 22 Apr 2025 08:10:49 +0700
Subject: [Slackbuilds-users] Please patch yelp and yelp-xsl to overcome
 a security flaw
In-Reply-To: <28f5695c-1c49-49c9-b39d-b51a17bde635@slint.fr>
References: <28f5695c-1c49-49c9-b39d-b51a17bde635@slint.fr>
Message-ID: <49e920d6-470d-471a-b929-0b7501550d0f@slackbuilds.org>

> as recommended by Michael Catanzaro:
> https://blogs.gnome.org/mcatanzaro/2025/04/15/dangerous-arbitrary-file-read-vulnerability-in-yelp-cve-2025-3155/
> I have patched locally yelp and yelp-xsl using these patches (also attached):
> https://gitlab.gnome.org/GNOME/yelp/-/issues/221#note_2359937
> against yelp-42.2 and yel-xsl-42.1 respectively
> 
> I suggest that they be applied to the SlackBuilds @ SBo.

I have read the blog and the patch, but i would prefer an official patch 
that has been reviewed by upstream itself.

> PS while I was at it I wanted to upgrade webkit2gtk to the last version as
> recommended by upstream for security reasons but could not because icu4c shipped
> in Slackware 15.0 is too old. I have posted about that on LQ:
> https://www.linuxquestions.org/questions/slackware-14/how-do-i-package-a-newer-icu4c-to-allow-upgrading-webkit2gtk-without-rebuilding-other-dependees-4175749884/
I also tried this before, but no luck after several attempts, so i 
didn't do further research on this.

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x3F617144D7238786.asc
Type: application/pgp-keys
Size: 8363 bytes
Desc: OpenPGP public key
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250422/5fb2b4df/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250422/5fb2b4df/attachment-0001.asc>

From denglermatt at posteo.net  Tue Apr 22 05:22:32 2025
From: denglermatt at posteo.net (MattD)
Date: Tue, 22 Apr 2025 05:22:32 +0000
Subject: [Slackbuilds-users] chmod invalid option -- 'h' when installing
 git-tools
Message-ID: <20250422012232.a54d7dff9bd94d2d3d8d319d@posteo.net>


https://slackbuilds.org/repository/15.0/development/git-tools/

I get the above error after sudo ./git-tools.SlackBuild  I checked the script, but I cannot deduce what's wrong.  Because -h isn't an option for chmod or find.

What do?

-- 
MattD <denglermatt at posteo.net>

From willysr at slackbuilds.org  Tue Apr 22 05:51:53 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 22 Apr 2025 12:51:53 +0700
Subject: [Slackbuilds-users] chmod invalid option -- 'h' when installing
 git-tools
In-Reply-To: <20250422012232.a54d7dff9bd94d2d3d8d319d@posteo.net>
References: <20250422012232.a54d7dff9bd94d2d3d8d319d@posteo.net>
Message-ID: <0ab55d73-b9ce-47c1-99da-b7a73268d1a3@slackbuilds.org>

> https://slackbuilds.org/repository/15.0/development/git-tools/
> 
> I get the above error after sudo ./git-tools.SlackBuild  I checked the script, but I cannot deduce what's wrong.  Because -h isn't an option for chmod or find.
> 
> What do?

use "su -" or "su", not "sudo"

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x3F617144D7238786.asc
Type: application/pgp-keys
Size: 8363 bytes
Desc: OpenPGP public key
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250422/c7926b7c/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250422/c7926b7c/attachment.asc>

From urchlay at slackware.uk  Tue Apr 22 06:26:32 2025
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 22 Apr 2025 02:26:32 -0400 (EDT)
Subject: [Slackbuilds-users] chmod invalid option -- 'h' when installing
 git-tools
In-Reply-To: <0ab55d73-b9ce-47c1-99da-b7a73268d1a3@slackbuilds.org>
References: <20250422012232.a54d7dff9bd94d2d3d8d319d@posteo.net>
 <0ab55d73-b9ce-47c1-99da-b7a73268d1a3@slackbuilds.org>
Message-ID: <d2c2d929-75b8-f8dd-5dac-18d5d4653af1@slackware.uk>



On Tue, 22 Apr 2025, Willy Sudiarto Raharjo wrote:

>> https://slackbuilds.org/repository/15.0/development/git-tools/
>> 
>> I get the above error after sudo ./git-tools.SlackBuild  I checked the 
>> script, but I cannot deduce what's wrong.  Because -h isn't an option for 
>> chmod or find.
>> 
>> What do?
>
> use "su -" or "su", not "sudo"

Actually, sudo is fine for SlackBuilds, provided your user has /sbin
and /usr/sbin in $PATH. I wrote the git-tools SlackBuild, and I just
built it with sudo, with no errors.

To the OP: no idea why your chmod doesn't have -h option. I'm looking
at "man chmod" and I see:

        -h, --no-dereference
               affect each symbolic link, rather than the referent

Slackware 15.0 and -current both have the -h option to chmod, so your
chmod must be something else.

Check & see if you've done something like install busybox and put its
binaries in $PATH before /bin and /usr/bin, maybe? As your user, what
does "which chmod" say? Should be "/usr/bin/chmod".

From arabusov at gmail.com  Tue Apr 22 07:21:01 2025
From: arabusov at gmail.com (=?UTF-8?B?0JDQvdC00YDQtdC5INCg0LDQsdGD0YHQvtCy?=)
Date: Tue, 22 Apr 2025 09:21:01 +0200
Subject: [Slackbuilds-users] chmod invalid option -- 'h' when installing
 git-tools
In-Reply-To: <d2c2d929-75b8-f8dd-5dac-18d5d4653af1@slackware.uk>
References: <20250422012232.a54d7dff9bd94d2d3d8d319d@posteo.net>
 <0ab55d73-b9ce-47c1-99da-b7a73268d1a3@slackbuilds.org>
 <d2c2d929-75b8-f8dd-5dac-18d5d4653af1@slackware.uk>
Message-ID: <CA+=LW18dfT5HcJM-BddPhUs-R2ZdOwAupdYy6vB5g=GkjMb0MQ@mail.gmail.com>

It could be an alias too.

Heck, shall we use the `/usr/bin` prefix for all of the standard binaries
to prevent that?

On Tue, Apr 22, 2025, 08:26 B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Tue, 22 Apr 2025, Willy Sudiarto Raharjo wrote:
>
> >> https://slackbuilds.org/repository/15.0/development/git-tools/
> >>
> >> I get the above error after sudo ./git-tools.SlackBuild  I checked the
> >> script, but I cannot deduce what's wrong.  Because -h isn't an option
> for
> >> chmod or find.
> >>
> >> What do?
> >
> > use "su -" or "su", not "sudo"
>
> Actually, sudo is fine for SlackBuilds, provided your user has /sbin
> and /usr/sbin in $PATH. I wrote the git-tools SlackBuild, and I just
> built it with sudo, with no errors.
>
> To the OP: no idea why your chmod doesn't have -h option. I'm looking
> at "man chmod" and I see:
>
>         -h, --no-dereference
>                affect each symbolic link, rather than the referent
>
> Slackware 15.0 and -current both have the -h option to chmod, so your
> chmod must be something else.
>
> Check & see if you've done something like install busybox and put its
> binaries in $PATH before /bin and /usr/bin, maybe? As your user, what
> does "which chmod" say? Should be "/usr/bin/chmod".
> _______________________________________________
> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250422/aa35d710/attachment-0001.htm>

From urchlay at slackware.uk  Tue Apr 22 07:29:29 2025
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 22 Apr 2025 03:29:29 -0400 (EDT)
Subject: [Slackbuilds-users] chmod invalid option -- 'h' when installing
 git-tools
In-Reply-To: <CA+=LW18dfT5HcJM-BddPhUs-R2ZdOwAupdYy6vB5g=GkjMb0MQ@mail.gmail.com>
References: <20250422012232.a54d7dff9bd94d2d3d8d319d@posteo.net>
 <0ab55d73-b9ce-47c1-99da-b7a73268d1a3@slackbuilds.org>
 <d2c2d929-75b8-f8dd-5dac-18d5d4653af1@slackware.uk>
 <CA+=LW18dfT5HcJM-BddPhUs-R2ZdOwAupdYy6vB5g=GkjMb0MQ@mail.gmail.com>
Message-ID: <9ac44173-edb6-2ce5-9489-92ac5e661199@slackware.uk>



On Tue, 22 Apr 2025, ?????? ??????? wrote:

> It could be an alias too.

If that were possible, it would be an absolute nightmare.

> Heck, shall we use the `/usr/bin` prefix for all of the standard binaries to prevent that?

Aliases don't "survive" sudo's user change. They don't live in the
environment, so they don't get propagated from your interactive shell
to the SlackBuild script.

Example:

$ alias foo='echo "gotcha"'
$ foo
gotcha
$ sudo foo
Password:
sudo: foo: command not found

From duncan_roe at optusnet.com.au  Tue Apr 22 22:15:06 2025
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Wed, 23 Apr 2025 08:15:06 +1000
Subject: [Slackbuilds-users] chmod invalid option -- 'h' when installing
 git-tools
In-Reply-To: <9ac44173-edb6-2ce5-9489-92ac5e661199@slackware.uk>
References: <20250422012232.a54d7dff9bd94d2d3d8d319d@posteo.net>
 <0ab55d73-b9ce-47c1-99da-b7a73268d1a3@slackbuilds.org>
 <d2c2d929-75b8-f8dd-5dac-18d5d4653af1@slackware.uk>
 <CA+=LW18dfT5HcJM-BddPhUs-R2ZdOwAupdYy6vB5g=GkjMb0MQ@mail.gmail.com>
 <9ac44173-edb6-2ce5-9489-92ac5e661199@slackware.uk>
Message-ID: <aAgU6qZviVFl+88l@slk15.local.net>

On Tue, Apr 22, 2025 at 03:29:29AM -0400, B. Watson wrote:
>
>
> On Tue, 22 Apr 2025, ???????????? ?????????????? wrote:
>
> > It could be an alias too.
>
> If that were possible, it would be an absolute nightmare.
>
> > Heck, shall we use the `/usr/bin` prefix for all of the standard binaries to prevent that?
>
> Aliases don't "survive" sudo's user change. They don't live in the
> environment, so they don't get propagated from your interactive shell
> to the SlackBuild script.
>
> Example:
>
> $ alias foo='echo "gotcha"'
> $ foo
> gotcha
> $ sudo foo
> Password:
> sudo: foo: command not found

It could be an exported function. These do live in the environment and survive
quite a lot of things, possibly including sudo. Starting a script with

#!/bin/bash -p

does prevent it.

If the admins would like, I could make a tree-wide PR or patch - maybe when
Slackware 15.1 appears would suit?

Cheers ... Duncan.

From urchlay at slackware.uk  Tue Apr 22 22:33:02 2025
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 22 Apr 2025 18:33:02 -0400 (EDT)
Subject: [Slackbuilds-users] chmod invalid option -- 'h' when installing
 git-tools
In-Reply-To: <aAgU6qZviVFl+88l@slk15.local.net>
References: <20250422012232.a54d7dff9bd94d2d3d8d319d@posteo.net>
 <0ab55d73-b9ce-47c1-99da-b7a73268d1a3@slackbuilds.org>
 <d2c2d929-75b8-f8dd-5dac-18d5d4653af1@slackware.uk>
 <CA+=LW18dfT5HcJM-BddPhUs-R2ZdOwAupdYy6vB5g=GkjMb0MQ@mail.gmail.com>
 <9ac44173-edb6-2ce5-9489-92ac5e661199@slackware.uk>
 <aAgU6qZviVFl+88l@slk15.local.net>
Message-ID: <58447797-0cd-e95f-a759-78497c6c75bb@slackware.uk>



On Wed, 23 Apr 2025, Duncan Roe wrote:

> It could be an exported function. These do live in the environment and survive
> quite a lot of things, possibly including sudo. Starting a script with

Took a look at this. You're talking about "declare -fx funcname",
right? Doesn't propagate into sudo. Probably there's a way to force it
to, by editing /etc/sudoers and explicitly including BASH_FUNC_<name>
in env_keep...

They *definitely* don't get propagated with "su -".

>
> #!/bin/bash -p
>
> does prevent it.
>
> If the admins would like, I could make a tree-wide PR or patch - maybe when
> Slackware 15.1 appears would suit?

I don't really think it's necessary. The standard way to run
SlackBuilds is with "su -". The only reason we're talking about
sudo here is that the OP used it. I checked it with sudo to see if
I had the same problem, and I don't. So whatever his problem is, it
wasn't caused by sudo (that's all I was trying to do, eliminate that
possibility).

Since we still haven't heard back from the OP, we're just spinning our
wheels at this point...

From duncan_roe at optusnet.com.au  Tue Apr 22 22:48:14 2025
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Wed, 23 Apr 2025 08:48:14 +1000
Subject: [Slackbuilds-users] chmod invalid option -- 'h' when installing
 git-tools
In-Reply-To: <58447797-0cd-e95f-a759-78497c6c75bb@slackware.uk>
References: <20250422012232.a54d7dff9bd94d2d3d8d319d@posteo.net>
 <0ab55d73-b9ce-47c1-99da-b7a73268d1a3@slackbuilds.org>
 <d2c2d929-75b8-f8dd-5dac-18d5d4653af1@slackware.uk>
 <CA+=LW18dfT5HcJM-BddPhUs-R2ZdOwAupdYy6vB5g=GkjMb0MQ@mail.gmail.com>
 <9ac44173-edb6-2ce5-9489-92ac5e661199@slackware.uk>
 <aAgU6qZviVFl+88l@slk15.local.net>
 <58447797-0cd-e95f-a759-78497c6c75bb@slackware.uk>
Message-ID: <aAgcroTkPR5UZnG9@slk15.local.net>

On Tue, Apr 22, 2025 at 06:33:02PM -0400, B. Watson wrote:
>
>
> You're talking about "declare -fx funcname", right?

Actually "export -f funcname". root has a few of these on my system.

Cheers ... Duncan.

From urchlay at slackware.uk  Tue Apr 22 23:15:57 2025
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 22 Apr 2025 19:15:57 -0400 (EDT)
Subject: [Slackbuilds-users] chmod invalid option -- 'h' when installing
 git-tools
In-Reply-To: <aAgcroTkPR5UZnG9@slk15.local.net>
References: <20250422012232.a54d7dff9bd94d2d3d8d319d@posteo.net>
 <0ab55d73-b9ce-47c1-99da-b7a73268d1a3@slackbuilds.org>
 <d2c2d929-75b8-f8dd-5dac-18d5d4653af1@slackware.uk>
 <CA+=LW18dfT5HcJM-BddPhUs-R2ZdOwAupdYy6vB5g=GkjMb0MQ@mail.gmail.com>
 <9ac44173-edb6-2ce5-9489-92ac5e661199@slackware.uk>
 <aAgU6qZviVFl+88l@slk15.local.net>
 <58447797-0cd-e95f-a759-78497c6c75bb@slackware.uk>
 <aAgcroTkPR5UZnG9@slk15.local.net>
Message-ID: <83b25a0-a9f-78a2-9f45-8bffece47735@slackware.uk>



On Wed, 23 Apr 2025, Duncan Roe wrote:

>> You're talking about "declare -fx funcname", right?
>
> Actually "export -f funcname". root has a few of these on my system.

Appears that declare -fx and export -f do the same thing.

That's something new to me, I never thought about exporting functions.
Now that I know how, I think I still won't do it...

From rcb at beco.cc  Thu Apr 24 15:00:34 2025
From: rcb at beco.cc (Beco)
Date: Thu, 24 Apr 2025 12:00:34 -0300
Subject: [Slackbuilds-users] CryFS debug build
Message-ID: <CALuYw2wZa1jxLUpTxzs2L8KtmZv-0XwbczEy0HF4T_j0oAj-4w@mail.gmail.com>

Dear SlackBuild users,

Just to report that I got this warning when using cryfs, which in my view
should not be how it is released into Slackware 15.0:

% cryfs --help
CryFS Version 0.10.3
WARNING! This is a debug build. Performance might be slow.

Usage: cryfs [options] baseDir mountPoint [-- [FUSE Mount Options]]



 Thank you and best regards.


-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

Essa mensagem ? destinada exclusivamente ao seu destinat?rio e pode conter
informa??es confidenciais, protegidas por sigilo profissional, direitos
autorais reservados, ou cuja divulga??o seja proibida por lei. O uso n?o
autorizado de tais informa??es ? proibido e est? sujeito ?s penalidades
cab?veis.

This message is intended exclusively for its addressee and may contain
information that is confidential and protected by a professional privilege,
reserved copyright, or whose disclosure is prohibited by law. Unauthorised
use of such information is prohibited and subject to applicable penalties.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250424/8f3dc046/attachment-0001.htm>

From matteo.bernardini at gmail.com  Thu Apr 24 15:25:03 2025
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 24 Apr 2025 17:25:03 +0200
Subject: [Slackbuilds-users] CryFS debug build
In-Reply-To: <CALuYw2wZa1jxLUpTxzs2L8KtmZv-0XwbczEy0HF4T_j0oAj-4w@mail.gmail.com>
References: <CALuYw2wZa1jxLUpTxzs2L8KtmZv-0XwbczEy0HF4T_j0oAj-4w@mail.gmail.com>
Message-ID: <CAPsDuS4i54WFGWCpES3cqpPQkZTU9+BdUd+Astbv+0nL0yqL5A@mail.gmail.com>

hi Beco,

from what I had read looks like a false warning, see

https://github.com/gentoo/gentoo/pull/4772

also, cryfs is not on SBo so we could not have done much also if it was
legit ;-)

Matteo


Il giorno gio 24 apr 2025 alle ore 17:01 Beco via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> ha scritto:

> Dear SlackBuild users,
>
> Just to report that I got this warning when using cryfs, which in my view
> should not be how it is released into Slackware 15.0:
>
> % cryfs --help
> CryFS Version 0.10.3
> WARNING! This is a debug build. Performance might be slow.
>
> Usage: cryfs [options] baseDir mountPoint [-- [FUSE Mount Options]]
>
>
>
>  Thank you and best regards.
>
>
> --
> Dr Beco
> A.I. researcher
>
> "I know you think you understand what you thought I said but I'm not sure
> you realize that what you heard is not what I meant" -- Alan Greenspan
>
> GPG Key:
> https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
> Creation date: pgp.mit.edu ID as of 2014-11-09
>
> Essa mensagem ? destinada exclusivamente ao seu destinat?rio e pode
> conter informa??es confidenciais, protegidas por sigilo profissional,
> direitos autorais reservados, ou cuja divulga??o seja proibida por lei. O
> uso n?o autorizado de tais informa??es ? proibido e est? sujeito ?s
> penalidades cab?veis.
>
> This message is intended exclusively for its addressee and may contain
> information that is confidential and protected by a professional privilege,
> reserved copyright, or whose disclosure is prohibited by law. Unauthorised
> use of such information is prohibited and subject to applicable penalties.
>
> _______________________________________________
> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250424/63d7d7e1/attachment.htm>

From rcb at beco.cc  Thu Apr 24 15:39:06 2025
From: rcb at beco.cc (Beco)
Date: Thu, 24 Apr 2025 12:39:06 -0300
Subject: [Slackbuilds-users] CryFS debug build
In-Reply-To: <CAPsDuS4i54WFGWCpES3cqpPQkZTU9+BdUd+Astbv+0nL0yqL5A@mail.gmail.com>
References: <CALuYw2wZa1jxLUpTxzs2L8KtmZv-0XwbczEy0HF4T_j0oAj-4w@mail.gmail.com>
 <CAPsDuS4i54WFGWCpES3cqpPQkZTU9+BdUd+Astbv+0nL0yqL5A@mail.gmail.com>
Message-ID: <CALuYw2zXr=j95rm=MtKDSg6QpupY3sgSp9o4KLOLmajS9v28jw@mail.gmail.com>

Hi Matteo,

Thanks for the reply.
I hope upstream fix this.

My best,
Beco


On Thu, 24 Apr 2025 at 12:25, Matteo Bernardini <matteo.bernardini at gmail.com>
wrote:

> hi Beco,
>
> from what I had read looks like a false warning, see
>
> https://github.com/gentoo/gentoo/pull/4772
>
> also, cryfs is not on SBo so we could not have done much also if it was
> legit ;-)
>
> Matteo
>
>
> Il giorno gio 24 apr 2025 alle ore 17:01 Beco via SlackBuilds-users <
> slackbuilds-users at slackbuilds.org> ha scritto:
>
>> Dear SlackBuild users,
>>
>> Just to report that I got this warning when using cryfs, which in my view
>> should not be how it is released into Slackware 15.0:
>>
>> % cryfs --help
>> CryFS Version 0.10.3
>> WARNING! This is a debug build. Performance might be slow.
>>
>> Usage: cryfs [options] baseDir mountPoint [-- [FUSE Mount Options]]
>>
>>
>>
>>  Thank you and best regards.
>>
>>
>>


-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

Essa mensagem ? destinada exclusivamente ao seu destinat?rio e pode conter
informa??es confidenciais, protegidas por sigilo profissional, direitos
autorais reservados, ou cuja divulga??o seja proibida por lei. O uso n?o
autorizado de tais informa??es ? proibido e est? sujeito ?s penalidades
cab?veis.

This message is intended exclusively for its addressee and may contain
information that is confidential and protected by a professional privilege,
reserved copyright, or whose disclosure is prohibited by law. Unauthorised
use of such information is prohibited and subject to applicable penalties.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250424/47b52c13/attachment.htm>

From didier at slint.fr  Thu Apr 24 16:05:21 2025
From: didier at slint.fr (Didier Spaier)
Date: Thu, 24 Apr 2025 18:05:21 +0200
Subject: [Slackbuilds-users] Please patch yelp and yelp-xsl to overcome
 a security flaw
In-Reply-To: <49e920d6-470d-471a-b929-0b7501550d0f@slackbuilds.org>
References: <28f5695c-1c49-49c9-b39d-b51a17bde635@slint.fr>
 <49e920d6-470d-471a-b929-0b7501550d0f@slackbuilds.org>
Message-ID: <303056eb-6f77-4a56-9798-fc66983dd2d7@slint.fr>

On 22/04/2025 03:10, Willy Sudiarto Raharjo wrote:
>> as recommended by Michael Catanzaro:
>> https://blogs.gnome.org/mcatanzaro/2025/04/15/dangerous-arbitrary-file-read-
>> vulnerability-in-yelp-cve-2025-3155/
>> I have patched locally yelp and yelp-xsl using these patches (also attached):
>> https://gitlab.gnome.org/GNOME/yelp/-/issues/221#note_2359937
>> against yelp-42.2 and yel-xsl-42.1 respectively
>>
>> I suggest that they be applied to the SlackBuilds @ SBo.
> 
> I have read the blog and the patch, but i would prefer an official patch that
> has been reviewed by upstream itself.

Your choice.

>> PS while I was at it I wanted to upgrade webkit2gtk to the last version as
>> recommended by upstream for security reasons but could not because icu4c shipped
>> in Slackware 15.0 is too old. I have posted about that on LQ:
>> https://www.linuxquestions.org/questions/slackware-14/how-do-i-package-a-
>> newer-icu4c-to-allow-upgrading-webkit2gtk-without-rebuilding-other-
>> dependees-4175749884/
> I also tried this before, but no luck after several attempts, so i didn't do
> further research on this.

I failed several times but ended up succeeding as I have posted here:
https://www.linuxquestions.org/questions/slackware-14/how-do-i-package-a-newer-icu4c-to-allow-upgrading-webkit2gtk-without-rebuilding-other-dependees-4175749884/#post6568326

I am glad ~/.ccache made the builds attempts faster;)

Cheers,
Didier



From willysr at slackbuilds.org  Sat Apr 26 03:28:19 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 26 Apr 2025 10:28:19 +0700
Subject: [Slackbuilds-users] Updates - 20250426.1
Message-ID: <2cb86d87-ebfd-4c18-bc2e-ba038b2c916a@slackbuilds.org>

Hi,

Just a kind reminder for maintainers who submitted new scripts or 
updates via submission form to make sure that you used the latest 
SlackBuild script from our repository or website to prevent reverting 
our changes. Also make sure that all files should be in 644 permission.


Sat Apr 26 03:19:58 UTC 2025
academic/cdo: Updated for version 2.5.1.
academic/copasi: Updated for version 4.45.298.
academic/nco: Updated for version 5.3.3.
academic/plus42: Updated for version 1.3
academic/smath-studio: Updated for verion 1.3.0.9126
audio/sayonara-player: Updated for version 1.11.0_stable1.
audio/zoom-edit-n-share: Added (Zoom Audio).
audio/zoom-edit-n-share: Fix permission.
desktop/SiriKali: Updated for version 1.8.2.
desktop/icewm: Updated for version 3.7.4.
desktop/nwg-shell: Updated for version 0.5.48.
desktop/rss-guard: updated for version 4.8.3
development/aws-cdk: Updated for version 2.1012.0.
development/dart-sass: Updated for version 1.87.0.
development/diffoscope: updated for version 294
development/golangci-lint: Updated for version 2.1.5.
development/hugo: updated for version 0.146.7
development/jupyter_events: Update for 0.12.0
development/jupyter_server: Update for 2.13.0
development/meld3: Updated for version 3.23.0.
development/mongodb-compass: Updated for version 1.46.1.
development/mysql-workbench: Updated for version 8.0.42.
development/mysql-workbench: Updated gdal to 3.10.3.
development/nodejs: Updated for version 20.19.1.
development/notepad++: Added (Text Editor).
development/notepad++: Fix permission.
development/obsidian: updated for version 1.8.10
development/openjdk8: Updated for version 8u442.
development/pahole: Updated for version 1.30.
development/pnpm: Updated for version 10.9.0.
development/tea: updated for version 63.3.1
development/udis86: Add udis86.pc
development/valgrind: Updated for version 3.25.0.
games/ags: updated for version 3.6.1.32
games/dwarffortress: Updated for version 0.47.05.
games/endless-sky: updated for version 0.10.12
games/lgogdownloader: updated for version 3.17
gis/eccodes: Updated for version 2.41.0.
gis/gdal: Updated for version 3.10.3.
gis/geopy: Edit README
gis/proj-data: Updated for version 1.21.
gis/proj: Updated for version 9.6.0.
graphics/converseen: Updated for version 0.14.0.0.
ham/gridtracker2: Updated for version 2.250421.1.
ham/qlog: Updated for version 0.43.1.
libraries/libcbor: updated for version 0.12.0
libraries/libheif: Updated for version 1.19.7.
libraries/libjodycode: updated for version 3.1.2
libraries/log4shib: Updated for version 2.0.1.
libraries/php-redis: updated for version 6.2.0
libraries/python3-rpyc: Updated for version 6.0.2.
libraries/raylib: Updated for version 5.5.
libraries/wxWidgets: Updated for version 3.2.8.
libraries/xml-security-c: Updated for version 3.0.0.
multimedia/AviSynthPlus: Updated for version 3.7.5.
multimedia/youtube-music: Updated for version 3.8.1.
network/AdGuardHome: Updated for version 0.107.61.
network/brave-browser: updated for version 1.77.101
network/discord: Version bump to 0.0.92
network/filezilla: Updated for version 3.69.1.
network/haproxy: Updated for version 3.0.10.
network/kubectl-bin: Updated for version 1.32.4.
network/kubectl: Updated for version 1.32.4.
network/librewolf: Updated for version 137.0.2
network/shadowsocks-rust: Updated for version 1.23.2.
network/signal-desktop: Updated for version 7.52.0.
network/sshuttle: updated for version 1.3.1
network/uwsgi: updated for version 2.0.29
network/youtube-dl: Updated for version 
2024.07.11_nightly+20250408_c052a16f7.
office/focuswriter-qt6: updated for version 1.8.11
office/novelWriter: Added (markdown-like editor).
office/novelWriter: Fix permission.
perl/zef: Updated for version 1.0.0
python/PyPy3: updated for version 7.3.19
python/PyPy: updated for version 7.3.19
python/Unidecode: Updated for version 1.4.0.
python/audible-cli: Updated for version 0.3.1.
python/audible: Updated for version 0.9.1.
python/holidays: Add missing dependency.
python/pypy3: updated for version 7.3.19
python/pypy: updated for version 7.3.19
python/python3-ZODB: updated for version 6.0.1
python/python3-aiohttp: Updated for version 3.11.18.
python/python3-alembic: updated for version 1.15.2
python/python3-aniso8601: Updated for version 10.0.1.
python/python3-automat: updated for version 25.4.16
python/python3-backlash: updated for version 0.4.0
python/python3-bcrypt: updated for version 4.3.0
python/python3-bottle: updated for version 0.13.3
python/python3-celery: updated for version 5.5.1
python/python3-decorator: updated for version 5.2.1
python/python3-docstring-to-markdown: Fix dependency.
python/python3-dulwich: updated for version 0.22.8
python/python3-frozenlist: Updated for version 1.6.0.
python/python3-grpcio: Actually remove the 
protobuf-reenable-private-headers patch
python/python3-h11: Updated for version 0.16.0.
python/python3-httpcore: Updated for version 1.0.9.
python/python3-httpx: Updated for version 0.28.1.
python/python3-jsonschema-specifications: Updated for version 2025.4.1.
python/python3-kombu: updated for version 5.5.3
python/python3-lxml: Version bump to 5.4.0
python/python3-more-itertools: Updated for version 10.7.0.
python/python3-msal: Version bump to 1.32.1
python/python3-narwhals: Added (Python module).
python/python3-packaging-opt: Updated for version 25.0.
python/python3-pdm: Version bump to 2.24.1
python/python3-persistent: updated for version 6.1.1
python/python3-plotly: Updated for version 6.0.1.
python/python3-prompt_toolkit: updated for version 3.0.51
python/python3-pyasn1-modules: updated for version 0.4.2
python/python3-qbittorrent-api: Version bump to 2025.4.0
python/python3-setuptools-opt: Updated for version 79.0.1.
python/python3-setuptools-scm-opt: Updated for version 8.3.1.
python/python3-tinydb: Updated for version 4.8.2.
python/python3-turbogears2: updated for version 2.5.0
system/dosbox-staging: updated for version 0.82.1
system/fzf: Updated for version 0.61.3.
system/heatshrink: Added (Data Compression Library).
system/incus: Update to use latest incus-ui
system/kbfs: Mark as x86_64 only.
system/limine: Updated for version 9.2.3
system/oils: Added (Run your shell scripts).
system/oxker-bin: Added (Control Docker Containers).
system/pgbadger: updated for version 13.1
system/postgresql17: Remove unrecognized parameter.
system/postgresql17: Switch to clang to fix aarch64.
system/redis: updated for version 7.4.3
system/slpkg: Updated for version 5.2.5.
system/valkey: updated for version 8.1.1
system/waydroid: Added (Android Container).
system/waydroid: Update README.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250426/818e4e7f/attachment-0001.asc>

From kingbeowulf at linuxgalaxy.org  Wed Apr 30 04:46:45 2025
From: kingbeowulf at linuxgalaxy.org (King Beowulf)
Date: Wed, 30 Apr 2025 04:46:45 +0000
Subject: [Slackbuilds-users] Bluefish and glib2
Message-ID: <073139cf-f790-49ec-aada-77068468dcb6@linuxgalaxy.org>

Hello, just an FYI -

Bluefish-2.2.17 fails to compile with

undefined symbol: g_string_free_and_steal

since Slackware-15.0 glib-2.70 is now too old.? Bluefish now requires 
glib >= 2.76

Thus, I've noted in the README that bluefish-2.2.16 is the last version 
for 15.0.? Since this is a minor update upstream, I'll skip any fix or 
patch since a new Slackware is due out "real soon now, when it's ready."

-kb



From didier at slint.fr  Wed Apr 30 07:39:26 2025
From: didier at slint.fr (Didier Spaier)
Date: Wed, 30 Apr 2025 09:39:26 +0200
Subject: [Slackbuilds-users] Bluefish and glib2
In-Reply-To: <073139cf-f790-49ec-aada-77068468dcb6@linuxgalaxy.org>
References: <073139cf-f790-49ec-aada-77068468dcb6@linuxgalaxy.org>
Message-ID: <93eacadb-2f4a-46ee-a54e-b9403dc74aae@slint.fr>

Hello, just another FYI,

Since nearly a month ago (I April 2025) I have upgraded glib2 to version 2.84.0
(then, 2.84.1) in Slint (mainly based on Slackware64-125.0) reusing the
SlackBuild from Slackware64-current without issue observed by me or reported by
users.

I won't suggesting that this should or could be done by SBo, instead that as
there is no ETA for for a new Slackware version doing that locally could help
users upgrade some software.

Cheers,
Didier

On 30/04/2025 06:46, King Beowulf wrote:
> Hello, just an FYI -
> 
> Bluefish-2.2.17 fails to compile with
> 
> undefined symbol: g_string_free_and_steal
> 
> since Slackware-15.0 glib-2.70 is now too old.? Bluefish now requires 
> glib >= 2.76
> 
> Thus, I've noted in the README that bluefish-2.2.16 is the last version 
> for 15.0.? Since this is a minor update upstream, I'll skip any fix or 
> patch since a new Slackware is due out "real soon now, when it's ready."
> 
> -kb
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 


From willysr at slackbuilds.org  Wed Apr 30 16:02:37 2025
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 30 Apr 2025 23:02:37 +0700
Subject: [Slackbuilds-users] Bluefish and glib2
In-Reply-To: <93eacadb-2f4a-46ee-a54e-b9403dc74aae@slint.fr>
References: <073139cf-f790-49ec-aada-77068468dcb6@linuxgalaxy.org>
 <93eacadb-2f4a-46ee-a54e-b9403dc74aae@slint.fr>
Message-ID: <3229f33e-02e8-47ce-b7c9-ad1e134238e0@slackbuilds.org>

> Since nearly a month ago (I April 2025) I have upgraded glib2 to version 2.84.0
> (then, 2.84.1) in Slint (mainly based on Slackware64-125.0) reusing the
> SlackBuild from Slackware64-current without issue observed by me or reported by
> users.
> 
> I won't suggesting that this should or could be done by SBo, instead that as
> there is no ETA for for a new Slackware version doing that locally could help
> users upgrade some software.

while it does fix this particular issue, it will make another issue 
(just probably not yet discovered) as newer glib2 usually make changes 
that are NOT backward compatible with previous version

This is just one of the example
GLib 2.83.0, 2024-11-06
Rename multiple g_unix_mount_*() APIs to g_unix_mount_entry_*()
Update to Unicode 16.0.0; there may be bugs in linebreaking support

If the program is a toolchain, it's probably easier to create a new 
*-opt script which is newer than what we have in Slackware, like meson, 
setuptools, rust, etc. If it's library, we might end up with same 
situation when some scripts in SBo requires newer glib2/icu4c version in 
the future while the rest is not yet patched to support the newer version.


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250430/cd6fc3d8/attachment.asc>

From didier at slint.fr  Wed Apr 30 16:53:14 2025
From: didier at slint.fr (Didier Spaier)
Date: Wed, 30 Apr 2025 18:53:14 +0200
Subject: [Slackbuilds-users] Bluefish and glib2
In-Reply-To: <3229f33e-02e8-47ce-b7c9-ad1e134238e0@slackbuilds.org>
References: <073139cf-f790-49ec-aada-77068468dcb6@linuxgalaxy.org>
 <93eacadb-2f4a-46ee-a54e-b9403dc74aae@slint.fr>
 <3229f33e-02e8-47ce-b7c9-ad1e134238e0@slackbuilds.org>
Message-ID: <e9540519-797c-48cc-80db-4d287693a1b4@slint.fr>

On 30/04/2025 18:02, Willy Sudiarto Raharjo wrote:
>> Since nearly a month ago (I April 2025) I have upgraded glib2 to version 2.84.0
>> (then, 2.84.1) in Slint (mainly based on Slackware64-125.0) reusing the
>> SlackBuild from Slackware64-current without issue observed by me or reported by
>> users.
>>
>> I won't suggesting that this should or could be done by SBo, instead that as
>> there is no ETA for for a new Slackware version doing that locally could help
>> users upgrade some software.
> 
> while it does fix this particular issue, it will make another issue (just
> probably not yet discovered) as newer glib2 usually make changes that are NOT
> backward compatible with previous version
> 
> This is just one of the example
> GLib 2.83.0, 2024-11-06
> Rename multiple g_unix_mount_*() APIs to g_unix_mount_entry_*()
> Update to Unicode 16.0.0; there may be bugs in linebreaking support

Yes. I will just add that the risk of coming across such a regression is indeed
greater among the 9734 SlackBuilds @ SBo than among the 1260 packages a Slint
user can get without third party packages..

> If the program is a toolchain, it's probably easier to create a new *-opt script
> which is newer than what we have in Slackware, like meson, setuptools, rust,
> etc. If it's library, we might end up with same situation when some scripts in
> SBo requires newer glib2/icu4c version in the future while the rest is not yet
> patched to support the newer version.

Thanks for the heads-up, full list:
https://slackbuilds.org/result/?search=-opt&sv=15.0.
There is also an issue with the software requiring python > 3.9 that leaded me
to build the 21 new deps of orca alongside their 3.9 versions :(

Cython3.11-0.29.36-x86_64-1slint.txz
dbus-python3.11-1.4.0-x86_64-1slint.txz
gobject-introspection3.11-1.84.0-x86_64-2slint.txz
psutil3.11-5.8.0-x86_64-1slint.txz
pycairo3.11-1.27.0-x86_64-1slint.txz
pygobject3.11-3.52.3-x86_64-1slint.txz
pyparsing3.11-2.4.7-x86_64-1slint.txz
python-build3.11-0.7.0-x86_64-slint.txz
python-importlib_metadata3.11-4.8.2-x86_64-1slint.txz
python-installer3.11-0.7.0-x86_64-1slint.txz
python-packaging3.11-21.3-x86_64-1slint.txz
python-pip3.11-25.0.1-x86_64-1slint.txz
python-pygments3.11-2.11.2-x86_64-1slint.txz
python-setuptools3.11-70.0.0-x86_64-1slint.txz
python-setuptools_scm3.11-6.3.2-x86_64-1slint.txz
python-tomli3.11-1.2.2-x86_64-2slint.txz
python-wheel3.11-0.41.2-x86_64-1slint.txz
python3-flit_core3.11-3.9.0-x86_64-1slint.txz
python3.11-3.11.9-x86_64-2slint.txz
setproctitle3.11-1.3.3-x86_64-1slint.txz
speech-dispatcher3.11-0.12.0-x86_64-1slint.txz

Cheers,
Didier

From poprocks at gmail.com  Wed Apr 30 19:36:20 2025
From: poprocks at gmail.com (Logan Rathbone)
Date: Wed, 30 Apr 2025 15:36:20 -0400
Subject: [Slackbuilds-users] Bluefish and glib2
In-Reply-To: <073139cf-f790-49ec-aada-77068468dcb6@linuxgalaxy.org>
References: <073139cf-f790-49ec-aada-77068468dcb6@linuxgalaxy.org>
Message-ID: <CAFOgM0rvSKAUYo1MSzC90UFHjKRcwHKVEgkCo5PXQVym7P0mTQ@mail.gmail.com>

On Wed, Apr 30, 2025 at 12:47?AM King Beowulf
<kingbeowulf at linuxgalaxy.org> wrote:
>
> Hello, just an FYI -
>
> Bluefish-2.2.17 fails to compile with
>
> undefined symbol: g_string_free_and_steal

Yes, when I first saw this I assumed it was an issue of having a local
version of glib2 installed that is too new for bluefish, and some
other function call is calling g_string_free_and_steal, resulting in a
linker error.

But i see looking at the bluefish source code that it does indeed call
g_string_free_and_steal, which should have caused it to bump its
configure.ac version of glib2 required, but it still claims to support
glib2 >= 2.24, which is way off.

Has this been reported upstream?

From sbo at linuxgalaxy.org  Wed Apr 30 20:16:49 2025
From: sbo at linuxgalaxy.org (KB_SBo)
Date: Wed, 30 Apr 2025 20:16:49 +0000
Subject: [Slackbuilds-users] Bluefish and glib2
In-Reply-To: <CAFOgM0rvSKAUYo1MSzC90UFHjKRcwHKVEgkCo5PXQVym7P0mTQ@mail.gmail.com>
References: <073139cf-f790-49ec-aada-77068468dcb6@linuxgalaxy.org>
 <CAFOgM0rvSKAUYo1MSzC90UFHjKRcwHKVEgkCo5PXQVym7P0mTQ@mail.gmail.com>
Message-ID: <11dd5037-5682-43cf-a852-be55f4fea1df@linuxgalaxy.org>

On 4/30/25 12:36, Logan Rathbone wrote:
> On Wed, Apr 30, 2025 at 12:47?AM King Beowulf
> <kingbeowulf at linuxgalaxy.org> wrote:
>>
>> Hello, just an FYI -
>>
>> Bluefish-2.2.17 fails to compile with
>>
>> undefined symbol: g_string_free_and_steal
...

> 
> But i see looking at the bluefish source code that it does indeed call
> g_string_free_and_steal, which should have caused it to bump its
> configure.ac version of glib2 required, but it still claims to support
> glib2 >= 2.24, which is way off.
> 
> Has this been reported upstream?

I was going to but then the version bump did not include any significant 
functional fixes over 2.2.16 for linux, mostly just build system 
updates, so I'm just going to let it go and hope 16.0 (or whatever) gets 
released.

I'm not a fan of creating *-opt local scripts "willy-nilly" (pun 
intended) for each of these edge cases.  I already have a 
python3-meson-opt for qemu, and I'd like to avoid that sort of nonsense, 
if at all possible.

-kb