From sbo at linuxgalaxy.org Wed Nov 1 18:43:34 2023 From: sbo at linuxgalaxy.org (KB_SBo) Date: Wed, 01 Nov 2023 18:43:34 +0000 Subject: [Slackbuilds-users] libgme homepage is no longer bitbucket Message-ID: <81b23baf-4f0d-4baf-9c6e-57dd3c872fbb@linuxgalaxy.org> FYI: Upstream migrated to github: ??THIS REPOSITORY HAS BEEN MIGRATED TO GitHub!?? This repository is de-facto abandoned and may contain outdated information. Repository has been moved to a new place here: https://github.com/libgme/game-music-emu -kb From slack at giand.it Wed Nov 1 20:31:54 2023 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Wed, 1 Nov 2023 21:31:54 +0100 Subject: [Slackbuilds-users] Has the saga-gis update been rejected? Message-ID: Hi, this morning I've uploaded the saga-gis update for a new version, but I don't see it in pending or approved lists. If it has been rejected I didn't received any report, so I don't know about problems: the tests with sbolint and sbopkglint didn't find errors. Can you help me? thanks Giancarlo -- ********************************************************* Giancarlo Dess? https://www.giand.it Slackware Linux... because it works! ********************************************************* From willysr at slackbuilds.org Thu Nov 2 05:57:09 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 2 Nov 2023 12:57:09 +0700 Subject: [Slackbuilds-users] Has the saga-gis update been rejected? In-Reply-To: References: Message-ID: <50b039a2-49ad-4f01-9bb7-6b0d97265f79@slackbuilds.org> > Hi, this morning I've uploaded the saga-gis update for a new version, > but I don't see it in pending or approved lists. If it has been rejected > I didn't received any report, so I don't know about problems: the tests > with sbolint and sbopkglint didn't find errors. Can you help me? it's being tested in our CI platform on github https://github.com/SlackBuildsOrg/slackbuilds/pull/3524 -- Willy Sudiarto Raharjo From slack at giand.it Thu Nov 2 10:45:26 2023 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Thu, 2 Nov 2023 11:45:26 +0100 Subject: [Slackbuilds-users] Has the saga-gis update been rejected? In-Reply-To: <50b039a2-49ad-4f01-9bb7-6b0d97265f79@slackbuilds.org> References: <50b039a2-49ad-4f01-9bb7-6b0d97265f79@slackbuilds.org> Message-ID: Il 02/11/23 06:57, Willy Sudiarto Raharjo ha scritto: >> Hi, this morning I've uploaded the saga-gis update for a new version, >> but I don't see it in pending or approved lists. If it has been >> rejected I didn't received any report, so I don't know about >> problems: the tests with sbolint and sbopkglint didn't find errors. >> Can you help me? > > it's being tested in our CI platform on github > https://github.com/SlackBuildsOrg/slackbuilds/pull/3524 > > Thanks, Willy I ignore several things about new approach of submissions! -- ********************************************************* Giancarlo Dess? https://www.giand.it Slackware Linux... because it works! ********************************************************* From milgram at cgpp.com Thu Nov 2 12:01:59 2023 From: milgram at cgpp.com (J. Milgram) Date: Thu, 2 Nov 2023 08:01:59 -0400 Subject: [Slackbuilds-users] SU2 handoff Message-ID: <47cecffa-26b3-417f-b7ec-aa075ea9111b@cgpp.com> All (especially Admins): Not sure whom I should notify, so I'll do it here: I've handed off SU2 to William PC Thank you William! regards Judah Milgram From marav8 at free.fr Fri Nov 3 12:18:34 2023 From: marav8 at free.fr (marav) Date: Fri, 3 Nov 2023 13:18:34 +0100 Subject: [Slackbuilds-users] Tuxpaint: homepage URL Message-ID: Hi Tim, The homepage of Tuxpaint is not : https://www.tuxpaint.org but https://tuxpaint.org Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Nov 3 14:43:53 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 3 Nov 2023 21:43:53 +0700 Subject: [Slackbuilds-users] Tuxpaint: homepage URL In-Reply-To: References: Message-ID: <53188001-02ce-4a1d-9275-6e8c411b9040@slackbuilds.org> > The homepage of Tuxpaint is not : > > https://www.tuxpaint.org > > but > > https://tuxpaint.org Fixed on my branch -- 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 rshepard at appl-ecosys.com Fri Nov 3 15:45:37 2023 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 3 Nov 2023 08:45:37 -0700 (PDT) Subject: [Slackbuilds-users] wmwebcam: window size Message-ID: <782cf98f-1460-9235-69b2-5bddb2d8622@appl-ecosys.com> I'm using a 24" monitor. The default wmwebcam window size is 352x288 px. It's a tiny square that displays one of my eyes and that's about all that fits in there. I modified customize.patch by setting the width to 800 and the height to 600, rebuilt, and reinstalled. The display window is the same size. The customize.patch file notes that non-default sizes require changes to the source; I assume that's done automatically. Apparently not. Please advise me how to adjust the wmwebcam window for use on a 24" (or 21") monitor. TIA, Rich From dickson.tim at googlemail.com Sat Nov 4 07:59:44 2023 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sat, 4 Nov 2023 07:59:44 +0000 Subject: [Slackbuilds-users] Tuxpaint: homepage URL In-Reply-To: <53188001-02ce-4a1d-9275-6e8c411b9040@slackbuilds.org> References: <53188001-02ce-4a1d-9275-6e8c411b9040@slackbuilds.org> Message-ID: thanks for the report and fix. I'll report the issue upstream, as it used to be ok. regards, Tim On 03/11/2023 14:43, Willy Sudiarto Raharjo wrote: >> The homepage of Tuxpaint is not : >> >> https://www.tuxpaint.org >> >> but >> >> https://tuxpaint.org > > Fixed on my branch > > > _______________________________________________ > 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 Sat Nov 4 09:58:26 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Nov 2023 16:58:26 +0700 Subject: [Slackbuilds-users] Updates - 20231104.1 Message-ID: <26f90c0d-67d2-439f-9126-be87a15b85a2@slackbuilds.org> Sat Nov 4 09:42:22 UTC 2023 academic/fet: Updated for version 6.11.1. academic/gaiasky: Updated for version 3.5.6. academic/gwyddion: Updated for version 2.64. academic/root: Updated for v6.28.08 audio/eawpats: Download URL changed; fix. audio/qpwgraph: Updated for version 0.5.3 desktop/nwg-shell: Updated for version 0.5.18 desktop/papirus-icon-theme: Updated for version 20231101 desktop/pidgin-guifications: Download URL changed; fix. development/OpenCobolIDE: Removed (unmaintained). development/cargo-c: Added (cargo c-abi helpers). development/dpkg: Updated for version 1.22.1. development/github-cli: Updated for version 2.38.0 development/hugo: update 0.120.3 development/kotlin: Updated for version 1.9.20. development/poedit: Updated for version 3.4.1. development/rstudio-desktop: Updated for version 2023.09.1+494. development/universal-ctags: Updated for version p6.0.20231029.0 development/valgrind: Updated for version 3.22.0. games/FlightGear-data: Updated for version 2020.3.19. games/FlightGear: Updated for version 2020.3.19. games/mame: Updated for version 0.260. games/yar: Download URL changed; fix. gis/SFCGAL: Updated for version 1.5.0. gis/eccodes: Updated for version 2.32.1. gis/gdal: Updated for version 3.7.3. gis/saga-gis: Updated for version 9.2.0. graphics/OpenSubdiv: Fixes for glfw3, tbb graphics/amide: Added (Medical Imaging Data Examiner). graphics/pygifme: Removed (unmaintained). graphics/tuxpaint-stamps: Fix HOMEPAGE. graphics/tuxpaint: Fix HOMEPAGE. graphics/viewnior: Fix for -current. graphics/vuescan: Updated for version 9.8.20. graphics/yed: Updated for version 3.23.2. libraries/SimGear: Updated for version 2020.3.19. libraries/botocore: Updated for version 1.31.76. libraries/gssdp: Updated for version 1.6.3. libraries/gupnp: Updated for version 1.6.6. libraries/libgme: Update HOMEPAGE. libraries/libheif: Updated for version 1.17.3. libraries/libsoup3: Updated for version 3.4.4. libraries/tbb: Updated for version 2021.10.0. misc/bitwarden-desktop: Updated for version 2023.10.0. misc/open-simh: Updated for version b23cde9. multimedia/Mopidy: Updated for version 3.4.2. multimedia/QMPlay2: Updated for version 23.10.22. multimedia/haruna: Updated for version 0.12.2 multimedia/inputstream.adaptive: Version bump to 20.3.14 multimedia/ivtv-utils: Download URL changed; fix. multimedia/plexmediaserver: Updated for version 1.32.7.7621_871adbd44. multimedia/rav1e: Added (AV1 encoder). multimedia/rav1e: Fix libdir on 32bit. network/Free-Cinema: Removed (unused anywhere else). network/asciinema: Updated for version 2.4.0. network/awscli: Updated for version 1.29.76. network/brave-browser: update 1.60.110 network/discord: Version bump to 0.0.33 network/gui-ufw: Updated for version 24.04.0 network/librewolf: Updated for version 119.0 network/libteam: Updated for version 1.32 network/linksys-tftp: Download URL changed; fix. network/newsboat: Updated for version 2.33. network/opensm: Updated for version 3.3.24. network/qbittorrent: Updated for version 4.6.0. network/signal-desktop: Updated for version 6.37.0. network/slack: Updated for version 4.35.121. network/teamviewer: Updated for version 15.47.3. network/telegram: Updated for version 4.11.0. network/telegram: Updated for version 4.11.1. network/telegram: Updated for version 4.11.3. network/tor-browser: Updated for version 13.0.1. network/vcspull: Updated for version 1.23.0. network/vivaldi: Updated for version 6.4.3160.41. network/yoda: Removed (unmaintained). network/yt-dlp: Updated for version 2023.10.13. network/zeek: Updated for version 6.0.2. network/zoom-linux: Updated for version 5.16.6.382 office/JabRef: Updated for version 5.11. office/homebank: Updated for version 5.7.1. office/pandoc-bin: update 3.1.9 perl/perl-Test-Harness: Updated for version 3.48. python/argcomplete: Removed (use python3-argcomplete). python/asgiref: Updated for version 3.7.2. python/certbot-dns-cloudflare: Updated for version 2.7.4 python/cloudpickle: Updated for version 3.0.0. python/python3-asttokens: Updated for version 2.4.1. python/python3-cloudflare: Updated for version 2.12.4 python/python3-django: Updated for version 4.2.7. python/python3-identify: Updated for version 2.5.31. python/python3-jsonlines: Updated for version 4.0.0 python/python3-libvcs: Added (python module). python/python3-stack_data: Switch dep to new python3 package ruby/ruby-build: Updated for version 20231025. system/B-em: Updated for version ac1baae. system/FreeFileSync: Updated for version 13.1. system/Iosevka-aile: Updated for version 27.3.3. system/Iosevka-etoile: Updated for version 27.3.3. system/UEFITool: Added (firmware images viewer). system/barman: Updated for version 3.9.0. system/btrbk: Updated for version 0.32.6. system/chronograf: Updated for version 1.10.2 system/edk2-aarch64: Added (aarch64 UEFI firmware for Qemu). system/epson-inkjet-printer-escpr2: Updated for version 1.2.9. system/fastfetch: Updated for version 2.2.0. system/fd: Updated for version 8.7.1. system/fonts-kannada-extra: Added (system fonts). system/fonts-tamil-tva: Added (system fonts) system/fwupd: Updated for version 1.9.7. system/kapacitor: Updated for version 1.7.1 system/letsencrypt: Updated for version 2.7.3. system/letsencrypt: Updated for version 2.7.4. system/limine: Updated for version 5.20231029.0. system/locust: Updated for version 2.18.0. system/netdata: Updated for version 1.43.1. system/netdata: Updated for version 1.43.2. system/openrazer-daemon: Updated for version 3.7.0. system/openrazer-kernel: Updated for version 3.7.0. system/osquery-bin: Updated for version 5.10.2. system/patool: Updated for version 1.15.0. system/restic: Updated for version 0.16.2 system/sarasa-gothic: Updated for version 0.42.4. system/slackrepo-hints: Updated for version 20231104. system/telegraf: Updated for version 1.28.3 system/wine-staging: Updated for version 8.19. +--------------------------+ -- 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 rshepard at appl-ecosys.com Sat Nov 4 12:43:45 2023 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 4 Nov 2023 05:43:45 -0700 (PDT) Subject: [Slackbuilds-users] wmwebcam: window size [RESOLVED] In-Reply-To: <782cf98f-1460-9235-69b2-5bddb2d8622@appl-ecosys.com> References: <782cf98f-1460-9235-69b2-5bddb2d8622@appl-ecosys.com> Message-ID: <7de699e5-5ad5-e96e-fca0-566c11b81a5@appl-ecosys.com> On Fri, 3 Nov 2023, Rich Shepard wrote: > Please advise me how to adjust the wmwebcam window for use on a 24" (or > 21") monitor. Please ignore this request. I built webcam instead and it works better than wmwebcam did. Rich From willysr at slackbuilds.org Sat Nov 4 17:02:56 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 5 Nov 2023 00:02:56 +0700 Subject: [Slackbuilds-users] Updates - 20231104.1 In-Reply-To: <26f90c0d-67d2-439f-9126-be87a15b85a2@slackbuilds.org> References: <26f90c0d-67d2-439f-9126-be87a15b85a2@slackbuilds.org> Message-ID: > system/letsencrypt: Updated for version 2.7.4. For those using letsencrypt, i missed 1 new dep on this cycle, which is python-importlib_metadata please make sure to install that one new script and it's dependency (python-zipp) in order to make letsencrypt/certbot script works again. -- 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 zsd+slackbuilds at jdvb.ca Sat Nov 4 20:31:20 2023 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Sat, 4 Nov 2023 17:31:20 -0300 Subject: [Slackbuilds-users] libheif / cargo-c compiling problem Message-ID: Using Slackware64 15.0... After today's updates, I tried to sboupgrade libheif, and the first thing sboupgrade wanted to do was to build cargo-c. After downloading many files, it unpacks cargo-c and then whines thusly: ... cargo-c-0.9.27/src/config.rs cargo-c-0.9.27/src/install.rs cargo-c-0.9.27/src/lib.rs cargo-c-0.9.27/src/pkg_config_gen.rs cargo-c-0.9.27/src/target.rs tar: /usr/sbo/repo/development/cargo-c/addr2line-0.19.0.crate: Cannot open: No such file or directory tar: Error is not recoverable: exiting now Failure encountered while building cargo-c: cargo-c.SlackBuild return non-zero Do you want to proceed? [n] Failures: cargo-c: cargo-c.SlackBuild return non-zero Perhaps there is something peculiar on my system, but before I go on the hunt, can anyone in slackbuild land tell me whether their 64-bit 15.0 system is happy about compiling libheif? Thanks. Jim From alik at ejik.org Sat Nov 4 21:10:05 2023 From: alik at ejik.org (Alexander Verbovetsky) Date: Sun, 5 Nov 2023 00:10:05 +0300 Subject: [Slackbuilds-users] libheif / cargo-c compiling problem In-Reply-To: References: Message-ID: On Sat, Nov 04, 2023 at 05:31:20PM -0300, Jim wrote: > Using Slackware64 15.0... > > After today's updates, I tried to sboupgrade libheif, and the first thing > sboupgrade wanted to do was to build cargo-c. After downloading many > files, it unpacks cargo-c and then whines thusly: > > ... > cargo-c-0.9.27/src/config.rs > cargo-c-0.9.27/src/install.rs > cargo-c-0.9.27/src/lib.rs > cargo-c-0.9.27/src/pkg_config_gen.rs > cargo-c-0.9.27/src/target.rs > tar: /usr/sbo/repo/development/cargo-c/addr2line-0.19.0.crate: Cannot open: No such file or directory > tar: Error is not recoverable: exiting now > Failure encountered while building cargo-c: > cargo-c.SlackBuild return non-zero > > Do you want to proceed? [n] > Failures: > cargo-c: cargo-c.SlackBuild return non-zero > > > Perhaps there is something peculiar on my system, but before I go on the > hunt, can anyone in slackbuild land tell me whether their 64-bit 15.0 > system is happy about compiling libheif? libheif has several new dependencies, one of them is rav1e, which in turn depends on cargo-c. Both are Rust packages and require rust16 during the build. I have successfully tested everything on a clean 64-bit version of 15.0. It's strange that cargo-c wants addr2line, it's not its dependency. rav1e requires addr2line. Best regards, Alexander From willysr at slackbuilds.org Sun Nov 5 02:06:44 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 5 Nov 2023 09:06:44 +0700 Subject: [Slackbuilds-users] libheif / cargo-c compiling problem In-Reply-To: References: Message-ID: <028dfb94-b7b1-42d8-946c-33732020c17b@slackbuilds.org> > Using Slackware64 15.0... > > After today's updates, I tried to sboupgrade libheif, and the first thing > sboupgrade wanted to do was to build cargo-c. After downloading many > files, it unpacks cargo-c and then whines thusly: > > ... > cargo-c-0.9.27/src/config.rs > cargo-c-0.9.27/src/install.rs > cargo-c-0.9.27/src/lib.rs > cargo-c-0.9.27/src/pkg_config_gen.rs > cargo-c-0.9.27/src/target.rs > tar: /usr/sbo/repo/development/cargo-c/addr2line-0.19.0.crate: Cannot open: No such file or directory > tar: Error is not recoverable: exiting now > Failure encountered while building cargo-c: > cargo-c.SlackBuild return non-zero > > Do you want to proceed? [n] > Failures: > cargo-c: cargo-c.SlackBuild return non-zero > > > Perhaps there is something peculiar on my system, but before I go on the > hunt, can anyone in slackbuild land tell me whether their 64-bit 15.0 > system is happy about compiling libheif? Yes, we tested this on our CI engine and it works with latest stable 15.0 https://github.com/SlackBuildsOrg/slackbuilds/pull/3563 this is cargo-c https://github.com/SlackBuildsOrg/slackbuilds/pull/3569 this is rav1e https://github.com/SlackBuildsOrg/slackbuilds/pull/3565 -- 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 zsd+slackbuilds at jdvb.ca Mon Nov 6 14:41:21 2023 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Mon, 6 Nov 2023 10:41:21 -0400 Subject: [Slackbuilds-users] libheif / cargo-c compiling problem In-Reply-To: References: Message-ID: (sorry about the last non-reply) Alexander and Willy, thanks for your replies. I tried it inside a S64-15.0 vbox VM, but got the same complaint. Presumably I have done the same Bad Thing inside the VM as I have in my bare-iron installation. I guess I have a project for a rainy day... :-( Jim On Sun, Nov 5, 2023 at 00:10 (+0300), Alexander Verbovetsky wrote: > On Sat, Nov 04, 2023 at 05:31:20PM -0300, Jim wrote: >> Using Slackware64 15.0... >> After today's updates, I tried to sboupgrade libheif, and the first thing >> sboupgrade wanted to do was to build cargo-c. After downloading many >> files, it unpacks cargo-c and then whines thusly: >> ... >> cargo-c-0.9.27/src/config.rs >> cargo-c-0.9.27/src/install.rs >> cargo-c-0.9.27/src/lib.rs >> cargo-c-0.9.27/src/pkg_config_gen.rs >> cargo-c-0.9.27/src/target.rs >> tar: /usr/sbo/repo/development/cargo-c/addr2line-0.19.0.crate: Cannot open: No such file or directory >> tar: Error is not recoverable: exiting now >> Failure encountered while building cargo-c: >> cargo-c.SlackBuild return non-zero >> Do you want to proceed? [n] >> Failures: >> cargo-c: cargo-c.SlackBuild return non-zero >> Perhaps there is something peculiar on my system, but before I go on the >> hunt, can anyone in slackbuild land tell me whether their 64-bit 15.0 >> system is happy about compiling libheif? > libheif has several new dependencies, one of them is rav1e, which in > turn depends on cargo-c. Both are Rust packages and require rust16 > during the build. > I have successfully tested everything on a clean 64-bit version of 15.0. > It's strange that cargo-c wants addr2line, it's not its dependency. > rav1e requires addr2line. > Best regards, > Alexander > _______________________________________________ > 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 zsd+slackbuilds at jdvb.ca Mon Nov 6 14:38:34 2023 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Mon, 6 Nov 2023 10:38:34 -0400 Subject: [Slackbuilds-users] libheif / cargo-c compiling problem In-Reply-To: References: Message-ID: Alexander and (in another replt) On Sun, Nov 5, 2023 at 00:10 (+0300), Alexander Verbovetsky wrote: > On Sat, Nov 04, 2023 at 05:31:20PM -0300, Jim wrote: >> Using Slackware64 15.0... >> After today's updates, I tried to sboupgrade libheif, and the first thing >> sboupgrade wanted to do was to build cargo-c. After downloading many >> files, it unpacks cargo-c and then whines thusly: >> ... >> cargo-c-0.9.27/src/config.rs >> cargo-c-0.9.27/src/install.rs >> cargo-c-0.9.27/src/lib.rs >> cargo-c-0.9.27/src/pkg_config_gen.rs >> cargo-c-0.9.27/src/target.rs >> tar: /usr/sbo/repo/development/cargo-c/addr2line-0.19.0.crate: Cannot open: No such file or directory >> tar: Error is not recoverable: exiting now >> Failure encountered while building cargo-c: >> cargo-c.SlackBuild return non-zero >> Do you want to proceed? [n] >> Failures: >> cargo-c: cargo-c.SlackBuild return non-zero >> Perhaps there is something peculiar on my system, but before I go on the >> hunt, can anyone in slackbuild land tell me whether their 64-bit 15.0 >> system is happy about compiling libheif? > libheif has several new dependencies, one of them is rav1e, which in > turn depends on cargo-c. Both are Rust packages and require rust16 > during the build. > I have successfully tested everything on a clean 64-bit version of 15.0. > It's strange that cargo-c wants addr2line, it's not its dependency. > rav1e requires addr2line. > Best regards, > Alexander > _______________________________________________ > 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 Sat Nov 11 01:20:39 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Nov 2023 08:20:39 +0700 Subject: [Slackbuilds-users] Updates - 20231111.1 Message-ID: <62725f34-b032-455b-a8ed-0dd914f24c74@slackbuilds.org> Sat Nov 11 01:09:27 UTC 2023 academic/avogadroapp: Update README. academic/avogadrolibs: Update README. academic/bowtie2: upgrade to version 2.5.2 academic/flexbar: incl. patches for newer tbb academic/gaiasky: Updated for version 3.5.7. academic/nco: Updated for version 5.1.9. academic/spqr: Disable tbb integration audio/mididings: REQUIRES update desktop/NsCDE: Updated for version 2.3. desktop/anki: REQUIRES update desktop/nwg-drawer: Updated for version 0.4.0. desktop/nwg-shell-config: Updated for version 0.5.23. desktop/nwg-shell: Updated for version 0.5.19. desktop/rss-guard: Updated for version 4.5.3. development/SQLAlchemy: Updated for version 1.4.50. development/astyle: Updated for version 3.4.10. development/codespell: Updated for version 2.2.6. development/henplus: Updated HOMEPAGE. development/jupyter-nbconvert: REQUIRES update development/lua-language-server: Updated for version 3.7.2. development/mold: Updated for version 2.3.2. development/postman: Updated for version 10.20.0 development/sbcl: Updated for version 2.3.10 development/tea: updated for version 62.1.1 development/textadept: updated for version 12.2 development/uftrace: Updated for version 20231105_567648d development/universal-ctags: Updated for version p6.0.20231105.0 development/vscode-bin: Updated for version 1.84.0. development/xmake: Updated for version 2.8.5. games/ags: Updated for version 3.6.0.53. games/freeciv: updated for version 3.0.9 games/warzone2100: updated for version 4.4.0 gis/OWSLib: Updated for version 0.29.3. gis/python3-netcdf4-python: Updated for version 1.6.5. gis/qgis: Updated for version 3.34.0. graphics/OpenSubdiv: Update for latest tbb graphics/brlcad: updated for version 7.38.0 graphics/vuescan: Updated for version 9.8.21. ham/qlog: Updated for version 0.29.1. misc/bitwarden-desktop: Updated for version 2023.10.1. multimedia/get_iplayer: Updated for version 3.34. multimedia/iptvnator: Updated for version 0.15.0. network/armcord: Updated for version 3.2.5. network/badwolf: Updated for version 1.3.0. network/cinny-desktop: Added (matrix client). network/element-desktop: Updated for version 1.11.48. network/emailrelay: Updated HOMEPAGE. network/feather: Updated for version 2.5.2. network/filezilla: Updated for version 3.66.1. network/firewalld: REQUIRES update network/flexget: Updated for version 3.9.17. network/gallery-dl: Updated for version 1.26.2. network/grpcurl: Added (curl for gRPC servers). network/gtorrentviewer: New maintainer, fix segfaults. network/mailman: build fix network/protonmail-bridge: Updated for version 3.6.1. network/qutebrowser-bin: Updated OpenSSL bundled library. network/signal-desktop: Updated for version 6.38.0. network/slack: Updated for version 4.35.126. network/tdlib: Added (Telegram Database library). network/telegram: Updated for version 4.11.6. network/telegram: updated for version 4.11.5. network/uwsgi: Updated for version 2.0.23. network/vcspull: Fix DEP. network/vivaldi: Updated for version 6.4.3160.42. network/zxing-cpp: Added (barcode image processing library). office/pdfarranger: upgrade to version 1.10.1 office/smoffice2024: Added (office suite). office/t-prot: Updated HOMEPAGE. office/wps-office: Updated for version 11.1.0.11708.XA. perl/MoarVM: Updated for version 2023.10 perl/nqp: Updated for version 2023.10 perl/rakudo: Updated for version 2023.10 perl/zef: Updated for version 0.20.0 python/Kallithea: REQUIRES update python/apprise: REQUIRES update python/bleach: Removed, replaced by python3-bleach python/constantly: Removed (use python3-constantly) python/decorator: Removed, replaced by python3-decorator python/hg-git: updated for version 1.0.3 python/ipython: REQUIRES update python/josepy: Updated for version 1.14.0. python/odoo: REQUIRES update python/python-gssapi: REQUIRES update python/python3-Flask-Login: Updated for version 0.6.3. python/python3-WTForms: Updated for version 3.1.1. python/python3-amqp: Updated for version 5.2.0. python/python3-autobahn: REQUIRES update python/python3-billiard: Updated for version 4.2.0. python/python3-bleach: Added (whitelist-based HTML-sanitizing tool). python/python3-blinker: Updated for version 1.7.0. python/python3-celery: updated for version 5.3.5 python/python3-constantly: Added (Symbolic constants in Python). python/python3-decorator: Added (python decorator). python/python3-dogpile.cache: REQUIRES update python/python3-formencode: Updated for version 2.1.0. python/python3-httpcore: Updated for version 1.0.1. python/python3-hyperlink: Added (A featureful, correct URL for Python). python/python3-incremental: Added (Python projects versioning). python/python3-jaraco.functools: Updated for version 4.0.0. python/python3-kombu: Updated for version 5.3.3. python/python3-obspy: REQUIRES update python/python3-orjson: Updated for version 3.9.10. python/python3-pdfCropMargins: Update script. python/python3-poetry-core: Updated for version 1.8.1. python/python3-prompt_toolkit: updated for version 3.0.40 python/python3-pydantic-core: Updated for version 2.13.0. python/python3-setuptools-rust-opt: Updated for version 1.8.1. python/python3-trove-classifiers: Updated for version 2023.11.7. python/python3-twisted: Updated for version 23.10.0. python/python3-wcwidth: Updated for version 0.2.9. python/python3-wheel: Updated for version 0.41.3. python/readme_renderer: REQUIRES update python/sqlalchemy-migrate: REQUIRES update ruby/ruby-build: Updated for version 20231107. system/Iosevka-aile: Updated for version 27.3.4. system/Iosevka-etoile: Updated for version 27.3.4. system/aespipe: Updated for version 2.4g. system/backintime: Updated for version 1.4.1. system/bleachbit: Updated for version 4.6.0. system/blueprint-compiler: Added (A markup language for GTK). system/fastfetch: Updated for version 2.2.1. system/letsencrypt: Update DEPS. system/razergenie: Updated for version 1.1.0. system/redis: Updated for version 7.2.3. system/sarasa-gothic: Updated for version 0.42.5. system/slackrepo-hints: Updated for version 20231111. system/slackrepo: Updated for version 20231111. +--------------------------+ -- 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 slack at giand.it Sun Nov 12 10:40:43 2023 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Sun, 12 Nov 2023 11:40:43 +0100 Subject: [Slackbuilds-users] Conflicts and/or redundancies of slackbuilds of some python packages (constantly, incremental, hyperlink) Message-ID: Hi, recent update includes three new slackbuilds of python packages supported by Python 3, but these are reduntant with other available slackbuilds or may cause conflicts between different versions of the same module: 1) redundancies python3-incremental: this builds and installs incremental for Python 3, but in the repository there is also the slackbuild incremental that builds and installs for both Python 2 and Python 3. Both slackbuilds build the same source. Also python3-hyperlink (supporting Python 3) conflicts with hyperlink (supporting both Python 2 and Python 3) These redundancies should cause issues in the package management because two different packages share the same files in Python 3 2) conflicts python3- constantly builds constantly-23.10.4 for Python 3, but there is also the slackbuild constantly, that builds and installs constantly-15.1.0 for Python 2 and Python 3. This should cause conflicts because in Python 3 could exist two different versions of the same module How to solve? -- ********************************************************* Giancarlo Dess? https://www.giand.it Slackware Linux... because it works! ********************************************************* From willysr at slackbuilds.org Sun Nov 12 10:42:57 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 12 Nov 2023 17:42:57 +0700 Subject: [Slackbuilds-users] Conflicts and/or redundancies of slackbuilds of some python packages (constantly, incremental, hyperlink) In-Reply-To: References: Message-ID: <3279e056-a6e5-40e8-b89b-ead41c5463b8@slackbuilds.org> > Hi, recent update includes three new slackbuilds of python packages > supported by Python 3, but these are reduntant with other available > slackbuilds or may cause conflicts between different versions of the > same module: > > 1) redundancies > > python3-incremental: this builds and installs incremental for Python 3, > but in the repository there is also the slackbuild incremental that > builds and installs for both Python 2 and Python 3. Both slackbuilds > build the same source. > > Also python3-hyperlink (supporting Python 3) conflicts with hyperlink > (supporting both Python 2 and Python 3) > > These redundancies should cause issues in the package management because > two different packages share the same files in Python 3 > > 2) conflicts > > python3- constantly builds constantly-23.10.4 for Python 3, but there is > also the slackbuild constantly, that builds and installs > constantly-15.1.0 for Python 2 and Python 3. This should cause conflicts > because in Python 3 could exist two different versions of the same module those packages were added in last cycle to provide python3-packages only i think the plan was to remove python2-packages but we need to have python3-packages first in the repo before we can remove the old one. -- 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 arnaud.garcia-fernandez at laposte.net Sun Nov 12 10:48:03 2023 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Sun, 12 Nov 2023 10:48:03 +0000 Subject: [Slackbuilds-users] Conflicts and/or redundancies of slackbuilds of some python packages (constantly, incremental, hyperlink) In-Reply-To: References: Message-ID: <1901B338-A725-4BBC-8FAB-BCF4187A84F8@laposte.net> hyperlink, bleach, constantly and incremental are being renamed to python3-package. In the last update, the new packages have been added, the old ones removed, and all relevant REQUIRES updated. Only two of them were still building for python2, and packages requiring them are python3 only, which justifies dropping python2 support. So everything should be good. - Yth. Le 12 novembre 2023 10:40:43 UTC, "Giancarlo Dess?" a ?crit?: >Hi, recent update includes three new slackbuilds of python packages supported by Python 3, but these are reduntant with other available slackbuilds or may cause conflicts between different versions of the same module: > >1) redundancies > >python3-incremental: this builds and installs incremental for Python 3, but in the repository there is also the slackbuild incremental that builds and installs for both Python 2 and Python 3. Both slackbuilds build the same source. > >Also python3-hyperlink (supporting Python 3) conflicts with hyperlink (supporting both Python 2 and Python 3) > >These redundancies should cause issues in the package management because two different packages share the same files in Python 3 > >2) conflicts > >python3- constantly builds constantly-23.10.4 for Python 3, but there is also the slackbuild constantly, that builds and installs constantly-15.1.0 for Python 2 and Python 3. This should cause conflicts because in Python 3 could exist two different versions of the same module > >How to solve? > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From slack at giand.it Sun Nov 12 11:14:09 2023 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Sun, 12 Nov 2023 12:14:09 +0100 Subject: [Slackbuilds-users] Conflicts and/or redundancies of slackbuilds of some python packages (constantly, incremental, hyperlink) In-Reply-To: <3279e056-a6e5-40e8-b89b-ead41c5463b8@slackbuilds.org> References: <3279e056-a6e5-40e8-b89b-ead41c5463b8@slackbuilds.org> Message-ID: <3013d84c-910c-4fd8-b20f-dfea896017d0@giand.it> Il 12/11/23 11:42, Willy Sudiarto Raharjo ha scritto: > but we need to have python3-packages first in the repo before we can > remove the old one. > Now it's all clear, sorry :-) -- ********************************************************* Giancarlo Dess? https://www.giand.it Slackware Linux... because it works! ********************************************************* From phalange at komputermatrix.com Thu Nov 16 00:53:52 2023 From: phalange at komputermatrix.com (phalange at komputermatrix.com) Date: Wed, 15 Nov 2023 19:53:52 -0500 Subject: [Slackbuilds-users] Microsoft Edge is up for grabs Message-ID: <8234b2522e528fbeb01fdf59e2520aba@komputermatrix.com> I'm still not able to get recent versions of Edge to run. I have neither the desire nor the expertise to fool with it any longer. The version on SBo is working but stale. -AP From fellype at gmail.com Fri Nov 17 18:10:15 2023 From: fellype at gmail.com (Fellype) Date: Fri, 17 Nov 2023 15:10:15 -0300 Subject: [Slackbuilds-users] petsc.SlackBuild - removal request Message-ID: Dear SBo admins, I would like to request the removal of petsc.SlackBuild from SBo. Such script was added to the SBo repo as a FreeFEM dependency in version 4.11. However, I changed it for FreeFEM v. 4.12. Thus, petsc is not required anymore. In addition, there is a problem with the installation of petsc on 64-bit Slackware systems, as you can see in the attached messages. I'm unable to solve it because the source config files do not have a "libdir" option (nor anything similar to it) and my sed/grep/gawk/etc skills are much far from the level required to solve it (I've asked how to do it in the petsc mailing list, but no solution was indicated). If anyone is interested in maintaining petsc, feel free to take over maintenance. Regards, Fellype ---------- Forwarded message --------- De: William PC Date: s?b., 3 de dez. de 2022 ?s 11:56 Subject: Re: [Slackbuilds-users] petsc To: SlackBuilds.org Users List Hi Fellype, I saw your attchment, but doesn't handle the installation at 64-bit systems. That is why it has some lines moving the files, because it's a requirement that slackbuilds install libraries at lib64 at 64bit systems. Nonetheless both approaches doesn't solve the issue. I would recommend you to fix the slackbuilds with some solution to update files that are pointing to lib, you can use sed for that. Besides shall be good to include at the configure process the libjpeg that is included at slackware stock installation and doesn't need any dependency. Cheers William ------------------------------ *From:* SlackBuilds-users on behalf of Fellype *Sent:* Saturday, December 3, 2022 5:52 AM *To:* SlackBuilds.org Users List *Subject:* Re: [Slackbuilds-users] petsc Hi William, Thank you for checking the petsc package and for noticing the problem. This script was not supposed to have those lines copying things from /lib to /lib64. I remember that I noticed the problem and re-submitted the script in the correct form (see attached slackbuild). This means that I tested the script/software at some point! And yes, all the packages submitted to SBo are checked. And the current policy is really strict. @SBo Admins I guess that there is a problem in the SlackBuilds.org submission system. I say that because I'm sure that I submitted the modified (and correct) buildscript without the issue pointed out by William. This is not the first time this has happened. But I don't remember when it was the previous. Best regards, Fellype Em sex., 2 de dez. de 2022 ?s 22:42, William PC escreveu: I checked the SlackBuild file and saw that it just move the files from lib to lib64 but there is nothing to fix the files that have relations to the /usr/lib path and it uses a if condition with only one equal signal, is that possible ? Besides the package doesn't even uses the libraries stock at Slackware, such as libjpeg. Neither sets to build the shared libraries. Will ------------------------------ *From:* SlackBuilds-users on behalf of William PC *Sent:* Friday, December 2, 2022 12:56 PM *To:* slackbuilds-users *Subject:* [Slackbuilds-users] petsc The petsc package has several files pointing to wrong locations at 64-bit. I don't know how this package can be used in 64-bit with all this bad paths: /usr/lib/petsc . The maintainer probably had made the SlackBuild without testing the software. Is there a policy to check the package before submit it ? William PC http://www.slack-it.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Nov 18 01:10:58 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 18 Nov 2023 08:10:58 +0700 Subject: [Slackbuilds-users] petsc.SlackBuild - removal request In-Reply-To: References: Message-ID: <4499bd35-6759-484e-aba3-33b0c787b9e6@slackbuilds.org> > I would like to request the removal of petsc.SlackBuild from SBo. > Such script was added to the SBo repo as a FreeFEM dependency in version > 4.11. However, I changed it for FreeFEM v. 4.12. Thus, petsc is not > required anymore. Done -- 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 Nov 18 02:26:52 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 18 Nov 2023 09:26:52 +0700 Subject: [Slackbuilds-users] Updates - 20231118.1 Message-ID: <44407f3a-a8d3-42e8-9541-811faad4d391@slackbuilds.org> Sat Nov 18 02:16:51 UTC 2023 academic/cadabra2: Updated for version 2.4.5. academic/petsc: Removed (requested by maintainer). audio/ocp: Updated for version 0.2.106. desktop/nwg-panel: Updated for version 0.9.17 desktop/nwg-shell-config: Updated for version 0.5.24 desktop/nwg-shell: Updated for version 0.5.22 desktop/todoman: Updated for version 4.4.0. desktop/xfce4-timer-plugin: Updated for version 1.7.2. development/aws-cdk: Added (AWS Cloud Development Kit). development/ghex: Update for 45.1 development/github-cli: Updated for version 2.39.0 development/kakoune: Updated for version 2023.08.05. development/openmodelica: Added (modeling environment). development/pycharm: Updated for version 2023.2.5.232.10227.11. development/vscode-bin: Updated for version 1.84.2. development/vstudio: Updated for version 13.5.1. development/wxFormBuilder: Updated for version 4.0.0. games/PrismLauncher: Updated for version 8.0. games/gltron: Fix DOWNLOAD. games/puzzles: Updated for version 20231115.96d65e8. gis/geos: Updated for version 3.12.1. gis/pdal: Enable support for Draco. gis/qgis: Fix README. graphics/Blender: Mention optional alembic-framework graphics/GraphicsMagick: Updated for version 1.3.42. graphics/alembic-framework: Added (CGI framework). graphics/opentoonz: Added (2D animation software). ham/gridtracker: Updated for version 1.23.1112. haskell/haskell-http: Removed (by request of the maintainer). libraries/QDarkStyle: Updated for version 3.2.1 libraries/hoel: Updated for version 1.4.29. libraries/iddawc: Updated for version 1.1.9. libraries/imlib2: Updated for version 1.12.1. libraries/jbig2dec: Updated for version 0.20. libraries/kaidan: Added (chat app). libraries/kquickimageeditor: Added (Image editing components). libraries/libdraco: Added (3D data compression). libraries/libfido2: Updated for version 1.14.0. libraries/libgusb: Updated for version 0.4.8. libraries/libindi-drivers: Updated for version 2.04 libraries/libindi-libraries: Updated for version 2.04 libraries/libindi: Updated for version 2.04 libraries/opensaml: Updated for version 3.2.1. libraries/pam_usb: Added (hardware authentication). libraries/pymediainfo: Updated for version 6.1.0. libraries/pyte: Updated for version 0.8.2. libraries/qxmpp: Added (xmpp client). libraries/rhonabwy: Updated for version 1.1.13. libraries/superlu: Updated for version 6.0.1. libraries/tinygltf: Added (C++ headers). libraries/tomcat-native: Updated for version 1.2.39. libraries/ulfius: Updated for version 2.7.15. libraries/wxWidgets: Updated for version 3.2.4. libraries/xml-security-c: Updated for version 2.0.4. libraries/xmltooling: Updated for version 3.2.4. libraries/zxing-cpp: Moved to libraries and build offline. multimedia/filebot: Updated for version 5.1.2. multimedia/haruna: Updated for version 0.12.3. multimedia/mkvtoolnix: Updated to 80.0 network/AdGuardHome: Updated for version 0.107.41. network/aria2: Updated for version 1.37.0. network/baikal: Updated for version 0.9.4. network/beegfs: Updated for version 7.4.2. network/discord: Updated for version 0.0.35. network/dropbox: Updated for version 187.4.5691. network/ejabberd: update build script. network/element-desktop: Updated for version 1.11.49. network/exim: Updated for version 4.97. network/flexget: Updated for version 3.9.19. network/glewlwyd: Updated for version 2.7.6. network/go-sendxmpp: Updated for version 0.7.0. network/heimdal: Updated for version 7.8.0. network/keepalived: Updated for version 2.2.8. network/lldpd: Updated for version 1.0.17. network/mod_auth_gssapi: Update script. network/ngrok: Updated for version 3.4.0 network/openconnect: Updated for version 9.12. network/palemoon-bin: updated for version 32.5.0 network/palemoon: updated for version 32.5.0 network/rspamd: Updated for version 3.7.3 network/shibboleth-sp: Updated for version 3.4.1. network/telegram: Updated for version 4.11.7. network/unbound: Updated for version 1.19.0. network/vivaldi: Updated for version 6.4.3160.44. network/weechat: Updated for version 4.1.1. network/wireshark: Updated for version 4.2.0. office/calibre-bin: Updated for version 7.0.0. perl/perl-File-FcntlLock: Added (File locking). perl/perl-Proc-Daemon: Updated for version 0.23. python/Kallithea: Fix dep. python/ipython: Updated for version 8.17.2. python/mypy: Updated for version 1.7.0. python/pipdeptree: Updated for version 2.13.1. python/python-msal: Updated for version 1.25.0. python/python3-executing: Updated for version 2.0.1. python/python3-filelock: Updated for version 3.13.1. python/python3-httpcore: Updated for version 1.0.2. python/python3-kombu: Updated for version 5.3.4. python/python3-maturin: Updated for version 1.3.2. python/python3-pandas: Updated for version 2.1.3. python/python3-pdm: Updated for version 2.10.1. python/python3-pdm: Updated for version 2.10.3. python/python3-platformdirs: Updated for version 4.0.0. python/python3-prompt_toolkit: Updated for version 3.0.41. python/python3-pydantic-core: Updated for version 2.14.3. python/python3-pydantic: Updated for version 2.5.1. python/python3-qbittorrent-api: Add update note to README. python/python3-rich: Updated for version 13.7.0. python/python3-sysrsync: Added (rsync wrapper). python/python3-transaction: Updated for version 4.0. python/python3-trove-classifiers: Updated for version 2023.11.14. python/python3-wcwidth: Updated for version 0.2.10. system/Iosevka-aile: Updated for version 27.3.5. system/Iosevka-etoile: Updated for version 27.3.5. system/Iosevka-slab: Updated for version 27.3.5. system/Iosevka: Updated for version 27.3.5. system/ancient: Added (decompression routines). system/cronie: Updated for version 1.7.0. system/cw: Added (tail cloudwatch logs). system/doublecmd-qt5: Added (open source file manager). system/intel-microcode: Update to version 20231114 system/irqbalance: Update for 1.9.3 system/locust: Updated for version 2.18.3. system/mount-s3: Fix DOWNLOAD. system/nvidia-driver: Updated for version 535.129.03. system/nvidia-kernel: Updated for version 535.129.03. system/nvidia-legacy470-driver: Updated for version 470.223.02. system/nvidia-legacy470-kernel: Updated for version 470.223.02. system/nvidia-open-kernel: Updated for version 535.129.03. system/prometheus: Updated for version 2.48.0. system/pymux: Removed (unmaintained). system/sarasa-gothic: Updated for version 0.42.6. system/thefuck: Added (typo corrector). system/wine-staging: Updated for version 8.20. +--------------------------+ -- 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 zsd+slackbuilds at jdvb.ca Sat Nov 18 14:42:28 2023 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Sat, 18 Nov 2023 10:42:28 -0400 Subject: [Slackbuilds-users] libheif / cargo-c compiling problem In-Reply-To: References: Message-ID: In case anyone else runs into this issue, here is a work-around. On a whim, rather than running sboupgrade libheif which starts by compiling cargo-c, I did sboupgrade cargo-c by itself, and in this case it successfully compiled and built the package. After that I ran 'sboupgrade libheif' and it worked as expected. So now I wonder whether people who successfully upgraded to the latest libheif already had cargo-c installed for some other reason, and thus didn't need to compile it as a dependency of libheif. I also wonder why sboupgrade does something different when building cargo-c directly, as opposed to building it as a dependency of libheif. Jim On Mon, Nov 6, 2023 at 10:41 (-0400), Jim wrote: > Alexander and Willy, > thanks for your replies. > I tried it inside a S64-15.0 vbox VM, but got the same complaint. > Presumably I have done the same Bad Thing inside the VM as I have in my > bare-iron installation. > I guess I have a project for a rainy day... :-( > Jim > On Sun, Nov 5, 2023 at 00:10 (+0300), Alexander Verbovetsky wrote: >> On Sat, Nov 04, 2023 at 05:31:20PM -0300, Jim wrote: >>> Using Slackware64 15.0... >>> After today's updates, I tried to sboupgrade libheif, and the first thing >>> sboupgrade wanted to do was to build cargo-c. After downloading many >>> files, it unpacks cargo-c and then whines thusly: >>> ... >>> cargo-c-0.9.27/src/config.rs >>> cargo-c-0.9.27/src/install.rs >>> cargo-c-0.9.27/src/lib.rs >>> cargo-c-0.9.27/src/pkg_config_gen.rs >>> cargo-c-0.9.27/src/target.rs >>> tar: /usr/sbo/repo/development/cargo-c/addr2line-0.19.0.crate: Cannot open: No such file or directory >>> tar: Error is not recoverable: exiting now >>> Failure encountered while building cargo-c: >>> cargo-c.SlackBuild return non-zero >>> Do you want to proceed? [n] >>> Failures: >>> cargo-c: cargo-c.SlackBuild return non-zero >>> Perhaps there is something peculiar on my system, but before I go on the >>> hunt, can anyone in slackbuild land tell me whether their 64-bit 15.0 >>> system is happy about compiling libheif? >> libheif has several new dependencies, one of them is rav1e, which in >> turn depends on cargo-c. Both are Rust packages and require rust16 >> during the build. >> I have successfully tested everything on a clean 64-bit version of 15.0. >> It's strange that cargo-c wants addr2line, it's not its dependency. >> rav1e requires addr2line. >> Best regards, >> Alexander From alik at ejik.org Sat Nov 18 16:51:27 2023 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 18 Nov 2023 19:51:27 +0300 Subject: [Slackbuilds-users] libheif / cargo-c compiling problem In-Reply-To: References: Message-ID: Hello, > >>> tar: /usr/sbo/repo/development/cargo-c/addr2line-0.19.0.crate: > >>> Cannot open: No such file or directory > >>> tar: Error is not recoverable: exiting now > >>> Failure encountered while building cargo-c: > >>> cargo-c.SlackBuild return non-zero > I also wonder why sboupgrade does something different when building > cargo-c directly, as opposed to building it as a dependency of > libheif. I really don't know how sboupgrade works (I'm a slackrepo user), but I suspect that somehow files Cargo.lock from cargo-c and rav1e are mixed. This explains why cargo-c script asks for addr2line, it is the first item in Cargo.lock for rav1e. Best regards, Alexander On Sat, Nov 18, 2023 at 10:42:28AM -0400, Jim wrote: > In case anyone else runs into this issue, here is a work-around. > > On a whim, rather than running > sboupgrade libheif > which starts by compiling cargo-c, I did > sboupgrade cargo-c > by itself, and in this case it successfully compiled and built the package. > After that I ran 'sboupgrade libheif' and it worked as expected. > > So now I wonder whether people who successfully upgraded to the latest > libheif already had cargo-c installed for some other reason, and thus > didn't need to compile it as a dependency of libheif. > > I also wonder why sboupgrade does something different when building cargo-c > directly, as opposed to building it as a dependency of libheif. > > Jim > > On Mon, Nov 6, 2023 at 10:41 (-0400), Jim wrote: > > > Alexander and Willy, > > > thanks for your replies. > > > I tried it inside a S64-15.0 vbox VM, but got the same complaint. > > Presumably I have done the same Bad Thing inside the VM as I have in my > > bare-iron installation. > > > I guess I have a project for a rainy day... :-( > > > Jim > > > On Sun, Nov 5, 2023 at 00:10 (+0300), Alexander Verbovetsky wrote: > > >> On Sat, Nov 04, 2023 at 05:31:20PM -0300, Jim wrote: > >>> Using Slackware64 15.0... > > >>> After today's updates, I tried to sboupgrade libheif, and the first thing > >>> sboupgrade wanted to do was to build cargo-c. After downloading many > >>> files, it unpacks cargo-c and then whines thusly: > > >>> ... > >>> cargo-c-0.9.27/src/config.rs > >>> cargo-c-0.9.27/src/install.rs > >>> cargo-c-0.9.27/src/lib.rs > >>> cargo-c-0.9.27/src/pkg_config_gen.rs > >>> cargo-c-0.9.27/src/target.rs > >>> tar: /usr/sbo/repo/development/cargo-c/addr2line-0.19.0.crate: Cannot open: No such file or directory > >>> tar: Error is not recoverable: exiting now > >>> Failure encountered while building cargo-c: > >>> cargo-c.SlackBuild return non-zero > > >>> Do you want to proceed? [n] > >>> Failures: > >>> cargo-c: cargo-c.SlackBuild return non-zero > > > >>> Perhaps there is something peculiar on my system, but before I go on the > >>> hunt, can anyone in slackbuild land tell me whether their 64-bit 15.0 > >>> system is happy about compiling libheif? > > >> libheif has several new dependencies, one of them is rav1e, which in > >> turn depends on cargo-c. Both are Rust packages and require rust16 > >> during the build. > > >> I have successfully tested everything on a clean 64-bit version of 15.0. > > >> It's strange that cargo-c wants addr2line, it's not its dependency. > >> rav1e requires addr2line. > > >> Best regards, > >> Alexander > _______________________________________________ > 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 erich.public at protonmail.com Mon Nov 20 17:06:58 2023 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 20 Nov 2023 17:06:58 +0000 Subject: [Slackbuilds-users] Updates - 20231118.1 In-Reply-To: <44407f3a-a8d3-42e8-9541-811faad4d391@slackbuilds.org> References: <44407f3a-a8d3-42e8-9541-811faad4d391@slackbuilds.org> Message-ID: On Friday, November 17th, 2023 at 8:26 PM, Willy Sudiarto Raharjo wrote: > > > Sat Nov 18 02:16:51 UTC 2023 > libraries/wxWidgets: Updated for version 3.2.4. I think this broke the audacity build. Here is my slackrepo hint file for audacity: # cat /var/lib/slackrepo/etr/hintfiles/audacity.hint ADDREQUIRES="jack ladspa_sdk soundtouch twolame vamp-plugin-sdk vst3sdk lilv suil" OPTIONS="MANUAL=yes" And here is a sampling of the build log: /usr/include/wx-3.2/wx/arrstr.h:353:20: error: cannot convert ?const wxArrayString? to ?wxArrayString::const_reference? {aka ?const wxString&?} 353 | push_back(*first); | ~~~~~~~~~^~~~~~~~ /usr/include/wx-3.2/wx/arrstr.h:383:34: note: initializing argument 1 of ?void wxArrayString::push_back(wxArrayString::const_reference)? 383 | void push_back(const_reference v) { Add(v); } | ~~~~~~~~~~~~~~~~^ make[2]: *** [src/CMakeFiles/Audacity.dir/build.make:3033: src/CMakeFiles/Audacity.dir/effects/lv2/LV2Ports.cpp.o] Error 1 make[2]: *** Waiting for unfinished jobs.... and later... /tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/src/prefs/GUIPrefs.cpp: In static member function ?static void GUIPrefs::GetRangeChoices(TranslatableStrings*, wxArrayStringEx*, int*)?: /tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/src/prefs/GUIPrefs.cpp:80:17: error: ambiguous overload for ?operator=? (operand types are ?wxArrayStringEx? and ?const std::initializer_list?) 80 | *pCodes = sCodes; | ^~~~~~ In file included from /tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/libraries/lib-preferences/Prefs.h:44, from /tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/libraries/lib-files/FileNames.h:17, from /tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/src/prefs/../widgets/wxPanelWrapper.h:161, from /tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/src/prefs/PrefsPanel.h:31, from /tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/src/prefs/GUIPrefs.h:18, from /tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/src/prefs/GUIPrefs.cpp:21: /tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/libraries/lib-strings/wxArrayStringEx.h:46:21: note: candidate: ?wxArrayStringEx& wxArrayStringEx::operator=(wxArrayString&&)? 46 | wxArrayStringEx &operator= ( wxArrayString &&other ) | ^~~~~~~~ /tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/libraries/lib-strings/wxArrayStringEx.h:17:7: note: candidate: ?wxArrayStringEx& wxArrayStringEx::operator=(const wxArrayStringEx&)? 17 | class wxArrayStringEx : public wxArrayString | ^~~~~~~~~~~~~~~ /tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/libraries/lib-strings/wxArrayStringEx.h:17:7: note: candidate: ?wxArrayStringEx& wxArrayStringEx::operator=(wxArrayStringEx&&)? make[2]: *** [src/CMakeFiles/Audacity.dir/build.make:3845: src/CMakeFiles/Audacity.dir/prefs/GUIPrefs.cpp.o] Error 1 and finally: make[2]: Leaving directory '/tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/build' make[1]: *** [CMakeFiles/Makefile2:1948: src/CMakeFiles/Audacity.dir/all] Error 2 make[1]: Leaving directory '/tmp/slackrepo/etr/slackrepo.4B686z/build_audacity/audacity-sources-3.2.5/build' make: *** [Makefile:159: all] Error 2 Build time 79 sec, peak load 66.90, peak memory 30331M, peak tmp 858M audio/audacity: audacity.SlackBuild failed (status 2) 16:25:27 Unmounting chroot ... :-( audio/audacity FAILED )-: Looks like upstream has already fixed the issue(s) on the 3.4.x branch (I assume?): https://support.audacityteam.org/additional-resources/changelog/audacity-3.4.2 https://github.com/audacity/audacity/issues/5598 https://github.com/audacity/audacity/pull/5552 Erich From erich.public at protonmail.com Wed Nov 22 14:14:31 2023 From: erich.public at protonmail.com (Erich Ritz) Date: Wed, 22 Nov 2023 14:14:31 +0000 Subject: [Slackbuilds-users] rasdaemon requires perl-DBD-SQLite Message-ID: Hello Julian, rasdaemon requires perl/perl-DBD-SQLite for full functionality. Without perl-DBD-SQlite: # ras-mc-ctl --summary install_driver(SQLite) failed: Can't locate DBD/SQLite.pm in @INC (you may need to install the DBD::SQLite module) (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5) at (eval 7) line 3. Perhaps the DBD::SQLite perl module hasn't been fully installed, or perhaps the capitalisation of 'SQLite' isn't right. Available drivers: DBM, ExampleP, File, Gofer, Mem, Proxy, Sponge, mysql. at /usr/bin/ras-mc-ctl line 1168. With perl-DBD-SQLite: # ras-mc-ctl --summary No Memory errors. No PCIe AER errors. No MCE errors. Erich From slack at giand.it Sat Nov 25 06:17:27 2023 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Sat, 25 Nov 2023 07:17:27 +0100 Subject: [Slackbuilds-users] Updates - 20231118.1 In-Reply-To: References: <44407f3a-a8d3-42e8-9541-811faad4d391@slackbuilds.org> Message-ID: <2fa9ce00-4e8d-4636-80f1-9cea0737b8bb@giand.it> Il 20/11/23 18:06, Erich Ritz via SlackBuilds-users ha scritto: > On Friday, November 17th, 2023 at 8:26 PM, Willy Sudiarto Raharjo wrote: > > >> >> Sat Nov 18 02:16:51 UTC 2023 >> libraries/wxWidgets: Updated for version 3.2.4. > > I think this broke the audacity build. > > Here is my slackrepo hint file for audacity: > > # cat /var/lib/slackrepo/etr/hintfiles/audacity.hint > ADDREQUIRES="jack ladspa_sdk soundtouch twolame vamp-plugin-sdk vst3sdk lilv suil" > OPTIONS="MANUAL=yes" > > And here is a sampling of the build log: > > /usr/include/wx-3.2/wx/arrstr.h:353:20: error: cannot convert ?const wxArrayString? to ?wxArrayString::const_reference? {aka ?const wxString&?} > 353 | push_back(*first); > | ~~~~~~~~~^~~~~~~~ I've found the same error with audacity 3.3 in current. I solved by building audacity 3.4.2 (the slackbuild works fine as is actually without any changes). First, an error occurred without lilv+suil installed. Since lv2 is an optional dependency I think a patch is needed if are not installed, but I solved installing also lilv and suil instead to find a patch. With these dependencies installed in the system the build of audacity 3.4.2 ends successfully. I didn't tested this solution in stable Slackware 15.0 -- ********************************************************* Giancarlo Dess? https://www.giand.it Slackware Linux... because it works! ********************************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Nov 25 15:20:55 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 25 Nov 2023 22:20:55 +0700 Subject: [Slackbuilds-users] Updates - 20231125.1 Message-ID: <995ddbc1-8ff2-48f2-aeca-14a1b72e1a0e@slackbuilds.org> Sat Nov 25 15:13:24 UTC 2023 academic/copasi: Updated for version 4.41.283. academic/fet: Updated for version 6.13.0. academic/hdfview: Added (visualization and exploration software). academic/suitesparse: Ensure correct linking academic/xschem: Added (schematic capture program). audio/audacity: Updated for version 3.4.2. audio/qjackctl: Updated for version 0.9.12, fix capabilities. desktop/nwg-drawer: Updated for version 0.4.1 desktop/nwg-look: Updated for version 0.2.5 desktop/nwg-shell-config: Updated for version 0.5.26 desktop/rss-guard: updated for version 4.5.5 desktop/wmclock: Updated for version 1.0.16. development/aws-cdk: Updated for version 2.110.0. development/bbcsdl: Updated for version 1.38a. development/cargo-vendor-filterer: Updated for version 0.5.12. development/dbeaver-ce: Updated for version 23.2.5. development/device-tree-compiler: Add -j1 to make commands. development/dkms: Updated for version 3.1.12 development/github-cli: Updated for version 2.39.1 development/kotlin: Updated for version 1.9.21. development/lua-language-server: Updated for version 3.7.3. development/mold: Updated for version 2.3.3. development/nodejs: Updated for version 20.10.0. development/php82: Updated for version 8.2.13 development/pli: Updated for version 1.2.0. development/uftrace: Updated for version 20231122_8343757 development/uncustify: Updated for version 0.78.1 development/universal-ctags: Updated for version p6.0.20231119.0 development/vstudio: Updated for version 13.5.2. games/odamex: Updated for version 10.4.0. games/puzzles: Updated for version 20231120.08365fb. games/zsnes: Updated for version 2.0.12. graphics/ART: Updated for version 1.20.2. graphics/OpenShadingLanguage: Added (language for shading) graphics/glmark2: Added (OpenGL and ES Benchmark). graphics/libplacebo: Use python3-meson-opt graphics/mcomix: Updated for version 3.0.0. graphics/openscad-threads: Added (modules for OpenSCAD). libraries/awscrt: Added (Python 3 bindings for the AWS CR). libraries/botocore: Updated for version 1.32.3. libraries/exiftool: Updated for version 12.70. libraries/libde265: Updated for version 1.0.14. libraries/libheif: Updated for version 1.17.5. libraries/libomemo-c: Added (fork of libsignal-protocol-c). libraries/nDPI: Updated for version 4.8. libraries/nanosvg: Added (SVG header file). libraries/python3-ruamel.yaml.clib: Added (reader for ruamel). libraries/skalibs: Updated for version 2.14.0.0 misc/fcitx5: Updated for version 5.1.5. misc/open-simh: Updated for version 2396fd0. misc/txt2tags: Updated for version 3.9. misc/vttest: Updated for version 2.7.20230924. misc/wcd: Updated for version 6.0.5. multimedia/mpv: Updated for version 0.37.0 network/awscli-v2: Added (AWS CLI). network/awscli: Updated for version 1.30.3. network/element-desktop: Updated for version 1.11.50 network/haproxy: Updated for version 2.8.4. network/jitsi-meet-desktop: Updated for version 2023.11.3 network/mailspring: Updated for version 1.12.0 network/netcat-openbsd: Updated for version 7.4_1 network/rspamd: Updated for version 3.7.4 network/slirp4netns: Updated for version 1.2.2. network/strongswan: Updated for version 5.9.11. network/toot: Updated for version 0.38.2. network/tor-browser: Updated for version 13.0.5. network/zoom-linux: Updated for version 5.16.10.668 office/LibreOffice: Updated for version 7.6.3.2 office/calibre-bin: Updated for version 7.1.0. office/hamster: Updated for version 3.0.3. office/libreoffice-helppack: Updated for version 7.6.3. office/libreoffice-langpack: Updated for version 7.6.3. office/libreoffice: Updated for version 7.6.3. office/smoffice2021: Updated for version 2021_1068. office/smoffice2024: Updated for version 2024_1206. office/wps-office: Updated for version 11.1.0.11711.XA. perl/perl-Config-Grammar: Added (perl module). python/Pyro4: Updated for version 4.82. python/alabaster: Updated for version 0.7.13. python/bottle-mysql: Updated for version 0.3.1. python/captcha: Updated for version 0.5.0. python/imagesize: Updated for version 1.4.1. python/jellyfish: Updated for version 1.0.3. python/pyelftools: Updated for version 0.30. python/python-serpent: Updated for version 1.41. python/python3-aiohttp: Updated for version 3.9.0 python/python3-augeas: Updated for version 1.2.0. python/python3-exceptiongroup: Updated for version 1.2.0. python/python3-expandvars: Added (Expand system variables). python/python3-ldap: Updated for version 3.4.4. python/python3-libtmux: Updated for version 0.24.1. python/python3-meson-opt: Updated for version 1.3.0. python/python3-pydantic-core: Updated for version 2.14.5. python/python3-pydantic: Updated for version 2.5.2. python/python3-rsa: Updated for version 4.9. python/python3-wheel: Update DEP. python/python3-yarl: Updated for version 1.9.3. python/s3transfer: Updated for version 0.7.0. system/CPU-X: Updated for version 5.0.2. system/FreeFileSync: Updated for version 13.2. system/conmon: Fix GIT commit version. system/conmon: Updated for version 2.1.8. system/duperemove: Updated for version 0.14. system/execline: Updated for version 2.9.4.0 system/locust: Updated for version 2.19.0. system/multitail: Updated for version 7.1.2. system/ntopng: Added (system monitoring). system/oksh: Updated for version 7.4. system/podman: Update for x86_64 only. system/podman: Updated for version 4.7.2. system/polychromatic: Updated for version 0.8.3. system/rasdaemon: add perl-DBD-SQLite dependency system/readpe: Added (CLI toolkit to analyze PE binaries). system/rtkit: Added (Realtime Policy and Watchdog Daemon). system/s6-linux-init: Updated for version 1.1.2.0 system/s6-rc: Updated for version 0.5.4.2 system/s6: Updated for version 2.12.0.0 system/sbo-create: Updated for version 2.0.7. system/stressapptest: Updated for version 1.0.11. system/telegraf: Updated for version 1.28.5 system/tmuxp: Updated for version 1.32.1. system/tuptime: Added (Report System Uptime). system/udiskie: Updated for version 2.5.1. system/xar: Updated for version 1.8dev+498. +--------------------------+ -- 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 mickski56 at hotmail.com Sun Nov 26 00:47:27 2023 From: mickski56 at hotmail.com (mickski56) Date: Sun, 26 Nov 2023 00:47:27 +0000 Subject: [Slackbuilds-users] Updates - 20231125.1 In-Reply-To: <995ddbc1-8ff2-48f2-aeca-14a1b72e1a0e@slackbuilds.org> References: <995ddbc1-8ff2-48f2-aeca-14a1b72e1a0e@slackbuilds.org> Message-ID: The VERSION field in audacity.info was not updated to 3.4.2 , everything else is showing 3.4.2 as it should. From willysr at slackbuilds.org Sun Nov 26 02:29:45 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 26 Nov 2023 09:29:45 +0700 Subject: [Slackbuilds-users] Updates - 20231125.1 In-Reply-To: References: <995ddbc1-8ff2-48f2-aeca-14a1b72e1a0e@slackbuilds.org> Message-ID: <184af45b-773d-4270-9ffc-f4a27d6efc38@slackbuilds.org> > The VERSION field in audacity.info was not updated to 3.4.2 , everything > else is showing 3.4.2 as it should. Fixed on my branch -- 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 slackalaxy at gmail.com Mon Nov 27 17:53:59 2023 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 27 Nov 2023 19:53:59 +0200 Subject: [Slackbuilds-users] Microsoft Edge is up for grabs In-Reply-To: <8234b2522e528fbeb01fdf59e2520aba@komputermatrix.com> References: <8234b2522e528fbeb01fdf59e2520aba@komputermatrix.com> Message-ID: hi, i was reading about a possible solution... newest Edge beta does not start either, but at least suggests running it with the "--enable-chrome-browser-cloud-management" option. Doing this, it complains about missing machine-id in /etc. Generating it by "dbus-uuidgen --ensure=/etc/machine-id" seems to fix the problem and Edge starts. I have no idea what "machine-id" is, though hope this helps best, Petar On Thu, 16 Nov 2023 at 02:54, wrote: > > I'm still not able to get recent versions of Edge to run. I have neither > the desire nor the expertise to fool with it any longer. > > The version on SBo is working but stale. > > -AP > > _______________________________________________ > 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 arnaud.garcia-fernandez at laposte.net Mon Nov 27 19:18:18 2023 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Mon, 27 Nov 2023 19:18:18 +0000 Subject: [Slackbuilds-users] Microsoft Edge is up for grabs In-Reply-To: References: <8234b2522e528fbeb01fdf59e2520aba@komputermatrix.com> Message-ID: Hmm, looks like a damn good way to track your activity, making sure all browsing happens from the same machine... Looks like a file needing to be regenerated on a daily basis, or each time you start edge. Ugly... - Yth. Le 27 novembre 2023 17:53:59 UTC, Petar Petrov a ?crit?: >hi, > >i was reading about a possible solution... > >newest Edge beta does not start either, but at least suggests running >it with the "--enable-chrome-browser-cloud-management" option. Doing >this, it complains about missing machine-id in /etc. Generating it by >"dbus-uuidgen --ensure=/etc/machine-id" seems to fix the problem and >Edge starts. I have no idea what "machine-id" is, though > >hope this helps > >best, > >Petar > >On Thu, 16 Nov 2023 at 02:54, wrote: >> >> I'm still not able to get recent versions of Edge to run. I have neither >> the desire nor the expertise to fool with it any longer. >> >> The version on SBo is working but stale. >> >> -AP >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - https://slackbuilds.org/faq/ > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From 414N at slacky.it Mon Nov 27 20:48:16 2023 From: 414N at slacky.it (414N) Date: Mon, 27 Nov 2023 21:48:16 +0100 Subject: [Slackbuilds-users] Microsoft Edge is up for grabs In-Reply-To: References: <8234b2522e528fbeb01fdf59e2520aba@komputermatrix.com> Message-ID: <908d75f4-edf4-46b0-88ce-5696c83e20fe@slacky.it> Il 27/11/23 20:18, Arnaud via SlackBuilds-users ha scritto: > Hmm, looks like a damn good way to track your activity, making sure all > browsing happens from the same machine... It depends on what component is requiring it and what it does with it. I also faced this issue with a software I use at work, where it did not start correctly if that file was missing, and I only understood the issue by looking at strace output... > Looks like a file needing to be regenerated on a daily basis, or each > time you start edge. Not really, you should generate it once (if missing) and keep it there. It's part of the systemd "bandwagon": https://www.man7.org/linux/man-pages/man5/machine-id.5.html If you run dbus on your system, you should already have a machine-id in /var/lib/dbus/machine-id. As these two files should have the same content, one usually symlinks one to the other (see the History section). -- Alan Alberghini SBo clone: https://github.com/414n/slackbuilds.org From for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net Tue Nov 28 09:21:10 2023 From: for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net (Lockywolf) Date: Tue, 28 Nov 2023 17:21:10 +0800 Subject: [Slackbuilds-users] [RFC] Adding features to .info format. Message-ID: <8734wqkyg2.fsf@laptop.lockywolf.net> Hello, colleagues There have been repeated discussions about two features that the current .info file format is missing: 1. aarch64 architecture. If in the past slarm64 was still an unofficial port, with -current it is official, and quite widely available, given the number of RPi machines available. 2. urls of the form https://example.test/address/ and https://example.test/address/1.json , which are either not supported by wget or can be mixed with each other, if downloaded into the same directory, which is especially bad with Golang and Haskell builds, which have many package-components, called 1.json. To address this issue, I propose a backward-compatible change to .info files format. 1. add DOWNLOAD_AARCH64 and DOWNLOAD_X86, a space-separated bash-string-list, identical in function to DOWNLOAD and DOWNLOAD_X86_64 2. add DOWNLOAD_NAME, DOWNLOAD_X86_64_NAME, DOWNLOAD_AARCH64_NAME, and DOWNLOAD_X86_NAME, space-separated _optional_ strings, which, if present, specify what the results of download should be named. If they are absent, current logic is not changed. Please, consider the upsides and downsides of this RFC. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) From erich.public at protonmail.com Tue Nov 28 13:21:43 2023 From: erich.public at protonmail.com (Erich Ritz) Date: Tue, 28 Nov 2023 13:21:43 +0000 Subject: [Slackbuilds-users] [RFC] Adding features to .info format. In-Reply-To: <8734wqkyg2.fsf@laptop.lockywolf.net> References: <8734wqkyg2.fsf@laptop.lockywolf.net> Message-ID: On Tuesday, November 28th, 2023 at 3:21 AM, Lockywolf wrote: > > > Hello, colleagues > > There have been repeated discussions about two features that the current > .info file format is missing: > > 1. aarch64 architecture. If in the past slarm64 was still an unofficial > port, with -current it is official, and quite widely available, given > the number of RPi machines available. > > 2. urls of the form https://example.test/address/ and > https://example.test/address/1.json , which are either not supported > by wget or can be mixed with each other, if downloaded into the same > directory, which is especially bad with Golang and Haskell builds, > which have many package-components, called 1.json. > > To address this issue, I propose a backward-compatible change to .info > files format. > > 1. add DOWNLOAD_AARCH64 and DOWNLOAD_X86, a space-separated > bash-string-list, identical in function to DOWNLOAD and > DOWNLOAD_X86_64 I think you mean DOWNLOAD_AARCH64 and DOWNLOAD_X86 function like DOWNLOAD_X86_64: they override DOWNLOAD for their respective arch. DOWNLOAD retains its current meaning. My first thought was DOWNLOAD_X86 is not needed because the same end result can be achieved with DOWNLOAD, DOWNLOAD_X86_64, and DOWNLOAD_AARCH64. But now I think I agree with you because it has a different meaning: DOWNLOAD is a (mostly) arch-independent download, where 1 or more of DOWNLOAD_* may be needed to override it. However, the absence of DOWNLOAD and the use of DOWNLOAD_* communicates that there are no arch-agnostic downloads; every download tarball is arch-specific. > > 2. add DOWNLOAD_NAME, DOWNLOAD_X86_64_NAME, DOWNLOAD_AARCH64_NAME, and > DOWNLOAD_X86_NAME, space-separated optional strings, which, if > present, specify what the results of download should be named. If > they are absent, current logic is not changed. Similarly, DOWNLOAD_NAME is arch-agnostic, while DOWNLOAD_X86_NAME, DOWNLOAD_X86_64_NAME, and DOWNLOAD_AARCH64_NAME provide overrides for their respective arch. > > Please, consider the upsides and downsides of this RFC. If this RFC is implemented, future changes could support DOWNLOAD_${ARCH} and DOWNLOAD_${ARCH}_NAME. By the way, I'm not explicitly supporting or NAKing this proposal. I'm just trying to help clarify the meaning of the new names. Erich > > -- > Your sincerely, > Vladimir Nikishkin (MiEr, lockywolf) > (Laptop) > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ From lockywolf at gmail.com Tue Nov 28 13:30:19 2023 From: lockywolf at gmail.com (Vladimir Nikishkin) Date: Tue, 28 Nov 2023 21:30:19 +0800 Subject: [Slackbuilds-users] [RFC] Adding features to .info format. In-Reply-To: References: <8734wqkyg2.fsf@laptop.lockywolf.net> Message-ID: <87v89mj932.fsf@laptop.lockywolf.net> Erich Ritz via SlackBuilds-users writes: > On Tuesday, November 28th, 2023 at 3:21 AM, Lockywolf wrote: > > >> >> >> Hello, colleagues >> >> There have been repeated discussions about two features that the current >> .info file format is missing: >> >> 1. aarch64 architecture. If in the past slarm64 was still an unofficial >> port, with -current it is official, and quite widely available, given >> the number of RPi machines available. >> >> 2. urls of the form https://example.test/address/ and >> https://example.test/address/1.json , which are either not supported >> by wget or can be mixed with each other, if downloaded into the same >> directory, which is especially bad with Golang and Haskell builds, >> which have many package-components, called 1.json. >> >> To address this issue, I propose a backward-compatible change to .info >> files format. >> >> 1. add DOWNLOAD_AARCH64 and DOWNLOAD_X86, a space-separated >> bash-string-list, identical in function to DOWNLOAD and >> DOWNLOAD_X86_64 > > I think you mean DOWNLOAD_AARCH64 and DOWNLOAD_X86 function like DOWNLOAD_X86_64: they override DOWNLOAD for their respective arch. DOWNLOAD retains its current meaning. > > My first thought was DOWNLOAD_X86 is not needed because the same end result can be > achieved with DOWNLOAD, DOWNLOAD_X86_64, and DOWNLOAD_AARCH64. But now I think I > agree with you because it has a different meaning: DOWNLOAD is a (mostly) > arch-independent download, where 1 or more of DOWNLOAD_* may be needed to override > it. However, the absence of DOWNLOAD and the use of DOWNLOAD_* communicates that > there are no arch-agnostic downloads; every download tarball is arch-specific. > Sorry, _almost_ like this, but not quite. To maintain current behaviour, the absence of arch-agnostic downloads is indicated by DOWNLOAD="UNSUPPORTED". >> >> 2. add DOWNLOAD_NAME, DOWNLOAD_X86_64_NAME, DOWNLOAD_AARCH64_NAME, and >> DOWNLOAD_X86_NAME, space-separated optional strings, which, if >> present, specify what the results of download should be named. If >> they are absent, current logic is not changed. > > Similarly, DOWNLOAD_NAME is arch-agnostic, while DOWNLOAD_X86_NAME, DOWNLOAD_X86_64_NAME, and DOWNLOAD_AARCH64_NAME provide overrides for their respective arch. > Yes. >> >> Please, consider the upsides and downsides of this RFC. > > If this RFC is implemented, future changes could support DOWNLOAD_${ARCH} and DOWNLOAD_${ARCH}_NAME. > > By the way, I'm not explicitly supporting or NAKing this proposal. I'm just trying to help clarify the meaning of the new names. > > Erich > >> >> -- >> Your sincerely, >> Vladimir Nikishkin (MiEr, lockywolf) >> (Laptop) >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ > _______________________________________________ > 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/ -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) From arnaud.garcia-fernandez at laposte.net Tue Nov 28 14:59:40 2023 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Tue, 28 Nov 2023 14:59:40 +0000 Subject: [Slackbuilds-users] [RFC] Adding features to .info format. In-Reply-To: <87v89mj932.fsf@laptop.lockywolf.net> References: <8734wqkyg2.fsf@laptop.lockywolf.net> <87v89mj932.fsf@laptop.lockywolf.net> Message-ID: >> My first thought was DOWNLOAD_X86 is not needed because the same end result can be >> achieved with DOWNLOAD, DOWNLOAD_X86_64, and DOWNLOAD_AARCH64. But now I think I >> agree with you because it has a different meaning: DOWNLOAD is a (mostly) >> arch-independent download, where 1 or more of DOWNLOAD_* may be needed to override >> it. However, the absence of DOWNLOAD and the use of DOWNLOAD_* communicates that >> there are no arch-agnostic downloads; every download tarball is arch-specific. >> > >Sorry, _almost_ like this, but not quite. To maintain current behaviour, >the absence of arch-agnostic downloads is indicated by >DOWNLOAD="UNSUPPORTED". That line currently means that the package does not build on ix86. The DOWNLOAD_X86 line would effectively break backward compatibility. But adding optional DOWNLOAD_{ARCH} for ARCH in ARM and AARCH64, and maybe later RISCV who knows, alongside the existing X86_64, looks like a fully backward-compatible evolution. And not very hard to use in existing tools, and easy to understand for maintainers, and users also. So I am fully in favor of that evolution : allowing DOWNLOAD_{ARCH} for other values, with the corresponding MD5SUM_{ARCH}. I already use it at home for syncthing on arm and aarch64. As for names, I'm unsure, but yeah, there are some problems with downloaded files, depending on tool, content-disposition, source also, etc. -- Yth. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Nov 28 15:03:12 2023 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 28 Nov 2023 22:03:12 +0700 Subject: [Slackbuilds-users] [RFC] Adding features to .info format. In-Reply-To: <8734wqkyg2.fsf@laptop.lockywolf.net> References: <8734wqkyg2.fsf@laptop.lockywolf.net> Message-ID: > There have been repeated discussions about two features that the current > .info file format is missing: > > 1. aarch64 architecture. If in the past slarm64 was still an unofficial > port, with -current it is official, and quite widely available, given > the number of RPi machines available. > > 2. urls of the form https://example.test/address/ and > https://example.test/address/1.json , which are either not supported > by wget or can be mixed with each other, if downloaded into the same > directory, which is especially bad with Golang and Haskell builds, > which have many package-components, called 1.json. > > To address this issue, I propose a backward-compatible change to .info > files format. > > 1. add DOWNLOAD_AARCH64 and DOWNLOAD_X86, a space-separated > bash-string-list, identical in function to DOWNLOAD and > DOWNLOAD_X86_64 > > 2. add DOWNLOAD_NAME, DOWNLOAD_X86_64_NAME, DOWNLOAD_AARCH64_NAME, and > DOWNLOAD_X86_NAME, space-separated _optional_ strings, which, if > present, specify what the results of download should be named. If > they are absent, current logic is not changed. This is my personal opinion and does not reflect other admins: My take on aarch64 is NO official support in SBo, but we can take "ELSE IF" in the SlackBuild to pass needed flags to build if the maintainer is using aarch and have done some testing to make sure it builds fine on aarch64. I personally don't have RPi machines to test it and we don't have enough resources and time to handle 3 architecture at the same time with over 8k scripts in SBo with only few active admins approving all the submissions that are coming in daily basis. I'm so grateful that Urchlay and Andrew has stepped up to help with the linter and semi-automatic CI engine in github. It really helped us to approve faster than before, but still requires some manual actions and time to make sure everything works as expected. i can't imagine how long would it take for the next repository to be ready if we have to test 8k+ scripts x 3 architectures using the number of resources we have. -- 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 dchmelik at gmail.com Tue Nov 28 15:38:34 2023 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Tue, 28 Nov 2023 07:38:34 -0800 Subject: [Slackbuilds-users] [RFC] Adding features to .info format. In-Reply-To: References: <8734wqkyg2.fsf@laptop.lockywolf.net> Message-ID: <4bc7d8e7-d0a4-b64f-e117-b00d1eca1307@gmail.com> On 11/28/23 7:03 AM, Willy Sudiarto Raharjo wrote: > This is my personal opinion and does not reflect other admins: > > My take on aarch64 is NO official support in SBo, but we can take > "ELSE IF" in the SlackBuild to pass needed flags to build if the > maintainer is using aarch and have done some testing to make sure it > builds fine on aarch64. [...] I hope that can change in future as I use /official/ arm(32|64) Slackware on Raspberry Pis... sbopkg & sbotools worked fine for me... didn't realize there was no official support but I didn't need a separate source code URL to install anything because nothing was arm-only.? However to use fans I installed I'd have to either program them myself or switch to RaspiOS or something similar with systemd. :( From slackalaxy at gmail.com Tue Nov 28 16:02:15 2023 From: slackalaxy at gmail.com (Petar Petrov) Date: Tue, 28 Nov 2023 18:02:15 +0200 Subject: [Slackbuilds-users] [RFC] Adding features to .info format. In-Reply-To: <8734wqkyg2.fsf@laptop.lockywolf.net> References: <8734wqkyg2.fsf@laptop.lockywolf.net> Message-ID: since we are talking about the INFO files again, I hope you guys will reconsider your decision and allow for having variables within the downloads links, e.g. for the sources version... -p On Tue, 28 Nov 2023 at 11:47, Lockywolf wrote: > > Hello, colleagues > > There have been repeated discussions about two features that the current > .info file format is missing: > > 1. aarch64 architecture. If in the past slarm64 was still an unofficial > port, with -current it is official, and quite widely available, given > the number of RPi machines available. > > 2. urls of the form https://example.test/address/ and > https://example.test/address/1.json , which are either not supported > by wget or can be mixed with each other, if downloaded into the same > directory, which is especially bad with Golang and Haskell builds, > which have many package-components, called 1.json. > > To address this issue, I propose a backward-compatible change to .info > files format. > > 1. add DOWNLOAD_AARCH64 and DOWNLOAD_X86, a space-separated > bash-string-list, identical in function to DOWNLOAD and > DOWNLOAD_X86_64 > > 2. add DOWNLOAD_NAME, DOWNLOAD_X86_64_NAME, DOWNLOAD_AARCH64_NAME, and > DOWNLOAD_X86_NAME, space-separated _optional_ strings, which, if > present, specify what the results of download should be named. If > they are absent, current logic is not changed. > > Please, consider the upsides and downsides of this RFC. > > -- > Your sincerely, > Vladimir Nikishkin (MiEr, lockywolf) > (Laptop) > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From lockywolf at gmail.com Thu Nov 30 01:11:07 2023 From: lockywolf at gmail.com (Vladimir Nikishkin) Date: Thu, 30 Nov 2023 09:11:07 +0800 Subject: [Slackbuilds-users] [RFC] Adding features to .info format. In-Reply-To: References: <8734wqkyg2.fsf@laptop.lockywolf.net> Message-ID: <87edg8hwh8.fsf@laptop.lockywolf.net> Willy Sudiarto Raharjo writes: > [[PGP Signed Part:Undecided]] >> There have been repeated discussions about two features that the current >> .info file format is missing: >> 1. aarch64 architecture. If in the past slarm64 was still an unofficial >> port, with -current it is official, and quite widely available, given >> the number of RPi machines available. >> 2. urls of the form https://example.test/address/ and >> https://example.test/address/1.json , which are either not supported >> by wget or can be mixed with each other, if downloaded into the same >> directory, which is especially bad with Golang and Haskell builds, >> which have many package-components, called 1.json. >> To address this issue, I propose a backward-compatible change to .info >> files format. >> 1. add DOWNLOAD_AARCH64 and DOWNLOAD_X86, a space-separated >> bash-string-list, identical in function to DOWNLOAD and >> DOWNLOAD_X86_64 >> 2. add DOWNLOAD_NAME, DOWNLOAD_X86_64_NAME, DOWNLOAD_AARCH64_NAME, and >> DOWNLOAD_X86_NAME, space-separated _optional_ strings, which, if >> present, specify what the results of download should be named. If >> they are absent, current logic is not changed. > > This is my personal opinion and does not reflect other admins: > > My take on aarch64 is NO official support in SBo, but we can take "ELSE IF" in the > SlackBuild to pass needed flags to build if the maintainer is using aarch and have > done some testing to make sure it builds fine on aarch64. I personally don't have > RPi machines to test it and we don't have enough resources and time to handle 3 > architecture at the same time with over 8k scripts in SBo with only few active > admins approving all the submissions that are coming in daily basis. > > I'm so grateful that Urchlay and Andrew has stepped up to help with the linter and > semi-automatic CI engine in github. It really helped us to approve faster than > before, but still requires some manual actions and time to make sure everything > works as expected. > > i can't imagine how long would it take for the next repository to be ready if we > have to test 8k+ scripts x 3 architectures using the number of resources we have. This RFC is not trying to make AARCH64 support mandatory, but is merely suggesting to allow such an entry in the info files. (I.e., allow sbolint to not bail out.) -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop)