From urchlay at slackware.uk Sun Dec 1 04:03:20 2024 From: urchlay at slackware.uk (B. Watson) Date: Sat, 30 Nov 2024 23:03:20 -0500 (EST) Subject: [Slackbuilds-users] Postgis can and can't find gdal In-Reply-To: References: Message-ID: <8c617650-ec98-ce66-2b66-45415f6fef4@slackware.uk> On Sat, 30 Nov 2024, M Wedin wrote: > I'm trying to compile todays updates. Right now postgis stumped the > queue, and I don't understand why it finds gdal and then says it isn't > found. For what it's worth, I saw your email and kicked off a compile of postgis and all its dependencies. It built fine here, in a clean VM (again, for what that's worth). > checking for gdal-config... /usr/bin/gdal-config > checking GDAL version... 3.9.3 > checking for OGR enabled... yes > checking gdal.h usability... yes > checking gdal.h presence... yes > checking for gdal.h... yes Same output here. > checking for library containing GDALAllRegister... no > configure: error: could not find GDAL This bit is different. I get this: checking for library containing GDALAllRegister... none required For more detail, you'll have to look in config.log. It should be in the same dir as the configure script (/tmp/SBo/postgis-3.4.2). It's got *excruciating* amounts of information in it, but you should be able to find the reason it complained. From slack at giand.it Sun Dec 1 22:52:15 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Sun, 1 Dec 2024 23:52:15 +0100 Subject: [Slackbuilds-users] Please remove qgis from pending Message-ID: <02dbaa18-d343-4b1a-9714-0b87926d209f@giand.it> Sorry, in current it's ok, so I submitted the update before ending the build in stable when it was at 99%. Unfortunately make install return an error due a file not found. I have to find the issue, but at the moment the slackbuild cannot be updated. Please remove my submission, thanks -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From sbo at linuxgalaxy.org Mon Dec 2 05:51:26 2024 From: sbo at linuxgalaxy.org (KB_SBo) Date: Mon, 02 Dec 2024 05:51:26 +0000 Subject: [Slackbuilds-users] Orphaned Message-ID: admins, Since the following is marked "orphaned" System/pigz I'll take it if there are no prior claims. pigz just popped up as a dependency for the Linux Game Server Manager which now uses pigz instead of plain gzip what making game server backups. -kb From urchlay at slackware.uk Mon Dec 2 06:47:27 2024 From: urchlay at slackware.uk (B. Watson) Date: Mon, 2 Dec 2024 01:47:27 -0500 (EST) Subject: [Slackbuilds-users] Orphaned In-Reply-To: References: Message-ID: <1186f9fe-1fc7-644a-2da9-8b8caf8a80df@slackware.uk> On Mon, 2 Dec 2024, KB_SBo wrote: > System/pigz > > I'll take it if there are no prior claims. Go for it. From julian at dotcore.co.il Mon Dec 2 09:12:36 2024 From: julian at dotcore.co.il (Julian Grinblat) Date: Mon, 2 Dec 2024 18:12:36 +0900 Subject: [Slackbuilds-users] scala package Message-ID: scala in slackbuilds.org is many versions behind now, and I had to upgrade to the latest version for it to work. I tried emailing Alessandro about it. He had responded to me promptly in the past regarding this package, but I haven't heard from him in almost a month now. If it is considered abandoned, I am willing to continue maintaining it. It would remain scala 2, although when 15.1 gets released, it might be worth it to upgrade to 3, and add a new scala2 package. From willysr at slackbuilds.org Mon Dec 2 11:32:50 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 2 Dec 2024 18:32:50 +0700 Subject: [Slackbuilds-users] scala package In-Reply-To: References: Message-ID: <9986da54-788e-4c8b-a25e-b5f5de969cbb@slackbuilds.org> > scala in slackbuilds.org is many versions behind now, and I had to > upgrade to the latest version for it to work. I tried emailing > Alessandro about it. He had responded to me promptly in the past > regarding this package, but I haven't heard from him in almost a month > now. > If it is considered abandoned, I am willing to continue maintaining it. > It would remain scala 2, although when 15.1 gets released, it might be > worth it to upgrade to 3, and add a new scala2 package. There's no other package requiring scala, so if you have other packages required newer version, go for it and update the existing one and take over maintainership -- 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: From willysr at slackbuilds.org Wed Dec 4 13:40:48 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 4 Dec 2024 20:40:48 +0700 Subject: [Slackbuilds-users] Plan for x265 Major Update Message-ID: <63c35422-deb5-4150-b82f-768137bd0870@slackbuilds.org> Hi i'm planning to push (again) for x265 4.1 Last time i tried to push, it breaks some scripts due to ABI changes (which is now reverted by upstream), so we reverted back to 3.6 Now upstream has released 4.1 which should be compatible with the old ABI, so let's test them again i have tried to build all scripts that depends on x265 on this github PR https://github.com/SlackBuildsOrg/slackbuilds/pull/8998 The issue is just runtime issues can't be detected by github CI. It will only tells us that the build works just fine, but we need actual people who uses those softwares to test if it's broken with the update. If you happens to use one of those software, please test them with x265 4.1 and let us know. If all goes ok, i plan to merge that PR for this week's update 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: From willysr at slackbuilds.org Sat Dec 7 02:38:42 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 7 Dec 2024 09:38:42 +0700 Subject: [Slackbuilds-users] Updates - 20241207.1 Message-ID: <41d3f541-9468-46eb-b104-f56c7c7868ef@slackbuilds.org> Sat Dec 7 02:28:50 UTC 2024 academic/edsim51di: Updated for version 2.1.38. accessibility/xsct: Added (X11 set color temperature). audio/qjackctl: Updated for version 1.0.3. audio/rubberband: Updated for version 4.0.0. desktop/cinnamon-desktop: Update for 6.4.1 desktop/fvwm3: Updated for verson 1.1.1. desktop/j4-dmenu-desktop: Updated for version 3.2. desktop/mint-themes: Update for 2.2.0 desktop/mint-y-icons: Update for 1.7.9 (+remove monochrome icons) desktop/numix-icon-theme-circle: Update for 24.10.22 desktop/numix-icon-theme-square: Update for 24.10.22 desktop/numix-icon-theme: Update for 24.09.18 desktop/nwg-panel: Updated for version 0.9.53. desktop/ufetch: Updated for version 0.4. desktop/yaru-icon-theme: Added (Icon Theme). development/github-cli: Updated for version 2.63.2 development/javacc: Fix ownership. development/jupyter-nbclient: Update for 0.10.1 development/pnpm: Updated for version 9.15.0. development/postman: Updated for version 11.22.0. development/sbt: Updated for version 1.10.6 development/scala: Updated for version 2.13.15 development/yabasic: Updated for version 2.90.5 games/acidwarp: Added (eye-candy program). games/bsd-tetris: Added (Tetris game). games/ecwolf: Fix -current build. games/ltris: Updated for version 2.0.3. games/paranoia: Added (text adventure game). games/pokerth: Fix more underlinking with the newest protobuf. games/stella: Updated for version 7.0. games/xbill: Added (xbill Game). games/xtetris: Added (tetris game). gis/osm2pgsql: Updated for version 2.0.0. gis/pgrouting: Updated for version 3.7.0. gis/qgis: Updated for version 3.40.1. gis/saga-gis: Updated for version 9.6.1. git/ci: Update CI dependencies. graphics/blender: Version bump to 4.3.0 graphics/pqiv: Updated for version 2.13.2. graphics/vuescan: Updated MD5SUM_x86_64. graphics/xviewer: Update for 3.4.7 ham/satdump: Updated for version 1.2.2. ham/sdrangel: Updated for version 7.22.4. libraries/digimend-kernel-drivers: Add detection for kernel 6.x. libraries/grpc: Update for 1.68.2 libraries/libgpr: Added (Handle GNAT project file). libraries/qt-avif-image-plugin: Updated for version 0.8.7. libraries/qt-jpegxl-image-plugin: Updated for version 0.7.0. libraries/webkit2gtk4.1: Fix build. libraries/webkit2gtk: Fix build. libraries/xapp: Updated for version 2.8.6 multimedia/HandBrake: Version bump to 1.9.0 multimedia/UxPlay: Added (AirPlay Unix mirroring server). multimedia/avidemux: Add patch for x265-4.1 update. multimedia/plexmediaserver: Updated for version 1.41.2.9200_c6bbc1b53. multimedia/x265: Updated for version 4.1. network/discord: Version bump to 0.0.76 network/dnsproxy-bin: Updated for version 0.73.4. network/element-desktop: updated for version 1.11.87 network/gallery-dl: Updated for version 1.28.0. network/gmi100: Update script. network/grafana: Updated for version 11.4.0. network/grpcurl: Updated for version 1.9.2 network/mullvadvpn-app: Updated for version 2024.8. network/nchat: Updated for version 5.3.5. network/nextcloud-server: Updated for version 29.0.10. network/opera: Updated for version 115.0.5322.77. network/prosody-mod-cloud-notify: Fix installing docs. network/prosody-mod-filter-chatstates: Fix installing docs. network/prosody-mod-http-upload: Fix installing docs. network/prosody-mod-throttle-presence: Fix installing docs. network/prosody-mod-turncredentials: Fix installing docs. network/prosody-mod-vcard-muc: Fix installing docs. network/syncterm: Updated for version 1.3. network/syncthingtray-bin: Updated for version 1.6.4. network/telegram: Updated for version 5.9.0. network/teleport-connect: Updated for version 17.0.4. network/vivaldi: Updated for version 7.0.3495.20. office/smoffice2024: Updated for version 2024-1220 python/python3-aiohappyeyeballs: Updated for version 2.4.4. python/python3-anyio: Updated for version 4.7.0. python/python3-async-timeout: Updated for version 5.0.1. python/python3-fastjsonschema: Update for 2.21.1 python/python3-geventhttpclient: Updated for version 2.3.3. python/python3-grpcio: Update for 1.68.2 python/python3-json5: Updated for version 0.10.0. python/python3-prometheus_client: Update for 0.21.1 python/python3-propcache: Updated for version 0.2.1. python/python3-pytest: Version bump to 8.3.4 python:python3-aiohttp: Updated for version 3.11.9. system/7zip: Updated for version 20.09 system/apache-cassandra: Updated for version 4.1.7. system/conky: Updated for version 1.21.9. system/docker-compose: Updated for version 2.31.0 system/doublecmd-qt5: Updated for version 1.1.21 system/fastfetch: Updated for version 2.31.0. system/iselect: Updated for version 1.4.2. system/locust: Updated for version 2.32.4. system/logiops: Added (driver for Logitech). system/memtester: Updated for version 4.7.0. system/mmv: Updated for version 2.10. system/nemo-fileroller: Update for 6.4.0 system/nemo: Update for 6.4.2 system/nemo: Update for 6.4.3 system/nerdctl: Relocate package docs system/nerdctl: Update GITHASH system/nerdctl: Updated for version 2.0.1 system/pigz: New maintainer system/plocate: Updated for version 1.1.23. system/prometheus: Updated for version 3.0.1 system/sbotools2: Updated for version 2.7.2. system/sbotools: Updated for version 3.1. system/slpkg: Updated for version 5.1.6. +--------------------------+ -- 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: From urchlay at slackware.uk Sat Dec 7 03:28:20 2024 From: urchlay at slackware.uk (B. Watson) Date: Fri, 6 Dec 2024 22:28:20 -0500 (EST) Subject: [Slackbuilds-users] Updates - 20241207.1 In-Reply-To: <41d3f541-9468-46eb-b104-f56c7c7868ef@slackbuilds.org> References: <41d3f541-9468-46eb-b104-f56c7c7868ef@slackbuilds.org> Message-ID: On Sat, 7 Dec 2024, Willy Sudiarto Raharjo wrote: > multimedia/x265: Updated for version 4.1. It's worth mentioning: any software that uses x265 probably needs to be rebuilt after upgrading x265 to 4.1. Builds affected: avidemux (x265 is optional) fceux (x265 is optional) heif-gimp-plugin kaffeine kaffeine-mozilla libheif obs-studio qdvdauthor qt-heif-image-plugin sopcast-player vlc vlsub These have been tested with the new x265 and should have no problems building/running with it. However, there have been some ABI changes in x265, so it's a good idea to rebuild these if you use them. In particular, avidemux will likely segfault if it was built with the old x265 and you try to run it with the new one and encode a video with the x265 codec. From slackcoder at server.ky Mon Dec 9 14:16:36 2024 From: slackcoder at server.ky (Slack Coder) Date: Mon, 9 Dec 2024 09:16:36 -0500 Subject: [Slackbuilds-users] Slackbuilds and GPG Message-ID: <1019b63a-c31f-4f1c-8a58-1f929d459f77@server.ky> Hi, Would the admin's consider publishing slackbuilds.org/GPG-KEY with security at slackware.com's signature?? As of now users need to fetch it from the key servers. Also, using the CHECKSUMS.md5 file fails after cloning using rsync.? Some of CHECKSUMS.md5's listed files are missing. ``` rsync -azq rsync://slackbuilds.org/slackbuilds/15.0 . cd 15.0 tail +13 CHECKSUMS.md5 | md5sum -c --quiet -; echo $? # md5sum: ./.github/workflows/ci.yml: No such file or directory # ./.github/workflows/ci.yml: FAILED open or read # md5sum: ./.gitlab-ci.yml: No such file or direcory # ./.gitlab-ci.yml: FAILED open or read # md5sum: WARNING: 2 listed files could not be read # 1 ``` Best Regards, Slack From willysr at slackbuilds.org Mon Dec 9 15:17:38 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 9 Dec 2024 22:17:38 +0700 Subject: [Slackbuilds-users] Slackbuilds and GPG In-Reply-To: <1019b63a-c31f-4f1c-8a58-1f929d459f77@server.ky> References: <1019b63a-c31f-4f1c-8a58-1f929d459f77@server.ky> Message-ID: > Also, using the CHECKSUMS.md5 file fails after cloning using rsync. Some > of CHECKSUMS.md5's listed files are missing. > > ``` > > rsync -azq rsync://slackbuilds.org/slackbuilds/15.0 . > > cd 15.0 > > tail +13 CHECKSUMS.md5 | md5sum -c --quiet -; echo $? > > # md5sum: ./.github/workflows/ci.yml: No such file or directory > # ./.github/workflows/ci.yml: FAILED open or read > # md5sum: ./.gitlab-ci.yml: No such file or direcory > # ./.gitlab-ci.yml: FAILED open or read > # md5sum: WARNING: 2 listed files could not be read > # 1 These files should not be listed i will have a look on 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: From willysr at slackbuilds.org Mon Dec 9 15:21:53 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 9 Dec 2024 22:21:53 +0700 Subject: [Slackbuilds-users] Slackbuilds and GPG In-Reply-To: References: <1019b63a-c31f-4f1c-8a58-1f929d459f77@server.ky> Message-ID: <23b4620e-79f5-495a-a473-a2458ba57fce@slackbuilds.org> >> Also, using the CHECKSUMS.md5 file fails after cloning using rsync. >> Some of CHECKSUMS.md5's listed files are missing. >> >> ``` >> >> rsync -azq rsync://slackbuilds.org/slackbuilds/15.0 . >> >> cd 15.0 >> >> tail +13 CHECKSUMS.md5 | md5sum -c --quiet -; echo $? >> >> # md5sum: ./.github/workflows/ci.yml: No such file or directory >> # ./.github/workflows/ci.yml: FAILED open or read >> # md5sum: ./.gitlab-ci.yml: No such file or direcory >> # ./.gitlab-ci.yml: FAILED open or read >> # md5sum: WARNING: 2 listed files could not be read >> # 1 > > These files should not be listed > i will have a look on it it should be fixed now -- 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: From slackcoder at server.ky Tue Dec 10 11:23:04 2024 From: slackcoder at server.ky (Slack Coder) Date: Tue, 10 Dec 2024 06:23:04 -0500 Subject: [Slackbuilds-users] Slackbuilds and GPG In-Reply-To: <23b4620e-79f5-495a-a473-a2458ba57fce@slackbuilds.org> References: <1019b63a-c31f-4f1c-8a58-1f929d459f77@server.ky> <23b4620e-79f5-495a-a473-a2458ba57fce@slackbuilds.org> Message-ID: Thanks, though unfortunately ./.github/workflows/ci.yml is still causing problems. ``` (rm -fr 15.0; rsync -azq rsync://slackbuilds.org/slackbuilds/15.0 . ; cd 15.0; tail +13 CHECKSUMS.md5 | md5sum -c --quiet -;echo $?) md5sum: ./.github/workflows/ci.yml: No such file or directory ./.github/workflows/ci.yml: FAILED open or read md5sum: WARNING: 1 listed file could not be read 1 ``` On 12/9/24 10:21, Willy Sudiarto Raharjo wrote: >>> Also, using the CHECKSUMS.md5 file fails after cloning using rsync. >>> Some of CHECKSUMS.md5's listed files are missing. >>> >>> ``` >>> >>> rsync -azq rsync://slackbuilds.org/slackbuilds/15.0 . >>> >>> cd 15.0 >>> >>> tail +13 CHECKSUMS.md5 | md5sum -c --quiet -; echo $? >>> >>> # md5sum: ./.github/workflows/ci.yml: No such file or directory >>> # ./.github/workflows/ci.yml: FAILED open or read >>> # md5sum: ./.gitlab-ci.yml: No such file or direcory >>> # ./.gitlab-ci.yml: FAILED open or read >>> # md5sum: WARNING: 2 listed files could not be read >>> # 1 >> >> These files should not be listed >> i will have a look on it > > it should be fixed now > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From willysr at slackbuilds.org Tue Dec 10 15:29:33 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 10 Dec 2024 22:29:33 +0700 Subject: [Slackbuilds-users] Slackbuilds and GPG In-Reply-To: References: <1019b63a-c31f-4f1c-8a58-1f929d459f77@server.ky> <23b4620e-79f5-495a-a473-a2458ba57fce@slackbuilds.org> Message-ID: > Thanks, though unfortunately ./.github/workflows/ci.yml is still causing > problems. > > > ``` > (rm -fr 15.0; rsync -azq rsync://slackbuilds.org/slackbuilds/15.0 . ; cd > 15.0; tail +13 CHECKSUMS.md5 | md5sum -c --quiet -;echo $?) > md5sum: ./.github/workflows/ci.yml: No such file or directory > ./.github/workflows/ci.yml: FAILED open or read > md5sum: WARNING: 1 listed file could not be read > 1 Please re-check again it should be fixed now -- 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: From slackcoder at server.ky Tue Dec 10 18:51:45 2024 From: slackcoder at server.ky (Slack Coder) Date: Tue, 10 Dec 2024 13:51:45 -0500 Subject: [Slackbuilds-users] Slackbuilds and GPG In-Reply-To: References: <1019b63a-c31f-4f1c-8a58-1f929d459f77@server.ky> <23b4620e-79f5-495a-a473-a2458ba57fce@slackbuilds.org> Message-ID: <139a962c-8b63-439f-8e57-109277bbb624@server.ky> On 12/10/24 10:29, Willy Sudiarto Raharjo wrote: >> Thanks, though unfortunately ./.github/workflows/ci.yml is still >> causing problems. >> >> >> ``` >> (rm -fr 15.0; rsync -azq rsync://slackbuilds.org/slackbuilds/15.0 . ; >> cd 15.0; tail +13 CHECKSUMS.md5 | md5sum -c --quiet -;echo $?) >> md5sum: ./.github/workflows/ci.yml: No such file or directory >> ./.github/workflows/ci.yml: FAILED open or read >> md5sum: WARNING: 1 listed file could not be read >> 1 > > Please re-check again > it should be fixed now > Nice, working. Re: the GPG key signature, it would be nice to have.? Alienbob includes it, and fetching security at slackware.com's signature from the keyserver's now requires an obscure '--keyserver-options no-self-sigs-only' argument.? Refreshing the key with the flag and re-exporting it to file will include it. From bobfunk11 at gmail.com Tue Dec 10 21:10:58 2024 From: bobfunk11 at gmail.com (Bob Funk) Date: Tue, 10 Dec 2024 15:10:58 -0600 Subject: [Slackbuilds-users] Looking to drop my xvfb-run SlackBuild In-Reply-To: References: Message-ID: So the 'xvfb-run' source URL has gone and changed again so this will fail to build unless it gets updated. Can an admin mark 'xvfb-run' for removal for next SBo update this weekend? No-one has reached out with interest in maintaining this package, and I have no interest either. Thanks, Bob Funk On Fri, May 24, 2024 at 4:24?PM Bob Funk wrote: > Hi, > > I maintain the 'xvfb-run' SlackBuild on slackbuilds.org. I no longer have > any use for it and would like to drop maintaining it. If anyone wants it, > feel free to take over. Otherwise if there's no interest after a while I'll > request the admin to remove it. > > For some background/context if anyone wants: > My 'mutter' and 'gnome-shell' slackbuilds used to depend on this package > for running some tests. I've removed that dependency and no longer need the > 'xvfb-run' package. The 'xvfb-run' package is a wrapper script for the Xvfb > server. It gets packaged with xvfb server by other distros like > debian/fedora/etc, but not in Slackware. This slackbuild is one I took over > from the previous abondoner and just maintained it because I had it as a > dependency. The annoying part about it is that it extracts the wrapper > script from a debian xvfb server package, and the source url/package > changes every other month or so when debian updates xvfb server. It really > should get a stable host of that wrapper script on github or something, but > I just don't have use for it anymore so I'd rather leave it for someone who > cares and uses it. > > Thanks for your time, > > Bob > -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Tue Dec 10 22:13:13 2024 From: urchlay at slackware.uk (B. Watson) Date: Tue, 10 Dec 2024 17:13:13 -0500 (EST) Subject: [Slackbuilds-users] Looking to drop my xvfb-run SlackBuild In-Reply-To: References: Message-ID: <68b4bfb6-495b-2659-50ac-a0bae627e97c@slackware.uk> On Tue, 10 Dec 2024, Bob Funk wrote: > So the 'xvfb-run' source URL has gone and changed again so this will fail to build unless it gets updated. > > Can an admin mark 'xvfb-run' for removal for next SBo update this weekend? No-one has reached out with interest in maintaining this package, and I have no interest either. I'll take over the build. Even though it's no longer a dependency for anything else, it looks like it could be useful. The "source" for xvfb-run only exists as part of the .diff that the Debian package applies to the xorg-server source. It doesn't change often (last update to the script was in 2018), and it's stupid to keep having "new" versions of it just because the source URL changed. What I'm going to do is extract just the script and man page from the Debian package, and host them on slackware.uk. And maybe bug the Debian maintainers to see if they'll host the script separately and give it a separate copyright/license: right now the copyright file in our xvfb-run package is over 7x the size of the script and man page put together, and names every corporate and individual contributor to the X.org project. From didier at slint.fr Tue Dec 10 23:15:38 2024 From: didier at slint.fr (Didier Spaier) Date: Wed, 11 Dec 2024 00:15:38 +0100 Subject: [Slackbuilds-users] I suggest to drop libksu and gksu, see what to do with qControlCenter. Message-ID: <13679644-415a-46cc-948b-b63f6517d12b@slint.fr> Hello, I have abandoned these scripts long ago, although I be still listed as maintainer by https://slackbuilds.org/advsearch.php?q=Didier+Spaier&stype=maint I don't use libgksu and gksu anymore and gnsu is a good replacement: https://github.com/gapan/gnsu (gapan aka George Vlahavas is the Salix maintainer). Building it is rather trivial. qControlCenter, if someone wants to maintain it, should no mare built from my github repo by from the one from Dimitris Tzemos (Slackel maintainer) who has taken over upstream maintenance: https://github.com/djemos/qControlCenter Dimitris as ported this software to python3 and PyQt5. If no one wants to take qControlCenter I suggest to drop it. Cheers, Didier From shin1.abe at nifty.com Wed Dec 11 00:17:44 2024 From: shin1.abe at nifty.com (ABE Shin-ichi) Date: Wed, 11 Dec 2024 09:17:44 +0900 Subject: [Slackbuilds-users] Plan for x265 Major Update In-Reply-To: <63c35422-deb5-4150-b82f-768137bd0870@slackbuilds.org> References: <63c35422-deb5-4150-b82f-768137bd0870@slackbuilds.org> Message-ID: <20241211091744.54b30654dea160ec04617ed5@nifty.com> Hi, Willy My slackware environment is 64-current. I upgraded x265 to version 4.1 two weeks ago. 1. FFmpeg I compiled ffmpeg-7.1 with --enable-libx265 and it works fine now. # ldd /usr/bin/ffmpeg |grep libx265 libx265.so.215 => /usr/share/cuda/lib64/libx265.so.215 (0x00007fb38ca00000 2. vlc # ldd /usr/lib64/vlc/plugins/codec/libx265_plugin.so |grep libx265 libx265.so.215 => /usr/share/cuda/lib64/libx265.so.215 (0x00007f87c2800000) 3. avidemux2 I comiled avidemux by using the latest git source (ce994de41a644f83d4d0c3f8c7be5c9deff7bbcf) with SBo's "x265-4.1.diff". The package was successfully created and working fine with "Nvidia HENVC" video encoder plugin. # ldd /usr/lib64/ADM_plugins6/videoEncoders/libADM_ve_x265_other.so |grep libx265 libx265.so.215 => /usr/share/cuda/lib64/libx265.so.215 (0x00007f17f3e00000) Thank you for x65-4.1.diff patch. I appreciate you and SBo team. JW -- JW (ABE Shin-ichi ) From urchlay at slackware.uk Wed Dec 11 01:53:12 2024 From: urchlay at slackware.uk (B. Watson) Date: Tue, 10 Dec 2024 20:53:12 -0500 (EST) Subject: [Slackbuilds-users] Plan for x265 Major Update In-Reply-To: <20241211091744.54b30654dea160ec04617ed5@nifty.com> References: <63c35422-deb5-4150-b82f-768137bd0870@slackbuilds.org> <20241211091744.54b30654dea160ec04617ed5@nifty.com> Message-ID: <36d9b724-4ede-67dd-a63e-d422d482e7c5@slackware.uk> On Wed, 11 Dec 2024, ABE Shin-ichi wrote: > Thank you for x65-4.1.diff patch. > I appreciate you and SBo team. We appreciate your thorough testing. Thanks. From jebrhansen+SBo at gmail.com Wed Dec 11 02:17:42 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 10 Dec 2024 18:17:42 -0800 Subject: [Slackbuilds-users] I suggest to drop libksu and gksu, see what to do with qControlCenter. In-Reply-To: <13679644-415a-46cc-948b-b63f6517d12b@slint.fr> References: <13679644-415a-46cc-948b-b63f6517d12b@slint.fr> Message-ID: On Tue, Dec 10, 2024, 3:16?PM Didier Spaier via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hello, > > I have abandoned these scripts long ago, although I be still listed as > maintainer by > https://slackbuilds.org/advsearch.php?q=Didier+Spaier&stype=maint Just an FYI, I think the old maintainer generally needs to be the one to submit the update to mark them as unmaintained. Announcing on the mailing list just allows others to take over but typically won't cause the SBo admins to remove your name. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Wed Dec 11 18:01:37 2024 From: didier at slint.fr (Didier Spaier) Date: Wed, 11 Dec 2024 19:01:37 +0100 Subject: [Slackbuilds-users] I suggest to drop libksu and gksu, see what to do with qControlCenter. In-Reply-To: References: <13679644-415a-46cc-948b-b63f6517d12b@slint.fr> Message-ID: <53d375ca-addf-4b35-b7d2-f698da71bc80@slint.fr> On 11/12/2024 03:17, Jeremy Hansen wrote: > On Tue, Dec 10, 2024, 3:16?PM Didier Spaier via SlackBuilds-users users at slackbuilds.org > wrote: > I have abandoned these scripts long ago, although I be still listed as > maintainer by https://slackbuilds.org/advsearch.php? > q=Didier+Spaier&stype=maint q=Didier+Spaier&stype=maint> > > > Just an FYI, I think the old maintainer generally needs to be the one to submit > the update to mark them as unmaintained. Announcing on the mailing list just > allows others to take over but typically won't cause the SBo admins to remove > your name.? Thanks for your answer Jeremy. Let's take libksu as an example. I understand that I should: 1. Download the tarball and extract the tarball: https://slackbuilds.org/slackbuilds/15.0/libraries/libgksu.tar.gz 2. Do in the .info: s/MAINTAINER="Didier Spaier"/MAINTAINER="unmaintained" s/EMAIL="didier at slint dot fr"/EMIL="" 3. make a new tarball with the changes and submit to https://slackbuilds.org/submit/ Is this correct? Other questions or issues: Looking at this SlackBuild: https://slackbuilds.org/slackbuilds/15.0/libraries/libgksu/libgksu.SlackBuild It appears that this script is actually maintained by B. Watson so would it not be preferable to make official that he is the current maintainer in such a case? I think that I should first ask him if he prefers that or drop the script. For gksu the last change is from Heinz Wiesinger on 2021-07-17 but his name does not appear anywhere in the tarball, same for qControlCenter. What should I do? Cheers, Didier From list+sbo at vahedi.org Wed Dec 11 18:43:46 2024 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Wed, 11 Dec 2024 18:43:46 +0000 Subject: [Slackbuilds-users] Cannot build elinks Message-ID: <1ef621d78d4da0d82a7dbea799950278c33926ef@vahedi.org> Building "elinks" on Slackware64-15.0 fails during the linking process: ------------------------- [LINK] src/elinks /usr/bin/ld: lib.o: in function `l_tmpname': core.c:(.text+0x74bc4): warning: the use of `tempnam' is dangerous, better use `mkstemp' /usr/bin/ld: lib.o: in function `script_hook_pre_format_html': hooks.c:(.text+0x75743): undefined reference to `lua_strlen' collect2: error: ld returned 1 exit status ------------------------- Could this be related to lua-jit upgrade of few weeks ago? -- Shahab From urchlay at slackware.uk Wed Dec 11 20:36:12 2024 From: urchlay at slackware.uk (B. Watson) Date: Wed, 11 Dec 2024 15:36:12 -0500 (EST) Subject: [Slackbuilds-users] Cannot build elinks In-Reply-To: <1ef621d78d4da0d82a7dbea799950278c33926ef@vahedi.org> References: <1ef621d78d4da0d82a7dbea799950278c33926ef@vahedi.org> Message-ID: On Wed, 11 Dec 2024, Shahab Vahedi via SlackBuilds-users wrote: > Could this be related to lua-jit upgrade of few weeks ago? It could be, and probably is. I thought I'd tested elinks with the new lua, but I'll check again. From urchlay at slackware.uk Wed Dec 11 20:53:49 2024 From: urchlay at slackware.uk (B. Watson) Date: Wed, 11 Dec 2024 15:53:49 -0500 (EST) Subject: [Slackbuilds-users] Cannot build elinks In-Reply-To: References: <1ef621d78d4da0d82a7dbea799950278c33926ef@vahedi.org> Message-ID: <11b98f8-d8e0-6d46-d5b8-eaa3b9b3bf99@slackware.uk> On Wed, 11 Dec 2024, B. Watson wrote: > > > On Wed, 11 Dec 2024, Shahab Vahedi via SlackBuilds-users wrote: > >> Could this be related to lua-jit upgrade of few weeks ago? > > It could be, and probably is. I thought I'd tested elinks with the new > lua, but I'll check again. Yep. I'd fixed it locally, but the fix never made its way into git. If you don't want to wait for this week's update, you can easily apply the fix yourself: Edit elinks.SlackBuid. Change line 137 from this: CFLAGS="$SLKCFLAGS -L/usr/lib$LIBDIRSUFFIX" \ ...to this: CFLAGS="$SLKCFLAGS -L/usr/lib$LIBDIRSUFFIX -DLUA_COMPAT_5_3" \ ...or, you can checkout my branch from the git repo. Thanks for spotting this! From list+sbo at vahedi.org Wed Dec 11 21:33:44 2024 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Wed, 11 Dec 2024 21:33:44 +0000 Subject: [Slackbuilds-users] Cannot build elinks In-Reply-To: <11b98f8-d8e0-6d46-d5b8-eaa3b9b3bf99@slackware.uk> References: <1ef621d78d4da0d82a7dbea799950278c33926ef@vahedi.org> <11b98f8-d8e0-6d46-d5b8-eaa3b9b3bf99@slackware.uk> Message-ID: December 11, 2024, "B. Watson" wrote: > If you don't want to wait for this week's update, you can easily apply > the fix yourself: > > Edit elinks.SlackBuid. Change line 137 from this: > > CFLAGS="$SLKCFLAGS -L/usr/lib$LIBDIRSUFFIX" \ > > ...to this: > > CFLAGS="$SLKCFLAGS -L/usr/lib$LIBDIRSUFFIX -DLUA_COMPAT_5_3" \ That works on my end. Thank you! -- Shahab From urchlay at slackware.uk Wed Dec 11 22:36:58 2024 From: urchlay at slackware.uk (B. Watson) Date: Wed, 11 Dec 2024 17:36:58 -0500 (EST) Subject: [Slackbuilds-users] Cannot build elinks In-Reply-To: References: <1ef621d78d4da0d82a7dbea799950278c33926ef@vahedi.org> <11b98f8-d8e0-6d46-d5b8-eaa3b9b3bf99@slackware.uk> Message-ID: <559f7cea-aff9-46c0-b34e-b98b2f26d14@slackware.uk> On Wed, 11 Dec 2024, Shahab Vahedi via SlackBuilds-users wrote: > That works on my end. Thank you! Interestingly enough, elinks will build with lua support if it finds either lua51 or lua, but it won't use luajit. I'm a daily elinks user, I've been using a build that's linked with lua 5.4, but I never tried to use the lua scripting support. I see there's also perl scripting support (disabled by default), I'd be more likely to use that if I wanted to script the browser. Hmm. From urchlay at slackware.uk Fri Dec 13 12:14:15 2024 From: urchlay at slackware.uk (B. Watson) Date: Fri, 13 Dec 2024 07:14:15 -0500 (EST) Subject: [Slackbuilds-users] Looking to drop my xvfb-run SlackBuild In-Reply-To: <68b4bfb6-495b-2659-50ac-a0bae627e97c@slackware.uk> References: <68b4bfb6-495b-2659-50ac-a0bae627e97c@slackware.uk> Message-ID: <2b2cd27e-4c22-24f2-3761-6ea23d67f7c8@slackware.uk> On Tue, 10 Dec 2024, B. Watson wrote: > I'll take over the build. Even though it's no longer a dependency for > anything else, it looks like it could be useful. I ran out of time this week. I'll take over the xvfb-run build after this week's update. Sorry for the delay. From bobfunk11 at gmail.com Fri Dec 13 20:54:32 2024 From: bobfunk11 at gmail.com (Bob Funk) Date: Fri, 13 Dec 2024 14:54:32 -0600 Subject: [Slackbuilds-users] Looking to drop my xvfb-run SlackBuild In-Reply-To: <2b2cd27e-4c22-24f2-3761-6ea23d67f7c8@slackware.uk> References: <68b4bfb6-495b-2659-50ac-a0bae627e97c@slackware.uk> <2b2cd27e-4c22-24f2-3761-6ea23d67f7c8@slackware.uk> Message-ID: No worries, thanks for taking over the build and looking into getting a better host for the source. Cheers, Bob On Fri, Dec 13, 2024, 06:14 B. Watson wrote: > > > On Tue, 10 Dec 2024, B. Watson wrote: > > > I'll take over the build. Even though it's no longer a dependency for > > anything else, it looks like it could be useful. > > I ran out of time this week. I'll take over the xvfb-run build after > this week's update. Sorry for the delay. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Dec 14 01:14:41 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 14 Dec 2024 08:14:41 +0700 Subject: [Slackbuilds-users] Updates - 20241214.1 Message-ID: <8baefda7-06d8-43fd-8fab-6653d529ecd7@slackbuilds.org> Sat Dec 14 01:03:01 UTC 2024 academic/xschem: Update MD5SUM. academic/xschem: Updated for version 3.4.5. academic/xsimd: Version bump to 13.1.0 academic/zotero: Updated for version 7.0.11. audio/mpd: Update for 0.23.16 audio/ncmpc: Updated for version 0.51 audio/qmmp-plugin-pack-qt5: Updated for version 1.7.1. audio/qmmp-qt5: Updated for version 1.7.2. audio/rakarrack: Updated for version 0.6.2+20150813_a620840. desktop/mint-themes: Update for 2.2.1 desktop/xmouseless: Update script. development/arduino-cli: Updated for version 1.1.1 development/aws-cdk: Updated for version 2.172.0. development/aws-cdk: Updated for version 2.173.0. development/composer: Updated for version 2.8.4 development/diffoscope: updated for version 284 development/golangci-lint: Added (Fast linters runner for Go). development/hugo: Updated for version 0.139.4. development/jdk23: Added (Java Development Kit). development/mongodb-compass: Updated for version 1.45.0. development/pgmodeler: Call qmake6 instead of qmake-qt6. development/protobuf3: Updated for version 29.1. development/rust-opt: Updated for version 1.83.0. development/sbcl: Updated for version 2.4.11 development/scite: Updated for version 5.5.3. development/terraform-ls: Updated for version 0.36.2. development/terraform: Updated for version 1.10.2 development/vscode: Updated for version 1.96.0. games/cowsay: Updated for version 3.8.4. games/ddnet: Updated for version 18.8 games/protonup: Version bump to 0.1.5 games/puNES: Call qmake6 instead of qmake-qt6. git/ci: Update CI dependencies. graphics/blender: Version bump to 4.3.1 graphics/kuickshow: Updated for version 20241006_93b7e35. graphics/vuescan: Updated MD5SUM_x86_64. ham/sdrangel: Updated for version 7.22.5. ham/sdrpp: Updated for version 20241212.b9145872. ham/sgp4: Updated for version 20241212.147b1ae7. libraries/dcmtk: Updated for version 3.6.9 libraries/gnatcoll-core: Added (GNAT Core Packages). libraries/libjxl: Updated for version 0.11.1. libraries/libmediainfo: Version bump to 24.12 libraries/qt6gtk2: Call qmake6 instead of qmake-qt6. libraries/xapp: Updated for version 2.8.7 misc/bitwarden-desktop: Updated for version 2024.12.0. misc/tarotplane: Updated for version 2.01. multimedia/QMPlay2: Updated for version 24.12.06. multimedia/mediainfo: Version bump to 24.12 multimedia/plexmediaserver: Updated for version 1.41.3.9292_bc7397402. network/AdGuardHome: Updated for version 0.107.55. network/brave-browser: Updated for version 1.73.101. network/discord: Version bump to 0.0.77 network/dropbox: Updated for version 213.4.4597. network/elinks: Fix for new lua. network/gem: Update script. network/gemget: Added (Command Line Downloader). network/haproxy: Updated for version 3.0.7. network/signal-desktop: Updated for version 7.36.0. network/spf-engine: Added (SPF Backend). network/tailscale: Updated for version 1.78.1. network/teamviewer: Updated for version 15.60.3. network/vivaldi: Updated for version 7.0.3495.23. network/yt-dlp-bin: Added (download videos from youtube). network/yt-dlp: Updated for version 2024.12.06. network/zmap: Updated for version 4.3.1. office/pandoc-bin: update 3.6 office/sent: Update script. office/smoffice2024: Fix permission. office/smoffice2024: Updated for version 2024_1222 perl/perl-Date-Manip: Updated for version 6.96. perl/perl-Test-Inter: Updated for version 1.12. python/jellyfish: Updated for version 1.1.2. python/python3-debugpy: Updated for version 1.8.11. python/python3-dep-logic: Version bump to 0.4.10 python/python3-identify: Updated for version 2.6.3. python/python3-loguru: Updated for version 0.7.3. python/python3-maturin: Updated for version 1.7.8. python/python3-pdm-build-locked: Version bump to 0.3.4 python/python3-pdm: Correct virtualenv dep to python3 ver python/python3-pdm: Version bump to 2.21.0 python/python3-pdm: Version bump to 2.22.0 python/python3-pydantic: Updated for version 2.10.3. python/python3-types-python-dateutil: Update for 2.9.0.20241206 python/python3-virtualenv: Version bump to 20.28.0 python/tinycss2: Update for 1.4.0 ruby/ruby-build: Updated for version 20241213. system/B-em: Updated for version 20241202_4036483 system/FreeFileSync: Updated for version 13.9 system/Iosevka-aile: Updated for version 32.2.1. system/Iosevka-etoile: Updated for version 32.2.1. system/Iosevka-slab: Updated for version 32.2.0 system/Iosevka: Updated for version 32.2.0 system/dget: Updated for version 2.24.6. system/docker-buildx: Updated for version 0.19.2. system/doublecmd-qt5: New maintainer system/etckeeper: Updated for version 1.18.22. system/incus: Upgraded for version 6.8 system/kiwix-tools-bin: Update script. system/mongodb: Updated for version 8.0.4. system/nvidia-driver: Updated for version 565.77. system/nvidia-kernel: Updated for version 565.77. system/openzfs: updated for version 2.2.7 system/partclone: Updated for version 0.3.32 system/postgresql15: Added (Object-relational DBMS). system/postgresql15: Fix some mismatch names. system/rasdaemon: Updated for version 0.8.2 system/sarasa-gothic: Updated for version 1.0.25. system/sbokeeper: Added (SlackBuild package manager helper). system/systraq: Updated for version 0.4. system/tarsnap: Updated for version 1.0.40. system/telegraf: Updated for version 1.33.0 system/timeshift: Updated for version 24.06.5 system/xen-nox: Updated for version 4.19.0. system/yq: Updated for version 4.44.6. +--------------------------+ -- 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: From isaacyu at protonmail.com Sat Dec 14 21:38:18 2024 From: isaacyu at protonmail.com (Isaac Yu) Date: Sat, 14 Dec 2024 21:38:18 +0000 Subject: [Slackbuilds-users] I will no longer maintain and update SlackBuilds after this week Message-ID: Hi everyone, This is the last week in which I am maintaining SlackBuilds (i.e. I will no longer maintain SlackBuilds after Dec 20). I have 200+ SlackBuilds to maintain. If you recall, I previously abandoned my SlackBuilds last year in June (and then went back to maintenance last December). My SlackBuilds are available at: https://github.com/isaackwy/slackbuilds-15.0 I plan on switching to Linux Mint Debian. It's just like vanilla Debian except with a better preinstalled desktop experience. - Isaac -------------- next part -------------- An HTML attachment was scrubbed... URL: From belka at caraus.de Sat Dec 14 22:36:26 2024 From: belka at caraus.de (Eugen Wissner) Date: Sat, 14 Dec 2024 23:36:26 +0100 Subject: [Slackbuilds-users] I will no longer maintain and update SlackBuilds after this week In-Reply-To: References: Message-ID: I could take ttf-nerd-fonts-symbols and jq. On Sat Dec 14, 2024 at 10:38 PM CET, Isaac Yu via SlackBuilds-users wrote: > Hi everyone, > > This is the last week in which I am maintaining SlackBuilds (i.e. I will no longer maintain SlackBuilds after Dec 20). > I have 200+ SlackBuilds to maintain. > If you recall, I previously abandoned my SlackBuilds last year in June (and then went back to maintenance last December). > > My SlackBuilds are available at: > https://github.com/isaackwy/slackbuilds-15.0 > > I plan on switching to Linux Mint Debian. > It's just like vanilla Debian except with a better preinstalled desktop experience. > - Isaac From didier at slint.fr Sat Dec 14 22:57:35 2024 From: didier at slint.fr (Didier Spaier) Date: Sat, 14 Dec 2024 23:57:35 +0100 Subject: [Slackbuilds-users] I will no longer maintain and update SlackBuilds after this week In-Reply-To: References: Message-ID: <1666d081-af6d-4ce8-8b51-68e866e027c6@slint.fr> On 14/12/2024 22:38, Isaac Yu via SlackBuilds-users wrote: > My SlackBuilds are available at: > https://github.com/isaackwy/slackbuilds-15.0 slackbuilds-15.0> This includes scripts for LXQt 1.3.0. Incidentally, Frank Honolka (lancsuk @ LQ) provides scripts for LXQt 1.4.0 and and 2.1.0: https://codeberg.org/snuk/lxqt1-snuk-15.0 https://codeberg.org/snuk/lxqt2-snuk-15.0 For folks who can live wihout KDE, see the READMEs ;) FYI other DEs are available in https://codeberg.org/snuk/ Cheers, Didier From jebrhansen+SBo at gmail.com Sun Dec 15 01:41:56 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 14 Dec 2024 17:41:56 -0800 Subject: [Slackbuilds-users] I will no longer maintain and update SlackBuilds after this week In-Reply-To: References: Message-ID: Thanks for all your efforts over the years. I can take the following simply because they're dependencies of programs I'm already maintaining. However, if someone else wants, I'm happy to let them maintain them... I just don't want them to go unsupported. development/abseil-cpp python/python2-BeautifulSoup4 python/python2-soupsieve python/python3-anyio python/python3-pexpect python/python3-pythran python/python3-pytz python/python3-sniffio python/python3-tomlkit I may come back later and take the following, if no one else is interested. piper & libratbag (and python3-evdev since it's a dep) seem interesting enough, even if I don't have a gaming mouse right now. However, these are currently fair game if others are interested. python/python3-evdev system/libratbag system/piper Jeremy On Sat, Dec 14, 2024 at 1:38?PM Isaac Yu via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hi everyone, > > This is the last week in which I am maintaining SlackBuilds (i.e. I will > no longer maintain SlackBuilds after Dec 20). > I have 200+ SlackBuilds to maintain. > If you recall, I previously abandoned my SlackBuilds last year in June > (and then went back to maintenance last December). > > My SlackBuilds are available at: > https://github.com/isaackwy/slackbuilds-15.0 > > I plan on switching to Linux Mint Debian. > It's just like vanilla Debian except with a better preinstalled desktop > experience. > > - Isaac > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at smallbone.se Sun Dec 15 07:43:32 2024 From: nick at smallbone.se (Nick Smallbone) Date: Sun, 15 Dec 2024 08:43:32 +0100 Subject: [Slackbuilds-users] I will no longer maintain and update SlackBuilds after this week In-Reply-To: References: Message-ID: I can take office/pdftk. Nick On Saturday 14 December, 2024 at 09:38 pm, Isaac Yu via SlackBuilds-users wrote: > Hi everyone, > > This is the last week in which I am maintaining SlackBuilds (i.e. I will no longer maintain SlackBuilds after Dec 20). > I have 200+ SlackBuilds to maintain. > If you recall, I previously abandoned my SlackBuilds last year in June (and then went back to maintenance last December). > > My SlackBuilds are available at: > https://github.com/isaackwy/slackbuilds-15.0 > > I plan on switching to Linux Mint Debian. > It's just like vanilla Debian except with a better preinstalled desktop experience. > - Isaac From r1w1s1 at disroot.org Sun Dec 15 16:20:30 2024 From: r1w1s1 at disroot.org (r1w1s1) Date: Sun, 15 Dec 2024 13:20:30 -0300 Subject: [Slackbuilds-users] I will no longer maintain and update SlackBuilds after this week In-Reply-To: References: Message-ID: On Sun Dec 15, 2024 at 4:43 AM -03, Nick Smallbone wrote: > I can take office/pdftk. > > Nick > > On Saturday 14 December, 2024 at 09:38 pm, Isaac Yu via SlackBuilds-users wrote: > > Hi everyone, > > > > This is the last week in which I am maintaining SlackBuilds (i.e. I will no longer maintain SlackBuilds after Dec 20). > > I have 200+ SlackBuilds to maintain. > > If you recall, I previously abandoned my SlackBuilds last year in June (and then went back to maintenance last December). > > > > My SlackBuilds are available at: > > https://github.com/isaackwy/slackbuilds-15.0 > > > > I plan on switching to Linux Mint Debian. > > It's just like vanilla Debian except with a better preinstalled desktop experience. > > - Isaac > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ I can take Other/System/jq Other/System/nnn -- r1w1s1 From tonus1 at free.fr Sun Dec 15 16:51:46 2024 From: tonus1 at free.fr (Tonus) Date: Sun, 15 Dec 2024 17:51:46 +0100 Subject: [Slackbuilds-users] I will no longer maintain and update SlackBuilds after this week In-Reply-To: References: Message-ID: On Sat, Dec 14, 2024 at 05:41:56PM GMT, Jeremy Hansen wrote: ... >python/python3-pytz ... >I may come back later and take the following, if no one else is interested. ... > >Jeremy Hi Jeremy, I could take this one as I have a few SlackBuilds relying on it : python3-icalendar calcure khal todoman taskw Let me know, and I will submit the change via git. -- Regards, Tonus From sbolokanov at abv.bg Sun Dec 15 17:03:00 2024 From: sbolokanov at abv.bg (=?utf-8?B?0KEuINCR0L7Qu9C+0LrQsNC90LDRgNGK?=) Date: Sun, 15 Dec 2024 19:03:00 +0200 (EET) Subject: [Slackbuilds-users] I will no longer maintain and update SlackBuilds after this week In-Reply-To: References: Message-ID: <224998275.503824.1734282180710@nm52.abv.bg> I will take over: cdemu-client cdemu-daemon libmirage vhba-module -- ?. ?. ?????????? >-------- ?????????? ????? -------- >??: Isaac Yu via SlackBuilds-users slackbuilds-users at slackbuilds.org >???????: [Slackbuilds-users] I will no longer maintain and update SlackBuilds after this week >??: "slackbuilds-users at slackbuilds.org" >????????? ??: 14.12.2024 23:38 Hi everyone, This is the last week in which I am maintaining SlackBuilds (i.e. I will no longer maintain SlackBuilds after Dec 20). I have 200+ SlackBuilds to maintain. If you recall, I previously abandoned my SlackBuilds last year in June (and then went back to maintenance last December). My SlackBuilds are available at: https://github.com/isaackwy/slackbuilds-15.0 I plan on switching to Linux Mint Debian. It's just like vanilla Debian except with a better preinstalled desktop experience. - Isaac -------------- next part -------------- An HTML attachment was scrubbed... URL: From sbolokanov at abv.bg Sun Dec 15 17:09:51 2024 From: sbolokanov at abv.bg (=?utf-8?B?0KEuINCR0L7Qu9C+0LrQsNC90LDRgNGK?=) Date: Sun, 15 Dec 2024 19:09:51 +0200 (EET) Subject: [Slackbuilds-users] I will no longer maintain and update SlackBuilds after this week In-Reply-To: <224998275.503824.1734282180710@nm52.abv.bg> References: <224998275.503824.1734282180710@nm52.abv.bg> Message-ID: <1354830454.504078.1734282591073@nm52.abv.bg> Also gcdemu and image-analyzer -- ?. ?. ?????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From slack at giand.it Sun Dec 15 21:38:08 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Sun, 15 Dec 2024 22:38:08 +0100 Subject: [Slackbuilds-users] I will no longer maintain and update SlackBuilds after this week In-Reply-To: References: Message-ID: <693f9f19-56d1-4f2c-8c50-f4cbd5ffdaba@giand.it> Il 14/12/24 22:38, Isaac Yu via SlackBuilds-users ha scritto: > Hi everyone, > > This is the last week in which I am maintaining SlackBuilds (i.e. I > will no longer maintain SlackBuilds after Dec 20). > I have 200+ SlackBuilds to maintain. > If you recall, I previously abandoned my SlackBuilds last year in June > (and then went back to maintenance last December). > > My SlackBuilds are available at: > https://github.com/isaackwy/slackbuilds-15.0 > > I plan on switching to Linux Mint Debian. > It's just like vanilla Debian except with a better preinstalled > desktop experience. > > - Isaac We lose a resource! Thanks for what you have done so far, Isaac, and best wishes for your new course. If anyone is interested I could take libspatialindex, since it is a dependency required by qgis. Next time I'll look for other slackbuilds that I don't know from Gis category if they remain orphanized > > _______________________________________________ > 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/ > -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Dec 21 00:20:23 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 21 Dec 2024 07:20:23 +0700 Subject: [Slackbuilds-users] Updates - 20241221.1 Message-ID: Sat Dec 21 00:11:49 UTC 2024 academic/FreeFem: Updated for version 4.15. academic/openboard: Updated for version 1.7.3. academic/plus42: Updated for version 1.1.15 audio/rakarrack: Fix download URL. audio/tuxguitar: Updated for version 1.6.5 desktop/jgmenu: Updated for version 4.5.0. desktop/mint-themes: Update for 2.2.2 desktop/mint-y-icons: Update for 1.8.0 development/aws-cdk: Updated for version 2.173.1. development/aws-cdk: Updated for version 2.173.2. development/dotnet-sdk-9.0: Updated for version 9.0.101. development/electron: Update for 33.3.0 development/jupyter-nbclient: Update for 0.10.2 development/lua-language-server: Updated for version 3.13.5. development/mold: Updated for version 2.35.1. development/pahole: Updated for version 1.28. development/pgmodeler: Source qt6 profile. development/php82: Updated for version 8.2.27 development/postman: Updated for version 11.23.1 development/protobuf3: Updated for version 29.2. development/qb64pe: Updated for version 4.0.0 development/rider: Updated for version 2024.3.2. development/rstudio-desktop: Update for 2024.12.0+467 development/spyder: Edit README development/vscode-bin: Updated for version 1.96.2. development/xmake: Updated for version 2.9.7. development/xnedit: Updated for version 1.6.0. games/mame: Updated for version 0.272. git/ci: Update CI dependencies. graphics/blender: Fix script exiting for unsupported arches graphics/blender: Version bump to 4.3.2 graphics/drawio: Updated for version 25.0.2. graphics/vuescan: Updated for version 9.8.41. libraries/aqbanking: Updated for version 6.6.0. libraries/dav1d: Version bump to 1.5.0 libraries/gnatcoll-bindings: Added (GNAT Bindings). libraries/gnatcoll-db: Added (GNAT Database packages). libraries/gwenhywfar: Updated for version 5.12.0. libraries/libcec: Version bump to 6.0.2 libraries/libcurl-gnutls: Updated for version 8.11.1. libraries/libotr: Fix build. libraries/onevpl: Version bump to 2.13.0 libraries/onevpl: Version bump to 2.14.0 libraries/qt6gtk2: Source qt6 profile. libraries/webkit2gtk4.1: Remove unneeded patch. libraries/webkit2gtk4.1: Updated for version 2.46.5. libraries/webkit2gtk: Remove unneeded patch. libraries/webkit2gtk: Updated for version 2.46.5. misc/jmri: Updated for version 5.10. multimedia/plexmediaserver: Updated for version 1.41.3.9314_a0bfb8370. network/aerc: Updated for version 0.18.2. network/coturn: Updated for version 4.6.3. network/discord: Version bump to 0.0.78 network/dropbox: Updated for version 214.4.5217. network/gallery-dl: Updated for version 1.28.2. network/librewolf: Updated for version 133.0.3 network/microsoft-edge: Updated for version 131.0.2903.99. network/opera: Updated for version 115.0.5322.109. network/vivaldi: Updated for version 7.0.3495.26. network/whalebird: Updated for version 6.1.8 network/yt-dlp-bin: Updated for version 2024.12.13. network/zoom-linux: Updated for version 6.3.0.5527 office/libreoffice-helppack: Updated for version 24.8.4. office/libreoffice-langpack: Updated for version 24.8.4. office/libreoffice: Updated for version 24.8.4. perl/MoarVM: Updated for version 2024.12 perl/nqp: Updated for version 2024.12 perl/perl-Capture-Tiny: Updated for version 0.50. perl/perl-Digest-SHA-PurePerl: Added (Perl SHA). perl/perl-Getopt-Long-Descriptive: Added (another Getopt library). perl/perl-Git-Sub: Added (Git from Perl). perl/perl-Net-SSH: Added (SSH Wrapper). perl/perl-Sub-Name: Updated for version 0.28. perl/perl-System-Command: Added (perl System Command). perl/perl-System-Sub: Added (perl module). perl/perl-UUID: Added (UUID library). perl/rakudo: Update rakudo.info perl/rakudo: Updated for version 2024.12 perl/zef: Updated for version 0.22.6 python/python3-asttokens: Updated for version 3.0.0. python/python3-hatchling: Updated for version 1.27.0. python/python3-json-logger: Update for 3.2.1 python/python3-lsp-server: Edit README python/python3-meson-opt: Updated for version 1.6.1. python/python3-pdm: Version bump to 2.22.1 python/python3-rope: Update for 1.1.1 python/python3-smart_open: Update for 7.1.0 system/FontAwesome: Update for 6.7.2 system/apache-tomcat: Updated for version 10.1.34. system/docker-compose: Updated for version 2.32.0 system/epson-inkjet-printer-escpr2: Updated for version 1.2.23. system/kitty: Updated for version 0.38.0 system/limine: Updated for version 8.6.0 system/lynis: Updated for version 3.1.3. system/memtester: Use working DOWNLOAD. system/nerdctl: Updated for version 2.0.2 system/oksh: Updated for version 7.6. system/postgresql15: Update README. system/postgresql16: Added (Object-relational DBMS). system/postgresql: Update README. system/sbokeeper: Updated for version 2.00. system/sbotools: Install the new man pages. system/sbotools: Updated for version 3.2. system/sbotools: Updated for version 3.2.1. system/tio: Updated for version 3.8 system/ttf-nerd-fonts-symbols: New maintainer system/xvfb-run: New maintainer, new source. +--------------------------+ -- 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: From fsleg at t-rg.ws Sat Dec 21 16:50:16 2024 From: fsleg at t-rg.ws (fsLeg) Date: Sat, 21 Dec 2024 19:50:16 +0300 Subject: [Slackbuilds-users] Rust program packaging woes Message-ID: <1463d0ec-0876-419c-8d2f-6d2a7637b95d@t-rg.ws> Hello. I've been maintaining a few SlackBuilds for myself in a private repo for quite a while. And recently I started thinking about submitting them officially here. But before I do that, I want to clarify a few things about packaging Rust programs, since I have a SlackBuild for one. 1. What is the policy with crates? The guidelines say that SlackBuilds must be usable offline, which would imply that crates should be specified in .info file. And the majority of Rust programs on SBo do just that. But there are a few packages, namely network/electrs, network/noip-duc and graphics/veles, which don't do that for some reason, and electrs doesn't even mention requiring internet access. Then there are audio/yabridge and python/python3-maturin which just use pre-bundled vendor/ directory uploaded to some place. IIRC such behavior is normally frowned upon. So is there a single standard for SlackBuilds of Rust programs? Or I can just use regular `cargo build` without bothering with vendoring of crates? I looked up a lot of information on that topic, and general consensus seems to be to stick to Cargo for everything, even vendoring, which would imply that fetching a tarball with vendor/ directory should be preferred. 2. What is the policy with additional scripts? I wrote a python script to vendor all crates. Can I use it? Do I bundle it alongside the SlackBuild to call when needed or do I embed it using here-document? There's nothing about including custom tools in a SlackBuild submission, which would mean it's allowed if necessary. I know that basically all SlackBuilds for Rust programs use a sub-shell with some voodoo inside, and at first I did too when I just switched to offline building. But I thought that looked way too dirty and hacky, and I prefer to understand what is happening. I understood a general idea, in fact it's what helped me to write my own script, but not what was happening with all those excessive regexps. I also tried to rewrite that chunk of magic in Shell in a more readable way, and I succeeded, but that code was way too slow (~3m20s for a program with 454 crates vs ~13s using a Python script or that black magic snippet). BTW, python/python3-maturin actually includes such a helper script, although it's not referenced anywhere and it requires another package to be installed first. 3. A more broad question. What is the purpose of including a program's SlackBuild into /usr/doc? Is it transparency about how a particular package was built as well as who's responsible for deciding how to build it? Or is it so users could rebuild a package themselves? But in this case some SlackBuilds aren't usable as there's no additional files that the SlackBuild might use, like patches or custom scripts, including helper scripts. Do I also need to put my helper script in /usr/doc? The SlackBuild in question: https://github.com/fsLeg/SlackBuilds/tree/master/shadowsocks-rust I also wrote a tool to help maintain SlackBuilds for Rust programs: https://gist.github.com/fsLeg/2f33cccbce9f3ae6af1a3f720f201cb0 It needs some more love, but it mostly works. With it you can get a list of crates' links, get a list of crates' links with their MD5 hashes, add those to DOWNLOAD and MD5SUM variables of .info file respectively and finally vendor pre-downloaded crates to test the building process. From urchlay at slackware.uk Sat Dec 21 21:51:49 2024 From: urchlay at slackware.uk (B. Watson) Date: Sat, 21 Dec 2024 16:51:49 -0500 (EST) Subject: [Slackbuilds-users] Rust program packaging woes In-Reply-To: <1463d0ec-0876-419c-8d2f-6d2a7637b95d@t-rg.ws> References: <1463d0ec-0876-419c-8d2f-6d2a7637b95d@t-rg.ws> Message-ID: <23ee1a36-e8e9-8637-4640-8c7f515c80d0@slackware.uk> On Sat, 21 Dec 2024, fsLeg wrote: > 1. What is the policy with crates? The guidelines say that SlackBuilds must > be usable offline, which would imply that crates should be specified in .info > file. And the majority of Rust programs on SBo do just that. > > But there are a few packages, namely network/electrs, network/noip-duc and > graphics/veles, which don't do that for some reason, and electrs doesn't even > mention requiring internet access. The ones that require 'net access during the build are "grandfathered in". We're not accepting new builds that need network access. If electrs doesn't mention it in the README, that's a bug. Thanks for pointing it out. > Then there are audio/yabridge and python/python3-maturin which just use > pre-bundled vendor/ directory uploaded to some place. IIRC such behavior is > normally frowned upon. Frowned upon by whom? I'm a SBo admin, and I don't frown on it. In fact I do the same thing whenever I have to: host the source myself, if there's some reason the original source URL(s) won't do. The only build I ever maintained that uses rust was libopenraw, and I used to use a self-hosted vendor/ tarball. In the later versions, upstream now includes all the rust sources in their release tarballs, so I don't have to do that any more. TBH, I don't like dealing with .info files with hundreds of crates, so I generally just don't package up anything written in rust. libopenraw is a corner case: when I took over as maintainer, it was originally pure C++. At some point, it got some Rust added to it (but still is primarily C++). > So is there a single standard for SlackBuilds of Rust programs? Or I can just > use regular `cargo build` without bothering with vendoring of crates? I > looked up a lot of information on that topic, and general consensus seems to > be to stick to Cargo for everything, even vendoring, which would imply that > fetching a tarball with vendor/ directory should be preferred. A tarball of vendor/ is preferred because it's the simplest way to do it, assuming you have a place to host it. If you don't, someone on this mailing list will probably volunteer to host it for you, or maybe give you write access to the sourceforge sbodirectlinks account (not sure who's in charge of that). > 2. What is the policy with additional scripts? I wrote a python script to > vendor all crates. Can I use it? Do I bundle it alongside the SlackBuild to > call when needed or do I embed it using here-document? There's nothing about > including custom tools in a SlackBuild submission, which would mean it's > allowed if necessary. Definitely allowed. A lot of existing scripts include helper scripts. No need for a here-doc. Just include it as a separate file, and run it from $CWD in the script. If at all possible (and it generally is), please ship the script non-executable, mode 0644, and run it from within the SlackBuild with e.g. "sh $CWD/helper.sh" or "python3 $CWD/helper.py" (whatever interpreter's needed). You don't want to depend on execute permission in $CWD, because our tarball-creation process might remove the +x bits. Writing to $CWD, even just "chmod +x $CWD/script.py", is forbidden. A few builds may break this rule, but it's still a rule. I'm actually working on a "maintainer FAQ" that includes this kind of information. It's one of those never-ending projects... your questions will go in there. > I know that basically all SlackBuilds for Rust programs use a sub-shell with > some voodoo inside, and at first I did too when I just switched to offline > building. But I thought that looked way too dirty and hacky, and I prefer to > understand what is happening. I understood a general idea, in fact it's what > helped me to write my own script, but not what was happening with all those > excessive regexps. I also tried to rewrite that chunk of magic in Shell in a > more readable way, and I succeeded, but that code was way too slow (~3m20s > for a program with 454 crates vs ~13s using a Python script or that black > magic snippet). So you've got a python script that works and is more readable, maintainable than the shell script other builds use? Definitely include it in your build, and possibly it'll end up being mentioned in a (hypothetical so far) rust template. > 3. A more broad question. What is the purpose of including a program's > SlackBuild into /usr/doc? Is it transparency about how a particular package > was built as well as who's responsible for deciding how to build it? Or is it > so users could rebuild a package themselves? But in this case some > SlackBuilds aren't usable as there's no additional files that the SlackBuild > might use, like patches or custom scripts, including helper scripts. Do I > also need to put my helper script in /usr/doc? So far as I know, the SlackBuild is included for reference purposes. There's no expectation of being able to run it, since any other files (even the slack-desc) aren't present in /usr/doc. Any helper scripts you write, you don't have to include in the package. See games/mame, there's a mkgroovy.sh script that I run when it's time to update mame, but it doesn't go in the installable package. > The SlackBuild in question: > https://github.com/fsLeg/SlackBuilds/tree/master/shadowsocks-rust > > I also wrote a tool to help maintain SlackBuilds for Rust programs: > https://gist.github.com/fsLeg/2f33cccbce9f3ae6af1a3f720f201cb0 It needs some > more love, but it mostly works. With it you can get a list of crates' links, > get a list of crates' links with their MD5 hashes, add those to DOWNLOAD and > MD5SUM variables of .info file respectively and finally vendor pre-downloaded > crates to test the building process. > _______________________________________________ > 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 fourtysixandtwo at sliderr.net Sat Dec 21 23:55:25 2024 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sat, 21 Dec 2024 16:55:25 -0700 Subject: [Slackbuilds-users] Rust program packaging woes In-Reply-To: <1463d0ec-0876-419c-8d2f-6d2a7637b95d@t-rg.ws> References: <1463d0ec-0876-419c-8d2f-6d2a7637b95d@t-rg.ws> Message-ID: Mr. Watson has already answered most of your questions so I will just add my reasons for vendoring with my rust slackbuilds. There are a couple of bash scripts around to do what your python script does but I'm not a fan of doing it that way. First of all, it is very slow checking all those hashes and when you do a lot of build testing, that is very annoying. Second, if one does not use cargo-vendor-filterer to create the list it includes a lot of useless crates for windows or other architectures we don't support which increases the download size by quite a bit. So for me, vendoring along with using cargo-vendor-filterer makes a lot more sense. The only problem is hosting those vendored sources somewhere that people trust. Note that I will eventually be creating a separate slackbuild for the cargo-mkvendored.sh script I include with cargo-vendor-filterer as the latter is included in -current. Cheers From willysr at slackbuilds.org Sun Dec 22 01:46:23 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 22 Dec 2024 08:46:23 +0700 Subject: [Slackbuilds-users] Rust program packaging woes In-Reply-To: <1463d0ec-0876-419c-8d2f-6d2a7637b95d@t-rg.ws> References: <1463d0ec-0876-419c-8d2f-6d2a7637b95d@t-rg.ws> Message-ID: > 1. What is the policy with crates? The guidelines say that SlackBuilds > must be usable offline, which would imply that crates should be > specified in .info file. And the majority of Rust programs on SBo do > just that. Although our ideal prefered way is to have an offline build capability, sometimes it's not how upstream and certain projects works, like golang or nodejs-based scripts definitely need network access since they need to download the modules on the fly, so it's reviewed case-by-case -- 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: From willysr at slackbuilds.org Sun Dec 22 01:56:34 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 22 Dec 2024 08:56:34 +0700 Subject: [Slackbuilds-users] Notice: Early Public Update Message-ID: <28431d74-496d-4f5e-82f9-90d2714e6276@slackbuilds.org> Hi everyone Due to traveling schedule, i may end up pushing the last public update in 2024 this week a day earlier than the normal schedule, so please make sure to submit your changes early instead of waiting for last minutes to gives us time to review your changes. -- 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: From fsleg at t-rg.ws Sun Dec 22 09:03:15 2024 From: fsleg at t-rg.ws (fsLeg) Date: Sun, 22 Dec 2024 12:03:15 +0300 Subject: [Slackbuilds-users] Rust program packaging woes In-Reply-To: <23ee1a36-e8e9-8637-4640-8c7f515c80d0@slackware.uk> References: <1463d0ec-0876-419c-8d2f-6d2a7637b95d@t-rg.ws> <23ee1a36-e8e9-8637-4640-8c7f515c80d0@slackware.uk> Message-ID: <3f6451dc-5aed-4d2a-b7e5-13759238d3b8@t-rg.ws> On 22.12.2024 00:51, B. Watson wrote: > Frowned upon by whom? I'm a SBo admin, and I don't frown on it. In > fact I do the same thing whenever I have to: host the source myself, > if there's some reason the original source URL(s) won't do. Ah. I just remembered that I read somewhere about not liking hosting sources. I now found where I read it: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2024-July/029497.html Turned out it was someone's single opinion. > A tarball of vendor/ is preferred because it's the simplest way to > do it, assuming you have a place to host it. If you don't, someone on > this mailing list will probably volunteer to host it for you, or maybe > give you write access to the sourceforge sbodirectlinks account (not > sure who's in charge of that). I do have a server, although since it's a private one I'm only concerned with it running when I need it, so there's occasional performance degradation or downtime when I perform maintenance tasks (overloaded Slackware server), also it might take time for me to discover when my server isn't available for some reason. But it's been working for many years with only short hiccups due to upstream issues. > So you've got a python script that works and is more readable, > maintainable than the shell script other builds use? Definitely > include it in your build, and possibly it'll end up being mentioned in > a (hypothetical so far) rust template. Well, it's still a spaghetti code since I'm doing manually what is supposed to be done automatically by Rust's toolchain, but there's less voodoo happening, and I explained what vendoring function does in the source, I can also include comments for every step if it'll be helpful. I also forgot to ask, do I need to provide a license for my helper script in the same way we do for SlackBuilds? From fsleg at t-rg.ws Sun Dec 22 09:25:19 2024 From: fsleg at t-rg.ws (fsLeg) Date: Sun, 22 Dec 2024 12:25:19 +0300 Subject: [Slackbuilds-users] Rust program packaging woes In-Reply-To: References: <1463d0ec-0876-419c-8d2f-6d2a7637b95d@t-rg.ws> Message-ID: <7b65fd15-3793-4353-94b0-db5cf665b4f1@t-rg.ws> On 22.12.2024 02:55, fourtysixandtwo wrote: > First of all, it > is very slow checking all those hashes and when you do a lot of build > testing, that is very annoying. I found that it's actually not that slow and might be a code issue. Like I said, my Shell script takes over three minutes while Python and Lockywolf's (I found the author) magic snippet is done in seconds, and that's to untar 454 crates and hash 26000+ files inside. If you're just going to check crates' checksums it shouldn't take more than a second or two to check the downloaded crates against their MD5. There's not that many Rust packages on SBo for that to be an issue. As I was writing that paragraph I slowly realized you were talking about the building process, not just source checking. Yeah, that would add up quickly. Although Shadowsocks-rust currently seems to be the program with the largest amount of required crates, so it should be faster for everything else. > Second, if one does not use > cargo-vendor-filterer to create the list it includes a lot of useless > crates for windows or other architectures we don't support which > increases the download size by quite a bit. I've been trying to do that manually for, like, two weeks. It turned out some crates have a hard dependency on Windows-specific crates, so Cargo was refusing to build my package unless I vendored all crates specified in Cargo.lock. Stupid, I know, but it is what it is. Maybe it's better for other programs. I also just tried cargo-vendor-filterer. Yeah, the number of crates in my case stayed the same, 454. > Note that I will eventually be creating a separate slackbuild for the > cargo-mkvendored.sh script I include with cargo-vendor-filterer as the > latter is included in -current. I think a script like that should be included alongside the templates, maybe inside a directory with some helper scripts, as it's mostly usable for packagers and is not actually used in the building process. Also a SlackBuild for a single script feels like an overkill.