From list+sbo at vahedi.org Thu Jan 2 13:47:46 2025 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Thu, 02 Jan 2025 13:47:46 +0000 Subject: [Slackbuilds-users] Symlinks and AUTOMATIC removals In-Reply-To: References: <214c859168862bbd8957bd95d96f98f97b9bc6d2@vahedi.org> <8469b4edde037e342a0cffaeb9bac3bde04de544@vahedi.org> Message-ID: <0d95a01d17bc8b514d0ea863574790a94d68f3fa@vahedi.org> December 31, "Jeremy Hansen" wrote: > This seems like *a lot* of unnecessary work for something makepkg is > literally designed to account for and automate (which minimizes chances of > mistakes). > ... > ... You're still able to manually > specify your symlinks in the doinst.sh, but I really think it's better to > just let makepkg handle them. Choice is up to you! I hear you. I will adapt my packages to "ln" in *.SlackBuild then. > You'd throw something like @LIBDIR@ into the doinst.sh and then use sed at > the end of the SlackBuild to make the necessary adjustments: > > sed -i "s|@LIBDIR@|lib$LIBDIRSUFFIX|g" doinst.sh That's neat. I'll keep that in mind if I ever need something like that. Thank you for sharing and spending the time on this! -- Shahab From mm at dorfdsl.de Sat Jan 4 11:12:13 2025 From: mm at dorfdsl.de (Marco Moock) Date: Sat, 4 Jan 2025 12:12:13 +0100 Subject: [Slackbuilds-users] older versions listed for upgrade Message-ID: <20250104121213.7a965d0a@ryz.dorfdsl.de> Hello! I used the tor slackbuild, but didn't use the old version listed in sbo, but the current version and changed the version info and used the current upstream tarball. VERSION=${VERSION:-0.4.8.13} Now sbocheck tells me that this can be "updated" to an older version. tor 0.4.8.13 < needs updating (0.4.8.7 from SBo) Is that a mistake by my own crafted stuff? -- kind regards Marco Send unsolicited bulk mail to 1735988903muell at stinkedores.dorfdsl.de From fsleg at t-rg.ws Sat Jan 4 12:22:57 2025 From: fsleg at t-rg.ws (fsLeg) Date: Sat, 4 Jan 2025 15:22:57 +0300 Subject: [Slackbuilds-users] older versions listed for upgrade In-Reply-To: <20250104121213.7a965d0a@ryz.dorfdsl.de> References: <20250104121213.7a965d0a@ryz.dorfdsl.de> Message-ID: <234f7e44-bb6e-4971-b9f1-16b26a1112b8@t-rg.ws> The answer to this is simple: sbocheck doesn't actually check version numbers, it only reports a potential update if the pulled version is different. This was answered years ago in sbotools' old repo: https://github.com/pink-mist/sbotools/issues/42#issuecomment-219218376 If you require newer versions than SBo provides and still use automated tools, you can set up local overrides as per comment I just mentioned. I also use local overrides to have my own scripts for things that aren't on SBo. You are supposed to inspect sbocheck's output before running sboupgrade anyway, and even if you do `sboupgrade --all` you still have to choose whether to upgrade each package individually, so just ignore the message if you know it's a false positive. On 04.01.2025 14:12, Marco Moock wrote: > Hello! > > I used the tor slackbuild, but didn't use the old version listed in > sbo, but the current version and changed the version info and used the > current upstream tarball. > > VERSION=${VERSION:-0.4.8.13} > > Now sbocheck tells me that this can be "updated" to an older version. > > tor 0.4.8.13 < needs updating (0.4.8.7 from SBo) > > Is that a mistake by my own crafted stuff? > From kvngncrlsn at gmail.com Sat Jan 4 12:30:16 2025 From: kvngncrlsn at gmail.com (K. Eugene Carlson) Date: Sat, 4 Jan 2025 21:30:16 +0900 Subject: [Slackbuilds-users] older versions listed for upgrade In-Reply-To: <20250104121213.7a965d0a@ryz.dorfdsl.de> References: <20250104121213.7a965d0a@ryz.dorfdsl.de> Message-ID: sbocheck and sboupgrade find the available version in the info file, not the SlackBuild. Like fsLeg wrote as I was starting this email, using a local overrides directory is good for this kind of situation. sbotools has been upgrading on version differences (not increments) since 2015. There's going to be an optional setting in 3.4 (should be able to get it out later this month) that will make it only go up by default. Cheers, Gene Carlson On Sat, Jan 4, 2025, 20:18 Marco Moock wrote: > Hello! > > I used the tor slackbuild, but didn't use the old version listed in > sbo, but the current version and changed the version info and used the > current upstream tarball. > > VERSION=${VERSION:-0.4.8.13} > > Now sbocheck tells me that this can be "updated" to an older version. > > tor 0.4.8.13 < needs updating (0.4.8.7 from SBo) > > Is that a mistake by my own crafted stuff? > > -- > kind regards > Marco > > Send unsolicited bulk mail to 1735988903muell at stinkedores.dorfdsl.de > _______________________________________________ > 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 Jan 4 15:39:25 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Jan 2025 22:39:25 +0700 Subject: [Slackbuilds-users] Updates - 20250104.1 Message-ID: <0b411a0c-d788-40b9-86b4-1cba7d32eddd@slackbuilds.org> Welcome to 2025 :) Sat Jan 4 15:28:16 UTC 2025 academic/fet: Updated for version 6.28.5. academic/grb: Added (Greek Bible). academic/kjv: Added (English Bible). academic/vul: Added (Latin Vulgate Bible). academic/vul: Update script. audio/cmus: Updated for version 2.12.0. audio/tuxguitar: Updated for version 1.6.6 desktop/fdpowermon: Added (Show Battery Info). desktop/kanshi: Handle content-disposition w/ git.sr.ht URLs desktop/kanshi: Updated for version 20241209_eed69c8 desktop/kanshi: Use constant version. desktop/mint-themes: Update script. desktop/mint-y-icons: Update maintainer. desktop/pdfsam: Removed (use pdfsam-basic). development/Catch2: Fixed pkgconfig paths for compat32 development/actionlint: Updated for version 1.7.5. development/aws-cdk: Updated for version 2.173.4. development/byacc: Updated for version 20241231. development/dart-sass: Added (Sass Reference Implementation). development/dkms: Updated for version 3.1.4 development/gede: Updated for version 2.22.1. development/gitlab-cli: Updated for version 1.51.0 development/golangci-lint: Updated for version 1.63.3. development/golangci-lint: Updated for version 1.63.4. development/heroku-cli: Updated for version 10.0.0 development/pnpm: Updated for version 9.15.2. development/vstudio: Updated for version 14.6.3 games/puzzles: Updated for version 20241230.79be403. games/scummvm: Updated for version 2.9.0. games/vkQuake: Updated for version 1.31.3. games/wesnoth: Updated for version 1.18.3 git/ci: Update CI dependencies. graphics/libresprite: Added (Animate Sprites). graphics/qiv: add .avif image support. graphics/vuescan: Updated for version 9.8.43. graphics/xmedcon: Updated for version 0.25.0. ham/redsea: Updated for version 1.1.0. ham/sdrpp: Updated for version 20241221.46bcba75. libraries/libheif: Update doinst.sh for gdk-pixbuf loader libraries/libheif: Update maintainer email libraries/libmobi: Added (Library for Mobipocket). libraries/luaexpat: Updated for version 1.5.2. libraries/luasec: Updated for version 1.3.2. libraries/mujs: Better soname handling libraries/notcurses: Added (TUI library). misc/yubikey-manager-qt: Added (GUI for Yubikey). misc/yubikey-manager: Added (Python library for yubikey). multimedia/mpv: Update README multimedia/saflashplayer-legacy: Added (Legacy version of saflashplayer). multimedia/saflashplayer: Added (Flash Player Projector). network/emailrelay: Updated for version 2.6. network/gajim: Always set protocol buffers impl. network/gpodder: Updated for version 3.11.5 (moved from multimedia). network/nchat: Updated for version 5.4.2. network/newsboat: Updated for version 2.38. network/newsraft: Added (Terminal Feed Reader). network/openfortivpn: Updated for version 1.22.1. network/opera: Updated for version 115.0.5322.119. network/prosody-mod-filter-chatstates: Updated for version hg6058. network/prosody-mod-throttle-presence: Updated for version hg6057. network/prosody: Updated for version 0.12.5. network/protonmail-bridge: Updated for version 3.15.1. network/scrcpy: Updated for version 3.1 network/shadowsocks-rust: Added (Rust port of shadowsocks). network/spf-engine: Updated for version 3.1.0. network/tcpbench: Updated for version 3.00. network/telegram: Updated for version 5.10.0. python/pyotherside: Added (Python Bindings for Qt5/6). python/pyscard: Added (Python Smart Card Library). python/python-fido2: Added (Library for FIDO devices). python/python2-BeautifulSoup4: Fix .info. python/python2-soupsieve: Fix .info. python/python3-anyio: Fix .info. python/python3-evdev: Fix .info. python/python3-identify: Updated for version 2.6.4. python/python3-pexpect: Fix .info. python/python3-pythran: Fix .info. python/python3-sniffio: Fix .info. python/python3-tomlkit: Fix .info. ruby/ruby-build: Updated for version 20241225.2. system/Iosevka-aile: Updated for version 32.3.1. system/Iosevka-etoile: Updated for version 32.3.1. system/Iosevka-slab: Updated for version 32.3.1. system/Iosevka: Updated for version 32.3.1. system/Solaar: Updated for version 1.1.14. system/argyllcms: Updated for version 3.3.0. system/chronograf: Updated for version 1.10.6 system/conky: Updated for version 1.22.0. system/docker-compose: Updated for version 2.32.1 system/dumptorrent: Added (Display Torrent Information). system/gamescope: Added (SteamOS Window Manager). system/jq: New maintainer system/jsawk: Removed (use jq). system/kapacitor: Updated for version 1.7.6 system/kitty: Updated for version 0.38.1 system/libratbag: Fix .info. system/onefetch: Updated for version 2.23.1. system/piper: Fix .info. system/prometheus: Updated for version 3.1.0. system/qemu: Updated for version 9.2.0 system/sarasa-gothic: Updated for version 1.0.27. system/sbokeeper: Updated for version 2.01. system/sbotools: Updated for version 3.3. system/skim: Updated for version 0.15.7. system/system76-io-dkms: Updated for version 1.0.4. system/yubico-piv-tool: Updated for version 2.7.1. +--------------------------+ -- 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 matt.egger at gmail.com Sat Jan 4 19:45:12 2025 From: matt.egger at gmail.com (Matt Egger) Date: Sat, 4 Jan 2025 14:45:12 -0500 Subject: [Slackbuilds-users] Fwd: obsidian on slackbuilds.org In-Reply-To: <5e213e3a93bbf44ada9a9aa65c821c1a@nikov.net> References: <5e213e3a93bbf44ada9a9aa65c821c1a@nikov.net> Message-ID: I'm submitting an updated slackbuild via github PR momentarily. ---------- Forwarded message --------- From: Date: Tue, Dec 24, 2024 at 10:11?AM Subject: Re: obsidian on slackbuilds.org To: Matt Egger Hi Matt, thank you for reaching out to me. Please go ahead, I am happy to transfer it to you. Best regards, Dimtiar On 2024-12-21 19:03, Matt Egger wrote: Greetings, I've noticed that the slackbuild for obsidian hasn't been updated yet. I've updated it in my repo and I'm interested in maintaining the script on slackbuilds.org going forward. Are you open to turning it over to me? If so, I'll email the list send in a PR with my update and change of maintainership. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From dchmelik at gmail.com Tue Jan 7 13:17:12 2025 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Tue, 7 Jan 2025 05:17:12 -0800 Subject: [Slackbuilds-users] updating mathics? Message-ID: <16b1b841-b22c-89ad-c070-40197e5a5b78@gmail.com> I want to update mathics, which now consists of mathics-core, mathics-django, mathics-scanner, or mathics-omnibus, and others.? I checked what I needed while building,and my SlackBuilds (mentioned last year are on my website) made packages: determined the set needs click, mathics-django, mathics_scanner, python3-mpmath, python3-numpy, python3-scipy, python3-sympy, but I don't know what goes to what, so I asked mathics' slack chat months ago.? They never answered.? I asked their github.? Instead they talked about finding python package dependencies in general, such as with pipdeptree, which instead lists llvmite, mathics_scanner, mpmath, numpy, palettable, pillow, pint, python-dateutil, requests, setuptools, sympy (mathics-django is for command-line but might not be needed for world wide web interface also for localhost, but I'm unsure). ??? ??? Then they proceeded to say 'standard' dependencies on Slackware 14--from 13 years ago--are old! ??? ??? That's without getting to details whether mathics-create-database script Urchlay wrote is still needed (maybe not). ??????? At this point, I give up: anyone can take over mathics. However, if no one does, I'll try to continue.? I just haven't known what to do since Mathics 4 (by/after which it doesn't work right) and now despite it's called Mathics3, it's mathics 7.? It's a 'mess of python dependencies' the programmers apparently aren't following/using strictly UNIX-like OS, so I'm stuck.? I won't be able to submit the new updates (though they work) without finding out what the dependencies really are. ??? ??? Maybe WolframEngine is easier (just haven't been able to install). From dchmelik at gmail.com Tue Jan 7 13:17:31 2025 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Tue, 7 Jan 2025 05:17:31 -0800 Subject: [Slackbuilds-users] updating mathics? Message-ID: <42f41a78-c1e7-5f8e-5641-0961ceac4ac7@gmail.com> I want to update mathics, which now consists of mathics-core, mathics-django, mathics-scanner, or mathics-omnibus, and others.? I checked what I needed while building,and my SlackBuilds (mentioned last year are on my website) made packages: determined the set needs click, mathics-django, mathics_scanner, python3-mpmath, python3-numpy, python3-scipy, python3-sympy, but I don't know what goes to what, so I asked mathics' slack chat months ago.? They never answered.? I asked their github.? Instead they talked about finding python package dependencies in general, such as with pipdeptree, which instead lists llvmite, mathics_scanner, mpmath, numpy, palettable, pillow, pint, python-dateutil, requests, setuptools, sympy (mathics-django is for command-line but might not be needed for world wide web interface also for localhost, but I'm unsure). ??? ??? Then they proceeded to say 'standard' dependencies on Slackware 14--from 13 years ago--are old! ??? ??? That's without getting to details whether mathics-create-database script Urchlay wrote is still needed (maybe not). ??????? At this point, I give up: anyone can take over mathics. However, if no one does, I'll try to continue.? I just haven't known what to do since Mathics 4 (by/after which it doesn't work right) and now despite it's called Mathics3, it's mathics 7.? It's a 'mess of python dependencies' the programmers apparently aren't following/using strictly UNIX-like OS, so I'm stuck.? I won't be able to submit the new updates (though they work) without finding out what the dependencies really are. ??? ??? Maybe WolframEngine is easier (just haven't been able to install). From willysr at slackbuilds.org Tue Jan 7 17:46:28 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 8 Jan 2025 00:46:28 +0700 Subject: [Slackbuilds-users] updating mathics? In-Reply-To: <16b1b841-b22c-89ad-c070-40197e5a5b78@gmail.com> References: <16b1b841-b22c-89ad-c070-40197e5a5b78@gmail.com> Message-ID: > I want to update mathics, which now consists of mathics-core, mathics- > django, mathics-scanner, or mathics-omnibus, and others.? I checked what > I needed while building,and my SlackBuilds (mentioned last year are on > my website) made packages: determined the set needs click, mathics- > django, mathics_scanner, python3-mpmath, python3-numpy, python3-scipy, > python3-sympy, but I don't know what goes to what, so I asked mathics' > slack chat months ago.? They never answered.? I asked their github. > Instead they talked about finding python package dependencies in > general, such as with pipdeptree, which instead lists llvmite, > mathics_scanner, mpmath, numpy, palettable, pillow, pint, python- > dateutil, requests, setuptools, sympy (mathics-django is for command- > line but might not be needed for world wide web interface also for > localhost, but I'm unsure). > ??? ??? Then they proceeded to say 'standard' dependencies on Slackware > 14--from 13 years ago--are old! > ??? ??? That's without getting to details whether mathics-create- > database script Urchlay wrote is still needed (maybe not). > ??????? At this point, I give up: anyone can take over mathics. > However, if no one does, I'll try to continue.? I just haven't known > what to do since Mathics 4 (by/after which it doesn't work right) and > now despite it's called Mathics3, it's mathics 7.? It's a 'mess of > python dependencies' the programmers apparently aren't following/using > strictly UNIX-like OS, so I'm stuck.? I won't be able to submit the new > updates (though they work) without finding out what the dependencies > really are. > ??? ??? Maybe WolframEngine is easier (just haven't been able to install). Start with the core package first https://github.com/mathics/Mathics/blob/master/setup.py https://github.com/mathics/Mathics/blob/master/requirements-full.txt -- 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 Wed Jan 8 00:42:03 2025 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Tue, 7 Jan 2025 16:42:03 -0800 Subject: [Slackbuilds-users] updating mathics? In-Reply-To: References: <16b1b841-b22c-89ad-c070-40197e5a5b78@gmail.com> Message-ID: On 1/7/25 9:46 AM, Willy Sudiarto Raharjo wrote: >> I want to update mathics, which now consists of mathics-core, >> mathics- django, mathics-scanner, or mathics-omnibus, and others.? I >> checked what I needed while building,and my SlackBuilds (mentioned >> last year are on my website) made packages: determined the set needs >> click, mathics- django, mathics_scanner, python3-mpmath, >> python3-numpy, python3-scipy, python3-sympy, but I don't know what >> goes to what, so I asked mathics' slack chat months ago.? They never >> answered.? I asked their github.? Instead they talked about finding >> python package dependencies in general, such as with pipdeptree, >> which instead lists llvmite, mathics_scanner, mpmath, numpy, >> palettable, pillow, pint, python- dateutil, requests, setuptools, >> sympy (mathics-django is for command- line but might not be needed >> for world wide web interface also for localhost, but I'm unsure). >> ???? ??? Then they proceeded to say 'standard' dependencies on >> Slackware 14--from 13 years ago--are old! >> ???? ??? That's without getting to details whether mathics-create- >> database script Urchlay wrote is still needed (maybe not). >> ???????? At this point, I give up: anyone can take over mathics. >> However, if no one does, I'll try to continue.? I just haven't known >> what to do since Mathics 4 (by/after which it doesn't work right) and >> now despite it's called Mathics3, it's mathics 7. It's a 'mess of >> python dependencies' the programmers apparently aren't >> following/using strictly UNIX-like OS, so I'm stuck.? I won't be able >> to submit the new updates (though they work) without finding out what >> the dependencies really are. >> ???? ??? Maybe WolframEngine is easier (just haven't been able to >> install). > > Start with the core package first > https://github.com/mathics/Mathics/blob/master/setup.py > https://github.com/mathics/Mathics/blob/master/requirements-full.txt As said (and in aforementioned SlackBuilds) it's Mathics3 now: http://github.com/Mathics3/mathics-core , so no longer that simple; I stated last October it no longer uses setup.py. From dchmelik at gmail.com Wed Jan 8 03:19:38 2025 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Tue, 7 Jan 2025 19:19:38 -0800 Subject: [Slackbuilds-users] deb2tgz deletes user's files! Message-ID: deb2tgz deletes my files!? I never gave it locations of these but it deletes them! root at 0.cosmos:~# deb2tgz AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb ... Making symbolic link creation script: ( cd . ; rm -rf art ) ( cd . ; ln -sf d/art art ) ( cd . ; rm -rf bookmark ) ( cd . ; ln -sf html/bookmark bookmark ) ( cd chroot-current/bin ; rm -rf ash ) ( cd chroot-current/bin ; ln -sf /bin/dash ash ) ... (some lines before that and thousands after) From urchlay at slackware.uk Wed Jan 8 03:24:27 2025 From: urchlay at slackware.uk (B. Watson) Date: Tue, 7 Jan 2025 22:24:27 -0500 (EST) Subject: [Slackbuilds-users] deb2tgz deletes user's files! In-Reply-To: References: Message-ID: On Tue, 7 Jan 2025, dchmelik at gmail.com wrote: > root at 0.cosmos:~# deb2tgz > AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb Can you give a URL where we can download this .deb file? From dchmelik at gmail.com Wed Jan 8 03:26:21 2025 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Tue, 7 Jan 2025 19:26:21 -0800 Subject: [Slackbuilds-users] deb2tgz deletes user's files! In-Reply-To: References: Message-ID: <8a1808c7-a2f5-6b9e-13c9-6cffb8ec7a13@gmail.com> On 1/7/25 7:24 PM, B. Watson wrote: > On Tue, 7 Jan 2025, dchmelik at gmail.com wrote: >> root at 0.cosmos:~# deb2tgz >> AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb > > Can you give a URL where we can download this .deb file? http://download.gigabyte.com/FileList/Utility/AI_TOP_Utility_ver_2_0_1_release.zip?v=3dcfb2d63a787c71cc8e34dea4db58c0 From urchlay at slackware.uk Wed Jan 8 04:05:57 2025 From: urchlay at slackware.uk (B. Watson) Date: Tue, 7 Jan 2025 23:05:57 -0500 (EST) Subject: [Slackbuilds-users] deb2tgz deletes user's files! In-Reply-To: <8a1808c7-a2f5-6b9e-13c9-6cffb8ec7a13@gmail.com> References: <8a1808c7-a2f5-6b9e-13c9-6cffb8ec7a13@gmail.com> Message-ID: On Tue, 7 Jan 2025, dchmelik at gmail.com wrote: > http://download.gigabyte.com/FileList/Utility/AI_TOP_Utility_ver_2_0_1_release.zip?v=3dcfb2d63a787c71cc8e34dea4db58c0 The .deb package inside the .zip file looks fine, when I pick it apart manually with ar and tar: # ar t AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb debian-binary control.tar.gz data.tar.xz # ar x AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb data.tar.xz # tar tvf data.tar.xz |head -5 drwxr-xr-x 0/0 0 2024-12-28 11:04 ./ drwxr-xr-x 0/0 0 2024-12-28 11:04 ./usr/ drwxr-xr-x 0/0 0 2024-12-28 11:04 ./usr/share/ drwxr-xr-x 0/0 0 2024-12-28 11:04 ./usr/share/icons/ drwxr-xr-x 0/0 0 2024-12-28 11:04 ./usr/share/icons/hicolor/ ...I tried running deb2tgz on it the same way you did, but got different results (also failure): # deb2tgz AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb ERROR: ar failed. (maybe AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb is not an DEB?) However, if you cd into the directory and run it with just the filename: # cd AI_TOP_Utility_ver_2_0_1 # deb2tgz gigabyte-ai-top-utility-2.0.1.deb # ls -l *.t?z -rw-r--r-- 1 root root 275757980 Jan 8 03:53 gigabyte-ai-top-utility-2.0.1.txz So it worked. It seems to hate having a relative path to the .deb file. I don't know why. In any case, I didn't get results like you got. Your output included "Making symbolic link creation script". That's normally printed by makepkg. *Nothing* in /usr/bin/deb2tgz has that text or calls makepkg. All it does it deduce the compression type (from looking at the output of 'ar'), extract the data.tar.*, and rename it to match the original .deb filename. Are you sure your deb2tgz command is actually the /usr/bin/deb2tgz one from SBo? # which deb2tgz /usr/bin/deb2tgz When I run it with no arguments, I get: # deb2tgz /usr/bin/deb2tgz: Converts DEB format to standard GNU tar + (GZ/XZ/LZ/BZ) format. (view converted packages with "less", install and remove with "installpkg", "removepkg", "pkgtool", or manually with "tar") Usage: /usr/bin/deb2tgz (Outputs "file.t*z") What output do you get from the above two commands? If it's the same as mine, your original email is missing whatever 'makepkg' command you ran, to produce the "Making symbolic link creation script". We can't try to diagnose the problem if we can't see it. From jebrhansen+SBo at gmail.com Wed Jan 8 04:13:20 2025 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 7 Jan 2025 20:13:20 -0800 Subject: [Slackbuilds-users] updating mathics? In-Reply-To: References: <16b1b841-b22c-89ad-c070-40197e5a5b78@gmail.com> Message-ID: On Tue, Jan 7, 2025 at 4:42?PM wrote: > On 1/7/25 9:46 AM, Willy Sudiarto Raharjo wrote: > >> I want to update mathics, which now consists of mathics-core, > >> mathics- django, mathics-scanner, or mathics-omnibus, and others. I > >> checked what I needed while building,and my SlackBuilds (mentioned > >> last year are on my website) made packages: determined the set needs > >> click, mathics- django, mathics_scanner, python3-mpmath, > >> python3-numpy, python3-scipy, python3-sympy, but I don't know what > >> goes to what, so I asked mathics' slack chat months ago. They never > >> answered. I asked their github. Instead they talked about finding > >> python package dependencies in general, such as with pipdeptree, > >> which instead lists llvmite, mathics_scanner, mpmath, numpy, > >> palettable, pillow, pint, python- dateutil, requests, setuptools, > >> sympy (mathics-django is for command- line but might not be needed > >> for world wide web interface also for localhost, but I'm unsure). > >> Then they proceeded to say 'standard' dependencies on > >> Slackware 14--from 13 years ago--are old! > >> That's without getting to details whether mathics-create- > >> database script Urchlay wrote is still needed (maybe not). > >> At this point, I give up: anyone can take over mathics. > >> However, if no one does, I'll try to continue. I just haven't known > >> what to do since Mathics 4 (by/after which it doesn't work right) and > >> now despite it's called Mathics3, it's mathics 7. It's a 'mess of > >> python dependencies' the programmers apparently aren't > >> following/using strictly UNIX-like OS, so I'm stuck. I won't be able > >> to submit the new updates (though they work) without finding out what > >> the dependencies really are. > >> Maybe WolframEngine is easier (just haven't been able to > >> install). > > > > Start with the core package first > > https://github.com/mathics/Mathics/blob/master/setup.py > > https://github.com/mathics/Mathics/blob/master/requirements-full.txt > As said (and in aforementioned SlackBuilds) it's Mathics3 now: > http://github.com/Mathics3/mathics-core , so no longer that simple; I > stated last October it no longer uses setup.py. > It's really just a matter of going through the dependencies listed in the now pyproject.toml, try building, and see if it complains. Once all the complaints are resolved and it builds, install it, and use `pip check` to see what else is missing that it's asking for. Install those, and then try running the program to see if it complains again. Then just make sure the dependencies are documented in the .info file. I had some free time this evening, so I tried my hand at this. I created a SlackBuild for mathics-core (using my SlackBuild generator script -- *shameless plug*). After running that, I removed the setup.py entries (from the template) and ran the script. It complained about setuptools being too old and missing mathics-scanner. So I added a dependency to mathics-scanner and python3-setuptools-opt and added the command in the script to update the python path for the newer setuptools. Then I created a script for mathics-scanner using the same slackbuild generator script and went through the same process as I previously did. Once mathics-scanner compiled, I went back to mathics-core and went through that process futher. Ultimately, I found that mathics-core requires a few packages not on SBo yet (palettable, pint, & pympler, which I've listed with "@" around them in the mathics-core.info) and it complained about an outdated pillow version. For testing, I installed them using pip (in an otherwise clean environment that I can reset easily to not have python modules installed via pip in normal operation), and was able to finally start up mathics without error. However, I know absolutely nothing about mathics and don't know what to run to check if it's working properly. I have no idea if having an outdated version of pillow (stock 15.0 package) will cause any issues with output, so that would certainly need to be tested further. I made a zip file of these two SlackBuilds and attached it (if it isn't blocked) and put it on my server (for at least a few weeks until I go through and purge unneeded files in there) if you're interested in creating SlackBuilds for pint and palettable and can otherwise test if mathics works once those dependencies are met. I won't be willing to maintain these SlackBuilds since I don't use mathics and wouldn't know how to test it, so feel free to take over if you (or someone else) is interested in continuing it. If you have any questions, I'll try to answer them the best I can. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mathics.tar.gz Type: application/gzip Size: 3232 bytes Desc: not available URL: From sbo at linuxgalaxy.org Wed Jan 8 04:26:14 2025 From: sbo at linuxgalaxy.org (KB_SBo) Date: Wed, 08 Jan 2025 04:26:14 +0000 Subject: [Slackbuilds-users] deb2tgz deletes user's files! In-Reply-To: <8a1808c7-a2f5-6b9e-13c9-6cffb8ec7a13@gmail.com> References: <8a1808c7-a2f5-6b9e-13c9-6cffb8ec7a13@gmail.com> Message-ID: On 1/7/25 19:26, dchmelik at gmail.com wrote: > On 1/7/25 7:24 PM, B. Watson wrote: >> On Tue, 7 Jan 2025, dchmelik at gmail.com wrote: >>> root at 0.cosmos:~# deb2tgz >>> AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb >> >> Can you give a URL where we can download this .deb file? > http://download.gigabyte.com/FileList/Utility/AI_TOP_Utility_ver_2_0_1_release.zip?v=3dcfb2d63a787c71cc8e34dea4db58c0 > > _______________________________________________ @dchmelik, I don't see anything in the deb2tgz shell script where it created symlinks or doinst.sh or runs any binary other that mkdir, echo, chmod,ar, mv, and rm $TMPDIR... deb2tgz just extracts the data.tar.gz in the .deb and just renames it as a tgz. Just ran it in a qemu VM. no issues. Sounds like you did something weird on your own. -kb From dchmelik at gmail.com Wed Jan 8 04:49:00 2025 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Tue, 7 Jan 2025 20:49:00 -0800 Subject: [Slackbuilds-users] deb2tgz deletes user's files! In-Reply-To: References: <8a1808c7-a2f5-6b9e-13c9-6cffb8ec7a13@gmail.com> Message-ID: <4946214d-4318-539a-40e3-33cb1e8f5140@gmail.com> On 1/7/25 8:05 PM, B. Watson wrote: > On Tue, 7 Jan 2025, dchmelik at gmail.com wrote: >> http://download.gigabyte.com/FileList/Utility/AI_TOP_Utility_ver_2_0_1_release.zip?v=3dcfb2d63a787c71cc8e34dea4db58c0 >> > [...] > ...I tried running deb2tgz on it the same way you did, but got different > results (also failure): > > # deb2tgz AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb > ERROR: ar failed. (maybe > AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb is not an > DEB?) I see. > However, if you cd into the directory and run it with just the filename: > > # cd AI_TOP_Utility_ver_2_0_1 > # deb2tgz gigabyte-ai-top-utility-2.0.1.deb > # ls -l *.t?z > -rw-r--r-- 1 root root 275757980 Jan? 8 03:53 > gigabyte-ai-top-utility-2.0.1.txz > > So it worked. It seems to hate having a relative path to the .deb > file. I don't know why. In any case, I didn't get results like you > got. It worked when I did it that way. > Your output included "Making symbolic link creation script". That's > normally printed by makepkg. *Nothing* in /usr/bin/deb2tgz has that > text or calls makepkg. All it does it deduce the compression type > (from looking at the output of 'ar'), extract the data.tar.*, and > rename it to match the original .deb filename. Okay. > > Are you sure your deb2tgz command is actually the /usr/bin/deb2tgz one > from SBo? > > # which deb2tgz > /usr/bin/deb2tgz Yes, but I also had one in /usr/local/bin (says from ZenWalk, which I never used, but don't recall where I got that). > > When I run it with no arguments, I get: > > # deb2tgz /usr/bin/deb2tgz:? Converts DEB format to standard GNU tar + > (GZ/XZ/LZ/BZ) format. > ?? (view converted packages with "less", install and remove > ?? with "installpkg", "removepkg", "pkgtool", or manually > ?? with "tar") > > Usage:??? /usr/bin/deb2tgz > ?? (Outputs "file.t*z") > > What output do you get from the above two commands? If it's the same > as mine, your original email is missing whatever 'makepkg' command you > ran, to produce the "Making symbolic link creation script". We can't > try to diagnose the problem if we can't see it. The same, but I didn't run that; deb2tgz (both versions) do, and it scrolls off the screen fast.? I can't do it again unless I setup to test somehow, because I don't want it removing /root symbolic links and a lot of stuff in /root/chroot-current I now had to reinstall that whole chroot. From urchlay at slackware.uk Wed Jan 8 05:44:17 2025 From: urchlay at slackware.uk (B. Watson) Date: Wed, 8 Jan 2025 00:44:17 -0500 (EST) Subject: [Slackbuilds-users] deb2tgz deletes user's files! In-Reply-To: <4946214d-4318-539a-40e3-33cb1e8f5140@gmail.com> References: <8a1808c7-a2f5-6b9e-13c9-6cffb8ec7a13@gmail.com> <4946214d-4318-539a-40e3-33cb1e8f5140@gmail.com> Message-ID: <5e8839e-1ba-5afd-de97-797fee98eea9@slackware.uk> On Tue, 7 Jan 2025, dchmelik at gmail.com wrote: > Yes, but I also had one in /usr/local/bin (says from ZenWalk, which I > never used, but don't recall where I got that). Is it this? https://github.com/jbarrett/deb2tgz Because even though the name is the same, it's a totally different program, by a different author. And it *does* call makepkg. Most likely, you had /usr/local/bin in $PATH before /usr/bin, and you ran that deb2tgz command instead of the one from SBo. >> What output do you get from the above two commands? > The same, but I didn't run that Right, you didn't. SlackBuilds.org didn't provide your /usr/local/bin/deb2tgz command, so we can't fix it. If there's a bug to be reported here, you should be reporting it to the maintainer of the ZenWalk deb2tgz package, or to its upstream (look for contact info inside the script). From willysr at slackbuilds.org Wed Jan 8 07:37:47 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 8 Jan 2025 14:37:47 +0700 Subject: [Slackbuilds-users] deb2tgz deletes user's files! In-Reply-To: References: Message-ID: <557497f2-d9ef-42c1-9461-88c43cd0e3f1@slackbuilds.org> > deb2tgz deletes my files!? I never gave it locations of these but it > deletes them! > root at 0.cosmos:~# deb2tgz AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top- > utility-2.0.1.deb This is not related to SBo, why report it here? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3F617144D7238786.asc Type: application/pgp-keys Size: 8363 bytes Desc: OpenPGP public key URL: -------------- 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 Jan 11 01:50:10 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Jan 2025 08:50:10 +0700 Subject: [Slackbuilds-users] Updates - 20250111.1 Message-ID: Sat Jan 11 01:44:22 UTC 2025 academic/cdo: Updated for version 2.5.0. academic/nco: Updated for version 5.3.0. academic/units: Updated for version 2.24. academic/vul: Updated for version 20230314_10d9d61. desktop/SiriKali: Updated for version 1.8.0. desktop/numix-icon-theme-circle: Updated for version 24.12.12. desktop/numix-icon-theme: Updated for version 24.12.12. desktop/pcb2gcodeGUI: Added (GUI for pcb2gcode). development/actionlint: Updated for version 1.7.6. development/aws-cdk: Updated for version 2.174.0. development/aws-cdk: Updated for version 2.175.0. development/dart-sass: Updated for version 1.83.1. development/dkms: Include autoinstaller development/dpkg: Updated for version 1.22.13. development/jupyter-ipywidgets: Added (HTML widgets for Jupyter). development/jupyter-widgetsnbextension: Added (Interactive widget for Jupyter). development/meld3: Updated for version 3.22.3. development/mold: Updated for version 2.36.0. development/obsidian: updated for version 1.7.7 development/php84: Added (Scripting Language). development/pnpm: Updated for version 9.15.3. development/protobuf3: Updated for version 29.3. games/attract: Added (Frontend for emulators). games/ddnet: updated for version 18.9. games/steamtinkerlaunch: New maintainer gis/eccodes: Updated for version 2.39.0. gis/gdal: Updated for version 3.10.0. gis/python3-xarray: Updated for version 2025.01.0 graphics/paraview: Updated for version 5.13.2 graphics/yacreader: Updated for version 9.15.0. libraries/pugixml: Updated for version 1.15. multimedia/QMPlay2: Updated for version 24.12.28. multimedia/aegisub: Updated for version 3.4.1. network/bitcoin: Updated for version 28.1. network/discord: Version bump to 0.0.79 network/dropbox: Updated for version 215.4.7202. network/gallery-dl: Updated for version 1.28.3. network/netsniff-ng: Updated for version 0.6.9. network/newsraft: Updated for version 0.28. network/shadowsocks-rust: Updated for version 1.22.0. network/signal-desktop: Update for version 7.37.0. network/syncthingtray-bin: Updated for version 1.7.1. network/teamviewer: Updated for version 15.61.3. network/telegram: Updated for version 5.10.1. network/telegram: Updated for version 5.10.3. network/tor-browser: Updated for version 14.0.4. network/vivaldi: Updated for version 7.0.3495.29. network/wireshark: Updated for version 4.4.3. network/zoom-linux: Updated for 6.3.5.6065 office/gnucash-docs: Updated for version 5.10. office/gnucash: Updated for version 5.10. office/pdfpc: Updated for version 4.7.0 python/pyrfc3339: Updated for version 2.0.1. python/python3-aiohttp-socks: Updated for version 0.10.1. python/python3-anyio: Version bump to 4.8.0 python/python3-cachecontrol: Version bump to 0.14.2 python/python3-identify: Updated for version 2.6.5. python/python3-kiwisolver: Version bump to 1.4.8 python/python3-poetry-dynamic-versioning: Updated for version 1.6.0. python/python3-socks: Updated for version 2.6.1. python/python3-soundfile: Version bump to 0.13.0 python/python3-virtualenv: Version bump to 20.28.1 python3/python3-poetry-dynamic-versioning: Updated for v 1.5.0. ruby/rbenv: Updated for version 1.3.2. system/CNS11643-kai-font: Updated for version 20241216. system/CNS11643-sung-font: Updated for version 20241216. system/bat: Updated for version 0.25.0. system/docker-compose: Updated for version 2.32.2 system/fastfetch: Updated for version 2.34.0. system/jenkins: Updated for version 2.479.3. system/letsencrypt: Updated for version 3.1.0. system/netdata: Updated for version 2.1.1. system/sbokeeper: Updated for version 2.02. +--------------------------+ -- 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 1.41421 at gmail.com Sat Jan 11 22:21:48 2025 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 11 Jan 2025 15:21:48 -0700 Subject: [Slackbuilds-users] Updates - 20250111.1 In-Reply-To: References: Message-ID: Trying to build the latest gnucash release I am getting the following: [ 31%] Built target scm-engine-0 [ 31%] Generating ../../lib64/guile/3.0/site-ccache/gnucash/engine.go wrote `/tmp/SBo/gnucash-5.10/build/lib64/guile/3.0/site-ccache/gnucash/engine.go' [ 31%] Built target scm-engine-1 [ 31%] Generating ../../share/guile/site/3.0/gnucash/utilities.scm [ 31%] Built target scm-engine-2-links [ 32%] Generating ../../lib64/guile/3.0/site-ccache/gnucash/utilities.go utilities.scm:43:3: warning: possibly unbound variable `gnc-log-warn' utilities.scm:46:3: warning: possibly unbound variable `gnc-log-error' utilities.scm:49:3: warning: possibly unbound variable `gnc-log-msg' utilities.scm:53:5: warning: possibly unbound variable `gnc-log-debug' wrote `/tmp/SBo/gnucash-5.10/build/lib64/guile/3.0/site-ccache/gnucash/utilities.go' [ 32%] Built target scm-engine-2 [ 34%] Generating ../../lib64/guile/3.0/site-ccache/gnucash/options.go Backtrace: In ice-9/eval.scm: 619:8 19 (_ #(#(#))) In /usr/bin/guild: 72:17 18 (main _) In srfi/srfi-1.scm: 634:9 17 (for-each # ?) In scripts/compile.scm: 279:26 16 (_ _) In system/base/target.scm: 65:6 15 (with-target _ _) In system/base/compile.scm: 187:6 14 (compile-file "/tmp/SBo/gnucash-5.10/bindings/guile/op?" ?) 53:4 13 (call-with-output-file/atomic _ _ _) In ice-9/boot-9.scm: 1752:10 12 (with-exception-handler _ _ #:unwind? _ # _) In system/base/compile.scm: 69:11 11 (_) 190:11 10 (_ #) 331:39 9 (read-and-compile # #:from _ #:to ?) 261:27 8 (_ _ _) In ice-9/boot-9.scm: 2835:4 7 (save-module-excursion #) In language/scheme/compile-tree-il.scm: 31:15 6 (_) In ice-9/psyntax.scm: 1230:36 5 (expand-top-sequence (#) ?) 1222:19 4 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?) 259:10 3 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?) In unknown file: 2 (load-extension "libgnucash-guile" "scm_init_sw_app_uti?") 1 (dlsym # "scm_init_sw_app_utils_modu?") In ice-9/boot-9.scm: 1685:16 0 (raise-exception _ #:continuable? _) ice-9/boot-9.scm:1685:16: In procedure raise-exception: In procedure dlsym: Error resolving "scm_init_sw_app_utils_module": "/usr/lib64/libgnucash-guile.so: undefined symbol: scm_init_sw_app_utils_module" make[2]: *** [bindings/guile/CMakeFiles/scm-options.dir/build.make:76: lib64/guile/3.0/site-ccache/gnucash/options.go] Error 1 make[1]: *** [CMakeFiles/Makefile2:9716: bindings/guile/CMakeFiles/scm-options.dir/all] Error 2 make: *** [Makefile:166: all] Error 2 Is it just me, or has anybody else out there observed this as well? On Fri, Jan 10, 2025 at 6:50?PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Sat Jan 11 01:44:22 UTC 2025 > academic/cdo: Updated for version 2.5.0. > academic/nco: Updated for version 5.3.0. > academic/units: Updated for version 2.24. > academic/vul: Updated for version 20230314_10d9d61. > desktop/SiriKali: Updated for version 1.8.0. > desktop/numix-icon-theme-circle: Updated for version 24.12.12. > desktop/numix-icon-theme: Updated for version 24.12.12. > desktop/pcb2gcodeGUI: Added (GUI for pcb2gcode). > development/actionlint: Updated for version 1.7.6. > development/aws-cdk: Updated for version 2.174.0. > development/aws-cdk: Updated for version 2.175.0. > development/dart-sass: Updated for version 1.83.1. > development/dkms: Include autoinstaller > development/dpkg: Updated for version 1.22.13. > development/jupyter-ipywidgets: Added (HTML widgets for Jupyter). > development/jupyter-widgetsnbextension: Added (Interactive widget for > Jupyter). > development/meld3: Updated for version 3.22.3. > development/mold: Updated for version 2.36.0. > development/obsidian: updated for version 1.7.7 > development/php84: Added (Scripting Language). > development/pnpm: Updated for version 9.15.3. > development/protobuf3: Updated for version 29.3. > games/attract: Added (Frontend for emulators). > games/ddnet: updated for version 18.9. > games/steamtinkerlaunch: New maintainer > gis/eccodes: Updated for version 2.39.0. > gis/gdal: Updated for version 3.10.0. > gis/python3-xarray: Updated for version 2025.01.0 > graphics/paraview: Updated for version 5.13.2 > graphics/yacreader: Updated for version 9.15.0. > libraries/pugixml: Updated for version 1.15. > multimedia/QMPlay2: Updated for version 24.12.28. > multimedia/aegisub: Updated for version 3.4.1. > network/bitcoin: Updated for version 28.1. > network/discord: Version bump to 0.0.79 > network/dropbox: Updated for version 215.4.7202. > network/gallery-dl: Updated for version 1.28.3. > network/netsniff-ng: Updated for version 0.6.9. > network/newsraft: Updated for version 0.28. > network/shadowsocks-rust: Updated for version 1.22.0. > network/signal-desktop: Update for version 7.37.0. > network/syncthingtray-bin: Updated for version 1.7.1. > network/teamviewer: Updated for version 15.61.3. > network/telegram: Updated for version 5.10.1. > network/telegram: Updated for version 5.10.3. > network/tor-browser: Updated for version 14.0.4. > network/vivaldi: Updated for version 7.0.3495.29. > network/wireshark: Updated for version 4.4.3. > network/zoom-linux: Updated for 6.3.5.6065 > office/gnucash-docs: Updated for version 5.10. > office/gnucash: Updated for version 5.10. > office/pdfpc: Updated for version 4.7.0 > python/pyrfc3339: Updated for version 2.0.1. > python/python3-aiohttp-socks: Updated for version 0.10.1. > python/python3-anyio: Version bump to 4.8.0 > python/python3-cachecontrol: Version bump to 0.14.2 > python/python3-identify: Updated for version 2.6.5. > python/python3-kiwisolver: Version bump to 1.4.8 > python/python3-poetry-dynamic-versioning: Updated for version 1.6.0. > python/python3-socks: Updated for version 2.6.1. > python/python3-soundfile: Version bump to 0.13.0 > python/python3-virtualenv: Version bump to 20.28.1 > python3/python3-poetry-dynamic-versioning: Updated for v 1.5.0. > ruby/rbenv: Updated for version 1.3.2. > system/CNS11643-kai-font: Updated for version 20241216. > system/CNS11643-sung-font: Updated for version 20241216. > system/bat: Updated for version 0.25.0. > system/docker-compose: Updated for version 2.32.2 > system/fastfetch: Updated for version 2.34.0. > system/jenkins: Updated for version 2.479.3. > system/letsencrypt: Updated for version 3.1.0. > system/netdata: Updated for version 2.1.1. > system/sbokeeper: Updated for version 2.02. > +--------------------------+ > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sat Jan 11 22:34:30 2025 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 11 Jan 2025 15:34:30 -0700 Subject: [Slackbuilds-users] Updates - 20250111.1 In-Reply-To: References: Message-ID: Actually, it builds without a problem when one first removes the previously installed, older version - I guess the build process tries to use the libgnucash-guile.so shared library under /usr/lib64 if present. On Sat, Jan 11, 2025 at 3:21?PM Luveh Keraph <1.41421 at gmail.com> wrote: > Trying to build the latest gnucash release I am getting the following: > > [ 31%] Built target scm-engine-0 > [ 31%] Generating ../../lib64/guile/3.0/site-ccache/gnucash/engine.go > wrote > `/tmp/SBo/gnucash-5.10/build/lib64/guile/3.0/site-ccache/gnucash/engine.go' > [ 31%] Built target scm-engine-1 > [ 31%] Generating ../../share/guile/site/3.0/gnucash/utilities.scm > [ 31%] Built target scm-engine-2-links > [ 32%] Generating ../../lib64/guile/3.0/site-ccache/gnucash/utilities.go > utilities.scm:43:3: warning: possibly unbound variable `gnc-log-warn' > utilities.scm:46:3: warning: possibly unbound variable `gnc-log-error' > utilities.scm:49:3: warning: possibly unbound variable `gnc-log-msg' > utilities.scm:53:5: warning: possibly unbound variable `gnc-log-debug' > wrote > `/tmp/SBo/gnucash-5.10/build/lib64/guile/3.0/site-ccache/gnucash/utilities.go' > [ 32%] Built target scm-engine-2 > [ 34%] Generating ../../lib64/guile/3.0/site-ccache/gnucash/options.go > Backtrace: > In ice-9/eval.scm: > 619:8 19 (_ #(#(#))) > In /usr/bin/guild: > 72:17 18 (main _) > In srfi/srfi-1.scm: > 634:9 17 (for-each # ?) > In scripts/compile.scm: > 279:26 16 (_ _) > In system/base/target.scm: > 65:6 15 (with-target _ _) > In system/base/compile.scm: > 187:6 14 (compile-file "/tmp/SBo/gnucash-5.10/bindings/guile/op?" ?) > 53:4 13 (call-with-output-file/atomic _ _ _) > In ice-9/boot-9.scm: > 1752:10 12 (with-exception-handler _ _ #:unwind? _ # _) > In system/base/compile.scm: > 69:11 11 (_) > 190:11 10 (_ #) > 331:39 9 (read-and-compile # #:from _ #:to ?) > 261:27 8 (_ _ _) > In ice-9/boot-9.scm: > 2835:4 7 (save-module-excursion #) > In language/scheme/compile-tree-il.scm: > 31:15 6 (_) > In ice-9/psyntax.scm: > 1230:36 5 (expand-top-sequence (#) ?) > 1222:19 4 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?) > 259:10 3 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?) > In unknown file: > 2 (load-extension "libgnucash-guile" "scm_init_sw_app_uti?") > 1 (dlsym # "scm_init_sw_app_utils_modu?") > In ice-9/boot-9.scm: > 1685:16 0 (raise-exception _ #:continuable? _) > > ice-9/boot-9.scm:1685:16: In procedure raise-exception: > In procedure dlsym: Error resolving "scm_init_sw_app_utils_module": > "/usr/lib64/libgnucash-guile.so: undefined symbol: > scm_init_sw_app_utils_module" > make[2]: *** [bindings/guile/CMakeFiles/scm-options.dir/build.make:76: > lib64/guile/3.0/site-ccache/gnucash/options.go] Error 1 > make[1]: *** [CMakeFiles/Makefile2:9716: > bindings/guile/CMakeFiles/scm-options.dir/all] Error 2 > make: *** [Makefile:166: all] Error 2 > > Is it just me, or has anybody else out there observed this as well? > > On Fri, Jan 10, 2025 at 6:50?PM Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> Sat Jan 11 01:44:22 UTC 2025 >> academic/cdo: Updated for version 2.5.0. >> academic/nco: Updated for version 5.3.0. >> academic/units: Updated for version 2.24. >> academic/vul: Updated for version 20230314_10d9d61. >> desktop/SiriKali: Updated for version 1.8.0. >> desktop/numix-icon-theme-circle: Updated for version 24.12.12. >> desktop/numix-icon-theme: Updated for version 24.12.12. >> desktop/pcb2gcodeGUI: Added (GUI for pcb2gcode). >> development/actionlint: Updated for version 1.7.6. >> development/aws-cdk: Updated for version 2.174.0. >> development/aws-cdk: Updated for version 2.175.0. >> development/dart-sass: Updated for version 1.83.1. >> development/dkms: Include autoinstaller >> development/dpkg: Updated for version 1.22.13. >> development/jupyter-ipywidgets: Added (HTML widgets for Jupyter). >> development/jupyter-widgetsnbextension: Added (Interactive widget for >> Jupyter). >> development/meld3: Updated for version 3.22.3. >> development/mold: Updated for version 2.36.0. >> development/obsidian: updated for version 1.7.7 >> development/php84: Added (Scripting Language). >> development/pnpm: Updated for version 9.15.3. >> development/protobuf3: Updated for version 29.3. >> games/attract: Added (Frontend for emulators). >> games/ddnet: updated for version 18.9. >> games/steamtinkerlaunch: New maintainer >> gis/eccodes: Updated for version 2.39.0. >> gis/gdal: Updated for version 3.10.0. >> gis/python3-xarray: Updated for version 2025.01.0 >> graphics/paraview: Updated for version 5.13.2 >> graphics/yacreader: Updated for version 9.15.0. >> libraries/pugixml: Updated for version 1.15. >> multimedia/QMPlay2: Updated for version 24.12.28. >> multimedia/aegisub: Updated for version 3.4.1. >> network/bitcoin: Updated for version 28.1. >> network/discord: Version bump to 0.0.79 >> network/dropbox: Updated for version 215.4.7202. >> network/gallery-dl: Updated for version 1.28.3. >> network/netsniff-ng: Updated for version 0.6.9. >> network/newsraft: Updated for version 0.28. >> network/shadowsocks-rust: Updated for version 1.22.0. >> network/signal-desktop: Update for version 7.37.0. >> network/syncthingtray-bin: Updated for version 1.7.1. >> network/teamviewer: Updated for version 15.61.3. >> network/telegram: Updated for version 5.10.1. >> network/telegram: Updated for version 5.10.3. >> network/tor-browser: Updated for version 14.0.4. >> network/vivaldi: Updated for version 7.0.3495.29. >> network/wireshark: Updated for version 4.4.3. >> network/zoom-linux: Updated for 6.3.5.6065 >> office/gnucash-docs: Updated for version 5.10. >> office/gnucash: Updated for version 5.10. >> office/pdfpc: Updated for version 4.7.0 >> python/pyrfc3339: Updated for version 2.0.1. >> python/python3-aiohttp-socks: Updated for version 0.10.1. >> python/python3-anyio: Version bump to 4.8.0 >> python/python3-cachecontrol: Version bump to 0.14.2 >> python/python3-identify: Updated for version 2.6.5. >> python/python3-kiwisolver: Version bump to 1.4.8 >> python/python3-poetry-dynamic-versioning: Updated for version 1.6.0. >> python/python3-socks: Updated for version 2.6.1. >> python/python3-soundfile: Version bump to 0.13.0 >> python/python3-virtualenv: Version bump to 20.28.1 >> python3/python3-poetry-dynamic-versioning: Updated for v 1.5.0. >> ruby/rbenv: Updated for version 1.3.2. >> system/CNS11643-kai-font: Updated for version 20241216. >> system/CNS11643-sung-font: Updated for version 20241216. >> system/bat: Updated for version 0.25.0. >> system/docker-compose: Updated for version 2.32.2 >> system/fastfetch: Updated for version 2.34.0. >> system/jenkins: Updated for version 2.479.3. >> system/letsencrypt: Updated for version 3.1.0. >> system/netdata: Updated for version 2.1.1. >> system/sbokeeper: Updated for version 2.02. >> +--------------------------+ >> >> >> -- >> Willy Sudiarto Raharjo >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at osh.id.au Sun Jan 12 05:08:50 2025 From: lists at osh.id.au (David O'Shaughnessy) Date: Sun, 12 Jan 2025 13:08:50 +0800 Subject: [Slackbuilds-users] Updates - 20250111.1 In-Reply-To: References: Message-ID: <58f68f07-edd5-4c6e-8f24-b57c48fdf94b@app.fastmail.com> Yep, I had the same error until I uninstalled the old version and then built it. On Sun, 12 Jan 2025, at 6:34 AM, Luveh Keraph wrote: > Actually, it builds without a problem when one first removes the previously installed, older version - I guess the build process tries to use the libgnucash-guile.so shared library under /usr/lib64 if present. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lenardrspencer at gmail.com Sun Jan 12 06:24:57 2025 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Sun, 12 Jan 2025 01:24:57 -0500 Subject: [Slackbuilds-users] Updates - 20250111.1 In-Reply-To: <58f68f07-edd5-4c6e-8f24-b57c48fdf94b@app.fastmail.com> References: <58f68f07-edd5-4c6e-8f24-b57c48fdf94b@app.fastmail.com> Message-ID: Thanks for the info on gnucash. I'll resubmit with an updated README to reflect this. On Sun, Jan 12, 2025 at 12:09?AM David O'Shaughnessy wrote: > Yep, I had the same error until I uninstalled the old version and then > built it. > > On Sun, 12 Jan 2025, at 6:34 AM, Luveh Keraph wrote: > > Actually, it builds without a problem when one first removes the > previously installed, older version - I guess the build process tries to > use the libgnucash-guile.so shared library under /usr/lib64 if present. > > > _______________________________________________ > 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 pintitas at hotmail.com Sun Jan 12 22:42:41 2025 From: pintitas at hotmail.com (Carmela bulemio) Date: Sun, 12 Jan 2025 22:42:41 +0000 Subject: [Slackbuilds-users] "Minidlna" fix to work with slackware real path (/var/run/minidlna) Message-ID: I built my minidlna package from slackbuilds. But it was faulty. Trying to do anything like Code: /etc/rc.d/rc.minidlna restart/stop/start .. Threw an error. It looked like the PID was still running, but it wasn't. The /etc/rc.d/rc.minidlna was faulty. Just correcting this line solved the problem >From this Code: PIDFILE="/var/run/${NAME}.pid" To this ( the right path) Code: PIDFILE="/var/run/minidlna/${NAME}.pid" -------------- next part -------------- An HTML attachment was scrubbed... URL: From mario at slackware.hr Wed Jan 15 17:33:20 2025 From: mario at slackware.hr (Mario) Date: Wed, 15 Jan 2025 18:33:20 +0100 Subject: [Slackbuilds-users] "Minidlna" fix to work with slackware real path (/var/run/minidlna) In-Reply-To: References: Message-ID: <753a8ec1-34be-4ca1-ace2-e146e36d796a@slackware.hr> On 1/12/25 11:42 PM, Carmela bulemio wrote: > > I built my minidlna package from slackbuilds. > > But it was faulty. Trying to do anything like > Code: > /etc/rc.d/rc.minidlna restart/stop/start .. > Threw an error. It looked like the PID was still running, but it wasn't. > > The*?/etc/rc.d/rc.minidlna*?was faulty. > > Just correcting this line solved the problem > > From this > Code: > PIDFILE="/var/run/${NAME}.pid" > To this ( the right path) > Code: > PIDFILE="/var/run/minidlna/${NAME}.pid" > > > Thanks, it's fixed in my branch. Note however, logrotate config also needs the fix. -- Mario -------------- next part -------------- An HTML attachment was scrubbed... URL: From fsleg at t-rg.ws Wed Jan 15 18:42:22 2025 From: fsleg at t-rg.ws (fsLeg) Date: Wed, 15 Jan 2025 21:42:22 +0300 Subject: [Slackbuilds-users] Script submission technicality Message-ID: I just realized something. Anyone can submit a SlackBuild. There's no authorization, no checks who actually submits it, and even Submission Guidelines don't mention anything about who can submit SlackBuilds. Even existing ones. So while it would be a good courtesy to notify some script's author that a new version came out or there's a bug in their script, you could just fix it yourself and submit it without changing author and maintainer fields. If it's a good-willed change, you just specify your own email when submitting a tarball. If you're slightly less good-willed, but still want the SlackBuild to just work, you can specify the maintainer's email, and it doesn't even matter since it seems that nothing is actually emailed when you submit a script. So does it mean that it's actually OK to submit updates, fixes and changes to existing SlackBuilds yourself if their maintainers don't do it in reasonable time? At what point would that be considered a takeover? Or is this just an oversight in the guidelines? And side question, since I mentioned a takeover. I emailed maintainers of two SlackBuilds and asked them to update their scripts, but got no response in two weeks by now. How long should I wait before asking here to take over their SlackBuilds? From urchlay at slackware.uk Wed Jan 15 19:06:51 2025 From: urchlay at slackware.uk (B. Watson) Date: Wed, 15 Jan 2025 14:06:51 -0500 (EST) Subject: [Slackbuilds-users] Script submission technicality In-Reply-To: References: Message-ID: <601052d-3f92-b6cd-a442-2553fc1ae098@slackware.uk> On Wed, 15 Jan 2025, fsLeg wrote: > I just realized something. Anyone can submit a SlackBuild. There's no > authorization, no checks who actually submits it, and even Submission > Guidelines don't mention anything about who can submit SlackBuilds. Even > existing ones. So while it would be a good courtesy to notify some script's > author that a new version came out or there's a bug in their script, you > could just fix it yourself and submit it without changing author and > maintainer fields. If it's a good-willed change, you just specify your own > email when submitting a tarball. If you're slightly less good-willed, but > still want the SlackBuild to just work, you can specify the maintainer's > email, and it doesn't even matter since it seems that nothing is actually > emailed when you submit a script. Well, there's the email with the removal code. Gets sent to the email you enter in the submission form. If you put the original maintainer's address there, he'll get that email and go "wait, I didn't submit an update for this". > So does it mean that it's actually OK to submit updates, fixes and changes to > existing SlackBuilds yourself if their maintainers don't do it in reasonable > time? At what point would that be considered a takeover? Or is this just an > oversight in the guidelines? It's not OK to update others' SlackBuilds. We don't have any technical measures in place to prevent it, we rely on people being honest. Maybe in the long run that won't work out, but so far it's been OK. > And side question, since I mentioned a takeover. I emailed maintainers of > two SlackBuilds and asked them to update their scripts, but got no response > in two weeks by now. How long should I wait before asking here to take over > their SlackBuilds? If it's been two weeks, please ask the list. There are some maintainers who changed their email addresses and forgot to update their .info files, but who still subscribe to the list with their new addresses. Do that, and if you don't get a response to the list mail within a week, the builds are yours to take over. Another thing to check: clone the git repo and search the git log for the maintainer's name and/or email, e.g.: git log --author="Joe Blow" The results will be most-recent first. If you see that the maintainer hasn't done anything in a long time (like, years), you can assume that maintainer's abandoned his builds. That's not always the case, e.g. someone changed their 'maintainer name' and forgot to update one of his builds, or someone maintains only one build and it hasn't been updated upstream in years, but it's at least a data item. If you see lots of recent activity from the maintainer, you can assume his builds are *not* up for grabs. From list+sbo at vahedi.org Wed Jan 15 19:21:38 2025 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Wed, 15 Jan 2025 20:21:38 +0100 (GMT+01:00) Subject: [Slackbuilds-users] Script submission technicality In-Reply-To: <601052d-3f92-b6cd-a442-2553fc1ae098@slackware.uk> References: <601052d-3f92-b6cd-a442-2553fc1ae098@slackware.uk> Message-ID: <3174baee-a143-4385-9016-09e3d54c8d19@vahedi.org> B. Watson wrote: > fsLeg wrote: >> So does it mean that it's actually OK to submit updates, fixes and changes to existing SlackBuilds yourself if their maintainers don't do it in reasonable time? At what point would that be considered a takeover? Or is this just an oversight in the guidelines? > > It's not OK to update others' SlackBuilds. We don't have any technical > measures in place to prevent it, we rely on people being honest. Shoot! I have done couple of updates through the submission form with my own email address of course. They were for packages who haven't been updated in years. I had no intention of takeover. Could I do it in GitLab with my user account? So it would immediately become clear that I'm not the author. -- Shahab From urchlay at slackware.uk Wed Jan 15 19:45:17 2025 From: urchlay at slackware.uk (B. Watson) Date: Wed, 15 Jan 2025 14:45:17 -0500 (EST) Subject: [Slackbuilds-users] Script submission technicality In-Reply-To: <3174baee-a143-4385-9016-09e3d54c8d19@vahedi.org> References: <601052d-3f92-b6cd-a442-2553fc1ae098@slackware.uk> <3174baee-a143-4385-9016-09e3d54c8d19@vahedi.org> Message-ID: <7b184bfe-aeb6-1ce-c621-3c5b3f2d258@slackware.uk> On Wed, 15 Jan 2025, Shahab Vahedi via SlackBuilds-users wrote: > Shoot! I have done couple of updates through the submission form with my own email address of course. They were for packages who haven't been updated in years. I had no intention of takeover. Please do take them over. We want every build to have an active maintainer. The rule is, if you want to update a build, you have to list yourself as maintainer. The only exception to that is that SBo admins can update/modify any build. Though we'd rather have the maintainers do that. From zsd+slackbuilds at jdvb.ca Wed Jan 15 19:45:50 2025 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Wed, 15 Jan 2025 15:45:50 -0400 Subject: [Slackbuilds-users] VBox slackbuild Message-ID: Hi all, Back in November I emailed the Virtualbox Slackbuild maintainer, pointing out that VBox was up to 7.1, whereas the Slackbuild is at 6.1.50. (And since then, VBox is up to 7.1.4.) I never heard back. Is anyone in touch with the maintainer (Heinz Wiesinger)? Thanks. Jim From erich.public at protonmail.com Wed Jan 15 20:18:48 2025 From: erich.public at protonmail.com (Erich Ritz) Date: Wed, 15 Jan 2025 20:18:48 +0000 Subject: [Slackbuilds-users] VBox slackbuild In-Reply-To: References: Message-ID: On Wednesday, January 15th, 2025 at 1:45 PM, Jim wrote: > > > Hi all, > > Back in November I emailed the Virtualbox Slackbuild maintainer, pointing > out that VBox was up to 7.1, whereas the Slackbuild is at 6.1.50. (And > since then, VBox is up to 7.1.4.) > > I never heard back. Is anyone in touch with the maintainer (Heinz > Wiesinger)? > This was his comment last time an update request came up (https://lists.slackbuilds.org/pipermail/slackbuilds-users/2023-May/028176.html): Is there a specific feature/bugfix you *need* from the newer version though? Generally, the version on SBo should work "just fine". If it's just about running the "latest and greatest", you should be able to fetch the SlackBuild from my -current or 15.0 repo (or even the packages). I don't typically update my scripts on SBo anymore unless there's a specific reason. > Thanks. > Jim > _______________________________________________ > 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 korgie at gmail.com Wed Jan 15 20:20:09 2025 From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=) Date: Wed, 15 Jan 2025 22:20:09 +0200 Subject: [Slackbuilds-users] VBox slackbuild In-Reply-To: References: Message-ID: > 15 ??? 2025, 21:46, ? ??????? ?Jim ? ??????: > > ?Hi all, > > Back in November I emailed the Virtualbox Slackbuild maintainer, pointing > out that VBox was up to 7.1, whereas the Slackbuild is at 6.1.50. (And > since then, VBox is up to 7.1.4. I tried the 7 series binary and it was a failure in my system. From zsd+slackbuilds at jdvb.ca Wed Jan 15 20:43:42 2025 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Wed, 15 Jan 2025 16:43:42 -0400 Subject: [Slackbuilds-users] VBox slackbuild In-Reply-To: References: Message-ID: On Wed, Jan 15, 2025 at 20:18 (+0000), Erich Ritz via SlackBuilds-users wrote: > On Wednesday, January 15th, 2025 at 1:45 PM, Jim wrote: >> Hi all, >> Back in November I emailed the Virtualbox Slackbuild maintainer, pointing >> out that VBox was up to 7.1, whereas the Slackbuild is at 6.1.50. (And >> since then, VBox is up to 7.1.4.) >> I never heard back. Is anyone in touch with the maintainer (Heinz >> Wiesinger)? > This was his comment last time an update request came up (https://lists.slackbuilds.org/pipermail/slackbuilds-users/2023-May/028176.html): > Is there a specific feature/bugfix you *need* from the newer version though? > Generally, the version on SBo should work "just fine". If it's just about > running the "latest and greatest", you should be able to fetch the SlackBuild > from my -current or 15.0 repo (or even the packages). I don't typically update > my scripts on SBo anymore unless there's a specific reason. *My* specific reason was that I updated to a newer kernel (6.10.3), because I was having some glitchy issues with one of the components of my laptop. And my info at the time was that versions before 7.0.16 would no longer compile on 6.10 kernels. So I guess you could say "I need a VBox that compiles on 6.10". (But, having said that, I suspect someone is going to tell me that my system isn't vanilla, so I'm on my own.) korgie at gmail.com: I compiled 7.0.20 and it has been working just fine on 6.10.3 (Slackware64 15.0). I agree that maintainers should not feel obligated to spend all day every day chasing updates to the packages that they have graciously agreed to support. But, on the flip side, perhaps occasionally, if someone needs a newer version for some reason, it is also possible that they might be motivated to do an update when requested. Anyway, now that you have pointed out Heinz' personal policy, I will know to not ask again about this. Cheers. Jim From matteo.bernardini at gmail.com Wed Jan 15 21:38:22 2025 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 15 Jan 2025 22:38:22 +0100 Subject: [Slackbuilds-users] VBox slackbuild In-Reply-To: References: Message-ID: Il giorno mer 15 gen 2025 alle ore 22:07 Jim ha scritto: > On Wed, Jan 15, 2025 at 20:18 (+0000), Erich Ritz via SlackBuilds-users > wrote: > > > On Wednesday, January 15th, 2025 at 1:45 PM, Jim < > zsd+slackbuilds at jdvb.ca> wrote: > > >> Hi all, > > >> Back in November I emailed the Virtualbox Slackbuild maintainer, > pointing > >> out that VBox was up to 7.1, whereas the Slackbuild is at 6.1.50. (And > >> since then, VBox is up to 7.1.4.) > > >> I never heard back. Is anyone in touch with the maintainer (Heinz > >> Wiesinger)? > > > > This was his comment last time an update request came up ( > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2023-May/028176.html > ): > > > Is there a specific feature/bugfix you *need* from the newer version > though? > > Generally, the version on SBo should work "just fine". If it's just > about > > running the "latest and greatest", you should be able to fetch the > SlackBuild > > from my -current or 15.0 repo (or even the packages). I don't typically > update > > my scripts on SBo anymore unless there's a specific reason. > > *My* specific reason was that I updated to a newer kernel (6.10.3), because > I was having some glitchy issues with one of the components of my laptop. > And my info at the time was that versions before 7.0.16 would no longer > compile on 6.10 kernels. > > So I guess you could say "I need a VBox that compiles on 6.10". (But, > having said that, I suspect someone is going to tell me that my system > isn't vanilla, so I'm on my own.) > > korgie at gmail.com: I compiled 7.0.20 and it has been working just fine on > 6.10.3 (Slackware64 15.0). > > I agree that maintainers should not feel obligated to spend all day every > day chasing updates to the packages that they have graciously agreed to > support. But, on the flip side, perhaps occasionally, if someone needs a > newer version for some reason, it is also possible that they might be > motivated to do an update when requested. > > Anyway, now that you have pointed out Heinz' personal policy, I will know > to not ask again about this. > > Cheers. > Jim Hi Jim, I noticed Heinz provides a build script for current (that I haven't tested myself) on his personal repository https://repo.liwjatan.org/pprkut/current/source/virtualbox/ I don't know if it works on stable but it's worth a try... Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From pprkut at slackbuilds.org Wed Jan 15 21:38:30 2025 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Wed, 15 Jan 2025 22:38:30 +0100 Subject: [Slackbuilds-users] VBox slackbuild In-Reply-To: References: Message-ID: <2289369.vFx2qVVIhK@amaterasu.liwjatan.org> On Wednesday, 15 January 2025 21:43:42 CET Jim wrote: > On Wed, Jan 15, 2025 at 20:18 (+0000), Erich Ritz via SlackBuilds-users wrote: > > On Wednesday, January 15th, 2025 at 1:45 PM, Jim wrote: > >> Hi all, > >> > >> Back in November I emailed the Virtualbox Slackbuild maintainer, pointing > >> out that VBox was up to 7.1, whereas the Slackbuild is at 6.1.50. (And > >> since then, VBox is up to 7.1.4.) > >> > >> I never heard back. Is anyone in touch with the maintainer (Heinz > >> Wiesinger)? > > > > This was his comment last time an update request came up > > (https://lists.slackbuilds.org/pipermail/slackbuilds-users/2023-May/02817 > > 6.html): > > > > Is there a specific feature/bugfix you *need* from the newer version > > though? Generally, the version on SBo should work "just fine". If it's > > just about running the "latest and greatest", you should be able to fetch > > the SlackBuild from my -current or 15.0 repo (or even the packages). I > > don't typically update my scripts on SBo anymore unless there's a > > specific reason. > > *My* specific reason was that I updated to a newer kernel (6.10.3), because > I was having some glitchy issues with one of the components of my laptop. > And my info at the time was that versions before 7.0.16 would no longer > compile on 6.10 kernels. > > So I guess you could say "I need a VBox that compiles on 6.10". (But, > having said that, I suspect someone is going to tell me that my system > isn't vanilla, so I'm on my own.) > > korgie at gmail.com: I compiled 7.0.20 and it has been working just fine on > 6.10.3 (Slackware64 15.0). > > I agree that maintainers should not feel obligated to spend all day every > day chasing updates to the packages that they have graciously agreed to > support. But, on the flip side, perhaps occasionally, if someone needs a > newer version for some reason, it is also possible that they might be > motivated to do an update when requested. > > Anyway, now that you have pointed out Heinz' personal policy, I will know > to not ask again about this. Hi Jim, Sorry, your mail seems to have gotten lost in the noise. The past couple months have been unreasonably busy here. I do have a SlackBuild ready for 7.1.4 for -current in my own repo (not advertising that here though. I'm sure you can find that yourself with a bit of google-fu ;-) ), but that would need a couple tweaks to get it up on SBo. That said, I'm not particularly invested in updating to it for various reasons: 1) 6.x worked better. Nothing major, some minor issue here and there. Just enough to make me flinch though. 2) It depends on Qt6, which 15.0 doesn't ship stock and I don't want to depend on the SBo version. Now, 7.0.x could possibly avoid the dependency on Qt6, but it still leaves me with my impression of 6.x working better. Barring any major issues I'll thus stick to 6.x. The kernel incompatibility is unfortunate, but like you said, you kinda run in non-stock territory there. You're free to pick the -current script and use that though :-) Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part. URL: From zsd+slackbuilds at jdvb.ca Wed Jan 15 23:32:51 2025 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Wed, 15 Jan 2025 19:32:51 -0400 Subject: [Slackbuilds-users] VBox slackbuild In-Reply-To: <2289369.vFx2qVVIhK@amaterasu.liwjatan.org> Message-ID: A two-in-one reply, in hope of keeping this thread from exponentially expanding... On Wed, Jan 15, 2025 at 22:38 (+0100), Matteo Bernardini wrote: > Il giorno mer 15 gen 2025 alle ore 22:07 Jim ha > scritto: >> On Wed, Jan 15, 2025 at 20:18 (+0000), Erich Ritz via SlackBuilds-users >> wrote: >>> On Wednesday, January 15th, 2025 at 1:45 PM, Jim < >> zsd+slackbuilds at jdvb.ca> wrote: >>>> Hi all, > Hi Jim, > I noticed Heinz provides a build script for current (that I haven't tested > myself) on his personal repository > https://repo.liwjatan.org/pprkut/current/source/virtualbox/ > I don't know if it works on stable but it's worth a try... Hi Matteo, Thanks for pointing that out. What I didn't explicitly say before (when I mentioned I had already compiled 7.0.20) was that I had indeed used a SlackBuild to compile 7.0.20. The one I downloaded was from https://github.com/mdinslage/Custom_SlackBuilds On Wed, Jan 15, 2025 at 22:38 (+0100), Heinz Wiesinger wrote: > On Wednesday, 15 January 2025 21:43:42 CET Jim wrote: >> On Wed, Jan 15, 2025 at 20:18 (+0000), Erich Ritz via SlackBuilds-users > wrote: >>> On Wednesday, January 15th, 2025 at 1:45 PM, Jim > wrote: >>>> Hi all, >>>> Back in November I emailed the Virtualbox Slackbuild maintainer, pointing >>>> out that VBox was up to 7.1, whereas the Slackbuild is at 6.1.50. (And >>>> since then, VBox is up to 7.1.4.) >>>> I never heard back. Is anyone in touch with the maintainer (Heinz >>>> Wiesinger)? Hi Heinz, > Sorry, your mail seems to have gotten lost in the noise. The past couple > months have been unreasonably busy here. No problem. It didn't take me too long to get something up and running. > I do have a SlackBuild ready for 7.1.4 for -current in my own repo (not > advertising that here though. I'm sure you can find that yourself with a > bit of google-fu ;-) ), but that would need a couple tweaks to get it up > on SBo. That said, I'm not particularly invested in updating to it for > various reasons: > 1) 6.x worked better. Nothing major, some minor issue here and there. Just > enough to make me flinch though. Huh. I haven't noticed any unimprovements (fortunately). Having said that, these days I only use VirtualBox occasionally. > 2) It depends on Qt6, which 15.0 doesn't ship stock and I don't want to > depend on the SBo version. I was about to say "That is a very very good reason.". However, for my 7.0.20 ldd /usr/lib64/virtualbox/VirtualBox | grep Qt only shows libQt5 libraries. > Now, 7.0.x could possibly avoid the dependency on Qt6, but it still > leaves me with my impression of 6.x working better. Barring any major > issues I'll thus stick to 6.x. OK, that's fine. > The kernel incompatibility is unfortunate, but like you said, you kinda > run in non-stock territory there. You're free to pick the -current script > and use that though :-) Thanks very much, I appreciate you getting back with all this information. At this point 7.0.20 works for me, and I am not feeling the need to update just for the latest and greatest. Cheers. Jim From urchlay at slackware.uk Thu Jan 16 06:56:43 2025 From: urchlay at slackware.uk (B. Watson) Date: Thu, 16 Jan 2025 01:56:43 -0500 (EST) Subject: [Slackbuilds-users] VBox slackbuild In-Reply-To: <2289369.vFx2qVVIhK@amaterasu.liwjatan.org> References: <2289369.vFx2qVVIhK@amaterasu.liwjatan.org> Message-ID: <31e5697c-e317-32ff-26f8-2162fdd454d0@slackware.uk> On Wed, 15 Jan 2025, Heinz Wiesinger wrote: > 1) 6.x worked better. Nothing major, some minor issue here and there. Just > enough to make me flinch though. > > 2) It depends on Qt6, which 15.0 doesn't ship stock and I don't want to depend > on the SBo version. A thought: add the above explanation to your README. I've done that for a few of mine, when I'm deliberately keeping them at an older version for some reason. Saves time/effort, both for users and for yourself. From slackcoder at server.ky Thu Jan 16 17:37:52 2025 From: slackcoder at server.ky (Slack Coder) Date: Thu, 16 Jan 2025 12:37:52 -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: <71f76155-1931-4bfa-a9a3-4c312163165f@server.ky> Following up on this, the checksum check is failing for versions 13.37 to 14.1.? The 'weboob' package is missing from the checksums file. ``` (rsync -azq rsync://slackbuilds.org/slackbuilds/14.1 . ; cd 14.1; tail +13 CHECKSUMS.md5 | md5sum -c --quiet -;echo $?) md5sum: ./network/weboob.tar.gz: No such file or directory ./network/weboob.tar.gz: FAILED open or read md5sum: ./network/weboob.tar.gz.asc: No such file or directory ./network/weboob.tar.gz.asc: FAILED open or read md5sum: ./network/weboob/README: No such file or directory ./network/weboob/README: FAILED open or read md5sum: ./network/weboob/doinst.sh: No such file or directory ./network/weboob/doinst.sh: FAILED open or read md5sum: ./network/weboob/slack-desc: No such file or directory ./network/weboob/slack-desc: FAILED open or read md5sum: ./network/weboob/weboob.SlackBuild: No such file or directory ./network/weboob/weboob.SlackBuild: FAILED open or read md5sum: ./network/weboob/weboob.info: No such file or directory ./network/weboob/weboob.info: FAILED open or read md5sum: WARNING: 7 listed files could not be read ``` 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 > From willysr at slackbuilds.org Fri Jan 17 01:49:21 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 17 Jan 2025 08:49:21 +0700 Subject: [Slackbuilds-users] Slackbuilds and GPG In-Reply-To: <71f76155-1931-4bfa-a9a3-4c312163165f@server.ky> References: <1019b63a-c31f-4f1c-8a58-1f929d459f77@server.ky> <23b4620e-79f5-495a-a473-a2458ba57fce@slackbuilds.org> <71f76155-1931-4bfa-a9a3-4c312163165f@server.ky> Message-ID: > Following up on this, the checksum check is failing for versions 13.37 > to 14.1.? The 'weboob' package is missing from the checksums file. I'm not sure if earlier version should be updated at this point since we never touch that repository anymore -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3F617144D7238786.asc Type: application/pgp-keys Size: 8363 bytes Desc: OpenPGP public key URL: -------------- 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 Jan 18 01:25:27 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 18 Jan 2025 08:25:27 +0700 Subject: [Slackbuilds-users] Updates - 20250118.1 Message-ID: Sat Jan 18 01:14:20 UTC 2025 academic/fet: Updated for version 6.28.6. academic/ngspice: Updated for version 44.2. academic/plus42: Updated for version 1.1.17 academic/xcircuit: Update script. audio/ocp: Updated for version 3.0.1. audio/swh-plugins-lv2: Use working homepage. desktop/dunst: Updated for version 1.12.1 desktop/xwallpaper: Updated for version 0.7.5. development/SQLAlchemy: Updated for version 2.0.37. development/aws-cdk: Updated for version 2.175.1. development/aws-cdk: Updated for versoin 2.176.0. development/blassic: Use working download URL. development/dart-sass: Updated for version 1.83.4. development/gambas3: Updated for version 3.20.0. development/git-lfs: Updated for version 3.6.1. development/github-cli: Updated for version 2.65.0 development/mongodb-compass: Updated for version 1.45.1. development/opencomal: Updated for version 0.2.11. development/pcc: Use working download URLs. development/pcc: Use working homepage URL. development/pnpm: Updated for version 9.15.4. development/postman: Updated for version 11.27.3 development/tflint: Updated for version 0.55.0. development/yabasic: Updated for version 2.91.0 games/PrismLauncher: Updated for version 9.2. games/chexquest3: Use working homepage/download URLs. games/clksignal-roms: Use working download URLs. games/ds-models: Use working homepage URL. games/hatari: Use working download URL. games/jezzball-kazzmir: Use working homepage URL. games/nevernoid: Use working download URLs. games/sms_sdl: Use working download URL. games/vbam: Use working homepage URL. games/xspacewarp: Use working homepage/download URLs. gis/gdal: Updated for version 3.10.1. gis/google-earth: Updated for version 7.3.6.10155. gis/libspatialindex: Updated for version 2.1.0. gis/python3-xarray: Updated for version 2025.01.1. graphics/fbv: Updated for version 1.0c. graphics/pngcheck: Added (check integrity of PNG files). ham/SDRPlay: Update script. ham/qlog: Updated for version 0.41.0. ham/sdrpp: Updated for version 20250112.ea3675da. libraries/agar: Use working download URL. libraries/allegro4: Use working homepage URL. libraries/aunit: Added (Ada Unit test framework). libraries/florist: Added (POSIX Ada Bindings). libraries/libmirage: new maintainer libraries/libosinfo: Updated for version 1.12.0. libraries/libportal: Updated for version 0.8.1. libraries/libsoup3: Updated for version 3.6.3. libraries/libsoup3: Updated for version 3.6.4. libraries/libvirt-glib: Updated for version 5.0.0. libraries/libvirt-python: Updated for version 10.10.0. libraries/libvirt: Updated for version 10.10.0. libraries/notcurses: Updated for version 3.0.13. libraries/python3-ruamel.yaml: Updated for version 0.18.10. libraries/tclcurl-fa: Added (TCL access to libcurl). libraries/toml11: Update script. libraries/toml11: Updated to 4.3.0. libraries/virglrenderer: Updated for version 1.0.1. libraries/xapp: Updated for version 2.8.8 libraries/xview: Use working homepage URL. misc/bitwarden-desktop: updated for version 2025.1.1 multimedia/aegisub: Updated for version 3.4.2. multimedia/kodi: Version bump to 21.2 multimedia/minidlna: Fixed run-time var data path. multimedia/opera-ffmpeg-codecs: Updated for version 0.94.1. network/acme.sh: Updated for version 3.1.0. network/aerc: Updated for version 0.19.0. network/deskflow: Added (upstream project for Synergy). network/discord: Version bump to 0.0.80 network/dnsproxy-bin: Updated for version 0.74.1. network/dog: Use working homepage. network/ircII: Use working homepage URL. network/jitsi-meet-desktop: Updated for version 2025.1.1 network/lighttpd: Updated for version 1.4.77. network/neomutt: Updated for version 20250113. network/opera: Updated for version 116.0.5366.35. network/scapy: Update script. network/signal-desktop: Updated for version 7.38.0. network/synergy: Removed (Move to deskflow). network/udpbench: Updated for version 1.12. network/vesktop: Added (Custom Discord). network/vesktop: Update script. network/whalebird: Updated for version 6.2.0 network/wp-cli: Updated for version 2.11.0. network/yt-dlp-bin: Updated for version 2025.01.12. network/yt-dlp: Updated for version 2025.01.15. network/zoom-linux: Updated for 6.3.6.6315 office/gnucash: Update script. office/lowdown: Updated to 1.3.2. office/lyx: Updated for version 2.4.3. office/mobiperl: Use working download URL. office/mobiperl: Use working homepage URL. python/click: Updated for version 8.1.8. python/cppy: Version bump to 1.3.0 python/git-fame: Correctly use setuptools-opt. python/jellyfish: Updated for version 1.1.3. python/mypy: Updated for version 1.14.1. python/pyOpenSSL: Updated for version 25.0.0. python/pygsl: Updated for version 2.5.1. python/pyscard: Updated for version 2.2.1. python/python-unicodedata2: Updated for version 16.0.0. python/python2-psutil: Updated for version 6.1.1. python/python3-aiorpcX: Updated for version 0.23.1. python/python3-aniso8601: Updated for version 10.0.0. python/python3-flit: Fix build to use flit_core. python/python3-gast: Update README note python/python3-glances: Updated for version 4.3.0.8. python/python3-libtmux: Updated for version 0.40.1. python/python3-maturin: Updated for version 1.8.1. python/python3-more-itertools: Updated for version 10.6.0. python/python3-orjson: Updated for version 3.10.14. python/python3-pdm: Version bump to 2.22.2 python/python3-plexapi: Updated to 4.16.1. python/python3-poetry-core: Updated for version 2.0.1. python/python3-psutil: Updated for version 6.1.1. python/python3-pulsectl: Updated to 24.12.0. python/python3-pydantic-core: Updated for version 2.27.2. python/python3-pydantic: Updated for version 2.10.5. python/python3-pysdl2: Updated to 0.9.17. python/python3-pythran: Add README note for pinned version python/python3-setuptools-opt: Updated for version 75.8.0. python/python3-tekore: Updated to 6.0.0. python/python3-tempora: Updated for version 5.8.0. python/python3-tomli_w: Updated for version 1.2.0. python/python3-trove-classifiers: Updated for version 2025.1.15.22. python/python3-virtualenv: Version bump to 20.29.0 ruby/ruby-build: Updated for version 20250115. system/B-em: Updated for version 20250101_8c0c1e4 system/Solaar: Add missing dep. system/alacritty: Updated for version 0.15.0. system/archivemount: Use working download URL. system/cdemu-client: new maintainer system/cdemu-daemon: new maintainer system/csh: Updated for version 20240808_2. system/dget: Updated for version 2.24.10. system/docker-compose: Updated for version 2.32.3 system/epson-inkjet-printer-escpr2: Updated for version 1.2.25. system/gcdemu: new maintainer system/image-analyzer: new maintainer system/jstest-gtk: Added (joystick tester). system/k3s: Updated for 1.32.0.1. system/locust: Updated for version 2.32.6. system/man-pages-ja: Use working download URL. system/man-pages-ja: Use working homepage URL. system/nix: Fix update. system/openzfs: updated for version 2.3.0 system/osinfo-db-tools: Updated for version 1.12.0. system/osinfo-db: Updated for version 20240701. system/pkg: Updated for version 0.2.0. system/sbokeeper: Updated for version 2.03. system/sdl-jstest: Updated for version 0.2.2+20240331_60f6e62. system/timeshift: Updated for version 24.06.6 system/tmuxp: Updated for version 1.50.1. system/usbmon: Use working homepage URL. system/usbredir: Updated for version 0.14.0. system/vcp: Use working homepage URL. system/vhba-module: new maintainer system/virt-manager: Updated for version 5.0.0, switch to meson. system/xar: Use working homepage URL. +--------------------------+ -- 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 Jan 18 14:39:22 2025 From: fsleg at t-rg.ws (fsLeg) Date: Sat, 18 Jan 2025 17:39:22 +0300 Subject: [Slackbuilds-users] Request to overtake gxkb and yubioath-desktop Message-ID: <31a0e4ee-e430-488c-be89-d48062a5ff14@t-rg.ws> SBo has outdated versions of desktop/gxkb and misc/yubioath-desktop. I emailed both maintainers back on 2025-01-01 and haven't got any response. The maintainer of gxkb is NK. According to cgit, his first contribution was on 2015-02-09, and 2015 was when he was the most active. Then there were a few updates here and there over the years with last contribution being on 2021-01-15. The maintainer of yubioath-desktop is Spycrowsoft. They had only two contributions, on 2020-05-16 and 2020-06-01, both regarding this SlackBuild. Current gxkb version is 0.9.6, while SBo has 0.8.2. Current yubioath-desktop (aka yubico-authenticator) is 7.1.1, while SBo has 5.1.0. I've had both SlackBuilds in my private repo for a while now. I'm requesting to take maintainership of these SlackBuilds. From lramos.prof at yahoo.com.br Sun Jan 19 19:24:18 2025 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Sun, 19 Jan 2025 16:24:18 -0300 Subject: [Slackbuilds-users] Updates - 20250111.1 In-Reply-To: References: Message-ID: Hello, here, when trying to build ngspice, an error happened when trying to chmod files at ${PKG}/usr/doc/ngspice-42/examples/klu/Circuits/libraries. The problem was easy to fix: it relies on the "ngspice-42" part of the directory, which doesn't match the newer version, 44.2. So, in short, it would be nspice-44.2 instead of ngspice. I managed to change it to "ngspice-${VERSION}", using the fact that this env variable would match the product version and one would expect that this rule will be followed by the upstream developers. Below a patch which does that is suggested as a fix. Many thanks and have a happy new year. Luiz Ramos S?o Paulo - Brazil lramos.prof at yahoo.com.br --- patch --- >From 4d907a9a3a5ebfd791169d8a93ea9524da5009c0 Mon Sep 17 00:00:00 2001 From: Luiz Ramos Date: Sun, 19 Jan 2025 16:11:58 -0300 Subject: [PATCH] academic/ngspice: fixed build script The previous version of the build script tried to change mod from files considering version 42. This updated version makes this command flexible, using the ${VERSION} variable to match the directory name. --- academic/ngspice/ngspice.SlackBuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/academic/ngspice/ngspice.SlackBuild b/academic/ngspice/ngspice.SlackBuild index ddda42d7de2936fb9215ddbf75973cf1586a9921..cc25f3320673ef4dd0e1fe908251c2dd0b24ac9a 100644 --- a/academic/ngspice/ngspice.SlackBuild +++ b/academic/ngspice/ngspice.SlackBuild @@ -134,7 +134,7 @@ ln -s "libngspice.so.0.0.12" "$PKG/usr/lib${LIBDIRSUFFIX}/libngspice.so" install -Dm644 ./src/include/ngspice/sharedspice.h $PKG/usr/include/ngspice/sharedspice.h # Move the configure output file. mv $TMP/$PRGNAM-$VERSION/release/src/include/ngspice/config.h $PKG/usr/include/ngspice/ -chmod 644 $PKG/usr/doc/ngspice-42/examples/klu/Circuits/libraries/*.lib +chmod 644 $PKG/usr/doc/ngspice-${VERSION}/examples/klu/Circuits/libraries/*.lib install -Dm644 $CWD/$PRGNAM.png $PKG/usr/share/icons/hicolor/48x48/apps/$PRGNAM.png -- 2.46.3 --- patch --- On Sat, Jan 11, 2025 at 08:50:10AM +0700, Willy Sudiarto Raharjo wrote: > Sat Jan 11 01:44:22 UTC 2025 > academic/cdo: Updated for version 2.5.0. > academic/nco: Updated for version 5.3.0. > academic/units: Updated for version 2.24. > academic/vul: Updated for version 20230314_10d9d61. > desktop/SiriKali: Updated for version 1.8.0. > desktop/numix-icon-theme-circle: Updated for version 24.12.12. > desktop/numix-icon-theme: Updated for version 24.12.12. > desktop/pcb2gcodeGUI: Added (GUI for pcb2gcode). > development/actionlint: Updated for version 1.7.6. > development/aws-cdk: Updated for version 2.174.0. > development/aws-cdk: Updated for version 2.175.0. > development/dart-sass: Updated for version 1.83.1. > development/dkms: Include autoinstaller > development/dpkg: Updated for version 1.22.13. > development/jupyter-ipywidgets: Added (HTML widgets for Jupyter). > development/jupyter-widgetsnbextension: Added (Interactive widget for > Jupyter). > development/meld3: Updated for version 3.22.3. > development/mold: Updated for version 2.36.0. > development/obsidian: updated for version 1.7.7 > development/php84: Added (Scripting Language). > development/pnpm: Updated for version 9.15.3. > development/protobuf3: Updated for version 29.3. > games/attract: Added (Frontend for emulators). > games/ddnet: updated for version 18.9. > games/steamtinkerlaunch: New maintainer > gis/eccodes: Updated for version 2.39.0. > gis/gdal: Updated for version 3.10.0. > gis/python3-xarray: Updated for version 2025.01.0 > graphics/paraview: Updated for version 5.13.2 > graphics/yacreader: Updated for version 9.15.0. > libraries/pugixml: Updated for version 1.15. > multimedia/QMPlay2: Updated for version 24.12.28. > multimedia/aegisub: Updated for version 3.4.1. > network/bitcoin: Updated for version 28.1. > network/discord: Version bump to 0.0.79 > network/dropbox: Updated for version 215.4.7202. > network/gallery-dl: Updated for version 1.28.3. > network/netsniff-ng: Updated for version 0.6.9. > network/newsraft: Updated for version 0.28. > network/shadowsocks-rust: Updated for version 1.22.0. > network/signal-desktop: Update for version 7.37.0. > network/syncthingtray-bin: Updated for version 1.7.1. > network/teamviewer: Updated for version 15.61.3. > network/telegram: Updated for version 5.10.1. > network/telegram: Updated for version 5.10.3. > network/tor-browser: Updated for version 14.0.4. > network/vivaldi: Updated for version 7.0.3495.29. > network/wireshark: Updated for version 4.4.3. > network/zoom-linux: Updated for 6.3.5.6065 > office/gnucash-docs: Updated for version 5.10. > office/gnucash: Updated for version 5.10. > office/pdfpc: Updated for version 4.7.0 > python/pyrfc3339: Updated for version 2.0.1. > python/python3-aiohttp-socks: Updated for version 0.10.1. > python/python3-anyio: Version bump to 4.8.0 > python/python3-cachecontrol: Version bump to 0.14.2 > python/python3-identify: Updated for version 2.6.5. > python/python3-kiwisolver: Version bump to 1.4.8 > python/python3-poetry-dynamic-versioning: Updated for version 1.6.0. > python/python3-socks: Updated for version 2.6.1. > python/python3-soundfile: Version bump to 0.13.0 > python/python3-virtualenv: Version bump to 20.28.1 > python3/python3-poetry-dynamic-versioning: Updated for v 1.5.0. > ruby/rbenv: Updated for version 1.3.2. > system/CNS11643-kai-font: Updated for version 20241216. > system/CNS11643-sung-font: Updated for version 20241216. > system/bat: Updated for version 0.25.0. > system/docker-compose: Updated for version 2.32.2 > system/fastfetch: Updated for version 2.34.0. > system/jenkins: Updated for version 2.479.3. > system/letsencrypt: Updated for version 3.1.0. > system/netdata: Updated for version 2.1.1. > system/sbokeeper: Updated for version 2.02. > +--------------------------+ > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From willysr at slackbuilds.org Wed Jan 22 14:29:13 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 22 Jan 2025 21:29:13 +0700 Subject: [Slackbuilds-users] Request to overtake gxkb and yubioath-desktop In-Reply-To: <31a0e4ee-e430-488c-be89-d48062a5ff14@t-rg.ws> References: <31a0e4ee-e430-488c-be89-d48062a5ff14@t-rg.ws> Message-ID: <8c38a773-4177-456e-8185-b257bc4f2a1f@slackbuilds.org> > SBo has outdated versions of desktop/gxkb and misc/yubioath-desktop. I > emailed both maintainers back on 2025-01-01 and haven't got any response. > > The maintainer of gxkb is NK. According to cgit, his first contribution > was on 2015-02-09, and 2015 was when he was the most active. Then there > were a few updates here and there over the years with last contribution > being on 2021-01-15. > > The maintainer of yubioath-desktop is Spycrowsoft. They had only two > contributions, on 2020-05-16 and 2020-06-01, both regarding this > SlackBuild. > > Current gxkb version is 0.9.6, while SBo has 0.8.2. > > Current yubioath-desktop (aka yubico-authenticator) is 7.1.1, while SBo > has 5.1.0. > > I've had both SlackBuilds in my private repo for a while now. I'm > requesting to take maintainership of these SlackBuilds. Feel free to take over -- 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 Thu Jan 23 14:25:42 2025 From: slackcoder at server.ky (Slack Coder) Date: Thu, 23 Jan 2025 09:25:42 -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> <71f76155-1931-4bfa-a9a3-4c312163165f@server.ky> Message-ID: <6dbb6261-6c4a-4079-bddc-bf05b069e484@server.ky> On 1/16/25 20:49, Willy Sudiarto Raharjo wrote: >> Following up on this, the checksum check is failing for versions >> 13.37 to 14.1.? The 'weboob' package is missing from the checksums file. > > I'm not sure if earlier version should be updated at this point since > we never touch that repository anymore The thing is, it appears it was updated later but incorrectly.? I don't know the history for the weboob package, maybe it was malware so it was removed from the filesystem? Case in point, the git branches contain the problematic package. ``` (git clone https://git.slackbuilds.org/slackbuilds; cd slackbuilds;git checkout 14.1; find . -name 'weboob') # [..] # branch '14.1' set up to track 'origin/14.1'. # Switched to a new branch '14.1' # ./network/weboob ``` From urchlay at slackware.uk Thu Jan 23 21:50:27 2025 From: urchlay at slackware.uk (B. Watson) Date: Thu, 23 Jan 2025 16:50:27 -0500 (EST) Subject: [Slackbuilds-users] Slackbuilds and GPG In-Reply-To: <6dbb6261-6c4a-4079-bddc-bf05b069e484@server.ky> References: <1019b63a-c31f-4f1c-8a58-1f929d459f77@server.ky> <23b4620e-79f5-495a-a473-a2458ba57fce@slackbuilds.org> <71f76155-1931-4bfa-a9a3-4c312163165f@server.ky> <6dbb6261-6c4a-4079-bddc-bf05b069e484@server.ky> Message-ID: <78aa73bc-ad43-f0c2-e23e-7e77d64adda@slackware.uk> On Thu, 23 Jan 2025, Slack Coder wrote: > The thing is, it appears it was updated later but incorrectly.? I don't > know the history for the weboob package, maybe it was malware so it was > removed from the filesystem? >From within the git tree, you can: git log -- network/weboob I see: commit 8146c4a1ff57855a9c459f255e4eda67ee6b64d2 Author: Willy Sudiarto Raharjo Date: Sat Dec 5 23:46:26 2020 +0700 network/weboob: Removed (requested by maintainer). It wasn't removed from the 14.1 branch, but it was from 14.2. Maybe that was a mistake, it should have been removed from the 14.1 branch too? ...but, do we really have to care about 14.1 perpetually from now until the end of time? Pat V has EOLed 14.1, see the ChangeLog: http://ftp.osuosl.org/pub/slackware/slackware-14.1/ChangeLog.txt So, we keep the old branches around for historical reference, but if something minor is wrong, do we really have to spend time/effort fixing it? We don't e.g. update download URLs in the 14.1 .info files. From willysr at slackbuilds.org Sat Jan 25 02:12:22 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 25 Jan 2025 09:12:22 +0700 Subject: [Slackbuilds-users] Updates - 20250125.1 Message-ID: <19e36f83-c549-4d18-8068-2ceb3c8f90b9@slackbuilds.org> Sat Jan 25 02:05:05 UTC 2025 academic/fet: Updated for version 7.0.0. academic/ngspice: Fix version. academic/plus42: Updated for version 1.1.17b academic/tiemu: gzip patches (CRLF endings). accessibility/svkbd: Updated for version 0.4.2. audio/butt: Updated for version 1.44.0 + New maintainer desktop/gxkb: Updated for version 0.9.6. desktop/xtrlock: Updated for version 2.16. development/actionlint: Updated for version 1.7.7. development/cargo-vendor-filterer: Updated for version 0.5.17. development/composer: Updated for version 2.8.5 development/dpkg: Updated for version 1.22.14. development/idea: Updated for version 2024.3.2.1. development/mdbook: Updated to 0.4.43. development/minikube: Updated for version 1.35.0. development/php84: Updated for version 8.4.3 development/postman: Updated for version 11.28.4 development/pre-commit: Updated for version 4.1.0. development/pycharm: Updated for version 2024.3.1.1.243.22562.220. development/robotframework: Updated for version 7.2. development/rust-opt: Updated for version 1.84.0. development/terraform-ls: Updated for version 0.36.4. development/vscode-bin: Updated for version 1.96.4. development/vstudio: Updated for version 14.7.1 development/xxd-standalone: Updated for version 9.1.1045. games/ZEsarUX: Updated for version 12.0 games/aklabeth: gzip patches (CRLF endings). games/gzdoom-legacy: gzip patches (CRLF endings). games/o2em: gzip patches (CRLF endings). games/steamtinkerlaunch: Version bump to 12.12 games/xroar: Updated for version 1.7.3. games/xu4: Updated for version 1.4.2. gis/google-earth: Updated for version 7.3.6.10201. graphics/converseen: Updated for version 0.12.2.5. graphics/meh: Fix spurious GIFLIB: (null), fix imagemagick. graphics/vuescan: Updated MD5SUM_x86_64. ham/SDRPlay: Update script. ham/SoapySDRPlay: Mark x86_64 only. ham/hamlib4: Updated for version 4.6.1. ham/qlog: Updated for version 0.41.1. libraries/eduvpn-common: Added (eduvpn client library). libraries/gupnp: Updated for version 1.6.8. libraries/libdatachannel: Added (C/C++ WebRTC network library). libraries/libjuice: Added (UDP Library). libraries/libpaper: Updated for version 2.2.6. libraries/libtorrent: Updated for version 0.15.1. libraries/libwpe: Updated for version 1.16.1. libraries/ode: Updated for version 0.16.6. libraries/qwt: Updated for version 6.3.0 libraries/skalibs: Updated for version 2.14.3.0 misc/pam-u2f: Updated for version 1.3.2. misc/vttest: Updated for version 2.7.20241208. misc/yubioath-desktop: Updated for version 7.1.1. multimedia/QMPlay2: Updated for version 25.01.19. multimedia/inputstream.adaptive: Version bump to 21.5.9 multimedia/kodi: Remove "v" from tag since it no longer works multimedia/videomass: Updated for version 5.0.25. multimedia/youtube-music: Updated for version 3.7.2. network/AdGuardHome: Updated for version 0.107.56. network/betterbird-bin: Fix permission. network/betterbird-bin: Updated for version 128.6.1esr. network/broadcom-wl: Updated for kernel 6.13. network/deskflow: Add REQUIRES libportal network/dillo: Updated for version 3.2.0. network/discord: Version bump to 0.0.81 network/dropbox: Updated for version 216.4.4420. network/eduvpn: Added (eduvpn client application). network/lagrange: Updated for version 1.18.4. network/mailspring: Updated for version 1.15.0 network/mullvadvpn-app: Updated for version 2025.2. network/phpmyadmin: Updated for version 5.2.2. network/rtorrent: Updated for version 0.15.1. network/rustdesk-opt: Added (remote access/control software). network/signal-desktop: Updated for version 7.39.0. network/syncterm: Updated for version 1.4. network/synochat: Added (Synology Chat Client). network/telegram: Updated for version 5.10.5. network/teleport-connect: Updated for version 17.2.2. network/udsclient3: Added (UDS Client). network/vivaldi: Updated for version 7.1.3570.39. network/weechat: Updated for version 4.5.1. office/kitscenarist: Added (screenplay authoring tool). office/lowdown: Updated to 1.4.0. office/re-typeset: gzip patches (CRLF endings). perl/perl-Net-Curl: Updated for version 0.57. python/josepy: Updated for version 1.15.0. python/python-importlib_metadata: Updated for version 8.6.1. python/python3-cachetools: Version bump to 5.5.1 python/python3-executing: Version bump to 2.2.0 python/python3-filelock: Version bump to 3.17.0 python/python3-identify: Updated for version 2.6.6. python/python3-orjson: Updated for version 3.10.15. python/python3-poetry-dynamic-versioning: Updated for version 1.7.0. python/python3-pydantic: Updated for version 2.10.6. python/python3-pyproject-api: Version bump to 1.9.0 python/python3-setuptools-git-versioning: Updated for version 2.1.0. python/python3-setuptools-opt: Remove dep. python/python3-tomli-opt: Added (TOML Parser). python/python3-tox: Version bump to 4.24.1 python/python3-virtualenv: Version bump to 20.29.1 python/tzdata: Updated for version 2025.1. ruby/ruby-build: Updated for version 20250121. system/B-em: Updated for version 20250116_2b5fe8e system/FreeFileSync: Updated for version 14.0 system/Iosevka-aile: Updated for version 32.4.0. system/Iosevka-etoile: Updated for version 32.4.0. system/clamav: Updated for version 1.4.2. system/distrobox: Updated for version 1.8.1. system/distrobox: Updated for version 1.8.1.1. system/docker-buildx: Updated for version 0.20.1. system/docker-compose: Updated for version 2.32.4 system/epson-inkjet-printer-escpr2: Updated for version 1.2.26. system/execline: Updated for version 2.9.6.1 system/gnsu: Added (grahical frontend for sudo). system/kubectx: Added (Power tools for kubectl). system/locust: Updated for version 2.32.5. system/nerdctl: Updated for version 2.0.3 system/peazip: Remove README in .info. system/pkg: Updated for version 0.4.0. system/quivira-font: Added (OpenType Font). system/s-tui: Added (Monitoring System). system/s-tui: Update deps. system/s6-linux-init: Updated for version 1.1.2.1 system/s6-rc: Updated for version 0.5.5.0 system/s6: Updated for version 2.13.1.0 system/sbotools: Updated for version 3.4. system/slpkg: Updated for version 5.1.7. system/slpkg: Updated for version 5.1.8. system/telegraf: Updated for version 1.33.1 system/vice: Updated for version 3.9. +--------------------------+ -- 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 erich.public at protonmail.com Tue Jan 28 19:39:14 2025 From: erich.public at protonmail.com (Erich Ritz) Date: Tue, 28 Jan 2025 19:39:14 +0000 Subject: [Slackbuilds-users] Updates - 20250125.1 In-Reply-To: <19e36f83-c549-4d18-8068-2ceb3c8f90b9@slackbuilds.org> References: <19e36f83-c549-4d18-8068-2ceb3c8f90b9@slackbuilds.org> Message-ID: <4qcey9BLr3dBjkDGR2Do8mKkDvzA3wF67Avu0nK5DsThUG9JtRTpS_qmrQi3cYNxdw3Z1F78W2C0kIULsH6hn6mO9Iz5zgvLuGACpP0lD8A=@protonmail.com> On Friday, January 24th, 2025 at 8:12 PM, Willy Sudiarto Raharjo wrote: > > > Sat Jan 25 02:05:05 UTC 2025 > ... > network/rustdesk-opt: Added (remote access/control software). > ... > +--------------------------+ > > What is the purpose of having both rustdesk and rustdesk-opt? Erich From erich.public at protonmail.com Tue Jan 28 19:44:50 2025 From: erich.public at protonmail.com (Erich Ritz) Date: Tue, 28 Jan 2025 19:44:50 +0000 Subject: [Slackbuilds-users] Updates - 20250125.1 In-Reply-To: <19e36f83-c549-4d18-8068-2ceb3c8f90b9@slackbuilds.org> References: <19e36f83-c549-4d18-8068-2ceb3c8f90b9@slackbuilds.org> Message-ID: On Friday, January 24th, 2025 at 8:12 PM, Willy Sudiarto Raharjo wrote: > > > Sat Jan 25 02:05:05 UTC 2025 > ... > python/python3-setuptools-opt: Remove dep. > ... > +--------------------------+ > > cppy and python3-maturin both fail to build due to missing dep python3-wheel, I guess because of this commit: https://git.slackbuilds.org/slackbuilds/commit/?id=d7acfaba5d45ce71b24f4f276a6f8726565430e2 Guys, don't rely on deps of deps to cover your direct dependencies! (only my humble opinion, of course) Erich > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ From fourtysixandtwo at sliderr.net Tue Jan 28 19:57:23 2025 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Tue, 28 Jan 2025 12:57:23 -0700 Subject: [Slackbuilds-users] Updates - 20250125.1 In-Reply-To: References: <19e36f83-c549-4d18-8068-2ceb3c8f90b9@slackbuilds.org> Message-ID: > python/python3-setuptools-opt: Remove dep. Willy has reverted that commit for the next update. It shouldn't have made it through my testing, but I made a mistake. Sorry for the hassle. On Tue, Jan 28, 2025 at 12:44?PM Erich Ritz via SlackBuilds-users wrote: > > On Friday, January 24th, 2025 at 8:12 PM, Willy Sudiarto Raharjo wrote: > > > > > > > Sat Jan 25 02:05:05 UTC 2025 > > ... > > python/python3-setuptools-opt: Remove dep. > > ... > > +--------------------------+ > > > > > > cppy and python3-maturin both fail to build due to missing dep python3-wheel, I guess because of this commit: https://git.slackbuilds.org/slackbuilds/commit/?id=d7acfaba5d45ce71b24f4f276a6f8726565430e2 > > Guys, don't rely on deps of deps to cover your direct dependencies! (only my humble opinion, of course) > > Erich > > > -- > > Willy Sudiarto Raharjo > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From ozan.turkyilmaz at gmail.com Fri Jan 31 15:21:08 2025 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Fri, 31 Jan 2025 18:21:08 +0300 Subject: [Slackbuilds-users] Gitlab is forgotten Message-ID: Hey Guys, Did you forget the gitlab merge requests? Regards, Ozan -------------- next part -------------- An HTML attachment was scrubbed... URL: