From andrzej at telszewski.com Wed Sep 1 12:39:01 2021 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Wed, 1 Sep 2021 14:39:01 +0200 Subject: [Slackbuilds-users] acpi_call update In-Reply-To: References: Message-ID: <07af3a05-374d-b717-3e7f-adb747ebfdd6@telszewski.com> On 8/31/21 18:16, Diego Borghetti via SlackBuilds-users wrote: > Hi all, > > I hit this bug https://github.com/mkottman/acpi_call/issues/96 using acpi_call with tlp and notice that mkottman/acpi_call don't have any update in years. > > Following the comments, there is a fork that ArchLinux seems to be using https://github.com/nix-community/acpi_call > > I still didn't try this version (planning to do it tonight). > Is there any plan to use the fork of acpi_call in the future ? I'll switch to the fork or alike soon. Thanks for letting me know. -- Best regards, Andrzej Telszewski From lramos.prof at yahoo.com.br Sun Sep 19 12:18:53 2021 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Sun, 19 Sep 2021 09:18:53 -0300 Subject: [Slackbuilds-users] libupnp: missing LICENSE file References: Message-ID: Hello, just when updating my machine, I had a failing libupnp build here. It stopped when trying to copy the LICENSE file, which is not in the tar file from version 1.21.1. I managed to supress it from the "cp" command line where it appears, and it worked. Follow my patch for this issue. Hope this can help! Luiz Ramos S?o Paulo - Brazil -------------- next part -------------- >From fc59d99665c7fe646e14bee5a039a2b7a617ad53 Mon Sep 17 00:00:00 2001 From: Luiz Ramos Date: Sun, 19 Sep 2021 09:05:13 -0300 Subject: [PATCH] libraries/libupnp: fixed build The build broke as there was a missing LICENSE file. The "cp" command line was rewritten without that file. -- Luiz Ramos, 20/Sep/2021 --- libraries/libupnp/libupnp.SlackBuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libraries/libupnp/libupnp.SlackBuild b/libraries/libupnp/libupnp.SlackBuild index ceb79d737e6aec34c5b0fba689202640b2389e0d..3a6a93b763bc2307ae5952dd24a36c915e55b4e3 100644 --- a/libraries/libupnp/libupnp.SlackBuild +++ b/libraries/libupnp/libupnp.SlackBuild @@ -110,7 +110,7 @@ find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | gr | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION -cp -a LICENSE THANKS $PKG/usr/doc/$PRGNAM-$VERSION +cp -a THANKS $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild mkdir -p $PKG/install -- 2.32.0 From matteo.bernardini at gmail.com Sun Sep 19 13:06:45 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 19 Sep 2021 15:06:45 +0200 Subject: [Slackbuilds-users] libupnp: missing LICENSE file In-Reply-To: References: Message-ID: Hi Luiz, libupnp is at version 1.8.3 here (also in git master): maybe you got that issue because you updated to a newer version locally... Matteo Il giorno dom 19 set 2021 alle ore 14:18 Luiz Carlos Ramos via SlackBuilds-users ha scritto: > Hello, > > just when updating my machine, I had a failing libupnp build here. It > stopped when trying to copy the LICENSE file, which is not in the tar > file from version 1.21.1. > > I managed to supress it from the "cp" command line where it appears, and > it worked. > > Follow my patch for this issue. > > Hope this can help! > > Luiz Ramos > S?o Paulo - Brazil > > _______________________________________________ > 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 slackalaxy at gmail.com Sun Sep 19 15:06:06 2021 From: slackalaxy at gmail.com (Petar Petrov) Date: Sun, 19 Sep 2021 15:06:06 +0000 Subject: [Slackbuilds-users] anyone wants my SlackBuilds? Message-ID: dear All, I am not using Slackware anymore, so hereby I turn my SlackBuilds over to whoever wants to adopt them. If at some point I come back to Slackware, I may once again take the maintenance of some. Here's a post in my humble blog: https://slackalaxy.com/2021/09/19/until-we-meet-again-slackware/ thanks for everything! best, Petar From slackbuilds at schoepfer.info Sun Sep 19 18:09:55 2021 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 19 Sep 2021 20:09:55 +0200 Subject: [Slackbuilds-users] anyone wants my SlackBuilds? In-Reply-To: References: Message-ID: <0876e49a5e58008f20380bf4ddabad3c@schoepfer.info> > I am not using Slackware anymore, so hereby I turn my SlackBuilds over > to whoever wants to adopt them. I'll take "digger". Johannes From arnaud.garcia-fernandez at laposte.net Sun Sep 19 18:19:42 2021 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Sun, 19 Sep 2021 18:19:42 +0000 Subject: [Slackbuilds-users] anyone wants my SlackBuilds? In-Reply-To: <0876e49a5e58008f20380bf4ddabad3c@schoepfer.info> References: <0876e49a5e58008f20380bf4ddabad3c@schoepfer.info> Message-ID: I'd be okay to take all vcmi related SlackBuilds along with heroes3 demo data. - Yth /Arnaud. Le 19 septembre 2021 18:09:55 UTC, Franzen via SlackBuilds-users a ?crit?: >> I am not using Slackware anymore, so hereby I turn my SlackBuilds over >> to whoever wants to adopt them. > >I'll take "digger". > >Johannes >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - https://slackbuilds.org/faq/ > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From lramos.prof at yahoo.com.br Sun Sep 19 18:29:58 2021 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Sun, 19 Sep 2021 15:29:58 -0300 Subject: [Slackbuilds-users] libupnp: missing LICENSE file In-Reply-To: References: Message-ID: Hi, Matteo, that's true... I updated libupnp here to 1.12.1. My apologies, and thanks! Luiz On Sun, Sep 19, 2021 at 03:06:45PM +0200, Matteo Bernardini wrote: > Hi Luiz, > > libupnp is at version 1.8.3 here (also in git master): maybe you got that > issue because you updated to a newer version locally... > > Matteo > > Il giorno dom 19 set 2021 alle ore 14:18 Luiz Carlos Ramos via > SlackBuilds-users ha scritto: > > > Hello, > > > > just when updating my machine, I had a failing libupnp build here. It > > stopped when trying to copy the LICENSE file, which is not in the tar > > file from version 1.21.1. > > > > I managed to supress it from the "cp" command line where it appears, and > > it worked. > > > > Follow my patch for this issue. > > > > Hope this can help! > > > > Luiz Ramos > > S?o Paulo - Brazil > > > > _______________________________________________ > > 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 fellype at gmail.com Tue Sep 21 21:43:56 2021 From: fellype at gmail.com (Fellype) Date: Tue, 21 Sep 2021 18:43:56 -0300 Subject: [Slackbuilds-users] anyone wants my SlackBuilds? In-Reply-To: References: Message-ID: Hi Petar! I am not using Slackware anymore, so hereby I turn my SlackBuilds over > to whoever wants to adopt them. > I can take maintenance of libraries/muParser Here's a post in my humble blog: > https://slackalaxy.com/2021/09/19/until-we-meet-again-slackware/ > > thanks for everything! > > Good luck on your journey. Best wishes, Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: From damagedone at gmx.com Fri Sep 24 12:19:27 2021 From: damagedone at gmx.com (Eugene M.) Date: Fri, 24 Sep 2021 17:19:27 +0500 Subject: [Slackbuilds-users] sxiv -> nsxiv Message-ID: <31af5518-aed9-05dc-0895-7946c452eaf5@gmx.com> Hello everyone. As you might heard, sxiv(https://github.com/muennich/sxiv) has been marked as an archived project on Github by author. As a result, I can offer only one thing - remove it from the master branch. In exchange, I can add a fork, which is called nsxiv(https://github.com/nsxiv/nsxiv) in next couple of weeks. What do you think about that? From sb at rbn.im Fri Sep 24 15:01:06 2021 From: sb at rbn.im (Ruben Schuller) Date: Fri, 24 Sep 2021 17:01:06 +0200 Subject: [Slackbuilds-users] lua-lpeg Message-ID: <20210924170106.1c6d1927@kiwi.kuchen> Hi list! I had a mail exchange with Benjamin Trigona-Harany and he agreed that i might take over his lua-lpeg SlackBuild. I also modified the SlackBuild to build and install lua-lpeg for every available lua version (5.1, 5.2, 5.3). Please see the attached patches for this modification and the takeover (the takeover patch also contains modifications for the building with all luas, which is a bit ugly, i can redo these patches if you want :) Cheers Ruben -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-build-lpeg-for-all-luas.patch Type: text/x-patch Size: 1394 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-take-over-lua-lpeg.patch Type: text/x-patch Size: 2260 bytes Desc: not available URL: From yalhcru at gmail.com Sun Sep 26 17:11:05 2021 From: yalhcru at gmail.com (B Watson) Date: Sun, 26 Sep 2021 13:11:05 -0400 Subject: [Slackbuilds-users] sxiv -> nsxiv In-Reply-To: <31af5518-aed9-05dc-0895-7946c452eaf5@gmx.com> References: <31af5518-aed9-05dc-0895-7946c452eaf5@gmx.com> Message-ID: On 9/24/21, Eugene M. wrote: > Hello everyone. > > As you might heard, sxiv(https://github.com/muennich/sxiv) has been > marked as an archived project on Github by author. As a result, I can > offer only one thing - remove it from the master branch. Why would that be? It's a small & simple piece of software, it's got a useful set of features, and the current version of it seems to work just fine. The download tarball is still available, it compiles and runs fine... Just because it won't be receiving updates doesn't mean it's suddenly useless and nonfunctional. 10 years from now, it will still be functional. Perhaps there will be new image formats it doesn't support, but I'm willing to bet they don't displace jpeg and png. At worst, it'll need some minor patching to compile with whatever gcc version we use in 2031. That said... > In exchange, I can add a fork, which is called > nsxiv(https://github.com/nsxiv/nsxiv) in next couple of weeks. What do > you think about that? Sure, why not? All the above isn't meant to convince you not to do this, it's just meant to make you think about your "unmaintained upstream = REMOVE IMMEDIATELY" approach. From jdashiel at panix.com Sun Sep 26 17:29:36 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Sun, 26 Sep 2021 13:29:36 -0400 Subject: [Slackbuilds-users] sofastats questions Message-ID: First, I suspect sofastats will only have a G.U.I. interface and I hope not kde or fltk since those don't work with the orca screen reader. It would be nice if sofastats had a command line interface but I'm prepared to make sacrifices. Second, sofastats using the slackbuild cannot build due to missing dependencies. I tried installing with spi and when that failed I ran sqg -p sofastats then sbopkg -i sofastats and used the q file and the package would not build. Might this failure be due to the incoming transition to slackware 15.0 and necessary package changes? If so, I can wait on this for a while. From jdashiel at panix.com Sun Sep 26 17:34:18 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Sun, 26 Sep 2021 13:34:18 -0400 Subject: [Slackbuilds-users] foldingathome Message-ID: Would it be possible to get a foldingathome slackbuild script after slackware 15.0 gets released? Many other distros have the capability to build and contribute to this project but not so slackware yet at least with slackbuilds. We could set up a slackware team to help solve covid and other diseases once a package like that became available. There might be a problem since slackware doesn't use systemd and so far as I know no such change is planned for the future. Foldingathome uses systemd to run but if there are ways around this this might be possible. From yalhcru at gmail.com Sun Sep 26 21:11:54 2021 From: yalhcru at gmail.com (B Watson) Date: Sun, 26 Sep 2021 17:11:54 -0400 Subject: [Slackbuilds-users] foldingathome In-Reply-To: References: Message-ID: On 9/26/21, Jude DaShiell wrote: > Would it be possible to get a foldingathome slackbuild script after > slackware 15.0 gets released? Many other distros have the capability to > build and contribute to this project but not so slackware yet at least > with slackbuilds. If you write a SlackBuild for it, we'll have one. Right now, submissions are still closed, until 15.0 releases... but if you have a tested/working script, you can submit it as soon as we reopen submissions. > There might be a problem since slackware doesn't use systemd and so far as > I know no such change is planned for the future. Foldingathome uses > systemd to run but if there are ways around this this might be possible. Does it just use systemd to start a daemon at boot? Would be simple enough to include an rc.whatever script with your SlackBuild, or just a set of instructions on how to start it from rc.local. From kingbeowulf at gmail.com Mon Sep 27 02:48:23 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 26 Sep 2021 19:48:23 -0700 Subject: [Slackbuilds-users] foldingathome In-Reply-To: References: Message-ID: On 9/26/21 10:34, Jude DaShiell wrote: > Would it be possible to get a foldingathome slackbuild script after > slackware 15.0 gets released? Many other distros have the capability to > build and contribute to this project but not so slackware yet at least > with slackbuilds. > We could set up a slackware team to help solve covid and other diseases > once a package like that became available. > There might be a problem since slackware doesn't use systemd and so far as > I know no such change is planned for the future. Foldingathome uses > systemd to run but if there are ways around this this might be possible. > It all depends on how folding at home is compiled re: systemd. I am also not sure if it's opensource: they only have pre-compiled binaries. Alternatively consider BOINC: it is available on SBo, is open source, is built from source, and hosts a number of projects for medicine, for example: rosetta at home GPUGrid World Community Grid I don't know why folding at home (originally at Stanford University) did not leverage the already existing BOINC at UC Berkeley. The nice thing about BOINC is that you are not limited to one science project. when 15.0 hits, I'll hope to get off my duff and do that rc.boinc init script for running headless, instead of running mostly with Boinc Manager GUI. -kb -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From ozan.turkyilmaz at gmail.com Mon Sep 27 06:53:11 2021 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Mon, 27 Sep 2021 09:53:11 +0300 Subject: [Slackbuilds-users] foldingathome In-Reply-To: References: Message-ID: King Beowulf , 27 Eyl 2021 Pzt, 05:48 tarihinde ?unu yazd?: > On 9/26/21 10:34, Jude DaShiell wrote: > > Would it be possible to get a foldingathome slackbuild script after > > slackware 15.0 gets released? Many other distros have the capability to > > build and contribute to this project but not so slackware yet at least > > with slackbuilds. > > We could set up a slackware team to help solve covid and other diseases > > once a package like that became available. > > There might be a problem since slackware doesn't use systemd and so far > as > > I know no such change is planned for the future. Foldingathome uses > > systemd to run but if there are ways around this this might be possible. > > > > It all depends on how folding at home is compiled re: systemd. I am also > not sure if it's opensource: they only have pre-compiled binaries. > > I just tested folding at home. It uses old system v style startup scripts and does not depend on systemd. Also, it seems it needs its own system user. I didnt tested or read the documentation but it started fine and downloaded workload, then started working on it. Official packages come in rpm, dep for x86_64 and Arm/RaspberryPi. Regards, Ozan -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvbernts at online.no Mon Sep 27 10:48:43 2021 From: jvbernts at online.no (Jostein Berntsen) Date: Mon, 27 Sep 2021 12:48:43 +0200 Subject: [Slackbuilds-users] foldingathome In-Reply-To: References: Message-ID: On 26.09.21,13:34, Jude DaShiell wrote: > Would it be possible to get a foldingathome slackbuild script after > slackware 15.0 gets released? Many other distros have the capability to > build and contribute to this project but not so slackware yet at least > with slackbuilds. > We could set up a slackware team to help solve covid and other diseases > once a package like that became available. > There might be a problem since slackware doesn't use systemd and so far as > I know no such change is planned for the future. Foldingathome uses > systemd to run but if there are ways around this this might be possible. > There are some instructions for how to set up foldingathome on Slakckware here: "how i setup folding at home as a background process" "https://www.linuxquestions.org/questions/slackware-14/how-i-setup-folding%40home-as-a-background-process-685323/" JB From jdashiel at panix.com Mon Sep 27 11:37:02 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Mon, 27 Sep 2021 07:37:02 -0400 Subject: [Slackbuilds-users] foldingathome In-Reply-To: References: Message-ID: Thanks for these instructions. On Mon, 27 Sep 2021, Jostein Berntsen wrote: > On 26.09.21,13:34, Jude DaShiell wrote: > > Would it be possible to get a foldingathome slackbuild script after > > slackware 15.0 gets released? Many other distros have the capability to > > build and contribute to this project but not so slackware yet at least > > with slackbuilds. > > We could set up a slackware team to help solve covid and other diseases > > once a package like that became available. > > There might be a problem since slackware doesn't use systemd and so far as > > I know no such change is planned for the future. Foldingathome uses > > systemd to run but if there are ways around this this might be possible. > > > > There are some instructions for how to set up foldingathome on > Slakckware here: > > "how i setup folding at home as a background process" > "https://www.linuxquestions.org/questions/slackware-14/how-i-setup-folding%40home-as-a-background-process-685323/" > > > JB > _______________________________________________ > 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 414N at slacky.it Mon Sep 27 21:45:15 2021 From: 414N at slacky.it (414N) Date: Mon, 27 Sep 2021 23:45:15 +0200 Subject: [Slackbuilds-users] sofastats questions In-Reply-To: References: Message-ID: <0be99c51-731d-c214-cd50-c90bc85b6ae7@slacky.it> Hello Jude, on what Slackware version are you trying to build it? On 14.2 it seems to still build fine. Could you please tell me what error(s) are you encountering? Alan Alberghini SBo clone: GitHub On 26/09/21 19:29, Jude DaShiell wrote: > First, I suspect sofastats will only have a G.U.I. interface and I hope > not kde or fltk since those don't work with the orca screen reader. It > would be nice if sofastats had a command line interface but I'm prepared > to make sacrifices. > Second, sofastats using the slackbuild cannot build due to missing > dependencies. I tried installing with spi and when that failed I ran sqg > -p sofastats then sbopkg -i sofastats and used the q file and the package > would not build. Might this failure be due to the incoming transition to > slackware 15.0 and necessary package changes? If so, I can wait on this > for a while. > > _______________________________________________ > 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 -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From jdashiel at panix.com Mon Sep 27 22:07:42 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Mon, 27 Sep 2021 18:07:42 -0400 Subject: [Slackbuilds-users] sofastats questions In-Reply-To: <0be99c51-731d-c214-cd50-c90bc85b6ae7@slacky.it> References: <0be99c51-731d-c214-cd50-c90bc85b6ae7@slacky.it> Message-ID: This is slackware version 14.2 specifically slint the international version of slackware. I get the following high level errors when using spi -i sofastats this happens with sbopkg on lower levels too even when each of the missing packages is run with sqg -p packagename first and then sbopkg -i packagename. The spi errors are: No such package or SlackBuild: matplotlib pywebkitgtk wkhtmltopdf python-requests pyPdf On Mon, 27 Sep 2021, 414N wrote: > Hello Jude, > > on what Slackware version are you trying to build it? > On 14.2 it seems to still build fine. > Could you please tell me what error(s) are you encountering? > > Alan Alberghini > > SBo clone: GitHub > > On 26/09/21 19:29, Jude DaShiell wrote: > > First, I suspect sofastats will only have a G.U.I. interface and I hope > > not kde or fltk since those don't work with the orca screen reader. It > > would be nice if sofastats had a command line interface but I'm prepared > > to make sacrifices. > > Second, sofastats using the slackbuild cannot build due to missing > > dependencies. I tried installing with spi and when that failed I ran sqg > > -p sofastats then sbopkg -i sofastats and used the q file and the package > > would not build. Might this failure be due to the incoming transition to > > slackware 15.0 and necessary package changes? If so, I can wait on this > > for a while. > > > > _______________________________________________ > > 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 rshepard at appl-ecosys.com Mon Sep 27 22:17:38 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 27 Sep 2021 15:17:38 -0700 (PDT) Subject: [Slackbuilds-users] sofastats questions In-Reply-To: References: <0be99c51-731d-c214-cd50-c90bc85b6ae7@slacky.it> Message-ID: <2532b3a-462-ec2-c952-90577cdbc17@appl-ecosys.com> On Mon, 27 Sep 2021, Jude DaShiell wrote: > This is slackware version 14.2 specifically slint the international > version of slackware. I get the following high level errors when using > spi -i sofastats this happens with sbopkg on lower levels too even when > each of the missing packages is run with sqg -p packagename first and then > sbopkg -i packagename. > The spi errors are: > No such package or SlackBuild: matplotlib pywebkitgtk wkhtmltopdf > python-requests pyPdf Jude, Have you considered R for statistical analyses and data modeling? Rich From jdashiel at panix.com Mon Sep 27 23:07:25 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Mon, 27 Sep 2021 19:07:25 -0400 Subject: [Slackbuilds-users] sofastats questions In-Reply-To: <2532b3a-462-ec2-c952-90577cdbc17@appl-ecosys.com> References: <0be99c51-731d-c214-cd50-c90bc85b6ae7@slacky.it> <2532b3a-462-ec2-c952-90577cdbc17@appl-ecosys.com> Message-ID: I haven't done a thing with R. On Mon, 27 Sep 2021, Rich Shepard wrote: > On Mon, 27 Sep 2021, Jude DaShiell wrote: > > > This is slackware version 14.2 specifically slint the international > > version of slackware. I get the following high level errors when using > > spi -i sofastats this happens with sbopkg on lower levels too even when > > each of the missing packages is run with sqg -p packagename first and then > > sbopkg -i packagename. > > The spi errors are: > > No such package or SlackBuild: matplotlib pywebkitgtk wkhtmltopdf > > python-requests pyPdf > > Jude, > > Have you considered R for statistical analyses > and data modeling? > > 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/ > > > From ld.jay at protonmail.com Sun Sep 19 00:22:06 2021 From: ld.jay at protonmail.com (ld.jay) Date: Sun, 19 Sep 2021 00:22:06 -0000 Subject: [Slackbuilds-users] Building nvidia-legacy304-kernel fails on 4.4 series kernels above release 167 Message-ID: <52SVYeRg_tTuFZZAdQMOE4kWQ-OHIlM5s3KJegedshlYD6GLfORBXAeUuT4SCywolFsMHU5Muc-lFN2UqQimxScACatEoRnmJpek52Q9VHM=@protonmail.com> The following small hack added to the SlackBuild at line 79 (right after "cd kernel || exit 1") fixes the problem: # Jay's hack to make the module compile on 4.4.y (for y > 167 ) KVER_MAJOR=$( echo $KERNEL | cut -f 1 -d . ) KVER_MINOR=$( echo $KERNEL | cut -f 2 -d . ) KVER_RELEASE=$( echo $KERNEL | cut -f 3 -d . | cut -f 1 -d - ) if [ $KVER_MAJOR -eq 4 ] ; then if [ $KVER_MINOR -eq 4 ] ; then if [ $KVER_RELEASE -gt 167 ] ; then sed -i "1927s/force,//" nv-linux.h fi fi fi ######################## Since this SlackBuild is unmaintained, and I have no plans to "upgrade" my current nVidia card, I would be willing to take over maintaining this one. Legacy304 is the "newest" driver that works with my FX3500, and when 15 becomes official, I'll continue to use it, assuming that I can get it to compile on 5.x.x kernels. Also, since I first drafted this message, I've been working on updating this SlackBuild to work on -current. This update is almost ready for prime time. I started a thread about it on LQ if anyone is interested. Thanks, Jay -------------- next part -------------- An HTML attachment was scrubbed... URL: From nerdmans at xs4all.nl Fri Sep 24 13:03:43 2021 From: nerdmans at xs4all.nl (Frans-Pieter Vonck) Date: Fri, 24 Sep 2021 13:03:43 -0000 Subject: [Slackbuilds-users] sxiv -> nsxiv In-Reply-To: <31af5518-aed9-05dc-0895-7946c452eaf5@gmx.com> References: <31af5518-aed9-05dc-0895-7946c452eaf5@gmx.com> Message-ID: <983457281.1139040.1632488614601@ox-webmail.xs4all.nl> Great to have suckless on slackware. Grts, Oberoid. > Op 24-09-2021 14:19 schreef Eugene M. : > > > Hello everyone. > > As you might heard, sxiv(https://github.com/muennich/sxiv) has been > marked as an archived project on Github by author. As a result, I can > offer only one thing - remove it from the master branch. > In exchange, I can add a fork, which is called > nsxiv(https://github.com/nsxiv/nsxiv) in next couple of weeks. What do > you think about that? > _______________________________________________ > 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/