From alleytrotter at gmail.com Tue Mar 1 20:25:43 2022 From: alleytrotter at gmail.com (John Yost) Date: Tue, 1 Mar 2022 15:25:43 -0500 Subject: [Slackbuilds-users] system76-power Message-ID: <9afd1f39-478e-f296-ba27-d5cc83abcf46@gmail.com> Having trouble building system76-power SlackBuild fails with tar: /home/john/SourceFiles/system/system76power/build/sysfs-class-0.1.3.crate: Cannot open: No such file or directory tar: Error is not recoverable: exiting now The SlackBuild in the past would the needed rust build just to build the program now it no longer seems to do that. I have tried adding the SlackBuild for rustup but no cigar. Can anyone offer any advice. -- John David Yost AlleyTrotter pub 2048D/F3BDEB55 2014-05-23 [expires: Never] From erich.public at protonmail.com Tue Mar 1 21:15:17 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Tue, 01 Mar 2022 21:15:17 +0000 Subject: [Slackbuilds-users] Respect Content-disposition header always? Message-ID: <0zcU39srXUs8mpo-6H8KIiJTFK9QMVO_yWw-xrP2DWzzzdHI4tOU7qXWhNW_1MBLlUfBVKQf2YdI-6NW30FR-jrijyMA5jhrDewWI_czqG4=@protonmail.com> Based on this commit: http://git.slackbuilds.org/slackbuilds/commit/?id=59ddd1a2287f3432c9bf1e3f690c8d17c9fcef5d I guess it's now SBo policy that downloads must respect Content-disposition? Or I missed that it always was? (note that wget --content-disposition downloads this file as pop-os-sysfs-class-0.1.3-1-gab63e7f.tar.gz). I've been (ab)using github's feature that you can name a download file whatever you want, with the purpose of making the SlackBuild much easier to write. Erich -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Mar 1 21:27:59 2022 From: yalhcru at gmail.com (B Watson) Date: Tue, 1 Mar 2022 16:27:59 -0500 Subject: [Slackbuilds-users] Respect Content-disposition header always? In-Reply-To: <0zcU39srXUs8mpo-6H8KIiJTFK9QMVO_yWw-xrP2DWzzzdHI4tOU7qXWhNW_1MBLlUfBVKQf2YdI-6NW30FR-jrijyMA5jhrDewWI_czqG4=@protonmail.com> References: <0zcU39srXUs8mpo-6H8KIiJTFK9QMVO_yWw-xrP2DWzzzdHI4tOU7qXWhNW_1MBLlUfBVKQf2YdI-6NW30FR-jrijyMA5jhrDewWI_czqG4=@protonmail.com> Message-ID: On 3/1/22, Erich Ritz via SlackBuilds-users wrote: > Based on this commit: > > http://git.slackbuilds.org/slackbuilds/commit/?id=59ddd1a2287f3432c9bf1e3f690c8d17c9fcef5d > > I guess it's now SBo policy that downloads must respect Content-disposition? > Or I missed that it always was? Yeah, that's something we've started doing systematically, because it makes life easier for us when we're doing mass-rebuilds. It also makes life easier for users, who persist in using whatever tool they feel like to download the file (which results in emails from the users when the script fails because of the filename...) A while back there was a post to the mailing list about it (like, a few years back). Probably one of us should write up a FAQ and link it from the submissions section on the web site. > (note that wget --content-disposition downloads this file as > pop-os-sysfs-class-0.1.3-1-gab63e7f.tar.gz). > > I've been (ab)using github's feature that you can name a download file > whatever you want, with the purpose of making the SlackBuild much easier to > write. Please don't do that... Plus, it doesn't make it that much easier: your script still has to refer to the extracted directory by the same name as the content-disposition would have given you. From erich.public at protonmail.com Tue Mar 1 21:52:50 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Tue, 01 Mar 2022 21:52:50 +0000 Subject: [Slackbuilds-users] Respect Content-disposition header always? In-Reply-To: References: <0zcU39srXUs8mpo-6H8KIiJTFK9QMVO_yWw-xrP2DWzzzdHI4tOU7qXWhNW_1MBLlUfBVKQf2YdI-6NW30FR-jrijyMA5jhrDewWI_czqG4=@protonmail.com> Message-ID: ------- Original Message ------- On Tuesday, March 1st, 2022 at 3:27 PM, B Watson wrote: > On 3/1/22, Erich Ritz via SlackBuilds-users > > slackbuilds-users at slackbuilds.org wrote: > > > Based on this commit: > > > > http://git.slackbuilds.org/slackbuilds/commit/?id=59ddd1a2287f3432c9bf1e3f690c8d17c9fcef5d > > > > I guess it's now SBo policy that downloads must respect Content-disposition? > > > > Or I missed that it always was? > > Yeah, that's something we've started doing systematically, because it > makes life easier for us when we're doing mass-rebuilds. It also makes > life easier for users, who persist in using whatever tool they feel > like to download the file (which results in emails from the users when > the script fails because of the filename...) > > A while back there was a post to the mailing list about it (like, a > few years back). Probably one of us should write up a FAQ and link it > from the submissions section on the web site. > > > (note that wget --content-disposition downloads this file as > > pop-os-sysfs-class-0.1.3-1-gab63e7f.tar.gz). > > > > I've been (ab)using github's feature that you can name a download file > > whatever you want, with the purpose of making the SlackBuild much easier to > > write. > > Please don't do that... I hear you loud and clear. Turns out the only 2 places I've done it were on crate files. The 1 you fixed and 1 I have not yet submitted waiting for 15.0 to open for new submissions. I fixed it as well. > > Plus, it doesn't make it that much easier: your script still > has to refer to the extracted directory by the same name as the > content-disposition would have given you. In my case I didn't, because I am using: mkdir $SPECIAL_DIR && tar xvf $CRATE_FILE -C $SPECIAL_DIR --strip-components=1. ... all so I can follow cargo's conventions! Thanks for the clarification. Erich From duncan_roe at optusnet.com.au Tue Mar 1 23:57:41 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Wed, 2 Mar 2022 10:57:41 +1100 Subject: [Slackbuilds-users] [SlackBuildsOrg/slackbuilds] Afdkov2 (PR #1276) In-Reply-To: References: Message-ID: On Tue, Mar 01, 2022 at 06:43:59AM -0800, Willy Sudiarto Raharjo wrote: > why do you put set -x when you have set -e at the middle? in scikit-build > Forgot to remove my local changes. When building, I always make up to 3 changes: 1. put 'set -x' at top 2. Change 'tar xvf' to 'tar xf' (to not lose o/p from 'set -x') 3. Change 'make' to 'make -j$$($(nproc)+1))||make' (N/A for scikit-build) set -e at the middle is from the template. Will do a v3 PR. Cheers ... Duncan. From duncan_roe at optusnet.com.au Wed Mar 2 01:15:26 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Wed, 2 Mar 2022 12:15:26 +1100 Subject: [Slackbuilds-users] Please update your zopfli SlackBuild Message-ID: Hi Oleg, zopfli is now a Python Package on https://pypi.org/. zopfli changed its revision numbering scheme so PyPi has 0.1.9 but e.g. > diff zopfli-zopfli-1.0.0/src/zopfli/zopfli.h zopfli-0.1.9/zopfli/src/zopfli/zopfli.h shows 1.0.9 is newer. I suggest adjust the C build for changed directory structure then insert > python3 setup.py install --root=$PKG before the line starting 'find $PKG -print0 | xargs -0 file |' zopfli is a runtime dependency of afdko and hence a build time dependency of Type1_to_OTF (which I maintain). Cheers ... Duncan. From duncan_roe at optusnet.com.au Wed Mar 2 01:22:07 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Wed, 2 Mar 2022 12:22:07 +1100 Subject: [Slackbuilds-users] Please update your zopfli SlackBuild In-Reply-To: References: Message-ID: On Wed, Mar 02, 2022 at 12:15:26PM +1100, Duncan Roe wrote: > Hi Oleg, > > zopfli is now a Python Package on https://pypi.org/. > > zopfli changed its revision numbering scheme so PyPi has 0.1.9 but e.g. > > > diff zopfli-zopfli-1.0.0/src/zopfli/zopfli.h zopfli-0.1.9/zopfli/src/zopfli/zopfli.h > > shows 1.0.9 is newer. *** 0.1.9 > > I suggest adjust the C build for changed directory structure then insert > > > python3 setup.py install --root=$PKG > > before the line starting 'find $PKG -print0 | xargs -0 file |' > > zopfli is a runtime dependency of afdko and hence a build time dependency of > Type1_to_OTF (which I maintain). > > Cheers ... Duncan. From fellype at gmail.com Wed Mar 2 13:03:23 2022 From: fellype at gmail.com (Fellype) Date: Wed, 2 Mar 2022 10:03:23 -0300 Subject: [Slackbuilds-users] patch for a suggested update: misc/ltunify Message-ID: Hi all! Here follows a patch to update misc/ltunify. Currently, Xgates (emailed in cc) is listed as the maintainer of this package. I don't want to take over maintenance of ltunify. I'm just suggesting an update and sharing a patch with the necessary changes. ltunify-0.2 (the version at SBo) is ~9yo and it is very outdated. Regards, Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ltunify_update.patch Type: text/x-patch Size: 1033 bytes Desc: not available URL: From slackbuilds at schoepfer.info Wed Mar 2 13:20:57 2022 From: slackbuilds at schoepfer.info (Franzen) Date: Wed, 02 Mar 2022 14:20:57 +0100 Subject: [Slackbuilds-users] maintenance patchage and ganv Message-ID: <385b8de9f660b9ecb0092f71bf76ad3a@schoepfer.info> Hi, as Ryan gave up maintenance of his scripts some years ago, i'd like to take over patchage and ganv, any objections? Johannes From ricardo at palmtx.com.ar Wed Mar 2 16:12:13 2022 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Wed, 02 Mar 2022 13:12:13 -0300 Subject: [Slackbuilds-users] NodeJS version in Slackbuild causing issues In-Reply-To: <20220226234133.onuu4ckdxjkjlzrj@epsilon> References: <20220226230416.ygeehhkcfa2qnrid@epsilon> <20220226172842.7b00c14a@home.rlworkman.net> <20220226234133.onuu4ckdxjkjlzrj@epsilon> Message-ID: <2069020.9o76ZdvQCi@lenovo.universe.dat> FYI, SBo admins surely know already but nodejs LTS got added to Slackware today: slackware64 current changes for Wed, 02 Mar 2022 01:54:23 GMT a/lrzip-0.650-x86_64-1.txz: Upgraded. d/mercurial-6.1-x86_64-1.txz: Upgraded. l/nodejs-16.14.0-x86_64-1.txz: Added. Thanks to Audrius Ka??ukauskas, Ryan P.C. McQuen, and Willy Sudiarto Raharjo for the slackbuilds.org version of the build script. El sabado, 26 de febrero de 2022 20:41:33 -03 nix escribio: > > The last post in that thread indicates to try upgrading nodejs to 17.6.0. > > Try that -- it's been updated in the SBo master branch already. > > > > -RW > > Ah, I forgot to pull the latest version in the repo. Thanks for for > that. I will give it a try. > > Eric -- Ricardo J. Barberis Usuario LFS N? 5121: https://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - DonWeb.com From dave at slackbuilds.org Wed Mar 2 17:41:14 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 2 Mar 2022 17:41:14 +0000 Subject: [Slackbuilds-users] patch for a suggested update: misc/ltunify In-Reply-To: References: Message-ID: <20220302174114.GT4508@localhost> On 02/03/22 10:03, Fellype put forth the proposition: > Hi all! > Here follows a patch to update misc/ltunify. > Currently, Xgates (emailed in cc) is listed as the maintainer of this > package. > I don't want to take over maintenance of ltunify. I'm just suggesting an > update and sharing a patch with the necessary changes. > ltunify-0.2 (the version at SBo) is ~9yo and it is very outdated. > Regards, > Fellype Pushed to my branch. Thanks -- Dave From duncan_roe at optusnet.com.au Wed Mar 2 23:09:47 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Thu, 3 Mar 2022 10:09:47 +1100 Subject: [Slackbuilds-users] NodeJS version in Slackbuild causing issues In-Reply-To: <2069020.9o76ZdvQCi@lenovo.universe.dat> References: <20220226230416.ygeehhkcfa2qnrid@epsilon> <20220226172842.7b00c14a@home.rlworkman.net> <20220226234133.onuu4ckdxjkjlzrj@epsilon> <2069020.9o76ZdvQCi@lenovo.universe.dat> Message-ID: On Wed, Mar 02, 2022 at 01:12:13PM -0300, Ricardo J. Barberis wrote: > FYI, SBo admins surely know already but nodejs LTS got added to Slackware > today: > > slackware64 current changes for Wed, 02 Mar 2022 01:54:23 GMT > a/lrzip-0.650-x86_64-1.txz: Upgraded. > d/mercurial-6.1-x86_64-1.txz: Upgraded. > l/nodejs-16.14.0-x86_64-1.txz: Added. > Thanks to Audrius Ka??ukauskas, Ryan P.C. McQuen, and Willy Sudiarto Raharjo > for the slackbuilds.org version of the build script. > > El sabado, 26 de febrero de 2022 20:41:33 -03 nix escribio: > > > The last post in that thread indicates to try upgrading nodejs to 17.6.0. > > > Try that -- it's been updated in the SBo master branch already. > > > > > > -RW > > > > Ah, I forgot to pull the latest version in the repo. Thanks for for > > that. I will give it a try. > > > > Eric > I don't see this in 15.0 patches http://slackware.osuosl.org/slackware64-15.0/patches/packages/ Cheers ... Duncan. From arnaud.garcia-fernandez at laposte.net Wed Mar 2 23:35:54 2022 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Wed, 02 Mar 2022 23:35:54 +0000 Subject: [Slackbuilds-users] NodeJS version in Slackbuild causing issues In-Reply-To: References: <20220226230416.ygeehhkcfa2qnrid@epsilon> <20220226172842.7b00c14a@home.rlworkman.net> <20220226234133.onuu4ckdxjkjlzrj@epsilon> <2069020.9o76ZdvQCi@lenovo.universe.dat> Message-ID: <7E1B2E1A-B548-482C-BE44-5D0CC6E6A28E@laposte.net> That will not change anything on slackbuilds.org, because node.js was added to -current. We are at 15.0, so no node.js there, and we need to keep maintaining it. It'll be dropped when 15.1 is out. Yeah, yeah, one day... ?? - Yth. Le 2 mars 2022 23:09:47 UTC, Duncan Roe a ?crit?: >On Wed, Mar 02, 2022 at 01:12:13PM -0300, Ricardo J. Barberis wrote: >> FYI, SBo admins surely know already but nodejs LTS got added to Slackware >> today: >> >> slackware64 current changes for Wed, 02 Mar 2022 01:54:23 GMT >> a/lrzip-0.650-x86_64-1.txz: Upgraded. >> d/mercurial-6.1-x86_64-1.txz: Upgraded. >> l/nodejs-16.14.0-x86_64-1.txz: Added. >> Thanks to Audrius Ka??ukauskas, Ryan P.C. McQuen, and Willy Sudiarto Raharjo >> for the slackbuilds.org version of the build script. >> >> El sabado, 26 de febrero de 2022 20:41:33 -03 nix escribio: >> > > The last post in that thread indicates to try upgrading nodejs to 17.6.0. >> > > Try that -- it's been updated in the SBo master branch already. >> > > >> > > -RW >> > >> > Ah, I forgot to pull the latest version in the repo. Thanks for for >> > that. I will give it a try. >> > >> > Eric >> >I don't see this in 15.0 patches >http://slackware.osuosl.org/slackware64-15.0/patches/packages/ > >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/ > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From nix at nixing.mx Wed Mar 2 23:36:32 2022 From: nix at nixing.mx (nix) Date: Wed, 2 Mar 2022 17:36:32 -0600 Subject: [Slackbuilds-users] NodeJS version in Slackbuild causing issues In-Reply-To: References: <20220226230416.ygeehhkcfa2qnrid@epsilon> <20220226172842.7b00c14a@home.rlworkman.net> <20220226234133.onuu4ckdxjkjlzrj@epsilon> <2069020.9o76ZdvQCi@lenovo.universe.dat> Message-ID: <20220302233632.amzeezxfisgruk5q@epsilon.local> > I don't see this in 15.0 patches > http://slackware.osuosl.org/slackware64-15.0/patches/packages/ > It seems to be in the dependencies for firefox and thunderbird: https://mirrors.eze.sysarmy.com/slackware/slackware64-15.0/source/xap/mozilla-firefox/build-deps/nodejs/ Eric, From j+sbo-users at maschinengott.de Thu Mar 3 00:21:18 2022 From: j+sbo-users at maschinengott.de (Johannes Georgi) Date: Thu, 3 Mar 2022 01:21:18 +0100 Subject: [Slackbuilds-users] Any help? In-Reply-To: References: Message-ID: <68aa6cd6-1bac-fda1-dbce-f9142cbfc3f3@maschinengott.de> Hi Barry, I suspect Jeremy misundestood you, and what you want is a list of SBo SlackBuilds that aren't yet updated AND weren't yet tested to work on Slackware 15.0. I think such a list exists only implicitly, as, to my knowledge, no infrastructure/workflow exists to maintain it. It implicitly exists inform of the repo itself, insofar as SlackBuilds tested negative and with no one willing to change that are dropped from the repo. If someone is willing to change it (maintain maintainership, so to say), they'll get updated eventually. So it's not much use testing if a package works if one is not willing to maintain it, because the maintainer will do that anyway, and if they don't, it will get dropped. I hope I got that right, cya, j12i On 28.02.22 00:07, Barry J. Grundy wrote: > I have tested all my SlackBuilds as the currently sit in the master > repo.? They all compile without error.? I have plenty of updates and new > submissions to add once submissions are open again. > > In the meantime I'm wondering if there is a list of SlackBuilds we can > test or that need some attention. Any other way the larger community can > help with the workload? > > Thanks for all the hard work, > Barry From jebrhansen+SBo at gmail.com Thu Mar 3 00:25:57 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 2 Mar 2022 17:25:57 -0700 Subject: [Slackbuilds-users] Any help? In-Reply-To: <68aa6cd6-1bac-fda1-dbce-f9142cbfc3f3@maschinengott.de> References: <68aa6cd6-1bac-fda1-dbce-f9142cbfc3f3@maschinengott.de> Message-ID: Johannes, No, I was referencing the "plenty of updates and new submissions to add once submissions are open again" portion of Barry's message. However, if there is a list of SlackBuilds that no one is maintaining that aren't working, I'd be happy to review them and potentially step up as maintainer. Until that becomes available, I'll just maintain my own. Jeremy On Wed, Mar 2, 2022 at 5:22 PM Johannes Georgi wrote: > Hi Barry, > I suspect Jeremy misundestood you, and what you want is a list of SBo > SlackBuilds that aren't yet updated AND weren't yet tested to work on > Slackware 15.0. > I think such a list exists only implicitly, as, to my knowledge, no > infrastructure/workflow exists to maintain it. It implicitly exists > inform of the repo itself, insofar as SlackBuilds tested negative and > with no one willing to change that are dropped from the repo. If someone > is willing to change it (maintain maintainership, so to say), they'll > get updated eventually. > So it's not much use testing if a package works if one is not willing to > maintain it, because the maintainer will do that anyway, and if they > don't, it will get dropped. > I hope I got that right, cya, j12i > > On 28.02.22 00:07, Barry J. Grundy wrote: > > I have tested all my SlackBuilds as the currently sit in the master > > repo. They all compile without error. I have plenty of updates and new > > submissions to add once submissions are open again. > > > > In the meantime I'm wondering if there is a list of SlackBuilds we can > > test or that need some attention. Any other way the larger community can > > help with the workload? > > > > Thanks for all the hard work, > > Barry > _______________________________________________ > 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 davidnchmelik at gmail.com Thu Mar 3 05:12:39 2022 From: davidnchmelik at gmail.com (David Chmelik) Date: Wed, 2 Mar 2022 21:12:39 -0800 Subject: [Slackbuilds-users] lbench In-Reply-To: References: <34c3bcd2-4d79-18e3-f9f7-b36389c343b1@gmail.com> <8e1f6e98-dfed-8f2a-047f-2a2f4976180b@slackbuilds.org> <9eeeff74-262d-c6b9-f493-cbcc87f31837@gmail.com> Message-ID: <49c5c3e0-d9cd-8494-4fda-f25125af8666@gmail.com> On 2/16/22 9:36 PM, Willy Sudiarto Raharjo wrote: >> A day or two ago it also built fine for me but now has several >> dependencies not in Slackware nor SBo but for some reason not required >> to compile, such as libclutter-gtk. >> >> ?? "libclutter-gtk dependencies: >> ?? libc6, libcairo2, libclutter, libcogl20, libgdk-pixbuf, libglib2, >> ?? libgtk-3, libwayland"--Michael Cornelison (lbench creator.) > I think it's an optional dependency > and also did you test them in a clean environment where no other > packages were installed? > > testing on a polluted environment can bring more dependencies sometimes Not optional... d at 0.cosmos:~$ lbench lbench: error while loading shared libraries: libcogl.so.20: cannot open shared object file: No such file or directory ??? I was emailing lbench creator and he makes Wayland/GNOME (or some such libraries) required now. From andrew.david.strong at gmail.com Thu Mar 3 08:12:07 2022 From: andrew.david.strong at gmail.com (andrew) Date: Thu, 3 Mar 2022 19:12:07 +1100 Subject: [Slackbuilds-users] maildrop and courier-unicode updates for 15.0 Message-ID: Attached is a patch to update maildrop and a patch to update its required dependency courier-unicode. courier unicode is a simple version bump, maildrop has dropped the HTML docs (which duplicate the man pages), dropped a rarely used build option and version bump. Andrew -- You think that's air you're breathing now? -------------- next part -------------- diff --git a/network/maildrop/maildrop.SlackBuild b/network/maildrop/maildrop.SlackBuild index 4a7501c3..78d5f551 100644 --- a/network/maildrop/maildrop.SlackBuild +++ b/network/maildrop/maildrop.SlackBuild @@ -3,7 +3,7 @@ # Slackware build script for maildrop # # Copyright 2010 - 2019 ?ime Ramov -# Copyright 2019 - 2021 Andrew Strong, Blue Mountains, Australia. +# Copyright 2019 - 2022 Andrew Strong, Blue Mountains, Australia. # # Permission to use, copy, modify, and distribute this software for # any purpose with or without fee is hereby granted, provided that @@ -27,7 +27,7 @@ cd $(dirname $0) ; CWD=$(pwd) PRGNAM=maildrop -VERSION=${VERSION:-3.0.1} +VERSION=${VERSION:-3.0.7} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} @@ -91,7 +91,6 @@ CXXFLAGS="$SLKCFLAGS" \ --datadir=/usr/doc/$PRGNAM-$VERSION \ --disable-static \ --enable-dovecotauth \ - --with-devel \ --build=$ARCH-slackware-linux make @@ -107,12 +106,16 @@ find $PKG/usr/man -type f -exec gzip -9 {} \; for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done mkdir -pv $PKG/usr/doc/$PRGNAM-$VERSION -mv $PKG/usr/share/doc/$PRGNAM/html $PKG/usr/doc/$PRGNAM-$VERSION -rm -rf $PKG/usr/share - cp -a \ AUTHORS COPYING* ChangeLog INSTALL README README.dovecotauth UPGRADE \ $PKG/usr/doc/$PRGNAM-$VERSION + +# The HTML docs are simply copies of the man pages, so are removed from +# generated package. If you really want the HTML version of the man pages +# simply uncomment the line below: +# mv $PKG/usr/share/doc/$PRGNAM/html $PKG/usr/doc/$PRGNAM-$VERSION +rm -rf $PKG/usr/share + cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild mkdir -p $PKG/install diff --git a/network/maildrop/maildrop.info b/network/maildrop/maildrop.info index 5becdd46..347b6dbc 100644 --- a/network/maildrop/maildrop.info +++ b/network/maildrop/maildrop.info @@ -1,8 +1,8 @@ PRGNAM="maildrop" -VERSION="3.0.1" +VERSION="3.0.7" HOMEPAGE="http://www.courier-mta.org/maildrop/" -DOWNLOAD="https://download.sourceforge.net/courier/maildrop-3.0.1.tar.bz2" -MD5SUM="28f6a5dfa6da4110719240696d528299" +DOWNLOAD="https://download.sourceforge.net/courier/maildrop-3.0.7.tar.bz2" +MD5SUM="7ae78e4dc2b0ad9a2d1d1d3e5d619e76" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="courier-unicode" -------------- next part -------------- diff --git a/network/courier-unicode/courier-unicode.SlackBuild b/network/courier-unicode/courier-unicode.SlackBuild index 90c7f3be..04beef2c 100644 --- a/network/courier-unicode/courier-unicode.SlackBuild +++ b/network/courier-unicode/courier-unicode.SlackBuild @@ -3,7 +3,7 @@ # Slackware build script for courier unicode # # Copyright 2015 - 2019 Derek Noonburg (derekn at foolabs.com) -# Copyright 2019 - 2021 Andrew Strong, Blue Mountains, Australia. +# Copyright 2019 - 2022 Andrew Strong, Blue Mountains, Australia. # # Permission to use, copy, modify, and distribute this software for # any purpose with or without fee is hereby granted, provided that @@ -27,7 +27,7 @@ cd $(dirname $0) ; CWD=$(pwd) PRGNAM=courier-unicode -VERSION=${VERSION:-2.1.2} +VERSION=${VERSION:-2.2.3} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} diff --git a/network/courier-unicode/courier-unicode.info b/network/courier-unicode/courier-unicode.info index 79b4f414..70f4f8db 100644 --- a/network/courier-unicode/courier-unicode.info +++ b/network/courier-unicode/courier-unicode.info @@ -1,8 +1,8 @@ PRGNAM="courier-unicode" -VERSION="2.1.2" +VERSION="2.2.3" HOMEPAGE="http://www.courier-mta.org/unicode/" -DOWNLOAD="https://download.sourceforge.net/courier/courier-unicode-2.1.2.tar.bz2" -MD5SUM="f35eb33593aa81a8a15c7d40cf5fb9b5" +DOWNLOAD="https://download.sourceforge.net/courier/courier-unicode-2.2.3.tar.bz2" +MD5SUM="2a3be811e113840500253c2b14bb1d7c" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" From andrew.clemons at gmail.com Thu Mar 3 08:38:15 2022 From: andrew.clemons at gmail.com (Andrew Clemons) Date: Thu, 3 Mar 2022 21:38:15 +1300 Subject: [Slackbuilds-users] maildrop and courier-unicode updates for 15.0 In-Reply-To: References: Message-ID: On 2022-03-03 19:12:07 +1100, andrew.david.strong at gmail.com wrote: > Attached is a patch to update maildrop and a patch to update its > required dependency courier-unicode. > > courier unicode is a simple version bump, maildrop has dropped the > HTML docs (which duplicate the man pages), dropped a rarely used build > option and version bump. Applied on my branch. thanks. From whynot at pozharski.name Thu Mar 3 10:21:50 2022 From: whynot at pozharski.name (Eric Pozharski) Date: Thu, 3 Mar 2022 12:21:50 +0200 Subject: [Slackbuilds-users] Any help? In-Reply-To: References: <68aa6cd6-1bac-fda1-dbce-f9142cbfc3f3@maschinengott.de> Message-ID: <20220303102150.GA2784@orphan.zombinet> On Wed, Mar 02, 2022 at 05:25:57PM -0700, Jeremy Hansen wrote: > No, I was referencing the "plenty of updates and new submissions to > add once submissions are open again" portion of Barry's message. > > However, if there is a list of SlackBuilds that no one is maintaining > that aren't working, I'd be happy to review them and potentially step > up as maintainer. Until that becomes available, I'll just maintain my > own. > Yes, please. Before current has left 15.0 behind (and went ahead) I had problems building few packages and I expect those aren't building now. Fixes were (are?) trivial (except one -- contrib/ wasn't building, I just disabled this part). And now 15.0 is a thing. And I don't what to do about it. What are procedures and resources for situations like this? *CUT* -- Torvalds' goal for Linux is very simple: World Domination Stallman's goal for GNU is even simpler: Freedom From fernando.lopezjr at gmail.com Thu Mar 3 16:00:55 2022 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 3 Mar 2022 09:00:55 -0700 Subject: [Slackbuilds-users] inkscape update to 1.1.2 Message-ID: thank you. -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: inkscape.tar.xz Type: application/x-xz Size: 3992 bytes Desc: not available URL: From ozan.turkyilmaz at gmail.com Thu Mar 3 19:25:47 2022 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Thu, 3 Mar 2022 22:25:47 +0300 Subject: [Slackbuilds-users] Slackbuild for sflphone In-Reply-To: References: <20140330002524.745d38cf@stygian.midgard.home> Message-ID: Christoph Willing , 4 Nis 2014 Cum, 16:24 tarihinde ?unu yazd?: > > The sflphone webbsite looked interesting so I built your packages but > found I couldn't do video with it. After also building the gnome client > directory (not just the kde client directory), the video became available. > That needs additional prerequisites to build - cogl, clutter & clutter-gtk. > That much looks good. > > I have ready scripts for clutter clutter-gtk and cogl for evolution build. https://gitlab.com/ozanty/slackbuild-scripts/-/tree/master/evolution Regards, Ozan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricardo at palmtx.com.ar Thu Mar 3 19:40:28 2022 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Thu, 03 Mar 2022 16:40:28 -0300 Subject: [Slackbuilds-users] NodeJS version in Slackbuild causing issues In-Reply-To: <7E1B2E1A-B548-482C-BE44-5D0CC6E6A28E@laposte.net> References: <20220226230416.ygeehhkcfa2qnrid@epsilon> <7E1B2E1A-B548-482C-BE44-5D0CC6E6A28E@laposte.net> Message-ID: <2606429.vuYhMxLoTh@lenovo.universe.dat> You're right of course, I mistakenly was reading current's changelog instead of 15.0's. El miercoles, 2 de marzo de 2022 20:35:54 -03 Arnaud via SlackBuilds-users escribio: > That will not change anything on slackbuilds.org, because node.js was added > to -current. We are at 15.0, so no node.js there, and we need to keep > maintaining it. > > It'll be dropped when 15.1 is out. > Yeah, yeah, one day... ??? > > - Yth. > > Le 2 mars 2022 23:09:47 UTC, Duncan Roe a ??crit? : > >On Wed, Mar 02, 2022 at 01:12:13PM -0300, Ricardo J. Barberis wrote: > >> FYI, SBo admins surely know already but nodejs LTS got added to Slackware > >> today: > >> > >> slackware64 current changes for Wed, 02 Mar 2022 01:54:23 GMT > >> a/lrzip-0.650-x86_64-1.txz: Upgraded. > >> d/mercurial-6.1-x86_64-1.txz: Upgraded. > >> l/nodejs-16.14.0-x86_64-1.txz: Added. > >> > >> Thanks to Audrius Ka? ??ukauskas, Ryan P.C. McQuen, and Willy Sudiarto > >> Raharjo for the slackbuilds.org version of the build script. > >> > >> El sabado, 26 de febrero de 2022 20:41:33 -03 nix escribio: > >> > > The last post in that thread indicates to try upgrading nodejs to > >> > > 17.6.0. > >> > > Try that -- it's been updated in the SBo master branch already. > >> > > > >> > > -RW > >> > > >> > Ah, I forgot to pull the latest version in the repo. Thanks for for > >> > that. I will give it a try. > >> > > >> > Eric > > > >I don't see this in 15.0 patches > >http://slackware.osuosl.org/slackware64-15.0/patches/packages/ > > > >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/ -- Ricardo J. Barberis Usuario LFS N? 5121: https://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - DonWeb.com From mrvladislavovich at gmail.com Thu Mar 3 23:01:53 2022 From: mrvladislavovich at gmail.com (MyRequiem) Date: Fri, 4 Mar 2022 03:01:53 +0400 Subject: [Slackbuilds-users] Source DVD iso image for 15.0 Message-ID: Hi all. Where can I download source codes for Slackware-15.0 like slackware-15.0-source-dvd.iso ? From duncan_roe at optusnet.com.au Fri Mar 4 01:25:04 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Fri, 4 Mar 2022 12:25:04 +1100 Subject: [Slackbuilds-users] Please update your tqdm SlackBuild Message-ID: Hi Dionysis, tqdm on PyPi is at version 4.63.0, but your SB is installing 4.62.0. Could you update your SB please? Type1_to_OTF (that I maintain) requires at least 4.62.3 to build. Cheers ... Duncan. From yakizarns1 at gmail.com Fri Mar 4 02:38:04 2022 From: yakizarns1 at gmail.com (Dionysis Ntreou) Date: Fri, 4 Mar 2022 02:38:04 +0000 Subject: [Slackbuilds-users] Please update your tqdm SlackBuild In-Reply-To: References: Message-ID: Hello Duncan, Sorry about this I will update it, I am just on Holidays getting back home on Monday. If you need it urgently I am happy for you to push an update in the meantime. Regards Dionysi On Fri, Mar 4, 2022 at 1:25 AM Duncan Roe wrote: > Hi Dionysis, > > tqdm on PyPi is at version 4.63.0, but your SB is installing 4.62.0. > > Could you update your SB please? Type1_to_OTF (that I maintain) requires at > least 4.62.3 to build. > > Cheers ... Duncan. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.david.strong at gmail.com Fri Mar 4 03:16:03 2022 From: andrew.david.strong at gmail.com (andrew) Date: Fri, 4 Mar 2022 14:16:03 +1100 Subject: [Slackbuilds-users] Update for 15.0: nv-codec-headers Message-ID: Hi, Attached is a patch against latest git for Slackware 15.0 and nv-codec-headers. Andrew -- You think that's air you're breathing now? -------------- next part -------------- diff --git a/libraries/nv-codec-headers/README b/libraries/nv-codec-headers/README index 54f1224e..35098671 100644 --- a/libraries/nv-codec-headers/README +++ b/libraries/nv-codec-headers/README @@ -1,8 +1,8 @@ The FFmpeg version of Nvidia Codec SDK headers which are required to interface with Nvidia's codec APIs. The purpose of these headers is to allow hardware (GPU) encoding with suitable NVidia -cards. This version corresponds to Video Codec SDK version 11.0.10 -and requires NVidia drivers version 455.28 or newer. +cards. This version corresponds to Video Codec SDK version 11.1.5 +and requires NVidia drivers version 470.57.02 or newer. There are 3 stages in the history of NVidia GPU encoding with FFmpeg: diff --git a/libraries/nv-codec-headers/nv-codec-headers.SlackBuild b/libraries/nv-codec-headers/nv-codec-headers.SlackBuild old mode 100644 new mode 100755 index fb90b4c4..4fcd92f2 --- a/libraries/nv-codec-headers/nv-codec-headers.SlackBuild +++ b/libraries/nv-codec-headers/nv-codec-headers.SlackBuild @@ -2,7 +2,7 @@ # Slackware build script for nv-codec-headers -# Copyright 2018-2021, Andrew Strong, Blue Mountains, Australia. +# Copyright 2018-2022, Andrew Strong, Blue Mountains, Australia. # All rights reserved. # # Redistribution and use of this script, with or without modification, is @@ -27,7 +27,7 @@ cd $(dirname $0) ; CWD=$(pwd) PRGNAM=nv-codec-headers # Note that the version number is contained # within the file ffnvcodec.pc.in: -VERSION=${VERSION:-11.0.10.0} +VERSION=${VERSION:-11.1.5.1} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} @@ -72,10 +72,10 @@ rm -rf $PRGNAM rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP -rm -rf $PRGNAM-$VERSION -tar xvf $CWD/$PRGNAM-$VERSION.tar.gz +rm -rf $PRGNAM-n$VERSION +tar xvf $CWD/$PRGNAM-n$VERSION.tar.gz -cd $PRGNAM-$VERSION +cd $PRGNAM-n$VERSION chown -R root:root . make PREFIX=/usr LIBDIR=lib${LIBDIRSUFFIX} install DESTDIR=$PKG diff --git a/libraries/nv-codec-headers/nv-codec-headers.info b/libraries/nv-codec-headers/nv-codec-headers.info index ff59df3c..da209c24 100644 --- a/libraries/nv-codec-headers/nv-codec-headers.info +++ b/libraries/nv-codec-headers/nv-codec-headers.info @@ -1,8 +1,8 @@ PRGNAM="nv-codec-headers" -VERSION="11.0.10.0" +VERSION="11.1.5.1" HOMEPAGE="https://github.com/FFmpeg/nv-codec-headers" -DOWNLOAD="https://github.com/FFmpeg/nv-codec-headers/releases/download/n11.0.10.0/nv-codec-headers-11.0.10.0.tar.gz" -MD5SUM="b3513b09f42036a0d591f2e68a27dfb5" +DOWNLOAD="https://github.com/FFmpeg/nv-codec-headers/archive/refs/tags/n11.1.5.1.tar.gz" +MD5SUM="7369898ed93e0c9bb4ad1fef80888806" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" diff --git a/libraries/nv-codec-headers/slack-desc b/libraries/nv-codec-headers/slack-desc index 2d7cc06f..c690a433 100644 --- a/libraries/nv-codec-headers/slack-desc +++ b/libraries/nv-codec-headers/slack-desc @@ -9,7 +9,7 @@ nv-codec-headers: nv-codec-headers (FFmpeg version of Nvidia Codec SDK headers) nv-codec-headers: nv-codec-headers: FFmpeg version of headers required to interface with Nvidia's -nv-codec-headers: codec APIs. Corresponds to Video Codec SDK version 11.0.10. +nv-codec-headers: codec APIs. Corresponds to Video Codec SDK version 11.1.5. nv-codec-headers: nv-codec-headers: nv-codec-headers: From duncan_roe at optusnet.com.au Fri Mar 4 07:41:42 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Fri, 4 Mar 2022 18:41:42 +1100 Subject: [Slackbuilds-users] Please update your tqdm SlackBuild In-Reply-To: References: Message-ID: On Fri, Mar 04, 2022 at 02:38:04AM +0000, Dionysis Ntreou wrote: > Hello Duncan, > > Sorry about this > > I will update it, I am just on Holidays getting back home on Monday. > If you need it urgently I am happy for you to push an update in the > meantime. > > Regards > Dionysi > > On Fri, Mar 4, 2022 at 1:25 AM Duncan Roe > wrote: > > > Hi Dionysis, > > > > tqdm on PyPi is at version 4.63.0, but your SB is installing 4.62.0. > > > > Could you update your SB please? Type1_to_OTF (that I maintain) requires at > > least 4.62.3 to build. > > > > Cheers ... Duncan. > > Hi Dionysis, Many thanks for that: I sent a pull request with the minumum necessary changes. On a freshly installed 15.0 system, python is python3, so your SB only makes the 3.9 packages. You might want to change `python` to `python2`, but I leave that up to you. Sorry to interrupt your holiday and enjoy the rest of it, Cheers ... Duncan. From willysr at slackbuilds.org Fri Mar 4 08:26:10 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 4 Mar 2022 15:26:10 +0700 Subject: [Slackbuilds-users] maintenance patchage and ganv In-Reply-To: <385b8de9f660b9ecb0092f71bf76ad3a@schoepfer.info> References: <385b8de9f660b9ecb0092f71bf76ad3a@schoepfer.info> Message-ID: > as Ryan gave up maintenance of his scripts some years ago, i'd like to > take over > patchage and ganv, any objections? Go for it -- 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 willysr at slackbuilds.org Fri Mar 4 08:31:37 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 4 Mar 2022 15:31:37 +0700 Subject: [Slackbuilds-users] lbench In-Reply-To: <49c5c3e0-d9cd-8494-4fda-f25125af8666@gmail.com> References: <34c3bcd2-4d79-18e3-f9f7-b36389c343b1@gmail.com> <8e1f6e98-dfed-8f2a-047f-2a2f4976180b@slackbuilds.org> <9eeeff74-262d-c6b9-f493-cbcc87f31837@gmail.com> <49c5c3e0-d9cd-8494-4fda-f25125af8666@gmail.com> Message-ID: <88716380-7f22-db85-ac76-225a33105561@slackbuilds.org> >>> A day or two ago it also built fine for me but now has several >>> dependencies not in Slackware nor SBo but for some reason not required >>> to compile, such as libclutter-gtk. >>> >>> ??? "libclutter-gtk dependencies: >>> ??? libc6, libcairo2, libclutter, libcogl20, libgdk-pixbuf, libglib2, >>> ??? libgtk-3, libwayland"--Michael Cornelison (lbench creator.) >> I think it's an optional dependency >> and also did you test them in a clean environment where no other >> packages were installed? >> >> testing on a polluted environment can bring more dependencies sometimes > Not optional... > > ?? d at 0.cosmos:~$ lbench > ?? lbench: error while loading shared libraries: libcogl.so.20: cannot > ?? open shared object file: No such file or directory > > ??? I was emailing lbench creator and he makes Wayland/GNOME (or some > such libraries) required now. Do you have other third party packages that relates to cogl? because it works here without cogl -- 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 willysr at slackbuilds.org Fri Mar 4 08:34:38 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 4 Mar 2022 15:34:38 +0700 Subject: [Slackbuilds-users] Source DVD iso image for 15.0 In-Reply-To: References: Message-ID: > Where can I download source codes for Slackware-15.0 like > slackware-15.0-source-dvd.iso ? https://mirrors.slackware.com/slackware/slackware-iso/slackware64-15.0-iso/ Sources are available here: https://slackware.osuosl.org/slackware64-15.0/source/ -- 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 davidnchmelik at gmail.com Fri Mar 4 08:43:10 2022 From: davidnchmelik at gmail.com (David Chmelik) Date: Fri, 4 Mar 2022 00:43:10 -0800 Subject: [Slackbuilds-users] lbench In-Reply-To: <88716380-7f22-db85-ac76-225a33105561@slackbuilds.org> References: <34c3bcd2-4d79-18e3-f9f7-b36389c343b1@gmail.com> <8e1f6e98-dfed-8f2a-047f-2a2f4976180b@slackbuilds.org> <9eeeff74-262d-c6b9-f493-cbcc87f31837@gmail.com> <49c5c3e0-d9cd-8494-4fda-f25125af8666@gmail.com> <88716380-7f22-db85-ac76-225a33105561@slackbuilds.org> Message-ID: On 3/4/22 12:31 AM, Willy Sudiarto Raharjo wrote: >>>> A day or two ago it also built fine for me but now has several >>>> dependencies not in Slackware nor SBo but for some reason not required >>>> to compile, such as libclutter-gtk. >>>> >>>> ??? "libclutter-gtk dependencies: >>>> ??? libc6, libcairo2, libclutter, libcogl20, libgdk-pixbuf, libglib2, >>>> ??? libgtk-3, libwayland"--Michael Cornelison (lbench creator.) >>> I think it's an optional dependency >>> and also did you test them in a clean environment where no other >>> packages were installed? >>> >>> testing on a polluted environment can bring more dependencies sometimes >> Not optional... >> >> ?? d at 0.cosmos:~$ lbench >> ?? lbench: error while loading shared libraries: libcogl.so.20: cannot >> ?? open shared object file: No such file or directory >> >> ??? I was emailing lbench creator and he makes Wayland/GNOME (or some >> such libraries) required now. > Do you have other third party packages that relates to cogl? > because it works here without cogl Not that I know of; COGL isn't on SBo as far as I'm aware: I had to get it (and Clutter libraries) from GFS, and I'm using lbench 6 (worked w/those)... lbench 3.n didn't have enough threads for my recent CPUs but used to work if I added lines for those myself. From mrvladislavovich at gmail.com Fri Mar 4 08:47:36 2022 From: mrvladislavovich at gmail.com (MyRequiem) Date: Fri, 4 Mar 2022 12:47:36 +0400 Subject: [Slackbuilds-users] Source DVD iso image for 15.0 In-Reply-To: References: Message-ID: Re: Willy Sudiarto Raharjo 04.03.2022 >> Where can I download source codes for Slackware-15.0 like >> slackware-15.0-source-dvd.iso ? > >https://mirrors.slackware.com/slackware/slackware-iso/slackware64-15.0-iso/ > >Sources are available here: >https://slackware.osuosl.org/slackware64-15.0/source/ > > >-- >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/ > The fact of the matter is that for 14.2 there is an image with source codes, but for 15.0 there is not. For 14.2 you can download via torrent, but where is the sr? image for 15.0? http://www.slackware.com/getslack/torrents.php It is not convenient to download the necessary package from the repository every time. From matteo.bernardini at gmail.com Fri Mar 4 08:56:28 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 4 Mar 2022 09:56:28 +0100 Subject: [Slackbuilds-users] Source DVD iso image for 15.0 In-Reply-To: References: Message-ID: actually you can download sources via rsync, it's even more handy (and faster too) than the torrent rsync -avP --delete-after rsync://slackware.uk/slackware/slackware64-15.0/source/ slackware64-15.0-source Il giorno ven 4 mar 2022 alle ore 09:47 MyRequiem ha scritto: > > Re: Willy Sudiarto Raharjo 04.03.2022 > >> Where can I download source codes for Slackware-15.0 like > >> slackware-15.0-source-dvd.iso ? > > > >https://mirrors.slackware.com/slackware/slackware-iso/slackware64-15.0-iso/ > > > >Sources are available here: > >https://slackware.osuosl.org/slackware64-15.0/source/ > > > > > >-- > >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/ > > > > The fact of the matter is that for 14.2 there is an image with source > codes, but for 15.0 there is not. > > For 14.2 you can download via torrent, but where is the sr? image for 15.0? > http://www.slackware.com/getslack/torrents.php > > It is not convenient to download the necessary package from the > repository every time. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From matteo.bernardini at gmail.com Fri Mar 4 08:57:35 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 4 Mar 2022 09:57:35 +0100 Subject: [Slackbuilds-users] Source DVD iso image for 15.0 In-Reply-To: References: Message-ID: Il giorno ven 4 mar 2022 alle ore 09:56 Matteo Bernardini ha scritto: > rsync -avP --delete-after > rsync://slackware.uk/slackware/slackware64-15.0/source/ > slackware64-15.0-source FWIW this is all in one line... From mrvladislavovich at gmail.com Fri Mar 4 09:00:49 2022 From: mrvladislavovich at gmail.com (MyRequiem) Date: Fri, 4 Mar 2022 13:00:49 +0400 Subject: [Slackbuilds-users] Source DVD iso image for 15.0 In-Reply-To: References: Message-ID: Re: Matteo Bernardini 04.03.2022 >Il giorno ven 4 mar 2022 alle ore 09:56 Matteo Bernardini > ha scritto: >> rsync -avP --delete-after >> rsync://slackware.uk/slackware/slackware64-15.0/source/ >> slackware64-15.0-source > >FWIW this is all in one line... >_______________________________________________ >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/ > Yes, I will have to do that. Many thanks :) From slackbuilds at schoepfer.info Fri Mar 4 10:37:39 2022 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 04 Mar 2022 11:37:39 +0100 Subject: [Slackbuilds-users] maintenance patchage and ganv In-Reply-To: References: <385b8de9f660b9ecb0092f71bf76ad3a@schoepfer.info> Message-ID: <1a7e2b332f5c70672d2366b95c8b06b2@schoepfer.info> On 2022-03-04 09:26, Willy Sudiarto Raharjo wrote: >> as Ryan gave up maintenance of his scripts some years ago, i'd like to >> take over >> patchage and ganv, any objections? > > Go for it Here are the patches. Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: ganv.patch Type: text/x-diff Size: 5450 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: patchage.patch Type: text/x-diff Size: 5149 bytes Desc: not available URL: From jdashiel at panix.com Fri Mar 4 12:36:35 2022 From: jdashiel at panix.com (Jude DaShiell) Date: Fri, 4 Mar 2022 07:36:35 -0500 Subject: [Slackbuilds-users] bas package status Message-ID: <4755a742-e20-51af-2871-357cfe4093c6@panix.com> Is this package orphaned? Its slackbuild is out-of-date. I downloaded what was on slackbuilds.org then did a little research and got bas to build on my system after making necessary modification on the slackbuild script locally. cut here. #!/bin/sh # Slackware build script for bas # Written by G. Schoenmakers PRGNAM=bas VERSION=${VERSION:-2.5} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} if [ -z "$ARCH" ]; then case "$( uname -m )" in i?86) ARCH=i586 ;; arm*) ARCH=arm ;; *) ARCH=$( uname -m ) ;; esac fi CWD=$(pwd) TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} if [ "$ARCH" = "i586" ]; then SLKCFLAGS="-O2 -march=i586 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="-O2 -march=i686 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" else SLKCFLAGS="-O2" LIBDIRSUFFIX="" fi set -e rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $PRGNAM-$VERSION tar xvf $CWD/$PRGNAM-$VERSION.tar.gz cd $PRGNAM-$VERSION chown -R root:root . find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 -o -perm 511 \) \ -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \ -exec chmod 644 {} \; CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ --prefix=$PKG/usr \ --libdir=$PKG/usr/lib${LIBDIRSUFFIX} \ --sysconfdir=$PKG/etc \ --localstatedir=$PKG/var \ --mandir=$PKG/usr/man \ --docdir=$PKG/usr/doc/$PRGNAM-$VERSION \ --build=$ARCH-slackware-linux make make install find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true find $PKG/usr/man -type f -exec gzip -9 {} \; for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cp -a INSTALL LICENSE NEWS README $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc cd $PKG /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} cut here. From willysr at slackbuilds.org Fri Mar 4 13:00:08 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 4 Mar 2022 20:00:08 +0700 Subject: [Slackbuilds-users] maintenance patchage and ganv In-Reply-To: <1a7e2b332f5c70672d2366b95c8b06b2@schoepfer.info> References: <385b8de9f660b9ecb0092f71bf76ad3a@schoepfer.info> <1a7e2b332f5c70672d2366b95c8b06b2@schoepfer.info> Message-ID: <07edf257-b186-26e1-3ee9-74521a4ab5e6@slackbuilds.org> > Here are the patches. Merged thanks -- 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 willysr at slackbuilds.org Fri Mar 4 13:04:59 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 4 Mar 2022 20:04:59 +0700 Subject: [Slackbuilds-users] Update for 15.0: nv-codec-headers In-Reply-To: References: Message-ID: > Attached is a patch against latest git for Slackware 15.0 and > nv-codec-headers. merged, but with some modification to keep github URL handling please use the same format for future updates -- 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 willysr at slackbuilds.org Fri Mar 4 13:09:07 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 4 Mar 2022 20:09:07 +0700 Subject: [Slackbuilds-users] 0001-games-OpenRA-OpenRA-updated-for-version-20210321-fix.patch In-Reply-To: References: Message-ID: <3047bc5a-ecd3-9d00-3925-e8dbe89fc9a4@slackbuilds.org> > I noticed that my update to OpenRA hadn't been merged at all, and no one > mentioned anything, so I looked it over and noticed, there was some > trailing white space. So here is a new patch. The dotnet dependency I > added applied cleanly so no need to revisit that. Merged -- 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 erich.public at protonmail.com Fri Mar 4 13:47:34 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Fri, 04 Mar 2022 13:47:34 +0000 Subject: [Slackbuilds-users] Please update your tqdm SlackBuild In-Reply-To: References: Message-ID: <6P1ZSxeTSx30wxmwLYUfIurvLOOjcP0mGlvnwluH3DjoIKAI9lueOiJqZzpKVjHmmA4tfYGuz9MQs0W1BhL13lAGc5OhIXhWf9TVWkUKofk=@protonmail.com> ------- Original Message ------- On Friday, March 4th, 2022 at 1:41 AM, Duncan Roe wrote: > On Fri, Mar 04, 2022 at 02:38:04AM +0000, Dionysis Ntreou wrote: > > > Hello Duncan, > > > > Sorry about this > > > > I will update it, I am just on Holidays getting back home on Monday. > > > > If you need it urgently I am happy for you to push an update in the > > > > meantime. > > > > Regards > > > > Dionysi > > > > On Fri, Mar 4, 2022 at 1:25 AM Duncan Roe duncan_roe at optusnet.com.au > > > > wrote: > > > > > Hi Dionysis, > > > > > > tqdm on PyPi is at version 4.63.0, but your SB is installing 4.62.0. > > > > > > Could you update your SB please? Type1_to_OTF (that I maintain) requires at > > > > > > least 4.62.3 to build. > > > > > > Cheers ... Duncan. > > Hi Dionysis, > > Many thanks for that: I sent a pull request with the minumum necessary changes. > > On a freshly installed 15.0 system, python is python3, so your SB only makes the > > 3.9 packages. You might want to change `python` to `python2`, but I leave that > > up to you. No, /usr/bin/python points to python2.7: $ ls -l /usr/bin/python* lrwxrwxrwx 1 root root 9 Apr 8 2021 /usr/bin/python -> python2.7* lrwxrwxrwx 1 root root 14 Apr 8 2021 /usr/bin/python-config -> python2-config* lrwxrwxrwx 1 root root 9 Apr 8 2021 /usr/bin/python2 -> python2.7* lrwxrwxrwx 1 root root 16 Apr 8 2021 /usr/bin/python2-config -> python2.7-config* -rwxr-xr-x 1 root root 14392 Feb 13 2021 /usr/bin/python2.7* -rwxr-xr-x 1 root root 1681 Feb 13 2021 /usr/bin/python2.7-config* lrwxrwxrwx 1 root root 9 Jan 18 13:46 /usr/bin/python3 -> python3.9* lrwxrwxrwx 1 root root 16 Jan 18 13:46 /usr/bin/python3-config -> python3.9-config* -rwxr-xr-x 1 root root 14392 Jan 15 20:42 /usr/bin/python3.9* -rwxr-xr-x 1 root root 3067 Jan 15 20:42 /usr/bin/python3.9-config* -rwxr-xr-x 1 root root 3020 Apr 18 2021 /usr/bin/pythontex* Looks like existing practice on SBo is split between "python setup.py" and python2 setup.py", with the majority being "python setup.py": $ git grep "python setup.py" | wc -l 662 $ git grep "python2 setup.py" | wc -l 298 $ git grep "python3 setup.py" | wc -l 671 Erich From arnaud.garcia-fernandez at laposte.net Fri Mar 4 13:55:38 2022 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Fri, 4 Mar 2022 14:55:38 +0100 Subject: [Slackbuilds-users] Please update your tqdm SlackBuild In-Reply-To: <6P1ZSxeTSx30wxmwLYUfIurvLOOjcP0mGlvnwluH3DjoIKAI9lueOiJqZzpKVjHmmA4tfYGuz9MQs0W1BhL13lAGc5OhIXhWf9TVWkUKofk=@protonmail.com> References: <6P1ZSxeTSx30wxmwLYUfIurvLOOjcP0mGlvnwluH3DjoIKAI9lueOiJqZzpKVjHmmA4tfYGuz9MQs0W1BhL13lAGc5OhIXhWf9TVWkUKofk=@protonmail.com> Message-ID: <20220304145538.794e84ac566c0eb48294c96f@laposte.net> > > Hi Dionysis, > > > > Many thanks for that: I sent a pull request with the minumum necessary changes. > > On a freshly installed 15.0 system, python is python3, so your SB only makes the > > 3.9 packages. You might want to change `python` to `python2`, but I leave that > > up to you. > > No, /usr/bin/python points to python2.7: [...] > Looks like existing practice on SBo is split between "python setup.py" and python2 setup.py", with the majority being "python setup.py": > > $ git grep "python setup.py" | wc -l > 662 > $ git grep "python2 setup.py" | wc -l > 298 > $ git grep "python3 setup.py" | wc -l > 671 > > > Erich Looking at install scripts for slackware's python2 and python3, the symbolic link /usr/bin/python is for python2, whatever package you install first. And even if python2 is uninstalled, you won't have a /usr/bin/python executable. So python is python2, and python3 is always explicit. However, more and more slackbuilds are explicit for python2 also, which is a good thing, and should be the rule, at least whenever any given python2 package is updated for another good reason. - Yth. From yalhcru at gmail.com Fri Mar 4 16:32:33 2022 From: yalhcru at gmail.com (B Watson) Date: Fri, 4 Mar 2022 11:32:33 -0500 Subject: [Slackbuilds-users] bas package status In-Reply-To: <4755a742-e20-51af-2871-357cfe4093c6@panix.com> References: <4755a742-e20-51af-2871-357cfe4093c6@panix.com> Message-ID: On 3/4/22, Jude DaShiell wrote: > Is this package orphaned? > Its slackbuild is out-of-date. I downloaded what was on slackbuilds.org > then did a little research and got bas to build on my system after making > necessary modification on the slackbuild script locally. The maintainer is G. Schoenmakers, who hasn't been active since 2015. Do you want to maintain bas? I'll update the .info file with your info, if so. From jdashiel at panix.com Fri Mar 4 16:49:16 2022 From: jdashiel at panix.com (Jude DaShiell) Date: Fri, 4 Mar 2022 11:49:16 -0500 Subject: [Slackbuilds-users] bas package status In-Reply-To: References: <4755a742-e20-51af-2871-357cfe4093c6@panix.com> Message-ID: I'll take it on if nobody else wants it and I hope I don't mess it up. So if I need to ask questions I'll be back here. On Fri, 4 Mar 2022, B Watson wrote: If I take this on, it will be the first package I've ever maintained. > On 3/4/22, Jude DaShiell wrote: > > Is this package orphaned? > > Its slackbuild is out-of-date. I downloaded what was on slackbuilds.org > > then did a little research and got bas to build on my system after making > > necessary modification on the slackbuild script locally. > > The maintainer is G. Schoenmakers, who hasn't been active since 2015. > > Do you want to maintain bas? I'll update the .info file with your > info, if so. > _______________________________________________ > 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 yalhcru at gmail.com Fri Mar 4 17:14:52 2022 From: yalhcru at gmail.com (B Watson) Date: Fri, 4 Mar 2022 12:14:52 -0500 Subject: [Slackbuilds-users] bas package status In-Reply-To: References: <4755a742-e20-51af-2871-357cfe4093c6@panix.com> Message-ID: On 3/4/22, Jude DaShiell wrote: > I'll take it on if nobody else wants it and I hope I don't mess it up. So > if I need to ask questions I'll be back here. -MAINTAINER="G. Schoenmakers" -EMAIL="gschoen at iinet.net.au" +MAINTAINER="Jude DaShiell" +EMAIL="jdashiel at panix.com" Welcome to the club! From erich.public at protonmail.com Fri Mar 4 17:32:24 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Fri, 04 Mar 2022 17:32:24 +0000 Subject: [Slackbuilds-users] Setting LD_LIBRARY_PATH for zulu-openjdk11 Message-ID: <4zOZ3LqQRPvUtPfdFYe93zUo6GAq5CgYqy9PXOuZtIYyekYYi2GYv4RWfuelm51fHp9VNI8PP9cl2fvf6ehNxkao757a-AjPiSjW2IqVykw=@protonmail.com> Hi S?bastien, Would you consider adding the patches attached (and also at https://gitlab.com/ErichRitz/slackbuilds/-/commits/zulu-openjdk11) for zulu-openjdk11? Currently this is the only thing I have setting LD_LIBRARY_PATH, and it prepends a ":", which in effect also adds "." to my LD_LIBRARY_PATH, which I don't want. This patch first checks if LD_LIBRARY_PATH is empty before setting it to account for this. The second patch is fancier and only adds ${JAVA_HOME}/lib/server to LD_LIBRARY_PATH if it doesn't already exist. With my setup contents of /etc/profile.d end up getting sourced more than once. If you don't want to take this patch that's fine. The same argument goes for MANPATH as well (patches 3 and 4). Erich -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-development-zulu-openjdk11-Do-not-prepend-to-LD_LIBR.patch Type: text/x-patch Size: 1886 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-development-zulu-openjdk11-Only-add-path-to-LD_LIBRA.patch Type: text/x-patch Size: 1174 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0004-development-zulu-openjdk11-Only-add-patch-to-MANPATH.patch Type: text/x-patch Size: 1009 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0003-development-zulu-openjdk11-Do-not-prepend-to-MANPATH.patch Type: text/x-patch Size: 1805 bytes Desc: not available URL: From andrzej at telszewski.com Fri Mar 4 18:37:49 2022 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Fri, 04 Mar 2022 19:37:49 +0100 Subject: [Slackbuilds-users] rtl8821ce: Reason for removal Message-ID: <9cc4d0fe-51c6-441c-9fb1-e3174887393f@www.fastmail.com> Hi, I noticed that _network/rtl8821ce_ has been removed from master branch. There is no info in the log why is it so. Could you please explain? Thank you! :-) -- Best regards, Andrzej Telszewski From dave at slackbuilds.org Fri Mar 4 20:07:36 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 4 Mar 2022 20:07:36 +0000 Subject: [Slackbuilds-users] rtl8821ce: Reason for removal In-Reply-To: <9cc4d0fe-51c6-441c-9fb1-e3174887393f@www.fastmail.com> References: <9cc4d0fe-51c6-441c-9fb1-e3174887393f@www.fastmail.com> Message-ID: <20220304200736.GX4508@localhost> On 04/03/22 19:37, Andrzej Telszewski put forth the proposition: > Hi, > I noticed that _network/rtl8821ce_ has been removed from master branch. > There is no info in the log why is it so. > Could you please explain? > Thank you! :-) Hi, I removed it because it failed to build when I tested it on 15.0. It looks like a header file was moved, but I'll try to make a patch for it. -- Dave From andrzej at telszewski.com Fri Mar 4 20:36:27 2022 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Fri, 4 Mar 2022 20:36:27 +0000 (UTC) Subject: [Slackbuilds-users] rtl8821ce: Reason for removal In-Reply-To: <20220304200736.GX4508@localhost> References: <9cc4d0fe-51c6-441c-9fb1-e3174887393f@www.fastmail.com> <20220304200736.GX4508@localhost> Message-ID: <7c3c328a-2879-4398-8745-0716a059d232@telszewski.com> Mar 4, 2022 21:07:44 Dave Woodfall : > I removed it because it failed to build when I tested it on 15.0. I wonder, is it a general rule in preparation for 15.0 to remove what does not build? I'm kind of concerned, because you didn't contact me about that. > It looks like a header file was moved, but I'll try to make a patch for > it. I have a report from a user that some recent commit from the upstream repo builds fine on 15.0. I'm not actively using this driver any more, so I cannot test it on real HW, but I surely can try building it. Would you like me to try it out and report back? Thank you for your effort! :-) From jebrhansen+SBo at gmail.com Fri Mar 4 20:37:06 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 4 Mar 2022 13:37:06 -0700 Subject: [Slackbuilds-users] Version Bump for HandBrake (1.5.1) Submitted to GitHub Message-ID: Klaatu, I took the liberty today to update HandBrake to v1.5.1 so it can compile on 15.0 and I added support for an optional dependency of onevpl (Intel's video processing library). onevpl did not already exist on SBo, so I created a SlackBuild for it. I submitted a PR on SBo's github if you'd like to review it. https://github.com/bassmadrigal/SBo-forked/pull/new/HandBrake I did not do this with the intention of taking over maintenance unless you no longer want to maintain it. Jeremy (aka bassmadrigal) -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Fri Mar 4 20:43:57 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 4 Mar 2022 20:43:57 +0000 Subject: [Slackbuilds-users] rtl8821ce: Reason for removal In-Reply-To: <20220304200736.GX4508@localhost> References: <9cc4d0fe-51c6-441c-9fb1-e3174887393f@www.fastmail.com> <20220304200736.GX4508@localhost> Message-ID: <20220304204357.GY4508@localhost> On 04/03/22 20:07, Dave Woodfall put forth the proposition: > On 04/03/22 19:37, > Andrzej Telszewski put forth the proposition: > > Hi, > > I noticed that _network/rtl8821ce_ has been removed from master branch. > > There is no info in the log why is it so. > > Could you please explain? > > Thank you! :-) > Hi, > I removed it because it failed to build when I tested it on 15.0. It > looks like a header file was moved, but I'll try to make a patch for > it. /tmp/SBo/rtl8821ce-20201006_fe97b50/core/rtw_br_ext.c:20:18: fatal error: net/ipx.h: No such file or directory 20 | #include however: find /usr/include -name ipx.h /usr/include/netipx/ipx.h and grep -wrs ipx.h /var/lib/pkgtools/packages/* /var/lib/pkgtools/packages/glibc-2.33-x86_64-5:usr/include/netipx/ipx.h but changing it also fails: sed -i "s,,," core/rtw_br_ext.c /tmp/SBo/rtl8821ce-20201006_fe97b50/core/rtw_br_ext.c:20:18: fatal error: netipx/ipx.h: No such file or directory 20 | #include -- Dave From dave at slackbuilds.org Fri Mar 4 20:47:03 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 4 Mar 2022 20:47:03 +0000 Subject: [Slackbuilds-users] rtl8821ce: Reason for removal In-Reply-To: <7c3c328a-2879-4398-8745-0716a059d232@telszewski.com> References: <9cc4d0fe-51c6-441c-9fb1-e3174887393f@www.fastmail.com> <20220304200736.GX4508@localhost> <7c3c328a-2879-4398-8745-0716a059d232@telszewski.com> Message-ID: <20220304204703.GZ4508@localhost> On 04/03/22 20:36, Andrzej Telszewski put forth the proposition: > Mar 4, 2022 21:07:44 Dave Woodfall : > > I removed it because it failed to build when I tested it on 15.0. > I wonder, is it a general rule in preparation for 15.0 to remove what does not build? Yes > I'm kind of concerned, because you didn't contact me about that. Unfortunately, it would take too long to contact someone every time. > I have a report from a user that some recent commit from the upstream repo builds fine on 15.0. > I'm not actively using this driver any more, so I cannot test it on real HW, but I surely can try building it. > Would you like me to try it out and report back? Please do. -- Dave From slackbuilds at schoepfer.info Fri Mar 4 21:03:43 2022 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 04 Mar 2022 22:03:43 +0100 Subject: [Slackbuilds-users] texworks, texlive-docs and texlive-extra Message-ID: <63943f29cfebfd9de6d16c8a82b81371@schoepfer.info> Hi, attached are an update to texworks, and small script fixes for texlive-docs und texlive-extra. Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: texworks.patch Type: text/x-diff Size: 4244 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: texlive-docs.patch Type: text/x-diff Size: 2666 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: texlive-extra.patch Type: text/x-diff Size: 9975 bytes Desc: not available URL: From jdashiel at panix.com Fri Mar 4 22:37:32 2022 From: jdashiel at panix.com (Jude DaShiell) Date: Fri, 4 Mar 2022 17:37:32 -0500 Subject: [Slackbuilds-users] corrected md5sum Message-ID: The upstream website didn't document an md5sum so I calculated that from the source file downloaded from the upstream website and updated files in bas.tgz accordingly. -------------- next part -------------- A non-text attachment was scrubbed... Name: bas.tgz Type: application/octet-stream Size: 7168 bytes Desc: URL: From duncan_roe at optusnet.com.au Fri Mar 4 22:37:48 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sat, 5 Mar 2022 09:37:48 +1100 Subject: [Slackbuilds-users] Please update your tqdm SlackBuild In-Reply-To: <20220304145538.794e84ac566c0eb48294c96f@laposte.net> References: <6P1ZSxeTSx30wxmwLYUfIurvLOOjcP0mGlvnwluH3DjoIKAI9lueOiJqZzpKVjHmmA4tfYGuz9MQs0W1BhL13lAGc5OhIXhWf9TVWkUKofk=@protonmail.com> <20220304145538.794e84ac566c0eb48294c96f@laposte.net> Message-ID: On Fri, Mar 04, 2022 at 02:55:38PM +0100, SlackBuilds wrote: > > > Hi Dionysis, > > > > > > Many thanks for that: I sent a pull request with the minumum necessary changes. > > > On a freshly installed 15.0 system, python is python3, so your SB only makes the > > > 3.9 packages. You might want to change `python` to `python2`, but I leave that > > > up to you. > > > > No, /usr/bin/python points to python2.7: [...] > > Looks like existing practice on SBo is split between "python setup.py" and python2 setup.py", with the majority being "python setup.py": > > > > $ git grep "python setup.py" | wc -l > > 662 > > $ git grep "python2 setup.py" | wc -l > > 298 > > $ git grep "python3 setup.py" | wc -l > > 671 > > > > > > Erich > > Looking at install scripts for slackware's python2 and python3, the symbolic link /usr/bin/python is for python2, whatever package you install first. And even if python2 is uninstalled, you won't have a /usr/bin/python executable. > > So python is python2, and python3 is always explicit. > > However, more and more slackbuilds are explicit for python2 also, which is a good thing, and should be the rule, at least whenever any given python2 package is updated for another good reason. > > - Yth. My bad - tqdm did install 2.7. Must have scrolled off the screen and I didn't scroll up to look. Cheers ... Duncan. From yalhcru at gmail.com Fri Mar 4 22:43:16 2022 From: yalhcru at gmail.com (B Watson) Date: Fri, 4 Mar 2022 17:43:16 -0500 Subject: [Slackbuilds-users] rtl8821ce: Reason for removal In-Reply-To: <20220304204703.GZ4508@localhost> References: <9cc4d0fe-51c6-441c-9fb1-e3174887393f@www.fastmail.com> <20220304200736.GX4508@localhost> <7c3c328a-2879-4398-8745-0716a059d232@telszewski.com> <20220304204703.GZ4508@localhost> Message-ID: On 3/4/22, Dave Woodfall wrote: > On 04/03/22 20:36, > Andrzej Telszewski put forth the proposition: > >> I have a report from a user that some recent commit from the upstream repo >> builds fine on 15.0. >> I'm not actively using this driver any more, so I cannot test it on real >> HW, but I surely can try building it. >> Would you like me to try it out and report back? > > Please do. Actually, I went ahead and re-added rtl8821ce (and rtl8188eu, removed at the same time), using the latest git. It builds correctly on 15.0, but I can't tell if it actually works because nothing I own has the hardware it's a driver for. If you (Andrzej, or anyone else who owns this hardware) want to test it on hardware, clone the SBo repo, then "git checkout urchlay", then run the SlackBuild from there... or if you wait a day or two, it'll get merged to git master (easier to deal with, if you want to use a tool like sbopkg). From willysr at slackbuilds.org Sat Mar 5 00:54:23 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Mar 2022 07:54:23 +0700 Subject: [Slackbuilds-users] texworks, texlive-docs and texlive-extra In-Reply-To: <63943f29cfebfd9de6d16c8a82b81371@schoepfer.info> References: <63943f29cfebfd9de6d16c8a82b81371@schoepfer.info> Message-ID: <750cb71c-19ab-8815-7194-e46ed0ab087c@slackbuilds.org> > attached are an update to texworks, and small script fixes for > texlive-docs und texlive-extra. merged -- 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 willysr at slackbuilds.org Sat Mar 5 00:59:37 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Mar 2022 07:59:37 +0700 Subject: [Slackbuilds-users] corrected md5sum In-Reply-To: References: Message-ID: > The upstream website didn't document an md5sum so I calculated that from > the source file downloaded from the upstream website and updated files in > bas.tgz accordingly. This changes revert our work please make necessary changes only, like the VERSION and MD5SUM and don't change other things that was already placed there according to the new template -- 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 jdashiel at panix.com Sat Mar 5 01:38:50 2022 From: jdashiel at panix.com (Jude DaShiell) Date: Fri, 4 Mar 2022 20:38:50 -0500 Subject: [Slackbuilds-users] bas necessary changes Message-ID: No license text in original bas.tgz added, Version updated, md5sum updated. I hope this clears your reversion. -------------- next part -------------- A non-text attachment was scrubbed... Name: bas.tgz Type: application/octet-stream Size: 10240 bytes Desc: URL: From slackbuilds at schoepfer.info Sat Mar 5 10:39:54 2022 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 05 Mar 2022 11:39:54 +0100 Subject: [Slackbuilds-users] frogatto build fix Message-ID: <95a1b4e492c59f431e49ef0bf55def0e@schoepfer.info> Hi, not my buildscript, attached patch fixes building on 15.0, so frogatto may be removed from https://slackbuilds.org/FAILED-15.0 Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: frogatto.patch Type: text/x-diff Size: 9027 bytes Desc: not available URL: From matteo.bernardini at gmail.com Sat Mar 5 12:06:04 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 5 Mar 2022 13:06:04 +0100 Subject: [Slackbuilds-users] frogatto build fix In-Reply-To: <95a1b4e492c59f431e49ef0bf55def0e@schoepfer.info> References: <95a1b4e492c59f431e49ef0bf55def0e@schoepfer.info> Message-ID: thanks, pushed! Il giorno sab 5 mar 2022 alle ore 11:40 Franzen via SlackBuilds-users ha scritto: > > Hi, > > not my buildscript, attached patch fixes building on 15.0, > so frogatto may be removed from https://slackbuilds.org/FAILED-15.0 > > 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/ > From didier at slint.fr Sat Mar 5 14:30:19 2022 From: didier at slint.fr (Didier Spaier) Date: Sat, 5 Mar 2022 15:30:19 +0100 Subject: [Slackbuilds-users] aqemu Message-ID: <05695592-800f-48ea-e40b-473c2acd41a4@slint.fr> Hi, I could build aqemu on Slackware 15 borrowing this sed comand to Arch: sed -i 's|#include |#include \n#include |' src/docopt/docopt_value.h This helps with GCC>=10 Also following Arch I built with this source tarball: https://codeload.github.com/TBK/aqemu/tar.gz/refs/tags/v0.9.4 The GUI per se works, I still have to build Qemu to check in contexet. Didier From willysr at slackbuilds.org Sat Mar 5 16:00:48 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Mar 2022 23:00:48 +0700 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress Message-ID: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> Hi guys we are still trimming down all the remaining scripts to check against Slackware 15.0 and hopefully we will see 15.0 repository soon. The list can be seen here: https://slackbuilds.org/FAILED-15.0 You can help by confirming whether a certain scripts does build correctly against Slackware 15.0 (full installation and clean environment please). Let us know in the mailing list when you have confirmed. I have also pushed new templates for 15.0 SlackBuilds to git and also to the website at https://slackbuilds.org/templates/ please download and use them for future new submission. Thanks -- 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 ozan.turkyilmaz at gmail.com Sat Mar 5 16:26:45 2022 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 5 Mar 2022 19:26:45 +0300 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> Message-ID: Hello, I started tinkering kodi now. New version looks like will work with 15.0. BUild system is now cmake. I'll keep you posted. I tinkered wine-nine-standalone. I don't think it will work without serious work. Regards, Ozan Willy Sudiarto Raharjo , 5 Mar 2022 Cmt, 19:01 tarihinde ?unu yazd?: > Hi guys > > we are still trimming down all the remaining scripts to check against > Slackware 15.0 and hopefully we will see 15.0 repository soon. > > The list can be seen here: https://slackbuilds.org/FAILED-15.0 > You can help by confirming whether a certain scripts does build > correctly against Slackware 15.0 (full installation and clean > environment please). Let us know in the mailing list when you have > confirmed. > > I have also pushed new templates for 15.0 SlackBuilds to git and also to > the website at https://slackbuilds.org/templates/ > > please download and use them for future new submission. > > Thanks > > > -- > 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 matteo.bernardini at gmail.com Sat Mar 5 16:28:48 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 5 Mar 2022 17:28:48 +0100 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> Message-ID: Hi Ozan, Jeremy already sent an update to 19.4 for kodi, it's on git https://git.slackbuilds.org/slackbuilds/commit/?id=2aaa8213472023ab08488efb41181864c8d106ff Matteo Il giorno sab 5 mar 2022 alle ore 17:26 Ozan T?rky?lmaz ha scritto: > > Hello, > > I started tinkering kodi now. New version looks like will work with 15.0. BUild system is now cmake. > I'll keep you posted. > I tinkered wine-nine-standalone. I don't think it will work without serious work. > > Regards, > Ozan > > Willy Sudiarto Raharjo , 5 Mar 2022 Cmt, 19:01 tarihinde ?unu yazd?: >> >> Hi guys >> >> we are still trimming down all the remaining scripts to check against >> Slackware 15.0 and hopefully we will see 15.0 repository soon. >> >> The list can be seen here: https://slackbuilds.org/FAILED-15.0 >> You can help by confirming whether a certain scripts does build >> correctly against Slackware 15.0 (full installation and clean >> environment please). Let us know in the mailing list when you have >> confirmed. >> >> I have also pushed new templates for 15.0 SlackBuilds to git and also to >> the website at https://slackbuilds.org/templates/ >> >> please download and use them for future new submission. >> >> Thanks >> >> >> -- >> Willy Sudiarto Raharjo >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From ozan.turkyilmaz at gmail.com Sat Mar 5 16:33:05 2022 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 5 Mar 2022 19:33:05 +0300 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> Message-ID: He beat me to it. ALso he had the same annoyances. Never fun of cmake. Matteo Bernardini , 5 Mar 2022 Cmt, 19:29 tarihinde ?unu yazd?: > Hi Ozan, > > Jeremy already sent an update to 19.4 for kodi, it's on git > > > https://git.slackbuilds.org/slackbuilds/commit/?id=2aaa8213472023ab08488efb41181864c8d106ff > > Matteo > > Il giorno sab 5 mar 2022 alle ore 17:26 Ozan T?rky?lmaz > ha scritto: > > > > Hello, > > > > I started tinkering kodi now. New version looks like will work with > 15.0. BUild system is now cmake. > > I'll keep you posted. > > I tinkered wine-nine-standalone. I don't think it will work without > serious work. > > > > Regards, > > Ozan > > > > Willy Sudiarto Raharjo , 5 Mar 2022 Cmt, 19:01 > tarihinde ?unu yazd?: > >> > >> Hi guys > >> > >> we are still trimming down all the remaining scripts to check against > >> Slackware 15.0 and hopefully we will see 15.0 repository soon. > >> > >> The list can be seen here: https://slackbuilds.org/FAILED-15.0 > >> You can help by confirming whether a certain scripts does build > >> correctly against Slackware 15.0 (full installation and clean > >> environment please). Let us know in the mailing list when you have > >> confirmed. > >> > >> I have also pushed new templates for 15.0 SlackBuilds to git and also to > >> the website at https://slackbuilds.org/templates/ > >> > >> please download and use them for future new submission. > >> > >> Thanks > >> > >> > >> -- > >> Willy Sudiarto Raharjo > >> _______________________________________________ > >> SlackBuilds-users mailing list > >> SlackBuilds-users at slackbuilds.org > >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > >> FAQ - https://slackbuilds.org/faq/ > >> > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > _______________________________________________ > 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 Sat Mar 5 17:07:11 2022 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sat, 5 Mar 2022 17:07:11 +0000 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> Message-ID: Hi Willie, I noticed that pdfpc is in the failed list. I have no problem building it here, can someone let me know what error they are getting? Cheers Greg On Sat, 5 Mar 2022 at 16:33, Ozan T?rky?lmaz wrote: > He beat me to it. ALso he had the same annoyances. Never fun of cmake. > > > Matteo Bernardini , 5 Mar 2022 Cmt, 19:29 > tarihinde ?unu yazd?: > >> Hi Ozan, >> >> Jeremy already sent an update to 19.4 for kodi, it's on git >> >> >> https://git.slackbuilds.org/slackbuilds/commit/?id=2aaa8213472023ab08488efb41181864c8d106ff >> >> Matteo >> >> Il giorno sab 5 mar 2022 alle ore 17:26 Ozan T?rky?lmaz >> ha scritto: >> > >> > Hello, >> > >> > I started tinkering kodi now. New version looks like will work with >> 15.0. BUild system is now cmake. >> > I'll keep you posted. >> > I tinkered wine-nine-standalone. I don't think it will work without >> serious work. >> > >> > Regards, >> > Ozan >> > >> > Willy Sudiarto Raharjo , 5 Mar 2022 Cmt, >> 19:01 tarihinde ?unu yazd?: >> >> >> >> Hi guys >> >> >> >> we are still trimming down all the remaining scripts to check against >> >> Slackware 15.0 and hopefully we will see 15.0 repository soon. >> >> >> >> The list can be seen here: https://slackbuilds.org/FAILED-15.0 >> >> You can help by confirming whether a certain scripts does build >> >> correctly against Slackware 15.0 (full installation and clean >> >> environment please). Let us know in the mailing list when you have >> >> confirmed. >> >> >> >> I have also pushed new templates for 15.0 SlackBuilds to git and also >> to >> >> the website at https://slackbuilds.org/templates/ >> >> >> >> please download and use them for future new submission. >> >> >> >> Thanks >> >> >> >> >> >> -- >> >> Willy Sudiarto Raharjo >> >> _______________________________________________ >> >> SlackBuilds-users mailing list >> >> SlackBuilds-users at slackbuilds.org >> >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> >> FAQ - https://slackbuilds.org/faq/ >> >> >> > _______________________________________________ >> > SlackBuilds-users mailing list >> > SlackBuilds-users at slackbuilds.org >> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> > FAQ - https://slackbuilds.org/faq/ >> > >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lramos.prof at yahoo.com.br Sat Mar 5 18:01:10 2022 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Sat, 5 Mar 2022 15:01:10 -0300 Subject: [Slackbuilds-users] Pitivi not running References: Message-ID: Hello, today I tried to upgrade Pitivi version to the last one, and it turns out that the final binary (in fact, a Python3 script) didn't run, showing signs of a missing matplotlib. Digging a little bit, one found that the problem was on two dependencies, kiwisolver and cycler, which didn't have the Python3 version built. I could solve it including in these packages a command to build Python3 bits along the Python2 ones, like that: python setup.py install --root $PKG [+] python3 setup.py install --root $PKG and rebuilding kiwisource and cycler. Conversely to what the error message points, it seems there is no need to install the whole matplotlib. By the way, the current matplotlib SBo lacks Python3 support. Hope it helps, Luiz Ramos lramos dot prof at yahoo dot com dot br Sao Paulo - Brazil From artourter at gmail.com Sat Mar 5 18:03:18 2022 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sat, 5 Mar 2022 18:03:18 +0000 Subject: [Slackbuilds-users] Pitivi not running In-Reply-To: References: Message-ID: there is a separate package for the python3 version of matplotlib: development/python3-matplotlib On Sat, 5 Mar 2022 at 18:00, Luiz Carlos Ramos via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hello, > > today I tried to upgrade Pitivi version to the last one, and it turns > out that the final binary (in fact, a Python3 script) didn't run, > showing signs of a missing matplotlib. > > Digging a little bit, one found that the problem was on two > dependencies, kiwisolver and cycler, which didn't have the Python3 > version built. > > I could solve it including in these packages a command to build Python3 > bits along the Python2 ones, like that: > > python setup.py install --root $PKG > [+] python3 setup.py install --root $PKG > > and rebuilding kiwisource and cycler. > > Conversely to what the error message points, it seems there is no need > to install the whole matplotlib. By the way, the current matplotlib SBo > lacks Python3 support. > > Hope it helps, > > Luiz Ramos > lramos dot prof at yahoo dot com dot br > Sao 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 jebrhansen+SBo at gmail.com Sat Mar 5 18:59:04 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 5 Mar 2022 11:59:04 -0700 Subject: [Slackbuilds-users] Pitivi not running In-Reply-To: References: Message-ID: On Sat, Mar 5, 2022, 11:00 AM Luiz Carlos Ramos via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hello, > > today I tried to upgrade Pitivi version to the last one, and it turns > out that the final binary (in fact, a Python3 script) didn't run, > showing signs of a missing matplotlib. > > Digging a little bit, one found that the problem was on two > dependencies, kiwisolver and cycler, which didn't have the Python3 > version built. > > I could solve it including in these packages a command to build Python3 > bits along the Python2 ones, like that: > > python setup.py install --root $PKG > [+] python3 setup.py install --root $PKG > > and rebuilding kiwisource and cycler. > > Conversely to what the error message points, it seems there is no need > to install the whole matplotlib. By the way, the current matplotlib SBo > lacks Python3 support. > I'm the maintainer of pitivi. It relies on python3-matplotlib, not the regular matplotlib on SBo. It should build properly with the dependencies listed on REQUIRES line in the pitivi.info. I tested it on a clean VM using sqg and sbopkg before I submitted it. If I missed something, let me know. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Sat Mar 5 21:51:49 2022 From: yalhcru at gmail.com (B Watson) Date: Sat, 5 Mar 2022 16:51:49 -0500 Subject: [Slackbuilds-users] Pitivi not running In-Reply-To: References: Message-ID: On 3/5/22, Luiz Carlos Ramos via SlackBuilds-users wrote: > > python setup.py install --root $PKG > [+] python3 setup.py install --root $PKG > > and rebuilding kiwisource and cycler. > > Conversely to what the error message points, it seems there is no need > to install the whole matplotlib. By the way, the current matplotlib SBo > lacks Python3 support. Thanks for that, it'll help a lot. From yalhcru at gmail.com Sat Mar 5 21:59:03 2022 From: yalhcru at gmail.com (B Watson) Date: Sat, 5 Mar 2022 16:59:03 -0500 Subject: [Slackbuilds-users] Pitivi not running In-Reply-To: References: Message-ID: On 3/5/22, B Watson wrote: > > Thanks for that, it'll help a lot. > I spake too soone: there's already python3- versions of kiwisolver and cycler. From jebrhansen+SBo at gmail.com Sat Mar 5 22:06:49 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 5 Mar 2022 15:06:49 -0700 Subject: [Slackbuilds-users] Pitivi not running In-Reply-To: References: Message-ID: On Sat, Mar 5, 2022 at 2:59 PM B Watson wrote: > On 3/5/22, B Watson wrote: > > > > Thanks for that, it'll help a lot. > > > > I spake too soone: there's already python3- versions of kiwisolver > and cycler. > > It should already be good. If you follow the dependencies of pitivi, you get python3 versions of the right dependencies. Here's the output from sqg python3-tornado python3-kiwisolver python3-cycler pytz python3-dateutil numpy3 python3-matplotlib libpeas gst-python gst-plugins-bad gst-editing-services gsound gcab appstream-glib pitivi I'm not sure why Luis installed the python2 versions, unless they didn't pay close enough attention to the dependencies and just installed "matplotlib" instead of "python3-matplotlib". Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From lenardrspencer at gmail.com Sat Mar 5 22:19:47 2022 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Sat, 5 Mar 2022 17:19:47 -0500 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> Message-ID: I have working scripts for openjdk{6,7,8} on my web page. I know openjdk6 has been dropped, but it is there. http://www.lenardspencer.net/linux/slackbuilds On Sat, Mar 5, 2022, 11:01 Willy Sudiarto Raharjo wrote: > Hi guys > > we are still trimming down all the remaining scripts to check against > Slackware 15.0 and hopefully we will see 15.0 repository soon. > > The list can be seen here: https://slackbuilds.org/FAILED-15.0 > You can help by confirming whether a certain scripts does build > correctly against Slackware 15.0 (full installation and clean > environment please). Let us know in the mailing list when you have > confirmed. > > I have also pushed new templates for 15.0 SlackBuilds to git and also to > the website at https://slackbuilds.org/templates/ > > please download and use them for future new submission. > > Thanks > > > -- > 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 kfritz at sonic.net Sat Mar 5 22:29:15 2022 From: kfritz at sonic.net (Kent Fritz) Date: Sat, 5 Mar 2022 14:29:15 -0800 Subject: [Slackbuilds-users] libvirt failing for me on 15.0 Message-ID: <1e55d755-cc02-db68-dc07-3e51ecb01d62@sonic.net> It's not on the list of failing builds, so does anybody know what this error means or how to fix? [974/1281] Generating 404.html with a custom command (wrapped by meson to capture output) FAILED: docs/404.html /usr/bin/meson --internal exe --capture docs/404.html -- /usr/bin/xsltproc --stringparam pagesrc docs/404.html.in --stringparam builddir /tmp/SBo/libvirt-8.0.0/build --stringparam timestamp 'Sat Mar? 5 22:15:01 2022 UTC' --nonet ../docs/site.xsl ../docs/404.html.in --- stderr --- runtime error: file ../docs/page.xsl line 223 element element xsl:element: The effective name '' is not a valid QName. no result for ../docs/404.html.in Thanks, Kent. From sbo at linuxgalaxy.org Sat Mar 5 23:08:37 2022 From: sbo at linuxgalaxy.org (Slackbuilds) Date: Sat, 05 Mar 2022 23:08:37 +0000 Subject: [Slackbuilds-users] aqemu In-Reply-To: <05695592-800f-48ea-e40b-473c2acd41a4@slint.fr> References: <05695592-800f-48ea-e40b-473c2acd41a4@slint.fr> Message-ID: <0e448553-0e29-1c97-ad6e-a102d6f3d405@linuxgalaxy.org> On 3/5/22 06:30, Didier Spaier wrote: > Hi, > I could build aqemu on Slackware 15 borrowing this sed comand to Arch: > sed -i 's|#include |#include \n#include |' > src/docopt/docopt_value.h > This helps with GCC>=10 > > Also following Arch I built with this source tarball: > https://codeload.github.com/TBK/aqemu/tar.gz/refs/tags/v0.9.4 > > The GUI per se works, I still have to build Qemu to check in contexet. > Not really worth resurrecting aqemu (vintage 2016)? Qemu has had a large number of option changes as well as deprecated features. These changes make aqemu pretty much useless, unless you drop to qemu-2.4.x or qemu-2.6.x There was some movement a while back and a move to github when the original authors dropped out and it was taken over. -kb From lramos.prof at yahoo.com.br Sun Mar 6 00:39:10 2022 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Sat, 5 Mar 2022 21:39:10 -0300 Subject: [Slackbuilds-users] Pitivi not running In-Reply-To: References: Message-ID: Jeremy, yes, confirmed. I checked now and much likely I was in a wrong version, at least regarding the .info file. This can explain what happened here. Thank you all for the timely replies! Luiz On Sat, Mar 05, 2022 at 03:06:49PM -0700, Jeremy Hansen wrote: > On Sat, Mar 5, 2022 at 2:59 PM B Watson wrote: > > > On 3/5/22, B Watson wrote: > > > > > > Thanks for that, it'll help a lot. > > > > > > > I spake too soone: there's already python3- versions of kiwisolver > > and cycler. > > > > > It should already be good. If you follow the dependencies of pitivi, you > get python3 versions of the right dependencies. Here's the output from sqg > > python3-tornado > python3-kiwisolver > python3-cycler > pytz > python3-dateutil > numpy3 > python3-matplotlib > libpeas > gst-python > gst-plugins-bad > gst-editing-services > gsound > gcab > appstream-glib > pitivi > > I'm not sure why Luis installed the python2 versions, unless they didn't > pay close enough attention to the dependencies and just > installed "matplotlib" instead of "python3-matplotlib". > > 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/ > From sborg63 at disroot.org Sun Mar 6 01:06:56 2022 From: sborg63 at disroot.org (sborg63) Date: Sun, 6 Mar 2022 01:06:56 +0000 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: References: Message-ID: <20220306010656.2fa02afd@knotsUL> Hi Willy, According to the new templates, .la files are not included in the package to be built as follows: # Don't ship .la files: rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la But some packages (for example geany) put .la files in subfolders too, say as /usr/lib${LIBDIRSUFFIX}/$PRGNAM/*.la Are maintainers supposed to make sure that these are omitted as well? Cheers, Rob On Sat, 05 Mar 2022 16:33:14 +0000 slackbuilds-users-request at slackbuilds.org wrote: > I have also pushed new templates for 15.0 SlackBuilds to git and also > to the website at https://slackbuilds.org/templates/ > > please download and use them for future new submission. > > Thanks > > > -- > Willy Sudiarto Raharjo From willysr at slackbuilds.org Sun Mar 6 01:35:18 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 6 Mar 2022 08:35:18 +0700 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> Message-ID: <73b2eb7f-64d3-289c-af50-dd1768a3484f@slackbuilds.org> > I noticed that pdfpc is in the failed list. I have no problem building it > here, can someone let me know what error they are getting? It could be false positive since that list is generated by CI system and it was designed with some restrictions such as no network access during build. If a script is downloading something in the middle of a build process and it has no internet access, it will fail eventually -- 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 willysr at slackbuilds.org Sun Mar 6 01:36:09 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 6 Mar 2022 08:36:09 +0700 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: <20220306010656.2fa02afd@knotsUL> References: <20220306010656.2fa02afd@knotsUL> Message-ID: <1b6e2468-34c2-2db9-8dfb-23c60fc056ef@slackbuilds.org> > According to the new templates, .la files are not included > in the package to be built as follows: > > # Don't ship .la files: > rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la > > > But some packages (for example geany) put .la files in subfolders too, > say as > /usr/lib${LIBDIRSUFFIX}/$PRGNAM/*.la > > Are maintainers supposed to make sure that these are omitted as > well? Yes please -- 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 willysr at slackbuilds.org Sun Mar 6 02:09:57 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 6 Mar 2022 09:09:57 +0700 Subject: [Slackbuilds-users] libvirt failing for me on 15.0 In-Reply-To: <1e55d755-cc02-db68-dc07-3e51ecb01d62@sonic.net> References: <1e55d755-cc02-db68-dc07-3e51ecb01d62@sonic.net> Message-ID: <7c9c7623-d869-ad41-8eeb-942d996a7622@slackbuilds.org> > It's not on the list of failing builds, so does anybody know what this > error means or how to fix? > > [974/1281] Generating 404.html with a custom command (wrapped by meson > to capture output) > FAILED: docs/404.html > /usr/bin/meson --internal exe --capture docs/404.html -- > /usr/bin/xsltproc --stringparam pagesrc docs/404.html.in --stringparam > builddir /tmp/SBo/libvirt-8.0.0/build --stringparam timestamp 'Sat Mar? > 5 22:15:01 2022 UTC' --nonet ../docs/site.xsl ../docs/404.html.in > --- stderr --- > runtime error: file ../docs/page.xsl line 223 element element > xsl:element: The effective name '' is not a valid QName. > no result for ../docs/404.html.in i'm testing latest release and some upstream commit to fix segfaults. Once it's done it will be pushed to my branch -- 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 erich.public at protonmail.com Sun Mar 6 02:24:11 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Sun, 06 Mar 2022 02:24:11 +0000 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: <1b6e2468-34c2-2db9-8dfb-23c60fc056ef@slackbuilds.org> References: <20220306010656.2fa02afd@knotsUL> <1b6e2468-34c2-2db9-8dfb-23c60fc056ef@slackbuilds.org> Message-ID: <2IKLFIfzn9kWo2-VGWAJgMwsaN5M6xF1EYcdkkFz1csvwus-ah16Ba12DfDRX5tMEfIuI3xPbaOsa3LjtmGFEV_qUgxrp8CXdqmlqo-N3M0=@protonmail.com> ------- Original Message ------- On Saturday, March 5th, 2022 at 7:36 PM, Willy Sudiarto Raharjo wrote: > > According to the new templates, .la files are not included > > in the package to be built as follows: > > > > # Don't ship .la files: > > rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la > > > > But some packages (for example geany) put .la files in subfolders too, > > say as > > > > /usr/lib${LIBDIRSUFFIX}/$PRGNAM/*.la > > > > Are maintainers supposed to make sure that these are omitted as > > well? > > Yes please > > -- > > Willy Sudiarto Raharjo > Doesn't it depend? From the Slackware ChangeLog entry from Thu Apr 19 2018: > The .la files that are outside of > the LD_LIBRARY_PATH were not removed (and shouldn't be) - those ones are > often used by the lt_dlopen() function to load plugins and removing those > ones can break things. But those ones don't cause problems... they aren't > likely to try to infect .la files produced by other packages. And on 64-bit Slackware 15.0 the contents of /etc/ld.so.conf are: include /etc/ld.so.conf.d/*.conf /lib64 /usr/lib64 /usr/local/lib64 /usr/x86_64-slackware-linux/lib64 So if I understand correctly there should be no .la files in those directories. But /usr/lib${LIBDIRSUFFIX}/$PRGNAM/*.la may very well be necessary for a program to operate correctly, and won't adversely affect the system. In fact several stock Slackware packages contain these files (do a "find /usr/lib64 -name "*.la" to see them). On the other hand, there are a few offending SBo packages in /usr/lib64 on my system (apologies if any of these have been fixed recently): # ls -l /usr/lib64/*.la -rwxr-xr-x 1 root root 1172 Feb 16 08:08 /usr/lib64/libflatpak.la* (flatpak-1.10.2-x86_64-2_SBo) -rwxr-xr-x 1 root root 980 Mar 3 12:10 /usr/lib64/libgeotiff.la* (libgeotiff-1.5.1-x86_64-1_SBo) -rwxr-xr-x 1 root root 910 Feb 7 10:46 /usr/lib64/libglpk.la* (glpk-4.61-x86_64-1_SBo) -rwxr-xr-x 1 root root 916 Feb 7 12:16 /usr/lib64/liblaszip.la* (laszip-2.2.0-x86_64-1_SBo) Erich From chris.willing at linux.com Sun Mar 6 03:29:26 2022 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 6 Mar 2022 13:29:26 +1000 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> Message-ID: <79cecbfa-2b8c-6af5-e542-e6d5f639b622@linux.com> On 6/3/22 02:00, Willy Sudiarto Raharjo wrote: > > The list can be seen here: https://slackbuilds.org/FAILED-15.0 > You can help by confirming whether a certain scripts does build > correctly against Slackware 15.0 (full installation and clean > environment please). Let us know in the mailing list when you have > confirmed. > I've just updated system/pixma to build on 15.0 and pushed to my updates branch so it can be removed from the FAILED-15.0 list. That done, I don't have a suitable printer to test it with so if anyone else would like to take over maintainership of this SlackBuild, they're more than welcome. Since the source code is unlikely to change (it's unchanged since 2013) and only rare updates expected to SL15.0 itself, I think the maintenance load will be very low. Any takers? chris From willysr at slackbuilds.org Sun Mar 6 03:54:31 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 6 Mar 2022 10:54:31 +0700 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: <79cecbfa-2b8c-6af5-e542-e6d5f639b622@linux.com> References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> <79cecbfa-2b8c-6af5-e542-e6d5f639b622@linux.com> Message-ID: > I've just updated system/pixma to build on 15.0 and pushed to my updates > branch so it can be removed from the FAILED-15.0 list. Done thanks -- 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 duncan_roe at optusnet.com.au Sun Mar 6 05:45:14 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sun, 6 Mar 2022 16:45:14 +1100 Subject: [Slackbuilds-users] Please update your zopfli SlackBuild In-Reply-To: References: Message-ID: Hi again Oleg, On Wed, Mar 02, 2022 at 12:15:26PM +1100, Duncan Roe wrote: > Hi Oleg, > > zopfli is now a Python Package on https://pypi.org/. [...] Sorry for the noise, please ignore this request. Your SB builds /usr/bin/zopfli, the PyPI package does not. I will make a python3-zopfli package Type1_to_OTF. Cheers ... Duncan. From matteo.bernardini at gmail.com Sun Mar 6 08:04:19 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 6 Mar 2022 09:04:19 +0100 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: <2IKLFIfzn9kWo2-VGWAJgMwsaN5M6xF1EYcdkkFz1csvwus-ah16Ba12DfDRX5tMEfIuI3xPbaOsa3LjtmGFEV_qUgxrp8CXdqmlqo-N3M0=@protonmail.com> References: <20220306010656.2fa02afd@knotsUL> <1b6e2468-34c2-2db9-8dfb-23c60fc056ef@slackbuilds.org> <2IKLFIfzn9kWo2-VGWAJgMwsaN5M6xF1EYcdkkFz1csvwus-ah16Ba12DfDRX5tMEfIuI3xPbaOsa3LjtmGFEV_qUgxrp8CXdqmlqo-N3M0=@protonmail.com> Message-ID: I agree with Erich considerations: just follow Pat's instructions and don't remove *.la files outside of LD_LIBRARY_PATH. Matteo Il giorno dom 6 mar 2022 alle ore 03:24 Erich Ritz via SlackBuilds-users ha scritto: > > ------- Original Message ------- > > On Saturday, March 5th, 2022 at 7:36 PM, Willy Sudiarto Raharjo wrote: > > > > According to the new templates, .la files are not included > > > in the package to be built as follows: > > > > > > # Don't ship .la files: > > > rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la > > > > > > But some packages (for example geany) put .la files in subfolders too, > > > say as > > > > > > /usr/lib${LIBDIRSUFFIX}/$PRGNAM/*.la > > > > > > Are maintainers supposed to make sure that these are omitted as > > > well? > > > > Yes please > > > > -- > > > > Willy Sudiarto Raharjo > > > > Doesn't it depend? From the Slackware ChangeLog entry from Thu Apr 19 2018: > > > The .la files that are outside of > > the LD_LIBRARY_PATH were not removed (and shouldn't be) - those ones are > > often used by the lt_dlopen() function to load plugins and removing those > > ones can break things. But those ones don't cause problems... they aren't > > likely to try to infect .la files produced by other packages. > > And on 64-bit Slackware 15.0 the contents of /etc/ld.so.conf are: > > include /etc/ld.so.conf.d/*.conf > /lib64 > /usr/lib64 > /usr/local/lib64 > /usr/x86_64-slackware-linux/lib64 > > So if I understand correctly there should be no .la files in those directories. But /usr/lib${LIBDIRSUFFIX}/$PRGNAM/*.la may very well be necessary for a program to operate correctly, and won't adversely affect the system. In fact several stock Slackware packages contain these files (do a "find /usr/lib64 -name "*.la" to see them). > > On the other hand, there are a few offending SBo packages in /usr/lib64 on my system (apologies if any of these have been fixed recently): > > # ls -l /usr/lib64/*.la > -rwxr-xr-x 1 root root 1172 Feb 16 08:08 /usr/lib64/libflatpak.la* (flatpak-1.10.2-x86_64-2_SBo) > -rwxr-xr-x 1 root root 980 Mar 3 12:10 /usr/lib64/libgeotiff.la* (libgeotiff-1.5.1-x86_64-1_SBo) > -rwxr-xr-x 1 root root 910 Feb 7 10:46 /usr/lib64/libglpk.la* (glpk-4.61-x86_64-1_SBo) > -rwxr-xr-x 1 root root 916 Feb 7 12:16 /usr/lib64/liblaszip.la* (laszip-2.2.0-x86_64-1_SBo) > > 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/ > From andrew.clemons at gmail.com Sun Mar 6 08:57:57 2022 From: andrew.clemons at gmail.com (Andrew Clemons) Date: Sun, 6 Mar 2022 21:57:57 +1300 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> Message-ID: <5cdac7f3-d540-8795-b54d-0be622e3a016@gmail.com> Hi Lenard, On 6/03/22 11:19, Lenard Spencer wrote: > I have working scripts for openjdk{6,7,8} on my web page.? I know > openjdk6 has been dropped, but it is there. > http://www.lenardspencer.net/linux/slackbuilds > Thanks for the link. I've pulled these down and tested openjdk7 as a start. It works fine, but does need network access to build (bootstrap compiler?). It would be nice if that could be avoided. I'm assuming you are keen to maintain these? Thanks, Andrew From slackbuilds at schoepfer.info Sun Mar 6 09:50:23 2022 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 06 Mar 2022 10:50:23 +0100 Subject: [Slackbuilds-users] glob2 build fix Message-ID: <772f38aa423387ad841534794b3f8020@schoepfer.info> Hi, not my buildscript, fix to make glob2 build on 15.0 attached. Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: glob2.patch Type: text/x-diff Size: 15361 bytes Desc: not available URL: From artourter at gmail.com Sun Mar 6 11:33:37 2022 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sun, 6 Mar 2022 11:33:37 +0000 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: <73b2eb7f-64d3-289c-af50-dd1768a3484f@slackbuilds.org> References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> <73b2eb7f-64d3-289c-af50-dd1768a3484f@slackbuilds.org> Message-ID: Hi Willie, Thanks for the explanation. I have just checked and the build script does download anything. There are a few warnings at build time but otherwise nothing out of the ordinary. I attach the log file where I built pdfpc and all its dependencies. Cheers Greg On Sun, 6 Mar 2022 at 01:35, Willy Sudiarto Raharjo wrote: > > I noticed that pdfpc is in the failed list. I have no problem building it > > here, can someone let me know what error they are getting? > > It could be false positive since that list is generated by CI system and > it was designed with some restrictions such as no network access during > build. If a script is downloading something in the middle of a build > process and it has no internet access, it will fail eventually > > > > -- > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: pdfpc_build.log.gz Type: application/gzip Size: 3740 bytes Desc: not available URL: From dwhisman245 at gmail.com Sun Mar 6 13:48:44 2022 From: dwhisman245 at gmail.com (Dan Whisman) Date: Sun, 6 Mar 2022 08:48:44 -0500 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: References: Message-ID: <0696c282-f96d-0071-4062-894cd8844e9c@gmail.com> I was able to build CubicSDR 0.2.7 just fine with the repo as-is, but it needed SoapySDR 0.8.1 which is not in master. I have attached a patch (which I also emailed to the maintainer). It bumps the version, adds Python3 support, and fixes the man page directory. With the upgraded SoapySDR, I was able to successfully test CubicSDR by listening to a local FM station. I did use newer versions of SoapySDRPlay and SDRPlay packages and I also emailed patches to the maintainer. Best, Dan Whisman On 3/5/22 11:33, slackbuilds-users-request at slackbuilds.org wrote: > Date: Sat, 5 Mar 2022 23:00:48 +0700 > From: Willy Sudiarto Raharjo > To: "SlackBuilds.org Users List" > Subject: [Slackbuilds-users] New Templates and 15.0 Repository > Progress > Message-ID:<28eebab4-9e99-cb6e-93f7-6ca236a4d765 at slackbuilds.org> > Content-Type: text/plain; charset="utf-8" > > Hi guys > > we are still trimming down all the remaining scripts to check against > Slackware 15.0 and hopefully we will see 15.0 repository soon. > > The list can be seen here:https://slackbuilds.org/FAILED-15.0 > You can help by confirming whether a certain scripts does build > correctly against Slackware 15.0 (full installation and clean > environment please). Let us know in the mailing list when you have > confirmed. > > I have also pushed new templates for 15.0 SlackBuilds to git and also to > the website athttps://slackbuilds.org/templates/ > > please download and use them for future new submission. > > Thanks > > > -- 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: > > -------------- next part -------------- A non-text attachment was scrubbed... Name: SoapySDR-0.8.1.patch Type: text/x-patch Size: 1914 bytes Desc: not available URL: From chas at chasmo.org Sun Mar 6 16:21:21 2022 From: chas at chasmo.org (Charles Polisher) Date: Sun, 6 Mar 2022 08:21:21 -0800 Subject: [Slackbuilds-users] libvirt failing for me on 15.0 In-Reply-To: <7c9c7623-d869-ad41-8eeb-942d996a7622@slackbuilds.org> References: <1e55d755-cc02-db68-dc07-3e51ecb01d62@sonic.net> <7c9c7623-d869-ad41-8eeb-942d996a7622@slackbuilds.org> Message-ID: On 3/5/22 18:09, Willy Sudiarto Raharjo wrote: >> It's not on the list of failing builds, so does anybody know what this >> error means or how to fix? >> >> [974/1281] Generating 404.html with a custom command (wrapped by meson >> to capture output) >> FAILED: docs/404.html >> /usr/bin/meson --internal exe --capture docs/404.html -- >> /usr/bin/xsltproc --stringparam pagesrc docs/404.html.in --stringparam >> builddir /tmp/SBo/libvirt-8.0.0/build --stringparam timestamp 'Sat Mar >> 5 22:15:01 2022 UTC' --nonet ../docs/site.xsl ../docs/404.html.in >> --- stderr --- >> runtime error: file ../docs/page.xsl line 223 element element >> xsl:element: The effective name '' is not a valid QName. >> no result for ../docs/404.html.in > i'm testing latest release and some upstream commit to fix segfaults. > Once it's done it will be pushed to my branch > Building latest libvirt (git trunk) on a clean Slackware 15.0 the build completes without error, but it does not build /usr/sbin/virtqemud, which causes the installed /usr/bin/virsh to fail with ??? error: failed to connect to the hypervisor ??? error: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': ?????????? No such file or directory I've reported the issue on libvirt-users, but no response yet. Will report back here when I find a fix. -- Chuck Polisher From andrzej at telszewski.com Sun Mar 6 16:36:08 2022 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Sun, 06 Mar 2022 17:36:08 +0100 Subject: [Slackbuilds-users] rtl8821ce: Reason for removal In-Reply-To: <20220304204703.GZ4508@localhost> References: <9cc4d0fe-51c6-441c-9fb1-e3174887393f@www.fastmail.com> <20220304200736.GX4508@localhost> <7c3c328a-2879-4398-8745-0716a059d232@telszewski.com> <20220304204703.GZ4508@localhost> Message-ID: <332cbf13-4b1e-47f8-9296-b4dc832dc979@www.fastmail.com> >> I have a report from a user that some recent commit from the upstream repo builds fine on 15.0. >> I'm not actively using this driver any more, so I cannot test it on real HW, but I surely can try building it. >> Would you like me to try it out and report back? > > Please do. I reverted _83c64a3e52_, then applied the attached patch. The driver builds and it can be loaded into the kernel (tested in VM). Because recently I received a ping from one of the *rtl8821ce* driver users, I assume it is still in use by someone. Please incorporate the attached patch. Please note that it is slightly different from what _B Watson_ did in his branch (thanks for testing :-)). Thank you! :-) -------------- next part -------------- A non-text attachment was scrubbed... Name: rtl8821ce.patch Type: text/x-patch Size: 2061 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun Mar 6 17:28:25 2022 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 6 Mar 2022 11:28:25 -0600 Subject: [Slackbuilds-users] libvirt failing for me on 15.0 In-Reply-To: <1e55d755-cc02-db68-dc07-3e51ecb01d62@sonic.net> References: <1e55d755-cc02-db68-dc07-3e51ecb01d62@sonic.net> Message-ID: <20220306112825.4f971cbe@home.rlworkman.net> On Sat, 5 Mar 2022 14:29:15 -0800 Kent Fritz wrote: > It's not on the list of failing builds, so does anybody know what > this error means or how to fix? > > [974/1281] Generating 404.html with a custom command (wrapped by > meson to capture output) > FAILED: docs/404.html > /usr/bin/meson --internal exe --capture docs/404.html -- > /usr/bin/xsltproc --stringparam pagesrc docs/404.html.in > --stringparam builddir /tmp/SBo/libvirt-8.0.0/build --stringparam > timestamp 'Sat Mar 5 22:15:01 2022 UTC' --nonet ../docs/site.xsl > ../docs/404.html.in --- stderr --- > runtime error: file ../docs/page.xsl line 223 element element > xsl:element: The effective name '' is not a valid QName. > no result for ../docs/404.html.in Try the libvirt and libvirt-python upgrades in my git branch. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Mar 6 17:56:01 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 7 Mar 2022 00:56:01 +0700 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> <73b2eb7f-64d3-289c-af50-dd1768a3484f@slackbuilds.org> Message-ID: <6de64398-bd2d-21d2-ba44-a015979d2ab3@slackbuilds.org> > Thanks for the explanation. I have just checked and the build script does > download anything. There are a few warnings at build time but otherwise > nothing out of the ordinary. > > I attach the log file where I built pdfpc and all its dependencies. OK, good to know we just have to make some adjustment on the CI tool -- 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 dave at slackbuilds.org Sun Mar 6 18:56:56 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 6 Mar 2022 18:56:56 +0000 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: <0696c282-f96d-0071-4062-894cd8844e9c@gmail.com> References: <0696c282-f96d-0071-4062-894cd8844e9c@gmail.com> Message-ID: <20220306185656.GA4508@localhost> On 06/03/22 08:48, Dan Whisman put forth the proposition: > I was able to build CubicSDR 0.2.7 just fine with the repo as-is, but it > needed SoapySDR 0.8.1 which is not in master. I have attached a patch > (which I also emailed to the maintainer). It bumps the version, adds > Python3 support, and fixes the man page directory. > With the upgraded SoapySDR, I was able to successfully test CubicSDR by > listening to a local FM station. I did use newer versions of SoapySDRPlay > and SDRPlay packages and I also emailed patches to the maintainer. Thanks Dan -- Dave From yalhcru at gmail.com Sun Mar 6 23:01:34 2022 From: yalhcru at gmail.com (B Watson) Date: Sun, 6 Mar 2022 18:01:34 -0500 Subject: [Slackbuilds-users] Please update your zopfli SlackBuild In-Reply-To: References: Message-ID: On 3/1/22, Duncan Roe wrote: > zopfli is a runtime dependency of afdko and hence a build time dependency > of > Type1_to_OTF (which I maintain). Apparently afdko also needs at least one new dep, since you updated it. Have you already got a build for python3-fontpens? File "/usr/lib64/python3.9/site-packages/afdko/ufotools.py", line 9, in from fontPens.thresholdPen import ThresholdPen ModuleNotFoundError: No module named 'fontPens' We're trying to clear the queue of broken builds (either fix or remove them), so we can launch the 15.0 repository in 100% working condition. Type1_to_OTF is failing to build, so if you have a working script for it and all its dependencies, please post them somewhere (patches on this mailing list would be my preference, or just tarball attachments). Possibly you already did this as a PR/MR on github... in which case, don't worry about this email. I don't do github, but others on the SBo team will take care of it. From dave at slackbuilds.org Sun Mar 6 23:29:36 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 6 Mar 2022 23:29:36 +0000 Subject: [Slackbuilds-users] rtl8821ce: Reason for removal In-Reply-To: <332cbf13-4b1e-47f8-9296-b4dc832dc979@www.fastmail.com> References: <9cc4d0fe-51c6-441c-9fb1-e3174887393f@www.fastmail.com> <20220304200736.GX4508@localhost> <7c3c328a-2879-4398-8745-0716a059d232@telszewski.com> <20220304204703.GZ4508@localhost> <332cbf13-4b1e-47f8-9296-b4dc832dc979@www.fastmail.com> Message-ID: <20220306232936.GB4508@localhost> On 06/03/22 17:36, Andrzej Telszewski put forth the proposition: > >> I have a report from a user that some recent commit from the upstream repo builds fine on 15.0. > >> I'm not actively using this driver any more, so I cannot test it on real HW, but I surely can try building it. > >> Would you like me to try it out and report back? > > > > Please do. > I reverted _83c64a3e52_, then applied the attached patch. > The driver builds and it can be loaded into the kernel (tested in VM). > Because recently I received a ping from one of the *rtl8821ce* driver users, I assume it is still in use by someone. > Please incorporate the attached patch. > Please note that it is slightly different from what _B Watson_ did in his branch (thanks for testing :-)). > Thank you! :-) Thanks Andrzej -- Dave From duncan_roe at optusnet.com.au Sun Mar 6 23:59:30 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Mon, 7 Mar 2022 10:59:30 +1100 Subject: [Slackbuilds-users] Please update your zopfli SlackBuild In-Reply-To: References: Message-ID: On Sun, Mar 06, 2022 at 06:01:34PM -0500, B Watson wrote: > On 3/1/22, Duncan Roe wrote: > > > zopfli is a runtime dependency of afdko and hence a build time dependency > > of > > Type1_to_OTF (which I maintain). > > Apparently afdko also needs at least one new dep, since you updated it. > > Have you already got a build for python3-fontpens? > > File "/usr/lib64/python3.9/site-packages/afdko/ufotools.py", line 9, > in > from fontPens.thresholdPen import ThresholdPen > ModuleNotFoundError: No module named 'fontPens' > > We're trying to clear the queue of broken builds (either fix or > remove them), so we can launch the 15.0 repository in 100% working > condition. Type1_to_OTF is failing to build, so if you have a working > script for it and all its dependencies, please post them somewhere > (patches on this mailing list would be my preference, or just tarball > attachments). > > Possibly you already did this as a PR/MR on github... in which case, > don't worry about this email. I don't do github, but others on the SBo > team will take care of it. There are at least 15 new deps, but I have them all covered. Hope to do a PR later today (needs to be a PR because tqdm will then be in front of it). Cheers ... Duncan. From duncan_roe at optusnet.com.au Mon Mar 7 00:06:20 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Mon, 7 Mar 2022 11:06:20 +1100 Subject: [Slackbuilds-users] lxml SlackBuild needs to be newer version In-Reply-To: References: Message-ID: Hi Larry, Your lxml SB is the only one left in the repo for which Type1_to_OTF needs a newer version. Would it be OK with you if I pushed a rev bump? Cheers ... Duncan. On Sun, Feb 27, 2022 at 12:24:37PM +1100, Duncan Roe wrote: > On Sun, Feb 27, 2022 at 12:15:27PM +1100, Duncan Roe wrote: > > Hi Larry, > > > > lxml SB is at version 4.6.3 but PyPi has 4.8.0. > > > > afdko (that I maintain) requires at least 4.7.1. > > > > For now, I built afdko using pip2tgz to get an up-to-date lxml, > > but could you update your SB please? > > Some clarification: lxml is a *runtime* dependency of afdko. afdko *builds* > w/out lxml. > > Type1_to_OTF uses afdko to build: I should have posted "I built Type1_to_OTF > using pip2tgz to get an up-to-date lxml". > > Cheers ... Duncan. From artourter at gmail.com Mon Mar 7 00:26:10 2022 From: artourter at gmail.com (Greg' Ar Tourter) Date: Mon, 7 Mar 2022 00:26:10 +0000 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: <6de64398-bd2d-21d2-ba44-a015979d2ab3@slackbuilds.org> References: <28eebab4-9e99-cb6e-93f7-6ca236a4d765@slackbuilds.org> <73b2eb7f-64d3-289c-af50-dd1768a3484f@slackbuilds.org> <6de64398-bd2d-21d2-ba44-a015979d2ab3@slackbuilds.org> Message-ID: I have also checked nagios_plugins and it builds fine at my end. If you can get more info as to why it fail, I can look further. Looking at the build logs, it doesn't download anything during the build however the configure script does test for ping and ping6 using 127.0.0.1 and ::1 to test the syntax, so if there is no network at all in CI, not even localhost that could explain the failure. Cheers Greg On Sun, 6 Mar 2022 at 17:56, Willy Sudiarto Raharjo wrote: > > Thanks for the explanation. I have just checked and the build script does > > download anything. There are a few warnings at build time but otherwise > > nothing out of the ordinary. > > > > I attach the log file where I built pdfpc and all its dependencies. > > OK, good to know > we just have to make some adjustment on the CI tool > > > -- > 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 willysr at slackbuilds.org Mon Mar 7 02:58:48 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 7 Mar 2022 09:58:48 +0700 Subject: [Slackbuilds-users] Please update your zopfli SlackBuild In-Reply-To: References: Message-ID: <7d28ebe3-fc25-1c28-9859-904a4b897faf@slackbuilds.org> >> Have you already got a build for python3-fontpens? >> >> File "/usr/lib64/python3.9/site-packages/afdko/ufotools.py", line 9, >> in >> from fontPens.thresholdPen import ThresholdPen >> ModuleNotFoundError: No module named 'fontPens' >> >> We're trying to clear the queue of broken builds (either fix or >> remove them), so we can launch the 15.0 repository in 100% working >> condition. Type1_to_OTF is failing to build, so if you have a working >> script for it and all its dependencies, please post them somewhere >> (patches on this mailing list would be my preference, or just tarball >> attachments). >> >> Possibly you already did this as a PR/MR on github... in which case, >> don't worry about this email. I don't do github, but others on the SBo >> team will take care of it. > > There are at least 15 new deps, but I have them all covered. > > Hope to do a PR later today (needs to be a PR because tqdm will then be in front > of it). Uh.. i removed it on my branch, i'll revert it and wait for your PR -- 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 willysr at slackbuilds.org Mon Mar 7 03:03:52 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 7 Mar 2022 10:03:52 +0700 Subject: [Slackbuilds-users] lxml SlackBuild needs to be newer version In-Reply-To: References: Message-ID: <9f87acbf-39c8-55af-9d23-695a3c1b93e3@slackbuilds.org> > Your lxml SB is the only one left in the repo for which Type1_to_OTF needs a > newer version. > > Would it be OK with you if I pushed a rev bump? please push it Larry hasn't replied my previous email as well, so i guess he's a bit inactive lately -- 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 matteo.bernardini at gmail.com Mon Mar 7 05:57:01 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 7 Mar 2022 06:57:01 +0100 Subject: [Slackbuilds-users] lxml SlackBuild needs to be newer version In-Reply-To: References: Message-ID: just be sure that the newer lxml doesn't break anything depending on lxml... Matteo Il giorno lun 7 mar 2022 alle ore 01:06 Duncan Roe ha scritto: > > Hi Larry, > > Your lxml SB is the only one left in the repo for which Type1_to_OTF needs a > newer version. > > Would it be OK with you if I pushed a rev bump? > > Cheers ... Duncan. > > On Sun, Feb 27, 2022 at 12:24:37PM +1100, Duncan Roe wrote: > > On Sun, Feb 27, 2022 at 12:15:27PM +1100, Duncan Roe wrote: > > > Hi Larry, > > > > > > lxml SB is at version 4.6.3 but PyPi has 4.8.0. > > > > > > afdko (that I maintain) requires at least 4.7.1. > > > > > > For now, I built afdko using pip2tgz to get an up-to-date lxml, > > > but could you update your SB please? > > > > Some clarification: lxml is a *runtime* dependency of afdko. afdko *builds* > > w/out lxml. > > > > Type1_to_OTF uses afdko to build: I should have posted "I built Type1_to_OTF > > using pip2tgz to get an up-to-date lxml". > > > > 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/ > From yalhcru at gmail.com Mon Mar 7 08:16:10 2022 From: yalhcru at gmail.com (B Watson) Date: Mon, 7 Mar 2022 03:16:10 -0500 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: <2IKLFIfzn9kWo2-VGWAJgMwsaN5M6xF1EYcdkkFz1csvwus-ah16Ba12DfDRX5tMEfIuI3xPbaOsa3LjtmGFEV_qUgxrp8CXdqmlqo-N3M0=@protonmail.com> References: <20220306010656.2fa02afd@knotsUL> <1b6e2468-34c2-2db9-8dfb-23c60fc056ef@slackbuilds.org> <2IKLFIfzn9kWo2-VGWAJgMwsaN5M6xF1EYcdkkFz1csvwus-ah16Ba12DfDRX5tMEfIuI3xPbaOsa3LjtmGFEV_qUgxrp8CXdqmlqo-N3M0=@protonmail.com> Message-ID: On 3/5/22, Erich Ritz via SlackBuilds-users wrote: > > On the other hand, there are a few offending SBo packages in /usr/lib64 on > my system (apologies if any of these have been fixed recently): > > # ls -l /usr/lib64/*.la > -rwxr-xr-x 1 root root 1172 Feb 16 08:08 /usr/lib64/libflatpak.la* > (flatpak-1.10.2-x86_64-2_SBo) > -rwxr-xr-x 1 root root 980 Mar 3 12:10 /usr/lib64/libgeotiff.la* > (libgeotiff-1.5.1-x86_64-1_SBo) > -rwxr-xr-x 1 root root 910 Feb 7 10:46 /usr/lib64/libglpk.la* > (glpk-4.61-x86_64-1_SBo) > -rwxr-xr-x 1 root root 916 Feb 7 12:16 /usr/lib64/liblaszip.la* > (laszip-2.2.0-x86_64-1_SBo) Thanks for the list, fixing these right now. From yalhcru at gmail.com Mon Mar 7 08:50:48 2022 From: yalhcru at gmail.com (B Watson) Date: Mon, 7 Mar 2022 03:50:48 -0500 Subject: [Slackbuilds-users] New Templates and 15.0 Repository Progress In-Reply-To: References: <20220306010656.2fa02afd@knotsUL> <1b6e2468-34c2-2db9-8dfb-23c60fc056ef@slackbuilds.org> <2IKLFIfzn9kWo2-VGWAJgMwsaN5M6xF1EYcdkkFz1csvwus-ah16Ba12DfDRX5tMEfIuI3xPbaOsa3LjtmGFEV_qUgxrp8CXdqmlqo-N3M0=@protonmail.com> Message-ID: Oh, while I'm thinking about it. The only builds that will ever include .la files in /usr/lib(64) are ones that use autotools (./configure script). I've never seen them in builds that use plain make, cmake, meson, scons, etc. In theory it could happen (some insane person could call libtool from a regular Makefile or CMakeLists.txt), but I kinda doubt it ever does. This might be useful info for someone... From peter at peter-dambier.de Mon Mar 7 10:04:19 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Mon, 7 Mar 2022 11:04:19 +0100 Subject: [Slackbuilds-users] Successfully built on Slackware 15.0 Message-ID: <20220307110419.54a72d33.peter@peter-dambier.de> Hi fellow SlackBuilders, sometimes avr-gcc in particular I had to install gcc-5.3.0 from Slackware 14.4. Dont remove! Install gcc-11.2.0 afterwards. Some version bumps. Here comes the list. Thanks Peter -------------- next part -------------- /*Successfully built on Slackware 15.0 64 Bit */ Academic/galculator/galculator-2.1.4-x86_64-1_SBo.tgz Academic/libqalculate/libqalculate-3.10.0-x86_64-1_SBo.tgz Academic/ncview/ncview-2.1.8-x86_64-1_SBo.tgz Academic/pcalc/pcalc-4-x86_64-1_SBo.tgz Academic/qalculate-gtk/qalculate-gtk-3.10.0-x86_64-1_SBo.tgz Academic/units/units-2.20-x86_64-1_SBo.tgz Audio/audacity/audacity-2.4.1-x86_64-1_SBo.tgz Audio/celt/celt-0.11.3-x86_64-1_SBo.tgz Audio/faac/faac-1.30-x86_64-1_SBo.tgz Audio/faad2/faad2-2.9.2-x86_64-1_SBo.tgz Audio/jack/jack-1.9.17-x86_64-1_SBo.tgz Audio/ladspa_sdk/ladspa_sdk-1.13-x86_64-4_SBo.tgz Audio/lv2/lv2-1.18.0-x86_64-1_SBo.tgz Audio/miniAudicle/miniAudicle-0.2.2c-x86_64-1_SBo.tgz Audio/minimodem/minimodem-0.24-x86_64-2_SBo.tgz Audio/paman/paman-0.9.4-x86_64-1_SBo.tgz Audio/pavumeter/pavumeter-0.9.3-x86_64-1_SBo.tgz Audio/ponymix/ponymix-5-x86_64-1_SBo.tgz Audio/qjackctl/qjackctl-0.9.1-x86_64-1_SBo.tgz Audio/rubberband/rubberband-1.9.0-x86_64-1_SBo.tgz Audio/twolame/twolame-0.4.0-x86_64-1_SBo.tgz Audio/vamp-plugin-sdk/vamp-plugin-sdk-2.9.0-x86_64-1_SBo.tgz Audio/xmp/xmp-4.1.0-x86_64-1_SBo.tgz Desktop/e16.theme.pack/e16.theme.pack-1.0.3-noarch-1_SBo.tgz Desktop/find-cursor/find-cursor-1.6-x86_64-1_SBo.tgz Desktop/fvwm-crystal/fvwm-crystal-3.4.1-x86_64-1_SBo.tgz Desktop/gkrellm-themes/gkrellm-themes-20030129-noarch-1_SBo.tgz Desktop/hsetroot/hsetroot-1.0.2-x86_64-1_SBo.tgz Desktop/lxmenu-data/lxmenu-data-0.1.5-x86_64-1_SBo.tgz Desktop/mh5000/mh5000-1.3.5-x86_64-1_SBo.tgz Desktop/nitrogen/nitrogen-1.6.1-x86_64-1_SBo.tgz Desktop/parcellite/parcellite-1.1.9-x86_64-1_SBo.tgz Desktop/slack-wallpapers/slack-wallpapers-1.0-noarch-2_SBo.tgz Desktop/slackware-xdm-theme/slackware-xdm-theme-20170522-x86_64-1_SBo.tgz Desktop/stalonetray/stalonetray-0.8.3-x86_64-1_SBo.tgz Desktop/x2x/x2x-1.30_beta+20200121_ec10215-x86_64-1_SBo.tgz Desktop/xearth/xearth-1.1-x86_64-1_SBo.tgz Desktop/xsession-xinitrc/xsession-xinitrc-0.0.1-x86_64-1_SBo.tgz Desktop/xsession/xsession-1.1-x86_64-1_SBo.tgz Desktop/zenity/zenity-3.28.0-x86_64-1_SBo.tgz Development/avr-binutils/avr-binutils-2.25-x86_64-1_SBo.tgz Development/avr-gcc/avr-gcc-4.9.2-x86_64-1_SBo.tgz Development/avrdude/avrdude-6.3-x86_64-1_SBo.tgz Development/bluefish/bluefish-2.2.12-x86_64-1_SBo.tgz Development/bzr/bzr-2.7.0-x86_64-1_SBo.tgz Development/cppunit/cppunit-1.15.1-x86_64-1_SBo.tgz Development/ghex/ghex-3.18.4-x86_64-1_SBo.tgz Development/hexe/hexe-20120305-x86_64-1_SBo.tgz Development/hexedit/hexedit-1.2.12-x86_64-1_SBo.tgz Development/lua/lua-5.1.5-x86_64-1_SBo.tgz Development/mkchroot/mkchroot-1.4-noarch-1_SBo.tgz Development/ninja/ninja-1.10.2-x86_64-1_SBo.tgz Development/numpy3/numpy3-1.22.2-x86_64-1_SBo.tgz Development/portaudio/portaudio-v190600_20161030-x86_64-1_SBo.tgz Development/qbs/qbs-1.16.0-x86_64-1_SBo.tgz Development/snappy/snappy-1.1.8-x86_64-2_SBo.tgz Development/swi-prolog/swi-prolog-8.2.1-x86_64-2_SBo.tgz Games/bluez-sixaxis/bluez-sixaxis-5.63-x86_64-1_SBo.tgz Graphics/GraphicsMagick/GraphicsMagick-1.3.35-x86_64-1_SBo.tgz Graphics/barcode/barcode-0.99-x86_64-1_SBo.tgz Graphics/dcraw/dcraw-9.28.0-x86_64-1_SBo.tgz Graphics/exif/exif-0.6.22-x86_64-1_SBo.tgz Graphics/exiftags/exiftags-1.01-x86_64-1_SBo.tgz Graphics/feh/feh-3.6.1-x86_64-1_SBo.tgz Graphics/fritzing/fritzing-0.9.3b-x86_64-1_SBo.tgz Graphics/graph-easy/graph-easy-0.76-x86_64-1_SBo.tgz Graphics/graphviz/graphviz-2.40.1-x86_64-1_SBo.tgz Graphics/hp2xx/hp2xx-3.4.4-x86_64-1_SBo.tgz Graphics/libfpx/libfpx-1.3.1_10-x86_64-1_SBo.tgz Graphics/png2ico/png2ico-20021208-x86_64-1_SBo.tgz Graphics/pygraphviz/pygraphviz-1.5-x86_64-1_SBo.tgz Graphics/qrencode/qrencode-4.1.1-x86_64-1_SBo.tgz Graphics/ralcgm/ralcgm-3.50-x86_64-1_SBo.tgz Graphics/scrot/scrot-0.8-x86_64-4_SBo.tgz Graphics/viewnior/viewnior-1.7-x86_64-2_SBo.tgz Graphics/xbmbrowser/xbmbrowser-5.1b-x86_64-1_SBo.tgz Graphics/xdaliclock/xdaliclock-2.44-x86_64-1_SBo.tgz Graphics/xfishtank/xfishtank-2.5-x86_64-1_SBo.tgz Ham/ax25-apps/ax25-apps-0.0.8_rc5-x86_64-1_SBo.tgz Ham/ax25-tools/ax25-tools-0.0.10_rc5-x86_64-1_SBo.tgz Ham/chirp/chirp-20201128-x86_64-1_SBo.tgz Ham/direwolf/direwolf-1.5-x86_64-1_SBo.tgz Ham/hamlib/hamlib-3.3-x86_64-1_SBo.tgz Ham/libax25/libax25-0.0.12_rc5-x86_64-1_SBo.tgz Ham/nec2c/nec2c-1.3-x86_64-1_SBo.tgz Ham/soundmodem/soundmodem-0.18-x86_64-1_SBo.tgz Libraries/Jinja2/Jinja2-2.11.3-x86_64-1_SBo.tgz Libraries/ORBit2/ORBit2-2.14.19-x86_64-3_SBo.tgz Libraries/OpenAL/OpenAL-1.18.0-x86_64-1_SBo.tgz Libraries/OpenBLAS/OpenBLAS-0.3.12-x86_64-1_SBo.tgz Libraries/avr-libc/avr-libc-1.8.1-x86_64-3_SBo.tgz Libraries/bluez-alsa/bluez-alsa-1.3.1-x86_64-1_SBo.tgz Libraries/dav1d/dav1d-0.5.2-x86_64-1_SBo.tgz Libraries/exiftool/exiftool-11.11-x86_64-1_SBo.tgz Libraries/gavl/gavl-1.4.0-x86_64-2_SBo.tgz Libraries/giblib/giblib-1.2.4-x86_64-3_SBo.tgz Libraries/goffice/goffice-0.10.34-x86_64-1_SBo.tgz Libraries/gsm/gsm-1.0.13-x86_64-2_SBo.tgz Libraries/gtkglarea/gtkglarea-2.1.0-x86_64-1_SBo.tgz Libraries/gts/gts-0.7.6-x86_64-3_SBo.tgz Libraries/hdf5/hdf5-1.10.6-x86_64-1_SBo.tgz Libraries/http-parser/http-parser-2.9.4-x86_64-1_SBo.tgz Libraries/imlib2/imlib2-1.7.1-x86_64-1_SBo.tgz Libraries/ipaddress/ipaddress-1.0.22-x86_64-1_SBo.tgz Libraries/jbigkit/jbigkit-2.1-x86_64-2_SBo.tgz Libraries/libbonobo/libbonobo-2.32.1-x86_64-3_SBo.tgz Libraries/libbsd/libbsd-0.10.0-x86_64-1_SBo.tgz Libraries/libcli/libcli-1.9.7-x86_64-1_SBo.tgz Libraries/libcpuid/libcpuid-0.5.1-x86_64-1_SBo.tgz Libraries/libdc1394/libdc1394-2.2.6-x86_64-1_SBo.tgz Libraries/libdvbpsi/libdvbpsi-1.3.1-x86_64-1_SBo.tgz Libraries/libetpan/libetpan-1.9.3-x86_64-1_SBo.tgz Libraries/libewf/libewf-20140811-x86_64-1_SBo.tgz Libraries/libfdk-aac/libfdk-aac-2.0.1-x86_64-1_SBo.tgz Libraries/libfilezilla/libfilezilla-0.16.0-x86_64-1_SBo.tgz Libraries/libfilezilla/libfilezilla-0.36.0-x86_64-1_SBo.tgz Libraries/libfm-extra/libfm-extra-1.3.2-x86_64-1_SBo.tgz Libraries/libfm/libfm-1.3.2-x86_64-1_SBo.tgz Libraries/libgit2/libgit2-1.0.0-x86_64-1_SBo.tgz Libraries/libglademm/libglademm-2.6.7-x86_64-2_SBo.tgz Libraries/libgme/libgme-0.6.3-x86_64-1_SBo.tgz Libraries/libilbc/libilbc-2.0.2-x86_64-2_SBo.tgz Libraries/liblo/liblo-0.31-x86_64-1_SBo.tgz Libraries/libminizip/libminizip-1.2.11-x86_64-1_SBo.tgz Libraries/libmodplug/libmodplug-0.8.9.0-x86_64-1_SBo.tgz Libraries/libmpeg2/libmpeg2-0.5.1-x86_64-1_SBo.tgz Libraries/libnet/libnet-1.1.6-x86_64-1_SBo.tgz Libraries/libnids/libnids-1.24-x86_64-2_SBo.tgz Libraries/libpaper/libpaper-1.1.28-x86_64-1_SBo.tgz Libraries/libshout/libshout-2.3.1-x86_64-1_SBo.tgz Libraries/libupnp/libupnp-1.8.3-x86_64-2_SBo.tgz Libraries/liburcu/liburcu-0.12.2-x86_64-1_SBo.tgz Libraries/libx86emu/libx86emu-2.4-x86_64-1_SBo.tgz Libraries/libxmp/libxmp-4.4.1-x86_64-1_SBo.tgz Libraries/lilv/lilv-0.24.8-x86_64-1_SBo.tgz Libraries/live555/live555-2020.08.19-x86_64-1_SBo.tgz Libraries/menu-cache/menu-cache-1.1.0-x86_64-1_SBo.tgz Libraries/mxml/mxml-3.1-x86_64-2_SBo.tgz Libraries/nacl/nacl-20110221-x86_64-1_SBo.tgz Libraries/netcdf/netcdf-4.7.4-x86_64-1_SBo.tgz Libraries/pugixml/pugixml-1.11.4-x86_64-1_SBo.tgz Libraries/serd/serd-0.30.4-x86_64-1_SBo.tgz Libraries/setproctitle/setproctitle-1.1.10-x86_64-1_SBo.tgz Libraries/sord/sord-0.16.4-x86_64-1_SBo.tgz Libraries/soundtouch/soundtouch-1.9.2-x86_64-1_SBo.tgz Libraries/sratom/sratom-0.6.4-x86_64-1_SBo.tgz Libraries/suil/suil-0.10.6-x86_64-1_SBo.tgz Libraries/tcllib/tcllib-1.20-x86_64-1_SBo.tgz Libraries/udunits/udunits-2.2.28-x86_64-1_SBo.tgz Libraries/uuid/uuid-1.6.2-x86_64-1_SBo.tgz Libraries/vid.stab/vid.stab-97c6ae2-x86_64-1_SBo.tgz Libraries/wv/wv-1.2.9-x86_64-1_SBo.tgz Libraries/wxGTK3/wxGTK3-3.0.5-x86_64-1_SBo.tgz Libraries/wxPython/wxPython-2.8.12.1-x86_64-2_SBo.tgz Libraries/zint/zint-2.9.1-x86_64-1_SBo.tgz Misc/altermime/altermime-0.3.10-x86_64-1_SBo.tgz Misc/cflow/cflow-1.4-x86_64-1_SBo.tgz Misc/clawsker/clawsker-1.1.0-noarch-1_SBo.tgz Misc/cp437/cp437-0.6-x86_64-1_SBo.tgz Misc/dbview/dbview-1.0.4-x86_64-1_SBo.tgz Misc/deb2tgz/deb2tgz-0.2-noarch-1_SBo.tgz Misc/deroff/deroff-2.0-x86_64-1_SBo.tgz Misc/dos2unix/dos2unix-7.4.1-x86_64-1_SBo.tgz Misc/fcrackzip/fcrackzip-1.0-x86_64-2_SBo.tgz Misc/gnome-mime-data/gnome-mime-data-2.18.0-x86_64-2_SBo.tgz Misc/paperkey/paperkey-1.5-x86_64-1_SBo.tgz Misc/protobuf/protobuf-2.6.1-x86_64-1_SBo.tgz Misc/ramdefrag/ramdefrag-0.4.0-x86_64-1_SBo.tgz Misc/rarcrack/rarcrack-0.2-x86_64-3_SBo.tgz Misc/recode/recode-3.7_beta2-x86_64-2_SBo.tgz Misc/sbo-templates/sbo-templates-1.3.2-x86_64-1_SBo.tgz Multimedia/aom/aom-2.0.1-x86_64-1_SBo.tgz Multimedia/schroedinger/schroedinger-1.0.11-x86_64-1_SBo.tgz Multimedia/x264/x264-20170225-x86_64-1_SBo.tgz Multimedia/x265/x265-3.4-x86_64-1_SBo.tgz Multimedia/xvidcore/xvidcore-1.3.5-x86_64-1_SBo.tgz Multimedia/zvbi/zvbi-0.2.35-x86_64-1_SBo.tgz Network/GeoIP/GeoIP-1.6.12-x86_64-1_SBo.tgz Network/aria2/aria2-1.35.0-x86_64-1_SBo.tgz Network/arp-scan/arp-scan-1.9-x86_64-1_SBo.tgz Network/driftnet/driftnet-1.3.0-x86_64-1_SBo.tgz Network/filezilla/filezilla-3.58.0-x86_64-1_SBo.tgz Network/nbtscan/nbtscan-1.0.35-x86_64-1_SBo.tgz Network/netdiscover/netdiscover-053dda2-x86_64-1_SBo.tgz Network/ngrep/ngrep-1.45-x86_64-2_SBo.tgz Network/persepolis/persepolis-3.2.0-x86_64-1_SBo.tgz Network/uudeview/uudeview-0.5.20-x86_64-1_SBo.tgz Network/you-get/you-get-0.4.1500-x86_64-1_SBo.tgz Network/youtube-dl/youtube-dl-2021.02.22-x86_64-1_SBo.tgz Office/Ted/Ted-2.23-x86_64-2_SBo.tgz Office/abiword/abiword-3.0.4-x86_64-1_SBo.tgz Office/antiword/antiword-0.37-x86_64-1_SBo.tgz Office/cups-pdf/cups-pdf-3.0.1-x86_64-1_SBo.tgz Office/ghostwriter/ghostwriter-1.8.1-x86_64-2_SBo.tgz Office/odt2txt/odt2txt-0.5-x86_64-1_SBo.tgz Office/ps2eps/ps2eps-1.64-x86_64-1_SBo.tgz Office/pstotext/pstotext-1.9-x86_64-1_SBo.tgz Python/MarkupSafe/MarkupSafe-1.1.1-x86_64-1_SBo.tgz Python/Unidecode/Unidecode-0.04.21-x86_64-1_SBo.tgz Python/google-apputils/google-apputils-0.4.2-x86_64-1_SBo.tgz Python/idna/idna-2.6-x86_64-1_SBo.tgz Python/mock/mock-2.0.0-x86_64-2_SBo.tgz Python/pbr/pbr-5.1.1-x86_64-1_SBo.tgz Python/psutil/psutil-5.6.7-x86_64-1_SBo.tgz Python/pyserial/pyserial-3.5-x86_64-1_SBo.tgz Python/python-certifi/python-certifi-2020.12.5-x86_64-1_SBo.tgz Python/python-chardet/python-chardet-3.0.4-x86_64-1_SBo.tgz Python/python-dateutil/python-dateutil-2.8.0-x86_64-1_SBo.tgz Python/python-gflags/python-gflags-3.1.0-x86_64-1_SBo.tgz Python/python-notify2/python-notify2-0.3.1-x86_64-2_SBo.tgz Python/python-requests/python-requests-2.25.0-x86_64-1_SBo.tgz Python/python-urllib3/python-urllib3-1.26.2-x86_64-1_SBo.tgz Python/python3-pythondialog/python3-pythondialog-3.5.1-x86_64-1_SBo.tgz Python/python3-sip/python3-sip-4.19.20-x86_64-3_SBo.tgz Python/pytz/pytz-2018.3-x86_64-1_SBo.tgz Python/setuptools-scm/setuptools-scm-3.4.1-x86_64-1_SBo.tgz Python/six/six-1.14.0-x86_64-1_SBo.tgz System/CPU-X/CPU-X-4.3.0-x86_64-1_SBo.tgz System/SavvyCAN/SavvyCAN-197-x86_64-1_SBo.tgz System/TermRecord/TermRecord-1.2.5-x86_64-1_SBo.tgz System/alien/alien-8.95-x86_64-1_SBo.tgz System/apg/apg-2.2.3-x86_64-1_SBo.tgz System/filerunner/filerunner-20.05.02.17-x86_64-1_SBo.tgz System/findpkg/findpkg-20160817-noarch-1_SBo.tgz System/foomatic-db-engine/foomatic-db-engine-4.0.13-x86_64-1_SBo.tgz System/foomatic-db/foomatic-db-20170729-noarch-1_SBo.tgz System/gpart/gpart-0.3-x86_64-2_SBo.tgz System/graveman/graveman-0.3.12.5-x86_64-6_SBo.tgz System/hardinfo/hardinfo-0.5.1-x86_64-3_SBo.tgz System/hddtemp/hddtemp-0.3beta15-x86_64-3_SBo.tgz System/hwinfo/hwinfo-21.67-x86_64-1_SBo.tgz System/listpkg/listpkg-0.1a-noarch-1_SBo.tgz System/lshw/lshw-B.02.19.2-x86_64-1_SBo.tgz System/p7zip/p7zip-16.02-x86_64-2_SBo.tgz System/patchelf/patchelf-0.10-x86_64-1_SBo.tgz System/pax/pax-20201030-x86_64-1_SBo.tgz System/pcmanfm/pcmanfm-1.3.2-x86_64-1_SBo.tgz System/picocom/picocom-3.1-x86_64-1_SBo.tgz System/read-edid/read-edid-3.0.2-x86_64-1_SBo.tgz System/rkhunter/rkhunter-1.4.6-x86_64-1_SBo.tgz System/rox-filer/rox-filer-2.11-x86_64-3_SBo.tgz System/safecopy/safecopy-1.7-x86_64-1_SBo.tgz System/sbotools/sbotools-2.7-noarch-1_SBo.tgz System/slackware-grub2-theme/slackware-grub2-theme-1.0-noarch-1_SBo.tgz System/sleuthkit/sleuthkit-4.10.1-x86_64-1_SBo.tgz System/slpkg/slpkg-3.9.1-x86_64-1_SBo.tgz System/smart/smart-1.4.1-x86_64-1_SBo.tgz System/spkg/spkg-1.1-x86_64-1_SBo.tgz System/sunflower/sunflower-0.3-x86_64-1_SBo.tgz System/the_silver_searcher/the_silver_searcher-2.2.0-x86_64-1_SBo.tgz System/ttf-ancient-fonts/ttf-ancient-fonts-2.60-noarch-1_SBo.tgz System/ttf-dark-courier/ttf-dark-courier-01182001-noarch-1_SBo.tgz System/ttf-ubuntu-font-family/ttf-ubuntu-font-family-0.83-noarch-1_SBo.tgz System/udevil/udevil-0.4.4-x86_64-1_SBo.tgz System/unp/unp-2.0~pre7+nmu1-noarch-1_SBo.tgz System/unrtf/unrtf-0.21.9-x86_64-1_SBo.tgz System/unshield/unshield-0.6-x86_64-1_SBo.tgz System/wipe/wipe-2.3.1-x86_64-2_SBo.tgz System/xarchiver/xarchiver-0.5.4.17-x86_64-1_SBo.tgz System/xdiskusage/xdiskusage-1.51-x86_64-1_SBo.tgz /* END */ From willysr at slackbuilds.org Mon Mar 7 12:25:48 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 7 Mar 2022 19:25:48 +0700 Subject: [Slackbuilds-users] lxml SlackBuild needs to be newer version In-Reply-To: References: Message-ID: <8a10faf0-82af-3086-ec72-a708c72260b3@slackbuilds.org> > just be sure that the newer lxml doesn't break anything depending on lxml... I hope the changes listed here (https://github.com/lxml/lxml/blob/master/CHANGES.txt) are not that invasive to other projects -- 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 erich.public at protonmail.com Mon Mar 7 14:25:28 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 07 Mar 2022 14:25:28 +0000 Subject: [Slackbuilds-users] libraries/atlas fails to build on Slackware 15.0 Message-ID: <14960LVPWatuFHXXZQnuvbOdsjfvriuHTs6JUjcxevoD_ICZu6FcpELuHgiYQV7cadtMw9gTOz7PTHSm95qdmlZkCsQkBhjq1pCEjh5g-kM=@protonmail.com> Hello Serban, I have been unable to get libraries/atlas to build on Slackware 15.0.? See here: https://www.linuxquestions.org/questions/slackware-14/when-will-https-slackbuilds-org-have-15-0-in-their-repos-4175708745/page3.html#post6335004 https://www.linuxquestions.org/questions/slackware-14/when-will-https-slackbuilds-org-have-15-0-in-their-repos-4175708745/page11.html#post6335871 Do you still use atlas? Is it ok if I send a pull request to drop atlas and lapack-atlas from SlackBuilds.org? Erich From peter at peter-dambier.de Mon Mar 7 15:06:22 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Mon, 7 Mar 2022 16:06:22 +0100 Subject: [Slackbuilds-users] SlackBuild 15.0 Office/scribus-1.5.8-x86_64-1_SBo.tgz Message-ID: <20220307160622.44115f55.peter@peter-dambier.de> Hi fellow SlackBuilders, with QT5, scribus-1.4.6.tar.xz no longer builds, nor does scribus-1.4.7.tar.xz But scribus-1.5.8.tar.xz does. It is development but it is meant for QT5 pcmanfm finds it under Graphics. It seems to be working. It takes its time loading - no wonder with so many libraries. ldd /usr/bin/scribus: linux-vdso.so.1 libcairo.so.2 libQt5Xml.so.5 libQt5Network.so.5 libQt5OpenGL.so.5 libQt5PrintSupport.so.5 libz.so.1 libxml2.so.2 libcups.so.2 libfreetype.so.6 libharfbuzz-icu.so.0 libharfbuzz.so.0 libharfbuzz-subset.so.0 libicuuc.so.69 libicudata.so.69 libtiff.so.5 libpng16.so.16 libjpeg.so.62 libfontconfig.so.1 libdl.so.2 liblcms2.so.2 libQt5Widgets.so.5 libQt5Gui.so.5 libQt5Core.so.5 libstdc++.so.6 libm.so.6 libgcc_s.so.1 libc.so.6 libpthread.so.0 libpixman-1.so.0 libEGL.so.1 libxcb-shm.so.0 libxcb.so.1 libxcb-render.so.0 libXrender.so.1 libX11.so.6 libXext.so.6 libGL.so.1 librt.so.1 libgssapi_krb5.so.2 libssl.so.1.1 libcrypto.so.1.1 liblzma.so.5 libkrb5.so.3 libk5crypto.so.3 libcom_err.so.2 libgnutls.so.30 libcrypt.so.1 libbz2.so.1 libbrotlidec.so.1 libgraphite2.so.3 libglib-2.0.so.0 /lib64/ld-linux-x86-64.so.2 libwebp.so.7 libzstd.so.1 libicui18n.so.69 libpcre2-16.so.0 libgthread-2.0.so.0 libGLdispatch.so.0 libXau.so.6 libXdmcp.so.6 libGLX.so.0 libkrb5support.so.0 libkeyutils.so.1 libresolv.so.2 libp11-kit.so.0 libidn2.so.0 libunistring.so.2 libnettle.so.8 libhogweed.so.6 libgmp.so.10 libbrotlicommon.so.1 libpcre.so.1 libffi.so.7 From erich.public at protonmail.com Mon Mar 7 17:19:14 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 07 Mar 2022 17:19:14 +0000 Subject: [Slackbuilds-users] libraries/atlas fails to build on Slackware 15.0 In-Reply-To: References: <14960LVPWatuFHXXZQnuvbOdsjfvriuHTs6JUjcxevoD_ICZu6FcpELuHgiYQV7cadtMw9gTOz7PTHSm95qdmlZkCsQkBhjq1pCEjh5g-kM=@protonmail.com> Message-ID: ------- Original Message ------- On Monday, March 7th, 2022 at 10:45 AM, Serban Udrea wrote: > On 3/7/22 3:25 PM, Erich Ritz wrote: > > > Hello Serban, > > > > I have been unable to get libraries/atlas to build on Slackware 15.0. See here: > > > > https://www.linuxquestions.org/questions/slackware-14/when-will-https-slackbuilds-org-have-15-0-in-their-repos-4175708745/page3.html#post6335004 > > > > https://www.linuxquestions.org/questions/slackware-14/when-will-https-slackbuilds-org-have-15-0-in-their-repos-4175708745/page11.html#post6335871 > > > > Do you still use atlas? Is it ok if I send a pull request to drop atlas and lapack-atlas from SlackBuilds.org? > > > > Erich > > Hello Erich, > > And thank you for the information. I didn't expect it to compile since nothing > happened for a long time upstream and ATLAS is quite sensitive to compiler > versions. Thus my plan was to take it over to Slackware 15.0 just if it compiles > on the first try. This doesn't seem to be the case. For now OpenBLAS appears to be > the best open source option. > > If a new ATLAS version gets released in the future I might update the scripts for > it and the corresponding LAPACK. For now you may drop them. Thanks again! > > Best regards, > Serban > > PS. I started to work on my scripts to upgrade everything for Slackware 15.0 but > progress was very slow until now and ATLAS had the lowest priority since numpy for > instance is OK with OpenBLAS. Thanks Serban, I will send a pull request to drop them. Erich From willysr at slackbuilds.org Mon Mar 7 17:25:39 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 8 Mar 2022 00:25:39 +0700 Subject: [Slackbuilds-users] libraries/atlas fails to build on Slackware 15.0 In-Reply-To: References: <14960LVPWatuFHXXZQnuvbOdsjfvriuHTs6JUjcxevoD_ICZu6FcpELuHgiYQV7cadtMw9gTOz7PTHSm95qdmlZkCsQkBhjq1pCEjh5g-kM=@protonmail.com> Message-ID: <39bdeff4-3c94-e652-be40-48b83f5eda4a@slackbuilds.org> > I will send a pull request to drop them. I have removed them in my branch already -- 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 peter at peter-dambier.de Mon Mar 7 17:54:08 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Mon, 7 Mar 2022 18:54:08 +0100 Subject: [Slackbuilds-users] Failed to build on Slackware 15:0 Message-ID: <20220307185408.52e246b8.peter@peter-dambier.de> Hi fellow SlackBuilders, these did not build on Slackware 15.0 gnulib shot its own foot when upgrading glibc - killing lots of gnu software. The gnu fellows have taken notice. Time will heal it. gcc-11 does not understand gcc-5 programmes and glibc not compatible with older version. That is why BSD is Clang LLVM not GCC. QT4 programmes not yet ported to QT5. Gnome is always a good reason for programmes to break, libgnome ... I am glad the list is quite short but other SlackBuilds do depend on some of these. Here comes the list. Cheers Peter -------------- next part -------------- /* SlackBuilds not building on 15.0 */ Desktop/gsimplecal/gsimplecal.SlackBuild Desktop/maitreya/maitreya.SlackBuild Development/qt-creator/qt-creator.SlackBuild Ham/xdemorse/xdemorse.SlackBuild Ham/xfhell/xfhell.SlackBuild Ham/xnec2c/xnec2c.SlackBuild Libraries/libquicktime/libquicktime.SlackBuild Libraries/podofo/podofo.SlackBuild Libraries/webkitgtk/webkitgtk.SlackBuild Libraries/webkitgtk3/webkitgtk3.SlackBuild Office/evince/evince.SlackBuild Office/gcal/gcal.SlackBuild Office/qpdfview/qpdfview.SlackBuild System/gnome-vfs/gnome-vfs.SlackBuild /' END */ From yalhcru at gmail.com Mon Mar 7 18:18:55 2022 From: yalhcru at gmail.com (B Watson) Date: Mon, 7 Mar 2022 13:18:55 -0500 Subject: [Slackbuilds-users] Failed to build on Slackware 15:0 In-Reply-To: <20220307185408.52e246b8.peter@peter-dambier.de> References: <20220307185408.52e246b8.peter@peter-dambier.de> Message-ID: On 3/7/22, Peter Dambier wrote: > Hi fellow SlackBuilders, > > these did not build on Slackware 15.0 Thanks for the effort, but... it looks like you're trying to run scripts from the 14.2 repo on 15.0 (you've listed webkitgtk and webkitgtk3 for instance, these have been removed already). You should be using the master branch from our git repository. It contains all the work we've done to get things ready for 15.0, and it will become the 15.0 repository when it's complete (should be pretty soon now). From duncan_roe at optusnet.com.au Mon Mar 7 22:47:32 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Tue, 8 Mar 2022 09:47:32 +1100 Subject: [Slackbuilds-users] lxml SlackBuild needs to be newer version In-Reply-To: <8a10faf0-82af-3086-ec72-a708c72260b3@slackbuilds.org> References: <8a10faf0-82af-3086-ec72-a708c72260b3@slackbuilds.org> Message-ID: On Mon, Mar 07, 2022 at 07:25:48PM +0700, Willy Sudiarto Raharjo wrote: > > just be sure that the newer lxml doesn't break anything depending on lxml... > > I hope the changes listed here > (https://github.com/lxml/lxml/blob/master/CHANGES.txt) are not that > invasive to other projects > They LGTM. w.r.t. 4.7.1: > Wheels include libxml2 2.9.12+ and libxslt 1.1.34 15.0 ships libxml2.so.2.9.12 and libxslt.so.1.1.34 Cheers ... Duncan. From artourter at gmail.com Tue Mar 8 00:26:03 2022 From: artourter at gmail.com (Greg' Ar Tourter) Date: Tue, 8 Mar 2022 00:26:03 +0000 Subject: [Slackbuilds-users] SlackBuild 15.0 Office/scribus-1.5.8-x86_64-1_SBo.tgz In-Reply-To: <20220307160622.44115f55.peter@peter-dambier.de> References: <20220307160622.44115f55.peter@peter-dambier.de> Message-ID: I am afraid you are still using the 14.2 tree rather than the git master branch which is the 15.0 working tree. Scribus has been updated to the 1.5.x version which is QT5 based about a year ago and the version currently in the master branch is 1.5.7 from November last year. https://git.slackbuilds.org/slackbuilds/log/?qt=grep&q=scribus Greg On Mon, 7 Mar 2022 at 15:06, Peter Dambier wrote: > Hi fellow SlackBuilders, > > with QT5, scribus-1.4.6.tar.xz no longer builds, nor does > scribus-1.4.7.tar.xz > > But scribus-1.5.8.tar.xz does. It is development but it is meant for QT5 > > pcmanfm finds it under Graphics. > It seems to be working. > It takes its time loading - no wonder with so many libraries. > > ldd /usr/bin/scribus: > > linux-vdso.so.1 > libcairo.so.2 > libQt5Xml.so.5 > libQt5Network.so.5 > libQt5OpenGL.so.5 > libQt5PrintSupport.so.5 > libz.so.1 > libxml2.so.2 > libcups.so.2 > libfreetype.so.6 > libharfbuzz-icu.so.0 > libharfbuzz.so.0 > libharfbuzz-subset.so.0 > libicuuc.so.69 > libicudata.so.69 > libtiff.so.5 > libpng16.so.16 > libjpeg.so.62 > libfontconfig.so.1 > libdl.so.2 > liblcms2.so.2 > libQt5Widgets.so.5 > libQt5Gui.so.5 > libQt5Core.so.5 > libstdc++.so.6 > libm.so.6 > libgcc_s.so.1 > libc.so.6 > libpthread.so.0 > libpixman-1.so.0 > libEGL.so.1 > libxcb-shm.so.0 > libxcb.so.1 > libxcb-render.so.0 > libXrender.so.1 > libX11.so.6 > libXext.so.6 > libGL.so.1 > librt.so.1 > libgssapi_krb5.so.2 > libssl.so.1.1 > libcrypto.so.1.1 > liblzma.so.5 > libkrb5.so.3 > libk5crypto.so.3 > libcom_err.so.2 > libgnutls.so.30 > libcrypt.so.1 > libbz2.so.1 > libbrotlidec.so.1 > libgraphite2.so.3 > libglib-2.0.so.0 > /lib64/ld-linux-x86-64.so.2 > libwebp.so.7 > libzstd.so.1 > libicui18n.so.69 > libpcre2-16.so.0 > libgthread-2.0.so.0 > libGLdispatch.so.0 > libXau.so.6 > libXdmcp.so.6 > libGLX.so.0 > libkrb5support.so.0 > libkeyutils.so.1 > libresolv.so.2 > libp11-kit.so.0 > libidn2.so.0 > libunistring.so.2 > libnettle.so.8 > libhogweed.so.6 > libgmp.so.10 > libbrotlicommon.so.1 > libpcre.so.1 > libffi.so.7 > _______________________________________________ > 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 lenardrspencer at gmail.com Tue Mar 8 01:33:42 2022 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Mon, 7 Mar 2022 20:33:42 -0500 Subject: [Slackbuilds-users] openjdk7 Message-ID: Here is the patch for openjdk7 to build under 15.0. I have openjdk6 running as well, but since it has been dropped, I won't bother with that one (for now). -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: openjdk7.diff Type: text/x-patch Size: 7728 bytes Desc: not available URL: From andrew.clemons at gmail.com Tue Mar 8 09:04:48 2022 From: andrew.clemons at gmail.com (Andrew Clemons) Date: Tue, 8 Mar 2022 22:04:48 +1300 Subject: [Slackbuilds-users] openjdk7 In-Reply-To: References: Message-ID: <8fc975a1-26fe-076b-a11c-78381edd0cb8@gmail.com> On 8/03/22 14:33, Lenard Spencer wrote: > Here is the patch for openjdk7 to build under 15.0.? I have openjdk6 > running as well, but since it has been dropped, I won't bother with that > one (for now). Hi Lenard, I replied in the other thread, but I've pulled in your patches and resurrected openjdk6 with you as maintainer. You can find this on the master branch now. Thanks, Andrew From peter at peter-dambier.de Tue Mar 8 09:54:35 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Tue, 8 Mar 2022 10:54:35 +0100 Subject: [Slackbuilds-users] Thankyou: SlackBuild 15.0 Office/scribus-1.5.8-x86_64-1_SBo.tgz In-Reply-To: References: <20220307160622.44115f55.peter@peter-dambier.de> Message-ID: <20220308105435.5b250889.peter@peter-dambier.de> On Tue, 8 Mar 2022 00:26:03 +0000 "Greg' Ar Tourter" wrote: > I am afraid you are still using the 14.2 tree rather than the git > master branch which is the 15.0 working tree. Scribus has been > updated to the 1.5.x version which is QT5 based about a year ago and > the version currently in the master branch is 1.5.7 from November > last year. > > https://git.slackbuilds.org/slackbuilds/log/?qt=grep&q=scribus > > Greg Thankyou for the info, Greg. Yes I was on the old one. Peter > > On Mon, 7 Mar 2022 at 15:06, Peter Dambier > wrote: > > > Hi fellow SlackBuilders, > > > > with QT5, scribus-1.4.6.tar.xz no longer builds, nor does > > scribus-1.4.7.tar.xz > > > > But scribus-1.5.8.tar.xz does. It is development but it is meant > > for QT5 > > > > pcmanfm finds it under Graphics. > > It seems to be working. > > It takes its time loading - no wonder with so many libraries. > > > > ldd /usr/bin/scribus: > > > > linux-vdso.so.1 > > libcairo.so.2 > > libQt5Xml.so.5 > > libQt5Network.so.5 > > libQt5OpenGL.so.5 > > libQt5PrintSupport.so.5 > > libz.so.1 > > libxml2.so.2 > > libcups.so.2 > > libfreetype.so.6 > > libharfbuzz-icu.so.0 > > libharfbuzz.so.0 > > libharfbuzz-subset.so.0 > > libicuuc.so.69 > > libicudata.so.69 > > libtiff.so.5 > > libpng16.so.16 > > libjpeg.so.62 > > libfontconfig.so.1 > > libdl.so.2 > > liblcms2.so.2 > > libQt5Widgets.so.5 > > libQt5Gui.so.5 > > libQt5Core.so.5 > > libstdc++.so.6 > > libm.so.6 > > libgcc_s.so.1 > > libc.so.6 > > libpthread.so.0 > > libpixman-1.so.0 > > libEGL.so.1 > > libxcb-shm.so.0 > > libxcb.so.1 > > libxcb-render.so.0 > > libXrender.so.1 > > libX11.so.6 > > libXext.so.6 > > libGL.so.1 > > librt.so.1 > > libgssapi_krb5.so.2 > > libssl.so.1.1 > > libcrypto.so.1.1 > > liblzma.so.5 > > libkrb5.so.3 > > libk5crypto.so.3 > > libcom_err.so.2 > > libgnutls.so.30 > > libcrypt.so.1 > > libbz2.so.1 > > libbrotlidec.so.1 > > libgraphite2.so.3 > > libglib-2.0.so.0 > > /lib64/ld-linux-x86-64.so.2 > > libwebp.so.7 > > libzstd.so.1 > > libicui18n.so.69 > > libpcre2-16.so.0 > > libgthread-2.0.so.0 > > libGLdispatch.so.0 > > libXau.so.6 > > libXdmcp.so.6 > > libGLX.so.0 > > libkrb5support.so.0 > > libkeyutils.so.1 > > libresolv.so.2 > > libp11-kit.so.0 > > libidn2.so.0 > > libunistring.so.2 > > libnettle.so.8 > > libhogweed.so.6 > > libgmp.so.10 > > libbrotlicommon.so.1 > > libpcre.so.1 > > libffi.so.7 > > _______________________________________________ > > 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 Tue Mar 8 09:58:38 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Tue, 8 Mar 2022 10:58:38 +0100 Subject: [Slackbuilds-users] Thanyou: Failed to build on Slackware 15:0 In-Reply-To: References: <20220307185408.52e246b8.peter@peter-dambier.de> Message-ID: <20220308105838.06a5c27d.peter@peter-dambier.de> On Mon, 7 Mar 2022 13:18:55 -0500 B Watson wrote: > On 3/7/22, Peter Dambier wrote: > > Hi fellow SlackBuilders, > > > > these did not build on Slackware 15.0 > > Thanks for the effort, but... it looks like you're trying to run > scripts from the 14.2 repo on 15.0 (you've listed webkitgtk and > webkitgtk3 for instance, these have been removed already). > > You should be using the master branch from our git repository. It > contains all the work we've done to get things ready for 15.0, and it > will become the 15.0 repository when it's complete (should be pretty > soon now). > Thankyou for the good news. and yes I was on the old one. Peter _______________________________________________ > 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 Tue Mar 8 11:09:15 2022 From: slackbuilds at schoepfer.info (Franzen) Date: Tue, 08 Mar 2022 12:09:15 +0100 Subject: [Slackbuilds-users] squidGuard version bump to fix build on 15.0 Message-ID: <78b89934335135915d23dd7e8d8d0512@schoepfer.info> Hi, not my buildscript. As said in the subject, patch attached. Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: squidGuard.patch Type: text/x-diff Size: 10637 bytes Desc: not available URL: From dickson.tim at googlemail.com Tue Mar 8 14:10:46 2022 From: dickson.tim at googlemail.com (Tim Dickson) Date: Tue, 8 Mar 2022 14:10:46 +0000 Subject: [Slackbuilds-users] epson-printer-utility slackbuild for 15.0 Message-ID: <0b536d71-6652-0f58-3c59-de4124c5070c@googlemail.com> Hi Willy, this can be scrapped for now, rather than holding up re-opening submissions. It might work vaguely with qt4 installed, but in reality it is waiting for epson to update their code to something that works. Regards, Tim -- This email has been checked for viruses by AVG. https://www.avg.com From jebrhansen+SBo at gmail.com Wed Mar 9 02:34:45 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 8 Mar 2022 19:34:45 -0700 Subject: [Slackbuilds-users] Kodi Fix for CEC Message-ID: Matteo, Thanks for catching the downloads that occur as well as the fact that I forgot to remove the build directory (or if you didn't catch them, for at least getting the fix submitted). I did check if crossguid was installed if it would use the system version, and it seems it will not. USUARIONUEVO found another thing I missed. I used LIBCEC as the variable in the cmake and CEC as the variable in the pkg-config detection. Can you please fix it? Attached is a patch, but it just needs the cmake line to have the variable changed from LIBCEC to CEC. I'm going to CC the SBo mailing list, since you're probably in bed right now. Thanks, Jeremy (aka bassmadrigal) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-multimedia-kodi-Fix-CEC-variable.patch Type: text/x-patch Size: 797 bytes Desc: not available URL: From khronosschoty at posteo.org Wed Mar 9 06:16:20 2022 From: khronosschoty at posteo.org (khronosschoty) Date: Wed, 9 Mar 2022 06:16:20 +0000 Subject: [Slackbuilds-users] network/et Message-ID: hi, I was looking over the master branch and saw this: http://git.slackbuilds.org/slackbuilds/commit/?id=59677cfd76fecb1c323dcd37d320bdc87118f588 "network/et: Removed" I was wondering what the reason for this might be? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 870 bytes Desc: not available URL: From dave at slackbuilds.org Wed Mar 9 06:34:29 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 9 Mar 2022 06:34:29 +0000 Subject: [Slackbuilds-users] network/et In-Reply-To: References: Message-ID: <20220309063429.GE30716@localhost> On 09/03/22 06:16, khronosschoty put forth the proposition: > hi, > I was looking over the master branch and saw this: > http://git.slackbuilds.org/slackbuilds/commit/?id=59677cfd76fecb1c323dcd37d320bdc87118f588 > "network/et: Removed" > I was wondering what the reason for this might be? Hi It didn't build in 15.0, and a version couldn't be found that would. But if you do manage to get it to build, let us know and/or send a patch etc. Removals without a reason given will likely be the for the same problem. -- Dave From andrew.david.strong at gmail.com Wed Mar 9 07:26:37 2022 From: andrew.david.strong at gmail.com (andrew) Date: Wed, 9 Mar 2022 18:26:37 +1100 Subject: [Slackbuilds-users] Update wavbreaker (audio) for 15.0 Message-ID: Hi, I picked up wavbreaker some time back: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2021-April/025629.html I have updated the SlackBuild for 15.0, diff taken against latest SBo git. All the best, Andrew Strong -- You think that's air you're breathing now? -------------- next part -------------- diff --git a/audio/wavbreaker/README b/audio/wavbreaker/README index 7ea0c830..0c8cdbac 100644 --- a/audio/wavbreaker/README +++ b/audio/wavbreaker/README @@ -1,11 +1,6 @@ -Wavbreaker is a GTK wave file splitter for Linux and Unix-like operating -systems licensed under the terms of the GNU General Public License. +wavbreaker is an open source WAV and MP3 file splitter. -This application's purpose in life is to take a wave file and break it -up into multiple wave files. It makes a clean break at the correct -position to burn the files to an audio cd without any dead air between -the tracks. It will only read wave files, so use an appropriate tool -such as SoX to convert other filetypes (e.g., ogg, mp3, etc.) and then -break them up. Also included is a command line tool, wavmerge, which -merges wave files together. This tool will only work on files that are -alike. For example, 44100 khz sample rate, 16-bit sample size, etc. +wavbreaker is a GTK gui application which takes WAV or MP3 files and +breaks them up into multiple sections. For MP3 manipulation wavbreaker +uses libmpg123. It also has command line tools which will merge WAV +files (wavmerge) and display format information for WAV files (wavinfo). diff --git a/audio/wavbreaker/slack-desc b/audio/wavbreaker/slack-desc index bcce2cdf..d65f2591 100644 --- a/audio/wavbreaker/slack-desc +++ b/audio/wavbreaker/slack-desc @@ -6,14 +6,14 @@ # customary to leave one space after the ':' except on otherwise blank lines. |-----handy-ruler------------------------------------------------------| -wavbreaker: wavbreaker (wave file splitter) +wavbreaker: wavbreaker (a WAV and MP3 file splitter) wavbreaker: -wavbreaker: This application's purpose in life is to take a wave file and -wavbreaker: break it up into multiple wave files. It makes a clean break -wavbreaker: at the correct position to burn the files to an audio cd -wavbreaker: without any dead air between the tracks. It will only read -wavbreaker: wave files, so use an appropriate tool to convert other file -wavbreaker: types (e.g., ogg, mp3, etc.) and then break them up. There is -wavbreaker: also a command line tool to merge wave files together, -wavbreaker: wavmerge. +wavbreaker: This application takes WAV or MP3 files and breaks them into multiple +wavbreaker: sections. It also has command line tools which will merge WAV files +wavbreaker: (wavmerge) and display format information for WAV files (wavinfo). +wavbreaker: +wavbreaker: +wavbreaker: +wavbreaker: https://wavbreaker.sourceforge.io/ +wavbreaker: wavbreaker: diff --git a/audio/wavbreaker/wavbreaker.SlackBuild b/audio/wavbreaker/wavbreaker.SlackBuild old mode 100644 new mode 100755 index 490ccfb2..d7b80bcf --- a/audio/wavbreaker/wavbreaker.SlackBuild +++ b/audio/wavbreaker/wavbreaker.SlackBuild @@ -3,6 +3,7 @@ # Slackware build script for wavbreaker # Copyright 2013, Josiah Boothby, Seattle +# Copyright 2022 Andrew Strong, Blue Mountains # All rights reserved. # # Redistribution and use of this script, with or without modification, is @@ -25,14 +26,14 @@ cd $(dirname $0) ; CWD=$(pwd) PRGNAM=wavbreaker -VERSION=${VERSION:-0.11} +VERSION=${VERSION:-0.13} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} if [ -z "$ARCH" ]; then case "$( uname -m )" in - i?86) ARCH=i486 ;; + i?86) ARCH=i586 ;; arm*) ARCH=arm ;; *) ARCH=$( uname -m ) ;; esac @@ -50,8 +51,8 @@ TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} -if [ "$ARCH" = "i486" ]; then - SLKCFLAGS="-O2 -march=i486 -mtune=i686" +if [ "$ARCH" = "i586" ]; then + SLKCFLAGS="-O2 -march=i586 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="-O2 -march=i686 -mtune=i686" @@ -79,19 +80,20 @@ find -L . \ \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \ -exec chmod 644 {} \; -CFLAGS="$SLKCFLAGS" \ -CXXFLAGS="$SLKCFLAGS" \ -./configure \ - --prefix=/usr \ - --libdir=/usr/lib${LIBDIRSUFFIX} \ - --sysconfdir=/etc \ - --localstatedir=/var \ - --mandir=/usr/man \ - --docdir=/usr/doc/$PRGNAM-$VERSION \ - --build=$ARCH-slackware-linux - -make -make install DESTDIR=$PKG +mkdir build +cd build + CFLAGS="$SLKCFLAGS" \ + CXXFLAGS="$SLKCFLAGS" \ + meson .. \ + --buildtype=release \ + --libdir=/usr/lib${LIBDIRSUFFIX} \ + --mandir=/usr/man \ + --prefix=/usr + "${NINJA:=ninja}" + DESTDIR=$PKG $NINJA install +cd .. + +rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true @@ -100,20 +102,8 @@ find $PKG/usr/man -type f -exec gzip -9 {} \; for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION -cp -a \ - AUTHORS \ - CONTRIBUTORS \ - COPYING \ - ChangeLog \ - NEWS \ - NOTES \ - README \ - README.PulseAudio \ - TODO \ - $PKG/usr/doc/$PRGNAM-$VERSION +cp -a AUTHORS CONTRIBUTORS COPYING README.md $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild -cat $CWD/slack-desc > $PKG/usr/doc/$PRGNAM-$VERSION/slack-desc -cat $CWD/doinst.sh > $PKG/usr/doc/$PRGNAM-$VERSION/doinst.sh mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc diff --git a/audio/wavbreaker/wavbreaker.info b/audio/wavbreaker/wavbreaker.info index 035b41a9..ae40deff 100644 --- a/audio/wavbreaker/wavbreaker.info +++ b/audio/wavbreaker/wavbreaker.info @@ -1,10 +1,10 @@ PRGNAM="wavbreaker" -VERSION="0.11" +VERSION="0.13" HOMEPAGE="http://wavbreaker.sourceforge.net" -DOWNLOAD="http://downloads.sourceforge.net/wavbreaker/wavbreaker-0.11.tar.gz" -MD5SUM="97f981baa6ca0d4d52b88314defeea4c" +DOWNLOAD="https://github.com/thp/wavbreaker/archive/0.13/wavbreaker-0.13.tar.gz" +MD5SUM="cc32a1afd0b52692a81ce7895b5ee767" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -MAINTAINER="Josiah Boothby" -EMAIL="josiahb at gmail.com" +MAINTAINER="Andrew Strong" +EMAIL="andrew.david.strong at gmail.com" From dave at slackbuilds.org Wed Mar 9 07:53:40 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 9 Mar 2022 07:53:40 +0000 Subject: [Slackbuilds-users] Update wavbreaker (audio) for 15.0 In-Reply-To: References: Message-ID: <20220309075340.GF30716@localhost> On 09/03/22 18:26, andrew put forth the proposition: > Hi, > I picked up wavbreaker some time back: > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2021-April/025629.html > I have updated the SlackBuild for 15.0, diff taken against latest SBo > git. > All the best, > Andrew Strong > -- > You think that's air you're breathing now? Pushed to my branch. Thanks for the update. -- Dave From erich.public at protonmail.com Wed Mar 9 15:01:27 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Wed, 09 Mar 2022 15:01:27 +0000 Subject: [Slackbuilds-users] Setting LD_LIBRARY_PATH for zulu-openjdk11 In-Reply-To: <4zOZ3LqQRPvUtPfdFYe93zUo6GAq5CgYqy9PXOuZtIYyekYYi2GYv4RWfuelm51fHp9VNI8PP9cl2fvf6ehNxkao757a-AjPiSjW2IqVykw=@protonmail.com> References: <4zOZ3LqQRPvUtPfdFYe93zUo6GAq5CgYqy9PXOuZtIYyekYYi2GYv4RWfuelm51fHp9VNI8PP9cl2fvf6ehNxkao757a-AjPiSjW2IqVykw=@protonmail.com> Message-ID: ------- Original Message ------- On Friday, March 4th, 2022 at 11:32 AM, Erich Ritz via SlackBuilds-users wrote: > Hi S?bastien, > > Would you consider adding the patches attached (and also at https://gitlab.com/ErichRitz/slackbuilds/-/commits/zulu-openjdk11) for zulu-openjdk11? > > Currently this is the only thing I have setting LD_LIBRARY_PATH, and it prepends a ":", which in effect also adds "." to my LD_LIBRARY_PATH, which I don't want. This patch first checks if LD_LIBRARY_PATH is empty before setting it to account for this. > > The second patch is fancier and only adds ${JAVA_HOME}/lib/server to LD_LIBRARY_PATH if it doesn't already exist. With my setup contents of /etc/profile.d end up getting sourced more than once. If you don't want to take this patch that's fine. > > The same argument goes for MANPATH as well (patches 3 and 4). > Hi S?bastien, Actually patches 3 and 4 (modifications to setting MANPATH) are not correct - they break man. If MANPATH is defined, it needs a leading or trailing ":" so that /etc/man_db.conf is still used. So the MANPATH setting is already correct. I also discovered that "man" can find the man pages even when MANPATH is unset: $ MANPATH= manpath /usr/local/man:/usr/man:/usr/lib64/zulu-openjdk11/man So perhaps MANPATH doesn't need to be set at all? Erich From yalhcru at gmail.com Wed Mar 9 17:09:37 2022 From: yalhcru at gmail.com (B Watson) Date: Wed, 9 Mar 2022 12:09:37 -0500 Subject: [Slackbuilds-users] epson-printer-utility slackbuild for 15.0 In-Reply-To: <0b536d71-6652-0f58-3c59-de4124c5070c@googlemail.com> References: <0b536d71-6652-0f58-3c59-de4124c5070c@googlemail.com> Message-ID: On 3/8/22, Tim Dickson via SlackBuilds-users wrote: > Hi Willy, this can be scrapped for now, rather than holding up > re-opening submissions. > It might work vaguely with qt4 installed, but in reality it is waiting > for epson to update their code to something that works. I managed to get the thing to compile on 15.0, and was able to at least start the daemon and the GUI, which told me it couldnt't find the printer (since I don't have an epson printer, that was correct). https://git.slackbuilds.org/slackbuilds/commit/?id=2a42a0916ad7d3b7f2cef7eacadefc0d96f0c2fb From dickson.tim at googlemail.com Wed Mar 9 17:52:22 2022 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 9 Mar 2022 17:52:22 +0000 Subject: [Slackbuilds-users] epson-printer-utility slackbuild for 15.0 In-Reply-To: References: <0b536d71-6652-0f58-3c59-de4124c5070c@googlemail.com> Message-ID: thanks B Watson. I'll see if I can test it out with a real printer. What's the best way to get qt4 and it's deps, or can I just wait till submissions are open and then use sbopkg ? If the package went out as is I could test it when sbopkg works with 15.0 :-) Regards, Tim On 09/03/2022 17:09, B Watson wrote: > On 3/8/22, Tim Dickson via SlackBuilds-users > wrote: >> Hi Willy, this can be scrapped for now, rather than holding up >> re-opening submissions. >> It might work vaguely with qt4 installed, but in reality it is waiting >> for epson to update their code to something that works. > I managed to get the thing to compile on 15.0, and was able to at > least start the daemon and the GUI, which told me it couldnt't find > the printer (since I don't have an epson printer, that was correct). > > https://git.slackbuilds.org/slackbuilds/commit/?id=2a42a0916ad7d3b7f2cef7eacadefc0d96f0c2fb > _______________________________________________ > 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/ > -- This email has been checked for viruses by AVG. https://www.avg.com From yalhcru at gmail.com Wed Mar 9 18:07:21 2022 From: yalhcru at gmail.com (B Watson) Date: Wed, 9 Mar 2022 13:07:21 -0500 Subject: [Slackbuilds-users] epson-printer-utility slackbuild for 15.0 In-Reply-To: References: <0b536d71-6652-0f58-3c59-de4124c5070c@googlemail.com> Message-ID: On 3/9/22, Tim Dickson via SlackBuilds-users wrote: > thanks B Watson. I'll see if I can test it out with a real printer. > What's the best way to get qt4 and it's deps, or can I just wait till > submissions are open and then use sbopkg ? The way I would do it would be to git clone the repo, then manually cd into the directories, download the stuff listed in the .info files, run the slackbuild scripts. If you want to use sbopkg, it can be configured to use git master. I can't give you directions (I don't use sbopkg), but I know people on IRC have explained it to each other a few times. > If the package went out as is I could test it when sbopkg works with > 15.0 :-) That's an option, too. Hopefully we aren't too far away from that happening... From willysr at slackbuilds.org Thu Mar 10 04:04:05 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 10 Mar 2022 11:04:05 +0700 Subject: [Slackbuilds-users] squidGuard version bump to fix build on 15.0 In-Reply-To: <78b89934335135915d23dd7e8d8d0512@schoepfer.info> References: <78b89934335135915d23dd7e8d8d0512@schoepfer.info> Message-ID: <0fb43e06-2c49-3c7b-3c1b-0ca60714e782@slackbuilds.org> > not my buildscript. As said in the subject, patch attached. As we have no maintainer, it's best to keep it removed until someone wants to step up as maintainer for this script. -- 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 rshepard at appl-ecosys.com Thu Mar 10 19:26:07 2022 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 10 Mar 2022 11:26:07 -0800 (PST) Subject: [Slackbuilds-users] Is there a gnucash*.sbo for 15.0? Message-ID: <56c5c368-a67f-5b3e-5a19-f27c5e6118da@appl-ecosys.com> Is there a Gnucash available for 15.0? I don't know where to look other than the SBo web repos. Rich From slackbuilds at schoepfer.info Thu Mar 10 19:49:13 2022 From: slackbuilds at schoepfer.info (Franzen) Date: Thu, 10 Mar 2022 20:49:13 +0100 Subject: [Slackbuilds-users] squidGuard version bump to fix build on 15.0 In-Reply-To: <0fb43e06-2c49-3c7b-3c1b-0ca60714e782@slackbuilds.org> References: <78b89934335135915d23dd7e8d8d0512@schoepfer.info> <0fb43e06-2c49-3c7b-3c1b-0ca60714e782@slackbuilds.org> Message-ID: On 2022-03-10 05:04, Willy Sudiarto Raharjo wrote: >> not my buildscript. As said in the subject, patch attached. > > As we have no maintainer, it's best to keep it removed until someone > wants to step up as maintainer for this script. How about keep it removed, put apply the patch anyway. That way someone who takes over has a working script, as the work has already be done. Johannes From heiko.rosemann at web.de Thu Mar 10 19:50:20 2022 From: heiko.rosemann at web.de (Heiko Rosemann) Date: Thu, 10 Mar 2022 20:50:20 +0100 Subject: [Slackbuilds-users] Is there a gnucash*.sbo for 15.0? In-Reply-To: <56c5c368-a67f-5b3e-5a19-f27c5e6118da@appl-ecosys.com> References: <56c5c368-a67f-5b3e-5a19-f27c5e6118da@appl-ecosys.com> Message-ID: Rich, yes, there is - from the git master: https://git.slackbuilds.org/slackbuilds/tree/office/gnucash The content of that repo will become the 15.0 web repo when it's ready. I can confirm that gnucash from that repo works on 15.0 (and also updating it to 4.9 works when you remove the Changelog file from the documentation copy line). Heiko On 3/10/22 20:26, Rich Shepard wrote: > Is there a Gnucash available for 15.0? > > I don't know where to look other than the SBo web repos. > > 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/ > -- eMails verschl?sseln mit PGP - privacy is your right! Mein PGP-Key zur Verifizierung: http://pgp.mit.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Thu Mar 10 20:32:35 2022 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 10 Mar 2022 12:32:35 -0800 (PST) Subject: [Slackbuilds-users] Is there a gnucash*.sbo for 15.0? In-Reply-To: References: <56c5c368-a67f-5b3e-5a19-f27c5e6118da@appl-ecosys.com> Message-ID: On Thu, 10 Mar 2022, Heiko Rosemann wrote: > yes, there is - from the git master: > https://git.slackbuilds.org/slackbuilds/tree/office/gnucash > > The content of that repo will become the 15.0 web repo when it's ready. > > I can confirm that gnucash from that repo works on 15.0 (and also updating it > to 4.9 works when you remove the Changelog file from the documentation copy > line). Heiko, Thanks! Rich From peter at peter-dambier.de Fri Mar 11 18:25:58 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Fri, 11 Mar 2022 19:25:58 +0100 Subject: [Slackbuilds-users] Libraries podofo-0.9.6-x86_64-1 successfully built Message-ID: <20220311192558.55a082d0.peter@peter-dambier.de> Hi fellow SlackBuilders successfully built and installed podofo-0.9.6-x86_64-1_SBo.tgz When reporting my faillure I was in the 14.2 tree. Cheers Peter From peter at peter-dambier.de Fri Mar 11 19:36:28 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Fri, 11 Mar 2022 20:36:28 +0100 Subject: [Slackbuilds-users] Libraries libquicktime-1.2.4-x86_64-4 successfully built Message-ID: <20220311203628.41d9c2ef.peter@peter-dambier.de> Hi fellow SlackBuilders, successfully built and installed libquicktime-1.2.4-x86_64-4_SBo.tgz When reporting my failure I was on the 14.2 tree. Cheers Peter From peter at peter-dambier.de Fri Mar 11 20:05:07 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Fri, 11 Mar 2022 21:05:07 +0100 Subject: [Slackbuilds-users] Please ignore: Failed to build on Slackware 15:0 In-Reply-To: <20220307185408.52e246b8.peter@peter-dambier.de> References: <20220307185408.52e246b8.peter@peter-dambier.de> Message-ID: <20220311210507.62421dfa.peter@peter-dambier.de> I was on the old 14.2 tree. I'll report on the files separately. So far they do build and I need them. Thank you for telling my the right tree and sorry for the noise. Cheers Peter From peter at peter-dambier.de Sat Mar 12 04:32:02 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Sat, 12 Mar 2022 05:32:02 +0100 Subject: [Slackbuilds-users] Office evince-41.3-x86_64-1 succes Message-ID: <20220312053202.5db0e9e6.peter@peter-dambier.de> Hi fellow SlackBuilders, successfully built and installed evince-41.3-x86_64-1_SBo.tgz Cheers Peter From JimDiamond at ns.sympatico.ca Fri Mar 11 18:35:29 2022 From: JimDiamond at ns.sympatico.ca (Jim Diamond) Date: Fri, 11 Mar 2022 14:35:29 -0400 Subject: [Slackbuilds-users] Libraries podofo-0.9.6-x86_64-1 successfully built In-Reply-To: <20220311192558.55a082d0.peter@peter-dambier.de> References: <20220311192558.55a082d0.peter@peter-dambier.de> Message-ID: On Fri, Mar 11, 2022 at 19:25 (+0100), Peter Dambier wrot:e > Hi fellow SlackBuilders > successfully built and installed podofo-0.9.6-x86_64-1_SBo.tgz > When reporting my faillure I was in the 14.2 tree. Hi Peter, I see 0.9.7 is out. Flush with success at 0.9.6, have you thought about 0.9.7? Cheers. Jim From peter at peter-dambier.de Sat Mar 12 09:07:31 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Sat, 12 Mar 2022 10:07:31 +0100 Subject: [Slackbuilds-users] Libraries podofo-0.9.6-x86_64-1 successfully built In-Reply-To: References: <20220311192558.55a082d0.peter@peter-dambier.de> Message-ID: <20220312100731.0c3311eb.peter@peter-dambier.de> On Fri, 11 Mar 2022 14:35:29 -0400 Jim Diamond wrote: > On Fri, Mar 11, 2022 at 19:25 (+0100), Peter Dambier wrot:e > > > Hi fellow SlackBuilders > > > successfully built and installed podofo-0.9.6-x86_64-1_SBo.tgz > > > When reporting my faillure I was in the 14.2 tree. > > Hi Peter, > > I see 0.9.7 is out. Flush with success at 0.9.6, have you thought > about 0.9.7? > > Cheers. > Jim > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > Hi Jim, I am not the maintainer. In the podofo.SlackBuild change "***-0.9.6***" to "***-0.9.7***" and give it a try. But there is no warranty :) When stuff is depending on other stuff then unexpected things might happen. That is what keeps the maintainers busy. Cheers Peter From peter at peter-dambier.de Sat Mar 12 12:52:23 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Sat, 12 Mar 2022 13:52:23 +0100 Subject: [Slackbuilds-users] Office qpdfview-0.4.18-x86_64-1 success Message-ID: <20220312135223.00250c7a.peter@peter-dambier.de> Hi fellow SlackBuilders, successfully built and installed qpdfview-0.4.18-x86_64-1_SBo.tgz Cheers Peter From willysr at slackbuilds.org Sat Mar 12 14:56:42 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 12 Mar 2022 21:56:42 +0700 Subject: [Slackbuilds-users] Slackbuilds Repository for Slackware 15.0 Message-ID: It's now official!!! SlackBuilds Repository 15.0 is available to the public It's been a long journey but we finally made it!!! We are 1 month late from Slackware 15.0 release, but taking care of 8000+ scripts in SBo plus six years of changes from Slackware 14.2 into 15.0 was not a trivial thing. Good thing we have a great community that helped us to finish the job. Big thanks to everyone who helped during this development cycle. We ended up with more than 9k commits since last April 2021 when we froze the 14.2 branch. Many scripts were dropped but many new ones were added along the way. We also updated our template during this cycle; please have a look on https://slackbuilds.org/templates/ for future submissions. On this great moment, i would like to welcome our newest admin, Andrew Clemons (aclemons) who really helped us with his build system to track build failures in our scripts. We will keep using github and gitlab to accept pull requests and merge requests for updates only. New submission should go into normal submission form which will be opened soon (we deserve a break). Happy Slacking and Building :) -- 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 rshepard at appl-ecosys.com Sat Mar 12 15:12:28 2022 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 12 Mar 2022 07:12:28 -0800 (PST) Subject: [Slackbuilds-users] Slackbuilds Repository for Slackware 15.0 In-Reply-To: References: Message-ID: <704133-908e-4049-824b-b18e60eaa74f@appl-ecosys.com> On Sat, 12 Mar 2022, Willy Sudiarto Raharjo wrote: > It's now official!!! > SlackBuilds Repository 15.0 is available to the public Kudos and my thanks to everyone who devoted a lot of time and effort to reach this point. As an end user who has run his professional services consultantcy on Slackware since 2003 I am grateful to everyone who makes it possible. Stay healthy and prosper, Rich From JimDiamond at ns.sympatico.ca Sat Mar 12 17:05:47 2022 From: JimDiamond at ns.sympatico.ca (Jim Diamond) Date: Sat, 12 Mar 2022 13:05:47 -0400 Subject: [Slackbuilds-users] Libraries podofo-0.9.6-x86_64-1 successfully built In-Reply-To: <20220312100731.0c3311eb.peter@peter-dambier.de> References: <20220311192558.55a082d0.peter@peter-dambier.de> <20220312100731.0c3311eb.peter@peter-dambier.de> Message-ID: Hi Peter, On Sat, Mar 12, 2022 at 10:07 (+0100), Peter Dambier wrote: > On Fri, 11 Mar 2022 14:35:29 -0400 > Jim Diamond wrote: >> On Fri, Mar 11, 2022 at 19:25 (+0100), Peter Dambier wrot:e >>> Hi fellow SlackBuilders >>> successfully built and installed podofo-0.9.6-x86_64-1_SBo.tgz >>> When reporting my faillure I was in the 14.2 tree. >> Hi Peter, >> I see 0.9.7 is out. Flush with success at 0.9.6, have you thought >> about 0.9.7? > Hi Jim, > I am not the maintainer. Sorry, my bad. I should have looked before sending that email to you. Jim From rsamurti at gmail.com Sat Mar 12 17:11:28 2022 From: rsamurti at gmail.com (Ananda Murthy) Date: Sat, 12 Mar 2022 22:41:28 +0530 Subject: [Slackbuilds-users] Please remove TexText-0.4.4 from the Slackware-15.0 repository. Message-ID: Hello, This version does not work with Inkscape 1.1.2. Thank you, R S Ananda Murthy -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Sat Mar 12 17:31:55 2022 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 12 Mar 2022 18:31:55 +0100 Subject: [Slackbuilds-users] Please remove TexText-0.4.4 from the Slackware-15.0 repository. In-Reply-To: References: Message-ID: <04d42ccb10879d4ffc8a6a04b6f9654d@schoepfer.info> On 2022-03-12 18:11, Ananda Murthy wrote: > Hello, > > This version does not work with Inkscape 1.1.2. Have you tried you tried a newer version from here https://github.com/textext/textext ? From didier at slint.fr Sat Mar 12 17:51:56 2022 From: didier at slint.fr (Didier Spaier) Date: Sat, 12 Mar 2022 18:51:56 +0100 Subject: [Slackbuilds-users] Slackbuilds Repository for Slackware 15.0 In-Reply-To: References: Message-ID: Sincere congratulations to the admins and maintainers, and to all who contributed. Thanks all!!! Didier Le 12/03/2022 ? 15:56, Willy Sudiarto Raharjo a ?crit?: > It's now official!!! > SlackBuilds Repository 15.0 is available to the public > > It's been a long journey but we finally made it!!! > We are 1 month late from Slackware 15.0 release, but taking care of > 8000+ scripts in SBo plus six years of changes from Slackware 14.2 into > 15.0 was not a trivial thing. Good thing we have a great community that > helped us to finish the job. Big thanks to everyone who helped during > this development cycle. We ended up with more than 9k commits since last > April 2021 when we froze the 14.2 branch. Many scripts were dropped but > many new ones were added along the way. > > We also updated our template during this cycle; please have a look on > https://slackbuilds.org/templates/ for future submissions. > > On this great moment, i would like to welcome our newest admin, Andrew > Clemons (aclemons) who really helped us with his build system to track > build failures in our scripts. > > We will keep using github and gitlab to accept pull requests and merge > requests for updates only. New submission should go into normal > submission form which will be opened soon (we deserve a break). > > Happy Slacking and Building :) > > > > _______________________________________________ > 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 exched at yandex.ru Sat Mar 12 22:12:09 2022 From: exched at yandex.ru (Ched Ex) Date: Sun, 13 Mar 2022 01:12:09 +0300 Subject: [Slackbuilds-users] Branch 15.0 PGP problems Message-ID: <52841647122989@mail.yandex.ru> An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sat Mar 12 22:56:49 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 12 Mar 2022 15:56:49 -0700 Subject: [Slackbuilds-users] Branch 15.0 PGP problems In-Reply-To: <52841647122989@mail.yandex.ru> References: <52841647122989@mail.yandex.ru> Message-ID: I guess this is the same problem that I am observing when using sbopkg: # sbopkg -ki reduce-algebra.sqf GPG check FAILED! Say (Y)es if you want keep the reduce-algebra directory and tarball and continue with the build process, or (N)o to delete the reduce-algebra directory and tarball (all local changes to reduce-algebra and its files will be lost), or (A)bort to stop the build process without deleting anything. (Y)es, (N)o, (A)bort?: On Sat, Mar 12, 2022 at 3:12 PM Ched Ex wrote: > Hello. > There is a problem with PGP signature for packed SB scripts at 15.0 branch. > e.g.: > Downloaded from https://slackbuilds.org/slackbuilds/15.0/development/ > $ gpg --verify 4th.tar.gz.asc > gpg: assuming signed data in `4th.tar.gz' > gpg: Signature made Sat 12 Mar 2022 07:26:07 AM MSK using DSA key ID > 9C7BA3B6 > gpg: BAD signature from "SlackBuilds.org Development Team < > slackbuilds-devel at slackbuilds.org>" > > If download from https://slackbuilds.org/slackbuilds/14.2/development/ > $ gpg --verify 4th.tar.gz.asc > gpg: assuming signed data in `4th.tar.gz' > gpg: Signature made Sat 17 Oct 2020 05:51:08 AM MSK using DSA key ID > 9C7BA3B6 > gpg: Good signature from "SlackBuilds.org Development Team < > slackbuilds-devel at slackbuilds.org>" > > Sincerely, > Ched. > > _______________________________________________ > 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 rsamurti at gmail.com Sun Mar 13 05:00:43 2022 From: rsamurti at gmail.com (Ananda Murthy) Date: Sun, 13 Mar 2022 10:30:43 +0530 Subject: [Slackbuilds-users] Please remove TexText-0.4.4 from the Slackware-15.0 repository. In-Reply-To: <04d42ccb10879d4ffc8a6a04b6f9654d@schoepfer.info> References: <04d42ccb10879d4ffc8a6a04b6f9654d@schoepfer.info> Message-ID: Yes. It works perfectly. On Sat, Mar 12, 2022 at 11:02 PM Franzen via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > On 2022-03-12 18:11, Ananda Murthy wrote: > > Hello, > > > > This version does not work with Inkscape 1.1.2. > > Have you tried you tried a newer version from here > https://github.com/textext/textext ? > > _______________________________________________ > 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/ > > -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.coldplayer at gmail.com Sun Mar 13 09:33:53 2022 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Sun, 13 Mar 2022 13:33:53 +0400 Subject: [Slackbuilds-users] Please remove TexText-0.4.4 from the Slackware-15.0 repository. In-Reply-To: References: <04d42ccb10879d4ffc8a6a04b6f9654d@schoepfer.info> Message-ID: Hi, did you mean this version https://github.com/textext/textext/releases/tag/1.8.1 ?? On Sun, 13 Mar 2022 at 09:01, Ananda Murthy wrote: > Yes. It works perfectly. > > On Sat, Mar 12, 2022 at 11:02 PM Franzen via SlackBuilds-users < > slackbuilds-users at slackbuilds.org> wrote: > >> On 2022-03-12 18:11, Ananda Murthy wrote: >> > Hello, >> > >> > This version does not work with Inkscape 1.1.2. >> >> Have you tried you tried a newer version from here >> https://github.com/textext/textext ? >> >> _______________________________________________ >> 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/ >> >> > > -- > > > Close Windows ! Open source !! > Free software from proprietary mafia !!! > _______________________________________________ > 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 dchmelik at gmail.com Sun Mar 13 10:11:27 2022 From: dchmelik at gmail.com (David Chmelik) Date: Sun, 13 Mar 2022 03:11:27 -0700 Subject: [Slackbuilds-users] mathics/dependencies (mpmath, python-django-legacy) Message-ID: <156a4289-06e5-d004-6265-3e48b67f2f38@gmail.com> I immediately drop mpath, python-django-legacy: now unneeded for mathics. ??? Seems only documented way to install is pip, which doesn't seem to work in SlackBuilds, and since you can install it yourself w/pip, I may drop mathics unless its programmers/developers/engineers finish instructions.? They write you can install it from GitHub, but it's undocumented, and they admit the documentation is unfinished. ??? Their main repository says it's 'now "mostly" in archive' and link a new one, Mathics3--which is actually Mathics 4--and a new one with more stuff, mathicsomnibus (which would be the one I use, but this is all getting rather confusing/obscure.) From dchmelik at gmail.com Sun Mar 13 11:10:29 2022 From: dchmelik at gmail.com (David Chmelik) Date: Sun, 13 Mar 2022 04:10:29 -0700 Subject: [Slackbuilds-users] rogue(like) & Lord of The Rings games SlackBuilds updates: angband, larn, rogue, stone_soup, tome-ah Message-ID: I updated five rogue(like) (fantasy roleplaying-like) games SlackBuilds: angband, larn, rogue, stone_soup, tome-ah, downloadable at http://davidchmelik.com/math/slackbuilds/games/ (source code elsewhere, linked in each SlackBuild.info... I'm pretty sure I updated all URLs & md5sums but occasionally forgot in past.) ??? One is classic Rogue itself, after fixing ISRUN bug it always had (after you slept, actually made monsters have bonuses to hit you entire game, so rogue was always more difficult than intended.) ??? One is Dungeon Crawl: Stone Soup which I might give up: I prefer classic versions (w/plain elves, etc.) or alternative compilation options on stable version (I might add later.) ??? Another is main Troubles/Tales of Middle-earth 2 fork (normally named tome2 but newer & unrelated tome4, now tome, SlackBuild maintained by Dimitris, redid version numbering, approaching 2) renamed tome-ah.? In case you don't know, Moria (based on JRR Tolkien's /The Hobbit/ & /Lord of The Rings/, LoTR) was forked to become Angband (adding colour, more monsters/bosses) was forked to become ZAngband (adding wilderness/towns map) was forked to become PernAngband (added dragonriding) which after copyright issue (but still available on Swedish/SUNET FTP servers) was renamed Troubles/Tales of Middle-earth and replaced random wilderness/towns with map of Tolkien's Middle-earth, and is one of the most amazing roguelikes ever created.? I'd compare it to the great old Advanced Dungeons & Dragons (D&D which AD&D was backwards-compatible, and AD&D second edition was also, after which TSR/WoTC started removing things and D&D wasn't as good, sort of like chess variants might be novelties but not standard.)? There is also TomeNet, based on multiplayer angband (MAngband, but you can download a TomeNet client from tomenet.eu ... there also was PernMAngband and there are dozens Angband variants and several Mangband ones.) ??? InterHack (ihack) was multiplayer NetHack (I still seek subsequent/final version source code) that actually sometimes worked on Slackware up to 12.n or 13.n. ??? I don't use git much (only 'git clone') but the SlackBuilds.org maintainers are free to add these into SBo-git (as of few hours ago tested on Slackwware64 15, Slackware64 15.1+current, but not x86-32) or tell me how (I won't on GitHub but maybe GitLab or of course git.SlackBuilds.org.) ??? I said 'roleplaying-like' because roleplaying game (RP, RPG) inventor Gary Gygax describes in his books /Role-playing Mastery/, /Master of The Game/ that computer games (at least single-player) are role assumption (RA,) not RP (which requires players, theatre-based aspects.) ??? Below are dates for SlackBuilds on my server (so you know if you want to upgrade.) 2022-03-13 angband.tar.gz 2017-10-07 ihack.tar.gz 2022-03-13 larn.tar.gz 2020-07-17 mangband.tar.gz 2021-03-21 moria.tar.gz 2022-03-13 rogue.tar.gz 2022-03-13 stone_soup.tar.gz 2022-03-13 tome-ah.tar.gz 2020-11-18 tome-sx.tar.gz From rsamurti at gmail.com Sun Mar 13 12:48:56 2022 From: rsamurti at gmail.com (Ananda Murthy) Date: Sun, 13 Mar 2022 18:18:56 +0530 Subject: [Slackbuilds-users] Please remove TexText-0.4.4 from the Slackware-15.0 repository. In-Reply-To: References: <04d42ccb10879d4ffc8a6a04b6f9654d@schoepfer.info> Message-ID: Yes. Version 1.8.1 works perfectly. On Sun, Mar 13, 2022 at 3:04 PM Jheengut Pritvi wrote: > Hi, > > did you mean this version > https://github.com/textext/textext/releases/tag/1.8.1 ?? > > On Sun, 13 Mar 2022 at 09:01, Ananda Murthy wrote: > >> Yes. It works perfectly. >> >> On Sat, Mar 12, 2022 at 11:02 PM Franzen via SlackBuilds-users < >> slackbuilds-users at slackbuilds.org> wrote: >> >>> On 2022-03-12 18:11, Ananda Murthy wrote: >>> > Hello, >>> > >>> > This version does not work with Inkscape 1.1.2. >>> >>> Have you tried you tried a newer version from here >>> https://github.com/textext/textext ? >>> >>> _______________________________________________ >>> 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/ >>> >>> >> >> -- >> >> >> Close Windows ! Open source !! >> Free software from proprietary mafia !!! >> _______________________________________________ >> 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/ > > -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Sun Mar 13 15:59:40 2022 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 13 Mar 2022 08:59:40 -0700 (PDT) Subject: [Slackbuilds-users] Has 15.0 dropped chromium? Message-ID: I could not find chromium in an SBo repository and it's not part of the core distribution. Is it no longer available for use in 15.0? TIA, Rich From yalhcru at gmail.com Sun Mar 13 16:09:26 2022 From: yalhcru at gmail.com (B Watson) Date: Sun, 13 Mar 2022 12:09:26 -0400 Subject: [Slackbuilds-users] rogue(like) & Lord of The Rings games SlackBuilds updates: angband, larn, rogue, stone_soup, tome-ah In-Reply-To: References: Message-ID: On 3/13/22, David Chmelik wrote: > I don't use git much (only 'git clone') but the SlackBuilds.org > maintainers are free to add these into SBo-git (as of few hours ago > tested on Slackwware64 15, Slackware64 15.1+current, but not x86-32) or > tell me how (I won't on GitHub but maybe GitLab or of course > git.SlackBuilds.org.) I don't use github either... Wait a few days, the submission form on the website will be open, and you'll be able to upload tarballs like you've done in the past. > I said 'roleplaying-like' because roleplaying game (RP, RPG) > inventor Gary Gygax describes in his books /Role-playing Mastery/, > /Master of The Game/ that computer games (at least single-player) are > role assumption (RA,) not RP (which requires players, theatre-based > aspects.) Hey, that's an interesting bit of information. I always knew roguelikes and other single-player "roleplaying" games aren't the same as a proper game of D&D (or I suppose World of Warcraft), but never knew there was actually a separate name for them. Thanks for that. From didier at slint.fr Sun Mar 13 19:48:17 2022 From: didier at slint.fr (Didier Spaier) Date: Sun, 13 Mar 2022 20:48:17 +0100 Subject: [Slackbuilds-users] Has 15.0 dropped chromium? In-Reply-To: References: Message-ID: <09293055-587d-0a73-e327-a6eee2f0270b@slint.fr> You can use on of the versions provided by Eric Hameleers, as mentioned on his blog: https://alien.slackbook.org/blog/ Cheers, Didier Le 13/03/2022 ? 16:59, Rich Shepard a ?crit?: > I could not find chromium in an SBo repository and it's not part of the core > distribution. Is it no longer available for use in 15.0? > > TIA, > > Rich From rshepard at appl-ecosys.com Sun Mar 13 20:02:32 2022 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 13 Mar 2022 13:02:32 -0700 (PDT) Subject: [Slackbuilds-users] Has 15.0 dropped chromium? In-Reply-To: <09293055-587d-0a73-e327-a6eee2f0270b@slint.fr> References: <09293055-587d-0a73-e327-a6eee2f0270b@slint.fr> Message-ID: <3547340-f15d-1ec0-37d1-5760a66f7c6@appl-ecosys.com> On Sun, 13 Mar 2022, Didier Spaier wrote: > You can use on of the versions provided by Eric Hameleers, as mentioned on > his blog: https://alien.slackbook.org/blog/ Didier, Thank you. I will. Rich From 1.41421 at gmail.com Sun Mar 13 21:53:05 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 13 Mar 2022 15:53:05 -0600 Subject: [Slackbuilds-users] No ssvnc for 15.0 in slackbuilds Message-ID: I notice that ssvnc is not present for 15.0, despite the fact that it was there for 14.2. Any idea why it was not added to 15.0? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Sun Mar 13 23:49:15 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 13 Mar 2022 17:49:15 -0600 Subject: [Slackbuilds-users] No ssvnc for 15.0 in slackbuilds In-Reply-To: References: Message-ID: On Sun, Mar 13, 2022, 3:53 PM Luveh Keraph <1.41421 at gmail.com> wrote: > I notice that ssvnc is not present for 15.0, despite the fact that it was > there for 14.2. Any idea why it was not added to 15.0? > It failed to build on 15.0, so it was removed so the 15.0 repo didn't have failed builds. https://git.slackbuilds.org/slackbuilds/commit/network/ssvnc?id=cfe9b2973baba1fabf6196e71a393968c3af34ba Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Mar 14 02:06:31 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 14 Mar 2022 09:06:31 +0700 Subject: [Slackbuilds-users] Branch 15.0 PGP problems In-Reply-To: References: <52841647122989@mail.yandex.ru> Message-ID: <2dbcd69d-9783-8e8e-d394-80d3412b3eb7@slackbuilds.org> > I guess this is the same problem that I am observing when using sbopkg: > > # sbopkg -ki reduce-algebra.sqf > GPG check FAILED! > > Say (Y)es if you want keep the reduce-algebra directory and tarball and > continue > with the build process, or (N)o to delete the reduce-algebra directory and > tarball > (all local changes to reduce-algebra and its files will be lost), or > (A)bort to stop > the build process without deleting anything. > (Y)es, (N)o, (A)bort?: > > On Sat, Mar 12, 2022 at 3:12 PM Ched Ex wrote: > >> Hello. >> There is a problem with PGP signature for packed SB scripts at 15.0 branch. >> e.g.: >> Downloaded from https://slackbuilds.org/slackbuilds/15.0/development/ >> $ gpg --verify 4th.tar.gz.asc >> gpg: assuming signed data in `4th.tar.gz' >> gpg: Signature made Sat 12 Mar 2022 07:26:07 AM MSK using DSA key ID >> 9C7BA3B6 >> gpg: BAD signature from "SlackBuilds.org Development Team < >> slackbuilds-devel at slackbuilds.org>" >> >> If download from https://slackbuilds.org/slackbuilds/14.2/development/ >> $ gpg --verify 4th.tar.gz.asc >> gpg: assuming signed data in `4th.tar.gz' >> gpg: Signature made Sat 17 Oct 2020 05:51:08 AM MSK using DSA key ID >> 9C7BA3B6 >> gpg: Good signature from "SlackBuilds.org Development Team < >> slackbuilds-devel at slackbuilds.org>" It has been fixed as per yesterday please run sbopkg -r again and it will download the correct signs Sorry for that issue.... last time we released a new repo was 6 years ago :-) -- 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 1.41421 at gmail.com Mon Mar 14 02:14:54 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sun, 13 Mar 2022 20:14:54 -0600 Subject: [Slackbuilds-users] Branch 15.0 PGP problems In-Reply-To: <2dbcd69d-9783-8e8e-d394-80d3412b3eb7@slackbuilds.org> References: <52841647122989@mail.yandex.ru> <2dbcd69d-9783-8e8e-d394-80d3412b3eb7@slackbuilds.org> Message-ID: Thanks. I have just verified with sbopkg and the diagnostic is gone. On Sun, Mar 13, 2022 at 8:06 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > I guess this is the same problem that I am observing when using sbopkg: > > > > # sbopkg -ki reduce-algebra.sqf > > GPG check FAILED! > > > > Say (Y)es if you want keep the reduce-algebra directory and tarball and > > continue > > with the build process, or (N)o to delete the reduce-algebra directory > and > > tarball > > (all local changes to reduce-algebra and its files will be lost), or > > (A)bort to stop > > the build process without deleting anything. > > (Y)es, (N)o, (A)bort?: > > > > On Sat, Mar 12, 2022 at 3:12 PM Ched Ex wrote: > > > >> Hello. > >> There is a problem with PGP signature for packed SB scripts at 15.0 > branch. > >> e.g.: > >> Downloaded from https://slackbuilds.org/slackbuilds/15.0/development/ > >> $ gpg --verify 4th.tar.gz.asc > >> gpg: assuming signed data in `4th.tar.gz' > >> gpg: Signature made Sat 12 Mar 2022 07:26:07 AM MSK using DSA key ID > >> 9C7BA3B6 > >> gpg: BAD signature from "SlackBuilds.org Development Team < > >> slackbuilds-devel at slackbuilds.org>" > >> > >> If download from https://slackbuilds.org/slackbuilds/14.2/development/ > >> $ gpg --verify 4th.tar.gz.asc > >> gpg: assuming signed data in `4th.tar.gz' > >> gpg: Signature made Sat 17 Oct 2020 05:51:08 AM MSK using DSA key ID > >> 9C7BA3B6 > >> gpg: Good signature from "SlackBuilds.org Development Team < > >> slackbuilds-devel at slackbuilds.org>" > > It has been fixed as per yesterday > please run sbopkg -r again and it will download the correct signs > > Sorry for that issue.... last time we released a new repo was 6 years > ago :-) > > > > > -- > 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 duncan_roe at optusnet.com.au Mon Mar 14 03:10:10 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Mon, 14 Mar 2022 14:10:10 +1100 Subject: [Slackbuilds-users] mathics/dependencies (mpmath, python-django-legacy) In-Reply-To: <156a4289-06e5-d004-6265-3e48b67f2f38@gmail.com> References: <156a4289-06e5-d004-6265-3e48b67f2f38@gmail.com> Message-ID: On Sun, Mar 13, 2022 at 03:11:27AM -0700, David Chmelik wrote: > I immediately drop mpath, python-django-legacy: now unneeded for mathics. > Seems only documented way to install is pip, which doesn't seem to work > in SlackBuilds, and since you can install it yourself w/pip, I may drop > mathics unless its programmers/developers/engineers finish instructions. > They write you can install it from GitHub, but it's undocumented, and they > admit the documentation is unfinished. > Their main repository says it's 'now "mostly" in archive' and link a new > one, Mathics3--which is actually Mathics 4--and a new one with more stuff, > mathicsomnibus (which would be the one I use, but this is all getting rather > confusing/obscure.) pip2tgz builds it (I just tried) which means you can write a SlackBuild that follows the python template. Cheers ... Duncan. From duncan_roe at optusnet.com.au Mon Mar 14 03:18:23 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Mon, 14 Mar 2022 14:18:23 +1100 Subject: [Slackbuilds-users] Has 15.0 dropped chromium? In-Reply-To: <09293055-587d-0a73-e327-a6eee2f0270b@slint.fr> References: <09293055-587d-0a73-e327-a6eee2f0270b@slint.fr> Message-ID: google-chrome is in 15.0 extra, as it was in Curent. Cheers ... Duncan. On Sun, Mar 13, 2022 at 08:48:17PM +0100, Didier Spaier wrote: > You can use on of the versions provided by Eric Hameleers, as mentioned on his > blog: https://alien.slackbook.org/blog/ > > Cheers, > Didier > > Le 13/03/2022 ? 16:59, Rich Shepard a ?crit?: > > I could not find chromium in an SBo repository and it's not part of the core > > distribution. Is it no longer available for use in 15.0? > > > > TIA, > > > > Rich From dchmelik at gmail.com Mon Mar 14 04:51:39 2022 From: dchmelik at gmail.com (David Chmelik) Date: Sun, 13 Mar 2022 21:51:39 -0700 Subject: [Slackbuilds-users] mathics/dependencies (mpmath, python-django-legacy) In-Reply-To: References: <156a4289-06e5-d004-6265-3e48b67f2f38@gmail.com> Message-ID: <9ba27551-09ee-bfa8-ff8f-6836c6e1990d@gmail.com> On 3/13/22 8:10 PM, Duncan Roe wrote: > On Sun, Mar 13, 2022 at 03:11:27AM -0700, David Chmelik wrote: >> I immediately drop mpath, python-django-legacy: now unneeded for mathics. >> Seems only documented way to install is pip, which doesn't seem to work >> in SlackBuilds, and since you can install it yourself w/pip, I may drop >> mathics unless its programmers/developers/engineers finish instructions. >> They write you can install it from GitHub, but it's undocumented, and they >> admit the documentation is unfinished. >> Their main repository says it's 'now "mostly" in archive' and link a new >> one, Mathics3--which is actually Mathics 4--and a new one with more stuff, >> mathicsomnibus (which would be the one I use, but this is all getting rather >> confusing/obscure.) > pip2tgz builds it (I just tried) which means you can write a SlackBuild > that follows the python template. [...] Okay; how?? The pip2tgz manpage says uses package archives like from PyPi which https://pypi.org/project/Mathics-omnibus/#files has .egg files.? I ran 'pip2tgz Mathics_omnibus-4.0.1-py3.9.egg ' which says it's not a .tar.? Best when manpages have examples... From jebrhansen+SBo at gmail.com Mon Mar 14 05:22:15 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 13 Mar 2022 23:22:15 -0600 Subject: [Slackbuilds-users] Has 15.0 dropped chromium? In-Reply-To: References: Message-ID: On Sun, Mar 13, 2022, 9:59 AM Rich Shepard wrote: > I could not find chromium in an SBo repository and it's not part of the > core > distribution. Is it no longer available for use in 15.0? > Chromium was rarely updated, so it was removed from SBo in 2018. https://git.slackbuilds.org/slackbuilds/log/network/chromium?h=master If you want to continue to use chromium, Alien Bob keeps chromium packages and his SlackBuild available on his repo. http://www.slackware.com/~alien/slackbuilds/chromium/ If you are fine with regular chrome, as already mentioned, Pat makes his SlackBuild for it available in extra/, or ruario has his excellent latest-chrome SlackBuild. https://gist.github.com/ruario/9672759 Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From dchmelik at gmail.com Mon Mar 14 05:26:33 2022 From: dchmelik at gmail.com (David Chmelik) Date: Sun, 13 Mar 2022 22:26:33 -0700 Subject: [Slackbuilds-users] Has 15.0 dropped chromium? In-Reply-To: References: <09293055-587d-0a73-e327-a6eee2f0270b@slint.fr> Message-ID: Yes, but that's now significantly old, after maybe security issue(s) found/fixed. ??? Eric (alienBOB) is on Slackware team, so one can trust his newer versions with fixes. On 3/13/22 8:18 PM, Duncan Roe wrote: > google-chrome is in 15.0 extra, as it was in Curent. > > Cheers ... Duncan. > > On Sun, Mar 13, 2022 at 08:48:17PM +0100, Didier Spaier wrote: >> You can use on of the versions provided by Eric Hameleers, as mentioned on his >> blog: https://alien.slackbook.org/blog/ >> >> Cheers, >> Didier >> >> Le 13/03/2022 ? 16:59, Rich Shepard a ?crit?: >>> I could not find chromium in an SBo repository and it's not part of the core >>> distribution. Is it no longer available for use in 15.0? >>> >>> TIA, >>> >>> Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ From yalhcru at gmail.com Mon Mar 14 06:53:31 2022 From: yalhcru at gmail.com (B Watson) Date: Mon, 14 Mar 2022 02:53:31 -0400 Subject: [Slackbuilds-users] No ssvnc for 15.0 in slackbuilds In-Reply-To: References: Message-ID: On 3/13/22, Jeremy Hansen wrote: > > It failed to build on 15.0, so it was removed so the 15.0 repo didn't have > failed builds. > > https://git.slackbuilds.org/slackbuilds/commit/network/ssvnc?id=cfe9b2973baba1fabf6196e71a393968c3af34ba Yes, and if anyone (the maintainer or you or whoever) wants to fix it so it does build and send us a patch, we'll add it back to the repo. We had close to 8,000 builds to run through... it took us 6 weeks to get to the point where everything that was broken was either patched, version-updated, or dropped. Any build that got removed, anyone's welcome to re-add it. If it'd help, I could make a list of builds that got removed, maybe some of you mailing list folk could pick them up and maintain them. From jebrhansen+SBo at gmail.com Mon Mar 14 07:18:28 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Mon, 14 Mar 2022 01:18:28 -0600 Subject: [Slackbuilds-users] No ssvnc for 15.0 in slackbuilds In-Reply-To: References: Message-ID: On Mon, Mar 14, 2022, 12:53 AM B Watson wrote: If it'd help, I could make a list of builds that got removed, maybe > some of you mailing list folk could pick them up and maintain them. > I'd definitely be interested in looking through it. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From duncan_roe at optusnet.com.au Mon Mar 14 07:46:57 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Mon, 14 Mar 2022 18:46:57 +1100 Subject: [Slackbuilds-users] mathics/dependencies (mpmath, python-django-legacy) In-Reply-To: <9ba27551-09ee-bfa8-ff8f-6836c6e1990d@gmail.com> References: <156a4289-06e5-d004-6265-3e48b67f2f38@gmail.com> <9ba27551-09ee-bfa8-ff8f-6836c6e1990d@gmail.com> Message-ID: <20220314074657.GA3050@smallstar.local.net> On Sun, Mar 13, 2022 at 09:51:39PM -0700, David Chmelik wrote: > On 3/13/22 8:10 PM, Duncan Roe wrote: > > On Sun, Mar 13, 2022 at 03:11:27AM -0700, David Chmelik wrote: > > > I immediately drop mpath, python-django-legacy: now unneeded for mathics. > > > Seems only documented way to install is pip, which doesn't seem to work > > > in SlackBuilds, and since you can install it yourself w/pip, I may drop > > > mathics unless its programmers/developers/engineers finish instructions. > > > They write you can install it from GitHub, but it's undocumented, and they > > > admit the documentation is unfinished. > > > Their main repository says it's 'now "mostly" in archive' and link a new > > > one, Mathics3--which is actually Mathics 4--and a new one with more stuff, > > > mathicsomnibus (which would be the one I use, but this is all getting rather > > > confusing/obscure.) > > pip2tgz builds it (I just tried) which means you can write a SlackBuild > > that follows the python template. [...] > > Okay; how?? The pip2tgz manpage says uses package archives like from PyPi > which https://pypi.org/project/Mathics-omnibus/#files has .egg files.? I ran > 'pip2tgz Mathics_omnibus-4.0.1-py3.9.egg ' which says it's not a .tar.? Best > when manpages have examples... > @David Chmelik: in your earlier email, you talked about mathics. I built Mathics 1.0. Now you are talking about Mathics-omnibus. As you say, Mathics-omnibus doesn't offer a source distro. pip2tgz can't build it. Cheers ... Duncan. From dchmelik at gmail.com Mon Mar 14 07:54:43 2022 From: dchmelik at gmail.com (David Chmelik) Date: Mon, 14 Mar 2022 00:54:43 -0700 Subject: [Slackbuilds-users] mathics/dependencies In-Reply-To: <20220314074657.GA3050@smallstar.local.net> References: <156a4289-06e5-d004-6265-3e48b67f2f38@gmail.com> <9ba27551-09ee-bfa8-ff8f-6836c6e1990d@gmail.com> <20220314074657.GA3050@smallstar.local.net> Message-ID: <317749b0-f464-927b-17cc-ef23364da946@gmail.com> On 3/14/22 12:46 AM, Duncan Roe wrote: > On Sun, Mar 13, 2022 at 09:51:39PM -0700, David Chmelik wrote: >> Okay; how?? The pip2tgz manpage says uses package archives like from PyPi >> which https://pypi.org/project/Mathics-omnibus/#files has .egg files.? I ran >> 'pip2tgz Mathics_omnibus-4.0.1-py3.9.egg ' which says it's not a .tar.? Best >> when manpages have examples... >> > @David Chmelik: in your earlier email, you talked about mathics. I built Mathics > 1.0. Now you are talking about Mathics-omnibus. As you say, Mathics-omnibus > doesn't offer a source distro. pip2tgz can't build it. [...] Mathics 1 SlackBuild existed since Slackware 14.2 and doesn't need changes. ??? Mathics-omnibus is newer stable Mathics full installation, which is what I want to update SlackBuild for, so of course I'm talking about it: many SlackBuilds will be being updated, sometimes with major changes. From alessandro.baggi at gmail.com Mon Mar 14 08:12:27 2022 From: alessandro.baggi at gmail.com (Alessandro Baggi) Date: Mon, 14 Mar 2022 09:12:27 +0100 Subject: [Slackbuilds-users] Slackware64 15.0 and iotop Message-ID: <4dc7f7ad-3eab-fde8-43d5-8308770d3ed2@gmail.com> Hi list, I installed iotop from slackbuilds.org but when running I get this message: CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO and all informations about I/O usage by the processes are reported as "unavailable". Other than recompile the kernel there is something that could be done? Question: Why CONFIG_TASK_DELAY_ACCT is disabled? What is the technical reason? Thank you in advance. From ozan.turkyilmaz at gmail.com Mon Mar 14 08:16:33 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Mon, 14 Mar 2022 11:16:33 +0300 Subject: [Slackbuilds-users] Slackware64 15.0 and iotop In-Reply-To: <4dc7f7ad-3eab-fde8-43d5-8308770d3ed2@gmail.com> References: <4dc7f7ad-3eab-fde8-43d5-8308770d3ed2@gmail.com> Message-ID: <7f2c76ba9bc453602f864dd820e80b1343887575.camel@gmail.com> Pzt, 2022-03-14 tarihinde 09:12 +0100 saatinde, Alessandro Baggi yazd?: > Hi list, > I installed iotop from slackbuilds.org but when running I get this > message: > > CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN > and IO > I did a quick check on my system: zcat /proc/config.gz | grep CONFIG_TASK_DELAY_ACCT CONFIG_TASK_DELAY_ACCT=y Can you also check it on your system? Regards, Ozan From alessandro.baggi at gmail.com Mon Mar 14 08:31:43 2022 From: alessandro.baggi at gmail.com (Alessandro Baggi) Date: Mon, 14 Mar 2022 09:31:43 +0100 Subject: [Slackbuilds-users] Slackware64 15.0 and iotop In-Reply-To: <7f2c76ba9bc453602f864dd820e80b1343887575.camel@gmail.com> References: <4dc7f7ad-3eab-fde8-43d5-8308770d3ed2@gmail.com> <7f2c76ba9bc453602f864dd820e80b1343887575.camel@gmail.com> Message-ID: <48be1a0a-ac2e-8a70-6a7f-cc42509f3be8@gmail.com> Il 14/03/22 09:16, Ozan T?rky?lmaz ha scritto: > Pzt, 2022-03-14 tarihinde 09:12 +0100 saatinde, Alessandro Baggi yazd?: >> Hi list, >> I installed iotop from slackbuilds.org but when running I get this >> message: >> >> CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN >> and IO >> > > I did a quick check on my system: > zcat /proc/config.gz | grep CONFIG_TASK_DELAY_ACCT > CONFIG_TASK_DELAY_ACCT=y > > Can you also check it on your system? > > Regards, > Ozan Hi Ozan # zcat /proc/config.gz | grep CONFIG_TASK_DELAY_ACCT CONFIG_TASK_DELAY_ACCT=y Why iotop report this problem if it is enabled? I'm trying it on a VM actually. This could be a problem? From ozan.turkyilmaz at gmail.com Mon Mar 14 08:49:06 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Mon, 14 Mar 2022 11:49:06 +0300 Subject: [Slackbuilds-users] Slackware64 15.0 and iotop In-Reply-To: <48be1a0a-ac2e-8a70-6a7f-cc42509f3be8@gmail.com> References: <4dc7f7ad-3eab-fde8-43d5-8308770d3ed2@gmail.com> <7f2c76ba9bc453602f864dd820e80b1343887575.camel@gmail.com> <48be1a0a-ac2e-8a70-6a7f-cc42509f3be8@gmail.com> Message-ID: <83c306e42f21a81cd3ca5ef6b5315f0d851c2163.camel@gmail.com> Pzt, 2022-03-14 tarihinde 09:31 +0100 saatinde, Alessandro Baggi yazd?: > > > I did a quick check on my system: > > zcat /proc/config.gz | grep CONFIG_TASK_DELAY_ACCT > > CONFIG_TASK_DELAY_ACCT=y > > > > Can you also check it on your system? > > > > Regards, > > Ozan > > Hi Ozan > > # zcat /proc/config.gz | grep CONFIG_TASK_DELAY_ACCT > CONFIG_TASK_DELAY_ACCT=y > > Why iotop report this problem if it is enabled? > > I'm trying it on a VM actually. This could be a problem? I tested it on my machine and it gave me the same error. Looking around, it seems you need to add "delayacct" to the kernel command line. I didnt test this. I cant reboot right now. Regards, Ozan From alessandro.baggi at gmail.com Mon Mar 14 08:55:19 2022 From: alessandro.baggi at gmail.com (Alessandro Baggi) Date: Mon, 14 Mar 2022 09:55:19 +0100 Subject: [Slackbuilds-users] Slackware64 15.0 and iotop In-Reply-To: <83c306e42f21a81cd3ca5ef6b5315f0d851c2163.camel@gmail.com> References: <4dc7f7ad-3eab-fde8-43d5-8308770d3ed2@gmail.com> <7f2c76ba9bc453602f864dd820e80b1343887575.camel@gmail.com> <48be1a0a-ac2e-8a70-6a7f-cc42509f3be8@gmail.com> <83c306e42f21a81cd3ca5ef6b5315f0d851c2163.camel@gmail.com> Message-ID: Il 14/03/22 09:49, Ozan T?rky?lmaz ha scritto: > Pzt, 2022-03-14 tarihinde 09:31 +0100 saatinde, Alessandro Baggi yazd?: >> >>> I did a quick check on my system: >>> zcat /proc/config.gz | grep CONFIG_TASK_DELAY_ACCT >>> CONFIG_TASK_DELAY_ACCT=y >>> >>> Can you also check it on your system? >>> >>> Regards, >>> Ozan >> >> Hi Ozan >> >> # zcat /proc/config.gz | grep CONFIG_TASK_DELAY_ACCT >> CONFIG_TASK_DELAY_ACCT=y >> >> Why iotop report this problem if it is enabled? >> >> I'm trying it on a VM actually. This could be a problem? > > I tested it on my machine and it gave me the same error. > Looking around, it seems you need to add "delayacct" to the kernel > command line. I didnt test this. I cant reboot right now. > > Regards, > Ozan I added delaycct to lilo and rebooted. It works now. Thank you for your help. From ozan.turkyilmaz at gmail.com Mon Mar 14 08:57:46 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Mon, 14 Mar 2022 11:57:46 +0300 Subject: [Slackbuilds-users] Slackware64 15.0 and iotop In-Reply-To: References: <4dc7f7ad-3eab-fde8-43d5-8308770d3ed2@gmail.com> <7f2c76ba9bc453602f864dd820e80b1343887575.camel@gmail.com> <48be1a0a-ac2e-8a70-6a7f-cc42509f3be8@gmail.com> <83c306e42f21a81cd3ca5ef6b5315f0d851c2163.camel@gmail.com> Message-ID: Pzt, 2022-03-14 tarihinde 09:55 +0100 saatinde, Alessandro Baggi yazd?: > > > I added delaycct to lilo and rebooted. It works now. > > Thank you for your help. I found this: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e4042ad492357fa995921376462b04a025dd53b6 It is not on by default now. We need to update README accordingly. Regards, Ozan From dchmelik at gmail.com Mon Mar 14 09:24:25 2022 From: dchmelik at gmail.com (David Chmelik) Date: Mon, 14 Mar 2022 02:24:25 -0700 Subject: [Slackbuilds-users] python-template.SlackBuild comment/question, Re: mathics In-Reply-To: <317749b0-f464-927b-17cc-ef23364da946@gmail.com> References: <156a4289-06e5-d004-6265-3e48b67f2f38@gmail.com> <9ba27551-09ee-bfa8-ff8f-6836c6e1990d@gmail.com> <20220314074657.GA3050@smallstar.local.net> <317749b0-f464-927b-17cc-ef23364da946@gmail.com> Message-ID: <55d98cdc-28d0-95d0-3fed-c290d32705d5@gmail.com> Working on mathics.SlackBuild, I'm thinking does maybe maybe python-template.SlackBuild template need update?? Seems /any/all/ (almost 10+) Python programs I try anymore use pip, not setuptools (haven't seen it for years) so shouldn't both be in template(s)?? But, maybe pip isn't going to work right without pip2tgz... On 3/14/22 12:54 AM, David Chmelik wrote: > On 3/14/22 12:46 AM, Duncan Roe wrote: >> @David Chmelik: in your earlier email, you talked about mathics. I >> built Mathics >> 1.0. Now you are talking about Mathics-omnibus. As you say, >> Mathics-omnibus >> doesn't offer a source distro. pip2tgz can't build it. [...] > Mathics 1 SlackBuild existed since Slackware 14.2 and doesn't need > changes. > ??? Mathics-omnibus is newer stable Mathics full installation, which > is what I want to update SlackBuild for, so of course I'm talking > about it: many SlackBuilds will be being updated, sometimes with major > changes. I mean Slackware 14.2 is barely older than Mathics 1, from 2 October 2016, w/newer commits (I didn't use) since that October 4th, until late 2020's 1.1.? Mathics 4 (though renamed still Mathics3) was mid-2021, so if anyone might prefer basic package, that would've been what to try.? I might make basic and/or full installation Mathics build scripts.? I want full but depends what others may want. ??? Incidentally 'pip3tgz Mathics3-4.0.0.tar.gz' builds (but crashes, so I'll be talking to upstream) but I avoid unusual build methods, like seems poor style when discord.SlackBuild gets .deb instead of .tar.gz (though pip2tgz may be better than plain pip because can/does specify .tar.gz.)? It may (or not--comments/suggestions/policies?) be best see if pip can be made to install to /tmp/SBo/package-mathics then do normal makepkg. W/pip2tgz would I put .tar.gz in mathics.info then use pip2tgz on it? From alessandro.baggi at gmail.com Mon Mar 14 09:36:40 2022 From: alessandro.baggi at gmail.com (Alessandro Baggi) Date: Mon, 14 Mar 2022 10:36:40 +0100 Subject: [Slackbuilds-users] Slackware 15.0 and osinfo-db Message-ID: <93a3ac79-6678-2779-eee7-7e8ab6365fba@gmail.com> Hi list, I'm trying to install virt-manager that requires osinfo-db. During running osinfo-db.SlackBuild I get: osinfo-db-import: cannot open archive /root/slackish/15.0/slackbuilds/osinfo-db/osinfo-db-20211216.tar.xz: Failed to open '/root/slackish/15.0/slackbuilds/osinfo-db/osinfo-db-20211216.tar.xz' Seems that osinfo-db-20211216.tar.xz is a BZ2 archive. Renaming the file with bz2 extension and modifying the slackbuild at line 52 pointing to the .bz2 file it works. Thank you in advance From rshepard at appl-ecosys.com Mon Mar 14 12:55:05 2022 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 14 Mar 2022 05:55:05 -0700 (PDT) Subject: [Slackbuilds-users] Has 15.0 dropped chromium? In-Reply-To: References: Message-ID: <75f66fe-b0e2-6d55-c89-b24376881fa@appl-ecosys.com> On Sun, 13 Mar 2022, Jeremy Hansen wrote: > Chromium was rarely updated, so it was removed from SBo in 2018. Jeremy, I didn't know that. > If you want to continue to use chromium, Alien Bob keeps chromium packages > and his SlackBuild available on his repo. Yes, and he has an ungoogled-chromium, too. > If you are fine with regular chrome, as already mentioned, Pat makes his > SlackBuild for it available in extra/, or ruario has his excellent > latest-chrome SlackBuild. I've used chromium on my 14.2 desktop since that firefox version is not supported by some web sites, mostly financial. I've avoided chrome. I'll use the brave browser rather than chromium on 15.0. Many thanks, Rich From jebrhansen+SBo at gmail.com Mon Mar 14 14:16:29 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Mon, 14 Mar 2022 08:16:29 -0600 Subject: [Slackbuilds-users] python-template.SlackBuild comment/question, Re: mathics In-Reply-To: <55d98cdc-28d0-95d0-3fed-c290d32705d5@gmail.com> References: <156a4289-06e5-d004-6265-3e48b67f2f38@gmail.com> <9ba27551-09ee-bfa8-ff8f-6836c6e1990d@gmail.com> <20220314074657.GA3050@smallstar.local.net> <317749b0-f464-927b-17cc-ef23364da946@gmail.com> <55d98cdc-28d0-95d0-3fed-c290d32705d5@gmail.com> Message-ID: On Mon, Mar 14, 2022, 3:24 AM David Chmelik wrote: > Working on mathics.SlackBuild, I'm thinking does maybe maybe > python-template.SlackBuild template need update? Seems /any/all/ > (almost 10+) Python programs I try anymore use pip, not setuptools > (haven't seen it for years) so shouldn't both be in template(s)? But, > maybe pip isn't going to work right without pip2tgz... > > On 3/14/22 12:54 AM, David Chmelik wrote: > > On 3/14/22 12:46 AM, Duncan Roe wrote: > >> @David Chmelik: in your earlier email, you talked about mathics. I > >> built Mathics > >> 1.0. Now you are talking about Mathics-omnibus. As you say, > >> Mathics-omnibus > >> doesn't offer a source distro. pip2tgz can't build it. [...] > > Mathics 1 SlackBuild existed since Slackware 14.2 and doesn't need > > changes. > > Mathics-omnibus is newer stable Mathics full installation, which > > is what I want to update SlackBuild for, so of course I'm talking > > about it: many SlackBuilds will be being updated, sometimes with major > > changes. > I mean Slackware 14.2 is barely older than Mathics 1, from 2 October > 2016, w/newer commits (I didn't use) since that October 4th, until late > 2020's 1.1. Mathics 4 (though renamed still Mathics3) was mid-2021, so > if anyone might prefer basic package, that would've been what to try. I > might make basic and/or full installation Mathics build scripts. I want > full but depends what others may want. > Incidentally 'pip3tgz Mathics3-4.0.0.tar.gz' builds (but crashes, > so I'll be talking to upstream) but I avoid unusual build methods, like > seems poor style when discord.SlackBuild gets .deb instead of .tar.gz > (though pip2tgz may be better than plain pip because can/does specify > .tar.gz.) It may (or not--comments/suggestions/policies?) be best see > if pip can be made to install to /tmp/SBo/package-mathics then do normal > makepkg. W/pip2tgz would I put .tar.gz in mathics.info then use pip2tgz > on it? > I'm not sure why discord came up when talking about python and pip2tgz, but I chose to use the deb because it places the files in the normal package locations. The tar.gz would need to be placed in /opt/ and it would need extra lines of code to get everything set up. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From brent at exitstatusone.com Mon Mar 14 16:02:45 2022 From: brent at exitstatusone.com (Brenton Earl) Date: Mon, 14 Mar 2022 10:02:45 -0600 (MDT) Subject: [Slackbuilds-users] Update lutris to version 0.5.9.1 Message-ID: Hello, Here is a patch to update lutris to 0.5.9.1. Is anyone interested in maintaining this script? I do not use Lutris and it should be in better hands. Regards, Brent -------------- next part -------------- diff --git a/games/lutris/lutris.SlackBuild b/games/lutris/lutris.SlackBuild index 73ddf9f8b9..39896a4453 100644 --- a/games/lutris/lutris.SlackBuild +++ b/games/lutris/lutris.SlackBuild @@ -3,7 +3,7 @@ # Slackware build script for lutris # Ryan P.C. McQuen | Everett, WA | ryanpcmcquen at member.fsf.org -# Copyright 2018 Brenton Earl +# Copyright 2018, 2022 Brenton Earl # This program is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -26,7 +26,7 @@ cd $(dirname $0) ; CWD=$(pwd) PRGNAM=lutris -VERSION=${VERSION:-0.4.23} +VERSION=${VERSION:-0.5.9.1} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} @@ -35,13 +35,11 @@ if [ -z "$ARCH" ]; then case "$( uname -m )" in i?86) ARCH=i586 ;; arm*) ARCH=arm ;; + aarch64) ARCH=$( uname -m ) ;; *) ARCH=$( uname -m ) ;; esac fi -# If the variable PRINT_PACKAGE_NAME is set, then this script will report what -# the name of the created package would be, and then exit. This information -# could be useful to other scripts. if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then echo "$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE" exit 0 @@ -51,7 +49,24 @@ TMP=${TMP:-/tmp/SBo} PKG=${PKG:-$TMP/package-$PRGNAM} OUTPUT=${OUTPUT:-/tmp} -DOCS="AUTHORS CHANGELOG LICENSE INSTALL.rst README.rst" +DOCS="AUTHORS LICENSE INSTALL.rst README.rst" + +if [ "$ARCH" = "i586" ]; then + SLKCFLAGS="-O2 -march=i586 -mtune=i686" + LIBDIRSUFFIX="" +elif [ "$ARCH" = "i686" ]; then + SLKCFLAGS="-O2 -march=i686 -mtune=i686" + LIBDIRSUFFIX="" +elif [ "$ARCH" = "x86_64" ]; then + SLKCFLAGS="-O2 -fPIC" + LIBDIRSUFFIX="64" +elif [ "$ARCH" = "aarch64" ]; then + SLKCFLAGS="-O2 -fPIC" + LIBDIRSUFFIX="64" +else + SLKCFLAGS="-O2" + LIBDIRSUFFIX="" +fi set -e @@ -59,8 +74,8 @@ rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $PRGNAM -tar xvf $CWD/$PRGNAM\_$VERSION.tar.xz -cd $PRGNAM +tar xvf $CWD/$PRGNAM\-$VERSION.tar.?z +cd $PRGNAM\-$VERSION chown -R root:root . find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ @@ -68,7 +83,8 @@ find -L . \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; -python3 setup.py install --root $PKG +python3 setup.py build +python3 setup.py install --root="$PKG" --optimize=1 --skip-build find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true diff --git a/games/lutris/lutris.info b/games/lutris/lutris.info index 88b945f081..5c260322e9 100644 --- a/games/lutris/lutris.info +++ b/games/lutris/lutris.info @@ -1,10 +1,10 @@ PRGNAM="lutris" -VERSION="0.4.23" +VERSION="0.5.9.1" HOMEPAGE="https://lutris.net/" -DOWNLOAD="http://lutris.net/releases/lutris_0.4.23.tar.xz" -MD5SUM="2300a2f6e617cf222aa47acd0b72436f" +DOWNLOAD="https://github.com/lutris/lutris/archive/refs/tags/v0.5.9.1/lutris-0.5.9.1.tar.gz" +MD5SUM="948e18e95750ca0f0af120ea86efe1f6" DOWNLOAD_x86_64="" MD5SUM_x86_64="" -REQUIRES="" +REQUIRES="python-magic gnome-desktop webkit2gtk lxml" MAINTAINER="Brenton Earl" EMAIL="brent at exitstatusone.com" From ozan.turkyilmaz at gmail.com Mon Mar 14 16:29:01 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Mon, 14 Mar 2022 19:29:01 +0300 Subject: [Slackbuilds-users] Update lutris to version 0.5.9.1 In-Reply-To: References: Message-ID: Pzt, 2022-03-14 tarihinde 10:02 -0600 saatinde, Brenton Earl yazd?: > > Hello, > > Here is a patch to update lutris to 0.5.9.1. > > Is anyone interested in maintaining this script? > > I do not use Lutris and it should be in better hands. > > Regards, > Brent I do use Lutris and I can take over. Regards, Ozan From 1.41421 at gmail.com Mon Mar 14 17:22:19 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 14 Mar 2022 11:22:19 -0600 Subject: [Slackbuilds-users] perl-X11-Protocol-Other not building in 15.0 Message-ID: I have just tried to build perl-X11-Protocol other in a Slackware 15.0 installation with all the current patches, and it is not building for me: # X11::Protocol::init_extension('X11::Protocol=HASH(0x21055a8)', 'XFree86-DGA') called at t/XFree86_DGA.t line 73 # # # Exit code 1 for warnings t/XFree86_DGA.t ................. Dubious, test returned 1 (wstat 256, 0x100) Failed 21/21 subtests t/XINERAMA-10.t ................. # X11::Protocol version 0.56 # XINERAMA extension is opcode=140 event=0 error=0 # PanoramiXQueryVersion 1.1 t/XINERAMA-10.t ................. 1/8 # PanoramiXGetState 1 # PanoramiXGetScreenCount 1 # PanoramiXGetScreenSize 3440, 1440 # END t/XINERAMA-10.t ................. ok t/XINERAMA-11.t ................. # X11::Protocol version 0.56 # XINERAMA extension is opcode=140 event=0 error=0 # XineramaIsActive 1 t/XINERAMA-11.t ................. 1/2 # XineramaQueryScreens count 1 # XineramaQueryScreens rectangle 0,0,3440,1440 # END t/XINERAMA-11.t ................. ok t/XINERAMA-use.t ................ ok t/XSetRoot.t .................... # X11::Protocol version 0.56 # DISPLAY 192.168.0.3:0.0 t/XSetRoot.t .................... 5/7 # have TOG-CUP: 0 t/XSetRoot.t .................... ok t/XTEST.t ....................... # X11::Protocol version 0.56 # XTEST extension opcode=132 event=0 error=0 # server XTEST version 2.0 t/XTEST.t ....................... 16/16 # END t/XTEST.t ....................... ok Test Summary Report ------------------- t/XFree86_DGA.t (Wstat: 256 Tests: 0 Failed: 0) Non-zero exit status: 1 Parse errors: Bad plan. You planned 21 tests but ran 0. Files=47, Tests=1098, 21 wallclock secs ( 0.33 usr 0.09 sys + 3.95 cusr 0.73 csys = 5.10 CPU) Result: FAIL Failed 1/47 test programs. 0/1098 subtests failed. make: *** [Makefile:978: test_dynamic] Error 255 -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Mar 14 17:37:50 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 15 Mar 2022 00:37:50 +0700 Subject: [Slackbuilds-users] perl-X11-Protocol-Other not building in 15.0 In-Reply-To: References: Message-ID: <6cf9c100-a24c-b6d4-2d5b-6f9f882128c7@slackbuilds.org> > I have just tried to build perl-X11-Protocol other in a Slackware 15.0 > installation with all the current patches, and it is not building for me: which "current" are we talking here? -current as the development branch or current as latest stable patches? -- 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 1.41421 at gmail.com Mon Mar 14 17:43:55 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 14 Mar 2022 11:43:55 -0600 Subject: [Slackbuilds-users] perl-X11-Protocol-Other not building in 15.0 In-Reply-To: <6cf9c100-a24c-b6d4-2d5b-6f9f882128c7@slackbuilds.org> References: <6cf9c100-a24c-b6d4-2d5b-6f9f882128c7@slackbuilds.org> Message-ID: I meant, with the patches under the patches/packages directory in the Slackware 15.0 distribution as retrieved yesterday. I also forgot to mention that this is for Slackware64 15.0. On Mon, Mar 14, 2022 at 11:38 AM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > I have just tried to build perl-X11-Protocol other in a Slackware 15.0 > > installation with all the current patches, and it is not building for me: > > which "current" are we talking here? > -current as the development branch or current as latest stable patches? > > > -- > Willy Sudiarto Raharjo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Mon Mar 14 17:48:28 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 14 Mar 2022 11:48:28 -0600 Subject: [Slackbuilds-users] No ssvnc for 15.0 in slackbuilds In-Reply-To: References: Message-ID: This may be of use to you: I got the 1.0.29-6 version patched as found in https://launchpad.net/ubuntu/+source/ssvnc/1.0.29-6, and applied the Debian patches to the 1.0.30 sources that used to build under 14.2, only leaving out the stuff to do with missing IMakefile. The resulting sources build under Slackware64 15.0, and the resulting executables seem to work fine - I have done a most perfunctory test, but the basic capabilities of the software seem to be doing what they are supposed to. On Mon, Mar 14, 2022 at 1:18 AM Jeremy Hansen wrote: > On Mon, Mar 14, 2022, 12:53 AM B Watson wrote: > > If it'd help, I could make a list of builds that got removed, maybe >> some of you mailing list folk could pick them up and maintain them. >> > > I'd definitely be interested in looking through it. > > 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 yalhcru at gmail.com Mon Mar 14 19:31:15 2022 From: yalhcru at gmail.com (B Watson) Date: Mon, 14 Mar 2022 15:31:15 -0400 Subject: [Slackbuilds-users] No ssvnc for 15.0 in slackbuilds In-Reply-To: References: Message-ID: On 3/14/22, Luveh Keraph <1.41421 at gmail.com> wrote: > This may be of use to you: I got the 1.0.29-6 version patched as found in > https://launchpad.net/ubuntu/+source/ssvnc/1.0.29-6, and applied the Debian > patches to the 1.0.30 sources that used to build under 14.2, only leaving > out the stuff to do with missing IMakefile. The resulting sources build > under Slackware64 15.0, and the resulting executables seem to work fine - I > have done a most perfunctory test, but the basic capabilities of the > software seem to be doing what they are supposed to. That's great! You should probably become the new ssvnc maintainer. Interested? From yalhcru at gmail.com Mon Mar 14 19:35:16 2022 From: yalhcru at gmail.com (B Watson) Date: Mon, 14 Mar 2022 15:35:16 -0400 Subject: [Slackbuilds-users] perl-X11-Protocol-Other not building in 15.0 In-Reply-To: References: Message-ID: On 3/14/22, Luveh Keraph <1.41421 at gmail.com> wrote: > I have just tried to build perl-X11-Protocol other in a Slackware 15.0 > installation with all the current patches, and it is not building for me: It's failing the "make test", because X isn't running (or, because the DISPLAY environment variable isn't set). For now, just comment out the 'make test' in the slackbuild. A proper patch will be coming soon. From 1.41421 at gmail.com Mon Mar 14 19:48:02 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 14 Mar 2022 13:48:02 -0600 Subject: [Slackbuilds-users] perl-X11-Protocol-Other not building in 15.0 In-Reply-To: References: Message-ID: OK, thanks. On Mon, Mar 14, 2022 at 1:35 PM B Watson wrote: > On 3/14/22, Luveh Keraph <1.41421 at gmail.com> wrote: > > I have just tried to build perl-X11-Protocol other in a Slackware 15.0 > > installation with all the current patches, and it is not building for me: > > It's failing the "make test", because X isn't running (or, because the > DISPLAY environment variable isn't set). > > For now, just comment out the 'make test' in the slackbuild. A proper > patch will be coming soon. > _______________________________________________ > 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 Mon Mar 14 20:04:39 2022 From: yalhcru at gmail.com (B Watson) Date: Mon, 14 Mar 2022 16:04:39 -0400 Subject: [Slackbuilds-users] List of builds that were removed for 15.0 Message-ID: We had a lot of builds that failed on 15.0, and not a lot of time or manpower to fix them. So some of them got removed... though since we use git, they're un-removable at any time. Since this is a long list (over 300 builds), I've placed a copy on a web server so you can download it and grep it: https://slackware.uk/~urchlay/src/sbo-removed-for-15.0.txt If any of these are your builds, or if you'd like to take over any of the ones that weren't being maintained, feel free to get them ready for submission... or fix them on github/gitlab and submit a PR/MR, if that's how you roll. The submission form will be open for business Real Soon Now. A few of these got removed because they're included in Slackware now, please don't resubmit those. network/BitchX should be on the list, but I've already claimed that one (with the previous maintainer's permission). Rest of this email is the contents of the list: multimedia/lwks: Removed (membership and licensing changes). network/wireguard-linux-compat: Removed (part of newer kernels). multimedia/gst-plugins-bad: Removed (conflict w/Slackware gst-plugins-bad-free). games/glPortal: Removed (will not build against bullet 3.x, ran out of patience). system/kitchen-sync: Removed (unused, no dependees). network/verm: Removed (unused, no dependees). python/planes: Removed. network/airpwn-ng: Removed network/vacuum-im: Removed (no maintainer). network/pgl: Removed (No maintainer). network/squidGuard: Removed (upstream no longer maintained). libraries/lapack-atlas: Removed (Along with atlas). libraries/atlas: Removed (use OpenBLAS). system/Type1_to_OTF: Removed (ftbfs). multimedia/plex-home-theater: Removed (ftbs, upstream dead). libraries/ring-lrc: Removed (superseded by jami). libraries/ring-daemon: Removed (superseded by jami). development/libbitcoin: Removed (incompat boost 1.78). development/couchdb: Removed (ftb, no maintainer). system/elo-mt-usb: Removed (download is gone, we dont have the hardware to test new versions). system/multicorn: Removed (FTBFS, even with debian patches and/or latest git). graphics/teighaviewer: Removed (outdated binary-only software). academic/Mnemosyne: Removed (requires nonexistent PyQtWebEngine dep). games/qtsixa: Removed (FTBFS, unmaintained, replace someday with "sixad"). office/marave: Removed (PyQt4; unmaintained upstream since 2015) libraries/trilinos: Removed (no dependees; conflicts with mpich and openmpi) desktop/cairo-compmgr: Removed. graphics/separate+: Removed (crashed at runtime). games/sumwars: Removed (ftbfs). libraries/libsunpinyin: Removed (no maintainer). games/ember: Removed (not compatible with latest OGRE). graphics/yesplz: Removed (No longer maintained). graphics/mitsuba-blender: Removed (ftbfs). graphics/mitsuba: Removed (ftbfs). system/suhosin: Removed (not compatible with newer PHP). graphics/freewrl: Removed (no maintainer, ftbfs). office/teapot: Removed (website and source are not available). development/atom: Removed (no maintainer). system/lxd: Removed (ftb, no maintainer). libraries/gstreamer-editing-services: Removed. network/valknut: Removed. academic/avogadro: Removed. academic/QtiPlot: Removed. network/ucspi-ssl: Removed. network/qutebrowser-tox: Removed. network/pound: Removed. network/ganglia-web: Removed. network/pdnsd: Removed. network/openrdate: Removed. network/openl2tp: Removed. network/mldonkey: Removed. network/linuxdcpp: Removed. network/knemo: Removed. network/imapproxy: Removed. network/ike: Removed. network/gtmess: Removed. network/gq: Removed. network/elemental-ircd: Removed. network/dogecoin: Removed. network/dclib: Removed. development/adoptopenjdk: Removed (EOL). development/jdk16: Removed (EOL). development/jdk15: Removed (EOL). development/jdk14: Removed (EOL). development/jdk13: Removed (EOL). development/jdk12: Removed (EOL). development/adoptopenjdk-openj9: Removed (EOL). network/rekonq: Removed (KDE4 app). graphics/k3d: Removed (FTBFS). graphics/rawstudio: Removed (FTBFS). academic/seaview: Removed the treerecs dependency (ftb). system/oracle-xe: Removed (old version, not available for download). libraries/qwt-qt5: Removed (redundant; use qwt). libraries/qwtpolar: Removed (FTBFS, and no dependees). network/sks-keyserver: Removed. network/openvas-manager: Removed. network/ntop: Removed. network/kfilebox: Removed. network/kcm_ufw: Removed. network/iptv-analyzer: Removed. network/guacamole-server: Removed. network/greenbone-security-assistant: Removed. network/ganglia: Removed. network/etcd: Removed. network/et: Removed. network/emacs-w3m: Removed. network/dobbscoin: Removed. network/dbmail: Removed. network/corebird: Removed. academic/treerecs: Removed (ftb + no active maintainer). academic/gcompris: Removed. academic/flashqard: Removed (no qt4-webkit available). academic/drawtiming: Removed (incompatible with the newer gcc). academic/Xyce: Removed (ftb). multimedia/subtitlecomposer: Removed (needs kde4). academic/vCAPS_coevolution: Removed (ftb + no active maintainer). academic/prank-msa: Removed (ftb + no active maintainer). academic/bpp1.9-utils: Removed (ftb + no active maintainer). academic/bpp1.9-seq: Removed (ftb + no active maintainer). academic/bpp1.9-phyl: Removed (ftb + no active maintainer). academic/bpp1.9-numcalc: Removed (ftb + no active maintainer). academic/bppsuite: Removed (ftb + no active maintainer). academic/bpp-seq-omics: Removed (ftb + no active maintainer). academic/bpp-popgen: Removed (ftb + no active maintainer). academic/bpp-phyl: Removed (ftb + no active maintainer). academic/bpp-phyl-omics: Removed (ftb + no active maintainer). academic/bpp-seq: Removed (ftb + no active maintainer). academic/bpp-core: Removed (ftb + no active maintainer). multimedia/mythplugins: Removed (ftb + no active maintainer) multimedia/mythtv: Removed (ftb + no active maintainer) network/hylafax: Removed (ftb + no active maintainer) network/fwbuilder: Removed (ftb + no active maintainer) network/base: Removed (ftp + no active maintainer) misc/igal2: Removed (ftp + no active maintainer) development/sourcenav: Removed. development/qt-creator2: Removed (abandoned). graphics/kamerka: Removed (KDE4 app, untouched since 2014). desktop/vivacious-colors-gtk-icon-theme: Removed (does not work well with xfce 4.16) desktop/vivacious-colors-gtk-theme: Removed (does not work well with xfce 4.16) development/flow: Removed (ftb). libraries/ocaml-bisect: Removed (ftb). libraries/ocaml-ounit: Removed (ftb). academic/abella: Removed (ftb). graphics/mlbrot: Removed (ftb). libraries/cppo: Removed (ftb). academic/coq: Removed (ftb). development/numpy-legacy3: Removed (ftb). games/etlegacy-from-source: Removed (use the binary). office/kate-latex-plugin: Removed (KDE4 app; use kile instead). office/kchmviewer: Removed (redundant; use kchmviewer-qt). libraries/GtkD: Removed (not used by any slackbuild) multimedia/OpenPHT: Removed (superseded by plex media player and plex htpc) office/teams-for-linux: Removed (Use official teams). network/ettercap-NG: Removed (incompatible with the newer openssl). network/lighttpd2: Removed (still too unripe). haskell/haskell-megaparsec: Removed (ftbfs, no maintainer). haskell/haskell-neat-interpolation: Removed (ftbfs, no maintainer). haskell/haskell-mustache: Removed (ftbfs, no maintainer). haskell/haskell-optparse-simple: Removed (ftbfs, unmaintained). haskell/haskell-parallel: Removed (ftbfs, unmaintained). haskell/haskell-http-api-data: Removed (ftbfs, unmaintained). haskell/haskell-persistent-template: Removed (ftbfs, unmaintained). haskell/haskell-persistent-sqlite: Removed (ftbfs, unmaintained). haskell/haskell-persistent: Removed (ftbfs, unmaintained). haskell/haskell-store: Removed (ftbfs, unmaintained). haskell/haskell-hslogger: Removed (ftbfs, unmaintained). haskell/haskell-haskell-src: Removed (ftbfs, unmaintained). haskell/haskell-hashed-storage: Removed (ftbfs, unmaintained). haskell/haskell-cabal-install: Removed (ftbfs, unmaintained). haskell/haskell-stack: Removed (ftbfs, unmaintained). haskell/haskell-hackage-security: Removed (ftbfs, unmaintained). ham/linlogbook: Removed. ham/qradiopredict: Removed. games/chocolate_duke3D: Removed (broken and abandoned). system/qingy_0.3_themepack: Removed (old age, lack of use). system/qingy: Removed (old age, lack of use). libraries/DirectFB: Removed (old age, lack of use). multimedia/gnash: Removed. It's dead, Jim. system/python3-urwid: Removed. office/fop-legacy: Removed (ftbfs) office/wyrd: Removed (ftbfs) audio/Pd-extended: Removed (ftbfs) libraries/libtunepimp: Removed (ftbfs) libraries/dbus-sharp: Removed (ftbfs) libraries/dbus-sharp-glib: Removed (dbus-sharp ftbfs) network/smuxi: Removed (dbus-sharp dep ftbfs) multimedia/totem: Removed (no maintainer, ftbfs). multimedia/gecko-mediaplayer: Removed. multimedia/freshplayerplugin: Removed. multimedia/pepperflash-plugin: Removed. development/mono-debugger: Removed (abandoned and ftb). development/gcclegacy494: Removed (FTB). system/nvidia-legacy304-driver: Removed (unmaintained, ftbfs). system/nvidia-legacy304-kernel: Removed (unmaintained, ftbfs). libraries/libido3: Removed. system/bareos-client: Removed (orphaned, ftbfs). system/bareos: Removed (orphaned, ftbfs). network/kadu: Removed (unmaintained). system/tilix: Removed (ftbfs, no maintainer). system/tpe-kmod: Removed (ftbfs, no upstream activity). development/swift: Removed (abandoned, ftbfs). system/spl-solaris: Removed (fails to build, unused). audio/lastfm: Removed (because libraries/lastfm was removed). libraries/db46: Removed (not needed, and conflicts with Slack db48) office/hyphen-id: Removed (merged with hunspell-id). office/focuswriter-legacy: Removed (use focuswriter instead). misc/protobuf: Removed (use protobuf3 instead). libraries/glfw: Removed (no dependees, conflicts with glfw3). development/nuget: Removed (abandoned). development/fsharp: Removed (abandoned). development/referenceassemblies-pcl: Removed (abandoned). development/monodevelop: Removed (abandoned). development/monkey-studio: Removed (no qt4-qscintilla). development/odb: Removed (abandoned). development/libodb-sqlite: Removed (abandoned). development/libodb-qt: Removed (abandoned). development/libodb-pgsql: Removed (abandoned). development/libodb-mysql: Removed (abandoned). development/libodb-boost: Removed (abandoned). development/libodb: Removed (abandoned). development/jupyter_core: Removed (abandoned). development/jupyter-nbclient: Removed (abandoned). development/jupyter-notebook: Removed (abandoned). development/jupyter-nbconvert: Removed (abandoned). development/jupyterlab_pygments: Removed (abandoned). development/jupyter-widgetsnbextension: Removed (abandoned). development/jupyter-nbdime: Removed (abandoned). development/jupyter-ipyleaflet: Removed (abandoned). python/python-branca: Removed (abandoned). python/traittypes: Removed (abandoned). development/jupyter_client: Removed (abandoned). development/jupyter-nbformat: Removed (abandoned). development/jupyter-ipywidgets: Removed (abandoned). python/python3-ipython-sql: Removed (no more ipython). python/traitlets: Removed (abandoned). python/ipython: Removed (abandoned). python/ipython_genutils: Removed (abandoned). development/jupyter_console: Removed (abandoned). development/QtPy: Removed (abandoned). development/jupyter-qtconsole: Removed (abandoned). development/jupyter-ipykernel: Removed (abandoned). network/libcapi20: Removed (roger-router is removed). audio/spandsp: Removed (roger-router is removed). network/roger-router: Removed (source only for flatpak). multimedia/simpleburn: Removed (upstream is dead). libraries/libquvi-scripts: Removed. libraries/libquvi: Removed (Not needed as cclive is removed). network/quvi: Removed (Not needed as cclive is removed). network/cclive: Removed (Not building on 15.0). haskell/haskell-exceptions: Removed (part of ghc). games/gargoyle: Removed SDL_sound dep (part of Slackware). games/roadfighter: Removed SDL_sound dep (part of Slackware). games/mog: Removed SDL_sound dep (part of Slackware). games/asc: Removed SDL_sound dep (part of Slackware). network/sqlninja: Removed dep perl-IO-Socket-SSL. network/spamassassin: Removed dep perl-IO-Socket-SSL. system/hebe: Removed (KDE4 app). system/kcm_touchpad: Removed (KDE4 app). system/kcollectd: Removed (KDE4 app). system/komparator4: Removed (KDE4 app). system/kvpm: Removed (KDE4 app). development/eric: Removed (needs PyQt4). development/ahven: Removed (needs gprbuild). development/JSONObject: Removed (incompatible with the newer boost). desktop/yawp: Removed (no more kde4). desktop/xfce4-embed-plugin: Removed (no more libxfce4ui-1). desktop/vertex-maia-themes: Removed. desktop/screensaver-icon: Removed (source does not exist). kildclient: Version updated. Added new dependency for gtkspell3. Removed perl-JSON dependency. python/python2-blake2: Removed (unused, python2, ftbfs). python/python-poppler-qt4: Removed (needs poppler-qt4). desktop/simon: Removed (no more kde4). desktop/recorditnow: Removed (no more kde4). desktop/quickaccess: Removed (no more kde4). desktop/quadkonsole4: Removed (no more kde4). desktop/qtcurve: Removed (no more kde4). desktop/qt-recordmydesktop: Removed (needs PyQt4). desktop/ptbatterysystemtray: Removed (abandoned upstream). desktop/plasma-geek-clock: Removed (no more kde4). desktop/plasma-applet-daisy: Removed (no more kde4). desktop/plasma-eyasdp: Removed (no more kde4). desktop/plasma-adjustable-clock: Removed (no more kde4). desktop/kover: Removed (no more kde4). desktop/kcometen4: Removed (no more kde4). desktop/gtk-kde4: Removed (no more kde4). desktop/homerun: Removed (no more kde4). network/guacamole-server: Removed freerdp dep (part of slackware). network/remmina: Removed freerdp dep (part of slackware). desktop/crystal: Removed (no more kde4). libraries/beignet: Removed (incompatible with the newer llvm). development/mrustc: Removed (rust now in slackware). libraries/pgplot: Removed (abandoned upstream and FTB). academic/openboard: Removed quazip-qt5 dep. (part of slackware). libraries/PyQwt: Removed (needs PyQt4). libraries/gazebo: Removed (no qt4-webkit available). games/rejoystick: Removed (no maintainer). system/flSynclient: Removed (no maintainer). libraries/hug: Removed (no maintainer). games/gens-gs: Removed (no maintainer). development/bacon: Removed (no maintainer). gis/CreateCloudMap: Removed (Service is shut down). gis/spatialite_gui: Removed. libraries/libgaiagraphics: Removed (obsoleted upstream). audio/llcon: Removed (abandoned, ftbfs). audio/cuberok: Removed (unmaintained, qt4). network/slimjet: Removed (abandoned by SBo maintainer) desktop/simplenote: Removed (abandoned by SBo maintainer) development/xemacs: Removed (unmaintained @ SBo) business/AssociationSubscribersManager: Removed (abandoned, ftbfs). business/lemonpos: Removed (requires KDE4). network/libinfinity: Removed (unused). network/libqinfinity: Removed (unused). network/kobby: Removed (no kde4 anymore). system/packagekit: Removed. libraries/libtorrent-rasterbar-legacy: Removed. libraries/mariadb_client: Removed (substituted by connector, FTB). libraries/opencv-legacy: Removed (not compatible with opencv). network/bird: Removed (no maintainer). network/basilisk: Removed (upstream development suspended). network/Icecat: Removed (unmaintained, ftbfs). libraries/php-mssql: Removed (no more mssql ext in php 7.4.x). network/arora: Removed (unmaintained upstream). libraries/opal: Removed. libraries/ptlib: Removed. libraries/gtk-qt-engine: Removed (abandoned ftbfs). libraries/hinnant-date: Removed (included in sqlpp11). libraries/sqlpp11-connector-sqlite3: Removed (included in sqlpp11). libraries/sqlpp11-connector-mysql: Removed (included in sqlpp11). network/t38modem: Removed (missing dependency). libraries/t38modem-opal: Removed (missing dependency). libraries/t38modem-ptlib: Removed (incompatible with openssl-1.1.x). desktop/plasma-widget-menubar: Removed (abandonded ftbfs). libraries/appmenu-qt: Removed (orphaned - qt4 + ftbfs). libraries/upscaledb: Removed (orphaned and FTB). libraries/hpx: Removed (orphaned and FTB). libraries/vdpau-video: Removed (obsolete, abandoned upstream, FTB). system/termite: Removed (obsoleted by alacritty). libraries/vte3-ng: Removed (conflicts with vte in Slackware). libraries/proxygen: Removed (orphaned and FTB). libraries/wangle: Removed (orphaned and FTB). libraries/folly: Removed (orphaned and FTB). misc/Publican: Removed (missing perl dependencies). misc/fribid: Removed (not compatible with openssl-1.1.x). misc/hashkill: Removed (not compatible with openssl-1.1.x). misc/readesm: Removed (no qt4-webkit available). misc/scim-chewing: Removed (no scim in Slackware anymore). From 1.41421 at gmail.com Mon Mar 14 20:19:08 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Mon, 14 Mar 2022 14:19:08 -0600 Subject: [Slackbuilds-users] No ssvnc for 15.0 in slackbuilds In-Reply-To: References: Message-ID: I am afraid that I am not competent for that responsibility - I know how to use common sense to patch C files by hand, but I have no clue about whatever software engineering tools to be used to get the job done for distribution. On Mon, Mar 14, 2022 at 1:31 PM B Watson wrote: > On 3/14/22, Luveh Keraph <1.41421 at gmail.com> wrote: > > This may be of use to you: I got the 1.0.29-6 version patched as found in > > https://launchpad.net/ubuntu/+source/ssvnc/1.0.29-6, and applied the > Debian > > patches to the 1.0.30 sources that used to build under 14.2, only leaving > > out the stuff to do with missing IMakefile. The resulting sources build > > under Slackware64 15.0, and the resulting executables seem to work fine > - I > > have done a most perfunctory test, but the basic capabilities of the > > software seem to be doing what they are supposed to. > > That's great! You should probably become the new ssvnc > maintainer. Interested? > _______________________________________________ > 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 duncan_roe at optusnet.com.au Mon Mar 14 20:55:01 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Tue, 15 Mar 2022 07:55:01 +1100 Subject: [Slackbuilds-users] python-template.SlackBuild comment/question, Re: mathics In-Reply-To: References: <156a4289-06e5-d004-6265-3e48b67f2f38@gmail.com> <9ba27551-09ee-bfa8-ff8f-6836c6e1990d@gmail.com> <20220314074657.GA3050@smallstar.local.net> <317749b0-f464-927b-17cc-ef23364da946@gmail.com> <55d98cdc-28d0-95d0-3fed-c290d32705d5@gmail.com> Message-ID: <20220314205501.GA3941@smallstar.local.net> On Mon, Mar 14, 2022 at 08:16:29AM -0600, Jeremy Hansen wrote: > On Mon, Mar 14, 2022, 3:24 AM David Chmelik wrote: > > > Working on mathics.SlackBuild, I'm thinking does maybe maybe > > python-template.SlackBuild template need update? Seems /any/all/ > > (almost 10+) Python programs I try anymore use pip, not setuptools > > (haven't seen it for years) so shouldn't both be in template(s)? But, > > maybe pip isn't going to work right without pip2tgz... > > > > On 3/14/22 12:54 AM, David Chmelik wrote: > > > On 3/14/22 12:46 AM, Duncan Roe wrote: > > >> @David Chmelik: in your earlier email, you talked about mathics. I > > >> built Mathics > > >> 1.0. Now you are talking about Mathics-omnibus. As you say, > > >> Mathics-omnibus > > >> doesn't offer a source distro. pip2tgz can't build it. [...] > > > Mathics 1 SlackBuild existed since Slackware 14.2 and doesn't need > > > changes. > > > Mathics-omnibus is newer stable Mathics full installation, which > > > is what I want to update SlackBuild for, so of course I'm talking > > > about it: many SlackBuilds will be being updated, sometimes with major > > > changes. > > I mean Slackware 14.2 is barely older than Mathics 1, from 2 October > > 2016, w/newer commits (I didn't use) since that October 4th, until late > > 2020's 1.1. Mathics 4 (though renamed still Mathics3) was mid-2021, so > > if anyone might prefer basic package, that would've been what to try. I > > might make basic and/or full installation Mathics build scripts. I want > > full but depends what others may want. > > Incidentally 'pip3tgz Mathics3-4.0.0.tar.gz' builds (but crashes, > > so I'll be talking to upstream) but I avoid unusual build methods, like > > seems poor style when discord.SlackBuild gets .deb instead of .tar.gz > > (though pip2tgz may be better than plain pip because can/does specify > > .tar.gz.) It may (or not--comments/suggestions/policies?) be best see > > if pip can be made to install to /tmp/SBo/package-mathics then do normal > > makepkg. W/pip2tgz would I put .tar.gz in mathics.info then use pip2tgz > > on it? > > > > I'm not sure why discord came up when talking about python and pip2tgz, but > I chose to use the deb because it places the files in the normal package > locations. > > The tar.gz would need to be placed in /opt/ and it would need extra lines > of code to get everything set up. > > Jeremy No, the created tar.gz is a Slackware package, same as you get from a SlackBuild normally. I think all the *2tgz packages work that way. Cheers ... Duncan. From duncan_roe at optusnet.com.au Mon Mar 14 20:58:01 2022 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Tue, 15 Mar 2022 07:58:01 +1100 Subject: [Slackbuilds-users] python-template.SlackBuild comment/question, Re: mathics In-Reply-To: <55d98cdc-28d0-95d0-3fed-c290d32705d5@gmail.com> References: <156a4289-06e5-d004-6265-3e48b67f2f38@gmail.com> <9ba27551-09ee-bfa8-ff8f-6836c6e1990d@gmail.com> <20220314074657.GA3050@smallstar.local.net> <317749b0-f464-927b-17cc-ef23364da946@gmail.com> <55d98cdc-28d0-95d0-3fed-c290d32705d5@gmail.com> Message-ID: <20220314205801.GB3941@smallstar.local.net> On Mon, Mar 14, 2022 at 02:24:25AM -0700, David Chmelik wrote: > Working on mathics.SlackBuild, I'm thinking does maybe maybe > python-template.SlackBuild template need update?? Seems /any/all/ (almost > 10+) Python programs I try anymore use pip, not setuptools (haven't seen it > for years) so shouldn't both be in template(s)?? But, maybe pip isn't going > to work right without pip2tgz... > > On 3/14/22 12:54 AM, David Chmelik wrote: > > On 3/14/22 12:46 AM, Duncan Roe wrote: > > > @David Chmelik: in your earlier email, you talked about mathics. I > > > built Mathics > > > 1.0. Now you are talking about Mathics-omnibus. As you say, > > > Mathics-omnibus > > > doesn't offer a source distro. pip2tgz can't build it. [...] > > Mathics 1 SlackBuild existed since Slackware 14.2 and doesn't need > > changes. > > ??? Mathics-omnibus is newer stable Mathics full installation, which is > > what I want to update SlackBuild for, so of course I'm talking about it: > > many SlackBuilds will be being updated, sometimes with major changes. > I mean Slackware 14.2 is barely older than Mathics 1, from 2 October 2016, > w/newer commits (I didn't use) since that October 4th, until late 2020's > 1.1.? Mathics 4 (though renamed still Mathics3) was mid-2021, so if anyone > might prefer basic package, that would've been what to try.? I might make > basic and/or full installation Mathics build scripts.? I want full but > depends what others may want. > ??? Incidentally 'pip3tgz Mathics3-4.0.0.tar.gz' builds (but crashes, so > I'll be talking to upstream) but I avoid unusual build methods, like seems > poor style when discord.SlackBuild gets .deb instead of .tar.gz (though > pip2tgz may be better than plain pip because can/does specify .tar.gz.)? It > may (or not--comments/suggestions/policies?) be best see if pip can be made > to install to /tmp/SBo/package-mathics then do normal makepkg. W/pip2tgz > would I put .tar.gz in mathics.info then use pip2tgz on it? > With pip2tgz, get the source archive from PyPI (may be tar.gz or zip) and pip2tgz will make an actual package ready to install. Cheers ... Duncan. From yalhcru at gmail.com Mon Mar 14 21:27:53 2022 From: yalhcru at gmail.com (B Watson) Date: Mon, 14 Mar 2022 17:27:53 -0400 Subject: [Slackbuilds-users] No ssvnc for 15.0 in slackbuilds In-Reply-To: References: Message-ID: On 3/14/22, Luveh Keraph <1.41421 at gmail.com> wrote: > I am afraid that I am not competent for that responsibility - I know how to > use common sense to patch C files by hand, but I have no clue about > whatever software engineering tools to be used to get the job done for > distribution. Common sense is all you really need. If you can patch C code, you can check that a SlackBuild runs correctly, makes a valid package, and that the software it packages actually works. That's what a maintainer does. That, and every once in a while check for newer versions and update the script for them. From jebrhansen+SBo at gmail.com Mon Mar 14 22:20:09 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Mon, 14 Mar 2022 16:20:09 -0600 Subject: [Slackbuilds-users] python-template.SlackBuild comment/question, Re: mathics In-Reply-To: <20220314205501.GA3941@smallstar.local.net> References: <156a4289-06e5-d004-6265-3e48b67f2f38@gmail.com> <9ba27551-09ee-bfa8-ff8f-6836c6e1990d@gmail.com> <20220314074657.GA3050@smallstar.local.net> <317749b0-f464-927b-17cc-ef23364da946@gmail.com> <55d98cdc-28d0-95d0-3fed-c290d32705d5@gmail.com> <20220314205501.GA3941@smallstar.local.net> Message-ID: On Mon, Mar 14, 2022 at 2:55 PM Duncan Roe wrote: > On Mon, Mar 14, 2022 at 08:16:29AM -0600, Jeremy Hansen wrote: > > On Mon, Mar 14, 2022, 3:24 AM David Chmelik wrote: > > > > > Working on mathics.SlackBuild, I'm thinking does maybe maybe > > > python-template.SlackBuild template need update? Seems /any/all/ > > > (almost 10+) Python programs I try anymore use pip, not setuptools > > > (haven't seen it for years) so shouldn't both be in template(s)? But, > > > maybe pip isn't going to work right without pip2tgz... > > > > > > On 3/14/22 12:54 AM, David Chmelik wrote: > > > > On 3/14/22 12:46 AM, Duncan Roe wrote: > > > >> @David Chmelik: in your earlier email, you talked about mathics. I > > > >> built Mathics > > > >> 1.0. Now you are talking about Mathics-omnibus. As you say, > > > >> Mathics-omnibus > > > >> doesn't offer a source distro. pip2tgz can't build it. [...] > > > > Mathics 1 SlackBuild existed since Slackware 14.2 and doesn't need > > > > changes. > > > > Mathics-omnibus is newer stable Mathics full installation, which > > > > is what I want to update SlackBuild for, so of course I'm talking > > > > about it: many SlackBuilds will be being updated, sometimes with > major > > > > changes. > > > I mean Slackware 14.2 is barely older than Mathics 1, from 2 October > > > 2016, w/newer commits (I didn't use) since that October 4th, until late > > > 2020's 1.1. Mathics 4 (though renamed still Mathics3) was mid-2021, so > > > if anyone might prefer basic package, that would've been what to try. > I > > > might make basic and/or full installation Mathics build scripts. I > want > > > full but depends what others may want. > > > Incidentally 'pip3tgz Mathics3-4.0.0.tar.gz' builds (but crashes, > > > so I'll be talking to upstream) but I avoid unusual build methods, like > > > seems poor style when discord.SlackBuild gets .deb instead of .tar.gz > > > (though pip2tgz may be better than plain pip because can/does specify > > > .tar.gz.) It may (or not--comments/suggestions/policies?) be best see > > > if pip can be made to install to /tmp/SBo/package-mathics then do > normal > > > makepkg. W/pip2tgz would I put .tar.gz in mathics.info then use > pip2tgz > > > on it? > > > > > > > I'm not sure why discord came up when talking about python and pip2tgz, > but > > I chose to use the deb because it places the files in the normal package > > locations. > > > > The tar.gz would need to be placed in /opt/ and it would need extra lines > > of code to get everything set up. > > > > Jeremy > > No, the created tar.gz is a Slackware package, same as you get from a > SlackBuild > normally. > > I think all the *2tgz packages work that way. > > The discord tar.gz you download from their site is a self-contained version of discord. It does not contain the normal folder structure found in a package. It is simply in a Discord/ folder, which everything extracts into that Discord/ folder. You can run it from that directory. If I used this, I would need to add extra lines into the script to place files properly (like a link in /usr/bin and placing the discord.desktop and icon in the proper locations for them to show up in a menu -- not hard, but entirely unnecessary when the .deb package already does it). The .deb is already prepped and ready to go. You just extract it and you're ready to make a Slackware package minus the Slackware specific things like a slack-desc, doinst.sh, and making the /usr/doc directory.. However, my initial question of why was discord brought up within a pip2tgz topic wasn't answered... Discord is not python and won't be found via pip. There is discord.py that can be found via pip, but it is an API wrapper, not the official discord chat app. So, pip2tgz can't do anything with discord, so what was the point in mentioning discord? Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From sborg63 at disroot.org Tue Mar 15 02:41:08 2022 From: sborg63 at disroot.org (sborg63) Date: Tue, 15 Mar 2022 02:41:08 +0000 Subject: [Slackbuilds-users] List of builds that were removed for 15.0 (B Watson) In-Reply-To: References: Message-ID: <20220315024108.6b7b55af@knotsUL> Sorry, no aim to interfere with anything; but I have a question with respect to the jupyter stack that is said to be removed; it is a bit confusing: > Date: Mon, 14 Mar 2022 16:04:39 -0400 > From: B Watson > To: "SlackBuilds.org Users List" > Subject: [Slackbuilds-users] List of builds that were removed for 15.0 .. > > We had a lot of builds that failed on 15.0, and not a lot of time or > manpower to fix them. So some of them got removed... though since we > use git, they're un-removable at any time. .. > development/jupyter_core: Removed (abandoned). > development/jupyter-nbclient: Removed (abandoned). > development/jupyter-notebook: Removed (abandoned). > development/jupyter-nbconvert: Removed (abandoned). > development/jupyterlab_pygments: Removed (abandoned). > development/jupyter-widgetsnbextension: Removed (abandoned). > development/jupyter-nbdime: Removed (abandoned). > development/jupyter-ipyleaflet: Removed (abandoned). > python/python-branca: Removed (abandoned). > python/traittypes: Removed (abandoned). > development/jupyter_client: Removed (abandoned). > development/jupyter-nbformat: Removed (abandoned). > development/jupyter-ipywidgets: Removed (abandoned). > python/python3-ipython-sql: Removed (no more ipython). > python/traitlets: Removed (abandoned). > python/ipython: Removed (abandoned). > python/ipython_genutils: Removed (abandoned). > development/jupyter_console: Removed (abandoned). > development/QtPy: Removed (abandoned). > development/jupyter-qtconsole: Removed (abandoned). > development/jupyter-ipykernel: Removed (abandoned). What does 'abandoned' imply, is that by the maintainer or upstream? A working suite is running atm on my box with Slackware1-15 using ponce's GIT scripts. On Slackbuilds.org there is still this list with some overlap with the abandoned set: Search Results for "jupyter" Name Category Version Slackware jupyter-ipykernel Development 6.9.1 15.0 jupyter-nbclient Development 0.5.12 15.0 jupyter-nbconvert Development 6.4.2 15.0 jupyter-nbformat Development 5.1.3 15.0 jupyter-notebook Development 6.4.8 15.0 jupyter-qtconsole Development 5.2.2 15.0 jupyter_client Development 7.1.2 15.0 jupyter_console Development 6.4.3 15.0 jupyter_core Development 4.9.1 15.0 jupyterlab_pygments Development 0.1.2 15.0 ipython Python 8.1.1 15.0 It seems a loss if this is all gone; is there an alternative coming in or are we supposed to use pip or to maintain our own script set? Thanks for all the work, Rob From yalhcru at gmail.com Tue Mar 15 05:41:14 2022 From: yalhcru at gmail.com (B Watson) Date: Tue, 15 Mar 2022 01:41:14 -0400 Subject: [Slackbuilds-users] List of builds that were removed for 15.0 (B Watson) In-Reply-To: <20220315024108.6b7b55af@knotsUL> References: <20220315024108.6b7b55af@knotsUL> Message-ID: On 3/14/22, sborg63 wrote: > > On Slackbuilds.org there is still this list with some overlap with > the abandoned set: > > Search Results for "jupyter" > Name Category Version Slackware > jupyter-ipykernel Development 6.9.1 15.0 > jupyter-nbclient Development 0.5.12 15.0 > jupyter-nbconvert Development 6.4.2 15.0 > jupyter-nbformat Development 5.1.3 15.0 > jupyter-notebook Development 6.4.8 15.0 > jupyter-qtconsole Development 5.2.2 15.0 > jupyter_client Development 7.1.2 15.0 > jupyter_console Development 6.4.3 15.0 > jupyter_core Development 4.9.1 15.0 > jupyterlab_pygments Development 0.1.2 15.0 > ipython Python 8.1.1 15.0 Sorry, my list was made by searching for "Removed" in the git log, then subtracting anything that has "Re-added". These got re-added after removal, but the commit messages just say "Added". So, my fault, these are still on SBo for 15.0. > It seems a loss if this is all gone; is there an alternative coming in > or are we supposed to use pip or to maintain our own script set? In most cases, the reason things are gone is that they can't be built on 15.0. Leaving them in the repo would have just left you with a frustrating experience of trying to build things and watching them fail. As for "is there an alternative coming in", that's up to the maintainers. The point of posting the list was to let the maintainers know they can re-add their scripts, after patching/fixing so they work on 15.0. I just included some stuff in the list that shouldn't have been there... In theory, the SBo admins could have spent the extra time to make sure *everything* got fixed... but there aren't that many of us, and we were trying to get the 15.0 repo out there in some usable form, in a reasonable amount of time (it took us, what, 6 weeks?) If we'd insisted on fixing everything first, not dropping anything, it would still be at least 2 or 3 more months before our 15.0 repo could be released. As it stands, we dropped less than 5% of the builds. And they can be re-added, when/if someone steps up to maintain them. Seemed like a good tradeoff to us. From peter at peter-dambier.de Tue Mar 15 09:12:49 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Tue, 15 Mar 2022 10:12:49 +0100 Subject: [Slackbuilds-users] If you really wont to try - the pain with GCC Message-ID: <20220315101249.5e124737.peter@peter-dambier.de> Hi fello SlackBuilders if you know a little C and if you cherish on old SlackBuild ... you might get overwhelmed with some nessages from gcc-11 that really do not make sense, actually! E.g. gcc-11 can no longer compile avr-gcc. If you are daring enoguh you might want to switch between gcc-5 and gcc-11. Here is how I did it. get from good old Slackware 14.2 in one directory - dont install yet! binutils-2.26-x86_64-3.txz gcc-5.3.0-x86_64-3.txz gcc-g++-5.3.0-x86_64-3.txz gcc-gfortran-5.3.0-x86_64-3.txz gcc-gnat-5.3.0-x86_64-3.txz gcc-go-5.3.0-x86_64-3.txz gcc-java-5.3.0-x86_64-3.txz gcc-objc-5.3.0-x86_64-3.txz gettext-0.19.8.1-x86_64-1.txz gmp-6.1.1-x86_64-1.txz libmpc-1.0.3-x86_64-1.txz mpfr-3.1.4-x86_64-1.txz Do the same for Slackware 15.0 in a different directory: binutils-2.37-x86_64-1.txz gcc-11.2.0-x86_64-2.txz gcc-brig-11.2.0-x86_64-2.txz gcc-g++-11.2.0-x86_64-2.txz gcc-gdc-11.2.0-x86_64-2.txz gcc-gfortran-11.2.0-x86_64-2.txz gcc-gnat-11.2.0-x86_64-2.txz gcc-go-11.2.0-x86_64-2.txz gcc-objc-11.2.0-x86_64-2.txz gettext-0.21-x86_64-3.txz gmp-6.2.1-x86_64-3.txz libmpc-1.2.1-x86_64-3.txz mpfr-4.1.0-x86_64-3.txz This may be overkill, depending on what you want to do. Do not removepkg anything! cd into the gcc-5 directory and installpkg *.txz. cd into your SlackBuild. SlackBuild and installpkg cd into the gcc-11 directory and installpkg *.txz Programmes built with gcc-5 will need some librararies ... They do coexist with those from gcc-11 but building is another Story. This is not for the faint of heart. Is it worth the hassle? You decide. I guess 3 from 15 SlackBuilds I was able to rescue with this. The Source is with You. Peter From royal.post at protonmail.com Tue Mar 15 03:35:32 2022 From: royal.post at protonmail.com (royal.post) Date: Tue, 15 Mar 2022 03:35:32 +0000 Subject: [Slackbuilds-users] Slack 15 gui-ufw not working with webkit2gtk Message-ID: <0farZz7CJMg348BHi7qYU3xZarTNhxch3cX4LxtEtDS8PTtaMRs6hmsOV1vPYP1ga9sMzCE2ZUUnPhSQXQjC1i4OeLZwoJ698fytzfkx-H8=@protonmail.com> Hello, The Slack 15 SBo for gui-ufwm doesn't seem to work with webkit2gtk 2.34.6 https://slackbuilds.org/repository/15.0/network/gui-ufw/ https://slackbuilds.org/repository/15.0/libraries/webkit2gtk/ I compiled all the requirements, when trying to run gufw from a term, after putting in the root password, nothing happens the GUI doesn't appear, and there are no messages at the term. 22.04 is the latest version of gufw, it would be greatly appreciated if we can get an updated SBo for gufw. https://github.com/costales/gufw THANKS -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.public at protonmail.com Tue Mar 15 12:53:26 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Tue, 15 Mar 2022 12:53:26 +0000 Subject: [Slackbuilds-users] If you really wont to try - the pain with GCC In-Reply-To: <20220315101249.5e124737.peter@peter-dambier.de> References: <20220315101249.5e124737.peter@peter-dambier.de> Message-ID: ------- Original Message ------- On Tuesday, March 15th, 2022 at 4:12 AM, Peter Dambier wrote: > Hi fello SlackBuilders > > if you know a little C and if you cherish on old SlackBuild ... > you might get overwhelmed with some nessages from gcc-11 that > really do not make sense, actually! > > E.g. gcc-11 can no longer compile avr-gcc. > > If you are daring enoguh you might want to switch between gcc-5 > and gcc-11. > > Here is how I did it. > > get from good old Slackware 14.2 in one directory - dont install yet! > > binutils-2.26-x86_64-3.txz > gcc-5.3.0-x86_64-3.txz > gcc-g++-5.3.0-x86_64-3.txz > gcc-gfortran-5.3.0-x86_64-3.txz > gcc-gnat-5.3.0-x86_64-3.txz > gcc-go-5.3.0-x86_64-3.txz > gcc-java-5.3.0-x86_64-3.txz > gcc-objc-5.3.0-x86_64-3.txz > gettext-0.19.8.1-x86_64-1.txz > gmp-6.1.1-x86_64-1.txz > libmpc-1.0.3-x86_64-1.txz > mpfr-3.1.4-x86_64-1.txz > > Do the same for Slackware 15.0 in a different directory: > > binutils-2.37-x86_64-1.txz > gcc-11.2.0-x86_64-2.txz > gcc-brig-11.2.0-x86_64-2.txz > gcc-g++-11.2.0-x86_64-2.txz > gcc-gdc-11.2.0-x86_64-2.txz > gcc-gfortran-11.2.0-x86_64-2.txz > gcc-gnat-11.2.0-x86_64-2.txz > gcc-go-11.2.0-x86_64-2.txz > gcc-objc-11.2.0-x86_64-2.txz > gettext-0.21-x86_64-3.txz > gmp-6.2.1-x86_64-3.txz > libmpc-1.2.1-x86_64-3.txz > mpfr-4.1.0-x86_64-3.txz > > This may be overkill, depending on what you want to do. > > Do not removepkg anything! > > cd into the gcc-5 directory and installpkg *.txz. > > cd into your SlackBuild. SlackBuild and installpkg > > cd into the gcc-11 directory and installpkg *.txz > > Programmes built with gcc-5 will need some librararies ... > > They do coexist with those from gcc-11 but building is another Story. > > This is not for the faint of heart. > > Is it worth the hassle? You decide. I guess 3 from 15 SlackBuilds I > was able to rescue with this. > > The Source is with You. > Peter, I would not recommend your method. But to each his own. gcc5 is available on SBo, as well as avr-gcc. They integrate into the system much nicer than your method. Another option is to do the old "./configure; make; make install" but target /opt/gcc as the DESTDIR. I did this on Slackware 14.2 with newer versions of GCC for use with MATLAB. > Peter > From peter at peter-dambier.de Tue Mar 15 14:16:36 2022 From: peter at peter-dambier.de (Peter Dambier) Date: Tue, 15 Mar 2022 15:16:36 +0100 Subject: [Slackbuilds-users] If you really wont to try - the pain with GCC In-Reply-To: References: <20220315101249.5e124737.peter@peter-dambier.de> Message-ID: <20220315151636.6edfb428.peter@peter-dambier.de> On Tue, 15 Mar 2022 12:53:26 +0000 Erich Ritz via SlackBuilds-users wrote: > ------- Original Message ------- > > On Tuesday, March 15th, 2022 at 4:12 AM, Peter Dambier > wrote: > > > Hi fello SlackBuilders > > > > if you know a little C and if you cherish on old SlackBuild ... > > you might get overwhelmed with some nessages from gcc-11 that > > really do not make sense, actually! > > > > E.g. gcc-11 can no longer compile avr-gcc. > > > > If you are daring enoguh you might want to switch between gcc-5 > > and gcc-11. > > > > Here is how I did it. > > > > get from good old Slackware 14.2 in one directory - dont install > > yet! > > > > binutils-2.26-x86_64-3.txz > > gcc-5.3.0-x86_64-3.txz > > gcc-g++-5.3.0-x86_64-3.txz > > gcc-gfortran-5.3.0-x86_64-3.txz > > gcc-gnat-5.3.0-x86_64-3.txz > > gcc-go-5.3.0-x86_64-3.txz > > gcc-java-5.3.0-x86_64-3.txz > > gcc-objc-5.3.0-x86_64-3.txz > > gettext-0.19.8.1-x86_64-1.txz > > gmp-6.1.1-x86_64-1.txz > > libmpc-1.0.3-x86_64-1.txz > > mpfr-3.1.4-x86_64-1.txz > > > > Do the same for Slackware 15.0 in a different directory: > > > > binutils-2.37-x86_64-1.txz > > gcc-11.2.0-x86_64-2.txz > > gcc-brig-11.2.0-x86_64-2.txz > > gcc-g++-11.2.0-x86_64-2.txz > > gcc-gdc-11.2.0-x86_64-2.txz > > gcc-gfortran-11.2.0-x86_64-2.txz > > gcc-gnat-11.2.0-x86_64-2.txz > > gcc-go-11.2.0-x86_64-2.txz > > gcc-objc-11.2.0-x86_64-2.txz > > gettext-0.21-x86_64-3.txz > > gmp-6.2.1-x86_64-3.txz > > libmpc-1.2.1-x86_64-3.txz > > mpfr-4.1.0-x86_64-3.txz > > > > This may be overkill, depending on what you want to do. > > > > Do not removepkg anything! > > > > cd into the gcc-5 directory and installpkg *.txz. > > > > cd into your SlackBuild. SlackBuild and installpkg > > > > cd into the gcc-11 directory and installpkg *.txz > > > > Programmes built with gcc-5 will need some librararies ... > > > > They do coexist with those from gcc-11 but building is another > > Story. > > > > This is not for the faint of heart. > > > > Is it worth the hassle? You decide. I guess 3 from 15 SlackBuilds I > > was able to rescue with this. > > > > The Source is with You. > > > > Peter, > > I would not recommend your method. But to each his own. > > gcc5 is available on SBo, as well as avr-gcc. They integrate into > the system much nicer than your method. > > Another option is to do the old "./configure; make; make install" but > target /opt/gcc as the DESTDIR. I did this on Slackware 14.2 > with newer versions of GCC for use with MATLAB. > > > Peter > > > > _______________________________________________ > 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/ > Erich, nor do I. I am glad for the new SlackBuild. That makes my workaround obsolete. Cheers Peter From poprocks at gmail.com Tue Mar 15 18:53:48 2022 From: poprocks at gmail.com (Logan Rathbone) Date: Tue, 15 Mar 2022 14:53:48 -0400 Subject: [Slackbuilds-users] Has 15.0 dropped chromium? In-Reply-To: References: <09293055-587d-0a73-e327-a6eee2f0270b@slint.fr> Message-ID: On Mon, Mar 14, 2022 at 01:26:33AM EDT, David Chmelik wrote: [reversed top-posting, for readability] > On 3/13/22 8:18 PM, Duncan Roe wrote: > > google-chrome is in 15.0 extra, as it was in Curent. > > > > Cheers ... Duncan. > Yes, but that's now significantly old, after maybe security issue(s) > found/fixed. Not so; the google-chrome SlackBuild in /extra simply takes the dpkg that you must manually download from the official Google servers, and converts that into a Slackware tgz package that matches the version of the dpkg downloaded. > ??? Eric (alienBOB) is on Slackware team, so one can trust his newer > versions with fixes. These are very high-quality packages as well, but they are de-googled. This may be against the grain around these parts, but for me, half the reason I *do* use Chrome is to get the Google Account integration. From jebrhansen+SBo at gmail.com Tue Mar 15 19:02:43 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 15 Mar 2022 13:02:43 -0600 Subject: [Slackbuilds-users] Has 15.0 dropped chromium? In-Reply-To: References: <09293055-587d-0a73-e327-a6eee2f0270b@slint.fr> Message-ID: On Tue, Mar 15, 2022, 12:55 PM Logan Rathbone wrote: > On Mon, Mar 14, 2022 at 01:26:33AM EDT, David Chmelik wrote: > [reversed top-posting, for readability] > > On 3/13/22 8:18 PM, Duncan Roe wrote: > > > Eric (alienBOB) is on Slackware team, so one can trust his newer > > versions with fixes. > > These are very high-quality packages as well, but they are de-googled. > This may be against the grain around these parts, but for me, half the > reason I *do* use Chrome is to get the Google Account integration. > He has both regular chromium and chromium-ungoogled packages. http://www.slackware.com/~alien/slackbuilds/chromium/ http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/ Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Mar 15 19:31:33 2022 From: yalhcru at gmail.com (B Watson) Date: Tue, 15 Mar 2022 15:31:33 -0400 Subject: [Slackbuilds-users] Slack 15 gui-ufw not working with webkit2gtk In-Reply-To: <0farZz7CJMg348BHi7qYU3xZarTNhxch3cX4LxtEtDS8PTtaMRs6hmsOV1vPYP1ga9sMzCE2ZUUnPhSQXQjC1i4OeLZwoJ698fytzfkx-H8=@protonmail.com> References: <0farZz7CJMg348BHi7qYU3xZarTNhxch3cX4LxtEtDS8PTtaMRs6hmsOV1vPYP1ga9sMzCE2ZUUnPhSQXQjC1i4OeLZwoJ698fytzfkx-H8=@protonmail.com> Message-ID: On 3/14/22, royal.post via SlackBuilds-users wrote: > > I compiled all the requirements, when trying to run gufw from a term, after > putting in the root password, nothing happens the GUI doesn't appear, and > there are no messages at the term. You sure you don't get any messages when you run it from a terminal? I see multiple issues. /usr/bin/gufw is a shell script that launches the real executable with pkexec, and tries to grant access to the local X server using loginctl as part of the logic... I think none of this is ever going to work, for users like me (and probably you) who log in at the console and use 'startx', rather than a GUI login with runlevel 4. There's a simpler way to do it. I'm going to replace that wrapper script. As for version updates, that's for the maintainer to decide (I'm not the maintainer, Skaendo is). From poprocks at gmail.com Tue Mar 15 19:39:47 2022 From: poprocks at gmail.com (Logan Rathbone) Date: Tue, 15 Mar 2022 15:39:47 -0400 Subject: [Slackbuilds-users] Has 15.0 dropped chromium? In-Reply-To: References: <09293055-587d-0a73-e327-a6eee2f0270b@slint.fr> Message-ID: On Tue, Mar 15, 2022 at 03:02:43PM EDT, Jeremy Hansen wrote: > On Tue, Mar 15, 2022, 12:55 PM Logan Rathbone wrote: > > > On Mon, Mar 14, 2022 at 01:26:33AM EDT, David Chmelik wrote: > > [reversed top-posting, for readability] > > > On 3/13/22 8:18 PM, Duncan Roe wrote: > > > > > Eric (alienBOB) is on Slackware team, so one can trust his newer > > > versions with fixes. > > > > These are very high-quality packages as well, but they are de-googled. > > This may be against the grain around these parts, but for me, half the > > reason I *do* use Chrome is to get the Google Account integration. > > > > He has both regular chromium and chromium-ungoogled packages. > > http://www.slackware.com/~alien/slackbuilds/chromium/ > http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/ Hm, yes, I have seen this. I think I'll take a second look, but I'm thinking ("googled") Chromium and Google Chrome still would have different levels of Google integration (Googlization, if you will). For instance, last time I checked, Google Account integration was not working with Alien's (googled) Chromium packages; as I understand, this was due to Google's muzzling of unofficial Chromium packages as of 15 March 2021; see https://alien.slackbook.org/blog/google-muzzles-all-chromium-browsers-on-15-march-2021/ From jebrhansen+SBo at gmail.com Tue Mar 15 20:06:33 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 15 Mar 2022 14:06:33 -0600 Subject: [Slackbuilds-users] Has 15.0 dropped chromium? In-Reply-To: References: <09293055-587d-0a73-e327-a6eee2f0270b@slint.fr> Message-ID: On Tue, Mar 15, 2022, 1:41 PM Logan Rathbone wrote: > On Tue, Mar 15, 2022 at 03:02:43PM EDT, Jeremy Hansen wrote: > > On Tue, Mar 15, 2022, 12:55 PM Logan Rathbone > wrote: > > > > > On Mon, Mar 14, 2022 at 01:26:33AM EDT, David Chmelik wrote: > > > [reversed top-posting, for readability] > > > > On 3/13/22 8:18 PM, Duncan Roe wrote: > > > > > > > Eric (alienBOB) is on Slackware team, so one can trust his newer > > > > versions with fixes. > > > > > > These are very high-quality packages as well, but they are de-googled. > > > This may be against the grain around these parts, but for me, half the > > > reason I *do* use Chrome is to get the Google Account integration. > > > > > > > He has both regular chromium and chromium-ungoogled packages. > > > > http://www.slackware.com/~alien/slackbuilds/chromium/ > > http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/ > > Hm, yes, I have seen this. I think I'll take a second look, but I'm > thinking ("googled") Chromium and Google Chrome still would have > different levels of Google integration (Googlization, if you will). > > For instance, last time I checked, Google Account integration was not > working with Alien's (googled) Chromium packages; as I understand, this > was due to Google's muzzling of unofficial Chromium packages as of 15 > March 2021; see > https://alien.slackbook.org/blog/google-muzzles-all-chromium-browsers-on-15-march-2021/ Yeah, I have no idea the difference between them, I just saw both on his repo and that he has 15.0 packages for both. I imagine there's some difference between them if he's packaging both. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From artourter at gmail.com Wed Mar 16 00:50:43 2022 From: artourter at gmail.com (Greg' Ar Tourter) Date: Wed, 16 Mar 2022 00:50:43 +0000 Subject: [Slackbuilds-users] netcdf package update In-Reply-To: References: <1761764.LH7GnMWURc@wintermute.sprawl.net> Message-ID: Hi I was wondering if it would be ok if I updated netcdf again. I have just realised that one of my packages (cdo), although it compiles fine with the version of netcdf in the repo, actually outputs incorrect data in some cases. compiling against the latest version of netcdf (4.8.1 - which also brings a few new features including zarr support) fixes the issue. I would of course check all it dependees (a few of which I maintain anyway) Cheers Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgrundy at gmail.com Wed Mar 16 01:58:47 2022 From: bgrundy at gmail.com (Barry J. Grundy) Date: Tue, 15 Mar 2022 21:58:47 -0400 Subject: [Slackbuilds-users] udiskie builds but fails to run on 15.0 Message-ID: <4d4ee2be-a92e-88f0-2c9b-01f66440cec6@gmail.com> Hello all, system/udiskie requires "gi" to run (from pygobject3). It's currently built using python2 with docopt and python2-PyYAML as deps. The build completes without error, but will not run (module gi not found). Building for python3 fixes the issue. Pygobject3 and python(3)-PyYAML are included in 15.0. The docopt SB already includes py3 support. So the only dep is now docopt. Thanks, Barry From yalhcru at gmail.com Wed Mar 16 03:56:19 2022 From: yalhcru at gmail.com (B Watson) Date: Tue, 15 Mar 2022 23:56:19 -0400 Subject: [Slackbuilds-users] Updated list of builds that were removed for 15.0 Message-ID: Since the list I posted before had some stuff that wasn't really removed, here's a corrected version. https://slackware.uk/~urchlay/src/sbo-removed-for-15.0.txt Some of these wouldn't be hard to get building on 15.0. I just re-added games/rejoystick, it needed a minor tweak to its configure command (LIBS="-lX11"). Some of them are never going to happen, e.g. KDE4 apps. Rest of this mail is the list (same as the URL above). academic/Mnemosyne: Removed (requires nonexistent PyQtWebEngine dep). academic/QtiPlot: Removed. academic/Xyce: Removed (ftb). academic/abella: Removed (ftb). academic/avogadro: Removed. academic/bpp-core: Removed (ftb + no active maintainer). academic/bpp-phyl-omics: Removed (ftb + no active maintainer). academic/bpp-phyl: Removed (ftb + no active maintainer). academic/bpp-popgen: Removed (ftb + no active maintainer). academic/bpp-seq-omics: Removed (ftb + no active maintainer). academic/bpp-seq: Removed (ftb + no active maintainer). academic/bpp1.9-numcalc: Removed (ftb + no active maintainer). academic/bpp1.9-phyl: Removed (ftb + no active maintainer). academic/bpp1.9-seq: Removed (ftb + no active maintainer). academic/bpp1.9-utils: Removed (ftb + no active maintainer). academic/bppsuite: Removed (ftb + no active maintainer). academic/coq: Removed (ftb). academic/drawtiming: Removed (incompatible with the newer gcc). academic/flashqard: Removed (no qt4-webkit available). academic/gcompris: Removed. academic/prank-msa: Removed (ftb + no active maintainer). academic/treerecs: Removed (ftb + no active maintainer). academic/vCAPS_coevolution: Removed (ftb + no active maintainer). audio/Pd-extended: Removed (ftbfs) audio/cuberok: Removed (unmaintained, qt4). audio/lastfm: Removed (because libraries/lastfm was removed). audio/llcon: Removed (abandoned, ftbfs). audio/spandsp: Removed (roger-router is removed). business/AssociationSubscribersManager: Removed (abandoned, ftbfs). business/lemonpos: Removed (requires KDE4). desktop/cairo-compmgr: Removed. desktop/crystal: Removed (no more kde4). desktop/gtk-kde4: Removed (no more kde4). desktop/homerun: Removed (no more kde4). desktop/kcometen4: Removed (no more kde4). desktop/kover: Removed (no more kde4). desktop/plasma-adjustable-clock: Removed (no more kde4). desktop/plasma-applet-daisy: Removed (no more kde4). desktop/plasma-eyasdp: Removed (no more kde4). desktop/plasma-geek-clock: Removed (no more kde4). desktop/plasma-widget-menubar: Removed (abandonded ftbfs). desktop/ptbatterysystemtray: Removed (abandoned upstream). desktop/qt-recordmydesktop: Removed (needs PyQt4). desktop/qtcurve: Removed (no more kde4). desktop/quadkonsole4: Removed (no more kde4). desktop/quickaccess: Removed (no more kde4). desktop/recorditnow: Removed (no more kde4). desktop/screensaver-icon: Removed (source does not exist). desktop/simon: Removed (no more kde4). desktop/simplenote: Removed (abandoned by SBo maintainer) desktop/vertex-maia-themes: Removed. desktop/vivacious-colors-gtk-icon-theme: Removed (does not work well with xfce 4.16) desktop/vivacious-colors-gtk-theme: Removed (does not work well with xfce 4.16) desktop/xfce4-embed-plugin: Removed (no more libxfce4ui-1). desktop/yawp: Removed (no more kde4). development/JSONObject: Removed (incompatible with the newer boost). development/adoptopenjdk-openj9: Removed (EOL). development/adoptopenjdk: Removed (EOL). development/ahven: Removed (needs gprbuild). development/atom: Removed (no maintainer). development/bacon: Removed (no maintainer). development/couchdb: Removed (ftb, no maintainer). development/eric: Removed (needs PyQt4). development/flow: Removed (ftb). development/fsharp: Removed (abandoned). development/gcclegacy494: Removed (FTB). development/jdk12: Removed (EOL). development/jdk13: Removed (EOL). development/jdk14: Removed (EOL). development/jdk15: Removed (EOL). development/jdk16: Removed (EOL). development/jupyter-ipyleaflet: Removed (abandoned). development/jupyter-ipywidgets: Removed (abandoned). development/jupyter-nbdime: Removed (abandoned). development/jupyter-widgetsnbextension: Removed (abandoned). development/libbitcoin: Removed (incompat boost 1.78). development/libodb-boost: Removed (abandoned). development/libodb-mysql: Removed (abandoned). development/libodb-pgsql: Removed (abandoned). development/libodb-qt: Removed (abandoned). development/libodb-sqlite: Removed (abandoned). development/libodb: Removed (abandoned). development/monkey-studio: Removed (no qt4-qscintilla). development/mono-debugger: Removed (abandoned and ftb). development/monodevelop: Removed (abandoned). development/mrustc: Removed (rust now in slackware). development/nuget: Removed (abandoned). development/numpy-legacy3: Removed (ftb). development/odb: Removed (abandoned). development/qt-creator2: Removed (abandoned). development/referenceassemblies-pcl: Removed (abandoned). development/sourcenav: Removed. development/swift: Removed (abandoned, ftbfs). development/xemacs: Removed (unmaintained @ SBo) games/chocolate_duke3D: Removed (broken and abandoned). games/ember: Removed (not compatible with latest OGRE). games/etlegacy-from-source: Removed (use the binary). games/gens-gs: Removed (no maintainer). games/glPortal: Removed (will not build against bullet 3.x, ran out of patience). games/qtsixa: Removed (FTBFS, unmaintained, replace someday with "sixad"). games/sumwars: Removed (ftbfs). gis/CreateCloudMap: Removed (Service is shut down). gis/spatialite_gui: Removed. graphics/freewrl: Removed (no maintainer, ftbfs). graphics/k3d: Removed (FTBFS). graphics/kamerka: Removed (KDE4 app, untouched since 2014). graphics/mitsuba-blender: Removed (ftbfs). graphics/mitsuba: Removed (ftbfs). graphics/mlbrot: Removed (ftb). graphics/rawstudio: Removed (FTBFS). graphics/separate+: Removed (crashed at runtime). graphics/teighaviewer: Removed (outdated binary-only software). graphics/yesplz: Removed (No longer maintained). ham/linlogbook: Removed. ham/qradiopredict: Removed. haskell/haskell-cabal-install: Removed (ftbfs, unmaintained). haskell/haskell-exceptions: Removed (part of ghc). haskell/haskell-hackage-security: Removed (ftbfs, unmaintained). haskell/haskell-hashed-storage: Removed (ftbfs, unmaintained). haskell/haskell-haskell-src: Removed (ftbfs, unmaintained). haskell/haskell-hslogger: Removed (ftbfs, unmaintained). haskell/haskell-http-api-data: Removed (ftbfs, unmaintained). haskell/haskell-megaparsec: Removed (ftbfs, no maintainer). haskell/haskell-mustache: Removed (ftbfs, no maintainer). haskell/haskell-neat-interpolation: Removed (ftbfs, no maintainer). haskell/haskell-optparse-simple: Removed (ftbfs, unmaintained). haskell/haskell-parallel: Removed (ftbfs, unmaintained). haskell/haskell-persistent-sqlite: Removed (ftbfs, unmaintained). haskell/haskell-persistent-template: Removed (ftbfs, unmaintained). haskell/haskell-persistent: Removed (ftbfs, unmaintained). haskell/haskell-stack: Removed (ftbfs, unmaintained). haskell/haskell-store: Removed (ftbfs, unmaintained). kildclient: Version updated. Added new dependency for gtkspell3. Removed perl-JSON dependency. libraries/DirectFB: Removed (old age, lack of use). libraries/GtkD: Removed (not used by any slackbuild) libraries/PyQwt: Removed (needs PyQt4). libraries/appmenu-qt: Removed (orphaned - qt4 + ftbfs). libraries/atlas: Removed (use OpenBLAS). libraries/beignet: Removed (incompatible with the newer llvm). libraries/cppo: Removed (ftb). libraries/db46: Removed (not needed, and conflicts with Slack db48) libraries/dbus-sharp-glib: Removed (dbus-sharp ftbfs) libraries/dbus-sharp: Removed (ftbfs) libraries/folly: Removed (orphaned and FTB). libraries/gazebo: Removed (no qt4-webkit available). libraries/glfw: Removed (no dependees, conflicts with glfw3). libraries/gstreamer-editing-services: Removed. libraries/gtk-qt-engine: Removed (abandoned ftbfs). libraries/hinnant-date: Removed (included in sqlpp11). libraries/hpx: Removed (orphaned and FTB). libraries/hug: Removed (no maintainer). libraries/lapack-atlas: Removed (Along with atlas). libraries/libgaiagraphics: Removed (obsoleted upstream). libraries/libido3: Removed. libraries/libquvi-scripts: Removed. libraries/libquvi: Removed (Not needed as cclive is removed). libraries/libsunpinyin: Removed (no maintainer). libraries/libtorrent-rasterbar-legacy: Removed. libraries/libtunepimp: Removed (ftbfs) libraries/mariadb_client: Removed (substituted by connector, FTB). libraries/ocaml-bisect: Removed (ftb). libraries/ocaml-ounit: Removed (ftb). libraries/opal: Removed. libraries/opencv-legacy: Removed (not compatible with opencv). libraries/pgplot: Removed (abandoned upstream and FTB). libraries/php-mssql: Removed (no more mssql ext in php 7.4.x). libraries/proxygen: Removed (orphaned and FTB). libraries/ptlib: Removed. libraries/qwt-qt5: Removed (redundant; use qwt). libraries/qwtpolar: Removed (FTBFS, and no dependees). libraries/ring-daemon: Removed (superseded by jami). libraries/ring-lrc: Removed (superseded by jami). libraries/sqlpp11-connector-mysql: Removed (included in sqlpp11). libraries/sqlpp11-connector-sqlite3: Removed (included in sqlpp11). libraries/t38modem-opal: Removed (missing dependency). libraries/t38modem-ptlib: Removed (incompatible with openssl-1.1.x). libraries/trilinos: Removed (no dependees; conflicts with mpich and openmpi) libraries/upscaledb: Removed (orphaned and FTB). libraries/vdpau-video: Removed (obsolete, abandoned upstream, FTB). libraries/vte3-ng: Removed (conflicts with vte in Slackware). libraries/wangle: Removed (orphaned and FTB). misc/Publican: Removed (missing perl dependencies). misc/fribid: Removed (not compatible with openssl-1.1.x). misc/hashkill: Removed (not compatible with openssl-1.1.x). misc/igal2: Removed (ftp + no active maintainer) misc/protobuf: Removed (use protobuf3 instead). misc/readesm: Removed (no qt4-webkit available). misc/scim-chewing: Removed (no scim in Slackware anymore). multimedia/OpenPHT: Removed (superseded by plex media player and plex htpc) multimedia/freshplayerplugin: Removed. multimedia/gecko-mediaplayer: Removed. multimedia/gst-plugins-bad: Removed (conflict w/Slackware gst-plugins-bad-free). multimedia/lwks: Removed (membership and licensing changes). multimedia/mythplugins: Removed (ftb + no active maintainer) multimedia/mythtv: Removed (ftb + no active maintainer) multimedia/pepperflash-plugin: Removed. multimedia/plex-home-theater: Removed (ftbs, upstream dead). multimedia/simpleburn: Removed (upstream is dead). multimedia/subtitlecomposer: Removed (needs kde4). multimedia/totem: Removed (no maintainer, ftbfs). network/Icecat: Removed (unmaintained, ftbfs). network/airpwn-ng: Removed network/arora: Removed (unmaintained upstream). network/base: Removed (ftp + no active maintainer) network/basilisk: Removed (upstream development suspended). network/bird: Removed (no maintainer). network/cclive: Removed (Not building on 15.0). network/corebird: Removed. network/dbmail: Removed. network/dclib: Removed. network/dobbscoin: Removed. network/dogecoin: Removed. network/elemental-ircd: Removed. network/emacs-w3m: Removed. network/etcd: Removed. network/ettercap-NG: Removed (incompatible with the newer openssl). network/fwbuilder: Removed (ftb + no active maintainer) network/ganglia-web: Removed. network/ganglia: Removed. network/gq: Removed. network/greenbone-security-assistant: Removed. network/gtmess: Removed. network/guacamole-server: Removed freerdp dep (part of slackware). network/guacamole-server: Removed. network/hylafax: Removed (ftb + no active maintainer) network/ike: Removed. network/imapproxy: Removed. network/iptv-analyzer: Removed. network/kadu: Removed (unmaintained). network/kcm_ufw: Removed. network/kfilebox: Removed. network/knemo: Removed. network/kobby: Removed (no kde4 anymore). network/libcapi20: Removed (roger-router is removed). network/libinfinity: Removed (unused). network/libqinfinity: Removed (unused). network/lighttpd2: Removed (still too unripe). network/linuxdcpp: Removed. network/mldonkey: Removed. network/ntop: Removed. network/openl2tp: Removed. network/openrdate: Removed. network/openvas-manager: Removed. network/pdnsd: Removed. network/pgl: Removed (No maintainer). network/pound: Removed. network/qutebrowser-tox: Removed. network/quvi: Removed (Not needed as cclive is removed). network/rekonq: Removed (KDE4 app). network/roger-router: Removed (source only for flatpak). network/sks-keyserver: Removed. network/slimjet: Removed (abandoned by SBo maintainer) network/smuxi: Removed (dbus-sharp dep ftbfs) network/squidGuard: Removed (upstream no longer maintained). network/t38modem: Removed (missing dependency). network/ucspi-ssl: Removed. network/vacuum-im: Removed (no maintainer). network/valknut: Removed. network/verm: Removed (unused, no dependees). network/wireguard-linux-compat: Removed (part of newer kernels). office/focuswriter-legacy: Removed (use focuswriter instead). office/fop-legacy: Removed (ftbfs) office/hyphen-id: Removed (merged with hunspell-id). office/kate-latex-plugin: Removed (KDE4 app; use kile instead). office/kchmviewer: Removed (redundant; use kchmviewer-qt). office/marave: Removed (PyQt4; unmaintained upstream since 2015) office/teams-for-linux: Removed (Use official teams). office/teapot: Removed (website and source are not available). office/wyrd: Removed (ftbfs) python/planes: Removed. python/python-branca: Removed (abandoned). python/python-poppler-qt4: Removed (needs poppler-qt4). python/python2-blake2: Removed (unused, python2, ftbfs). python/traittypes: Removed (abandoned). system/bareos-client: Removed (orphaned, ftbfs). system/bareos: Removed (orphaned, ftbfs). system/elo-mt-usb: Removed (download is gone, we dont have the hardware to test new versions). system/flSynclient: Removed (no maintainer). system/hebe: Removed (KDE4 app). system/kcm_touchpad: Removed (KDE4 app). system/kcollectd: Removed (KDE4 app). system/kitchen-sync: Removed (unused, no dependees). system/komparator4: Removed (KDE4 app). system/kvpm: Removed (KDE4 app). system/lxd: Removed (ftb, no maintainer). system/multicorn: Removed (FTBFS, even with debian patches and/or latest git). system/nvidia-legacy304-driver: Removed (unmaintained, ftbfs). system/nvidia-legacy304-kernel: Removed (unmaintained, ftbfs). system/oracle-xe: Removed (old version, not available for download). system/packagekit: Removed. system/python3-urwid: Removed. system/qingy: Removed (old age, lack of use). system/qingy_0.3_themepack: Removed (old age, lack of use). system/spl-solaris: Removed (fails to build, unused). system/suhosin: Removed (not compatible with newer PHP). system/termite: Removed (obsoleted by alacritty). system/tilix: Removed (ftbfs, no maintainer). system/tpe-kmod: Removed (ftbfs, no upstream activity). From sbo at linuxgalaxy.org Wed Mar 16 04:18:27 2022 From: sbo at linuxgalaxy.org (Slackbuilds) Date: Wed, 16 Mar 2022 04:18:27 +0000 Subject: [Slackbuilds-users] move cdw category Message-ID: <6a79818c-e6da-3e66-a3e5-69c0c50e1d7f@linuxgalaxy.org> Admins, I should have thought of this (or remembered?) earlier, but IMHO the category for cdw should be multimedia instead of system system/cdw -> multimedia/cdw to be with the other CD/DVD authoring tools. -kb From davidnchmelik at gmail.com Wed Mar 16 04:36:20 2022 From: davidnchmelik at gmail.com (David Chmelik) Date: Tue, 15 Mar 2022 21:36:20 -0700 Subject: [Slackbuilds-users] move cdw category In-Reply-To: <6a79818c-e6da-3e66-a3e5-69c0c50e1d7f@linuxgalaxy.org> References: <6a79818c-e6da-3e66-a3e5-69c0c50e1d7f@linuxgalaxy.org> Message-ID: <846f0e26-fe3e-6f55-5a62-1f2b984a0f5a@gmail.com> On 3/15/22 9:18 PM, Slackbuilds wrote: > [...] I should have thought of this (or remembered?) earlier, but IMHO the > category for cdw should be multimedia instead of system > > system/cdw -> multimedia/cdw > > to be with the other CD/DVD authoring tools. [...] Since people also make data/OS discs, I think those tools should mostly/all be system, just like tools for a floppy disc drive (FDD) would be. ??? I haven't made audio CDs since mid-to-late 1990s; since then it's only been several data CDs/DVDs and dozens OS ones... on certain older computers, sometimes a CD will boot better than USB or is the only option... ??? I don't think I'm alone on this? From yalhcru at gmail.com Wed Mar 16 05:21:42 2022 From: yalhcru at gmail.com (B Watson) Date: Wed, 16 Mar 2022 01:21:42 -0400 Subject: [Slackbuilds-users] move cdw category In-Reply-To: <6a79818c-e6da-3e66-a3e5-69c0c50e1d7f@linuxgalaxy.org> References: <6a79818c-e6da-3e66-a3e5-69c0c50e1d7f@linuxgalaxy.org> Message-ID: On 3/16/22, Slackbuilds wrote: > Admins, > > I should have thought of this (or remembered?) earlier, but IMHO the > category for cdw should be multimedia instead of system > > system/cdw -> multimedia/cdw > > to be with the other CD/DVD authoring tools. I agree in principle, all the CD/DVD creation tools should be in the same category (not 100% sure whether that should be system or multimedia)... but then we have a *lot* of builds that are in the wrong category, or that really belong in two categories (not possible of course). For instance, applications that are in python/ because they happen to be written in python. Or, python modules that should be in python/, but are in libraries/ instead. IMO, we should have finer-grained categories, like cd-authoring, or text-editors, or emulators. But that's unlikely to happen any time soon (would represent a lot of extra work for the admins, and we're unpaid volunteers). If cdw is your build, moving it would be no problem. Or, if you can convince its maintainer, he can move it easily enough. Otherwise, it'll have to stay where it is for now. From willysr at slackbuilds.org Wed Mar 16 16:33:47 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Mar 2022 23:33:47 +0700 Subject: [Slackbuilds-users] move cdw category In-Reply-To: <6a79818c-e6da-3e66-a3e5-69c0c50e1d7f@linuxgalaxy.org> References: <6a79818c-e6da-3e66-a3e5-69c0c50e1d7f@linuxgalaxy.org> Message-ID: > I should have thought of this (or remembered?) earlier, but IMHO the > category for cdw should be multimedia instead of system > > system/cdw -> multimedia/cdw > > to be with the other CD/DVD authoring tools. Most people will not really care about category anymore to be honest :) if they search for something and it came up, that's good enough -- 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 Wed Mar 16 17:00:01 2022 From: ml at mareichelt.com (Markus Reichelt) Date: Wed, 16 Mar 2022 18:00:01 +0100 Subject: [Slackbuilds-users] Tor is up for grabs In-Reply-To: References: Message-ID: * MDrights wrote: > Tor is not taken up by anyone yet, right? > I will take it. I know this thread is old, but: Your reply was the only one - after all those months, even with the crisis happening in Ukraine just recently. I therefore may rather optimistically assume that involved and caring Tor folks on Slackware just know their way around Tor... I've set up some bridges & relays myself, helped out where I could, and still do. Please be advised that the script, and config, need some adapting, bumping things to modern times, but Tor is yours if you still want it. If not, I'll keep holding up the torch. Let's return to giving (potentially new) maintainers that fancy 2 weeks grace period. We haven't heard from you back by April, then we know. And thank you for your interest in taking over Tor SlackBuild maintenance. Best regards, Markus From yakizarns1 at gmail.com Wed Mar 16 17:19:29 2022 From: yakizarns1 at gmail.com (Dionysis Ntreou) Date: Wed, 16 Mar 2022 17:19:29 +0000 Subject: [Slackbuilds-users] Tor is up for grabs In-Reply-To: References: Message-ID: Hello, I would like Tor too if nobody has taken it . Although I do not have the same experience as you Markus but I am keen to learn. Regards Dionysi On Wed, Mar 16, 2022 at 5:00 PM Markus Reichelt via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > * MDrights wrote: > > > Tor is not taken up by anyone yet, right? > > I will take it. > > I know this thread is old, but: > > Your reply was the only one - after all those months, even with the > crisis happening in Ukraine just recently. I therefore may rather > optimistically assume that involved and caring Tor folks on Slackware > just know their way around Tor... > > I've set up some bridges & relays myself, helped out where I could, > and still do. > > Please be advised that the script, and config, need some adapting, > bumping things to modern times, but Tor is yours if you still want > it. > > If not, I'll keep holding up the torch. Let's return to giving > (potentially new) maintainers that fancy 2 weeks grace period. > We haven't heard from you back by April, then we know. > > And thank you for your interest in taking over Tor SlackBuild > maintenance. > > Best regards, > Markus > _______________________________________________ > 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 Wed Mar 16 22:26:02 2022 From: ml at mareichelt.com (Markus Reichelt) Date: Wed, 16 Mar 2022 23:26:02 +0100 Subject: [Slackbuilds-users] Tor is up for grabs In-Reply-To: References: Message-ID: * Dionysis Ntreou wrote: > Hello, > I would like Tor too if nobody has taken it . Thank you for your interest. I would like to stick to the paragraph highlighted >> below for the short term, because Ukraine crisis happened. I feel an obligation to make this right. I've seen 'MDrights' work on this list before. so let's see what we can come up with together, eventually. > Although I do not have the same experience as you Markus but I am > keen to learn. We all started at some point. Kudos for starting in the first place. Mabye SBo manages to evolve to the point that there can be a team of maintainers for a given application. IMHO such an approach would need 'release signing keys' like so many other projects use. Not talking about how, or how fast one could get onto the team, it's about trust within the team. a working team is the goal. the team shall be resiliant. I was just thinking out loud... We'll see. There's time. > On Wed, Mar 16, 2022 at 5:00 PM Markus Reichelt via > SlackBuilds-users wrote: > > > * MDrights wrote: > > > > > Tor is not taken up by anyone yet, right? > > > I will take it. > > > > I know this thread is old, but: [...] > > >>> > If not, I'll keep holding up the torch. Let's return to giving >>> > (potentially new) maintainers that fancy 2 weeks grace period. >>> > We haven't heard from you back by April, then we know. From psychi2009 at gmail.com Thu Mar 17 01:43:16 2022 From: psychi2009 at gmail.com (MDrights) Date: Thu, 17 Mar 2022 01:43:16 +0000 Subject: [Slackbuilds-users] Tor is up for grabs In-Reply-To: References: Message-ID: Hi Markus, Thanks for raising this thread again, after several months! I thought my request was forgotten by folks :) Yes, I am glad to take on Tor Slackbuild. I have been a long time Tor user as well :) I will submit an updated script shortly. My slackbuilds fork: https://gitlab.com/mdrights/slackbuilds/-/tree/local Let me know if any of you folks have any suggestions/concerns. (I am really feeling painful for the situation in Ukraine. God bless. and hope Tor may help.) Cheers, MDrights On Wed, Mar 16, 2022 at 11:26:02PM +0100, Markus Reichelt via SlackBuilds-users wrote: > * Dionysis Ntreou wrote: > > > Hello, > > I would like Tor too if nobody has taken it . > > Thank you for your interest. I would like to stick to the paragraph > highlighted >> below for the short term, because Ukraine crisis > happened. I feel an obligation to make this right. I've seen > 'MDrights' work on this list before. > > so let's see what we can come up with together, eventually. > > > > Although I do not have the same experience as you Markus but I am > > keen to learn. > > We all started at some point. Kudos for starting in the first place. > > Mabye SBo manages to evolve to the point that there can be a team > of maintainers for a given application. IMHO such an approach would > need 'release signing keys' like so many other projects use. > > Not talking about how, or how fast one could get onto the team, it's > about trust within the team. a working team is the goal. the team > shall be resiliant. > > I was just thinking out loud... > > We'll see. There's time. > > > > > On Wed, Mar 16, 2022 at 5:00 PM Markus Reichelt via > > SlackBuilds-users wrote: > > > > > * MDrights wrote: > > > > > > > Tor is not taken up by anyone yet, right? > > > > I will take it. > > > > > > I know this thread is old, but: [...] > > > > >>> > If not, I'll keep holding up the torch. Let's return to giving > >>> > (potentially new) maintainers that fancy 2 weeks grace period. > >>> > We haven't heard from you back by April, then we know. > > _______________________________________________ > 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 dave at slackbuilds.org Thu Mar 17 02:31:43 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Thu, 17 Mar 2022 02:31:43 +0000 Subject: [Slackbuilds-users] Tor is up for grabs In-Reply-To: References: Message-ID: <20220317023142.GO30716@localhost> On 17/03/22 01:43, MDrights put forth the proposition: > Hi Markus, > Thanks for raising this thread again, after several months! > I thought my request was forgotten by folks :) > Yes, I am glad to take on Tor Slackbuild. I have been a long time Tor user as well :) > I will submit an updated script shortly. > My slackbuilds fork: https://gitlab.com/mdrights/slackbuilds/-/tree/local > Let me know if any of you folks have any suggestions/concerns. > (I am really feeling painful for the situation in Ukraine. God bless. and hope Tor may help.) > Cheers, > MDrights > On Wed, Mar 16, 2022 at 11:26:02PM +0100, Markus Reichelt via SlackBuilds-users wrote: > > * Dionysis Ntreou wrote: > > > > > Hello, > > > I would like Tor too if nobody has taken it . > > > > Thank you for your interest. I would like to stick to the paragraph > > highlighted >> below for the short term, because Ukraine crisis > > happened. I feel an obligation to make this right. I've seen > > 'MDrights' work on this list before. > > > > so let's see what we can come up with together, eventually. > > > > > > > Although I do not have the same experience as you Markus but I am > > > keen to learn. > > > > We all started at some point. Kudos for starting in the first place. > > > > Mabye SBo manages to evolve to the point that there can be a team > > of maintainers for a given application. IMHO such an approach would > > need 'release signing keys' like so many other projects use. > > > > Not talking about how, or how fast one could get onto the team, it's > > about trust within the team. a working team is the goal. the team > > shall be resiliant. > > > > I was just thinking out loud... > > > > We'll see. There's time. > > > > > > > > > On Wed, Mar 16, 2022 at 5:00 PM Markus Reichelt via > > > SlackBuilds-users wrote: > > > > > > > * MDrights wrote: > > > > > > > > > Tor is not taken up by anyone yet, right? > > > > > I will take it. > > > > > > > > I know this thread is old, but: [...] > > > > > > >>> > If not, I'll keep holding up the torch. Let's return to giving > > >>> > (potentially new) maintainers that fancy 2 weeks grace period. > > >>> > We haven't heard from you back by April, then we know. Since MDrights was the first to say he'd take it I've added him as new maintainer in my branch. Thanks -- Dave From willysr at slackbuilds.org Thu Mar 17 19:34:08 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 18 Mar 2022 02:34:08 +0700 Subject: [Slackbuilds-users] Updates - 20220317.1 Message-ID: Hey guys, For the last few days we have been making a lot of changes (almost 1.5k commits in this batch of update alone) consists of fixing build failures on x86 (still ongoing process), renaming for python scripts, and fixing READMEs. Make sure not to break the READMEs again in the future. Just another reminder that submission form is NOT YET opened and new scripts should go via submission form and not submitted via github/gitlab. Thu Mar 17 17:28:01 UTC 2022 academic/bowtie2: Mark x86 as unsupported. academic/bowtie: Mark x86 as unsupported. academic/celestia: Wrap README at 72 columns. academic/ds9: Wrap README at 72 columns. academic/fiji: Fix 32bit build. academic/fiji: Fix source name on 32bit. academic/gcompris-qt: Updated for version 2.3.1. academic/labplot2: Wrap README at 72 columns. academic/ladr: Wrap README at 72 columns. academic/ncbi-blast+: Fix build on i586. academic/octave: Wrap README at 72 columns. academic/qrupdate: Wrap README at 72 columns. academic/root: Actually install doinst.sh. academic/scipy3: Wrap README at 72 columns. academic/spqr: Wrap README at 72 columns. academic/suitesparse: Wrap README at 72 columns. academic/treebest-ensembl: Wrap README at 72 columns. academic/ugene: Wrap README at 72 columns. academic/umfpack: Wrap README at 72 columns. academic/verilator: Make slack-desc ASCII. academic/xflr5: Wrap README at 72 columns. accessibility/eflite: Wrap README at 72 columns. audio/TiMidity++: Handle content-disposition download. audio/amSynth: Wrap README at 72 columns. audio/clementine: Wrap README at 72 columns. audio/clockchimes: Wrap README at 72 columns. audio/cmus: Wrap README at 72 columns. audio/darkice: Wrap README at 72 columns. audio/deadbeef: Wrap README at 72 columns. audio/gnump3d: Wrap README at 72 columns. audio/google-musicmanager: Fix broken symlink. audio/jack_capture: Wrap README at 72 columns. audio/rhythmbox: Wrap README at 72 columns. audio/tta: Fix 32-bit build. desktop/Qogir-icon-theme: Fix VERSION in script. desktop/Surfn: Fix VERSION in script. desktop/bumblebee-status: Wrap README at 72 columns. desktop/e16: Remove template comment. desktop/obshutdown: Fix DOWNLOAD/HOMEPAGE. desktop/xdm-slackware-theme: Wrap README at 72 columns. development/J-Link: Wrap README at 72 columns. development/android-tools: Add network warning to README. development/apache-maven: Updated for version 3.8.5. development/bluefish: Wrap README at 72 columns. development/dfu-programmer: Move setup instructions to README.SBo. development/f2c: Remove template comment. development/gcc5: Fix sbolint nitpicks. development/git-extras: Wrap README at 72 columns. development/github-cli: Updated for version 2.6.0 development/golang-googlecode-gotools: Wrap README at 72 columns. development/hugo: Updated for version 94.2. development/jdk11: Wrap README at 72 columns. development/jupyter-nbclient: Update for 0.5.13 development/jupyter-nbconvert: Update for 6.4.3 development/jupyterlab_pygments: Wrap README at 72 columns. development/lighttable: Add network warning to README. development/mysql-workbench: Wrap README at 72 columns. development/nodejs: Updated for version 17.7.1. development/openjdk7: Move template preamble to top of script. development/php-xdebug: Fix PRGNAM in script. development/racer: Add network warning to README. development/racer: Wrap README at 72 columns. development/sbcl: Updated for version 2.2.2 development/shc: Fix DOWNLOAD. development/shc: Wrap README at 72 columns. development/shiboken2: Wrap README at 72 columns. development/sqlcl: Wrap README at 72 columns. development/sqlitebrowser: Wrap README at 72 columns. development/tora: Fix VERSION in script. development/vscode-bin: Updated for version 3.6.1. games/clksignal-roms: Host 2 of the downloads under sane names. games/dmagnetic: gzip the man pages. games/jin: Update email games/lutris: Updated for version 0.5.9.1, new maintainer games/m64py: Remove template comment. games/scid_vs_pc: Wrap README at 72 columns. games/scummvm: Wrap README at 72 columns. games/sl: Wrap README at 72 columns. games/smashbattle: Wrap README at 72 columns. games/solarus-quest-editor: Wrap README at 72 columns. games/speed-dreams: Wrap README at 72 columns. games/steam: Wrap README at 72 columns. games/tintin: Wrap README at 72 columns. games/tome-ah: Wrap README at 72 columns. games/trigger-rally: Wrap README at 72 columns. games/tuxnes: Wrap README at 72 columns. games/uligo: Wrap README at 72 columns. games/ut2004: Wrap README at 72 columns. games/vcmi: updated for version 0.99_git20220314 games/voxelands: Wrap README at 72 columns. games/warzone2100: Wrap README at 72 columns. games/warzone2100: updated for version 4.2.7 games/wesnoth: Wrap README at 72 columns. games/worldofgoo: Wrap README at 72 columns. games/xroar-roms: Get rid of duplicate ROMs. games/xye: Wrap README at 72 columns. games/yamagi-quake2: Wrap README at 72 columns. games/zaz: Wrap README at 72 columns. games/zelda-roth-se: Wrap README at 72 columns. games/zseal: Wrap README at 72 columns. gis/Fiona: Wrap README at 72 columns. gis/Geohash: Wrap README at 72 columns. gis/OTB: Wrap README at 72 columns. gis/SFCGAL: Wrap README at 72 columns. gis/TauDEM: Wrap README at 72 columns. gis/geographiclib-python: Wrap README at 72 columns. gis/geopandas: Changed REQUIRES for python3-psycopg2 gis/geopandas: Wrap README at 72 columns. gis/gpsbabel: Wrap README at 72 columns. gis/grass: Wrap README at 72 columns. gis/josm: Wrap README at 72 columns. gis/laszip: Wrap README at 72 columns. gis/libspatialindex: Wrap README at 72 columns. gis/libspatialite: Wrap README at 72 columns. gis/mapnik: Wrap README at 72 columns. gis/opengrads: Wrap README at 72 columns. gis/openorienteering-mapper: Wrap README at 72 columns. gis/osgEarth: Wrap README at 72 columns. gis/osm-gps-map: Wrap README at 72 columns. gis/ossim: Wrap README at 72 columns. gis/pdal: Wrap README at 72 columns. gis/pgrouting: Wrap README at 72 columns. gis/pgsql-ogr-fdw: Wrap README at 72 columns. gis/pktools: Wrap README at 72 columns. gis/pointcloud: Wrap README at 72 columns. gis/polyline: Wrap README at 72 columns. gis/postgis: Wrap README at 72 columns. gis/python-mapnik: Fix VERSION in script. gis/python-pygeos: Wrap README at 72 columns. gis/python3-cartopy: Wrap README at 72 columns. gis/python3-pyproj: Wrap README at 72 columns. gis/python3-pyshp: Wrap README at 72 columns. gis/python3-xarray: Wrap README at 72 columns. gis/qgis: Changed REQUIRES for python3-psycopg2 gis/qgis: Wrap README at 72 columns. gis/rasterio: Wrap README at 72 columns. gis/routino: Wrap README at 72 columns. gis/saga-gis: Wrap README at 72 columns. gis/spatialite-tools: Wrap README at 72 columns. gis/tangogps: Wrap README at 72 columns. gis/whitebox-tools: Wrap README at 72 columns. gis/xplanet: Wrap README at 72 columns. graphics/Blender: Wrap README at 72 columns. graphics/FreeCAD: Wrap README at 72 columns. graphics/LDView: Wrap README at 72 columns. graphics/SweetHome3D: Update email graphics/VariCAD: Wrap README at 72 columns. graphics/XnViewMP: Wrap README at 72 columns. graphics/abcm2ps: Wrap README at 72 columns. graphics/aewan: Wrap README at 72 columns. graphics/apitrace: Wrap README at 72 columns. graphics/brlcad: Wrap README at 72 columns. graphics/converseen: Updated for version 0.9.9.5. graphics/darktable: Wrap README at 72 columns. graphics/dia: Wrap README at 72 columns. graphics/dvisvgm: Wrap README at 72 columns. graphics/embree: Make slack-desc ASCII. graphics/embree: Wrap README at 72 columns. graphics/enblend-enfuse: Wrap README at 72 columns. graphics/fbpic: Wrap README at 72 columns. graphics/fig2sxd: Wrap README at 72 columns. graphics/fotowall: Wrap README at 72 columns. graphics/frescobaldi: Wrap README at 72 columns. graphics/fritzing: Wrap README at 72 columns. graphics/gliv: Wrap README at 72 columns. graphics/gnome-themes-extras: Wrap README at 72 columns. graphics/gpicview: Wrap README at 72 columns. graphics/gpscorrelate: Wrap README at 72 columns. graphics/graph-easy: Wrap README at 72 columns. graphics/gthumb: Wrap README at 72 columns. graphics/img2pdf: Remove tabs from README. graphics/imgmin: Wrap README at 72 columns. graphics/jp2a: Wrap README at 72 columns. graphics/jpeg2ps: Wrap README at 72 columns. graphics/leocad_pieces: Wrap README at 72 columns. graphics/maim: Wrap README at 72 columns. graphics/meshlab: Wrap README at 72 columns. graphics/nsxiv: Updated for version 29 graphics/nvidia-texture-tools: Wrap README at 72 columns. graphics/openclipart: Wrap README at 72 columns. graphics/opencollada: Wrap README at 72 columns. graphics/openscad-mcad: Fix VERSION in script. graphics/openscad: Wrap README at 72 columns. graphics/paraview: Wrap README at 72 columns. graphics/pdf2png: Wrap README at 72 columns. graphics/pencil3: Wrap README at 72 columns. graphics/pho: Wrap README at 72 columns. graphics/png2ico: Wrap README at 72 columns. graphics/pngcrush: Wrap README at 72 columns. graphics/potrace: Wrap README at 72 columns. graphics/pygraphviz: Wrap README at 72 columns. graphics/qcad: Wrap README at 72 columns. graphics/rawtherapee: Wrap README at 72 columns. graphics/scrot: Wrap README at 72 columns. graphics/tesseract: Wrap README at 72 columns. graphics/tgif-QPL: Wrap README at 72 columns. graphics/tkpng: Wrap README at 72 columns. graphics/trimage: Wrap README at 72 columns. graphics/ueberzug: Make slack-desc ASCII. graphics/ufraw: Wrap README at 72 columns. graphics/unpaper: Wrap README at 72 columns. graphics/vuescan: Updated for version 9.7.80. graphics/wavelet-denoise: Wrap README at 72 columns. graphics/whyteboard: Wrap README at 72 columns. graphics/xcalib: Wrap README at 72 columns. graphics/xdot: Wrap README at 72 columns. graphics/yafaray-blender: Wrap README at 72 columns. graphics/zgv: Wrap README at 72 columns. ham/ax25-apps: Wrap README at 72 columns. ham/baudline: Wrap README at 72 columns. ham/csdr: Wrap README at 72 columns. ham/cwdaemon: Wrap README at 72 columns. ham/ebook2cw: Wrap README at 72 columns. ham/grig: Wrap README at 72 columns. ham/libax25: Wrap README at 72 columns. ham/svxlink-sounds-en_US-heather-16k: Wrap README at 72 columns. ham/svxlink: Wrap README at 72 columns. ham/tlf: Wrap README at 72 columns. ham/tqsl: Wrap README at 72 columns. ham/xfhell: Wrap README at 72 columns. ham/xpsk31: Wrap README at 72 columns. ham/xwxapt: Wrap README at 72 columns. haskell/ghc: Wrap README at 72 columns. haskell/haskell-HTTP: Wrap README at 72 columns. haskell/haskell-HUnit: Wrap README at 72 columns. haskell/haskell-ShellCheck: Wrap README at 72 columns. haskell/haskell-base16-bytestring: Wrap README at 72 columns. haskell/haskell-cgi: Wrap README at 72 columns. haskell/haskell-cmark: Wrap README at 72 columns. haskell/haskell-colour: Wrap README at 72 columns. haskell/haskell-digest: Wrap README at 72 columns. haskell/haskell-fail: Wrap README at 72 columns. haskell/haskell-graphviz: Wrap README at 72 columns. haskell/haskell-lpeg: Make slack-desc ASCII. haskell/haskell-memory: Wrap README at 72 columns. haskell/haskell-pandoc-types: Wrap README at 72 columns. haskell/haskell-polyparse: Wrap README at 72 columns. haskell/haskell-regex-applicative: Wrap README at 72 columns. haskell/haskell-texmath: Wrap README at 72 columns. haskell/haskell-zlib: Wrap README at 72 columns. libraries/BeautifulSoup: Wrap README at 72 columns. libraries/CGAL: Wrap README at 72 columns. libraries/CondConfigParser: Wrap README at 72 columns. libraries/ConfigParser: Wrap README at 72 columns. libraries/DevIL: Wrap README at 72 columns. libraries/FreeImage: Wrap README at 72 columns. libraries/Geraldo: Wrap README at 72 columns. libraries/Nevow: Wrap README at 72 columns. libraries/OpenBLAS: Wrap README at 72 columns. libraries/OpenCSG: Wrap README at 72 columns. libraries/OpenSceneGraph: Remove tabs from README. libraries/OpenSceneGraph: Wrap README at 72 columns. libraries/PyOpenGL: Wrap README at 72 columns. libraries/Pykka: Wrap README at 72 columns. libraries/SFML: Wrap README at 72 columns. libraries/Smarty: Wrap README at 72 columns. libraries/VTK: Wrap README at 72 columns. libraries/adodb: Wrap README at 72 columns. libraries/agg: Wrap README at 72 columns. libraries/allegro: Wrap README at 72 columns. libraries/antlr4: Add network warning to README. libraries/antlr4: Wrap README at 72 columns. libraries/barry: Wrap README at 72 columns. libraries/batinfo: Wrap README at 72 columns. libraries/bctoolbox: Wrap README at 72 columns. libraries/bitstream: Wrap README at 72 columns. libraries/blas: Wrap README at 72 columns. libraries/bluez-alsa: Wrap README at 72 columns. libraries/bzrtp: Wrap README at 72 columns. libraries/cal3d: Wrap README at 72 columns. libraries/cdk: Wrap README at 72 columns. libraries/cffi: Wrap README at 72 columns. libraries/confuse: Wrap README at 72 columns. libraries/console_bridge: Wrap README at 72 columns. libraries/crossguid: Wrap README at 72 columns. libraries/curses_ex: Wrap README at 72 columns. libraries/dcadec: Wrap README at 72 columns. libraries/dcmtk: Wrap README at 72 columns. libraries/edelib: Wrap README at 72 columns. libraries/efl: Wrap README at 72 columns. libraries/eris: Wrap README at 72 columns. libraries/evernote-python: Wrap README at 72 columns. libraries/exiftool: Wrap README at 72 columns. libraries/facebook-python: Wrap README at 72 columns. libraries/fcgi: Wrap README at 72 columns. libraries/fifechan: Wrap README at 72 columns. libraries/fltk: Wrap README at 72 columns. libraries/fox-toolkit-devel: Wrap README at 72 columns. libraries/freexl: Wrap README at 72 columns. libraries/ftplib: Wrap README at 72 columns. libraries/futures: Wrap README at 72 columns. libraries/gitdb2: Wrap README at 72 columns. libraries/gitdb: Wrap README at 72 columns. libraries/gl2ps: Wrap README at 72 columns. libraries/goffice0.8: Wrap README at 72 columns. libraries/grpc: Wrap README at 72 columns. libraries/gspell: Wrap README at 72 columns. libraries/gtkdatabox: Wrap README at 72 columns. libraries/gtkglarea: Wrap README at 72 columns. libraries/hdf: Wrap README at 72 columns. libraries/hoel: updated for version 1.4.19 libraries/http-parser: Wrap README at 72 columns. libraries/hurry-filesize: Wrap README at 72 columns. libraries/iddawc: Wrap README at 72 columns. libraries/ignition-transport: Wrap README at 72 columns. libraries/iksemel: Wrap README at 72 columns. libraries/imlib: Wrap README at 72 columns. libraries/irrlicht: Wrap README at 72 columns. libraries/isodate: Wrap README at 72 columns. libraries/itcl: Wrap README at 72 columns. libraries/lablgtk: Wrap README at 72 columns. libraries/lapack: Wrap README at 72 columns. libraries/levmar: Wrap README at 72 columns. libraries/libEMF: Wrap README at 72 columns. libraries/libaacs: Wrap README at 72 columns. libraries/libass: Wrap README at 72 columns. libraries/libavc1394: Update email libraries/libavc1394: Wrap README at 72 columns. libraries/libb64: Wrap README at 72 columns. libraries/libbde: Wrap README at 72 columns. libraries/libbdplus: Wrap README at 72 columns. libraries/libbsd: Wrap README at 72 columns. libraries/libbtbb: Wrap README at 72 columns. libraries/libcangjie: Wrap README at 72 columns. libraries/libcbor: Wrap README at 72 columns. libraries/libcec: Wrap README at 72 columns. libraries/libchewing: Wrap README at 72 columns. libraries/libcli: Wrap README at 72 columns. libraries/libdbh2: Wrap README at 72 columns. libraries/libdc1394: Wrap README at 72 columns. libraries/libdca: Wrap README at 72 columns. libraries/libdv: Wrap README at 72 columns. libraries/libeatmydata: Wrap README at 72 columns. libraries/libesedb: Wrap README at 72 columns. libraries/libesmtp: Wrap README at 72 columns. libraries/libexe: Wrap README at 72 columns. libraries/libfaketime: Wrap README at 72 columns. libraries/libg15: Wrap README at 72 columns. libraries/libg15render: Wrap README at 72 columns. libraries/libgit2-glib: Wrap README at 72 columns. libraries/libgit2: Wrap README at 72 columns. libraries/libgnomecanvas: Wrap README at 72 columns. libraries/libgnomecups: Wrap README at 72 columns. libraries/libgsasl: Wrap README at 72 columns. libraries/libharu: Wrap README at 72 columns. libraries/libhid: Wrap README at 72 columns. libraries/libhtp: Wrap README at 72 columns. libraries/libiec61883: Update email libraries/libiec61883: Wrap README at 72 columns. libraries/libindi-drivers: Update email libraries/libindi: Update email libraries/libindi: Wrap README at 72 columns. libraries/libiptcdata: Wrap README at 72 columns. libraries/libircclient: Wrap README at 72 columns. libraries/libisoburn: Wrap README at 72 columns. libraries/libkate: Wrap README at 72 columns. libraries/libkml: Wrap README at 72 columns. libraries/liblightgrep: Wrap README at 72 columns. libraries/liblxi: Wrap README at 72 columns. libraries/libmicrohttpd: Wrap README at 72 columns. libraries/libmimic: Wrap README at 72 columns. libraries/libmpdclient: Wrap README at 72 columns. libraries/libmsiecf: Wrap README at 72 columns. libraries/libmspack: Wrap README at 72 columns. libraries/libmusicbrainz3: Wrap README at 72 columns. libraries/libmusicbrainz5: Wrap README at 72 columns. libraries/libnids: Wrap README at 72 columns. libraries/liboglappth: Wrap README at 72 columns. libraries/libolecf: Wrap README at 72 columns. libraries/libotr: Wrap README at 72 columns. libraries/libp11: Wrap README at 72 columns. libraries/libpar2: Wrap README at 72 columns. libraries/libpff: Wrap README at 72 columns. libraries/libpri: Wrap README at 72 columns. libraries/libqcow: Wrap README at 72 columns. libraries/librapi2: Wrap README at 72 columns. libraries/libraqm: Wrap README at 72 columns. libraries/libreadline-java: Wrap README at 72 columns. libraries/librsync: Wrap README at 72 columns. libraries/libscrypt: Wrap README at 72 columns. libraries/libshout: Wrap README at 72 columns. libraries/libslack: Wrap README at 72 columns. libraries/libsmraw: Wrap README at 72 columns. libraries/libsoup3: Update to 15.0 template. libraries/libsrtp: Wrap README at 72 columns. libraries/libsynce: Wrap README at 72 columns. libraries/libtermkey: Wrap README at 72 columns. libraries/libthai: Wrap README at 72 columns. libraries/libticonv: Wrap README at 72 columns. libraries/libtubo0: Wrap README at 72 columns. libraries/libucil: Wrap README at 72 columns. libraries/libversion: Wrap README at 72 columns. libraries/libvhdi: Wrap README at 72 columns. libraries/libvirt: Wrap README at 72 columns. libraries/libvmime: Wrap README at 72 columns. libraries/libvorbisidec: Wrap README at 72 columns. libraries/libvshadow: Wrap README at 72 columns. libraries/libvslvm: Wrap README at 72 columns. libraries/libvterm: Wrap README at 72 columns. libraries/libwebsockets: Wrap README at 72 columns. libraries/libwhisker2: Wrap README at 72 columns. libraries/libxmi: Wrap README at 72 columns. libraries/libxml++: Wrap README at 72 columns. libraries/libxmp: Wrap README at 72 columns. libraries/live555: Wrap README at 72 columns. libraries/lockdev: Wrap README at 72 columns. libraries/log4net: Wrap README at 72 columns. libraries/lua-lpeg: Wrap README at 72 columns. libraries/lua-luv: Wrap README at 72 columns. libraries/lua-mpack: Wrap README at 72 columns. libraries/lua-posix: Wrap README at 72 columns. libraries/lunatic-python: Wrap README at 72 columns. libraries/meanwhile: Wrap README at 72 columns. libraries/menu-cache: Wrap README at 72 columns. libraries/mowitz: Wrap README at 72 columns. libraries/mpir: Wrap README at 72 columns. libraries/msgpack-c: Wrap README at 72 columns. libraries/mujs: Wrap README at 72 columns. libraries/mysql++: Wrap README at 72 columns. libraries/nextaw: Wrap README at 72 columns. libraries/nini: Wrap README at 72 columns. libraries/ocaml-batteries: Wrap README at 72 columns. libraries/ocaml-camomile: Wrap README at 72 columns. libraries/ocaml-findlib: Wrap README at 72 columns. libraries/opencl-amd: Wrap README at 72 columns. libraries/orcania: updated for version 2.2.2 libraries/paho-mqtt: Update to 15.0 template. libraries/paho-mqtt: Wrap README at 72 columns. libraries/pcl: Wrap README at 72 columns. libraries/pexpect: Wrap README at 72 columns. libraries/pgtcl-ng: Wrap README at 72 columns. libraries/physfs: Wrap README at 72 columns. libraries/plplot: Wrap README at 72 columns. libraries/progressbar: Wrap README at 72 columns. libraries/pycparser: Wrap README at 72 columns. libraries/pyftpdlib: Wrap README at 72 columns. libraries/pylast: Wrap README at 72 columns. libraries/pymdstat: Wrap README at 72 columns. libraries/pysendfile: Wrap README at 72 columns. libraries/python-efl: Wrap README at 72 columns. libraries/python-gnupg: Wrap README at 72 columns. libraries/python-meld3: Wrap README at 72 columns. libraries/rarfile: Wrap README at 72 columns. libraries/reportlab: Wrap README at 72 columns. libraries/rhino: Wrap README at 72 columns. libraries/robin-map: Wrap README at 72 columns. libraries/rpyc: Wrap README at 72 columns. libraries/rrdtool: Wrap README at 72 columns. libraries/rtorrent-python: Wrap README at 72 columns. libraries/rudiments: Wrap README at 72 columns. libraries/setproctitle: Wrap README at 72 columns. libraries/skalibs: Updated for version 2.11.2.0 libraries/soundtouch: Wrap README at 72 columns. libraries/spread-sheet-widget: Wrap README at 72 columns. libraries/sqlpp11: Add network warning to README. libraries/tDOM: Wrap README at 72 columns. libraries/tbb: Wrap README at 72 columns. libraries/tinyxml2: Wrap README at 72 columns. libraries/totem-pl-parser: Wrap README at 72 columns. libraries/tsocks: Wrap README at 72 columns. libraries/ulfius: updated for version 2.7.8 libraries/unibilium: Wrap README at 72 columns. libraries/unixODBC: Wrap README at 72 columns. libraries/urdfdom_headers: Wrap README at 72 columns. libraries/varconf: Wrap README at 72 columns. libraries/volk: Wrap README at 72 columns. libraries/web.py: Wrap README at 72 columns. libraries/wv: Wrap README at 72 columns. libraries/wxGTK3: Wrap README at 72 columns. libraries/wxGTK: Wrap README at 72 columns. libraries/wxPython3: Wrap README at 72 columns. libraries/wxPython4: Wrap README at 72 columns. libraries/wxPython: Wrap README at 72 columns. libraries/wxX11: Wrap README at 72 columns. libraries/xerces-c: Fix 32bit build. libraries/xforms: Wrap README at 72 columns. libraries/xmlrpc-c: Wrap README at 72 columns. libraries/yaz: Wrap README at 72 columns. libraries/yder: updated for version 1.4.15 libraries/zfec: Wrap README at 72 columns. libraries/zziplib: Wrap README at 72 columns. misc/ardesia: Wrap README at 72 columns. misc/asr-manpages: Wrap README at 72 columns. misc/bchunk: Wrap README at 72 columns. misc/beep: Wrap README at 72 columns. misc/biosdisk: Wrap README at 72 columns. misc/boncuk: Wrap README at 72 columns. misc/bsdmainutils: Wrap README at 72 columns. misc/ccze: Wrap README at 72 columns. misc/chm2pdf: Wrap README at 72 columns. misc/cksfv: Wrap README at 72 columns. misc/clawsker: Wrap README at 72 columns. misc/dcc: Wrap README at 72 columns. misc/dmg2img: Update email misc/drg2sbg: Wrap README at 72 columns. misc/dvtm: Wrap README at 72 columns. misc/dwdiff: Wrap README at 72 columns. misc/figlet-contributed: Wrap README at 72 columns. misc/funny-manpages: Wrap README at 72 columns. misc/g15composer: Wrap README at 72 columns. misc/g15daemon: Wrap README at 72 columns. misc/gcp: Wrap README at 72 columns. misc/goldencheetah: Wrap README at 72 columns. misc/gramps: Wrap README at 72 columns. misc/heimdall: Wrap README at 72 columns. misc/hoorex: Wrap README at 72 columns. misc/kasumi: Wrap README at 72 columns. misc/keychain: Wrap README at 72 columns. misc/kronometer: Wrap README at 72 columns. misc/ltunify: Wrap README at 72 columns. misc/mdic: Wrap README at 72 columns. misc/megatunix: Wrap README at 72 columns. misc/moedict-desktop.app: Wrap README at 72 columns. misc/mosquitto: Wrap README at 72 columns. misc/myclippings: Wrap README at 72 columns. misc/par2cmdline-tbb: Wrap README at 72 columns. misc/par2cmdline: Wrap README at 72 columns. misc/projectM: Wrap README at 72 columns. misc/recode: Wrap README at 72 columns. misc/rsnapshot: Wrap README at 72 columns. misc/solunar: Wrap README at 72 columns. misc/subsurface: Wrap README at 72 columns. misc/sunwait: Wrap README at 72 columns. misc/torrentinfo: Wrap README at 72 columns. misc/weather: Wrap README at 72 columns. misc/xdelta: Wrap README at 72 columns. misc/xwinwrap: Wrap README at 72 columns. misc/yara: Wrap README at 72 columns. misc/ykpers: Wrap README at 72 columns. multimedia/HandBrake: Wrap README at 72 columns. multimedia/Mopidy: Wrap README at 72 columns. multimedia/OpenLP: Wrap README at 72 columns. multimedia/SimpleSysexxer: Wrap README at 72 columns. multimedia/abcMIDI: Wrap README at 72 columns. multimedia/anyremote: Wrap README at 72 columns. multimedia/audiopreview: Wrap README at 72 columns. multimedia/avidemux: Wrap README at 72 columns. multimedia/castnow: Add network warning to README. multimedia/ccxstream: Wrap README at 72 columns. multimedia/dirac: Wrap README at 72 columns. multimedia/droidcam: Wrap README at 72 columns. multimedia/dsmidiwifi: Wrap README at 72 columns. multimedia/dvblast: Wrap README at 72 columns. multimedia/dvdrip: Wrap README at 72 columns. multimedia/exaile: Wrap README at 72 columns. multimedia/flvtool2: Wrap README at 72 columns. multimedia/gaupol: Wrap README at 72 columns. multimedia/genpuid: Wrap README at 72 columns. multimedia/gmidimonitor: Wrap README at 72 columns. multimedia/gmtp: Wrap README at 72 columns. multimedia/gnome-mplayer: Wrap README at 72 columns. multimedia/gnupod: Wrap README at 72 columns. multimedia/gpac: Wrap README at 72 columns. multimedia/gst-plugins-ugly: Wrap README at 72 columns. multimedia/gst0-plugins-ugly: Wrap README at 72 columns. multimedia/iat: Wrap README at 72 columns. multimedia/inputstream.adaptive: Remove template comment. multimedia/ivtv-utils: Wrap README at 72 columns. multimedia/jlscp: Wrap README at 72 columns. multimedia/minitube: Wrap README at 72 columns. multimedia/mjpegtools: Update email multimedia/mjpegtools: Wrap README at 72 columns. multimedia/mjpegtools: fix email multimedia/mp3fm: Wrap README at 72 columns. multimedia/mpgtx: Wrap README at 72 columns. multimedia/musixmatch: Make slack-desc ASCII. multimedia/obs-studio: Updated for version 27.2.3 multimedia/obs-studio: Wrap README at 72 columns. multimedia/oggconvert: Wrap README at 72 columns. multimedia/oggvideotools: Wrap README at 72 columns. multimedia/opencaster: Wrap README at 72 columns. multimedia/parole: Wrap README at 72 columns. multimedia/ripperX: Wrap README at 72 columns. multimedia/smpeg: Wrap README at 72 columns. multimedia/spek: Wrap README at 72 columns. multimedia/subtitleeditor: Wrap README at 72 columns. multimedia/subtitleripper: Wrap README at 72 columns. multimedia/tovid: Update email multimedia/tovid: Wrap README at 72 columns. multimedia/transcode: Wrap README at 72 columns. multimedia/tstools: Wrap README at 72 columns. multimedia/tvtime: Wrap README at 72 columns. multimedia/ucview: Wrap README at 72 columns. multimedia/vcdimager: Wrap README at 72 columns. multimedia/vlc: Wrap README at 72 columns. multimedia/wxcam: Update email multimedia/wxcam: Wrap README at 72 columns. multimedia/xjadeo: Wrap README at 72 columns. multimedia/xmltv: Wrap README at 72 columns. multimedia/xvid4conf: Wrap README at 72 columns. multimedia/yarock: Wrap README at 72 columns. multimedia/zvbi: Wrap README at 72 columns. network/3proxy: Wrap README at 72 columns. network/CherryMusic: Wrap README at 72 columns. network/ClusterSSH: Wrap README at 72 columns. network/DarTui: Wrap README at 72 columns. network/Flootty: Wrap README at 72 columns. network/Free-Cinema: Wrap README at 72 columns. network/GhostInTheMail: Wrap README at 72 columns. network/LOIC: Wrap README at 72 columns. network/NetworkManager-l2tp: Wrap README at 72 columns. network/Pafy: Wrap README at 72 columns. network/PyRSS2Gen: Wrap README at 72 columns. network/Pyrit: Wrap README at 72 columns. network/SoulseekQt: Wrap README at 72 columns. network/TeamSpeak3: Update email network/WhatWeb: Wrap README at 72 columns. network/aMule: Wrap README at 72 columns. network/amap: Wrap README at 72 columns. network/amavisd-new: Wrap README at 72 columns. network/arno-iptables-firewall: Wrap README at 72 columns. network/avahi: Wrap README at 72 columns. network/awstats: Wrap README at 72 columns. network/bip: Wrap README at 72 columns. network/bitlbee: Wrap README at 72 columns. network/brave-browser: Updated for version 1.35.112 network/btpd: Wrap README at 72 columns. network/c-toxcore: Wrap README at 72 columns. network/cacti: Wrap README at 72 columns. network/cadaver: Wrap README at 72 columns. network/cherokee: Wrap README at 72 columns. network/clamav-unofficial-sigs: Wrap README at 72 columns. network/claws-mail: Wrap README at 72 columns. network/cmdiag: Wrap README at 72 columns. network/cni-plugins: Add network warning to README. network/cni-plugins: Wrap README at 72 columns. network/comgt: Wrap README at 72 columns. network/corkscrew: Wrap README at 72 columns. network/csync: Wrap README at 72 columns. network/ctorrent: Wrap README at 72 columns. network/darkhttpd: Wrap README at 72 columns. network/darkstat: Wrap README at 72 columns. network/ddgr: Wrap README at 72 columns. network/deluge: Wrap README at 72 columns. network/dillo: Wrap README at 72 columns. network/dirb: Wrap README at 72 columns. network/dma: Wrap README at 72 columns. network/dmitry: Wrap README at 72 columns. network/dnscrypt-proxy: Wrap README at 72 columns. network/dnscrypt-wrapper: Wrap README at 72 columns. network/dnsmap: Wrap README at 72 columns. network/dnstop: Wrap README at 72 columns. network/dovecot-pigeonhole: Wrap README at 72 columns. network/driftnet: Wrap README at 72 columns. network/dropbox: Updated for version 144.4.4491. network/dsniff: Wrap README at 72 columns. network/easyrsa: Wrap README at 72 columns. network/efax-gtk: Wrap README at 72 columns. network/efax: Remove template comment. network/efax: Wrap README at 72 columns. network/eiskaltdcpp: Wrap README at 72 columns. network/emailrelay: Wrap README at 72 columns. network/enet: Wrap README at 72 columns. network/etherape: Wrap README at 72 columns. network/etherpad-lite: Add network warning to README. network/ettercap: Wrap README at 72 columns. network/exim: Wrap README at 72 columns. network/fdm: Wrap README at 72 columns. network/filezilla: Wrap README at 72 columns. network/firehol: Wrap README at 72 columns. network/flvstreamer: Wrap README at 72 columns. network/fping: Wrap README at 72 columns. network/freeradius-server: Wrap README at 72 columns. network/gajim: Wrap README at 72 columns. network/geoipupdate: Wrap README at 72 columns. network/glewlwyd: Wrap README at 72 columns. network/gns3: Wrap README at 72 columns. network/googler: Wrap README at 72 columns. network/gophernicus: Move setup instructions to README.SBo. network/graphite-carbon: Wrap README at 72 columns. network/gtk-gnutella: Wrap README at 72 columns. network/gui-ufw: Fix broken wrapper scripts. network/hamachi: Wrap README at 72 columns. network/haproxy: Wrap README at 72 columns. network/haskell-network-multicast: Wrap README at 72 columns. network/havp: Wrap README at 72 columns. network/host-sflow: Wrap README at 72 columns. network/hostsblock: Wrap README at 72 columns. network/hping3: Wrap README at 72 columns. network/httpie: Wrap README at 72 columns. network/icinga2: Wrap README at 72 columns. network/identicurse: Wrap README at 72 columns. network/inadyn: Wrap README at 72 columns. network/iodine: Wrap README at 72 columns. network/ipcalc: Wrap README at 72 columns. network/iperf: Wrap README at 72 columns. network/ircd-hybrid: Wrap README at 72 columns. network/isync: Wrap README at 72 columns. network/jabberd2: Wrap README at 72 columns. network/jboss-as: Wrap README at 72 columns. network/jitsi: Wrap README at 72 columns. network/kivy-garden: Wrap README at 72 columns. network/knock: Wrap README at 72 columns. network/leafnode: Wrap README at 72 columns. network/libmaxminddb: Wrap README at 72 columns. network/libnatpmp: Wrap README at 72 columns. network/libnfsidmap: Wrap README at 72 columns. network/light-firefox: Wrap README at 72 columns. network/linphone: Wrap README at 72 columns. network/linssid: Wrap README at 72 columns. network/livestreamer: Wrap README at 72 columns. network/lizardfs: Wrap README at 72 columns. network/lxi-tools: Wrap README at 72 columns. network/mailman: Wrap README at 72 columns. network/mailspring: Updated for version 1.10.1 network/malheur: Wrap README at 72 columns. network/masscan: Wrap README at 72 columns. network/megatools: Wrap README at 72 columns. network/memcached: Wrap README at 72 columns. network/mitmproxy-bin: Update to 15.0 template. network/mod_auth_kerb: Wrap README at 72 columns. network/mod_chroot: Wrap README at 72 columns. network/mod_evasive: Wrap README at 72 columns. network/mod_geoip2: Wrap README at 72 columns. network/mod_ruid2: Wrap README at 72 columns. network/mod_wsgi: Wrap README at 72 columns. network/monkey: Wrap README at 72 columns. network/mumble-server: Wrap README at 72 columns. network/mysecureshell: Wrap README at 72 columns. network/nagios: Wrap README at 72 columns. network/ncrack: Wrap README at 72 columns. network/netcat-openbsd: Update download URL network/netcat: Wrap README at 72 columns. network/netdiscover: Wrap README at 72 columns. network/netdrive-connector: Wrap README at 72 columns. network/netqmail: Wrap README at 72 columns. network/netsurf: Wrap README at 72 columns. network/newsboat: Wrap README at 72 columns. network/nextcloud-client: Wrap README at 72 columns. network/nginx: Wrap README at 72 columns. network/ngrep: Wrap README at 72 columns. network/ngrok: Wrap README at 72 columns. network/nikto: Wrap README at 72 columns. network/nrpe: Wrap README at 72 columns. network/nsca: Wrap README at 72 columns. network/nsd: Wrap README at 72 columns. network/nss-mdns: Wrap README at 72 columns. network/nweb: Fix VERSION in script. network/oidentd: Wrap README at 72 columns. network/onedrive: Updated to version 2.4.16 network/onionshare: Wrap README at 72 columns. network/openconnect: Wrap README at 72 columns. network/opendchub: Wrap README at 72 columns. network/opendkim: Wrap README at 72 columns. network/opendmarc: Wrap README at 72 columns. network/openntpd: Wrap README at 72 columns. network/opensmtpd: Wrap README at 72 columns. network/openvswitch-utils: Wrap README at 72 columns. network/owncloud-client: Wrap README at 72 columns. network/owncloud-server: Wrap README at 72 columns. network/p0f: Wrap README at 72 columns. network/pCloudDrive: Wrap README at 72 columns. network/packit: Wrap README at 72 columns. network/palemoon-bin: Wrap README at 72 columns. network/pdns: Remove tabs from README. network/periscope: Wrap README at 72 columns. network/pflogsumm: Wrap README at 72 columns. network/pfqueue: Wrap README at 72 columns. network/pgpool-II: Wrap README at 72 columns. network/phpmyadmin: Wrap README at 72 columns. network/pidgin-nudge: Wrap README at 72 columns. network/pidgin-otr: Wrap README at 72 columns. network/pidgin-privacy-please: Wrap README at 72 columns. network/pidgin-sound: Wrap README at 72 columns. network/plowshare: Wrap README at 72 columns. network/pmacct: Wrap README at 72 columns. network/policyd2: Wrap README at 72 columns. network/polipo: Wrap README at 72 columns. network/postgrey: Wrap README at 72 columns. network/pptpd: Wrap README at 72 columns. network/prosody-mod-turncredentials: Wrap README at 72 columns. network/prosody-mod-vcard-muc: Wrap README at 72 columns. network/protonvpn-cli: Remove template comment. network/protonvpn-cli: Update homepage and download link. network/proxymini: Wrap README at 72 columns. network/proxytunnel: Wrap README at 72 columns. network/psad: Wrap README at 72 columns. network/psi-plus: Add network warning to README. network/qTox: Wrap README at 72 columns. network/radvd: Wrap README at 72 columns. network/reaver: Wrap README at 72 columns. network/rejik: Wrap README at 72 columns. network/republicanywhere: Wrap README at 72 columns. network/retroshare: Wrap README at 72 columns. network/riot-web: Remove tabs from README. network/riot-web: Wrap README at 72 columns. network/rtl8821ce: Make slack-desc ASCII. network/seahub: Wrap README at 72 columns. network/shibboleth-sp: Wrap README at 72 columns. network/sickrage: Wrap README at 72 columns. network/siege: Wrap README at 72 columns. network/signal-desktop: Updated for version 5.35.0 network/silc-toolkit: Wrap README at 72 columns. network/skypeforlinux: Wrap README at 72 columns. network/slirp4netns: Wrap README at 72 columns. network/slowhttptest: Wrap README at 72 columns. network/smcroute: Wrap README at 72 columns. network/sniffjoke: Wrap README at 72 columns. network/snort: Wrap README at 72 columns. network/spamassassin: Wrap README at 72 columns. network/spambayes: Wrap README at 72 columns. network/speedometer: Wrap README at 72 columns. network/speedtest-cli: Wrap README at 72 columns. network/sqlninja: Wrap README at 72 columns. network/sqlrelay: Wrap README at 72 columns. network/squid: Wrap README at 72 columns. network/squidanalyzer: Wrap README at 72 columns. network/sshguard: Wrap README at 72 columns. network/sstp-client: Wrap README at 72 columns. network/strongswan: Wrap README at 72 columns. network/sylpheed: Wrap README at 72 columns. network/tahoe-lafs: Wrap README at 72 columns. network/tcpflow: Wrap README at 72 columns. network/teams: Make slack-desc ASCII. network/telegram: Updated for version 3.6.1. network/telegram: Wrap README at 72 columns. network/thrift: Wrap README at 72 columns. network/thttpd: Wrap README at 72 columns. network/tinc: Wrap README at 72 columns. network/tinyproxy: Wrap README at 72 columns. network/tmate: Wrap README at 72 columns. network/tor: New maintainer. network/toxcore: Wrap README at 72 columns. network/translate-shell: Wrap README at 72 columns. network/ttcp: Wrap README at 72 columns. network/ttdnsd: Wrap README at 72 columns. network/tunctl: Wrap README at 72 columns. network/turbolift: Wrap README at 72 columns. network/ubertooth: Wrap README at 72 columns. network/ucspi-tcp: Wrap README at 72 columns. network/udpcast: Wrap README at 72 columns. network/ufw: Wrap README at 72 columns. network/uget-chrome-wrapper: Wrap README at 72 columns. network/uget-integrator: Wrap README at 72 columns. network/urlgrabber: Wrap README at 72 columns. network/urlscan: Wrap README at 72 columns. network/urlview: Wrap README at 72 columns. network/uudeview: Wrap README at 72 columns. network/verlihub: Wrap README at 72 columns. network/vmware-horizon-client: Wrap README at 72 columns. network/vnstat: Move setup instructions to README.SBo. network/vnstat: Wrap README at 72 columns. network/vrrpd: Wrap README at 72 columns. network/w3af: Wrap README at 72 columns. network/webhook: Wrap README at 72 columns. network/weighmail: Wrap README at 72 columns. network/wendzelnntpd: Remove template comment. network/wildfly: Wrap README at 72 columns. network/wireshark: Wrap README at 72 columns. network/wmget: Wrap README at 72 columns. network/wmnotify: Wrap README at 72 columns. network/wp-cli: Remove tabs from README. network/wrk: Wrap README at 72 columns. network/wvdial: Wrap README at 72 columns. network/x11spice: Wrap README at 72 columns. network/x11vnc: Wrap README at 72 columns. network/x2goserver: Wrap README at 72 columns. network/xinetd: Wrap README at 72 columns. network/xl2tpd: Wrap README at 72 columns. network/xnetload: Wrap README at 72 columns. network/yadifa: Remove tabs from README. network/yate: Wrap README at 72 columns. network/youtube-dl-gui: Wrap README at 72 columns. network/zabbix_agentd: Wrap README at 72 columns. network/zabbix_java_gateway: Wrap README at 72 columns. network/zabbix_proxy: Wrap README at 72 columns. network/zabbix_server: Wrap README at 72 columns. network/zmap: Wrap README at 72 columns. network/znc: Wrap README at 72 columns. network/zoom-linux: Make slack-desc ASCII. office/FreeOffice: Make slack-desc ASCII. office/JabRef: Fix BUILD usage. office/LanguageTool: Wrap README at 72 columns. office/LibreOffice: Remove tabs from README. office/LibreOffice: Wrap README at 72 columns. office/Ted: Wrap README at 72 columns. office/adobe-reader-fontpacks: Wrap README at 72 columns. office/aigaion: Wrap README at 72 columns. office/anorack: Remove tabs from README. office/apvlv: Wrap README at 72 columns. office/basket: Wrap README at 72 columns. office/briss: Wrap README at 72 columns. office/broffice.org: Wrap README at 72 columns. office/calibre: Wrap README at 72 columns. office/cups-pdf: Wrap README at 72 columns. office/devtodo: Wrap README at 72 columns. office/ding: Wrap README at 72 columns. office/docx2txt: Wrap README at 72 columns. office/elyxer: Wrap README at 72 columns. office/epdfview: Wrap README at 72 columns. office/flowkeeper: Wrap README at 72 columns. office/ghostwriter: Remove template comment. office/homebank: Wrap README at 72 columns. office/htmldoc: Wrap README at 72 columns. office/jstock: Wrap README at 72 columns. office/keepassxc: Wrap README at 72 columns. office/keepnote: Wrap README at 72 columns. office/latex2rtf: Wrap README at 72 columns. office/lcal: Wrap README at 72 columns. office/libreoffice-langpack: Wrap README at 72 columns. office/minidjvu: Wrap README at 72 columns. office/moneydance: Wrap README at 72 columns. office/msee: Add network warning to README. office/msee: Wrap README at 72 columns. office/mu: Wrap README at 72 columns. office/multivalent-tool-pdf: Wrap README at 72 columns. office/odt2txt: Wrap README at 72 columns. office/pandoc: Wrap README at 72 columns. office/pdfpc: Wrap README at 72 columns. office/pdftk: Wrap README at 72 columns. office/ps2eps: Wrap README at 72 columns. office/pstoedit: Wrap README at 72 columns. office/pstotext: Wrap README at 72 columns. office/pyspread: Wrap README at 72 columns. office/scribus: Wrap README at 72 columns. office/t-prot: Wrap README at 72 columns. office/taskjuggler: Wrap README at 72 columns. office/taskopen: Wrap README at 72 columns. office/tellico: Wrap README at 72 columns. office/text2pdf: Wrap README at 72 columns. office/tpp: Wrap README at 72 columns. office/traduisons: Wrap README at 72 columns. office/trello-cli: Add network warning to README. office/tudu: Wrap README at 72 columns. office/verbiste: Wrap README at 72 columns. office/vmd: Wrap README at 72 columns. office/watson: Wrap README at 72 columns. office/xmind: Wrap README at 72 columns. perl/perl-Bit-Vector: Wrap README at 72 columns. perl/perl-CGI: Wrap README at 72 columns. perl/perl-CPAN-Changes: Wrap README at 72 columns. perl/perl-Carp-Clan: Wrap README at 72 columns. perl/perl-Class-Gomor: Wrap README at 72 columns. perl/perl-Config-File: Wrap README at 72 columns. perl/perl-Config-IniFiles: Wrap README at 72 columns. perl/perl-Convert-ASN1: Wrap README at 72 columns. perl/perl-Crypt-Blowfish_PP: Wrap README at 72 columns. perl/perl-Crypt-CAST5: Wrap README at 72 columns. perl/perl-Crypt-CBC: Wrap README at 72 columns. perl/perl-Crypt-IDEA: Wrap README at 72 columns. perl/perl-Crypt-OpenSSL-AES: Wrap README at 72 columns. perl/perl-Crypt-OpenSSL-Guess: Wrap README at 72 columns. perl/perl-Crypt-OpenSSL-RSA: Wrap README at 72 columns. perl/perl-Crypt-Rijndael: Wrap README at 72 columns. perl/perl-Data-UUID: Wrap README at 72 columns. perl/perl-Date-Calc: Wrap README at 72 columns. perl/perl-DateTime-Format-Builder: Wrap README at 72 columns. perl/perl-DateTime-Format-ISO8601: Wrap README at 72 columns. perl/perl-DateTime-Format-Strptime: Wrap README at 72 columns. perl/perl-Devel-PartialDump: Wrap README at 72 columns. perl/perl-Encode-Detect: Wrap README at 72 columns. perl/perl-ExtUtils-Install: Wrap README at 72 columns. perl/perl-ExtUtils-ModuleMaker: Wrap README at 72 columns. perl/perl-File-Copy-Recursive: Wrap README at 72 columns. perl/perl-File-Finder: Wrap README at 72 columns. perl/perl-File-Remove: Wrap README at 72 columns. perl/perl-File-ShareDir-Install: Wrap README at 72 columns. perl/perl-File-Slurp: Wrap README at 72 columns. perl/perl-Geo-IP: Wrap README at 72 columns. perl/perl-Geography-Countries: Wrap README at 72 columns. perl/perl-Gtk2-Ex-Simple-List: Wrap README at 72 columns. perl/perl-HTML-HTMLDoc: Wrap README at 72 columns. perl/perl-IO-All: Wrap README at 72 columns. perl/perl-IO-CaptureOutput: Wrap README at 72 columns. perl/perl-IO-Socket-INET6: Wrap README at 72 columns. perl/perl-IO-Socket-Multicast: Wrap README at 72 columns. perl/perl-IO-Tty: Wrap README at 72 columns. perl/perl-IO-stringy: Wrap README at 72 columns. perl/perl-Inline-C: Wrap README at 72 columns. perl/perl-List-AllUtils: Wrap README at 72 columns. perl/perl-Log-Dispatch: Wrap README at 72 columns. perl/perl-MIME-tools: Wrap README at 72 columns. perl/perl-Mail-SPF-Query: Wrap README at 72 columns. perl/perl-MailTools: Wrap README at 72 columns. perl/perl-Math-Base85: Wrap README at 72 columns. perl/perl-Module-Build: Wrap README at 72 columns. perl/perl-Mojolicious-Plugin-Humane: Wrap README at 72 columns. perl/perl-MooX-StrictConstructor: Wrap README at 72 columns. perl/perl-Net-CIDR-Lite: Wrap README at 72 columns. perl/perl-Net-CIDR: Wrap README at 72 columns. perl/perl-Net-IPv4Addr: Wrap README at 72 columns. perl/perl-Net-IPv6Addr: Wrap README at 72 columns. perl/perl-Net-Jabber: Wrap README at 72 columns. perl/perl-Net-LibIDN: Wrap README at 72 columns. perl/perl-Net-Libdnet: Wrap README at 72 columns. perl/perl-Net-Pcap: Wrap README at 72 columns. perl/perl-Net-RawIP: Wrap README at 72 columns. perl/perl-Net-SNMP: Wrap README at 72 columns. perl/perl-Net-Telnet: Wrap README at 72 columns. perl/perl-Net-Write: Wrap README at 72 columns. perl/perl-NetPacket: Wrap README at 72 columns. perl/perl-Pegex: Wrap README at 72 columns. perl/perl-Proc-PID-File: Wrap README at 72 columns. perl/perl-Scope-Guard: Wrap README at 72 columns. perl/perl-Socket6: Wrap README at 72 columns. perl/perl-Statistics-Descriptive: Wrap README at 72 columns. perl/perl-String-PerlIdentifier: Wrap README at 72 columns. perl/perl-Switch: Wrap README at 72 columns. perl/perl-Syntax-Highlight-Engine-Kate: Wrap README at 72 columns. perl/perl-Sys-Mmap: Wrap README at 72 columns. perl/perl-TeX-Hyphen: Wrap README at 72 columns. perl/perl-Term-ProgressBar: Wrap README at 72 columns. perl/perl-Test-LongString: Wrap README at 72 columns. perl/perl-Test-PerlTidy: Wrap README at 72 columns. perl/perl-Test-RequiresInternet: Wrap README at 72 columns. perl/perl-Test-Simple: Wrap README at 72 columns. perl/perl-Test-SubCalls: Wrap README at 72 columns. perl/perl-Text-CSV_XS: Wrap README at 72 columns. perl/perl-Text-Tabs+Wrap: Wrap README at 72 columns. perl/perl-TryCatch: Wrap README at 72 columns. perl/perl-Unicode-Map8: Wrap README at 72 columns. perl/perl-Unicode-Map: Wrap README at 72 columns. perl/perl-X11-Protocol-Other: Disable test by default (requires X). perl/perl-X11-Protocol-Other: Wrap README at 72 columns. perl/perl-XML-XPath: Wrap README at 72 columns. perl/perl-YAML-LibYAML: Wrap README at 72 columns. perl/perl-digest-hmac: Wrap README at 72 columns. perl/perl-encode-locale: Wrap README at 72 columns. perl/perl-file-desktopentry: Wrap README at 72 columns. perl/perl-file-listing: Wrap README at 72 columns. perl/perl-html-parser: Wrap README at 72 columns. perl/perl-http-tiny: Wrap README at 72 columns. perl/perl-inc-latest: Wrap README at 72 columns. perl/perl-x11-protocol: Wrap README at 72 columns. python/Baker: Wrap README at 72 columns. python/PyGreSQL: Wrap README at 72 columns. python/PyInstaller: Wrap README at 72 columns. python/PyPDF2: Wrap README at 72 columns. python/PyStemmer: Wrap README at 72 columns. python/PythonQt: Wrap README at 72 columns. python/RBTools: Wrap README at 72 columns. python/WebHelpers: Removed, replaced by WebHelpers2 on python3-webhelpers2 python/XlsxWriter: Wrap README at 72 columns. python/affine: Wrap README at 72 columns. python/anyjson: Removed, very old and not in any more REQUIRES python/apsw: Wrap README at 72 columns. python/argcomplete: Wrap README at 72 columns. python/argh: Wrap README at 72 columns. python/arrow: Wrap README at 72 columns. python/artifacts: Wrap README at 72 columns. python/asgiref: Wrap README at 72 columns. python/atomicwrites: Wrap README at 72 columns. python/backcall: Wrap README at 72 columns. python/backports.lzma: Wrap README at 72 columns. python/bencode: Wrap README at 72 columns. python/biplist: Wrap README at 72 columns. python/bleach: Wrap README at 72 columns. python/boto3: Wrap README at 72 columns. python/boto: Wrap README at 72 columns. python/buildbot-worker: updated for version 3.5.0, updated dependencies python/cddb-py: Wrap README at 72 columns. python/cfgparse: Wrap README at 72 columns. python/cheetah3: Make slack-desc ASCII. python/cheroot: Wrap README at 72 columns. python/click-default-group: Wrap README at 72 columns. python/click-didyoumean: Make slack-desc ASCII. python/click: Wrap README at 72 columns. python/clint: Wrap README at 72 columns. python/colorama: Wrap README at 72 columns. python/construct: Wrap README at 72 columns. python/contextlib2: Make slack-desc ASCII. python/contextlib2: Wrap README at 72 columns. python/coverage: Wrap README at 72 columns. python/cryptography: Wrap README at 72 columns. python/cssselect: Wrap README at 72 columns. python/defusedxml: Wrap README at 72 columns. python/dfdatetime: Wrap README at 72 columns. python/dfvfs: Wrap README at 72 columns. python/dfwinreg: Wrap README at 72 columns. python/django-debug-toolbar: Wrap README at 72 columns. python/dotty: Wrap README at 72 columns. python/dtfabric: Wrap README at 72 columns. python/dukpy: Wrap README at 72 columns. python/easygui: Wrap README at 72 columns. python/elasticsearch5: Wrap README at 72 columns. python/entrypoints: Wrap README at 72 columns. python/feedparser: Remove tabs from README. python/feedparser: Wrap README at 72 columns. python/flask-paginate: Wrap README at 72 columns. python/frosted: Wrap README at 72 columns. python/hachoir-core: Wrap README at 72 columns. python/hachoir-metadata: Wrap README at 72 columns. python/hachoir-parser: Wrap README at 72 columns. python/hachoir: Wrap README at 72 columns. python/ipython_genutils: Wrap README at 72 columns. python/josepy: Updated for version 1.13.0. python/json-py: Wrap README at 72 columns. python/llfuse: Wrap README at 72 columns. python/mini-amf: Wrap README at 72 columns. python/monotonic: Wrap README at 72 columns. python/more-itertools: Wrap README at 72 columns. python/mpmath: Wrap README at 72 columns. python/msgpack-python: Wrap README at 72 columns. python/ndg_httpsclient: Wrap README at 72 columns. python/nest_asyncio: Wrap README at 72 columns. python/numexpr: Wrap README at 72 columns. python/odoo: Changed REQUIRES for python3-psycopg2 python/parso: Wrap README at 72 columns. python/pefile: Wrap README at 72 columns. python/phply: Wrap README at 72 columns. python/pickleshare: Wrap README at 72 columns. python/pillowfight: Wrap README at 72 columns. python/pkginfo: Wrap README at 72 columns. python/plaso: Changed REQUIRES for python2-pyzmq python/poster: Wrap README at 72 columns. python/psutil: Wrap README at 72 columns. python/pyamf: Wrap README at 72 columns. python/pybind11: Updated for version 2.9.1 python/pybind11: Wrap README at 72 columns. python/pycdio: Wrap README at 72 columns. python/pychecker: Wrap README at 72 columns. python/pycryptopp: Wrap README at 72 columns. python/pycxx: Wrap README at 72 columns. python/pyflakes: Wrap README at 72 columns. python/pygpgme: Wrap README at 72 columns. python/pyjwt: Wrap README at 72 columns. python/pynzb: Wrap README at 72 columns. python/pyqode.cobol: Wrap README at 72 columns. python/pyresample: Wrap README at 72 columns. python/pysha3: Wrap README at 72 columns. python/pysqlite: Wrap README at 72 columns. python/pysvn: Wrap README at 72 columns. python/pytest-cov: Wrap README at 72 columns. python/pytest: Changed REQUIRES for python2-attrs python/python-PySnooper: Wrap README at 72 columns. python/python-argopt: Wrap README at 72 columns. python/python-emoji: Wrap README at 72 columns. python/python-fonttools: Updated for version 4.30.0. python/python-importlib_metadata: Wrap README at 72 columns. python/python-joblib: Wrap README at 72 columns. python/python-jsonrpclib: Updated for verson 0.4.3.2. python/python-kerberos: Wrap README at 72 columns. python/python-ly: Wrap README at 72 columns. python/python-magic: Wrap README at 72 columns. python/python-markdown-math: Wrap README at 72 columns. python/python-musicbrainz2: Wrap README at 72 columns. python/python-nbxmpp: Wrap README at 72 columns. python/python-neovim: Wrap README at 72 columns. python/python-pcapy: Wrap README at 72 columns. python/python-precis-i18n: Wrap README at 72 columns. python/python-prometheus_client: Wrap README at 72 columns. python/python-sh: Wrap README at 72 columns. python/python2-attrs: renamed from attrs, updated for version 21.2.0 python/python2-automat: renamed from Automat, updated for version 20.2.0 python/python2-pycrypto: Fix PRGNAM in script. python/python2-pyzmq: renamed from pyzmq python/python2-selectors2: Wrap README at 72 columns. python/python2-twisted: updated for version 20.3.0, updated REQUIRES python/python3-amqp: Wrap README at 72 columns. python/python3-defusedxml: Wrap README at 72 columns. python/python3-django: Wrap README at 72 columns. python/python3-gitdb2: Wrap README at 72 columns. python/python3-hupper: Wrap README at 72 columns. python/python3-ipaddr: Wrap README at 72 columns. python/python3-isort: Wrap README at 72 columns. python/python3-jedi: Changed REQUIRES for python3-parso python/python3-kiwisolver: Wrap README at 72 columns. python/python3-monotonic: Wrap README at 72 columns. python/python3-nltk: Wrap README at 72 columns. python/python3-nxt-python: Wrap README at 72 columns. python/python3-paginate: Wrap README at 72 columns. python/python3-pandas: Wrap README at 72 columns. python/python3-parso: renamed from parso python/python3-paste: Wrap README at 72 columns. python/python3-pexpect: Wrap README at 72 columns. python/python3-prompt_toolkit: Wrap README at 72 columns. python/python3-psycopg2: renamed from psycopg2 python/python3-pyjwt: Wrap README at 72 columns. python/python3-pylint: Wrap README at 72 columns. python/python3-pyparted: Wrap README at 72 columns. python/python3-rsa: Make slack-desc ASCII. python/python3-setuptools_autover: Wrap README at 72 columns. python/python3-tekore: Make slack-desc ASCII. python/python3-twisted: Wrap README at 72 columns. python/python3-urlobject: Wrap README at 72 columns. python/python3-uth: Wrap README at 72 columns. python/python3-waitress: Wrap README at 72 columns. python/python3-webhelpers2: Wrap README at 72 columns. python/pyudev: Wrap README at 72 columns. python/readme_renderer: Wrap README at 72 columns. python/requirements-detector: Wrap README at 72 columns. python/rfc6555: Wrap README at 72 columns. python/rsa: Wrap README at 72 columns. python/salt: Changed REQUIRES for python2-pyzmq python/scikit-learn: Wrap README at 72 columns. python/selenium: Wrap README at 72 columns. python/send2trash: Wrap README at 72 columns. python/service_identity: Changed REQUIRES for python2-attrs python/setuptools-scm-git-archive: Wrap README at 72 columns. python/simplejson: Wrap README at 72 columns. python/snowballstemmer: Wrap README at 72 columns. python/sphinxcontrib-applehelp: Wrap README at 72 columns. python/sphinxcontrib-devhelp: Wrap README at 72 columns. python/sphinxcontrib-jsmath: Wrap README at 72 columns. python/sphinxcontrib-qthelp: Wrap README at 72 columns. python/sphinxcontrib-serializinghtml: Wrap README at 72 columns. python/sphinxcontrib-websupport: Wrap README at 72 columns. python/sqlparse: Wrap README at 72 columns. python/stopit: Wrap README at 72 columns. python/subprocess32: Wrap README at 72 columns. python/subuser: Wrap README at 72 columns. python/testpath: Wrap README at 72 columns. python/timehash: Wrap README at 72 columns. python/tinycss: Wrap README at 72 columns. python/tox: Wrap README at 72 columns. python/traitlets: Wrap README at 72 columns. python/trezor: Wrap README at 72 columns. python/typed_ast: Wrap README at 72 columns. python/vinetto: Wrap README at 72 columns. python/waitress: Wrap README at 72 columns. python/websocket-client: Wrap README at 72 columns. python/werkzeug: Wrap README at 72 columns. python/xlutils: Wrap README at 72 columns. python/yara-python: Wrap README at 72 columns. python/zxcvbn-python: Wrap README at 72 columns. ruby/ncurses-ruby: Wrap README at 72 columns. ruby/rbenv: Wrap README at 72 columns. ruby/ruby-native-package-installer: Wrap README at 72 columns. ruby/rubygem-activesupport: Wrap README at 72 columns. ruby/rubygem-coderay: Wrap README at 72 columns. ruby/rubygem-concurrent-ruby: Wrap README at 72 columns. ruby/rubygem-cool.io: Wrap README at 72 columns. ruby/rubygem-daemons: Wrap README at 72 columns. ruby/rubygem-diff-lcs: Wrap README at 72 columns. ruby/rubygem-fastercsv: Wrap README at 72 columns. ruby/rubygem-file-tail: Wrap README at 72 columns. ruby/rubygem-fluentd: Wrap README at 72 columns. ruby/rubygem-gtk2: Wrap README at 72 columns. ruby/rubygem-highline: Wrap README at 72 columns. ruby/rubygem-http_parser.rb: Wrap README at 72 columns. ruby/rubygem-manpages: Wrap README at 72 columns. ruby/rubygem-msgpack: Wrap README at 72 columns. ruby/rubygem-mustache: Wrap README at 72 columns. ruby/rubygem-net-ssh: Wrap README at 72 columns. ruby/rubygem-optimist: Wrap README at 72 columns. ruby/rubygem-ronn: Wrap README at 72 columns. ruby/rubygem-rspec-mocks: Wrap README at 72 columns. ruby/rubygem-rspec: Wrap README at 72 columns. ruby/rubygem-ruby2ruby: Wrap README at 72 columns. ruby/rubygem-ruby_parser: Wrap README at 72 columns. ruby/rubygem-sass: Wrap README at 72 columns. ruby/rubygem-sexp_processor: Wrap README at 72 columns. ruby/rubygem-slop3: Wrap README at 72 columns. ruby/rubygem-sourcify: Wrap README at 72 columns. ruby/rubygem-trogdoro-el4r: Wrap README at 72 columns. ruby/rubygem-tzinfo-data: Wrap README at 72 columns. ruby/rubygem-xiki: Wrap README at 72 columns. system/AnonymousPro: Wrap README at 72 columns. system/GentiumPlus: Wrap README at 72 columns. system/Iosevka: Updated for version 15.0.2 system/SavvyCAN: Wrap README at 72 columns. system/Sl: Silence sbolint doinst.sh warning. system/TLP: Wrap README at 72 columns. system/ZoneMinder: Wrap README at 72 columns. system/acpi: Wrap README at 72 columns. system/adobe-source-code-pro-font: Wrap README at 72 columns. system/adobe-source-sans-pro-font: Wrap README at 72 columns. system/afuse: Wrap README at 72 columns. system/amanda: Wrap README at 72 columns. system/apache-activemq: Wrap README at 72 columns. system/apache-tomcat: Updated for version 10.0.18. system/apache-tomcat: Wrap README at 72 columns. system/apachetop: Wrap README at 72 columns. system/apcupsd: Wrap README at 72 columns. system/apparmor: Wrap README at 72 columns. system/artwiz-aleczapka: Wrap README at 72 columns. system/artwiz-cursor: Wrap README at 72 columns. system/asbt: Wrap README at 72 columns. system/aterm: Wrap README at 72 columns. system/audit: Wrap README at 72 columns. system/augeas: Wrap README at 72 columns. system/avfs: Wrap README at 72 columns. system/bacula-client: Wrap README at 72 columns. system/bacula: Wrap README at 72 columns. system/barman: Changed REQUIRES for python3-psycopg2 and python3-dateutil system/bcache-tools: Wrap README at 72 columns. system/binfmt-support: Wrap README at 72 columns. system/bootchart: Wrap README at 72 columns. system/btop: Update to 15.0 template. system/bubblewrap: Wrap README at 72 columns. system/buildah: Wrap README at 72 columns. system/bulk_extractor: Wrap README at 72 columns. system/burp: Wrap README at 72 columns. system/byobu: Wrap README at 72 columns. system/capabilities: Wrap README at 72 columns. system/caprice32: Wrap README at 72 columns. system/ccd2iso: Wrap README at 72 columns. system/ccid: Wrap README at 72 columns. system/cdemu-client: Wrap README at 72 columns. system/cdrkit: Wrap README at 72 columns. system/cdw: Update email system/cdw: Wrap README at 72 columns. system/chronograf: Make slack-desc ASCII. system/clamav: Wrap README at 72 columns. system/cndrvcups-capt: Wrap README at 72 columns. system/cndrvcups-common: Wrap README at 72 columns. system/cnijfilter2: Wrap README at 72 columns. system/cntlm: Wrap README at 72 columns. system/commons-daemon: Wrap README at 72 columns. system/conmon: Wrap README at 72 columns. system/containerd: Add network warning to README. system/coolkey: Wrap README at 72 columns. system/corosync: Wrap README at 72 columns. system/crashplan: Wrap README at 72 columns. system/crmsh: Wrap README at 72 columns. system/cronie: Wrap README at 72 columns. system/cwtex-q-fonts-TTFs: Wrap README at 72 columns. system/daemontools: Wrap README at 72 columns. system/dahdi-complete: Wrap README at 72 columns. system/davfs2: Wrap README at 72 columns. system/debootstrap: Wrap README at 72 columns. system/diskscan: Wrap README at 72 columns. system/disksearch: Wrap README at 72 columns. system/displaylink: Wrap README at 72 columns. system/dlm: Wrap README at 72 columns. system/dosbox-dev: Move setup instructions to README.SBo. system/dosbox-dev: Wrap README at 72 columns. system/dosbox-dev: updated for version 0.75_pre4473 system/drbd-utils: Wrap README at 72 columns. system/driconf: Wrap README at 72 columns. system/dstat: Wrap README at 72 columns. system/duplicity: Wrap README at 72 columns. system/dust: Wrap README at 72 columns. system/dvdisaster: Wrap README at 72 columns. system/ecryptfs-utils: Wrap README at 72 columns. system/efitools: Wrap README at 72 columns. system/eibd: Wrap README at 72 columns. system/elasticsearch: Wrap README at 72 columns. system/eltclsh: Wrap README at 72 columns. system/eventlog: Wrap README at 72 columns. system/execline: Updated for version 2.8.3.0 system/exfat-utils: Wrap README at 72 columns. system/fence-agents: Wrap README at 72 columns. system/findpkg: Wrap README at 72 columns. system/fio: Wrap README at 72 columns. system/firejail: Wrap README at 72 columns. system/firmware-gobi-2000: Wrap README at 72 columns. system/foomatic-db-engine: Wrap README at 72 columns. system/foomatic-db: Wrap README at 72 columns. system/foremost: Wrap README at 72 columns. system/freeswitch: Wrap README at 72 columns. system/fslint: Wrap README at 72 columns. system/fswatch: Wrap README at 72 columns. system/fuse-exfat: Wrap README at 72 columns. system/gammu: Wrap README at 72 columns. system/gconf-editor: Wrap README at 72 columns. system/gdmap: Wrap README at 72 columns. system/gigolo: Wrap README at 72 columns. system/glances: Wrap README at 72 columns. system/gnu-unifont: Updated for version 14.0.02. system/gnu-unifont: Wrap README at 72 columns. system/go-mtree: Add network warning to README. system/gpart: Wrap README at 72 columns. system/heartbeat: Wrap README at 72 columns. system/hstr: Wrap README at 72 columns. system/hwinfo: Wrap README at 72 columns. system/i8kutils: Wrap README at 72 columns. system/icingaweb2: Wrap README at 72 columns. system/idle3-tools: Wrap README at 72 columns. system/influxdb: Wrap README at 72 columns. system/irqbalance: Wrap README at 72 columns. system/isight-firmware-tools: Wrap README at 72 columns. system/isomaster: Wrap README at 72 columns. system/jdiskreport: Wrap README at 72 columns. system/kapacitor: Wrap README at 72 columns. system/kbfs: Wrap README at 72 columns. system/kc: Remove tabs from README. system/kc: Wrap README at 72 columns. system/ksh-openbsd: Wrap README at 72 columns. system/laptop-mode-tools: Wrap README at 72 columns. system/letsencrypt: Updated for version 1.25.0. system/letsencrypt: Wrap README at 72 columns. system/libnatspec: Wrap README at 72 columns. system/local-persist: Add network warning to README. system/locust: Wrap README at 72 columns. system/logkeys: Wrap README at 72 columns. system/luckybackup: Wrap README at 72 columns. system/lxsplit: Wrap README at 72 columns. system/mailfromd: Wrap README at 72 columns. system/mailutils: Wrap README at 72 columns. system/makepp: Fix broken symlinks. system/makeself: Wrap README at 72 columns. system/mcrypt: Wrap README at 72 columns. system/memtest86+: Wrap README at 72 columns. system/memtest86: Wrap README at 72 columns. system/microcode_ctl: Wrap README at 72 columns. system/monit: Wrap README at 72 columns. system/monitoring-plugins: Wrap README at 72 columns. system/motion: Wrap README at 72 columns. system/mpich: Wrap README at 72 columns. system/msr-tools: Wrap README at 72 columns. system/multiload-ng: Wrap README at 72 columns. system/multitail: Wrap README at 72 columns. system/munin-node: Wrap README at 72 columns. system/musl: Wrap README at 72 columns. system/nagios-plugins: Wrap README at 72 columns. system/nagvis: Wrap README at 72 columns. system/nano-syntax-highlighting: Wrap README at 72 columns. system/nbench: Wrap README at 72 columns. system/netatop: Wrap README at 72 columns. system/nix: Wrap README at 72 columns. system/nmon: Wrap README at 72 columns. system/noto-emoji: Wrap README at 72 columns. system/nsca-ng: Wrap README at 72 columns. system/nss_ldap: Wrap README at 72 columns. system/nut: Wrap README at 72 columns. system/nvidia-legacy340-kernel: Wrap README at 72 columns. system/ohsnap: Wrap README at 72 columns. system/opendoas: Handle environment BUILD better. system/openrc: Wrap README at 72 columns. system/opensc: Wrap README at 72 columns. system/ossec-agent: Wrap README at 72 columns. system/ossec-local: Wrap README at 72 columns. system/ossec-server: Wrap README at 72 columns. system/otf-hermit: Wrap README at 72 columns. system/pacemaker: Wrap README at 72 columns. system/pass-otp: Wrap README at 72 columns. system/passwdqc: Wrap README at 72 columns. system/password-store: Wrap README at 72 columns. system/patool: Wrap README at 72 columns. system/pause: Wrap README at 72 columns. system/pbzip2: Wrap README at 72 columns. system/pcsc-lite: Wrap README at 72 columns. system/pcsc-tools: Wrap README at 72 columns. system/percona-toolkit: Wrap README at 72 columns. system/phpsysinfo: Wrap README at 72 columns. system/picocom: Wrap README at 72 columns. system/pixma: Remove tabs from README. system/pixma: Wrap README at 72 columns. system/plan9port: Remove tabs from README. system/plan9port: Wrap README at 72 columns. system/podman: Wrap README at 72 columns. system/porg: Wrap README at 72 columns. system/procinfo-ng: Wrap README at 72 columns. system/prometheus: Updated to version 2.34.0 system/pwgen: Wrap README at 72 columns. system/pwman: Wrap README at 72 columns. system/pwsafe: Wrap README at 72 columns. system/qdirstat: Wrap README at 72 columns. system/qemu: Wrap README at 72 columns. system/qtgzmanager: Wrap README at 72 columns. system/ranger: Wrap README at 72 columns. system/rar2fs: Wrap README at 72 columns. system/rear: Wrap README at 72 columns. system/recoverdm: Wrap README at 72 columns. system/refind: Wrap README at 72 columns. system/rename: Wrap README at 72 columns. system/resource-agents: Wrap README at 72 columns. system/rhash: Wrap README at 72 columns. system/rkhunter: Wrap README at 72 columns. system/rng-tools: Wrap README at 72 columns. system/runit-services: Wrap README at 72 columns. system/runit: Wrap README at 72 columns. system/rush: Wrap README at 72 columns. system/s3ql: Wrap README at 72 columns. system/s6-linux-init: Updated for version 1.0.7.3 system/s6: Updated for version 2.11.1.0 system/saleae-logic: Wrap README at 72 columns. system/samhain: Wrap README at 72 columns. system/sargon: Add network warning to README. system/sbbdep: Wrap README at 72 columns. system/sbotools: Wrap README at 72 columns. system/sboui: Wrap README at 72 columns. system/scalpel: Wrap README at 72 columns. system/scangearmp2: Wrap README at 72 columns. system/scanmem: Wrap README at 72 columns. system/schedtool: Wrap README at 72 columns. system/sdltrs: Wrap README at 72 columns. system/sentimental-skk: Wrap README at 72 columns. system/signify: Wrap README at 72 columns. system/skim: Wrap README at 72 columns. system/skopeo: Wrap README at 72 columns. system/slack-osquery: Fix HOMEPAGE. system/slack-osquery: Wrap README at 72 columns. system/smart: Wrap README at 72 columns. system/socklog: Wrap README at 72 columns. system/softhsm: Wrap README at 72 columns. system/splix: Wrap README at 72 columns. system/sqlcipher: Wrap README at 72 columns. system/sqldiff: Wrap README at 72 columns. system/squidclamav: Move setup instructions to README.SBo. system/srm: Wrap README at 72 columns. system/sudosh2: Wrap README at 72 columns. system/sunflower: Fix VERSION in script. system/sysdig: Wrap README at 72 columns. system/syslog-ng: Wrap README at 72 columns. system/system76-io-dkms: Wrap README at 72 columns. system/tagainijisho: Updated for version 1.1.93. system/telegraf: Make slack-desc ASCII. system/telegraf: Wrap README at 72 columns. system/termenu: Wrap README at 72 columns. system/terminator: Wrap README at 72 columns. system/terminology: Wrap README at 72 columns. system/thermald: Wrap README at 72 columns. system/thin-provisioning-tools: Wrap README at 72 columns. system/thinkfan: Wrap README at 72 columns. system/tinycdb: Wrap README at 72 columns. system/tm: Move setup instructions to README.SBo. system/tm: Wrap README at 72 columns. system/trashy: Clean up build. system/ts: Wrap README at 72 columns. system/ttf-lato: Wrap README at 72 columns. system/ttop: Wrap README at 72 columns. system/tty2gif: Wrap README at 72 columns. system/ttygif: Wrap README at 72 columns. system/twin: Wrap README at 72 columns. system/unace: Wrap README at 72 columns. system/unhide: Wrap README at 72 columns. system/unison: Wrap README at 72 columns. system/unp: Wrap README at 72 columns. system/uptimed: Wrap README at 72 columns. system/usbrelay: Wrap README at 72 columns. system/usbview: Wrap README at 72 columns. system/vagrant: Wrap README at 72 columns. system/vhba-module: Wrap README at 72 columns. system/virt-manager: Wrap README at 72 columns. system/volatility: Wrap README at 72 columns. system/wangfonts: Wrap README at 72 columns. system/webcore-fonts: Wrap README at 72 columns. system/webmin: Wrap README at 72 columns. system/wiimms-iso-tools: Wrap README at 72 columns. system/wmconfig: Wrap README at 72 columns. system/wmfsm: Wrap README at 72 columns. system/wqy-microhei-font-ttf: Wrap README at 72 columns. system/x86_energy_perf_policy: Wrap README at 72 columns. system/xbindkeys: Wrap README at 72 columns. system/xen: Wrap README at 72 columns. system/xen: x86 is unsupported. system/xjobs: Wrap README at 72 columns. system/xorgxrdp: Wrap README at 72 columns. system/xosd: Wrap README at 72 columns. system/xrdp: Wrap README at 72 columns. system/xstow: Wrap README at 72 columns. system/xtrs: Wrap README at 72 columns. system/yaft: Wrap README at 72 columns. system/yelp-tools: Wrap README at 72 columns. system/yelp: Wrap README at 72 columns. system/zfs-auto-snapshot: Wrap README at 72 columns. system/zookeeper: Wrap README at 72 columns. system/zopfli: Wrap README at 72 columns. system/zpaq: Wrap README at 72 columns. system/zsh-syntax-highlighting: Wrap README at 72 columns. +--------------------------+ -- 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 1.41421 at gmail.com Thu Mar 17 19:52:45 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Thu, 17 Mar 2022 13:52:45 -0600 Subject: [Slackbuilds-users] Surprising failure building GHC Message-ID: In the process of building the Haskell compiler ghc I came across the following failure: echo 'ghcprog="ghc-stage2"' >> "inplace/bin/runghc" echo 'export LD_LIBRARY_PATH="/tmp/SBo/ghc-8.10.4/libraries/process/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/directory/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/unix/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/time/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/filepath/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/bytestring/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/deepseq/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/array/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/base/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/integer-gmp/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/ghc-prim/dist-install/build:/tmp/SBo/ghc-8.10.4/rts/dist/build${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"' >> inplace/bin/runghc cat utils/runghc/runghc.wrapper >> inplace/bin/runghc chmod +x inplace/bin/runghc /opt/SageMath/local/bin/sphinx-build -b html -d docs/users_guide/.doctrees-html -w docs/users_guide/.log -n -D latex_paper_size=letter docs/users_guide docs/users_guide/build-html/users_guide Running Sphinx v4.0.1 Configuration error: There is a syntax error in your configuration file: (unicode error) 'unicodeescape' codec can't decode bytes in position 1-2: truncated \uXXXX escape (conf.py, line 110) make[1]: *** [docs/users_guide/ghc.mk:16: docs/users_guide/build-html/users_guide/index.html] Error 2 make: *** [Makefile:128: all] Error 2 What has Sage got to do with ghc? It is most certainly not a prerequisite. Why is a Sage utility being invoked here at all, and resulting in an error to boot? -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.public at protonmail.com Thu Mar 17 21:32:11 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Thu, 17 Mar 2022 21:32:11 +0000 Subject: [Slackbuilds-users] Surprising failure building GHC In-Reply-To: References: Message-ID: ------- Original Message ------- On Thursday, March 17th, 2022 at 2:52 PM, Luveh Keraph <1.41421 at gmail.com> wrote: > In the process of building the Haskell compiler ghc I came across the following failure: > > echo 'ghcprog="ghc-stage2"' >> "inplace/bin/runghc" > > echo 'export LD_LIBRARY_PATH="/tmp/SBo/ghc-8.10.4/libraries/process/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/directory/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/unix/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/time/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/filepath/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/bytestring/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/deepseq/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/array/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/base/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/integer-gmp/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/ghc-prim/dist-install/build:/tmp/SBo/ghc-8.10.4/rts/dist/build${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"' >> inplace/bin/runghc > > cat utils/runghc/runghc.wrapper >> inplace/bin/runghc > > chmod +x inplace/bin/runghc > > /opt/SageMath/local/bin/sphinx-build -b html -d docs/users_guide/.doctrees-html -w docs/users_guide/.log -n -D latex_paper_size=letter docs/users_guide docs/users_guide/build-html/users_guide > > Running Sphinx v4.0.1 > > Configuration error: > > There is a syntax error in your configuration file: (unicode error) 'unicodeescape' codec can't decode bytes in position 1-2: truncated \uXXXX escape (conf.py, line 110) > > make[1]: *** [docs/users_guide/ghc.mk:16: docs/users_guide/build-html/users_guide/index.html] Error 2 > > make: *** [Makefile:128: all] Error 2 > > What has Sage got to do with ghc? It is most certainly not a prerequisite. Why is a Sage utility being invoked here at all, and resulting in an error to boot? >From ghc's README: Optional dependency: Sphinx (for building the documentation). It's finding Sphinx in /opt/SageMath/local/bin - which means you aren't building in a clean environment. Also note Sphinx on SBo is 4.2.0, but yours is 4.0.1. Try cleansing your PATH environment variable at the very least and try building again. Erich From 1.41421 at gmail.com Thu Mar 17 23:38:36 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Thu, 17 Mar 2022 17:38:36 -0600 Subject: [Slackbuilds-users] Surprising failure building GHC In-Reply-To: References: Message-ID: It's because of the following that the issue arises: 1. Sphinx is an optional requirement for ghc, which is why I did not install it. 2. I had Sage already installed. The Sage installer adds /opt/SageMath/local/bin to the root PATH environment variable. 3. Because of this, the ghc build code finds a Sphinx utility that it needs in the wrong place. On Thu, Mar 17, 2022 at 3:32 PM Erich Ritz via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > ------- Original Message ------- > > On Thursday, March 17th, 2022 at 2:52 PM, Luveh Keraph <1.41421 at gmail.com> > wrote: > > > In the process of building the Haskell compiler ghc I came across the > following failure: > > > > echo 'ghcprog="ghc-stage2"' >> "inplace/bin/runghc" > > > > echo 'export > LD_LIBRARY_PATH="/tmp/SBo/ghc-8.10.4/libraries/process/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/directory/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/unix/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/time/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/filepath/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/bytestring/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/deepseq/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/array/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/base/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/integer-gmp/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/ghc-prim/dist-install/build:/tmp/SBo/ghc-8.10.4/rts/dist/build${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"' > >> inplace/bin/runghc > > > > cat utils/runghc/runghc.wrapper >> inplace/bin/runghc > > > > chmod +x inplace/bin/runghc > > > > /opt/SageMath/local/bin/sphinx-build -b html -d > docs/users_guide/.doctrees-html -w docs/users_guide/.log -n -D > latex_paper_size=letter docs/users_guide > docs/users_guide/build-html/users_guide > > > > Running Sphinx v4.0.1 > > > > Configuration error: > > > > There is a syntax error in your configuration file: (unicode error) > 'unicodeescape' codec can't decode bytes in position 1-2: truncated \uXXXX > escape (conf.py, line 110) > > > > make[1]: *** [docs/users_guide/ghc.mk:16: > docs/users_guide/build-html/users_guide/index.html] Error 2 > > > > make: *** [Makefile:128: all] Error 2 > > > > What has Sage got to do with ghc? It is most certainly not a > prerequisite. Why is a Sage utility being invoked here at all, and > resulting in an error to boot? > > From ghc's README: > > Optional dependency: Sphinx (for building the documentation). > > > > It's finding Sphinx in /opt/SageMath/local/bin - which means you aren't > building in a clean environment. Also note Sphinx on SBo is 4.2.0, but > yours is 4.0.1. > > Try cleansing your PATH environment variable at the very least and try > building again. > > 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 1.41421 at gmail.com Fri Mar 18 03:21:39 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Thu, 17 Mar 2022 21:21:39 -0600 Subject: [Slackbuilds-users] Surprising failure building GHC In-Reply-To: References: Message-ID: After getting Sage out of the way, and installing Sphinx for good measure, ghc still refuses to build: echo 'export LD_LIBRARY_PATH="/tmp/SBo/ghc-8.10.4/libraries/process/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/directory/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/unix/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/time/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/filepath/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/bytestring/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/deepseq/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/array/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/base/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/integer-gmp/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/ghc-prim/dist-install/build:/tmp/SBo/ghc-8.10.4/rts/dist/build${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"' >> inplace/bin/runghc cat utils/runghc/runghc.wrapper >> inplace/bin/runghc chmod +x inplace/bin/runghc /usr/bin/sphinx-build -b html -d docs/users_guide/.doctrees-html -w docs/users_guide/.log -n -D latex_paper_size=letter docs/users_guide docs/users_guide/build-html/users_guide Running Sphinx v4.2.0 Configuration error: There is a syntax error in your configuration file: (unicode error) 'unicodeescape' codec can't decode bytes in position 1-2: truncated \uXXXX escape (conf.py, line 110) make[1]: *** [docs/users_guide/ghc.mk:16: docs/users_guide/build-html/users_guide/index.html] Error 2 make: *** [Makefile:128: all] Error 2 On Thu, Mar 17, 2022 at 5:38 PM Luveh Keraph <1.41421 at gmail.com> wrote: > It's because of the following that the issue arises: > > 1. Sphinx is an optional requirement for ghc, which is why I did not > install it. > 2. I had Sage already installed. The Sage installer adds > /opt/SageMath/local/bin to the root PATH environment variable. > 3. Because of this, the ghc build code finds a Sphinx utility that it > needs in the wrong place. > > > On Thu, Mar 17, 2022 at 3:32 PM Erich Ritz via SlackBuilds-users < > slackbuilds-users at slackbuilds.org> wrote: > >> ------- Original Message ------- >> >> On Thursday, March 17th, 2022 at 2:52 PM, Luveh Keraph <1.41421 at gmail.com> >> wrote: >> >> > In the process of building the Haskell compiler ghc I came across the >> following failure: >> > >> > echo 'ghcprog="ghc-stage2"' >> "inplace/bin/runghc" >> > >> > echo 'export >> LD_LIBRARY_PATH="/tmp/SBo/ghc-8.10.4/libraries/process/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/directory/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/unix/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/time/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/filepath/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/bytestring/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/deepseq/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/array/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/base/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/integer-gmp/dist-install/build:/tmp/SBo/ghc-8.10.4/libraries/ghc-prim/dist-install/build:/tmp/SBo/ghc-8.10.4/rts/dist/build${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"' >> >> inplace/bin/runghc >> > >> > cat utils/runghc/runghc.wrapper >> inplace/bin/runghc >> > >> > chmod +x inplace/bin/runghc >> > >> > /opt/SageMath/local/bin/sphinx-build -b html -d >> docs/users_guide/.doctrees-html -w docs/users_guide/.log -n -D >> latex_paper_size=letter docs/users_guide >> docs/users_guide/build-html/users_guide >> > >> > Running Sphinx v4.0.1 >> > >> > Configuration error: >> > >> > There is a syntax error in your configuration file: (unicode error) >> 'unicodeescape' codec can't decode bytes in position 1-2: truncated \uXXXX >> escape (conf.py, line 110) >> > >> > make[1]: *** [docs/users_guide/ghc.mk:16: >> docs/users_guide/build-html/users_guide/index.html] Error 2 >> > >> > make: *** [Makefile:128: all] Error 2 >> > >> > What has Sage got to do with ghc? It is most certainly not a >> prerequisite. Why is a Sage utility being invoked here at all, and >> resulting in an error to boot? >> >> From ghc's README: >> >> Optional dependency: Sphinx (for building the documentation). >> >> >> >> It's finding Sphinx in /opt/SageMath/local/bin - which means you aren't >> building in a clean environment. Also note Sphinx on SBo is 4.2.0, but >> yours is 4.0.1. >> >> Try cleansing your PATH environment variable at the very least and try >> building again. >> >> 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 dchmelik at gmail.com Fri Mar 18 03:37:46 2022 From: dchmelik at gmail.com (David Chmelik) Date: Thu, 17 Mar 2022 20:37:46 -0700 Subject: [Slackbuilds-users] peer-to-peer: aMule / mldonkey , gnutella, soulseek, transmission-qt, etc.? Message-ID: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com> I thought I read aMule and/or mldonkey were being dropped... ??? I don't use aMule because seems mldonkey does the same and more, but seems it's dropped. ??? I hate to see it go but don't know I could compile/maintain it. ??? The compilation instructions seem complicated/incomplete and about bad OSs. ??? Has anyone heard from mldonkey maintainer? ??? On topic of peer-to-peer (p2p) programs, seems SlackBuilds.org (SBo) has two old GNUtellas: GNUtella (GTK,) was forked into versions of Limewire, forked into Frostwire, forkedin to Wireshare. I'd like to see the latter, as latest fork, so I emailed gtk-gnutella maintainer, but maybe frostwire maintainer would be interested?? Seems you need a certain Java... compilation instructions seem complicated/incomplete and about bad OSs, but someone at www.gnutellaforums.com might know. ??? I hope to see transmission-qt back.? The transmission-gtk doesn't seem to be able to change to a 'night mode' (bright text on black.) ??? It's good EiskaltDC++ and SoulSeek are still on but latter's six years old but for some idiotic reason they made newer version require SELinux. ??? Do other useful ones exist? From jebrhansen+SBo at gmail.com Fri Mar 18 05:31:41 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Thu, 17 Mar 2022 23:31:41 -0600 Subject: [Slackbuilds-users] peer-to-peer: aMule / mldonkey , gnutella, soulseek, transmission-qt, etc.? In-Reply-To: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com> References: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com> Message-ID: On Thu, Mar 17, 2022, 9:38 PM David Chmelik wrote: > I hope to see transmission-qt back. The transmission-gtk doesn't > seem to be able to change to a 'night mode' (bright text on black.) Have you looked into transgui at all? I maintain it on SBo and they show a dark theme on their README (likely tied to the system theme, which I don't currently use a dark one, so I can't verify it works). https://github.com/transmission-remote-gui/transgui https://slackbuilds.org/repository/15.0/network/transgui/ Note: transgui is just a frontend for transmission's webclient. I use it with transmission-daemon, but it should work fine with transmission-gtk as long as you enable web control. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozan.turkyilmaz at gmail.com Fri Mar 18 05:33:27 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Fri, 18 Mar 2022 08:33:27 +0300 Subject: [Slackbuilds-users] peer-to-peer: aMule / mldonkey , gnutella, soulseek, transmission-qt, etc.? In-Reply-To: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com> References: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com> Message-ID: <92f0f284b39cd721639beec15382d9283b7de0a3.camel@gmail.com> Pr?, 2022-03-17 tarihinde 20:37 -0700 saatinde, David Chmelik yazd?: > I thought I read aMule and/or mldonkey were being dropped... > ???? I don't use aMule because seems mldonkey does the same and more, > but seems it's dropped. > ???? I hate to see it go but don't know I could compile/maintain it. aMule uses autotools for now and it means actually it is easier for users than to developers. So far, I want to drop it as I dont really use it anymore. HOwever, they dont do a lot of releases and so far we got it stable and working. Regards, Ozan From slackbuilds at schoepfer.info Fri Mar 18 08:03:05 2022 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 18 Mar 2022 09:03:05 +0100 Subject: [Slackbuilds-users] Nextcloud client In-Reply-To: References: Message-ID: <7fab3bd2c2c153c1d909c8d2673cc385@schoepfer.info> > I keep a current build of it, so I'd be willing to take over > maintenance if no one objects. May i ask to send the build to me or this list? Thanks! From erich.public at protonmail.com Fri Mar 18 13:09:30 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Fri, 18 Mar 2022 13:09:30 +0000 Subject: [Slackbuilds-users] Surprising failure building GHC In-Reply-To: References: Message-ID: ------- Original Message ------- On Thursday, March 17th, 2022 at 10:21 PM, Luveh Keraph <1.41421 at gmail.com> wrote: > After getting Sage out of the way, and installing Sphinx for good measure, ghc still refuses to build: Try installing without Sphinx. On my build I did not have Sphinx installed and it worked. Erich From dominik.drobek at o2.pl Fri Mar 18 17:45:02 2022 From: dominik.drobek at o2.pl (Dominik Drobek) Date: Fri, 18 Mar 2022 18:45:02 +0100 Subject: [Slackbuilds-users] peer-to-peer: aMule / mldonkey , gnutella, soulseek, transmission-qt, etc.? In-Reply-To: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com> References: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com> Message-ID: <9a835028-58ef-43ed-31a7-6a1baba3f510@o2.pl> W dniu 18.03.2022 o?04:37, David Chmelik pisze: > It's good EiskaltDC++ and SoulSeek are still on but latter's six > years old but for some idiotic reason they made newer version require > SELinux. Hi David, I'm the maintainer of SoulseekQt. There is a workaround for this SELinux dependency, I just didn't have the motivation to implement it and post an update to SBo. But I can look into this if there's demand for it. I recommend Nicotine+ over the official client anyway. :) Regards, Dominik From zhu.qunying at gmail.com Fri Mar 18 19:21:31 2022 From: zhu.qunying at gmail.com (Qun-Ying) Date: Fri, 18 Mar 2022 12:21:31 -0700 Subject: [Slackbuilds-users] Updates - 20220317.1 In-Reply-To: References: Message-ID: Hi, fltk is provided from extra in official release, should be removed from SlackBuild. On 3/17/22, Willy Sudiarto Raharjo wrote: > Hey guys, > > For the last few days we have been making a lot of changes (almost 1.5k > commits in this batch of update alone) consists of fixing build failures > on x86 (still ongoing process), renaming for python scripts, and fixing > READMEs. Make sure not to break the READMEs again in the future. > > Just another reminder that submission form is NOT YET opened and new > scripts should go via submission form and not submitted via github/gitlab. > > > Thu Mar 17 17:28:01 UTC 2022 > academic/bowtie2: Mark x86 as unsupported. > academic/bowtie: Mark x86 as unsupported. > academic/celestia: Wrap README at 72 columns. > academic/ds9: Wrap README at 72 columns. > academic/fiji: Fix 32bit build. > academic/fiji: Fix source name on 32bit. > academic/gcompris-qt: Updated for version 2.3.1. > academic/labplot2: Wrap README at 72 columns. > academic/ladr: Wrap README at 72 columns. > academic/ncbi-blast+: Fix build on i586. > academic/octave: Wrap README at 72 columns. > academic/qrupdate: Wrap README at 72 columns. > academic/root: Actually install doinst.sh. > academic/scipy3: Wrap README at 72 columns. > academic/spqr: Wrap README at 72 columns. > academic/suitesparse: Wrap README at 72 columns. > academic/treebest-ensembl: Wrap README at 72 columns. > academic/ugene: Wrap README at 72 columns. > academic/umfpack: Wrap README at 72 columns. > academic/verilator: Make slack-desc ASCII. > academic/xflr5: Wrap README at 72 columns. > accessibility/eflite: Wrap README at 72 columns. > audio/TiMidity++: Handle content-disposition download. > audio/amSynth: Wrap README at 72 columns. > audio/clementine: Wrap README at 72 columns. > audio/clockchimes: Wrap README at 72 columns. > audio/cmus: Wrap README at 72 columns. > audio/darkice: Wrap README at 72 columns. > audio/deadbeef: Wrap README at 72 columns. > audio/gnump3d: Wrap README at 72 columns. > audio/google-musicmanager: Fix broken symlink. > audio/jack_capture: Wrap README at 72 columns. > audio/rhythmbox: Wrap README at 72 columns. > audio/tta: Fix 32-bit build. > desktop/Qogir-icon-theme: Fix VERSION in script. > desktop/Surfn: Fix VERSION in script. > desktop/bumblebee-status: Wrap README at 72 columns. > desktop/e16: Remove template comment. > desktop/obshutdown: Fix DOWNLOAD/HOMEPAGE. > desktop/xdm-slackware-theme: Wrap README at 72 columns. > development/J-Link: Wrap README at 72 columns. > development/android-tools: Add network warning to README. > development/apache-maven: Updated for version 3.8.5. > development/bluefish: Wrap README at 72 columns. > development/dfu-programmer: Move setup instructions to README.SBo. > development/f2c: Remove template comment. > development/gcc5: Fix sbolint nitpicks. > development/git-extras: Wrap README at 72 columns. > development/github-cli: Updated for version 2.6.0 > development/golang-googlecode-gotools: Wrap README at 72 columns. > development/hugo: Updated for version 94.2. > development/jdk11: Wrap README at 72 columns. > development/jupyter-nbclient: Update for 0.5.13 > development/jupyter-nbconvert: Update for 6.4.3 > development/jupyterlab_pygments: Wrap README at 72 columns. > development/lighttable: Add network warning to README. > development/mysql-workbench: Wrap README at 72 columns. > development/nodejs: Updated for version 17.7.1. > development/openjdk7: Move template preamble to top of script. > development/php-xdebug: Fix PRGNAM in script. > development/racer: Add network warning to README. > development/racer: Wrap README at 72 columns. > development/sbcl: Updated for version 2.2.2 > development/shc: Fix DOWNLOAD. > development/shc: Wrap README at 72 columns. > development/shiboken2: Wrap README at 72 columns. > development/sqlcl: Wrap README at 72 columns. > development/sqlitebrowser: Wrap README at 72 columns. > development/tora: Fix VERSION in script. > development/vscode-bin: Updated for version 3.6.1. > games/clksignal-roms: Host 2 of the downloads under sane names. > games/dmagnetic: gzip the man pages. > games/jin: Update email > games/lutris: Updated for version 0.5.9.1, new maintainer > games/m64py: Remove template comment. > games/scid_vs_pc: Wrap README at 72 columns. > games/scummvm: Wrap README at 72 columns. > games/sl: Wrap README at 72 columns. > games/smashbattle: Wrap README at 72 columns. > games/solarus-quest-editor: Wrap README at 72 columns. > games/speed-dreams: Wrap README at 72 columns. > games/steam: Wrap README at 72 columns. > games/tintin: Wrap README at 72 columns. > games/tome-ah: Wrap README at 72 columns. > games/trigger-rally: Wrap README at 72 columns. > games/tuxnes: Wrap README at 72 columns. > games/uligo: Wrap README at 72 columns. > games/ut2004: Wrap README at 72 columns. > games/vcmi: updated for version 0.99_git20220314 > games/voxelands: Wrap README at 72 columns. > games/warzone2100: Wrap README at 72 columns. > games/warzone2100: updated for version 4.2.7 > games/wesnoth: Wrap README at 72 columns. > games/worldofgoo: Wrap README at 72 columns. > games/xroar-roms: Get rid of duplicate ROMs. > games/xye: Wrap README at 72 columns. > games/yamagi-quake2: Wrap README at 72 columns. > games/zaz: Wrap README at 72 columns. > games/zelda-roth-se: Wrap README at 72 columns. > games/zseal: Wrap README at 72 columns. > gis/Fiona: Wrap README at 72 columns. > gis/Geohash: Wrap README at 72 columns. > gis/OTB: Wrap README at 72 columns. > gis/SFCGAL: Wrap README at 72 columns. > gis/TauDEM: Wrap README at 72 columns. > gis/geographiclib-python: Wrap README at 72 columns. > gis/geopandas: Changed REQUIRES for python3-psycopg2 > gis/geopandas: Wrap README at 72 columns. > gis/gpsbabel: Wrap README at 72 columns. > gis/grass: Wrap README at 72 columns. > gis/josm: Wrap README at 72 columns. > gis/laszip: Wrap README at 72 columns. > gis/libspatialindex: Wrap README at 72 columns. > gis/libspatialite: Wrap README at 72 columns. > gis/mapnik: Wrap README at 72 columns. > gis/opengrads: Wrap README at 72 columns. > gis/openorienteering-mapper: Wrap README at 72 columns. > gis/osgEarth: Wrap README at 72 columns. > gis/osm-gps-map: Wrap README at 72 columns. > gis/ossim: Wrap README at 72 columns. > gis/pdal: Wrap README at 72 columns. > gis/pgrouting: Wrap README at 72 columns. > gis/pgsql-ogr-fdw: Wrap README at 72 columns. > gis/pktools: Wrap README at 72 columns. > gis/pointcloud: Wrap README at 72 columns. > gis/polyline: Wrap README at 72 columns. > gis/postgis: Wrap README at 72 columns. > gis/python-mapnik: Fix VERSION in script. > gis/python-pygeos: Wrap README at 72 columns. > gis/python3-cartopy: Wrap README at 72 columns. > gis/python3-pyproj: Wrap README at 72 columns. > gis/python3-pyshp: Wrap README at 72 columns. > gis/python3-xarray: Wrap README at 72 columns. > gis/qgis: Changed REQUIRES for python3-psycopg2 > gis/qgis: Wrap README at 72 columns. > gis/rasterio: Wrap README at 72 columns. > gis/routino: Wrap README at 72 columns. > gis/saga-gis: Wrap README at 72 columns. > gis/spatialite-tools: Wrap README at 72 columns. > gis/tangogps: Wrap README at 72 columns. > gis/whitebox-tools: Wrap README at 72 columns. > gis/xplanet: Wrap README at 72 columns. > graphics/Blender: Wrap README at 72 columns. > graphics/FreeCAD: Wrap README at 72 columns. > graphics/LDView: Wrap README at 72 columns. > graphics/SweetHome3D: Update email > graphics/VariCAD: Wrap README at 72 columns. > graphics/XnViewMP: Wrap README at 72 columns. > graphics/abcm2ps: Wrap README at 72 columns. > graphics/aewan: Wrap README at 72 columns. > graphics/apitrace: Wrap README at 72 columns. > graphics/brlcad: Wrap README at 72 columns. > graphics/converseen: Updated for version 0.9.9.5. > graphics/darktable: Wrap README at 72 columns. > graphics/dia: Wrap README at 72 columns. > graphics/dvisvgm: Wrap README at 72 columns. > graphics/embree: Make slack-desc ASCII. > graphics/embree: Wrap README at 72 columns. > graphics/enblend-enfuse: Wrap README at 72 columns. > graphics/fbpic: Wrap README at 72 columns. > graphics/fig2sxd: Wrap README at 72 columns. > graphics/fotowall: Wrap README at 72 columns. > graphics/frescobaldi: Wrap README at 72 columns. > graphics/fritzing: Wrap README at 72 columns. > graphics/gliv: Wrap README at 72 columns. > graphics/gnome-themes-extras: Wrap README at 72 columns. > graphics/gpicview: Wrap README at 72 columns. > graphics/gpscorrelate: Wrap README at 72 columns. > graphics/graph-easy: Wrap README at 72 columns. > graphics/gthumb: Wrap README at 72 columns. > graphics/img2pdf: Remove tabs from README. > graphics/imgmin: Wrap README at 72 columns. > graphics/jp2a: Wrap README at 72 columns. > graphics/jpeg2ps: Wrap README at 72 columns. > graphics/leocad_pieces: Wrap README at 72 columns. > graphics/maim: Wrap README at 72 columns. > graphics/meshlab: Wrap README at 72 columns. > graphics/nsxiv: Updated for version 29 > graphics/nvidia-texture-tools: Wrap README at 72 columns. > graphics/openclipart: Wrap README at 72 columns. > graphics/opencollada: Wrap README at 72 columns. > graphics/openscad-mcad: Fix VERSION in script. > graphics/openscad: Wrap README at 72 columns. > graphics/paraview: Wrap README at 72 columns. > graphics/pdf2png: Wrap README at 72 columns. > graphics/pencil3: Wrap README at 72 columns. > graphics/pho: Wrap README at 72 columns. > graphics/png2ico: Wrap README at 72 columns. > graphics/pngcrush: Wrap README at 72 columns. > graphics/potrace: Wrap README at 72 columns. > graphics/pygraphviz: Wrap README at 72 columns. > graphics/qcad: Wrap README at 72 columns. > graphics/rawtherapee: Wrap README at 72 columns. > graphics/scrot: Wrap README at 72 columns. > graphics/tesseract: Wrap README at 72 columns. > graphics/tgif-QPL: Wrap README at 72 columns. > graphics/tkpng: Wrap README at 72 columns. > graphics/trimage: Wrap README at 72 columns. > graphics/ueberzug: Make slack-desc ASCII. > graphics/ufraw: Wrap README at 72 columns. > graphics/unpaper: Wrap README at 72 columns. > graphics/vuescan: Updated for version 9.7.80. > graphics/wavelet-denoise: Wrap README at 72 columns. > graphics/whyteboard: Wrap README at 72 columns. > graphics/xcalib: Wrap README at 72 columns. > graphics/xdot: Wrap README at 72 columns. > graphics/yafaray-blender: Wrap README at 72 columns. > graphics/zgv: Wrap README at 72 columns. > ham/ax25-apps: Wrap README at 72 columns. > ham/baudline: Wrap README at 72 columns. > ham/csdr: Wrap README at 72 columns. > ham/cwdaemon: Wrap README at 72 columns. > ham/ebook2cw: Wrap README at 72 columns. > ham/grig: Wrap README at 72 columns. > ham/libax25: Wrap README at 72 columns. > ham/svxlink-sounds-en_US-heather-16k: Wrap README at 72 columns. > ham/svxlink: Wrap README at 72 columns. > ham/tlf: Wrap README at 72 columns. > ham/tqsl: Wrap README at 72 columns. > ham/xfhell: Wrap README at 72 columns. > ham/xpsk31: Wrap README at 72 columns. > ham/xwxapt: Wrap README at 72 columns. > haskell/ghc: Wrap README at 72 columns. > haskell/haskell-HTTP: Wrap README at 72 columns. > haskell/haskell-HUnit: Wrap README at 72 columns. > haskell/haskell-ShellCheck: Wrap README at 72 columns. > haskell/haskell-base16-bytestring: Wrap README at 72 columns. > haskell/haskell-cgi: Wrap README at 72 columns. > haskell/haskell-cmark: Wrap README at 72 columns. > haskell/haskell-colour: Wrap README at 72 columns. > haskell/haskell-digest: Wrap README at 72 columns. > haskell/haskell-fail: Wrap README at 72 columns. > haskell/haskell-graphviz: Wrap README at 72 columns. > haskell/haskell-lpeg: Make slack-desc ASCII. > haskell/haskell-memory: Wrap README at 72 columns. > haskell/haskell-pandoc-types: Wrap README at 72 columns. > haskell/haskell-polyparse: Wrap README at 72 columns. > haskell/haskell-regex-applicative: Wrap README at 72 columns. > haskell/haskell-texmath: Wrap README at 72 columns. > haskell/haskell-zlib: Wrap README at 72 columns. > libraries/BeautifulSoup: Wrap README at 72 columns. > libraries/CGAL: Wrap README at 72 columns. > libraries/CondConfigParser: Wrap README at 72 columns. > libraries/ConfigParser: Wrap README at 72 columns. > libraries/DevIL: Wrap README at 72 columns. > libraries/FreeImage: Wrap README at 72 columns. > libraries/Geraldo: Wrap README at 72 columns. > libraries/Nevow: Wrap README at 72 columns. > libraries/OpenBLAS: Wrap README at 72 columns. > libraries/OpenCSG: Wrap README at 72 columns. > libraries/OpenSceneGraph: Remove tabs from README. > libraries/OpenSceneGraph: Wrap README at 72 columns. > libraries/PyOpenGL: Wrap README at 72 columns. > libraries/Pykka: Wrap README at 72 columns. > libraries/SFML: Wrap README at 72 columns. > libraries/Smarty: Wrap README at 72 columns. > libraries/VTK: Wrap README at 72 columns. > libraries/adodb: Wrap README at 72 columns. > libraries/agg: Wrap README at 72 columns. > libraries/allegro: Wrap README at 72 columns. > libraries/antlr4: Add network warning to README. > libraries/antlr4: Wrap README at 72 columns. > libraries/barry: Wrap README at 72 columns. > libraries/batinfo: Wrap README at 72 columns. > libraries/bctoolbox: Wrap README at 72 columns. > libraries/bitstream: Wrap README at 72 columns. > libraries/blas: Wrap README at 72 columns. > libraries/bluez-alsa: Wrap README at 72 columns. > libraries/bzrtp: Wrap README at 72 columns. > libraries/cal3d: Wrap README at 72 columns. > libraries/cdk: Wrap README at 72 columns. > libraries/cffi: Wrap README at 72 columns. > libraries/confuse: Wrap README at 72 columns. > libraries/console_bridge: Wrap README at 72 columns. > libraries/crossguid: Wrap README at 72 columns. > libraries/curses_ex: Wrap README at 72 columns. > libraries/dcadec: Wrap README at 72 columns. > libraries/dcmtk: Wrap README at 72 columns. > libraries/edelib: Wrap README at 72 columns. > libraries/efl: Wrap README at 72 columns. > libraries/eris: Wrap README at 72 columns. > libraries/evernote-python: Wrap README at 72 columns. > libraries/exiftool: Wrap README at 72 columns. > libraries/facebook-python: Wrap README at 72 columns. > libraries/fcgi: Wrap README at 72 columns. > libraries/fifechan: Wrap README at 72 columns. > libraries/fltk: Wrap README at 72 columns. > libraries/fox-toolkit-devel: Wrap README at 72 columns. > libraries/freexl: Wrap README at 72 columns. > libraries/ftplib: Wrap README at 72 columns. > libraries/futures: Wrap README at 72 columns. > libraries/gitdb2: Wrap README at 72 columns. > libraries/gitdb: Wrap README at 72 columns. > libraries/gl2ps: Wrap README at 72 columns. > libraries/goffice0.8: Wrap README at 72 columns. > libraries/grpc: Wrap README at 72 columns. > libraries/gspell: Wrap README at 72 columns. > libraries/gtkdatabox: Wrap README at 72 columns. > libraries/gtkglarea: Wrap README at 72 columns. > libraries/hdf: Wrap README at 72 columns. > libraries/hoel: updated for version 1.4.19 > libraries/http-parser: Wrap README at 72 columns. > libraries/hurry-filesize: Wrap README at 72 columns. > libraries/iddawc: Wrap README at 72 columns. > libraries/ignition-transport: Wrap README at 72 columns. > libraries/iksemel: Wrap README at 72 columns. > libraries/imlib: Wrap README at 72 columns. > libraries/irrlicht: Wrap README at 72 columns. > libraries/isodate: Wrap README at 72 columns. > libraries/itcl: Wrap README at 72 columns. > libraries/lablgtk: Wrap README at 72 columns. > libraries/lapack: Wrap README at 72 columns. > libraries/levmar: Wrap README at 72 columns. > libraries/libEMF: Wrap README at 72 columns. > libraries/libaacs: Wrap README at 72 columns. > libraries/libass: Wrap README at 72 columns. > libraries/libavc1394: Update email > libraries/libavc1394: Wrap README at 72 columns. > libraries/libb64: Wrap README at 72 columns. > libraries/libbde: Wrap README at 72 columns. > libraries/libbdplus: Wrap README at 72 columns. > libraries/libbsd: Wrap README at 72 columns. > libraries/libbtbb: Wrap README at 72 columns. > libraries/libcangjie: Wrap README at 72 columns. > libraries/libcbor: Wrap README at 72 columns. > libraries/libcec: Wrap README at 72 columns. > libraries/libchewing: Wrap README at 72 columns. > libraries/libcli: Wrap README at 72 columns. > libraries/libdbh2: Wrap README at 72 columns. > libraries/libdc1394: Wrap README at 72 columns. > libraries/libdca: Wrap README at 72 columns. > libraries/libdv: Wrap README at 72 columns. > libraries/libeatmydata: Wrap README at 72 columns. > libraries/libesedb: Wrap README at 72 columns. > libraries/libesmtp: Wrap README at 72 columns. > libraries/libexe: Wrap README at 72 columns. > libraries/libfaketime: Wrap README at 72 columns. > libraries/libg15: Wrap README at 72 columns. > libraries/libg15render: Wrap README at 72 columns. > libraries/libgit2-glib: Wrap README at 72 columns. > libraries/libgit2: Wrap README at 72 columns. > libraries/libgnomecanvas: Wrap README at 72 columns. > libraries/libgnomecups: Wrap README at 72 columns. > libraries/libgsasl: Wrap README at 72 columns. > libraries/libharu: Wrap README at 72 columns. > libraries/libhid: Wrap README at 72 columns. > libraries/libhtp: Wrap README at 72 columns. > libraries/libiec61883: Update email > libraries/libiec61883: Wrap README at 72 columns. > libraries/libindi-drivers: Update email > libraries/libindi: Update email > libraries/libindi: Wrap README at 72 columns. > libraries/libiptcdata: Wrap README at 72 columns. > libraries/libircclient: Wrap README at 72 columns. > libraries/libisoburn: Wrap README at 72 columns. > libraries/libkate: Wrap README at 72 columns. > libraries/libkml: Wrap README at 72 columns. > libraries/liblightgrep: Wrap README at 72 columns. > libraries/liblxi: Wrap README at 72 columns. > libraries/libmicrohttpd: Wrap README at 72 columns. > libraries/libmimic: Wrap README at 72 columns. > libraries/libmpdclient: Wrap README at 72 columns. > libraries/libmsiecf: Wrap README at 72 columns. > libraries/libmspack: Wrap README at 72 columns. > libraries/libmusicbrainz3: Wrap README at 72 columns. > libraries/libmusicbrainz5: Wrap README at 72 columns. > libraries/libnids: Wrap README at 72 columns. > libraries/liboglappth: Wrap README at 72 columns. > libraries/libolecf: Wrap README at 72 columns. > libraries/libotr: Wrap README at 72 columns. > libraries/libp11: Wrap README at 72 columns. > libraries/libpar2: Wrap README at 72 columns. > libraries/libpff: Wrap README at 72 columns. > libraries/libpri: Wrap README at 72 columns. > libraries/libqcow: Wrap README at 72 columns. > libraries/librapi2: Wrap README at 72 columns. > libraries/libraqm: Wrap README at 72 columns. > libraries/libreadline-java: Wrap README at 72 columns. > libraries/librsync: Wrap README at 72 columns. > libraries/libscrypt: Wrap README at 72 columns. > libraries/libshout: Wrap README at 72 columns. > libraries/libslack: Wrap README at 72 columns. > libraries/libsmraw: Wrap README at 72 columns. > libraries/libsoup3: Update to 15.0 template. > libraries/libsrtp: Wrap README at 72 columns. > libraries/libsynce: Wrap README at 72 columns. > libraries/libtermkey: Wrap README at 72 columns. > libraries/libthai: Wrap README at 72 columns. > libraries/libticonv: Wrap README at 72 columns. > libraries/libtubo0: Wrap README at 72 columns. > libraries/libucil: Wrap README at 72 columns. > libraries/libversion: Wrap README at 72 columns. > libraries/libvhdi: Wrap README at 72 columns. > libraries/libvirt: Wrap README at 72 columns. > libraries/libvmime: Wrap README at 72 columns. > libraries/libvorbisidec: Wrap README at 72 columns. > libraries/libvshadow: Wrap README at 72 columns. > libraries/libvslvm: Wrap README at 72 columns. > libraries/libvterm: Wrap README at 72 columns. > libraries/libwebsockets: Wrap README at 72 columns. > libraries/libwhisker2: Wrap README at 72 columns. > libraries/libxmi: Wrap README at 72 columns. > libraries/libxml++: Wrap README at 72 columns. > libraries/libxmp: Wrap README at 72 columns. > libraries/live555: Wrap README at 72 columns. > libraries/lockdev: Wrap README at 72 columns. > libraries/log4net: Wrap README at 72 columns. > libraries/lua-lpeg: Wrap README at 72 columns. > libraries/lua-luv: Wrap README at 72 columns. > libraries/lua-mpack: Wrap README at 72 columns. > libraries/lua-posix: Wrap README at 72 columns. > libraries/lunatic-python: Wrap README at 72 columns. > libraries/meanwhile: Wrap README at 72 columns. > libraries/menu-cache: Wrap README at 72 columns. > libraries/mowitz: Wrap README at 72 columns. > libraries/mpir: Wrap README at 72 columns. > libraries/msgpack-c: Wrap README at 72 columns. > libraries/mujs: Wrap README at 72 columns. > libraries/mysql++: Wrap README at 72 columns. > libraries/nextaw: Wrap README at 72 columns. > libraries/nini: Wrap README at 72 columns. > libraries/ocaml-batteries: Wrap README at 72 columns. > libraries/ocaml-camomile: Wrap README at 72 columns. > libraries/ocaml-findlib: Wrap README at 72 columns. > libraries/opencl-amd: Wrap README at 72 columns. > libraries/orcania: updated for version 2.2.2 > libraries/paho-mqtt: Update to 15.0 template. > libraries/paho-mqtt: Wrap README at 72 columns. > libraries/pcl: Wrap README at 72 columns. > libraries/pexpect: Wrap README at 72 columns. > libraries/pgtcl-ng: Wrap README at 72 columns. > libraries/physfs: Wrap README at 72 columns. > libraries/plplot: Wrap README at 72 columns. > libraries/progressbar: Wrap README at 72 columns. > libraries/pycparser: Wrap README at 72 columns. > libraries/pyftpdlib: Wrap README at 72 columns. > libraries/pylast: Wrap README at 72 columns. > libraries/pymdstat: Wrap README at 72 columns. > libraries/pysendfile: Wrap README at 72 columns. > libraries/python-efl: Wrap README at 72 columns. > libraries/python-gnupg: Wrap README at 72 columns. > libraries/python-meld3: Wrap README at 72 columns. > libraries/rarfile: Wrap README at 72 columns. > libraries/reportlab: Wrap README at 72 columns. > libraries/rhino: Wrap README at 72 columns. > libraries/robin-map: Wrap README at 72 columns. > libraries/rpyc: Wrap README at 72 columns. > libraries/rrdtool: Wrap README at 72 columns. > libraries/rtorrent-python: Wrap README at 72 columns. > libraries/rudiments: Wrap README at 72 columns. > libraries/setproctitle: Wrap README at 72 columns. > libraries/skalibs: Updated for version 2.11.2.0 > libraries/soundtouch: Wrap README at 72 columns. > libraries/spread-sheet-widget: Wrap README at 72 columns. > libraries/sqlpp11: Add network warning to README. > libraries/tDOM: Wrap README at 72 columns. > libraries/tbb: Wrap README at 72 columns. > libraries/tinyxml2: Wrap README at 72 columns. > libraries/totem-pl-parser: Wrap README at 72 columns. > libraries/tsocks: Wrap README at 72 columns. > libraries/ulfius: updated for version 2.7.8 > libraries/unibilium: Wrap README at 72 columns. > libraries/unixODBC: Wrap README at 72 columns. > libraries/urdfdom_headers: Wrap README at 72 columns. > libraries/varconf: Wrap README at 72 columns. > libraries/volk: Wrap README at 72 columns. > libraries/web.py: Wrap README at 72 columns. > libraries/wv: Wrap README at 72 columns. > libraries/wxGTK3: Wrap README at 72 columns. > libraries/wxGTK: Wrap README at 72 columns. > libraries/wxPython3: Wrap README at 72 columns. > libraries/wxPython4: Wrap README at 72 columns. > libraries/wxPython: Wrap README at 72 columns. > libraries/wxX11: Wrap README at 72 columns. > libraries/xerces-c: Fix 32bit build. > libraries/xforms: Wrap README at 72 columns. > libraries/xmlrpc-c: Wrap README at 72 columns. > libraries/yaz: Wrap README at 72 columns. > libraries/yder: updated for version 1.4.15 > libraries/zfec: Wrap README at 72 columns. > libraries/zziplib: Wrap README at 72 columns. > misc/ardesia: Wrap README at 72 columns. > misc/asr-manpages: Wrap README at 72 columns. > misc/bchunk: Wrap README at 72 columns. > misc/beep: Wrap README at 72 columns. > misc/biosdisk: Wrap README at 72 columns. > misc/boncuk: Wrap README at 72 columns. > misc/bsdmainutils: Wrap README at 72 columns. > misc/ccze: Wrap README at 72 columns. > misc/chm2pdf: Wrap README at 72 columns. > misc/cksfv: Wrap README at 72 columns. > misc/clawsker: Wrap README at 72 columns. > misc/dcc: Wrap README at 72 columns. > misc/dmg2img: Update email > misc/drg2sbg: Wrap README at 72 columns. > misc/dvtm: Wrap README at 72 columns. > misc/dwdiff: Wrap README at 72 columns. > misc/figlet-contributed: Wrap README at 72 columns. > misc/funny-manpages: Wrap README at 72 columns. > misc/g15composer: Wrap README at 72 columns. > misc/g15daemon: Wrap README at 72 columns. > misc/gcp: Wrap README at 72 columns. > misc/goldencheetah: Wrap README at 72 columns. > misc/gramps: Wrap README at 72 columns. > misc/heimdall: Wrap README at 72 columns. > misc/hoorex: Wrap README at 72 columns. > misc/kasumi: Wrap README at 72 columns. > misc/keychain: Wrap README at 72 columns. > misc/kronometer: Wrap README at 72 columns. > misc/ltunify: Wrap README at 72 columns. > misc/mdic: Wrap README at 72 columns. > misc/megatunix: Wrap README at 72 columns. > misc/moedict-desktop.app: Wrap README at 72 columns. > misc/mosquitto: Wrap README at 72 columns. > misc/myclippings: Wrap README at 72 columns. > misc/par2cmdline-tbb: Wrap README at 72 columns. > misc/par2cmdline: Wrap README at 72 columns. > misc/projectM: Wrap README at 72 columns. > misc/recode: Wrap README at 72 columns. > misc/rsnapshot: Wrap README at 72 columns. > misc/solunar: Wrap README at 72 columns. > misc/subsurface: Wrap README at 72 columns. > misc/sunwait: Wrap README at 72 columns. > misc/torrentinfo: Wrap README at 72 columns. > misc/weather: Wrap README at 72 columns. > misc/xdelta: Wrap README at 72 columns. > misc/xwinwrap: Wrap README at 72 columns. > misc/yara: Wrap README at 72 columns. > misc/ykpers: Wrap README at 72 columns. > multimedia/HandBrake: Wrap README at 72 columns. > multimedia/Mopidy: Wrap README at 72 columns. > multimedia/OpenLP: Wrap README at 72 columns. > multimedia/SimpleSysexxer: Wrap README at 72 columns. > multimedia/abcMIDI: Wrap README at 72 columns. > multimedia/anyremote: Wrap README at 72 columns. > multimedia/audiopreview: Wrap README at 72 columns. > multimedia/avidemux: Wrap README at 72 columns. > multimedia/castnow: Add network warning to README. > multimedia/ccxstream: Wrap README at 72 columns. > multimedia/dirac: Wrap README at 72 columns. > multimedia/droidcam: Wrap README at 72 columns. > multimedia/dsmidiwifi: Wrap README at 72 columns. > multimedia/dvblast: Wrap README at 72 columns. > multimedia/dvdrip: Wrap README at 72 columns. > multimedia/exaile: Wrap README at 72 columns. > multimedia/flvtool2: Wrap README at 72 columns. > multimedia/gaupol: Wrap README at 72 columns. > multimedia/genpuid: Wrap README at 72 columns. > multimedia/gmidimonitor: Wrap README at 72 columns. > multimedia/gmtp: Wrap README at 72 columns. > multimedia/gnome-mplayer: Wrap README at 72 columns. > multimedia/gnupod: Wrap README at 72 columns. > multimedia/gpac: Wrap README at 72 columns. > multimedia/gst-plugins-ugly: Wrap README at 72 columns. > multimedia/gst0-plugins-ugly: Wrap README at 72 columns. > multimedia/iat: Wrap README at 72 columns. > multimedia/inputstream.adaptive: Remove template comment. > multimedia/ivtv-utils: Wrap README at 72 columns. > multimedia/jlscp: Wrap README at 72 columns. > multimedia/minitube: Wrap README at 72 columns. > multimedia/mjpegtools: Update email > multimedia/mjpegtools: Wrap README at 72 columns. > multimedia/mjpegtools: fix email > multimedia/mp3fm: Wrap README at 72 columns. > multimedia/mpgtx: Wrap README at 72 columns. > multimedia/musixmatch: Make slack-desc ASCII. > multimedia/obs-studio: Updated for version 27.2.3 > multimedia/obs-studio: Wrap README at 72 columns. > multimedia/oggconvert: Wrap README at 72 columns. > multimedia/oggvideotools: Wrap README at 72 columns. > multimedia/opencaster: Wrap README at 72 columns. > multimedia/parole: Wrap README at 72 columns. > multimedia/ripperX: Wrap README at 72 columns. > multimedia/smpeg: Wrap README at 72 columns. > multimedia/spek: Wrap README at 72 columns. > multimedia/subtitleeditor: Wrap README at 72 columns. > multimedia/subtitleripper: Wrap README at 72 columns. > multimedia/tovid: Update email > multimedia/tovid: Wrap README at 72 columns. > multimedia/transcode: Wrap README at 72 columns. > multimedia/tstools: Wrap README at 72 columns. > multimedia/tvtime: Wrap README at 72 columns. > multimedia/ucview: Wrap README at 72 columns. > multimedia/vcdimager: Wrap README at 72 columns. > multimedia/vlc: Wrap README at 72 columns. > multimedia/wxcam: Update email > multimedia/wxcam: Wrap README at 72 columns. > multimedia/xjadeo: Wrap README at 72 columns. > multimedia/xmltv: Wrap README at 72 columns. > multimedia/xvid4conf: Wrap README at 72 columns. > multimedia/yarock: Wrap README at 72 columns. > multimedia/zvbi: Wrap README at 72 columns. > network/3proxy: Wrap README at 72 columns. > network/CherryMusic: Wrap README at 72 columns. > network/ClusterSSH: Wrap README at 72 columns. > network/DarTui: Wrap README at 72 columns. > network/Flootty: Wrap README at 72 columns. > network/Free-Cinema: Wrap README at 72 columns. > network/GhostInTheMail: Wrap README at 72 columns. > network/LOIC: Wrap README at 72 columns. > network/NetworkManager-l2tp: Wrap README at 72 columns. > network/Pafy: Wrap README at 72 columns. > network/PyRSS2Gen: Wrap README at 72 columns. > network/Pyrit: Wrap README at 72 columns. > network/SoulseekQt: Wrap README at 72 columns. > network/TeamSpeak3: Update email > network/WhatWeb: Wrap README at 72 columns. > network/aMule: Wrap README at 72 columns. > network/amap: Wrap README at 72 columns. > network/amavisd-new: Wrap README at 72 columns. > network/arno-iptables-firewall: Wrap README at 72 columns. > network/avahi: Wrap README at 72 columns. > network/awstats: Wrap README at 72 columns. > network/bip: Wrap README at 72 columns. > network/bitlbee: Wrap README at 72 columns. > network/brave-browser: Updated for version 1.35.112 > network/btpd: Wrap README at 72 columns. > network/c-toxcore: Wrap README at 72 columns. > network/cacti: Wrap README at 72 columns. > network/cadaver: Wrap README at 72 columns. > network/cherokee: Wrap README at 72 columns. > network/clamav-unofficial-sigs: Wrap README at 72 columns. > network/claws-mail: Wrap README at 72 columns. > network/cmdiag: Wrap README at 72 columns. > network/cni-plugins: Add network warning to README. > network/cni-plugins: Wrap README at 72 columns. > network/comgt: Wrap README at 72 columns. > network/corkscrew: Wrap README at 72 columns. > network/csync: Wrap README at 72 columns. > network/ctorrent: Wrap README at 72 columns. > network/darkhttpd: Wrap README at 72 columns. > network/darkstat: Wrap README at 72 columns. > network/ddgr: Wrap README at 72 columns. > network/deluge: Wrap README at 72 columns. > network/dillo: Wrap README at 72 columns. > network/dirb: Wrap README at 72 columns. > network/dma: Wrap README at 72 columns. > network/dmitry: Wrap README at 72 columns. > network/dnscrypt-proxy: Wrap README at 72 columns. > network/dnscrypt-wrapper: Wrap README at 72 columns. > network/dnsmap: Wrap README at 72 columns. > network/dnstop: Wrap README at 72 columns. > network/dovecot-pigeonhole: Wrap README at 72 columns. > network/driftnet: Wrap README at 72 columns. > network/dropbox: Updated for version 144.4.4491. > network/dsniff: Wrap README at 72 columns. > network/easyrsa: Wrap README at 72 columns. > network/efax-gtk: Wrap README at 72 columns. > network/efax: Remove template comment. > network/efax: Wrap README at 72 columns. > network/eiskaltdcpp: Wrap README at 72 columns. > network/emailrelay: Wrap README at 72 columns. > network/enet: Wrap README at 72 columns. > network/etherape: Wrap README at 72 columns. > network/etherpad-lite: Add network warning to README. > network/ettercap: Wrap README at 72 columns. > network/exim: Wrap README at 72 columns. > network/fdm: Wrap README at 72 columns. > network/filezilla: Wrap README at 72 columns. > network/firehol: Wrap README at 72 columns. > network/flvstreamer: Wrap README at 72 columns. > network/fping: Wrap README at 72 columns. > network/freeradius-server: Wrap README at 72 columns. > network/gajim: Wrap README at 72 columns. > network/geoipupdate: Wrap README at 72 columns. > network/glewlwyd: Wrap README at 72 columns. > network/gns3: Wrap README at 72 columns. > network/googler: Wrap README at 72 columns. > network/gophernicus: Move setup instructions to README.SBo. > network/graphite-carbon: Wrap README at 72 columns. > network/gtk-gnutella: Wrap README at 72 columns. > network/gui-ufw: Fix broken wrapper scripts. > network/hamachi: Wrap README at 72 columns. > network/haproxy: Wrap README at 72 columns. > network/haskell-network-multicast: Wrap README at 72 columns. > network/havp: Wrap README at 72 columns. > network/host-sflow: Wrap README at 72 columns. > network/hostsblock: Wrap README at 72 columns. > network/hping3: Wrap README at 72 columns. > network/httpie: Wrap README at 72 columns. > network/icinga2: Wrap README at 72 columns. > network/identicurse: Wrap README at 72 columns. > network/inadyn: Wrap README at 72 columns. > network/iodine: Wrap README at 72 columns. > network/ipcalc: Wrap README at 72 columns. > network/iperf: Wrap README at 72 columns. > network/ircd-hybrid: Wrap README at 72 columns. > network/isync: Wrap README at 72 columns. > network/jabberd2: Wrap README at 72 columns. > network/jboss-as: Wrap README at 72 columns. > network/jitsi: Wrap README at 72 columns. > network/kivy-garden: Wrap README at 72 columns. > network/knock: Wrap README at 72 columns. > network/leafnode: Wrap README at 72 columns. > network/libmaxminddb: Wrap README at 72 columns. > network/libnatpmp: Wrap README at 72 columns. > network/libnfsidmap: Wrap README at 72 columns. > network/light-firefox: Wrap README at 72 columns. > network/linphone: Wrap README at 72 columns. > network/linssid: Wrap README at 72 columns. > network/livestreamer: Wrap README at 72 columns. > network/lizardfs: Wrap README at 72 columns. > network/lxi-tools: Wrap README at 72 columns. > network/mailman: Wrap README at 72 columns. > network/mailspring: Updated for version 1.10.1 > network/malheur: Wrap README at 72 columns. > network/masscan: Wrap README at 72 columns. > network/megatools: Wrap README at 72 columns. > network/memcached: Wrap README at 72 columns. > network/mitmproxy-bin: Update to 15.0 template. > network/mod_auth_kerb: Wrap README at 72 columns. > network/mod_chroot: Wrap README at 72 columns. > network/mod_evasive: Wrap README at 72 columns. > network/mod_geoip2: Wrap README at 72 columns. > network/mod_ruid2: Wrap README at 72 columns. > network/mod_wsgi: Wrap README at 72 columns. > network/monkey: Wrap README at 72 columns. > network/mumble-server: Wrap README at 72 columns. > network/mysecureshell: Wrap README at 72 columns. > network/nagios: Wrap README at 72 columns. > network/ncrack: Wrap README at 72 columns. > network/netcat-openbsd: Update download URL > network/netcat: Wrap README at 72 columns. > network/netdiscover: Wrap README at 72 columns. > network/netdrive-connector: Wrap README at 72 columns. > network/netqmail: Wrap README at 72 columns. > network/netsurf: Wrap README at 72 columns. > network/newsboat: Wrap README at 72 columns. > network/nextcloud-client: Wrap README at 72 columns. > network/nginx: Wrap README at 72 columns. > network/ngrep: Wrap README at 72 columns. > network/ngrok: Wrap README at 72 columns. > network/nikto: Wrap README at 72 columns. > network/nrpe: Wrap README at 72 columns. > network/nsca: Wrap README at 72 columns. > network/nsd: Wrap README at 72 columns. > network/nss-mdns: Wrap README at 72 columns. > network/nweb: Fix VERSION in script. > network/oidentd: Wrap README at 72 columns. > network/onedrive: Updated to version 2.4.16 > network/onionshare: Wrap README at 72 columns. > network/openconnect: Wrap README at 72 columns. > network/opendchub: Wrap README at 72 columns. > network/opendkim: Wrap README at 72 columns. > network/opendmarc: Wrap README at 72 columns. > network/openntpd: Wrap README at 72 columns. > network/opensmtpd: Wrap README at 72 columns. > network/openvswitch-utils: Wrap README at 72 columns. > network/owncloud-client: Wrap README at 72 columns. > network/owncloud-server: Wrap README at 72 columns. > network/p0f: Wrap README at 72 columns. > network/pCloudDrive: Wrap README at 72 columns. > network/packit: Wrap README at 72 columns. > network/palemoon-bin: Wrap README at 72 columns. > network/pdns: Remove tabs from README. > network/periscope: Wrap README at 72 columns. > network/pflogsumm: Wrap README at 72 columns. > network/pfqueue: Wrap README at 72 columns. > network/pgpool-II: Wrap README at 72 columns. > network/phpmyadmin: Wrap README at 72 columns. > network/pidgin-nudge: Wrap README at 72 columns. > network/pidgin-otr: Wrap README at 72 columns. > network/pidgin-privacy-please: Wrap README at 72 columns. > network/pidgin-sound: Wrap README at 72 columns. > network/plowshare: Wrap README at 72 columns. > network/pmacct: Wrap README at 72 columns. > network/policyd2: Wrap README at 72 columns. > network/polipo: Wrap README at 72 columns. > network/postgrey: Wrap README at 72 columns. > network/pptpd: Wrap README at 72 columns. > network/prosody-mod-turncredentials: Wrap README at 72 columns. > network/prosody-mod-vcard-muc: Wrap README at 72 columns. > network/protonvpn-cli: Remove template comment. > network/protonvpn-cli: Update homepage and download link. > network/proxymini: Wrap README at 72 columns. > network/proxytunnel: Wrap README at 72 columns. > network/psad: Wrap README at 72 columns. > network/psi-plus: Add network warning to README. > network/qTox: Wrap README at 72 columns. > network/radvd: Wrap README at 72 columns. > network/reaver: Wrap README at 72 columns. > network/rejik: Wrap README at 72 columns. > network/republicanywhere: Wrap README at 72 columns. > network/retroshare: Wrap README at 72 columns. > network/riot-web: Remove tabs from README. > network/riot-web: Wrap README at 72 columns. > network/rtl8821ce: Make slack-desc ASCII. > network/seahub: Wrap README at 72 columns. > network/shibboleth-sp: Wrap README at 72 columns. > network/sickrage: Wrap README at 72 columns. > network/siege: Wrap README at 72 columns. > network/signal-desktop: Updated for version 5.35.0 > network/silc-toolkit: Wrap README at 72 columns. > network/skypeforlinux: Wrap README at 72 columns. > network/slirp4netns: Wrap README at 72 columns. > network/slowhttptest: Wrap README at 72 columns. > network/smcroute: Wrap README at 72 columns. > network/sniffjoke: Wrap README at 72 columns. > network/snort: Wrap README at 72 columns. > network/spamassassin: Wrap README at 72 columns. > network/spambayes: Wrap README at 72 columns. > network/speedometer: Wrap README at 72 columns. > network/speedtest-cli: Wrap README at 72 columns. > network/sqlninja: Wrap README at 72 columns. > network/sqlrelay: Wrap README at 72 columns. > network/squid: Wrap README at 72 columns. > network/squidanalyzer: Wrap README at 72 columns. > network/sshguard: Wrap README at 72 columns. > network/sstp-client: Wrap README at 72 columns. > network/strongswan: Wrap README at 72 columns. > network/sylpheed: Wrap README at 72 columns. > network/tahoe-lafs: Wrap README at 72 columns. > network/tcpflow: Wrap README at 72 columns. > network/teams: Make slack-desc ASCII. > network/telegram: Updated for version 3.6.1. > network/telegram: Wrap README at 72 columns. > network/thrift: Wrap README at 72 columns. > network/thttpd: Wrap README at 72 columns. > network/tinc: Wrap README at 72 columns. > network/tinyproxy: Wrap README at 72 columns. > network/tmate: Wrap README at 72 columns. > network/tor: New maintainer. > network/toxcore: Wrap README at 72 columns. > network/translate-shell: Wrap README at 72 columns. > network/ttcp: Wrap README at 72 columns. > network/ttdnsd: Wrap README at 72 columns. > network/tunctl: Wrap README at 72 columns. > network/turbolift: Wrap README at 72 columns. > network/ubertooth: Wrap README at 72 columns. > network/ucspi-tcp: Wrap README at 72 columns. > network/udpcast: Wrap README at 72 columns. > network/ufw: Wrap README at 72 columns. > network/uget-chrome-wrapper: Wrap README at 72 columns. > network/uget-integrator: Wrap README at 72 columns. > network/urlgrabber: Wrap README at 72 columns. > network/urlscan: Wrap README at 72 columns. > network/urlview: Wrap README at 72 columns. > network/uudeview: Wrap README at 72 columns. > network/verlihub: Wrap README at 72 columns. > network/vmware-horizon-client: Wrap README at 72 columns. > network/vnstat: Move setup instructions to README.SBo. > network/vnstat: Wrap README at 72 columns. > network/vrrpd: Wrap README at 72 columns. > network/w3af: Wrap README at 72 columns. > network/webhook: Wrap README at 72 columns. > network/weighmail: Wrap README at 72 columns. > network/wendzelnntpd: Remove template comment. > network/wildfly: Wrap README at 72 columns. > network/wireshark: Wrap README at 72 columns. > network/wmget: Wrap README at 72 columns. > network/wmnotify: Wrap README at 72 columns. > network/wp-cli: Remove tabs from README. > network/wrk: Wrap README at 72 columns. > network/wvdial: Wrap README at 72 columns. > network/x11spice: Wrap README at 72 columns. > network/x11vnc: Wrap README at 72 columns. > network/x2goserver: Wrap README at 72 columns. > network/xinetd: Wrap README at 72 columns. > network/xl2tpd: Wrap README at 72 columns. > network/xnetload: Wrap README at 72 columns. > network/yadifa: Remove tabs from README. > network/yate: Wrap README at 72 columns. > network/youtube-dl-gui: Wrap README at 72 columns. > network/zabbix_agentd: Wrap README at 72 columns. > network/zabbix_java_gateway: Wrap README at 72 columns. > network/zabbix_proxy: Wrap README at 72 columns. > network/zabbix_server: Wrap README at 72 columns. > network/zmap: Wrap README at 72 columns. > network/znc: Wrap README at 72 columns. > network/zoom-linux: Make slack-desc ASCII. > office/FreeOffice: Make slack-desc ASCII. > office/JabRef: Fix BUILD usage. > office/LanguageTool: Wrap README at 72 columns. > office/LibreOffice: Remove tabs from README. > office/LibreOffice: Wrap README at 72 columns. > office/Ted: Wrap README at 72 columns. > office/adobe-reader-fontpacks: Wrap README at 72 columns. > office/aigaion: Wrap README at 72 columns. > office/anorack: Remove tabs from README. > office/apvlv: Wrap README at 72 columns. > office/basket: Wrap README at 72 columns. > office/briss: Wrap README at 72 columns. > office/broffice.org: Wrap README at 72 columns. > office/calibre: Wrap README at 72 columns. > office/cups-pdf: Wrap README at 72 columns. > office/devtodo: Wrap README at 72 columns. > office/ding: Wrap README at 72 columns. > office/docx2txt: Wrap README at 72 columns. > office/elyxer: Wrap README at 72 columns. > office/epdfview: Wrap README at 72 columns. > office/flowkeeper: Wrap README at 72 columns. > office/ghostwriter: Remove template comment. > office/homebank: Wrap README at 72 columns. > office/htmldoc: Wrap README at 72 columns. > office/jstock: Wrap README at 72 columns. > office/keepassxc: Wrap README at 72 columns. > office/keepnote: Wrap README at 72 columns. > office/latex2rtf: Wrap README at 72 columns. > office/lcal: Wrap README at 72 columns. > office/libreoffice-langpack: Wrap README at 72 columns. > office/minidjvu: Wrap README at 72 columns. > office/moneydance: Wrap README at 72 columns. > office/msee: Add network warning to README. > office/msee: Wrap README at 72 columns. > office/mu: Wrap README at 72 columns. > office/multivalent-tool-pdf: Wrap README at 72 columns. > office/odt2txt: Wrap README at 72 columns. > office/pandoc: Wrap README at 72 columns. > office/pdfpc: Wrap README at 72 columns. > office/pdftk: Wrap README at 72 columns. > office/ps2eps: Wrap README at 72 columns. > office/pstoedit: Wrap README at 72 columns. > office/pstotext: Wrap README at 72 columns. > office/pyspread: Wrap README at 72 columns. > office/scribus: Wrap README at 72 columns. > office/t-prot: Wrap README at 72 columns. > office/taskjuggler: Wrap README at 72 columns. > office/taskopen: Wrap README at 72 columns. > office/tellico: Wrap README at 72 columns. > office/text2pdf: Wrap README at 72 columns. > office/tpp: Wrap README at 72 columns. > office/traduisons: Wrap README at 72 columns. > office/trello-cli: Add network warning to README. > office/tudu: Wrap README at 72 columns. > office/verbiste: Wrap README at 72 columns. > office/vmd: Wrap README at 72 columns. > office/watson: Wrap README at 72 columns. > office/xmind: Wrap README at 72 columns. > perl/perl-Bit-Vector: Wrap README at 72 columns. > perl/perl-CGI: Wrap README at 72 columns. > perl/perl-CPAN-Changes: Wrap README at 72 columns. > perl/perl-Carp-Clan: Wrap README at 72 columns. > perl/perl-Class-Gomor: Wrap README at 72 columns. > perl/perl-Config-File: Wrap README at 72 columns. > perl/perl-Config-IniFiles: Wrap README at 72 columns. > perl/perl-Convert-ASN1: Wrap README at 72 columns. > perl/perl-Crypt-Blowfish_PP: Wrap README at 72 columns. > perl/perl-Crypt-CAST5: Wrap README at 72 columns. > perl/perl-Crypt-CBC: Wrap README at 72 columns. > perl/perl-Crypt-IDEA: Wrap README at 72 columns. > perl/perl-Crypt-OpenSSL-AES: Wrap README at 72 columns. > perl/perl-Crypt-OpenSSL-Guess: Wrap README at 72 columns. > perl/perl-Crypt-OpenSSL-RSA: Wrap README at 72 columns. > perl/perl-Crypt-Rijndael: Wrap README at 72 columns. > perl/perl-Data-UUID: Wrap README at 72 columns. > perl/perl-Date-Calc: Wrap README at 72 columns. > perl/perl-DateTime-Format-Builder: Wrap README at 72 columns. > perl/perl-DateTime-Format-ISO8601: Wrap README at 72 columns. > perl/perl-DateTime-Format-Strptime: Wrap README at 72 columns. > perl/perl-Devel-PartialDump: Wrap README at 72 columns. > perl/perl-Encode-Detect: Wrap README at 72 columns. > perl/perl-ExtUtils-Install: Wrap README at 72 columns. > perl/perl-ExtUtils-ModuleMaker: Wrap README at 72 columns. > perl/perl-File-Copy-Recursive: Wrap README at 72 columns. > perl/perl-File-Finder: Wrap README at 72 columns. > perl/perl-File-Remove: Wrap README at 72 columns. > perl/perl-File-ShareDir-Install: Wrap README at 72 columns. > perl/perl-File-Slurp: Wrap README at 72 columns. > perl/perl-Geo-IP: Wrap README at 72 columns. > perl/perl-Geography-Countries: Wrap README at 72 columns. > perl/perl-Gtk2-Ex-Simple-List: Wrap README at 72 columns. > perl/perl-HTML-HTMLDoc: Wrap README at 72 columns. > perl/perl-IO-All: Wrap README at 72 columns. > perl/perl-IO-CaptureOutput: Wrap README at 72 columns. > perl/perl-IO-Socket-INET6: Wrap README at 72 columns. > perl/perl-IO-Socket-Multicast: Wrap README at 72 columns. > perl/perl-IO-Tty: Wrap README at 72 columns. > perl/perl-IO-stringy: Wrap README at 72 columns. > perl/perl-Inline-C: Wrap README at 72 columns. > perl/perl-List-AllUtils: Wrap README at 72 columns. > perl/perl-Log-Dispatch: Wrap README at 72 columns. > perl/perl-MIME-tools: Wrap README at 72 columns. > perl/perl-Mail-SPF-Query: Wrap README at 72 columns. > perl/perl-MailTools: Wrap README at 72 columns. > perl/perl-Math-Base85: Wrap README at 72 columns. > perl/perl-Module-Build: Wrap README at 72 columns. > perl/perl-Mojolicious-Plugin-Humane: Wrap README at 72 columns. > perl/perl-MooX-StrictConstructor: Wrap README at 72 columns. > perl/perl-Net-CIDR-Lite: Wrap README at 72 columns. > perl/perl-Net-CIDR: Wrap README at 72 columns. > perl/perl-Net-IPv4Addr: Wrap README at 72 columns. > perl/perl-Net-IPv6Addr: Wrap README at 72 columns. > perl/perl-Net-Jabber: Wrap README at 72 columns. > perl/perl-Net-LibIDN: Wrap README at 72 columns. > perl/perl-Net-Libdnet: Wrap README at 72 columns. > perl/perl-Net-Pcap: Wrap README at 72 columns. > perl/perl-Net-RawIP: Wrap README at 72 columns. > perl/perl-Net-SNMP: Wrap README at 72 columns. > perl/perl-Net-Telnet: Wrap README at 72 columns. > perl/perl-Net-Write: Wrap README at 72 columns. > perl/perl-NetPacket: Wrap README at 72 columns. > perl/perl-Pegex: Wrap README at 72 columns. > perl/perl-Proc-PID-File: Wrap README at 72 columns. > perl/perl-Scope-Guard: Wrap README at 72 columns. > perl/perl-Socket6: Wrap README at 72 columns. > perl/perl-Statistics-Descriptive: Wrap README at 72 columns. > perl/perl-String-PerlIdentifier: Wrap README at 72 columns. > perl/perl-Switch: Wrap README at 72 columns. > perl/perl-Syntax-Highlight-Engine-Kate: Wrap README at 72 columns. > perl/perl-Sys-Mmap: Wrap README at 72 columns. > perl/perl-TeX-Hyphen: Wrap README at 72 columns. > perl/perl-Term-ProgressBar: Wrap README at 72 columns. > perl/perl-Test-LongString: Wrap README at 72 columns. > perl/perl-Test-PerlTidy: Wrap README at 72 columns. > perl/perl-Test-RequiresInternet: Wrap README at 72 columns. > perl/perl-Test-Simple: Wrap README at 72 columns. > perl/perl-Test-SubCalls: Wrap README at 72 columns. > perl/perl-Text-CSV_XS: Wrap README at 72 columns. > perl/perl-Text-Tabs+Wrap: Wrap README at 72 columns. > perl/perl-TryCatch: Wrap README at 72 columns. > perl/perl-Unicode-Map8: Wrap README at 72 columns. > perl/perl-Unicode-Map: Wrap README at 72 columns. > perl/perl-X11-Protocol-Other: Disable test by default (requires X). > perl/perl-X11-Protocol-Other: Wrap README at 72 columns. > perl/perl-XML-XPath: Wrap README at 72 columns. > perl/perl-YAML-LibYAML: Wrap README at 72 columns. > perl/perl-digest-hmac: Wrap README at 72 columns. > perl/perl-encode-locale: Wrap README at 72 columns. > perl/perl-file-desktopentry: Wrap README at 72 columns. > perl/perl-file-listing: Wrap README at 72 columns. > perl/perl-html-parser: Wrap README at 72 columns. > perl/perl-http-tiny: Wrap README at 72 columns. > perl/perl-inc-latest: Wrap README at 72 columns. > perl/perl-x11-protocol: Wrap README at 72 columns. > python/Baker: Wrap README at 72 columns. > python/PyGreSQL: Wrap README at 72 columns. > python/PyInstaller: Wrap README at 72 columns. > python/PyPDF2: Wrap README at 72 columns. > python/PyStemmer: Wrap README at 72 columns. > python/PythonQt: Wrap README at 72 columns. > python/RBTools: Wrap README at 72 columns. > python/WebHelpers: Removed, replaced by WebHelpers2 on python3-webhelpers2 > python/XlsxWriter: Wrap README at 72 columns. > python/affine: Wrap README at 72 columns. > python/anyjson: Removed, very old and not in any more REQUIRES > python/apsw: Wrap README at 72 columns. > python/argcomplete: Wrap README at 72 columns. > python/argh: Wrap README at 72 columns. > python/arrow: Wrap README at 72 columns. > python/artifacts: Wrap README at 72 columns. > python/asgiref: Wrap README at 72 columns. > python/atomicwrites: Wrap README at 72 columns. > python/backcall: Wrap README at 72 columns. > python/backports.lzma: Wrap README at 72 columns. > python/bencode: Wrap README at 72 columns. > python/biplist: Wrap README at 72 columns. > python/bleach: Wrap README at 72 columns. > python/boto3: Wrap README at 72 columns. > python/boto: Wrap README at 72 columns. > python/buildbot-worker: updated for version 3.5.0, updated dependencies > python/cddb-py: Wrap README at 72 columns. > python/cfgparse: Wrap README at 72 columns. > python/cheetah3: Make slack-desc ASCII. > python/cheroot: Wrap README at 72 columns. > python/click-default-group: Wrap README at 72 columns. > python/click-didyoumean: Make slack-desc ASCII. > python/click: Wrap README at 72 columns. > python/clint: Wrap README at 72 columns. > python/colorama: Wrap README at 72 columns. > python/construct: Wrap README at 72 columns. > python/contextlib2: Make slack-desc ASCII. > python/contextlib2: Wrap README at 72 columns. > python/coverage: Wrap README at 72 columns. > python/cryptography: Wrap README at 72 columns. > python/cssselect: Wrap README at 72 columns. > python/defusedxml: Wrap README at 72 columns. > python/dfdatetime: Wrap README at 72 columns. > python/dfvfs: Wrap README at 72 columns. > python/dfwinreg: Wrap README at 72 columns. > python/django-debug-toolbar: Wrap README at 72 columns. > python/dotty: Wrap README at 72 columns. > python/dtfabric: Wrap README at 72 columns. > python/dukpy: Wrap README at 72 columns. > python/easygui: Wrap README at 72 columns. > python/elasticsearch5: Wrap README at 72 columns. > python/entrypoints: Wrap README at 72 columns. > python/feedparser: Remove tabs from README. > python/feedparser: Wrap README at 72 columns. > python/flask-paginate: Wrap README at 72 columns. > python/frosted: Wrap README at 72 columns. > python/hachoir-core: Wrap README at 72 columns. > python/hachoir-metadata: Wrap README at 72 columns. > python/hachoir-parser: Wrap README at 72 columns. > python/hachoir: Wrap README at 72 columns. > python/ipython_genutils: Wrap README at 72 columns. > python/josepy: Updated for version 1.13.0. > python/json-py: Wrap README at 72 columns. > python/llfuse: Wrap README at 72 columns. > python/mini-amf: Wrap README at 72 columns. > python/monotonic: Wrap README at 72 columns. > python/more-itertools: Wrap README at 72 columns. > python/mpmath: Wrap README at 72 columns. > python/msgpack-python: Wrap README at 72 columns. > python/ndg_httpsclient: Wrap README at 72 columns. > python/nest_asyncio: Wrap README at 72 columns. > python/numexpr: Wrap README at 72 columns. > python/odoo: Changed REQUIRES for python3-psycopg2 > python/parso: Wrap README at 72 columns. > python/pefile: Wrap README at 72 columns. > python/phply: Wrap README at 72 columns. > python/pickleshare: Wrap README at 72 columns. > python/pillowfight: Wrap README at 72 columns. > python/pkginfo: Wrap README at 72 columns. > python/plaso: Changed REQUIRES for python2-pyzmq > python/poster: Wrap README at 72 columns. > python/psutil: Wrap README at 72 columns. > python/pyamf: Wrap README at 72 columns. > python/pybind11: Updated for version 2.9.1 > python/pybind11: Wrap README at 72 columns. > python/pycdio: Wrap README at 72 columns. > python/pychecker: Wrap README at 72 columns. > python/pycryptopp: Wrap README at 72 columns. > python/pycxx: Wrap README at 72 columns. > python/pyflakes: Wrap README at 72 columns. > python/pygpgme: Wrap README at 72 columns. > python/pyjwt: Wrap README at 72 columns. > python/pynzb: Wrap README at 72 columns. > python/pyqode.cobol: Wrap README at 72 columns. > python/pyresample: Wrap README at 72 columns. > python/pysha3: Wrap README at 72 columns. > python/pysqlite: Wrap README at 72 columns. > python/pysvn: Wrap README at 72 columns. > python/pytest-cov: Wrap README at 72 columns. > python/pytest: Changed REQUIRES for python2-attrs > python/python-PySnooper: Wrap README at 72 columns. > python/python-argopt: Wrap README at 72 columns. > python/python-emoji: Wrap README at 72 columns. > python/python-fonttools: Updated for version 4.30.0. > python/python-importlib_metadata: Wrap README at 72 columns. > python/python-joblib: Wrap README at 72 columns. > python/python-jsonrpclib: Updated for verson 0.4.3.2. > python/python-kerberos: Wrap README at 72 columns. > python/python-ly: Wrap README at 72 columns. > python/python-magic: Wrap README at 72 columns. > python/python-markdown-math: Wrap README at 72 columns. > python/python-musicbrainz2: Wrap README at 72 columns. > python/python-nbxmpp: Wrap README at 72 columns. > python/python-neovim: Wrap README at 72 columns. > python/python-pcapy: Wrap README at 72 columns. > python/python-precis-i18n: Wrap README at 72 columns. > python/python-prometheus_client: Wrap README at 72 columns. > python/python-sh: Wrap README at 72 columns. > python/python2-attrs: renamed from attrs, updated for version 21.2.0 > python/python2-automat: renamed from Automat, updated for version 20.2.0 > python/python2-pycrypto: Fix PRGNAM in script. > python/python2-pyzmq: renamed from pyzmq > python/python2-selectors2: Wrap README at 72 columns. > python/python2-twisted: updated for version 20.3.0, updated REQUIRES > python/python3-amqp: Wrap README at 72 columns. > python/python3-defusedxml: Wrap README at 72 columns. > python/python3-django: Wrap README at 72 columns. > python/python3-gitdb2: Wrap README at 72 columns. > python/python3-hupper: Wrap README at 72 columns. > python/python3-ipaddr: Wrap README at 72 columns. > python/python3-isort: Wrap README at 72 columns. > python/python3-jedi: Changed REQUIRES for python3-parso > python/python3-kiwisolver: Wrap README at 72 columns. > python/python3-monotonic: Wrap README at 72 columns. > python/python3-nltk: Wrap README at 72 columns. > python/python3-nxt-python: Wrap README at 72 columns. > python/python3-paginate: Wrap README at 72 columns. > python/python3-pandas: Wrap README at 72 columns. > python/python3-parso: renamed from parso > python/python3-paste: Wrap README at 72 columns. > python/python3-pexpect: Wrap README at 72 columns. > python/python3-prompt_toolkit: Wrap README at 72 columns. > python/python3-psycopg2: renamed from psycopg2 > python/python3-pyjwt: Wrap README at 72 columns. > python/python3-pylint: Wrap README at 72 columns. > python/python3-pyparted: Wrap README at 72 columns. > python/python3-rsa: Make slack-desc ASCII. > python/python3-setuptools_autover: Wrap README at 72 columns. > python/python3-tekore: Make slack-desc ASCII. > python/python3-twisted: Wrap README at 72 columns. > python/python3-urlobject: Wrap README at 72 columns. > python/python3-uth: Wrap README at 72 columns. > python/python3-waitress: Wrap README at 72 columns. > python/python3-webhelpers2: Wrap README at 72 columns. > python/pyudev: Wrap README at 72 columns. > python/readme_renderer: Wrap README at 72 columns. > python/requirements-detector: Wrap README at 72 columns. > python/rfc6555: Wrap README at 72 columns. > python/rsa: Wrap README at 72 columns. > python/salt: Changed REQUIRES for python2-pyzmq > python/scikit-learn: Wrap README at 72 columns. > python/selenium: Wrap README at 72 columns. > python/send2trash: Wrap README at 72 columns. > python/service_identity: Changed REQUIRES for python2-attrs > python/setuptools-scm-git-archive: Wrap README at 72 columns. > python/simplejson: Wrap README at 72 columns. > python/snowballstemmer: Wrap README at 72 columns. > python/sphinxcontrib-applehelp: Wrap README at 72 columns. > python/sphinxcontrib-devhelp: Wrap README at 72 columns. > python/sphinxcontrib-jsmath: Wrap README at 72 columns. > python/sphinxcontrib-qthelp: Wrap README at 72 columns. > python/sphinxcontrib-serializinghtml: Wrap README at 72 columns. > python/sphinxcontrib-websupport: Wrap README at 72 columns. > python/sqlparse: Wrap README at 72 columns. > python/stopit: Wrap README at 72 columns. > python/subprocess32: Wrap README at 72 columns. > python/subuser: Wrap README at 72 columns. > python/testpath: Wrap README at 72 columns. > python/timehash: Wrap README at 72 columns. > python/tinycss: Wrap README at 72 columns. > python/tox: Wrap README at 72 columns. > python/traitlets: Wrap README at 72 columns. > python/trezor: Wrap README at 72 columns. > python/typed_ast: Wrap README at 72 columns. > python/vinetto: Wrap README at 72 columns. > python/waitress: Wrap README at 72 columns. > python/websocket-client: Wrap README at 72 columns. > python/werkzeug: Wrap README at 72 columns. > python/xlutils: Wrap README at 72 columns. > python/yara-python: Wrap README at 72 columns. > python/zxcvbn-python: Wrap README at 72 columns. > ruby/ncurses-ruby: Wrap README at 72 columns. > ruby/rbenv: Wrap README at 72 columns. > ruby/ruby-native-package-installer: Wrap README at 72 columns. > ruby/rubygem-activesupport: Wrap README at 72 columns. > ruby/rubygem-coderay: Wrap README at 72 columns. > ruby/rubygem-concurrent-ruby: Wrap README at 72 columns. > ruby/rubygem-cool.io: Wrap README at 72 columns. > ruby/rubygem-daemons: Wrap README at 72 columns. > ruby/rubygem-diff-lcs: Wrap README at 72 columns. > ruby/rubygem-fastercsv: Wrap README at 72 columns. > ruby/rubygem-file-tail: Wrap README at 72 columns. > ruby/rubygem-fluentd: Wrap README at 72 columns. > ruby/rubygem-gtk2: Wrap README at 72 columns. > ruby/rubygem-highline: Wrap README at 72 columns. > ruby/rubygem-http_parser.rb: Wrap README at 72 columns. > ruby/rubygem-manpages: Wrap README at 72 columns. > ruby/rubygem-msgpack: Wrap README at 72 columns. > ruby/rubygem-mustache: Wrap README at 72 columns. > ruby/rubygem-net-ssh: Wrap README at 72 columns. > ruby/rubygem-optimist: Wrap README at 72 columns. > ruby/rubygem-ronn: Wrap README at 72 columns. > ruby/rubygem-rspec-mocks: Wrap README at 72 columns. > ruby/rubygem-rspec: Wrap README at 72 columns. > ruby/rubygem-ruby2ruby: Wrap README at 72 columns. > ruby/rubygem-ruby_parser: Wrap README at 72 columns. > ruby/rubygem-sass: Wrap README at 72 columns. > ruby/rubygem-sexp_processor: Wrap README at 72 columns. > ruby/rubygem-slop3: Wrap README at 72 columns. > ruby/rubygem-sourcify: Wrap README at 72 columns. > ruby/rubygem-trogdoro-el4r: Wrap README at 72 columns. > ruby/rubygem-tzinfo-data: Wrap README at 72 columns. > ruby/rubygem-xiki: Wrap README at 72 columns. > system/AnonymousPro: Wrap README at 72 columns. > system/GentiumPlus: Wrap README at 72 columns. > system/Iosevka: Updated for version 15.0.2 > system/SavvyCAN: Wrap README at 72 columns. > system/Sl: Silence sbolint doinst.sh warning. > system/TLP: Wrap README at 72 columns. > system/ZoneMinder: Wrap README at 72 columns. > system/acpi: Wrap README at 72 columns. > system/adobe-source-code-pro-font: Wrap README at 72 columns. > system/adobe-source-sans-pro-font: Wrap README at 72 columns. > system/afuse: Wrap README at 72 columns. > system/amanda: Wrap README at 72 columns. > system/apache-activemq: Wrap README at 72 columns. > system/apache-tomcat: Updated for version 10.0.18. > system/apache-tomcat: Wrap README at 72 columns. > system/apachetop: Wrap README at 72 columns. > system/apcupsd: Wrap README at 72 columns. > system/apparmor: Wrap README at 72 columns. > system/artwiz-aleczapka: Wrap README at 72 columns. > system/artwiz-cursor: Wrap README at 72 columns. > system/asbt: Wrap README at 72 columns. > system/aterm: Wrap README at 72 columns. > system/audit: Wrap README at 72 columns. > system/augeas: Wrap README at 72 columns. > system/avfs: Wrap README at 72 columns. > system/bacula-client: Wrap README at 72 columns. > system/bacula: Wrap README at 72 columns. > system/barman: Changed REQUIRES for python3-psycopg2 and python3-dateutil > system/bcache-tools: Wrap README at 72 columns. > system/binfmt-support: Wrap README at 72 columns. > system/bootchart: Wrap README at 72 columns. > system/btop: Update to 15.0 template. > system/bubblewrap: Wrap README at 72 columns. > system/buildah: Wrap README at 72 columns. > system/bulk_extractor: Wrap README at 72 columns. > system/burp: Wrap README at 72 columns. > system/byobu: Wrap README at 72 columns. > system/capabilities: Wrap README at 72 columns. > system/caprice32: Wrap README at 72 columns. > system/ccd2iso: Wrap README at 72 columns. > system/ccid: Wrap README at 72 columns. > system/cdemu-client: Wrap README at 72 columns. > system/cdrkit: Wrap README at 72 columns. > system/cdw: Update email > system/cdw: Wrap README at 72 columns. > system/chronograf: Make slack-desc ASCII. > system/clamav: Wrap README at 72 columns. > system/cndrvcups-capt: Wrap README at 72 columns. > system/cndrvcups-common: Wrap README at 72 columns. > system/cnijfilter2: Wrap README at 72 columns. > system/cntlm: Wrap README at 72 columns. > system/commons-daemon: Wrap README at 72 columns. > system/conmon: Wrap README at 72 columns. > system/containerd: Add network warning to README. > system/coolkey: Wrap README at 72 columns. > system/corosync: Wrap README at 72 columns. > system/crashplan: Wrap README at 72 columns. > system/crmsh: Wrap README at 72 columns. > system/cronie: Wrap README at 72 columns. > system/cwtex-q-fonts-TTFs: Wrap README at 72 columns. > system/daemontools: Wrap README at 72 columns. > system/dahdi-complete: Wrap README at 72 columns. > system/davfs2: Wrap README at 72 columns. > system/debootstrap: Wrap README at 72 columns. > system/diskscan: Wrap README at 72 columns. > system/disksearch: Wrap README at 72 columns. > system/displaylink: Wrap README at 72 columns. > system/dlm: Wrap README at 72 columns. > system/dosbox-dev: Move setup instructions to README.SBo. > system/dosbox-dev: Wrap README at 72 columns. > system/dosbox-dev: updated for version 0.75_pre4473 > system/drbd-utils: Wrap README at 72 columns. > system/driconf: Wrap README at 72 columns. > system/dstat: Wrap README at 72 columns. > system/duplicity: Wrap README at 72 columns. > system/dust: Wrap README at 72 columns. > system/dvdisaster: Wrap README at 72 columns. > system/ecryptfs-utils: Wrap README at 72 columns. > system/efitools: Wrap README at 72 columns. > system/eibd: Wrap README at 72 columns. > system/elasticsearch: Wrap README at 72 columns. > system/eltclsh: Wrap README at 72 columns. > system/eventlog: Wrap README at 72 columns. > system/execline: Updated for version 2.8.3.0 > system/exfat-utils: Wrap README at 72 columns. > system/fence-agents: Wrap README at 72 columns. > system/findpkg: Wrap README at 72 columns. > system/fio: Wrap README at 72 columns. > system/firejail: Wrap README at 72 columns. > system/firmware-gobi-2000: Wrap README at 72 columns. > system/foomatic-db-engine: Wrap README at 72 columns. > system/foomatic-db: Wrap README at 72 columns. > system/foremost: Wrap README at 72 columns. > system/freeswitch: Wrap README at 72 columns. > system/fslint: Wrap README at 72 columns. > system/fswatch: Wrap README at 72 columns. > system/fuse-exfat: Wrap README at 72 columns. > system/gammu: Wrap README at 72 columns. > system/gconf-editor: Wrap README at 72 columns. > system/gdmap: Wrap README at 72 columns. > system/gigolo: Wrap README at 72 columns. > system/glances: Wrap README at 72 columns. > system/gnu-unifont: Updated for version 14.0.02. > system/gnu-unifont: Wrap README at 72 columns. > system/go-mtree: Add network warning to README. > system/gpart: Wrap README at 72 columns. > system/heartbeat: Wrap README at 72 columns. > system/hstr: Wrap README at 72 columns. > system/hwinfo: Wrap README at 72 columns. > system/i8kutils: Wrap README at 72 columns. > system/icingaweb2: Wrap README at 72 columns. > system/idle3-tools: Wrap README at 72 columns. > system/influxdb: Wrap README at 72 columns. > system/irqbalance: Wrap README at 72 columns. > system/isight-firmware-tools: Wrap README at 72 columns. > system/isomaster: Wrap README at 72 columns. > system/jdiskreport: Wrap README at 72 columns. > system/kapacitor: Wrap README at 72 columns. > system/kbfs: Wrap README at 72 columns. > system/kc: Remove tabs from README. > system/kc: Wrap README at 72 columns. > system/ksh-openbsd: Wrap README at 72 columns. > system/laptop-mode-tools: Wrap README at 72 columns. > system/letsencrypt: Updated for version 1.25.0. > system/letsencrypt: Wrap README at 72 columns. > system/libnatspec: Wrap README at 72 columns. > system/local-persist: Add network warning to README. > system/locust: Wrap README at 72 columns. > system/logkeys: Wrap README at 72 columns. > system/luckybackup: Wrap README at 72 columns. > system/lxsplit: Wrap README at 72 columns. > system/mailfromd: Wrap README at 72 columns. > system/mailutils: Wrap README at 72 columns. > system/makepp: Fix broken symlinks. > system/makeself: Wrap README at 72 columns. > system/mcrypt: Wrap README at 72 columns. > system/memtest86+: Wrap README at 72 columns. > system/memtest86: Wrap README at 72 columns. > system/microcode_ctl: Wrap README at 72 columns. > system/monit: Wrap README at 72 columns. > system/monitoring-plugins: Wrap README at 72 columns. > system/motion: Wrap README at 72 columns. > system/mpich: Wrap README at 72 columns. > system/msr-tools: Wrap README at 72 columns. > system/multiload-ng: Wrap README at 72 columns. > system/multitail: Wrap README at 72 columns. > system/munin-node: Wrap README at 72 columns. > system/musl: Wrap README at 72 columns. > system/nagios-plugins: Wrap README at 72 columns. > system/nagvis: Wrap README at 72 columns. > system/nano-syntax-highlighting: Wrap README at 72 columns. > system/nbench: Wrap README at 72 columns. > system/netatop: Wrap README at 72 columns. > system/nix: Wrap README at 72 columns. > system/nmon: Wrap README at 72 columns. > system/noto-emoji: Wrap README at 72 columns. > system/nsca-ng: Wrap README at 72 columns. > system/nss_ldap: Wrap README at 72 columns. > system/nut: Wrap README at 72 columns. > system/nvidia-legacy340-kernel: Wrap README at 72 columns. > system/ohsnap: Wrap README at 72 columns. > system/opendoas: Handle environment BUILD better. > system/openrc: Wrap README at 72 columns. > system/opensc: Wrap README at 72 columns. > system/ossec-agent: Wrap README at 72 columns. > system/ossec-local: Wrap README at 72 columns. > system/ossec-server: Wrap README at 72 columns. > system/otf-hermit: Wrap README at 72 columns. > system/pacemaker: Wrap README at 72 columns. > system/pass-otp: Wrap README at 72 columns. > system/passwdqc: Wrap README at 72 columns. > system/password-store: Wrap README at 72 columns. > system/patool: Wrap README at 72 columns. > system/pause: Wrap README at 72 columns. > system/pbzip2: Wrap README at 72 columns. > system/pcsc-lite: Wrap README at 72 columns. > system/pcsc-tools: Wrap README at 72 columns. > system/percona-toolkit: Wrap README at 72 columns. > system/phpsysinfo: Wrap README at 72 columns. > system/picocom: Wrap README at 72 columns. > system/pixma: Remove tabs from README. > system/pixma: Wrap README at 72 columns. > system/plan9port: Remove tabs from README. > system/plan9port: Wrap README at 72 columns. > system/podman: Wrap README at 72 columns. > system/porg: Wrap README at 72 columns. > system/procinfo-ng: Wrap README at 72 columns. > system/prometheus: Updated to version 2.34.0 > system/pwgen: Wrap README at 72 columns. > system/pwman: Wrap README at 72 columns. > system/pwsafe: Wrap README at 72 columns. > system/qdirstat: Wrap README at 72 columns. > system/qemu: Wrap README at 72 columns. > system/qtgzmanager: Wrap README at 72 columns. > system/ranger: Wrap README at 72 columns. > system/rar2fs: Wrap README at 72 columns. > system/rear: Wrap README at 72 columns. > system/recoverdm: Wrap README at 72 columns. > system/refind: Wrap README at 72 columns. > system/rename: Wrap README at 72 columns. > system/resource-agents: Wrap README at 72 columns. > system/rhash: Wrap README at 72 columns. > system/rkhunter: Wrap README at 72 columns. > system/rng-tools: Wrap README at 72 columns. > system/runit-services: Wrap README at 72 columns. > system/runit: Wrap README at 72 columns. > system/rush: Wrap README at 72 columns. > system/s3ql: Wrap README at 72 columns. > system/s6-linux-init: Updated for version 1.0.7.3 > system/s6: Updated for version 2.11.1.0 > system/saleae-logic: Wrap README at 72 columns. > system/samhain: Wrap README at 72 columns. > system/sargon: Add network warning to README. > system/sbbdep: Wrap README at 72 columns. > system/sbotools: Wrap README at 72 columns. > system/sboui: Wrap README at 72 columns. > system/scalpel: Wrap README at 72 columns. > system/scangearmp2: Wrap README at 72 columns. > system/scanmem: Wrap README at 72 columns. > system/schedtool: Wrap README at 72 columns. > system/sdltrs: Wrap README at 72 columns. > system/sentimental-skk: Wrap README at 72 columns. > system/signify: Wrap README at 72 columns. > system/skim: Wrap README at 72 columns. > system/skopeo: Wrap README at 72 columns. > system/slack-osquery: Fix HOMEPAGE. > system/slack-osquery: Wrap README at 72 columns. > system/smart: Wrap README at 72 columns. > system/socklog: Wrap README at 72 columns. > system/softhsm: Wrap README at 72 columns. > system/splix: Wrap README at 72 columns. > system/sqlcipher: Wrap README at 72 columns. > system/sqldiff: Wrap README at 72 columns. > system/squidclamav: Move setup instructions to README.SBo. > system/srm: Wrap README at 72 columns. > system/sudosh2: Wrap README at 72 columns. > system/sunflower: Fix VERSION in script. > system/sysdig: Wrap README at 72 columns. > system/syslog-ng: Wrap README at 72 columns. > system/system76-io-dkms: Wrap README at 72 columns. > system/tagainijisho: Updated for version 1.1.93. > system/telegraf: Make slack-desc ASCII. > system/telegraf: Wrap README at 72 columns. > system/termenu: Wrap README at 72 columns. > system/terminator: Wrap README at 72 columns. > system/terminology: Wrap README at 72 columns. > system/thermald: Wrap README at 72 columns. > system/thin-provisioning-tools: Wrap README at 72 columns. > system/thinkfan: Wrap README at 72 columns. > system/tinycdb: Wrap README at 72 columns. > system/tm: Move setup instructions to README.SBo. > system/tm: Wrap README at 72 columns. > system/trashy: Clean up build. > system/ts: Wrap README at 72 columns. > system/ttf-lato: Wrap README at 72 columns. > system/ttop: Wrap README at 72 columns. > system/tty2gif: Wrap README at 72 columns. > system/ttygif: Wrap README at 72 columns. > system/twin: Wrap README at 72 columns. > system/unace: Wrap README at 72 columns. > system/unhide: Wrap README at 72 columns. > system/unison: Wrap README at 72 columns. > system/unp: Wrap README at 72 columns. > system/uptimed: Wrap README at 72 columns. > system/usbrelay: Wrap README at 72 columns. > system/usbview: Wrap README at 72 columns. > system/vagrant: Wrap README at 72 columns. > system/vhba-module: Wrap README at 72 columns. > system/virt-manager: Wrap README at 72 columns. > system/volatility: Wrap README at 72 columns. > system/wangfonts: Wrap README at 72 columns. > system/webcore-fonts: Wrap README at 72 columns. > system/webmin: Wrap README at 72 columns. > system/wiimms-iso-tools: Wrap README at 72 columns. > system/wmconfig: Wrap README at 72 columns. > system/wmfsm: Wrap README at 72 columns. > system/wqy-microhei-font-ttf: Wrap README at 72 columns. > system/x86_energy_perf_policy: Wrap README at 72 columns. > system/xbindkeys: Wrap README at 72 columns. > system/xen: Wrap README at 72 columns. > system/xen: x86 is unsupported. > system/xjobs: Wrap README at 72 columns. > system/xorgxrdp: Wrap README at 72 columns. > system/xosd: Wrap README at 72 columns. > system/xrdp: Wrap README at 72 columns. > system/xstow: Wrap README at 72 columns. > system/xtrs: Wrap README at 72 columns. > system/yaft: Wrap README at 72 columns. > system/yelp-tools: Wrap README at 72 columns. > system/yelp: Wrap README at 72 columns. > system/zfs-auto-snapshot: Wrap README at 72 columns. > system/zookeeper: Wrap README at 72 columns. > system/zopfli: Wrap README at 72 columns. > system/zpaq: Wrap README at 72 columns. > system/zsh-syntax-highlighting: Wrap README at 72 columns. > +--------------------------+ > > > -- > Willy Sudiarto Raharjo > -- Qun-Ying From matteo.bernardini at gmail.com Fri Mar 18 19:48:09 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 18 Mar 2022 20:48:09 +0100 Subject: [Slackbuilds-users] Updates - 20220317.1 In-Reply-To: References: Message-ID: Hi Qun-Ying, actually stuff in /extra, not being part of a Slackware full installation, is provided also here if being a dependency of something else: this is the case, for example, for fltk or the various java implementations... Matteo Il giorno ven 18 mar 2022 alle ore 20:21 Qun-Ying ha scritto: > Hi, > > fltk is provided from extra in official release, should be removed > from SlackBuild. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.pribs11 at gmail.com Sat Mar 19 05:05:48 2022 From: b.pribs11 at gmail.com (Brandon Pribula) Date: Fri, 18 Mar 2022 22:05:48 -0700 Subject: [Slackbuilds-users] Creating First Slackbuilds and Github Message-ID: <87v8waedi4.fsf@gmail.com> Hi, I'm new to creating SlackBuilds and using github so I apologize if this is obvious. I'm in the process of putting my first SlackBuilds together. The repos are on github. The first repo has archived releases but I would like to use master up to the most recent commit. And the second repo only has a master and no archived releases. I'm curious what the policy is regarding slackbuilds.org hosting tarballs? Thanks From dchmelik at gmail.com Sat Mar 19 11:35:28 2022 From: dchmelik at gmail.com (David Chmelik) Date: Sat, 19 Mar 2022 04:35:28 -0700 Subject: [Slackbuilds-users] Mathics 4 SlackBuild out Message-ID: <0e03b47d-47bc-973e-ac42-79318c93e5f6@gmail.com> Mathics 4 SlackBuilds is out (can add to SBo-git: ) http://davidchmelik.com/slackbuilds/academic/mathics.tar.gz . ? ? Mathics is Free/Libre/Opensource Software (FLS, OSS, FOSS, FLOSS) implementation of Wolfram (Mathematica) programming language subset.? Mathematica seemed main academic mathematics software during decades I was maths majoring at two colleges/unviersities (used at many worldwide and there are conferences for it.)? Of course many more exist (Casio & HP & Sharp & Ti & newer graphing calculators, Antiprism, Cadabra, Cantor, FET, Fractint, Genius, Geogebra, Gnofract, LabPlot, Maple, Mathomatic, MATLAB, Maxima, Pari, R, Reduce-Algebra, Rocs, SAGE, SMath Studio, Scilab, TeX, XaoS, ZeGrapher, most these being on SBo and some for mathematical logic,? applied mathematics/natural science, etc.) but all professors I had used Mathematica whether other software also. ??? Mathematica manual doesn't even fit a bookshelf since late '0s or early '10s and the only other almost-all-encompassing alternative one professor suggested is SAGE.? While a few others like MATLAB (unfortunately proprietary) may be easier for specific uses they're not as comprehensive. ??? Mathics is command-line/graphical but seems graphical version might now be separate software, so if you want that. don't necessarily upgrade... I'll try to SlackBuild and stated I'd try to SlackBuild Mathics-omnibus but if anyone beats me to those it's fine... From dchmelik at gmail.com Sat Mar 19 11:47:45 2022 From: dchmelik at gmail.com (David Neil Chmelik) Date: Sat, 19 Mar 2022 11:47:45 -0000 (UTC) Subject: [Slackbuilds-users] Mathics 4 SlackBuild out References: <0e03b47d-47bc-973e-ac42-79318c93e5f6@gmail.com> Message-ID: On Sat, 19 Mar 2022 04:35:28 -0700, David Chmelik wrote: > Mathics 4 SlackBuilds is out (can add to SBo-git: ) > http://davidchmelik.com/slackbuilds/academic/mathics.tar.gz Oops; https://davidchmelik.com/math/slackbuilds/academic/mathics.tar.gz From z.coldplayer at gmail.com Sat Mar 19 12:08:38 2022 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Sat, 19 Mar 2022 16:08:38 +0400 Subject: [Slackbuilds-users] Creating First Slackbuilds and Github In-Reply-To: <87v8waedi4.fsf@gmail.com> References: <87v8waedi4.fsf@gmail.com> Message-ID: Hi Brandon, You should consult this page first https://slackbuilds.org/guidelines/. If you have trouble , you can continue on this thread. Enjoy a good day Pritvi Jheengut On Sat, 19 Mar 2022 at 09:08, Brandon Pribula wrote: > Hi, > > I'm new to creating SlackBuilds and using github so I apologize if this is > obvious. > > I'm in the process of putting my first SlackBuilds together. The repos are > on github. The first repo has archived releases but I would like to use > master up to the most recent commit. > And the second repo only has a master and no archived releases. > > I'm curious what the policy is regarding slackbuilds.org hosting tarballs? > > Thanks > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sat Mar 19 13:08:02 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 19 Mar 2022 07:08:02 -0600 Subject: [Slackbuilds-users] Surprising failure building GHC In-Reply-To: References: Message-ID: Without Sphinx and/or Sage already in place, ghc can be built all right. With either of them already in place, it won't. On Fri, Mar 18, 2022 at 7:09 AM Erich Ritz wrote: > ------- Original Message ------- > > On Thursday, March 17th, 2022 at 10:21 PM, Luveh Keraph <1.41421 at gmail.com> > wrote: > > > After getting Sage out of the way, and installing Sphinx for good > measure, ghc still refuses to build: > > Try installing without Sphinx. On my build I did not have Sphinx > installed and it worked. > > Erich > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sb at rbn.im Sat Mar 19 14:08:12 2022 From: sb at rbn.im (Ruben Schuller) Date: Sat, 19 Mar 2022 15:08:12 +0100 Subject: [Slackbuilds-users] Creating First Slackbuilds and Github In-Reply-To: <87v8waedi4.fsf@gmail.com> References: <87v8waedi4.fsf@gmail.com> Message-ID: <20220319150812.6b876a5a@kiwi.kuchen> Hi, 2022-03-18 Brandon Pribula : > I'm in the process of putting my first SlackBuilds together. The > repos are on github. The first repo has archived releases but I would > like to use master up to the most recent commit. And the second repo > only has a master and no archived releases. I'd just use the link to the archive (zip) at a certain commit of your choice. > I'm curious what the policy is regarding slackbuilds.org hosting > tarballs? SBo doesn't host source tarballs :) Cheers Ruben From matteo.bernardini at gmail.com Sat Mar 19 14:18:13 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 19 Mar 2022 15:18:13 +0100 Subject: [Slackbuilds-users] Mathics 4 SlackBuild out In-Reply-To: References: <0e03b47d-47bc-973e-ac42-79318c93e5f6@gmail.com> Message-ID: New SlackBuilds must go through the submissions form once submissions will reopen... Matteo Il sab 19 mar 2022, 12:48 David Neil Chmelik ha scritto: > On Sat, 19 Mar 2022 04:35:28 -0700, David Chmelik wrote: > > > Mathics 4 SlackBuilds is out (can add to SBo-git: ) > > http://davidchmelik.com/slackbuilds/academic/mathics.tar.gz > > Oops; https://davidchmelik.com/math/slackbuilds/academic/mathics.tar.gz > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From psychi2009 at gmail.com Sat Mar 19 14:49:46 2022 From: psychi2009 at gmail.com (MDrights) Date: Sat, 19 Mar 2022 14:49:46 +0000 Subject: [Slackbuilds-users] Tor is up for grabs In-Reply-To: <20220317023142.GO30716@localhost> References: <20220317023142.GO30716@localhost> Message-ID: My PR has been created: https://gitlab.com/SlackBuilds.org/slackbuilds/-/merge_requests/293 And it is tested in 15.0. (hope the target branch, master, is the correct branch for the PR.) Cheers MDrights On Thu, Mar 17, 2022 at 02:31:43AM +0000, Dave Woodfall wrote: > On 17/03/22 01:43, > MDrights put forth the proposition: > > Hi Markus, > > Thanks for raising this thread again, after several months! > > I thought my request was forgotten by folks :) > > Yes, I am glad to take on Tor Slackbuild. I have been a long time Tor user as well :) > > I will submit an updated script shortly. > > My slackbuilds fork: https://gitlab.com/mdrights/slackbuilds/-/tree/local > > Let me know if any of you folks have any suggestions/concerns. > > (I am really feeling painful for the situation in Ukraine. God bless. and hope Tor may help.) > > Cheers, > > MDrights > > On Wed, Mar 16, 2022 at 11:26:02PM +0100, Markus Reichelt via SlackBuilds-users wrote: > > > * Dionysis Ntreou wrote: > > > > > > > Hello, > > > > I would like Tor too if nobody has taken it . > > > > > > Thank you for your interest. I would like to stick to the paragraph > > > highlighted >> below for the short term, because Ukraine crisis > > > happened. I feel an obligation to make this right. I've seen > > > 'MDrights' work on this list before. > > > > > > so let's see what we can come up with together, eventually. > > > > > > > > > > Although I do not have the same experience as you Markus but I am > > > > keen to learn. > > > > > > We all started at some point. Kudos for starting in the first place. > > > > > > Mabye SBo manages to evolve to the point that there can be a team > > > of maintainers for a given application. IMHO such an approach would > > > need 'release signing keys' like so many other projects use. > > > > > > Not talking about how, or how fast one could get onto the team, it's > > > about trust within the team. a working team is the goal. the team > > > shall be resiliant. > > > > > > I was just thinking out loud... > > > > > > We'll see. There's time. > > > > > > > > > > > > > On Wed, Mar 16, 2022 at 5:00 PM Markus Reichelt via > > > > SlackBuilds-users wrote: > > > > > > > > > * MDrights wrote: > > > > > > > > > > > Tor is not taken up by anyone yet, right? > > > > > > I will take it. > > > > > > > > > > I know this thread is old, but: [...] > > > > > > > > >>> > If not, I'll keep holding up the torch. Let's return to giving > > > >>> > (potentially new) maintainers that fancy 2 weeks grace period. > > > >>> > We haven't heard from you back by April, then we know. > > Since MDrights was the first to say he'd take it I've added him as > new maintainer in my branch. > > Thanks > > -- > Dave > _______________________________________________ > 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 b.pribs11 at gmail.com Sat Mar 19 19:11:36 2022 From: b.pribs11 at gmail.com (Brandon Pribula) Date: Sat, 19 Mar 2022 12:11:36 -0700 Subject: [Slackbuilds-users] Creating First Slackbuilds and Github In-Reply-To: References: <87v8waedi4.fsf@gmail.com> Message-ID: Thanks for your reply, Pritvi :) I've read the submissions page before and maybe it's just me but I didn't see my question answered on there? On Sat, Mar 19, 2022 at 5:09 AM Jheengut Pritvi wrote: > Hi Brandon, > > You should consult this page first https://slackbuilds.org/guidelines/. > > If you have trouble , you can continue on this thread. > > Enjoy a good day > > > Pritvi Jheengut > > On Sat, 19 Mar 2022 at 09:08, Brandon Pribula wrote: > >> Hi, >> >> I'm new to creating SlackBuilds and using github so I apologize if this >> is obvious. >> >> I'm in the process of putting my first SlackBuilds together. The repos >> are on github. The first repo has archived releases but I would like to use >> master up to the most recent commit. >> And the second repo only has a master and no archived releases. >> >> I'm curious what the policy is regarding slackbuilds.org hosting >> tarballs? >> >> Thanks >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.pribs11 at gmail.com Sat Mar 19 19:22:19 2022 From: b.pribs11 at gmail.com (Brandon Pribula) Date: Sat, 19 Mar 2022 12:22:19 -0700 Subject: [Slackbuilds-users] Creating First Slackbuilds and Github In-Reply-To: <20220319150812.6b876a5a@kiwi.kuchen> References: <87v8waedi4.fsf@gmail.com> <20220319150812.6b876a5a@kiwi.kuchen> Message-ID: Thanks for your reply, Ruben :) That's great! I can't believe I missed that before. When I download it I get: nameofpackage-1369d247e3d2bc697892795dea8cc1713344749f.zip Is the version of the package okay like this: nameofpackage-*1369d247e3d2bc697892795dea8cc1713344749f*-noarch-1_SBo Thanks again On Sat, Mar 19, 2022 at 7:08 AM Ruben Schuller wrote: > Hi, > > 2022-03-18 Brandon Pribula : > > > I'm in the process of putting my first SlackBuilds together. The > > repos are on github. The first repo has archived releases but I would > > like to use master up to the most recent commit. And the second repo > > only has a master and no archived releases. > > I'd just use the link to the archive (zip) at a certain commit of your > choice. > > > I'm curious what the policy is regarding slackbuilds.org hosting > > tarballs? > > SBo doesn't host source tarballs :) > > Cheers > Ruben > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sb at rbn.im Sat Mar 19 21:06:51 2022 From: sb at rbn.im (Ruben Schuller) Date: Sat, 19 Mar 2022 22:06:51 +0100 Subject: [Slackbuilds-users] Creating First Slackbuilds and Github In-Reply-To: References: <87v8waedi4.fsf@gmail.com> <20220319150812.6b876a5a@kiwi.kuchen> Message-ID: <20220319220651.5ed47ae5@kiwi.kuchen> Hi, 2022-03-19 Brandon Pribula : > Thanks for your reply, Ruben :) That's great! I can't believe I > missed that before. When I download it I get: > > nameofpackage-1369d247e3d2bc697892795dea8cc1713344749f.zip > > Is the version of the package okay like this: > > nameofpackage-*1369d247e3d2bc697892795dea8cc1713344749f*-noarch-1_SBo You'll definitively need this version to extract the zip archive, but you can store this in another variable in your slackbuild like ZIPVER="1369d247e3d2bc697892795dea8cc1713344749f" for the version I'd either go with the date like 220319 if there aren't multiple commits on that date, or with the short-hash of git: git rev-parse --short 1369d247e3d2bc697892795dea8cc1713344749f (you need to clone the git repository and execute this). You also find the short hash in the github UI, but it's hard to explain in a mail :) Cheers Ruben From b.pribs11 at gmail.com Sun Mar 20 00:27:57 2022 From: b.pribs11 at gmail.com (Brandon Pribula) Date: Sat, 19 Mar 2022 17:27:57 -0700 Subject: [Slackbuilds-users] Creating First Slackbuilds and Github In-Reply-To: <20220319220651.5ed47ae5@kiwi.kuchen> References: <87v8waedi4.fsf@gmail.com> <20220319150812.6b876a5a@kiwi.kuchen> <20220319220651.5ed47ae5@kiwi.kuchen> Message-ID: Thanks again, Ruben! I already had a slackbuild packaged for the latest release version. So I followed your instructions and applied the necessary changes and tested it and it all works. Here's how I did it: VERSION=${VERSION:-1369d24} TARVERSION=${TARVERSION:-1369d247e3d2bc697892795dea8cc1713344749f} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} PKGTYPE=${PKGTYPE:-tgz} ARCH="noarch" rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $PRGNAM-$VERSION tar xvf $CWD/$PRGNAM-$TARVERSION.tar.gz && mv $PRGNAM-$TARVERSION $PRGNAM-$VERSION cd $PRGNAM-$VERSION chown -R root:root . On Sat, Mar 19, 2022 at 2:07 PM Ruben Schuller wrote: > Hi, > > 2022-03-19 Brandon Pribula : > > > Thanks for your reply, Ruben :) That's great! I can't believe I > > missed that before. When I download it I get: > > > > nameofpackage-1369d247e3d2bc697892795dea8cc1713344749f.zip > > > > Is the version of the package okay like this: > > > > nameofpackage-*1369d247e3d2bc697892795dea8cc1713344749f*-noarch-1_SBo > > You'll definitively need this version to extract the zip archive, but > you can store this in another variable in your slackbuild like > > ZIPVER="1369d247e3d2bc697892795dea8cc1713344749f" > > for the version I'd either go with the date like 220319 if there aren't > multiple commits on that date, or with the short-hash of git: > > git rev-parse --short 1369d247e3d2bc697892795dea8cc1713344749f > > (you need to clone the git repository and execute this). You also > find the short hash in the github UI, but it's hard to explain in a > mail :) > > Cheers > Ruben > > > _______________________________________________ > 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 dchmelik at gmail.com Sun Mar 20 07:46:55 2022 From: dchmelik at gmail.com (David Chmelik) Date: Sun, 20 Mar 2022 00:46:55 -0700 Subject: [Slackbuilds-users] numpy builds w/problems Message-ID: <8b1c94d8-2a6f-cc05-dfe7-58ac9b0f9d3a@gmail.com> Some days/weeks ago I mentioned a build not working on Slackware64 15.1+current and Urchlay said we're not worrying about SBo-git until 15 is ready (ready now except submissions I guess) so I resorted to report another SBo-git problem on LinuxQuestions.com (LQ) then ponce said post here... ??? Built numpy3-1.21.2-x86_64-1ponce but some/most/all packages depending on it don't build right. One I maintain, mathics.SlackBuild (updated for Slackware 15 at http://davidchmelik.com/math/slackbuilds/academic/mathics.tar.gz but not updated on SBo[-git] yet) which I reported on http://GitHub.com/mathics who said I have a broken numpy... despite that built, something went wrong. I don't recall what others didn't build but don't need any these urgently unless anyone needs Slackware-current Mathics 4... ??? Mathics 4 builds but crashes on run... d at cosmos:~$ mathics Traceback (most recent call last): ? File "/usr/lib64/python3.9/site-packages/numpy/core/__init__.py", line 22, in ??? from . import multiarray ? File "/usr/lib64/python3.9/site-packages/numpy/core/multiarray.py", line 12, in ??? from . import overrides ? File "/usr/lib64/python3.9/site-packages/numpy/core/overrides.py", line 7, in ??? from numpy.core._multiarray_umath import ( ImportError: libopenblas.so.0: cannot open shared object file: No such file or directory During handling of the above exception, another exception occurred: Traceback (most recent call last): ? File "/usr/bin/mathics", line 33, in ??? sys.exit(load_entry_point('Mathics3==4.0.0', 'console_scripts', 'mathics')()) ? File "/usr/bin/mathics", line 25, in importlib_load_entry_point ??? return next(matches).load() ? File "/usr/lib64/python3.9/importlib/metadata.py", line 77, in load ??? module = import_module(match.group('module')) ? File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in import_module ??? return _bootstrap._gcd_import(name[level:], package, level) ? File "", line 1030, in _gcd_import ? File "", line 1007, in _find_and_load ? File "", line 972, in _find_and_load_unlocked ? File "", line 228, in _call_with_frames_removed ? File "", line 1030, in _gcd_import ? File "", line 1007, in _find_and_load ? File "", line 986, in _find_and_load_unlocked ? File "", line 680, in _load_unlocked ? File "", line 850, in exec_module ? File "", line 228, in _call_with_frames_removed ? File "/usr/lib64/python3.9/site-packages/mathics/__init__.py", line 8, in ??? import numpy ? File "/usr/lib64/python3.9/site-packages/numpy/__init__.py", line 150, in ??? from . import core ? File "/usr/lib64/python3.9/site-packages/numpy/core/__init__.py", line 48, in ??? raise ImportError(msg) ImportError: IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE! Importing the numpy C-extensions failed. This error can happen for many reasons, often due to issues with your setup or how NumPy was installed. We have compiled some common reasons and troubleshooting tips at: https://numpy.org/devdocs/user/troubleshooting-importerror.html Please note and check the following: ? * The Python version is: Python3.9 from "/usr/bin/python3" ? * The NumPy version is: "1.21.2" and make sure that they are the versions you expect. Please carefully study the documentation linked above for further help. Original error was: libopenblas.so.0: cannot open shared object file: No such file or directory From matteo.bernardini at gmail.com Sun Mar 20 07:51:36 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 20 Mar 2022 08:51:36 +0100 Subject: [Slackbuilds-users] numpy builds w/problems In-Reply-To: <8b1c94d8-2a6f-cc05-dfe7-58ac9b0f9d3a@gmail.com> References: <8b1c94d8-2a6f-cc05-dfe7-58ac9b0f9d3a@gmail.com> Message-ID: maybe you just built numpy3 against OpenBLAS and then removed OpenBLAS from your system? Matteo Il giorno dom 20 mar 2022 alle ore 08:47 David Chmelik ha scritto: > Some days/weeks ago I mentioned a build not working on Slackware64 > 15.1+current and Urchlay said we're not worrying about SBo-git until 15 > is ready (ready now except submissions I guess) so I resorted to report > another SBo-git problem on LinuxQuestions.com (LQ) then ponce said post > here... > Built numpy3-1.21.2-x86_64-1ponce but some/most/all packages > depending on it don't build right. One I maintain, mathics.SlackBuild > (updated for Slackware 15 at > http://davidchmelik.com/math/slackbuilds/academic/mathics.tar.gz but not > updated on SBo[-git] yet) which I reported on http://GitHub.com/mathics > who said I have a broken numpy... despite that built, something went > wrong. I don't recall what others didn't build but don't need any these > urgently unless anyone needs Slackware-current Mathics 4... > Mathics 4 builds but crashes on run... > > d at cosmos:~$ mathics > Traceback (most recent call last): > File "/usr/lib64/python3.9/site-packages/numpy/core/__init__.py", > line 22, in > from . import multiarray > File "/usr/lib64/python3.9/site-packages/numpy/core/multiarray.py", > line 12, in > from . import overrides > File "/usr/lib64/python3.9/site-packages/numpy/core/overrides.py", > line 7, in > from numpy.core._multiarray_umath import ( > ImportError: libopenblas.so.0: cannot open shared object file: No such > file or directory > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/bin/mathics", line 33, in > sys.exit(load_entry_point('Mathics3==4.0.0', 'console_scripts', > 'mathics')()) > File "/usr/bin/mathics", line 25, in importlib_load_entry_point > return next(matches).load() > File "/usr/lib64/python3.9/importlib/metadata.py", line 77, in load > module = import_module(match.group('module')) > File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in > import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "", line 1030, in _gcd_import > File "", line 1007, in _find_and_load > File "", line 972, in > _find_and_load_unlocked > File "", line 228, in > _call_with_frames_removed > File "", line 1030, in _gcd_import > File "", line 1007, in _find_and_load > File "", line 986, in > _find_and_load_unlocked > File "", line 680, in _load_unlocked > File "", line 850, in exec_module > File "", line 228, in > _call_with_frames_removed > File "/usr/lib64/python3.9/site-packages/mathics/__init__.py", line > 8, in > import numpy > File "/usr/lib64/python3.9/site-packages/numpy/__init__.py", line > 150, in > from . import core > File "/usr/lib64/python3.9/site-packages/numpy/core/__init__.py", > line 48, in > raise ImportError(msg) > ImportError: > > IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE! > > Importing the numpy C-extensions failed. This error can happen for > many reasons, often due to issues with your setup or how NumPy was > installed. > > We have compiled some common reasons and troubleshooting tips at: > > https://numpy.org/devdocs/user/troubleshooting-importerror.html > > Please note and check the following: > > * The Python version is: Python3.9 from "/usr/bin/python3" > * The NumPy version is: "1.21.2" > > and make sure that they are the versions you expect. > Please carefully study the documentation linked above for further help. > > Original error was: libopenblas.so.0: cannot open shared object file: No > such file or directory > > > _______________________________________________ > 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 dchmelik at gmail.com Sun Mar 20 08:07:16 2022 From: dchmelik at gmail.com (David Chmelik) Date: Sun, 20 Mar 2022 01:07:16 -0700 Subject: [Slackbuilds-users] numpy builds w/problems In-Reply-To: References: <8b1c94d8-2a6f-cc05-dfe7-58ac9b0f9d3a@gmail.com> Message-ID: Apparently; I reinstalled saved packages: now mathics 4 works on Slackware64 15.1+current w/earlier numpy & OpenBLAS.? However beforehand I removed numpy3 and now was trying to rebuild because no longer could: something else happens with that which I'm waiting on another attempt to save output to a TXT... On 3/20/22 12:51 AM, Matteo Bernardini wrote: > maybe you just built numpy3 against OpenBLAS and then removed OpenBLAS > from your system? > > Matteo > > Il giorno dom 20 mar 2022 alle ore 08:47 David Chmelik > > ha scritto: > > Some days/weeks ago I mentioned a build not working on Slackware64 > 15.1+current and Urchlay said we're not worrying about SBo-git > until 15 > is ready (ready now except submissions I guess) so I resorted to > report > another SBo-git problem on LinuxQuestions.com (LQ) then ponce said > post > here... > ???? Built numpy3-1.21.2-x86_64-1ponce but some/most/all packages > depending on it don't build right. One I maintain, mathics.SlackBuild > (updated for Slackware 15 at > http://davidchmelik.com/math/slackbuilds/academic/mathics.tar.gz > > but not > updated on SBo[-git] yet) which I reported on > http://GitHub.com/mathics > who said I have a broken numpy... despite that built, something went > wrong. I don't recall what others didn't build but don't need any > these > urgently unless anyone needs Slackware-current Mathics 4... > ???? Mathics 4 builds but crashes on run... > > d at cosmos:~$ mathics > Traceback (most recent call last): > ?? File "/usr/lib64/python3.9/site-packages/numpy/core/__init__.py", > line 22, in > ???? from . import multiarray > ?? File > "/usr/lib64/python3.9/site-packages/numpy/core/multiarray.py", > line 12, in > ???? from . import overrides > ?? File "/usr/lib64/python3.9/site-packages/numpy/core/overrides.py", > line 7, in > ???? from numpy.core._multiarray_umath import ( > ImportError: libopenblas.so.0: cannot open shared object file: No > such > file or directory > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > ?? File "/usr/bin/mathics", line 33, in > ???? sys.exit(load_entry_point('Mathics3==4.0.0', 'console_scripts', > 'mathics')()) > ?? File "/usr/bin/mathics", line 25, in importlib_load_entry_point > ???? return next(matches).load() > ?? File "/usr/lib64/python3.9/importlib/metadata.py", line 77, in load > ???? module = import_module(match.group('module')) > ?? File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in > import_module > ???? return _bootstrap._gcd_import(name[level:], package, level) > ?? File "", line 1030, in _gcd_import > ?? File "", line 1007, in _find_and_load > ?? File "", line 972, in > _find_and_load_unlocked > ?? File "", line 228, in > _call_with_frames_removed > ?? File "", line 1030, in _gcd_import > ?? File "", line 1007, in _find_and_load > ?? File "", line 986, in > _find_and_load_unlocked > ?? File "", line 680, in _load_unlocked > ?? File "", line 850, in > exec_module > ?? File "", line 228, in > _call_with_frames_removed > ?? File "/usr/lib64/python3.9/site-packages/mathics/__init__.py", > line > 8, in > ???? import numpy > ?? File "/usr/lib64/python3.9/site-packages/numpy/__init__.py", line > 150, in > ???? from . import core > ?? File "/usr/lib64/python3.9/site-packages/numpy/core/__init__.py", > line 48, in > ???? raise ImportError(msg) > ImportError: > > IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE! > > Importing the numpy C-extensions failed. This error can happen for > many reasons, often due to issues with your setup or how NumPy was > installed. > > We have compiled some common reasons and troubleshooting tips at: > > https://numpy.org/devdocs/user/troubleshooting-importerror.html > > > Please note and check the following: > > ?? * The Python version is: Python3.9 from "/usr/bin/python3" > ?? * The NumPy version is: "1.21.2" > > and make sure that they are the versions you expect. > Please carefully study the documentation linked above for further > help. > > Original error was: libopenblas.so.0: cannot open shared object > file: No > such file or directory > > > _______________________________________________ > 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 matteo.bernardini at gmail.com Sun Mar 20 08:25:45 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 20 Mar 2022 09:25:45 +0100 Subject: [Slackbuilds-users] numpy builds w/problems In-Reply-To: References: <8b1c94d8-2a6f-cc05-dfe7-58ac9b0f9d3a@gmail.com> Message-ID: before reporting issues you should build the problematic packages from scratch, together with all their dependencies, on a clean and full installation (no other third party packages or customizations): I suggest you to use virtual machines for the task (that's what most people do). Matteo Il giorno dom 20 mar 2022 alle ore 09:07 David Chmelik ha scritto: > Apparently; I reinstalled saved packages: now mathics 4 works on > Slackware64 15.1+current w/earlier numpy & OpenBLAS. However beforehand > I removed numpy3 and now was trying to rebuild because no longer could: > something else happens with that which I'm waiting on another attempt to > save output to a TXT... > > On 3/20/22 12:51 AM, Matteo Bernardini wrote: > > maybe you just built numpy3 against OpenBLAS and then removed OpenBLAS > > from your system? > > > > Matteo > > > > Il giorno dom 20 mar 2022 alle ore 08:47 David Chmelik > > > ha scritto: > > > > Some days/weeks ago I mentioned a build not working on Slackware64 > > 15.1+current and Urchlay said we're not worrying about SBo-git > > until 15 > > is ready (ready now except submissions I guess) so I resorted to > > report > > another SBo-git problem on LinuxQuestions.com (LQ) then ponce said > > post > > here... > > Built numpy3-1.21.2-x86_64-1ponce but some/most/all packages > > depending on it don't build right. One I maintain, mathics.SlackBuild > > (updated for Slackware 15 at > > http://davidchmelik.com/math/slackbuilds/academic/mathics.tar.gz > > > > but not > > updated on SBo[-git] yet) which I reported on > > http://GitHub.com/mathics > > who said I have a broken numpy... despite that built, something went > > wrong. I don't recall what others didn't build but don't need any > > these > > urgently unless anyone needs Slackware-current Mathics 4... > > Mathics 4 builds but crashes on run... > > > > d at cosmos:~$ mathics > > Traceback (most recent call last): > > File "/usr/lib64/python3.9/site-packages/numpy/core/__init__.py", > > line 22, in > > from . import multiarray > > File > > "/usr/lib64/python3.9/site-packages/numpy/core/multiarray.py", > > line 12, in > > from . import overrides > > File "/usr/lib64/python3.9/site-packages/numpy/core/overrides.py", > > line 7, in > > from numpy.core._multiarray_umath import ( > > ImportError: libopenblas.so.0: cannot open shared object file: No > > such > > file or directory > > > > During handling of the above exception, another exception occurred: > > > > Traceback (most recent call last): > > File "/usr/bin/mathics", line 33, in > > sys.exit(load_entry_point('Mathics3==4.0.0', 'console_scripts', > > 'mathics')()) > > File "/usr/bin/mathics", line 25, in importlib_load_entry_point > > return next(matches).load() > > File "/usr/lib64/python3.9/importlib/metadata.py", line 77, in > load > > module = import_module(match.group('module')) > > File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in > > import_module > > return _bootstrap._gcd_import(name[level:], package, level) > > File "", line 1030, in _gcd_import > > File "", line 1007, in _find_and_load > > File "", line 972, in > > _find_and_load_unlocked > > File "", line 228, in > > _call_with_frames_removed > > File "", line 1030, in _gcd_import > > File "", line 1007, in _find_and_load > > File "", line 986, in > > _find_and_load_unlocked > > File "", line 680, in _load_unlocked > > File "", line 850, in > > exec_module > > File "", line 228, in > > _call_with_frames_removed > > File "/usr/lib64/python3.9/site-packages/mathics/__init__.py", > > line > > 8, in > > import numpy > > File "/usr/lib64/python3.9/site-packages/numpy/__init__.py", line > > 150, in > > from . import core > > File "/usr/lib64/python3.9/site-packages/numpy/core/__init__.py", > > line 48, in > > raise ImportError(msg) > > ImportError: > > > > IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE! > > > > Importing the numpy C-extensions failed. This error can happen for > > many reasons, often due to issues with your setup or how NumPy was > > installed. > > > > We have compiled some common reasons and troubleshooting tips at: > > > > https://numpy.org/devdocs/user/troubleshooting-importerror.html > > > > > > Please note and check the following: > > > > * The Python version is: Python3.9 from "/usr/bin/python3" > > * The NumPy version is: "1.21.2" > > > > and make sure that they are the versions you expect. > > Please carefully study the documentation linked above for further > > help. > > > > Original error was: libopenblas.so.0: cannot open shared object > > file: No > > such file or directory > > > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > > Archives - > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > > > FAQ - https://slackbuilds.org/faq/ > > > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From psychi2009 at gmail.com Sun Mar 20 08:43:51 2022 From: psychi2009 at gmail.com (MDrights) Date: Sun, 20 Mar 2022 08:43:51 +0000 Subject: [Slackbuilds-users] Updated list of builds that were removed for 15.0 In-Reply-To: References: Message-ID: Hi, I suddenly found that network/riot-web was not removed. I was the maintainer of it but once announced the giving-up. Actually riot-web was renamed to element.io and seemingly most users are using web version. So this slackbuild can be removed otherwise someone would like to take over it. :) Cheers MDrights On Tue, Mar 15, 2022 at 11:56:19PM -0400, B Watson wrote: > Since the list I posted before had some stuff that wasn't really > removed, here's a corrected version. > > https://slackware.uk/~urchlay/src/sbo-removed-for-15.0.txt > > Some of these wouldn't be hard to get building on 15.0. I just > re-added games/rejoystick, it needed a minor tweak to its configure > command (LIBS="-lX11"). Some of them are never going to happen, > e.g. KDE4 apps. > > Rest of this mail is the list (same as the URL above). > > academic/Mnemosyne: Removed (requires nonexistent PyQtWebEngine dep). > academic/QtiPlot: Removed. > academic/Xyce: Removed (ftb). > academic/abella: Removed (ftb). > academic/avogadro: Removed. > academic/bpp-core: Removed (ftb + no active maintainer). > academic/bpp-phyl-omics: Removed (ftb + no active maintainer). > academic/bpp-phyl: Removed (ftb + no active maintainer). > academic/bpp-popgen: Removed (ftb + no active maintainer). > academic/bpp-seq-omics: Removed (ftb + no active maintainer). > academic/bpp-seq: Removed (ftb + no active maintainer). > academic/bpp1.9-numcalc: Removed (ftb + no active maintainer). > academic/bpp1.9-phyl: Removed (ftb + no active maintainer). > academic/bpp1.9-seq: Removed (ftb + no active maintainer). > academic/bpp1.9-utils: Removed (ftb + no active maintainer). > academic/bppsuite: Removed (ftb + no active maintainer). > academic/coq: Removed (ftb). > academic/drawtiming: Removed (incompatible with the newer gcc). > academic/flashqard: Removed (no qt4-webkit available). > academic/gcompris: Removed. > academic/prank-msa: Removed (ftb + no active maintainer). > academic/treerecs: Removed (ftb + no active maintainer). > academic/vCAPS_coevolution: Removed (ftb + no active maintainer). > audio/Pd-extended: Removed (ftbfs) > audio/cuberok: Removed (unmaintained, qt4). > audio/lastfm: Removed (because libraries/lastfm was removed). > audio/llcon: Removed (abandoned, ftbfs). > audio/spandsp: Removed (roger-router is removed). > business/AssociationSubscribersManager: Removed (abandoned, ftbfs). > business/lemonpos: Removed (requires KDE4). > desktop/cairo-compmgr: Removed. > desktop/crystal: Removed (no more kde4). > desktop/gtk-kde4: Removed (no more kde4). > desktop/homerun: Removed (no more kde4). > desktop/kcometen4: Removed (no more kde4). > desktop/kover: Removed (no more kde4). > desktop/plasma-adjustable-clock: Removed (no more kde4). > desktop/plasma-applet-daisy: Removed (no more kde4). > desktop/plasma-eyasdp: Removed (no more kde4). > desktop/plasma-geek-clock: Removed (no more kde4). > desktop/plasma-widget-menubar: Removed (abandonded ftbfs). > desktop/ptbatterysystemtray: Removed (abandoned upstream). > desktop/qt-recordmydesktop: Removed (needs PyQt4). > desktop/qtcurve: Removed (no more kde4). > desktop/quadkonsole4: Removed (no more kde4). > desktop/quickaccess: Removed (no more kde4). > desktop/recorditnow: Removed (no more kde4). > desktop/screensaver-icon: Removed (source does not exist). > desktop/simon: Removed (no more kde4). > desktop/simplenote: Removed (abandoned by SBo maintainer) > desktop/vertex-maia-themes: Removed. > desktop/vivacious-colors-gtk-icon-theme: Removed (does not work well > with xfce 4.16) > desktop/vivacious-colors-gtk-theme: Removed (does not work well with xfce 4.16) > desktop/xfce4-embed-plugin: Removed (no more libxfce4ui-1). > desktop/yawp: Removed (no more kde4). > development/JSONObject: Removed (incompatible with the newer boost). > development/adoptopenjdk-openj9: Removed (EOL). > development/adoptopenjdk: Removed (EOL). > development/ahven: Removed (needs gprbuild). > development/atom: Removed (no maintainer). > development/bacon: Removed (no maintainer). > development/couchdb: Removed (ftb, no maintainer). > development/eric: Removed (needs PyQt4). > development/flow: Removed (ftb). > development/fsharp: Removed (abandoned). > development/gcclegacy494: Removed (FTB). > development/jdk12: Removed (EOL). > development/jdk13: Removed (EOL). > development/jdk14: Removed (EOL). > development/jdk15: Removed (EOL). > development/jdk16: Removed (EOL). > development/jupyter-ipyleaflet: Removed (abandoned). > development/jupyter-ipywidgets: Removed (abandoned). > development/jupyter-nbdime: Removed (abandoned). > development/jupyter-widgetsnbextension: Removed (abandoned). > development/libbitcoin: Removed (incompat boost 1.78). > development/libodb-boost: Removed (abandoned). > development/libodb-mysql: Removed (abandoned). > development/libodb-pgsql: Removed (abandoned). > development/libodb-qt: Removed (abandoned). > development/libodb-sqlite: Removed (abandoned). > development/libodb: Removed (abandoned). > development/monkey-studio: Removed (no qt4-qscintilla). > development/mono-debugger: Removed (abandoned and ftb). > development/monodevelop: Removed (abandoned). > development/mrustc: Removed (rust now in slackware). > development/nuget: Removed (abandoned). > development/numpy-legacy3: Removed (ftb). > development/odb: Removed (abandoned). > development/qt-creator2: Removed (abandoned). > development/referenceassemblies-pcl: Removed (abandoned). > development/sourcenav: Removed. > development/swift: Removed (abandoned, ftbfs). > development/xemacs: Removed (unmaintained @ SBo) > games/chocolate_duke3D: Removed (broken and abandoned). > games/ember: Removed (not compatible with latest OGRE). > games/etlegacy-from-source: Removed (use the binary). > games/gens-gs: Removed (no maintainer). > games/glPortal: Removed (will not build against bullet 3.x, ran out of > patience). > games/qtsixa: Removed (FTBFS, unmaintained, replace someday with "sixad"). > games/sumwars: Removed (ftbfs). > gis/CreateCloudMap: Removed (Service is shut down). > gis/spatialite_gui: Removed. > graphics/freewrl: Removed (no maintainer, ftbfs). > graphics/k3d: Removed (FTBFS). > graphics/kamerka: Removed (KDE4 app, untouched since 2014). > graphics/mitsuba-blender: Removed (ftbfs). > graphics/mitsuba: Removed (ftbfs). > graphics/mlbrot: Removed (ftb). > graphics/rawstudio: Removed (FTBFS). > graphics/separate+: Removed (crashed at runtime). > graphics/teighaviewer: Removed (outdated binary-only software). > graphics/yesplz: Removed (No longer maintained). > ham/linlogbook: Removed. > ham/qradiopredict: Removed. > haskell/haskell-cabal-install: Removed (ftbfs, unmaintained). > haskell/haskell-exceptions: Removed (part of ghc). > haskell/haskell-hackage-security: Removed (ftbfs, unmaintained). > haskell/haskell-hashed-storage: Removed (ftbfs, unmaintained). > haskell/haskell-haskell-src: Removed (ftbfs, unmaintained). > haskell/haskell-hslogger: Removed (ftbfs, unmaintained). > haskell/haskell-http-api-data: Removed (ftbfs, unmaintained). > haskell/haskell-megaparsec: Removed (ftbfs, no maintainer). > haskell/haskell-mustache: Removed (ftbfs, no maintainer). > haskell/haskell-neat-interpolation: Removed (ftbfs, no maintainer). > haskell/haskell-optparse-simple: Removed (ftbfs, unmaintained). > haskell/haskell-parallel: Removed (ftbfs, unmaintained). > haskell/haskell-persistent-sqlite: Removed (ftbfs, unmaintained). > haskell/haskell-persistent-template: Removed (ftbfs, unmaintained). > haskell/haskell-persistent: Removed (ftbfs, unmaintained). > haskell/haskell-stack: Removed (ftbfs, unmaintained). > haskell/haskell-store: Removed (ftbfs, unmaintained). > kildclient: Version updated. Added new dependency for gtkspell3. > Removed perl-JSON dependency. > libraries/DirectFB: Removed (old age, lack of use). > libraries/GtkD: Removed (not used by any slackbuild) > libraries/PyQwt: Removed (needs PyQt4). > libraries/appmenu-qt: Removed (orphaned - qt4 + ftbfs). > libraries/atlas: Removed (use OpenBLAS). > libraries/beignet: Removed (incompatible with the newer llvm). > libraries/cppo: Removed (ftb). > libraries/db46: Removed (not needed, and conflicts with Slack db48) > libraries/dbus-sharp-glib: Removed (dbus-sharp ftbfs) > libraries/dbus-sharp: Removed (ftbfs) > libraries/folly: Removed (orphaned and FTB). > libraries/gazebo: Removed (no qt4-webkit available). > libraries/glfw: Removed (no dependees, conflicts with glfw3). > libraries/gstreamer-editing-services: Removed. > libraries/gtk-qt-engine: Removed (abandoned ftbfs). > libraries/hinnant-date: Removed (included in sqlpp11). > libraries/hpx: Removed (orphaned and FTB). > libraries/hug: Removed (no maintainer). > libraries/lapack-atlas: Removed (Along with atlas). > libraries/libgaiagraphics: Removed (obsoleted upstream). > libraries/libido3: Removed. > libraries/libquvi-scripts: Removed. > libraries/libquvi: Removed (Not needed as cclive is removed). > libraries/libsunpinyin: Removed (no maintainer). > libraries/libtorrent-rasterbar-legacy: Removed. > libraries/libtunepimp: Removed (ftbfs) > libraries/mariadb_client: Removed (substituted by connector, FTB). > libraries/ocaml-bisect: Removed (ftb). > libraries/ocaml-ounit: Removed (ftb). > libraries/opal: Removed. > libraries/opencv-legacy: Removed (not compatible with opencv). > libraries/pgplot: Removed (abandoned upstream and FTB). > libraries/php-mssql: Removed (no more mssql ext in php 7.4.x). > libraries/proxygen: Removed (orphaned and FTB). > libraries/ptlib: Removed. > libraries/qwt-qt5: Removed (redundant; use qwt). > libraries/qwtpolar: Removed (FTBFS, and no dependees). > libraries/ring-daemon: Removed (superseded by jami). > libraries/ring-lrc: Removed (superseded by jami). > libraries/sqlpp11-connector-mysql: Removed (included in sqlpp11). > libraries/sqlpp11-connector-sqlite3: Removed (included in sqlpp11). > libraries/t38modem-opal: Removed (missing dependency). > libraries/t38modem-ptlib: Removed (incompatible with openssl-1.1.x). > libraries/trilinos: Removed (no dependees; conflicts with mpich and openmpi) > libraries/upscaledb: Removed (orphaned and FTB). > libraries/vdpau-video: Removed (obsolete, abandoned upstream, FTB). > libraries/vte3-ng: Removed (conflicts with vte in Slackware). > libraries/wangle: Removed (orphaned and FTB). > misc/Publican: Removed (missing perl dependencies). > misc/fribid: Removed (not compatible with openssl-1.1.x). > misc/hashkill: Removed (not compatible with openssl-1.1.x). > misc/igal2: Removed (ftp + no active maintainer) > misc/protobuf: Removed (use protobuf3 instead). > misc/readesm: Removed (no qt4-webkit available). > misc/scim-chewing: Removed (no scim in Slackware anymore). > multimedia/OpenPHT: Removed (superseded by plex media player and plex htpc) > multimedia/freshplayerplugin: Removed. > multimedia/gecko-mediaplayer: Removed. > multimedia/gst-plugins-bad: Removed (conflict w/Slackware gst-plugins-bad-free). > multimedia/lwks: Removed (membership and licensing changes). > multimedia/mythplugins: Removed (ftb + no active maintainer) > multimedia/mythtv: Removed (ftb + no active maintainer) > multimedia/pepperflash-plugin: Removed. > multimedia/plex-home-theater: Removed (ftbs, upstream dead). > multimedia/simpleburn: Removed (upstream is dead). > multimedia/subtitlecomposer: Removed (needs kde4). > multimedia/totem: Removed (no maintainer, ftbfs). > network/Icecat: Removed (unmaintained, ftbfs). > network/airpwn-ng: Removed > network/arora: Removed (unmaintained upstream). > network/base: Removed (ftp + no active maintainer) > network/basilisk: Removed (upstream development suspended). > network/bird: Removed (no maintainer). > network/cclive: Removed (Not building on 15.0). > network/corebird: Removed. > network/dbmail: Removed. > network/dclib: Removed. > network/dobbscoin: Removed. > network/dogecoin: Removed. > network/elemental-ircd: Removed. > network/emacs-w3m: Removed. > network/etcd: Removed. > network/ettercap-NG: Removed (incompatible with the newer openssl). > network/fwbuilder: Removed (ftb + no active maintainer) > network/ganglia-web: Removed. > network/ganglia: Removed. > network/gq: Removed. > network/greenbone-security-assistant: Removed. > network/gtmess: Removed. > network/guacamole-server: Removed freerdp dep (part of slackware). > network/guacamole-server: Removed. > network/hylafax: Removed (ftb + no active maintainer) > network/ike: Removed. > network/imapproxy: Removed. > network/iptv-analyzer: Removed. > network/kadu: Removed (unmaintained). > network/kcm_ufw: Removed. > network/kfilebox: Removed. > network/knemo: Removed. > network/kobby: Removed (no kde4 anymore). > network/libcapi20: Removed (roger-router is removed). > network/libinfinity: Removed (unused). > network/libqinfinity: Removed (unused). > network/lighttpd2: Removed (still too unripe). > network/linuxdcpp: Removed. > network/mldonkey: Removed. > network/ntop: Removed. > network/openl2tp: Removed. > network/openrdate: Removed. > network/openvas-manager: Removed. > network/pdnsd: Removed. > network/pgl: Removed (No maintainer). > network/pound: Removed. > network/qutebrowser-tox: Removed. > network/quvi: Removed (Not needed as cclive is removed). > network/rekonq: Removed (KDE4 app). > network/roger-router: Removed (source only for flatpak). > network/sks-keyserver: Removed. > network/slimjet: Removed (abandoned by SBo maintainer) > network/smuxi: Removed (dbus-sharp dep ftbfs) > network/squidGuard: Removed (upstream no longer maintained). > network/t38modem: Removed (missing dependency). > network/ucspi-ssl: Removed. > network/vacuum-im: Removed (no maintainer). > network/valknut: Removed. > network/verm: Removed (unused, no dependees). > network/wireguard-linux-compat: Removed (part of newer kernels). > office/focuswriter-legacy: Removed (use focuswriter instead). > office/fop-legacy: Removed (ftbfs) > office/hyphen-id: Removed (merged with hunspell-id). > office/kate-latex-plugin: Removed (KDE4 app; use kile instead). > office/kchmviewer: Removed (redundant; use kchmviewer-qt). > office/marave: Removed (PyQt4; unmaintained upstream since 2015) > office/teams-for-linux: Removed (Use official teams). > office/teapot: Removed (website and source are not available). > office/wyrd: Removed (ftbfs) > python/planes: Removed. > python/python-branca: Removed (abandoned). > python/python-poppler-qt4: Removed (needs poppler-qt4). > python/python2-blake2: Removed (unused, python2, ftbfs). > python/traittypes: Removed (abandoned). > system/bareos-client: Removed (orphaned, ftbfs). > system/bareos: Removed (orphaned, ftbfs). > system/elo-mt-usb: Removed (download is gone, we dont have the > hardware to test new versions). > system/flSynclient: Removed (no maintainer). > system/hebe: Removed (KDE4 app). > system/kcm_touchpad: Removed (KDE4 app). > system/kcollectd: Removed (KDE4 app). > system/kitchen-sync: Removed (unused, no dependees). > system/komparator4: Removed (KDE4 app). > system/kvpm: Removed (KDE4 app). > system/lxd: Removed (ftb, no maintainer). > system/multicorn: Removed (FTBFS, even with debian patches and/or latest git). > system/nvidia-legacy304-driver: Removed (unmaintained, ftbfs). > system/nvidia-legacy304-kernel: Removed (unmaintained, ftbfs). > system/oracle-xe: Removed (old version, not available for download). > system/packagekit: Removed. > system/python3-urwid: Removed. > system/qingy: Removed (old age, lack of use). > system/qingy_0.3_themepack: Removed (old age, lack of use). > system/spl-solaris: Removed (fails to build, unused). > system/suhosin: Removed (not compatible with newer PHP). > system/termite: Removed (obsoleted by alacritty). > system/tilix: Removed (ftbfs, no maintainer). > system/tpe-kmod: Removed (ftbfs, no upstream activity). > _______________________________________________ > 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 phalange at komputermatrix.com Sun Mar 20 13:14:40 2022 From: phalange at komputermatrix.com (Andrew Payne) Date: Sun, 20 Mar 2022 09:14:40 -0400 (EDT) Subject: [Slackbuilds-users] Nextcloud client In-Reply-To: <7fab3bd2c2c153c1d909c8d2673cc385@schoepfer.info> References: <7fab3bd2c2c153c1d909c8d2673cc385@schoepfer.info> Message-ID: My build is a PR on SBo github, but since I changed the name from client to desktop, willy said he's holding it until new submissions open. It's viewable there meanwhile. On Fri, 18 Mar 2022, Franzen via SlackBuilds-users wrote: >> I keep a current build of it, so I'd be willing to take over >> maintenance if no one objects. > > May i ask to send the build to me or this list? > Thanks! > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > From willysr at slackbuilds.org Sun Mar 20 14:07:19 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 20 Mar 2022 21:07:19 +0700 Subject: [Slackbuilds-users] Updates - 20220322.1 Message-ID: <2ef92927-1b8f-3bd5-8ab8-cc0a8f041c65@slackbuilds.org> Here's some more updates to fix more build failures on 32 bit architecture and some version bumps from maintainers who send their PR/MR. Sun Mar 20 13:46:41 UTC 2022 academic/cap3: Fix 32-bit build when ARCH set in environment. academic/karma: Allow ARCH=i586 in environment. academic/ncbi-rmblastn: Allow ARCH=i586 in environment. audio/tta++: Removed (redundant; use tta). desktop/libqtxdg: Updated for version 3.8.0. development/autogen: Fix 32-bit build. development/edb-debugger: Fix PKG assignment. development/frobtads: Fix 32-bit build. development/kforth: Fix build on 15.0. development/mysql-workbench: Fix 32-bit build. development/pforth: Fix 32-bit build. development/phantomjs: Fix 32-bit build. development/xvile: Do not write to /usr/lib during build. development/zope.interface: new maintainer, updated for version 5.4.0 games/dgen: Fix 32-bit build. games/gzdoom: Fix 32-bit build (require SSE2). games/odamex: Fix 32-bit build. games/zdoom: Fix 32-bit build. graphics/mozjpeg: Fix 32-bit build. graphics/screengrab: Updated for version 2.3.0. graphics/vuescan: Updated for version 9.7.81. libraries/lxqt-build-tools: Updated for version 0.10.0. libraries/qt3: Fix 32-bit build. misc/sbo-templates: Updated for version 1.3.3. network/avahi: Included several patches from Debian network/haproxy: Avoid specifying CFLAGS. network/libnfsidmap: Removed (included in Slackware). network/palemoon-bin: updated for version 30.0.0 network/palemoon: updated for version 30.0.0 network/tor: Updated for version 0.4.6.10 network/uudeview: Fix 32-bit build. perl/perl-MIME-Types: Updated for version 2.22. perl/perl-Math-BigInt-GMP: Updated for version 1.6010. perl/perl-Math-BigInt: Updated for version 1.999829. perl/perl-Math-GMPq: Updated for version 0.51. perl/perl-Math-GMPz: Updated for version 0.54. perl/perl-Math-Int128: Mark as unsupported on 32-bit (it really is). perl/perl-Math-MPC: Updated for version 1.15. perl/perl-Math-MPFR: Updated for version 4.21. perl/perl-Sidef: Updated for version 3.99. python/python2-automat: Fix MD5SUM. python/python2-twisted: reverted to version 17.9.0 python/python3-pythondialog: Updated for version 3.5.3. system/Iosevka-slab: Updated for version 15.0.2. system/capstone: Fix .pc file and 32-bit build. system/cnijfilter2: Fix permission. system/cnijfilter2: Updated for version 6.30.1. system/dosemu: Fix segfaults on 15.0 (use gcc5). system/hddtemp: Fix 32-bit build. system/ksh-openbsd: Use correct github URL. system/mediaextract: Fix 32-bit build. system/mksh: Allow tests to pass without controlling tty. system/scangearmp2: Updated for version 4.30.1. +--------------------------+ -- 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 urchlay at slackware.uk Sun Mar 20 17:06:48 2022 From: urchlay at slackware.uk (B. Watson) Date: Sun, 20 Mar 2022 13:06:48 -0400 (EDT) Subject: [Slackbuilds-users] Creating First Slackbuilds and Github In-Reply-To: <20220319220651.5ed47ae5@kiwi.kuchen> References: <87v8waedi4.fsf@gmail.com> <20220319150812.6b876a5a@kiwi.kuchen> <20220319220651.5ed47ae5@kiwi.kuchen> Message-ID: On Sat, 19 Mar 2022, Ruben Schuller wrote: > > ZIPVER="1369d247e3d2bc697892795dea8cc1713344749f" > > for the version I'd either go with the date like 220319 if there aren't > multiple commits on that date, or with the short-hash of git: Recommendations... in fact I'm begging you: if you're going to use a git commit, *please* include the date in YYMMDD format in your VERSION number. Example: VERSION="20220319+1369d24" Notice the 4-digit year comes first... the point of doing it this way is that a user can easily tell which version is newer, when looking at multiple packages. If you use only the git commit hash, those are effectively random, there's no sense of which is newest. The SlackBuild can split up the VERSION variable as needed. Also, while I'm thinking about it: VERSION *must* be a constant that can be overridden by the environment. Example: VERSION=${VERSION:-3.4.1} *Please* don't try to get clever and do stuff like: COMMIT=1369d247e3d2bc697892795dea8cc1713344749f VERSION="$( echo $COMMIT | head -c7 )" The reason for this is that we have scripts that check for consistency, and VERSION in the SlackBuild has to match VERSION in the .info file to pass the check. For the same reason, PRGNAM has to be a constant. Don't do stuff like this: SRCNAM="Blah" PRGNAM="python-$SRCNAM" I know it looks clever, but it doesn't actually accomplish anything useful, and it makes life harder for the admins. From dickson.tim at googlemail.com Sun Mar 20 18:29:43 2022 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sun, 20 Mar 2022 18:29:43 +0000 Subject: [Slackbuilds-users] qemu build issue Message-ID: <3a331878-1238-1f14-916a-296e09654dc0@googlemail.com> I am getting the following error when attempting to create qemu package. /usr/bin/qemu-keymap: error while loading shared libraries: libjemalloc.so.1: cannot open shared object file: No such file or directory /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there is a libjemalloc installed (part of slackware 15.0). It seems that the build script is looking for the wrong version of the lib. Ideally it would try libjemalloc.so and thus pick up whichever version was installed. Is there a quick fix. (if it involves a sim-link would that have to be done on target computers as well?) regards, Tim -- This email has been checked for viruses by AVG. https://www.avg.com From matteo.bernardini at gmail.com Sun Mar 20 18:31:50 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 20 Mar 2022 19:31:50 +0100 Subject: [Slackbuilds-users] qemu build issue In-Reply-To: <3a331878-1238-1f14-916a-296e09654dc0@googlemail.com> References: <3a331878-1238-1f14-916a-296e09654dc0@googlemail.com> Message-ID: have you tried removing the already installed qemu package first? Il giorno dom 20 mar 2022 alle ore 19:29 Tim Dickson via SlackBuilds-users < slackbuilds-users at slackbuilds.org> ha scritto: > I am getting the following error when attempting to create qemu package. > > /usr/bin/qemu-keymap: error while loading shared libraries: > libjemalloc.so.1: cannot open shared object file: No such file or directory > > /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there > is a libjemalloc installed (part of slackware 15.0). > It seems that the build script is looking for the wrong version of the > lib. Ideally it would try libjemalloc.so and thus pick up whichever > version was installed. > Is there a quick fix. (if it involves a sim-link would that have to be > done on target computers as well?) > regards, Tim > > > -- > This email has been checked for viruses by AVG. > https://www.avg.com > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Sun Mar 20 18:38:49 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 20 Mar 2022 18:38:49 +0000 Subject: [Slackbuilds-users] qemu build issue In-Reply-To: <3a331878-1238-1f14-916a-296e09654dc0@googlemail.com> References: <3a331878-1238-1f14-916a-296e09654dc0@googlemail.com> Message-ID: <20220320183849.GA12020@localhost> On 20/03/22 18:29, Tim Dickson via SlackBuilds-users put forth the proposition: > I am getting the following error when attempting to create qemu package. > /usr/bin/qemu-keymap: error while loading shared libraries: It looks like qemu was compiled against an older jemalloc and not jemalloc-3.6.0 in 15.0 > libjemalloc.so.1: cannot open shared object file: No such file or directory > /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there is a > libjemalloc installed (part of slackware 15.0). > It seems that the build script is looking for the wrong version of the lib. > Ideally it would try libjemalloc.so and thus pick up whichever version was > installed. > Is there a quick fix. (if it involves a sim-link would that have to be done > on target computers as well?) > regards, Tim > -- > This email has been checked for viruses by AVG. > https://www.avg.com -- Dave From dave at slackbuilds.org Sun Mar 20 18:43:32 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 20 Mar 2022 18:43:32 +0000 Subject: [Slackbuilds-users] qemu build issue In-Reply-To: <20220320183849.GA12020@localhost> References: <3a331878-1238-1f14-916a-296e09654dc0@googlemail.com> <20220320183849.GA12020@localhost> Message-ID: <20220320184332.GB12020@localhost> On 20/03/22 18:38, Dave Woodfall put forth the proposition: > On 20/03/22 18:29, > Tim Dickson via SlackBuilds-users put forth the proposition: > > I am getting the following error when attempting to create qemu package. > > /usr/bin/qemu-keymap: error while loading shared libraries: > It looks like qemu was compiled against an older jemalloc and not > jemalloc-3.6.0 in 15.0 jemalloc-5.2.1 :-) > > libjemalloc.so.1: cannot open shared object file: No such file or directory > > /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there is a > > libjemalloc installed (part of slackware 15.0). > > It seems that the build script is looking for the wrong version of the lib. > > Ideally it would try libjemalloc.so and thus pick up whichever version was > > installed. > > Is there a quick fix. (if it involves a sim-link would that have to be done > > on target computers as well?) > > regards, Tim > > -- > > This email has been checked for viruses by AVG. > > https://www.avg.com > -- > Dave -- Dave From sb at rbn.im Sun Mar 20 22:58:19 2022 From: sb at rbn.im (Ruben Schuller) Date: Sun, 20 Mar 2022 23:58:19 +0100 Subject: [Slackbuilds-users] Creating First Slackbuilds and Github In-Reply-To: References: <87v8waedi4.fsf@gmail.com> <20220319150812.6b876a5a@kiwi.kuchen> <20220319220651.5ed47ae5@kiwi.kuchen> Message-ID: <20220320235819.5fe9d824@kiwi.kuchen> Hi, 2022-03-20 "B. Watson" : > On Sat, 19 Mar 2022, Ruben Schuller wrote: > > > > ZIPVER="1369d247e3d2bc697892795dea8cc1713344749f" > > > > for the version I'd either go with the date like 220319 if there > > aren't multiple commits on that date, or with the short-hash of > > git: > > Recommendations... in fact I'm begging you: if you're going to use > a git commit, *please* include the date in YYMMDD format in your > VERSION number. Example: > > VERSION="20220319+1369d24" > > Notice the 4-digit year comes first... the point of doing it this way > is that a user can easily tell which version is newer, when looking > at multiple packages. If you use only the git commit hash, those are > effectively random, there's no sense of which is newest. > > The SlackBuild can split up the VERSION variable as needed. > > Also, while I'm thinking about it: VERSION *must* be a constant that > can be overridden by the environment. Example: > > VERSION=${VERSION:-3.4.1} Very good point, including the date never hurts. > *Please* don't try to get clever and do stuff like: > > COMMIT=1369d247e3d2bc697892795dea8cc1713344749f > VERSION="$( echo $COMMIT | head -c7 )" Note, for completeness, that the git short hash might be longer than seven characters because of collisions. The git command figures that out. Don't just shorten it :) Cheers Ruben From jebrhansen+SBo at gmail.com Sun Mar 20 23:01:07 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 20 Mar 2022 17:01:07 -0600 Subject: [Slackbuilds-users] Creating First Slackbuilds and Github In-Reply-To: <20220320235819.5fe9d824@kiwi.kuchen> References: <87v8waedi4.fsf@gmail.com> <20220319150812.6b876a5a@kiwi.kuchen> <20220319220651.5ed47ae5@kiwi.kuchen> <20220320235819.5fe9d824@kiwi.kuchen> Message-ID: On Sun, Mar 20, 2022, 4:58 PM Ruben Schuller wrote: > Hi, > > 2022-03-20 "B. Watson" : > > > On Sat, 19 Mar 2022, Ruben Schuller wrote: > > > > > > ZIPVER="1369d247e3d2bc697892795dea8cc1713344749f" > > > > > > for the version I'd either go with the date like 220319 if there > > > aren't multiple commits on that date, or with the short-hash of > > > git: > > > > Recommendations... in fact I'm begging you: if you're going to use > > a git commit, *please* include the date in YYMMDD format in your > > VERSION number. Example: > > > > VERSION="20220319+1369d24" > > > > Notice the 4-digit year comes first... the point of doing it this way > > is that a user can easily tell which version is newer, when looking > > at multiple packages. If you use only the git commit hash, those are > > effectively random, there's no sense of which is newest. > > > > The SlackBuild can split up the VERSION variable as needed. > > > > Also, while I'm thinking about it: VERSION *must* be a constant that > > can be overridden by the environment. Example: > > > > VERSION=${VERSION:-3.4.1} > > Very good point, including the date never hurts. > > > *Please* don't try to get clever and do stuff like: > > > > COMMIT=1369d247e3d2bc697892795dea8cc1713344749f > > VERSION="$( echo $COMMIT | head -c7 )" > > Note, for completeness, that the git short hash might be longer than > seven characters because of collisions. The git command figures that > out. Don't just shorten it :) > On SBo, it won't matter if there's collisions. It's simply a reference to a version that exists on SBo. If there's collisions within the upstream repo, it won't affect the version we have on SBo. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dickson.tim at googlemail.com Mon Mar 21 12:48:18 2022 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 21 Mar 2022 12:48:18 +0000 Subject: [Slackbuilds-users] qemu build issue In-Reply-To: References: <3a331878-1238-1f14-916a-296e09654dc0@googlemail.com> Message-ID: <322e80d5-682d-a4d6-1291-d1a1764adcb5@googlemail.com> thanks Matteo, that did the trick. It looks like part of the build process uses already created binaries to process files, and when older binaries are already in the path they are used instead, giving the error. It may be worth adding a comment to remove existing version of qemu before installing a newer one into the README. regards, Tim On 20/03/2022 18:31, Matteo Bernardini wrote: > have you tried removing the already installed qemu package first? > > Il giorno dom 20 mar 2022 alle ore 19:29 Tim Dickson via > SlackBuilds-users ha scritto: > > I am getting the following error when attempting to create qemu > package. > > /usr/bin/qemu-keymap: error while loading shared libraries: > libjemalloc.so.1: cannot open shared object file: No such file or > directory > > /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so > there > is a libjemalloc installed (part of slackware 15.0). > It seems that the build script is looking for the wrong version of > the > lib. Ideally it would try libjemalloc.so and thus pick up whichever > version was installed. > Is there a quick fix. (if it involves a sim-link would that have > to be > done on target computers as well?) > regards, Tim > > > -- > This email has been checked for viruses by AVG. > https://www.avg.com > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ -https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Mon Mar 21 12:54:52 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 21 Mar 2022 13:54:52 +0100 Subject: [Slackbuilds-users] qemu build issue In-Reply-To: <322e80d5-682d-a4d6-1291-d1a1764adcb5@googlemail.com> References: <3a331878-1238-1f14-916a-296e09654dc0@googlemail.com> <322e80d5-682d-a4d6-1291-d1a1764adcb5@googlemail.com> Message-ID: well, to be fair that shouldn't actually be a problem in a Slackware stable setup because libraries' versions should be the same... that should only happens when you are using current or upgrading between Slackware versions (but in that case many other things could happen). Matteo Il giorno lun 21 mar 2022 alle ore 13:48 Tim Dickson via SlackBuilds-users < slackbuilds-users at slackbuilds.org> ha scritto: > thanks Matteo, that did the trick. It looks like part of the build process > uses already created binaries to process files, and when older binaries are > already in the path they are used instead, giving the error. > > It may be worth adding a comment to remove existing version of qemu before > installing a newer one into the README. > > regards, Tim > > On 20/03/2022 18:31, Matteo Bernardini wrote: > > have you tried removing the already installed qemu package first? > > Il giorno dom 20 mar 2022 alle ore 19:29 Tim Dickson via SlackBuilds-users > ha scritto: > >> I am getting the following error when attempting to create qemu package. >> >> /usr/bin/qemu-keymap: error while loading shared libraries: >> libjemalloc.so.1: cannot open shared object file: No such file or >> directory >> >> /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there >> is a libjemalloc installed (part of slackware 15.0). >> It seems that the build script is looking for the wrong version of the >> lib. Ideally it would try libjemalloc.so and thus pick up whichever >> version was installed. >> Is there a quick fix. (if it involves a sim-link would that have to be >> done on target computers as well?) >> regards, Tim >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Mon Mar 21 13:05:56 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 21 Mar 2022 13:05:56 +0000 Subject: [Slackbuilds-users] qemu build issue In-Reply-To: References: <3a331878-1238-1f14-916a-296e09654dc0@googlemail.com> <322e80d5-682d-a4d6-1291-d1a1764adcb5@googlemail.com> Message-ID: <20220321130556.GD12020@localhost> On 21/03/22 13:54, Matteo Bernardini put forth the proposition: > well, to be fair that shouldn't actually be a problem in a Slackware stable > setup because libraries' versions should be the same... > that should only happens when you are using current or upgrading between > Slackware versions (but in that case many other things could happen). > Matteo I've just put a small note at the bottom of the README, that if there are any problems with missing or wrong versioned libraries to try uninstalling older versions first. Dave > Il giorno lun 21 mar 2022 alle ore 13:48 Tim Dickson via SlackBuilds-users < > slackbuilds-users at slackbuilds.org> ha scritto: > > thanks Matteo, that did the trick. It looks like part of the build process > > uses already created binaries to process files, and when older binaries are > > already in the path they are used instead, giving the error. > > > > It may be worth adding a comment to remove existing version of qemu before > > installing a newer one into the README. > > > > regards, Tim > > > > On 20/03/2022 18:31, Matteo Bernardini wrote: > > > > have you tried removing the already installed qemu package first? > > > > Il giorno dom 20 mar 2022 alle ore 19:29 Tim Dickson via SlackBuilds-users > > ha scritto: > > > >> I am getting the following error when attempting to create qemu package. > >> > >> /usr/bin/qemu-keymap: error while loading shared libraries: > >> libjemalloc.so.1: cannot open shared object file: No such file or > >> directory > >> > >> /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there > >> is a libjemalloc installed (part of slackware 15.0). > >> It seems that the build script is looking for the wrong version of the > >> lib. Ideally it would try libjemalloc.so and thus pick up whichever > >> version was installed. > >> Is there a quick fix. (if it involves a sim-link would that have to be > >> done on target computers as well?) > >> regards, Tim > >> > > > > -- Dave From dickson.tim at googlemail.com Mon Mar 21 15:04:51 2022 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 21 Mar 2022 15:04:51 +0000 Subject: [Slackbuilds-users] qemu build issue In-Reply-To: <20220321130556.GD12020@localhost> References: <3a331878-1238-1f14-916a-296e09654dc0@googlemail.com> <322e80d5-682d-a4d6-1291-d1a1764adcb5@googlemail.com> <20220321130556.GD12020@localhost> Message-ID: <019b0ad6-ab39-f872-9612-8cfd8cd6f679@googlemail.com> point noted, and thanks. qemu was my first slackbuild to be built for 15.0 to get my dev vm's up to date so I can get on with the rest, including the ones i look after. regards, Tim On 21/03/2022 13:05, Dave Woodfall wrote: > On 21/03/22 13:54, > Matteo Bernardini put forth the proposition: >> well, to be fair that shouldn't actually be a problem in a Slackware stable >> setup because libraries' versions should be the same... >> that should only happens when you are using current or upgrading between >> Slackware versions (but in that case many other things could happen). >> Matteo > I've just put a small note at the bottom of the README, that if there > are any problems with missing or wrong versioned libraries to try > uninstalling older versions first. > > Dave > >> Il giorno lun 21 mar 2022 alle ore 13:48 Tim Dickson via SlackBuilds-users < >> slackbuilds-users at slackbuilds.org> ha scritto: >>> thanks Matteo, that did the trick. It looks like part of the build process >>> uses already created binaries to process files, and when older binaries are >>> already in the path they are used instead, giving the error. >>> >>> It may be worth adding a comment to remove existing version of qemu before >>> installing a newer one into the README. >>> >>> regards, Tim >>> >>> On 20/03/2022 18:31, Matteo Bernardini wrote: >>> >>> have you tried removing the already installed qemu package first? >>> >>> Il giorno dom 20 mar 2022 alle ore 19:29 Tim Dickson via SlackBuilds-users >>> ha scritto: >>> >>>> I am getting the following error when attempting to create qemu package. >>>> >>>> /usr/bin/qemu-keymap: error while loading shared libraries: >>>> libjemalloc.so.1: cannot open shared object file: No such file or >>>> directory >>>> >>>> /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there >>>> is a libjemalloc installed (part of slackware 15.0). >>>> It seems that the build script is looking for the wrong version of the >>>> lib. Ideally it would try libjemalloc.so and thus pick up whichever >>>> version was installed. >>>> Is there a quick fix. (if it involves a sim-link would that have to be >>>> done on target computers as well?) >>>> regards, Tim >>>> >>> > -- > Dave > _______________________________________________ > 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/ > -- This email has been checked for viruses by AVG. https://www.avg.com From fernando.lopezjr at gmail.com Mon Mar 21 21:15:29 2022 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 21 Mar 2022 15:15:29 -0600 Subject: [Slackbuilds-users] heard of radicle? Message-ID: have you guys heard of radicle? It is git with torrent technology fused together. *https://radicle.xyz * -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vbatts at hashbangbash.com Mon Mar 21 21:43:55 2022 From: vbatts at hashbangbash.com (Vincent Batts) Date: Mon, 21 Mar 2022 17:43:55 -0400 Subject: [Slackbuilds-users] heard of radicle? In-Reply-To: References: Message-ID: Not quite bit torrent, but secure scuttle butt (ssb). Kind of a public network graph of storage and sharing. No private or personal options. It's neat. vb On March 21, 2022 5:15:29 PM EDT, Fernando Lopez wrote: >have you guys heard of radicle? It is git with torrent technology fused >together. > >*https://radicle.xyz * > >-- > >------------ >Regards, > Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rsamurti at gmail.com Tue Mar 22 11:55:35 2022 From: rsamurti at gmail.com (Ananda Murthy) Date: Tue, 22 Mar 2022 17:25:35 +0530 Subject: [Slackbuilds-users] Updates for fet.SlackBuild for Slackware 15.0 Message-ID: Hello, Please see the attachments. With regards, RSA -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fet.info Type: application/octet-stream Size: 296 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fet.SlackBuild Type: application/octet-stream Size: 3294 bytes Desc: not available URL: From rsamurti at gmail.com Tue Mar 22 12:00:03 2022 From: rsamurti at gmail.com (Ananda Murthy) Date: Tue, 22 Mar 2022 17:30:03 +0530 Subject: [Slackbuilds-users] Updates for ngspice.SlackBuild for Slackware 15.0 Message-ID: Hello, Please the attachments. With regards, RSA -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ngspice.info Type: application/octet-stream Size: 468 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ngspice.SlackBuild Type: application/octet-stream Size: 3677 bytes Desc: not available URL: From willysr at slackbuilds.org Tue Mar 22 13:42:57 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 22 Mar 2022 20:42:57 +0700 Subject: [Slackbuilds-users] Updates for ngspice.SlackBuild for Slackware 15.0 In-Reply-To: References: Message-ID: <607c871a-ed6d-a8a0-1368-53f143cc718d@slackbuilds.org> > Please the attachments. Hi Ananda Is it possible to do PR or MR? It's easier to track and email tends to get lost when lots of people sending patches to the list -- 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 mab974 at gmail.com Tue Mar 22 14:25:35 2022 From: mab974 at gmail.com (Michel BEGUE) Date: Tue, 22 Mar 2022 18:25:35 +0400 Subject: [Slackbuilds-users] fcron for 15.0 Message-ID: fcron does not build. just a line to add to ./configure " --with-sendmail=/usr/sbin/postfix " and maybe get to v3.3.1. regards. Michel -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Tue Mar 22 14:56:17 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Tue, 22 Mar 2022 14:56:17 +0000 Subject: [Slackbuilds-users] fcron for 15.0 In-Reply-To: References: Message-ID: <20220322145617.GE12020@localhost> On 22/03/22 18:25, Michel BEGUE put forth the proposition: > fcron does not build. > just a line to add to ./configure > " --with-sendmail=/usr/sbin/postfix " > and maybe get to v3.3.1. > regards. > Michel Done. -- Dave From rsamurti at gmail.com Tue Mar 22 14:57:09 2022 From: rsamurti at gmail.com (Ananda Murthy) Date: Tue, 22 Mar 2022 20:27:09 +0530 Subject: [Slackbuilds-users] Updates for ngspice.SlackBuild for Slackware 15.0 In-Reply-To: <607c871a-ed6d-a8a0-1368-53f143cc718d@slackbuilds.org> References: <607c871a-ed6d-a8a0-1368-53f143cc718d@slackbuilds.org> Message-ID: Sorry. Can you please elaborate what is PR or MR? On Tue, Mar 22, 2022 at 7:13 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Please the attachments. > > Hi Ananda > > Is it possible to do PR or MR? > It's easier to track and email tends to get lost when lots of people > sending patches to the list > > > -- > 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/ > > -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Mar 22 14:58:40 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 22 Mar 2022 21:58:40 +0700 Subject: [Slackbuilds-users] Updates for ngspice.SlackBuild for Slackware 15.0 In-Reply-To: References: <607c871a-ed6d-a8a0-1368-53f143cc718d@slackbuilds.org> Message-ID: <49c71b6d-b848-a4ce-8a56-aad1bcb62304@slackbuilds.org> > Sorry. Can you please elaborate what is PR or MR? pull request / merge request if you want to send to the list, please do it in .patch format, not diffs -- 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 rsamurti at gmail.com Tue Mar 22 15:50:04 2022 From: rsamurti at gmail.com (Ananda Murthy) Date: Tue, 22 Mar 2022 21:20:04 +0530 Subject: [Slackbuilds-users] Updates for ngspice.SlackBuild for Slackware 15.0 In-Reply-To: <49c71b6d-b848-a4ce-8a56-aad1bcb62304@slackbuilds.org> References: <607c871a-ed6d-a8a0-1368-53f143cc718d@slackbuilds.org> <49c71b6d-b848-a4ce-8a56-aad1bcb62304@slackbuilds.org> Message-ID: How to do PR and MR? On Tue, Mar 22, 2022 at 8:28 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Sorry. Can you please elaborate what is PR or MR? > > pull request / merge request > if you want to send to the list, please do it in .patch format, not diffs > > > -- > 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/ > > -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Tue Mar 22 17:33:28 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 22 Mar 2022 11:33:28 -0600 Subject: [Slackbuilds-users] Updates for ngspice.SlackBuild for Slackware 15.0 In-Reply-To: References: <607c871a-ed6d-a8a0-1368-53f143cc718d@slackbuilds.org> <49c71b6d-b848-a4ce-8a56-aad1bcb62304@slackbuilds.org> Message-ID: You would fork the repo from GitHub or GitLab and create a new branch with your changes. Then submit a Pull Request (GitHub) or Merge Request (GitLab) with those changes back to the upstream repo. https://github.com/SlackBuildsOrg/slackbuilds https://gitlab.com/SlackBuilds.org/slackbuilds/ Jeremy On Tue, Mar 22, 2022, 9:50 AM Ananda Murthy wrote: > How to do PR and MR? > > On Tue, Mar 22, 2022 at 8:28 PM Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> > Sorry. Can you please elaborate what is PR or MR? >> >> pull request / merge request >> if you want to send to the list, please do it in .patch format, not diffs >> >> >> -- >> 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/ >> >> > > -- > > > Close Windows ! Open source !! > Free software from proprietary mafia !!! > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tonus1 at gmail.com Tue Mar 22 20:34:30 2022 From: tonus1 at gmail.com (Tonus) Date: Tue, 22 Mar 2022 21:34:30 +0100 Subject: [Slackbuilds-users] Updates for ngspice.SlackBuild for Slackware 15.0 In-Reply-To: References: Message-ID: <4073947C-FFF2-49F3-B86C-F4955676BCDE@gmail.com> Hi, It a git thing to do via github.com for instance. You clone the repo, make your edits and you will be prompted on the web interface to do a PR. Regards Le 22 mars 2022 16:50:42 GMT+01:00, slackbuilds-users-request at slackbuilds.org a ?crit?: >Send SlackBuilds-users mailing list submissions to > slackbuilds-users at slackbuilds.org > >To subscribe or unsubscribe via the World Wide Web, visit > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >or, via email, send a message with subject or body 'help' to > slackbuilds-users-request at slackbuilds.org > >You can reach the person managing the list at > slackbuilds-users-owner at slackbuilds.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of SlackBuilds-users digest..." > > >Today's Topics: > > 1. Updates for ngspice.SlackBuild for Slackware 15.0 (Ananda Murthy) > 2. Re: Updates for ngspice.SlackBuild for Slackware 15.0 > (Willy Sudiarto Raharjo) > 3. fcron for 15.0 (Michel BEGUE) > 4. Re: fcron for 15.0 (Dave Woodfall) > 5. Re: Updates for ngspice.SlackBuild for Slackware 15.0 > (Ananda Murthy) > 6. Re: Updates for ngspice.SlackBuild for Slackware 15.0 > (Willy Sudiarto Raharjo) > 7. Re: Updates for ngspice.SlackBuild for Slackware 15.0 > (Ananda Murthy) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Tue, 22 Mar 2022 17:30:03 +0530 >From: Ananda Murthy >To: "SlackBuilds.org Users List" >Subject: [Slackbuilds-users] Updates for ngspice.SlackBuild for > Slackware 15.0 >Message-ID: > >Content-Type: text/plain; charset="utf-8" > >Hello, > >Please the attachments. > >With regards, > >RSA >-- > > >Close Windows ! Open source !! >Free software from proprietary mafia !!! >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: >-------------- next part -------------- >A non-text attachment was scrubbed... >Name: ngspice.info >Type: application/octet-stream >Size: 468 bytes >Desc: not available >URL: >-------------- next part -------------- >A non-text attachment was scrubbed... >Name: ngspice.SlackBuild >Type: application/octet-stream >Size: 3677 bytes >Desc: not available >URL: > >------------------------------ > >Message: 2 >Date: Tue, 22 Mar 2022 20:42:57 +0700 >From: Willy Sudiarto Raharjo >To: slackbuilds-users at slackbuilds.org >Subject: Re: [Slackbuilds-users] Updates for ngspice.SlackBuild for > Slackware 15.0 >Message-ID: <607c871a-ed6d-a8a0-1368-53f143cc718d at slackbuilds.org> >Content-Type: text/plain; charset="utf-8" > >> Please the attachments. > >Hi Ananda > >Is it possible to do PR or MR? >It's easier to track and email tends to get lost when lots of people >sending patches to the list > > >-- >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: > >------------------------------ > >Message: 3 >Date: Tue, 22 Mar 2022 18:25:35 +0400 >From: Michel BEGUE >To: richard at aaazen.com >Cc: "SlackBuilds.org Users List" >Subject: [Slackbuilds-users] fcron for 15.0 >Message-ID: > >Content-Type: text/plain; charset="utf-8" > >fcron does not build. >just a line to add to ./configure >" --with-sendmail=/usr/sbin/postfix " >and maybe get to v3.3.1. > >regards. >Michel >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: > >------------------------------ > >Message: 4 >Date: Tue, 22 Mar 2022 14:56:17 +0000 >From: Dave Woodfall >To: slackbuilds-users at slackbuilds.org >Subject: Re: [Slackbuilds-users] fcron for 15.0 >Message-ID: <20220322145617.GE12020 at localhost> >Content-Type: text/plain; charset=utf-8 > >On 22/03/22 18:25, >Michel BEGUE put forth the proposition: >> fcron does not build. >> just a line to add to ./configure >> " --with-sendmail=/usr/sbin/postfix " >> and maybe get to v3.3.1. >> regards. >> Michel > >Done. > >-- >Dave > > >------------------------------ > >Message: 5 >Date: Tue, 22 Mar 2022 20:27:09 +0530 >From: Ananda Murthy >To: "SlackBuilds.org Users List" >Subject: Re: [Slackbuilds-users] Updates for ngspice.SlackBuild for > Slackware 15.0 >Message-ID: > >Content-Type: text/plain; charset="utf-8" > >Sorry. Can you please elaborate what is PR or MR? > >On Tue, Mar 22, 2022 at 7:13 PM Willy Sudiarto Raharjo < >willysr at slackbuilds.org> wrote: > >> > Please the attachments. >> >> Hi Ananda >> >> Is it possible to do PR or MR? >> It's easier to track and email tends to get lost when lots of people >> sending patches to the list >> >> >> -- >> 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/ >> >> > >-- > > >Close Windows ! Open source !! >Free software from proprietary mafia !!! >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: > >------------------------------ > >Message: 6 >Date: Tue, 22 Mar 2022 21:58:40 +0700 >From: Willy Sudiarto Raharjo >To: slackbuilds-users at slackbuilds.org >Subject: Re: [Slackbuilds-users] Updates for ngspice.SlackBuild for > Slackware 15.0 >Message-ID: <49c71b6d-b848-a4ce-8a56-aad1bcb62304 at slackbuilds.org> >Content-Type: text/plain; charset="utf-8" > >> Sorry. Can you please elaborate what is PR or MR? > >pull request / merge request >if you want to send to the list, please do it in .patch format, not diffs > > >-- >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: > >------------------------------ > >Message: 7 >Date: Tue, 22 Mar 2022 21:20:04 +0530 >From: Ananda Murthy >To: "SlackBuilds.org Users List" >Subject: Re: [Slackbuilds-users] Updates for ngspice.SlackBuild for > Slackware 15.0 >Message-ID: > >Content-Type: text/plain; charset="utf-8" > >How to do PR and MR? > >On Tue, Mar 22, 2022 at 8:28 PM Willy Sudiarto Raharjo < >willysr at slackbuilds.org> wrote: > >> > Sorry. Can you please elaborate what is PR or MR? >> >> pull request / merge request >> if you want to send to the list, please do it in .patch format, not diffs >> >> >> -- >> 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/ >> >> > >-- > > >Close Windows ! Open source !! >Free software from proprietary mafia !!! >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: > >------------------------------ > >Subject: Digest Footer > >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > >------------------------------ > >End of SlackBuilds-users Digest, Vol 191, Issue 48 >************************************************** -- Tonus -------------- next part -------------- An HTML attachment was scrubbed... URL: From bencollver at riseup.net Wed Mar 23 02:46:29 2022 From: bencollver at riseup.net (Ben Collver) Date: Tue, 22 Mar 2022 19:46:29 -0700 Subject: [Slackbuilds-users] Please change email in system/pax Message-ID: Greetings, I plan to delete my Google account. Please change the email in system/pax/pax.info OLD: EMAIL="bencollver at gmail.com" NEW: EMAIL="bencollver at riseup.net" Thanks! -Ben From dave at slackbuilds.org Wed Mar 23 02:58:05 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Wed, 23 Mar 2022 02:58:05 +0000 Subject: [Slackbuilds-users] Please change email in system/pax In-Reply-To: References: Message-ID: <20220323025805.GA18559@localhost> On 22/03/22 19:46, Ben Collver put forth the proposition: > Greetings, > I plan to delete my Google account. Please change the email in > system/pax/pax.info > OLD: EMAIL="bencollver at gmail.com" > NEW: EMAIL="bencollver at riseup.net" > Thanks! > -Ben Done. -- Dave From lenardrspencer at gmail.com Wed Mar 23 03:12:11 2022 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Tue, 22 Mar 2022 23:12:11 -0400 Subject: [Slackbuilds-users] nvidia driver and kernel updates Message-ID: Here are patches for the nvidia-{kernel,driver} and nvidia-legacy390-{kernel,driver} scripts, diff'ed against master. nvidia-{kernel,driver} have been updated to 510.60.02. nvidia-legacy390--{kernel,driver} have been updated to 390.147. nvidia-legacy390-kernel also includes a patch for the 5.17 kernel to make it current-ready. As soon as submissions reopen I will be uploading nvidia-legacy470 scripts. According to upstream, the 470 series will be supported through December2024, the 390 series through December 2022. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-driver-kernel-patches.tar.gz Type: application/gzip Size: 5980 bytes Desc: not available URL: From b.pribs11 at gmail.com Wed Mar 23 03:22:21 2022 From: b.pribs11 at gmail.com (Brandon Pribula) Date: Tue, 22 Mar 2022 20:22:21 -0700 Subject: [Slackbuilds-users] Slackbuild with Two Executables Message-ID: Hi, There's a program I would like to package into a slackbuild. The program itself is really two programs; two shell scripts. One is in bash (appname) and the other is POSIX compliant (appnameposix). Rather than installing both I decided to include two slackbuild scripts: one for each program so the user can choose if they want to install just one or both. But it seems if the 'appname' in slack-desc doesn't match $PRGNAM in the slackbuild then installpkg doesn't print the slack-desc. I tried to get around this by replacing $PRGNAM with ${PRGNAM}posix but this didn't work. The only options I can see are either splitting the package up into two separate slackbuilds, or install both. Which of those two options are preferable or is there another option? Any help would be appreciated, Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Wed Mar 23 03:34:47 2022 From: urchlay at slackware.uk (B. Watson) Date: Tue, 22 Mar 2022 23:34:47 -0400 (EDT) Subject: [Slackbuilds-users] Slackbuild with Two Executables In-Reply-To: References: Message-ID: On Tue, 22 Mar 2022, Brandon Pribula wrote: > only options I can see are either splitting the package up into two separate > slackbuilds, or install both. > Which of those two options are preferable or is there another option? Other options: - Install both scripts in $PKG/usr/bin, call one "appname" and the other "appname-posix", and explain the situation in your README. - Use an environment variable (APPNAME_POSIX=yes|no) to let the user choose which of the scripts to include in the package. One thing that's *not* an option: Don't have one SlackBuild script that creates two separate packages (in other words, don't ever call makepkg twice). If you do decide to make separate packages for 'appname' and 'appname-posix', it'll have to be two separate SlackBuilds. Personally, I'd choose one of the other options (one SlackBuild, one package, either include both scripts or use the env to select one). From b.pribs11 at gmail.com Wed Mar 23 04:32:17 2022 From: b.pribs11 at gmail.com (Brandon Pribula) Date: Tue, 22 Mar 2022 21:32:17 -0700 Subject: [Slackbuilds-users] Slackbuild with Two Executables In-Reply-To: References: Message-ID: On Tue, Mar 22, 2022, 8:35 PM B. Watson, wrote: > > > On Tue, 22 Mar 2022, Brandon Pribula wrote: > > > only options I can see are either splitting the package up into two > separate > > slackbuilds, or install both. > > > Which of those two options are preferable or is there another option? > > Other options: > > - Install both scripts in $PKG/usr/bin, call one "appname" and the other > "appname-posix", and explain the situation in your README. > > - Use an environment variable (APPNAME_POSIX=yes|no) to let the user > choose which of the scripts to include in the package. > > One thing that's *not* an option: Don't have one SlackBuild script > that creates two separate packages (in other words, don't ever > call makepkg twice). > > If you do decide to make separate packages for 'appname' and > 'appname-posix', it'll have to be two separate SlackBuilds. > Personally, I'd choose one of the other options (one SlackBuild, one > package, either include both scripts or use the env to select one). > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ Thanks for the reply, B. Watson :) For the option of using an ENV variable, can it also be used to install both scripts as long as makepkg isn't called twice? Then just use appname for the package name no matter which option is chosen. In the README I could specify which executable to call depending on the options chosen. -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Wed Mar 23 05:43:04 2022 From: urchlay at slackware.uk (B. Watson) Date: Wed, 23 Mar 2022 01:43:04 -0400 (EDT) Subject: [Slackbuilds-users] Slackbuild with Two Executables In-Reply-To: References: Message-ID: <90f666f-488b-1add-16a-30d3709899b@slackware.uk> On Tue, 22 Mar 2022, Brandon Pribula wrote: > For the option of using an ENV variable, can it also be used to install both > scripts as long as makepkg isn't called twice? > Then just use appname for the package name no matter which option is chosen. Sure, but... > In the README I could specify which executable to call depending on the > options chosen. If you're using the environment variable approach... why not name the executable 'appname' in the package, regardless of whether it was originally called 'appname' or 'appname-posix' in the source? User always types same command to run the script... But, if you're going to go to the trouble of writing up an explanation in the README, you might as well skip the environment variable, and just install both scripts in the package, and mention in the README the fact that the user can choose to run either 'appname' or 'appname-posix'. If the two scripts are in two separate download files, that's not really a problem (put both in DOWNLOAD= in the .info file, write SlackBuild code to extract both). One thing you might want to do... look through the repo and see what others have done, to get ideas. Though these days that can be pretty time-consuming (we have almost 8000 builds now). From jebrhansen+SBo at gmail.com Wed Mar 23 06:32:38 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 23 Mar 2022 00:32:38 -0600 Subject: [Slackbuilds-users] Slackbuild with Two Executables In-Reply-To: References: Message-ID: On Tue, Mar 22, 2022, 10:32 PM Brandon Pribula wrote: > > > On Tue, Mar 22, 2022, 8:35 PM B. Watson, wrote: > >> >> >> On Tue, 22 Mar 2022, Brandon Pribula wrote: >> >> > only options I can see are either splitting the package up into two >> separate >> > slackbuilds, or install both. >> >> > Which of those two options are preferable or is there another option? >> >> Other options: >> >> - Install both scripts in $PKG/usr/bin, call one "appname" and the other >> "appname-posix", and explain the situation in your README. >> >> - Use an environment variable (APPNAME_POSIX=yes|no) to let the user >> choose which of the scripts to include in the package. >> >> One thing that's *not* an option: Don't have one SlackBuild script >> that creates two separate packages (in other words, don't ever >> call makepkg twice). >> >> If you do decide to make separate packages for 'appname' and >> 'appname-posix', it'll have to be two separate SlackBuilds. >> Personally, I'd choose one of the other options (one SlackBuild, one >> package, either include both scripts or use the env to select one). >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ > > > Thanks for the reply, B. Watson :) > > For the option of using an ENV variable, can it also be used to install > both scripts as long as makepkg isn't called twice? > > Then just use appname for the package name no matter which option is > chosen. In the README I could specify which executable to call depending on > the options chosen. > If you'd like to see an example of enabling different options, you could look at my mediainfo script. It defaults to build only the CLI, but you can enable the GUI with the CLI or do only the GUI. It'd be a little different since you're only dealing with scripts instead of compiling programs. https://slackbuilds.org/repository/15.0/multimedia/mediainfo/ Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Mar 23 07:19:19 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 23 Mar 2022 14:19:19 +0700 Subject: [Slackbuilds-users] Fixing 32 bit FTBFS Message-ID: <1145347a-c0a3-bbdb-3ed8-8420a85942d9@slackbuilds.org> Hi everyone we are still fixing 32 bit failures and we think it could go faster if the community are involved (like what we did during development cycle). Here's the list of failed builds: https://slackware.uk/~urchlay/src/ftbfs.32bit.20220323 Please test them on clean environment (VM or Chroot) with latest -Stable Update Thank you -- 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 urchlay at slackware.uk Wed Mar 23 07:52:42 2022 From: urchlay at slackware.uk (B. Watson) Date: Wed, 23 Mar 2022 03:52:42 -0400 (EDT) Subject: [Slackbuilds-users] Fixing 32 bit FTBFS In-Reply-To: <1145347a-c0a3-bbdb-3ed8-8420a85942d9@slackbuilds.org> References: <1145347a-c0a3-bbdb-3ed8-8420a85942d9@slackbuilds.org> Message-ID: <1226eef7-e897-3226-57fa-f317236891c0@slackware.uk> On Wed, 23 Mar 2022, Willy Sudiarto Raharjo wrote: > Here's the list of failed builds: > https://slackware.uk/~urchlay/src/ftbfs.32bit.20220323 Addendum: ignore onevpl, from that list. It can only be built on x86_64, 32-bit builds are impossible (so don't waste your time trying). From urchlay at slackware.uk Wed Mar 23 08:18:48 2022 From: urchlay at slackware.uk (B. Watson) Date: Wed, 23 Mar 2022 04:18:48 -0400 (EDT) Subject: [Slackbuilds-users] Fixing 32 bit FTBFS In-Reply-To: <1226eef7-e897-3226-57fa-f317236891c0@slackware.uk> References: <1145347a-c0a3-bbdb-3ed8-8420a85942d9@slackbuilds.org> <1226eef7-e897-3226-57fa-f317236891c0@slackware.uk> Message-ID: <64dabed-6696-9db0-1b6-86463b868e6@slackware.uk> On Wed, 23 Mar 2022, B. Watson wrote: > > > On Wed, 23 Mar 2022, Willy Sudiarto Raharjo wrote: > >> Here's the list of failed builds: >> https://slackware.uk/~urchlay/src/ftbfs.32bit.20220323 > > Addendum: ignore onevpl, from that list. It can only be built on > x86_64, 32-bit builds are impossible (so don't waste your time > trying). Also, I just fixed helm and pushed it to my git branch. From ozan.turkyilmaz at gmail.com Wed Mar 23 08:22:09 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Wed, 23 Mar 2022 11:22:09 +0300 Subject: [Slackbuilds-users] Fixing 32 bit FTBFS In-Reply-To: <1145347a-c0a3-bbdb-3ed8-8420a85942d9@slackbuilds.org> References: <1145347a-c0a3-bbdb-3ed8-8420a85942d9@slackbuilds.org> Message-ID: <463c37c976c9df01e2d5a2254d544ddc201f0e9e.camel@gmail.com> ?r?, 2022-03-23 tarihinde 14:19 +0700 saatinde, Willy Sudiarto Raharjo yazd?: > Hi everyone > > we are still fixing 32 bit failures and we think it could go faster > if > the community are involved (like what we did during development > cycle). > > Here's the list of failed builds: > https://slackware.uk/~urchlay/src/ftbfs.32bit.20220323 > > Please test them on clean environment (VM or Chroot) with latest - > Stable > Update I started installing 32 bit Slackware chroot right now. I'll take look at handbrake. My system is 64 bit originally so anything that deals with kernel might not be possible for me to test correctly. Regards, Ozan From erich.public at protonmail.com Wed Mar 23 13:04:10 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Wed, 23 Mar 2022 13:04:10 +0000 Subject: [Slackbuilds-users] Fixing 32 bit FTBFS In-Reply-To: <1145347a-c0a3-bbdb-3ed8-8420a85942d9@slackbuilds.org> References: <1145347a-c0a3-bbdb-3ed8-8420a85942d9@slackbuilds.org> Message-ID: ------- Original Message ------- On Wednesday, March 23rd, 2022 at 2:19 AM, Willy Sudiarto Raharjo willysr at slackbuilds.org wrote: > Hi everyone > > we are still fixing 32 bit failures and we think it could go faster if > the community are involved (like what we did during development cycle). > > Here's the list of failed builds: > https://slackware.uk/~urchlay/src/ftbfs.32bit.20220323 > > Please test them on clean environment (VM or Chroot) with latest -Stable > Update > > Thank you > > -- > > Willy Sudiarto Raharjo > > system76-power - seems upstream do not test on 32bit - https://github.com/pop-os/system76-power/blob/master/src/sideband.rs#L45 - i64 type declared, rust fails with: expected `i32`, found `i64` As I'm maintainer of this one, I'll investigate to see if it can be fixed or mark 32-bit as "UNSUPPORTED". Erich From richard at aaazen.com Wed Mar 23 14:18:24 2022 From: richard at aaazen.com (Richard Narron) Date: Wed, 23 Mar 2022 07:18:24 -0700 (PDT) Subject: [Slackbuilds-users] fcron for 15.0 In-Reply-To: References: Message-ID: <4cac219a-58b6-7bf8-29c3-4bdf392484db@aaazen.com> On Tue, 22 Mar 2022, Michel BEGUE wrote: > fcron does not build. > just a line to add to ./configure > " --with-sendmail=/usr/sbin/postfix " I do not get any errors in building 3.3.0 With postfix installed, the fcron 3.3.0 build finds sendmail at /usr/sbin/sendmail. What error did you get building fcron 3.3.0? > and maybe get to v3.3.1. This is a good idea. I am waiting to be able to update my scripts... Richard Narron From rasp at spitzner.org Wed Mar 23 15:33:22 2022 From: rasp at spitzner.org (Ralph Spitzner) Date: Wed, 23 Mar 2022 16:33:22 +0100 Subject: [Slackbuilds-users] codeblocks slackbuild slarm64 Message-ID: <582d4b92-de3c-74b7-6081-ce3cac25d8b5@spitzner.org> without this configure can't find the version of libboost (on slarm/slackware64/ aarch64) on 15.0 + -rasp --- codeblocks.SlackBuild~ 2022-03-23 15:27:29.055474367 +0100 +++ codeblocks.SlackBuild 2022-03-23 15:42:48.790231733 +0100 @@ -59,6 +59,10 @@ elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" +elif [ "$ARCH" = "aarch64" ]; then + SLKCFLAGS="-O2 -fPIC" + LIBDIRSUFFIX="64" + else SLKCFLAGS="-O2" LIBDIRSUFFIX="" -- "ich brauche keine Verschluesselung, mich versteht eh keiner" -Icke From willysr at slackbuilds.org Wed Mar 23 17:25:26 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 24 Mar 2022 00:25:26 +0700 Subject: [Slackbuilds-users] codeblocks slackbuild slarm64 In-Reply-To: <582d4b92-de3c-74b7-6081-ce3cac25d8b5@spitzner.org> References: <582d4b92-de3c-74b7-6081-ce3cac25d8b5@spitzner.org> Message-ID: <4c3e1059-92cc-c41c-7761-56fae79d6272@slackbuilds.org> > without this configure can't find the version of libboost (on > slarm/slackware64/ aarch64) on 15.0 + > > --- codeblocks.SlackBuild~????? 2022-03-23 15:27:29.055474367 +0100 > +++ codeblocks.SlackBuild?????? 2022-03-23 15:42:48.790231733 +0100 > @@ -59,6 +59,10 @@ > ?elif [ "$ARCH" = "x86_64" ]; then > ?? SLKCFLAGS="-O2 -fPIC" > ?? LIBDIRSUFFIX="64" > +elif [ "$ARCH" = "aarch64" ]; then > +? SLKCFLAGS="-O2 -fPIC" > +? LIBDIRSUFFIX="64" > + > ?else > ?? SLKCFLAGS="-O2" > ?? LIBDIRSUFFIX="" Please note that 15.0+ and ARM are both not officially supported by SBo We can add that, but we can't really test it -- 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 rasp at spitzner.org Wed Mar 23 17:57:40 2022 From: rasp at spitzner.org (Ralph Spitzner) Date: Wed, 23 Mar 2022 18:57:40 +0100 Subject: [Slackbuilds-users] codeblocks slackbuild slarm64 In-Reply-To: <4c3e1059-92cc-c41c-7761-56fae79d6272@slackbuilds.org> References: <582d4b92-de3c-74b7-6081-ce3cac25d8b5@spitzner.org> <4c3e1059-92cc-c41c-7761-56fae79d6272@slackbuilds.org> Message-ID: <3fce5bd6-5d18-7c7e-0874-5664216be7db@spitzner.org> Willy Sudiarto Raharjo wrote on 3/23/22 6:25 PM: > > Please note that 15.0+ and ARM are both not officially supported by SBo > We can add that, but we can't really test it I just built it on slarm64, it works and doesn't hurt anyone/thing... :-) -rasp -- "ich brauche keine Verschluesselung, mich versteht eh keiner" -Icke From b.pribs11 at gmail.com Wed Mar 23 19:33:37 2022 From: b.pribs11 at gmail.com (Brandon Pribula) Date: Wed, 23 Mar 2022 12:33:37 -0700 Subject: [Slackbuilds-users] Slackbuild with Two Executables In-Reply-To: <90f666f-488b-1add-16a-30d3709899b@slackware.uk> References: <90f666f-488b-1add-16a-30d3709899b@slackware.uk> Message-ID: On Tue, Mar 22, 2022 at 10:43 PM B. Watson wrote: > > > On Tue, 22 Mar 2022, Brandon Pribula wrote: > > > For the option of using an ENV variable, can it also be used to install > both > > scripts as long as makepkg isn't called twice? > > > Then just use appname for the package name no matter which option is > chosen. > > Sure, but... > > > In the README I could specify which executable to call depending on the > > options chosen. > > If you're using the environment variable approach... why not name the > executable 'appname' in the package, regardless of whether it was > originally called 'appname' or 'appname-posix' in the source? User > always types same command to run the script... > > But, if you're going to go to the trouble of writing up an explanation > in the README, you might as well skip the environment variable, > and just install both scripts in the package, and mention in the > README the fact that the user can choose to run either 'appname' or > 'appname-posix'. > > If the two scripts are in two separate download files, that's not > really a problem (put both in DOWNLOAD= in the .info file, write > SlackBuild code to extract both). > > One thing you might want to do... look through the repo and see what > others have done, to get ideas. Though these days that can be pretty > time-consuming (we have almost 8000 builds now). > _______________________________________________ > 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/ > > Well for the environment variable approach I wanted to give the option of installing both, so in that case the executables would have to have different names. So in terms of the script I thought it would make sense to just have distinct names for the executables no matter which option they chose. I didn't realize there were that many slackbuilds. That's impressive! Thanks again for your help :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.pribs11 at gmail.com Wed Mar 23 19:45:09 2022 From: b.pribs11 at gmail.com (Brandon Pribula) Date: Wed, 23 Mar 2022 12:45:09 -0700 Subject: [Slackbuilds-users] Slackbuild with Two Executables In-Reply-To: References: Message-ID: Thanks for the example, Jeremy :) Although I've written shell scripts before these will be my first slackbuilds and I'm second guessing everything (I guess want everything to be perfect) so this example really helped. On Tue, Mar 22, 2022 at 11:32 PM Jeremy Hansen wrote: > On Tue, Mar 22, 2022, 10:32 PM Brandon Pribula > wrote: > >> >> >> On Tue, Mar 22, 2022, 8:35 PM B. Watson, wrote: >> >>> >>> >>> On Tue, 22 Mar 2022, Brandon Pribula wrote: >>> >>> > only options I can see are either splitting the package up into two >>> separate >>> > slackbuilds, or install both. >>> >>> > Which of those two options are preferable or is there another option? >>> >>> Other options: >>> >>> - Install both scripts in $PKG/usr/bin, call one "appname" and the other >>> "appname-posix", and explain the situation in your README. >>> >>> - Use an environment variable (APPNAME_POSIX=yes|no) to let the user >>> choose which of the scripts to include in the package. >>> >>> One thing that's *not* an option: Don't have one SlackBuild script >>> that creates two separate packages (in other words, don't ever >>> call makepkg twice). >>> >>> If you do decide to make separate packages for 'appname' and >>> 'appname-posix', it'll have to be two separate SlackBuilds. >>> Personally, I'd choose one of the other options (one SlackBuild, one >>> package, either include both scripts or use the env to select one). >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >> >> >> Thanks for the reply, B. Watson :) >> >> For the option of using an ENV variable, can it also be used to install >> both scripts as long as makepkg isn't called twice? >> >> Then just use appname for the package name no matter which option is >> chosen. In the README I could specify which executable to call depending on >> the options chosen. >> > > If you'd like to see an example of enabling different options, you could > look at my mediainfo script. It defaults to build only the CLI, but you can > enable the GUI with the CLI or do only the GUI. > > It'd be a little different since you're only dealing with scripts instead > of compiling programs. > > https://slackbuilds.org/repository/15.0/multimedia/mediainfo/ > > 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 b.pribs11 at gmail.com Wed Mar 23 19:47:52 2022 From: b.pribs11 at gmail.com (Brandon Pribula) Date: Wed, 23 Mar 2022 12:47:52 -0700 Subject: [Slackbuilds-users] Slackbuild with Two Executables In-Reply-To: References: Message-ID: On Wed, Mar 23, 2022 at 12:45 PM Brandon Pribula wrote: > Thanks for the example, Jeremy :) > > Although I've written shell scripts before these will be my first > slackbuilds and I'm second guessing everything (I guess want everything to > be perfect) so this example really helped. > > On Tue, Mar 22, 2022 at 11:32 PM Jeremy Hansen > wrote: > >> On Tue, Mar 22, 2022, 10:32 PM Brandon Pribula >> wrote: >> >>> >>> >>> On Tue, Mar 22, 2022, 8:35 PM B. Watson, wrote: >>> >>>> >>>> >>>> On Tue, 22 Mar 2022, Brandon Pribula wrote: >>>> >>>> > only options I can see are either splitting the package up into two >>>> separate >>>> > slackbuilds, or install both. >>>> >>>> > Which of those two options are preferable or is there another option? >>>> >>>> Other options: >>>> >>>> - Install both scripts in $PKG/usr/bin, call one "appname" and the other >>>> "appname-posix", and explain the situation in your README. >>>> >>>> - Use an environment variable (APPNAME_POSIX=yes|no) to let the user >>>> choose which of the scripts to include in the package. >>>> >>>> One thing that's *not* an option: Don't have one SlackBuild script >>>> that creates two separate packages (in other words, don't ever >>>> call makepkg twice). >>>> >>>> If you do decide to make separate packages for 'appname' and >>>> 'appname-posix', it'll have to be two separate SlackBuilds. >>>> Personally, I'd choose one of the other options (one SlackBuild, one >>>> package, either include both scripts or use the env to select one). >>>> _______________________________________________ >>>> SlackBuilds-users mailing list >>>> SlackBuilds-users at slackbuilds.org >>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>>> FAQ - https://slackbuilds.org/faq/ >>> >>> >>> Thanks for the reply, B. Watson :) >>> >>> For the option of using an ENV variable, can it also be used to install >>> both scripts as long as makepkg isn't called twice? >>> >>> Then just use appname for the package name no matter which option is >>> chosen. In the README I could specify which executable to call depending on >>> the options chosen. >>> >> >> If you'd like to see an example of enabling different options, you could >> look at my mediainfo script. It defaults to build only the CLI, but you can >> enable the GUI with the CLI or do only the GUI. >> >> It'd be a little different since you're only dealing with scripts instead >> of compiling programs. >> >> https://slackbuilds.org/repository/15.0/multimedia/mediainfo/ >> >> 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/ >> >> Sorry for top posting. -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Wed Mar 23 20:16:09 2022 From: urchlay at slackware.uk (B. Watson) Date: Wed, 23 Mar 2022 16:16:09 -0400 (EDT) Subject: [Slackbuilds-users] Slackbuild with Two Executables In-Reply-To: References: <90f666f-488b-1add-16a-30d3709899b@slackware.uk> Message-ID: <358dea71-5dee-e1cc-f0e3-765d2d7f7318@slackware.uk> On Wed, 23 Mar 2022, Brandon Pribula wrote: > Well for the environment variable approach I wanted to give the option of > installing both, so in that case the executables would have to have > different names. So in terms of the script I thought it would make sense to > just have distinct names for the executables no matter which option they > chose. Yes, but... if you're going to have 2 separate executables, with different names. Why bother with the environment variable at all? Just include both executables (e.g. /usr/bin/appname and /usr/bin/appname-posix) in your package, and mention in README that there are two, and give both their names. Users who prefer the -posix version can just type "appname-posix" to use it, and users who don't care can just type "appname"... It'd be different if they were mutually exclusive, a compiled program that either has or does not have some option built in. Or if your programs were huge and took up a lot of disk space, so a user might care about not installing the one he doesn't need. In the absence of such concerns, go with simplicity: don't force a user to make a choice if it's trivial to avoid it. If I were a new user of your app that you're packaging, I'd have no idea whether I wanted the regular or -posix version, so I'd either go with the default (most people do), or have to spend time & effort researching the alternative. Slackware for instance includes two emacs executables (emacs-with-X11 and emacs-no-X11), and two strings commands (strings-BSD and strings-GNU)... although those are more complex examples, using symlinks. You won't need symlinks, it doesn't sound like. > I didn't realize there were that many slackbuilds. That's impressive! They sorta grew beyond expectations, but that just means we're doing something right. From urchlay at slackware.uk Wed Mar 23 20:50:31 2022 From: urchlay at slackware.uk (B. Watson) Date: Wed, 23 Mar 2022 16:50:31 -0400 (EDT) Subject: [Slackbuilds-users] Updated ftbfs list Message-ID: Fixed a few of these, removed a few: https://slackware.uk/~urchlay/src/ftbfs.32bit.20220323 Same URL as previous version of the list, make sure you're not working from an outdated copy. From b.pribs11 at gmail.com Thu Mar 24 02:35:54 2022 From: b.pribs11 at gmail.com (Brandon Pribula) Date: Wed, 23 Mar 2022 19:35:54 -0700 Subject: [Slackbuilds-users] Slackbuild with Two Executables In-Reply-To: <358dea71-5dee-e1cc-f0e3-765d2d7f7318@slackware.uk> References: <90f666f-488b-1add-16a-30d3709899b@slackware.uk> <358dea71-5dee-e1cc-f0e3-765d2d7f7318@slackware.uk> Message-ID: On Wed, Mar 23, 2022, 1:16 PM B. Watson, wrote: > > > On Wed, 23 Mar 2022, Brandon Pribula wrote: > > > Well for the environment variable approach I wanted to give the option of > > installing both, so in that case the executables would have to have > > different names. So in terms of the script I thought it would make sense > to > > just have distinct names for the executables no matter which option they > > chose. > > Yes, but... if you're going to have 2 separate executables, > with different names. Why bother with the environment variable > at all? Just include both executables (e.g. /usr/bin/appname and > /usr/bin/appname-posix) in your package, and mention in README that > there are two, and give both their names. Users who prefer the -posix > version can just type "appname-posix" to use it, and users who don't > care can just type "appname"... > > It'd be different if they were mutually exclusive, a compiled program > that either has or does not have some option built in. Or if your > programs were huge and took up a lot of disk space, so a user might > care about not installing the one he doesn't need. > > In the absence of such concerns, go with simplicity: don't force a > user to make a choice if it's trivial to avoid it. If I were a new > user of your app that you're packaging, I'd have no idea whether > I wanted the regular or -posix version, so I'd either go with the > default (most people do), or have to spend time & effort researching > the alternative. > > Slackware for instance includes two emacs executables (emacs-with-X11 > and emacs-no-X11), and two strings commands (strings-BSD and > strings-GNU)... although those are more complex examples, using > symlinks. You won't need symlinks, it doesn't sound like. > That's true. I did think I could make installing both the default. If the user wants to install only one version they could specify which with an environment variable otherwise no environment variable is used. This does feel overengineered considering the small size of the executables, etc. The only other justification I can think of to give the user a choice would be minimalism. But this kind of minimalism isn't part of the Slackware philosophy. Thanks for talking it through with me. I'll just have the script install both. KISS. > > > I didn't realize there were that many slackbuilds. That's impressive! > > They sorta grew beyond expectations, but that just means we're doing > something right. > I did notice looking for software that isn't packaged for Slackware is quite difficult. Most of the time when I go looking it's available on SBo. There's quite an increase of activity on the Slackware sub-forum since the release of 15.0. Hopefully it will continue to attract new users and bring back old users leading to more SBo maintainers. > _______________________________________________ > 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 ozan.turkyilmaz at gmail.com Thu Mar 24 07:11:31 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Thu, 24 Mar 2022 10:11:31 +0300 Subject: [Slackbuilds-users] Updated ftbfs list In-Reply-To: References: Message-ID: <9dd52873c1b7983119cd355edf2fdd9d58a365fc.camel@gmail.com> ?r?, 2022-03-23 tarihinde 16:50 -0400 saatinde, B. Watson yazd?: > > Fixed a few of these, removed a few: > > https://slackware.uk/~urchlay/src/ftbfs.32bit.20220323 > News on HandBrake: First of all, it seems HandBrake does not support 32bit compile anymore [1]. However, someone did get it compile it as 32bit [2] with disabling x265. I know x265 itself builds actually, if we can find a way to force it using the system x265 and we will be fine. Regards, Ozan [1] https://github.com/HandBrake/HandBrake/issues/1363 [2] https://git.archlinux32.org/packages/tree/community/handbrake/PKGBUILD From ozan.turkyilmaz at gmail.com Thu Mar 24 12:47:18 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Thu, 24 Mar 2022 15:47:18 +0300 Subject: [Slackbuilds-users] Updated ftbfs list In-Reply-To: References: Message-ID: ?r?, 2022-03-23 tarihinde 16:50 -0400 saatinde, B. Watson yazd?: > > Fixed a few of these, removed a few: > > https://slackware.uk/~urchlay/src/ftbfs.32bit.20220323 > I digged around the eduke32 a little bit. It fails at the linking of tools. I tried adding baselayer.cpp to the GNUMakefile but not really worked. This time the compiler compiler complined about multible definition of "initputs" and "initprintf". /usr/bin/ld: obj/build/baselayer.o (symbol from plugin): in function `baselayer_osdcmd_vidmode_func': (.text+0x0): multiple definition of `initputs'; obj/tools/compat_tools.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: obj/build/baselayer.o (symbol from plugin): in function `baselayer_osdcmd_vidmode_func': (.text+0x0): multiple definition of `initprintf'; obj/tools/compat_tools.o (symbol from plugin):(.text+0x0): first defined here Definitely, it needs adjusting the makefile but I am now out of ideas. Regards, Ozan From dave at slackbuilds.org Thu Mar 24 14:15:42 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Thu, 24 Mar 2022 14:15:42 +0000 Subject: [Slackbuilds-users] fcron for 15.0 In-Reply-To: <4cac219a-58b6-7bf8-29c3-4bdf392484db@aaazen.com> References: <4cac219a-58b6-7bf8-29c3-4bdf392484db@aaazen.com> Message-ID: <20220324141542.GA23134@localhost> On 23/03/22 07:18, Richard Narron put forth the proposition: > On Tue, 22 Mar 2022, Michel BEGUE wrote: > > fcron does not build. > > just a line to add to ./configure > > " --with-sendmail=/usr/sbin/postfix " > I do not get any errors in building 3.3.0 > With postfix installed, the fcron 3.3.0 build finds sendmail at > /usr/sbin/sendmail. > What error did you get building fcron 3.3.0? Hi I also assumed that because sendmail is in extra/ now, that postfix would be the correct binary to use, but it seems that postfix comes with it's own version of sendmail. I'll revert that change. If /usr/sbin/sendmail doesn't exist, then reinstalling postfix ought to fix it. -- Dave From 1.41421 at gmail.com Thu Mar 24 16:54:05 2022 From: 1.41421 at gmail.com (Luveh Keraph) Date: Thu, 24 Mar 2022 10:54:05 -0600 Subject: [Slackbuilds-users] Question about Brave browser Message-ID: I have installed the Brave browser in my 15.0 system using the Slackbuilds software for the purpose. I noticed that, after the installation is completed, some MIME handling settings are silently changed: $ xdg-mime query default x-scheme-handler/http brave-browser.desktop $ xdg-mime query default x-scheme-handler/https brave-browser.desktop Before installing Brave, the output of these commands was, in my case, chromium.desktop. The default browser setting remains unchanged though: $ xdg-settings get default-web-browser chromium.desktop The above changes imply that when clicking on a link embedded in an email in Thunderbird, the Brave browser will be launched, instead of whatever was the default before - Chromium, in my case. This is OK if you want to use the Brave browser for that purpose. It is, however, a bit annoying that the changes are carried out under the wraps and without asking the person in charge of the installation of this browser whether such an action is what one wants to do - installing a browser does not necessarily mean that it is meant to become the default browser for MIME data handling. It is easy enough to restore the MIME settings to what they were - in my case I would do $ xdg-mime default chromium.desktop x-scheme-handler/http $ xdg-mime default chromium.desktop x-scheme-handler/https However, it would be nice if the installation software were not to change the MIME settings silently, or, at the very least, for the documentation in the Slackbuilds installer to warn about this action and explain how to revert it. Looking into the files in the Slackbuilds installation software it would seem that doinst.sh has something to do with all this, but being totally ignorant about such issues, I wouldn't know - the xdg-mime recipes that I mentioned I got from a network search, they work for me, and that's all I know about them. -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Thu Mar 24 18:49:00 2022 From: urchlay at slackware.uk (B. Watson) Date: Thu, 24 Mar 2022 14:49:00 -0400 (EDT) Subject: [Slackbuilds-users] 32-bit fails, updated list Message-ID: HandBrake - asm code fails to build, in the x265 sub-make (and --disable-asm doesn't fix it). nix - multiple issues, broken on both 32-bit and 64-bit, see https://slackware.uk/~urchlay/src/nix.32bit.fail.log and https://slackware.uk/~urchlay/src/nix.64bit.write.to.usr.log openjdk6 - bedlam is testing now, initial report is 'still broken'... openjdk7 - FTBFS, it's using gcc-5, but trying to link with /usr/lib/libstdc++.so instead of the one in /usr/lib/gcc/i586-slackware-linux/5.5.0/libstdc++.so openjdk8 - can't test, needs openjdk8 first. wgettable version here: https://slackware.uk/~urchlay/src/ftbfs.32bit.20220324 From mab974 at gmail.com Thu Mar 24 19:09:37 2022 From: mab974 at gmail.com (mab974) Date: Thu, 24 Mar 2022 23:09:37 +0400 Subject: [Slackbuilds-users] fcron for 15.0 In-Reply-To: <4cac219a-58b6-7bf8-29c3-4bdf392484db@aaazen.com> References: <4cac219a-58b6-7bf8-29c3-4bdf392484db@aaazen.com> Message-ID: <20220324230937.12ee47d386e1357da5bbec94@gmail.com> Selon Richard Narron : > On Tue, 22 Mar 2022, Michel BEGUE wrote: > > > fcron does not build. > > just a line to add to ./configure > > " --with-sendmail=/usr/sbin/postfix " > > I do not get any errors in building 3.3.0 > > With postfix installed, the fcron 3.3.0 build finds sendmail at > /usr/sbin/sendmail. > > What error did you get building fcron 3.3.0? > > > and maybe get to v3.3.1. > > This is a good idea. I am waiting to be able to update my scripts... > > Richard Narron Sorry, I?m trying to find the exact build conditions. I?m not near my computer right now. Michel From mab974 at gmail.com Thu Mar 24 19:24:12 2022 From: mab974 at gmail.com (mab974) Date: Thu, 24 Mar 2022 23:24:12 +0400 Subject: [Slackbuilds-users] new email address Message-ID: <20220324232412.20462bd4c1a8de4c310b8c1f@gmail.com> Hi, I intend to change my email address. Is it possible to change it globally in all the packages I am the maintainer? Or do I have to do it in my next updates? Michel -*- mab974 From urchlay at slackware.uk Thu Mar 24 20:39:38 2022 From: urchlay at slackware.uk (B. Watson) Date: Thu, 24 Mar 2022 16:39:38 -0400 (EDT) Subject: [Slackbuilds-users] 32-bit fails, updated list In-Reply-To: References: Message-ID: On Thu, 24 Mar 2022, B. Watson wrote: > HandBrake - asm code fails to build, in the x265 sub-make (and --disable-asm > doesn't fix it). Remove this from the list, it's fixed in my git branch. From fourtysixandtwo at sliderr.net Thu Mar 24 21:05:07 2022 From: fourtysixandtwo at sliderr.net (fourtysix andtwo) Date: Thu, 24 Mar 2022 15:05:07 -0600 Subject: [Slackbuilds-users] rmlmmc, smlnj, and mlton Message-ID: Hi, Has anyone been able to build all three of these slackbuilds on 15.0? Interesting mix of REQUIRES and 32/64-bit issues. mlton: -builds from source on x86_64 only with binary of itself smlnj: -older version that did not support x86_64 -also ftbfs on 32-bit -updated version to 110.99.2 builds in 32 and 64-bit -32-bit did require -j1 to be set before building successfully rmlmmc: -REQUIRES: smlnj and mlton -64-bit is unsupported -ftbfs in 32-bit -would appear to be latest version available Cheers. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at linux.com Thu Mar 24 23:00:37 2022 From: chris.willing at linux.com (Christoph Willing) Date: Fri, 25 Mar 2022 09:00:37 +1000 Subject: [Slackbuilds-users] Updated ftbfs list - pixma In-Reply-To: References: Message-ID: On 24/3/22 06:50, B. Watson wrote: > > Fixed a few of these, removed a few: > > https://slackware.uk/~urchlay/src/ftbfs.32bit.20220323 > > Same URL as previous version of the list, make sure you're not working > from an outdated copy. pixma can be removed from the list. I've just pushed a 32bit fix to my updates branch. chris From urchlay at slackware.uk Fri Mar 25 07:19:24 2022 From: urchlay at slackware.uk (B. Watson) Date: Fri, 25 Mar 2022 03:19:24 -0400 (EDT) Subject: [Slackbuilds-users] Updated ftbfs list In-Reply-To: <9dd52873c1b7983119cd355edf2fdd9d58a365fc.camel@gmail.com> References: <9dd52873c1b7983119cd355edf2fdd9d58a365fc.camel@gmail.com> Message-ID: <1ed2320-f2be-598b-e629-534defd98ed8@slackware.uk> On Thu, 24 Mar 2022, Ozan T?rky?lmaz wrote: > News on HandBrake: > First of all, it seems HandBrake does not support 32bit compile anymore > [1]. However, someone did get it compile it as 32bit [2] with disabling > x265. I know x265 itself builds actually, if we can find a way to force > it using the system x265 and we will be fine. That's actually what I did. Debian's got a patch for HandBrake that makes it use system libraries for everything it bundles... I adapted that patch, made it only use the system x265. It might be better to use the whole patch, and make HandBrake depend on only system libraries, but that would be something for the maintainer to try, not me (I just made it build with the minimum possible change). From urchlay at slackware.uk Fri Mar 25 07:21:46 2022 From: urchlay at slackware.uk (B. Watson) Date: Fri, 25 Mar 2022 03:21:46 -0400 (EDT) Subject: [Slackbuilds-users] 32-bit fails Message-ID: I've just pushed a fix for nix, so it looks like the only remaining 32-bit FTBFS from our original list are: openjdk6 openjdk7 openjdk8 ...though we've got some new ones reported today :( From ozan.turkyilmaz at gmail.com Fri Mar 25 07:37:19 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Fri, 25 Mar 2022 07:37:19 +0000 Subject: [Slackbuilds-users] Updated ftbfs list In-Reply-To: <1ed2320-f2be-598b-e629-534defd98ed8@slackware.uk> References: <9dd52873c1b7983119cd355edf2fdd9d58a365fc.camel@gmail.com> <1ed2320-f2be-598b-e629-534defd98ed8@slackware.uk> Message-ID: Cum, 2022-03-25 tarihinde 03:19 -0400 saatinde, B. Watson yazd?: > On Thu, 24 Mar 2022, Ozan T?rky?lmaz wrote: > > > News on HandBrake: > > First of all, it seems HandBrake does not support 32bit compile > > anymore > > [1]. However, someone did get it compile it as 32bit [2] with > > disabling > > x265. I know x265 itself builds actually, if we can find a way to > > force > > it using the system x265 and we will be fine. > > That's actually what I did. Debian's got a patch for HandBrake that > makes it use system libraries for everything it bundles... I adapted > that patch, made it only use the system x265. > > It might be better to use the whole patch, and make HandBrake > depend on only system libraries, but that would be something for > the maintainer to try, not me (I just made it build with the minimum > possible change). Yes, that is the debian method also Arch32 uses the same method. I would prefer using the system labraries for whole but then again most media upstreams prefer to use their own internal versions. Regards, Ozan From ozan.turkyilmaz at gmail.com Fri Mar 25 07:40:19 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Fri, 25 Mar 2022 07:40:19 +0000 Subject: [Slackbuilds-users] 32-bit fails In-Reply-To: References: Message-ID: Cum, 2022-03-25 tarihinde 03:21 -0400 saatinde, B. Watson yazd?: > > I've just pushed a fix for nix, so it looks like the only remaining > 32-bit FTBFS from our original list are: > > openjdk6 > openjdk7 > openjdk8 > > ...though we've got some new ones reported today :( Looking at the upstream sources, a lot of project simply drops 32 bit compiles or tests all too gether. NOt having hardware also adds to this. Debian already at the edge of dropping 32 bit. Wine also started working on making 32 bit libs work using 64 bit versions using trunking (pretty much how MS did their multi lib system with Windows on Windows). We are close to end of an era now. Regards, Ozan From urchlay at slackware.uk Fri Mar 25 15:56:06 2022 From: urchlay at slackware.uk (B. Watson) Date: Fri, 25 Mar 2022 11:56:06 -0400 (EDT) Subject: [Slackbuilds-users] 32-bit fails In-Reply-To: References: Message-ID: <37f575ff-935-bd52-482c-c2182c75679@slackware.uk> On Fri, 25 Mar 2022, Ozan T?rky?lmaz wrote: > Looking at the upstream sources, a lot of project simply drops 32 bit > compiles or tests all too gether. We've run into that in a few cases in our attempt to fix all the 32-bit fails. In a few cases (pdns, pdns-recursor, heimdal), 32-bit support is broken because of the y2k38 bug, either by accident or on purpose. I went ahead and allowed those 3 to build on 32-bit, because it's only 2022 now. The y2k38 issue... there's now kernel support for a 64-bit time_t on 32-bit, but AFAICT no support in glibc. There's also another problem: anything with the y2k38 bug that tries to validate an SSL cert whose expiration date is past 2038, will fail. That's the reason heimdal wouldn't build: the code was fine, but the certs used by the test suite have an expiration date 500 years in the future... This looks interesting, though it's from 2015: https://lwn.net/Articles/664800/ > NOt having hardware also adds to this. Eh, I never heard of an x86_64 CPU that doesn't also support 32-bit x86. They have the hardware... but they may not have the time (or desire) to maintain a 32-bit container/VM/chroot for testing 32-bit builds. > Debian already at the edge of dropping 32 bit. Wine also started > working on making 32 bit libs work using 64 bit versions using trunking > (pretty much how MS did their multi lib system with Windows on > Windows). We are close to end of an era now. Didn't know that about Wine, that'll be nice to have when it's working. No more need for multilib or a VM with a full windows install just to play a couple of games I bought last century. I'm assuming SBo will continue to support 32-bit as long as Slackware does, and no longer. From mab974 at gmail.com Fri Mar 25 17:32:56 2022 From: mab974 at gmail.com (mab974) Date: Fri, 25 Mar 2022 21:32:56 +0400 Subject: [Slackbuilds-users] fcron for 15.0 In-Reply-To: <20220324230937.12ee47d386e1357da5bbec94@gmail.com> References: <4cac219a-58b6-7bf8-29c3-4bdf392484db@aaazen.com> <20220324230937.12ee47d386e1357da5bbec94@gmail.com> Message-ID: <20220325213256.c5b3bb5ec00492beeeede798@gmail.com> Selon mab974 : > Selon Richard Narron : > > On Tue, 22 Mar 2022, Michel BEGUE wrote: > > > > > fcron does not build. > > > just a line to add to ./configure > > > " --with-sendmail=/usr/sbin/postfix " > > > > I do not get any errors in building 3.3.0 > > > > With postfix installed, the fcron 3.3.0 build finds sendmail at > > /usr/sbin/sendmail. > > > > What error did you get building fcron 3.3.0? > > > > > and maybe get to v3.3.1. > > > > This is a good idea. I am waiting to be able to update my scripts... > > > > Richard Narron > > Sorry, I?m trying to find the exact build conditions. > I?m not near my computer right now. > > Michel Sorry. I have run 'sudo ./fcron.SlackBuild' and postfix is not accessible. 'su -c ./fcron.SlackBuild' is better. my apologies to Richard and Dave. Michel -*- From matteo.bernardini at gmail.com Fri Mar 25 19:14:38 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 25 Mar 2022 20:14:38 +0100 Subject: [Slackbuilds-users] fcron for 15.0 In-Reply-To: <20220325213256.c5b3bb5ec00492beeeede798@gmail.com> References: <4cac219a-58b6-7bf8-29c3-4bdf392484db@aaazen.com> <20220324230937.12ee47d386e1357da5bbec94@gmail.com> <20220325213256.c5b3bb5ec00492beeeede798@gmail.com> Message-ID: Il giorno ven 25 mar 2022 alle ore 18:33 mab974 ha scritto: > Selon mab974 : > > Selon Richard Narron : > > > On Tue, 22 Mar 2022, Michel BEGUE wrote: > > > > > > > fcron does not build. > > > > just a line to add to ./configure > > > > " --with-sendmail=/usr/sbin/postfix " > > > > > > I do not get any errors in building 3.3.0 > > > > > > With postfix installed, the fcron 3.3.0 build finds sendmail at > > > /usr/sbin/sendmail. > > > > > > What error did you get building fcron 3.3.0? > > > > > > > and maybe get to v3.3.1. > > > > > > This is a good idea. I am waiting to be able to update my > scripts... > > > > > > Richard Narron > > > > Sorry, I?m trying to find the exact build conditions. > > I?m not near my computer right now. > > > > Michel > > Sorry. > I have run 'sudo ./fcron.SlackBuild' and postfix is not accessible. > 'su -c ./fcron.SlackBuild' is better. > > my apologies to Richard and Dave. > > Michel > -*- > Hi Michel, please have a look at the HOWTO https://slackbuilds.org/howto/ the last paragraph of "Step 4" in particular Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From lenardrspencer at gmail.com Fri Mar 25 20:29:03 2022 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Fri, 25 Mar 2022 16:29:03 -0400 Subject: [Slackbuilds-users] 32-bit fails In-Reply-To: References: Message-ID: I'm trying something with openjdk7, and I'll know if it works when I get home later tonight. On Fri, Mar 25, 2022, 03:21 B. Watson wrote: > > I've just pushed a fix for nix, so it looks like the only remaining > 32-bit FTBFS from our original list are: > > openjdk6 > openjdk7 > openjdk8 > > ...though we've got some new ones reported today :( > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Mar 26 02:31:07 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 26 Mar 2022 09:31:07 +0700 Subject: [Slackbuilds-users] Updates - 20220326.1 Message-ID: <19aba1cc-55d0-20bb-0783-bb5141b1c977@slackbuilds.org> Hello everyone, Another week and we finally managed to trim down the FTBFS list and i think we only have openjdk{6,7,8} left on our list and the maintainer is looking into it now. If you notice more failures, please let us know. With that said, we are ready to open submission for 15.0 repository. All scripts must be tested against full installation of Slackware{64}-15.0 with latest patches applied. New submission should go into submission form, while future updates can be done via github pull requests or gitlab merge requests. Make sure to use the latest TEMPLATE files here: https://slackbuilds.org/templates/ If you want to send patches to SBo mailing list, please use git format-patch. I wrote a simple tutorial here: https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html Please note that we may have changed your scripts during development cycle to make sure it compiles according to our policy. Please make sure to check the changes and don't revert our changes back. Happy building and have a great weekend :) Sat Mar 26 01:58:27 UTC 2022 academic/SU2: Mark as 64-bit only. academic/arpack: Disable parallel build. academic/qucs: Align to template. academic/ugene: Mark 32bit as UNSUPPORTED. academic/z3: Updated for version 4.8.12. audio/deadbeef: Fix 32-bit build. audio/google-musicmanager: Fix 32-bit build. audio/google-musicmanager: Fix VERSION+MD5SUM. audio/guitarix: Fix 32-bit build. audio/helm: Fix 32-bit build. audio/sbagen: Fix 32-bit build. desktop/bumblebee-status: Fix SLKCFLAGS -02 typo. desktop/kwalletcli: Fix 32-bit build. development/atom-amd64: Updated for version 1.60.0. development/avr8-gnu-toolchain: Fix download URL. development/cf-cli: Fix ARCH detection. development/crystal-lang: Fix ARCH detection. development/crystal-lang: Fix BUILD usage. development/energia: Update ARCH handling. development/gforth: Disable parallel build. development/guile1.8: Fix build on 32 bit. development/icon: Disable parallel build. development/jupyter-ipykernel: Update for 6.9.2 development/jupyter-nbconvert: Update for 6.4.4 development/jupyter-nbformat: Update for 5.2.0 development/jupyter-notebook: Update for 6.4.10 development/jupyter_core: Update for 4.9.2 development/maude: Fix 32-bit build. development/neovim: Updated for version 0.6.1. development/nodejs: Updated for version 17.7.2. development/nsis: Removed (FTBFS; not updated since 2010). development/perf: Fix build with x86 -smp kernel. development/postman: Updated for version 9.15.2 development/ruff: Updated for version 2.2.0. development/sonarqube: i486 => i586. development/vis: Updated for version 0.7. development/xmlcopyeditor: Fix wxPython/wxGTK3 conflict. games/bluez-sixaxis: Remove .la files. games/d1x-rebirth: Fix 32-bit build. games/d2x-rebirth: Fix 32-bit build. games/eduke32: Fix 32-bit build. games/ffgo: Fix doinst.sh. games/fgo: Fix doinst.sh. games/hedgewars: Document different dep on 32-bit. games/hexglass: Fix 32-bit build. games/speed-dreams: Updated MD5SUM. games/waterCloset: Fix 32-bit build. graphics/Blender: Fix 32-bit build (make embree optional). graphics/brlcad: Fix 32bit build. graphics/darktable: Mark as 64-bit only (it really is). graphics/embree: Mark as 64-bit only. graphics/fotowall: Fix 32-bit build. graphics/luminance-hdr: Fix 32-bit build. graphics/mitsuba2: Fix 32-bit build. graphics/nsxiv: Use correct github URL. graphics/opencolorio: Fix 32-bit build. graphics/vuescan: Updated for version 9.7.82. libraries/OpenBLAS: Fix Build on 32 bit. libraries/antlr4: Update DEP. libraries/bctoolbox: Update DOWNLOAD. libraries/belle-sip: Updated DOWNLOAD. libraries/bzrtp: Fix download URL. libraries/libhoard: i486 => i586. libraries/libindi-drivers: Mark 32bit as unsupported. libraries/libpri: Removed (No maintainer and not used). libraries/libsoup3: Updated for version 3.0.5. libraries/lua-lpeg: install lpeg for all luas libraries/msgpack-c: Updated for version 4.0.0. libraries/onevpl: Mark as 64-bit only. libraries/qt5-postgresql: Fix DOWNLOAD url. libraries/xmpppy: Fix SLKCFLAGS -02 typo. misc/moedict-desktop.app: Fix ARCH detection. misc/sbo-templates: Wrap README at 72 columns. misc/stardict: Updated for version 3.0.6 (3.0.6.2 segfaults). multimedia/Gem: Fix build on 32bit. multimedia/HandBrake: Fix 32-bit build. multimedia/cantata: Updated for version 2.5.0. multimedia/minitube: Fix 32-bit build. multimedia/tvheadend: Fix 32-bit build. network/heimdal: Fix 32-bit build. network/icecat: Fix ARCH detection and support. network/opendmarc: Remove .la files. network/opera-legacy: Fix ARCH detection and support. network/pdns-recursor: Fix 32-bit build (until 2038!). network/pdns: Fix 32-bit build (until 2038!). network/pidgin-musictracker: Fix 32-bit build. network/rclone: Updated for version 1.58.0 network/riot-web: Removed at maintainer's request (mailing list). network/rspamd: Add missing patch. network/rspamd: Fix 32-bit build. network/seafile-server: Remove .la files. network/slurm: Fix 32-bit build. network/suricata: Remove .la files. network/teams: Fix glibc compatibility. network/tntnet: Remove .la files. network/tor-browser: Updated for version 11.0.9. network/varnish: Remove .la files. network/wireshark: Updated for version 3.6.3. network/zoom-linux: Updated for version 5.10.0.2450 office/lout: Updated for version 3.42.1. office/pandoc: i486 => i586. python/jedi: Fix renamed dependency reference. python/nbxmpp: Updated for version 2.0.6. python/python3-aiorpcX: Update for 0.22.1 python/terminado: Update for 0.13.3 python/terminado: Wrap README at 72 columns. system/afdko: Fix downloading during build. system/bacula-client: Updated for version 9.6.7. system/bacula: Exit with failure status if user/group don't exist. system/bacula: Updated for version 9.6.7. system/bulk_extractor: Fix 32-bit build. system/commons-daemon: Fix download URLs. system/dahdi-complete: Removed (no maintainer and ftbfs). system/ksh-openbsd: Fix DOWNLOAD. system/libtrash: Align to template. system/multipath-tools: Fix 32-bit build. system/nix: Fix 32-bit build; stop spamming /usr. system/pax: Update EMAIL. system/pixma: Fix 32bit build system/qemu: Update README. system/samsung-mfp-drivers: Updated for version 1.00.39. system/slackrepo-hints: Updated for version 20220325. system/slackrepo: Updated for version 20220325. system/sysdig: Mark 32bit as UNSUPPORTED. system/system76-power: Mark 32bit as unsupported. system/virtualbox-kernel: Mark as 64-bit only. system/virtualbox: Mark as 64-bit only. +--------------------------+ -- 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 ozan.turkyilmaz at gmail.com Sun Mar 27 14:21:04 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Sun, 27 Mar 2022 17:21:04 +0300 Subject: [Slackbuilds-users] 32-bit fails In-Reply-To: <37f575ff-935-bd52-482c-c2182c75679@slackware.uk> References: <37f575ff-935-bd52-482c-c2182c75679@slackware.uk> Message-ID: <71bb66dd178f33d45eef3c504213a53ce3f31df7.camel@gmail.com> Cum, 2022-03-25 tarihinde 11:56 -0400 saatinde, B. Watson yazd?: > > > On Fri, 25 Mar 2022, Ozan T?rky?lmaz wrote: > > The y2k38 issue... there's now kernel support for a 64-bit time_t on > 32-bit, but AFAICT no support in glibc. > That's a big ABI break. I am not surprised they are holding it down. BSD people used binary compatibility layer to handle this ABI break. > > Didn't know that about Wine, that'll be nice to have when it's > working. No more need for multilib or a VM with a full windows > install > just to play a couple of games I bought last century. > They started the work with 7.0. THey are working on converting them all so we can use 32 bit wine without multiblib. THey worry that there wont be 32 bit packages to use soon. > I'm assuming SBo will continue to support 32-bit as long as Slackware > does, and no longer. > Of course! Regards, Ozan From urchlay at slackware.uk Sun Mar 27 15:13:11 2022 From: urchlay at slackware.uk (B. Watson) Date: Sun, 27 Mar 2022 11:13:11 -0400 (EDT) Subject: [Slackbuilds-users] 32-bit fails In-Reply-To: <71bb66dd178f33d45eef3c504213a53ce3f31df7.camel@gmail.com> References: <37f575ff-935-bd52-482c-c2182c75679@slackware.uk> <71bb66dd178f33d45eef3c504213a53ce3f31df7.camel@gmail.com> Message-ID: On Sun, 27 Mar 2022, Ozan T?rky?lmaz wrote: > Cum, 2022-03-25 tarihinde 11:56 -0400 saatinde, B. Watson yazd?: >> >> >> On Fri, 25 Mar 2022, Ozan T?rky?lmaz wrote: >> >> The y2k38 issue... there's now kernel support for a 64-bit time_t on >> 32-bit, but AFAICT no support in glibc. >> > That's a big ABI break. I am not surprised they are holding it down. > BSD people used binary compatibility layer to handle this ABI break. Actually... I looked into it a bit more... we *have* 64-bit time_t support in glibc, on Slackware 15.0. It works like large file support, you "#define _TIME_BITS 64" before including or . Doesn't break the ABI, it causes your code to be compiled with 64-bit versions of the time-related functions (e.g. you write "gettimeofday" and what really gets compiled is a call to a gettimeofday64() function). See https://www.gnu.org/software/libc/manual/html_mono/libc.html and search for TIME_BITS within the page. Also: $ cat 1.c #define _FILE_OFFSET_BITS 64 #define _TIME_BITS 64 #include #include int main(int argc, char **argv) { printf("%lu\n", sizeof(time_t)); return 0; } $ gcc -Wall -o 1 1.c $ ./1 8 ...didn't know this last week, or I would have used it for pdns and and pdns-recursor. Just adding -D_FILE_OFFSET_BITS=64 and -D_TIME_BITS=64 to SLKCFLAGS would be a better fix than what I actually did. From urchlay at slackware.uk Sun Mar 27 15:24:32 2022 From: urchlay at slackware.uk (B. Watson) Date: Sun, 27 Mar 2022 11:24:32 -0400 (EDT) Subject: [Slackbuilds-users] 32-bit fails In-Reply-To: References: <37f575ff-935-bd52-482c-c2182c75679@slackware.uk> <71bb66dd178f33d45eef3c504213a53ce3f31df7.camel@gmail.com> Message-ID: On Sun, 27 Mar 2022, B. Watson wrote: > Actually... I looked into it a bit more... we *have* 64-bit time_t > support in glibc, on Slackware 15.0. It works like large file > support, you "#define _TIME_BITS 64" before including > or . Doesn't break the ABI, it causes your code to be > compiled with 64-bit versions of the time-related functions (e.g. > you write "gettimeofday" and what really gets compiled is a call to a > gettimeofday64() function). Grrrr. Ignore all that I said in that email. It doesn't actually work, we would need a newer glibc for that. I was looking at the manual for glibc-2.35, but our glibc is 2.33. And I thought it worked because I was doing my test compile in the wrong terminal: *not* the one for my 32-bit chroot. Of course my test program said sizeof(time_t) is 8, I was running it on 64-bit. On an *actual* 32-bit Slackware 15.0 system, sizeof(time_t) is still 4 bytes (32-bit), regardless of any -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 stuff. This is why I shouldn't try to think before I've digested at least 2 cups of coffee. From jebrhansen+SBo at gmail.com Sun Mar 27 18:07:33 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 27 Mar 2022 12:07:33 -0600 Subject: [Slackbuilds-users] Updated ftbfs list In-Reply-To: <1ed2320-f2be-598b-e629-534defd98ed8@slackware.uk> References: <9dd52873c1b7983119cd355edf2fdd9d58a365fc.camel@gmail.com> <1ed2320-f2be-598b-e629-534defd98ed8@slackware.uk> Message-ID: On Fri, Mar 25, 2022, 1:19 AM B. Watson wrote: > > > On Thu, 24 Mar 2022, Ozan T?rky?lmaz wrote: > > > News on HandBrake: > > First of all, it seems HandBrake does not support 32bit compile anymore > > [1]. However, someone did get it compile it as 32bit [2] with disabling > > x265. I know x265 itself builds actually, if we can find a way to force > > it using the system x265 and we will be fine. > > That's actually what I did. Debian's got a patch for HandBrake that > makes it use system libraries for everything it bundles... I adapted > that patch, made it only use the system x265. > > It might be better to use the whole patch, and make HandBrake > depend on only system libraries, but that would be something for > the maintainer to try, not me (I just made it build with the minimum > possible change). > Where do you go to find how Debian builds its packages? I know about the AUR for Arch and Gentoo's gitweb. When I was updating handbrake to the latest version to allow building on 15.0, I was hoping to find the ability to use system versions?, but I couldn't find any patches. It seems they existed with Debian, but my google-fu was lacking. Jeremy ? https://www.linuxquestions.org/questions/slackware-14/when-will-https-slackbuilds-org-have-15-0-in-their-repos-4175708745/page3.html#post6335052 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From luc.vanrompaey at gmail.com Sun Mar 27 18:24:15 2022 From: luc.vanrompaey at gmail.com (Luc Van Rompaey) Date: Sun, 27 Mar 2022 20:24:15 +0200 Subject: [Slackbuilds-users] Updated ftbfs list In-Reply-To: References: <9dd52873c1b7983119cd355edf2fdd9d58a365fc.camel@gmail.com> <1ed2320-f2be-598b-e629-534defd98ed8@slackware.uk> Message-ID: Op zo 27 mrt. 2022 om 20:07 schreef Jeremy Hansen : > On Fri, Mar 25, 2022, 1:19 AM B. Watson wrote: > >> >> >> On Thu, 24 Mar 2022, Ozan T?rky?lmaz wrote: >> >> > News on HandBrake: >> > First of all, it seems HandBrake does not support 32bit compile anymore >> > [1]. However, someone did get it compile it as 32bit [2] with disabling >> > x265. I know x265 itself builds actually, if we can find a way to force >> > it using the system x265 and we will be fine. >> >> That's actually what I did. Debian's got a patch for HandBrake that >> makes it use system libraries for everything it bundles... I adapted >> that patch, made it only use the system x265. >> >> It might be better to use the whole patch, and make HandBrake >> depend on only system libraries, but that would be something for >> the maintainer to try, not me (I just made it build with the minimum >> possible change). >> > > Where do you go to find how Debian builds its packages? I know about the > AUR for Arch and Gentoo's gitweb. > > When I was updating handbrake to the latest version to allow building on > 15.0, I was hoping to find the ability to use system versions?, but I > couldn't find any patches. It seems they existed with Debian, but my > google-fu was lacking. > > Jeremy > > ? > https://www.linuxquestions.org/questions/slackware-14/when-will-https-slackbuilds-org-have-15-0-in-their-repos-4175708745/page3.html#post6335052 > >> _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > I would go to https://www.debian.org/distrib/packages and scroll down to "Search package directories". There you can enter a keyword (e.g., "Handbrake", verify that the "Package names only" option is selected, and click "Search". On the next page, select the Handbrake package. On the right-hand side, you will see links to various resources, among which the source package. If Debian applied any patches, then these should be available in the "debian.tar.xz" file. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sun Mar 27 18:49:03 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 27 Mar 2022 20:49:03 +0200 Subject: [Slackbuilds-users] Updated ftbfs list In-Reply-To: References: <9dd52873c1b7983119cd355edf2fdd9d58a365fc.camel@gmail.com> <1ed2320-f2be-598b-e629-534defd98ed8@slackware.uk> Message-ID: Il giorno dom 27 mar 2022 alle ore 20:07 Jeremy Hansen < jebrhansen+SBo at gmail.com> ha scritto: > Where do you go to find how Debian builds its packages? I know about the > AUR for Arch and Gentoo's gitweb. > there's also https://sources.debian.org there search for handbrake, click on the package name, then on the latest version (usually sid is ok) and then on the "debian folder" with the build stuff. there you will have the "rules" file with the build rules and the "patches" folder with the patches used (there's also usually a "series" file with the patching order). Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Sun Mar 27 18:59:18 2022 From: didier at slint.fr (Didier Spaier) Date: Sun, 27 Mar 2022 20:59:18 +0200 Subject: [Slackbuilds-users] Updated ftbfs list In-Reply-To: References: <9dd52873c1b7983119cd355edf2fdd9d58a365fc.camel@gmail.com> <1ed2320-f2be-598b-e629-534defd98ed8@slackware.uk> Message-ID: <951d598a-5022-733c-463b-5aafe20830d7@slint.fr> Le 27/03/2022 ? 20:24, Luc Van Rompaey a ?crit?: > > I would go to https://www.debian.org/distrib/packages > and scroll down to "Search package > directories". There you can enter a keyword (e.g., "Handbrake", verify that the > "Package names only" option is selected, and click "Search". > On the next page, select the Handbrake package. On the right-hand side, you will > see links to various resources, among which the source package. > If Debian applied any patches, then these should be available in the > "debian.tar.xz" file. Or just web search "handbrake debian package" This leads to https://packages.debian.org/search?keywords=handbrake I would select the sid (aka -current) edition which leads to: https://packages.debian.org/sid/handbrake then on the right you have download links for the source package In this case I would select http://deb.debian.org/debian/pool/main/h/handbrake/handbrake_1.5.1+ds1-1.debian.tar.xz this untar to a debian diractory in which is a sub-directory patches. To apply them all: while read patch; do patch -p1 --verbose $CWD/debian/patches/$patch || exit 1 done < $CWD/debian/patches/series Didier From lenardrspencer at gmail.com Sun Mar 27 19:02:22 2022 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Sun, 27 Mar 2022 15:02:22 -0400 Subject: [Slackbuilds-users] 32-bit fails In-Reply-To: <71bb66dd178f33d45eef3c504213a53ce3f31df7.camel@gmail.com> References: <37f575ff-935-bd52-482c-c2182c75679@slackware.uk> <71bb66dd178f33d45eef3c504213a53ce3f31df7.camel@gmail.com> Message-ID: I am now officially asking for help on openjdk7 32-bit. When it is linking the launcher, it wants to link in libstdc++.so from /usr/lib (from gcc11), instead of /usr/lib/gcc/i586-slackware-linux/5.5.0 (same with openjdk6). They built fine with -current back on June 8. Openjdk8 builds fine with zulu-openjdk7, with the proper adjustment in the SB script. Unfortunately, there is no 32-bit zulu-openjdk6 available to be able to build openjdk7 on 32-bit. If all fails, unless anything on SBo absolutely needs openjdk 6 or 7, we may have to just drop those two. On Sun, Mar 27, 2022 at 10:21 AM Ozan T?rky?lmaz wrote: > Cum, 2022-03-25 tarihinde 11:56 -0400 saatinde, B. Watson yazd?: > > > > > > On Fri, 25 Mar 2022, Ozan T?rky?lmaz wrote: > > > > The y2k38 issue... there's now kernel support for a 64-bit time_t on > > 32-bit, but AFAICT no support in glibc. > > > That's a big ABI break. I am not surprised they are holding it down. > BSD people used binary compatibility layer to handle this ABI break. > > > > Didn't know that about Wine, that'll be nice to have when it's > > working. No more need for multilib or a VM with a full windows > > install > > just to play a couple of games I bought last century. > > > They started the work with 7.0. THey are working on converting them all > so we can use 32 bit wine without multiblib. THey worry that there wont > be 32 bit packages to use soon. > > > I'm assuming SBo will continue to support 32-bit as long as Slackware > > does, and no longer. > > > Of course! > > Regards, > Ozan > > _______________________________________________ > 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 urchlay at slackware.uk Sun Mar 27 20:13:13 2022 From: urchlay at slackware.uk (B. Watson) Date: Sun, 27 Mar 2022 16:13:13 -0400 (EDT) Subject: [Slackbuilds-users] Updated ftbfs list In-Reply-To: References: <9dd52873c1b7983119cd355edf2fdd9d58a365fc.camel@gmail.com> <1ed2320-f2be-598b-e629-534defd98ed8@slackware.uk> Message-ID: On Sun, 27 Mar 2022, Jeremy Hansen wrote: > > Where do you go to find how Debian builds its packages? I know about the AUR > for Arch and Gentoo's gitweb. Search for the package name on https://www.debian.org/distrib/packages > When I was updating handbrake to the latest version to allow building on > 15.0, I was hoping to find the ability to use system versions?, but I > couldn't find any patches. It seems they existed with Debian, but my > google-fu was lacking. When you find the package in the Debian search, click on the version you want (the version you're packaging for SBo, if it exists), and on the details page there's a "Download Source Package" section... the debian patches are found inside the file with a name like "whatever_1.2.3-1.debian.tar.xz" Sometimes it's a .tar.gz, sometimes it's a .diff.gz, sometimes there's extra components in the version number (dfsg shows up a lot), but you get the idea. The HandBrake patch I based mine on is in the handbrake_1.5.1+ds1-1.debian.tar.xz tarball, as debian/patches/0001-Remove-embedded-downloaded-copies-of-various-librari.patch Hope this helps. I probably should write it up in more detail and post it somewhere more permanent than this... From urchlay at slackware.uk Sun Mar 27 20:35:52 2022 From: urchlay at slackware.uk (B. Watson) Date: Sun, 27 Mar 2022 16:35:52 -0400 (EDT) Subject: [Slackbuilds-users] 32-bit fails In-Reply-To: References: <37f575ff-935-bd52-482c-c2182c75679@slackware.uk> <71bb66dd178f33d45eef3c504213a53ce3f31df7.camel@gmail.com> Message-ID: On Sun, 27 Mar 2022, Lenard Spencer wrote: > If all fails, unless anything on SBo absolutely needs openjdk 6 or 7, we may > have to just drop those two. No, if all else fails, we'd have to mark them as unsupported on 32-bit. They build fine on 64-bit, don't they? It'd be nicer to have them building on 32-bit... you're running into the same libstdc++ issue I ran into, so at least we can duplicate the problem. That's a step in the right direction. One thing you can try to do. Instead of -lstdc++ in the command, you can replace that with the full path to the actual .so file. Like if it's doing this: gcc -o foo -lstdc++ you can replace that with: gcc -o foo /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/libstdc++.so ...on 64-bit; the path is different on 32-bit of course. Another thing: you can find the correct path to gcc5's libstdc++.so on either 32-bit or 64-bit like so: user at slack64$ gcc-5 --print-file-name libstdc++.so /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/libstdc++.so user at slack32$ gcc-5 --print-file-name libstdc++.so /usr/lib/gcc/i586-slackware-linux/5.5.0/libstdc++.so So in a simpler build script, you could probably do this: sed -i "s,-lstdc++,$( gcc-5 --print-file-name libstdc++.so )," Makefile ...which combines the two. Trouble with the openjdk* builds is that it's a PITA to patch anything due to the multiple tarballs and sha checksums (you had to unpack, patch, repack, then calculate a new checksum and patch the main build). The other potential problem: the command above would fix linking during the build... you'd also want to make sure the *runtime* linker finds the correct libstdc++.so. This may or may not be a problem, you'd run ldd on the binary to find out for sure. If ldd shows libstdc++ from /usr/lib is being used, you'll have to use "-Wl,-rpath". Something like this might do: D=$( dirname $( gcc-5 --print-file-name libstdc++.so )) SLKCFLAGS+=" -L$D -Wl,-rpath $D" The -L tells the compiler what to link with at build time, and the -Wl,-rpath embeds the path to the library in the binary, where it gets applied when the compiled binary is actually run. I'm not even sure whether openjdk7.SlackBuild actually uses SLKCFLAGS, but you get the idea I hope. From chris.willing at linux.com Sun Mar 27 21:41:20 2022 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 28 Mar 2022 07:41:20 +1000 Subject: [Slackbuilds-users] Name clash Message-ID: <00e98d7f-0234-59a1-b77d-8e518cd6c58a@linux.com> After I submitted a new SlackBuild, I checked that it existed in the pending queue. Right after my own submission, I noticed another submission for a SlackBuild which already exists - dcmtk.tar.gz Assuming the new submission is for new _different_ software, the name will have to be changed. chris From fourtysixandtwo at sliderr.net Sun Mar 27 22:16:34 2022 From: fourtysixandtwo at sliderr.net (fourtysix andtwo) Date: Sun, 27 Mar 2022 16:16:34 -0600 Subject: [Slackbuilds-users] failed to download source list Message-ID: Here's a few more I've come across, including the 3 I mentioned in #slackbuilds. #The following are easily fixed with sbofindsrc: development/flawfinder development/latrace development/s51dude network/csync network/mod_auth_kerb network/mod_geoip2 network/pgbouncer network/sslstrip network/webalizer #These two are from the same source, but the site has disappeared: python/xe # http://archive.ubuntu.com/ubuntu/pool/universe/x/xmlelements/xmlelements_0.7.4.orig.tar.gz #has a different filename but the md5sum is a match python/pyfeed #sbofindsrc fixed with alt dl #Original site is gone. There is a fork on github but it's an older version. Found this match instead. network/sniffjoke #dl link error, https://slackware.uk/sbosrcarch/by-name/network/sniffjoke/vecna-sniffjoke-aa2a003.tar.gz #I've attached a patch for these two as the decision was easy. network/unicornscan #updated download link from sourceforge office/treesheets #updated md5sum (noted issue in the README) Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-network-unicornscan-Fix-DOWNLOAD-url.patch Type: text/x-patch Size: 1019 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-office-treesheets-Fixed-MD5SUM.patch Type: text/x-patch Size: 1012 bytes Desc: not available URL: From arnaud.garcia-fernandez at laposte.net Mon Mar 28 00:58:46 2022 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Mon, 28 Mar 2022 00:58:46 +0000 Subject: [Slackbuilds-users] Name clash In-Reply-To: <00e98d7f-0234-59a1-b77d-8e518cd6c58a@linux.com> References: <00e98d7f-0234-59a1-b77d-8e518cd6c58a@linux.com> Message-ID: The submission queue is also for updates. It is mandatory for new packages. - Yth. Le 27 mars 2022 21:41:20 UTC, Christoph Willing a ?crit?: >After I submitted a new SlackBuild, I checked that it existed in the >pending queue. Right after my own submission, I noticed another >submission for a SlackBuild which already exists - dcmtk.tar.gz > >Assuming the new submission is for new _different_ software, the name >will have to be changed. > >chris >_______________________________________________ >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 jebrhansen+SBo at gmail.com Mon Mar 28 01:23:15 2022 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 27 Mar 2022 19:23:15 -0600 Subject: [Slackbuilds-users] Updated ftbfs list In-Reply-To: References: <9dd52873c1b7983119cd355edf2fdd9d58a365fc.camel@gmail.com> <1ed2320-f2be-598b-e629-534defd98ed8@slackware.uk> Message-ID: On Sun, Mar 27, 2022, 2:13 PM B. Watson wrote: > > > On Sun, 27 Mar 2022, Jeremy Hansen wrote: > > > > > Where do you go to find how Debian builds its packages? I know about the > AUR > > for Arch and Gentoo's gitweb. > > Search for the package name on https://www.debian.org/distrib/packages > > > When I was updating handbrake to the latest version to allow building on > > 15.0, I was hoping to find the ability to use system versions?, but I > > couldn't find any patches. It seems they existed with Debian, but my > > google-fu was lacking. > > When you find the package in the Debian search, click on the > version you want (the version you're packaging for SBo, if it > exists), and on the details page there's a "Download Source Package" > section... the debian patches are found inside the file with a name > like "whatever_1.2.3-1.debian.tar.xz" > > Sometimes it's a .tar.gz, sometimes it's a .diff.gz, sometimes there's > extra components in the version number (dfsg shows up a lot), but you > get the idea. > > The HandBrake patch I based mine on is in the > handbrake_1.5.1+ds1-1.debian.tar.xz tarball, as > > debian/patches/0001-Remove-embedded-downloaded-copies-of-various-librari.patch > > Hope this helps. I probably should write it up in more detail and > post it somewhere more permanent than this... > Thanks everyone! I now have new tools in my toolbox. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at linux.com Mon Mar 28 05:06:13 2022 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 28 Mar 2022 15:06:13 +1000 Subject: [Slackbuilds-users] Name clash In-Reply-To: References: <00e98d7f-0234-59a1-b77d-8e518cd6c58a@linux.com> Message-ID: On 28/3/22 10:58, Arnaud via SlackBuilds-users wrote: > The submission queue is also for updates. > It is mandatory for new packages. > > - Yth. > Since I maintain the existing SlackBuild dcmtk and I didn't submit a change, I presume the dcmtk.tar.gz in the pending queue is a new submission (which would result in a name clash). BTW I'm not sure if this is actually a rule, but we generally don't top post in this list. chris > Le 27 mars 2022 21:41:20 UTC, Christoph Willing > a ?crit?: > > After I submitted a new SlackBuild, I checked that it existed in the > pending queue. Right after my own submission, I noticed another > submission for a SlackBuild which already exists - dcmtk.tar.gz > > Assuming the new submission is for new _different_ software, the name > will have to be changed. > > chris > ------------------------------------------------------------------------ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From ozan.turkyilmaz at gmail.com Mon Mar 28 05:49:50 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Mon, 28 Mar 2022 08:49:50 +0300 Subject: [Slackbuilds-users] 32-bit fails In-Reply-To: References: <37f575ff-935-bd52-482c-c2182c75679@slackware.uk> <71bb66dd178f33d45eef3c504213a53ce3f31df7.camel@gmail.com> Message-ID: Paz, 2022-03-27 tarihinde 11:24 -0400 saatinde, B. Watson yazd?: > > Grrrr. Ignore all that I said in that email. It doesn't actually > work, we would need a newer glibc for that. > > I was looking at the manual for glibc-2.35, but our glibc is 2.33. > > And I thought it worked because I was doing my test compile in the > wrong terminal: *not* the one for my 32-bit chroot. Of course my test > program said sizeof(time_t) is 8, I was running it on 64-bit. > > On an *actual* 32-bit Slackware 15.0 system, sizeof(time_t) is > still 4 bytes (32-bit), regardless of any -D_FILE_OFFSET_BITS=64 > -D_TIME_BITS=64 stuff. > That was what I meant having 32 bit hardware. Chroot wont help you. Kernel is still 64 bit and there are differences between running under 32 bit and 64 bit kernels. The second best way is to create a full 32 bit installation under an emulator. The best way is of course having a 32 bit slackware installed on a partition and booting into it. But emulator is the second best thing and will do. Regards, Ozan From urchlay at slackware.uk Mon Mar 28 06:20:48 2022 From: urchlay at slackware.uk (B. Watson) Date: Mon, 28 Mar 2022 02:20:48 -0400 (EDT) Subject: [Slackbuilds-users] 32-bit fails In-Reply-To: References: <37f575ff-935-bd52-482c-c2182c75679@slackware.uk> <71bb66dd178f33d45eef3c504213a53ce3f31df7.camel@gmail.com> Message-ID: <41adc388-2bc3-ee9-c062-75c94fe82a2d@slackware.uk> On Mon, 28 Mar 2022, Ozan T?rky?lmaz wrote: > > That was what I meant having 32 bit hardware. Chroot wont help you. > Kernel is still 64 bit and there are differences between running under > 32 bit and 64 bit kernels. The second best way is to create a full 32 > bit installation under an emulator. The best way is of course having a > 32 bit slackware installed on a partition and booting into it. But > emulator is the second best thing and will do. Nah, my 32-bit chroot correctly reports time_t is 32 bits. I run it with "linux32 chroot /path/to/os". Anything that checks the CPU type (e.g. uname -m) will see i686. Even if it didn't, sizeof(time_t) in 32-bit glibc is 32 bits because that's how it's defined in whichever header actually defines it. The trouble was, I was running my test compiles outside of the chroot entirely (on my regular 64-bit install). So of course my code reports time_t is 64 bits there... From willysr at slackbuilds.org Mon Mar 28 10:31:35 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 28 Mar 2022 17:31:35 +0700 Subject: [Slackbuilds-users] Name clash In-Reply-To: References: <00e98d7f-0234-59a1-b77d-8e518cd6c58a@linux.com> Message-ID: > Since I maintain the existing SlackBuild dcmtk and I didn't submit a > change, I presume the dcmtk.tar.gz in the pending queue is a new > submission (which would result in a name clash). > > BTW I'm not sure if this is actually a rule, but we generally don't top > post in this list. I don't see any dcmtk in pending (https://slackbuilds.org/pending/) nor in ready (https://slackbuilds.org/ready/) -- 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 matteo.bernardini at gmail.com Mon Mar 28 10:41:44 2022 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 28 Mar 2022 12:41:44 +0200 Subject: [Slackbuilds-users] Name clash In-Reply-To: References: <00e98d7f-0234-59a1-b77d-8e518cd6c58a@linux.com> Message-ID: Robby removed it ;-) Il lun 28 mar 2022, 12:31 Willy Sudiarto Raharjo ha scritto: > > Since I maintain the existing SlackBuild dcmtk and I didn't submit a > > change, I presume the dcmtk.tar.gz in the pending queue is a new > > submission (which would result in a name clash). > > > > BTW I'm not sure if this is actually a rule, but we generally don't top > > post in this list. > > I don't see any dcmtk in pending (https://slackbuilds.org/pending/) nor > in ready (https://slackbuilds.org/ready/) > > > -- > 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 ozan.turkyilmaz at outlook.com Mon Mar 28 11:00:34 2022 From: ozan.turkyilmaz at outlook.com (Ozan Turkyilmaz) Date: Mon, 28 Mar 2022 11:00:34 +0000 Subject: [Slackbuilds-users] CTAGs Message-ID: <0612002e964f1ceab0ab928cef160791cad55cf8.camel@outlook.com> Hello All, Where is the correct place to put ctags? There's a small update to liboop after years and I went over the script as well. Now it can build ctags for the labrary but I dont really know where to put it. Regards, Ozan From urchlay at slackware.uk Mon Mar 28 14:35:56 2022 From: urchlay at slackware.uk (B. Watson) Date: Mon, 28 Mar 2022 10:35:56 -0400 (EDT) Subject: [Slackbuilds-users] CTAGs In-Reply-To: <0612002e964f1ceab0ab928cef160791cad55cf8.camel@outlook.com> References: <0612002e964f1ceab0ab928cef160791cad55cf8.camel@outlook.com> Message-ID: <673c7f0-bdb9-97c9-909e-da87ea3d66f6@slackware.uk> On Mon, 28 Mar 2022, Ozan Turkyilmaz wrote: > Where is the correct place to put ctags? > There's a small update to liboop after years and I went over the script > as well. Now it can build ctags for the labrary but I dont really know > where to put it. Normally, tags files aren't installed system-wide. The only people who really *need* a tags file for the liboop source are people who are editing the source (its developers, in other words, not users). Are the tags generated for the whole library source, or just the headers? If it's the source, then the library's source would have to be installed somewhere like /usr/src or /usr/share/$PRGNAM/source, and the tags file would have to have the full paths (meaning you'd have to use sed or something to fix it up). If it's just the headers, it would still need the full paths, and it wouldn't be all that useful anyway. If you really want to install them... vim, at least, doesn't have a default global directory for tags. The user would have to add a line to .vimrc to use them, something like: set tags=./tags,./TAGS,tags,TAGS,/usr/share/liboop/tags emacs users would have to do the equivalent (no idea how to do that). From lists at osh.id.au Mon Mar 28 16:21:33 2022 From: lists at osh.id.au (David O'Shaughnessy) Date: Tue, 29 Mar 2022 00:21:33 +0800 Subject: [Slackbuilds-users] wire needs maintainer Message-ID: <9120a9e1-d586-48aa-a41c-1d361f6f838d@www.fastmail.com> Hello, Since I no longer use the program, I'm putting wire up for grabs. It's an easy one (binary repack), not often updated. -- Dave From ozan.turkyilmaz at gmail.com Mon Mar 28 16:56:57 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Mon, 28 Mar 2022 19:56:57 +0300 Subject: [Slackbuilds-users] CTAGs In-Reply-To: <673c7f0-bdb9-97c9-909e-da87ea3d66f6@slackware.uk> References: <0612002e964f1ceab0ab928cef160791cad55cf8.camel@outlook.com> <673c7f0-bdb9-97c9-909e-da87ea3d66f6@slackware.uk> Message-ID: <03dc3ef6088167ec42a669eaaf5481a67b559d40.camel@gmail.com> Pzt, 2022-03-28 tarihinde 10:35 -0400 saatinde, B. Watson yazd?: > > > On Mon, 28 Mar 2022, Ozan Turkyilmaz wrote: > > > Where is the correct place to put ctags? > > There's a small update to liboop after years and I went over the > > script > > as well. Now it can build ctags for the labrary but I dont really > > know > > where to put it. > > Normally, tags files aren't installed system-wide. The only people > who really *need* a tags file for the liboop source are people who > are > editing the source (its developers, in other words, not users). > > Yes, I went against the tag files in the end. Merge request is sent. Regards, Ozan From didier at slint.fr Tue Mar 29 22:07:00 2022 From: didier at slint.fr (Didier Spaier) Date: Wed, 30 Mar 2022 00:07:00 +0200 Subject: [Slackbuilds-users] [ANNOUNCE] Slint needs a translation manager Message-ID: <5b4a35da-8186-475d-db6b-733c8b20ce73@slint.fr> Hi, I know this is off-topic for this list but some could be interested and not all visit LQ. More information there: https://www.linuxquestions.org/questions/slackware-14/%5Bannounce%5D-slint-needs-a-translation-manager-4175710143/ Cheers, Didier From didier at slint.fr Wed Mar 30 12:07:30 2022 From: didier at slint.fr (Didier Spaier) Date: Wed, 30 Mar 2022 14:07:30 +0200 Subject: [Slackbuilds-users] Duplicates Message-ID: Hello, we have SackBuilds for the same python module under two names: https://slackbuilds.org/repository/15.0/development/sphinx_rtd_theme/ https://slackbuilds.org/repository/15.0/python/sphinx-rtd-theme/ The module is named with underscores but on pypi with hyphens. The most recent version is 1.0.0 at time of writing. Additionally, it seems that this module be needed to build the Qemu documentation (this how I came across this duplicate). Cheers, Didier From erich.public at protonmail.com Wed Mar 30 13:45:43 2022 From: erich.public at protonmail.com (Erich Ritz) Date: Wed, 30 Mar 2022 13:45:43 +0000 Subject: [Slackbuilds-users] multimedia/gtk-recordmydesktop: remove? Message-ID: Hi Emmanuel and List, I think either gtk-recordmydesktop should be removed, or else someone needs to add recordmydesktop to SBo.? recordmydesktop was removed from Slackware: Tue Feb 16 20:57:36 UTC 2021 extra/recordmydesktop/recordmydesktop-0.3.8.1-x86_64-4.txz: Removed. There's not much need for this as ssr is better maintained. but the README for gtk-recordmydesktop states: NOTE: This requires recordmydesktop from Slackware's extra directory. If someone (I'm not volunteering - I'm still cleaning out my upgraded installation and noticed this) would like to resurrect it, here is the commit that removed recordmydesktop from SBo when Pat added it to extra: https://git.slackbuilds.org/slackbuilds/commit/?id=ddc52938f60e62674b3e274f96d507da219f5cbd Or perhaps better yet, here is its state when removed from Slackware: https://git.slackware.nl/current/commit/?id=8b03d869e114578be209fde7fe72498970f6998e Erich From urchlay at slackware.uk Wed Mar 30 20:00:02 2022 From: urchlay at slackware.uk (B. Watson) Date: Wed, 30 Mar 2022 16:00:02 -0400 (EDT) Subject: [Slackbuilds-users] failed to download source list In-Reply-To: References: Message-ID: On Sun, 27 Mar 2022, fourtysix andtwo wrote: > Here's a few more I've come across, including the 3 I mentioned in > #slackbuilds. Thanks, applied your patches and fixed the rest in my branch. From milgram at cgpp.com Thu Mar 31 12:04:26 2022 From: milgram at cgpp.com (Judah Milgram) Date: Thu, 31 Mar 2022 08:04:26 -0400 Subject: [Slackbuilds-users] GNU parallel Message-ID: <39459a21-589a-ebb6-910c-18e327e65df3@cgpp.com> Hello, I got interested in trying GNU parallel: https://www.gnu.org/software/parallel/ It doesn't seem to be in 14.2 (haven't upgraded yet) and I don't see a slackbuild for it. Which surprises me. So before downloading and building it (and writing a slackbuild) I thought I check here to see if it was already covered. Is it in 15.0? Or already in 14.2 hiding in plain sight? thanks! Judah From lists at osh.id.au Thu Mar 31 12:27:59 2022 From: lists at osh.id.au (David O'Shaughnessy) Date: Thu, 31 Mar 2022 20:27:59 +0800 Subject: [Slackbuilds-users] GNU parallel In-Reply-To: <39459a21-589a-ebb6-910c-18e327e65df3@cgpp.com> References: <39459a21-589a-ebb6-910c-18e327e65df3@cgpp.com> Message-ID: <735ee258-f41a-439d-b3d9-d46927640328@www.fastmail.com> It's in 15.0, and was added to -current (pre 15.0) back in 2018: Wed Apr 25 04:38:51 UTC 2018 [...] d/parallel-20180422-noarch-1.txz: Added. On Thu, 31 Mar 2022, at 8:04 PM, Judah Milgram wrote: > Hello, > > I got interested in trying GNU parallel: > > https://www.gnu.org/software/parallel/ > > It doesn't seem to be in 14.2 (haven't upgraded yet) and I don't see a > slackbuild for it. Which surprises me. So before downloading and > building it (and writing a slackbuild) I thought I check here to see if > it was already covered. > > Is it in 15.0? Or already in 14.2 hiding in plain sight? > > thanks! > > Judah > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ From milgram at cgpp.com Thu Mar 31 13:37:33 2022 From: milgram at cgpp.com (Judah Milgram) Date: Thu, 31 Mar 2022 09:37:33 -0400 Subject: [Slackbuilds-users] GNU parallel In-Reply-To: <735ee258-f41a-439d-b3d9-d46927640328@www.fastmail.com> References: <39459a21-589a-ebb6-910c-18e327e65df3@cgpp.com> <735ee258-f41a-439d-b3d9-d46927640328@www.fastmail.com> Message-ID: <3ac456d1-b3a8-8a36-867e-1ff09da2c0a4@cgpp.com> OK, thanks! J. On 3/31/22 8:27 AM, David O'Shaughnessy wrote: > It's in 15.0, and was added to -current (pre 15.0) back in 2018: > > Wed Apr 25 04:38:51 UTC 2018 > [...] > d/parallel-20180422-noarch-1.txz: Added. > > > On Thu, 31 Mar 2022, at 8:04 PM, Judah Milgram wrote: >> Hello, >> >> I got interested in trying GNU parallel: >> >> https://www.gnu.org/software/parallel/ >> >> It doesn't seem to be in 14.2 (haven't upgraded yet) and I don't see a >> slackbuild for it. Which surprises me. So before downloading and >> building it (and writing a slackbuild) I thought I check here to see if >> it was already covered. >> >> Is it in 15.0? Or already in 14.2 hiding in plain sight? >> >> thanks! >> >> Judah >> >> _______________________________________________ >> 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/ > -- Judah Milgram milgram at cgpp.com 301-257-7069 From ozan.turkyilmaz at gmail.com Thu Mar 31 16:37:09 2022 From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=) Date: Thu, 31 Mar 2022 19:37:09 +0300 Subject: [Slackbuilds-users] GNU parallel In-Reply-To: <39459a21-589a-ebb6-910c-18e327e65df3@cgpp.com> References: <39459a21-589a-ebb6-910c-18e327e65df3@cgpp.com> Message-ID: <96b0fe518b5a6c75d4f2faeb25c432e38fdbf5af.camel@gmail.com> Pr?, 2022-03-31 tarihinde 08:04 -0400 saatinde, Judah Milgram yazd?: > > > Hello, > t was already covered. > > Is it in 15.0? Or already in 14.2 hiding in plain sight? It is in 15.0. I dont remember 14.2 thou. It's not something I use. Regards, Ozan From b.pribs11 at gmail.com Thu Mar 31 17:11:51 2022 From: b.pribs11 at gmail.com (Brandon Pribula) Date: Thu, 31 Mar 2022 10:11:51 -0700 Subject: [Slackbuilds-users] GNU parallel In-Reply-To: <39459a21-589a-ebb6-910c-18e327e65df3@cgpp.com> References: <39459a21-589a-ebb6-910c-18e327e65df3@cgpp.com> Message-ID: On Thu, Mar 31, 2022, 5:06 AM Judah Milgram, wrote: > > > Hello, > > I got interested in trying GNU parallel: > > https://www.gnu.org/software/parallel/ > > It doesn't seem to be in 14.2 (haven't upgraded yet) and I don't see a > slackbuild for it. Which surprises me. So before downloading and > building it (and writing a slackbuild) I thought I check here to see if > it was already covered. > > Is it in 15.0? Or already in 14.2 hiding in plain sight? > > thanks! > > Judah > > _______________________________________________ > 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/ Just in case you didn't know and would like to see a real world example, the newest version of sbopkg specifically sqg uses gnu parallel. There's a big speed improvement. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrzej at telszewski.com Thu Mar 31 18:06:05 2022 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Thu, 31 Mar 2022 18:06:05 +0000 (UTC) Subject: [Slackbuilds-users] Duplicates In-Reply-To: References: Message-ID: Hi, and two different maintainers, one being me. ;-) I will happily accept whatever decision SBo crew takes. The version with underscores is longer on SBo. On the other hand, version with hyphens is more _upstreamish_. :-) -- Best regards, Andrzej Telszewski From didier at slint.fr Thu Mar 31 19:28:52 2022 From: didier at slint.fr (Didier Spaier) Date: Thu, 31 Mar 2022 21:28:52 +0200 Subject: [Slackbuilds-users] new upstream URL for recode Message-ID: Hello, the version 3.17.2 available in https://github.com/rrthomas/recode can be built on Slackware64-5.O against python3: Built here with sed command in the SlackBuild commented out. Cheers, Didier From slack at giand.it Thu Mar 31 20:23:04 2022 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=) Date: Thu, 31 Mar 2022 22:23:04 +0200 Subject: [Slackbuilds-users] Request to team members: File exists; a submission by the name 'molequeue' is already pending approval Message-ID: <97add266-7960-7193-a62d-c68288596919@giand.it> Hi, I uploaded some slackbuilds for a new package, Avogadro 2, but the slack-desc of two slackbuilds wasn't correctly formatted, then I removed them: avogadroapp, avogadrolibs, and molequeue. Second step I uploaded avogadroapp and avogadrolibs with the slack-desc fixed. However I cannot upload "molequeue.tar.gz" (dependency needed by "avogadrolibs") because it appears already uploaded: *"*File exists; a submission by the name 'molequeue' is already pending approval" But the old tarball has been removed! It appears only in the database of pending istances. Sorry, I surely made a mistake with the removal, but Avogadro 2 cannot be built without molequeue and I can't send this dependency. Please, would you solve the issue? Thanks gian -- ********************************************************* Giancarlo Dess? https://www.giand.it https://twitter.com/gian_d_gian Slackware Linux... because it works! ********************************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From arnaud.garcia-fernandez at laposte.net Thu Mar 31 20:29:37 2022 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Thu, 31 Mar 2022 22:29:37 +0200 Subject: [Slackbuilds-users] Request to team members: File exists; a submission by the name 'molequeue' is already pending approval In-Reply-To: <97add266-7960-7193-a62d-c68288596919@giand.it> References: <97add266-7960-7193-a62d-c68288596919@giand.it> Message-ID: <20220331222937.b90d59df9e1c7dd3b749ec90@laposte.net> > Hi, > > I uploaded some slackbuilds for a new package, Avogadro 2, but the > slack-desc of two slackbuilds wasn't correctly formatted, then I removed > them: avogadroapp, avogadrolibs, and molequeue. Second step I uploaded > avogadroapp and avogadrolibs with the slack-desc fixed. > > However I cannot upload "molequeue.tar.gz" (dependency needed by > "avogadrolibs") because it appears already uploaded: > > *"*File exists; a submission by the name 'molequeue' is already pending > approval" > > But the old tarball has been removed! It appears only in the database of > pending istances. Sorry, I surely made a mistake with the removal, but > Avogadro 2 cannot be built without molequeue and I can't send this > dependency. Please, would you solve the issue? > > Thanks > > gian Hi! Looks like I've got the same problem with python3-tubes, I need to submit it, but I've made a mistake and I can't... - Yth. From dave at slackbuilds.org Thu Mar 31 20:32:34 2022 From: dave at slackbuilds.org (Dave Woodfall) Date: Thu, 31 Mar 2022 21:32:34 +0100 Subject: [Slackbuilds-users] Request to team members: File exists; a submission by the name 'molequeue' is already pending approval In-Reply-To: <97add266-7960-7193-a62d-c68288596919@giand.it> References: <97add266-7960-7193-a62d-c68288596919@giand.it> Message-ID: On 31/03/22 22:23, Giancarlo Dess? put forth the proposition: > Hi, > I uploaded some slackbuilds for a new package, Avogadro 2, but the > slack-desc of two slackbuilds wasn't correctly formatted, then I removed > them: avogadroapp, avogadrolibs, and molequeue. Second step I uploaded > avogadroapp and avogadrolibs with the slack-desc fixed. > However I cannot upload "molequeue.tar.gz" (dependency needed by > "avogadrolibs") because it appears already uploaded: > *"*File exists; a submission by the name 'molequeue' is already pending > approval" > But the old tarball has been removed! It appears only in the database of > pending istances. Sorry, I surely made a mistake with the removal, but > Avogadro 2 cannot be built without molequeue and I can't send this > dependency. Please, would you solve the issue? > Thanks > gian Hi Gian molequeue can't be removed because it's required by the other 2, so they need to be re-removed first and then molequeue removed. -- Dave From slack at giand.it Thu Mar 31 20:44:57 2022 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=) Date: Thu, 31 Mar 2022 22:44:57 +0200 Subject: [Slackbuilds-users] Request to team members: File exists; a submission by the name 'molequeue' is already pending approval In-Reply-To: References: <97add266-7960-7193-a62d-c68288596919@giand.it> Message-ID: <3adf8ced-dff4-3671-e471-7a5edd3b5ba2@giand.it> Il 31/03/22 22:32, Dave Woodfall ha scritto: > On 31/03/22 22:23, > Giancarlo Dess? put forth the proposition: >> Hi, >> I uploaded some slackbuilds for a new package, Avogadro 2, but the >> slack-desc of two slackbuilds wasn't correctly formatted, then I removed >> them: avogadroapp, avogadrolibs, and molequeue. Second step I uploaded >> avogadroapp and avogadrolibs with the slack-desc fixed. >> However I cannot upload "molequeue.tar.gz" (dependency needed by >> "avogadrolibs") because it appears already uploaded: >> *"*File exists; a submission by the name 'molequeue' is already pending >> approval" >> But the old tarball has been removed! It appears only in the database of >> pending istances. Sorry, I surely made a mistake with the removal, but >> Avogadro 2 cannot be built without molequeue and I can't send this >> dependency. Please, would you solve the issue? >> Thanks >> gian > Hi Gian > > molequeue can't be removed because it's required by the other 2, > so they need to be re-removed first and then molequeue removed. I'll remove the other two, but the tarball of molequeue is already removed. I think that the issue was generated because in the first instance I tried to remove molequeue but this failed since avogadroapp and avogadrolibs need it. So, I removed these packages and after molequeue. But only the tarball has been removed. Sorry for my mistake > -- > Dave > _______________________________________________ > 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/ > -- ********************************************************* Giancarlo Dess? https://www.giand.it https://twitter.com/gian_d_gian Slackware Linux... because it works! ********************************************************* From willysr at slackbuilds.org Thu Mar 31 20:45:19 2022 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 1 Apr 2022 03:45:19 +0700 Subject: [Slackbuilds-users] Request to team members: File exists; a submission by the name 'molequeue' is already pending approval In-Reply-To: <97add266-7960-7193-a62d-c68288596919@giand.it> References: <97add266-7960-7193-a62d-c68288596919@giand.it> Message-ID: > I uploaded some slackbuilds for a new package, Avogadro 2, but the > slack-desc of two slackbuilds wasn't correctly formatted, then I removed > them: avogadroapp, avogadrolibs, and molequeue. Second step I uploaded > avogadroapp and avogadrolibs with the slack-desc fixed. > > However I cannot upload "molequeue.tar.gz" (dependency needed by > "avogadrolibs") because it appears already uploaded: > > *"*File exists; a submission by the name 'molequeue' is already pending > approval" > > But the old tarball has been removed! It appears only in the database of > pending istances. Sorry, I surely made a mistake with the removal, but > Avogadro 2 cannot be built without molequeue and I can't send this > dependency. Please, would you solve the issue? Ok, i removed avogadro* and molequeue please resubmit again -- 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 slack at giand.it Thu Mar 31 20:58:16 2022 From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=) Date: Thu, 31 Mar 2022 22:58:16 +0200 Subject: [Slackbuilds-users] Request to team members: File exists; a submission by the name 'molequeue' is already pending approval In-Reply-To: References: <97add266-7960-7193-a62d-c68288596919@giand.it> Message-ID: Il 31/03/22 22:45, Willy Sudiarto Raharjo ha scritto: >> I uploaded some slackbuilds for a new package, Avogadro 2, but the >> slack-desc of two slackbuilds wasn't correctly formatted, then I removed >> them: avogadroapp, avogadrolibs, and molequeue. Second step I uploaded >> avogadroapp and avogadrolibs with the slack-desc fixed. >> >> However I cannot upload "molequeue.tar.gz" (dependency needed by >> "avogadrolibs") because it appears already uploaded: >> >> *"*File exists; a submission by the name 'molequeue' is already pending >> approval" >> >> But the old tarball has been removed! It appears only in the database of >> pending istances. Sorry, I surely made a mistake with the removal, but >> Avogadro 2 cannot be built without molequeue and I can't send this >> dependency. Please, would you solve the issue? > Ok, i removed avogadro* and molequeue > please resubmit again > Well, now it worked resubmissions done, thanks Willy :-) -- ********************************************************* Giancarlo Dess? https://www.giand.it https://twitter.com/gian_d_gian Slackware Linux... because it works! *********************************************************