From rshepard at appl-ecosys.com Fri Oct 1 15:14:25 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 1 Oct 2021 08:14:25 -0700 (PDT) Subject: [Slackbuilds-users] Issue building qgis Message-ID: Installed here is qt5-webkit-5.212.0_alpha4-x86_64-3_SBo. Building qgis fails with a qt5-webkit version error: CMake Error at CMakeLists.txt:453 (find_package): Found package configuration file: /usr/lib64/cmake/Qt5WebKit/Qt5WebKitConfig.cmake but it set Qt5WebKit_FOUND to FALSE so package "Qt5WebKit" is considered to be NOT FOUND. Reason given by package: Qt5WebKit could not be found because dependency is required to have exact version 5.12.x. Please advise me how to resolve this issue. TIA, Rich From kingbeowulf at gmail.com Sat Oct 2 20:18:10 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 2 Oct 2021 13:18:10 -0700 Subject: [Slackbuilds-users] Issue building qgis In-Reply-To: References: Message-ID: <31a6f08b-c191-d2df-74b3-8362c76d2beb@gmail.com> On 10/1/21 08:14, Rich Shepard wrote: > Installed here is qt5-webkit-5.212.0_alpha4-x86_64-3_SBo. > > Building qgis fails with a qt5-webkit version error: > CMake Error at CMakeLists.txt:453 (find_package): > ? Found package configuration file: > > ??? /usr/lib64/cmake/Qt5WebKit/Qt5WebKitConfig.cmake > > ? but it set Qt5WebKit_FOUND to FALSE so package "Qt5WebKit" is > considered to > ? be NOT FOUND.? Reason given by package: > > ? Qt5WebKit could not be found because dependency is required to have exact > ? version 5.12.x. > > Please advise me how to resolve this issue. > > Rich, On 14.2, make sure you know which gt5 you have installed (and make sure to compile with qtwebengine support). also, if you upgraded qt5, you need to recompile qt5-webkit. You may also need to have libwebp installed before compiling qt5. on the SBo, qgis page, there is also a warning to be sure to compile some dependencies in the correct order. On Slackware Current, qgis may be a bit easier. https://github.com/Ponce/slackbuilds/tree/current/gis/qgis -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Sat Oct 2 20:27:58 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 2 Oct 2021 13:27:58 -0700 (PDT) Subject: [Slackbuilds-users] Issue building qgis In-Reply-To: <31a6f08b-c191-d2df-74b3-8362c76d2beb@gmail.com> References: <31a6f08b-c191-d2df-74b3-8362c76d2beb@gmail.com> Message-ID: <3ab6695-618-5365-fdca-fe1484ff6176@appl-ecosys.com> On Sat, 2 Oct 2021, King Beowulf wrote: > On 14.2, make sure you know which gt5 you have installed (and make sure to > compile with qtwebengine support). also, if you upgraded qt5, you need to > recompile qt5-webkit. You may also need to have libwebp installed before > compiling qt5. Ed, Ah, I have the latest qt5, but probably installed it without the web engine. I guess I'll recompile qt5 and the webkit. Sigh. Takes hours even on my comparatively fast host with 32G RAM. > on the SBo, qgis page, there is also a warning to be sure to compile > some dependencies in the correct order. > On Slackware Current, qgis may be a bit easier. > https://github.com/Ponce/slackbuilds/tree/current/gis/qgis I need to get this project to a client before spending a day or so wiring the new host and installing -current on it, then copying over /home, /opt, and /data. Thanks, Rich From mr.chew.baka at gmail.com Mon Oct 4 01:45:30 2021 From: mr.chew.baka at gmail.com (Mr. B-o-B) Date: Sun, 3 Oct 2021 20:45:30 -0500 Subject: [Slackbuilds-users] unixODBC - up for grabs Message-ID: <21369617-9d33-1e16-1556-8d051347f445@gmail.com> Hello all and well met.? I have been the maintainer for the unixODBC package for many years.? I left the job I used this package at back in May 2019, and I feel it is time to pass the torch for the maintenance on this one.? This package was required for a DB we used call Actian (formerly Pervasive, formerly Btrieve) SQL, and I pray to the gods that I never have to work on or with the software that was used on this DB.? So long story short I no longer have a use for this package anymore, and would like to offer it up for someone else to maintain. Thank You! Bob From fernando.lopezjr at gmail.com Mon Oct 4 21:10:57 2021 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 4 Oct 2021 15:10:57 -0600 Subject: [Slackbuilds-users] unixODBC - up for grabs In-Reply-To: <21369617-9d33-1e16-1556-8d051347f445@gmail.com> References: <21369617-9d33-1e16-1556-8d051347f445@gmail.com> Message-ID: ill take it. thank you. On Sun, Oct 3, 2021 at 7:45 PM Mr. B-o-B wrote: > Hello all and well met. I have been the maintainer for the unixODBC > package for many years. I left the job I used this package at back in > May 2019, and I feel it is time to pass the torch for the maintenance on > this one. This package was required for a DB we used call Actian > (formerly Pervasive, formerly Btrieve) SQL, and I pray to the gods that > I never have to work on or with the software that was used on this DB. > So long story short I no longer have a use for this package anymore, and > would like to offer it up for someone else to maintain. > > > Thank You! > > > Bob > > _______________________________________________ > 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 willysr at slackbuilds.org Thu Oct 7 05:29:32 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 7 Oct 2021 12:29:32 +0700 Subject: [Slackbuilds-users] unixODBC - up for grabs In-Reply-To: References: <21369617-9d33-1e16-1556-8d051347f445@gmail.com> Message-ID: <10bca752-a77a-96a1-9569-d747bde53398@slackbuilds.org> > ill take it. thank you. Hi Fernando please make sure to handle the conflict that unixODBC have with core package in Slackware as mentioned in README -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From ml at mareichelt.com Thu Oct 7 19:34:09 2021 From: ml at mareichelt.com (Markus Reichelt) Date: Thu, 7 Oct 2021 21:34:09 +0200 Subject: [Slackbuilds-users] python-cryptography up for grabs Message-ID: Yo. python-cryptography is up for grabs. https://slackbuilds.org/repository/14.2/python/cryptography/ -- From ml at mareichelt.com Thu Oct 7 19:49:28 2021 From: ml at mareichelt.com (Markus Reichelt) Date: Thu, 7 Oct 2021 21:49:28 +0200 Subject: [Slackbuilds-users] notice of change of maintainership Message-ID: Yo. Many moons ago already maintainership was passed along for the following scripts: (CC: because of reasons :-) buildbot-worker / -slave, python-twisted, attrs, Automat, constantly, hyperlink, incremental for the transitional period, this is done exactly how? :-) just switch me for 'yth at ythogtha.org' in the sea of scripts, that'd work for me. All the best. --jg71 -- From arnaud.garcia-fernandez at laposte.net Thu Oct 7 19:56:27 2021 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Thu, 7 Oct 2021 21:56:27 +0200 Subject: [Slackbuilds-users] notice of change of maintainership In-Reply-To: References: Message-ID: <20211007215627.98cc37f82d7e5e83b815ea01@laposte.net> On Thu, 7 Oct 2021 21:49:28 +0200 Markus Reichelt wrote: > Yo. Many moons ago already maintainership was passed along for the > following scripts: (CC: because of reasons :-) > > buildbot-worker / -slave, python-twisted, attrs, Automat, constantly, hyperlink, incremental > > for the transitional period, this is done exactly how? :-) > > just switch me for 'yth at ythogtha.org' in the sea of scripts, that'd > work for me. > > All the best. --jg71 > > > -- Hi Markus ! yes, I'll work on it again, maybe not waiting for 15.0 anymore, since we don't really know when it'll be there. I'll update my draft-PR and submit it ! - Yth / Arnaud From willysr at slackbuilds.org Sat Oct 9 09:19:27 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 Oct 2021 16:19:27 +0700 Subject: [Slackbuilds-users] python-cryptography up for grabs In-Reply-To: References: Message-ID: <9f65c3c1-bc5d-0ebc-1b93-74acbf1165b0@slackbuilds.org> > Yo. python-cryptography is up for grabs. > > https://slackbuilds.org/repository/14.2/python/cryptography/ I'll take it then -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From dchmelik at gmail.com Mon Oct 11 04:06:51 2021 From: dchmelik at gmail.com (David Chmelik) Date: Sun, 10 Oct 2021 21:06:51 -0700 Subject: [Slackbuilds-users] [Slackware64-current] zfs-on-linux build broken Message-ID: <7097fbc2-319c-4e13-b923-25e73f423188@gmail.com> People were able to get zfs-on-linux (now actually openzfs) working on Slackware64-current by just changing the SlackBuild version number.? People should be using 2.1.1 now and in SBo-git it should be updated to reflect that.? However with the recent Slackware64-current python3 upgrade, zfs-on-linux will no longer build.? Its configure script is broken and detects python 3.10.0 as 3.1 and says it's too old, so won't continue.? What can be done about this meantime so people can continue to use zfs-on-linux with newer kernels on Slackware64-current before Slackware 15? From arnaud.garcia-fernandez at laposte.net Mon Oct 11 05:12:55 2021 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Mon, 11 Oct 2021 05:12:55 +0000 Subject: [Slackbuilds-users] [Slackware64-current] zfs-on-linux build broken In-Reply-To: <7097fbc2-319c-4e13-b923-25e73f423188@gmail.com> References: <7097fbc2-319c-4e13-b923-25e73f423188@gmail.com> Message-ID: Apparently, installing latest update of Slackware-current should fix that problem. Changelog says you need tu run autoreconf -vif for exactly that problem, with automake-1.16.5 - Yth. Le 11 octobre 2021 04:06:51 UTC, David Chmelik a ?crit?: >People were able to get zfs-on-linux (now actually openzfs) working on >Slackware64-current by just changing the SlackBuild version number.? >People should be using 2.1.1 now and in SBo-git it should be updated to >reflect that.? However with the recent Slackware64-current python3 >upgrade, zfs-on-linux will no longer build.? Its configure script is >broken and detects python 3.10.0 as 3.1 and says it's too old, so won't >continue.? What can be done about this meantime so people can continue >to use zfs-on-linux with newer kernels on Slackware64-current before >Slackware 15? >_______________________________________________ >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 ml at mareichelt.com Mon Oct 11 08:35:14 2021 From: ml at mareichelt.com (Markus Reichelt) Date: Mon, 11 Oct 2021 10:35:14 +0200 Subject: [Slackbuilds-users] [Slackware64-current] zfs-on-linux build broken In-Reply-To: <7097fbc2-319c-4e13-b923-25e73f423188@gmail.com> References: <7097fbc2-319c-4e13-b923-25e73f423188@gmail.com> Message-ID: * David Chmelik wrote: > People were able to get zfs-on-linux (now actually openzfs) working > on Slackware64-current by just changing the SlackBuild version > number.? People should be using 2.1.1 now and in SBo-git it should > be updated to reflect people should be careful jumping on the 'most recent version is best version' bandwaggon. there also is a 2.0.x branch maintained > that.? However with the recent Slackware64-current python3 upgrade, > zfs-on-linux will no longer build.? Its configure script is broken > and detects python 3.10.0 as 3.1 and says it's too old, so won't > continue.? What can be done about this meantime so people can > continue to use zfs-on-linux with newer kernels on > Slackware64-current before Slackware 15? reading the official changelog Sun Oct 10 00:11:13 UTC 2021 helps, there is a hint in there From fernando.lopezjr at gmail.com Mon Oct 11 13:24:25 2021 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 11 Oct 2021 07:24:25 -0600 Subject: [Slackbuilds-users] unixODBC - up for grabs In-Reply-To: <10bca752-a77a-96a1-9569-d747bde53398@slackbuilds.org> References: <21369617-9d33-1e16-1556-8d051347f445@gmail.com> <10bca752-a77a-96a1-9569-d747bde53398@slackbuilds.org> Message-ID: sure, i'll try to fix it... can you update the maintainer on it since i can't submit. thank you. On Wed, Oct 6, 2021 at 11:29 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > ill take it. thank you. > > Hi Fernando > > please make sure to handle the conflict that unixODBC have with core > package in Slackware as mentioned in README > > > > -- > Willy Sudiarto Raharjo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Wed Oct 13 17:24:50 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 13 Oct 2021 10:24:50 -0700 (PDT) Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? Message-ID: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> My LaTeX/LyX documents throw a Biber/biblatex error when compiling with pdflatex. The issue is having bibliographic database entry labels with apostrophes, such as O'Conner. This was fixed in Biber 2.2 but the 14.2 version is 2.14. (Apostrophes in other value fields are okay as they're enclosed in curley braces {}, but the cite key/label isn't.) The latest biblatex and Biber (3.16, 2020-12-31) is included in TeXLive2021. Could I build the -current TexLive2021 in 14.2? Or should I upgrade biblatex/Biber to 3.16? Rich From didier at slint.fr Wed Oct 13 17:33:28 2021 From: didier at slint.fr (Didier Spaier) Date: Wed, 13 Oct 2021 19:33:28 +0200 Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? In-Reply-To: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> References: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> Message-ID: Not an answer to your question but you could try this package: https://slackware.uk/slint/x86_64/slint-14.2.1/slint/texlive-2021.210418-x86_64-1slint.txz md5sum: https://slackware.uk/slint/x86_64/slint-14.2.1/slint/texlive-2021.210418-x86_64-1slint.md5 Caveat: I didn't build texlive-doc and texlive-extra at the same version Didier Le 13/10/2021 ? 19:24, Rich Shepard a ?crit?: > My LaTeX/LyX documents throw a Biber/biblatex error when compiling with > pdflatex. The issue is having bibliographic database entry labels with > apostrophes, such as O'Conner. This was fixed in Biber 2.2 but the 14.2 > version is 2.14. (Apostrophes in other value fields are okay as they're > enclosed in curley braces {}, but the cite key/label isn't.) > > The latest biblatex and Biber (3.16, 2020-12-31) is included in > TeXLive2021. > > Could I build the -current TexLive2021 in 14.2? Or should I upgrade > biblatex/Biber to 3.16? > > Rich From rshepard at appl-ecosys.com Wed Oct 13 17:51:50 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 13 Oct 2021 10:51:50 -0700 (PDT) Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? In-Reply-To: References: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> Message-ID: On Wed, 13 Oct 2021, Didier Spaier wrote: > Caveat: I didn't build texlive-doc and texlive-extra at the same version Didier, Does that make a difference? I'm getting all sorts of errors when building documents for a client so I need to fix them by upgrading ASAP. Thanks, Rich From matteo.bernardini at gmail.com Wed Oct 13 17:57:58 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 13 Oct 2021 19:57:58 +0200 Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? In-Reply-To: References: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> Message-ID: Hi Rich, if you need mission-critical stuff IMHO should be better to consider some sort of paid support (but I have no idea from whom). IMHO you shouldn't count on volunteers that try to help people in their spare time and that could have other (maybe also paid too) priorities. Matteo Il giorno mer 13 ott 2021 alle ore 19:51 Rich Shepard < rshepard at appl-ecosys.com> ha scritto: > On Wed, 13 Oct 2021, Didier Spaier wrote: > > > Caveat: I didn't build texlive-doc and texlive-extra at the same version > > Didier, > > Does that make a difference? > > I'm getting all sorts of errors when building documents for a client so I > need to fix them by upgrading ASAP. > > Thanks, > > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Wed Oct 13 18:07:24 2021 From: didier at slint.fr (Didier Spaier) Date: Wed, 13 Oct 2021 20:07:24 +0200 Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? In-Reply-To: References: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> Message-ID: <34acf7ff-3788-d7e8-d5b3-bf97428a16c8@slint.fr> Le 13/10/2021 ? 19:51, Rich Shepard a ?crit?: > Does that make a difference? It all dpends if you need the additional features provided by texlive-extra. Only you know. From rshepard at appl-ecosys.com Wed Oct 13 18:16:52 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 13 Oct 2021 11:16:52 -0700 (PDT) Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? In-Reply-To: <34acf7ff-3788-d7e8-d5b3-bf97428a16c8@slint.fr> References: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> <34acf7ff-3788-d7e8-d5b3-bf97428a16c8@slint.fr> Message-ID: <353bbdb7-80c7-8358-ee2d-e0e4c43b0c@appl-ecosys.com> On Wed, 13 Oct 2021, Didier Spaier wrote: > It all dpends if you need the additional features provided by > texlive-extra. Only you know. I'll see. :-) Thanks, Rich From sb at rbn.im Wed Oct 13 19:21:25 2021 From: sb at rbn.im (Ruben Schuller) Date: Wed, 13 Oct 2021 21:21:25 +0200 Subject: [Slackbuilds-users] git access Message-ID: <20211013212125.17e92ac4@kiwi.kuchen> Hi list! I'm pretty sure it was already discussed here or I missed some documentation, but what is the process to get git access to SBo? It just would be easier to push updates to my SlackBuilds somewhere instead of uploading a tarball, as i have them already stored in a git repository. Cheers Ruben From duncan_roe at optusnet.com.au Thu Oct 14 00:46:09 2021 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Thu, 14 Oct 2021 11:46:09 +1100 Subject: [Slackbuilds-users] git access In-Reply-To: <20211013212125.17e92ac4@kiwi.kuchen> References: <20211013212125.17e92ac4@kiwi.kuchen> Message-ID: On Wed, Oct 13, 2021 at 09:21:25PM +0200, Ruben Schuller wrote: > Hi list! > > I'm pretty sure it was already discussed here or I missed some > documentation, but what is the process to get git access to SBo? > It just would be easier to push updates to my SlackBuilds somewhere > instead of uploading a tarball, as i have them already stored in a git > repository. > > Cheers > Ruben git clone git://git.slackbuilds.org/slackbuilds.git Cheers ... Duncan. From kingbeowulf at gmail.com Thu Oct 14 01:22:07 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 13 Oct 2021 18:22:07 -0700 Subject: [Slackbuilds-users] git access In-Reply-To: <20211013212125.17e92ac4@kiwi.kuchen> References: <20211013212125.17e92ac4@kiwi.kuchen> Message-ID: On 10/13/21 12:21, Ruben Schuller wrote: > Hi list! > > I'm pretty sure it was already discussed here or I missed some > documentation, but what is the process to get git access to SBo? > It just would be easier to push updates to my SlackBuilds somewhere > instead of uploading a tarball, as i have them already stored in a git > repository. > > Cheers > Ruben The SBo admins can set that up if you are *worthy* haha. It a bit more than just "git clone"... you can email Willy or Robby for the procedure and permissions. If they agree, they'll set up the git server, ask for your gpg key etc, then you'll config your git, pull/fetch/push via a local branch. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Oct 14 02:41:56 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 14 Oct 2021 09:41:56 +0700 Subject: [Slackbuilds-users] unixODBC - up for grabs In-Reply-To: References: <21369617-9d33-1e16-1556-8d051347f445@gmail.com> <10bca752-a77a-96a1-9569-d747bde53398@slackbuilds.org> Message-ID: <930ac687-09b3-69d3-644c-80d83a962997@slackbuilds.org> > sure, i'll try to fix it... can you update the maintainer on it since i > can't submit. thank you. Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From slackbuilds at jaxartes.net Thu Oct 14 03:06:54 2021 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Thu, 14 Oct 2021 03:06:54 +0000 (UTC) Subject: [Slackbuilds-users] Slackbuilds Message-ID: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> I am no longer going to be maintaining my Slackbuilds. Please feel free to claim them. Best, Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Thu Oct 14 03:47:56 2021 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Wed, 13 Oct 2021 21:47:56 -0600 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> Message-ID: sad to see you go. :| On Wed, Oct 13, 2021 at 9:07 PM Benjamin Trigona-Harany < slackbuilds at jaxartes.net> wrote: > I am no longer going to be maintaining my Slackbuilds. Please feel free to > claim them. > > Best, Ben > _______________________________________________ > 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 Thu Oct 14 04:47:38 2021 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 13 Oct 2021 22:47:38 -0600 Subject: [Slackbuilds-users] git access In-Reply-To: References: <20211013212125.17e92ac4@kiwi.kuchen> Message-ID: On Wed, Oct 13, 2021, 6:47 PM Duncan Roe wrote: > On Wed, Oct 13, 2021 at 09:21:25PM +0200, Ruben Schuller wrote: > > Hi list! > > > > I'm pretty sure it was already discussed here or I missed some > > documentation, but what is the process to get git access to SBo? > > It just would be easier to push updates to my SlackBuilds somewhere > > instead of uploading a tarball, as i have them already stored in a git > > repository. > > > > Cheers > > Ruben > > git clone git://git.slackbuilds.org/slackbuilds.git > > Cheers ... Duncan. > _______________________________________________ > 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/ You can also use the SBo mirrors on GitHub and GitLab to submit pull/merge requests. https://github.com/SlackBuildsOrg/slackbuilds https://gitlab.com/SlackBuilds.org/slackbuilds That is generally how I submit my updates. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From sb at rbn.im Thu Oct 14 08:21:06 2021 From: sb at rbn.im (Ruben Schuller) Date: Thu, 14 Oct 2021 10:21:06 +0200 Subject: [Slackbuilds-users] git access In-Reply-To: References: <20211013212125.17e92ac4@kiwi.kuchen> Message-ID: <20211014102106.1a1af715@kiwi.kuchen> Hi! 2021-10-13 Jeremy Hansen : > You can also use the SBo mirrors on GitHub and GitLab to submit > pull/merge requests. > > https://github.com/SlackBuildsOrg/slackbuilds > https://gitlab.com/SlackBuilds.org/slackbuilds That's exactly what I need, thanks! Ruben From artourter at gmail.com Thu Oct 14 12:22:13 2021 From: artourter at gmail.com (Greg' Ar Tourter) Date: Thu, 14 Oct 2021 13:22:13 +0100 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> Message-ID: Thanks for all your work Ben. Sorry to see you go. Unless someone else want them, I am happy to take over - keepassxc - proj - proj-data - geos - cartopy Cheers Greg On Thu, 14 Oct 2021 at 04:07, Benjamin Trigona-Harany < slackbuilds at jaxartes.net> wrote: > I am no longer going to be maintaining my Slackbuilds. Please feel free to > claim them. > > Best, Ben > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arnaud.garcia-fernandez at laposte.net Thu Oct 14 12:33:54 2021 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Thu, 14 Oct 2021 14:33:54 +0200 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> Message-ID: <20211014143354.3b8ca78d36886ef160616c45@laposte.net> > I am no longer going to be maintaining my Slackbuilds. Please feel free to > claim them. > > Best, Ben Well, that's a shame, you were doing a great work. Best of luck in the future, and thanks for all the time spent ! I could take over those slackbuilds : development/psycopg2 libraries/Jinja2 python/Pygments python/bleach python/decorator python/parso python/mistune python/click-plugins python/pyzmq python/python3-pyzmq python/python3-wcwidth python/python3-dateutil python/python3-babel python/python3-prompt_toolkit python/python3-webencodings Mostly requirements of stuff I already do. Yth - Arnaud From erich.public at protonmail.com Thu Oct 14 13:37:59 2021 From: erich.public at protonmail.com (Erich Ritz) Date: Thu, 14 Oct 2021 13:37:59 +0000 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> Message-ID: I'll take system/bat system/dust I use these and maintain other rust programs, so I already know how to handle the countless static dependencies. Erich ??????? Original Message ??????? On Wednesday, October 13th, 2021 at 10:06 PM, Benjamin Trigona-Harany wrote: > I am no longer going to be maintaining my Slackbuilds. Please feel free to claim them. > > Best, Ben From johannes at schoepfer.info Thu Oct 14 13:55:39 2021 From: johannes at schoepfer.info (johannes at schoepfer.info) Date: Thu, 14 Oct 2021 15:55:39 +0200 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> Message-ID: <39e518e93dff4c8f4df4bb1f0340146f@schoepfer.info> On 2021-10-14 05:06, Benjamin Trigona-Harany wrote: > I am no longer going to be maintaining my Slackbuilds. Please feel > free to claim them. I'd take: xplanet xawtv Could some Admin please put me in as maintainer, also for digger Thanks, Johannes From artourter at gmail.com Thu Oct 14 14:29:56 2021 From: artourter at gmail.com (Greg' Ar Tourter) Date: Thu, 14 Oct 2021 15:29:56 +0100 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> Message-ID: Also add - Shapely - pyshp - gdal Greg On Thu, 14 Oct 2021 at 13:22, Greg' Ar Tourter wrote: > Thanks for all your work Ben. Sorry to see you go. > > Unless someone else want them, I am happy to take over > - keepassxc > - proj > - proj-data > - geos > - cartopy > > Cheers > > Greg > > > On Thu, 14 Oct 2021 at 04:07, Benjamin Trigona-Harany < > slackbuilds at jaxartes.net> wrote: > >> I am no longer going to be maintaining my Slackbuilds. Please feel free >> to claim them. >> >> Best, Ben >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Oct 14 14:57:14 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 14 Oct 2021 21:57:14 +0700 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: <39e518e93dff4c8f4df4bb1f0340146f@schoepfer.info> References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> <39e518e93dff4c8f4df4bb1f0340146f@schoepfer.info> Message-ID: > Could some Admin please put me in as maintainer, also for > digger Please make a PR/MR, which is easier for us to do all this stuff or send a patch works fine too -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From ml at mareichelt.com Thu Oct 14 15:39:58 2021 From: ml at mareichelt.com (Markus Reichelt) Date: Thu, 14 Oct 2021 17:39:58 +0200 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: <20211014143354.3b8ca78d36886ef160616c45@laposte.net> References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> <20211014143354.3b8ca78d36886ef160616c45@laposte.net> Message-ID: * Arnaud via SlackBuilds-users wrote: > Mostly requirements of stuff I already do. thanks From didier at slint.fr Thu Oct 14 16:30:04 2021 From: didier at slint.fr (Didier Spaier) Date: Thu, 14 Oct 2021 18:30:04 +0200 Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? In-Reply-To: References: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> Message-ID: <3ac32f53-4623-8b17-96dd-60c9d1550ec2@slint.fr> CCing the mailing list. Sorry Rich, I won't provide support off list. Le 14/10/2021 ? 17:21, Rich Shepard a ?crit?: > On Wed, 13 Oct 2021, Didier Spaier wrote: > >> Not an answer to your question but you could try this package: >> https://slackware.uk/slint/x86_64/slint-14.2.1/slint/texlive-2021.210418-x86_64-1slint.txz >> >> md5sum: >> https://slackware.uk/slint/x86_64/slint-14.2.1/slint/texlive-2021.210418-x86_64-1slint.md5 >> > > Didier, > > Off the mail list. > > Your package works fine, but I still can't get the bibliography to be > present in the PDF. It might be a bibliography issue; I'm looking into that > today. > > The -current version doesn't have an -extra package, but > texlive-20210324-source.tar.xz and texlive-base-210418.tar.xz. > > After 9-and-a-half minutes the build failed: > > Makefile:9698: recipe for target > 'luatexdir/luaharfbuzz/src/luaharfbuzz/libluaharfbuzz_a-buffer.o' failed > make[4]: *** > [luatexdir/luaharfbuzz/src/luaharfbuzz/libluaharfbuzz_a-buffer.o] Error 1 > make[4]: Leaving directory '/tmp/texlive-20210324-source/build/texk/web2c' > Makefile:18786: recipe for target 'all-recursive' failed > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory '/tmp/texlive-20210324-source/build/texk/web2c' > Makefile:5487: recipe for target 'all' failed > make[2]: *** [all] Error 2 > make[2]: Leaving directory '/tmp/texlive-20210324-source/build/texk/web2c' > Makefile:492: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/tmp/texlive-20210324-source/build/texk' > Makefile:583: recipe for target 'all-recursive' failed > make: *** [all-recursive] Error 1 > > web2c is installed. I'd appreciate a hint on how to identify the source > so I > can fix the issue and let it build to completion. > > Thanks in advance, > > Rich > From didier at slint.fr Thu Oct 14 16:44:21 2021 From: didier at slint.fr (Didier Spaier) Date: Thu, 14 Oct 2021 18:44:21 +0200 Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? In-Reply-To: <3ac32f53-4623-8b17-96dd-60c9d1550ec2@slint.fr> References: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> <3ac32f53-4623-8b17-96dd-60c9d1550ec2@slint.fr> Message-ID: <49a8a185-88f9-b821-a2dd-6f88afef5286@slint.fr> PS Further, I fully agree with Matteo: volunteers in this list kindy provide support in case running a SlackBuild doesn't provide its expected outcome (i.e. either it fails to build or there is an issue at run time and you have benefited of their time for free many, many times). You request goes beyond that so consider getting paid support or (better, in my humble opinion) do some learn to build packages and sort out youselmf the issues you could come across. It is about time. tl;dr: please, don't be a help vampire. Best regards, Didier Le 14/10/2021 ? 18:30, Didier Spaier a ?crit?: > CCing the mailing list. > > Sorry Rich, I won't provide support off list. > > Le 14/10/2021 ? 17:21, Rich Shepard a ?crit?: >> On Wed, 13 Oct 2021, Didier Spaier wrote: >> >>> Not an answer to your question but you could try this package: >>> https://slackware.uk/slint/x86_64/slint-14.2.1/slint/texlive-2021.210418-x86_64-1slint.txz >>> >>> md5sum: >>> https://slackware.uk/slint/x86_64/slint-14.2.1/slint/texlive-2021.210418-x86_64-1slint.md5 >>> >> >> Didier, >> >> Off the mail list. >> >> Your package works fine, but I still can't get the bibliography to be >> present in the PDF. It might be a bibliography issue; I'm looking into >> that >> today. >> >> The -current version doesn't have an -extra package, but >> texlive-20210324-source.tar.xz and texlive-base-210418.tar.xz. >> >> After 9-and-a-half minutes the build failed: >> >> Makefile:9698: recipe for target >> 'luatexdir/luaharfbuzz/src/luaharfbuzz/libluaharfbuzz_a-buffer.o' failed >> make[4]: *** >> [luatexdir/luaharfbuzz/src/luaharfbuzz/libluaharfbuzz_a-buffer.o] Error 1 >> make[4]: Leaving directory >> '/tmp/texlive-20210324-source/build/texk/web2c' >> Makefile:18786: recipe for target 'all-recursive' failed >> make[3]: *** [all-recursive] Error 1 >> make[3]: Leaving directory >> '/tmp/texlive-20210324-source/build/texk/web2c' >> Makefile:5487: recipe for target 'all' failed >> make[2]: *** [all] Error 2 >> make[2]: Leaving directory >> '/tmp/texlive-20210324-source/build/texk/web2c' >> Makefile:492: recipe for target 'all-recursive' failed >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory '/tmp/texlive-20210324-source/build/texk' >> Makefile:583: recipe for target 'all-recursive' failed >> make: *** [all-recursive] Error 1 >> >> web2c is installed. I'd appreciate a hint on how to identify the >> source so I >> can fix the issue and let it build to completion. >> >> Thanks in advance, >> >> 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 artourter at gmail.com Fri Oct 15 03:03:48 2021 From: artourter at gmail.com (Greg' Ar Tourter) Date: Fri, 15 Oct 2021 04:03:48 +0100 Subject: [Slackbuilds-users] updating gis/proj? Message-ID: I am trying to update proj to the latest 8.x version after taking maintainership. I have tested the new version will all its first level dependees and most of them compile without any modifications: - cartopy (taking over as well and updating to 0.20.1 which requires proj 8.x) - cdo - gdal - libgeotiff - pyproj - proj-data however, a couple of the dependees fail to compile as is. - libspatialite needs to be updated to version 5.x (tested with the latest 5.0.1) - openorienteering-mapper fails to compile and even updating to the latest version doesn't help Should I hold off updating? Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at osh.id.au Fri Oct 15 03:28:31 2021 From: lists at osh.id.au (David O'Shaughnessy) Date: Fri, 15 Oct 2021 11:28:31 +0800 Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? In-Reply-To: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> References: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> Message-ID: On Thu, 14 Oct 2021, at 1:24 AM, Rich Shepard wrote: > Could I build the -current TexLive2021 in 14.2? Or should I upgrade > biblatex/Biber to 3.16? You can easily have the latest version of TeX Live installed if you use the official installer (it's non-intrusive and installs to /usr/local by default). Simply install and use tlmgr to keep up to date. -- Dave From slackbuilds at schoepfer.info Fri Oct 15 05:38:30 2021 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 15 Oct 2021 07:38:30 +0200 Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? In-Reply-To: References: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> Message-ID: On 2021-10-13 19:33, Didier Spaier wrote: > Not an answer to your question but you could try this package: > https://slackware.uk/slint/x86_64/slint-14.2.1/slint/texlive-2021.210418-x86_64-1slint.txz Biber is in texlive-extra, so if you use the package from Didier, and build https://github.com/Ponce/slackbuilds/tree/current/office/texlive-extra you should have a complete texlive2021 on 14.2 From sb at rbn.im Fri Oct 15 10:07:42 2021 From: sb at rbn.im (Ruben Schuller) Date: Fri, 15 Oct 2021 12:07:42 +0200 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> Message-ID: <20211015120742.4dae78a3@kiwi.kuchen> Hi, 2021-10-14 Benjamin Trigona-Harany : > I am no longer going to be maintaining my Slackbuilds. Please feel > free to claim them. I have send a mail here a few days ago about taking lua-lpeg. If the patches attached to that mail aren't fine, I can do a merge request via GitLab. There are some other scripts i currently use which i could take if nobody else wants them: libtermkey libvterm lua-lpeg lua-luv lua-mpack msgpack-c neovim unibilium Cheers Ruben From slackbuilds at schoepfer.info Fri Oct 15 10:40:55 2021 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 15 Oct 2021 12:40:55 +0200 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: <20211015120742.4dae78a3@kiwi.kuchen> References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> <20211015120742.4dae78a3@kiwi.kuchen> Message-ID: <054a72b43150785550d191dcabcc3d54@schoepfer.info> > neovim Maybe helpful: https://www.linuxquestions.org/questions/slackware-14/neovim-problems-and-solution-for-slackware-current-4175702020/ From rshepard at appl-ecosys.com Fri Oct 15 12:41:05 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 15 Oct 2021 05:41:05 -0700 (PDT) Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? In-Reply-To: References: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> Message-ID: On Fri, 15 Oct 2021, Franzen via SlackBuilds-users wrote: > Biber is in texlive-extra, so if you use the package from Didier, and > build > https://github.com/Ponce/slackbuilds/tree/current/office/texlive-extra you > should have a complete texlive2021 on 14.2 Thank you, Franzen. There is a bug in the default 14.2 Biber that has been fixed in newer versions. I downloaded a copy of Biber-3.16 and am looking for instructions on how to use it to upgrade the installed version. The issue is when a record in the bibliographic database has a name value with an apostrophe; e.g., '@Article{O'Conner,' because it has no closing curley brace (that's at the end of the entire entry. Apostrophes in any other key:value pair are accepted because the value is enclosed in curley braces. I'll take your advice and use Ponce's texlive-extra. Regards, Rich From rshepard at appl-ecosys.com Fri Oct 15 12:42:32 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 15 Oct 2021 05:42:32 -0700 (PDT) Subject: [Slackbuilds-users] Upgrade 14.2 to TexLive2021 or just biblatex? In-Reply-To: References: <702b3f81-535d-cb5-ea7-dbd6961cb255@appl-ecosys.com> Message-ID: On Fri, 15 Oct 2021, David O'Shaughnessy wrote: > You can easily have the latest version of TeX Live installed if you use > the official installer (it's non-intrusive and installs to /usr/local by > default). Simply install and use tlmgr to keep up to date. Dave, I'll learn how to do this. Thank you, Rich From rshepard at appl-ecosys.com Fri Oct 15 12:47:56 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 15 Oct 2021 05:47:56 -0700 (PDT) Subject: [Slackbuilds-users] updating gis/proj? In-Reply-To: References: Message-ID: On Fri, 15 Oct 2021, Greg' Ar Tourter wrote: > I am trying to update proj to the latest 8.x version after taking > maintainership. > I have tested the new version will all its first level dependees and most > of them compile without any modifications: > - cartopy (taking over as well and updating to 0.20.1 which requires proj > 8.x) > - cdo > - gdal > - libgeotiff > - pyproj > - proj-data > > however, a couple of the dependees fail to compile as is. > - libspatialite needs to be updated to version 5.x (tested with the latest > 5.0.1) > - openorienteering-mapper fails to compile and even updating to the latest > version doesn't help > > Should I hold off updating? Greg' Ar, I'm not an SBo package maintainer but I offer a thought I learned a long time ago about the build sequence for spatial analyses packages. Perhaps it's relavent to your question, perhaps not. The stack proj -> geos -> gdal need to be built in that order. If proj is updated then the other two must also be upgraded. If geos is upgraded then gdal has to be rebuilt. Any other software depending on those need the stack to be rebuilt before they are. I've found this is needed with GRASS, R, and SAGA. Regards, Rich From artourter at gmail.com Fri Oct 15 16:23:02 2021 From: artourter at gmail.com (Greg' Ar Tourter) Date: Fri, 15 Oct 2021 17:23:02 +0100 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> Message-ID: I am going to add pyproj to my list as well since it is required by the latest version of cartopy Cheers Greg On Thu, 14 Oct 2021 at 15:29, Greg' Ar Tourter wrote: > Also add > - Shapely > - pyshp > - gdal > > Greg > > On Thu, 14 Oct 2021 at 13:22, Greg' Ar Tourter > wrote: > >> Thanks for all your work Ben. Sorry to see you go. >> >> Unless someone else want them, I am happy to take over >> - keepassxc >> - proj >> - proj-data >> - geos >> - cartopy >> >> Cheers >> >> Greg >> >> >> On Thu, 14 Oct 2021 at 04:07, Benjamin Trigona-Harany < >> slackbuilds at jaxartes.net> wrote: >> >>> I am no longer going to be maintaining my Slackbuilds. Please feel free >>> to claim them. >>> >>> Best, Ben >>> _______________________________________________ >>> 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 artourter at gmail.com Fri Oct 15 21:07:15 2021 From: artourter at gmail.com (Greg' Ar Tourter) Date: Fri, 15 Oct 2021 22:07:15 +0100 Subject: [Slackbuilds-users] updating gis/proj? In-Reply-To: References: Message-ID: Rich, this is not really what I am asking. I have taken over the maintenance of several of Ben's scripts, some of which can be updated to newer versions, especially proj. proj version 8 has removed something that had been deprecated for quite some time but was still accessible to allow devs to modify their code. Now it is no longer available and therefore some packages can no longer be compiled as they haven't been modified. This is the case for openorienteering-mapper. What I am asking the admins/list is whether it is ok for me to submit an update if a package that depends on it will suffer until a patch is found. Greg On Fri, 15 Oct 2021 at 13:48, Rich Shepard wrote: > On Fri, 15 Oct 2021, Greg' Ar Tourter wrote: > > > I am trying to update proj to the latest 8.x version after taking > > maintainership. > > I have tested the new version will all its first level dependees and most > > of them compile without any modifications: > > - cartopy (taking over as well and updating to 0.20.1 which requires proj > > 8.x) > > - cdo > > - gdal > > - libgeotiff > > - pyproj > > - proj-data > > > > however, a couple of the dependees fail to compile as is. > > - libspatialite needs to be updated to version 5.x (tested with the > latest > > 5.0.1) > > - openorienteering-mapper fails to compile and even updating to the > latest > > version doesn't help > > > > Should I hold off updating? > > Greg' Ar, > > I'm not an SBo package maintainer but I offer a thought I learned a long > time ago about the build sequence for spatial analyses packages. Perhaps > it's relavent to your question, perhaps not. > > The stack proj -> geos -> gdal need to be built in that order. If proj is > updated then the other two must also be upgraded. If geos is upgraded then > gdal has to be rebuilt. Any other software depending on those need the > stack > to be rebuilt before they are. > > I've found this is needed with GRASS, R, and SAGA. > > Regards, > > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Fri Oct 15 21:32:20 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 15 Oct 2021 14:32:20 -0700 (PDT) Subject: [Slackbuilds-users] updating gis/proj? In-Reply-To: References: Message-ID: On Fri, 15 Oct 2021, Greg' Ar Tourter wrote: > Rich, this is not really what I am asking. Greg, Okay. I didn't fully understand your original post. I incorrectly thought it was a build sequence issue, not a removed capability that other packages have not yet accommodated. Stay well, Rich From willysr at slackbuilds.org Sat Oct 16 12:03:59 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 16 Oct 2021 19:03:59 +0700 Subject: [Slackbuilds-users] updating gis/proj? In-Reply-To: References: Message-ID: > proj version 8 has removed something that had been deprecated for quite > some time but was still accessible to allow devs to modify their code. Now > it is no longer available and therefore some packages can no longer be > compiled as they haven't been modified. This is the case for > openorienteering-mapper. > > What I am asking the admins/list is whether it is ok for me to submit an > update if a package that depends on it will suffer until a patch is found. Did you try to update openorienteering-mapper to 0.9.5 and see if it works? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From artourter at gmail.com Sat Oct 16 12:45:08 2021 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sat, 16 Oct 2021 13:45:08 +0100 Subject: [Slackbuilds-users] updating gis/proj? In-Reply-To: References: Message-ID: Hi Willy, Yes I did, it still tries to find proj by looking for the now removed proj_api.h rather than proj.h. I have tried to modify the FindPROJ.cmake file, but since I have never really played with cmake I am just guessing things and it didn't work. The way the version is stored in proj.h is different from what it was before so it is not as simple as just replacing proj_api.h with proj.h. I Will try and dig deeper but haven't found the time yet. If I manage to do it so that it still works with the older file as well I will submit a patch upstream. Whether there are more things in the code that need to be changed, I don't know yet. Cheers Greg On Sat, 16 Oct 2021 at 13:04, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > proj version 8 has removed something that had been deprecated for quite > > some time but was still accessible to allow devs to modify their code. > Now > > it is no longer available and therefore some packages can no longer be > > compiled as they haven't been modified. This is the case for > > openorienteering-mapper. > > > > What I am asking the admins/list is whether it is ok for me to submit an > > update if a package that depends on it will suffer until a patch is > found. > > Did you try to update openorienteering-mapper to 0.9.5 and see if it works? > > > -- > Willy Sudiarto Raharjo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at jaxartes.net Sun Oct 17 10:58:34 2021 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sun, 17 Oct 2021 10:58:34 +0000 (UTC) Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> Message-ID: Thanks Fernando. Oct. 14, 2021 05:47:53 Fernando Lopez : > sad to see you go. :| > > On Wed, Oct 13, 2021 at 9:07 PM Benjamin Trigona-Harany wrote: >> I am no longer going to be maintaining my Slackbuilds. Please feel free to claim them. >> >> Best, Ben >> _______________________________________________ >> 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. > _______________________________________________ > 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 yalhcru at gmail.com Sun Oct 17 16:22:48 2021 From: yalhcru at gmail.com (B Watson) Date: Sun, 17 Oct 2021 12:22:48 -0400 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> Message-ID: On 10/13/21, Benjamin Trigona-Harany wrote: > I am no longer going to be maintaining my Slackbuilds. Please feel free to > claim them. If nobody's already claimed them, I'll take: the_silver_searcher tre weechat From slackbuilds at schoepfer.info Thu Oct 21 07:47:57 2021 From: slackbuilds at schoepfer.info (Franzen) Date: Thu, 21 Oct 2021 09:47:57 +0200 Subject: [Slackbuilds-users] Fwd: Undelivered Mail Returned to Sender In-Reply-To: <20211021074042.97113932DD@mail2.0ur.de> References: <20211021074042.97113932DD@mail2.0ur.de> Message-ID: <2234112fc1884b476d4d2e7e41c722aa@schoepfer.info> Hi, last saturday i mailed to Nishant, and now got the message below. Do i need to try again, or may i take over the mentioned packages? -------- Original Message -------- Subject: Undelivered Mail Returned to Sender Date: 2021-10-21 09:40 From: MAILER-DAEMON at mail2.0ur.de (Mail Delivery System) To: slackbuilds at schoepfer.info This is the mail system at host mail2.0ur.de. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system : connect to mogambo.mnspace.net[73.9.117.31]:25: Connection timed out -------------- next part -------------- UmVwb3J0aW5nLU1UQTogZG5zOyBtYWlsMi4wdXIuZGUNClgtUG9zdGZpeC1RdWV1ZS1JRDogRDRG MUI5MTA3Ng0KWC1Qb3N0Zml4LVNlbmRlcjogcmZjODIyOyBzbGFja2J1aWxkc0BzY2hvZXBmZXIu aW5mbw0KQXJyaXZhbC1EYXRlOiBTYXQsIDE2IE9jdCAyMDIxIDA4OjQ1OjIwICswMjAwIChDRVNU KQ0KDQpGaW5hbC1SZWNpcGllbnQ6IHJmYzgyMjsgbmlzaGFudEBtbnNwYWNlLm5ldA0KT3JpZ2lu YWwtUmVjaXBpZW50OiByZmM4MjI7bmlzaGFudEBtbnNwYWNlLm5ldA0KQWN0aW9uOiBmYWlsZWQN ClN0YXR1czogNC40LjENCkRpYWdub3N0aWMtQ29kZTogWC1Qb3N0Zml4OyBjb25uZWN0IHRvIG1v Z2FtYm8ubW5zcGFjZS5uZXRbNzMuOS4xMTcuMzFdOjI1Og0KICAgIENvbm5lY3Rpb24gdGltZWQg b3V0DQo= -------------- next part -------------- An embedded message was scrubbed... From: Franzen Subject: Slackbuilds and maintaining Date: Sat, 16 Oct 2021 08:45:20 +0200 Size: 1319 URL: From matteo.bernardini at gmail.com Thu Oct 21 07:57:06 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 21 Oct 2021 09:57:06 +0200 Subject: [Slackbuilds-users] Fwd: Undelivered Mail Returned to Sender In-Reply-To: <2234112fc1884b476d4d2e7e41c722aa@schoepfer.info> References: <20211021074042.97113932DD@mail2.0ur.de> <2234112fc1884b476d4d2e7e41c722aa@schoepfer.info> Message-ID: hi Johannes, have you tried at his gmail address too? I'll avoid pasting it here to avoid any possibility of spam, but you can find it on our git. Matteo Il giorno gio 21 ott 2021 alle ore 09:48 Franzen via SlackBuilds-users < slackbuilds-users at slackbuilds.org> ha scritto: > Hi, > > last saturday i mailed to Nishant, and now got the message below. > Do i need to try again, or may i take over the mentioned packages? > > > > -------- Original Message -------- > Subject: Undelivered Mail Returned to Sender > Date: 2021-10-21 09:40 > From: MAILER-DAEMON at mail2.0ur.de (Mail Delivery System) > To: slackbuilds at schoepfer.info > > This is the mail system at host mail2.0ur.de. > > I'm sorry to have to inform you that your message could not > be delivered to one or more recipients. It's attached below. > > For further assistance, please send mail to postmaster. > > If you do so, please include this problem report. You can > delete your own text from the attached returned message. > > The mail system > > : connect to mogambo.mnspace.net[73.9.117.31]:25: > Connection timed out_______________________________________________ > 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 slackbuilds at schoepfer.info Thu Oct 21 08:10:35 2021 From: slackbuilds at schoepfer.info (Franzen) Date: Thu, 21 Oct 2021 10:10:35 +0200 Subject: [Slackbuilds-users] Fwd: Undelivered Mail Returned to Sender In-Reply-To: References: <20211021074042.97113932DD@mail2.0ur.de> <2234112fc1884b476d4d2e7e41c722aa@schoepfer.info> Message-ID: <28ad500add78112cb8d242d632fa16ea@schoepfer.info> Hi Matteo, > have you tried at his gmail address too? No, thanks, i now mailed to him with the gmail account. Johannes From jdashiel at panix.com Thu Oct 21 09:44:50 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Thu, 21 Oct 2021 05:44:50 -0400 Subject: [Slackbuilds-users] sbopkg -c note Message-ID: Note: repo version not obtainable by standard method, may be inaccurate. Can this be cleared by now or should it be cleared later by configuration? One thing I have noticed about slackware and maybe this applies to other linux distros is that the /tmp directory tree tends to be rather permanent unless cleaned out every so often. I've had instances where the root user ran out of space on the system and this was with I think the standard 30gb root partition install space a while ago. I need to go through logs and clean some of those out too so disk quota situations don't happen again for a while. From jebrhansen+SBo at gmail.com Thu Oct 21 16:42:04 2021 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Thu, 21 Oct 2021 10:42:04 -0600 Subject: [Slackbuilds-users] sbopkg -c note In-Reply-To: References: Message-ID: On Thu, Oct 21, 2021, 3:45 AM Jude DaShiell wrote: > Note: repo version not obtainable by standard method, may be inaccurate. > Can this be cleared by now or should it be cleared later by configuration? > One thing I have noticed about slackware and maybe this applies to other > linux distros is that the /tmp directory tree tends to be rather permanent > unless cleaned out every so often. I've had instances where the root user > ran out of space on the system and this was with I think the standard 30gb > root partition install space a while ago. > I need to go through logs and clean some of those out too so disk quota > situations don't happen again for a while. > I can't answer about your error, but while sbopkg doesn't clean up the files in /tmp/ by default, you can change it by setting the following in /etc/sbopkg/sbopkg.conf CLEANUP=${CLEANUP:-NO} to CLEANUP=YES Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From duncan_roe at optusnet.com.au Fri Oct 22 00:32:44 2021 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Fri, 22 Oct 2021 11:32:44 +1100 Subject: [Slackbuilds-users] sbopkg -c note In-Reply-To: References: Message-ID: On Thu, Oct 21, 2021 at 10:42:04AM -0600, Jeremy Hansen wrote: > On Thu, Oct 21, 2021, 3:45 AM Jude DaShiell wrote: > > > Note: repo version not obtainable by standard method, may be inaccurate. > > Can this be cleared by now or should it be cleared later by configuration? > > One thing I have noticed about slackware and maybe this applies to other > > linux distros is that the /tmp directory tree tends to be rather permanent > > unless cleaned out every so often. I've had instances where the root user > > ran out of space on the system and this was with I think the standard 30gb > > root partition install space a while ago. > > I need to go through logs and clean some of those out too so disk quota > > situations don't happen again for a while. > > > > I can't answer about your error, but while sbopkg doesn't clean up the > files in /tmp/ by default, you can change it by setting the following in > /etc/sbopkg/sbopkg.conf > > CLEANUP=${CLEANUP:-NO} > > to > > CLEANUP=YES > > Jeremy I think you are meant to: export CLEANUP=YES before running (un-amended) sbopkg Cheers ... Duncan. From dioput12 at gmail.com Thu Oct 21 02:40:14 2021 From: dioput12 at gmail.com (Dio Putra) Date: Thu, 21 Oct 2021 09:40:14 +0700 Subject: [Slackbuilds-users] [PATCH] spice-vdagentd isn't running Message-ID: It really bother me when using Slackware VM and I can't use spice-vdagent anymore, well until I look at this answer: https://askubuntu.com/a/1298868 Here the result and patch. Ponce, may you put this in the next batch of spice-vdagent package? Thank you. # ls -l /etc/rc.d/rc.spice-vdagent* -rwxr-xr-x 1 root root 1360 Oct 21 09:05 /etc/rc.d/rc.spice-vdagent* -rwxr-xr-x 1 root root 1404 Oct 21 08:11 /etc/rc.d/rc.spice-vdagent.new* -rwxr-xr-x 1 root root 1360 Oct 21 08:11 /etc/rc.d/rc.spice-vdagent.orig* # sh /etc/rc.d/rc.spice-vdagent start Starting spice-vdagentd: # sh /etc/rc.d/rc.spice-vdagent stop spice-vdagentd not running # echo $? 1 # sh /etc/rc.d/rc.spice-vdagent.new start Starting spice-vdagentd: # sh /etc/rc.d/rc.spice-vdagent.new stop Stopping spice-vdagentd: # echo $? 0 # diff -aruN /etc/rc.d/rc.spice-vdagent.{orig,new} --- /etc/rc.d/rc.spice-vdagent.orig 2021-10-21 08:11:14.462000000 +0700 +++ /etc/rc.d/rc.spice-vdagent.new 2021-10-21 08:11:54.457000000 +0700 @@ -20,6 +20,7 @@ /sbin/modprobe uinput > /dev/null 2>&1 # In case the previous running vdagentd crashed /usr/bin/rm -f /var/run/spice-vdagentd/spice-vdagent-sock + /usr/bin/mkdir -p /var/run/spice-vdagentd /usr/bin/echo "Starting $prog: " $exec -s $port retval=$? From jebrhansen+SBo at gmail.com Fri Oct 22 01:20:40 2021 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Thu, 21 Oct 2021 19:20:40 -0600 Subject: [Slackbuilds-users] sbopkg -c note In-Reply-To: References: Message-ID: On Thu, Oct 21, 2021, 6:33 PM Duncan Roe wrote: > On Thu, Oct 21, 2021 at 10:42:04AM -0600, Jeremy Hansen wrote: > > On Thu, Oct 21, 2021, 3:45 AM Jude DaShiell wrote: > > > > > Note: repo version not obtainable by standard method, may be > inaccurate. > > > Can this be cleared by now or should it be cleared later by > configuration? > > > One thing I have noticed about slackware and maybe this applies to > other > > > linux distros is that the /tmp directory tree tends to be rather > permanent > > > unless cleaned out every so often. I've had instances where the root > user > > > ran out of space on the system and this was with I think the standard > 30gb > > > root partition install space a while ago. > > > I need to go through logs and clean some of those out too so disk quota > > > situations don't happen again for a while. > > > > > > > I can't answer about your error, but while sbopkg doesn't clean up the > > files in /tmp/ by default, you can change it by setting the following in > > /etc/sbopkg/sbopkg.conf > > > > CLEANUP=${CLEANUP:-NO} > > > > to > > > > CLEANUP=YES > > > > Jeremy > > I think you are meant to: > > export CLEANUP=YES > > before running (un-amended) sbopkg > > Cheers ... Duncan. > If you want this to stick, you'd need to add the export to your ~/.profile or change the config file I mentioned earlier. Exporting it will only save it for that instance of bash (and any bash sessions spawned from this one) and won't stick to any other sessions already running. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From ml at mareichelt.com Sat Oct 23 21:09:36 2021 From: ml at mareichelt.com (Markus Reichelt) Date: Sat, 23 Oct 2021 23:09:36 +0200 Subject: [Slackbuilds-users] Tor is up for grabs Message-ID: I'm done. Anybody care to step up? Done deal. From slackbuilds at schoepfer.info Sun Oct 24 10:49:31 2021 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 24 Oct 2021 12:49:31 +0200 Subject: [Slackbuilds-users] anyone wants my SlackBuilds? In-Reply-To: <0876e49a5e58008f20380bf4ddabad3c@schoepfer.info> References: <0876e49a5e58008f20380bf4ddabad3c@schoepfer.info> Message-ID: On 2021-09-19 20:09, Franzen via SlackBuilds-users wrote: >> I am not using Slackware anymore, so hereby I turn my SlackBuilds over >> to whoever wants to adopt them. > > I'll take "digger". > > Johannes Here's a patch for taking over maintenance. Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: digger.patch Type: text/x-diff Size: 1553 bytes Desc: not available URL: From matteo.bernardini at gmail.com Sun Oct 24 11:06:54 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 24 Oct 2021 13:06:54 +0200 Subject: [Slackbuilds-users] anyone wants my SlackBuilds? In-Reply-To: References: <0876e49a5e58008f20380bf4ddabad3c@schoepfer.info> Message-ID: Thanks Johannes, pushed in my branch! Matteo Il giorno dom 24 ott 2021 alle ore 12:49 Franzen via SlackBuilds-users < slackbuilds-users at slackbuilds.org> ha scritto: > On 2021-09-19 20:09, Franzen via SlackBuilds-users wrote: > >> I am not using Slackware anymore, so hereby I turn my SlackBuilds over > >> to whoever wants to adopt them. > > > > I'll take "digger". > > > > Johannes > > Here's a patch for taking over maintenance. > > 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 psychi2009 at gmail.com Sun Oct 24 12:49:04 2021 From: psychi2009 at gmail.com (MDrights) Date: Sun, 24 Oct 2021 12:49:04 +0000 Subject: [Slackbuilds-users] Tor is up for grabs In-Reply-To: References: Message-ID: Hi, Tor is not taken up by anyone yet, right? I will take it. Cheers MDrights On Sat, Oct 23, 2021 at 11:09:36PM +0200, Markus Reichelt via SlackBuilds-users wrote: > I'm done. Anybody care to step up? Done deal. > _______________________________________________ > 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 slackbuilds at schoepfer.info Sun Oct 24 12:57:11 2021 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 24 Oct 2021 14:57:11 +0200 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: <39e518e93dff4c8f4df4bb1f0340146f@schoepfer.info> References: <3e3db8c6-69c9-4afe-b8d3-edd487915c15@jaxartes.net> <39e518e93dff4c8f4df4bb1f0340146f@schoepfer.info> Message-ID: On 2021-10-14 15:55, johannes--- via SlackBuilds-users wrote: > On 2021-10-14 05:06, Benjamin Trigona-Harany wrote: >> I am no longer going to be maintaining my Slackbuilds. Please feel >> free to claim them. > > I'd take: > xplanet > xawtv Here are the patches, thanks, Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: xawtv.patch Type: text/x-diff Size: 878 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xplanet.patch Type: text/x-diff Size: 2991 bytes Desc: not available URL: From slackbuilds at schoepfer.info Sun Oct 24 15:57:13 2021 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 24 Oct 2021 17:57:13 +0200 Subject: [Slackbuilds-users] Fwd: Undelivered Mail Returned to Sender In-Reply-To: <28ad500add78112cb8d242d632fa16ea@schoepfer.info> References: <20211021074042.97113932DD@mail2.0ur.de> <2234112fc1884b476d4d2e7e41c722aa@schoepfer.info> <28ad500add78112cb8d242d632fa16ea@schoepfer.info> Message-ID: >> have you tried at his gmail address too? > > No, thanks, i now mailed to him with the gmail account. Here's the answer from Nishant, and a patch for simple-scan, the other builds will follow some time later. Johannes -------- Original Message -------- Subject: Re: Slackbuilds and maintaining Date: 2021-10-21 13:39 From: Nishant Limbachia To: Franzen Hi Johannes, Yes you can take over the maintenance of the slackbuilds. I personally don't use Slack that much these days. Nishant Limbachia On Thu, Oct 21, 2021, 3:08 AM Franzen wrote: > Hi Nishant, > > since your last commit to SBo was two years ago, i wonder if you're > still active. > I'm particular interested in the following builds: > -gocr > -simple-scan > -pflogsumm > -clamav-unofficial-sigs > > May i take over maintenance for these? > > Btw. the mailadress xxx at mnspace.net listed in your various other > packages didn't work for me. > > johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: simple-scan.patch Type: text/x-diff Size: 4874 bytes Desc: not available URL: From alessandro.baggi at gmail.com Mon Oct 25 08:36:29 2021 From: alessandro.baggi at gmail.com (Alessandro Baggi) Date: Mon, 25 Oct 2021 10:36:29 +0200 Subject: [Slackbuilds-users] iotop source download link does not work Message-ID: <7d1e00a4-e122-e7d4-9ba3-2c2bc5f4e310@gmail.com> Hi, I'm trying to compile iotop from ponce-current but the source's link of iotop is dead, well the site seems dead: ??? http://guichaz.free.fr/iotop/files/iotop-0.6.tar.bz2 I found this but I don't know if it is the same with a different version: https://github.com/Tomas-M/iotop/releases/download/v1.20/iotop-1.20.tar.xz Best regards. From artourter at gmail.com Tue Oct 26 16:14:34 2021 From: artourter at gmail.com (Greg' Ar Tourter) Date: Tue, 26 Oct 2021 17:14:34 +0100 Subject: [Slackbuilds-users] updating gis/proj? In-Reply-To: References: Message-ID: Willy, debian has submitted a pull request to support proj8. I have tested it and it seems to work fine on version 0.9.5. I can submit a PR for this update and libspatialite along with my other updates if that is ok so that nothing breaks. Note I am not proposing to take over maintenance of openorienteering-mapper or libspatialite, simply submitting updates to stop these packages from breaking after my updating of the packages I am taking over maintenance. Cheers Greg On Sat, 16 Oct 2021 at 13:45, Greg' Ar Tourter wrote: > Hi Willy, > > Yes I did, it still tries to find proj by looking for the now removed > proj_api.h rather than proj.h. I have tried to modify the FindPROJ.cmake > file, but since I have never really played with cmake I am just guessing > things and it didn't work. > > The way the version is stored in proj.h is different from what it was > before so it is not as simple as just replacing proj_api.h with proj.h. I > Will try and dig deeper but haven't found the time yet. If I manage to do > it so that it still works with the older file as well I will submit a patch > upstream. > > Whether there are more things in the code that need to be changed, I don't > know yet. > > Cheers > > Greg > > > > On Sat, 16 Oct 2021 at 13:04, Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> > proj version 8 has removed something that had been deprecated for quite >> > some time but was still accessible to allow devs to modify their code. >> Now >> > it is no longer available and therefore some packages can no longer be >> > compiled as they haven't been modified. This is the case for >> > openorienteering-mapper. >> > >> > What I am asking the admins/list is whether it is ok for me to submit an >> > update if a package that depends on it will suffer until a patch is >> found. >> >> Did you try to update openorienteering-mapper to 0.9.5 and see if it >> works? >> >> >> -- >> Willy Sudiarto Raharjo >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.public at protonmail.com Wed Oct 27 15:08:51 2021 From: erich.public at protonmail.com (Erich Ritz) Date: Wed, 27 Oct 2021 15:08:51 +0000 Subject: [Slackbuilds-users] douninst.sh in SBo packages Message-ID: <-4yx20_kIH8MAa0GTtm5rfzD4y5cBnFRTA0NEsWLzQjb5dvDqj7ceadRZxynPloCX3W93jO3YRq8VUsSumbmKL9mOOErEXfOeDJOhUcJlO8=@protonmail.com> Hello list, (This question pertains to -current, not 14.2). I want to ask about allowable/preferred behavior in doinst.sh and douninst.sh. Motivation: I maintain a package (system76-io-dkms) that makes use of dkms. This allows new kernel modules to be automatically built for new kernel versions without requiring a package rebuild. Obviously these files won't be tracked by pkgtools, but they are tracked by dkms. The desire then is that when removing the package (by removepkg) it calls out to dkms to remove all files. Hurdles in implementation: removepkg removes all package files before calling douninst.sh, so any configuration files owned by the package won't be available by douninst.sh. This complicates using dkms. Solution: Lucky for me another user described a simple solution: https://www.linuxquestions.org/questions/slackware-14/how-can-removepkg-be-triggered-to-remove-stuff-placed-by-a-doinst-sh-4175672073/page4.html#post6109767. Create a copy of the dkms configuration file in doinst.sh. This will create a file that is not tracked by pkgtools. Now in douninst.sh use that file to call out to dkms to remove the remaining modules that may have been automatically built, and finally remove that file. The end result is that after calling removepkg no more files remain on the filesystem from the package. Here is the patch to system76-io-dkms that implements this behavior: https://gitlab.com/ErichRitz/slackbuilds/-/commit/9c48fe02ac32c382fdac871373054865642440f0 Question: is this behavior acceptable for SBo? I would assume so, but so far there is only 1 other package that makes use of douninst.sh (nvidia-legacy390-driver), so I thought it best to ask first. Erich -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.coldplayer at gmail.com Wed Oct 27 18:48:49 2021 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Wed, 27 Oct 2021 22:48:49 +0400 Subject: [Slackbuilds-users] sbopkg -c note In-Reply-To: References: Message-ID: My /tmp is a tmpfs On Fri, 22 Oct 2021 at 05:20, Jeremy Hansen wrote: > > > On Thu, Oct 21, 2021, 6:33 PM Duncan Roe > wrote: > >> On Thu, Oct 21, 2021 at 10:42:04AM -0600, Jeremy Hansen wrote: >> > On Thu, Oct 21, 2021, 3:45 AM Jude DaShiell wrote: >> > >> > > Note: repo version not obtainable by standard method, may be >> inaccurate. >> > > Can this be cleared by now or should it be cleared later by >> configuration? >> > > One thing I have noticed about slackware and maybe this applies to >> other >> > > linux distros is that the /tmp directory tree tends to be rather >> permanent >> > > unless cleaned out every so often. I've had instances where the root >> user >> > > ran out of space on the system and this was with I think the standard >> 30gb >> > > root partition install space a while ago. >> > > I need to go through logs and clean some of those out too so disk >> quota >> > > situations don't happen again for a while. >> > > >> > >> > I can't answer about your error, but while sbopkg doesn't clean up the >> > files in /tmp/ by default, you can change it by setting the following in >> > /etc/sbopkg/sbopkg.conf >> > >> > CLEANUP=${CLEANUP:-NO} >> > >> > to >> > >> > CLEANUP=YES >> > >> > Jeremy >> >> I think you are meant to: >> >> export CLEANUP=YES >> >> before running (un-amended) sbopkg >> >> Cheers ... Duncan. >> > > If you want this to stick, you'd need to add the export to your ~/.profile > or change the config file I mentioned earlier. > > Exporting it will only save it for that instance of bash (and any bash > sessions spawned from this one) and won't stick to any other sessions > already running. > > Jeremy > _______________________________________________ > 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 z.coldplayer at gmail.com Wed Oct 27 18:53:31 2021 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Wed, 27 Oct 2021 22:53:31 +0400 Subject: [Slackbuilds-users] douninst.sh in SBo packages In-Reply-To: <-4yx20_kIH8MAa0GTtm5rfzD4y5cBnFRTA0NEsWLzQjb5dvDqj7ceadRZxynPloCX3W93jO3YRq8VUsSumbmKL9mOOErEXfOeDJOhUcJlO8=@protonmail.com> References: <-4yx20_kIH8MAa0GTtm5rfzD4y5cBnFRTA0NEsWLzQjb5dvDqj7ceadRZxynPloCX3W93jO3YRq8VUsSumbmKL9mOOErEXfOeDJOhUcJlO8=@protonmail.com> Message-ID: you might have given the answer with nvidia-legacy script. I do not remember douninst.sh being documented. Need to check that . On Wed, 27 Oct 2021 at 19:09, Erich Ritz via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hello list, > > (This question pertains to -current, not 14.2). > > I want to ask about allowable/preferred behavior in doinst.sh and > douninst.sh. > > Motivation: I maintain a package (system76-io-dkms) that makes use of > dkms. This allows new kernel modules to be automatically built for new > kernel versions without requiring a package rebuild. Obviously these files > won't be tracked by pkgtools, but they are tracked by dkms. The desire > then is that when removing the package (by removepkg) it calls out to dkms > to remove all files. > > Hurdles in implementation: removepkg removes all package files before > calling douninst.sh, so any configuration files owned by the package won't > be available by douninst.sh. This complicates using dkms. > > Solution: Lucky for me another user described a simple solution: > https://www.linuxquestions.org/questions/slackware-14/how-can-removepkg-be-triggered-to-remove-stuff-placed-by-a-doinst-sh-4175672073/page4.html#post6109767. > Create a copy of the dkms configuration file in doinst.sh. This will > create a file that is not tracked by pkgtools. Now in douninst.sh use that > file to call out to dkms to remove the remaining modules that may have been > automatically built, and finally remove that file. The end result is that > after calling removepkg no more files remain on the filesystem from the > package. > > Here is the patch to system76-io-dkms that implements this behavior: > https://gitlab.com/ErichRitz/slackbuilds/-/commit/9c48fe02ac32c382fdac871373054865642440f0 > > Question: is this behavior acceptable for SBo? I would assume so, but so > far there is only 1 other package that makes use of douninst.sh > (nvidia-legacy390-driver), so I thought it best to ask first. > > Erich > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.public at protonmail.com Thu Oct 28 12:21:40 2021 From: erich.public at protonmail.com (Erich Ritz) Date: Thu, 28 Oct 2021 12:21:40 +0000 Subject: [Slackbuilds-users] douninst.sh in SBo packages In-Reply-To: References: <-4yx20_kIH8MAa0GTtm5rfzD4y5cBnFRTA0NEsWLzQjb5dvDqj7ceadRZxynPloCX3W93jO3YRq8VUsSumbmKL9mOOErEXfOeDJOhUcJlO8=@protonmail.com> Message-ID: <8BckV9AiDlTp1qUau7hRuipH5U44tQ6xvqlXpHwXvvSKjBPYr0yQ9aPmbeLIXLi4Xm5teqPG_APTZJmtLX9vRiOHj8ZFAAlqFFLkVE_Tk4E=@protonmail.com> ??????? Original Message ??????? On Wednesday, October 27th, 2021 at 1:53 PM, Jheengut Pritvi wrote: > you might have given the answer with? nvidia-legacy script. I do not remember douninst.sh being documented.? Need to check that . douninst.sh was added to SlackBuilds templates here: https://git.slackbuilds.org/templates/commit/?id=2dbac016f564b0fe57019b56c2b1b176b4c3ebe9 The only comments are: # NOTE: This script is run AFTER package removal, so be careful! # Consider it optional, use if it is really needed. So not much guidance there on what is allowable by SBo standards. Erich From yalhcru at gmail.com Thu Oct 28 18:44:23 2021 From: yalhcru at gmail.com (B Watson) Date: Thu, 28 Oct 2021 14:44:23 -0400 Subject: [Slackbuilds-users] douninst.sh in SBo packages In-Reply-To: <8BckV9AiDlTp1qUau7hRuipH5U44tQ6xvqlXpHwXvvSKjBPYr0yQ9aPmbeLIXLi4Xm5teqPG_APTZJmtLX9vRiOHj8ZFAAlqFFLkVE_Tk4E=@protonmail.com> References: <-4yx20_kIH8MAa0GTtm5rfzD4y5cBnFRTA0NEsWLzQjb5dvDqj7ceadRZxynPloCX3W93jO3YRq8VUsSumbmKL9mOOErEXfOeDJOhUcJlO8=@protonmail.com> <8BckV9AiDlTp1qUau7hRuipH5U44tQ6xvqlXpHwXvvSKjBPYr0yQ9aPmbeLIXLi4Xm5teqPG_APTZJmtLX9vRiOHj8ZFAAlqFFLkVE_Tk4E=@protonmail.com> Message-ID: On 10/28/21, Erich Ritz via SlackBuilds-users wrote: > > The only comments are: > > # NOTE: This script is run AFTER package removal, so be careful! > # Consider it optional, use if it is really needed. > > So not much guidance there on what is allowable by SBo standards. I dunno if there's been any discussion of 'allowable', I came up with this: # 20211015 bkw: I was going to have a douninst.sh that runs # /usr/bin/install-info --delete /usr/info/xroar.info.gz /usr/info/dir # but this won't work because removepkg has already deleted # /usr/info/xroar.info.gz before it runs douninst.sh. And you can't # use install-info to remove stuff *by name* from /usr/info/dir; # the info file must actually exist. # So the script has to manually remove the entry from the info dir, # and the Emulators section if it's become empty. if [ -e usr/info/dir ]; then # Remove the entry first: sed -i '/^\* XRoar:/d' usr/info/dir # If the Emulators section is empty now, remove it too: if grep -A1 '^Emulators$' usr/info/dir | tail -1 | grep -q '^$'; then sed -i '/^Emulators$/,+1d' usr/info/dir fi fi From jdashiel at panix.com Fri Oct 29 20:20:08 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Fri, 29 Oct 2021 16:20:08 -0400 Subject: [Slackbuilds-users] clockchimes package Message-ID: can no longer be built. apparently website holding tar file is inaccessible at least with browsers that don't do javascript. From didier at slint.fr Fri Oct 29 21:12:07 2021 From: didier at slint.fr (Didier Spaier) Date: Fri, 29 Oct 2021 23:12:07 +0200 Subject: [Slackbuilds-users] clockchimes package In-Reply-To: References: Message-ID: Hi, Confirmed: the website is up but trying to fetch the source archive gives an error 404. Didier Le 29/10/2021 ? 22:20, Jude DaShiell a ?crit?: > can no longer be built. apparently website holding tar file is > inaccessible at least with browsers that don't do javascript. From slackbuilds at go4it2day.com Fri Oct 29 22:09:49 2021 From: slackbuilds at go4it2day.com (SlackBuilds) Date: Fri, 29 Oct 2021 16:09:49 -0600 Subject: [Slackbuilds-users] clockchimes package In-Reply-To: References: Message-ID: <99b2133b283df514e08fca3b39b049d8@go4it2day.com> Should be all fixed now. Sorry for the mess! Stu On 2021-10-29 15:12, Didier Spaier wrote: > Hi, > > Confirmed: the website is up but trying to fetch the source archive > gives an error 404. > > Didier > > Le 29/10/2021 ? 22:20, Jude DaShiell a ?crit?: >> can no longer be built. apparently website holding tar file is >> inaccessible at least with browsers that don't do javascript. > _______________________________________________ > 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 Oct 29 22:48:14 2021 From: didier at slint.fr (Didier Spaier) Date: Sat, 30 Oct 2021 00:48:14 +0200 Subject: [Slackbuilds-users] clockchimes package In-Reply-To: <99b2133b283df514e08fca3b39b049d8@go4it2day.com> References: <99b2133b283df514e08fca3b39b049d8@go4it2day.com> Message-ID: <8ce551c9-b517-037d-1975-72974d237477@slint.fr> Thanks. But now even though I get answer to ping the website doesn't load in a browser (seems stuck). Didier Le 30/10/2021 ? 00:09, SlackBuilds a ?crit?: > Should be all fixed now. Sorry for the mess! > > Stu > > > On 2021-10-29 15:12, Didier Spaier wrote: >> Hi, >> >> Confirmed: the website is up but trying to fetch the source archive >> gives an error 404. >> >> Didier >> >> Le 29/10/2021 ? 22:20, Jude DaShiell a ?crit?: >>> can no longer be built.? apparently website holding tar file is >>> inaccessible at least with browsers that don't do javascript. >> _______________________________________________ >> 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 Oct 29 22:50:58 2021 From: didier at slint.fr (Didier Spaier) Date: Sat, 30 Oct 2021 00:50:58 +0200 Subject: [Slackbuilds-users] clockchimes package In-Reply-To: <8ce551c9-b517-037d-1975-72974d237477@slint.fr> References: <99b2133b283df514e08fca3b39b049d8@go4it2day.com> <8ce551c9-b517-037d-1975-72974d237477@slint.fr> Message-ID: Sending the previous email I get: : host go4it2day.com[184.96.136.171] said: 550 5.7.1 ... Access denied (in reply to MAIL FROM command) Le 30/10/2021 ? 00:48, Didier Spaier a ?crit?: > Thanks. > > But now even though I get answer to ping the website doesn't load in a > browser (seems stuck). > > Didier > > Le 30/10/2021 ? 00:09, SlackBuilds a ?crit?: >> Should be all fixed now. Sorry for the mess! >> >> Stu >> >> >> On 2021-10-29 15:12, Didier Spaier wrote: >>> Hi, >>> >>> Confirmed: the website is up but trying to fetch the source archive >>> gives an error 404. >>> >>> Didier >>> >>> Le 29/10/2021 ? 22:20, Jude DaShiell a ?crit?: >>>> can no longer be built.? apparently website holding tar file is >>>> inaccessible at least with browsers that don't do javascript. >>> _______________________________________________ From peter at peter-dambier.de Sat Oct 30 08:39:21 2021 From: peter at peter-dambier.de (Peter Dambier) Date: Sat, 30 Oct 2021 10:39:21 +0200 Subject: [Slackbuilds-users] clockchimes package In-Reply-To: References: Message-ID: <20211030103921.3b19a28a@cesium.fritz.box> I found Homepage: https://www.go4it2day.com/news/clockchimes-0.3.html The site offers: https://www.go4it2day.com/downloads/clockchimes/0.3/clockchimes-0.3.tar.gz and a slackbuild: https://www.go4it2day.com/downloads/clockchimes/0.3/clockchimes.tar.gz Stu, are you on the boat? Jude DaShiell wrote: > can no longer be built. apparently website holding tar file is > inaccessible at least with browsers that don't do javascript. > > _______________________________________________ > 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 peter at peter-dambier.de Sat Oct 30 09:26:42 2021 From: peter at peter-dambier.de (Peter Dambier) Date: Sat, 30 Oct 2021 11:26:42 +0200 Subject: [Slackbuilds-users] clockchimes package In-Reply-To: <99b2133b283df514e08fca3b39b049d8@go4it2day.com> References: <99b2133b283df514e08fca3b39b049d8@go4it2day.com> Message-ID: <20211030112642.5534fbac@cesium.fritz.box> Thankyou for the fix Stu. My mail was out of sync. Sorry for the noise. Cheers Peter On Fri, 29 Oct 2021 16:09:49 -0600 SlackBuilds wrote: > Should be all fixed now. Sorry for the mess! > > Stu > > > On 2021-10-29 15:12, Didier Spaier wrote: > > Hi, > > > > Confirmed: the website is up but trying to fetch the source archive > > gives an error 404. > > > > Didier > > > > Le 29/10/2021 ? 22:20, Jude DaShiell a ?crit?: > >> can no longer be built. apparently website holding tar file is > >> inaccessible at least with browsers that don't do javascript. > > _______________________________________________ > > 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 sb at rbn.im Sat Oct 30 16:16:57 2021 From: sb at rbn.im (Ruben Schuller) Date: Sat, 30 Oct 2021 18:16:57 +0200 Subject: [Slackbuilds-users] gnubg Message-ID: <20211030181657.1411d17f@kiwi.kuchen> Hi! The sources for gnubg seem to have moved to https://ftp.gnu.org/gnu/gnubg/gnubg-release-1.06.002-sources.tar.gz Unfortunately the version of the SlackBuild isn't present on the server but just changing the version accordingly builds fine on -current. I haven't tried the OpenGL extension though. Cheers Ruben From jdashiel at panix.com Sat Oct 30 16:18:29 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Sat, 30 Oct 2021 12:18:29 -0400 Subject: [Slackbuilds-users] clockchimes package In-Reply-To: <20211030103921.3b19a28a@cesium.fritz.box> References: <20211030103921.3b19a28a@cesium.fritz.box> Message-ID: Thank you all, the fixes worked and I have clockchimes running on this system now. On Sat, 30 Oct 2021, Peter Dambier wrote: > I found > > Homepage: > > https://www.go4it2day.com/news/clockchimes-0.3.html > > The site offers: > > https://www.go4it2day.com/downloads/clockchimes/0.3/clockchimes-0.3.tar.gz > > and a slackbuild: > > https://www.go4it2day.com/downloads/clockchimes/0.3/clockchimes.tar.gz > > Stu, are you on the boat? > > > Jude DaShiell wrote: > > > can no longer be built. apparently website holding tar file is > > inaccessible at least with browsers that don't do javascript. > > > > _______________________________________________ > > 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/ > > > >