From slackalaxy at gmail.com Fri Mar 1 09:38:27 2024 From: slackalaxy at gmail.com (Petar Petrov) Date: Fri, 1 Mar 2024 11:38:27 +0200 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: Message-ID: there were several discussions about Slackware needing a tool such as revdep, to check for issues like this. Search LQ, however, I did not find a good solution that just works. I got advice to make my own tool, as well as, statements how people use their own "home made" tools for this. -p On Thu, 29 Feb 2024 at 18: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 dickson.tim at googlemail.com Fri Mar 1 10:16:05 2024 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 1 Mar 2024 10:16:05 +0000 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: Message-ID: <0398ccd2-6967-43f9-9ce4-591d905bca05@googlemail.com> the problem is the optional dependencies. how does a tool know which options you like. Only when such a tool which has your preferred optional deps recorded exists, can there be a way to reverse dep without missing out bits. regards, Tim On 01/03/2024 09:38, Petar Petrov wrote: > there were several discussions about Slackware needing a tool such as > revdep, to check for issues like this. Search LQ, however, I did not > find a good solution that just works. I got advice to make my own > tool, as well as, statements how people use their own "home made" > tools for this. > > -p > > On Thu, 29 Feb 2024 at 18: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/ > From slackalaxy at gmail.com Fri Mar 1 10:19:57 2024 From: slackalaxy at gmail.com (Petar Petrov) Date: Fri, 1 Mar 2024 12:19:57 +0200 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: <0398ccd2-6967-43f9-9ce4-591d905bca05@googlemail.com> References: <0398ccd2-6967-43f9-9ce4-591d905bca05@googlemail.com> Message-ID: revdep checks for broken *.so, so it would not matter whether your deps were optional or not. People running -current, who install stuff from SBo, would greatly benefit from such a tool. regards, -p On Fri, 1 Mar 2024 at 12:16, Tim Dickson via SlackBuilds-users wrote: > > the problem is the optional dependencies. how does a tool know which > options you like. > Only when such a tool which has your preferred optional deps recorded > exists, can there > be a way to reverse dep without missing out bits. > regards, Tim > > On 01/03/2024 09:38, Petar Petrov wrote: > > there were several discussions about Slackware needing a tool such as > > revdep, to check for issues like this. Search LQ, however, I did not > > find a good solution that just works. I got advice to make my own > > tool, as well as, statements how people use their own "home made" > > tools for this. > > > > -p > > > > On Thu, 29 Feb 2024 at 18: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/ > > > > _______________________________________________ > 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 Mar 1 10:28:27 2024 From: didier at slint.fr (Didier Spaier) Date: Fri, 1 Mar 2024 11:28:27 +0100 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: <0398ccd2-6967-43f9-9ce4-591d905bca05@googlemail.com> Message-ID: What about the non-binary deps (perl, python and ruby...)? Cheers, Didier Le 01/03/2024 ? 11:19, Petar Petrov a ?crit?: > revdep checks for broken *.so, so it would not matter whether your > deps were optional or not. People running -current, who install stuff > from SBo, would greatly benefit from such a tool. > > regards, > > -p > > > On Fri, 1 Mar 2024 at 12:16, Tim Dickson via SlackBuilds-users > wrote: >> >> the problem is the optional dependencies. how does a tool know which >> options you like. >> Only when such a tool which has your preferred optional deps recorded >> exists, can there >> be a way to reverse dep without missing out bits. >> regards, Tim >> >> On 01/03/2024 09:38, Petar Petrov wrote: >>> there were several discussions about Slackware needing a tool such as >>> revdep, to check for issues like this. Search LQ, however, I did not >>> find a good solution that just works. I got advice to make my own >>> tool, as well as, statements how people use their own "home made" >>> tools for this. >>> >>> -p >>> >>> On Thu, 29 Feb 2024 at 18: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 From slackalaxy at gmail.com Fri Mar 1 10:32:10 2024 From: slackalaxy at gmail.com (Petar Petrov) Date: Fri, 1 Mar 2024 12:32:10 +0200 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: <0398ccd2-6967-43f9-9ce4-591d905bca05@googlemail.com> Message-ID: what about them? Of course it won't 'catch' these. Still, checking the *.so libs is a great help. do you think that since it won't work for perl, python and ruby such tool is unneeded? -p On Fri, 1 Mar 2024 at 12:28, Didier Spaier wrote: > > What about the non-binary deps (perl, python and ruby...)? > > Cheers, > Didier > > Le 01/03/2024 ? 11:19, Petar Petrov a ?crit : > > revdep checks for broken *.so, so it would not matter whether your > > deps were optional or not. People running -current, who install stuff > > from SBo, would greatly benefit from such a tool. > > > > regards, > > > > -p > > > > > > On Fri, 1 Mar 2024 at 12:16, Tim Dickson via SlackBuilds-users > > wrote: > >> > >> the problem is the optional dependencies. how does a tool know which > >> options you like. > >> Only when such a tool which has your preferred optional deps recorded > >> exists, can there > >> be a way to reverse dep without missing out bits. > >> regards, Tim > >> > >> On 01/03/2024 09:38, Petar Petrov wrote: > >>> there were several discussions about Slackware needing a tool such as > >>> revdep, to check for issues like this. Search LQ, however, I did not > >>> find a good solution that just works. I got advice to make my own > >>> tool, as well as, statements how people use their own "home made" > >>> tools for this. > >>> > >>> -p > >>> > >>> On Thu, 29 Feb 2024 at 18: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 j at lngn.net Fri Mar 1 10:44:58 2024 From: j at lngn.net (Jay Lanagan) Date: Fri, 1 Mar 2024 05:44:58 -0500 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: <0398ccd2-6967-43f9-9ce4-591d905bca05@googlemail.com> Message-ID: <2B6161EA-27D8-420C-AA9B-D39C295E9161@edison.tech> This tool emmet1 made based on and acting like the CRUX tool of the same name is still my favorite out of Didler?s, Pat?s and others I?ve used. It?s simple and powerful and finds missing .so?s perfectly. https://gist.github.com/emmett1/eb71186ba5567be46ad34ae59ba1fa57 Of course things like Firefox/thunderbird will show up but they can be safely ignored. Everything else will be shown correctly and for .so files, it?s invaluable. ? Jay Lanagan > > On Mar 1, 2024 at 5:20 AM, wrote: > > > > revdep checks for broken *.so, so it would not matter whether your deps were optional or not. People running -current, who install stuff from SBo, would greatly benefit from such a tool. regards, -p On Fri, 1 Mar 2024 at 12:16, Tim Dickson via SlackBuilds-users wrote: > > the problem is the optional dependencies. how does a tool know which > options you like. > Only when such a tool which has your preferred optional deps recorded > exists, can there > be a way to reverse dep without missing out bits. > regards, Tim > > On 01/03/2024 09:38, Petar Petrov wrote: > > there were several discussions about Slackware needing a tool such as > > revdep, to check for issues like this. Search LQ, however, I did not > > find a good solution that just works. I got advice to make my own > > tool, as well as, statements how people use their own "home made" > > tools for this. > > > > -p > > > > On Thu, 29 Feb 2024 at 18: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/ > > > > _______________________________________________ > 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 didier at slint.fr Fri Mar 1 10:49:33 2024 From: didier at slint.fr (Didier Spaier) Date: Fri, 1 Mar 2024 11:49:33 +0100 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: <0398ccd2-6967-43f9-9ce4-591d905bca05@googlemail.com> Message-ID: Hi, Le 01/03/2024 ? 11:32, Petar Petrov a ?crit?: > what about them? Of course it won't 'catch' these. Still, checking the > *.so libs is a great help. > > do you think that since it won't work for perl, python and ruby such > tool is unneeded? > > -p No, I don't. But.. Things would be so much simpler if Slackware packages' metadata included their dependencies, as other distributions do. Back to my rabbit hole. Didier > On Fri, 1 Mar 2024 at 12:28, Didier Spaier wrote: >> >> What about the non-binary deps (perl, python and ruby...)? >> >> Cheers, >> Didier >> >> Le 01/03/2024 ? 11:19, Petar Petrov a ?crit : >>> revdep checks for broken *.so, so it would not matter whether your >>> deps were optional or not. People running -current, who install stuff >>> from SBo, would greatly benefit from such a tool. >>> >>> regards, >>> >>> -p From dchmelik at gmail.com Fri Mar 1 11:00:16 2024 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Fri, 1 Mar 2024 03:00:16 -0800 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: Message-ID: <780c881c-567e-dcec-3b31-9137382b1026@gmail.com> On 2/29/24 8: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? [...] What about depfinder by Salix? From slackalaxy at gmail.com Fri Mar 1 11:06:10 2024 From: slackalaxy at gmail.com (Petar Petrov) Date: Fri, 1 Mar 2024 13:06:10 +0200 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: <2B6161EA-27D8-420C-AA9B-D39C295E9161@edison.tech> References: <0398ccd2-6967-43f9-9ce4-591d905bca05@googlemail.com> <2B6161EA-27D8-420C-AA9B-D39C295E9161@edison.tech> Message-ID: yes, i am aware of that. the problem is that, unlike CRUX's revdep, this does not have a /etc/revdep.d where to store files indicating libraries in custom places, package wise. So, if I want to maintain a binary repackaging script, Emmets' revdep for Slackware will not report what such package is missing. anyway. That's beating a deadhorse as already wisely stated and i am fully aware nothing will change -p On Fri, 1 Mar 2024 at 12:45, Jay Lanagan via SlackBuilds-users wrote: > > This tool emmet1 made based on and acting like the CRUX tool of the same name is still my favorite out of Didler?s, Pat?s and others I?ve used. It?s simple and powerful and finds missing .so?s perfectly. > > https://gist.github.com/emmett1/eb71186ba5567be46ad34ae59ba1fa57 > > Of course things like Firefox/thunderbird will show up but they can be safely ignored. Everything else will be shown correctly and for .so files, it?s invaluable. > > ? Jay Lanagan > > > On Mar 1, 2024 at 5:20 AM, wrote: > From erich.public at protonmail.com Fri Mar 1 14:20:32 2024 From: erich.public at protonmail.com (Erich Ritz) Date: Fri, 01 Mar 2024 14:20:32 +0000 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: <0398ccd2-6967-43f9-9ce4-591d905bca05@googlemail.com> References: <0398ccd2-6967-43f9-9ce4-591d905bca05@googlemail.com> Message-ID: On Friday, March 1st, 2024 at 4:16 AM, Tim Dickson via SlackBuilds-users wrote: > > > the problem is the optional dependencies. how does a tool know which > options you like. > Only when such a tool which has your preferred optional deps recorded > exists, can there > be a way to reverse dep without missing out bits. > regards, Tim > As already mentioned, slackrepo handles this. Optional deps are stored in hintfiles: $ cat /var/lib/slackrepo/etr/hintfiles/vlc.hint ADDREQUIRES="dav1d" You can even replace deps with other deps (e.g. use OpenBLAS instead of blas and lapack for octave): $ cat /var/lib/slackrepo/etr/hintfiles/blas.hint SKIP="Use OpenBLAS instead" $ cat /var/lib/slackrepo/etr/hintfiles/lapack.hint SKIP="Use OpenBLAS instead" $ cat /var/lib/slackrepo/etr/hintfiles/octave.hint DELREQUIRES="lapack" ADDREQUIRES="OpenBLAS suitesparse glpk arpack-ng qrupdate sundials qhull hdf5 fltk ftgl gl2ps GraphicsMagick portaudio rapidjson zulu-openjdk21" So when using slackrepo if blas has an update from SBo nothing will happen on my end (since nothing depends on blas). An upgrade of OpenBLAS will trigger octave to be rebuilt. Note: since required dependencies are not listed in hintfiles (they are already present in *.info), I also maintain a set of sbopkg queue files (which list both required and optional deps) so I can quickly grep for dependencies, though I rarely need to do so. Most often I use it when removing a package and then removing all of its deps that aren't used by other programs I have installed. After every public update I run (in a clean chroot); slackrepo update --preview to first review what will be rebuilt, taking note of any new optional deps I may want to add (rare). Then: slackrepo update This builds everything that needs an upgrade or rebuild. Erich From alik at ejik.org Fri Mar 1 14:42:56 2024 From: alik at ejik.org (Alexander Verbovetsky) Date: Fri, 1 Mar 2024 17:42:56 +0300 Subject: [Slackbuilds-users] Some abandoned SlackBuilds In-Reply-To: References: Message-ID: On Sat, Apr 22, 2023 at 09:33:58AM -0500, Konrad J Hambrick wrote: > On Sat, Apr 22, 2023 at 8:50?AM Alexander Verbovetsky > wrote: > > > On Sat, Apr 22, 2023 at 08:11:52AM -0500, Konrad J Hambrick wrote: > > > > However, rabbitmq-server-3.11.13 and rabbitmq-c-0.13.0 require > > > erlang-otp-25.3 and elixir-1.14.4 to build. > > > > And then ejabberd depends on erlang-otp which is maintained by > > > Alexander Verbovetsky ( also copied here ). > > > Are there any issues with the erlang-otp and elixr updates ? > > > Ejabberd will be happy with this update. > > Thanks Alexander. > I'll continue testing and let the list know when I have something :) Is there any news? In fact, without the update, Ejabber is a bit unhappy :-) rebar3 binaries included with ejabberd requires Erlang 24+ I plan to workaround this by providing a Slackbuild for rebar3, but even so, I think it would be a good idea to move to Erlang 25 or 26, unless there's a good reason to stay with Erlang 23. Also, Ejabberd can be used with Elixir, and in this case the documentation highly recommend to use Elixir 1.13.4 or higher. Best regards, Alexander From arnaud.garcia-fernandez at laposte.net Fri Mar 1 14:47:38 2024 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Fri, 1 Mar 2024 15:47:38 +0100 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: <35779813-952E-4E08-B804-F2F10F000DDD@laposte.net> Message-ID: <20240301154738.fdbbf8eea3086a7c684abd86@laposte.net> > > 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. So I've looked again, and sbbdep is quite useful. So my libheif is built with dav1d, but not my VLC. And then : $ hoorex -i dav1d dav1d libheif $ sbbdep --whoneeds /var/log/packages/dav1d-1.4.0-x86_64-1yth dav1d-1.4.0-x86_64-1yth libheif-1.17.6-x86_64-1yth Which returns what is relevant. Then I rebuilt VLC, which might probably have been built without dav1d. And then : $ sbbdep --whoneeds /var/log/packages/dav1d-1.4.0-x86_64-1yth dav1d-1.4.0-x86_64-1yth libheif-1.17.6-x86_64-1yth vlc-3.0.20-x86_64-1yth So it does work, for binary dependencies. I know that either libheif or vlc could require rebuilding after an update of dav1d. To be noted : I haven't tested building vlc with libdav1d.so.6, then updating dav1d to libdav1d.so.7, and asking sbbdep. It might fail, because the link is broken, vlc wouldn't show a link to dav1d since it doesn't link to libdav1d.so.7 But, you could update sbbdep database before an update, and ask without updating the sbbdep database. Let's say, it might not be perfect, and may require something on top of it, to detect, through comparison of dependencies before and after an update, what links may have been severed. As I said, I didn't test such a situation. For perl and python (and haskell, and... maybe other), it's less problematic, since most dependencies are SBo-related, hence we have a dependency tree available. That would be more True on stable 15.0 where python/perl and system modules aren't very updated, but could be pretty wrong on -current. - Yth. From willysr at slackbuilds.org Fri Mar 1 19:35:09 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 2 Mar 2024 02:35:09 +0700 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 Message-ID: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> Hi i have just started to work on protobuf3 updates, pushing 2y of works by upstream since last update. However, there are 26 other scripts which depends on protobuf3, listed here (https://slackbuilds.org/advsearch.php?q=protobuf3&stype=revdep1) although we do have CI engine that could help us test whether the new update will break them or not, it won't help us testing the runtime issues. Therefore, i would like to ask for help by those who are using these 26 packages to see if by upgrading protobuf3 and rebuilding them will have any runtime issues or not. I will keep the protobuf3 updates for future public update (like 1-2 weeks delay) to give others more time to test. The protobuf3 update can be seen here https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip Big thanks in advance -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Mar 2 02:28:20 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 2 Mar 2024 09:28:20 +0700 Subject: [Slackbuilds-users] Updates - 20240302.1 Message-ID: <528de5b4-e144-4331-be1d-0109ff61d72d@slackbuilds.org> Sat Mar 2 02:20:27 UTC 2024 academic/cdo: Updated for version 2.4.0. academic/fet: Updated for version 6.18.0. audio/aeolus: Fix download, md5sum, icon, docs. audio/clxclient: update script. audio/spectmorph: New maintainer, PDF manual. audio/yoshimi: Updated for version 2.3.2. business/ledger: Updated for version 3.3.2. desktop/dunst: Updated for version 1.10.0 desktop/mate-terminal: Updated for version 1.28.1. desktop/menulibre: Updated for version 2.4.0. desktop/nwg-panel: Updated for version 0.9.25. desktop/nwg-readme-browser: Updated for version 0.1.5. desktop/nwg-shell-wallpapers: Updated for version 1.5. desktop/python3-autotiling: Updated for version 1.9.1. desktop/rofi-emoji: Updated for version 3.3.0. desktop/wofi-pass: Added (Wayland-native interface). desktop/wofi: Updated for version 1.4.1. desktop/wtype: Added (xdotool type for wayland). development/actionlint: Updated for version 1.6.27. development/geany-plugins: Updated for version 2.0. development/geany: Updated for version 2.0. development/hugo: update 0.123.3 development/jupyter-ipykernel: Update for 6.29.3 development/kicad: Updated for version 8.0. development/mold: Updated for version 2.4.1. development/neovim: update dep. development/obsidian: Updated for version 1.5.8. development/pahole: Updated for version 1.26. development/postman: Updated for version 10.23.5 development/pycharm: Updated for version 2023.3.4.233.14475.56. development/python3-spyder-kernels: Update for 2.5.1 development/rebar3: Added (erlang build tool). development/rizin: Updated for version 0.7.0 development/terraform: Updated for version 1.7.4 development/vile: update to 9.8z development/vscode-bin: Updated for version 1.87.0. development/wxFormBuilder: Update for version 4.1.0 development/xmake: Updated for version 2.8.7. development/xvile: update to 9.8z games/LucasChess: Fix download, doc perms, CWD write. games/dustrac: updated for version 2.1.1. New maintainer games/freeciv: updated for version 3.1.0 games/open-adventure: Upstream changed tarball; fix md5sum. games/stockfish: Updated for version 16.1. games/supertuxkart: Fix compiling with gcc13 games/wolfmame: Updated for version 0.263. gis/eccodes: Updated for version 2.34.1. gis/gpxsee: Updated for version 13.16. graphics/ueberzugpp: Updated for version 2.9.4. graphics/vuescan: Updated for version 9.8.28. libraries/canfigger: Update dependency. libraries/libkml: fixed outdated libkml build libraries/libstrophe: Updated for version 0.13.1. libraries/libtermkey: New maintainer. libraries/libvterm: Updated for version 0.3.3. libraries/lua-lpeg: Updated for version 1.1.0. libraries/python3-rpyc: Updated for version 6.0.0. libraries/unibilium: New maintainer. misc/open-simh: Fix permission. network/brave-browser: update 1.63.162 network/coturn: Update script. network/darkhttpd: updated for version 1.16 network/dnsproxy-bin: Updated for version 0.65.2. network/gallery-dl: Updated for version 1.26.8. network/haproxy: Updated for version 2.8.7. network/nextcloud-desktop: update 3.12.0 network/nicotine+: Updated for version 3.3.2. network/opera: Updated for version 107.0.5045.36. network/profanity: Updated for version 0.14.0. network/protonvpn-cli: Updated for version 2.2.12. network/qbittorrent: Updated for version 4.6.3. network/rclone: update 1.65.2 network/signal-desktop: Updated for version 7.0.0. network/tailscale: update 1.60.0 network/teamviewer: Updated for version 15.51.5. network/vivaldi: Updated for version 6.6.3271.45. network/whalebird: Updated for version 6.0.2. network/zoom-linux: Updated for version 5.17.10.3512 office/asymptote: Updated for version 2.87. office/calibre-bin: Updated for version 7.6.0. office/goldendict: Updated for version 1.5.0. office/grisbi: updated for version 3.1.0 office/onlyoffice-desktopeditors: Updated for version 8.0.1. office/pandoc-bin: update 3.1.12.1 perl/perl-Crypt-OpenSSL-Bignum: Adjust doc file permissions. perl/perl-Crypt-OpenSSL-Bignum: Updated for version 0.09. perl/perl-Crypt-OpenSSL-Guess: Updated for version 0.15. perl/perl-Crypt-OpenSSL-RSA: Updated for version 0.33. perl/perl-Expect: Updated for version 1.36. perl/perl-digest-hmac: Updated for version 1.04. python/argon2-cffi: Update for 23.1.0 python/certbot-dns-cloudflare: Updated for version 2.9.0 python/nest_asyncio: Update for 1.6.0 python/pipdeptree: Updated for version 2.15.1. python/pyinotify: New maintainer, remove Python 2 support python/python3-anyio: Remove python3-setuptools-scm-opt from DEPs python/python3-cachetools: Version bump to 5.3.3 python/python3-cloudflare: Updated for version 2.19.2 python/python3-compreffor: Updated for version 0.5.5. python/python3-dateutil: updated for version 2.9.0 python/python3-fontmake: Updated for version 3.8.1. python/python3-fonttools: Updated for version 4.49.0. python/python3-glyphslib: Updated for version 6.6.5. python/python3-identify: Updated for version 2.5.35. python/python3-json5: Add missing dep. python/python3-keyring: Update for 24.3.1 python/python3-neovim: Updated for version 0.5.0. python/python3-openstep-plist: Updated for version 0.3.1. python/python3-orjson: Updated for version 3.9.15. python/python3-pdm: Version bump to 2.12.4 python/python3-pooch: Version bump to 1.8.1 python/python3-pydantic: Updated for version 2.6.2. python/python3-pykeepass: Update for 4.0.7 python/python3-pytest: Version bump to 8.0.2 python/python3-setuptools-opt: Updated for version 69.1.1. python/python3-setuptools-rust-opt: Updated for version 1.9.0. python/python3-sniffio: Update for 1.3.1 python/python3-tomlkit: Update for 0.12.4 python/python3-trio: Remove python3-setuptools-scm-opt from DEPs python/python3-trove-classifiers: Updated for version 2024.2.23. python/python3-ufo2ft: Updated for version 3.1.0. python/python3-ufolib2: Updated for version 0.16.0. python/python3-uharfbuzz: Updated for version 0.39.0. python/sphinxcontrib-applehelp: Updated for version 1.0.8. python/sphinxcontrib-devhelp: Updated for version 1.0.6. python/sphinxcontrib-htmlhelp: Updated for version 2.0.5. python/sphinxcontrib-qthelp: Updated for version 1.0.7. python/sphinxcontrib-serializinghtml: Updated for version 1.1.10. system/FreeFileSync: Fix permission. system/FreeFileSync: Updated for version 13.4. system/arqiver: New Maintainer system/barman: Fix md5sum. system/capstone: Updated for version 4.0.2. system/conky: Updated for version 1.19.8. system/distrobox: Updated for version 1.7.0. system/fastfetch: Updated for version 2.8.6. system/fcron: Update script. system/greetd: Fixed SlackBuild $PRINT_PACKAGE_NAME. system/hw-probe: Updated for version 1.6. system/jq: Update for 1.7.1 (+new maintainer) system/libsignal-protocol-c: Update script. system/loksh: Remove unwanted man page. system/mongodb: Updated for version 7.0.6. system/musl: Updated for version 1.2.5. system/pass-import: Update for 3.5 system/pledge: New maintainer, minor fixes. system/redis-py: updated for version 5.0.2 system/s3fs-fuse: Updated for version 1.94. system/sane-airscan: Updated for version 0.99.29. system/slackrepo: Updated for version 20240302. system/slackroll: Updated for version v54. system/telegraf: Updated for version 1.29.5 system/upx: Updated for version 4.2.2. system/warp-terminal: Added (warp terminal). system/xprintidle: New maintainer, minor fixes. system/yq: Updated for version 4.42.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From z.coldplayer at gmail.com Sat Mar 2 09:58:31 2024 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Sat, 2 Mar 2024 13:58:31 +0400 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: Message-ID: sqg -p dav1d On Thu, 29 Feb 2024 at 20: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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sb at rbn.im Sat Mar 2 12:37:13 2024 From: sb at rbn.im (Ruben Schuller) Date: Sat, 2 Mar 2024 13:37:13 +0100 Subject: [Slackbuilds-users] spring cleaning some packages In-Reply-To: References: <20240229123951.6b8ca5e8@kiwi.kuchen> Message-ID: <20240302133713.10a37908@kiwi.kuchen> Hi, sorry for the late answer, was a bit sick this week. 2024-02-29 Alexander Verbovetsky : > I can take four neovim dependencies: > > libtermkey > libvterm > lua-lpeg > unibilium > > (lua-mpack dependency is going to be dropped) Much appreciated! Cheers Ruben From jebrhansen+SBo at gmail.com Sat Mar 2 17:26:20 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 2 Mar 2024 09:26:20 -0800 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: References: Message-ID: This would only show dependencies of dav1d. It wouldn't show any packages that depend on dav1d (unless there was a circular dependency), so it wouldn't help find things that would be broken. You could grep all the queue files for dav1d, but that would only show the packages that had it as a hard dependency. Several will add support if dav1d is found on the system (like VLC) without needing to specify it on the REQUIRES line in the .info. It's certainly one benefit of building in a clean system to prevent picking accidental dependencies (which slackrepo does very well when set up properly). Jeremy On Sat, Mar 2, 2024, 1:59?AM Jheengut Pritvi wrote: > sqg -p dav1d > > On Thu, 29 Feb 2024 at 20: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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slack at giand.it Sat Mar 2 21:10:31 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Sat, 2 Mar 2024 22:10:31 +0100 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 In-Reply-To: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> References: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> Message-ID: <45ae0ae9-d1b0-4952-adf8-ae52ce905d00@giand.it> Il 01/03/24 20:35, Willy Sudiarto Raharjo ha scritto: > Hi > > i have just started to work on protobuf3 updates, pushing 2y of works > by upstream since last update. > > However, there are 26 other scripts which depends on protobuf3, listed > here (https://slackbuilds.org/advsearch.php?q=protobuf3&stype=revdep1) > > although we do have CI engine that could help us test whether the new > update will break them or not, it won't help us testing the runtime > issues. Therefore, i would like to ask for help by those who are using > these 26 packages to see if by upgrading protobuf3 and rebuilding them > will have any runtime issues or not. > > I will keep the protobuf3 updates for future public update (like 1-2 > weeks delay) to give others more time to test. > > The protobuf3 update can be seen here > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > > Big thanks in advance > At the moment I tested new protobuf3 in -current, it works for protobuf-c/postgis and qgis After upgrade of protobuf3 the entire tree until qgis was broken, I had to rebuild protobuf-c and then postgis and finally qgis because protobuf is required as first level dependency also by qgis -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From willysr at slackbuilds.org Sun Mar 3 01:14:52 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 3 Mar 2024 08:14:52 +0700 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 In-Reply-To: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> References: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> Message-ID: > i have just started to work on protobuf3 updates, pushing 2y of works by > upstream since last update. > > However, there are 26 other scripts which depends on protobuf3, listed > here (https://slackbuilds.org/advsearch.php?q=protobuf3&stype=revdep1) > > although we do have CI engine that could help us test whether the new > update will break them or not, it won't help us testing the runtime > issues. Therefore, i would like to ask for help by those who are using > these 26 packages to see if by upgrading protobuf3 and rebuilding them > will have any runtime issues or not. > > I will keep the protobuf3 updates for future public update (like 1-2 > weeks delay) to give others more time to test. > > The protobuf3 update can be seen here > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip I did some checkings and the results are recorded here https://github.com/SlackBuildsOrg/slackbuilds/pull/5281 Some of those got fixed and applied to my branch for trivial changes and protobuf3-wip for protobuf3-related changes https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip the one i have been strugling with are ola and pokerth if anyone can help, that would be much appreciated -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Mar 3 04:31:14 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 3 Mar 2024 11:31:14 +0700 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 In-Reply-To: References: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> Message-ID: <2e917cd9-0299-43db-b48c-90fbaf8d8a12@slackbuilds.org> >> The protobuf3 update can be seen here >> https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > > I did some checkings and the results are recorded here > https://github.com/SlackBuildsOrg/slackbuilds/pull/5281 > > Some of those got fixed and applied to my branch for trivial changes and > protobuf3-wip for protobuf3-related changes > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > > the one i have been strugling with are ola and pokerth > if anyone can help, that would be much appreciated here are the final list of scripts that don't work with new protobuf3 development/ola games/pokerth libraries/grpc libraries/ignition-transport python/python3-grpcio -- 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 heiko.rosemann at web.de Sun Mar 3 21:26:56 2024 From: heiko.rosemann at web.de (Heiko Rosemann) Date: Sun, 3 Mar 2024 22:26:56 +0100 Subject: [Slackbuilds-users] Updates - 20240302.1 In-Reply-To: <528de5b4-e144-4331-be1d-0109ff61d72d@slackbuilds.org> References: <528de5b4-e144-4331-be1d-0109ff61d72d@slackbuilds.org> Message-ID: Thank you, Willy and everyone! On 3/2/24 03:28, Willy Sudiarto Raharjo wrote: > development/kicad: Updated for version 8.0. I get a checksum mismatch for the kicad source. Is that a mistake on our end or did the kicad or gitlab people change the download file? 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 willysr at slackbuilds.org Sun Mar 3 23:52:55 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 4 Mar 2024 06:52:55 +0700 Subject: [Slackbuilds-users] Updates - 20240302.1 In-Reply-To: References: <528de5b4-e144-4331-be1d-0109ff61d72d@slackbuilds.org> Message-ID: <3be85c7b-23ad-435f-93d4-e870371105b8@slackbuilds.org> > Thank you, Willy and everyone! > > On 3/2/24 03:28, Willy Sudiarto Raharjo wrote: >> development/kicad: Updated for version 8.0. > > I get a checksum mismatch for the kicad source. Is that a mistake on our > end or did the kicad or gitlab people change the download file? I think they always regenerates the tarball so it always get mismatch checksums. I happened that many times in CI -- 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 list+sbo at vahedi.org Mon Mar 4 11:54:05 2024 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Mon, 4 Mar 2024 12:54:05 +0100 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: Message-ID: <92cde1b9-d2c2-4cb4-9933-6311c42b9904@vahedi.org> Jim, Would a script like the one at the bottom of this email point you toward the right package(s)? I have to warn you it roughly took 11 minutes to finish on my laptop with 1680 packages installed: $ time ./depcheck libacl.so acl-2.3.2-x86_64-1: /usr/bin/chacl cdrtools-3.02a09-x86_64-1: /usr/bin/isoinfo coreutils-9.4-x86_64-1: /bin/cp ... vim-gvim-9.1.0136-x86_64-1: /usr/bin/gvim xorriso-1.5.6.pl02-x86_64-1: /usr/bin/xorriso real 11m16.558s ... ----------------------------------8<------------------------------------ #! /bin/bash - # depcheck -- List Slackware packages that directly rely on a library. # shellcheck disable=SC2312 readonly lib="$1" sanity_check() { if test -z "${lib}" then echo -e "\nProvide one library name as an argument. Example:\n" echo " $ $0 libacl.so" exit 1 fi if ! command -v "parallel" > /dev/null 2>&1 then echo "GNU Parallel is necessary for this tool." exit 1 fi } process_package() { _lib="$1" _pkg="$2" grep -e '^[^ ]\+/.\+' "${_pkg}" | while read -r fl do fl="/${fl}" if test -f "${fl}" && file --brief --mime-type "${fl}" | grep -q "x-executable\|x-sharedlib" then if readelf -d "${fl}" 2>/dev/null | grep -i -q "shared library: \[${_lib}" then echo "${_pkg##*/}: ${fl}" # no need to go through other files of this package break fi fi done } export -f process_package sanity_check SHELL=$(type -p bash) find /var/lib/pkgtools/packages -type f | sort | parallel process_package "${lib}" ----------------------------------8<------------------------------------ Cheers, Shahab From jdashiel at panix.com Mon Mar 4 12:19:02 2024 From: jdashiel at panix.com (Jude DaShiell) Date: Mon, 4 Mar 2024 07:19:02 -0500 Subject: [Slackbuilds-users] tracking down missing sbo dependencies Message-ID: I found the glktermw package had at least one missing dependency so ended up building glkterm directly from git packages outside of slackware and outside of slackbuilds. Does this routinely happen when scripts on slackbuilds could have been written better so those dependencies get pulled in and compiled? I think that glktermw package is meant for graphical user environment not necessarily text user interfaces. Now I already have glkterm working here, I could download glktermw and see if it will build and if it can work in text user interface. -- Jude "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. From jdashiel at panix.com Mon Mar 4 12:26:22 2024 From: jdashiel at panix.com (Jude DaShiell) Date: Mon, 4 Mar 2024 07:26:22 -0500 Subject: [Slackbuilds-users] tracking down missing sbo dependencies In-Reply-To: References: Message-ID: <388d967f-8416-b38e-5e02-78f2fef0eeb7@panix.com> It turns out glktermw is for unicode wide character support but didn't make glulxe so far as I can tell. The out of slackbuilds made that for me and installed it in /usr/local/bin. -- Jude "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Mon, 4 Mar 2024, Jude DaShiell wrote: > I found the glktermw package had at least one missing dependency so ended > up building glkterm directly from git packages outside of slackware and > outside of slackbuilds. Does this routinely happen when scripts on > slackbuilds could have been written better so those dependencies get > pulled in and compiled? > I think that glktermw package is meant for graphical user environment not > necessarily text user interfaces. Now I already have glkterm working > here, I could download glktermw and see if it will build and if it can > work in text user interface. > > > -- > Jude > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. > Please use in that order." > Ed Howdershelt 1940. > _______________________________________________ > 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 list+sbo at vahedi.org Mon Mar 4 14:02:36 2024 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Mon, 4 Mar 2024 15:02:36 +0100 Subject: [Slackbuilds-users] tracking down SBo "dependencies" In-Reply-To: <92cde1b9-d2c2-4cb4-9933-6311c42b9904@vahedi.org> References: <92cde1b9-d2c2-4cb4-9933-6311c42b9904@vahedi.org> Message-ID: > $ time ./depcheck libacl.so > ... > real 11m16.558s For the record, I just managed to make it 3 times faster by using "xxd" instead of "file", skipping "-noarch-" packages, etc. $ time ./depcheck libacl.so ... real 3m49.661s However, I won't pollute the mailing list with the new version, unless it is deemed needed. Most likely, it is easily possible to modify this script to look for any missing library that an executable or shared library of a package may need. Cheers, Shahab From urchlay at slackware.uk Mon Mar 4 18:53:02 2024 From: urchlay at slackware.uk (B. Watson) Date: Mon, 4 Mar 2024 13:53:02 -0500 (EST) Subject: [Slackbuilds-users] tracking down missing sbo dependencies In-Reply-To: References: Message-ID: On Mon, 4 Mar 2024, Jude DaShiell wrote: > I found the glktermw package had at least one missing dependency so ended > up building glkterm directly from git packages outside of slackware and > outside of slackbuilds What dependency is missing? It builds on a clean full install of 15.0, and it works when fizmo is built with glktermw installed: I get a fizmo-glktermw executable, which works (I'm playing Zork in it now). Looking at glktermw's Makefile, the only dependency I see is libncursesw, which is in a full Slackware install. What did you mean by "at least one missing dependency"? What problems did you have building glktermw with the SBo script? Can you post the full log (stdout and stderr) of the build? > Does this routinely happen when scripts on > slackbuilds could have been written better so those dependencies get > pulled in and compiled? No, broken builds do not routinely happen. If they do, they get fixed ASAP... which is why I want to see your build log: if something's wrong with my build, I want to fix it. If you're using -current rather than 15.0, well, SBo only supports 15.0 (or whatever the latest stable is). Still, if there's a way to fix it so it works on -current, I'll go ahead & do that if I can. > I think that glktermw package is meant for graphical user environment not > necessarily text user interfaces. Now I already have glkterm working > here, I could download glktermw and see if it will build and if it can > work in text user interface. fizmo-glktermw is definitely a text user interface. It runs in a terminal. Also, glktermw's own readme.txt says: GlkTerm: Curses.h Implementation of the Glk API. ... This is source code for an implementation of the Glk library which runs in a terminal window, using the curses.h library for screen control. Curses definitely means terminal, not GUI. fizmo is actually the only thing on SBo that uses glktermw. I don't know any other applications that use it... what are you using when you say you have it "working here"? From urchlay at slackware.uk Mon Mar 4 19:38:34 2024 From: urchlay at slackware.uk (B. Watson) Date: Mon, 4 Mar 2024 14:38:34 -0500 (EST) Subject: [Slackbuilds-users] tracking down missing sbo dependencies In-Reply-To: <388d967f-8416-b38e-5e02-78f2fef0eeb7@panix.com> References: <388d967f-8416-b38e-5e02-78f2fef0eeb7@panix.com> Message-ID: <83ddd34a-d951-8449-2f46-ae89cea0f753@slackware.uk> On Mon, 4 Mar 2024, Jude DaShiell wrote: > It turns out glktermw is for unicode wide character support but didn't > make glulxe so far as I can tell. The out of slackbuilds made that for me > and installed it in /usr/local/bin. glulxe isn't included in glktermw at all, the only mention of it is in in readme-widechar.txt... What source were you building that gave you a glulxe binary? I might want to add it to SBo... I thought it might be https://github.com/erkyrath/glkterm but that doesn't have glulxe either (it looks like the non-wide-char version of glktermw). From didier at slint.fr Mon Mar 4 20:30:17 2024 From: didier at slint.fr (Didier Spaier) Date: Mon, 4 Mar 2024 21:30:17 +0100 Subject: [Slackbuilds-users] tracking down missing sbo dependencies In-Reply-To: <83ddd34a-d951-8449-2f46-ae89cea0f753@slackware.uk> References: <388d967f-8416-b38e-5e02-78f2fef0eeb7@panix.com> <83ddd34a-d951-8449-2f46-ae89cea0f753@slackware.uk> Message-ID: <62632775-c40e-4086-9b0d-cc852a7b2572@slint.fr> Le 04/03/2024 ? 20:38, B. Watson a ?crit?: > > > On Mon, 4 Mar 2024, Jude DaShiell wrote: > >> It turns out glktermw is for unicode wide character support but didn't >> make glulxe so far as I can tell.? The out of slackbuilds made that for me >> and installed it in /usr/local/bin. > > glulxe isn't included in glktermw at all, the only mention of it is in > in readme-widechar.txt... What source were you building that gave you > a glulxe binary? I might want to add it to SBo... > > I thought it might be https://github.com/erkyrath/glkterm but that > doesn't have glulxe either (it looks like the non-wide-char version > of glktermw). Isn't it this one? https://github.com/erkyrath/glulxe Also, Jude uses Slint but there is no issue building glktermw there, using slapt-src for instance. A prebuilt package can also installed using slapt-get, but I digress. So, Jude: maybe you thought that glktermw depended on glkterm? But this is not the case as B. Watson pointed out. To sum it up, gkterm, glktemrw and glulxe are all stand-alone software. Cheers, Didier From urchlay at slackware.uk Mon Mar 4 20:47:36 2024 From: urchlay at slackware.uk (B. Watson) Date: Mon, 4 Mar 2024 15:47:36 -0500 (EST) Subject: [Slackbuilds-users] tracking down missing sbo dependencies In-Reply-To: <62632775-c40e-4086-9b0d-cc852a7b2572@slint.fr> References: <388d967f-8416-b38e-5e02-78f2fef0eeb7@panix.com> <83ddd34a-d951-8449-2f46-ae89cea0f753@slackware.uk> <62632775-c40e-4086-9b0d-cc852a7b2572@slint.fr> Message-ID: <4d88d32f-5f9f-4be2-7c1e-2c5570b09e9f@slackware.uk> On Mon, 4 Mar 2024, Didier Spaier wrote: > To sum it up, gkterm, glktemrw and glulxe are all stand-alone software. Close. Actually, on further research, I've found that glulxe isn't standalone: it depends on having a glk implementation. Which can be either glkterm or glktermw. So Jude got the relationship backwards, glktermw doesn't have glulxe as a dependency, it *is* a dependency of glulxe. Now that I've worked out the relationship between them, I'll be submitting glulxe to SBo, with REQUIRES="glktermw". Jude, you can build glulxe with my glktermw package with a command like: make OPTIONS="-DOS_UNIX -DUNIX_RAND_GETRANDOM" \ GLKINCLUDEDIR=/usr/include/glktermw \ GLKLIBDIR=/usr/lib64 \ GLKMAKEFILE=Make.glktermw I haven't tested it thoroughly yet, but it at least will load up Advent.ulx from the glulxe homepage, here: https://www.eblong.com/zarf/glulx/ ...or, wait 5 days or so and glulxe will be on SBo. From jebrhansen+SBo at gmail.com Tue Mar 5 05:27:25 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Mon, 4 Mar 2024 21:27:25 -0800 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 In-Reply-To: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> References: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> Message-ID: On Fri, Mar 1, 2024 at 11:35?AM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Hi > > i have just started to work on protobuf3 updates, pushing 2y of works by > upstream since last update. > > However, there are 26 other scripts which depends on protobuf3, listed > here (https://slackbuilds.org/advsearch.php?q=protobuf3&stype=revdep1) > > although we do have CI engine that could help us test whether the new > update will break them or not, it won't help us testing the runtime > issues. Therefore, i would like to ask for help by those who are using > these 26 packages to see if by upgrading protobuf3 and rebuilding them > will have any runtime issues or not. > > I will keep the protobuf3 updates for future public update (like 1-2 > weeks delay) to give others more time to test. > > The protobuf3 update can be seen here > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > > Big thanks in advance > audio/clementine requires a minor update. PR is available below. Update works with both current and upgraded protobuf3, so the change is able to be merged immediately, whether or not protobuf3 is updated. https://github.com/SlackBuildsOrg/slackbuilds/pull/5353 Let me know if you have any questions! Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Tue Mar 5 05:29:21 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Mon, 4 Mar 2024 21:29:21 -0800 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 In-Reply-To: References: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> Message-ID: On Mon, Mar 4, 2024 at 9:27?PM Jeremy Hansen wrote: > On Fri, Mar 1, 2024 at 11:35?AM Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> Hi >> >> i have just started to work on protobuf3 updates, pushing 2y of works by >> upstream since last update. >> >> However, there are 26 other scripts which depends on protobuf3, listed >> here (https://slackbuilds.org/advsearch.php?q=protobuf3&stype=revdep1) >> >> although we do have CI engine that could help us test whether the new >> update will break them or not, it won't help us testing the runtime >> issues. Therefore, i would like to ask for help by those who are using >> these 26 packages to see if by upgrading protobuf3 and rebuilding them >> will have any runtime issues or not. >> >> I will keep the protobuf3 updates for future public update (like 1-2 >> weeks delay) to give others more time to test. >> >> The protobuf3 update can be seen here >> https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip >> >> Big thanks in advance >> > > audio/clementine requires a minor update. PR is available below. Update > works with both current and upgraded protobuf3, so the change is able to be > merged immediately, whether or not protobuf3 is updated. > > https://github.com/SlackBuildsOrg/slackbuilds/pull/5353 > > Let me know if you have any questions! > > Jeremy > Ooops.... :| Disregard... you already did the fix I found :D I'll close the PR. I should've read the entire email. Sorry for the noise! Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrzej at telszewski.com Fri Mar 8 13:24:54 2024 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Fri, 8 Mar 2024 14:24:54 +0100 Subject: [Slackbuilds-users] audacity fails to build if wxWidgets is built with STL=yes Message-ID: <80a6fcd2-356f-4181-93fd-fb4f0068c184@telszewski.com> Hi, it turns out that _audacity_ fails to build if _wxWidgets_ is built with `STL=yes`. The error is: ``` error: cannot convert ?wxString? to ?const char*? ``` Maybe add a note in the wxWidgets' README about that? Bcc'd maintainer. :-) -- Best regards, Andrzej Telszewski From andrzej at telszewski.com Fri Mar 8 23:51:54 2024 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Sat, 9 Mar 2024 00:51:54 +0100 Subject: [Slackbuilds-users] android-tools requires google-go-lang? Message-ID: <7881bed8-f873-42db-8cb0-7f7be7ffeb53@telszewski.com> Hi, in order to build _android-tools_ I needed to install _google-go-lang_, but it's not in `REQUIRES`. Isn't that incorrect? Bcc'd maintainer. -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Fri Mar 8 23:55:58 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 Mar 2024 06:55:58 +0700 Subject: [Slackbuilds-users] audacity fails to build if wxWidgets is built with STL=yes In-Reply-To: <80a6fcd2-356f-4181-93fd-fb4f0068c184@telszewski.com> References: <80a6fcd2-356f-4181-93fd-fb4f0068c184@telszewski.com> Message-ID: <5defc967-99e1-451d-95de-df86225d507c@slackbuilds.org> > it turns out that _audacity_ fails to build if _wxWidgets_ is built with > `STL=yes`. > > The error is: > > ``` > error: cannot convert ?wxString? to ?const char*? > ``` > > Maybe add a note in the wxWidgets' README about that? a note in audacity is probably the correct action -- 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 andrew.clemons at gmail.com Sat Mar 9 00:05:19 2024 From: andrew.clemons at gmail.com (andrew.clemons at gmail.com) Date: Sat, 9 Mar 2024 09:05:19 +0900 Subject: [Slackbuilds-users] android-tools requires google-go-lang? In-Reply-To: <7881bed8-f873-42db-8cb0-7f7be7ffeb53@telszewski.com> References: <7881bed8-f873-42db-8cb0-7f7be7ffeb53@telszewski.com> Message-ID: <4854d467-4fc9-4dc0-9835-6f023ba42ad2@gmail.com> On 9/03/24 08:51, Andrzej Telszewski wrote: > Hi, > > in order to build _android-tools_ I needed to install _google-go-lang_, > but it's not in `REQUIRES`. > > Isn't that incorrect? > > Bcc'd maintainer. The last update built fine: https://github.com/SlackBuildsOrg/slackbuilds/pull/4709 I just built it here locally in a clean 15.0 env without google-go-lang. Are you also building on stable? From willysr at slackbuilds.org Sat Mar 9 01:18:44 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 Mar 2024 08:18:44 +0700 Subject: [Slackbuilds-users] Updates - 20240309.1 Message-ID: Sat Mar 9 01:09:03 UTC 2024 academic/Gridcoin-Research: Updated for version 5.4.6.0 academic/fet: Updated for version 6.18.1. academic/zotero: update 6.0.35 audio/clementine: Fix build with new protobuf3. audio/mpd: Updated for version 0.23.15. audio/ncspot: Updated for version 1.1.0. audio/qsynth: Updated for version 0.9.13. audio/stops: Updated for version 0.4.0. desktop/anki: Fix ownership. desktop/autorandr: Updated for version 1.15.0. desktop/mate-terminal: Updated for version 1.28.1. desktop/nwg-displays: Updated for version 0.3.14. desktop/nwg-shell: Updated for version 0.5.33. desktop/qt6ct: Use qmake6 instead of qmake-qt6. desktop/wmsorsen: Added (temperature sensors). development/SQLAlchemy: Updated for version 1.4.52. development/aws-cdk: Updated for version 2.131.0. development/bbcsdl: Updated for version 1.39a. development/d-tools: Updated for version 2.107.1 development/dmd: Updated for version 2.107.1 development/dynarmic: Removed (requested by maintainer). development/git-lfs: Updated for version 3.5.1. development/github-cli: Updated for version 2.45.0 development/google-go-lang: Updated for version 1.21.8. development/gtest: Downgraded to version 1.12.1. development/hugo: update 0.123.8 development/jupyter-nbconvert: Update for 7.16.2 development/jupyter_client: Update dep. development/jupyter_server: Update dep. development/kotlin: Updated for version 1.9.23. development/lazarus: Updated for version 3.2. development/mongodb-compass: Updated for version 1.42.2. development/mongodb-shell: Updated for version 2.1.5. development/ola: Removed (FTB and maintainer is inactive). development/postman: Updated for version 10.23.9 development/protobuf3: Updated for version 25.3. development/protoc-gen-go: Update for 1.33.0 development/qb64pe: Updated for version 3.12.0. development/radare2: Updated for version 5.8.8. development/tea: Use qmake6 instead of qmake-qt6. development/tea: updated for version 62.3.0 development/textadept: updated for version 12.3 games/PrismLauncher: Updated for version 8.2. games/glulxe: Added (Portable VM). games/pokerth: Updated for version 20230930_ecf031e. games/principia: Updated for version 2024.02.29. games/yuzu: Removed (project shutting down). gis/proj-data: Updated for version 1.17. gis/proj: Updated for version 9.4.0. gis/qgis: Updated for version 3.34.4. graphics/FotoKilof: Updated for version 4.4.6. graphics/MaterialX: Updated for version 1.38.9. graphics/embree: Updated for version 4.3.1. graphics/lximage-qt: Added (Image viewer). graphics/vuescan: Updated for version 9.8.29. ham/inspectrum: Updated for version 0.3.1. ham/qlog: Updated for version 0.33.0. libraries/CGAL5: Updated for version 5.6.1. libraries/LucenePlusPlus: Update script. libraries/camlpdf: Updated for version 2.7. libraries/canfigger: Updated for version 0.3.0. libraries/cheapglk: Added (Cheapass Implementation of the Glk API). libraries/grpc: Updated for version 1.62.0. libraries/ignition-transport: Removed (outdated and FTB). libraries/imlib2: Updated for version 1.12.2. libraries/libcompizconfig: Update script. libraries/libjodycode: migrated from github to codeberg libraries/libopenshot: Fix build with new protobuf3. libraries/mygpoclient: Updated for version 1.9. libraries/wimlib: Updated for version 1.14.4. libraries/zita-alsa-pcmi: Updated for version 0.6.1. misc/bitwarden-desktop: Updated for version 2024.2.1 multimedia/MuseScore-Legacy: Updated script. multimedia/MuseScore: Updated script, removed wrong dependency. multimedia/filebot: Version bump to 5.1.3 multimedia/gpodder: Updated for version 3.11.4. multimedia/kodi: Version bump to 20.5 multimedia/opera-ffmpeg-codecs: Updated for version 0.85.0. multimedia/podcastparser: Updated for version 0.6.10. multimedia/sickchill: Version bump to 2024.3.1 multimedia/spotify: Updated for version 1.2.31.1205. multimedia/vokoscreenNG: Use qmake6 instead of qmake-qt6. multimedia/winff: Updated for version 1.6.3 network/AdGuardHome: Updated for version 0.107.45. network/bozohttpd: Update homepage. network/brave-browser: update 1.63.169 network/discord: Version bump to 0.0.44 network/dropbox: Updated for vesion 194.4.6267. network/gmi100: Added (Gemini CLI protocol). network/goimapnotify: Updated for version 2.3.12. network/mosh: Fix build with new protobuf3 network/mumble-server: Fix build with new protobuf3 network/mumble: Fix build with new protobuf3 network/nethogs: Updated for version 0.8.6. network/nextcloud-desktop: update 3.12.1 network/nordvpn: Updated for version 3.17.2. network/opera: Updated for version 108.0.5067.20. network/signal-desktop: Updated for version 7.1.1. network/tailscale: update 1.60.1 network/telegram: Updated for version 4.15.1. network/tor-browser: Updated for version 13.0.11. network/unbound: Updated for version 1.19.2. network/vivaldi: Updated for version 6.6.3271.48. network/windscribe: Updated for version 2.9.9. office/asymptote: Updated for version 2.88. office/cpdf: Updated for version 2.7. office/libreoffice-helppack: Updated for version 24.2.1. office/libreoffice-langpack: Updated for version 24.2.1. office/libreoffice: Updated for version 24.2.1. office/pandoc-bin: update 3.1.12.2 office/sent: Added (Presentation tool). office/smoffice2024: Updated for version 2024_1210. perl/MoarVM: Updated for version 2024.02 perl/nqp: Updated for version 2024.02 perl/perl-Crypt-OpenSSL-Guess: Updated dependencies. perl/perl-Crypt-OpenSSL-Random: Add missing dependency. perl/perl-Crypt-OpenSSL-Random: Updated for version 0.15. perl/perl-Date-Manip: Updated for version 6.95. perl/perl-Mail-DKIM: Updated for version 1.20240124. perl/perl-Mail-SPF: Updated for version 3.20240206. perl/perl-Net-DNS-Resolver-Programmable: Updated for version 0.009. perl/perl-Net-Ident: Updated for version 1.25. perl/perl-Net-Server: Updated for version 2.014. perl/perl-Test-Inter: Updated for version 1.11. perl/perl-http-cookies: Updated for version 6.16. perl/perl-http-date: Updated for version 6.06. perl/perl-net-dns: Updated for version 1.44. perl/perl-net-http: Updated for version 6.23. perl/rakudo: Updated for version 2024.02 python/buildbot-badges: updated for version 3.11.1 python/buildbot-worker: updated for version 3.11.1 python/buildbot: updated for version 3.11.1 python/cssselect: Removed (split into python2-cssselect and python3-cssselect python/email-validator: Updated for version 2.1.1. python/hg-git: updated for version 1.1.1 python/lxml: Removed (split into python2-lxml and python3-lxml) python/pipdeptree: Updated for version 2.16.1. python/python-importlib_metadata: Updated for version 7.0.2. python/python3-Flask-Dance: Updated for version 7.1.0. python/python3-Flask-Security-Too: Updated for version 5.4.1. python/python3-aiosmtpd: updated for version 1.4.5 python/python3-argon2-cffi-bindings: Added (python2 of argon2-cffi-bindings). python/python3-argon2-cffi: Added (python3 of argon2-cffi). python/python3-build: Updated for version 1.1.1. python/python3-cffsubr: Updated for version 0.3.0. python/python3-entrypoints: Added (python3 of entrypoints). python/python3-grpcio: Updated for version 1.62.0. python/python3-keyring: Add python3-setuptools-opt dependency python/python3-libtmux: Updated for version 0.32.0. python/python3-maturin: Updated for version 1.5.0. python/python3-nest_asyncio: Added (python3 of nest_asyncio). python/python3-putio.py: Fix versioning issue python/python3-pydantic: Updated for version 2.6.3. python/python3-pydocstyle: Update for 6.2.0 python/python3-pykeepass: Update dep. python/python3-qbittorrent-api: Version bump to 2024.2.59 python/python3-rich: Updated for version 13.7.1. python/python3-tox: Version bump to 4.14.1 python/python3-trove-classifiers: Updated for version 2024.3.3. python/python3-twisted: updated for version 24.3.0 python/scikit-learn: Update README system/android-udev-rules: Updated for version 2024.02.21. system/capstone: Updated for version 5.0. system/fzy: Added (Fuzzy finder). system/hp-wmi-sensors: Added (monitoring system). system/iselect: Added (dialog system). system/jdupes: migrated from github to codeberg system/kc: Updated for version 2.5.3. system/lxqt-config: Remove lxqt-themes dependency system/nvidia-driver: Updated for version 550.54.14. system/nvidia-kernel: Updated for version 550.54.14. system/nvidia-legacy390-driver: Update HOMEPAGE. system/nvidia-legacy390-kernel: Update HOMEPAGE. system/nvidia-legacy470-driver: Updated for version 470.239.06. system/nvidia-legacy470-kernel: Updated for version 470.239.06. system/nvidia-open-kernel: Updated for version 550.54.14. system/percol: Added (dialog system). system/slackrepo: Updated for version 20240308. system/tmuxp: Updated for version 1.40.0. system/yank: Added (dialog system). +--------------------------+ -- 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 philip at vd-hoeven.nl Sat Mar 9 10:15:14 2024 From: philip at vd-hoeven.nl (Philip van der Hoeven) Date: Sat, 9 Mar 2024 11:15:14 +0100 Subject: [Slackbuilds-users] android-tools requires google-go-lang? In-Reply-To: <7881bed8-f873-42db-8cb0-7f7be7ffeb53@telszewski.com> References: <7881bed8-f873-42db-8cb0-7f7be7ffeb53@telszewski.com> Message-ID: Hi, google-go-lang should not be necessary, because android-tools can be build with gcc-go. Are you sure you have gcc-go installed? It's included with Slackware in the d series. Philip On Sat, Mar 9, 2024 at 12:52?AM Andrzej Telszewski wrote: > Hi, > > in order to build _android-tools_ I needed to install _google-go-lang_, > but it's not in `REQUIRES`. > > Isn't that incorrect? > > Bcc'd maintainer. > > -- > Best regards, > Andrzej Telszewski > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Sat Mar 9 20:34:45 2024 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sat, 9 Mar 2024 20:34:45 +0000 Subject: [Slackbuilds-users] eclipse-platform slackbuild Message-ID: the download link for the source?/binary for this package appears not be be available any more. newer versions are available, but they require java 17 or higher. regards, Tim From urchlay at slackware.uk Sat Mar 9 21:28:22 2024 From: urchlay at slackware.uk (B. Watson) Date: Sat, 9 Mar 2024 16:28:22 -0500 (EST) Subject: [Slackbuilds-users] eclipse-platform slackbuild In-Reply-To: References: Message-ID: <9e40317f-3e4f-2be9-a625-ba71dbee8c45@slackware.uk> On Sat, 9 Mar 2024, Tim Dickson via SlackBuilds-users wrote: > the download link for the source?/binary for this package appears not be be > available any more. > newer versions are available, but they require java 17 or higher. > regards, Tim If you just want to build the existing version, there's a copy of the source in the SBo source archive, here: https://slackware.uk/sbosrcarch/by-md5/4/8/48253adbb219851359613344d942d934/eclipse-platform-4.19-linux-gtk-x86_64.tar.gz From fourtysixandtwo at sliderr.net Sat Mar 9 22:32:30 2024 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sat, 9 Mar 2024 15:32:30 -0700 Subject: [Slackbuilds-users] SQLAlchemy 2.0.x upgrade Message-ID: Hi all, I've submitted a PR. Here's the patch. https://github.com/SlackBuildsOrg/slackbuilds/commit/d3cd6e0ecfeff64ecc315ca92a2e940eeccc9fa2.diff Any further testing and questions or concerns would be appreciated. Here's a list of the builds that have issues with the upgrade: - sickchill -have emailed maintainer to remove patch to make it work with SQLAlchemy 1.x - buildbot -seems to run fine, but has warning -buildbot 3.11.0 has requirement sqlalchemy<1.5,>=1.3.0, but you have sqlalchemy 2.0.28. -have emailed maintainer for further testing Slackbuilds suggested for removal: - alembic (python2 only and previously broken) -replaced by python3-alembic. -maintainer is not active (3 years) - Pyfa -unless someone would like to take it over and upgrade it -maintainer is not active (4 years) - sqlalchemy-migrate -Kyle has given ok to remove as it is no longer a dep of pytrainer -no updates to project since 2019. - gourmet (python2) -believe it is broken, SQLAlchemy's python2 support was removed before I took it over -maintainer is not active (9 years) Here is the remaining list of builds that have SQLAlchemy as a dep. Basic testing shows no issues: flexget python3-cinemagoer zope.sqlalchemy python3-paginate_sqlalchemy python3-obspy slpkg python3-Flask-SQLAlchemy pytrainer python3-alembic python3-mailman Kallithea kallithea-frontend buildbot-badges pychess python3-ipython-sql Cheers From dickson.tim at googlemail.com Sun Mar 10 10:33:45 2024 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sun, 10 Mar 2024 10:33:45 +0000 Subject: [Slackbuilds-users] kicad slackbuild Message-ID: <7a2a61f1-7a0a-4e8f-baf3-bd53502c8143@googlemail.com> anyone having issues with md5sum i'm getting Expected: dd187abbfb1109f8d417aa08fc75d19f ??? Found:??? 414143a111e9217b3ae792328ff98bdc ? regards, Tim From fernando.lopezjr at gmail.com Sun Mar 10 10:57:41 2024 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 10 Mar 2024 05:57:41 -0500 Subject: [Slackbuilds-users] kicad slackbuild In-Reply-To: <7a2a61f1-7a0a-4e8f-baf3-bd53502c8143@googlemail.com> References: <7a2a61f1-7a0a-4e8f-baf3-bd53502c8143@googlemail.com> Message-ID: yes. it changes every time. just ignore the md5sum. On Sun, Mar 10, 2024 at 5:33?AM Tim Dickson via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > anyone having issues with md5sum i'm getting > Expected: dd187abbfb1109f8d417aa08fc75d19f > Found: 414143a111e9217b3ae792328ff98bdc > > ? > 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/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Sun Mar 10 12:46:47 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 10 Mar 2024 05:46:47 -0700 Subject: [Slackbuilds-users] kicad slackbuild In-Reply-To: References: <7a2a61f1-7a0a-4e8f-baf3-bd53502c8143@googlemail.com> Message-ID: On Sun, Mar 10, 2024, 3:58?AM Fernando Lopez wrote: > yes. it changes every time. just ignore the md5sum. > > On Sun, Mar 10, 2024 at 5:33?AM Tim Dickson via SlackBuilds-users < > slackbuilds-users at slackbuilds.org> wrote: > >> anyone having issues with md5sum i'm getting >> Expected: dd187abbfb1109f8d417aa08fc75d19f >> Found: 414143a111e9217b3ae792328ff98bdc >> >> ? >> regards, Tim > > If GitLab can't provide consistent downloads to match md5 hashes, maybe it should be switched to GitHub downloads: https://github.com/KiCad/kicad-source-mirror/archive/refs/tags/8.0.0/kicad-source-mirror-8.0.0.tar.gz The SlackBuild would only need minor corrections to reflect the new source filename, since it is different than the existing filename (introduce a SRCNAM variable and swap out PRGNAM when the file or folder is referenced). If something else caused this mismatch, feel free to ignore this message :) Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From rcb at beco.cc Sun Mar 10 16:54:41 2024 From: rcb at beco.cc (Ruben Carlo Benante) Date: Sun, 10 Mar 2024 13:54:41 -0300 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 In-Reply-To: <45ae0ae9-d1b0-4952-adf8-ae52ce905d00@giand.it> References: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> <45ae0ae9-d1b0-4952-adf8-ae52ce905d00@giand.it> Message-ID: <18e2949a282.e802155b2535715.8372097867534222834@beco.cc> Hello, Is there an error in the version number? Or is it going from 3 to 25 and keep growing further in the next versions? The following names are what it looked like in the past: * Packages/protobuf-2.6.1-x86_64-1_SBo.tgz * Packages/protobuf3-3.17.3-x86_64-1_SBo.tgz * Packages/protobuf3-3.18.1-x86_64-1_SBo.tgz * Packages/protobuf3-3.19.1-x86_64-1_SBo.tgz * Packages/protobuf3-3.19.3-x86_64-1_SBo.tgz * Packages/protobuf3-3.19.4-x86_64-1_SBo.tgz * Packages/protobuf3-3.20.0-x86_64-1_SBo.tgz * Packages/protobuf3-3.20.1-x86_64-1_SBo.tgz * Packages/protobuf3-25.3-x86_64-1_SBo.tgz I'm afraid slackpkg or sbotools or sbopkg will complain if the next comes with something like ?Packages/protobuf3-3.26.0-x86_64-1_SBo.tgz or something as previous format Cordialmente, Ruben -- Dr. Beco AI Researcher ---- On Sat, 02 Mar 2024 18:10:31 -0300 Giancarlo Dess? wrote --- Il 01/03/24 20:35, Willy Sudiarto Raharjo ha scritto: > Hi > > i have just started to work on protobuf3 updates, pushing 2y of works > by upstream since last update. > > However, there are 26 other scripts which depends on protobuf3, listed > here (https://slackbuilds.org/advsearch.php?q=protobuf3&stype=revdep1) > > although we do have CI engine that could help us test whether the new > update will break them or not, it won't help us testing the runtime > issues. Therefore, i would like to ask for help by those who are using > these 26 packages to see if by upgrading protobuf3 and rebuilding them > will have any runtime issues or not. > > I will keep the protobuf3 updates for future public update (like 1-2 > weeks delay) to give others more time to test. > > The protobuf3 update can be seen here > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > > Big thanks in advance > At the moment I tested new protobuf3 in -current, it works for protobuf-c/postgis and qgis After upgrade of protobuf3 the entire tree until qgis was broken, I had to rebuild protobuf-c and then postgis and finally qgis because protobuf is required as first level dependency also by qgis -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* _______________________________________________ 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 rcb at beco.cc Sun Mar 10 20:51:01 2024 From: rcb at beco.cc (Ruben Carlo Benante) Date: Sun, 10 Mar 2024 17:51:01 -0300 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 In-Reply-To: <18e2949a282.e802155b2535715.8372097867534222834@beco.cc> References: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> <45ae0ae9-d1b0-4952-adf8-ae52ce905d00@giand.it> <18e2949a282.e802155b2535715.8372097867534222834@beco.cc> Message-ID: <18e2a2040ce.10c7a79e32545886.80972166299494485@beco.cc> Another thing that may or may not be related: The mp3 player Clementine has stoped working after upgrade. I've returned to grpc-1.48.4 and protobuf3-3.20.1, and after the downgrade Clementine works fine again. Cordialmente, Ruben -- Dr. Beco AI Researcher ---- On Sun, 10 Mar 2024 13:54:41 -0300 Ruben Carlo Benante wrote --- Hello, Is there an error in the version number? Or is it going from 3 to 25 and keep growing further in the next versions? The following names are what it looked like in the past: * Packages/protobuf-2.6.1-x86_64-1_SBo.tgz * Packages/protobuf3-3.17.3-x86_64-1_SBo.tgz * Packages/protobuf3-3.18.1-x86_64-1_SBo.tgz * Packages/protobuf3-3.19.1-x86_64-1_SBo.tgz * Packages/protobuf3-3.19.3-x86_64-1_SBo.tgz * Packages/protobuf3-3.19.4-x86_64-1_SBo.tgz * Packages/protobuf3-3.20.0-x86_64-1_SBo.tgz * Packages/protobuf3-3.20.1-x86_64-1_SBo.tgz * Packages/protobuf3-25.3-x86_64-1_SBo.tgz I'm afraid slackpkg or sbotools or sbopkg will complain if the next comes with something like ?Packages/protobuf3-3.26.0-x86_64-1_SBo.tgz or something as previous format Cordialmente, Ruben -- Dr. Beco AI Researcher ---- On Sat, 02 Mar 2024 18:10:31 -0300 Giancarlo Dess? wrote --- Il 01/03/24 20:35, Willy Sudiarto Raharjo ha scritto: > Hi > > i have just started to work on protobuf3 updates, pushing 2y of works > by upstream since last update. > > However, there are 26 other scripts which depends on protobuf3, listed > here (https://slackbuilds.org/advsearch.php?q=protobuf3&stype=revdep1) > > although we do have CI engine that could help us test whether the new > update will break them or not, it won't help us testing the runtime > issues. Therefore, i would like to ask for help by those who are using > these 26 packages to see if by upgrading protobuf3 and rebuilding them > will have any runtime issues or not. > > I will keep the protobuf3 updates for future public update (like 1-2 > weeks delay) to give others more time to test. > > The protobuf3 update can be seen here > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > > Big thanks in advance > At the moment I tested new protobuf3 in -current, it works for protobuf-c/postgis and qgis After upgrade of protobuf3 the entire tree until qgis was broken, I had to rebuild protobuf-c and then postgis and finally qgis because protobuf is required as first level dependency also by qgis -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* _______________________________________________ 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 milgram at cgpp.com Sun Mar 10 22:21:03 2024 From: milgram at cgpp.com (J. Milgram) Date: Sun, 10 Mar 2024 18:21:03 -0400 Subject: [Slackbuilds-users] sbotools config issues Message-ID: Hello. Once again having problems installing with sbotools. There's evidently some config subtlety I'm not grasping, hopefully someone can set me straight. I have a fresh -current install and am using the default 15.0 repo. Many slackbuilds installed fine, but then: /usr/sbin/sboinstall XXX fails with: "Unable to locate XXX in the SlackBuilds.org tree." Where XXX is in [ python3-build, python3-wheel ] ... and maybe others. May be just python3 packages that fail but haven't investigated. I do see these slackbuilds in the slackbuilds repo so they're not mirages. Some config stuff: >> cat /etc/slackware-version Slackware 15.0+ >> cat /etc/sbotools/sbotools.conf JOBS=5 DISTCLEAN=TRUE >> /usr/sbin/sboconfig -l sboconfig -d|--distclean: ??? DISTCLEAN=TRUE sboconfig -j|--jobs: ??? JOBS=5 sboconfig -o|--local-overrides: ??? LOCAL_OVERRIDES=FALSE sboconfig -c|--noclean: ??? NOCLEAN=FALSE sboconfig -p|--pkg-dir: ??? PKG_DIR=FALSE sboconfig -r|--repo: ??? REPO=FALSE sboconfig -s|--sbo-home: ??? SBO_HOME=/usr/sbo sboconfig -V|--slackware-version: ??? SLACKWARE_VERSION=FALSE /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for python3-build or python3-wheel. /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and have also done sboclean -d. /usr/sbin/sbosnap and sboupdate both run seemingly without error, but don't pick up the missing slackbuilds. I'm guessing this is a 15.0 vs. -current thing, but I am out of ideas. Grateful for any advice! Maybe I need to install these problem packages by hand ... if it must be, so be it. But in the long term it would be nice to get everything configured properly. thanks! Judah -- ===== milgram at cgpp.com 301-257-7069 From milgram at cgpp.com Sun Mar 10 22:35:01 2024 From: milgram at cgpp.com (J. Milgram) Date: Sun, 10 Mar 2024 18:35:01 -0400 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: References: Message-ID: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> ... or maybe I just need to switch to sbopkg? On 3/10/24 18:21, J. Milgram wrote: > > Hello. > > Once again having problems installing with sbotools. There's evidently > some config subtlety I'm not grasping, hopefully someone can set me > straight. > > I have a fresh -current install and am using the default 15.0 repo. > Many slackbuilds installed fine, but then: > > /usr/sbin/sboinstall XXX fails with: > > "Unable to locate XXX in the SlackBuilds.org tree." > > Where XXX is in [ python3-build, python3-wheel ] ... and maybe others. > May be just python3 packages that fail but haven't investigated. I do > see these slackbuilds in the slackbuilds repo so they're not mirages. > > Some config stuff: > > >> cat /etc/slackware-version > Slackware 15.0+ > > >> cat /etc/sbotools/sbotools.conf > JOBS=5 > DISTCLEAN=TRUE > > >> /usr/sbin/sboconfig -l > sboconfig -d|--distclean: > ??? DISTCLEAN=TRUE > sboconfig -j|--jobs: > ??? JOBS=5 > sboconfig -o|--local-overrides: > ??? LOCAL_OVERRIDES=FALSE > sboconfig -c|--noclean: > ??? NOCLEAN=FALSE > sboconfig -p|--pkg-dir: > ??? PKG_DIR=FALSE > sboconfig -r|--repo: > ??? REPO=FALSE > sboconfig -s|--sbo-home: > ??? SBO_HOME=/usr/sbo > sboconfig -V|--slackware-version: > ??? SLACKWARE_VERSION=FALSE > > /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for > python3-build or python3-wheel. > > /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and > have also done sboclean -d. > > /usr/sbin/sbosnap and sboupdate both run seemingly without error, but > don't pick up the missing slackbuilds. > > I'm guessing this is a 15.0 vs. -current thing, but I am out of ideas. > Grateful for any advice! > > Maybe I need to install these problem packages by hand ... if it must > be, so be it. But in the long term it would be nice to get everything > configured properly. > > thanks! > > Judah > -- ===== milgram at cgpp.com 301-257-7069 From didier at slint.fr Sun Mar 10 22:41:05 2024 From: didier at slint.fr (Didier Spaier) Date: Sun, 10 Mar 2024 23:41:05 +0100 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> References: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> Message-ID: Rather you should not use the default 15.0 repo on -current, regardless of the tool you use for packages management. Cheers, Didier Le 10/03/2024 ? 23:35, J. Milgram a ?crit?: > > ... or maybe I just need to switch to sbopkg? > > > On 3/10/24 18:21, J. Milgram wrote: >> >> Hello. >> >> Once again having problems installing with sbotools. There's evidently some >> config subtlety I'm not grasping, hopefully someone can set me straight. >> >> I have a fresh -current install and am using the default 15.0 repo. Many >> slackbuilds installed fine, but then: >> >> /usr/sbin/sboinstall XXX fails with: >> >> "Unable to locate XXX in the SlackBuilds.org tree." >> >> Where XXX is in [ python3-build, python3-wheel ] ... and maybe others. May be >> just python3 packages that fail but haven't investigated. I do see these >> slackbuilds in the slackbuilds repo so they're not mirages. >> >> Some config stuff: >> >> >> cat /etc/slackware-version >> Slackware 15.0+ >> >> >> cat /etc/sbotools/sbotools.conf >> JOBS=5 >> DISTCLEAN=TRUE >> >> >> /usr/sbin/sboconfig -l >> sboconfig -d|--distclean: >> ??? DISTCLEAN=TRUE >> sboconfig -j|--jobs: >> ??? JOBS=5 >> sboconfig -o|--local-overrides: >> ??? LOCAL_OVERRIDES=FALSE >> sboconfig -c|--noclean: >> ??? NOCLEAN=FALSE >> sboconfig -p|--pkg-dir: >> ??? PKG_DIR=FALSE >> sboconfig -r|--repo: >> ??? REPO=FALSE >> sboconfig -s|--sbo-home: >> ??? SBO_HOME=/usr/sbo >> sboconfig -V|--slackware-version: >> ??? SLACKWARE_VERSION=FALSE >> >> /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for python3-build >> or python3-wheel. >> >> /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and have >> also done sboclean -d. >> >> /usr/sbin/sbosnap and sboupdate both run seemingly without error, but don't >> pick up the missing slackbuilds. >> >> I'm guessing this is a 15.0 vs. -current thing, but I am out of ideas. >> Grateful for any advice! >> >> Maybe I need to install these problem packages by hand ... if it must be, so >> be it. But in the long term it would be nice to get everything configured >> properly. >> >> thanks! >> >> Judah >> > From jebrhansen+SBo at gmail.com Sun Mar 10 22:45:43 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 10 Mar 2024 15:45:43 -0700 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 In-Reply-To: <18e2a2040ce.10c7a79e32545886.80972166299494485@beco.cc> References: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> <45ae0ae9-d1b0-4952-adf8-ae52ce905d00@giand.it> <18e2949a282.e802155b2535715.8372097867534222834@beco.cc> <18e2a2040ce.10c7a79e32545886.80972166299494485@beco.cc> Message-ID: Did you rebuild clementine after updating protobuf3? You should be on build 2 of clementine as that includes fixes for the new protobuf3 version. It works fine on my end (I'm the clementine maintainer). Jeremy On Sun, Mar 10, 2024, 1:51?PM Ruben Carlo Benante via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Another thing that may or may not be related: > > The mp3 player Clementine has stoped working after upgrade. > > I've returned to grpc-1.48.4 and protobuf3-3.20.1, and after the downgrade > Clementine works fine again. > > Cordialmente, > Ruben > > -- > Dr. Beco > AI Researcher > > > > > ---- On Sun, 10 Mar 2024 13:54:41 -0300 *Ruben Carlo Benante >* wrote --- > > Hello, > > Is there an error in the version number? Or is it going from 3 to 25 and > keep growing further in the next versions? > > The following names are what it looked like in the past: > > * Packages/protobuf-2.6.1-x86_64-1_SBo.tgz > * Packages/protobuf3-3.17.3-x86_64-1_SBo.tgz > * Packages/protobuf3-3.18.1-x86_64-1_SBo.tgz > * Packages/protobuf3-3.19.1-x86_64-1_SBo.tgz > * Packages/protobuf3-3.19.3-x86_64-1_SBo.tgz > * Packages/protobuf3-3.19.4-x86_64-1_SBo.tgz > * Packages/protobuf3-3.20.0-x86_64-1_SBo.tgz > * Packages/protobuf3-3.20.1-x86_64-1_SBo.tgz > * Packages/protobuf3-25.3-x86_64-1_SBo.tgz > > > I'm afraid slackpkg or sbotools or sbopkg will complain if the next comes > with something like > > Packages/protobuf3-3.26.0-x86_64-1_SBo.tgz or something as previous format > > > Cordialmente, > Ruben > > -- > Dr. Beco > AI Researcher > > > > > ---- On Sat, 02 Mar 2024 18:10:31 -0300 *Giancarlo Dess? >* wrote --- > > Il 01/03/24 20:35, Willy Sudiarto Raharjo ha scritto: > > Hi > > > > i have just started to work on protobuf3 updates, pushing 2y of works > > by upstream since last update. > > > > However, there are 26 other scripts which depends on protobuf3, listed > > here (https://slackbuilds.org/advsearch.php?q=protobuf3&stype=revdep1) > > > > although we do have CI engine that could help us test whether the new > > update will break them or not, it won't help us testing the runtime > > issues. Therefore, i would like to ask for help by those who are using > > these 26 packages to see if by upgrading protobuf3 and rebuilding them > > will have any runtime issues or not. > > > > I will keep the protobuf3 updates for future public update (like 1-2 > > weeks delay) to give others more time to test. > > > > The protobuf3 update can be seen here > > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > > > > Big thanks in advance > > > At the moment I tested new protobuf3 in -current, it works for > protobuf-c/postgis and qgis > > After upgrade of protobuf3 the entire tree until qgis was broken, I had > to rebuild protobuf-c and then postgis and finally qgis because protobuf > is required as first level dependency also by qgis > > -- > > ********************************************************* > 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/ > > > > > > _______________________________________________ > 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 fourtysixandtwo at sliderr.net Sun Mar 10 23:07:56 2024 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sun, 10 Mar 2024 17:07:56 -0600 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> References: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> Message-ID: Both work fine pointed at ponce's repo for -current. sbotools by default does point to ponce's repo, but maybe try pointing at it explicitly. sboconfig -r https://github.com/Ponce/slackbuilds.git sbocheck Cheers On Sun, Mar 10, 2024 at 4:35?PM J. Milgram wrote: > > > ... or maybe I just need to switch to sbopkg? > > > On 3/10/24 18:21, J. Milgram wrote: > > > > Hello. > > > > Once again having problems installing with sbotools. There's evidently > > some config subtlety I'm not grasping, hopefully someone can set me > > straight. > > > > I have a fresh -current install and am using the default 15.0 repo. > > Many slackbuilds installed fine, but then: > > > > /usr/sbin/sboinstall XXX fails with: > > > > "Unable to locate XXX in the SlackBuilds.org tree." > > > > Where XXX is in [ python3-build, python3-wheel ] ... and maybe others. > > May be just python3 packages that fail but haven't investigated. I do > > see these slackbuilds in the slackbuilds repo so they're not mirages. > > > > Some config stuff: > > > > >> cat /etc/slackware-version > > Slackware 15.0+ > > > > >> cat /etc/sbotools/sbotools.conf > > JOBS=5 > > DISTCLEAN=TRUE > > > > >> /usr/sbin/sboconfig -l > > sboconfig -d|--distclean: > > DISTCLEAN=TRUE > > sboconfig -j|--jobs: > > JOBS=5 > > sboconfig -o|--local-overrides: > > LOCAL_OVERRIDES=FALSE > > sboconfig -c|--noclean: > > NOCLEAN=FALSE > > sboconfig -p|--pkg-dir: > > PKG_DIR=FALSE > > sboconfig -r|--repo: > > REPO=FALSE > > sboconfig -s|--sbo-home: > > SBO_HOME=/usr/sbo > > sboconfig -V|--slackware-version: > > SLACKWARE_VERSION=FALSE > > > > /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for > > python3-build or python3-wheel. > > > > /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and > > have also done sboclean -d. > > > > /usr/sbin/sbosnap and sboupdate both run seemingly without error, but > > don't pick up the missing slackbuilds. > > > > I'm guessing this is a 15.0 vs. -current thing, but I am out of ideas. > > Grateful for any advice! > > > > Maybe I need to install these problem packages by hand ... if it must > > be, so be it. But in the long term it would be nice to get everything > > configured properly. > > > > thanks! > > > > Judah > > > > -- > ===== > milgram at cgpp.com > 301-257-7069 > > _______________________________________________ > 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 milgram at cgpp.com Mon Mar 11 00:51:40 2024 From: milgram at cgpp.com (J. Milgram) Date: Sun, 10 Mar 2024 20:51:40 -0400 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: References: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> Message-ID: <669f47e6-359a-40fa-8604-a89328063db6@cgpp.com> Thanks, and thanks Didier too. ( I misunderstood ... item #15 at https://slackbuilds.org/faq/ says: "Slackware -current is not supported, but as a general rule, the scripts should work on it as well." so I didn't think to look for a -current repo. ) So I did: sboconfig -r https://github.com/Ponce/slackbuilds.git sboconfig -l # to confirm sbo was in fact pointed at that URL sbocheck It ran, didn't seem to download anything new. But no improvement, still got "Unable to locate..." Then just to be sure, started from scratch: rm -rf /usr/sbo sbosnap fetch sboinstall python3-matplotlib ... but same problem. FWIW sbotools is 2.7. So tried it with sbopkg, selected the -current git repo and it seems to have worked. Good enough for me, though I would still like to know what went wrong with sbotools. Is sbopkg more actively maintained than sbotools? thx Judah On 3/10/24 19:07, fourtysixandtwo wrote: > Both work fine pointed at ponce's repo for -current. > > sbotools by default does point to ponce's repo, but maybe try pointing > at it explicitly. > > sboconfig -r https://github.com/Ponce/slackbuilds.git > sbocheck > > Cheers > > On Sun, Mar 10, 2024 at 4:35?PM J. Milgram wrote: >> >> ... or maybe I just need to switch to sbopkg? >> >> >> On 3/10/24 18:21, J. Milgram wrote: >>> Hello. >>> >>> Once again having problems installing with sbotools. There's evidently >>> some config subtlety I'm not grasping, hopefully someone can set me >>> straight. >>> >>> I have a fresh -current install and am using the default 15.0 repo. >>> Many slackbuilds installed fine, but then: >>> >>> /usr/sbin/sboinstall XXX fails with: >>> >>> "Unable to locate XXX in the SlackBuilds.org tree." >>> >>> Where XXX is in [ python3-build, python3-wheel ] ... and maybe others. >>> May be just python3 packages that fail but haven't investigated. I do >>> see these slackbuilds in the slackbuilds repo so they're not mirages. >>> >>> Some config stuff: >>> >>>>> cat /etc/slackware-version >>> Slackware 15.0+ >>> >>>>> cat /etc/sbotools/sbotools.conf >>> JOBS=5 >>> DISTCLEAN=TRUE >>> >>>>> /usr/sbin/sboconfig -l >>> sboconfig -d|--distclean: >>> DISTCLEAN=TRUE >>> sboconfig -j|--jobs: >>> JOBS=5 >>> sboconfig -o|--local-overrides: >>> LOCAL_OVERRIDES=FALSE >>> sboconfig -c|--noclean: >>> NOCLEAN=FALSE >>> sboconfig -p|--pkg-dir: >>> PKG_DIR=FALSE >>> sboconfig -r|--repo: >>> REPO=FALSE >>> sboconfig -s|--sbo-home: >>> SBO_HOME=/usr/sbo >>> sboconfig -V|--slackware-version: >>> SLACKWARE_VERSION=FALSE >>> >>> /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for >>> python3-build or python3-wheel. >>> >>> /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and >>> have also done sboclean -d. >>> >>> /usr/sbin/sbosnap and sboupdate both run seemingly without error, but >>> don't pick up the missing slackbuilds. >>> >>> I'm guessing this is a 15.0 vs. -current thing, but I am out of ideas. >>> Grateful for any advice! >>> >>> Maybe I need to install these problem packages by hand ... if it must >>> be, so be it. But in the long term it would be nice to get everything >>> configured properly. >>> >>> thanks! >>> >>> Judah >>> >> -- >> ===== >> milgram at cgpp.com >> 301-257-7069 >> >> _______________________________________________ >> 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/ > -- ===== milgram at cgpp.com From jebrhansen+SBo at gmail.com Mon Mar 11 00:55:22 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 10 Mar 2024 17:55:22 -0700 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: <669f47e6-359a-40fa-8604-a89328063db6@cgpp.com> References: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> <669f47e6-359a-40fa-8604-a89328063db6@cgpp.com> Message-ID: On Sun, Mar 10, 2024, 5:51?PM J. Milgram wrote: > > Is sbopkg more actively maintained than sbotools? > SBo tools hasn't been updated in almost 5 years. https://github.com/pink-mist/sbotools Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kvngncrlsn at gmail.com Mon Mar 11 01:30:15 2024 From: kvngncrlsn at gmail.com (K. Eugene Carlson) Date: Mon, 11 Mar 2024 10:30:15 +0900 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: <669f47e6-359a-40fa-8604-a89328063db6@cgpp.com> References: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> <669f47e6-359a-40fa-8604-a89328063db6@cgpp.com> Message-ID: Hi, SBo packages that have been added to -current are removed from Ponce's repo to avoid file conflicts, which is why sbotools didn't find python3-wheel and python3-build. When the "unable to locate" message comes up (and it often does for Python stuff), I just select "y" to ignore and continue. That should work provided that the corresponding Slackware packages have been installed. Gene On Mon, Mar 11, 2024 at 9:51?AM J. Milgram wrote: > > Thanks, and thanks Didier too. > > ( I misunderstood ... item #15 at https://slackbuilds.org/faq/ says: > "Slackware -current is not supported, but as a general rule, the scripts > should work on it as well." so I didn't think to look for a -current repo. > ) > > So I did: > > sboconfig -r https://github.com/Ponce/slackbuilds.git > sboconfig -l # to confirm sbo was in fact pointed at that URL > sbocheck > > It ran, didn't seem to download anything new. But no improvement, still > got "Unable to locate..." > > Then just to be sure, started from scratch: > > rm -rf /usr/sbo > sbosnap fetch > sboinstall python3-matplotlib > > ... but same problem. FWIW sbotools is 2.7. > > So tried it with sbopkg, selected the -current git repo and it seems to > have worked. Good enough for me, though I would still like to know what > went wrong with sbotools. > > Is sbopkg more actively maintained than sbotools? > > thx > Judah > > On 3/10/24 19:07, fourtysixandtwo wrote: > > Both work fine pointed at ponce's repo for -current. > > > > sbotools by default does point to ponce's repo, but maybe try pointing > > at it explicitly. > > > > sboconfig -r https://github.com/Ponce/slackbuilds.git > > sbocheck > > > > Cheers > > > > On Sun, Mar 10, 2024 at 4:35?PM J. Milgram wrote: > >> > >> ... or maybe I just need to switch to sbopkg? > >> > >> > >> On 3/10/24 18:21, J. Milgram wrote: > >>> Hello. > >>> > >>> Once again having problems installing with sbotools. There's evidently > >>> some config subtlety I'm not grasping, hopefully someone can set me > >>> straight. > >>> > >>> I have a fresh -current install and am using the default 15.0 repo. > >>> Many slackbuilds installed fine, but then: > >>> > >>> /usr/sbin/sboinstall XXX fails with: > >>> > >>> "Unable to locate XXX in the SlackBuilds.org tree." > >>> > >>> Where XXX is in [ python3-build, python3-wheel ] ... and maybe others. > >>> May be just python3 packages that fail but haven't investigated. I do > >>> see these slackbuilds in the slackbuilds repo so they're not mirages. > >>> > >>> Some config stuff: > >>> > >>>>> cat /etc/slackware-version > >>> Slackware 15.0+ > >>> > >>>>> cat /etc/sbotools/sbotools.conf > >>> JOBS=5 > >>> DISTCLEAN=TRUE > >>> > >>>>> /usr/sbin/sboconfig -l > >>> sboconfig -d|--distclean: > >>> DISTCLEAN=TRUE > >>> sboconfig -j|--jobs: > >>> JOBS=5 > >>> sboconfig -o|--local-overrides: > >>> LOCAL_OVERRIDES=FALSE > >>> sboconfig -c|--noclean: > >>> NOCLEAN=FALSE > >>> sboconfig -p|--pkg-dir: > >>> PKG_DIR=FALSE > >>> sboconfig -r|--repo: > >>> REPO=FALSE > >>> sboconfig -s|--sbo-home: > >>> SBO_HOME=/usr/sbo > >>> sboconfig -V|--slackware-version: > >>> SLACKWARE_VERSION=FALSE > >>> > >>> /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for > >>> python3-build or python3-wheel. > >>> > >>> /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and > >>> have also done sboclean -d. > >>> > >>> /usr/sbin/sbosnap and sboupdate both run seemingly without error, but > >>> don't pick up the missing slackbuilds. > >>> > >>> I'm guessing this is a 15.0 vs. -current thing, but I am out of ideas. > >>> Grateful for any advice! > >>> > >>> Maybe I need to install these problem packages by hand ... if it must > >>> be, so be it. But in the long term it would be nice to get everything > >>> configured properly. > >>> > >>> thanks! > >>> > >>> Judah > >>> > >> -- > >> ===== > >> milgram at cgpp.com > >> 301-257-7069 > >> > >> _______________________________________________ > >> 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/ > > > > -- > ===== > milgram at cgpp.com > > _______________________________________________ > 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 fourtysixandtwo at sliderr.net Mon Mar 11 01:39:14 2024 From: fourtysixandtwo at sliderr.net (fourtysixandtwo) Date: Sun, 10 Mar 2024 19:39:14 -0600 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: References: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> <669f47e6-359a-40fa-8604-a89328063db6@cgpp.com> Message-ID: An instance where seeing the full error message would be helpful. On Sun, Mar 10, 2024 at 7:30?PM K. Eugene Carlson wrote: > > Hi, > > SBo packages that have been added to -current are removed from Ponce's repo to avoid file conflicts, which is why sbotools didn't find python3-wheel and python3-build. > > When the "unable to locate" message comes up (and it often does for Python stuff), I just select "y" to ignore and continue. That should work provided that the corresponding Slackware packages have been installed. > > Gene > > On Mon, Mar 11, 2024 at 9:51?AM J. Milgram wrote: >> >> >> Thanks, and thanks Didier too. >> >> ( I misunderstood ... item #15 at https://slackbuilds.org/faq/ says: >> "Slackware -current is not supported, but as a general rule, the scripts >> should work on it as well." so I didn't think to look for a -current repo. ) >> >> So I did: >> >> sboconfig -r https://github.com/Ponce/slackbuilds.git >> sboconfig -l # to confirm sbo was in fact pointed at that URL >> sbocheck >> >> It ran, didn't seem to download anything new. But no improvement, still got "Unable to locate..." >> >> Then just to be sure, started from scratch: >> >> rm -rf /usr/sbo >> sbosnap fetch >> sboinstall python3-matplotlib >> >> ... but same problem. FWIW sbotools is 2.7. >> >> So tried it with sbopkg, selected the -current git repo and it seems to have worked. Good enough for me, though I would still like to know what went wrong with sbotools. >> >> Is sbopkg more actively maintained than sbotools? >> >> thx >> Judah >> >> On 3/10/24 19:07, fourtysixandtwo wrote: >> > Both work fine pointed at ponce's repo for -current. >> > >> > sbotools by default does point to ponce's repo, but maybe try pointing >> > at it explicitly. >> > >> > sboconfig -r https://github.com/Ponce/slackbuilds.git >> > sbocheck >> > >> > Cheers >> > >> > On Sun, Mar 10, 2024 at 4:35?PM J. Milgram wrote: >> >> >> >> ... or maybe I just need to switch to sbopkg? >> >> >> >> >> >> On 3/10/24 18:21, J. Milgram wrote: >> >>> Hello. >> >>> >> >>> Once again having problems installing with sbotools. There's evidently >> >>> some config subtlety I'm not grasping, hopefully someone can set me >> >>> straight. >> >>> >> >>> I have a fresh -current install and am using the default 15.0 repo. >> >>> Many slackbuilds installed fine, but then: >> >>> >> >>> /usr/sbin/sboinstall XXX fails with: >> >>> >> >>> "Unable to locate XXX in the SlackBuilds.org tree." >> >>> >> >>> Where XXX is in [ python3-build, python3-wheel ] ... and maybe others. >> >>> May be just python3 packages that fail but haven't investigated. I do >> >>> see these slackbuilds in the slackbuilds repo so they're not mirages. >> >>> >> >>> Some config stuff: >> >>> >> >>>>> cat /etc/slackware-version >> >>> Slackware 15.0+ >> >>> >> >>>>> cat /etc/sbotools/sbotools.conf >> >>> JOBS=5 >> >>> DISTCLEAN=TRUE >> >>> >> >>>>> /usr/sbin/sboconfig -l >> >>> sboconfig -d|--distclean: >> >>> DISTCLEAN=TRUE >> >>> sboconfig -j|--jobs: >> >>> JOBS=5 >> >>> sboconfig -o|--local-overrides: >> >>> LOCAL_OVERRIDES=FALSE >> >>> sboconfig -c|--noclean: >> >>> NOCLEAN=FALSE >> >>> sboconfig -p|--pkg-dir: >> >>> PKG_DIR=FALSE >> >>> sboconfig -r|--repo: >> >>> REPO=FALSE >> >>> sboconfig -s|--sbo-home: >> >>> SBO_HOME=/usr/sbo >> >>> sboconfig -V|--slackware-version: >> >>> SLACKWARE_VERSION=FALSE >> >>> >> >>> /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for >> >>> python3-build or python3-wheel. >> >>> >> >>> /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and >> >>> have also done sboclean -d. >> >>> >> >>> /usr/sbin/sbosnap and sboupdate both run seemingly without error, but >> >>> don't pick up the missing slackbuilds. >> >>> >> >>> I'm guessing this is a 15.0 vs. -current thing, but I am out of ideas. >> >>> Grateful for any advice! >> >>> >> >>> Maybe I need to install these problem packages by hand ... if it must >> >>> be, so be it. But in the long term it would be nice to get everything >> >>> configured properly. >> >>> >> >>> thanks! >> >>> >> >>> Judah >> >>> >> >> -- >> >> ===== >> >> milgram at cgpp.com >> >> 301-257-7069 >> >> >> >> _______________________________________________ >> >> 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/ >> > >> >> -- >> ===== >> milgram at cgpp.com >> >> _______________________________________________ >> 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 milgram at cgpp.com Mon Mar 11 03:00:51 2024 From: milgram at cgpp.com (J. Milgram) Date: Sun, 10 Mar 2024 23:00:51 -0400 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: References: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> <669f47e6-359a-40fa-8604-a89328063db6@cgpp.com> Message-ID: The whole error message: (Had to use --reinstall because in the meantime I got in installed, somehow.) # sboinstall --reinstall python3-build python3-build (python3-build-1.1.1-x86_64-1_SBo) is already installed. Do you want to reinstall from SBo? [n] y Unable to locate python3-build in the SlackBuilds.org tree. Do you want to ignore it and continue? [n] So I'm guessing I installed python3-build from the 15.0 SBo repo, and it's not finding it now because I switched to Ponce's repo. (Curiously, also didn't find it either in Ponce's repo or in slackware64-current) One problem with that explanation: I was getting the error even when I still had the 15.0 SBo repo dialed in. Am making good headway with sbopkg so will set this aside for now. Will be more methodical going forward so should have more details to report if it comes up again. BTW I hadn't considered that packages can migrate from Ponce's SBo repo to -current. Will keep this in mind. thanks for the help! Judah On 3/10/24 21:39, fourtysixandtwo wrote: > An instance where seeing the full error message would be helpful. > > On Sun, Mar 10, 2024 at 7:30?PM K. Eugene Carlson wrote: >> Hi, >> >> SBo packages that have been added to -current are removed from Ponce's repo to avoid file conflicts, which is why sbotools didn't find python3-wheel and python3-build. >> >> When the "unable to locate" message comes up (and it often does for Python stuff), I just select "y" to ignore and continue. That should work provided that the corresponding Slackware packages have been installed. >> >> Gene >> >> On Mon, Mar 11, 2024 at 9:51?AM J. Milgram wrote: >>> >>> Thanks, and thanks Didier too. >>> >>> ( I misunderstood ... item #15 at https://slackbuilds.org/faq/ says: >>> "Slackware -current is not supported, but as a general rule, the scripts >>> should work on it as well." so I didn't think to look for a -current repo. ) >>> >>> So I did: >>> >>> sboconfig -r https://github.com/Ponce/slackbuilds.git >>> sboconfig -l # to confirm sbo was in fact pointed at that URL >>> sbocheck >>> >>> It ran, didn't seem to download anything new. But no improvement, still got "Unable to locate..." >>> >>> Then just to be sure, started from scratch: >>> >>> rm -rf /usr/sbo >>> sbosnap fetch >>> sboinstall python3-matplotlib >>> >>> ... but same problem. FWIW sbotools is 2.7. >>> >>> So tried it with sbopkg, selected the -current git repo and it seems to have worked. Good enough for me, though I would still like to know what went wrong with sbotools. >>> >>> Is sbopkg more actively maintained than sbotools? >>> >>> thx >>> Judah >>> >>> On 3/10/24 19:07, fourtysixandtwo wrote: >>>> Both work fine pointed at ponce's repo for -current. >>>> >>>> sbotools by default does point to ponce's repo, but maybe try pointing >>>> at it explicitly. >>>> >>>> sboconfig -r https://github.com/Ponce/slackbuilds.git >>>> sbocheck >>>> >>>> Cheers >>>> >>>> On Sun, Mar 10, 2024 at 4:35?PM J. Milgram wrote: >>>>> ... or maybe I just need to switch to sbopkg? >>>>> >>>>> >>>>> On 3/10/24 18:21, J. Milgram wrote: >>>>>> Hello. >>>>>> >>>>>> Once again having problems installing with sbotools. There's evidently >>>>>> some config subtlety I'm not grasping, hopefully someone can set me >>>>>> straight. >>>>>> >>>>>> I have a fresh -current install and am using the default 15.0 repo. >>>>>> Many slackbuilds installed fine, but then: >>>>>> >>>>>> /usr/sbin/sboinstall XXX fails with: >>>>>> >>>>>> "Unable to locate XXX in the SlackBuilds.org tree." >>>>>> >>>>>> Where XXX is in [ python3-build, python3-wheel ] ... and maybe others. >>>>>> May be just python3 packages that fail but haven't investigated. I do >>>>>> see these slackbuilds in the slackbuilds repo so they're not mirages. >>>>>> >>>>>> Some config stuff: >>>>>> >>>>>>>> cat /etc/slackware-version >>>>>> Slackware 15.0+ >>>>>> >>>>>>>> cat /etc/sbotools/sbotools.conf >>>>>> JOBS=5 >>>>>> DISTCLEAN=TRUE >>>>>> >>>>>>>> /usr/sbin/sboconfig -l >>>>>> sboconfig -d|--distclean: >>>>>> DISTCLEAN=TRUE >>>>>> sboconfig -j|--jobs: >>>>>> JOBS=5 >>>>>> sboconfig -o|--local-overrides: >>>>>> LOCAL_OVERRIDES=FALSE >>>>>> sboconfig -c|--noclean: >>>>>> NOCLEAN=FALSE >>>>>> sboconfig -p|--pkg-dir: >>>>>> PKG_DIR=FALSE >>>>>> sboconfig -r|--repo: >>>>>> REPO=FALSE >>>>>> sboconfig -s|--sbo-home: >>>>>> SBO_HOME=/usr/sbo >>>>>> sboconfig -V|--slackware-version: >>>>>> SLACKWARE_VERSION=FALSE >>>>>> >>>>>> /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for >>>>>> python3-build or python3-wheel. >>>>>> >>>>>> /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and >>>>>> have also done sboclean -d. >>>>>> >>>>>> /usr/sbin/sbosnap and sboupdate both run seemingly without error, but >>>>>> don't pick up the missing slackbuilds. >>>>>> >>>>>> I'm guessing this is a 15.0 vs. -current thing, but I am out of ideas. >>>>>> Grateful for any advice! >>>>>> >>>>>> Maybe I need to install these problem packages by hand ... if it must >>>>>> be, so be it. But in the long term it would be nice to get everything >>>>>> configured properly. >>>>>> >>>>>> thanks! >>>>>> >>>>>> Judah >>>>>> >>>>> -- >>>>> ===== >>>>> milgram at cgpp.com >>>>> 301-257-7069 >>>>> >>>>> _______________________________________________ >>>>> 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/ >>>> >>> -- >>> ===== >>> milgram at cgpp.com >>> >>> _______________________________________________ >>> 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/ > -- ===== milgram at cgpp.com 301-257-7069 From gen-bch at useyouresp.org.uk Mon Mar 11 10:21:28 2024 From: gen-bch at useyouresp.org.uk (Habs) Date: Mon, 11 Mar 2024 10:21:28 +0000 (GMT) Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: References: Message-ID: <5o7p9122-7793-5372-3r83-s5op94nqn2pq@hfrlbherfc.bet.hx> On Sun, 10 Mar 2024, J. Milgram wrote: > > Hello. > > Once again having problems installing with sbotools. There's evidently some > config subtlety I'm not grasping, hopefully someone can set me straight. > > I have a fresh -current install and am using the default 15.0 repo. Many > slackbuilds installed fine, but then: > > /usr/sbin/sboinstall XXX fails with: > > "Unable to locate XXX in the SlackBuilds.org tree." > > Where XXX is in [ python3-build, python3-wheel ] ... and maybe others. May be > just python3 packages that fail but haven't investigated. I do see these > slackbuilds in the slackbuilds repo so they're not mirages. > > Some config stuff: > >>> cat /etc/slackware-version > Slackware 15.0+ > >>> cat /etc/sbotools/sbotools.conf > JOBS=5 > DISTCLEAN=TRUE > good morning all Perhaps using REPO in the conf e.g.: REPO=https://gitlab.com/SlackBuilds.org/slackbuilds.git That sorted a few issues out in a similar case. sbofind/install/etc all work fine with it set. Habs --- Sent using Alpine/Pine, probably the best MUA --- From matteo.bernardini at gmail.com Mon Mar 11 11:06:10 2024 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 11 Mar 2024 12:06:10 +0100 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: <5o7p9122-7793-5372-3r83-s5op94nqn2pq@hfrlbherfc.bet.hx> References: <5o7p9122-7793-5372-3r83-s5op94nqn2pq@hfrlbherfc.bet.hx> Message-ID: hi, just for testing I downloaded, packaged and installed sbotools from here https://slackbuilds.org/repository/15.0/system/sbotools/ following what's written on the documentation https://pink-mist.github.io/sbotools/documentation/ I run "sbosnap fetch" to download the repository and I saw that in /usr/sbo/repo what is downloaded by default the unofficial repository for current that I maintain (check /usr/sbo/repo/.git/config) that shouldn't be used for 15.0 (maybe some other default should be set in the package on SBo) but should help who's running current. the reason why it should help who's running current is that it contains patches for the broken scripts that don't build on current and that are reported to me through the dedicated stickied thread on LQ and, also, scripts that are added to current are removed from there to avoid risks of overlap with what is already in current, like Gene explained in another message of this thread. what I don't edit in my unofficial repository for current are the mentions of the removed scripts in the REQUIRED variables in the *.info files of what use these scripts as dependencies: that would be simply non maintenable because simple version changes of these scripts would result in a gazillion of conflicts in these git forks. users of current should learn to ignore these non existant scripts warning (and optionally refer to this list to check what has been removed and why https://cgit.ponce.cc/slackbuilds/refs/heads), still like Gene pointed out in the previous message this to say that the repository you were using as default should already had been probably ok and the "unable to locate" message were normal (I don't think you ever had a repository for 15.0 setup in sbotools). consider also that this mailing list is not actually the proper place to help you in your eventual issues with current as the developer's version of Slackware is not supported by SBo: if you find problems using this unofficial repository for current or any of the SBo's scripts with current, IMHO, the best option is to open a topic on LQ describing the issue and your setup. Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From rcb at beco.cc Mon Mar 11 12:13:58 2024 From: rcb at beco.cc (Ruben Carlo Benante) Date: Mon, 11 Mar 2024 09:13:58 -0300 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 In-Reply-To: References: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> <45ae0ae9-d1b0-4952-adf8-ae52ce905d00@giand.it> <18e2949a282.e802155b2535715.8372097867534222834@beco.cc> <18e2a2040ce.10c7a79e32545886.80972166299494485@beco.cc> Message-ID: <18e2d6d3ec7.d79330882724249.31809054317240023@beco.cc> Hi Jeremi, I did not rebuild clementine after updating protobuf3 at the time. Since this is a prod machine, I won't be able to test. I'm still looking for some guidelines on how developers usually create virtual machines to test. I used virtualbox when I developed for debian, but I don't like this approach anymore. I'm trying to learn LCX, and for slackware it doesn't have templates ready to go, so there is that. Anyway, thanks for your reply. Good to know it works. I'm still waiting for the protobuf3 maintainer reply on the version numbers (previous email) Cordialmente, Ruben -- Dr. Beco AI Researcher ---- On Sun, 10 Mar 2024 19:45:43 -0300 Jeremy Hansen wrote --- Did you rebuild clementine after updating protobuf3? You should be on build 2 of clementine as that includes fixes for the new protobuf3 version. It works fine on my end (I'm the clementine maintainer). Jeremy On Sun, Mar 10, 2024, 1:51?PM Ruben Carlo Benante via SlackBuilds-users wrote: Another thing that may or may not be related: The mp3 player Clementine has stoped working after upgrade. I've returned to grpc-1.48.4 and protobuf3-3.20.1, and after the downgrade Clementine works fine again. Cordialmente, Ruben -- Dr. Beco AI Researcher ---- On Sun, 10 Mar 2024 13:54:41 -0300 Ruben Carlo Benante wrote --- Hello, Is there an error in the version number? Or is it going from 3 to 25 and keep growing further in the next versions? The following names are what it looked like in the past: * Packages/protobuf-2.6.1-x86_64-1_SBo.tgz * Packages/protobuf3-3.17.3-x86_64-1_SBo.tgz * Packages/protobuf3-3.18.1-x86_64-1_SBo.tgz * Packages/protobuf3-3.19.1-x86_64-1_SBo.tgz * Packages/protobuf3-3.19.3-x86_64-1_SBo.tgz * Packages/protobuf3-3.19.4-x86_64-1_SBo.tgz * Packages/protobuf3-3.20.0-x86_64-1_SBo.tgz * Packages/protobuf3-3.20.1-x86_64-1_SBo.tgz * Packages/protobuf3-25.3-x86_64-1_SBo.tgz I'm afraid slackpkg or sbotools or sbopkg will complain if the next comes with something like ?Packages/protobuf3-3.26.0-x86_64-1_SBo.tgz or something as previous format Cordialmente, Ruben -- Dr. Beco AI Researcher ---- On Sat, 02 Mar 2024 18:10:31 -0300 Giancarlo Dess? wrote --- Il 01/03/24 20:35, Willy Sudiarto Raharjo ha scritto: > Hi > > i have just started to work on protobuf3 updates, pushing 2y of works > by upstream since last update. > > However, there are 26 other scripts which depends on protobuf3, listed > here (https://slackbuilds.org/advsearch.php?q=protobuf3&stype=revdep1) > > although we do have CI engine that could help us test whether the new > update will break them or not, it won't help us testing the runtime > issues. Therefore, i would like to ask for help by those who are using > these 26 packages to see if by upgrading protobuf3 and rebuilding them > will have any runtime issues or not. > > I will keep the protobuf3 updates for future public update (like 1-2 > weeks delay) to give others more time to test. > > The protobuf3 update can be seen here > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > > Big thanks in advance > At the moment I tested new protobuf3 in -current, it works for protobuf-c/postgis and qgis After upgrade of protobuf3 the entire tree until qgis was broken, I had to rebuild protobuf-c and then postgis and finally qgis because protobuf is required as first level dependency also by qgis -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Mon Mar 11 12:51:05 2024 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Mon, 11 Mar 2024 05:51:05 -0700 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 In-Reply-To: <18e2d6d3ec7.d79330882724249.31809054317240023@beco.cc> References: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> <45ae0ae9-d1b0-4952-adf8-ae52ce905d00@giand.it> <18e2949a282.e802155b2535715.8372097867534222834@beco.cc> <18e2a2040ce.10c7a79e32545886.80972166299494485@beco.cc> <18e2d6d3ec7.d79330882724249.31809054317240023@beco.cc> Message-ID: If you update just a single package without checking other programs you have installed, you could continue to run into issues like this. We ensured the clementine update was pushed in the same public update as protobuf3 to make sure that the repo continued to work. This week we're working on an SQLAlchemy update and another package I maintain (sickchill) needs to have an update to work (I actually have to remove a patch that allowed it to still work with the older version). If you update sickchill without updating SQLAlchemy, sickchill will break, just as if you update SQLAlchemy without updating sickchill, sickchill will break. If you do pick and choose which updates to make without doing everything and something is broken, try rebuilding it to see if it fixes it. As for the versioning, this is the version from upstream. On SBo, it hadn't seen an update in almost two years while upstream kept chugging along. Also, sometimes upstream will change how they version things, so you might see big jumps at times. The tools don't care about jumps in versions, in fact, they don't even care what the version number is, just that the version and/or build number is different than the current version or build number. This is why there is no issue using commit IDs as versions or throwing dates or kernel versions into the version. Jeremy On Mon, Mar 11, 2024, 5:14?AM Ruben Carlo Benante wrote: > Hi Jeremi, > > I did not rebuild clementine after updating protobuf3 at the time. > Since this is a prod machine, I won't be able to test. > > I'm still looking for some guidelines on how developers usually create > virtual machines to test. I used virtualbox when I developed for debian, > but I don't like this approach anymore. I'm trying to learn LCX, and for > slackware it doesn't have templates ready to go, so there is that. > > Anyway, thanks for your reply. Good to know it works. I'm still waiting > for the protobuf3 maintainer reply on the version numbers (previous email) > > Cordialmente, > > Ruben > > -- > Dr. Beco > AI Researcher > > > > > ---- On Sun, 10 Mar 2024 19:45:43 -0300 *Jeremy Hansen > >* wrote --- > > Did you rebuild clementine after updating protobuf3? You should be on > build 2 of clementine as that includes fixes for the new protobuf3 version. > > It works fine on my end (I'm the clementine maintainer). > > Jeremy > > On Sun, Mar 10, 2024, 1:51?PM Ruben Carlo Benante via SlackBuilds-users < > slackbuilds-users at slackbuilds.org> wrote: > > > Another thing that may or may not be related: > > The mp3 player Clementine has stoped working after upgrade. > > I've returned to grpc-1.48.4 and protobuf3-3.20.1, and after the downgrade > Clementine works fine again. > > Cordialmente, > Ruben > > -- > Dr. Beco > AI Researcher > > > > > ---- On Sun, 10 Mar 2024 13:54:41 -0300 *Ruben Carlo Benante >* wrote --- > > Hello, > > Is there an error in the version number? Or is it going from 3 to 25 and > keep growing further in the next versions? > > The following names are what it looked like in the past: > > * Packages/protobuf-2.6.1-x86_64-1_SBo.tgz > * Packages/protobuf3-3.17.3-x86_64-1_SBo.tgz > * Packages/protobuf3-3.18.1-x86_64-1_SBo.tgz > * Packages/protobuf3-3.19.1-x86_64-1_SBo.tgz > * Packages/protobuf3-3.19.3-x86_64-1_SBo.tgz > * Packages/protobuf3-3.19.4-x86_64-1_SBo.tgz > * Packages/protobuf3-3.20.0-x86_64-1_SBo.tgz > * Packages/protobuf3-3.20.1-x86_64-1_SBo.tgz > * Packages/protobuf3-25.3-x86_64-1_SBo.tgz > > > I'm afraid slackpkg or sbotools or sbopkg will complain if the next comes > with something like > > Packages/protobuf3-3.26.0-x86_64-1_SBo.tgz or something as previous format > > > Cordialmente, > Ruben > > -- > Dr. Beco > AI Researcher > > > > > ---- On Sat, 02 Mar 2024 18:10:31 -0300 *Giancarlo Dess? >* wrote --- > > Il 01/03/24 20:35, Willy Sudiarto Raharjo ha scritto: > > Hi > > > > i have just started to work on protobuf3 updates, pushing 2y of works > > by upstream since last update. > > > > However, there are 26 other scripts which depends on protobuf3, listed > > here (https://slackbuilds.org/advsearch.php?q=protobuf3&stype=revdep1) > > > > although we do have CI engine that could help us test whether the new > > update will break them or not, it won't help us testing the runtime > > issues. Therefore, i would like to ask for help by those who are using > > these 26 packages to see if by upgrading protobuf3 and rebuilding them > > will have any runtime issues or not. > > > > I will keep the protobuf3 updates for future public update (like 1-2 > > weeks delay) to give others more time to test. > > > > The protobuf3 update can be seen here > > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > > > > Big thanks in advance > > > At the moment I tested new protobuf3 in -current, it works for > protobuf-c/postgis and qgis > > After upgrade of protobuf3 the entire tree until qgis was broken, I had > to rebuild protobuf-c and then postgis and finally qgis because protobuf > is required as first level dependency also by qgis > > -- > > ********************************************************* > Giancarlo Dess? > https://www.giand.it > https://github.com/giandex > > Slackware Linux... because it works! > ********************************************************* > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.public at protonmail.com Mon Mar 11 21:51:59 2024 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 11 Mar 2024 21:51:59 +0000 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: References: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> <669f47e6-359a-40fa-8604-a89328063db6@cgpp.com> Message-ID: <9HT5ZTDdkUBg6JiWmKgBLYma8eZgLSsrJHFGqqub5bslEII1-Wnym_A0EFW9ZqtJNLVJEDntARQ4UpTyfodK5Z8DL5PuoN0nRAZo3TM9DNs=@protonmail.com> If using current you shouldn't overwrite stock Slackware packages with those from SBo like you did. You need to go back and reinstall the Slackware packages. > The whole error message: (Had to use --reinstall because in the meantime > I got in installed, somehow.) > > # sboinstall --reinstall python3-build > python3-build (python3-build-1.1.1-x86_64-1_SBo) is already installed. > Do you want to reinstall from SBo? [n] y Do not answer "y" here! > Unable to locate python3-build in the SlackBuilds.org tree. > Do you want to ignore it and continue? [n] > > So I'm guessing I installed python3-build from the 15.0 SBo repo, and > it's not finding it now because I switched to Ponce's repo. (Curiously, > also didn't find it either in Ponce's repo or in slackware64-current) > > One problem with that explanation: I was getting the error even when I > still had the 15.0 SBo repo dialed in. > > Am making good headway with sbopkg so will set this aside for now. Will > be more methodical going forward so should have more details to report > if it comes up again. > > BTW I hadn't considered that packages can migrate from Ponce's SBo repo > to -current. Will keep this in mind. > > thanks for the help! > > Judah > > From milgram at cgpp.com Tue Mar 12 02:12:38 2024 From: milgram at cgpp.com (J. Milgram) Date: Mon, 11 Mar 2024 22:12:38 -0400 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: <9HT5ZTDdkUBg6JiWmKgBLYma8eZgLSsrJHFGqqub5bslEII1-Wnym_A0EFW9ZqtJNLVJEDntARQ4UpTyfodK5Z8DL5PuoN0nRAZo3TM9DNs=@protonmail.com> References: <493bf19c-96e9-4147-a61b-88fd45685ba1@cgpp.com> <669f47e6-359a-40fa-8604-a89328063db6@cgpp.com> <9HT5ZTDdkUBg6JiWmKgBLYma8eZgLSsrJHFGqqub5bslEII1-Wnym_A0EFW9ZqtJNLVJEDntARQ4UpTyfodK5Z8DL5PuoN0nRAZo3TM9DNs=@protonmail.com> Message-ID: Thanks for the reply. On 3/11/24 17:51, Erich Ritz via SlackBuilds-users wrote: > If using current you shouldn't overwrite stock Slackware packages with those from SBo like you did. You need to go back and reinstall the Slackware packages. You may be right. It would be interesting to go back and try that. But for whatever reason, sbopkg got everything installed and it's all working, so for now I'm going to declare victory. >> The whole error message: (Had to use --reinstall because in the meantime >> I got in installed, somehow.) >> >> # sboinstall --reinstall python3-build >> python3-build (python3-build-1.1.1-x86_64-1_SBo) is already installed. >> Do you want to reinstall from SBo? [n] y > Do not answer "y" here! Right. I only answered "y" to trigger the error message from sboinstall: >> Unable to locate python3-build in the SlackBuilds.org tree. >> Do you want to ignore it and continue? [n] ... and here I answered "n" regards Judah From milgram at cgpp.com Tue Mar 12 02:28:52 2024 From: milgram at cgpp.com (J. Milgram) Date: Mon, 11 Mar 2024 22:28:52 -0400 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: References: <5o7p9122-7793-5372-3r83-s5op94nqn2pq@hfrlbherfc.bet.hx> Message-ID: Thanks Matteo, all very interesting. So I was probably installing correct -current SBo's right from the beginning. I wonder if sbotools looks at /etc/slackware-version to decide which repo to default to. Good advice on going to LQ for questions about -current (and sbotools too, I guess.) thanks again all! As mentioned in other post, everything's installed now, and running properly. r/ Judah On 3/11/24 07:06, Matteo Bernardini wrote: > hi, > > just for testing I downloaded, packaged and installed sbotools from here > > https://slackbuilds.org/repository/15.0/system/sbotools/ > > following what's written on the documentation > > https://pink-mist.github.io/sbotools/documentation/ > > I run "sbosnap fetch" to download the repository and I saw that in > /usr/sbo/repo what is downloaded by default the unofficial repository > for current that I maintain (check /usr/sbo/repo/.git/config) that > shouldn't be used for 15.0 (maybe some other default should be set in > the package on SBo) but should help who's running current. > > the reason why it should help who's running current is that it > contains patches for the broken scripts that don't build on current > and that are reported to me through the dedicated stickied thread on > LQ and, also, scripts that are added to current are removed from there > to avoid risks of overlap with what is already in current, like Gene > explained in another message of this thread. > > what I don't edit in my unofficial repository for current are the > mentions of the removed scripts in the REQUIRED variables in the > *.info files of what use these scripts as dependencies: that would be > simply non maintenable because simple version changes of these scripts > would result in a gazillion of conflicts in these git forks. > > users of current should learn to ignore these non existant scripts > warning (and optionally refer to this list to check what has been > removed and why https://cgit.ponce.cc/slackbuilds/refs/heads), still > like Gene pointed out in the previous message > > this to say that the repository you were using as default should > already had been probably ok and the "unable to locate" message were > normal (I don't think you ever had a repository for 15.0 setup in > sbotools). > > consider also that this mailing list is not actually the proper place > to help you in your eventual issues with current as the developer's > version of Slackware is not supported by SBo: if you find problems > using this unofficial repository for current or any of the SBo's > scripts with current, IMHO, the best option is to open a topic on LQ > describing the issue and your setup. > > Matteo > > _______________________________________________ > 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 mrvladislavovich at gmail.com Tue Mar 12 05:43:04 2024 From: mrvladislavovich at gmail.com (myrequiem) Date: Tue, 12 Mar 2024 09:43:04 +0400 Subject: [Slackbuilds-users] qt6 build error with new protobuf3-25.3 (Slackware 15.0 x86_64) Message-ID: <67ea0e6b-415d-402e-9cb3-610453c1edd0@gmail.com> Hello. After updating protobuf3-25.3, building package qt6 gives an error. The old protobuf3 package had 17 header files, the new package has only 5, which are located in /usr/include/google/protobuf/stubs/ This is why the qt6 assembly complains that there are not enough headers: ERROR qt-everywhere-src-6.5.2/qtgrpc/src/tools/qtprotoccommon/generatorbase.cpp: fatal error: 'google/protobuf/stubs/logging.h' file not found #include The same with the header google/protobuf/stubs/macros.h Even if you add these header files from the old protobuf3 package, the build still fails -------------- next part -------------- An HTML attachment was scrubbed... URL: From tonus1 at free.fr Tue Mar 12 06:32:25 2024 From: tonus1 at free.fr (Tonus) Date: Tue, 12 Mar 2024 07:32:25 +0100 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: References: <5o7p9122-7793-5372-3r83-s5op94nqn2pq@hfrlbherfc.bet.hx> Message-ID: Hi You wrote your repo was initially 15.0+ This "+" tells it's -current and not stable, that's why the now official packages are told missing. Regards -- Tonus From slackinfo at slackwarelinux.se Tue Mar 12 08:30:25 2024 From: slackinfo at slackwarelinux.se (slackinfo at slackwarelinux.se) Date: Tue, 12 Mar 2024 09:30:25 +0100 Subject: [Slackbuilds-users] eclipse-platform slackbuild In-Reply-To: <9e40317f-3e4f-2be9-a625-ba71dbee8c45@slackware.uk> References: <9e40317f-3e4f-2be9-a625-ba71dbee8c45@slackware.uk> Message-ID: If anyone should want to download the latest version, it can be found here https://www.eclipse.org/downloads/packages/release/2023-12/r and as already pointed out, it requires a newer version of JAVA... /MDKDIO On 2024-03-09 22:28, B. Watson wrote: > On Sat, 9 Mar 2024, Tim Dickson via SlackBuilds-users wrote: > >> the download link for the source?/binary for this package appears not >> be be available any more. >> newer versions are available, but they require java 17 or higher. >> regards, Tim > > If you just want to build the existing version, there's a copy of the > source > in the SBo source archive, here: > > https://slackware.uk/sbosrcarch/by-md5/4/8/48253adbb219851359613344d942d934/eclipse-platform-4.19-linux-gtk-x86_64.tar.gz > _______________________________________________ > 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 matteo.bernardini at gmail.com Tue Mar 12 09:59:20 2024 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 12 Mar 2024 10:59:20 +0100 Subject: [Slackbuilds-users] qt6 build error with new protobuf3-25.3 (Slackware 15.0 x86_64) In-Reply-To: <67ea0e6b-415d-402e-9cb3-610453c1edd0@gmail.com> References: <67ea0e6b-415d-402e-9cb3-610453c1edd0@gmail.com> Message-ID: Il giorno mar 12 mar 2024 alle ore 06:43 myrequiem < mrvladislavovich at gmail.com> ha scritto: > Hello. After updating protobuf3-25.3, building package qt6 gives an error. > The > old protobuf3 package had 17 header files, the new package has only 5, > which > are located in > /usr/include/google/protobuf/stubs/ > This is why the qt6 assembly complains that there are not enough headers: > > ERROR > qt-everywhere-src-6.5.2/qtgrpc/src/tools/qtprotoccommon/generatorbase.cpp: > fatal error: 'google/protobuf/stubs/logging.h' file not found > #include > > The same with the header google/protobuf/stubs/macros.h > > Even if you add these header files from the old protobuf3 package, the > build > still fails > it seems that a component, qtgrpc, added with qt6-6.5.x, uses some protobuf deprecated headers if it find this installed: there are some specific patches upstream fot qt-7.x (!!!) that I just backported to 6.5.2 https://git.slackbuilds.org/slackbuilds/commit/?id=87b5f24 Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net Fri Mar 15 14:00:11 2024 From: for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net (Vladimir Nikishkin) Date: Fri, 15 Mar 2024 22:00:11 +0800 Subject: [Slackbuilds-users] coeurl fails to build with new spdlog Message-ID: <87r0gbvbj5.fsf@laptop.lockywolf.net> Hello, everyone. spdlog has been recently updated, and now my coeurl build fails to build Does anybody know how to overcome this? [1/2] ccache c++ -Ilibcoeurl.so.0.3.p -I. -I.. -I../include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra -Wpedantic -std=c++17 -g -fPIC -pthread -DSPDLOG_SHARED_LIB -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -MD -MQ libcoeurl.so.0.3.p/lib_client.cpp.o -MF libcoeurl.so.0.3.p/lib_client.cpp.o.d -o libcoeurl.so.0.3.p/lib_client.cpp.o -c ../lib/client.cpp FAILED: libcoeurl.so.0.3.p/lib_client.cpp.o ccache c++ -Ilibcoeurl.so.0.3.p -I. -I.. -I../include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra -Wpedantic -std=c++17 -g -fPIC -pthread -DSPDLOG_SHARED_LIB -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -MD -MQ libcoeurl.so.0.3.p/lib_client.cpp.o -MF libcoeurl.so.0.3.p/lib_client.cpp.o.d -o libcoeurl.so.0.3.p/lib_client.cpp.o -c ../lib/client.cpp In file included from /usr/include/fmt/format.h:49, from /usr/include/fmt/ostream.h:21, from /usr/include/spdlog/fmt/ostr.h:20, from ../lib/client.cpp:1: /usr/include/fmt/core.h: In instantiation of ?constexpr fmt::v10::detail::value fmt::v10::detail::make_arg(T&) [with bool PACKED = true; Context = fmt::v10::basic_format_context; T = CURLcode; typename std::enable_if::type = 0]?: /usr/include/fmt/core.h:1842:51: required from ?constexpr fmt::v10::format_arg_store::format_arg_store(T& ...) [with T = {std::__cxx11::basic_string, std::allocator >, CURLcode, char [256], long int}; Context = fmt::v10::basic_format_context; Args = {std::__cxx11::basic_string, std::allocator >, CURLcode, char [256], long int}]? /usr/include/fmt/core.h:1860:18: required from ?constexpr fmt::v10::format_arg_store::type>::type ...> fmt::v10::make_format_args(T& ...) [with Context = fmt::v10::basic_format_context; T = {std::__cxx11::basic_string, std::allocator >, CURLcode, char [256], long int}]? /usr/include/spdlog/logger.h:374:75: required from ?void spdlog::logger::log_(spdlog::source_loc, spdlog::level::level_enum, spdlog::string_view_t, Args&& ...) [with Args = {std::__cxx11::basic_string, std::allocator >&, CURLcode&, char (&)[256], long int&}; spdlog::string_view_t = fmt::v10::basic_string_view]? /usr/include/spdlog/logger.h:90:13: required from ?void spdlog::logger::log(spdlog::source_loc, spdlog::level::level_enum, fmt::v10::format_string, Args&& ...) [with Args = {std::__cxx11::basic_string, std::allocator >&, CURLcode&, char (&)[256], long int&}; fmt::v10::format_string = fmt::v10::basic_format_string, std::allocator >&, CURLcode&, char (&)[256], long int&>]? /usr/include/spdlog/logger.h:96:12: required from ?void spdlog::logger::log(spdlog::level::level_enum, fmt::v10::format_string, Args&& ...) [with Args = {std::__cxx11::basic_string, std::allocator >&, CURLcode&, char (&)[256], long int&}; fmt::v10::format_string = fmt::v10::basic_format_string, std::allocator >&, CURLcode&, char (&)[256], long int&>]? /usr/include/spdlog/logger.h:146:12: required from ?void spdlog::logger::trace(fmt::v10::format_string, Args&& ...) [with Args = {std::__cxx11::basic_string, std::allocator >&, CURLcode&, char (&)[256], long int&}; fmt::v10::format_string = fmt::v10::basic_format_string, std::allocator >&, CURLcode&, char (&)[256], long int&>]? ../lib/client.cpp:358:27: required from here /usr/include/fmt/core.h:1600:63: error: ?fmt::v10::detail::type_is_unformattable_for _? has incomplete type 1600 | type_is_unformattable_for _; | ^ /usr/include/fmt/core.h:1604:7: error: static assertion failed: Cannot format an argument. To make type T formattable provide a formatter specialization: https://fmt.dev/latest/api.html#udt 1604 | formattable, | ^~~~~~~~~~~ /usr/include/fmt/core.h:1604:7: note: ?formattable? evaluates to false ninja: build stopped: subcommand failed. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From matteo.bernardini at gmail.com Fri Mar 15 14:22:25 2024 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 15 Mar 2024 15:22:25 +0100 Subject: [Slackbuilds-users] coeurl fails to build with new spdlog In-Reply-To: <87r0gbvbj5.fsf@laptop.lockywolf.net> References: <87r0gbvbj5.fsf@laptop.lockywolf.net> Message-ID: Il giorno ven 15 mar 2024 alle ore 15:09 Vladimir Nikishkin < for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net> ha scritto: > Hello, everyone. > > spdlog has been recently updated, and now my coeurl build fails to build > > Does anybody know how to overcome this? > > [1/2] ccache c++ -Ilibcoeurl.so.0.3.p -I. -I.. -I../include > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch > -Wnon-virtual-dtor -Wextra -Wpedantic -std=c++17 -g -fPIC -pthread > -DSPDLOG_SHARED_LIB -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -MD -MQ > libcoeurl.so.0.3.p/lib_client.cpp.o -MF > libcoeurl.so.0.3.p/lib_client.cpp.o.d -o > libcoeurl.so.0.3.p/lib_client.cpp.o -c ../lib/client.cpp > FAILED: libcoeurl.so.0.3.p/lib_client.cpp.o > ccache c++ -Ilibcoeurl.so.0.3.p -I. -I.. -I../include > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch > -Wnon-virtual-dtor -Wextra -Wpedantic -std=c++17 -g -fPIC -pthread > -DSPDLOG_SHARED_LIB -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -MD -MQ > libcoeurl.so.0.3.p/lib_client.cpp.o -MF > libcoeurl.so.0.3.p/lib_client.cpp.o.d -o > libcoeurl.so.0.3.p/lib_client.cpp.o -c ../lib/client.cpp > In file included from /usr/include/fmt/format.h:49, > from /usr/include/fmt/ostream.h:21, > from /usr/include/spdlog/fmt/ostr.h:20, > from ../lib/client.cpp:1: > /usr/include/fmt/core.h: In instantiation of ?constexpr > fmt::v10::detail::value fmt::v10::detail::make_arg(T&) [with bool > PACKED = true; Context = fmt::v10::basic_format_context char>; T = CURLcode; typename std::enable_if::type > = 0]?: > /usr/include/fmt/core.h:1842:51: required from ?constexpr > fmt::v10::format_arg_store::format_arg_store(T& ...) [with T > = {std::__cxx11::basic_string, > std::allocator >, CURLcode, char [256], long int}; Context = > fmt::v10::basic_format_context; Args = > {std::__cxx11::basic_string, > std::allocator >, CURLcode, char [256], long int}]? > /usr/include/fmt/core.h:1860:18: required from ?constexpr > fmt::v10::format_arg_store std::remove_reference::type>::type ...> fmt::v10::make_format_args(T& > ...) [with Context = fmt::v10::basic_format_context char>; T = {std::__cxx11::basic_string, > std::allocator >, CURLcode, char [256], long int}]? > /usr/include/spdlog/logger.h:374:75: required from ?void > spdlog::logger::log_(spdlog::source_loc, spdlog::level::level_enum, > spdlog::string_view_t, Args&& ...) [with Args = > {std::__cxx11::basic_string, > std::allocator >&, CURLcode&, char (&)[256], long int&}; > spdlog::string_view_t = fmt::v10::basic_string_view]? > /usr/include/spdlog/logger.h:90:13: required from ?void > spdlog::logger::log(spdlog::source_loc, spdlog::level::level_enum, > fmt::v10::format_string, Args&& ...) [with Args = > {std::__cxx11::basic_string, > std::allocator >&, CURLcode&, char (&)[256], long int&}; > fmt::v10::format_string = fmt::v10::basic_format_string std::__cxx11::basic_string, > std::allocator >&, CURLcode&, char (&)[256], long int&>]? > /usr/include/spdlog/logger.h:96:12: required from ?void > spdlog::logger::log(spdlog::level::level_enum, fmt::v10::format_string ...>, Args&& ...) [with Args = {std::__cxx11::basic_string std::char_traits, std::allocator >&, CURLcode&, char (&)[256], > long int&}; fmt::v10::format_string = > fmt::v10::basic_format_string std::char_traits, std::allocator >&, CURLcode&, char (&)[256], > long int&>]? > /usr/include/spdlog/logger.h:146:12: required from ?void > spdlog::logger::trace(fmt::v10::format_string, Args&& ...) [with > Args = {std::__cxx11::basic_string, > std::allocator >&, CURLcode&, char (&)[256], long int&}; > fmt::v10::format_string = fmt::v10::basic_format_string std::__cxx11::basic_string, > std::allocator >&, CURLcode&, char (&)[256], long int&>]? > ../lib/client.cpp:358:27: required from here > /usr/include/fmt/core.h:1600:63: error: > ?fmt::v10::detail::type_is_unformattable_for _? has > incomplete type > 1600 | type_is_unformattable_for _; > | ^ > /usr/include/fmt/core.h:1604:7: error: static assertion failed: Cannot > format an argument. To make type T formattable provide a formatter > specialization: https://fmt.dev/latest/api.html#udt > 1604 | formattable, > | ^~~~~~~~~~~ > /usr/include/fmt/core.h:1604:7: note: ?formattable? evaluates to false > ninja: build stopped: subcommand failed. > > -- > Your sincerely, > Vladimir Nikishkin (MiEr, lockywolf) > (Laptop) > > Hi Vladimir, that happens because spdlog has been build against fmt >= 10.x: I found this patch in the archlinux repo that let coeurl build also in this situation https://nheko.im/nheko-reborn/coeurl/-/commit/831e2ee8e9cf08ea1ee9736cde8370f9d0312abc.patch Matteo P.S. please use sane email addresses when you write to the mailing list, thanks in advance! ;-) -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Mar 16 03:30:23 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 16 Mar 2024 10:30:23 +0700 Subject: [Slackbuilds-users] Updates - 20240316.1 Message-ID: <9c649c72-6b74-4266-a4be-0545d6281a2b@slackbuilds.org> Sat Mar 16 03:23:02 UTC 2024 academic/Gridcoin-Research: Updated for version 5.4.7.0 academic/ITK: Fix build. academic/R: update 4.3.3 accessibility/wgetpaste: Updated for version 2.34. audio/PAmix: Added (pulseaudio mixer in c++). audio/audacity: Note incompatibility in the README. audio/milkytracker: Fix conflict with rtmidi. desktop/rss-guard: updated for version 4.6.4 desktop/rss-guard: updated for version 4.6.6 development/astyle: Updated for version 3.4.13. development/aws-cdk: Updated for version 2.132.0. development/bcpp: Updated for version 20240111. development/composer: Updated for version 2.7.2 development/cosmocc: Updated for version 3.3.2. development/f2c: Updated for version 20240130. development/gitlab-cli: Added (Gitlab CLI). development/google-go-lang: Updated for version 1.22.1. development/ispc: Added (Intel Compiler). development/mawk: Updated for version 1.3.4_20240123. development/php82: Updated for version 8.2.17 development/rizin: Updated for version 0.7.2 development/sbcl: Updated for version 2.4.2 development/tea: updated for version 62.4.0 development/vscode-bin: Updated for version 1.87.1. development/xa: Updated for version 2.4.1. development/xmake: Updated for version 2.8.8. games/atari800: Updated for version 5.2.0. games/jg-geolith: Updated for version 0.2.1. games/xroar: Updated for version 1.5.4. gis/OTB-legacy: Added (Legacy version of OTB). gis/OTB: Updated for version 9.0.0. gis/google-earth: Updated for version 7.3.6.9796. graphics/embree: Add ISPC support. ham/hackrf: Updated for version 2024.02.1. ham/qlog: Updated for version 0.33.1. ham/rtl_433: Added (decode radio transmissions). libraries/grpc: Update for 1.62.1 libraries/libpaper: Updated for version 2.2.5. libraries/libsvm: Added (SVM library). libraries/libtommath: Updated for version 1.2.1. libraries/libunibreak: Updated for version 6.1. libraries/muparserx: Added (C++ library for parsing expressions). libraries/plog: Added (C++ logging library). libraries/qt6: Backport upstream patches for the newer protobuf. libraries/qt6keychain: Added (QT Keychain). libraries/re2: Update for 2024_03_01 libraries/rtmidi: Added (API for realtime MIDI). libraries/tree-sitter: Updated for version 0.22.1 libraries/zziplib: Updated for version 0.13.74. misc/doclifter: Updated for version 2.21. misc/rbutil: Fix FTBFS. misc/vttest: Updated for version 2.7.20240218. multimedia/pipe-viewer: Updated for version 0.5.0. multimedia/plexmediaserver: Updated for version 1.40.1.8227_c0dd5a73e. network/Electrum: Updated for version 4.5.4. network/amfora-bin: Added (Gemini browser client). network/brave-browser: update 1.63.174 network/discord: Version bump to 0.0.45 network/dnsproxy-bin: Updated for version 0.66.0. network/gemget-bin: Added (CLI for gemini protocol). network/go-sendxmpp: Updated for version 0.8.4. network/jitsi-meet-desktop: Updated for version 2024.3.0 network/rclone: update 1.66.0 network/signal-desktop: Updated for version 7.2.0. network/tailscale: update 1.62.0 network/vivaldi: Updated for version 6.6.3271.50. network/yt-dlp: Updated for version 2024.03.10. network/zabbix_agentd: Updated for version 6.4.11. network/zabbix_frontend: Updated for version 6.4.11. network/zabbix_java_gateway: Updated for version 6.4.11. network/zabbix_proxy: Updated for version 6.4.11. network/zabbix_server: Updated for version 6.4.11. office/LibreOffice: Updated for version 24.2.1.2 office/calibre-bin: Updated for version 7.7.0. office/keepassxc: Updated for version 2.7.7. office/sent: Update email. perl/perl-http-daemon: Updated for version 6.16. perl/perl-http-message: Updated for version 6.45. python/Kallithea: Patched for python3-dateutil python/Kallithea: Patches for SQLAlchemy 2, and Bleach bug python/SQLAlchemy-legacy: Added (Legacy version of SQLAlchemy). python/argon2-cffi-bindings: Removed (renamed to python3-argon2-cffi-bindings) python/argon2-cffi: Removed (renamed to python3-argon2-cffi) python/buildbot: REQUIRES update python/cryptography: Updated for version 42.0.5. python/entrypoints: Removed (renamed to python3-entrypoints) python/hg-git: reverted to version 1.0.5, because mercurial is too old python/mypy: Updated for version 1.9.0. python/nest_asyncio: Removed (renamed to python3-nest_asyncio) python/objgraph: Updated for version 3.6.1. python/pyOpenSSL: Updated for versin 24.1.0. python/python-zipp: Updated for version 3.18.1. python/python3-alembic: README update python/python3-comm: Update for 0.2.2 python/python3-grpcio: Update for 1.62.1 python/python3-hatch_jupyter_builder: Update for 0.9.1 python/python3-meson-opt: Updated for version 1.4.0. python/python3-plotly: Update for 5.20.0 python/python3-pydantic: Updated for version 2.6.4. python/python3-pydocstyle: Update for 6.3.0 python/python3-pykeepass: Fix missing kdbx_parsing submodule, +use built-in isoformat support python/python3-pypandoc: Update for 1.13 python/python3-pytest: Version bump to 8.1.1 python/python3-setuptools-opt: Updated for version 69.2.0. python/python3-types-python-dateutil: Update for 2.8.19.20240311 python/python3-wheel: Updated for version 0.43.0. system/86box: Updated for version 4.1. system/Iosevka-aile: Updated for version 29.0.1. system/Iosevka-etoile: Updated for version 29.0.1. system/backintime: Updated for version 1.4.3. system/containerd: Updated for version 1.7.14. system/cronie: Updated for version 1.7.1. system/ded: Updated for version 20230122. system/docker-buildx: Updated for versino 0.13.1. system/docker-compose: Updated for version 2.24.7 system/dosbox-x: updated for version 2024.03.01 system/edk2-ovmf: Updated for version 202402. system/fzy: Update email. system/google-chrome-the-latest: Updated for version 3.2 system/joyce: Updated for version 2.4.2. system/kiwix-tools-bin: Added (offline wikipedia). system/lnav: Updated for version 0.12.0. system/locust: Updated for version 2.24.0. system/mmv: Updated for version 2.6. system/nvidia-legacy390-kernel: Fix build on i586. system/pam_ssh_agent_auth: Updated for version 0.10.4. system/prometheus: Updated to version 2.50.1 system/redis-py: updated for version 5.0.3 system/renameutils: Added (file renaming utilities). system/sarasa-gothic: Updated for version 1.0.6. system/sbpkg: Added (SBo package manager). system/sdl2trs: Added (TRS-80 emulation). system/sdltrs: Use SDL1 only. system/smenu: Added (dialog system). system/worker: Updated for version 5.0.2 system/yubico-piv-tool: Updated for version 2.5.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From antonioleal at yahoo.com Sun Mar 17 21:32:30 2024 From: antonioleal at yahoo.com (Antonio Leal) Date: Sun, 17 Mar 2024 21:32:30 +0000 Subject: [Slackbuilds-users] Segmentation Fault help needed References: Message-ID: Hi list, I need some C expert opinion. Slackbuild bbcsdl "console edition" is causing a segmentation fault on slackware, works well on Debian, which is annoying :-| https://github.com/rtrussell/BBCSDL/commit/6f12425251b72974268a6fb82e26382c2ee1acc0 is the one with the problem. (previous release https://github.com/rtrussell/BBCSDL/commit/b501c7856904be335bf891879b1f2329a1a2bfac was working well.) reproduction: 1) wget https://github.com/rtrussell/BBCSDL/archive/6f12425/BBCSDL-6f12425251b72974268a6fb82e26382c2ee1acc0.tar.gz 2) tar xvfz BBCSDL-6f12425251b72974268a6fb82e26382c2ee1acc0.tar.gz 3) mv BBCSDL-6f12425251b72974268a6fb82e26382c2ee1acc0 BBCSDL 4) cd BBCSDL/console/linux 5) make? # compiles 1 less than 20 seconds.. 6) ./bbcbasic? # bang! :-( I tried -Os, gcc-13.2.0,... to no success... For now I'm removing console support from the SlackBuild, but any help is welcome. Ant?nio From 414N at slacky.it Mon Mar 18 21:14:17 2024 From: 414N at slacky.it (414N) Date: Mon, 18 Mar 2024 22:14:17 +0100 Subject: [Slackbuilds-users] Segmentation Fault help needed In-Reply-To: References: Message-ID: Hello Antonio! TL;DR: the error seems to be caused by the MAP_FIXED mmap flag used in bbccon.c:1728. You can find a patch attached that solves that issue, but I cannot guarantee that the program will still work as intended with it. The program seems to really want to allocate memory at a specific address and removing that flag breaks that assumption. The steps I followed to determine the source of the issue: 1. modify the src/console/makefile file to change every optimization flag (i.e. gcc "-O2" or "-Os") to debug flags ("-O0 -g" for gcc, "-g" for nasm) and removing any stripping instruction ("-Wl,-s") 2. recompile and run via gdb: cd console/linux make -f makefile gdb ./bbcbasic (gdb) run Starting program: /tmp/BBCSDL/console/linux/bbcbasic [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x000 0x00000001003fffff in ?? () (gdb) bt #0 0x00000001003fffff in ?? () #1 0x0000000000000001 in ?? () #2 0x0000000103ae75f6 in ?? () #3 0x0000000000000000 in ?? () (gdb) 3. as can be seen from the gdb backtrace (bt) output, no useful information can be discerned 4. another way to catch the problem is by stepping one instruction at a time from the main() function entrypoint (hoping that the error spawns early in the program code ^_^), so, back in gdb (starting another session)[1]: (gdb) run Starting program: /tmp/BBCSDL/console/linux/bbcbasic [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Breakpoint 1, main (argc=1, argv=0x7fffffffdf68) at ../../src /bbccon.c:1683 1683 int exitcode = 0 ; (gdb) next 1684 void *immediate = NULL ; (gdb) 1715 pthread_t hThread = 0 ; (gdb) 1717 platform = 1 ; (gdb) 1719 void *base = NULL ; (gdb) 1721 while ((MaximumRAM >= MINIMUM_RAM) && (NULL == (base = mymap (MaximumRAM)))) (gdb) 1726 if (base != NULL) (gdb) 1727 userRAM = mmap (base, MaximumRAM, PROT_EXEC | PROT_READ | PROT_WRITE, (gdb) Program received signal SIGSEGV, Segmentation fault. 0x00000001003fffff in ?? () (gdb) As can be seen, the SIGSEGV occurred after trying to step over the mmap function call in bbccon.c at line 1727. By inspecting it in the source file and by looking at the "mmap" man page, one can see that: - the MAP_FIXED flag needs some care to be correctly used; - the SIGSEGV signal can be the result of "Attempted write into a region mapped as read-only." I think this means that the "base" address returned by the "mymap" function does not work well in the following "mmap" call with the MAP_FIXED flag, probably due to some memory management kernel settings that are different between Slackware and Debian, like "/proc/sys/vm/mmap_min_addr" (if I remember correctly). Hope to be helpful! -- Alan Alberghini SBo clone: https://github.com/414n/slackbuilds.org [1]: after the first "next" instruction no command is echoed in the following (gdb) prompts because I just pressed ENTER on the keyboard to repeat the last command entered -------------- next part -------------- A non-text attachment was scrubbed... Name: bbcsdl-no-SIGSEGV.patch Type: text/x-patch Size: 330 bytes Desc: not available URL: From sbo at linuxgalaxy.org Tue Mar 19 01:57:44 2024 From: sbo at linuxgalaxy.org (KB_SBo) Date: Tue, 19 Mar 2024 01:57:44 +0000 Subject: [Slackbuilds-users] Mumble gtav plugin compile error on Slackware 32-bit Message-ID: <6fa24cb1-cdf9-4699-b6a4-cc3ab43036c2@linuxgalaxy.org> Hello Seems there was some sort of omission or regression (or "Who still uses 32-bit?") when the gtav plugin is compiled for mumble. This was fixed previously in mumble-master but somehow did not end up in mumble-1.4.287 I've posted the fix to my branch for the next update. However, other than a qemu VM (not set up for audio), I'm not able to test fully. https://github.com/mumble-voip/mumble/issues/5849 https://github.com/mumble-voip/mumble/pull/5850 ------------8<------------ From 13c051b36b387356815cff5d685bc628b74ba136 Mon Sep 17 00:00:00 2001 From: Davide Beatrici Date: Thu, 1 Sep 2022 23:32:57 +0200 Subject: [PATCH] FIX(positional-audio): Force 8 bytes alignment for CCameraAngles in GTAV plugin https://en.cppreference.com/w/cpp/language/alignas This fixes compilation when the implicit alignment is not 8 bytes. It can be the case with 32 bit targets. --- plugins/gtav/structs.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/gtav/structs.h b/plugins/gtav/structs.h index 2829dc11e1..0e4f76edab 100644 --- a/plugins/gtav/structs.h +++ b/plugins/gtav/structs.h @@ -118,7 +118,7 @@ struct CCameraManagerAngles { ptr_t cameraAngles; // CCameraAngles * }; -struct CCameraAngles { +struct alignas(8) CCameraAngles { uint8_t pad1[960]; ptr_t playerAngles; // CPlayerAngles * uint8_t pad2[60]; ------------------->8--------------------- -kb From willysr at slackbuilds.org Tue Mar 19 02:56:21 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 19 Mar 2024 09:56:21 +0700 Subject: [Slackbuilds-users] Mumble gtav plugin compile error on Slackware 32-bit In-Reply-To: <6fa24cb1-cdf9-4699-b6a4-cc3ab43036c2@linuxgalaxy.org> References: <6fa24cb1-cdf9-4699-b6a4-cc3ab43036c2@linuxgalaxy.org> Message-ID: <7bad893b-d1c7-4726-b8c0-377671b0ead4@slackbuilds.org> > Seems there was some sort of omission or regression (or "Who still uses > 32-bit?") when the gtav plugin is compiled for mumble. This was fixed > previously in mumble-master but somehow did not end up in mumble-1.4.287 > > I've posted the fix to my branch for the next update. However, other > than a qemu VM (not set up for audio), I'm not able to test fully. Thanks for this update can you also test with latest protobuf3? https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3F617144D7238786.asc Type: application/pgp-keys Size: 8363 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net Tue Mar 19 03:51:20 2024 From: for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net (Lockywolf) Date: Tue, 19 Mar 2024 11:51:20 +0800 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: <5ca1fd6b-2900-a951-174b-20bf7831aa6d@open-t.co.uk> References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <5ca1fd6b-2900-a951-174b-20bf7831aa6d@open-t.co.uk> Message-ID: <87plvqlvyf.fsf@laptop.lockywolf.net> Sebastian Arcus writes: > 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? Is anybody going to take linphone-desktop away from me? -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From sbo at linuxgalaxy.org Tue Mar 19 04:32:15 2024 From: sbo at linuxgalaxy.org (KB_SBo) Date: Tue, 19 Mar 2024 04:32:15 +0000 Subject: [Slackbuilds-users] Mumble gtav plugin compile error on Slackware 32-bit In-Reply-To: <7bad893b-d1c7-4726-b8c0-377671b0ead4@slackbuilds.org> References: <6fa24cb1-cdf9-4699-b6a4-cc3ab43036c2@linuxgalaxy.org> <7bad893b-d1c7-4726-b8c0-377671b0ead4@slackbuilds.org> Message-ID: <992a0500-8d85-4f49-a67f-88fe07c3aea6@linuxgalaxy.org> On 3/18/24 19:56, Willy Sudiarto Raharjo wrote: >> Seems there was some sort of omission or regression (or "Who still uses >> 32-bit?") when the gtav plugin is compiled for mumble. This was fixed >> previously in mumble-master but somehow did not end up in mumble-1.4.287 >> >> I've posted the fix to my branch for the next update. However, other >> than a qemu VM (not set up for audio), I'm not able to test fully. > > Thanks for this update > can you also test with latest protobuf3? > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > Looks like mumble compiles ok withe protobuf3-26 on Slackware32. I'll test Slackware64 once I clean up my VM. -kb From s.arcus at open-t.co.uk Tue Mar 19 11:31:00 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 19 Mar 2024 11:31:00 +0000 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: <87plvqlvyf.fsf@laptop.lockywolf.net> References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <5ca1fd6b-2900-a951-174b-20bf7831aa6d@open-t.co.uk> <87plvqlvyf.fsf@laptop.lockywolf.net> Message-ID: On 19/03/2024 03:51, Lockywolf wrote: > > Sebastian Arcus writes: > >> 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? > > Is anybody going to take linphone-desktop away from me? I asked if I could take it over - I think we were waiting for an answer from the admins From sbo at linuxgalaxy.org Tue Mar 19 17:56:10 2024 From: sbo at linuxgalaxy.org (KB_SBo) Date: Tue, 19 Mar 2024 17:56:10 +0000 Subject: [Slackbuilds-users] Mumble gtav plugin compile error on Slackware 32-bit In-Reply-To: <7bad893b-d1c7-4726-b8c0-377671b0ead4@slackbuilds.org> References: <6fa24cb1-cdf9-4699-b6a4-cc3ab43036c2@linuxgalaxy.org> <7bad893b-d1c7-4726-b8c0-377671b0ead4@slackbuilds.org> Message-ID: <97061c6e-4128-4443-90ad-be332958c18e@linuxgalaxy.org> On 3/18/24 19:56, Willy Sudiarto Raharjo wrote: >> Seems there was some sort of omission or regression (or "Who still uses >> 32-bit?") when the gtav plugin is compiled for mumble. This was fixed >> previously in mumble-master but somehow did not end up in mumble-1.4.287 >> >> I've posted the fix to my branch for the next update. However, other >> than a qemu VM (not set up for audio), I'm not able to test fully. > > Thanks for this update > can you also test with latest protobuf3? > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > All is good. with the new protobuf3-26, mumble-1.4.287 compiles and runs on Slackware{32,64}-15.0 I did notice a message from protobuf3 that LIB_SUFFIX specified is not used. libs appear to be sorted into /usr/lib and /usr/lib64 based on arch correctly. The scripts I posted to my branch should be good to go. -kb From zhu.qunying at gmail.com Tue Mar 19 18:31:00 2024 From: zhu.qunying at gmail.com (Qun-Ying) Date: Tue, 19 Mar 2024 11:31:00 -0700 Subject: [Slackbuilds-users] suggestion for a new category for fonts Message-ID: Hi, Currently fonts are put under category system, they mix with other system tools. Would it be better to have a separate category (fonts) for them? -- Qun-Ying From urchlay at slackware.uk Tue Mar 19 18:50:16 2024 From: urchlay at slackware.uk (B. Watson) Date: Tue, 19 Mar 2024 14:50:16 -0400 (EDT) Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: Message-ID: <16ef9bc1-2c70-60e2-baa8-524de9607238@slackware.uk> On Tue, 19 Mar 2024, Qun-Ying wrote: > Currently fonts are put under category system, they mix with other > system tools. Would it be better to have a separate category (fonts) > for them? If we're voting, I vote for this. From slack at giand.it Tue Mar 19 19:38:42 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Tue, 19 Mar 2024 20:38:42 +0100 Subject: [Slackbuilds-users] Updates - 20240316.1 In-Reply-To: <9c649c72-6b74-4266-a4be-0545d6281a2b@slackbuilds.org> References: <9c649c72-6b74-4266-a4be-0545d6281a2b@slackbuilds.org> Message-ID: <8bbe524f-5b20-4b50-9e95-f7582ab19beb@giand.it> Il 16/03/24 04:30, Willy Sudiarto Raharjo ha scritto: > Sat Mar 16 03:23:02 UTC 2024 > academic/Gridcoin-Research: Updated for version 5.4.7.0 > academic/ITK: Fix build. > ITK slackbuild requires to be fixed for build against gtest 1.12.1. The build works if gtest is not installed, I think with a bundle googletest, but if a googletest system is found, it is used by default. Unfortunately cmake returns an error if gtest 1.12.1 is installed. I solved passing this flag to cmake: -DITK_USE_SYSTEM_GOOGLETEST=OFF This should be added in the slackbuild script, otherwise ITK must be built after uninstalling gtest Thanks -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From willysr at slackbuilds.org Tue Mar 19 23:43:08 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 20 Mar 2024 06:43:08 +0700 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <5ca1fd6b-2900-a951-174b-20bf7831aa6d@open-t.co.uk> <87plvqlvyf.fsf@laptop.lockywolf.net> Message-ID: <9b2647fb-5b0d-4fcf-910f-90f22d43fdc8@slackbuilds.org> >> Is anybody going to take linphone-desktop away from me? > > I asked if I could take it over - I think we were waiting for an answer > from the admins You should ask the maintainer if the maintainer is still active -- 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 Mar 20 00:48:25 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 20 Mar 2024 00:48:25 +0000 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: <9b2647fb-5b0d-4fcf-910f-90f22d43fdc8@slackbuilds.org> References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <5ca1fd6b-2900-a951-174b-20bf7831aa6d@open-t.co.uk> <87plvqlvyf.fsf@laptop.lockywolf.net> <9b2647fb-5b0d-4fcf-910f-90f22d43fdc8@slackbuilds.org> Message-ID: <2122d496-1839-30b5-a9a0-f9cc5409c0a5@open-t.co.uk> On 19/03/2024 23:43, Willy Sudiarto Raharjo wrote: >>> Is anybody going to take linphone-desktop away from me? >> >> I asked if I could take it over - I think we were waiting for an >> answer from the admins > > You should ask the maintainer if the maintainer is still active I have copied Euan into the email I sent to the list on 07 Feb 2024 asking if the Linphone scripts could be updated - but there hasn't been any reply. I already accepted to look after BcToolbox, which he used to maintain - as he hasn't been active in a long time. Should I try to contact Euan again? From urchlay at slackware.uk Wed Mar 20 01:03:11 2024 From: urchlay at slackware.uk (B. Watson) Date: Tue, 19 Mar 2024 21:03:11 -0400 (EDT) Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: <2122d496-1839-30b5-a9a0-f9cc5409c0a5@open-t.co.uk> References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <5ca1fd6b-2900-a951-174b-20bf7831aa6d@open-t.co.uk> <87plvqlvyf.fsf@laptop.lockywolf.net> <9b2647fb-5b0d-4fcf-910f-90f22d43fdc8@slackbuilds.org> <2122d496-1839-30b5-a9a0-f9cc5409c0a5@open-t.co.uk> Message-ID: <118c803d-fce0-1fb6-8871-471d176a96@slackware.uk> On Wed, 20 Mar 2024, Sebastian Arcus wrote: > I have copied Euan into the email I sent to the list on 07 Feb 2024 asking if > the Linphone scripts could be updated - but there hasn't been any reply. I > already accepted to look after BcToolbox, which he used to maintain - as he > hasn't been active in a long time. > > Should I try to contact Euan again? Don't bother. Euan Thoms' last activity was in November of 2017, over 6 years ago. I think we can consider this one an ex-maintainer. Whoever wants to take over linphone, and any other of his builds, just submit an update (possibly after discussing it on this mailing list). I recommend whoever takes linphone also takes its dependencies that were maintained by Euan: libraries/libantlr3c libraries/libsrtp libraries/bzrtp libraries/belle-sip Whoever wants them should also take Euan's other builds: libraries/ccrtp libraries/libzrtpcpp libraries/msx264 libraries/ucommon network/netdrive-connector From sbo at linuxgalaxy.org Wed Mar 20 02:22:23 2024 From: sbo at linuxgalaxy.org (KB_SBo) Date: Wed, 20 Mar 2024 02:22:23 +0000 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: Message-ID: On 3/19/24 11:31, Qun-Ying wrote: > Hi, > > Currently fonts are put under category system, they mix with other > system tools. Would it be better to have a separate category (fonts) > for them? > > +1 for fonts as its own category -kb From for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net Wed Mar 20 06:32:54 2024 From: for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net (Lockywolf) Date: Wed, 20 Mar 2024 14:32:54 +0800 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: Message-ID: <87y1adjthi.fsf@laptop.lockywolf.net> KB_SBo writes: > On 3/19/24 11:31, Qun-Ying wrote: >> Hi, >> >> Currently fonts are put under category system, they mix with other >> system tools. Would it be better to have a separate category (fonts) >> for them? >> >> > > +1 for fonts as its own category > > -kb > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ +1 for fonts as its own category, and, if possible, please, one more category for "slackware-specific" stuffs, such as: 1. slackrepo 2. slackrepo-hints 3. sbotools 4. sbo-create 5. sbo-maintainer-tools 6. sbotools 7. sboui 8. slpkg 9. listpkg 10. gnome-pkgtool 11. findpkg 12. slack-osquery 13. slack-utils 14. slackchlog 15. slackroll 16. slackupdr 17. slackware-grub2-theme 18. slackyd 19. slack-wallpapers 20. slackware-xdg-menu 21. slackware-xdm-theme 22. xdm-slackware-theme 23. fortune-slackware 24. perl-CPANPLUS-Dist-Slackware 25. python2-slacklog This is comparable to the size of, say accessibility/ nowadays those packages are scattered over many categories, not just system/, and system/ has a lot of packages, whereas having all Slackware-related in one place would have been really convenient. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From fernando.lopezjr at gmail.com Wed Mar 20 06:42:58 2024 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Wed, 20 Mar 2024 01:42:58 -0500 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: <87y1adjthi.fsf@laptop.lockywolf.net> References: <87y1adjthi.fsf@laptop.lockywolf.net> Message-ID: +1 On Wed, Mar 20, 2024, 1:41?AM Lockywolf < for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net> wrote: > > > > KB_SBo writes: > > > On 3/19/24 11:31, Qun-Ying wrote: > >> Hi, > >> > >> Currently fonts are put under category system, they mix with other > >> system tools. Would it be better to have a separate category (fonts) > >> for them? > >> > >> > > > > +1 for fonts as its own category > > > > -kb > > > > > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > +1 for fonts as its own category, and, if possible, please, one more > category for "slackware-specific" stuffs, such as: > > 1. slackrepo > 2. slackrepo-hints > 3. sbotools > 4. sbo-create > 5. sbo-maintainer-tools > 6. sbotools > 7. sboui > 8. slpkg > 9. listpkg > 10. gnome-pkgtool > 11. findpkg > 12. slack-osquery > 13. slack-utils > 14. slackchlog > 15. slackroll > 16. slackupdr > 17. slackware-grub2-theme > 18. slackyd > 19. slack-wallpapers > 20. slackware-xdg-menu > 21. slackware-xdm-theme > 22. xdm-slackware-theme > 23. fortune-slackware > 24. perl-CPANPLUS-Dist-Slackware > 25. python2-slacklog > > This is comparable to the size of, say accessibility/ > > nowadays those packages are scattered over many categories, not just > system/, and system/ has a lot of packages, whereas having all > Slackware-related in one place would have been really convenient. > > > -- > Your sincerely, > Vladimir Nikishkin (MiEr, lockywolf) > (Laptop) > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slack at giand.it Wed Mar 20 07:29:52 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Wed, 20 Mar 2024 08:29:52 +0100 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: Message-ID: <516ebc1f-0baa-4f50-bdb6-d86b9d9b5686@giand.it> Il 19/03/24 19:31, Qun-Ying ha scritto: > Hi, > > Currently fonts are put under category system, they mix with other > system tools. Would it be better to have a separate category (fonts) > for them? > It seems a good idea -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From davidnchmelik at gmail.com Wed Mar 20 07:32:29 2024 From: davidnchmelik at gmail.com (David Chmelik) Date: Wed, 20 Mar 2024 00:32:29 -0700 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: <87y1adjthi.fsf@laptop.lockywolf.net> References: <87y1adjthi.fsf@laptop.lockywolf.net> Message-ID: On 3/19/24 11:32 PM, Lockywolf wrote: > KB_SBo writes: > On 3/19/24 11:31, Qun-Ying wrote: >>> [...] Currently fonts are put under category system, they mix with other >>> system tools. Would it be better to have a separate category (fonts) >>> for them? >> +1 for fonts as its own category >> >> -kb [...] > +1 for fonts as its own category, and, if possible, please, one more > category for "slackware-specific" stuffs, such as: > > 1. slackrepo > 2. slackrepo-hints > 3. sbotools > 4. sbo-create > 5. sbo-maintainer-tools > 6. sbotools > 7. sboui > 8. slpkg > 9. listpkg > 10. gnome-pkgtool > 11. findpkg > 12. slack-osquery > 13. slack-utils > 14. slackchlog > 15. slackroll > 16. slackupdr > 17. slackware-grub2-theme > 18. slackyd > 19. slack-wallpapers > 20. slackware-xdg-menu > 21. slackware-xdm-theme > 22. xdm-slackware-theme > 23. fortune-slackware > 24. perl-CPANPLUS-Dist-Slackware > 25. python2-slacklog > > This is comparable to the size of, say accessibility/ > > nowadays those packages are scattered over many categories, not just > system/, and system/ has a lot of packages, whereas having all > Slackware-related in one place would have been really convenient. There are several/many others, also, like depfinder, gslapt, hoorex, magiic, slapt-get, slapt-src, slpkg, sourcery, spi, spkg... not all have the word 'slack' in. From kvngncrlsn at gmail.com Wed Mar 20 09:38:02 2024 From: kvngncrlsn at gmail.com (K. Eugene Carlson) Date: Wed, 20 Mar 2024 18:38:02 +0900 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: <87y1adjthi.fsf@laptop.lockywolf.net> References: <87y1adjthi.fsf@laptop.lockywolf.net> Message-ID: I'd be in favor of both new categories. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tonus1 at free.fr Wed Mar 20 11:13:13 2024 From: tonus1 at free.fr (Tonus) Date: Wed, 20 Mar 2024 12:13:13 +0100 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: <87y1adjthi.fsf@laptop.lockywolf.net> Message-ID: Hi list That would be great for the 2 proposals. Regards -- Tonus Le 20 mars 2024 08:32:29 GMT+01:00, David Chmelik a ?crit?: >On 3/19/24 11:32 PM, Lockywolf wrote: >> KB_SBo writes: >> On 3/19/24 11:31, Qun-Ying wrote: >>>> [...] Currently fonts are put under category system, they mix with other >>>> system tools. Would it be better to have a separate category (fonts) >>>> for them? >>> +1 for fonts as its own category >>> >>> -kb [...] >> +1 for fonts as its own category, and, if possible, please, one more >> category for "slackware-specific" stuffs, such as: >> >> 1. slackrepo >> 2. slackrepo-hints >> 3. sbotools >> 4. sbo-create >> 5. sbo-maintainer-tools >> 6. sbotools >> 7. sboui >> 8. slpkg >> 9. listpkg >> 10. gnome-pkgtool >> 11. findpkg >> 12. slack-osquery >> 13. slack-utils >> 14. slackchlog >> 15. slackroll >> 16. slackupdr >> 17. slackware-grub2-theme >> 18. slackyd >> 19. slack-wallpapers >> 20. slackware-xdg-menu >> 21. slackware-xdm-theme >> 22. xdm-slackware-theme >> 23. fortune-slackware >> 24. perl-CPANPLUS-Dist-Slackware >> 25. python2-slacklog >> >> This is comparable to the size of, say accessibility/ >> >> nowadays those packages are scattered over many categories, not just >> system/, and system/ has a lot of packages, whereas having all >> Slackware-related in one place would have been really convenient. > >There are several/many others, also, like depfinder, gslapt, hoorex, magiic, slapt-get, slapt-src, slpkg, sourcery, spi, spkg... not all have the word 'slack' in. >_______________________________________________ >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 j+sbo-users at maschinengott.de Wed Mar 20 11:27:45 2024 From: j+sbo-users at maschinengott.de (j+sbo-users at maschinengott.de) Date: Wed, 20 Mar 2024 12:27:45 +0100 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: <87y1adjthi.fsf@laptop.lockywolf.net> References: <87y1adjthi.fsf@laptop.lockywolf.net> Message-ID: On 20.03.24 07:32, Lockywolf wrote:> > +1 for fonts as its own category, and, if possible, please, one more > category for "slackware-specific" stuffs, such as: As a few people have spoken in favour of this, what would be a good name? Just to get the conversation going: I think "slackware" is too unspecific. My first thought was "meta", but I think it does not fit all the proposed packages. Same with "packaging". From s.arcus at open-t.co.uk Wed Mar 20 12:20:05 2024 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 20 Mar 2024 12:20:05 +0000 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: <118c803d-fce0-1fb6-8871-471d176a96@slackware.uk> References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <5ca1fd6b-2900-a951-174b-20bf7831aa6d@open-t.co.uk> <87plvqlvyf.fsf@laptop.lockywolf.net> <9b2647fb-5b0d-4fcf-910f-90f22d43fdc8@slackbuilds.org> <2122d496-1839-30b5-a9a0-f9cc5409c0a5@open-t.co.uk> <118c803d-fce0-1fb6-8871-471d176a96@slackware.uk> Message-ID: <772f1f36-bacf-b2e8-a4d0-871360be18a9@open-t.co.uk> On 20/03/2024 01:03, B. Watson wrote: > > > On Wed, 20 Mar 2024, Sebastian Arcus wrote: > >> I have copied Euan into the email I sent to the list on 07 Feb 2024 >> asking if the Linphone scripts could be updated - but there hasn't >> been any reply. I already accepted to look after BcToolbox, which he >> used to maintain - as he hasn't been active in a long time. >> >> Should I try to contact Euan again? > > Don't bother. Euan Thoms' last activity was in November of 2017, over > 6 years ago. I think we can consider this one an ex-maintainer. > > Whoever wants to take over linphone, and any other of his builds, just > submit an update (possibly after discussing it on this mailing list). > > I recommend whoever takes linphone also takes its dependencies that > were maintained by Euan: > > libraries/libantlr3c > libraries/libsrtp > libraries/bzrtp > libraries/belle-sip > > Whoever wants them should also take Euan's other builds: > > libraries/ccrtp > libraries/libzrtpcpp > libraries/msx264 > libraries/ucommon > network/netdrive-connector That would make sense. They are quite a few packages, and I have no idea how straight forward will be to bring them up to date, but if nobody else is stepping up, I can try to push updates for the above, as and when I find the time. It could be a few weeks until I get to it - if that's ok. I do use Linphone from time to time, so I would prefer it stays in the SBo repo. From dchmelik at gmail.com Wed Mar 20 12:31:52 2024 From: dchmelik at gmail.com (dchmelik at gmail.com) Date: Wed, 20 Mar 2024 05:31:52 -0700 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: <87y1adjthi.fsf@laptop.lockywolf.net> References: <87y1adjthi.fsf@laptop.lockywolf.net> Message-ID: On 3/19/24 11:32 PM, Lockywolf wrote: > [...] +1 for fonts as its own category, and, if possible, please, one more > category for "slackware-specific" stuffs, such as: > > 1. slackrepo > 2. slackrepo-hints > 3. sbotools > 4. sbo-create > 5. sbo-maintainer-tools > 6. sbotools > 7. sboui > 8. slpkg > 9. listpkg > 10. gnome-pkgtool > 11. findpkg > 12. slack-osquery > 13. slack-utils > 14. slackchlog > 15. slackroll > 16. slackupdr > 17. slackware-grub2-theme > 18. slackyd > 19. slack-wallpapers > 20. slackware-xdg-menu > 21. slackware-xdm-theme > 22. xdm-slackware-theme > 23. fortune-slackware > 24. perl-CPANPLUS-Dist-Slackware > 25. python2-slacklog These are many mixed categories and are best where they are now.? I mentioned maybe 10+ more but in fact there are dozens/hundreds, as software from all categories is patched for Slackware.? I don't want command-line system tools, package management tools mixed up in a category with GUI stuff and development dependencies for other stuff I don't even use. From luc.vanrompaey at gmail.com Wed Mar 20 12:44:01 2024 From: luc.vanrompaey at gmail.com (Luc Van Rompaey) Date: Wed, 20 Mar 2024 13:44:01 +0100 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: <87y1adjthi.fsf@laptop.lockywolf.net> Message-ID: "slack-tools" or some such? j+sbo-users at maschinengott.de schreef op 20 maart 2024 12:27:45 CET: >On 20.03.24 07:32, Lockywolf wrote:> >> +1 for fonts as its own category, and, if possible, please, one more >> category for "slackware-specific" stuffs, such as: > >As a few people have spoken in favour of this, what would be a good name? Just to get the conversation going: I think "slackware" is too unspecific. My first thought was "meta", but I think it does not fit all the proposed packages. Same with "packaging". >_______________________________________________ >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 tonus1 at free.fr Wed Mar 20 17:50:53 2024 From: tonus1 at free.fr (Tonus) Date: Wed, 20 Mar 2024 18:50:53 +0100 Subject: [Slackbuilds-users] jq fails to build Message-ID: <7qakf7v67innbmqif7x7m46falh2mpf26bmpaaltjmxh2p6ppp@eoowinsghtxs> Hi list, Just tried to update jq and build failed on tests. ? configure: WARNING: valgrind is required to test jq. ? checking for memmem... yes ? checking for sys/cygwin.h... no ? checking for shlwapi.h... no ? checking for pipenv... no ? checking for Python dependencies... no ? configure: WARNING: Error checking python dependencies: ? ***************************************************************** ? * Python dependencies for building jq documentation not found. * ? * You can still build, install and hack on jq, but the manpage * ? * will not be rebuilt and new manpage tests will not be run. * ? * See docs/README.md for how to install the docs dependencies. * ? ***************************************************************** and further ? PASS: tests/mantest ? FAIL: tests/jqtest ? PASS: tests/shtest ? PASS: tests/utf8test ? PASS: tests/base64test ? FAIL: tests/optionaltest ? PASS: tests/onigtest ? PASS: tests/manonigtest ? ========================================================================== ? Testsuite summary for jq 1.7.1 ? ========================================================================== ? # TOTAL: 8 ? # PASS: 6 ? # SKIP: 0 ? # XFAIL: 0 ? # FAIL: 2 ? # XPASS: 0 ? # ERROR: 0 ? ========================================================================== ? See ./test-suite.log ? Please report to https://github.com/jqlang/jq/issues ? ========================================================================== Installing valgrind gives same errors. -- Regards, Tonus From tonus1 at free.fr Wed Mar 20 19:46:02 2024 From: tonus1 at free.fr (Tonus) Date: Wed, 20 Mar 2024 20:46:02 +0100 Subject: [Slackbuilds-users] WIP: protobuf3 25.3 In-Reply-To: <18e2d6d3ec7.d79330882724249.31809054317240023@beco.cc> References: <1d1e15ed-3aaf-46dc-b99a-8334f036619b@slackbuilds.org> <45ae0ae9-d1b0-4952-adf8-ae52ce905d00@giand.it> <18e2949a282.e802155b2535715.8372097867534222834@beco.cc> <18e2a2040ce.10c7a79e32545886.80972166299494485@beco.cc> <18e2d6d3ec7.d79330882724249.31809054317240023@beco.cc> Message-ID: On Mon, Mar 11, 2024 at 09:13:58AM -0300, Slackbuilds Mailing List wrote: >I'm still looking for some guidelines on how developers usually create virtual machines to test. I used virtualbox when I developed for debian, but I don't like this approach anymore. I'm trying to learn LCX, and for slackware it doesn't have templates ready to go, so there is that. > Hi Not really a developer here but found great advice from Alien Bob with qemu. Can't find the source with a quick search so here's the pitch : - create a qemu base image with genuine and up-to-date Slackware - I only add autocompletion, bash magic key and sbo tools and tree - then I use the following script to get a snapshot - I launch it , do stuff and tests, save the package on host - test on my machine and share on SBo - an important thing is to get a share between machines - another one is to keep a consistant SBo tree on base qemu image Now the script from AlienBOB (modified but can't recall if/how) : ? #!/bin/sh ? # ? # Start Slackware in QEMU ? # Use QEMU snapshots (COW - Copy On Write images) for the purpose of ? # testing software in a clean environment. ? ? ## --------------------------------------------------------------------------- ? ## Create an empty 15GB image file like this: ? ## # dd if=/dev/zero of=slackware.img bs=1k count=15000000 ? ## ? ## You must install a version of Slackware in this image file. ? ## This installation will be your base image. It will not change unless ? ## you want to install security patches. ? ## ? ## Then create the QCOW (qemu copy-on-write) file like this: ? ## $ qemu-img create -b slackware.img -f qcow slackware_snapshot.qcow ? ## ? ## DO NOT commit the changes made in the QCOW file back to the base image! ? ## The QCOW image is only used once and re-created every time the script runs! ? ## --------------------------------------------------------------------------- ? ? # Location of your QEMU images: ? IMAGEDIR=/path/to/disk_img/slackware ? ? # ISO location ? iso_file=/path/to/disk_img/slackware64-current-iso/slackware64-15.0-install-dvd.iso ? # add next option to have it ? # -cdrom "${iso_file}" ? ? #[ ! -z $* ] && PARAMS=$* ? # add command line parameters to defaults ? PARAMS=$* ? ? # Qemu can use SDL sound instead of the default OSS ? export QEMU_AUDIO_DRV=sdl ? ? # Whereas SDL can play through alsa: ? export SDL_AUDIODRIVER=alsa ? ? cd $IMAGEDIR ? # Remove old QCOW file, create a new one: ? if [ -f slackware-15.0_snapshot.qcow ]; then ? rm -f slackware-15.0_snapshot.qcow ? fi ? qemu-img create -f qcow2 -b slackware64-15.0.qcow2 -F qcow2 slackware64-15.0_snapshot.qcow ? ? qemu-system-x86_64 -enable-kvm -smp cpus=2 -smp maxcpus=3 -m 4096 -k fr -daemonize \ ? -vga virtio -boot menu=on -usb -drive file=slackware64-15.0_snapshot.qcow \ ? -fsdev local,id=repos,path=/path/to/share,security_model=none \ ? -device virtio-9p-pci,fsdev=repos,mount_tag=repos ${PARAMS} >slackware-15.0_snapshot.log \ ? 2>slackware-15.0_snapshot.err -- Regards, Tonus From matteo.bernardini at gmail.com Wed Mar 20 19:53:43 2024 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 20 Mar 2024 20:53:43 +0100 Subject: [Slackbuilds-users] jq fails to build In-Reply-To: <7qakf7v67innbmqif7x7m46falh2mpf26bmpaaltjmxh2p6ppp@eoowinsghtxs> References: <7qakf7v67innbmqif7x7m46falh2mpf26bmpaaltjmxh2p6ppp@eoowinsghtxs> Message-ID: Il giorno mer 20 mar 2024 alle ore 18:50 Tonus ha scritto: > ? PASS: tests/mantest > ? FAIL: tests/jqtest > ? PASS: tests/shtest > ? PASS: tests/utf8test > ? PASS: tests/base64test > ? FAIL: tests/optionaltest > ? PASS: tests/onigtest > ? PASS: tests/manonigtest > ? > ========================================================================== > ? Testsuite summary for jq 1.7.1 > ? > ========================================================================== > ? # TOTAL: 8 > ? # PASS: 6 > ? # SKIP: 0 > ? # XFAIL: 0 > ? # FAIL: 2 > ? # XPASS: 0 > ? # ERROR: 0 > hi Tonus, jq seems to build fine here so I am inclined to think about a local issue: for hints maybe you can have a look in your /tmp/SBo/jq-1.7.1/tests directory, and in particular check the content of the jqtest.log and optionaltest.log diles that you can find there... Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From j+sbo-users at maschinengott.de Wed Mar 20 19:54:36 2024 From: j+sbo-users at maschinengott.de (j+sbo-users at maschinengott.de) Date: Wed, 20 Mar 2024 20:54:36 +0100 Subject: [Slackbuilds-users] kicad md5sum mismatch (again) In-Reply-To: <1cda9f15-601b-4bb2-8da3-a0448d0a4f90@googlemail.com> References: <1cda9f15-601b-4bb2-8da3-a0448d0a4f90@googlemail.com> Message-ID: <9183c0cd-c03f-4d47-9a83-a24ed2e83835@maschinengott.de> hey, for KiCad 8.0 Expected: dd187abbfb1109f8d417aa08fc75d19f Found: 03f46e27af35c003c985f96618d566a9 From nomnombtc at arcor.de Wed Mar 20 19:55:19 2024 From: nomnombtc at arcor.de (nnb) Date: Wed, 20 Mar 2024 20:55:19 +0100 Subject: [Slackbuilds-users] jq fails to build In-Reply-To: <7qakf7v67innbmqif7x7m46falh2mpf26bmpaaltjmxh2p6ppp@eoowinsghtxs> References: <7qakf7v67innbmqif7x7m46falh2mpf26bmpaaltjmxh2p6ppp@eoowinsghtxs> Message-ID: Hello, Am 20.03.24 um 18:50 schrieb Tonus: > Hi list, > > Just tried to update jq and build failed on tests. > > [...] build failed for me too, in my case it was this issue: https://github.com/jqlang/jq/issues/3038 Some tests fail because of locale setting. I did run sbopkg like this and the build worked fine 'LANG=C sbopkg'. Best regards From tonus1 at free.fr Wed Mar 20 20:02:40 2024 From: tonus1 at free.fr (Tonus) Date: Wed, 20 Mar 2024 21:02:40 +0100 Subject: [Slackbuilds-users] jq fails to build In-Reply-To: References: <7qakf7v67innbmqif7x7m46falh2mpf26bmpaaltjmxh2p6ppp@eoowinsghtxs> Message-ID: >build failed for me too, in my case it was this issue: >https://github.com/jqlang/jq/issues/3038 > >Some tests fail because of locale setting. I did run sbopkg >like this and the build worked fine 'LANG=C sbopkg'. Thank you, that worked ! -- Regards, Tonus From zhu.qunying at gmail.com Wed Mar 20 20:37:45 2024 From: zhu.qunying at gmail.com (Qun-Ying) Date: Wed, 20 Mar 2024 13:37:45 -0700 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: <87y1adjthi.fsf@laptop.lockywolf.net> Message-ID: On Wed, Mar 20, 2024 at 5:44?AM Luc Van Rompaey wrote: > > "slack-tools" or some such? > > > j+sbo-users at maschinengott.de schreef op 20 maart 2024 12:27:45 CET: +1 for "slack-tools" From fernando.lopezjr at gmail.com Wed Mar 20 22:27:50 2024 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Wed, 20 Mar 2024 17:27:50 -0500 Subject: [Slackbuilds-users] kicad md5sum mismatch (again) In-Reply-To: <9183c0cd-c03f-4d47-9a83-a24ed2e83835@maschinengott.de> References: <1cda9f15-601b-4bb2-8da3-a0448d0a4f90@googlemail.com> <9183c0cd-c03f-4d47-9a83-a24ed2e83835@maschinengott.de> Message-ID: this is a known issue. On Wed, Mar 20, 2024, 2:54?PM wrote: > hey, for KiCad 8.0 > > Expected: dd187abbfb1109f8d417aa08fc75d19f > Found: 03f46e27af35c003c985f96618d566a9 > _______________________________________________ > 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 lramos.prof at yahoo.com.br Thu Mar 21 00:00:46 2024 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Wed, 20 Mar 2024 21:00:46 -0300 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: <87y1adjthi.fsf@laptop.lockywolf.net> Message-ID: slackware-specific On Wed, Mar 20, 2024 at 12:27:45PM +0100, j+sbo-users at maschinengott.de wrote: > On 20.03.24 07:32, Lockywolf wrote:> > > +1 for fonts as its own category, and, if possible, please, one more > > category for "slackware-specific" stuffs, such as: > > As a few people have spoken in favour of this, what would be a good name? > Just to get the conversation going: I think "slackware" is too unspecific. > My first thought was "meta", but I think it does not fit all the proposed > packages. Same with "packaging". > _______________________________________________ > 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 urchlay at slackware.uk Thu Mar 21 02:44:10 2024 From: urchlay at slackware.uk (B. Watson) Date: Wed, 20 Mar 2024 22:44:10 -0400 (EDT) Subject: [Slackbuilds-users] jq fails to build In-Reply-To: References: <7qakf7v67innbmqif7x7m46falh2mpf26bmpaaltjmxh2p6ppp@eoowinsghtxs> Message-ID: <2e44268d-6adb-5d81-9693-75f818eeb35f@slackware.uk> On Wed, 20 Mar 2024, nnb via SlackBuilds-users wrote: > Some tests fail because of locale setting. I did run sbopkg > like this and the build worked fine 'LANG=C sbopkg'. Hopefully the maintainer can add 'export LANG=C' somewhere near the top of the script. From willysr at slackbuilds.org Thu Mar 21 03:00:41 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 21 Mar 2024 10:00:41 +0700 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: Message-ID: <744553fa-0b00-4533-9fc5-2d53d113eade@slackbuilds.org> > Currently fonts are put under category system, they mix with other > system tools. Would it be better to have a separate category (fonts) > for them? This is my personal opinion and do not express other admin's opinion i think having more categories doesn't really give benefits to this project besides cosmetic values. It just adds more work moving scripts around during development cycle, adding new categories in the database, web forms, etc. Since we have search form in our website, i wonder how many people would go through each categories when looking for some scripts instead of just using the search form? During development cycle (which usually started when Pat declared Alpha or Beta version of Slackware-Current), admins will be busy verifying each scripts in the repo to make sure it builds fine against slackware-current, which will be a moving target since Pat usually have a long period of testing before he declares stable release. Some of these scripts have been checked and fixed by Ponce so it gives a headstart for us, but we have over 9k scripts (per December 2023) and it's growing each week. There are tons of work to make sure the new repo is ready when next Slackware is released and we are targeting for same-day release (if it's possible). -- Willy Sudiarto Raharjo From davidnchmelik at gmail.com Thu Mar 21 03:51:37 2024 From: davidnchmelik at gmail.com (David Chmelik) Date: Wed, 20 Mar 2024 20:51:37 -0700 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: Message-ID: On 3/19/24 11:31 AM, Qun-Ying wrote: > [...] Currently fonts are put under category system, they mix with other > system tools. Would it be better to have a separate category (fonts) > for them? yes From urchlay at slackware.uk Thu Mar 21 05:00:37 2024 From: urchlay at slackware.uk (B. Watson) Date: Thu, 21 Mar 2024 01:00:37 -0400 (EDT) Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: <744553fa-0b00-4533-9fc5-2d53d113eade@slackbuilds.org> References: <744553fa-0b00-4533-9fc5-2d53d113eade@slackbuilds.org> Message-ID: On Thu, 21 Mar 2024, Willy Sudiarto Raharjo wrote: > Since we have search form in our website, i wonder how many people would go > through each categories when looking for some scripts instead of just using > the search form? OK, so in that case, why do we have categories at all? Would it bother you to get rid of them entirely? Other than the amount of work it would take to accomplish it, I mean. Would we be better off if there had never been categories? We could just add a keyword for each build, with its former category. system/dosbox would just become dosbox/, and get "system" added to its list of keywords... ...which is silly of course. It's intended to be silly. From zhu.qunying at gmail.com Thu Mar 21 05:04:20 2024 From: zhu.qunying at gmail.com (Qun-Ying) Date: Wed, 20 Mar 2024 22:04:20 -0700 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: <744553fa-0b00-4533-9fc5-2d53d113eade@slackbuilds.org> References: <744553fa-0b00-4533-9fc5-2d53d113eade@slackbuilds.org> Message-ID: It is good to have suggestion, but then all decision is by the slackbuild admin. For the use case, I occasionally browser through the categories not looking for a particular package but to discover what packages are available for Slackware and sometimes found some packages that I would want to try on. It would be nice if the categories are more accurate. On Wed, Mar 20, 2024 at 8:00?PM Willy Sudiarto Raharjo wrote: > > > Currently fonts are put under category system, they mix with other > > system tools. Would it be better to have a separate category (fonts) > > for them? > > This is my personal opinion and do not express other admin's opinion > > i think having more categories doesn't really give benefits to this > project besides cosmetic values. It just adds more work moving scripts > around during development cycle, adding new categories in the database, > web forms, etc. > > Since we have search form in our website, i wonder how many people would > go through each categories when looking for some scripts instead of just > using the search form? From for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net Thu Mar 21 05:04:08 2024 From: for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net (Lockywolf) Date: Thu, 21 Mar 2024 13:04:08 +0800 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: <744553fa-0b00-4533-9fc5-2d53d113eade@slackbuilds.org> Message-ID: <87sf0ki2kd.fsf@laptop.lockywolf.net> "B. Watson" writes: > On Thu, 21 Mar 2024, Willy Sudiarto Raharjo wrote: > >> Since we have search form in our website, i wonder how many people would go >> through each categories when looking for some scripts instead of just using the >> search form? > > OK, so in that case, why do we have categories at all? Would it bother > you to get rid of them entirely? Other than the amount of work it > would take to accomplish it, I mean. Would we be better off if there > had never been categories? > > We could just add a keyword for each build, with its former category. > system/dosbox would just become dosbox/, and get "system" added to its > list of keywords... > > ...which is silly of course. It's intended to be silly. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ I do use categories often. I am finding them useful when understanding optional deps, and when searching for "related software". Admittedly, perhaps not _all_ of them are useful, but for me many make sense. I am often finding myself searching for packages using sbopkg -g. They are not fool-proof, but they do help when there are packages with similar names, but doing different things. For example, I might be searching for something which encrypts with aes: sbopkg -g aes. This is the result: academic/aeskulap 0.2.2_e710562d haskell/haskell-aeson 2.0.2.0 haskell/haskell-aeson-compat 0.3.10 haskell/haskell-aeson-pretty 0.8.9 haskell/haskell-cipher-aes 0.2.11 haskell/haskell-hslua-aeson 2.1.0 libraries/SlowAES 0.1a1 libraries/libcaes 20230406 office/unaesgcm 0.4.1.20220827_0cf9cb perl/perl-Crypt-OpenSSL-AES 0.02 python/pyaes 1.6.1 system/aespipe 2.4g From those I immediately see that I need no "academic, haskell, libraries, perl, python." Which leaves me with either unaesgcm or aespipe. And both of those generally do what I expect them to do. When a program is in the "network" category, very high chances are that it doesn't work without network access. Some things are not entirely clear, such as "desktop/office/development". Like, I am a developer, and I use a desktop computer, and I work in an office. But even so, a "desktop" program probably has a GUI, or at least and interactive TUI. Replacing categories _entirely_ with tags might be an option, but for me it seems too radical of a reform, to be honest. But at least (python, ruby, haskell), "network", and "libraries" do make a lot of sense. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From davidnchmelik at gmail.com Thu Mar 21 10:25:52 2024 From: davidnchmelik at gmail.com (David Chmelik) Date: Thu, 21 Mar 2024 03:25:52 -0700 Subject: [Slackbuilds-users] sbotools config issues In-Reply-To: References: Message-ID: <6ef9e2bb-f458-2003-0fc5-a1049686cb6f@gmail.com> On 3/10/24 3:21 PM, J. Milgram wrote: > [...] Once again having problems installing with sbotools. There's > evidently some config subtlety I'm not grasping, hopefully someone can > set me straight. > > I have a fresh -current install and am using the default 15.0 repo. > Many slackbuilds installed fine, but then: > > /usr/sbin/sboinstall XXX fails with: > > "Unable to locate XXX in the SlackBuilds.org tree." > > Where XXX is in [ python3-build, python3-wheel ] ... and maybe others. > May be just python3 packages that fail but haven't investigated. I do > see these slackbuilds in the slackbuilds repo so they're not mirages. I have same problem on Slackware 15 (64-bit) servers that never were on 15.1-current, with both sbopkg and sbotools... some packages depending on python3 build & wheel for some reason can't find them when building, and they weren't loaded into the queue, though when I search for them in sbopkg, they are there, so I had to load them manually... I guess this is normal for sbopkg (unless you load a queue) but shouldn't be happening with sbotools?? I run 'sbocheck' and then try to build things.? Maybe sbotools is too old? > Some config stuff: > > >> cat /etc/slackware-version > Slackware 15.0+ > > >> cat /etc/sbotools/sbotools.conf > JOBS=5 > DISTCLEAN=TRUE > > >> /usr/sbin/sboconfig -l > sboconfig -d|--distclean: > ??? DISTCLEAN=TRUE > sboconfig -j|--jobs: > ??? JOBS=5 > sboconfig -o|--local-overrides: > ??? LOCAL_OVERRIDES=FALSE > sboconfig -c|--noclean: > ??? NOCLEAN=FALSE > sboconfig -p|--pkg-dir: > ??? PKG_DIR=FALSE > sboconfig -r|--repo: > ??? REPO=FALSE > sboconfig -s|--sbo-home: > ??? SBO_HOME=/usr/sbo > sboconfig -V|--slackware-version: > ??? SLACKWARE_VERSION=FALSE > > /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for > python3-build or python3-wheel. > > /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and > have also done sboclean -d. > > /usr/sbin/sbosnap and sboupdate both run seemingly without error, but > don't pick up the missing slackbuilds. > > I'm guessing this is a 15.0 vs. -current thing, but I am out of ideas. > Grateful for any advice! > > Maybe I need to install these problem packages by hand ... if it must > be, so be it. But in the long term it would be nice to get everything > configured properly. > > thanks! [...] From willysr at slackbuilds.org Thu Mar 21 12:06:44 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 21 Mar 2024 19:06:44 +0700 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: <744553fa-0b00-4533-9fc5-2d53d113eade@slackbuilds.org> Message-ID: <3f5ed7bd-da21-4662-8cb3-2825932af5bf@slackbuilds.org> > OK, so in that case, why do we have categories at all? Would it bother > you to get rid of them entirely? Other than the amount of work it > would take to accomplish it, I mean. Would we be better off if there > had never been categories? actually removing it will have more work to do as to change the whole backend process and website code refactoring -- 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 fellype at gmail.com Thu Mar 21 13:41:28 2024 From: fellype at gmail.com (Fellype) Date: Thu, 21 Mar 2024 10:41:28 -0300 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: <3f5ed7bd-da21-4662-8cb3-2825932af5bf@slackbuilds.org> References: <744553fa-0b00-4533-9fc5-2d53d113eade@slackbuilds.org> <3f5ed7bd-da21-4662-8cb3-2825932af5bf@slackbuilds.org> Message-ID: Hello everybody, Just an opinion: In case you decide to add new categories, I believe this could be done at slow steps. First, just create the desired categories. Then, let the maintainers add and/or move their scripts to the appropriate category. In the meantime, the SBo admins could move some scripts when they have time. Pros and cons of doing this way (from my POV): Pros: no one will be overworked and, in the end of the process, the categories will be more representative. Cons: there will be a "little" mess until every piece is in the correct place. Cheers, Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: From zsd+slackbuilds at jdvb.ca Thu Mar 21 15:01:47 2024 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Thu, 21 Mar 2024 12:01:47 -0300 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: <744553fa-0b00-4533-9fc5-2d53d113eade@slackbuilds.org> References: <744553fa-0b00-4533-9fc5-2d53d113eade@slackbuilds.org> Message-ID: On Thu, Mar 21, 2024 at 10:00 (+0700), Willy Sudiarto Raharjo wrote: >> Currently fonts are put under category system, they mix with other >> system tools. Would it be better to have a separate category (fonts) >> for them? > This is my personal opinion and do not express other admin's opinion > i think having more categories doesn't really give benefits to this project > besides cosmetic values. Willy, speaking as someone who does *not* know all the offerings inside out, I found the list of items suggested for "slackware tools" (or whatever it would hypothetically be called) useful. > It just adds more work moving scripts around during development cycle, > adding new categories in the database, web forms, etc. > Since we have search form in our website, i wonder how many people would go > through each categories when looking for some scripts instead of just using > the search form? I would. I'm not sure what search term would list all the slackware-specific packages. (Maybe everyone else knows how to do that, but I don't.) > During development cycle (which usually started when Pat declared Alpha or > Beta version of Slackware-Current), admins will be busy verifying each > scripts in the repo to make sure it builds fine against slackware-current, > which will be a moving target since Pat usually have a long period of > testing before he declares stable release. > Some of these scripts have been checked and fixed by Ponce so it gives a > headstart for us, but we have over 9k scripts (per December 2023) and it's > growing each week. There are tons of work to make sure the new repo is ready > when next Slackware is released and we are targeting for same-day release > (if it's possible). I realize that the SBo volunteers do a lot of work for the Slackware community, and I would not want to unduly add to the workload. Having said that, would the work load be acceptable if (a) you created the categories (fonts and Slackware-specific), and (b) whenever a maintainer puts in a new version, it goes into the new category. Cheers. Jim From willysr at slackbuilds.org Fri Mar 22 01:48:59 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 22 Mar 2024 08:48:59 +0700 Subject: [Slackbuilds-users] suggestion for a new category for fonts In-Reply-To: References: <744553fa-0b00-4533-9fc5-2d53d113eade@slackbuilds.org> Message-ID: <42a65e83-2acf-4842-b5a4-d915b51d03ca@slackbuilds.org> > I realize that the SBo volunteers do a lot of work for the Slackware > community, and I would not want to unduly add to the workload. Having said > that, would the work load be acceptable if > (a) you created the categories (fonts and Slackware-specific), and > (b) whenever a maintainer puts in a new version, it goes into the new > category. moving category is more work during normal cycle because you have to move the files via git and during public update, we need to remove the leftover tarball and signature of it. It's ok for small number of scripts (less than 5), but if you do massive move on a week, that's a lot of work and we might slip few of them (it happened before until someone posted on LQ and we had massive cleanups few weeks ago) during development cycle, since we don't have any repository, tarball, and signatures, we only work in git tree. Those tarball and signatures will be created when new repository is ready. This is the perfect time actually, but i would rather spend my time fixing scripts not working rather than moving scripts :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3F617144D7238786.asc Type: application/pgp-keys Size: 8363 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From list+sbo at vahedi.org Fri Mar 22 09:10:33 2024 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Fri, 22 Mar 2024 09:10:33 +0000 Subject: [Slackbuilds-users] skypeforlinux cannot be fetched Message-ID: Hi Mario, I cannot install "skypeforlinux" because it cannot fetch the specified Debian package from Skype's website: ------------------------8<----------------------- Processing skypeforlinux skypeforlinux: skypeforlinux not found in /var/cache/sbopkg. --2024-03-22 09:21:59-- https://repo.skype.com/deb/pool/main/s/skypeforlinux/skypeforlinux_8.94.0.428_amd64.deb Resolving repo.skype.com (repo.skype.com)... 23.210.16.177, 2a02:26f0:c900:490::1263, 2a02:26f0:c900:4ae::1263 Connecting to repo.skype.com (repo.skype.com)|23.210.16.177|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2024-03-22 09:21:59 ERROR 404: Not Found. ------------------------8<----------------------- Checking "https://repo.skype.com/deb/pool/main/s/skypeforlinux/", I only see versions "8.106.*" till "8.110.*". I think it is a matter of upgrading the package. Since you're the maintainer and probably know any possible issues, I'm kindly asking you to look into this. Cheers, Shahab From j+sbo-users at maschinengott.de Fri Mar 22 09:33:01 2024 From: j+sbo-users at maschinengott.de (j+sbo-users at maschinengott.de) Date: Fri, 22 Mar 2024 10:33:01 +0100 Subject: [Slackbuilds-users] skypeforlinux cannot be fetched In-Reply-To: References: Message-ID: As a stopgap: https://slackware.uk/sbosrcarch/by-name/network/skypeforlinux/skypeforlinux_8.94.0.428_amd64.deb Or just try if the SlackBuild still works with the most recent version: # VERSION=8.110.76.107 skypeforlinux.SlackBuild cheers, jay On 22.03.24 10:10, Shahab Vahedi via SlackBuilds-users wrote: > Hi Mario, > > I cannot install "skypeforlinux" because it cannot fetch the specified > Debian package from Skype's website: From artourter at gmail.com Fri Mar 22 10:03:25 2024 From: artourter at gmail.com (Greg Tourte) Date: Fri, 22 Mar 2024 10:03:25 +0000 Subject: [Slackbuilds-users] skypeforlinux cannot be fetched In-Reply-To: References: Message-ID: skype moved the skype4linux packages to snap and no longer provides new ones as debs or rpms. The latest snap version is at the time of writing 8.115.0.215. I have tried to figure out how to get the url for these but don't know anything about snaps so failed. Cheers Greg On Fri, 22 Mar 2024 at 09:33, wrote: > As a stopgap: > > https://slackware.uk/sbosrcarch/by-name/network/skypeforlinux/skypeforlinux_8.94.0.428_amd64.deb > Or just try if the SlackBuild still works with the most recent version: > # VERSION=8.110.76.107 skypeforlinux.SlackBuild > > cheers, jay > > On 22.03.24 10:10, Shahab Vahedi via SlackBuilds-users wrote: > > Hi Mario, > > > > I cannot install "skypeforlinux" because it cannot fetch the specified > > Debian package from Skype's website: > _______________________________________________ > 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 list+sbo at vahedi.org Fri Mar 22 10:14:05 2024 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Fri, 22 Mar 2024 10:14:05 +0000 Subject: [Slackbuilds-users] skypeforlinux cannot be fetched In-Reply-To: References: Message-ID: <3d389130d5fc70ac67aa4eacefe2a794e9b422ff@vahedi.org> March 22, 2024, Jay via SlackBuilds-users wrote: > As a stopgap: https://slackware.uk/sbosrcarch/by-name/network/skypeforlinux/skypeforlinux_8.94.0.428_amd64.deb Thank you very much! I didn't know about this "*/sbosrcarch/by-name/*". The package built this way works pretty well on my system. See below. > Or just try if the SlackBuild still works with the most recent version: > > # VERSION=8.110.76.107 skypeforlinux.SlackBuild I just tried it and I see a few things that I don't like: 1. In settings, I could not disable the _optional_ diagnostics data collection. 2. Once again, in settings, clicking on "Default device" for "Speaker" and "Mic" reveals no drop down menu. The older version, lists the devices. 3. There's an initial setup in the older version that you use to test. 4. The shortcut is called "Skype Preview". I will stick with the older version from slackware.uk. However, the script on SlackBuilds.org remain broken. If the maintainer/list agrees, I will submit a new package, only changing the URL to slackware.uk. Cheers, Shahab From j+sbo-users at maschinengott.de Fri Mar 22 10:58:28 2024 From: j+sbo-users at maschinengott.de (j+sbo-users at maschinengott.de) Date: Fri, 22 Mar 2024 11:58:28 +0100 Subject: [Slackbuilds-users] skypeforlinux cannot be fetched In-Reply-To: <3d389130d5fc70ac67aa4eacefe2a794e9b422ff@vahedi.org> References: <3d389130d5fc70ac67aa4eacefe2a794e9b422ff@vahedi.org> Message-ID: Hey Shahab, On 22.03.24 11:14, Shahab Vahedi via SlackBuilds-users wrote: > March 22, 2024, Jay via SlackBuilds-users wrote: > >> As a stopgap: https://slackware.uk/sbosrcarch/by-name/network/skypeforlinux/skypeforlinux_8.94.0.428_amd64.deb > > Thank you very much! I didn't know about this "*/sbosrcarch/by-name/*". > The package built this way works pretty well on my system. See below. People using 'sbopkg' to manage their SBo packages get an option to get sources from this archive automatically if a normal download fails. If you don't plan on taking over maintenance, I believe it would be better not do a submission. It will be easier for the SBo admins to just change it in git without a submission, and one of them will most certainly read this soon. cheers, Jay From rshepard at appl-ecosys.com Fri Mar 22 13:03:27 2024 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 22 Mar 2024 06:03:27 -0700 (PDT) Subject: [Slackbuilds-users] Kernel upgrade question Message-ID: <36257898-3f28-d71d-6097-cf3a5825972@appl-ecosys.com> I'm setting up 15.0 on a desktop and need to run rsync_slackware_patches.sh. Last December there was a kernel upgrade. It's been a very long time since I last upgraded a kernel and I remember that it should be done manually rather than allowing the patches upgrade script do it. What I have forgotten is where there is an upgrade blacklist that will not download and install kernels when other patches are upgraded by the script. Please point me to the proper file so I can bring this host, and my laptop, current with 15.0 patches, and separately the kernel. TIA, Rich From j+sbo-users at maschinengott.de Fri Mar 22 13:07:31 2024 From: j+sbo-users at maschinengott.de (j+sbo-users at maschinengott.de) Date: Fri, 22 Mar 2024 14:07:31 +0100 Subject: [Slackbuilds-users] Kernel upgrade question In-Reply-To: <36257898-3f28-d71d-6097-cf3a5825972@appl-ecosys.com> References: <36257898-3f28-d71d-6097-cf3a5825972@appl-ecosys.com> Message-ID: Rich, this question has nothing to do with SlackBuilds.org. Please seek help elsewhere. (e.g. https://www.linuxquestions.org/questions/slackware-14/) From rshepard at appl-ecosys.com Fri Mar 22 14:03:04 2024 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 22 Mar 2024 07:03:04 -0700 (PDT) Subject: [Slackbuilds-users] Kernel upgrade question In-Reply-To: References: <36257898-3f28-d71d-6097-cf3a5825972@appl-ecosys.com> Message-ID: <2394241-f4bf-fe56-67ff-8f498ead757@appl-ecosys.com> On Fri, 22 Mar 2024, j+sbo-users at maschinengott.de wrote: > Rich, this question has nothing to do with SlackBuilds.org. Please seek help > elsewhere. (e.g. https://www.linuxquestions.org/questions/slackware-14/) Well, while not SBo-specific I thought someone here had the answer. Bye, Rich From j+sbo-users at maschinengott.de Fri Mar 22 14:25:53 2024 From: j+sbo-users at maschinengott.de (j+sbo-users at maschinengott.de) Date: Fri, 22 Mar 2024 15:25:53 +0100 Subject: [Slackbuilds-users] Kernel upgrade question In-Reply-To: <2394241-f4bf-fe56-67ff-8f498ead757@appl-ecosys.com> References: <36257898-3f28-d71d-6097-cf3a5825972@appl-ecosys.com> <2394241-f4bf-fe56-67ff-8f498ead757@appl-ecosys.com> Message-ID: Probably. But you're wasting dozens of peoples' time that are here to discuss/support _SBo_, and not to be your free personal support agent for anything that comes up. This has been going on long enough. Please cease it. (Note I'm not a moderator of this list, just a user.) Bye. Jay On 22.03.24 15:03, Rich Shepard wrote: > On Fri, 22 Mar 2024, j+sbo-users at maschinengott.de wrote: > >> Rich, this question has nothing to do with SlackBuilds.org. Please >> seek help elsewhere. (e.g. >> https://www.linuxquestions.org/questions/slackware-14/) > > Well, while not SBo-specific I thought someone here had the answer. > > Bye, > > Rich From willysr at slackbuilds.org Sat Mar 23 01:31:16 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 23 Mar 2024 08:31:16 +0700 Subject: [Slackbuilds-users] Updates - 20240323.1 Message-ID: <0974de2c-9588-4bd0-a51d-1b5e500a200f@slackbuilds.org> We have 2 major bumps this week, protobuf (again) and webkit2gtk{4.1}. While we have tried to catch all build failures using our CI engine, we might miss runtime failures. Please help testing your scripts if it happened to use one of those two new versions. We also just found out that our GitLab CI engine is not working in the last few days, so we are looking into this case, but the one in github is still working fine. Hopefully it will be restored as soon as possible. Sat Mar 23 01:18:40 UTC 2024 academic/cryptominisat: Updated for version 5.11.21. academic/ent: Use https URLs. audio/asap: Updated for version 6.0.3. audio/aseqview: Fix download URL. audio/clementine: Fix build with protobuf3. audio/connie: Fix homepage. audio/jack1: Updated for version 0.126.0. audio/podget: Updated for version 0.9.3. audio/puddletag: Version bump to 2.3.0 audio/rubberband: Updated for version 3.3.0. audio/tap_plugins: Fix download URL. audio/vocoder-ladspa: Fix URLs. audio/vocoder: Fix URLs. audio/volumeicon: Fix download URL. audio/xmms-jack: Fix URLs. desktop/cwm: Updated for version 7.4. desktop/icewm: Updated for version 3.4.6. desktop/nwg-displays: Updated for version 0.3.15. desktop/nwg-displays: Updated for version 0.3.16. desktop/nwg-drawer: Updated for version 0.4.7. desktop/nwg-hello: Updated for version 0.1.8. desktop/nwg-look: Updated for version 0.2.7. desktop/nwg-menu: Updated for version 0.1.3. desktop/nwg-panel: Updated for version 0.9.26. desktop/salmon: Fix URLs. desktop/wmcpuwatch: Fix download URL, add doinst.sh. desktop/wmnet: Fix URLs. desktop/wofi-pass: Updated for version 24.0.2 desktop/xsecurelock: Make pandoc-bin an optional dependency development/SQLAlchemy: Updated for version 2.0.28. development/apache-log4cxx: Fix download URL. development/as31: Fix URLs. development/aws-cdk: Updated for version 2.133.0. development/bbcsdl: Updated script development/bsdiff: Fix download URL. development/devhelp: compress man page. development/github-desktop: Updated for version 3.3.10. development/hexe: Fix homepage. development/jdk: Updated for version 8u391. development/jupyter_packaging: Update for 0.12.3 development/mongodb-compass: Updated for version 1.42.3. development/msbasic2ascii: Fix URLs. development/nvidia-container-toolkit: Added (NVidia container toolkit). development/pgmodeler: Updated for version 1.1.1. development/postman: Updated for version 10.24.3 development/protobuf3: Updated for version 26.0. development/pycharm: Updated for version 2023.3.5.233.15026.15. development/remake: Updated for version 4.3+dbg_1.6_4 development/uftrace: Updated for version 20240313_1919a15 development/vscode-bin: Updated for version 1.87.2. development/wxHexEditor: Update script. games/advancemame: Updated for version 3.10. games/alephone: Updated for version 20240119. games/citra: Updated for version 0.2090. games/joy2key: Fix download URL. games/marathon-data: Updated for version 20240119. games/marathon-infinity-data: Updated for version 20240119. games/marathon2-data: Updated for version 20240119. games/pioneer: Updated for version 20240314. gis/OWSLib: Updated for version 0.30.0. graphics/MaterialX: Fix github URLs. graphics/brlcad: updated for version 7.38.2 graphics/converseen: Updated for version 0.12.2.0. graphics/converseen: Updated for version 0.12.2.1. graphics/gifsicle: Updated for version 1.95. graphics/imv: Updated for version 4.5.0, add libjxl support. graphics/kuickshow: Updated for version 20240316_791359a. graphics/mozjpeg: Updated for version 4.1.5. graphics/pqiv: Updated for version 2.13.1. graphics/tgif-QPL: Fix download URL. graphics/vuescan: Updated for version 9.8.30. libraries/coeurl: Add patch. libraries/girara: Updated for version 0.4.2. libraries/libaec: Updated for version 1.1.3. libraries/libminizip: Update for 1.2.13 (+new maintainer) libraries/libwpe: Updated for version 1.16.0. libraries/openimagedenoise: Added (High-Performance Denoising Library). libraries/openvkl: Added (Intel Open Volume Kernel Library). libraries/ospray: Added (Ray Tracing Engine). libraries/ospray_studio: Added (interactive visualization and ray tracing application). libraries/protobuf-c: Fix build with new protobuf. libraries/rkcommon: Added (Intel RenderKit Utilities). libraries/simde: Added (Implementations of SIMD). libraries/tree-sitter: Updated for version 0.22.2 libraries/unixODBC: Updated for version 2.3.12. libraries/webkit2gtk4.1: Fix BUILD. libraries/webkit2gtk4.1: Fix build on x86. libraries/webkit2gtk4.1: Updated for version 2.44.0. libraries/webkit2gtk: Fix build on x86. libraries/webkit2gtk: Updated for version 2.44.0. misc/bitwarden-desktop: revert to version 2024.1.0 misc/ghostpcl: Updated for version 10.03.0. misc/ramdefrag: Fix homepage URL & maintainer email misc/xdelta: Fix download URL. multimedia/guvcview: Updated for version 2.1.0. multimedia/lightspark: Updated for version 0.8.7. multimedia/podcastparser: move to libraries. multimedia/sickchill: Support newer SQLAlchemy multimedia/vkeybd: Fix download URL. network/csync: Fix download URL. network/cyrus-imapd: Updated for version 3.2.12. network/discord: Version bump to 0.0.46 network/dropbox: Updated for version 195.4.4995. network/librewolf: Updated for version 123.0.1 network/midori: Removed (abandoned upstream). network/mumble-server: Added ICE option network/mumble-server: update build number network/mumble: fix gtav plugin 32-bit compile network/nheko: Update script. network/nyxt: Updated for version 3.11.5. network/opera: Updated for version 108.0.5067.29. network/opera: Updated for version 108.0.5067.40. network/signal-desktop: Updated for version 7.3.0. network/tcpbench: Added (OpenBSD tcpbench). network/telegram: Updated for version 4.15.2. network/thorium-browser: Updated for version 122.0.6261.132. network/tor-browser: Updated for version 13.0.13. network/unbound: Updated for version 1.19.3. network/vimb: Updated for version 3.7.0. network/vivaldi: Updated for version 6.6.3271.53. network/xmrig: Updated for version 6.21.1. network/zabbix_agent2: Added (new generation of Zabbix agent). network/zoom-linux: Updated for version 5.17.11.3835 office/mupdf: Updated for version 1.23.11. office/zathura: Updated for version 0.5.4. perl/perl-Archive-Zip: Updated for version 1.68. perl/perl-Clone: Updated for version 0.46. perl/perl-HTTP-CookieJar: Added (Perl Module). perl/perl-Net-LibIDN2: Added (Perl bindings for GNU Libidn2). perl/perl-file-listing: Updated for version 6.16. perl/perl-html-parser: Updated for version 3.82. perl/perl-html-tagset: Updated for version 3.24. perl/perl-http-message: Updated dependencies. perl/perl-lwp-mediatypes: Updated for version 6.04. python/python-axolotl-curve25519: Use python2 for python 2.x. python/python-axolotl: Use python2 for python 2.x. python/python-mysql-replication: Updated for version 1.0.7. python/python3-PyMuPDF: Updated for version 1.23.26. python/python3-backlash: updated for version 0.3.2 python/python3-boto3: Update for 1.34.14 python/python3-geventhttpclient: Updated for version 2.0.12. python/python3-levenshtein: Added (C extension module for fast computation). python/python3-paste: updated for version 3.8.0 python/python3-pyinotify: Added (Python3 of pyinotify). python/python3-rapidfuzz: Added (Fuzzy string matching). python/python3-smart_open: Update for 7.0.1 python/python3-threadpoolctl: Version bump to 3.4.0 python/python3-types-python-dateutil: Update for 2.9.0.20240316 python/python3-unearth: Version bump to 0.15.0 python/python3-validators: Version bump to 0.23.2 python/rfc6555: Use python2 for python 2.x. ruby/ruby-build: Updated for version 20240319. system/Iosevka-aile: Updated for version 29.0.2. system/Iosevka-etoile: Updated for version 29.0.2. system/Iosevka-slab: Updated for version 29.0.2 system/Iosevka: Updated for version 29.0.2 system/OpenSnitch: Update dep. system/dina-font: Fix download URL. system/distrobox: Updated for version 1.7.0.1. system/docker-compose: Updated for version 2.26.0 system/fish: Updated for version 3.7.1. system/isomd5sum: Updated for version 1.2.4. system/jenkins: Updated for version 2.440.2. system/kitty: Updated for version 0.33.1 system/limine: Updated for version 7.1.0 system/locust: Updated for version 2.24.1. system/lynis: Updated for version 3.1.0. system/lynis: Updated for version 3.1.1. system/mongodb: Updated for version 7.0.7. system/nvidia-driver: Updated for version 550.67. system/nvidia-kernel: Updated for version 550.67. system/nvidia-legacy390-kernel: Fix typo. system/nvidia-open-kernel: Updated for version 550.67. system/onefetch: Updated for version 2.20.0. system/rmw: Updated for version 0.9.2. system/sarasa-gothic: Updated for version 1.0.7. system/sbpkg: Updated for version 1.0.5. system/sbpkg: Updated for version 1.0.6. system/slackroll: Updated for version v55. system/ttf-babelstone-cjk: update md5sum system/watch-fs: Update dep. system/yash: Updated for version 2.56.1. system/yelp: Update 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 slack at giand.it Sat Mar 23 17:44:29 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Sat, 23 Mar 2024 18:44:29 +0100 Subject: [Slackbuilds-users] Updates - 20240323.1 In-Reply-To: <0974de2c-9588-4bd0-a51d-1b5e500a200f@slackbuilds.org> References: <0974de2c-9588-4bd0-a51d-1b5e500a200f@slackbuilds.org> Message-ID: <613fea9b-4fb3-430a-8977-21d280233a7c@giand.it> Il 23/03/24 02:31, Willy Sudiarto Raharjo ha scritto: > We have 2 major bumps this week, protobuf (again) and webkit2gtk{4.1}. > While we have tried to catch all build failures using our CI engine, > we might miss runtime failures. Please help testing your scripts if it > happened to use one of those two new versions. I rewrite a message about the updates of last week that it is lost ITK slackbuild requires to be fixed for build against gtest 1.12.1. The build works if gtest is not installed, I think with a bundle googletest, but if a googletest system is found, it is used by default. Unfortunately cmake returns an error if gtest 1.12.1 is installed. I solved passing this flag to cmake: -DITK_USE_SYSTEM_GOOGLETEST=OFF This should be added in the slackbuild script, otherwise ITK must be built after uninstalling gtest Thanks Giancarlo -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From slack at giand.it Sat Mar 23 17:54:29 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Sat, 23 Mar 2024 18:54:29 +0100 Subject: [Slackbuilds-users] Updates - 20240323.1 In-Reply-To: <613fea9b-4fb3-430a-8977-21d280233a7c@giand.it> References: <0974de2c-9588-4bd0-a51d-1b5e500a200f@slackbuilds.org> <613fea9b-4fb3-430a-8977-21d280233a7c@giand.it> Message-ID: <8a791acb-d47d-4231-9695-cd5a52d6fc53@giand.it> Il 23/03/24 18:44, Giancarlo Dess? ha scritto: > Il 23/03/24 02:31, Willy Sudiarto Raharjo ha scritto: >> We have 2 major bumps this week, protobuf (again) and webkit2gtk{4.1}. >> While we have tried to catch all build failures using our CI engine, >> we might miss runtime failures. Please help testing your scripts if >> it happened to use one of those two new versions. > I rewrite a message about the updates of last week that it is lost > > ITK slackbuild requires to be fixed for build against gtest 1.12.1. > The build works if gtest is not installed, I think with a bundle > googletest, but if a googletest system is found, it is used by > default. Unfortunately cmake returns an error if gtest 1.12.1 is > installed. I solved passing this flag to cmake: > > -DITK_USE_SYSTEM_GOOGLETEST=OFF > > This should be added in the slackbuild script, otherwise ITK must be > built after uninstalling gtest > > Thanks > > Giancarlo > I could also take? ITK since it is still orphanized. ITK cannot be updated to a greater version because its dependencies OTB and OTB-legacy do not support ITK versions greater than 4.x. New versions of ITK have dropped a deprecated module that is required by Orfeo ToolBox. If a new version of ITK could be useful as dependency for other packages (at the moment it seems not needed), an additional package is required (as ITK5) but it could not coexists with other installations of ITK. -- ********************************************************* Giancarlo Dess? https://www.giand.it https://github.com/giandex Slackware Linux... because it works! ********************************************************* From list+sbo at vahedi.org Sat Mar 23 19:09:52 2024 From: list+sbo at vahedi.org (Shahab Vahedi) Date: Sat, 23 Mar 2024 20:09:52 +0100 Subject: [Slackbuilds-users] skypeforlinux cannot be fetched In-Reply-To: Message-ID: <4e9fde51-74cb-4d9c-a85b-c47c474ed77a@vahedi.org> Hi Jay, March 22, 2024, Jay via SlackBuilds-users wrote: > People using 'sbopkg' to manage their SBo packages get an option to get > sources from this archive automatically if a normal download fails. How can I trigger this fall-back mechanism in "sbopkg"? I've checked the /usr/sbin/sbopkg script and it looks like that "make_archive_url()" should automatically take care of it through the the default hardcoded "http://slackware.uk/sbosrcarch" URL. However, the fall-back doesn't kick in. I've also tried uncommenting the "SRC_REPO" line in /etc/sbo/sbopkg.conf that points to "http://slackware.uk/sbosrcarch" to no avail. Am I doing something wrong or do I need to investigate the situation better? Cheers, Shahab From willysr at slackbuilds.org Sat Mar 23 23:50:53 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 24 Mar 2024 06:50:53 +0700 Subject: [Slackbuilds-users] Updates - 20240323.1 In-Reply-To: <613fea9b-4fb3-430a-8977-21d280233a7c@giand.it> References: <0974de2c-9588-4bd0-a51d-1b5e500a200f@slackbuilds.org> <613fea9b-4fb3-430a-8977-21d280233a7c@giand.it> Message-ID: > ITK slackbuild requires to be fixed for build against gtest 1.12.1. The > build works if gtest is not installed, I think with a bundle googletest, > but if a googletest system is found, it is used by default. > Unfortunately cmake returns an error if gtest 1.12.1 is installed. I > solved passing this flag to cmake: > > -DITK_USE_SYSTEM_GOOGLETEST=OFF > > This should be added in the slackbuild script, otherwise ITK must be > built after uninstalling gtest please send PR/MR for this issue -- 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 mario at slackware.hr Sun Mar 24 03:09:54 2024 From: mario at slackware.hr (Mario) Date: Sun, 24 Mar 2024 04:09:54 +0100 Subject: [Slackbuilds-users] skypeforlinux cannot be fetched In-Reply-To: References: Message-ID: On 3/22/24 10:10 AM, Shahab Vahedi wrote: > I cannot install "skypeforlinux" because it cannot fetch the specified > Debian package from Skype's website: > --2024-03-22 09:21:59--https://repo.skype.com/deb/pool/main/s/skypeforlinux/skypeforlinux_8.94.0.428_amd64.deb > HTTP request sent, awaiting response... 404 Not Found It looks like the last stable version of skypeforlinux is now at 8.109.0.209. I am unsure what the future of this script is, but for now I fixed it in my branch. Regards, -- Mario -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Sun Mar 24 07:51:57 2024 From: urchlay at slackware.uk (B. Watson) Date: Sun, 24 Mar 2024 03:51:57 -0400 (EDT) Subject: [Slackbuilds-users] skypeforlinux cannot be fetched In-Reply-To: <4e9fde51-74cb-4d9c-a85b-c47c474ed77a@vahedi.org> References: <4e9fde51-74cb-4d9c-a85b-c47c474ed77a@vahedi.org> Message-ID: On Sat, 23 Mar 2024, Shahab Vahedi via SlackBuilds-users wrote: > Hi Jay, > > March 22, 2024, Jay via SlackBuilds-users wrote: > >> People using 'sbopkg' to manage their SBo packages get an option to get >> sources from this archive automatically if a normal download fails. > > How can I trigger this fall-back mechanism in "sbopkg"? > > I've checked the /usr/sbin/sbopkg script and it looks like that > "make_archive_url()" should automatically take care of it through the > the default hardcoded "http://slackware.uk/sbosrcarch" URL. However, the > fall-back doesn't kick in. > > I've also tried uncommenting the "SRC_REPO" line in /etc/sbo/sbopkg.conf > that points to "http://slackware.uk/sbosrcarch" to no avail. Am I doing > something wrong or do I need to investigate the situation better? No, it's broken, and has never worked properly, despite what people have said. The only time it works correctly is if wget succeeds in downloading *something*, but the downloaded file's md5sum doesn't match the .info file. If wget fails to download anything at all (404 not found, or site down entirely), the archive stuff doesn't get called at all. I know this because I'm the one who put the sbosrcarch support in sbopkg, I checked it into git as a proof of concept, and hoped that someone who *knows* the sbopkg codebase would be able to finish it. But no such person exists (or, anyway, no such person is actively working on sbopkg any more). The sbopkg codebase is utterly alien to my ways of thinking about code. It's not "bad" or "wrong", it obviously works very well. But I found it difficult to follow the logic, so I punted and tried to hand it over to someone who already knew how it worked. Finishing the job is now on my TODO list, I'll go back and work out a better solution, one that actually works. I had honestly forgot about this (I'm not a sbopkg user, myself), so thanks for reminding me. From slack at giand.it Sun Mar 24 08:56:56 2024 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=C3=AC?=) Date: Sun, 24 Mar 2024 09:56:56 +0100 Subject: [Slackbuilds-users] Updates - 20240323.1 In-Reply-To: References: <0974de2c-9588-4bd0-a51d-1b5e500a200f@slackbuilds.org> <613fea9b-4fb3-430a-8977-21d280233a7c@giand.it> Message-ID: <1a6f5b30-73a1-4cb7-aff1-d1facd0fcdf8@giand.it> Il 24/03/24 00:50, Willy Sudiarto Raharjo ha scritto: >> ITK slackbuild requires to be fixed for build against gtest 1.12.1. >> The build works if gtest is not installed, I think with a bundle >> googletest, but if a googletest system is found, it is used by >> default. Unfortunately cmake returns an error if gtest 1.12.1 is >> installed. I solved passing this flag to cmake: >> >> -DITK_USE_SYSTEM_GOOGLETEST=OFF >> >> This should be added in the slackbuild script, otherwise ITK must be >> built after uninstalling gtest > > please send PR/MR for this issue Sorry, I don't know what PR/MR means. I've just now submitted a new tarball with the flag added in the slackbuild script -- ********************************************************* 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 Sun Mar 24 10:39:08 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 24 Mar 2024 17:39:08 +0700 Subject: [Slackbuilds-users] Updates - 20240323.1 In-Reply-To: <1a6f5b30-73a1-4cb7-aff1-d1facd0fcdf8@giand.it> References: <0974de2c-9588-4bd0-a51d-1b5e500a200f@slackbuilds.org> <613fea9b-4fb3-430a-8977-21d280233a7c@giand.it> <1a6f5b30-73a1-4cb7-aff1-d1facd0fcdf8@giand.it> Message-ID: <469eb05d-528d-4c63-8f1a-e15dbc2381cd@slackbuilds.org> >> please send PR/MR for this issue > > Sorry, I don't know what PR/MR means. I've just now submitted a new > tarball with the flag added in the slackbuild script pull request (github) merge request (gitlab) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Mar 25 15:18:16 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 25 Mar 2024 22:18:16 +0700 Subject: [Slackbuilds-users] Help on testing netdata 1.45.0 Message-ID: <51c50c7e-46f8-4f75-bee6-102213c1ac2b@slackbuilds.org> Hi i just bumped netdata to 1.45.0 and since this is a major changes compared to 1.44.x, if you are using this package, please help by testing the new version (mind the new dependencies) changes/commit can be seen here: https://git.slackbuilds.org/slackbuilds/log/?h=netdata if no major issue, it will be merged on this week's 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 rshepard at appl-ecosys.com Wed Mar 27 20:04:27 2024 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 27 Mar 2024 13:04:27 -0700 (PDT) Subject: [Slackbuilds-users] Running rxvt-unicode Message-ID: <5cecfd4c-70d8-687d-663a-fbb533d81e0@appl-ecosys.com> Setting up my laptop with a fully patched 15.0 and multilib. I've used the urxvt terminal emulated in previous versions and the SBo repo says that rxvt has been replaced in 15.0 with rxvt-unicode. I find the file rxvt-unicode in /usr/share/terminfo/r/ but it's not executable. How do I tell xfce4 to use rxvt-unicode as the terminal emulator? TIA, Rich From marav8 at free.fr Wed Mar 27 20:18:26 2024 From: marav8 at free.fr (marav) Date: Wed, 27 Mar 2024 21:18:26 +0100 Subject: [Slackbuilds-users] Running rxvt-unicode In-Reply-To: <5cecfd4c-70d8-687d-663a-fbb533d81e0@appl-ecosys.com> References: <5cecfd4c-70d8-687d-663a-fbb533d81e0@appl-ecosys.com> Message-ID: <77b92c33-d35b-43ac-94d4-9253e10c6767@free.fr> Le 27/03/2024 ? 21:04, Rich Shepard a ?crit?: > Setting up my laptop with a fully patched 15.0 and multilib. I've used > the > urxvt terminal emulated in previous versions and the SBo repo says > that rxvt > has been replaced in 15.0 with rxvt-unicode. > > I find the file rxvt-unicode in /usr/share/terminfo/r/ but it's not > executable. How do I tell xfce4 to use rxvt-unicode as the terminal > emulator? > > TIA, > > Rich > _______________________________________________ > 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/ > Hi Rich The executable is located here : /usr/bin/urxvt -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Wed Mar 27 20:33:47 2024 From: urchlay at slackware.uk (B. Watson) Date: Wed, 27 Mar 2024 16:33:47 -0400 (EDT) Subject: [Slackbuilds-users] Running rxvt-unicode In-Reply-To: <5cecfd4c-70d8-687d-663a-fbb533d81e0@appl-ecosys.com> References: <5cecfd4c-70d8-687d-663a-fbb533d81e0@appl-ecosys.com> Message-ID: <4151bf5-90f0-178a-6f52-1c2757d5ec15@slackware.uk> On Wed, 27 Mar 2024, Rich Shepard wrote: > I find the file rxvt-unicode in /usr/share/terminfo/r/ but it's not > executable. How do I tell xfce4 to use rxvt-unicode as the terminal > emulator? Again, wrong list for this question. Absolutely nothing to do with SBo. It's not even a Slackware-specific question. Most likely, if you just do a google or duckduckgo search for something like "set default terminal in xfce4", you will be illuminated. From rshepard at appl-ecosys.com Wed Mar 27 20:45:09 2024 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 27 Mar 2024 13:45:09 -0700 (PDT) Subject: [Slackbuilds-users] Running rxvt-unicode In-Reply-To: <4151bf5-90f0-178a-6f52-1c2757d5ec15@slackware.uk> References: <5cecfd4c-70d8-687d-663a-fbb533d81e0@appl-ecosys.com> <4151bf5-90f0-178a-6f52-1c2757d5ec15@slackware.uk> Message-ID: <57ace58-ae3b-5b1c-9848-19e4b8f14c36@appl-ecosys.com> On Wed, 27 Mar 2024, B. Watson wrote: > Again, wrong list for this question. Absolutely nothing to do with SBo. > It's not even a Slackware-specific question. B, I found the information on the SBo repo. > Most likely, if you just do a google or duckduckgo search for something > like "set default terminal in xfce4", you will be illuminated. I need to install it first. A new search on the laptop found it was not installed from the 15.0 ap source. Will fix that. Thanks, Rich From rshepard at appl-ecosys.com Wed Mar 27 21:53:21 2024 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 27 Mar 2024 14:53:21 -0700 (PDT) Subject: [Slackbuilds-users] Running rxvt-unicode In-Reply-To: <77b92c33-d35b-43ac-94d4-9253e10c6767@free.fr> References: <5cecfd4c-70d8-687d-663a-fbb533d81e0@appl-ecosys.com> <77b92c33-d35b-43ac-94d4-9253e10c6767@free.fr> Message-ID: <24988587-72f4-6b2c-2ce2-8ff1f5dbf060@appl-ecosys.com> On Wed, 27 Mar 2024, marav wrote: > The executable is located here : /usr/bin/urxvt Marav, I learned that urxvt was not installed by the 15.0 installer while other xap applications were. So I cd'd to the file tree and installed it. It's now up and running. Thanks very much, Rich From willysr at slackbuilds.org Sat Mar 30 03:02:37 2024 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 30 Mar 2024 10:02:37 +0700 Subject: [Slackbuilds-users] Updates - 20240330.1 Message-ID: <4b67b2d0-c8cb-498b-96a4-4e4817534b15@slackbuilds.org> For next week schedule, it will be 1 day ahead due to my traveling schedule, so make sure to send PR/MR/updates early. Gitlab CI engine is now fixed so you can start sending Merge Request again on gitlab platform. Another note for those running -current, Pat just updated Python3 to 3.11.x and it places the python libraries under /usr/lib for both i586 and x86_64 and this may cause some python scripts to be broken. It's relatively easy to fix: you just need change /usr/lib${LIBDIRSUFFIX} with /usr/lib* within the script and it should work fine. You may want to recompile all python3 scripts on your machines in order to get all the python3 modules built under python 3.11.x Sat Mar 30 02:47:11 UTC 2024 academic/cryptominisat: Fix build. academic/gaiasky: Updated for version 3.6.0. academic/louvain-community: Added (Louvain Detection Library). audio/acousticbrainz-gui: Fix github URL. audio/acousticbrainz-music-extractor: New maintainer, new downloads. audio/bitwig-studio: Updated for version 5.1.6. audio/fabla: Fix github URL. audio/jack1: Fix md5sums. audio/qmmp-qt5: Updated for version 1.6.6. audio/qpwgraph: Updated for version 0.6.3 desktop/dwmblocks: Update for 20240319 desktop/evilwm: Updated for version 1.4.3. desktop/i3minator: Fix github URL. desktop/i3situation: Fix github URL and doc perms. desktop/icewm: Updated for version 3.4.7. desktop/numix-icon-theme: Updated for version 23.12.02. desktop/nwg-bar: Fix github URL. desktop/nwg-panel: Updated for version 0.9.27. desktop/quickswitch-i3: Fix github URL. desktop/spectrwm: Fix github URL. desktop/stoken: Fix github URL. desktop/superkey-launch: Fix github URL. development/aws-cdk: Updated for version 2.134.0. development/cargo-c: Updated for version 0.9.31. development/cargo-vendor-filterer: Updated for version 0.5.13. development/cpan2tgz: Fix github URL. development/dpkg: Updated for version 1.22.6. development/dreampie: Fix github URL. development/eclipse-cpp: Updated for version 4.31. development/eclipse-java: Updated for version 4.31. development/eclipse-jee: Updated for version 4.31. development/eclipse-php: Updated for version 4.31. development/gambas3: Updated for version 3.19.1. development/ghidra: Updated for version 11.0.2 development/github-cli: Updated for version 2.46.0 development/heroku-cli: Updated for version 8.11.0. development/jupyter-nbformat: Update for 5.10.3 development/jupyter_core: Update for 5.7.1 development/lighttable: Fix github URL. development/love: Updated for version 11.5. development/meld3: Updated for version 3.22.2. development/mongodb-shell: Updated for version 2.2.1. development/mono: Updated for version 6.12.0.205. development/mosml: Fix github URL. development/nodejs: Updated for version 20.12.0. development/protobuf3: Re-enable python bindings. development/pyside-tools: Fix github URL. development/sbcl: Updated for version 2.4.3 development/z88dk: Updated for version 2.3. games/citra: Removed (upstream quit the project). games/crispy-doom: Fix github URL. games/ddnet: Added (Multiplayer games). games/ddnet: Remove duplicate code. games/einstein: Fix github URL. games/glxosd: Fix github URL. games/mednafen: Disable debugger. games/openmsx-debugger: Fix github URL. games/term2048: Fix github URL. games/yetris: Fix github URL. gis/OTB: Remove -j10. gis/pdal: Updated for version 2.7.0. graphics/jp2a: Fix github URL. graphics/mapcrafter: Fix github URL. ham/qlog: Updated for version 0.34.0. haskell/haskell-th-compat: Update maintainer. libraries/MDI_Library: Added (Code Interoperability via MDI). libraries/glfw3: Updated for version 3.4. libraries/jreen: Fix github URL. libraries/libmediainfo: Updated for version 24.03. libraries/libscrypt: Fix github URL. libraries/lua-md5: Fix github URL. libraries/luaevent: Fix github URL. libraries/netcdf-fortran: Fix github URL. libraries/ode: Updated for version 0.16.5. libraries/opencl-amd: Updated for version 22.20.3. libraries/scafacos: Added (Scalable Fast Coulomb Solver). libraries/wjelement: Fix github URL. misc/boxes: Fix github URL. misc/torrentinfo: Fix github URL. multimedia/QMPlay2: Updated for version 24.03.16. multimedia/mediainfo: Updated for version 24.03. multimedia/sickchill: Remove unnecessary validators version requirement multimedia/sickchill: Tweak shutdown/startup/restart for rc file network/AdGuardHome: Updated for version 0.107.46. network/Pyrit: Fix github URL. network/baikal: Updated for version 0.9.5. network/brave-browser: Updated for version 1.64.113. network/discord: Updated for version 0.0.47. network/emailrelay: Updated for version 2.5.2. network/floorp-bin: Added (Floorp Browser). network/go-sendxmpp: Updated for version 0.9.0. network/luakit: Updated for version 2.3.6. network/mullvadvpn-app: Updated for version 2024.1. network/nheko: Fix typo. network/opera: Updated for version 109.0.5097.35. network/postfix-pgsql: Updated for version 3.6.15 network/qbittorrent: Updated for version 4.6.4. network/rspamd: Updated for version 3.8.4 network/skypeforlinux: Updated for version 8.109.0.209. network/slack: Updated for version 4.37.94. network/vivaldi: Updated for version 6.6.3271.55. network/wireshark: Updated for version 4.2.4. network/wp-cli: Updated for version 2.10.0. office/libreoffice-helppack: Updated for version 24.2.2. office/libreoffice-langpack: Updated for version 24.2.2. office/libreoffice: Updated for version 24.2.2. perl/perl-PAR: Updated for version 1.020. python/pipdeptree: Updated for version 2.16.2. python/pyinotify: Removed (renamed to python3-pyinotify) python/python-importlib_metadata: Updated for version 7.1.0. python/python3-Flask-SQLAlchemy: Updated for version 3.1.1. python/python3-Flask-Security-Too: Updated for version 5.4.3. python/python3-build: Updated for version 1.2.1. python/python3-click-didyoumean: updated for version 0.3.1 python/python3-filelock: Updated for version 3.13.3. python/python3-findpython: Updated for version 0.6.0. python/python3-flask-paginate: Updated for version 2024.3.28. python/python3-flit_core: Fix build on current. python/python3-glances: Updated for version 3.4.0.5. python/python3-hatchling: Updated for version 1.22.4. python/python3-httpcore: Updated for version 1.0.5. python/python3-json5: Updated for version 0.9.24. python/python3-keyring: Update for 25.0.0 python/python3-kombu: updated for version 5.3.6 python/python3-libtmux: Updated for version 0.36.0. python/python3-maturin: Updated for version 1.5.1. python/python3-orjson: Updated for version 3.10.0. python/python3-pdfCropMargins: Updated for version 2.1.0. python/python3-pyasn1-modules: updated for version 0.4.0 python/python3-pyasn1: updated for version 0.6.0 python/python3-qtawesome: Update for 1.3.1 python/python3-smart_open: Update for 7.0.3 python/python3-tox: Updated for version 4.14.2. python/python3-trove-classifiers: Updated for version 2024.3.25. python/python3-unearth: Updated for version 0.15.1. python/sphinx-rtd-theme: Updated for version 2.0.0, new maintainer. python/sphinxcontrib-jquery: Added (python extension). system/Iosevka-slab: Updated for version 29.0.4 system/Iosevka: Updated for version 29.0.4 system/debootstrap: Updated for version 1.0.134. system/distrobox: Updated for version 1.7.1. system/docker-machine-kvm: Fix for the newer google-go-lang. system/dust: Updated for version 1.0.0. system/fio: Updated for version 3.37. system/jq: Fix build test failures associated with non-English modules system/ktls-utils: Added (TLS handshake utilities). system/letsencrypt: Fix build with python3 3.11.x. system/limine: Updated for version 7.2.0 system/netdata: Updated for version 1.45.0. system/pdfgrep: Updated for version 2.2.0. system/prometheus: Updated to version 2.51.0 system/qemu: Updated for version 8.2.2 system/slpkg: Updated for version 5.0.0. system/slpkg: Updated for version 5.0.1. system/sst: Updated for version 1.12. system/tmuxp: Updated for version 1.45.0. system/wine-staging: Updated for version 9.5. system/wine: script cleanup. system/yq: Updated for version 4.43.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From y.aleayoub at gmail.com Wed Mar 6 13:44:51 2024 From: y.aleayoub at gmail.com (Yousha Aleayoub) Date: Wed, 06 Mar 2024 13:44:51 -0000 Subject: [Slackbuilds-users] Broken package - skypeforlinux - 404 not found Message-ID: Hi The package "skypeforlinux" is broken and SBOPKG unable to install it. https://slackbuilds.org/repository/15.0/network/skypeforlinux/ "Source not found 404" -------------- next part -------------- An HTML attachment was scrubbed... URL: From lockywolf at gmail.com Tue Mar 19 11:57:19 2024 From: lockywolf at gmail.com (Vladimir Nikishkin) Date: Tue, 19 Mar 2024 11:57:19 -0000 Subject: [Slackbuilds-users] Linphone maintenance In-Reply-To: References: <2ab5e4ae-db8c-72e0-3e9b-bbea3f70bcc0@open-t.co.uk> <87eddn219d.fsf@laptop.lockywolf.net> <5ca1fd6b-2900-a951-174b-20bf7831aa6d@open-t.co.uk> <87plvqlvyf.fsf@laptop.lockywolf.net> Message-ID: You don't need more of an answer. Just update the hashes to the latest version and submit. I'm giving it to you. Sebastian Arcus ? 2024?3?19??? 19:31??? > On 19/03/2024 03:51, Lockywolf wrote: > > > > Sebastian Arcus writes: > > > >> 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? > > > > Is anybody going to take linphone-desktop away from me? > > I asked if I could take it over - I think we were waiting for an answer > from the admins > -------------- next part -------------- An HTML attachment was scrubbed... URL: From list at vahedi.org Fri Mar 22 10:09:49 2024 From: list at vahedi.org (Shahab Vahedi) Date: Fri, 22 Mar 2024 10:09:49 -0000 Subject: [Slackbuilds-users] skypeforlinux cannot be fetched In-Reply-To: References: Message-ID: <0fa8206056aff4afab896fac15be80a7ae8fde44@vahedi.org> March 22, 2024, Jay via SlackBuilds-users wrote: > As a stopgap: https://slackware.uk/sbosrcarch/by-name/network/skypeforlinux/skypeforlinux_8.94.0.428_amd64.deb Thank you very much! I didn't know about this "*/sbosrcarch/by-name/*". The package built this way works pretty well on my system. See below. > Or just try if the SlackBuild still works with the most recent version: > > # VERSION=8.110.76.107 skypeforlinux.SlackBuild I just tried it and I see a few things that I don't like: 1. In settings, I could not disable the _optional_ diagnostics data collection. 2. Once again, in settings, clicking on "Default device" for "Speaker" and "Mic" reveals no drop down menu. The older version, lists the devices. 3. There's an initial setup in the older version that you use to test. 4. The shortcut is called "Skype Preview". I will stick with the older version from slackware.uk. However, the script on SlackBuilds.org remain broken. If the maintainer/list agrees, I will submit a new package, only changing the URL to slackware.uk. Cheers, Shahab