From willysr at slackbuilds.org Thu Feb 1 00:48:45 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 1 Feb 2024 07:48:45 +0700 Subject: [Slackbuilds-users] dnsproxy uid/gid In-Reply-To: References: Message-ID: <0a587d8d-9247-4e4c-853d-b6040ffa3d84@slackbuilds.org> > I'm writing a dnsproxy SlackBuild, which needs a dnsproxy user. Can I > use 383 for it? please use 384 i forgot to update 383 is for smokeping -- Willy Sudiarto Raharjo From zsd+slackbuilds at jdvb.ca Fri Feb 2 14:01:41 2024 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Fri, 2 Feb 2024 10:01:41 -0400 Subject: [Slackbuilds-users] virtualbox slackbuilds Message-ID: All, I recently started running the 6.6.12 kernel. All (well, everything I use) is working except virtualbox-kernel, which won't compile on that kernel. Looking on the web, I see the particular problem I'm having has been fixed in newer versions of virtualbox. I see that aside from 6.1.55, there is also 7.0.14. I emailed the maintainer on Monday, but haven't heard back. Maybe he's away, and that's fine, but I was wondering if anyone has been in touch with him recently. Anyone? Jim From ltlnx at disroot.org Fri Feb 2 19:03:04 2024 From: ltlnx at disroot.org (=?UTF-8?B?6auY5paH5YGJ?=) Date: Sat, 03 Feb 2024 03:03:04 +0800 Subject: [Slackbuilds-users] virtualbox slackbuilds In-Reply-To: References: Message-ID: Hi Jim, Some others and I have been waiting too, as seen in this thread (https://www.linuxquestions.org/questions/slackware-14/building-virtualbox-7-on-slackware-15-a-4175727199/) and this thread (https://www.linuxquestions.org/questions/slackware-14/building-virtualbox-kernel-slackbuild-for-6-6-x-kernel-branch-4175731627/). You can try suggestions in both, I also weighed in but currently I'll recommend Daedra's scripts (https://github.com/mdinslage/Custom_SlackBuilds/tree/main/virtualbox-7.0.12) in the former post. -- ltlnx -------------- next part -------------- An HTML attachment was scrubbed... URL: From slack at giand.it Fri Feb 2 23:17:34 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Sat, 3 Feb 2024 00:17:34 +0100 Subject: [Slackbuilds-users] virtualbox slackbuilds In-Reply-To: References: Message-ID: Il 02/02/24 15:01, Jim ha scritto: > All, > > I recently started running the 6.6.12 kernel. All (well, everything I use) > is working except virtualbox-kernel, which won't compile on that kernel. > > Looking on the web, I see the particular problem I'm having has been fixed > in newer versions of virtualbox. I see that aside from 6.1.55, there is > also 7.0.14. > > I emailed the maintainer on Monday, but haven't heard back. Maybe he's > away, and that's fine, but I was wondering if anyone has been in touch with > him recently. > > Anyone? > > Jim In current I used VB 6.1.32 for a long time and solved issues due last updates of the kernel using a patch. It works fine, but the recent upgrade of libvpx has required the rebuild of virtualbox driver. This has brought many problems and some day ago I decided to use the slackbuild of Daedra for virtualbox 7.0.12. In Slackware current It works and should also work with VB 7.0.14. https://github.com/mdinslage/Custom_SlackBuilds/tree/main/virtualbox-7.0.12 You have to do the following things: 1) if you require the software virtualization install the multilib of AlienBob 2) if you have an installation of Java 11 or earlier, downgrade to Java 8 because the build of VirtualBox needs wsimport (droppend since Java 11). It is required only for the build: next time you can upgrade to earlier version of JDK The installation of gsoap and acpica from SBo's slackbuilds are fully compatible. This happened in current, I don't know if there are problems with Slackware 15.0 - ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Feb 3 01:36:02 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 3 Feb 2024 08:36:02 +0700 Subject: [Slackbuilds-users] Updates - 20240203.1 Message-ID: Sat Feb 3 01:09:59 UTC 2024 academic/STAR:Upgrade to version 2.7.11b academic/gaiasky: Updated for version 3.5.8. academic/ngspice: Point the chmod to the correct directory. academic/samtools: Upgrade to version 1.19.2 audio/linuxsampler: Updated for version 2.3.0. audio/plug: Fix permission. desktop/gopsuinfo: Updated for version 0.1.6. desktop/nwg-bar: Updated for version 0.1.6. desktop/nwg-clipman: Updated for version 0.2.1. desktop/nwg-displays: Updated for version 0.3.13. desktop/nwg-hello: Updated for version 0.1.7. desktop/nwg-icon-picker: Updated for version 0.1.1. desktop/nwg-panel: Updated for version 0.9.22. desktop/nwg-readme-browser: Added (NWG Browser). desktop/nwg-shell-config: Updated for version 0.5.32. desktop/nwg-shell-wallpapers: Updated for version 1.4. desktop/nwg-shell: Updated for version 0.5.31. desktop/papirus-icon-theme: Updated for version 20240201. development/aws-cdk: Updated for version 2.126.0. development/ghidra: Updated for version 11.0.1 development/github-cli: Updated for version 2.43.0 development/gnustep-base: Patched for libxml2 >= 2.11.x. development/jupyter-ipykernel: Update for 6.29.0 development/jupyter-nbconvert: Update for 7.14.2 development/mongodb-compass: Updated for version 1.42.0. development/pycharm: Updated for version 2023.3.3.233.13763.11. development/roswell: Updated for version 23.10.14.114. development/tofuenv: Updated for version 1.0.5. development/vscode-bin: Updated for version 1.86.0. games/7kaa: Updated for version 2.15.6. games/endless-sky: updated for version 0.10.5 games/vcmi: updated for version 1.4.5 games/wolfmame: Updated for version 0.262. graphics/tuxpaint-stamps: Updated for version 2024.01.29. graphics/tuxpaint: Updated for version 0.9.32. graphics/vuescan: Updated MD5SUMs. ham/redsea: Updated for version 0.21. libraries/SFML: Updated for version 2.6.1. libraries/SOPE: Fix DOWNLOAD. libraries/exiftool: Updated for version 12.76. libraries/htslib: Upgrade to version 1.19.1 libraries/isodate: Removed (replaced by python3-isodate). libraries/libgig: Updated for version 4.4.0. libraries/libpaper: Updated for version 2.1.3. libraries/nghttp3: Updated for version 1.1.0. libraries/ngtcp2: Updated for version 1.2.0. libraries/pexpect: Updated for version 4.9.0. misc/fcitx5-chinese-addons: Updated for version 5.1.3. misc/fcitx5-configtool: Updated for version 5.1.3. misc/fcitx5-gtk: Updated for version 5.1.1. misc/fcitx5-qt: Updated for version 5.1.4. misc/fcitx5-table-extra: Updated for version 5.1.3. misc/fcitx5: Updated for version 5.1.7. misc/libime: Updated for version 1.1.5. misc/open-simh: Fix permission. misc/tinytldr: Updated for version 1.1.3 multimedia/strawberry: Updated for version 1.0.23. multimedia/vlc: Updated for version 3.0.20. network/armcord: Updated for version 3.2.6. network/curl-quic: Updated for version 8.6.0. network/dnsproxy-bin: Added (DNS Proxy). network/opera: Updated for version 106.0.4998.70. network/qutebrowser-bin: Update components. network/rspamd: Updated for version 3.8.1 network/signal-desktop: Updated for version 6.46.0. network/slack: Fix .info. network/slack: Updated for version 4.35.140. network/telegram: Updated for version 4.14.12. network/tut: Added (mastodon CLI). network/vivaldi: Updated for version 6.5.3206.59. network/whalebird: Update for 6.0.1 network/youtube-dl: Updated for version 2021.12.17+20240122_dc512e3a8. office/SOGo: Fix DOWNLOAD. office/atril: Updated for version 1.26.2. office/hebcal: Updated for version 5.8.4. office/libreoffice-helppack: Updated for version 24.2.0. office/libreoffice-langpack: Updated for version 24.2.0. office/libreoffice: Updated for version 24.2.0. office/onlyoffice-desktopeditors: Updated for version 8.0.0. perl/perl-Linux-FD: Updated for version 0.016. python/pyOpenSSL: Updated for version 24.0.0. python/python3-aiohttp: Updated for version 3.9.3. python/python3-daemon: Added (Python Daemon). python/python3-isodate: Added (ISO Date). python/python3-multidict: Updated for version 6.0.5. python/python3-overrides: Update for 7.7.0 system/B-em: Fix permission. system/Iosevka-aile: Updated for version 28.0.7. system/Iosevka-etoile: Updated for version 28.0.7. system/Iosevka-slab: Updated for version 28.0.7. system/Iosevka: Updated for version 28.0.7. system/OpenSnitch: Edit SlackBuild system/cyberjack: Added (Smart Card Devices driver). system/docker-compose: Updated for version 2.24.5 system/fastfetch: Updated for version 2.7.0. system/fonts-arabic-extra: Added (system fonts). system/fonts-farsi-extra: Added (system fonts). system/fonts-nastaliq: Added (system fonts). system/fzf: Updated for version 0.46.1. system/kitty: Updated for version 0.32.1 system/limine: Updated for version 7.0.2 system/locust: Updated for version 2.21.0. system/logwatch: Updated for version 7.10. system/lxgw-wenkai-fonts: Updated for version 1.315. system/prometheus: Updated to version 2.49.1 system/readpe: Updated for version 20240131_3c4163e system/runc: Updated for version 1.1.12. system/sarasa-gothic: Updated for version 1.0.5. system/slackrepo: Updated for version 20240131. system/tio: Added (Serial TTY). system/ttf-x2: Added (system fonts). system/waypipe: Added (wayland pipeline). system/yubico-piv-tool: Updated for version 2.5.0. system/zutty: Updated for version 0.15. +--------------------------+ -- 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 alik at ejik.org Sat Feb 3 07:47:30 2024 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 3 Feb 2024 10:47:30 +0300 Subject: [Slackbuilds-users] Updates - 20240203.1 In-Reply-To: References: Message-ID: Hello, a few days ago I submitted ocserv. Now it has disappeared, neither in today's updates nor in the pending queue. Best regards, Alexander From dchmelik at gmail.com Sat Feb 3 08:14:05 2024 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Sat, 3 Feb 2024 00:14:05 -0800 Subject: [Slackbuilds-users] Updates - 20240203.1 In-Reply-To: References: Message-ID: <5e94ca64-d7e8-21f9-39bf-9558e1245181@gmail.com> On 2/2/24 11:47 PM, Alexander Verbovetsky wrote: > a few days ago I submitted ocserv. Now it has disappeared, neither in > today's updates nor in the pending queue. [...] I had same problem with crawl, though made md5sum mistake then downloaded onto a symbolic link which for some reason didn't overwrite, so had same md5sum again.? When I used submission md5sum to delete, it said it wasn't in pending, but when I tried to resubmit, it said it was in pending.? Some days ago I informed/asked willysr about this (and that I finally got same md5sum he did) and was only told 'done' which I didn't know if meant was deleted or I have to resubmit.? I got no other reply so waited and now it's not in update so apparently I must resubmit. ??? After years/decades ago I was in habit of checking/updating md5sums.? What happened recent years is I SlackBuild on server because my PC has Slackware-current... first I build on my PC, and then on server... I forgot to copy over files from server which were same for building but have updated/correct md5sum. From willysr at slackbuilds.org Sat Feb 3 15:01:44 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 3 Feb 2024 22:01:44 +0700 Subject: [Slackbuilds-users] Updates - 20240203.1 In-Reply-To: References: Message-ID: > a few days ago I submitted ocserv. Now it has disappeared, neither in > today's updates nor in the pending queue. Hi Alexander I think i forgot to apply the patch from github after i closed the issue my apologies it's now in my branch, so it should be included in next week public update. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From zsd+slackbuilds at jdvb.ca Sun Feb 4 00:00:03 2024 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Sat, 3 Feb 2024 20:00:03 -0400 Subject: [Slackbuilds-users] virtualbox slackbuilds In-Reply-To: Message-ID: Thanks to both ??? and Giancarlo, with the slackbuilds from mdinslage at github, I had VBox 7.0.14 running in no time. (And thanks to Matt Dinslage as well!) SBO admins and volunteers: if the VBox 6 maintainer is out for a long walkabout, perhaps a regular VBox user would like to get the ones from mdinslage up to standards? Cheers. Jim On Sat, Feb 3, 2024 at 03:03 (+0800), ??? via SlackBuilds-users wrote: > Hi Jim, > Some others and I have been waiting too, as seen in this thread > (https://www.linuxquestions.org/questions/slackware-14/building-virtualbox-7-on-slackware-15-a-4175727199/) > and this thread > (https://www.linuxquestions.org/questions/slackware-14/building-virtualbox-kernel-slackbuild-for-6-6-x-kernel-branch-4175731627/). You > can try suggestions in both, I also weighed in but currently I'll > recommend Daedra's scripts > (https://github.com/mdinslage/Custom_SlackBuilds/tree/main/virtualbox-7.0.12) > in the former post. > -- ltlnx > _______________________________________________ > 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/ On Sat, Feb 3, 2024 at 00:17 (+0100), Giancarlo Dess? wrote: > Il 02/02/24 15:01, Jim ha scritto: >> All, >> I recently started running the 6.6.12 kernel. All (well, everything I use) >> is working except virtualbox-kernel, which won't compile on that kernel. >> Looking on the web, I see the particular problem I'm having has been fixed >> in newer versions of virtualbox. I see that aside from 6.1.55, there is >> also 7.0.14. >> I emailed the maintainer on Monday, but haven't heard back. Maybe he's >> away, and that's fine, but I was wondering if anyone has been in touch with >> him recently. >> Anyone? >> Jim > In current I used VB 6.1.32 for a long time and solved issues due last > updates of the kernel using a patch. It works fine, but the recent upgrade > of libvpx has required the rebuild of virtualbox driver. This has brought > many problems and some day ago I decided to use the slackbuild of Daedra for > virtualbox 7.0.12. In Slackware current It works and should also work with > VB 7.0.14. > https://github.com/mdinslage/Custom_SlackBuilds/tree/main/virtualbox-7.0.12 > You have to do the following things: > 1) if you require the software virtualization install the multilib of > AlienBob > 2) if you have an installation of Java 11 or earlier, downgrade to Java 8 > because the build of VirtualBox needs wsimport (droppend since Java 11). It > is required only for the build: next time you can upgrade to earlier version > of JDK > The installation of gsoap and acpica from SBo's slackbuilds are fully > compatible. This happened in current, I don't know if there are problems > with Slackware 15.0 > - > ********************************************************* > Giancarlo Dess? > https://www.giand.it > https://github.com/giandex > Slackware Linux... because it works! > ********************************************************* > _______________________________________________ > 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 sb at rbn.im Sun Feb 4 00:19:49 2024 From: sb at rbn.im (Ruben Schuller) Date: Sun, 4 Feb 2024 01:19:49 +0100 Subject: [Slackbuilds-users] barrier update Message-ID: <20240204011949.1844e057@kiwi.kuchen> Hi list, hi M?rio, I have prepared an update to 2.4.0, the lastest version. I'll submit it via gitlab in the next days after some more polishing. Would it be OK for you, M?rio, if I'd take maintainership of barrier? Cheers Ruben From mariolpantunes at gmail.com Sun Feb 4 00:36:15 2024 From: mariolpantunes at gmail.com (=?UTF-8?Q?M=C3=A1rio_Antunes?=) Date: Sun, 4 Feb 2024 00:36:15 +0000 Subject: [Slackbuilds-users] barrier update In-Reply-To: <20240204011949.1844e057@kiwi.kuchen> References: <20240204011949.1844e057@kiwi.kuchen> Message-ID: Please, I haven't used the application in quite some time. Thanks, M?rio Antunes On Sun, Feb 4, 2024, 12:19?AM Ruben Schuller wrote: > Hi list, hi M?rio, > > I have prepared an update to 2.4.0, the lastest version. I'll submit it > via gitlab in the next days after some more polishing. > > Would it be OK for you, M?rio, if I'd take maintainership of barrier? > > Cheers > Ruben > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mariolpantunes at gmail.com Sun Feb 4 00:48:52 2024 From: mariolpantunes at gmail.com (=?UTF-8?Q?M=C3=A1rio_Antunes?=) Date: Sun, 4 Feb 2024 00:48:52 +0000 Subject: [Slackbuilds-users] barrier update In-Reply-To: References: <20240204011949.1844e057@kiwi.kuchen> Message-ID: By the way, I think that on my GitHub there is a slack build version for 2.4.0, but ir uses git to get the source code. On Sun, Feb 4, 2024, 12:36?AM M?rio Antunes wrote: > Please, > > I haven't used the application in quite some time. > > Thanks, > M?rio Antunes > > On Sun, Feb 4, 2024, 12:19?AM Ruben Schuller wrote: > >> Hi list, hi M?rio, >> >> I have prepared an update to 2.4.0, the lastest version. I'll submit it >> via gitlab in the next days after some more polishing. >> >> Would it be OK for you, M?rio, if I'd take maintainership of barrier? >> >> Cheers >> Ruben >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dchmelik at gmail.com Sun Feb 4 02:52:40 2024 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Sat, 3 Feb 2024 18:52:40 -0800 Subject: [Slackbuilds-users] [testing] kuickshow Message-ID: New kuickshow from git commit for testing is below (I don't use normally-numbered release anymore since it's over a year or few old with many new git commits).? You'll need Slackware-stable but newer extra cmake modules (ECM).? If Slackware or anyone makes a newer ECM SlackBuild/package, please let me know, because then I could submit this. more uptime: http://mirror.davidchmelik.com/math/slackbuilds/graphics/kuickshow.tar.xz updated first: http://davidchmelik.com/math/slackbuilds/graphics/kuickshow.tar.xz From jebrhansen+SBo at gmail.com Sun Feb 4 08:52:14 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 4 Feb 2024 00:52:14 -0800 Subject: [Slackbuilds-users] icalendar & python3-icalendar Duplicate Message-ID: It seems that icalendar has been added twice by tonus. One as python/icalendar and another as python/python3-icalendar. https://slackbuilds.org/repository/15.0/python/icalendar/ https://slackbuilds.org/repository/15.0/python/python3-icalendar/ There seems to be no real difference between the two, so I propose we remove icalendar and keep python3-icalendar. Only desktop/calcure will need its REQUIRES line updated. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Feb 4 08:56:31 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 4 Feb 2024 15:56:31 +0700 Subject: [Slackbuilds-users] icalendar & python3-icalendar Duplicate In-Reply-To: References: Message-ID: > It seems that icalendar has been added twice by tonus. One as > python/icalendar and another as python/python3-icalendar. > > https://slackbuilds.org/repository/15.0/python/icalendar/ > https://slackbuilds.org/repository/15.0/python/python3-icalendar/ > > There seems to be no real difference between the two, so I propose we > remove icalendar and keep python3-icalendar. > > Only desktop/calcure will need its REQUIRES line updated. Thanks for spotting that it's removed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From sb at rbn.im Sun Feb 4 09:43:55 2024 From: sb at rbn.im (Ruben Schuller) Date: Sun, 4 Feb 2024 10:43:55 +0100 Subject: [Slackbuilds-users] barrier update In-Reply-To: References: <20240204011949.1844e057@kiwi.kuchen> Message-ID: <20240204104355.59bbbc65@kiwi.kuchen> Hi M?rio, thanks for the quick answer! I have changed things around so that the used submodules (shudder) are downloaded as tarball from github, so git isn't required anymore :) I'll prepare the update and change the maintainer line accordingly. Cheers! Ruben 2024-02-04 M?rio Antunes : > By the way, I think that on my GitHub there is a slack build version > for 2.4.0, but ir uses git to get the source code. > > On Sun, Feb 4, 2024, 12:36?AM M?rio Antunes > wrote: > > > Please, > > > > I haven't used the application in quite some time. > > > > Thanks, > > M?rio Antunes > > > > On Sun, Feb 4, 2024, 12:19?AM Ruben Schuller wrote: > > > >> Hi list, hi M?rio, > >> > >> I have prepared an update to 2.4.0, the lastest version. I'll > >> submit it via gitlab in the next days after some more polishing. > >> > >> Would it be OK for you, M?rio, if I'd take maintainership of > >> barrier? > >> > >> Cheers > >> Ruben > >> > > From mariolpantunes at gmail.com Sun Feb 4 09:44:51 2024 From: mariolpantunes at gmail.com (=?UTF-8?Q?M=C3=A1rio_Antunes?=) Date: Sun, 4 Feb 2024 09:44:51 +0000 Subject: [Slackbuilds-users] barrier update In-Reply-To: <20240204104355.59bbbc65@kiwi.kuchen> References: <20240204011949.1844e057@kiwi.kuchen> <20240204104355.59bbbc65@kiwi.kuchen> Message-ID: Thanks for the update. On Sun, Feb 4, 2024, 9:44?AM Ruben Schuller wrote: > Hi M?rio, > > thanks for the quick answer! I have changed things around so that the > used submodules (shudder) are downloaded as tarball from github, so git > isn't required anymore :) > > I'll prepare the update and change the maintainer line accordingly. > > Cheers! > Ruben > > 2024-02-04 M?rio Antunes : > > > By the way, I think that on my GitHub there is a slack build version > > for 2.4.0, but ir uses git to get the source code. > > > > On Sun, Feb 4, 2024, 12:36?AM M?rio Antunes > > wrote: > > > > > Please, > > > > > > I haven't used the application in quite some time. > > > > > > Thanks, > > > M?rio Antunes > > > > > > On Sun, Feb 4, 2024, 12:19?AM Ruben Schuller wrote: > > > > > >> Hi list, hi M?rio, > > >> > > >> I have prepared an update to 2.4.0, the lastest version. I'll > > >> submit it via gitlab in the next days after some more polishing. > > >> > > >> Would it be OK for you, M?rio, if I'd take maintainership of > > >> barrier? > > >> > > >> Cheers > > >> Ruben > > >> > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sb at rbn.im Sun Feb 4 23:00:35 2024 From: sb at rbn.im (Ruben Schuller) Date: Mon, 5 Feb 2024 00:00:35 +0100 Subject: [Slackbuilds-users] packaging rust Message-ID: <20240205000035.6f991381@kiwi.kuchen> Hi list, I'm currently trying to package a program (difftastic, https://difftastic.wilfred.me.uk/) written in rust. Downloading and extracting the sources from crates.io like in the alacritty slackbuild (pretty cool work! :) seems to work fine. One of the dependencies has a git repository listed as source and I can't seem to get that load correctly from the vendor directory. I always get complains about that it can't be download as I'm in offline mode. Any suggestions or examples I can look at? Cheers Ruben From kvngncrlsn at gmail.com Mon Feb 5 01:11:24 2024 From: kvngncrlsn at gmail.com (K. Eugene Carlson) Date: Mon, 5 Feb 2024 10:11:24 +0900 Subject: [Slackbuilds-users] packaging rust In-Reply-To: <20240205000035.6f991381@kiwi.kuchen> References: <20240205000035.6f991381@kiwi.kuchen> Message-ID: On Mon, Feb 5, 2024 at 8:00?AM Ruben Schuller wrote: > Any suggestions or examples I can look at? > The SlackBuild for wezterm has a few tarballs from GitHub in it, so that might be a decent example to start with. Gene -------------- next part -------------- An HTML attachment was scrubbed... URL: From tonus1 at free.fr Mon Feb 5 05:30:02 2024 From: tonus1 at free.fr (Tonus) Date: Mon, 05 Feb 2024 06:30:02 +0100 Subject: [Slackbuilds-users] icalendar & python3-icalendar Duplicate In-Reply-To: References: Message-ID: <81BB6C55-DC11-4B99-B0C4-5662BB5BFCA7@free.fr> Thanks Forgot to remove icalendar the week after I submitted the slackbuild with new name. Regards Tonus Le 4 f?vrier 2024 09:56:31 GMT+01:00, Willy Sudiarto Raharjo a ?crit?: >> It seems that icalendar has been added twice by tonus. One as >> python/icalendar and another as python/python3-icalendar. >> >> https://slackbuilds.org/repository/15.0/python/icalendar/ >> https://slackbuilds.org/repository/15.0/python/python3-icalendar/ >> >> There seems to be no real difference between the two, so I propose we >> remove icalendar and keep python3-icalendar. >> >> Only desktop/calcure will need its REQUIRES line updated. > >Thanks for spotting that >it's removed in my branch > From erich.public at protonmail.com Mon Feb 5 13:56:09 2024 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 05 Feb 2024 13:56:09 +0000 Subject: [Slackbuilds-users] packaging rust In-Reply-To: References: <20240205000035.6f991381@kiwi.kuchen> Message-ID: On Sunday, February 4th, 2024 at 7:11 PM, K. Eugene Carlson wrote: > On Mon, Feb 5, 2024 at 8:00?AM Ruben Schuller wrote: > >> Any suggestions or examples I can look at? > > The SlackBuild for wezterm has a few tarballs from GitHub in it, so that might be a decent > example to start with. > > Gene Also system76-power. Erich -------------- next part -------------- An HTML attachment was scrubbed... URL: From sb at rbn.im Mon Feb 5 14:26:24 2024 From: sb at rbn.im (Ruben Schuller) Date: Mon, 5 Feb 2024 15:26:24 +0100 Subject: [Slackbuilds-users] packaging rust In-Reply-To: References: <20240205000035.6f991381@kiwi.kuchen> Message-ID: <20240205152624.6aa37473@kiwi.kuchen> Hi! 2024-02-05 Erich Ritz via SlackBuilds-users : > On Sunday, February 4th, 2024 at 7:11 PM, K. Eugene Carlson > wrote: > > The SlackBuild for wezterm has a few tarballs from GitHub in it, so > > that might be a decent example to start with. > Also system76-power. Thanks for both these recommendations, I'll take a look into how it's done there! Cheers Ruben From erich.public at protonmail.com Mon Feb 5 15:21:36 2024 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 05 Feb 2024 15:21:36 +0000 Subject: [Slackbuilds-users] SFML update breaks extremetuxracer Message-ID: It looks like the recent update to SFML breaks the extremetuxracer build: Building games/extremetuxracer (rebuild for updated deps) 2024-02-05 14:42:12Verifying source files ... Installing dependencies ... SFML-2.6.1-x86_64-1_SBo: Simple and Fast Multimedia Library .............................. [ 2.2M] Running extremetuxracer.SlackBuild ... ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?ETA 14:43:?? env MAKEFLAGS='-j176 -l89' nice -n 5 bash ./extremetuxracer.SlackBuild ... checking pkg-config is at least version 0.9.0... yes checking for sfml-system >= 2.4... no configure: error: sfml-system not found games/extremetuxracer: extremetuxracer.SlackBuild failed (status 1) 14:42:19 Unmounting chroot ... :-( games/extremetuxracer FAILED )-: From matteo.bernardini at gmail.com Mon Feb 5 15:37:05 2024 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 5 Feb 2024 16:37:05 +0100 Subject: [Slackbuilds-users] SFML update breaks extremetuxracer In-Reply-To: References: Message-ID: Hi Erich, this happens because the new SFML installs its pkgconfi files in the wrong location (/usr/pkgconfig): if you add the line -DSFML_PKGCONFIG_INSTALL_PREFIX=/usr/lib$LIBDIRSUFFIX/pkgconfig \ between the cmake options in the SlackBuild then stuff using pkgconfig to locate SFML will find it again correctly. I'll push the change in our git, it will be fixed in the repository at the next global update. Matteo Il giorno lun 5 feb 2024 alle ore 16:22 Erich Ritz via SlackBuilds-users < slackbuilds-users at slackbuilds.org> ha scritto: > It looks like the recent update to SFML breaks the extremetuxracer build: > > Building games/extremetuxracer (rebuild for updated deps) 2024-02-05 > 14:42:12Verifying source files ... > Installing dependencies ... > SFML-2.6.1-x86_64-1_SBo: Simple and Fast Multimedia Library > .............................. [ 2.2M] > Running extremetuxracer.SlackBuild ... ETA > 14:43:?? > env MAKEFLAGS='-j176 -l89' nice -n 5 bash ./extremetuxracer.SlackBuild > ... > checking pkg-config is at least version 0.9.0... yes > checking for sfml-system >= 2.4... no > configure: error: sfml-system not found > games/extremetuxracer: extremetuxracer.SlackBuild failed (status 1) > 14:42:19 > Unmounting chroot ... > :-( games/extremetuxracer FAILED )-: > _______________________________________________ > 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 erich.public at protonmail.com Mon Feb 5 16:18:43 2024 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 05 Feb 2024 16:18:43 +0000 Subject: [Slackbuilds-users] SFML update breaks extremetuxracer In-Reply-To: References: Message-ID: On Monday, February 5th, 2024 at 9:37 AM, Matteo Bernardini wrote: > Hi Erich, > > this happens because the new SFML installs its pkgconfi files in the wrong location (/usr/pkgconfig): if you add the line > > -DSFML_PKGCONFIG_INSTALL_PREFIX=/usr/lib$LIBDIRSUFFIX/pkgconfig \ > > between the cmake options in the SlackBuild then stuff using pkgconfig to locate SFML will find it again correctly. > > I'll push the change in our git, it will be fixed in the repository at the next global update. > > Matteo > > Il giorno lun 5 feb 2024 alle ore 16:22 Erich Ritz via SlackBuilds-users ha scritto: > > > It looks like the recent update to SFML breaks the extremetuxracer build: > > > > Building games/extremetuxracer (rebuild for updated deps) 2024-02-05 14:42:12Verifying source files ... > > Installing dependencies ... > > SFML-2.6.1-x86_64-1_SBo: Simple and Fast Multimedia Library .............................. [ 2.2M] > > Running extremetuxracer.SlackBuild ... ETA 14:43:?? > > env MAKEFLAGS='-j176 -l89' nice -n 5 bash ./extremetuxracer.SlackBuild > > ... > > checking pkg-config is at least version 0.9.0... yes > > checking for sfml-system >= 2.4... no > > configure: error: sfml-system not found > > games/extremetuxracer: extremetuxracer.SlackBuild failed (status 1) 14:42:19 > > Unmounting chroot ... > > :-( games/extremetuxracer FAILED )-: > > _______________________________________________ > > 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/ There is another problem as well highlighted by sbopkglint (forbidden directory usr/share/doc): # sbopkglint /var/lib/slackrepo/etr/packages/15.0/x86_64/libraries/SFML/SFML-2.6.1-x86_64-1_SBo.txz Using tests from /usr/share/sbo-maintainer-tools/sbopkglint.d Exploding /var/lib/slackrepo/etr/packages/15.0/x86_64/libraries/SFML/SFML-2.6.1-x86_64-1_SBo.txz to /tmp/SBo/sbopkglint.QLp0Dt ...OK Running pre-doinst test...OK Installing /var/lib/slackrepo/etr/packages/15.0/x86_64/libraries/SFML/SFML-2.6.1-x86_64-1_SBo.txz to /tmp/SBo/sbopkglint.QLp0Dt ...OK Running test: 05-basic-sanity... --- nonstandard directory in /usr: usr/pkgconfig --- forbidden directory exists: usr/share/doc FAILED Running test: 10-docs...OK Running test: 15-noarch...OK Running test: 20-arch...OK Running test: 25-lafiles...OK Running test: 30-manpages...OK Running test: 35-desktop...OK Running test: 40-newconfig...OK Running test: 45-doinst...OK Running test: 50-icons...OK Running test: 60-usr_info...OK Running test: 65-python...OK Running test: 70-tmp_path...OK Running test: 75-static_libs...OK Running test: 85-perl...OK !!! SFML-2.6.1-x86_64-1_SBo.txz: 2 failures From matteo.bernardini at gmail.com Mon Feb 5 16:33:26 2024 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 5 Feb 2024 17:33:26 +0100 Subject: [Slackbuilds-users] SFML update breaks extremetuxracer In-Reply-To: References: Message-ID: Il giorno lun 5 feb 2024 alle ore 17:19 Erich Ritz < erich.public at protonmail.com> ha scritto: > On Monday, February 5th, 2024 at 9:37 AM, Matteo Bernardini < > matteo.bernardini at gmail.com> wrote: > > > Hi Erich, > > > > this happens because the new SFML installs its pkgconfi files in the > wrong location (/usr/pkgconfig): if you add the line > > > > -DSFML_PKGCONFIG_INSTALL_PREFIX=/usr/lib$LIBDIRSUFFIX/pkgconfig \ > > > > between the cmake options in the SlackBuild then stuff using pkgconfig > to locate SFML will find it again correctly. > > > > I'll push the change in our git, it will be fixed in the repository at > the next global update. > > > > Matteo > > > > Il giorno lun 5 feb 2024 alle ore 16:22 Erich Ritz via SlackBuilds-users > ha scritto: > > > > > It looks like the recent update to SFML breaks the extremetuxracer > build: > > > > > > Building games/extremetuxracer (rebuild for updated deps) 2024-02-05 > 14:42:12Verifying source files ... > > > Installing dependencies ... > > > SFML-2.6.1-x86_64-1_SBo: Simple and Fast Multimedia Library > .............................. [ 2.2M] > > > Running extremetuxracer.SlackBuild ... ETA 14:43:?? > > > env MAKEFLAGS='-j176 -l89' nice -n 5 bash ./extremetuxracer.SlackBuild > > > ... > > > checking pkg-config is at least version 0.9.0... yes > > > checking for sfml-system >= 2.4... no > > > configure: error: sfml-system not found > > > games/extremetuxracer: extremetuxracer.SlackBuild failed (status 1) > 14:42:19 > > > Unmounting chroot ... > > > :-( games/extremetuxracer FAILED )-: > > > _______________________________________________ > > > 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/ > > There is another problem as well highlighted by sbopkglint (forbidden > directory usr/share/doc): > > # sbopkglint /var/lib/slackrepo/etr/packages/15.0/x86_64/libraries/SFML/ > SFML-2.6.1-x86_64-1_SBo.txz > Using tests from /usr/share/sbo-maintainer-tools/sbopkglint.d > Exploding /var/lib/slackrepo/etr/packages/15.0/x86_64/libraries/SFML/SFML-2.6.1-x86_64-1_SBo.txz > to /tmp/SBo/sbopkglint.QLp0Dt ...OK > Running pre-doinst test...OK > Installing /var/lib/slackrepo/etr/packages/15.0/x86_64/libraries/SFML/SFML-2.6.1-x86_64-1_SBo.txz > to /tmp/SBo/sbopkglint.QLp0Dt ...OK > Running test: 05-basic-sanity... > --- nonstandard directory in /usr: usr/pkgconfig > --- forbidden directory exists: usr/share/doc > FAILED > Running test: 10-docs...OK > Running test: 15-noarch...OK > Running test: 20-arch...OK > Running test: 25-lafiles...OK > Running test: 30-manpages...OK > Running test: 35-desktop...OK > Running test: 40-newconfig...OK > Running test: 45-doinst...OK > Running test: 50-icons...OK > Running test: 60-usr_info...OK > Running test: 65-python...OK > Running test: 70-tmp_path...OK > Running test: 75-static_libs...OK > Running test: 85-perl...OK > !!! SFML-2.6.1-x86_64-1_SBo.txz: 2 failures > thanks for the heads-up, fixed that too! Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.arcus at open-t.co.uk Tue Feb 6 23:22:14 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 6 Feb 2024 23:22:14 +0000 Subject: [Slackbuilds-users] BcToolbox download link broken - but later version will compile on 15.0 Message-ID: <30cc3d7a-30fe-0f79-be20-2a42f778fb36@open-t.co.uk> Hello. In case it helps - the download link for BcToolbox v0.6.0 is broken - but I've managed to compile version 5.2.2 using the SBo scripts on 15.0 without complaints (the SlackBuild script needs amending slightly for the location of some of the docs file). Versions after 5.2.2 require cmake 3.22, which Slackware 15.0 doesn't have. Unless there is a particular reason to stick with BcToolbox 0.6.0 - if anyone knows? From willysr at slackbuilds.org Tue Feb 6 23:24:40 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 7 Feb 2024 06:24:40 +0700 Subject: [Slackbuilds-users] BcToolbox download link broken - but later version will compile on 15.0 In-Reply-To: <30cc3d7a-30fe-0f79-be20-2a42f778fb36@open-t.co.uk> References: <30cc3d7a-30fe-0f79-be20-2a42f778fb36@open-t.co.uk> Message-ID: > Hello. In case it helps - the download link for BcToolbox v0.6.0 is > broken - but I've managed to compile version 5.2.2 using the SBo scripts > on 15.0 without complaints (the SlackBuild script needs amending > slightly for the location of some of the docs file). Versions after > 5.2.2 require cmake 3.22, which Slackware 15.0 doesn't have. > > Unless there is a particular reason to stick with BcToolbox 0.6.0 - if > anyone knows? i think maintainer is no longer active as he never update the script since he submitted it back in 2017 if you are using it actively, i would suggest to take over maintainership of this script -- 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 s.arcus at open-t.co.uk Wed Feb 7 00:10:38 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 7 Feb 2024 00:10:38 +0000 Subject: [Slackbuilds-users] BcToolbox download link broken - but later version will compile on 15.0 In-Reply-To: References: <30cc3d7a-30fe-0f79-be20-2a42f778fb36@open-t.co.uk> Message-ID: <9fd576e7-2d67-8510-0706-06cc6d6b3c5f@open-t.co.uk> On 06/02/2024 23:24, Willy Sudiarto Raharjo wrote: >> Hello. In case it helps - the download link for BcToolbox v0.6.0 is >> broken - but I've managed to compile version 5.2.2 using the SBo >> scripts on 15.0 without complaints (the SlackBuild script needs >> amending slightly for the location of some of the docs file). Versions >> after 5.2.2 require cmake 3.22, which Slackware 15.0 doesn't have. >> >> Unless there is a particular reason to stick with BcToolbox 0.6.0 - if >> anyone knows? > > i think maintainer is no longer active as he never update the script > since he submitted it back in 2017 > > if you are using it actively, i would suggest to take over > maintainership of this script Yes please - it is mostly working as is - so it shouldn't involve too much effort to look after it - I'll have it From pprkut at slackbuilds.org Wed Feb 7 10:00:26 2024 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Wed, 07 Feb 2024 11:00:26 +0100 Subject: [Slackbuilds-users] virtualbox slackbuilds In-Reply-To: References: Message-ID: <2060094.YKUYFuaPT4@amaterasu.liwjatan.org> On Friday, 2 February 2024 15:01:41 CET Jim wrote: > All, > > I recently started running the 6.6.12 kernel. All (well, everything I use) > is working except virtualbox-kernel, which won't compile on that kernel. > > Looking on the web, I see the particular problem I'm having has been fixed > in newer versions of virtualbox. I see that aside from 6.1.55, there is > also 7.0.14. > > I emailed the maintainer on Monday, but haven't heard back. Maybe he's > away, and that's fine, but I was wondering if anyone has been in touch with > him recently. Hi all! Sorry for the radio silence lately, was certainly not intentional. Between being sick for a couple weeks and stress at work it just wasn't a very great start into the year :( I have updated slackbuilds for -current, but haven't come around to testing them yet. There are some issues with virtualbox-addons (I can't get anything newer than 7.0.10 to compile), and while that isn't a deal breaker per se, it's enough for me to not push anything I haven't tested myself. Once I have the updates in my -current repo, I'll look into updates for - stable, but realistically, that's still a couple weeks away. Sorry about that! 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 s.arcus at open-t.co.uk Wed Feb 7 23:25:40 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 7 Feb 2024 23:25:40 +0000 Subject: [Slackbuilds-users] Linphone maintenance Message-ID: Anyone knows if Linphone is still actively maintained? I have managed to compile a current version on Slackware, and it would be nice if it could be updated at SBo as well From willysr at slackbuilds.org Thu Feb 8 00:37:30 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 8 Feb 2024 07:37:30 +0700 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: References: Message-ID: > Anyone knows if Linphone is still actively maintained? I have managed to > compile a current version on Slackware, and it would be nice if it could > be updated at SBo as well nope, maintainer is no longer active, so if you are willing to take over maintainership, that would be great idea -- 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 s.arcus at open-t.co.uk Thu Feb 8 00:51:16 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 8 Feb 2024 00:51:16 +0000 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: References: Message-ID: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> On 08/02/2024 00:37, Willy Sudiarto Raharjo wrote: >> Anyone knows if Linphone is still actively maintained? I have managed >> to compile a current version on Slackware, and it would be nice if it >> could be updated at SBo as well > > nope, maintainer is no longer active, so if you are willing to take over > maintainership, that would be great idea Ok - thank you - I will take it over and try to update the scripts. I might need a hand with a few bits I haven't figured out yet - but I will send a separate message to the list From s.arcus at open-t.co.uk Thu Feb 8 01:19:45 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 8 Feb 2024 01:19:45 +0000 Subject: [Slackbuilds-users] Linphone sources and dependencies Message-ID: <0cefd7af-c7c6-6a65-22b1-95a334dfa13e@open-t.co.uk> I have just taken over Linphone maintenance and trying to update the SBo scripts for the current version. What I have done so far: 1. I have followed the instructions and cloned the repo on a Slackware -current (because of cmake minimum version - see below): $ git clone https://gitlab.linphone.org/BC/public/linphone-desktop.git --recursive This downloads 3.0GB of files on my computer in a directory called linphone-desktop. A large chunk of this is in a dir called linphone-sdk. Leaving aside for a minute the huge size of the archive, I can follow through with the instructions and manually build and compile Linphone. 2. However, if I just download version 5.0.0 directly from git (later versions require cmake 3.2.2) on either Slackware -current or 15.0: $ wget https://gitlab.linphone.org/BC/public/linphone-desktop/-/archive/5.0.0/linphone-desktop-5.0.0.tar.gz This downloads a 3MB file, without the sdk. Now if I try to follow the instructions and compile this, I get: -- No plugins found for the application to build CMake Error at /usr/share/cmake-3.21/Modules/ExternalProject.cmake:2866 (message): No download info given for 'sdk' and its source directory: /usr/src/linphone-desktop-5.0.0/linphone-sdk is not an existing non-empty directory. Please specify one of: * SOURCE_DIR with an existing non-empty directory * DOWNLOAD_COMMAND * URL * GIT_REPOSITORY * SVN_REPOSITORY * HG_REPOSITORY * CVS_REPOSITORY and CVS_MODULE Call Stack (most recent call first): /usr/share/cmake-3.21/Modules/ExternalProject.cmake:3700 (_ep_add_download_command) CMakeLists.txt:212 (ExternalProject_Add) My question is - does that mean the only way to compile Linphone is: 1. To download a 3GB archive (which I'm still not sure why is so large) of 5.0.0 - so that it compiles on Slackware 15.0? or 2. To somehow install separately linphone-sdk - maybe having to create a separate SBo package for it? or 3. Pass somehow on the command line the address of the git repository for it - but this will presumably again result in a large download? I'm a bit out of my depth here, so if anyone could provide some hints where to look next, that would be much appreciated From for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net Thu Feb 8 01:28:35 2024 From: for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net (Lockywolf) Date: Thu, 08 Feb 2024 09:28:35 +0800 Subject: [Slackbuilds-users] Linphone sources and dependencies In-Reply-To: <0cefd7af-c7c6-6a65-22b1-95a334dfa13e@open-t.co.uk> References: <0cefd7af-c7c6-6a65-22b1-95a334dfa13e@open-t.co.uk> Message-ID: <878r3v2170.fsf@laptop.lockywolf.net> Sebastian Arcus writes: > 2. However, if I just download version 5.0.0 directly from git (later versions > require cmake 3.2.2) on either Slackware -current or 15.0: > You don't have to do any of that, just change the hashes in my build, and re-submit. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) From for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net Thu Feb 8 01:23:06 2024 From: for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net (Lockywolf) Date: Thu, 08 Feb 2024 09:23:06 +0800 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> Message-ID: <87eddn219d.fsf@laptop.lockywolf.net> Sebastian Arcus writes: > On 08/02/2024 00:37, Willy Sudiarto Raharjo wrote: >>> Anyone knows if Linphone is still actively maintained? I have managed to compile >>> a current version on Slackware, and it would be nice if it could be updated at >>> SBo as well >> nope, maintainer is no longer active, so if you are willing to take over >> maintainership, that would be great idea > > Ok - thank you - I will take it over and try to update the scripts. I might need a > hand with a few bits I haven't figured out yet - but I will send a separate message > to the list > _______________________________________________ > 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/ What WSR is responding is factually wrong. I have submitted the slackbuild for the most recent version of linphone (submitted as linphone-desktop, because nowadays linphone is very different from what it was in the past, and the developers, Belledonne Communications, keep it in a separate repo from the old linphone). The code is here: https://gitlab.com/Lockywolf/lwfslackbuilds/-/tree/master/05_submitted/linphone-desktop?ref_type=heads It was rejected for the reason of being "for the alpha version". (WSR's own responce from Sat, 23 Sep 2023 10:34:46 +0700) >do you mind to wait until 5.2.0 is released or go for previous version which is >released under stable label? So I have been waiting for the 5.2.0 since. You can roll-back to the most-recent non-alpha, and re-submit, I do not mind. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) From s.arcus at open-t.co.uk Thu Feb 8 01:47:17 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 8 Feb 2024 01:47:17 +0000 Subject: [Slackbuilds-users] Linphone sources and dependencies In-Reply-To: <878r3v2170.fsf@laptop.lockywolf.net> References: <0cefd7af-c7c6-6a65-22b1-95a334dfa13e@open-t.co.uk> <878r3v2170.fsf@laptop.lockywolf.net> Message-ID: <1f3116bc-17bc-f205-6281-03152c8a8167@open-t.co.uk> On 08/02/2024 01:28, Lockywolf wrote: > > Sebastian Arcus writes: > >> 2. However, if I just download version 5.0.0 directly from git (later versions >> require cmake 3.2.2) on either Slackware -current or 15.0: >> > > You don't have to do any of that, just change the hashes in my build, > and re-submit. I'm happy for you to carry on being the maintainer, if Willy / admins are ok with that. It sounds like you have already done the work - I'm just happy if there is a recent version of Linphone in the repo's. Thank you for your work From s.arcus at open-t.co.uk Thu Feb 8 01:57:55 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 8 Feb 2024 01:57:55 +0000 Subject: [Slackbuilds-users] Linphone sources and dependencies In-Reply-To: <878r3v2170.fsf@laptop.lockywolf.net> References: <0cefd7af-c7c6-6a65-22b1-95a334dfa13e@open-t.co.uk> <878r3v2170.fsf@laptop.lockywolf.net> Message-ID: <82dd9810-c9ce-7b43-b056-3500d7f5e9e9@open-t.co.uk> On 08/02/2024 01:28, Lockywolf wrote: > > Sebastian Arcus writes: > >> 2. However, if I just download version 5.0.0 directly from git (later versions >> require cmake 3.2.2) on either Slackware -current or 15.0: >> > > You don't have to do any of that, just change the hashes in my build, > and re-submit. Looking at your scripts, maybe a possibility would be to rename the old Linphone in SBo repos linphone-3 - and make a note that it can't be installed on the same system as linphone-app. This way linphone-app could place its binaries in the usual /usr/bin? From willysr at slackbuilds.org Thu Feb 8 02:54:26 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 8 Feb 2024 09:54:26 +0700 Subject: [Slackbuilds-users] Linphone sources and dependencies In-Reply-To: <82dd9810-c9ce-7b43-b056-3500d7f5e9e9@open-t.co.uk> References: <0cefd7af-c7c6-6a65-22b1-95a334dfa13e@open-t.co.uk> <878r3v2170.fsf@laptop.lockywolf.net> <82dd9810-c9ce-7b43-b056-3500d7f5e9e9@open-t.co.uk> Message-ID: <60403786-544f-4dd3-bc54-56f8e00d6c81@slackbuilds.org> >>> 2. However, if I just download version 5.0.0 directly from git (later >>> versions >>> require cmake 3.2.2) on either Slackware -current or 15.0: >>> >> >> You don't have to do any of that, just change the hashes in my build, >> and re-submit. > > Looking at your scripts, maybe a possibility would be to rename the old > Linphone in SBo repos linphone-3 - and make a note that it can't be > installed on the same system as linphone-app. This way linphone-app > could place its binaries in the usual /usr/bin? do we need to keep the old version? if not, just use the current script and update it to any version you would like to use -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Feb 8 02:56:57 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 8 Feb 2024 09:56:57 +0700 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: <87eddn219d.fsf@laptop.lockywolf.net> References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> Message-ID: > What WSR is responding is factually wrong. > > I have submitted the slackbuild for the most recent version of linphone > (submitted as linphone-desktop, because nowadays linphone is very > different from what it was in the past, and the developers, Belledonne > Communications, keep it in a separate repo from the old linphone). > > The code is here: > https://gitlab.com/Lockywolf/lwfslackbuilds/-/tree/master/05_submitted/linphone-desktop?ref_type=heads > > It was rejected for the reason of being "for the alpha version". > (WSR's own responce from Sat, 23 Sep 2023 10:34:46 +0700) > >> do you mind to wait until 5.2.0 is released or go for previous version which is >> released under stable label? > > So I have been waiting for the 5.2.0 since. > > You can roll-back to the most-recent non-alpha, and re-submit, I do not > mind. They have released 5.2.1 6 days ago https://gitlab.linphone.org/BC/public/linphone-desktop/-/tags -- 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 s.arcus at open-t.co.uk Thu Feb 8 11:37:27 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 8 Feb 2024 11:37:27 +0000 Subject: [Slackbuilds-users] Linphone sources and dependencies In-Reply-To: <60403786-544f-4dd3-bc54-56f8e00d6c81@slackbuilds.org> References: <0cefd7af-c7c6-6a65-22b1-95a334dfa13e@open-t.co.uk> <878r3v2170.fsf@laptop.lockywolf.net> <82dd9810-c9ce-7b43-b056-3500d7f5e9e9@open-t.co.uk> <60403786-544f-4dd3-bc54-56f8e00d6c81@slackbuilds.org> Message-ID: On 08/02/2024 02:54, Willy Sudiarto Raharjo wrote: >>>> 2. However, if I just download version 5.0.0 directly from git >>>> (later versions >>>> require cmake 3.2.2) on either Slackware -current or 15.0: >>>> >>> >>> You don't have to do any of that, just change the hashes in my build, >>> and re-submit. >> >> Looking at your scripts, maybe a possibility would be to rename the >> old Linphone in SBo repos linphone-3 - and make a note that it can't >> be installed on the same system as linphone-app. This way linphone-app >> could place its binaries in the usual /usr/bin? > > do we need to keep the old version? > if not, just use the current script and update it to any version you > would like to use I can't think of a good reason to keep the old version. After all, if anyone really needs it, the scripts will continue to be available in the 14.2 repo From s.arcus at open-t.co.uk Thu Feb 8 11:48:41 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 8 Feb 2024 11:48:41 +0000 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> Message-ID: <9e6d2717-8b8e-2f22-d08b-1a4f53fd89a1@open-t.co.uk> -- *Sebastian Arcus* *OpenTerritory - open solutions* Systems Support | Linux Servers | Asterisk and VoIP | Network Maintenance | In-house Cloud *www.open-t.co.uk* *p:* 0151 733 9648 *m:* 07940 348 898 *e:* s.arcus at open-t.co.uk On 08/02/2024 02:56, Willy Sudiarto Raharjo wrote: >> What WSR is responding is factually wrong. >> >> I have submitted the slackbuild for the most recent version of linphone >> (submitted as linphone-desktop, because nowadays linphone is very >> different from what it was in the past, and the developers, Belledonne >> Communications, keep it in a separate repo from the old linphone). >> >> The code is here: >> https://gitlab.com/Lockywolf/lwfslackbuilds/-/tree/master/05_submitted/linphone-desktop?ref_type=heads >> >> >> It was rejected for the reason of being "for the alpha version". >> (WSR's own responce from Sat, 23 Sep 2023 10:34:46 +0700) >> >>> do you mind to wait until 5.2.0 is released or go for previous >>> version which is >>> released under stable label? >> >> So I have been waiting for the 5.2.0 since. >> >> You can roll-back to the most-recent non-alpha, and re-submit, I do not >> mind. > > They have released 5.2.1 6 days ago > https://gitlab.linphone.org/BC/public/linphone-desktop/-/tags In my tests I had to go back to 5.1.2, as later releases require cmake 3.22 - which Slackware 15.0 doesn't have (see error message below). Later versions (all the way up to 3.0.0-alpha) seem to be fine on Slackware -current though. Unless there is a way around this? Still, even 5.1.2 would be far more recent than 3.x series CMake Error at CMakeLists.txt:23 (cmake_minimum_required): CMake 3.22 or higher is required. You are running version 3.21.4 From dickson.tim at googlemail.com Thu Feb 8 14:24:00 2024 From: dickson.tim at googlemail.com (Tim Dickson) Date: Thu, 8 Feb 2024 14:24:00 +0000 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: <9e6d2717-8b8e-2f22-d08b-1a4f53fd89a1@open-t.co.uk> References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <9e6d2717-8b8e-2f22-d08b-1a4f53fd89a1@open-t.co.uk> Message-ID: you could do a cmake-202x opt package like was done for 14.2 with the newest version of cmake have a look at it's README_SBo.txt for tips as well. regards, Tim On 08/02/2024 11:48, Sebastian Arcus wrote: > > From fernando.lopezjr at gmail.com Thu Feb 8 16:32:07 2024 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 8 Feb 2024 09:32:07 -0700 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <9e6d2717-8b8e-2f22-d08b-1a4f53fd89a1@open-t.co.uk> Message-ID: why dont you use the previous version of cmake. i am pretty sure it will compile. just patch your program. hopefully it will work. On Thu, Feb 8, 2024, 7:24?AM Tim Dickson via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > you could do a cmake-202x opt package like was done for 14.2 with the > newest version of cmake > have a look at it's README_SBo.txt for tips as well. > regards, Tim > > On 08/02/2024 11:48, Sebastian Arcus wrote: > > > > > > _______________________________________________ > 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 s.arcus at open-t.co.uk Fri Feb 9 12:12:05 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Fri, 9 Feb 2024 12:12:05 +0000 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <9e6d2717-8b8e-2f22-d08b-1a4f53fd89a1@open-t.co.uk> Message-ID: <92d7a3be-fffd-b54e-8055-9c12182fd923@open-t.co.uk> Sounds like an option - but a bit above my current level of skill. If anyone wants to contribute a patch, I'm sure the admins will take a look On 08/02/2024 16:32, Fernando Lopez wrote: > why dont you use the previous version of cmake. i am pretty sure it will > compile. just patch your program. hopefully it will work. > > On Thu, Feb 8, 2024, 7:24?AM Tim Dickson via SlackBuilds-users > > wrote: > > you could do a cmake-202x opt package like was done for 14.2 with the > newest version of cmake > have a look at it's README_SBo.txt for tips as well. > regards, Tim > > On 08/02/2024 11:48, Sebastian Arcus wrote: > > > > > > _______________________________________________ > 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 s.arcus at open-t.co.uk Fri Feb 9 12:17:54 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Fri, 9 Feb 2024 12:17:54 +0000 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> Message-ID: <5ca1fd6b-2900-a951-174b-20bf7831aa6d@open-t.co.uk> On 08/02/2024 02:56, Willy Sudiarto Raharjo wrote: >> What WSR is responding is factually wrong. >> >> I have submitted the slackbuild for the most recent version of linphone >> (submitted as linphone-desktop, because nowadays linphone is very >> different from what it was in the past, and the developers, Belledonne >> Communications, keep it in a separate repo from the old linphone). >> >> The code is here: >> https://gitlab.com/Lockywolf/lwfslackbuilds/-/tree/master/05_submitted/linphone-desktop?ref_type=heads >> >> >> It was rejected for the reason of being "for the alpha version". >> (WSR's own responce from Sat, 23 Sep 2023 10:34:46 +0700) >> >>> do you mind to wait until 5.2.0 is released or go for previous >>> version which is >>> released under stable label? >> >> So I have been waiting for the 5.2.0 since. >> >> You can roll-back to the most-recent non-alpha, and re-submit, I do not >> mind. > > They have released 5.2.1 6 days ago > https://gitlab.linphone.org/BC/public/linphone-desktop/-/tags Just checking if we reached any decision on this? Are we happy to use Lockywolf's scripts - and move Linphone to version 5.1.2 which compiles on Slackware 15.0 - and replace the old Linphone scripts? From jebrhansen+SBo at gmail.com Sat Feb 10 00:16:21 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 9 Feb 2024 16:16:21 -0800 Subject: [Slackbuilds-users] Larry Hajali's SlackBuilds Message-ID: Are Larry Hajali's SlackBuilds up for grabs? There has only been one update from him since April 2021 and that was in May of 2022[1]. I found this because another python3 package I'm working on required lxml and it pulled in several python2 packages as dependencies, so I'd like to split lxml into python2 and python3 packages. It seems many of his other python packages could use naming changes and/or splits. If they are available, I can take the following as they're dependencies for some of the SlackBuilds I maintain: libraries/libcec/ libraries/libnfs/ libraries/platform/ libraries/tinyxml/ libraries/tinyxml2/ python/lxml/ The remaining SlackBuilds are: academic/chartgeany academic/qalculate-gtk academic/speedcrunch academic/tuxmath academic/wxMaxima accessibility/easystroke audio/eyeD3 audio/kradio desktop/notification-daemon development/ldns development/xmlcopyeditor games/alienarena games/assaultcube games/brainparty games/chroma games/chromium-bsu games/cubosphere games/cuyo games/dustrac games/glestae games/jag games/meandmyshadow games/megaglest games/opensonic games/pasang-emas games/peg-e games/rezerwar games/yabause graphics/qcad graphics/yagf libraries/bitstream libraries/cdk libraries/cuneiform libraries/dcadec libraries/enca libraries/fpconst libraries/gdata libraries/gtkimageview libraries/http-parser libraries/irrlicht libraries/libaacs libraries/libb64 libraries/libbdplus libraries/libdc1394 libraries/libdivecomputer libraries/libdvbcsa libraries/libgit2 libraries/libmodplug libraries/libmusicbrainz3 libraries/libotf libraries/libunique libraries/lockdev libraries/mini18n libraries/ois libraries/podofo libraries/soil libraries/t4k_common misc/keychain misc/subsurface multimedia/audiopreview multimedia/dvblast multimedia/shotcut multimedia/xvst network/flvstreamer network/nginx network/pidgin-toobars office/grisbi office/sigil office/texmaker office/texstudio perl/perl-Cstools perl/perl-IO-CaptureOutput perl/perl-Unicode-Map perl/perl-Unicode-Map8 perl/perl-trayicon python/apsw python/boto python/boto3 python/css-parser python/cssselect python/cssutils python/dnspython python/dukpy python/filechunkio python/gst0-python python/html5-parser python/mechanize python/pydf python/pyinotify python/pymysql python/pypoppler python/python-distutils-extra python/python-libnacl python/python-musicbrainz2 python/python-sh python/python2-MarkupSafe python/python2-dateutil python/python2-keyczar python/rope python/rsa python/s3cmd python/simplejson python/unrardll system/dosemu system/sysdig Thanks, Jeremy [1] https://git.slackbuilds.org/slackbuilds/log/?h=15.0&qt=author&q=Larry+Hajali -------------- next part -------------- An HTML attachment was scrubbed... URL: From arnaud.garcia-fernandez at laposte.net Sat Feb 10 08:43:49 2024 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Sat, 10 Feb 2024 09:43:49 +0100 Subject: [Slackbuilds-users] Larry Hajali's SlackBuilds In-Reply-To: References: Message-ID: <20240210094349.4ad64ace246fe727daf20983@laposte.net> > Are Larry Hajali's SlackBuilds up for grabs? There has only been one update > from him since April 2021 and that was in May of 2022[1]. I found this > because another python3 package I'm working on required lxml and it pulled > in several python2 packages as dependencies, so I'd like to split lxml into > python2 and python3 packages. It seems many of his other python packages > could use naming changes and/or splits. > > If they are available, I can take the following as they're dependencies for > some of the SlackBuilds I maintain: > > libraries/libcec/ > libraries/libnfs/ > libraries/platform/ > libraries/tinyxml/ > libraries/tinyxml2/ > python/lxml/ > > The remaining SlackBuilds are: > [...a lot...] > > Thanks, > Jeremy > > [1] > https://git.slackbuilds.org/slackbuilds/log/?h=15.0&qt=author&q=Larry+Hajali If that is the case, my own Slackbuilds have dnspython and tinyxml2 as requirements. I'd be ok to maintain dnspython until it dies, as I'm already maintainer of python3-dnspython. If really those slackbuilds are abandoned I could take care of those ones : office/grisbi because I use it system/dosemu, so I'll maintain almost anything DOS-related ^^ network/nginx to cuddle along my darkhttpd and thttpd office/texmaker, office/texstudio and office/sigil, because they ought to be maintained. And also those games because I like games : games/megaglest, games/alienarena, games/chromium-bsu, games/assaultcube, ggames/lestae, games/opensonic, games/dustrac. - Yth. From willysr at slackbuilds.org Sat Feb 10 09:31:27 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 10 Feb 2024 16:31:27 +0700 Subject: [Slackbuilds-users] Updates - 20240210.1 Message-ID: This week, we have another great news to share with you Andrew Clemons has already finished deploying our CI engine in Gitlab platform and he has been doing some extensive testing for the last few days and it seems to work as expected, so you can now send your merge request to gitlab and have our CI engine test your submission. As a reminder, please avoid using local copy of the SlackBuild for submitting updates as we might have modify your script to make sure it stays consistent and compliance with our template. It's always recommended to use the SlackBuild files from our website or even better, keep a local copy of our repository from SBo, github or gitlab and start from there. If you want to send your updates via Github, you can do so by following this guide: https://slackbuilds.org/SBo-Github-Workflows.txt The same workflow can be used for gitlab platform as well with some adjustment. have a nice weekend :) Sat Feb 10 09:18:29 UTC 2024 academic/fet: Updated for version 6.16.0. academic/gmsh: Updated for version 4.12.2. academic/gplates: Added (plate tectonics program). academic/plus42: Updated for version 1.1.3. academic/python3-scipy: Version bump to 1.12.0 accessibility/pastebinit: Updated for version 1.6.2. audio/qpwgraph: Updated for version 0.6.2 audio/wildmidi: Update HOMEPAGE. desktop/calcure: Update DEP. desktop/engrampa: Updated for version 1.26.2. desktop/nwg-drawer: Updated for version 0.4.6. desktop/nwg-look: Updated for version 0.2.6. desktop/nwg-menu: Updated for version 0.1.2. desktop/python3-autotiling: Updated for version 1.9. desktop/xpra: Updated for version 5.0.4, add HTML5 server support. development/FreeBASIC: Updated for version 1.10.1. development/atasm: Updated for version 1.23. development/composer: Updated for version 2.7.0 development/cosmocc: Added (C library). development/eisl: Updated for version 3.70. development/fasm: Updated for version 1.73.32. development/gambas3: Updated for version 3.19.0. development/github-desktop: Updated for version 3.3.8. development/google-go-lang: Updated for version 1.21.6. development/jupyter-ipykernel: Update for 6.29.2 development/jupyter-nbconvert: Update for 7.15.0 development/mongodb-shell: Updated for version 2.1.3. development/quickjs: Updated for version 2024.01.13. development/rgbds: Updated for version 0.7.0. development/uftrace: Updated for version 20240205_9c1792d development/yarn: Updated for version 1.22.19. games/angband: Build tweaks. games/crawl: Updated for version 0.31.0. games/devilutionx: Updated for version 1.5.2. games/freeciv: Updated for version 3.0.10. games/freedoom: Updated for version 0.13.0. games/gtklife: Updated for version 5.3. games/jg-mednafen: Updated for version 1.32.0. games/jg-mgba: Updated for version 0.10.3. games/jg-sameboy: Updated for version 0.16.2. games/openmsx-catapult: Updated for version 19.0 games/openmsx-debugger: Updated for version 20230717 games/openmsx: Updated for version 19.1 games/pioneer: Updated for version 20240203. games/sl: Updated for version 5.05 games/x16emu: Added (Commander X16 emulator). gis/eccodes: Updated for version 2.34.0. graphics/chafa: Updated for version 1.14.0. graphics/converseen: Updated for version 0.12.1.0. graphics/leocad: Updated for version 23.03. graphics/leocad_pieces: Updated for version 23.06. graphics/mcomix: Updated for version 3.1.0. graphics/xbmbrowser: Update xbmbrowser.info libraries/CLI11: Updated for version 2.4.1. libraries/Ipopt: Updated for version 3.14.14. libraries/SFML: Fix pkgconfig and doc files install locations. libraries/bctoolbox: Updated for version 5.2.2. libraries/cmark: Updated for version 0.31.0. libraries/fmt: Updated for version 10.2.0. libraries/libavif: Updated for version 1.0.3. libraries/libcbor: Updated for version 0.11.0. libraries/libfilezilla: Updated for version 0.46.0. libraries/libmediainfo: Version bump to 24.01 libraries/libyuv: Updated for version 20240116_95d8726. libraries/onevpl: Version bump to 2023.4.0 libraries/simpleini: Updated for version 4.22. libraries/webkit2gtk4.1: Updated for version 2.42.5. libraries/webkit2gtk: Updated for version 2.42.5. libraries/zope.proxy: Updated for version 5.2. misc/Bitwarden-desktop: Updated for version 2024.2.0 misc/cliphist: Updated for version 0.5.0. misc/grc: Minor bugfix from Debian. multimedia/ffmpegfs: Updated for version 2.15. multimedia/kvazaar: Updated for version 2.3.0. multimedia/mediainfo: Version bump to 24.01 multimedia/picard-plugins: Version bump to 7b3b379 multimedia/picard: Version bump to 2.11 multimedia/sickchill: Version bump to 2024.2.2 multimedia/svt-av1: Updated for version 1.8.0. network/AdGuardHome: Updated for version 0.107.44. network/ani-cli: Updated for version 4.8. network/barrier: Updated for version 2.4.0. network/bozohttpd: Updated for version 20240126. network/brave-browser: Updated for version 1.62.162. network/discord: Version bump to 0.0.42 network/dnsproxy-bin: Updated for version 0.65.0. network/easyrsa: Updated for version 3.1.7. network/filezilla: Updated for version 3.66.5. network/go-sendxmpp: Bump go version. network/goimapnotify: Updated for version 2.3.11. network/iperf3: Updated for version 3.16. network/neomutt: Updated for version 20240201. network/ocserv: Added (OpenConnect VPN). network/opera: Updated for version 107.0.5045.15. network/protonmail-bridge: Updated for version 3.8.2. network/signal-desktop: Updated for version 6.47.0. network/syncthing: Updated for version 1.27.3. network/tailscale: Updated for version 1.58.2. network/telegram: Updated for version 4.14.13. network/toot: Updated for version 0.41.1. network/uwsgi: Updated for version 2.0.24. network/vivaldi: Updated for version 6.5.3206.61. network/wego: Added (openweathermap app). network/yle-dl: Updated for version 20240130. network/ytfzf: Updated for version 2.6.2. office/MasterPDFEditor: Updated for version 5.9.82. office/calibre-bin: Updated for version 7.5.1. office/fbreader: Fix DOWNLOAD. office/smoffice2024: Updated for version 2024_1208. office/tapecalc: Updated for version 20240110. perl/perl-Error: Added (perl error). perl/perl-Mojolicious: Updated for version 9.35. python/Kallithea: Updated patch. python/certbot-dns-cloudflare: Updated for version 2.8.0 python/icalendar: Removed (use python3-icalendar). python/ipython: Note on why we can't update. python/python-mysql-replication: Updated for version 1.0.6. python/python3-BTrees: Updated for version 5.2. python/python3-PyGithub: Version bump to 2.2.0 python/python3-cachecontrol: Version bump to 0.14.0 python/python3-cloudflare: Updater for version 2.17.0 python/python3-daemon: Updated dependencies. python/python3-dogpile.cache: Updated for version 1.3.1. python/python3-lockfile: Added (file locking module). python/python3-pandas: Note on why we can't update. python/python3-pdm: Version bump to 2.12.3 python/python3-platformdirs: Version bump to 4.2.0 python/python3-playsound: Added (Python sound library). python/python3-plotly: Added (graphing library). python/python3-pluggy: Version bump to 1.4.0 python/python3-profilehooks: Added (Python decorators). python/python3-pytest: Version bump to 8.0.0 python/python3-qbittorrent-api: Version bump to 2024.1.58 python/python3-routes: Add missing chown step. python/python3-slugify: Version bump to 8.0.3 python/python3-tenacity: Added (retrying library). python/python3-tox: Version bump to 4.12.1 python/python3-waitress: Updated for version 3.0.0. python/python3-watchdog: Update for 4.0.0 python/python3-webhelpers2: Updated for version 2.1. python/scikit-learn: Version bump to 1.4.0 system/Iosevka-aile: Updated for version 28.1.0. system/Iosevka-etoile: Updated for version 28.1.0. system/OpenSnitch: Updated for version 1.6.5. system/augeas: Updated for version 1.14.1. system/clamav: Updated for version 1.3.0. system/containerd: Updated for version 1.7.13. system/docker-cli: Updated for version 24.0.9. system/docker-proxy: Updated for version 20231021_3f00484. system/docker: Updated for version 24.0.9. system/epson-printer-utility: Updated for version 1.1.3. system/fnt: Updated for version 1.5. system/fonts-devanagari-extra: Added (system fonts). system/fonts-sinhala-extra: Added (extra sinhala fonts). system/lcdf-typetools: Updated for version 2.110. system/locust: Updated for version 2.22.0. system/lxqt-archiver: Added (LXQT Archiver). system/motion: Updated for version 4.6.0. system/mount-zip: Updated for version 1.0.12. system/netdata: Updated for version 1.44.2. system/nvidia-kernel: Add patch for 6.x kernels. system/nvidia-legacy470-kernel: Add patch for 6.x kernels. system/nvidia-open-kernel: Add patch for 6.x kernels. system/pcem: Update home page. system/pledge: Added (Port of OpenBSD pledge). system/rsyslog: Updated for version 8.2312.0. system/runc: Fix GITSHA. system/slackrepo: Updated for version 20240209. system/telegraf: Updated for version 1.29.4 system/usbrelay: Updated for version 1.2.1. system/vhba-module: Update for 20240202 system/yash: Update home page. +--------------------------+ -- 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 emmanueln at gmail.com Sat Feb 10 14:10:38 2024 From: emmanueln at gmail.com (Emmanuel) Date: Sat, 10 Feb 2024 11:10:38 -0300 Subject: [Slackbuilds-users] Larry Hajali's SlackBuilds In-Reply-To: <20240210094349.4ad64ace246fe727daf20983@laposte.net> References: <20240210094349.4ad64ace246fe727daf20983@laposte.net> Message-ID: On Sat, Feb 10, 2024 at 5:44?AM Arnaud via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > > Are Larry Hajali's SlackBuilds up for grabs? There has only been one > update > > from him since April 2021 and that was in May of 2022[1]. I found this > > because another python3 package I'm working on required lxml and it > pulled > > in several python2 packages as dependencies, so I'd like to split lxml > into > > python2 and python3 packages. It seems many of his other python packages > > could use naming changes and/or splits. > > > > If they are available, I can take the following as they're dependencies > for > > some of the SlackBuilds I maintain: > > > > libraries/libcec/ > > libraries/libnfs/ > > libraries/platform/ > > libraries/tinyxml/ > > libraries/tinyxml2/ > > python/lxml/ > > > > The remaining SlackBuilds are: > > [...a lot...] > > > > Thanks, > > Jeremy > > > > [1] > > > https://git.slackbuilds.org/slackbuilds/log/?h=15.0&qt=author&q=Larry+Hajali > > If that is the case, my own Slackbuilds have dnspython and tinyxml2 as > requirements. > I'd be ok to maintain dnspython until it dies, as I'm already maintainer of > python3-dnspython. > > If really those slackbuilds are abandoned I could take care of those ones : > office/grisbi because I use it > system/dosemu, so I'll maintain almost anything DOS-related ^^ > network/nginx to cuddle along my darkhttpd and thttpd > office/texmaker, office/texstudio and office/sigil, because they ought to > be > maintained. > And also those games because I like games : games/megaglest, > games/alienarena, > games/chromium-bsu, games/assaultcube, ggames/lestae, games/opensonic, > games/dustrac. > > Hello, I can maintain office/texstudio and office/texmaker if no one else wants them, I use texstudio often. Best regards. > - Yth. > _______________________________________________ > 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/ > > -- ***************** Emmanuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From rcb at beco.cc Sun Feb 11 12:38:57 2024 From: rcb at beco.cc (Ruben Carlo Benante) Date: Sun, 11 Feb 2024 09:38:57 -0300 Subject: [Slackbuilds-users] Bear missing libraries Message-ID: <18d982bb277.ed707da2695996.8222601866956036279@beco.cc> Hello there Ivan Kovmir, hello guys, The software Bear ( https://slackbuilds.org/repository/15.0/development/Bear/ ) is complaining about missing libraries in Slackware 15.0: * bear: error [...]: libgrpc++.so.1: cannot open shared object: No such file or directory * bear: error [...]: libgrpc.so.9: cannot open shared object: No such file or directory * bear: error [...]:?libgpr.so.9: cannot open shared object: No such file or directory * bear: error [...]:?libspdlog.so.1.11: cannot open shared object: No such file or directory * bear: error [...]:?libfmt.so.9: cannot open shared object: No such file or directory Could you take a peek at it, if you be kind? Thanks a bucket. Cordialmente, Ruben -- Dr. Beco AI Researcher -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sun Feb 11 13:21:08 2024 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 11 Feb 2024 14:21:08 +0100 Subject: [Slackbuilds-users] Bear missing libraries In-Reply-To: <18d982bb277.ed707da2695996.8222601866956036279@beco.cc> References: <18d982bb277.ed707da2695996.8222601866956036279@beco.cc> Message-ID: hi Ruben, the error you are reporting is because you most probably built Bear or against older versions of fmt and/or grpc: try to rebuild Bear (and everything on which it depends which build scripts are hosted on SBo). when you do that you will discover that the version of Bear we have here (3.1.1) cannot be built because of the new fmt: just build version 3.1.3 and that will work ok (I'll push a fix in our git for that). Matteo Il giorno dom 11 feb 2024 alle ore 13:39 Ruben Carlo Benante via SlackBuilds-users ha scritto: > Hello there Ivan Kovmir, hello guys, > > The software Bear ( > https://slackbuilds.org/repository/15.0/development/Bear/ ) is > complaining about missing libraries in Slackware 15.0: > > * bear: error [...]: libgrpc++.so.1: cannot open shared object: No such > file or directory > * bear: error [...]: libgrpc.so.9: cannot open shared object: No such file > or directory > * bear: error [...]: libgpr.so.9: cannot open shared object: No such file > or directory > * bear: error [...]: libspdlog.so.1.11: cannot open shared object: No such > file or directory > * bear: error [...]: libfmt.so.9: cannot open shared object: No such file > or directory > > Could you take a peek at it, if you be kind? > > Thanks a bucket. > > Cordialmente, > > Ruben > > -- > Dr. Beco > AI Researcher > > > > _______________________________________________ > 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 rcb at beco.cc Sun Feb 11 14:11:33 2024 From: rcb at beco.cc (Ruben Carlo Benante) Date: Sun, 11 Feb 2024 11:11:33 -0300 Subject: [Slackbuilds-users] Bear missing libraries In-Reply-To: References: <18d982bb277.ed707da2695996.8222601866956036279@beco.cc> Message-ID: <18d988078f8.e1bdf2de701975.2609421241027388473@beco.cc> Ciao Matteo, Indeed Bear-3.1.1 cannot be build. ( /usr/include/fmt/core.h:1600:63: error: ) I guess Bear 3.1.1 was already installed and fmt upgraded, breaking it. I'll take a look at Bear 3.1.3. Appreciate your disposition to fix our sbo git! Cordialmente, Ruben -- Dr. Beco AI Researcher ---- On Sun, 11 Feb 2024 10:21:08 -0300 Matteo Bernardini wrote --- hi Ruben, the error you are reporting is because you most probably built Bear or against older versions of fmt and/or grpc: try to rebuild Bear (and everything on which it depends which build scripts are hosted on SBo). when you do that you will discover that the version of Bear we have here (3.1.1) cannot be built because of the new fmt: just build version 3.1.3 and that will work ok (I'll push a fix in our git for that). Matteo Il giorno dom 11 feb 2024 alle ore 13:39 Ruben Carlo Benante via SlackBuilds-users ha scritto: Hello there Ivan Kovmir, hello guys, The software Bear ( https://slackbuilds.org/repository/15.0/development/Bear/ ) is complaining about missing libraries in Slackware 15.0: * bear: error [...]: libgrpc++.so.1: cannot open shared object: No such file or directory * bear: error [...]: libgrpc.so.9: cannot open shared object: No such file or directory * bear: error [...]:?libgpr.so.9: cannot open shared object: No such file or directory * bear: error [...]:?libspdlog.so.1.11: cannot open shared object: No such file or directory * bear: error [...]:?libfmt.so.9: cannot open shared object: No such file or directory Could you take a peek at it, if you be kind? Thanks a bucket. Cordialmente, Ruben -- Dr. Beco AI Researcher _______________________________________________ SlackBuilds-users mailing list mailto: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 mab974 at misouk.com Sun Feb 11 17:12:34 2024 From: mab974 at misouk.com (Mab974) Date: Sun, 11 Feb 2024 21:12:34 +0400 Subject: [Slackbuilds-users] mongo-tools problem Message-ID: <20240211211234.aed6b2341803ff86ab58286f@misouk.com> Hi all, Impossible for me to build the latest version of mongo-tools v100.9.4. the package is build but the bin directory is empty. In the log file errors concern the versions of google-go. Did I miss something? Regards -*- Mab974 From heiko.rosemann at web.de Sun Feb 11 21:54:01 2024 From: heiko.rosemann at web.de (Heiko Rosemann) Date: Sun, 11 Feb 2024 22:54:01 +0100 Subject: [Slackbuilds-users] opera-ffmpeg-codecs needs update for opera-107... Message-ID: <29ab3c27-3ca2-4811-a0d0-2c95661bf226@web.de> Hi everyone, with yesterday's update of opera, I can't play any videos anymore. I'm guessing that's because 107.x requires a newer opera-ffmpeg-codecs than the 0.83.0 we have at the moment. I seem to recall some discussions about both opera and opera-ffmpeg-codecs being orphaned, but can't find them for reference. So: Is anyone working on opera-ffmpeg-codecs still or should I take over? Thanks for all the great work everyone's putting in, Heiko -- eMails verschl?sseln mit PGP - privacy is your right! Mein PGP-Key zur Verifizierung: http://pgp.mit.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From urchlay at slackware.uk Sun Feb 11 22:32:30 2024 From: urchlay at slackware.uk (B. Watson) Date: Sun, 11 Feb 2024 17:32:30 -0500 (EST) Subject: [Slackbuilds-users] opera-ffmpeg-codecs needs update for opera-107... In-Reply-To: <29ab3c27-3ca2-4811-a0d0-2c95661bf226@web.de> References: <29ab3c27-3ca2-4811-a0d0-2c95661bf226@web.de> Message-ID: On Sun, 11 Feb 2024, Heiko Rosemann via SlackBuilds-users wrote: > So: Is anyone working on opera-ffmpeg-codecs still or should I take over? Looks like its maintainer, Dmitris Zlatanidis, just updated it in January: commit ab0440d8ba06f78e20b1fcdd87ab25de8012db82 Author: Dimitris Zlatanidis Date: Thu Jan 4 23:22:08 2024 +0200 multimedia/opera-ffmpeg-codecs: Updated for version 0.83.0. From heiko.rosemann at web.de Sun Feb 11 23:02:52 2024 From: heiko.rosemann at web.de (Heiko Rosemann) Date: Mon, 12 Feb 2024 00:02:52 +0100 Subject: [Slackbuilds-users] opera-ffmpeg-codecs needs update for opera-107... In-Reply-To: References: <29ab3c27-3ca2-4811-a0d0-2c95661bf226@web.de> Message-ID: <68b0e5ae-80fb-43a8-9884-a1e1cf46c481@web.de> On 2/11/24 23:32, B. Watson wrote: > On Sun, 11 Feb 2024, Heiko Rosemann via SlackBuilds-users wrote: > >> So: Is anyone working on opera-ffmpeg-codecs still or should I take over? > > Looks like its maintainer, Dmitris Zlatanidis, just updated it in January: Thanks, I CC'd him on my first email already (with the address in the .info file) But your message triggered me into searching, and I found the discussion I had in mind, titled Updates - 20231216.1. It ended with him taking over maintainership, so yay, no extra work for me :) Heiko -- eMails verschl?sseln mit PGP - privacy is your right! Mein PGP-Key zur Verifizierung: http://pgp.mit.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From lockywolf at gmail.com Thu Feb 8 15:02:54 2024 From: lockywolf at gmail.com (Vladimir Nikishkin) Date: Thu, 8 Feb 2024 23:02:54 +0800 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <9e6d2717-8b8e-2f22-d08b-1a4f53fd89a1@open-t.co.uk> Message-ID: It might be that they haven't changed much in their cmake in a point-release. It might be that removing that check and introducing some crutch to work around that one place where they use the new feature will do. Tim Dickson via SlackBuilds-users ? 2024?2?8??? 22:24??? > you could do a cmake-202x opt package like was done for 14.2 with the > newest version of cmake > have a look at it's README_SBo.txt for tips as well. > regards, Tim > > On 08/02/2024 11:48, Sebastian Arcus wrote: > > > > > > _______________________________________________ > 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 viel.losero at gmail.com Sun Feb 11 11:35:22 2024 From: viel.losero at gmail.com (viel.losero at gmail.com) Date: Sun, 11 Feb 2024 12:35:22 +0100 Subject: [Slackbuilds-users] unattended package python3 3.7.2 Message-ID: <7ee6471d-870c-44fa-ae93-5e38e2255442@gmail.com> Hi, I think i found an unattended package. python3 3.7.2 from last update with rsync, the python3.tar.gz seems that is old. I found it because don't have an extracted dir with the SlackBuild file and others ... and that make me curious. [root at arcadia t1]# grep python3 /var/lib/srpm/repositories/sbo/15.0/CHECKSUMS.md5 | tail -20 c2124db45079c4a5da5b3bcef405ecf5? ./python/python3-zxcvbn/README 53fea0b9500c79fdce7bd062a0ed4c1d ./python/python3-zxcvbn/python3-zxcvbn.SlackBuild a33997f0ddb2f53a45ecbafaa937192e ./python/python3-zxcvbn/python3-zxcvbn.info 5a57d63831a7525b534550277e4a07ec ./python/python3-zxcvbn/slack-desc a22977ecb64571bec6ad412ffa807102? ./python/python3.tar.gz ab6fb66d89dd19f037d24c6bdee81608? ./python/python3.tar.gz.asc 0d1931eeacdf713b2ba148b2fc77ad43 ./system/python3-docker-compose.tar.gz 288689b99fdeec238f258a58c263f09e ./system/python3-docker-compose.tar.gz.asc f75c198eff9a1380fd7fd36a6d58fce8 ./system/python3-docker-compose/README 1022470b1dba49604f7bab796001098c ./system/python3-docker-compose/python3-docker-compose.SlackBuild 1b4a5d97267ea0cbfec736e0dc4a1f33 ./system/python3-docker-compose/python3-docker-compose.info ba06334d025d892dcf9f9390a6057240 ./system/python3-docker-compose/slack-desc 47327a75b6b992f233db9889919d6148 ./system/python3-nvidia-ml-py.tar.gz a571f1b03c02a3a35fafc1b27bff7e1e ./system/python3-nvidia-ml-py.tar.gz.asc da2082d1f5880f5150f220996b6ac3d2 ./system/python3-nvidia-ml-py/README 3d460b5e71059f7e761f329a9789b2ad ./system/python3-nvidia-ml-py/python3-nvidia-ml-py.SlackBuild 2bdc12478783998e3c05ea34dbfed411 ./system/python3-nvidia-ml-py/python3-nvidia-ml-py.info f4020b4564a1fd325dad9a5a6fae5c45 ./system/python3-nvidia-ml-py/slack-desc 4bd0be69e441b4131997982b9a0861c7? ./system/python3-urwid.tar.gz 2372411b8895787ae82c8c86890114d5 ./system/python3-urwid.tar.gz.asc [root at arcadia t1]# Happy to help, regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: From viel.losero at gmail.com Mon Feb 12 00:16:59 2024 From: viel.losero at gmail.com (viel.losero at gmail.com) Date: Mon, 12 Feb 2024 01:16:59 +0100 Subject: [Slackbuilds-users] Fwd: unattended package python3 3.7.2 In-Reply-To: <7ee6471d-870c-44fa-ae93-5e38e2255442@gmail.com> References: <7ee6471d-870c-44fa-ae93-5e38e2255442@gmail.com> Message-ID: <657c011b-0a7f-42e3-9cbf-9edc6e81d96b@gmail.com> Hi again, Don't know if the information is helpful but more than 800 pkg's remain uncompressed, maybe out of date? I don't know if u store it for templates or other reasons. -----stripped------ bloodcm blueMSX-libretro bsnes-mercury cannonball-libretro chocolate_duke3D fbalpha fmsx-libretro gambatte-libretro gens-gs glPortal gw-libretro ^C [root at arcadia t1]# for i in $(grep .asc /opt/slackware-repositories/slackbuilds/15.0/CHECKSUMS.md5 | cut -d" " -f3 |rev | cut -d. -f4 | cut -d/ -f1| rev) ; do if [ "$(grep $i /opt/slackware-repositories/slackbuilds/15.0/CHECKSUMS.md5 | wc -l)" == "2" ] ; then echo $i ; fi? ; done | wc -l 803 [root at arcadia t1]# Cheers, -------- Forwarded Message -------- From: - Sun <>, 26 GMT <> X-Mozilla-Status: 0001 X-Mozilla-Status2: 00800000 Content-Type: multipart/alternative; boundary="------------8Ti6ei1b5em3QFTEhtIhpt8F" Message-ID: <7ee6471d-870c-44fa-ae93-5e38e2255442 at gmail.com> Date: Sun, 11 Feb 2024 12:35:22 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: slackbuilds-users at slackbuilds.org From: viel.losero at gmail.com Subject: unattended package python3 3.7.2 Hi, I think i found an unattended package. python3 3.7.2 from last update with rsync, the python3.tar.gz seems that is old. I found it because don't have an extracted dir with the SlackBuild file and others ... and that make me curious. [root at arcadia t1]# grep python3 /var/lib/srpm/repositories/sbo/15.0/CHECKSUMS.md5 | tail -20 c2124db45079c4a5da5b3bcef405ecf5? ./python/python3-zxcvbn/README 53fea0b9500c79fdce7bd062a0ed4c1d ./python/python3-zxcvbn/python3-zxcvbn.SlackBuild a33997f0ddb2f53a45ecbafaa937192e ./python/python3-zxcvbn/python3-zxcvbn.info 5a57d63831a7525b534550277e4a07ec ./python/python3-zxcvbn/slack-desc a22977ecb64571bec6ad412ffa807102? ./python/python3.tar.gz ab6fb66d89dd19f037d24c6bdee81608? ./python/python3.tar.gz.asc 0d1931eeacdf713b2ba148b2fc77ad43 ./system/python3-docker-compose.tar.gz 288689b99fdeec238f258a58c263f09e ./system/python3-docker-compose.tar.gz.asc f75c198eff9a1380fd7fd36a6d58fce8 ./system/python3-docker-compose/README 1022470b1dba49604f7bab796001098c ./system/python3-docker-compose/python3-docker-compose.SlackBuild 1b4a5d97267ea0cbfec736e0dc4a1f33 ./system/python3-docker-compose/python3-docker-compose.info ba06334d025d892dcf9f9390a6057240 ./system/python3-docker-compose/slack-desc 47327a75b6b992f233db9889919d6148 ./system/python3-nvidia-ml-py.tar.gz a571f1b03c02a3a35fafc1b27bff7e1e ./system/python3-nvidia-ml-py.tar.gz.asc da2082d1f5880f5150f220996b6ac3d2 ./system/python3-nvidia-ml-py/README 3d460b5e71059f7e761f329a9789b2ad ./system/python3-nvidia-ml-py/python3-nvidia-ml-py.SlackBuild 2bdc12478783998e3c05ea34dbfed411 ./system/python3-nvidia-ml-py/python3-nvidia-ml-py.info f4020b4564a1fd325dad9a5a6fae5c45 ./system/python3-nvidia-ml-py/slack-desc 4bd0be69e441b4131997982b9a0861c7? ./system/python3-urwid.tar.gz 2372411b8895787ae82c8c86890114d5 ./system/python3-urwid.tar.gz.asc [root at arcadia t1]# Happy to help, regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Mon Feb 12 12:59:08 2024 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 12 Feb 2024 06:59:08 -0600 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: <92d7a3be-fffd-b54e-8055-9c12182fd923@open-t.co.uk> References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <9e6d2717-8b8e-2f22-d08b-1a4f53fd89a1@open-t.co.uk> <92d7a3be-fffd-b54e-8055-9c12182fd923@open-t.co.uk> Message-ID: hit me up on irc... ill gladly teach you how to do it. On Fri, Feb 9, 2024, 6:12?AM Sebastian Arcus wrote: > Sounds like an option - but a bit above my current level of skill. If > anyone wants to contribute a patch, I'm sure the admins will take a look > > > On 08/02/2024 16:32, Fernando Lopez wrote: > > why dont you use the previous version of cmake. i am pretty sure it will > > compile. just patch your program. hopefully it will work. > > > > On Thu, Feb 8, 2024, 7:24?AM Tim Dickson via SlackBuilds-users > > > > wrote: > > > > you could do a cmake-202x opt package like was done for 14.2 with the > > newest version of cmake > > have a look at it's README_SBo.txt for tips as well. > > regards, Tim > > > > On 08/02/2024 11:48, Sebastian Arcus wrote: > > > > > > > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arnaud.garcia-fernandez at laposte.net Mon Feb 12 13:06:07 2024 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Mon, 12 Feb 2024 13:06:07 +0000 Subject: [Slackbuilds-users] unattended package python3 3.7.2 In-Reply-To: <7ee6471d-870c-44fa-ae93-5e38e2255442@gmail.com> References: <7ee6471d-870c-44fa-ae93-5e38e2255442@gmail.com> Message-ID: <0050EF50-7F6A-4B5F-B964-954252B56EEB@laposte.net> Can't it be some leftovers from a previous rsync ? Because there's no python3 package since 15.0, as it has been a part of Slackware stable since the release of 15.0. - Yth Le 11 f?vrier 2024 11:35:22 UTC, "viel.losero at gmail.com" a ?crit?: >Hi, >I think i found an unattended package. python3 3.7.2 > >from last update with rsync, the python3.tar.gz seems that is old. I found it because don't have an extracted dir with the SlackBuild file and others ... and that make me curious. > >[root at arcadia t1]# grep python3 /var/lib/srpm/repositories/sbo/15.0/CHECKSUMS.md5 | tail -20 >c2124db45079c4a5da5b3bcef405ecf5? ./python/python3-zxcvbn/README >53fea0b9500c79fdce7bd062a0ed4c1d ./python/python3-zxcvbn/python3-zxcvbn.SlackBuild >a33997f0ddb2f53a45ecbafaa937192e ./python/python3-zxcvbn/python3-zxcvbn.info >5a57d63831a7525b534550277e4a07ec ./python/python3-zxcvbn/slack-desc >a22977ecb64571bec6ad412ffa807102? ./python/python3.tar.gz >ab6fb66d89dd19f037d24c6bdee81608? ./python/python3.tar.gz.asc >0d1931eeacdf713b2ba148b2fc77ad43 ./system/python3-docker-compose.tar.gz >288689b99fdeec238f258a58c263f09e ./system/python3-docker-compose.tar.gz.asc >f75c198eff9a1380fd7fd36a6d58fce8 ./system/python3-docker-compose/README >1022470b1dba49604f7bab796001098c ./system/python3-docker-compose/python3-docker-compose.SlackBuild >1b4a5d97267ea0cbfec736e0dc4a1f33 ./system/python3-docker-compose/python3-docker-compose.info >ba06334d025d892dcf9f9390a6057240 ./system/python3-docker-compose/slack-desc >47327a75b6b992f233db9889919d6148 ./system/python3-nvidia-ml-py.tar.gz >a571f1b03c02a3a35fafc1b27bff7e1e ./system/python3-nvidia-ml-py.tar.gz.asc >da2082d1f5880f5150f220996b6ac3d2 ./system/python3-nvidia-ml-py/README >3d460b5e71059f7e761f329a9789b2ad ./system/python3-nvidia-ml-py/python3-nvidia-ml-py.SlackBuild >2bdc12478783998e3c05ea34dbfed411 ./system/python3-nvidia-ml-py/python3-nvidia-ml-py.info >f4020b4564a1fd325dad9a5a6fae5c45 ./system/python3-nvidia-ml-py/slack-desc >4bd0be69e441b4131997982b9a0861c7? ./system/python3-urwid.tar.gz >2372411b8895787ae82c8c86890114d5 ./system/python3-urwid.tar.gz.asc >[root at arcadia t1]# > >Happy to help, > >regards. > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.public at protonmail.com Mon Feb 12 14:03:10 2024 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 12 Feb 2024 14:03:10 +0000 Subject: [Slackbuilds-users] Fwd: unattended package python3 3.7.2 In-Reply-To: <657c011b-0a7f-42e3-9cbf-9edc6e81d96b@gmail.com> References: <7ee6471d-870c-44fa-ae93-5e38e2255442@gmail.com> <657c011b-0a7f-42e3-9cbf-9edc6e81d96b@gmail.com> Message-ID: <9KsRmvC-0CVibG2RPjgz3bs80riBPKxfDcrExMfMmSD9Y3fq0MLtRzzv--hlFoXTdchqZnxq5w8aqtznvWCU10tGIQL0pCxVNHbpnRvC6IQ=@protonmail.com> On Sunday, February 11th, 2024 at 6:16 PM, viel.losero at gmail.com wrote: > Hi again, > > Don't know if the information is helpful but more than 800 pkg's remain uncompressed, maybe out of date? > > I don't know if u store it for templates or other reasons. > > -----stripped------ > > bloodcm > blueMSX-libretro > bsnes-mercury > cannonball-libretro > chocolate_duke3D > fbalpha > fmsx-libretro > gambatte-libretro > gens-gs > glPortal > gw-libretro > ^C > [root at arcadia t1]# for i in $(grep .asc /opt/slackware-repositories/slackbuilds/15.0/CHECKSUMS.md5 | cut -d" " -f3 |rev | cut -d. -f4 | > cut -d/ -f1| rev) ; do if [ "$(grep $i /opt/slackware-repositories/slackbuilds/15.0/CHECKSUMS.md5 | wc -l)" == "2" ] ; then echo $i ; fi ; done | wc -l > 803 > [root at arcadia t1]# > > Cheers, > > > > -------- Forwarded Message -------- > > From: > > - Sun <>, 26 GMT <> > > X-Mozilla-Status: > > 0001 > > X-Mozilla-Status2: > > 00800000 > > Content-Type: > > multipart/alternative; boundary="------------8Ti6ei1b5em3QFTEhtIhpt8F" > > Message-ID: > > <7ee6471d-870c-44fa-ae93-5e38e2255442 at gmail.com> > > Date: > > Sun, 11 Feb 2024 12:35:22 +0100 > > MIME-Version: > > 1.0 > > User-Agent: > > Mozilla Thunderbird > > Content-Language: > > en-US > > To: > > slackbuilds-users at slackbuilds.org > > From: > > viel.losero at gmail.com > > Subject: > > unattended package python3 3.7.2 > > > > Hi, > I think i found an unattended package. python3 3.7.2 > > from last update with rsync, the python3.tar.gz seems that is old. I found it because don't have an extracted dir with the SlackBuild file and others ... and that make me curious. > > [root at arcadia t1]# grep python3 /var/lib/srpm/repositories/sbo/15.0/CHECKSUMS.md5 | tail -20 > c2124db45079c4a5da5b3bcef405ecf5 ./python/python3-zxcvbn/README > 53fea0b9500c79fdce7bd062a0ed4c1d ./python/python3-zxcvbn/python3-zxcvbn.SlackBuild > a33997f0ddb2f53a45ecbafaa937192e ./python/python3-zxcvbn/python3-zxcvbn.info > 5a57d63831a7525b534550277e4a07ec ./python/python3-zxcvbn/slack-desc > a22977ecb64571bec6ad412ffa807102 ./python/python3.tar.gz > ab6fb66d89dd19f037d24c6bdee81608 ./python/python3.tar.gz.asc > 0d1931eeacdf713b2ba148b2fc77ad43 ./system/python3-docker-compose.tar.gz > 288689b99fdeec238f258a58c263f09e ./system/python3-docker-compose.tar.gz.asc > f75c198eff9a1380fd7fd36a6d58fce8 ./system/python3-docker-compose/README > 1022470b1dba49604f7bab796001098c ./system/python3-docker-compose/python3-docker-compose.SlackBuild > 1b4a5d97267ea0cbfec736e0dc4a1f33 ./system/python3-docker-compose/python3-docker-compose.info > ba06334d025d892dcf9f9390a6057240 ./system/python3-docker-compose/slack-desc > 47327a75b6b992f233db9889919d6148 ./system/python3-nvidia-ml-py.tar.gz > a571f1b03c02a3a35fafc1b27bff7e1e ./system/python3-nvidia-ml-py.tar.gz.asc > da2082d1f5880f5150f220996b6ac3d2 ./system/python3-nvidia-ml-py/README > 3d460b5e71059f7e761f329a9789b2ad ./system/python3-nvidia-ml-py/python3-nvidia-ml-py.SlackBuild > 2bdc12478783998e3c05ea34dbfed411 ./system/python3-nvidia-ml-py/python3-nvidia-ml-py.info > f4020b4564a1fd325dad9a5a6fae5c45 ./system/python3-nvidia-ml-py/slack-desc > 4bd0be69e441b4131997982b9a0861c7 ./system/python3-urwid.tar.gz > 2372411b8895787ae82c8c86890114d5 ./system/python3-urwid.tar.gz.asc > [root at arcadia t1]# > > Happy to help, > > regards. > I think OP found in oversight in the SBo tree. Removed packages are not fully being removed. That is, the *.tar.gz and *.tar.gz.asc files are not being deleted. For example, QtiPlot was removed March 2022 but QtiPlot.tar.gz and QtiPlot.tar.gz.asc are still available at https://slackbuilds.org/slackbuilds/15.0/academic/ See https://www.linuxquestions.org/questions/slackware-14/slackbuilds-rsync-have-uncompressed-packages-4175733765/#post6483028 Erich From willysr at slackbuilds.org Mon Feb 12 14:06:11 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 12 Feb 2024 21:06:11 +0700 Subject: [Slackbuilds-users] Fwd: unattended package python3 3.7.2 In-Reply-To: <9KsRmvC-0CVibG2RPjgz3bs80riBPKxfDcrExMfMmSD9Y3fq0MLtRzzv--hlFoXTdchqZnxq5w8aqtznvWCU10tGIQL0pCxVNHbpnRvC6IQ=@protonmail.com> References: <7ee6471d-870c-44fa-ae93-5e38e2255442@gmail.com> <657c011b-0a7f-42e3-9cbf-9edc6e81d96b@gmail.com> <9KsRmvC-0CVibG2RPjgz3bs80riBPKxfDcrExMfMmSD9Y3fq0MLtRzzv--hlFoXTdchqZnxq5w8aqtznvWCU10tGIQL0pCxVNHbpnRvC6IQ=@protonmail.com> Message-ID: <1648f172-de51-4098-af37-ea5bf907651d@slackbuilds.org> > I think OP found in oversight in the SBo tree. Removed packages are not fully being removed. That is, the *.tar.gz and *.tar.gz.asc files are not being deleted. For example, QtiPlot was removed March 2022 but QtiPlot.tar.gz and QtiPlot.tar.gz.asc are still available at https://slackbuilds.org/slackbuilds/15.0/academic/ > > See https://www.linuxquestions.org/questions/slackware-14/slackbuilds-rsync-have-uncompressed-packages-4175733765/#post6483028 Well, they should have been removed, but probably i missed that part :) it's now removed, but let us know if you found any leftover tarball that should have been deleted -- 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 lramos.prof at yahoo.com.br Mon Feb 12 14:39:31 2024 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Mon, 12 Feb 2024 11:39:31 -0300 Subject: [Slackbuilds-users] Updates - 20240210.1 In-Reply-To: References: Message-ID: willy, I have run into problems here when upgrading filezilla. My diagnosis is that the configure script from filezilla found an incompatible version when running wx-config. It has found a version 3.0 "config" (actually, I'm not sure what this component really is) which belongs to wxGTK3 (3.0.5), when it should get the version 3.2.4 from wxWidgets (3.2.4). I could work around this applying the patch below to filezilla.Slackbuild, which makes the configure script grab the correct "config": diff --git a/network/filezilla/filezilla.SlackBuild b/network/filezilla/filezilla.SlackBuild index b986f14f0a..639e14ff78 100644 --- a/network/filezilla/filezilla.SlackBuild +++ b/network/filezilla/filezilla.SlackBuild @@ -86,7 +86,7 @@ find -L . \ # Needed for gcc >= 10.x patch -p1 < $CWD/interface_Mainfrm_h_include_list.patch -WX_CONFIG_NAME=/usr/lib${LIBDIRSUFFIX}/wx/config/gtk3-unicode-3.0 \ +WX_CONFIG_NAME=/usr/lib${LIBDIRSUFFIX}/wx/config/gtk3-unicode-3.2 \ ./configure \ --prefix=/usr \ --libdir=/usr/lib${LIBDIRSUFFIX} \ and then I could build filezilla. Hope it helps, Luiz Carlos Ramos lramos.prof at yahoo.com.br S?o Paulo - Brazil On Sat, Feb 10, 2024 at 04:31:27PM +0700, Willy Sudiarto Raharjo wrote: > This week, we have another great news to share with you > > Andrew Clemons has already finished deploying our CI engine in Gitlab > platform and he has been doing some extensive testing for the last few days > and it seems to work as expected, so you can now send your merge request to > gitlab and have our CI engine test your submission. > > As a reminder, please avoid using local copy of the SlackBuild for > submitting updates as we might have modify your script to make sure it stays > consistent and compliance with our template. It's always recommended to use > the SlackBuild files from our website or even better, keep a local copy of > our repository from SBo, github or gitlab and start from there. > > If you want to send your updates via Github, you can do so by following this > guide: https://slackbuilds.org/SBo-Github-Workflows.txt > The same workflow can be used for gitlab platform as well with some > adjustment. > > have a nice weekend :) > > > Sat Feb 10 09:18:29 UTC 2024 > academic/fet: Updated for version 6.16.0. > academic/gmsh: Updated for version 4.12.2. > academic/gplates: Added (plate tectonics program). > academic/plus42: Updated for version 1.1.3. > academic/python3-scipy: Version bump to 1.12.0 > accessibility/pastebinit: Updated for version 1.6.2. > audio/qpwgraph: Updated for version 0.6.2 > audio/wildmidi: Update HOMEPAGE. > desktop/calcure: Update DEP. > desktop/engrampa: Updated for version 1.26.2. > desktop/nwg-drawer: Updated for version 0.4.6. > desktop/nwg-look: Updated for version 0.2.6. > desktop/nwg-menu: Updated for version 0.1.2. > desktop/python3-autotiling: Updated for version 1.9. > desktop/xpra: Updated for version 5.0.4, add HTML5 server support. > development/FreeBASIC: Updated for version 1.10.1. > development/atasm: Updated for version 1.23. > development/composer: Updated for version 2.7.0 > development/cosmocc: Added (C library). > development/eisl: Updated for version 3.70. > development/fasm: Updated for version 1.73.32. > development/gambas3: Updated for version 3.19.0. > development/github-desktop: Updated for version 3.3.8. > development/google-go-lang: Updated for version 1.21.6. > development/jupyter-ipykernel: Update for 6.29.2 > development/jupyter-nbconvert: Update for 7.15.0 > development/mongodb-shell: Updated for version 2.1.3. > development/quickjs: Updated for version 2024.01.13. > development/rgbds: Updated for version 0.7.0. > development/uftrace: Updated for version 20240205_9c1792d > development/yarn: Updated for version 1.22.19. > games/angband: Build tweaks. > games/crawl: Updated for version 0.31.0. > games/devilutionx: Updated for version 1.5.2. > games/freeciv: Updated for version 3.0.10. > games/freedoom: Updated for version 0.13.0. > games/gtklife: Updated for version 5.3. > games/jg-mednafen: Updated for version 1.32.0. > games/jg-mgba: Updated for version 0.10.3. > games/jg-sameboy: Updated for version 0.16.2. > games/openmsx-catapult: Updated for version 19.0 > games/openmsx-debugger: Updated for version 20230717 > games/openmsx: Updated for version 19.1 > games/pioneer: Updated for version 20240203. > games/sl: Updated for version 5.05 > games/x16emu: Added (Commander X16 emulator). > gis/eccodes: Updated for version 2.34.0. > graphics/chafa: Updated for version 1.14.0. > graphics/converseen: Updated for version 0.12.1.0. > graphics/leocad: Updated for version 23.03. > graphics/leocad_pieces: Updated for version 23.06. > graphics/mcomix: Updated for version 3.1.0. > graphics/xbmbrowser: Update xbmbrowser.info > libraries/CLI11: Updated for version 2.4.1. > libraries/Ipopt: Updated for version 3.14.14. > libraries/SFML: Fix pkgconfig and doc files install locations. > libraries/bctoolbox: Updated for version 5.2.2. > libraries/cmark: Updated for version 0.31.0. > libraries/fmt: Updated for version 10.2.0. > libraries/libavif: Updated for version 1.0.3. > libraries/libcbor: Updated for version 0.11.0. > libraries/libfilezilla: Updated for version 0.46.0. > libraries/libmediainfo: Version bump to 24.01 > libraries/libyuv: Updated for version 20240116_95d8726. > libraries/onevpl: Version bump to 2023.4.0 > libraries/simpleini: Updated for version 4.22. > libraries/webkit2gtk4.1: Updated for version 2.42.5. > libraries/webkit2gtk: Updated for version 2.42.5. > libraries/zope.proxy: Updated for version 5.2. > misc/Bitwarden-desktop: Updated for version 2024.2.0 > misc/cliphist: Updated for version 0.5.0. > misc/grc: Minor bugfix from Debian. > multimedia/ffmpegfs: Updated for version 2.15. > multimedia/kvazaar: Updated for version 2.3.0. > multimedia/mediainfo: Version bump to 24.01 > multimedia/picard-plugins: Version bump to 7b3b379 > multimedia/picard: Version bump to 2.11 > multimedia/sickchill: Version bump to 2024.2.2 > multimedia/svt-av1: Updated for version 1.8.0. > network/AdGuardHome: Updated for version 0.107.44. > network/ani-cli: Updated for version 4.8. > network/barrier: Updated for version 2.4.0. > network/bozohttpd: Updated for version 20240126. > network/brave-browser: Updated for version 1.62.162. > network/discord: Version bump to 0.0.42 > network/dnsproxy-bin: Updated for version 0.65.0. > network/easyrsa: Updated for version 3.1.7. > network/filezilla: Updated for version 3.66.5. > network/go-sendxmpp: Bump go version. > network/goimapnotify: Updated for version 2.3.11. > network/iperf3: Updated for version 3.16. > network/neomutt: Updated for version 20240201. > network/ocserv: Added (OpenConnect VPN). > network/opera: Updated for version 107.0.5045.15. > network/protonmail-bridge: Updated for version 3.8.2. > network/signal-desktop: Updated for version 6.47.0. > network/syncthing: Updated for version 1.27.3. > network/tailscale: Updated for version 1.58.2. > network/telegram: Updated for version 4.14.13. > network/toot: Updated for version 0.41.1. > network/uwsgi: Updated for version 2.0.24. > network/vivaldi: Updated for version 6.5.3206.61. > network/wego: Added (openweathermap app). > network/yle-dl: Updated for version 20240130. > network/ytfzf: Updated for version 2.6.2. > office/MasterPDFEditor: Updated for version 5.9.82. > office/calibre-bin: Updated for version 7.5.1. > office/fbreader: Fix DOWNLOAD. > office/smoffice2024: Updated for version 2024_1208. > office/tapecalc: Updated for version 20240110. > perl/perl-Error: Added (perl error). > perl/perl-Mojolicious: Updated for version 9.35. > python/Kallithea: Updated patch. > python/certbot-dns-cloudflare: Updated for version 2.8.0 > python/icalendar: Removed (use python3-icalendar). > python/ipython: Note on why we can't update. > python/python-mysql-replication: Updated for version 1.0.6. > python/python3-BTrees: Updated for version 5.2. > python/python3-PyGithub: Version bump to 2.2.0 > python/python3-cachecontrol: Version bump to 0.14.0 > python/python3-cloudflare: Updater for version 2.17.0 > python/python3-daemon: Updated dependencies. > python/python3-dogpile.cache: Updated for version 1.3.1. > python/python3-lockfile: Added (file locking module). > python/python3-pandas: Note on why we can't update. > python/python3-pdm: Version bump to 2.12.3 > python/python3-platformdirs: Version bump to 4.2.0 > python/python3-playsound: Added (Python sound library). > python/python3-plotly: Added (graphing library). > python/python3-pluggy: Version bump to 1.4.0 > python/python3-profilehooks: Added (Python decorators). > python/python3-pytest: Version bump to 8.0.0 > python/python3-qbittorrent-api: Version bump to 2024.1.58 > python/python3-routes: Add missing chown step. > python/python3-slugify: Version bump to 8.0.3 > python/python3-tenacity: Added (retrying library). > python/python3-tox: Version bump to 4.12.1 > python/python3-waitress: Updated for version 3.0.0. > python/python3-watchdog: Update for 4.0.0 > python/python3-webhelpers2: Updated for version 2.1. > python/scikit-learn: Version bump to 1.4.0 > system/Iosevka-aile: Updated for version 28.1.0. > system/Iosevka-etoile: Updated for version 28.1.0. > system/OpenSnitch: Updated for version 1.6.5. > system/augeas: Updated for version 1.14.1. > system/clamav: Updated for version 1.3.0. > system/containerd: Updated for version 1.7.13. > system/docker-cli: Updated for version 24.0.9. > system/docker-proxy: Updated for version 20231021_3f00484. > system/docker: Updated for version 24.0.9. > system/epson-printer-utility: Updated for version 1.1.3. > system/fnt: Updated for version 1.5. > system/fonts-devanagari-extra: Added (system fonts). > system/fonts-sinhala-extra: Added (extra sinhala fonts). > system/lcdf-typetools: Updated for version 2.110. > system/locust: Updated for version 2.22.0. > system/lxqt-archiver: Added (LXQT Archiver). > system/motion: Updated for version 4.6.0. > system/mount-zip: Updated for version 1.0.12. > system/netdata: Updated for version 1.44.2. > system/nvidia-kernel: Add patch for 6.x kernels. > system/nvidia-legacy470-kernel: Add patch for 6.x kernels. > system/nvidia-open-kernel: Add patch for 6.x kernels. > system/pcem: Update home page. > system/pledge: Added (Port of OpenBSD pledge). > system/rsyslog: Updated for version 8.2312.0. > system/runc: Fix GITSHA. > system/slackrepo: Updated for version 20240209. > system/telegraf: Updated for version 1.29.4 > system/usbrelay: Updated for version 1.2.1. > system/vhba-module: Update for 20240202 > system/yash: Update home page. > +--------------------------+ > > > -- > Willy Sudiarto Raharjo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From willysr at slackbuilds.org Mon Feb 12 23:50:21 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 13 Feb 2024 06:50:21 +0700 Subject: [Slackbuilds-users] Updates - 20240210.1 In-Reply-To: References: Message-ID: > My diagnosis is that the configure script from filezilla found an > incompatible version when running wx-config. It has found a version 3.0 > "config" (actually, I'm not sure what this component really is) which > belongs to wxGTK3 (3.0.5), when it should get the version 3.2.4 from > wxWidgets (3.2.4). > > I could work around this applying the patch below to > filezilla.Slackbuild, which makes the configure script grab the correct > "config": > > diff --git a/network/filezilla/filezilla.SlackBuild b/network/filezilla/filezilla.SlackBuild > index b986f14f0a..639e14ff78 100644 > --- a/network/filezilla/filezilla.SlackBuild > +++ b/network/filezilla/filezilla.SlackBuild > @@ -86,7 +86,7 @@ find -L . \ > # Needed for gcc >= 10.x > patch -p1 < $CWD/interface_Mainfrm_h_include_list.patch > > -WX_CONFIG_NAME=/usr/lib${LIBDIRSUFFIX}/wx/config/gtk3-unicode-3.0 \ > +WX_CONFIG_NAME=/usr/lib${LIBDIRSUFFIX}/wx/config/gtk3-unicode-3.2 \ > ./configure \ > --prefix=/usr \ > --libdir=/usr/lib${LIBDIRSUFFIX} \ did you recently rebuild any other wx* package besides wxWidgets? that could explain why wx-config point you to the incorrect location as those packages have race condition. Whoever comes last will be the one pointed whenever any packages are locating wx-config. -- 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 lramos.prof at yahoo.com.br Tue Feb 13 13:21:48 2024 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Tue, 13 Feb 2024 10:21:48 -0300 Subject: [Slackbuilds-users] Updates - 20240210.1 In-Reply-To: References: Message-ID: On Tue, Feb 13, 2024 at 06:50:21AM +0700, Willy Sudiarto Raharjo wrote: > > My diagnosis is that the configure script from filezilla found an > > incompatible version when running wx-config. It has found a version 3.0 > > "config" (actually, I'm not sure what this component really is) which > > belongs to wxGTK3 (3.0.5), when it should get the version 3.2.4 from > > wxWidgets (3.2.4). > > > > I could work around this applying the patch below to > > filezilla.Slackbuild, which makes the configure script grab the correct > > "config": > > > > diff --git a/network/filezilla/filezilla.SlackBuild b/network/filezilla/filezilla.SlackBuild > > index b986f14f0a..639e14ff78 100644 > > --- a/network/filezilla/filezilla.SlackBuild > > +++ b/network/filezilla/filezilla.SlackBuild > > @@ -86,7 +86,7 @@ find -L . \ > > # Needed for gcc >= 10.x > > patch -p1 < $CWD/interface_Mainfrm_h_include_list.patch > > > > -WX_CONFIG_NAME=/usr/lib${LIBDIRSUFFIX}/wx/config/gtk3-unicode-3.0 \ > > +WX_CONFIG_NAME=/usr/lib${LIBDIRSUFFIX}/wx/config/gtk3-unicode-3.2 \ > > ./configure \ > > --prefix=/usr \ > > --libdir=/usr/lib${LIBDIRSUFFIX} \ > > did you recently rebuild any other wx* package besides wxWidgets? > that could explain why wx-config point you to the incorrect location as > those packages have race condition. Whoever comes last will be the one > pointed whenever any packages are locating wx-config. > Nope, gtk3-unicode-3.2 is the last one: [user at host:/home/user] $ ls -l /usr/lib64/wx/config/ total 144 -rwxr-xr-x 1 root root 43401 out 14 2021 gtk2-unicode-release-2.8 -rwxr-xr-x 1 root root 48498 fev 21 2022 gtk3-unicode-3.0 -rwxr-xr-x 1 root root 50854 nov 18 15:19 gtk3-unicode-3.2 (gtk3-unicode-3.2 is the one installed alongside wxWidgets; gtk3-unicode-3.0 is the one from wxGTK3) By the other side, I wouldn't be happy to depend on a race condition here (and in any other case). Going more deep, as far as I could learn, this version of filezilla requires this component to be 3.2.1 or newer (see filezilla's ./configure, line 19640). So I would not force ./configure to use gtk3-unicode-3.0 with the env variable WX_CONFIG_NAME; I think it wouldn't find anything different from 3.0, which doesn't satisfy the requirement. By the way, how the build run in systems other than mine? Tks, Luiz > -- > Willy Sudiarto Raharjo > From dickson.tim at googlemail.com Tue Feb 13 14:30:19 2024 From: dickson.tim at googlemail.com (Tim Dickson) Date: Tue, 13 Feb 2024 14:30:19 +0000 Subject: [Slackbuilds-users] update homepage query Message-ID: <1f1930c4-aa3e-4aea-8845-9df5b0cd42cc@googlemail.com> Hi all, there are three slackbuilds I look after which need a homepage update from http to https should I submit 3 updates with .info updated and build no. bumped, or is there an easier way. as the build is identical, maybe the build number doesn't need bumping, but is it possible to do an updated with no change in version or build? the old http home sites still work, they are just permanently redirected to the https versions. regards, Tim From rcb at beco.cc Tue Feb 13 17:48:04 2024 From: rcb at beco.cc (Ruben Carlo Benante) Date: Tue, 13 Feb 2024 14:48:04 -0300 Subject: [Slackbuilds-users] Bear missing libraries In-Reply-To: <20240213113640.nehcnc66ie6kcro2@vps.kovmir.cc> References: <18d982bb277.ed707da2695996.8222601866956036279@beco.cc> <18d988078f8.e1bdf2de701975.2609421241027388473@beco.cc> <20240213113640.nehcnc66ie6kcro2@vps.kovmir.cc> Message-ID: <18da3936a0d.11fa5f626120181.8529763856745708092@beco.cc> Dear Ivan Kovmir, Thank you for your reply. Have you contacted gRPC maintainer to figure out the problem? I'll use compiledb for now, because I can't build Bear. If things change, I'll write back with news. Cordialmente, Ruben -- Dr. Beco AI Researcher ------------------------------------------------------------------------------------------------ ---- On Tue, 13 Feb 2024 08:43:37 -0300 i i at kovmir.eu> wrote --- > Bear is currently broken due to old gRPC SlackBuild. If you want to > generate `compilation_database.json`, use > https://github.com/nickdiego/compiledb ------------------------------------------------------------------------------------------------ ---- On Tue, 13 Feb 2024 08:36:40 -0300 i wrote --- > >Please write back whether you can build Bear 3.1.3 on 15.0. ------------------------------------------------------------------------------------------------ > > > On 2024-02-11 11:11, Ruben Carlo Benante wrote: > > >Ciao Matteo, > > >Indeed Bear-3.1.1 cannot be build. > > >( /usr/include/fmt/core.h:1600:63: error: ) > > >I guess Bear 3.1.1 was already installed and fmt upgraded, breaking it. > > >I'll take a look at Bear 3.1.3. Appreciate your disposition to fix our sbo git! > > >Cordialmente, > > >Ruben > > >-- > > >Dr. Beco > > >AI Researcher > > > ------------------------------------------------------------------------------------------------ > > > >---- On Sun, 11 Feb 2024 10:21:08 -0300 Matteo Bernardini matteo.bernardini at gmail.com> wrote --- > > > >hi Ruben, > > > >the error you are reporting is because you most probably built Bear or against older versions of fmt and/or grpc: try to rebuild Bear (and everything on which it depends which build scripts are hosted on SBo). > > > >when you do that you will discover that the version of Bear we have here (3.1.1) cannot be built because of the new fmt: just build version 3.1.3 and that will work ok (I'll push a fix in our git for that). > > > >Matteo > > > > ------------------------------------------------------------------------------------------------ > > > > >Il giorno dom 11 feb 2024 alle ore 13:39 Ruben Carlo Benante via SlackBuilds-users slackbuilds-users at slackbuilds.org> ha scritto: > > > > >Hello there Ivan Kovmir, hello guys, > > > > >The software Bear ( https://slackbuilds.org/repository/15.0/development/Bear/ ) is complaining about missing libraries in Slackware 15.0: > > > > >* bear: error [...]: libgrpc++.so.1: cannot open shared object: No such file or directory > > > > >* bear: error [...]: libgrpc.so.9: cannot open shared object: No such file or directory > > > > >* bear: error [...]:?libgpr.so.9: cannot open shared object: No such file or directory > > > > >* bear: error [...]:?libspdlog.so.1.11: cannot open shared object: No such file or directory > > > > >* bear: error [...]:?libfmt.so.9: cannot open shared object: No such file or directory > > > > >Could you take a peek at it, if you be kind? > > > > >Thanks a bucket. > > > > >Cordialmente, > > > > >Ruben > > > > >-- > > > > >Dr. Beco > > > > >AI Researcher > > > > > > > > > >_______________________________________________ > > > > > SlackBuilds-users mailing list > > > > > mailto: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 jebrhansen+SBo at gmail.com Tue Feb 13 18:58:06 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 13 Feb 2024 10:58:06 -0800 Subject: [Slackbuilds-users] update homepage query In-Reply-To: <1f1930c4-aa3e-4aea-8845-9df5b0cd42cc@googlemail.com> References: <1f1930c4-aa3e-4aea-8845-9df5b0cd42cc@googlemail.com> Message-ID: On Tue, Feb 13, 2024, 6:30?AM Tim Dickson via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hi all, there are three slackbuilds I look after which need a homepage > update from http to https > should I submit 3 updates with .info updated and build no. bumped, or is > there an easier way. > > as the build is identical, maybe the build number doesn't need bumping, > but is it possible > to do an updated with no change in version or build? > > the old http home sites still work, they are just permanently redirected > to the https versions. > regards, Tim > I wouldn't do a build number bump since the resulting program that's created remains unchanged. If you changed dependencies or the compilation process, that should constitute a build number bump. Personally, I would do individual commits but submit them under a single PR... like I did here in the following PR: https://github.com/SlackBuildsOrg/slackbuilds/pull/3261 Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rcb at beco.cc Tue Feb 13 23:34:19 2024 From: rcb at beco.cc (Ruben Carlo Benante) Date: Tue, 13 Feb 2024 20:34:19 -0300 Subject: [Slackbuilds-users] Bear missing libraries In-Reply-To: <18da3936a0d.11fa5f626120181.8529763856745708092@beco.cc> References: <18d982bb277.ed707da2695996.8222601866956036279@beco.cc> <18d988078f8.e1bdf2de701975.2609421241027388473@beco.cc> <20240213113640.nehcnc66ie6kcro2@vps.kovmir.cc> <18da3936a0d.11fa5f626120181.8529763856745708092@beco.cc> Message-ID: <18da4d06b57.12805b122202639.1512753216376547148@beco.cc> Hello guys, Since compiledb (pip install) was not working for other reasons, I tried to compile Bear-3-1-3 again, this time successfuly. The package is available here: https://mirrors.slackware.devl.club/slackware64-15.0-packages/kernel-5.15.145-x86_64/Bear-3.1.3-x86_64-1_SBo.tgz Ivan, as the maintainer, do you want the merge request to be sent somewhere? Or pull request? Or do you allow me to send it to? https://gitlab.com/SlackBuilds.org myself, if it is ok? Cordialmente, Ruben -- Dr. Beco AI Researcher ---- On Tue, 13 Feb 2024 14:48:04 -0300 Ruben Carlo Benante wrote --- Dear Ivan Kovmir, Thank you for your reply. Have you contacted gRPC maintainer to figure out the problem? I'll use compiledb for now, because I can't build Bear. If things change, I'll write back with news. Cordialmente, Ruben -- Dr. Beco AI Researcher ------------------------------------------------------------------------------------------------ ---- On Tue, 13 Feb 2024 08:43:37 -0300 i mailto:i at kovmir.eu> wrote --- > Bear is currently broken due to old gRPC SlackBuild. If you want to > generate `compilation_database.json`, use > https://github.com/nickdiego/compiledb ------------------------------------------------------------------------------------------------ ---- On Tue, 13 Feb 2024 08:36:40 -0300 i wrote --- > >Please write back whether you can build Bear 3.1.3 on 15.0. ------------------------------------------------------------------------------------------------ > > > On 2024-02-11 11:11, Ruben Carlo Benante wrote: > > >Ciao Matteo, > > >Indeed Bear-3.1.1 cannot be build. > > >( /usr/include/fmt/core.h:1600:63: error: ) > > >I guess Bear 3.1.1 was already installed and fmt upgraded, breaking it. > > >I'll take a look at Bear 3.1.3. Appreciate your disposition to fix our sbo git! > > >Cordialmente, > > >Ruben > > >-- > > >Dr. Beco > > >AI Researcher > > > ------------------------------------------------------------------------------------------------ > > > >---- On Sun, 11 Feb 2024 10:21:08 -0300 Matteo Bernardini mailto:matteo.bernardini at gmail.com> wrote --- > > > >hi Ruben, > > > >the error you are reporting is because you most probably built Bear or against older versions of fmt and/or grpc: try to rebuild Bear (and everything on which it depends which build scripts are hosted on SBo). > > > >when you do that you will discover that the version of Bear we have here (3.1.1) cannot be built because of the new fmt: just build version 3.1.3 and that will work ok (I'll push a fix in our git for that). > > > >Matteo > > > > ------------------------------------------------------------------------------------------------ > > > > >Il giorno dom 11 feb 2024 alle ore 13:39 Ruben Carlo Benante via SlackBuilds-users mailto:slackbuilds-users at slackbuilds.org> ha scritto: > > > > >Hello there Ivan Kovmir, hello guys, > > > > >The software Bear ( https://slackbuilds.org/repository/15.0/development/Bear/ ) is complaining about missing libraries in Slackware 15.0: > > > > >* bear: error [...]: libgrpc++.so.1: cannot open shared object: No such file or directory > > > > >* bear: error [...]: libgrpc.so.9: cannot open shared object: No such file or directory > > > > >* bear: error [...]:?libgpr.so.9: cannot open shared object: No such file or directory > > > > >* bear: error [...]:?libspdlog.so.1.11: cannot open shared object: No such file or directory > > > > >* bear: error [...]:?libfmt.so.9: cannot open shared object: No such file or directory > > > > >Could you take a peek at it, if you be kind? > > > > >Thanks a bucket. > > > > >Cordialmente, > > > > >Ruben > > > > >-- > > > > >Dr. Beco > > > > >AI Researcher > > > > > > > > > >_______________________________________________ > > > > > SlackBuilds-users mailing list > > > > > mailto:mailto: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 tonus1 at free.fr Wed Feb 14 00:34:47 2024 From: tonus1 at free.fr (Tonus) Date: Wed, 14 Feb 2024 01:34:47 +0100 Subject: [Slackbuilds-users] Good practice to manage autodetected optional deps Message-ID: Hi all I have a slackbuild that builds man pages if Pandoc is installed (autodetected). If it isn't, the man pages compression in the SBo template makes the script fail What's the good practice ? Add `|| true` at the end of the lines ? Tryed on clean system without Pandoc and on my system that has Pandoc, it builds fine. -- Regards, Tonus From jebrhansen+SBo at gmail.com Wed Feb 14 01:08:03 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 13 Feb 2024 17:08:03 -0800 Subject: [Slackbuilds-users] Good practice to manage autodetected optional deps In-Reply-To: References: Message-ID: On Tue, Feb 13, 2024, 4:34?PM Tonus wrote: > Hi all > > I have a slackbuild that builds man pages if Pandoc is installed > (autodetected). > > If it isn't, the man pages compression in the SBo template makes the > script fail > What's the good practice ? Add `|| true` at the end of the lines ? > > Tryed on clean system without Pandoc and on my system that has Pandoc, > it builds fine. > > -- > Regards, > > Tonus > There are a couple of options: 1. You could do an if/then check to see if the man pages exist and then run the command if found. 2. You could require the user to pass an option to enable man page support (with the note pandoc is required) and then use that to enable/disable the building of the man pages (I assume they have an on/off override of the autodetect). You could continue to use that flag to determine if the man pages should be compressed. 3. You could detect whether pandoc is installed and make the above decision for the user based on that. Personally, #1 seems the easiest. Just detect if there are man pages with an if/then statement and if they are, run the compression command: if [ -d $PKG/usr/man ]; then # run compression command fi (You may need to tweak that if statement depending on how the program handles dirs.) Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From tonus1 at free.fr Wed Feb 14 02:52:11 2024 From: tonus1 at free.fr (Tonus) Date: Wed, 14 Feb 2024 03:52:11 +0100 Subject: [Slackbuilds-users] Good practice to manage autodetected optional deps In-Reply-To: References: Message-ID: On Tue, Feb 13, 2024 at 05:08:03PM -0800, Jeremy Hansen wrote: >On Tue, Feb 13, 2024, 4:34?PM Tonus wrote: > >> Hi all >> >> I have a slackbuild that builds man pages if Pandoc is installed >> (autodetected). >> >> If it isn't, the man pages compression in the SBo template makes the >> script fail >> What's the good practice ? Add `|| true` at the end of the lines ? >> > >There are a couple of options: > >1. You could do an if/then check to see if the man pages exist and then run >the command if found. >2. You could require the user to pass an option to enable man page support >(with the note pandoc is required) and then use that to enable/disable the >building of the man pages (I assume they have an on/off override of the >autodetect). You could continue to use that flag to determine if the man >pages should be compressed. >3. You could detect whether pandoc is installed and make the above decision >for the user based on that. > Thank you for your input ! I choosed to go with 2. with a sed command to leave have the Pandoc install optional. Hope it's clean enough. -- Regards, Tonus From dickson.tim at googlemail.com Wed Feb 14 09:45:39 2024 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 14 Feb 2024 09:45:39 +0000 Subject: [Slackbuilds-users] update homepage query In-Reply-To: References: <1f1930c4-aa3e-4aea-8845-9df5b0cd42cc@googlemail.com> Message-ID: <83a22f7b-069b-4839-8cf0-11fa63165a16@googlemail.com> On 13/02/2024 18:58, Jeremy Hansen wrote: > On Tue, Feb 13, 2024, 6:30?AM Tim Dickson via SlackBuilds-users > wrote: > > Hi all, there are three slackbuilds I look after which need a > homepage > update from http to https > should I submit 3 updates with .info updated and build no. bumped, > or is > there an easier way. > > as the build is identical, maybe the build number doesn't need > bumping, > but is it possible > to do an updated with no change in version or build? > > the old http home sites still work, they are just permanently > redirected > to the https versions. > regards, Tim > > > I wouldn't do a build number bump since the resulting program that's > created remains unchanged. If you changed dependencies or the > compilation process, that should constitute a build number bump. > > Personally, I would do individual commits but submit them under a > single PR... like I did here in the following PR: > > https://github.com/SlackBuildsOrg/slackbuilds/pull/3261 > > Jeremy > thanks. I submitted individual updates. it turns out one needed a md5sum update as well, so that particular one got a build bump. I'm not used to git so just used the web submit form which works well. Regards, Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: From slack at giand.it Wed Feb 14 18:11:14 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Wed, 14 Feb 2024 19:11:14 +0100 Subject: [Slackbuilds-users] Lost submissions? Message-ID: <9bd4a688-d514-41b8-95de-d72de4edc179@giand.it> A few days ago (last Monday) I sent two updates for new releases of pdal and postgis, but they appear neither in pending nor in approved. Do I have to send them again? thanks -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From 1.41421 at gmail.com Thu Feb 15 00:14:43 2024 From: 1.41421 at gmail.com (Luveh Keraph) Date: Wed, 14 Feb 2024 17:14:43 -0700 Subject: [Slackbuilds-users] mkvtoolnix must be rebuilt Message-ID: After the latest upgrade of the cmark to version 0.31 mkvtoolnix-gui won't run any more, for it is expecting to find libcmark 0.30. Things work again once mkvtoolnix is rebuilt. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Feb 15 01:00:06 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 15 Feb 2024 08:00:06 +0700 Subject: [Slackbuilds-users] Lost submissions? In-Reply-To: <9bd4a688-d514-41b8-95de-d72de4edc179@giand.it> References: <9bd4a688-d514-41b8-95de-d72de4edc179@giand.it> Message-ID: <1102828c-a350-4b1e-87c8-106bf05bd3c7@slackbuilds.org> > A few days ago (last Monday) I sent two updates for new releases of pdal > and postgis, but they appear neither in pending nor in approved. Do I > have to send them again? Someone must have removed my branch but now it's back -- Willy Sudiarto Raharjo From slack at giand.it Thu Feb 15 03:54:15 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Thu, 15 Feb 2024 04:54:15 +0100 Subject: [Slackbuilds-users] Lost submissions? In-Reply-To: <1102828c-a350-4b1e-87c8-106bf05bd3c7@slackbuilds.org> References: <9bd4a688-d514-41b8-95de-d72de4edc179@giand.it> <1102828c-a350-4b1e-87c8-106bf05bd3c7@slackbuilds.org> Message-ID: <6cd5442c-2d51-4342-b06b-cd26611fc028@giand.it> Il 15/02/24 02:00, Willy Sudiarto Raharjo ha scritto: >> A few days ago (last Monday) I sent two updates for new releases of >> pdal and postgis, but they appear neither in pending nor in approved. >> Do I have to send them again? > > Someone must have removed my branch but now it's back > Thanks, Willy -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From list+sbo at vahedi.org Fri Feb 16 08:53:09 2024 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Fri, 16 Feb 2024 09:53:09 +0100 Subject: [Slackbuilds-users] [PATCH] development/hexedit: Updated for version 1.6. Message-ID: <20240216085309.23633-1-list+sbo@vahedi.org> The current version (1.2.12) cannot even be built anymore, because that source version exists no more. Tested on a Slackware64 15.0 with the latest patches in. The lint results are OK both for the script and the package. Signed-off-by: Shahab Vahedi --- development/hexedit/hexedit.SlackBuild | 9 ++++++--- development/hexedit/hexedit.info | 8 ++++---- 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/development/hexedit/hexedit.SlackBuild b/development/hexedit/hexedit.SlackBuild index 21381bcac0..33f3d82e5c 100644 --- a/development/hexedit/hexedit.SlackBuild +++ b/development/hexedit/hexedit.SlackBuild @@ -27,7 +27,7 @@ cd $(dirname $0) ; CWD=$(pwd) PRGNAM=hexedit -VERSION=${VERSION:-1.2.12} +VERSION=${VERSION:-1.6} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} @@ -66,8 +66,8 @@ rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $PRGNAM-$VERSION -tar xvf $CWD/$PRGNAM-$VERSION.src.tgz -cd $PRGNAM +tar xvf $CWD/$VERSION.tar.gz +cd $PRGNAM-$VERSION chown -R root:root . find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ @@ -75,6 +75,7 @@ find -L . \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; +./autogen.sh CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ @@ -103,6 +104,8 @@ DOCS="COPYING Changes TODO" mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cp -a $DOCS $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild +# TODO file is empty in version 1.6 +test -s $PKG/usr/doc/$PRGNAM-$VERSION/TODO || rm $PKG/usr/doc/$PRGNAM-$VERSION/TODO mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc diff --git a/development/hexedit/hexedit.info b/development/hexedit/hexedit.info index 111b69d3b3..c4cd5ac420 100644 --- a/development/hexedit/hexedit.info +++ b/development/hexedit/hexedit.info @@ -1,8 +1,8 @@ PRGNAM="hexedit" -VERSION="1.2.12" -HOMEPAGE="http://prigaux.chez.com/hexedit.html" -DOWNLOAD="http://rigaux.org/hexedit-1.2.12.src.tgz" -MD5SUM="0d2f48610006278cd93359fea9a06d5c" +VERSION="1.6" +HOMEPAGE="https://rigaux.org/hexedit.html" +DOWNLOAD="https://github.com/pixel/hexedit/archive/1.6.tar.gz" +MD5SUM="9b5849759dbda9ab25ec22818c16e970" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -- 2.35.8 From matteo.bernardini at gmail.com Fri Feb 16 09:25:13 2024 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 16 Feb 2024 10:25:13 +0100 Subject: [Slackbuilds-users] Fwd: [PATCH] development/hexedit: Updated for version 1.6. In-Reply-To: <20240216085309.23633-1-list+sbo@vahedi.org> References: <20240216085309.23633-1-list+sbo@vahedi.org> Message-ID: Forwarded for consideration to the hexedit maintainer ---------- Forwarded message --------- Da: Shahab Vahedi via SlackBuilds-users Date: ven 16 feb 2024 alle ore 09:53 Subject: [Slackbuilds-users] [PATCH] development/hexedit: Updated for version 1.6. To: Cc: Shahab Vahedi The current version (1.2.12) cannot even be built anymore, because that source version exists no more. Tested on a Slackware64 15.0 with the latest patches in. The lint results are OK both for the script and the package. Signed-off-by: Shahab Vahedi --- development/hexedit/hexedit.SlackBuild | 9 ++++++--- development/hexedit/hexedit.info | 8 ++++---- 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/development/hexedit/hexedit.SlackBuild b/development/hexedit/hexedit.SlackBuild index 21381bcac0..33f3d82e5c 100644 --- a/development/hexedit/hexedit.SlackBuild +++ b/development/hexedit/hexedit.SlackBuild @@ -27,7 +27,7 @@ cd $(dirname $0) ; CWD=$(pwd) PRGNAM=hexedit -VERSION=${VERSION:-1.2.12} +VERSION=${VERSION:-1.6} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} @@ -66,8 +66,8 @@ rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $PRGNAM-$VERSION -tar xvf $CWD/$PRGNAM-$VERSION.src.tgz -cd $PRGNAM +tar xvf $CWD/$VERSION.tar.gz +cd $PRGNAM-$VERSION chown -R root:root . find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ @@ -75,6 +75,7 @@ find -L . \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; +./autogen.sh CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ @@ -103,6 +104,8 @@ DOCS="COPYING Changes TODO" mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cp -a $DOCS $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/ $PRGNAM.SlackBuild +# TODO file is empty in version 1.6 +test -s $PKG/usr/doc/$PRGNAM-$VERSION/TODO || rm $PKG/usr/doc/$PRGNAM-$VERSION/TODO mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc diff --git a/development/hexedit/hexedit.info b/development/hexedit/ hexedit.info index 111b69d3b3..c4cd5ac420 100644 --- a/development/hexedit/hexedit.info +++ b/development/hexedit/hexedit.info @@ -1,8 +1,8 @@ PRGNAM="hexedit" -VERSION="1.2.12" -HOMEPAGE="http://prigaux.chez.com/hexedit.html" -DOWNLOAD="http://rigaux.org/hexedit-1.2.12.src.tgz" -MD5SUM="0d2f48610006278cd93359fea9a06d5c" +VERSION="1.6" +HOMEPAGE="https://rigaux.org/hexedit.html" +DOWNLOAD="https://github.com/pixel/hexedit/archive/1.6.tar.gz" +MD5SUM="9b5849759dbda9ab25ec22818c16e970" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -- 2.35.8 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Fri Feb 16 10:55:05 2024 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 16 Feb 2024 10:55:05 +0000 Subject: [Slackbuilds-users] webkit2gtk api question Message-ID: <7ae856cf-6221-4345-bc53-7fbea30edda5@googlemail.com> hi all, I have a question about webkit2gtk api 4.0 vs 4.1 webkit2gtk is currently used by wxGTK3, yelp, xiphos, wxWidgets, gambas3 and wxPython4 plus a lot of other packages which I don't use. Does anyone know which dependant packages work with both versions of the api ? Apparently a number of major distros are moving over to 4.1api so I'm trying to find out what packages support either api versions as you can't have both installed at the same time. I've responded to the xiphos developer who first raised the question to me on the devel mailing list, and asked the question on the gambas mailing list, but if someone has collated the information that would be useful. regards, Tim From didier at slint.fr Fri Feb 16 12:16:14 2024 From: didier at slint.fr (Didier Spaier) Date: Fri, 16 Feb 2024 13:16:14 +0100 Subject: [Slackbuilds-users] webkit2gtk api question In-Reply-To: <7ae856cf-6221-4345-bc53-7fbea30edda5@googlemail.com> References: <7ae856cf-6221-4345-bc53-7fbea30edda5@googlemail.com> Message-ID: Hi, I can't answer this is question but a search of direct dependees on SBO tells that 4.0 has 29 (in addition atril and geany-plugins can be built against it) and 4.1 only one: epiphany. I remember having discussed this with Bob and if 4.1 is removed maybe epiphany could be installed as a flatpak (i do not require its removal though). I do not know if a bundle of epiphany with 4.1 could be built. Cheers, Didier Le 2/16/24 ? 11:55, Tim Dickson via SlackBuilds-users a ?crit?: > hi all, I have a question about webkit2gtk api 4.0 vs 4.1 > webkit2gtk is currently used by wxGTK3, yelp, xiphos, wxWidgets, gambas3 and > wxPython4 plus a lot of other packages which I don't use. > > Does anyone know which dependant packages work with both versions of the api ? > Apparently a number of major distros are moving over to 4.1api so I'm trying to > find out what packages support either api versions > as you can't have both installed at the same time. > I've responded to the xiphos developer who first raised the question to me on > the devel mailing list, and asked the question on the gambas mailing list, but > if someone has collated the information that would be useful. > regards, Tim From dickson.tim at googlemail.com Fri Feb 16 16:46:52 2024 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 16 Feb 2024 16:46:52 +0000 Subject: [Slackbuilds-users] webkit2gtk api question In-Reply-To: References: <7ae856cf-6221-4345-bc53-7fbea30edda5@googlemail.com> Message-ID: 4.1 is optionally used by zenity as well. I raised the question on linuxquestions a couple of years ago, https://www.linuxquestions.org/questions/slackware-14/webkit2gtk4-1-gtk3-query-4175710629/ and at the time we standardised on the 4.0 api, as the problem was if multiple components link to different versions of libsoup (2 and 3) then the binaries fail, because there can't be links to 2 different soup libs in the same binary without it crashing as soon as one of them is referenced. As distros such as ubuntu and debian are moving to 4.1api it means that applications are looking at moving as well, so I wondered what the situation was these days. As far as I understand, the only difference between the 2 api's is one links to soup2 and the other links to soup3, the api is the same, just not binary compatible.? If the packages detect the newer webkit2gtk it may be possible to just switch, and as long as all the deps are rebuilt, it may just work. I don't know if there are links to slackware's stock libsoup(2) that are also being used, which might be problematic. the reason I asked this time is because the developer of xiphos is thinking of updating to 4.1 api, which would effect yelp as well. I don't mind which is the standard, but I wouldn't like to loose an application if it changes either. I guess it depends on whether the build scripts see the 4.1 webkit2gtk and use it if it is present. As you point out, it affects a number of builds. regards, Tim On 16/02/2024 12:16, Didier Spaier wrote: > Hi, > I can't answer this is question but a search of direct dependees on SBO tells > that 4.0 has 29 (in addition atril and geany-plugins can be built against it) > and 4.1 only one: epiphany. > > I remember having discussed this with Bob and if 4.1 is removed maybe epiphany > could be installed as a flatpak (i do not require its removal though). I do not > know if a bundle of epiphany with 4.1 could be built. > > Cheers, > Didier > > > > Le 2/16/24 ? 11:55, Tim Dickson via SlackBuilds-users a ?crit?: >> hi all, I have a question about webkit2gtk api 4.0 vs 4.1 >> webkit2gtk is currently used by wxGTK3, yelp, xiphos, wxWidgets, gambas3 and >> wxPython4 plus a lot of other packages which I don't use. >> >> Does anyone know which dependant packages work with both versions of the api ? >> Apparently a number of major distros are moving over to 4.1api so I'm trying to >> find out what packages support either api versions >> as you can't have both installed at the same time. >> I've responded to the xiphos developer who first raised the question to me on >> the devel mailing list, and asked the question on the gambas mailing list, but >> if someone has collated the information that would be useful. >> regards, Tim > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From didier at slint.fr Fri Feb 16 17:31:36 2024 From: didier at slint.fr (Didier Spaier) Date: Fri, 16 Feb 2024 17:31:36 +0000 Subject: [Slackbuilds-users] webkit2gtk api question In-Reply-To: References: <7ae856cf-6221-4345-bc53-7fbea30edda5@googlemail.com> Message-ID: <364ac47f-3197-4256-8a12-ae1cc7a8f4a8@slint.fr> Since zenity version 3.43.0 the requirement for WebkitGTK optional dependency has been bumped to API 4.1 :( As it is optional I will just built it without if I need to upgrade. But for yelp (current version: 42.2) one can still choose the API, fortunately for me (Mate is the flagship of Slint and I wouldn't ship Mate without its contextual help system). Cheers, Didier Le 2/16/24 ? 16:46, Tim Dickson via SlackBuilds-users a ?crit?: > 4.1 is optionally used by zenity as well. > I raised the question on linuxquestions a couple of years ago, > https://www.linuxquestions.org/questions/slackware-14/webkit2gtk4-1-gtk3-query-4175710629/ and at the time we standardised on the 4.0 api, as the problem was if multiple components link to different versions of libsoup (2 and 3) then the binaries fail, because there can't be links to 2 different soup libs in the same binary without it crashing as soon as one of them is referenced. As distros such as ubuntu and debian are moving to 4.1api it means that applications are looking at moving as well, so I wondered what the situation was these days. > > As far as I understand, the only difference between the 2 api's is one links to > soup2 and the other links to soup3, the api is the same, just not binary > compatible.? If the packages detect the newer webkit2gtk it may be possible to > just switch, and as long as all the deps are rebuilt, it may just work. I don't > know if there are links to slackware's stock libsoup(2) that are also being > used, which might be problematic. > the reason I asked this time is because the developer of xiphos is thinking of > updating to 4.1 api, which would effect yelp as well. I don't mind which is the > standard, but I wouldn't like to loose an application if it changes either. I > guess it depends on whether the build scripts see the 4.1 webkit2gtk and use it > if it is present. As you point out, it affects a number of builds. > regards, Tim > > On 16/02/2024 12:16, Didier Spaier wrote: >> Hi, >> I can't answer this is question but a search of direct dependees on SBO tells >> that 4.0 has 29 (in addition atril and geany-plugins can be built against it) >> and 4.1 only one: epiphany. >> >> I remember having discussed this with Bob and if 4.1 is removed maybe epiphany >> could be installed as a flatpak (i do not require its removal though). I do not >> know if a bundle of epiphany with 4.1 could be built. >> >> Cheers, >> Didier >> >> >> >> Le 2/16/24 ? 11:55, Tim Dickson via SlackBuilds-users a ?crit?: >>> hi all, I have a question about webkit2gtk api 4.0 vs 4.1 >>> webkit2gtk is currently used by wxGTK3, yelp, xiphos, wxWidgets, gambas3 and >>> wxPython4 plus a lot of other packages which I don't use. >>> >>> Does anyone know which dependant packages work with both versions of the api ? >>> Apparently a number of major distros are moving over to 4.1api so I'm trying to >>> find out what packages support either api versions >>> as you can't have both installed at the same time. >>> I've responded to the xiphos developer who first raised the question to me on >>> the devel mailing list, and asked the question on the gambas mailing list, but >>> if someone has collated the information that would be useful. >>> regards, Tim >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > _______________________________________________ > 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 dickson.tim at googlemail.com Fri Feb 16 17:49:39 2024 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 16 Feb 2024 17:49:39 +0000 Subject: [Slackbuilds-users] webkit2gtk api question In-Reply-To: <364ac47f-3197-4256-8a12-ae1cc7a8f4a8@slint.fr> References: <7ae856cf-6221-4345-bc53-7fbea30edda5@googlemail.com> <364ac47f-3197-4256-8a12-ae1cc7a8f4a8@slint.fr> Message-ID: <643e3d70-6747-4369-a52e-e3244ebfb122@googlemail.com> yes, I noticed a discussion online about the issues relating to gnome and the search in the help system getting broken with the shift to 4.1. I've requested to the xiphos developer that he provides a way to enable using the 4.0 api even if he adds support for 4.1 to support those of us stuck on 4.0. regards, Tim On 16/02/2024 17:31, Didier Spaier wrote: > Since zenity version 3.43.0 the requirement for WebkitGTK optional dependency > has been bumped to API 4.1 :( > > As it is optional I will just built it without if I need to upgrade. > > But for yelp (current version: 42.2) one can still choose the API, fortunately > for me (Mate is the flagship of Slint and I wouldn't ship Mate without its > contextual help system). > > Cheers, > Didier > > Le 2/16/24 ? 16:46, Tim Dickson via SlackBuilds-users a ?crit?: >> 4.1 is optionally used by zenity as well. >> I raised the question on linuxquestions a couple of years ago, >> https://www.linuxquestions.org/questions/slackware-14/webkit2gtk4-1-gtk3-query-4175710629/ and at the time we standardised on the 4.0 api, as the problem was if multiple components link to different versions of libsoup (2 and 3) then the binaries fail, because there can't be links to 2 different soup libs in the same binary without it crashing as soon as one of them is referenced. As distros such as ubuntu and debian are moving to 4.1api it means that applications are looking at moving as well, so I wondered what the situation was these days. >> >> As far as I understand, the only difference between the 2 api's is one links to >> soup2 and the other links to soup3, the api is the same, just not binary >> compatible.? If the packages detect the newer webkit2gtk it may be possible to >> just switch, and as long as all the deps are rebuilt, it may just work. I don't >> know if there are links to slackware's stock libsoup(2) that are also being >> used, which might be problematic. >> the reason I asked this time is because the developer of xiphos is thinking of >> updating to 4.1 api, which would effect yelp as well. I don't mind which is the >> standard, but I wouldn't like to loose an application if it changes either. I >> guess it depends on whether the build scripts see the 4.1 webkit2gtk and use it >> if it is present. As you point out, it affects a number of builds. >> regards, Tim >> >> On 16/02/2024 12:16, Didier Spaier wrote: >>> Hi, >>> I can't answer this is question but a search of direct dependees on SBO tells >>> that 4.0 has 29 (in addition atril and geany-plugins can be built against it) >>> and 4.1 only one: epiphany. >>> >>> I remember having discussed this with Bob and if 4.1 is removed maybe epiphany >>> could be installed as a flatpak (i do not require its removal though). I do not >>> know if a bundle of epiphany with 4.1 could be built. >>> >>> Cheers, >>> Didier >>> >>> >>> >>> Le 2/16/24 ? 11:55, Tim Dickson via SlackBuilds-users a ?crit?: >>>> hi all, I have a question about webkit2gtk api 4.0 vs 4.1 >>>> webkit2gtk is currently used by wxGTK3, yelp, xiphos, wxWidgets, gambas3 and >>>> wxPython4 plus a lot of other packages which I don't use. >>>> >>>> Does anyone know which dependant packages work with both versions of the api ? >>>> Apparently a number of major distros are moving over to 4.1api so I'm trying to >>>> find out what packages support either api versions >>>> as you can't have both installed at the same time. >>>> I've responded to the xiphos developer who first raised the question to me on >>>> the devel mailing list, and asked the question on the gambas mailing list, but >>>> if someone has collated the information that would be useful. >>>> regards, Tim >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> >> _______________________________________________ >> 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 willysr at slackbuilds.org Sat Feb 17 02:16:10 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 17 Feb 2024 09:16:10 +0700 Subject: [Slackbuilds-users] Updates - 20240217.1 Message-ID: Sat Feb 17 02:08:34 UTC 2024 academic/fet: Updated for version 6.16.1. academic/nco: Updated for version 5.2.0. academic/xiphos: Update HOMEPAGE. audio/acxi: Updated for version 3.6.01. audio/gusersoundfont: Update HOMEPAGE. audio/musikcube: Use asio as submodule. audio/sayonara-player: Updated for version 1.9.0_stable1. desktop/battery-notify: Added (Battery notify daemon). desktop/foot: Updated MD5SUM. desktop/mate-system-monitor: Added (system monitoring). desktop/ncpamixer: Added (sound mixer). desktop/nwg-readme-browser: Updated for version 0.1.4. desktop/nwg-shell-config: Updated for version 0.5.34. desktop/nwg-shell: Updated for version 0.5.32. desktop/sun: Fix doinst.sh. desktop/sun: Updated for version 1.6.0. development/aspnetcore-runtime-7.0: Updated for version 7.0.16. development/aspnetcore-runtime-8.0: Updated for version 8.0.2. development/aws-cdk: Updated for version 2.127.0. development/cargo-vendor-filterer: Fix FTB on arm. development/composer: Updated for version 2.7.1 development/diff-so-fancy: Added (Diff tool). development/dotnet-runtime-6.0: Updated for version 6.0.27. development/dotnet-runtime-7.0: Updated for version 7.0.16. development/dotnet-runtime-8.0: Updated for version 8.0.2. development/dotnet-sdk-6.0: Updated for version 6.0.419. development/dotnet-sdk-7.0: Updated for version 7.0.406. development/dotnet-sdk-8.0: Updated for version 8.0.200. development/dpkg: Updated for version 1.22.4. development/gambas3: Update MD5SUM. development/jupyter-nbconvert: Update for 7.16.0 development/jupyter-notebook_shim: Update for 0.2.4 development/php82: Updated for version 8.2.16 development/postman: Updated for version 10.23.0 development/pre-commit: Updated for version 3.6.1. development/robotframework: Updated for version 7.0. development/rust16: Updated for version 1.76.0. development/vscode-bin: Updated for version 1.86.1. development/vscode-bin: Updated for version 1.86.2. development/xxd-standalone: Updated for version 9.1.0094. development/zope.interface: updated for version 6.2 games/chexquest: Added (FPS game). games/open-adventure: Updated for version 1.18. games/stella: Updated for version 6.7.1. games/vbam: Updated for version 2.1.9. games/xroar: Updated for version 1.5.3. gis/osm2pgsql: Updated for version 1.11.0. gis/pdal: Updated for version 2.6.3. gis/postgis: Updated for version 3.4.2. gis/python3-shapely: Updated for version 2.0.3. graphics/focus-stack: Added (focus stacking). graphics/graphviz: updated for version 10.0.1 graphics/yacreader: Updated for version 9.14.2.2402143. ham/qlog: Updated for version 0.32.0. libraries/aribb25: Updated for version 0.2.7. libraries/aspnetcore-runtime-6.0: Updated for version 6.0.27. libraries/highway: Updated for version 1.0.7. libraries/libcurl-gnutls: Updated for version 8.6.0. libraries/libjwt: updated for version 1.17.0 libraries/libosmium: Added (C++ library). libraries/protozero: Added (protocol buffer decoder and encoder). libraries/tinygltf: Updated for version 2.8.21. libraries/zope.configuration: updated for version 5.0.1 misc/ghostpcl: Updated for version 10.02.1. misc/open-simh: Fix permission. misc/open-simh: Updated for version 1a1396d. multimedia/MuseScore-Legacy: Added (WYSIWYG Music Score Typesetter). multimedia/MuseScore: Updated for version 4.2.1. multimedia/kodi: Version bump to 20.4 multimedia/openh264: Updated for version 2.4.1. multimedia/opera-ffmpeg-codecs: Updated for version 0.84.0. multimedia/pipe-viewer: Updated for version 0.4.9. multimedia/plexmediaserver: Updated for version 1.40.0.7998_c29d4c0c8. multimedia/smplayer: Update for version 23.12.0 network/clipgrab: Updated for version 3.9.10. network/discord: Version bump to 0.0.43 network/haproxy: Updated for version 2.8.6. network/nordvpn: Updated for version 3.17.1. network/opera: Updated for version 107.0.5045.21. network/signal-desktop: Updated for version 6.47.1. network/telegram: Updated for version 4.14.15. network/twine: Updated for version 5.0.0. network/unbound: Updated for version 1.19.1. network/vivaldi: Updated for version 6.5.3206.63. network/weechat: Updated for version 4.2.1. network/windscribe: Fixed sbolint warnings. network/windscribe: Updated for version 2.8.6. network/wireshark: Updated for version 4.2.3. network/yt-dlp: Updated for version 2023.12.30. office/khal: Updated for version 0.11.3 office/lout: Updated for version 3.43 office/mate-calc: Updated for version 1.28.0. perl/perl-Glib-Object-Introspection: Updated for version 0.051. perl/perl-PAR: Updated for version 1.019. perl/perl-file-mimeinfo: Updated for version 0.34. perl/perl-glib: Updated for version 1.3294. python/lockfile: Removed (splitted to python2 & python3). python/python2-cssselect: Added (Python2 of cssselect). python/python2-lockfile: Added (file locking module). python/python2-lxml: Added (Python2 of lxml). python/python3-argcomplete: Updated for version 3.0.8. python/python3-colorlog: Updated for version 6.8.2. python/python3-cssselect: Added (Python3 of cssselect). python/python3-debugpy: Update for 1.8.1 python/python3-hatchling: Updated for version 1.21.1. python/python3-identify: Updated for version 2.5.34. python/python3-klepto: Updated for version 0.2.5. python/python3-lxml: Added (Python3 of lxml). python/python3-marisa-trie: Updated for version 1.1.0. python/python3-persistent: updated for version 5.2 python/python3-pipx: Updated for version 1.3.1. python/python3-plotly: Update for 5.19.0 python/python3-pox: Updated for version 0.3.4. python/python3-prometheus_client: Update for 0.20.0 python/python3-pyosmium: Added (python binding for osmium). python/python3-pytest: Version bump to 8.0.1 python/python3-reportlab: Updated for version 4.1.0. python/python3-slugify: Version bump to 8.0.4 python/python3-threadpoolctl: Updated for version 3.3.0. python/python3-trio: Added (Python library for async concurrency). python/python3-userpath: Updated for version 1.9.1. python/python3-zodbpickle: updated for version 3.2 python/rst2pdf: Updated for version 0.101. system/OpenSnitch: Update for 1.6.5.1 system/android-udev-rules: Updated for version 2024.01.14. system/ansible-core: Added (Ansible core). system/ansible: Updated for version 8.7.0. system/catatonit: Fix script. system/cpuid2cpuflags: Updated for version 14.0. system/duplicity: Updated dependencies. system/intelmas: Update for 2.3 system/kitty: Updated for version 0.32.2 system/letsencrypt: Updated for version 2.9.0. system/netdata: Updated for version 1.44.3. system/nvidia-legacy470-kernel: Fix typo. system/pcmanfm-qt: Update for 1.4.1 system/powershell: Updated for version 7.4.1. system/sbo-create: Updated for version 2.0.8. system/sdltrs: Updated for version 1.2.28. system/slpkg: Updated for version 4.9.8. system/uhubctl: Updated for version 2.5.0. system/vice: Updated for version 3.8. system/wezterm: Updated for version 20240203_110809_5046fc22 system/yq: Updated for version 4.41.1. system/zsh-syntax-highlighting: Updated for version 0.8.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From wedinm at gmail.com Sat Feb 17 10:18:03 2024 From: wedinm at gmail.com (M Wedin) Date: Sat, 17 Feb 2024 11:18:03 +0100 Subject: [Slackbuilds-users] Wrong md5sum for rav1e Message-ID: I'm trying to install FlightGear. cargo-c compiled and installed ok. Oversight or foul play? Found rav1e-0.7.1.tar.gz in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for rav1e-0.7.1.tar.gz ... OK Found Cargo.lock in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for Cargo.lock ... FAILED! Expected: 3c8e14548d37d9fd0efad829bb979e76 Found: b4da9f76a4b4fe2fe547be2980f2168c Do you want to use the downloaded rav1e source: Cargo.lock in /var/cache/sbopkg? Wedin From alik at ejik.org Sat Feb 17 13:16:25 2024 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 17 Feb 2024 16:16:25 +0300 Subject: [Slackbuilds-users] Wrong md5sum for rav1e In-Reply-To: References: Message-ID: On Sat, Feb 17, 2024 at 11:18:03AM +0100, M Wedin wrote: > I'm trying to install FlightGear. cargo-c compiled and installed ok. > > Oversight or foul play? > > Found rav1e-0.7.1.tar.gz in /var/cache/sbopkg. > Checking MD5SUM: > MD5SUM check for rav1e-0.7.1.tar.gz ... OK > Found Cargo.lock in /var/cache/sbopkg. > Checking MD5SUM: > MD5SUM check for Cargo.lock ... FAILED! > Expected: 3c8e14548d37d9fd0efad829bb979e76 > Found: b4da9f76a4b4fe2fe547be2980f2168c > > Do you want to use the downloaded rav1e source: > Cargo.lock in /var/cache/sbopkg? There's something wrong with the building process. rav1e requires cargo-c. Both download source files called Cargo.lock: https://github.com/lu-zero/cargo-c/releases/download/v0.9.27/Cargo.lock md5sum: b4da9f76a4b4fe2fe547be2980f2168c https://github.com/xiph/rav1e/releases/download/v0.7.1/Cargo.lock md5sum: 3c8e14548d37d9fd0efad829bb979e76 By some reason the building process for rav1e tries to use Cargo.lock from cargo-c instead of downloading its own Cargo.lock. It seems an oversight or foul play is involved in > Found Cargo.lock in /var/cache/sbopkg. Best regards, Alexander From heiko.rosemann at web.de Sat Feb 17 13:40:28 2024 From: heiko.rosemann at web.de (Heiko Rosemann) Date: Sat, 17 Feb 2024 14:40:28 +0100 Subject: [Slackbuilds-users] Wrong md5sum for rav1e In-Reply-To: References: Message-ID: <917aee59-b93f-4b26-9ccc-96e682223674@web.de> On 2/17/24 14:16, Alexander Verbovetsky wrote: > By some reason the building process for rav1e tries to use Cargo.lock > from cargo-c instead of downloading its own Cargo.lock. > > It seems an oversight or foul play is involved in >> Found Cargo.lock in /var/cache/sbopkg. That absolutely works as intended: Before downloading, sbopkg checks if a file of the correct name already exists in the cache directory. It does not keep track where that file came from or when it was downloaded. Heiko -- eMails verschl?sseln mit PGP - privacy is your right! Mein PGP-Key zur Verifizierung: http://pgp.mit.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From alik at ejik.org Sat Feb 17 13:56:25 2024 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 17 Feb 2024 16:56:25 +0300 Subject: [Slackbuilds-users] Wrong md5sum for rav1e In-Reply-To: <917aee59-b93f-4b26-9ccc-96e682223674@web.de> References: <917aee59-b93f-4b26-9ccc-96e682223674@web.de> Message-ID: On Sat, Feb 17, 2024 at 02:40:28PM +0100, Heiko Rosemann via SlackBuilds-users wrote: > On 2/17/24 14:16, Alexander Verbovetsky wrote: > > By some reason the building process for rav1e tries to use > > Cargo.lock from cargo-c instead of downloading its own Cargo.lock. > > > > It seems an oversight or foul play is involved in > > > Found Cargo.lock in /var/cache/sbopkg. > That absolutely works as intended: Before downloading, sbopkg checks > if a file of the correct name already exists in the cache directory. > It does not keep track where that file came from or when it was > downloaded. To me it sounds like receipt for disaster. Are there any recommendation what a slackbuild script should do about this problem? Clean $CWD at the very end? Best regards, Alexander From for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net Sat Feb 17 13:59:10 2024 From: for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net (Lockywolf) Date: Sat, 17 Feb 2024 21:59:10 +0800 Subject: [Slackbuilds-users] Wrong md5sum for rav1e In-Reply-To: References: <917aee59-b93f-4b26-9ccc-96e682223674@web.de> Message-ID: <87y1bjqjf5.fsf@laptop.lockywolf.net> Alexander Verbovetsky writes: > On Sat, Feb 17, 2024 at 02:40:28PM +0100, Heiko Rosemann via SlackBuilds-users wrote: >> On 2/17/24 14:16, Alexander Verbovetsky wrote: >> > By some reason the building process for rav1e tries to use >> > Cargo.lock from cargo-c instead of downloading its own Cargo.lock. >> > >> > It seems an oversight or foul play is involved in >> > > Found Cargo.lock in /var/cache/sbopkg. > > >> That absolutely works as intended: Before downloading, sbopkg checks >> if a file of the correct name already exists in the cache directory. > >> It does not keep track where that file came from or when it was >> downloaded. > > To me it sounds like receipt for disaster. > > Are there any recommendation what a slackbuild script should do about > this problem? > > Clean $CWD at the very end? > > Best regards, > Alexander > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ Do we actually need those Cargo.lock files to successfully build a rust binary? I have a few rust slackbuilds (helvum, lean-elan, tzupdate), and they just use .crate files, not Cargo.lock files. I am pre-generating .info files with the following script: https://gitlab.com/Lockywolf/lwfslackbuilds/-/blob/master/02_lockywolf-sbo-scripts/lwf_make-cargolinks.bash?ref_type=heads -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) From alik at ejik.org Sat Feb 17 14:29:47 2024 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 17 Feb 2024 17:29:47 +0300 Subject: [Slackbuilds-users] Wrong md5sum for rav1e In-Reply-To: <87y1bjqjf5.fsf@laptop.lockywolf.net> References: <917aee59-b93f-4b26-9ccc-96e682223674@web.de> <87y1bjqjf5.fsf@laptop.lockywolf.net> Message-ID: > Do we actually need those Cargo.lock files to successfully build a > rust binary? > > I have a few rust slackbuilds (helvum, lean-elan, tzupdate), and they > just use .crate files, not Cargo.lock files. My understanding is that all rust slackbuilds use the command find [..] -name Cargo.lock In your case, as in most cases, Cargo.lock is included to the package, but for rav1e and cargo-c it's a separate download. Best regards, Alexander From j+sbo-users at maschinengott.de Sat Feb 17 15:07:22 2024 From: j+sbo-users at maschinengott.de (j+sbo-users at maschinengott.de) Date: Sat, 17 Feb 2024 16:07:22 +0100 Subject: [Slackbuilds-users] Wrong md5sum for rav1e In-Reply-To: References: <917aee59-b93f-4b26-9ccc-96e682223674@web.de> <87y1bjqjf5.fsf@laptop.lockywolf.net> Message-ID: <64642042-03bb-4b62-acdc-b2f4b8d1fe8e@maschinengott.de> On 17.02.24 15:29, Alexander Verbovetsky wrote:>> Do we actually need those Cargo.lock files to successfully build a >> rust binary? >> >> I have a few rust slackbuilds (helvum, lean-elan, tzupdate), and they >> just use .crate files, not Cargo.lock files. > > My understanding is that all rust slackbuilds use the command > find [..] -name Cargo.lock > > In your case, as in most cases, Cargo.lock is included to the package, > but for rav1e and cargo-c it's a separate download. In rav1e-0.7.1.tar.gz there is a Cargo.lock file and it's identical to the separately downloaded one. From alik at ejik.org Sat Feb 17 15:34:48 2024 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 17 Feb 2024 18:34:48 +0300 Subject: [Slackbuilds-users] Wrong md5sum for rav1e In-Reply-To: <64642042-03bb-4b62-acdc-b2f4b8d1fe8e@maschinengott.de> References: <917aee59-b93f-4b26-9ccc-96e682223674@web.de> <87y1bjqjf5.fsf@laptop.lockywolf.net> <64642042-03bb-4b62-acdc-b2f4b8d1fe8e@maschinengott.de> Message-ID: > In rav1e-0.7.1.tar.gz there is a Cargo.lock file and it's identical to > the separately downloaded one. You're right, thank you! I'll remove the separate Cargo.lock. Hope it will fix the sbopkg problem in this case. Best regards, Alexander From isaacyu at protonmail.com Sat Feb 17 21:02:02 2024 From: isaacyu at protonmail.com (Isaac Yu) Date: Sat, 17 Feb 2024 21:02:02 +0000 Subject: [Slackbuilds-users] I will no longer maintain arqiver and whalebird Message-ID: Hello everyone, I will no longer maintain these 2 SlackBuilds: arqiver whalebird Regarding arqiver (a qt5 archive manager) - I am now instead maintaining lxqt-archiver (another qt5 file archiver). In addition, I am no longer interested in whalebird as a (graphical) Mastodon client. I am now instead using tut (a command-line Mastodon client). - Isaac -------------- next part -------------- An HTML attachment was scrubbed... URL: From edps.mundognu at gmail.com Sun Feb 18 14:55:50 2024 From: edps.mundognu at gmail.com (Edinaldo P. Silva) Date: Sun, 18 Feb 2024 11:55:50 -0300 Subject: [Slackbuilds-users] bleachbit vs localepurge Message-ID: since bleachbit is better than localepurge to clean system locales, i think is better remove localepurge from SBo or made him orphaned for now... Cheers, Edinaldo -------------- next part -------------- An HTML attachment was scrubbed... URL: From antonioleal at yahoo.com Sun Feb 18 15:09:48 2024 From: antonioleal at yahoo.com (Antonio Leal) Date: Sun, 18 Feb 2024 15:09:48 +0000 Subject: [Slackbuilds-users] I will no longer maintain arqiver and whalebird In-Reply-To: References: Message-ID: Hi Isaac, all, I can take up arqiver... Cheers, Ant?nio On 17/02/24 21:02, Isaac Yu via SlackBuilds-users wrote: > Hello everyone, > > I will no longer maintain these 2 SlackBuilds: > arqiver > whalebird > > Regarding arqiver (a qt5 archive manager) - I am now instead > maintaining lxqt-archiver (another qt5 file archiver). > > In addition, I am no longer interested in whalebird as a (graphical) > Mastodon client. > I am now instead using tut (a command-line Mastodon client). > > -?Isaac > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ -https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From antonioleal at yahoo.com Sun Feb 18 15:20:36 2024 From: antonioleal at yahoo.com (Antonio Leal) Date: Sun, 18 Feb 2024 15:20:36 +0000 Subject: [Slackbuilds-users] I will no longer maintain arqiver and whalebird In-Reply-To: References: Message-ID: <107707b1-84f7-4338-ab49-ebd27eb47b57@yahoo.com> ...and whalebird. On 17/02/24 21:02, Isaac Yu via SlackBuilds-users wrote: > Hello everyone, > > I will no longer maintain these 2 SlackBuilds: > arqiver > whalebird > > Regarding arqiver (a qt5 archive manager) - I am now instead > maintaining lxqt-archiver (another qt5 file archiver). > > In addition, I am no longer interested in whalebird as a (graphical) > Mastodon client. > I am now instead using tut (a command-line Mastodon client). > > -?Isaac > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ -https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanmlasca at gmail.com Mon Feb 19 07:04:00 2024 From: juanmlasca at gmail.com (Juan Lasca) Date: Mon, 19 Feb 2024 04:04:00 -0300 Subject: [Slackbuilds-users] Scripts up for grabs Message-ID: Hi list! For quite some time I've enjoyed contributing to this project with a few scripts, a couple of small patches here and there, and with some of you with questions, answers, troubleshooting and advice in general. I think we have an excellent community here full of kind volunteers capable of amazing things, always willing to help others, and would like to thank you for the time and resources you put to keep projects like this going, and also thank the developers of the many tools built around it. Without you, it wouldn't be the same. But given recent circumstances beyond my control, I will be having little to almost no spare time to put here, and thus won't be able to keep collaborating in any significant way anymore. Consequently, to avoid going from casual to poorly made or maintained contributions, I believe the best thing to be done here is to leave all my scripts for any of you who wishes to take over maintenance, namely: academic/aris academic/gerbv academic/plus42 audio/spectmorph desktop/budgie-desktop desktop/budgie-desktop-view desktop/budgie-desktop-view desktop/budgie-screensaver desktop/cutefish-calculator desktop/cutefish-core desktop/cutefish-dock desktop/cutefish-filemanager desktop/cutefish-gtk-themes desktop/cutefish-icons desktop/cutefish-launcher desktop/cutefish-screenlocker desktop/cutefish-settings desktop/cutefish-statusbar desktop/cutefish-terminal desktop/cutefish-wallpapers development/cosmocc development/critcl development/eisl development/gedit development/gedit-plugins development/gedit-plugins development/metakit development/newlisp development/quickjs development/recutils development/tclvfs development/tkcon development/tktable development/ttk-themes graphics/amide libraries/Ipopt libraries/cutefish-kwin-plugins libraries/cutefish-qt-plugins libraries/fishui libraries/libcutefish libraries/libgedit-amtk libraries/libgedit-gtksourceview libraries/pdf4tcl libraries/tcc4tcl libraries/tclsoap libraries/tclws libraries/tclxml libraries/tepl libraries/tksvg network/gnome-bluetooth network/httpie network/rtl8188fu office/gmdb2 office/homebank office/mdbtools office/openoffice.org system/brlaser system/pledge system/xprintidle Feel free to grab any of them and modify it as you see fit, be it source, license, URLs, descriptions, patches, docs, etc. Best regards, Juan From sb at rbn.im Mon Feb 19 09:13:30 2024 From: sb at rbn.im (Ruben Schuller) Date: Mon, 19 Feb 2024 10:13:30 +0100 Subject: [Slackbuilds-users] Scripts up for grabs In-Reply-To: References: Message-ID: <20240219101330.631f48be@kiwi.kuchen> Hi list, if no one else is claiming them, I'd take the Tcl/Tk related ones: 2024-02-19 Juan Lasca : > development/critcl > development/tclvfs > development/tkcon > development/tktable > development/ttk-themes > libraries/pdf4tcl > libraries/tcc4tcl > libraries/tclsoap > libraries/tclws > libraries/tclxml > libraries/tksvg Cheers Ruben From antonioleal at yahoo.com Mon Feb 19 13:14:48 2024 From: antonioleal at yahoo.com (Antonio Leal) Date: Mon, 19 Feb 2024 13:14:48 +0000 Subject: [Slackbuilds-users] Scripts up for grabs In-Reply-To: References: Message-ID: Hi all, If no one opposes I can take over academic/plus42 desktop/cutefish-calculator desktop/cutefish-core desktop/cutefish-dock desktop/cutefish-filemanager desktop/cutefish-gtk-themes desktop/cutefish-icons desktop/cutefish-launcher desktop/cutefish-screenlocker desktop/cutefish-settings desktop/cutefish-statusbar desktop/cutefish-terminal desktop/cutefish-wallpapers libraries/cutefish-kwin-plugins libraries/cutefish-qt-plugins libraries/fishui libraries/libcutefish Cheers, Ant?nio On 19/02/24 07:04, Juan Lasca wrote: > Hi list! > For quite some time I've enjoyed contributing to this project with a > few scripts, a couple of small patches here and there, and with some > of you with questions, answers, troubleshooting and advice in general. > I think we have an excellent community here full of kind volunteers > capable of amazing things, always willing to help others, and would > like to thank you for the time and resources you put to keep projects > like this going, and also thank the developers of the many tools built > around it. Without you, it wouldn't be the same. > But given recent circumstances beyond my control, I will be having > little to almost no spare time to put here, and thus won't be able to > keep collaborating in any significant way anymore. > Consequently, to avoid going from casual to poorly made or maintained > contributions, I believe the best thing to be done here is to leave > all my scripts for any of you who wishes to take over maintenance, > namely: > > academic/aris > academic/gerbv > academic/plus42 > audio/spectmorph > desktop/budgie-desktop > desktop/budgie-desktop-view > desktop/budgie-desktop-view > desktop/budgie-screensaver > desktop/cutefish-calculator > desktop/cutefish-core > desktop/cutefish-dock > desktop/cutefish-filemanager > desktop/cutefish-gtk-themes > desktop/cutefish-icons > desktop/cutefish-launcher > desktop/cutefish-screenlocker > desktop/cutefish-settings > desktop/cutefish-statusbar > desktop/cutefish-terminal > desktop/cutefish-wallpapers > development/cosmocc > development/critcl > development/eisl > development/gedit > development/gedit-plugins > development/gedit-plugins > development/metakit > development/newlisp > development/quickjs > development/recutils > development/tclvfs > development/tkcon > development/tktable > development/ttk-themes > graphics/amide > libraries/Ipopt > libraries/cutefish-kwin-plugins > libraries/cutefish-qt-plugins > libraries/fishui > libraries/libcutefish > libraries/libgedit-amtk > libraries/libgedit-gtksourceview > libraries/pdf4tcl > libraries/tcc4tcl > libraries/tclsoap > libraries/tclws > libraries/tclxml > libraries/tepl > libraries/tksvg > network/gnome-bluetooth > network/httpie > network/rtl8188fu > office/gmdb2 > office/homebank > office/mdbtools > office/openoffice.org > system/brlaser > system/pledge > system/xprintidle > > Feel free to grab any of them and modify it as you see fit, be it > source, license, URLs, descriptions, patches, docs, etc. > > Best regards, > Juan > _______________________________________________ > 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 bobfunk11 at gmail.com Wed Feb 21 01:25:27 2024 From: bobfunk11 at gmail.com (Bob Funk) Date: Tue, 20 Feb 2024 19:25:27 -0600 Subject: [Slackbuilds-users] Scripts up for grabs In-Reply-To: References: Message-ID: Hi Juan, I actively use gedit and gnome-bluetooth so I can take over those and their dependencies that you have listed. That would be these packages: libraries/libgedit-gtksourceview libraries/libgedit-amtk libraries/tepl development/gedit development/gedit-plugins network/gnome-bluetooth I have a number of other gnome slackbuilds already so those will just add to my collection to maintain. If you ever want to get active again and take back maintenance, just let me know. All the best, Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: From list+sbo at vahedi.org Wed Feb 21 11:21:18 2024 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Wed, 21 Feb 2024 11:21:18 +0000 Subject: [Slackbuilds-users] [PATCH] development/hexedit: Updated for version 1.6. In-Reply-To: References: <20240216085309.23633-1-list+sbo@vahedi.org> Message-ID: February 16, 2024 at 10:25 AM, "Matteo Bernardini" wrote: > Forwarded for consideration to the hexedit maintainer Could someone review and/or push the change? From slack at giand.it Wed Feb 21 17:04:15 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Wed, 21 Feb 2024 18:04:15 +0100 Subject: [Slackbuilds-users] issues with msgpack-c Message-ID: Hi I use msgpack-c as required dependency for mmtf-cpp, that is a dependency for avogadrolibs Some days ago I had to build and install all dependencies required for Avogadro 2 for testing it in another machine, but the build of msgpack-c failed due an error returned by gtest: [ 15%] Building CXX object test/CMakeFiles/zone.dir/zone.cpp.o In file included from /usr/include/gtest/gtest-message.h:57, ???????????????? from /usr/include/gtest/gtest-assertion-result.h:46, ???????????????? from /usr/include/gtest/gtest.h:64, ???????????????? from /tmp/SBo/msgpack-3.3.0/test/zone.cpp:8: /usr/include/gtest/internal/gtest-port.h:279:2: error: #error C++ versions less than C++14 are not supported. ? 279 | #error C++ versions less than C++14 are not supported. ????? |? ^~~~~ Previous builds have not brought problems, but I think this is caused by recent upgrade of gtest package (January 2024). Furthermore, I don't know if gtest is a required or optional dependency and if it can be disabled, I have to check about this in the source. Since msgpack-c 3.3 is outdated, I tried also other solutions and I adapted the slackbuild for the latest release, msgpack-c-cpp-6.1.0. The build works but another problem happens: while msgpack-c 3.3 (and previous versions) support both C and C++, earlier releases (>= 4.0.0) have separated? the part C from C++ and the source is maintained with two distint git branches. At the moment I have built the package with the C++ part of latest sources released, it was easy because is a header-only library and I think this should be enough for mmtf-cpp package, but other packages released in SBo and requiring msgpack-c could need the C part of source. How to solved this? I think that the packages should be replaced with two separated packages, respectively for each implementation (C and C++), but it would be reasonable to test and check if all packages based on msgpack-c require both or single C/C++ implementations. The slackbuild for msgpack needs surely an upgrade if the issue given by gtest cannot be solved (the build of some parts of source requires C++11 standard and this conflicts with new version of googletest). Otherwise the slackbuilds of 11 packages remain broken: https://slackbuilds.org/advsearch.php?q=msgpack-c&stype=revdep However, I make myself available to do a possible split of the two packages if Ruben does not want to work on it -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From sb at rbn.im Wed Feb 21 20:15:20 2024 From: sb at rbn.im (Ruben Schuller) Date: Wed, 21 Feb 2024 21:15:20 +0100 Subject: [Slackbuilds-users] issues with msgpack-c In-Reply-To: References: Message-ID: <20240221211520.109ba3bb@kiwi.kuchen> Hi Giancarlo, hi list! Thank you for your mail! IIRC a while back I did submit an update to msgpack-c which was reverted as something else broke, I'm not sure what exactly. So having multiple SlackBuilds might well be required. I did take up maintenance of msgpack-c as dependency of neovim. I don't maintain neovim anymore so if you or anyone else wants to take it, that would be fine. Cheers Ruben 2024-02-21 Giancarlo Dess? : > Hi > > I use msgpack-c as required dependency for mmtf-cpp, that is a > dependency for avogadrolibs Some days ago I had to build and install > all dependencies required for Avogadro 2 for testing it in another > machine, but the build of msgpack-c failed due an error returned by > gtest: > > [ 15%] Building CXX object test/CMakeFiles/zone.dir/zone.cpp.o > In file included from /usr/include/gtest/gtest-message.h:57, > ???????????????? from /usr/include/gtest/gtest-assertion-result.h:46, > ???????????????? from /usr/include/gtest/gtest.h:64, > ???????????????? from /tmp/SBo/msgpack-3.3.0/test/zone.cpp:8: > /usr/include/gtest/internal/gtest-port.h:279:2: error: #error C++ > versions less than C++14 are not supported. > ? 279 | #error C++ versions less than C++14 are not supported. > ????? |? ^~~~~ > > Previous builds have not brought problems, but I think this is caused > by recent upgrade of gtest package (January 2024). Furthermore, I > don't know if gtest is a required or optional dependency and if it > can be disabled, I have to check about this in the source. > > Since msgpack-c 3.3 is outdated, I tried also other solutions and I > adapted the slackbuild for the latest release, msgpack-c-cpp-6.1.0. > The build works but another problem happens: while msgpack-c 3.3 (and > previous versions) support both C and C++, earlier releases (>= > 4.0.0) have separated? the part C from C++ and the source is > maintained with two distint git branches. > > At the moment I have built the package with the C++ part of latest > sources released, it was easy because is a header-only library and I > think this should be enough for mmtf-cpp package, but other packages > released in SBo and requiring msgpack-c could need the C part of > source. How to solved this? > > I think that the packages should be replaced with two separated > packages, respectively for each implementation (C and C++), but it > would be reasonable to test and check if all packages based on > msgpack-c require both or single C/C++ implementations. The > slackbuild for msgpack needs surely an upgrade if the issue given by > gtest cannot be solved (the build of some parts of source requires > C++11 standard and this conflicts with new version of googletest). > Otherwise the slackbuilds of 11 packages remain broken: > https://slackbuilds.org/advsearch.php?q=msgpack-c&stype=revdep > > However, I make myself available to do a possible split of the two > packages if Ruben does not want to work on it > From slack at giand.it Thu Feb 22 07:13:52 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Thu, 22 Feb 2024 08:13:52 +0100 Subject: [Slackbuilds-users] issues with msgpack-c In-Reply-To: <20240221211520.109ba3bb@kiwi.kuchen> References: <20240221211520.109ba3bb@kiwi.kuchen> Message-ID: <1cacf704-a8f9-414e-a8c1-cd6512fd337e@giand.it> Il 21/02/24 21:15, Ruben Schuller ha scritto: > Hi Giancarlo, hi list! > > Thank you for your mail! IIRC a while back I did submit an update to > msgpack-c which was reverted as something else broke, I'm not sure what > exactly. So having multiple SlackBuilds might well be required. > > I did take up maintenance of msgpack-c as dependency of neovim. I don't > maintain neovim anymore so if you or anyone else wants to take it, that > would be fine. > > Cheers > Ruben > > 2024-02-21 Giancarlo Dess?: > Well, meanwhile I tested some of these dependencies with the header-only library for C++. mmtf-cpp requires a little patch to find include files through cmake, PyMOL seems no have problems, whereas opendht surely requires a package for the C implementation and a patch for cmake findpackage. Other dependencies are not checked. I'll try to make two separate packages with different names as alternatives to old msgpack-c for transition. Greetings -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From slack at giand.it Thu Feb 22 19:26:04 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Thu, 22 Feb 2024 20:26:04 +0100 Subject: [Slackbuilds-users] issues with msgpack-c In-Reply-To: <20240221211520.109ba3bb@kiwi.kuchen> References: <20240221211520.109ba3bb@kiwi.kuchen> Message-ID: Il 21/02/24 21:15, Ruben Schuller ha scritto: > Hi Giancarlo, hi list! > > Thank you for your mail! IIRC a while back I did submit an update to > msgpack-c which was reverted as something else broke, I'm not sure what > exactly. So having multiple SlackBuilds might well be required. > > I did take up maintenance of msgpack-c as dependency of neovim. I don't > maintain neovim anymore so if you or anyone else wants to take it, that > would be fine. > > Cheers > Ruben > I solved the issue given by new gtest version since the tests can be disabled passing the option OFF to cmake. I fixed also some warnings from cmake. Now the build of msgpack-c 3.3.0 works and it can be kept for compatibility with the previously mentioned slackbuild. I submitted the update of msgpack-c. I have also submitted two new slackbuilds (msgpack-c-c and msgpack-c-cpp) for lastest versions of msgpack that have separate implementation of C and C++. Some slackbuilds cannot use new versions of this dependency because need to adapt the slackbuild and the .info file, so the name msgpack-c must be reserved to the legacy version 3.3.0, but an update for newer version can be useful for future uses. To manage possible issues given by other users I've proposed myself as new maintainer of all these packages but if you would maintain them feel free to take my place: I was interested only to solve the issue with mmtf-cpp. Greetings -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From sb at rbn.im Thu Feb 22 22:25:16 2024 From: sb at rbn.im (Ruben Schuller) Date: Thu, 22 Feb 2024 23:25:16 +0100 Subject: [Slackbuilds-users] issues with msgpack-c In-Reply-To: References: <20240221211520.109ba3bb@kiwi.kuchen> Message-ID: <20240222232516.5004e23a@kiwi.kuchen> Hi Giancarlo, hi list, 2024-02-22 Giancarlo Dess? : > To manage possible issues given by other users I've proposed myself > as new maintainer of all these packages but if you would maintain > them feel free to take my place: I was interested only to solve the > issue with mmtf-cpp. By all means, take it! Judging by your results you seem to be a much better maintainer for msgpack-c than I am! :) Cheers Ruben From slack at giand.it Fri Feb 23 05:52:24 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Fri, 23 Feb 2024 06:52:24 +0100 Subject: [Slackbuilds-users] Lost submissions? Message-ID: <8d64a10e-9ecb-450a-8b29-026480fba2e0@giand.it> Last Thursday I've submitted two updates, for FotoKilof and gaiasky, but they do not appears both from pending and approved lists. -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From slackbuilds at schoepfer.info Fri Feb 23 07:18:11 2024 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 23 Feb 2024 08:18:11 +0100 Subject: [Slackbuilds-users] Lost submissions? In-Reply-To: <8d64a10e-9ecb-450a-8b29-026480fba2e0@giand.it> References: <8d64a10e-9ecb-450a-8b29-026480fba2e0@giand.it> Message-ID: <43997050749db076b5089bb12d0c55c2@schoepfer.info> > Last Thursday I've submitted two updates, for FotoKilof and gaiasky, > but they do not appears both from pending and approved lists. It seems Andrew took the whole batch from(and before) Thursday and at this moment these builds appear once by once in https://slackbuilds.org/ready/ I wonder if the SBo-admins keep track if checking builds in parallel, as meanwhile i've submitted builds which depend on builds submitted before Thursday. Johannes From slack at giand.it Fri Feb 23 08:06:06 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Fri, 23 Feb 2024 09:06:06 +0100 Subject: [Slackbuilds-users] Lost submissions? In-Reply-To: <43997050749db076b5089bb12d0c55c2@schoepfer.info> References: <8d64a10e-9ecb-450a-8b29-026480fba2e0@giand.it> <43997050749db076b5089bb12d0c55c2@schoepfer.info> Message-ID: <07a923e8-77f1-441c-b90a-063f332671a1@giand.it> Il 23/02/24 08:18, Franzen via SlackBuilds-users ha scritto: >> Last Thursday I've submitted two updates, for FotoKilof and gaiasky, >> but they do not appears both from pending and approved lists. > > It seems Andrew took the whole batch from(and before) Thursday and at > this > moment these builds appear once by once in https://slackbuilds.org/ready/ > > I wonder if the SBo-admins keep track if checking builds in parallel, as > meanwhile i've submitted builds which depend on builds submitted > before Thursday. > > Johannes > _______________________________________________ > 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/ > Thanks Johannes, unfortunately there are several things that I can't understand :-) -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From slackbuilds at schoepfer.info Fri Feb 23 08:46:45 2024 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 23 Feb 2024 09:46:45 +0100 Subject: [Slackbuilds-users] Lost submissions? In-Reply-To: <07a923e8-77f1-441c-b90a-063f332671a1@giand.it> References: <8d64a10e-9ecb-450a-8b29-026480fba2e0@giand.it> <43997050749db076b5089bb12d0c55c2@schoepfer.info> <07a923e8-77f1-441c-b90a-063f332671a1@giand.it> Message-ID: > Thanks Johannes, unfortunately there are several things that I can't > understand :-) In short it means: Nothing got lost. FotoKilof https://git.slackbuilds.org/slackbuilds/commit/?h=user/aclemons/updates&id=5a8330f8a0c174b63194d9477b665a6249de3c69 gaiasky https://git.slackbuilds.org/slackbuilds/commit/?id=e075b33ad From willysr at slackbuilds.org Sat Feb 24 08:54:23 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 24 Feb 2024 15:54:23 +0700 Subject: [Slackbuilds-users] Updates - 20240224.1 Message-ID: <56ac4526-e931-4280-9374-af94ee8b15f3@slackbuilds.org> Sat Feb 24 08:35:48 UTC 2024 academic/gaiasky: Updated for version 3.5.9. academic/gcompris-qt: Updated for version 4.0. academic/nco: Updated for version 5.2.1. academic/plus42: Updated for version 1.1.4 academic/qucs-s: Updated for version 24.1.0. academic/units: Updated for version 2.23. audio/puddletag: Update dependencies audio/qmmp-plugin-pack-qt5: Updated for version 1.6.1. audio/qmmp-qt5: Updated for version 1.6.5. audio/sunvox: Updated for version v2.1.1c. desktop/battery-notify: Updated for version 1.4. desktop/caja: Updated for version 1.28.0. desktop/compiz-boxmenu: Switched to python2-lxml desktop/dbgl: updated for version 0.98 desktop/engrampa: Updated for version 1.28.0. desktop/marco: Updated for version 1.28.1. desktop/mate-control-center: Updated for version 1.28.0. desktop/mate-desktop-environment: Updated for version 1.28. desktop/mate-desktop: Updated for version 1.28.0. desktop/mate-media: Updated for version 1.28.0. desktop/mate-menus: Updated for version 1.28.0. desktop/mate-panel: Updated for version 1.28.0. desktop/mate-power-manager: Updated for version 1.28.0. desktop/mate-screensaver: Updated for version 1.28.0. desktop/mate-session-manager: Updated for version 1.28.0. desktop/mate-settings-daemon: Updated for version 1.28.0. desktop/mate-terminal: Updated for version 1.28.0. desktop/mate-utils: Updated for version 1.28.0. desktop/mozo: Updated for version 1.28.0. desktop/recoll: Split lxml dep into python2/python3 desktop/thunar-custom-actions: Switched to python3-lxml development/arduino-cli: Updated for version 0.35.2 development/aws-cdk: Updated for version 2.130.0. development/cargo-c: Updated for version 0.9.30. development/cloc: Version bump to 2.00 development/cosmocc: New maintainer, fix script perms. development/github-cli: Updated for version 2.44.1 development/heroku-cli: Added (heroku CLI). development/hexedit: Updated for version 1.6. development/jupyter-nbconvert: Update for 7.16.1 development/meld3: Updated for version 3.22.1. development/mmtf-cpp: Updates. development/mongodb-compass: Updated for version 1.42.1. development/nodejs: Updated for version 20.11.1. development/opentofu: Added (fork of terraform). development/pinner: Added (geany plugin). development/pre-commit: Updated for version 3.6.2. development/sbcl: Updated for version 2.4.1 development/tofuenv: Updated for version 1.0.6. development/xa: Updated for version 2.4.0. development/xnedit: Updated for version 1.5.3. games/LucasChess: Updated for version R2.11d. games/ags: updated for version 3.6.0.57 games/endless-sky: updated for version 0.10.6 games/lutris: Switched to python3-lxml gis/OWSLib: Switch to python3-lxml gis/gdal: Updated for version 3.8.4. gis/python3-basemap: Updated for version 1.4.1. gis/python3-xarray: Updated for version 2024.02.0. gis/pytrainer: Switched to python3-lxml graphics/FotoKilof: Updated for version 4.4.5. graphics/inkscape-gtk2: Switched to python2-lxml graphics/inkscape: Switched to python3-lxml libraries/canfigger: Added (file parser library). libraries/dav1d: Updated for version 1.4.0. libraries/highway: Updated for version 1.1.0. libraries/libavif: Updated for version 1.0.4. libraries/libei: Add missing python3-attr dependency. libraries/libei: Added (library for Emulated Input). libraries/libfabric: Updated for version 1.20.1. libraries/libgig: Updated for version 4.4.1. libraries/libindi-drivers: Updated for version 2.0.6 libraries/libindi-libraries: Corrected md5sum libraries/libindi-libraries: Updated for version 2.0.6 libraries/libindi: Updated for version 2.0.6 libraries/libjxl: Updated for version 0.9.2. libraries/libmatekbd: Updated for version 1.28.0. libraries/libmatemixer: Updated for version 1.28.0. libraries/libmateweather: Updated for version 1.28.0. libraries/libmysofa: Updated for version 1.3.2. libraries/librist: Updated for version 0.2.10. libraries/msgpack-c-c: Added (msgpack for C/C++). libraries/msgpack-c-cpp: Added (MessagePack implementation for C++). libraries/msgpack-c: Updates. libraries/pyPEG2: Add python3-lxml dep libraries/pyPEG2: Switched to python2-lxml libraries/qt-avif-image-plugin: Updated for version 0.8.0. libraries/qt-jpegxl-image-plugin: Updated for version 0.6.0. libraries/qt6: Use the internal re2. libraries/tree-sitter: Updated for version 0.21.0 libraries/vmaf: Updated for version 3.0.0. libraries/webkit2gtk4.1: Fix build on i586. libraries/webkit2gtk: Fix build on i586. misc/KeePass: Updated for version 2.56. misc/gourmet: Switched to python2-lxml misc/moreutils: Updated for version 0.68. misc/open-simh: Update for version a588496. multimedia/AviSynthPlus: Updated for version 3.7.3. multimedia/inputstream.adaptive: Version bump to 20.3.18 multimedia/muse-sounds-manager: Added (library for Emulated Input). multimedia/pocketsphinx: Updated for version 5.0.3. multimedia/radiotray: Switched to python2-lxml multimedia/rav1e: update component. multimedia/shine: Updated for version 3.1.1. multimedia/uavs3d: Updated for version 1.1. multimedia/videomass: Updated for version 5.0.6. network/Electrum: Updated for version 4.5.3. network/dropbox: Updated for version 193.4.5594. network/go-sendxmpp: Updated for version 0.8.3. network/httpie: new maintainer. network/llhttp: Updated for version 9.2.0. network/mailman: updated REQUIRES network/nessus: Updated for version 10.7.0. network/nmh: Updated for version 1.8. network/nyxt: Updated for version 3.11.3. network/openconnect: Remove workaround for broken oath-toolkit. network/protonmail-bridge: Updated for version 3.9.1. network/signal-desktop: Updated for version 6.48.1. network/sshuttle: updated for version 1.1.2 network/syncterm: Fix build on -current. network/telegram: Updated for version 4.14.16. network/telegram: Updated for version 4.15.0. network/tor-browser: Updated for version 13.0.10. network/translate: Switched to python3-lxml network/w3af: Switched to python2-lxml network/yle-dl: Switched to python3-lxml network/yt-dlp: Switch to versioned source. office/atril: Updated for version 1.28.0. office/grisbi: updated for version 3.0.3. New maintainer. office/openoffice.org: new maintainer. office/sigil: Split lxml dep into python2/python3 office/texworks: Updated for version 0.6.9. office/trelby: Switched to python2-lxml perl/perl-Digest-SHA: Added (Perl SHA). python/Flask: Updated for version 3.0.2. python/Unidecode: Updated for version 1.3.8. python/dnspython: Removed, renamed to python2-dnspython python/et_xmlfile: Switched to python3-lxml python/euca2ools: Switched to python2-lxml python/html5parser: Switched to python2-lxml python/jdcal: Split lxml dep into python2/python3 python/odoo: Switched to python3-lxml python/parsel: Switch to python2-lxml and rm cssselect (dep of lxml) python/pikepdf: Switched to python3-lxml python/pipdeptree: Updated for version 2.14.0. python/pycryptodomex: Updated for version 3.20.0. python/pyquery: Switch to python2-lxml and rm cssselect (dep of lxml) python/python-evdev: Updated for version 1.7.0. python/python2-dnspython: Added (Python2 of dnspython). python/python2-psutil: Updated for version 5.9.8. python/python3-aksharamukha: Switched to python3-lxml python/python3-anyio: Update for 4.3.0 python/python3-cinemagoer: Switched to python3-lxml python/python3-cookiecutter: Update for 2.6.0 python/python3-deluge-client: Version bump to 1.10.2 python/python3-dep-logic: Version bump to 0.2.0 python/python3-dnspython: updated for version 2.6.1 python/python3-docstring-to-markdown: Update for 0.15 python/python3-dogpile.cache: Version bump to 1.3.2 python/python3-dotenv: Updated for version 1.0.1. python/python3-fontMath: Updated for version 0.9.3 python/python3-httpcore: Updated for version 1.0.4. python/python3-jaraco.classes: Updated for version 3.3.1. python/python3-json5: Updated for version 0.9.17. python/python3-libtmux: Updated for version 0.31.0.post0. python/python3-meson-opt: Updated for version 1.3.2. python/python3-obspy: Switched to python3-lxml python/python3-orjson: Updated for version 3.9.14. python/python3-pdfminer.six: Updated for version 20231228. python/python3-poetry-core: Updated for version 1.9.0. python/python3-psutil: Updated for version 5.9.8. python/python3-pydantic-core: Updated for version 2.16.3. python/python3-pydantic: Updated for version 2.6.1. python/python3-pygame: Update script. python/python3-pykeepass: Switched to python3-lxml python/python3-pythran: Update for 0.15.0 python/python3-requests-cache: Updated for version 1.2.0. python/python3-setuptools-git-versioning: Added (python module). python/python3-sipsimple: Switched to python3-lxml python/python3-stevedore: Version bump to 5.2.0 python/python3-svglib: Switched to python3-lxml python/python3-tempora: Updated for version 5.5.1. python/python3-tox: Version bump to 4.13.0 python/python3-trove-classifiers: Updated for version 2024.2.22. python/python3-ufolib2: Switched to python3-lxml python/python3-uri_template: Update for 1.3.0 python/python3-virtualenv: Version bump to 20.25.1 python/python3-xmldiff: Switched to python3-lxml python/relatorio: Switched to python2-lxml python/tzdata: Updated for version 2024.1. ruby/ruby-build: Updated for version 20240221. system/Solaar: Updated for version 1.1.11. system/afdko: Switched to python3-lxml system/catatonit: Fix github tarball handling. system/docker-compose: Updated for version 2.24.6 system/hw-probe: Added (Hardware detection). system/iotop-c: Updated for version 1.26. system/jenkins: Updated for version 2.440.1. system/localepurge: Removed (use bleachbit). system/locust: Updated for version 2.23.1. system/lxqt-archiver: Update for 0.9.1 system/openzfs: updated for version 2.2.3 system/piper: Switched to python3-lxml system/plocate: Updated for version 1.1.22. system/pmdk: Updated for version 1.13.1. system/slackrepo-hints: Updated for version 20240224. system/targetcli-fb: Updated for version 2.1.58. system/tilda: Updated for version 2.0.0. system/tmuxp: Updated for version 1.39.0. system/xdg-ninja: Updated for version 0.2.0.2. system/xvfb-run: Updated for version 21.1.11 system/yelp-xsl: Switched to python3-lxml +--------------------------+ -- 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 didier at slint.fr Sun Feb 25 21:23:25 2024 From: didier at slint.fr (Didier Spaier) Date: Sun, 25 Feb 2024 22:23:25 +0100 Subject: [Slackbuilds-users] Can someone send a PR to allow building mate-control-center without systemd? Message-ID: Hello, Trying to build system-control-center 1.28 I came across this reported issue: https://github.com/mate-desktop/mate-control-center/issues/744 and added a comment to it, then just realized that Johannes had already found and applied a workaround in the SlackBuild he submitted https://slackbuilds.org/slackbuilds/15.0/desktop/mate-control-center/mate-control-center.SlackBuild I will also apply it, thanks Johannes but as suggested by lukefromdc in the GitHub issue thread it would be nice (also for other distros in the same no-systemd-yet league) to submit a PR. I could to do that, but someone else reading this is would do it better ;) Cheers, Didier From slackbuilds at schoepfer.info Mon Feb 26 06:36:34 2024 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 26 Feb 2024 07:36:34 +0100 Subject: [Slackbuilds-users] Can someone send a PR to allow building mate-control-center without systemd? In-Reply-To: References: Message-ID: <4c3266a5a2d3f861f7817f008396055e@schoepfer.info> Hi Didier, > I will also apply it, thanks Johannes but as suggested by lukefromdc in > the > GitHub issue thread it would be nice (also for other distros in the > same > no-systemd-yet league) to submit a PR. My sed-fix is not enough, as there is no meson or this package as far as i can recoll. An option --disable-systemd must be put into autotools, which also should trigger mate-system-info to get the hostname not with the help of systemd. This is the output of mate-system-info: Failed to get property 'Hostname': GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.hostname1 was not provided by any .service files By the way, mate-system-monitor -> "system" is very similar to mate-system-monitor and also shows the hostname. Maybe a better option would be --disable-capplet-system-info. Unfortunately i have hardly time the next days. We can move this off-list, as it is not directly SBo-related. Johannes From erich.public at protonmail.com Mon Feb 26 21:38:00 2024 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 26 Feb 2024 21:38:00 +0000 Subject: [Slackbuilds-users] hw-probe should be arch independent Message-ID: <_SIAFEJwwuevQ19LXmK67GWdkTJ6Sq6BWkMnwmY3WKJCsuuyl8a8s3z_FBreKQCNTZKURk63Opa2KfBJfuraXw7JntleFbqRYHBIsMyKXtk=@protonmail.com> Hello Dimitar, hw-probe looked interesting so I tried building it.? The build failed as x86_64 is "UNSUPPORTED".? But the Debian package is arch independent, so I don't know why you have this restriction. More than that though, I don't think you need to repackage the Debian binary.? The project supplies a Makefile. The software is just a perl script that gets installed to /usr/bin/hw-probe. Upstream doesn't provide a man page, but it looks like Debian just uses help2man, which Slackware has. Here is the contents of the Debian package (I just exploded the Debian package tarball): $ tree usr usr ??? bin ??? ??? hw-probe ??? share ??? doc ??? ??? hw-probe ??? ??? README.md.gz ??? ??? changelog.Debian.gz ??? ??? copyright ??? man ??? man1 ??? hw-probe.1.gz 6 directories, 6 files So it shouldn't be too difficult to just grab the upstream source to generate the package. Erich From dimitar at nikov.net Tue Feb 27 09:40:39 2024 From: dimitar at nikov.net (dimitar at nikov.net) Date: Tue, 27 Feb 2024 09:40:39 +0000 Subject: [Slackbuilds-users] hw-probe should be arch independent In-Reply-To: <_SIAFEJwwuevQ19LXmK67GWdkTJ6Sq6BWkMnwmY3WKJCsuuyl8a8s3z_FBreKQCNTZKURk63Opa2KfBJfuraXw7JntleFbqRYHBIsMyKXtk=@protonmail.com> References: <_SIAFEJwwuevQ19LXmK67GWdkTJ6Sq6BWkMnwmY3WKJCsuuyl8a8s3z_FBreKQCNTZKURk63Opa2KfBJfuraXw7JntleFbqRYHBIsMyKXtk=@protonmail.com> Message-ID: Hi Erich, I hope you are doing well. Thank you for your feedback, it is much appreciated. On 2024-02-26 21:38, Erich Ritz wrote: > Hello Dimitar, > > hw-probe looked interesting so I tried building it.? The build failed > as x86_64 is "UNSUPPORTED".? But the Debian package is arch > independent, so I don't know why you have this restriction. > Slackware package is arch independent too, hence x86_64 download is marked as unsupported. I do believe this is correct for acrh independent packages. There should be no issues building the package using SlackBiulds script. Would you mind providing me more details about the errors you are getting when trying to build it please? Thank you. > More than that though, I don't think you need to repackage the Debian > binary.? The project supplies a Makefile. The software is just a perl > script that gets installed to /usr/bin/hw-probe. > Makefile provided by upstream does not make any difference as it does a simple mkdir -p / copy (when installing) and rm -f (when uninstalling). The idea to repackage Debian package have a man page and I am little bit lazy (as any other programmer) :D > Upstream doesn't provide a man page, but it looks like Debian just uses > help2man, which Slackware has. > Nice shout, will move to help2man in next version update. > Here is the contents of the Debian package (I just exploded the Debian > package tarball): > > $ tree usr > usr > ??? bin > ??? ??? hw-probe > ??? share > ??? doc > ??? ??? hw-probe > ??? ??? README.md.gz > ??? ??? changelog.Debian.gz > ??? ??? copyright > ??? man > ??? man1 > ??? hw-probe.1.gz > > 6 directories, 6 files > > So it shouldn't be too difficult to just grab the upstream source to > generate the package. > Yes, you are absolutely right. I will move to upstream source in the upcoming update. > Erich Best regards, Dimitar From arnaud.garcia-fernandez at laposte.net Tue Feb 27 09:48:18 2024 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Tue, 27 Feb 2024 09:48:18 +0000 Subject: [Slackbuilds-users] hw-probe should be arch independent In-Reply-To: References: <_SIAFEJwwuevQ19LXmK67GWdkTJ6Sq6BWkMnwmY3WKJCsuuyl8a8s3z_FBreKQCNTZKURk63Opa2KfBJfuraXw7JntleFbqRYHBIsMyKXtk=@protonmail.com> Message-ID: <0DA3A76E-826B-4EFC-9ACE-4ED7B5B87D67@laposte.net> Hi fellow slackers. I'd guess that x86_64=UNSUPPORTED means it is unsupported. Which is not the case, it works. It should be left empty. Most builds have a unique source for all arch, noarch is the same, with only DOWNLOAD and MD5SUM. Best regards, - Yth. Le 27 f?vrier 2024 09:40:39 UTC, Dimitar Nikov via SlackBuilds-users a ?crit?: >Hi Erich, >I hope you are doing well. > >Thank you for your feedback, it is much appreciated. > >On 2024-02-26 21:38, Erich Ritz wrote: >> Hello Dimitar, >> >> hw-probe looked interesting so I tried building it.? The build failed as x86_64 is "UNSUPPORTED".? But the Debian package is arch independent, so I don't know why you have this restriction. >> > >Slackware package is arch independent too, hence x86_64 download is marked as unsupported. I do believe this is correct for acrh independent packages. >There should be no issues building the package using SlackBiulds script. >Would you mind providing me more details about the errors you are getting when trying to build it please? >Thank you. > >> More than that though, I don't think you need to repackage the Debian binary.? The project supplies a Makefile. The software is just a perl script that gets installed to /usr/bin/hw-probe. >> > >Makefile provided by upstream does not make any difference as it does a simple mkdir -p / copy (when installing) and rm -f (when uninstalling). The idea to repackage Debian package have a man page and I am little bit lazy (as any other programmer) :D > >> Upstream doesn't provide a man page, but it looks like Debian just uses help2man, which Slackware has. >> > >Nice shout, will move to help2man in next version update. > >> Here is the contents of the Debian package (I just exploded the Debian package tarball): >> >> $ tree usr >> usr >> ??? bin >> ??? ??? hw-probe >> ??? share >> ??? doc >> ??? ??? hw-probe >> ??? ??? README.md.gz >> ??? ??? changelog.Debian.gz >> ??? ??? copyright >> ??? man >> ??? man1 >> ??? hw-probe.1.gz >> >> 6 directories, 6 files >> >> So it shouldn't be too difficult to just grab the upstream source to generate the package. >> > >Yes, you are absolutely right. I will move to upstream source in the upcoming update. > >> Erich > >Best regards, >Dimitar >_______________________________________________ >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 dimitar at nikov.net Tue Feb 27 10:27:21 2024 From: dimitar at nikov.net (dimitar at nikov.net) Date: Tue, 27 Feb 2024 10:27:21 +0000 Subject: [Slackbuilds-users] hw-probe should be arch independent In-Reply-To: <0DA3A76E-826B-4EFC-9ACE-4ED7B5B87D67@laposte.net> References: <_SIAFEJwwuevQ19LXmK67GWdkTJ6Sq6BWkMnwmY3WKJCsuuyl8a8s3z_FBreKQCNTZKURk63Opa2KfBJfuraXw7JntleFbqRYHBIsMyKXtk=@protonmail.com> <0DA3A76E-826B-4EFC-9ACE-4ED7B5B87D67@laposte.net> Message-ID: <6fc8ab87e99cdfdb2578075c8f369210@nikov.net> Hi Arnaud, On 2024-02-27 09:48, Arnaud via SlackBuilds-users wrote: > Hi fellow slackers. > > I'd guess that x86_64=UNSUPPORTED means it is unsupported. > Which is not the case, it works. > It should be left empty. Thank you for clarification, I misinterpreted the instructions in Submission Guidelines. This is corrected now and new version update was submitted. > Most builds have a unique source for all arch, noarch is the same, with > only DOWNLOAD and MD5SUM. > > Best regards, > > - Yth. > > -- > _______________________________________________ > 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/ Best regards, Dimitar -------------- next part -------------- An HTML attachment was scrubbed... URL: From list+sbo at vahedi.org Tue Feb 27 13:37:13 2024 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Tue, 27 Feb 2024 13:37:13 +0000 Subject: [Slackbuilds-users] Fix qBittorrent BUILD number Message-ID: <6869ccd6050924a5de49fbfca2fa872c7a24819b@vahedi.org> Hi, I was just snooping around in the ready list [1] and then I noticed that the qBittorrent package update [2] has the wrong BUILD number: "2" instead of "1". Since it won't be possible to fix it later in a meaning manner (upgrading from build number "2" to "1"), if anybody cares, please fix it before pushing it to the main branch. I know I should have sent this message to the "devel" list, but I can't. So appologies for that. Cheers, Shahab [1] https://slackbuilds.org/ready/ [2] https://git.slackbuilds.org/slackbuilds/commit/?id=b273b7177 From urchlay at slackware.uk Tue Feb 27 23:52:31 2024 From: urchlay at slackware.uk (B. Watson) Date: Tue, 27 Feb 2024 18:52:31 -0500 (EST) Subject: [Slackbuilds-users] hw-probe should be arch independent In-Reply-To: References: <_SIAFEJwwuevQ19LXmK67GWdkTJ6Sq6BWkMnwmY3WKJCsuuyl8a8s3z_FBreKQCNTZKURk63Opa2KfBJfuraXw7JntleFbqRYHBIsMyKXtk=@protonmail.com> Message-ID: <70ddede5-a524-8786-f27c-adb1165b2335@slackware.uk> On Tue, 27 Feb 2024, Dimitar Nikov via SlackBuilds-users wrote: > Slackware package is arch independent too, hence x86_64 download is > marked as unsupported. I do believe this is correct for acrh independent > packages. No, it should just be blank... DOWNLOAD_x86_64="" ...which means "x86_64 uses the same source as the regular DOWNLOAD". UNSUPPORTED would mean the package can't be built on x86_64, which is obviously not the case here. >> Upstream doesn't provide a man page, but it looks like Debian just uses >> help2man, which Slackware has. >> > > Nice shout, will move to help2man in next version update. Beware: Slackware's help2man isn't the same as Debian's. You might make it work, but it might take some messing with. If you have trouble, just grab the man page from the Debian package and include it with your script. Install with something like: mkdir -p $PKG/usr/man/man1 gzip -9c < $CWD/$PRGNAM.1 > $PKG/usr/man/man1/$PRGNAM.1.gz Hope this helps... From sbo at linuxgalaxy.org Wed Feb 28 01:30:17 2024 From: sbo at linuxgalaxy.org (KB_SBo) Date: Wed, 28 Feb 2024 01:30:17 +0000 Subject: [Slackbuilds-users] AMD ROCm SlackBuilds In-Reply-To: References: Message-ID: On 12/30/23 11:25, 414N wrote: > - location: I've currently put all the ROCm packages under the > "graphics" section. Is this correct or should I change it? I suggest the location as "system" or maybe it's better under "rocm" a new category given the number of scripts and packages with all the interdependencies. -kb From 414N at slacky.it Wed Feb 28 10:49:38 2024 From: 414N at slacky.it (414N) Date: Wed, 28 Feb 2024 11:49:38 +0100 Subject: [Slackbuilds-users] AMD ROCm SlackBuilds In-Reply-To: References: Message-ID: Il 28/02/24 02:30, KB_SBo ha scritto: > On 12/30/23 11:25, 414N wrote: >> - location: I've currently put all the ROCm packages under the >> "graphics" section. Is this correct or should I change it? > > > I suggest the location as "system" or maybe it's better under "rocm" a > new category given the number of scripts and packages with all the > interdependencies. Yes, that's a possibility. On the other hand, the cudatoolkit and cudnn packages are currently under the "development" category, so maybe that's a better fit for the majority (if not all) of the rocm packages. -- Alan Alberghini SBo clone: https://github.com/414n/slackbuilds.org From dimitar at nikov.net Wed Feb 28 11:02:41 2024 From: dimitar at nikov.net (dimitar at nikov.net) Date: Wed, 28 Feb 2024 11:02:41 +0000 Subject: [Slackbuilds-users] hw-probe should be arch independent In-Reply-To: <70ddede5-a524-8786-f27c-adb1165b2335@slackware.uk> References: <_SIAFEJwwuevQ19LXmK67GWdkTJ6Sq6BWkMnwmY3WKJCsuuyl8a8s3z_FBreKQCNTZKURk63Opa2KfBJfuraXw7JntleFbqRYHBIsMyKXtk=@protonmail.com> <70ddede5-a524-8786-f27c-adb1165b2335@slackware.uk> Message-ID: On 2024-02-27 23:52, B. Watson wrote: > On Tue, 27 Feb 2024, Dimitar Nikov via SlackBuilds-users wrote: > >> Slackware package is arch independent too, hence x86_64 download is >> marked as unsupported. I do believe this is correct for acrh >> independent packages. > > No, it should just be blank... > > DOWNLOAD_x86_64="" > > ...which means "x86_64 uses the same source as the regular DOWNLOAD". > > UNSUPPORTED would mean the package can't be built on x86_64, which is > obviously not the case here. > Thank you for the clarification, this one is already fixed. >>> Upstream doesn't provide a man page, but it looks like Debian just >>> uses help2man, which Slackware has. >>> >> >> Nice shout, will move to help2man in next version update. > > Beware: Slackware's help2man isn't the same as Debian's. You might make > it > work, but it might take some messing with. > > If you have trouble, just grab the man page from the Debian package and > include it with your script. Install with something like: > > mkdir -p $PKG/usr/man/man1 > gzip -9c < $CWD/$PRGNAM.1 > $PKG/usr/man/man1/$PRGNAM.1.gz > > Hope this helps... That would not be necessary, help2man worked a treat. Best regards, Dimitar From list+sbo at vahedi.org Thu Feb 15 15:54:40 2024 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Thu, 15 Feb 2024 16:54:40 +0100 Subject: [Slackbuilds-users] [PATCH] development/hexedit: Updated for version 1.6 Message-ID: <20240215155440.39223-1-list+sbo@vahedi.org> The current version (1.2.12) cannot even be built anymore, because that source version exists no more. Tested on a Slackware64 15.0 with the latest patches in. The lint results are OK both for the script and the package. Signed-off-by: Shahab Vahedi --- development/hexedit/hexedit.SlackBuild | 9 ++++++--- development/hexedit/hexedit.info | 8 ++++---- 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/development/hexedit/hexedit.SlackBuild b/development/hexedit/hexedit.SlackBuild index 21381bcac0..33f3d82e5c 100644 --- a/development/hexedit/hexedit.SlackBuild +++ b/development/hexedit/hexedit.SlackBuild @@ -27,7 +27,7 @@ cd $(dirname $0) ; CWD=$(pwd) PRGNAM=hexedit -VERSION=${VERSION:-1.2.12} +VERSION=${VERSION:-1.6} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} @@ -66,8 +66,8 @@ rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $PRGNAM-$VERSION -tar xvf $CWD/$PRGNAM-$VERSION.src.tgz -cd $PRGNAM +tar xvf $CWD/$VERSION.tar.gz +cd $PRGNAM-$VERSION chown -R root:root . find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ @@ -75,6 +75,7 @@ find -L . \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; +./autogen.sh CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ @@ -103,6 +104,8 @@ DOCS="COPYING Changes TODO" mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cp -a $DOCS $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild +# TODO file is empty in version 1.6 +test -s $PKG/usr/doc/$PRGNAM-$VERSION/TODO || rm $PKG/usr/doc/$PRGNAM-$VERSION/TODO mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc diff --git a/development/hexedit/hexedit.info b/development/hexedit/hexedit.info index 111b69d3b3..c4cd5ac420 100644 --- a/development/hexedit/hexedit.info +++ b/development/hexedit/hexedit.info @@ -1,8 +1,8 @@ PRGNAM="hexedit" -VERSION="1.2.12" -HOMEPAGE="http://prigaux.chez.com/hexedit.html" -DOWNLOAD="http://rigaux.org/hexedit-1.2.12.src.tgz" -MD5SUM="0d2f48610006278cd93359fea9a06d5c" +VERSION="1.6" +HOMEPAGE="https://rigaux.org/hexedit.html" +DOWNLOAD="https://github.com/pixel/hexedit/archive/1.6.tar.gz" +MD5SUM="9b5849759dbda9ab25ec22818c16e970" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -- 2.35.8 From gian at giand.it Wed Feb 21 16:50:27 2024 From: gian at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Wed, 21 Feb 2024 17:50:27 +0100 Subject: [Slackbuilds-users] issues with msgpack-c Message-ID: <488ad0ff-4591-4ccc-b717-c05fbbbfb6ee@giand.it> Hi I use msgpack-c as required dependency for mmtf-cpp, that is a dependency for avogadrolibs Some days ago I had to build and install all dependencies required for Avogadro 2 for testing it in another machine, but the build of msgpack-c failed due an error returned by gtest: [ 15%] Building CXX object test/CMakeFiles/zone.dir/zone.cpp.o In file included from /usr/include/gtest/gtest-message.h:57, ???????????????? from /usr/include/gtest/gtest-assertion-result.h:46, ???????????????? from /usr/include/gtest/gtest.h:64, ???????????????? from /tmp/SBo/msgpack-3.3.0/test/zone.cpp:8: /usr/include/gtest/internal/gtest-port.h:279:2: error: #error C++ versions less than C++14 are not supported. ? 279 | #error C++ versions less than C++14 are not supported. ????? |? ^~~~~ Previous builds have not brought problems, but I think this is caused by recent upgrade of gtest package (January 2024). Furthermore, I don't know if gtest is a required or optional dependency and if it can be disabled, I have to check about this in the source. Since msgpack-c 3.3 is outdated, I tried also other solutions and I adapted the slackbuild for the latest release, msgpack-c-cpp-6.1.0. The build works but another problem happens: while msgpack-c 3.3 (and previous versions) support both C and C++, earlier releases (>= 4.0.0) have separated? the part C from C++ and the source is maintained with two distint git branches. At the moment I have built the package with the C++ part of latest sources released, it was easy because is a header-only library and I think this should be enough for mmtf-cpp package, but other packages released in SBo and requiring msgpack-c could need the C part of source. How to solved this? I think that the packages should be replaced with two separated packages, respectively for each implementation (C and C++), but it would be reasonable to test and check if all packages based on msgpack-c require both or single C/C++ implementations. The slackbuild for msgpack needs surely an upgrade if the issue given by gtest cannot be solved (the build of some parts of source requires C++11 standard and this conflicts with new version of googletest). Otherwise the slackbuilds of 11 packages remain broken: https://slackbuilds.org/advsearch.php?q=msgpack-c&stype=revdep However, I make myself available to do a possible split of the two packages if Ruben does not want to work on it -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From sb at rbn.im Thu Feb 29 11:39:51 2024 From: sb at rbn.im (Ruben Schuller) Date: Thu, 29 Feb 2024 12:39:51 +0100 Subject: [Slackbuilds-users] spring cleaning some packages Message-ID: <20240229123951.6b8ca5e8@kiwi.kuchen> Hi list, I don't really use these anymore, so if anyone wants them feel free - I think they could be in better hands :) libtermkey libvterm lua-lpeg lua-luv lua-mpack unibilium vis nim Most of these are dependencies for neovim and vis - except nim. I will try to maintain them if no one wants them, the pace might be slow though. I think xsession-xinitrc can be deleted as well, it's a crude hack I invented :) Cheers Ruben From alik at ejik.org Thu Feb 29 13:47:02 2024 From: alik at ejik.org (Alexander Verbovetsky) Date: Thu, 29 Feb 2024 16:47:02 +0300 Subject: [Slackbuilds-users] spring cleaning some packages In-Reply-To: <20240229123951.6b8ca5e8@kiwi.kuchen> References: <20240229123951.6b8ca5e8@kiwi.kuchen> Message-ID: Hello, On Thu, Feb 29, 2024 at 12:39:51PM +0100, Ruben Schuller wrote: > I don't really use these anymore, so if anyone wants them feel free - > I think they could be in better hands :) > > libtermkey > libvterm > lua-lpeg > lua-luv > lua-mpack > unibilium > vis > nim > > Most of these are dependencies for neovim and vis - except nim. I will > try to maintain them if no one wants them, the pace might be slow > though. I can take four neovim dependencies: libtermkey libvterm lua-lpeg unibilium (lua-mpack dependency is going to be dropped) Best regards, Alexander From zsd+slackbuilds at jdvb.ca Thu Feb 29 16:12:14 2024 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Thu, 29 Feb 2024 12:12:14 -0400 Subject: [Slackbuilds-users] tracking down SBo "dependencies" Message-ID: I recently upgraded the SBo dav1d, which upgraded the library from libdav1d.so.6 to libdav1d.so.7. Unfortunately, a couple of other SBo packages (libheif and vlc) had references to (specifically) libdav1d.so.6, which caused them to whine a bit. It was easy enough to recompile libheif and vlc after I found the problem, but this got me wondering... Does anyone have an easy way of tracking down this sort of "breakage" which might happen when upgrading an SBo package? Thanks. Jim From andrzej at telszewski.com Thu Feb 29 16:47:49 2024 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Thu, 29 Feb 2024 17:47:49 +0100 (GMT+01:00) Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: Message-ID: <253e9c31-d1e0-4055-a1ca-135473c99655@telszewski.com> *From: *Jim *To: *slackbuilds-users at slackbuilds.org *Date: *29 Feb 2024 17:12:58 *Subject: *[Slackbuilds-users] tracking down SBo "dependencies" > I recently upgraded the SBo dav1d, which upgraded the library from > libdav1d.so.6 to libdav1d.so.7. > > Unfortunately, a couple of other SBo packages (libheif and vlc) had > references to (specifically) libdav1d.so.6, which caused them to whine a > bit. > > It was easy enough to recompile libheif and vlc after I found the problem, > but this got me wondering... > > Does anyone have an easy way of tracking down this sort of "breakage" which > might happen when upgrading an SBo package? > > Thanks. > Please consider tool like _slackrepo_. It will rebuild a package in question should its dependiences be updated. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 691 bytes Desc: not available URL: From arnaud.garcia-fernandez at laposte.net Thu Feb 29 16:53:30 2024 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Thu, 29 Feb 2024 16:53:30 +0000 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: Message-ID: <35779813-952E-4E08-B804-F2F10F000DDD@laposte.net> Tracking the breakage might require launching the app, or checking with ldd. However, tracking potential breakages could be done using hoorex. # hoorex -i dav1d This'll list all installed packages requiring directly dav1d. - Yth. Le 29 f?vrier 2024 16:12:14 UTC, Jim a ?crit?: >I recently upgraded the SBo dav1d, which upgraded the library from >libdav1d.so.6 to libdav1d.so.7. > >Unfortunately, a couple of other SBo packages (libheif and vlc) had >references to (specifically) libdav1d.so.6, which caused them to whine a >bit. > >It was easy enough to recompile libheif and vlc after I found the problem, >but this got me wondering... > >Does anyone have an easy way of tracking down this sort of "breakage" which >might happen when upgrading an SBo package? > >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/ > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.public at protonmail.com Thu Feb 29 16:54:42 2024 From: erich.public at protonmail.com (Erich Ritz) Date: Thu, 29 Feb 2024 16:54:42 +0000 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: Message-ID: <_mmBPl1qQilH8nPVVHAPLQ6m-Zxm_UR7_ZfI9bnQ10brFS6M-wwZE09aw69Hu0yTdbQYD0H3LjKnqOR9wFfkiDoPbsgNspHK4SnmgmFSKxs=@protonmail.com> On Thursday, February 29th, 2024 at 10:12 AM, Jim wrote: > > > I recently upgraded the SBo dav1d, which upgraded the library from > libdav1d.so.6 to libdav1d.so.7. > > Unfortunately, a couple of other SBo packages (libheif and vlc) had > references to (specifically) libdav1d.so.6, which caused them to whine a > bit. > > It was easy enough to recompile libheif and vlc after I found the problem, > but this got me wondering... > > Does anyone have an easy way of tracking down this sort of "breakage" which > might happen when upgrading an SBo package? > If you are using sbopkg's queue files they should list direct dependencies (including optional ones). So a quick grep should help there. For example: $ grep dav1d /var/lib/sbopkg/queues/*.sqf /var/lib/sbopkg/queues/dav1d.sqf:dav1d /var/lib/sbopkg/queues/ffmpeg.sqf:@dav1d /var/lib/sbopkg/queues/vlc.sqf:@dav1d If using slackrepo packages should get automatically rebuilt when direct dependencies are upgraded (when using "slackrepo update"). Using slackrepo for quite a while now I've never had the problem of a package failing to recompile when necessary. By the way, the slackrepo method relies on the *.info file to list ALL direct dependencies, even those which are also dependencies of dependencies. Some maintainers like to cull the list of dependencies which are also dependencies of dependencies (which I personally disagree with...). Erich > 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 dickson.tim at googlemail.com Thu Feb 29 16:55:35 2024 From: dickson.tim at googlemail.com (Tim Dickson) Date: Thu, 29 Feb 2024 16:55:35 +0000 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: Message-ID: it is hard for optional dependencies. for hard deps, you can do an advanced reverse dependency(full) search on slackbuilds.org Personally I keep build lists for the things I use, including optional deps, and build flags and other special build instructions. It is more work, and when a package is updated one should recheck the deps incase they have changed, but it helps, so I rebuild all packages that directly depend on the updated one. Occasionally you have to rebuild further up the dep tree, but it works most of the time. Regards, Tim On 29/02/2024 16:12, Jim wrote: > I recently upgraded the SBo dav1d, which upgraded the library from > libdav1d.so.6 to libdav1d.so.7. > > Unfortunately, a couple of other SBo packages (libheif and vlc) had > references to (specifically) libdav1d.so.6, which caused them to whine a > bit. > > It was easy enough to recompile libheif and vlc after I found the problem, > but this got me wondering... > > Does anyone have an easy way of tracking down this sort of "breakage" which > might happen when upgrading an SBo package? > > 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 zsd+slackbuilds at jdvb.ca Thu Feb 29 19:22:49 2024 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Thu, 29 Feb 2024 15:22:49 -0400 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: <35779813-952E-4E08-B804-F2F10F000DDD@laposte.net> References: <35779813-952E-4E08-B804-F2F10F000DDD@laposte.net> Message-ID: Hi Arnaud, On Thu, Feb 29, 2024 at 16:53 (+0000), Arnaud via SlackBuilds-users wrote: > Tracking the breakage might require launching the app, Trying *every* program after upgrading a library seems like a bit of a non-starter. > or checking with ldd. After seeing a complaint appear in my terminal window I ran ldd on a lot of things (such as the vlc binary and the libraries of libheif) and it didn't show up. However, what I didn't look at immediately, which I now know was the place to look, is /usr/X11/lib64/vlc/plugins/codec/libdav1d_plugin.so, which is (presumably) the thing that whined after I upgrades dav1d. Similarly /usr/X11/lib64/libheif/libheif-dav1d.so has a reference to libdav1d.so.7. > However, tracking potential breakages could be done using hoorex. Not in this case... > # hoorex -i dav1d This'll list all installed packages requiring directly > dav1d. And there's the problem... Neither vlc nor libheif (nor maybe others I haven't found yet) *directly* require dav1d, so hoorex doesn't list them. Cheers. Jim > Le 29 f?vrier 2024 16:12:14 UTC, Jim a ?crit?: >>I recently upgraded the SBo dav1d, which upgraded the library from >>libdav1d.so.6 to libdav1d.so.7. >>Unfortunately, a couple of other SBo packages (libheif and vlc) had >>references to (specifically) libdav1d.so.6, which caused them to whine a >>bit. >>It was easy enough to recompile libheif and vlc after I found the problem, >>but this got me wondering... >>Does anyone have an easy way of tracking down this sort of "breakage" which >>might happen when upgrading an SBo package? >>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/ > -- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ From arnaud.garcia-fernandez at laposte.net Thu Feb 29 19:30:49 2024 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Thu, 29 Feb 2024 19:30:49 +0000 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: <35779813-952E-4E08-B804-F2F10F000DDD@laposte.net> Message-ID: <249D4F9F-4E55-4AC2-83D2-16B0C420B582@laposte.net> Well, you've still got sbbdep then, in reverse mode it could help you. It does calculate a full dependency tree, binary only, so for like python packages it won't work, but in your case it should. I never used it like that though, so it's kind of a guess. - Yth Le 29 f?vrier 2024 19:22:49 UTC, Jim a ?crit?: >Hi Arnaud, > >On Thu, Feb 29, 2024 at 16:53 (+0000), Arnaud via SlackBuilds-users wrote: > >> Tracking the breakage might require launching the app, > >Trying *every* program after upgrading a library seems like a bit of a >non-starter. > >> or checking with ldd. > >After seeing a complaint appear in my terminal window I ran ldd on a lot of >things (such as the vlc binary and the libraries of libheif) and it didn't >show up. However, what I didn't look at immediately, which I now know was >the place to look, is /usr/X11/lib64/vlc/plugins/codec/libdav1d_plugin.so, >which is (presumably) the thing that whined after I upgrades dav1d. > >Similarly /usr/X11/lib64/libheif/libheif-dav1d.so has a reference to >libdav1d.so.7. > >> However, tracking potential breakages could be done using hoorex. > >Not in this case... > >> # hoorex -i dav1d This'll list all installed packages requiring directly >> dav1d. > >And there's the problem... Neither vlc nor libheif (nor maybe others I >haven't found yet) *directly* require dav1d, so hoorex doesn't list them. > >Cheers. > Jim > >> Le 29 f?vrier 2024 16:12:14 UTC, Jim a ?crit?: >>>I recently upgraded the SBo dav1d, which upgraded the library from >>>libdav1d.so.6 to libdav1d.so.7. > >>>Unfortunately, a couple of other SBo packages (libheif and vlc) had >>>references to (specifically) libdav1d.so.6, which caused them to whine a >>>bit. > >>>It was easy enough to recompile libheif and vlc after I found the problem, >>>but this got me wondering... > >>>Does anyone have an easy way of tracking down this sort of "breakage" which >>>might happen when upgrading an SBo package? > >>>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/ > > >> -- > >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ > > >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - https://slackbuilds.org/faq/ > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From zsd+slackbuilds at jdvb.ca Thu Feb 29 19:34:02 2024 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Thu, 29 Feb 2024 15:34:02 -0400 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: <_mmBPl1qQilH8nPVVHAPLQ6m-Zxm_UR7_ZfI9bnQ10brFS6M-wwZE09aw69Hu0yTdbQYD0H3LjKnqOR9wFfkiDoPbsgNspHK4SnmgmFSKxs=@protonmail.com> References: <_mmBPl1qQilH8nPVVHAPLQ6m-Zxm_UR7_ZfI9bnQ10brFS6M-wwZE09aw69Hu0yTdbQYD0H3LjKnqOR9wFfkiDoPbsgNspHK4SnmgmFSKxs=@protonmail.com> Message-ID: On Thu, Feb 29, 2024 at 16:54 (+0000), Erich Ritz via SlackBuilds-users wrote: > On Thursday, February 29th, 2024 at 10:12 AM, Jim wrote: >> I recently upgraded the SBo dav1d, which upgraded the library from >> libdav1d.so.6 to libdav1d.so.7. >> Unfortunately, a couple of other SBo packages (libheif and vlc) had >> references to (specifically) libdav1d.so.6, which caused them to whine a >> bit. >> It was easy enough to recompile libheif and vlc after I found the problem, >> but this got me wondering... >> Does anyone have an easy way of tracking down this sort of "breakage" which >> might happen when upgrading an SBo package? > If you are using sbopkg's queue files they should list direct dependencies (including optional ones). So a quick grep should help there. > For example: > $ grep dav1d /var/lib/sbopkg/queues/*.sqf > /var/lib/sbopkg/queues/dav1d.sqf:dav1d > /var/lib/sbopkg/queues/ffmpeg.sqf:@dav1d > /var/lib/sbopkg/queues/vlc.sqf:@dav1d I am not using sbopkg, but maybe I should be. > If using slackrepo packages should get automatically rebuilt when direct > dependencies are upgraded (when using "slackrepo update"). dav1d is *not* in the REQUIRES list of vlc, so I don't think it qualifies as a "direct dependency". > Using slackrepo for quite a while now I've never had the problem of a > package failing to recompile when necessary. That's good to know, thanks. > By the way, the slackrepo method relies on the *.info file to list ALL > direct dependencies, even those which are also dependencies of > dependencies. Some maintainers like to cull the list of dependencies > which are also dependencies of dependencies (which I personally disagree > with...). Hmmm... I don't see any dependency path in the .info files which leads me from vlc to dav1d. Maybe I'm missing it, but if it is not there, I wonder if slackrepo would actually catch this. I guess there's one way to find out. Cheers. Jim From zsd+slackbuilds at jdvb.ca Thu Feb 29 19:46:27 2024 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Thu, 29 Feb 2024 15:46:27 -0400 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: <253e9c31-d1e0-4055-a1ca-135473c99655@telszewski.com> References: <253e9c31-d1e0-4055-a1ca-135473c99655@telszewski.com> Message-ID: On Thu, Feb 29, 2024 at 17:47 (+0100), Andrzej Telszewski wrote: > *From: *Jim > *To: *slackbuilds-users at slackbuilds.org > *Date: *29 Feb 2024 17:12:58 > *Subject: *[Slackbuilds-users] tracking down SBo "dependencies" >> I recently upgraded the SBo dav1d, which upgraded the library from >> libdav1d.so.6 to libdav1d.so.7. >> Unfortunately, a couple of other SBo packages (libheif and vlc) had >> references to (specifically) libdav1d.so.6, which caused them to whine a >> bit. >> It was easy enough to recompile libheif and vlc after I found the problem, >> but this got me wondering... >> Does anyone have an easy way of tracking down this sort of "breakage" which >> might happen when upgrading an SBo package? > Please consider tool like _slackrepo_. > It will rebuild a package in question should its dependiences be updated. Hi Andrzej, thanks for that pointer. >From other discussions it's not clear that slackrepo would catch this, but maybe I'll find out. Jim From alik at ejik.org Thu Feb 29 19:52:14 2024 From: alik at ejik.org (Alexander Verbovetsky) Date: Thu, 29 Feb 2024 22:52:14 +0300 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: <35779813-952E-4E08-B804-F2F10F000DDD@laposte.net> Message-ID: On Thu, Feb 29, 2024 at 03:22:49PM -0400, Jim wrote: > And there's the problem... Neither vlc nor libheif (nor maybe others I > haven't found yet) *directly* require dav1d, so hoorex doesn't list > them. https://slackbuilds.org/slackbuilds/15.0/libraries/libheif/libheif.info has davd1 in the REQUIRES field. On Thu, Feb 29, 2024 at 04:54:42PM +0000, Erich Ritz via SlackBuilds-users wrote: > By the way, the slackrepo method relies on the *.info file to list ALL > direct dependencies, even those which are also dependencies of > dependencies. Some maintainers like to cull the list of dependencies > which are also dependencies of dependencies (which I personally > disagree with...). slackrepo creates the list of all dependencies foo.dep and I think it uses it. Maybe I'm wrong. Best regards, Alexander From matteo.bernardini at gmail.com Thu Feb 29 19:55:57 2024 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 29 Feb 2024 20:55:57 +0100 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: Message-ID: Il giorno gio 29 feb 2024 alle ore 17:12 Jim ha scritto: > I recently upgraded the SBo dav1d, which upgraded the library from > libdav1d.so.6 to libdav1d.so.7. > > Unfortunately, a couple of other SBo packages (libheif and vlc) had > references to (specifically) libdav1d.so.6, which caused them to whine a > bit. > > It was easy enough to recompile libheif and vlc after I found the problem, > but this got me wondering... > > Does anyone have an easy way of tracking down this sort of "breakage" which > might happen when upgrading an SBo package? > > Thanks. > Jim > > some time ago Pat shared one script he uses for this cases https://www.linuxquestions.org/questions/slackware-14/why-slackpkg-doesn%27t-resolve-dependencies-4175720632/#post6403575 Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Thu Feb 29 19:57:19 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Thu, 29 Feb 2024 11:57:19 -0800 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: <253e9c31-d1e0-4055-a1ca-135473c99655@telszewski.com> Message-ID: On Thu, Feb 29, 2024, 11:46?AM Jim wrote: > On Thu, Feb 29, 2024 at 17:47 (+0100), Andrzej Telszewski wrote: > > > *From: *Jim > > *To: *slackbuilds-users at slackbuilds.org > > *Date: *29 Feb 2024 17:12:58 > > *Subject: *[Slackbuilds-users] tracking down SBo "dependencies" > > >> I recently upgraded the SBo dav1d, which upgraded the library from > >> libdav1d.so.6 to libdav1d.so.7. > > >> Unfortunately, a couple of other SBo packages (libheif and vlc) had > >> references to (specifically) libdav1d.so.6, which caused them to whine a > >> bit. > > >> It was easy enough to recompile libheif and vlc after I found the > problem, > >> but this got me wondering... > > >> Does anyone have an easy way of tracking down this sort of "breakage" > which > >> might happen when upgrading an SBo package? > > > Please consider tool like _slackrepo_. > > It will rebuild a package in question should its dependiences be updated. > > Hi Andrzej, > > thanks for that pointer. > > From other discussions it's not clear that slackrepo would catch this, but > maybe I'll find out. > > Jim > Looking at VLC's SBo page, dav1d support is detected automatically, but not listed as a required dependency. If slackrepo is used in a clean environment like expected, VLC would not be compiled with dav1d support without explicitly adding that dependency through the ADDREQUIRES option in the hintfile. Thus, an upgrade to dav1d would leave VLC unaffected unless you manually added that dependency to the hint file. If the dependency was added, VLC would be rebuilt automatically by slackrepo. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zsd+slackbuilds at jdvb.ca Thu Feb 29 19:44:58 2024 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Thu, 29 Feb 2024 15:44:58 -0400 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: Message-ID: On Thu, Feb 29, 2024 at 16:55 (+0000), Tim Dickson via SlackBuilds-users wrote: > it is hard for optional dependencies. for hard deps, you can do an advanced > reverse dependency(full) search on slackbuilds.org > Personally I keep build lists for the things I use, including optional deps, > and build flags and other special build instructions. > It is more work, and when a package is updated one should recheck the deps > incase they have changed, but it helps, so I rebuild > all packages that directly depend on the updated one. Occasionally you have > to rebuild further up the dep tree, but it works > most of the time. Thanks Tim. I do see the value of writing things like this down. However, up until the day before yesterday, I had no idea that libheif and vlc would have pulled in dav1d, so I wouldn't have known to write it down. Certainly, this is a rare problem, at least in my experience. Had the update to dav1d been to 6.1 instead of 7.0, all would have been OK. Cheers. Jim > On 29/02/2024 16:12, Jim wrote: >> I recently upgraded the SBo dav1d, which upgraded the library from >> libdav1d.so.6 to libdav1d.so.7. >> Unfortunately, a couple of other SBo packages (libheif and vlc) had >> references to (specifically) libdav1d.so.6, which caused them to whine a >> bit. >> It was easy enough to recompile libheif and vlc after I found the problem, >> but this got me wondering... >> Does anyone have an easy way of tracking down this sort of "breakage" which >> might happen when upgrading an SBo package? >> 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/ > _______________________________________________ > 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/