From lramos.prof at yahoo.com.br Mon Oct 1 12:40:08 2018 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Mon, 1 Oct 2018 09:40:08 -0300 Subject: [Slackbuilds-users] proposed addition to doinst template In-Reply-To: <201809291951.49637.ricardo@palmtx.com.ar> References: <20180929133025.GE20627@giustizia.org> <201809291951.49637.ricardo@palmtx.com.ar> Message-ID: <20181001124007.GA5868@giustizia.org> Hello, I'd add one more suggestion, based on Ricardo's: add some code to take /usr/share/fonts/misc as the default value, like this: update_font_index() { local _dir=$1 _dir=${_dir:-/usr/share/fonts/misc} if [ -x /usr/bin/mkfontdir -o -x /usr/X11R6/bin/mkfontdir ]; then ( cd "$_dir" && mkfontscale . && mkfontdir -e /usr/share/fonts/encodings \ -e /usr/share/fonts/encodings/large . ) fi if [ -x /usr/bin/fc-cache ]; then /usr/bin/fc-cache -f fi } Another suggestion, which requires more code, is to consider a group of a reasonable set of directories as the default. My 2 cents, Luiz On Sat, Sep 29, 2018 at 07:51:49PM -0300, Ricardo J. Barberis wrote: > Hello all! > > While we're at it, how about passing the dir to the function (and some basic > error control)? > > update_font_index() { > if [ -x /usr/bin/mkfontdir -o -x /usr/X11R6/bin/mkfontdir ]; then > ( cd $1 && > mkfontscale . && > mkfontdir -e /usr/share/fonts/encodings \ > -e /usr/share/fonts/encodings/large . > ) > fi > if [ -x /usr/bin/fc-cache ]; then > /usr/bin/fc-cache -f > fi > } > > > Then you can call it for every needed dir: > > (...) > # Update the X font indexes: > update_font_index /usr/share/fonts/misc > update_font_index /usr/share/fonts/100dpi > (...) > > > Cheers! > > El S?bado 29/09/2018 a las 10:30, Luiz Carlos Ramos via SlackBuilds-users > escribi?: > > Hello, > > > > I'm not used to reply in this list, but I keep watching the message > > flow... let me add a suggestion. > > > > This addition could be added as a function, that is, it would be like > > > > update_font_index() { > > if [ -x /usr/bin/mkfontdir -o -x /usr/X11R6/bin/mkfontdir ]; then > > ( cd /usr/share/fonts/misc > > mkfontscale . > > mkfontdir -e /usr/share/fonts/encodings \ > > -e /usr/share/fonts/encodings/large . > > ) > > fi > > if [ -x /usr/bin/fc-cache ]; then > > /usr/bin/fc-cache -f > > fi > > } > > > > That is, it's the same code, but encapsulated as a function. This > > function could be in the template for all packages. If a specific > > package needs to do it, it could simply add one line to the "main" > > script: > > > > (...) > > # Update the X font indexes: > > update_font_index > > (...) > > > > IMHO, this makes things more clear for folks who will maintain the code. > > That is, the task to be done would be synthesized in that one line in > > the install step (the call to "update_font_index"); and the way it's > > done is coded in the function itself. Someone who needs to code the same > > thing in a new slackbuild could copy the template and add one line to > > the "main" procedure. > > > > Only my 2 cents, > > > > thanks, > > > > Luiz Carlos Ramos > > lramos.prof at yahoo.com.br > > > > On Fri, Sep 28, 2018 at 07:26:34PM -0400, B Watson wrote: > > > Any build that installs non-TTF fonts in the global font path > > > (/usr/share/fonts/*) should include this in doinst.sh: > > > > > > # Update the X font indexes: > > > if [ -x /usr/bin/mkfontdir -o -x /usr/X11R6/bin/mkfontdir ]; then > > > ( cd /usr/share/fonts/misc > > > mkfontscale . > > > mkfontdir -e /usr/share/fonts/encodings -e > > > /usr/share/fonts/encodings/large . > > > ) > > > fi > > > if [ -x /usr/bin/fc-cache ]; then > > > /usr/bin/fc-cache -f > > > fi > > > > > > The above was taken from one of Pat's font-* packages (it's included in > > > multiple ones). > > > > > > Change the "fonts/misc" to e.g. "fonts/100dpi" or whatever your package > > > actually installs fonts to (if multiple subdirs, mkfontscale and > > > mkfontdir will have to be run in all of them). > > > > > > Ideally, packages won't install fonts.dir files at all, but Pat's font-* > > > packages do (and then immediately overwrite them via the doinst.sh). > > > > > > For those not familiar with it, fonts.dir is a list of all the installed > > > fonts in a directory. If a font is present, but not mentioned in > > > fonts.dir, "old-style" X apps (ones that don't use fontconfig) won't be > > > able to use that font. > > > > > > For a specific example of a SBo build that needs this, see libdockapp. It > > > installs 2 fonts in /usr/share/fonts/misc, and includes a fonts.dir > > > that only lists those 2 fonts. After installing this package, other apps > > > (e.g. xterm) have problems loading fonts, depending on what font they're > > > configured to use. > > > -- > Ricardo J. Barberis > Usuario Linux N? 250625: http://counter.li.org/ > Usuario LFS N? 5121: http://www.linuxfromscratch.org/ > Senior SysAdmin / IT Architect - www.DonWeb.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/ > From rshepard at appl-ecosys.com Mon Oct 1 20:36:35 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 1 Oct 2018 13:36:35 -0700 (PDT) Subject: [Slackbuilds-users] Error building OpenBLAS Message-ID: I'm building all my SBo packages on a newly minted desktop running -14.2/x86_64. I downloaded from the repository the *.tar.gz and build directory so all files are fresh. Running the SlackBuild script stops with this: gemv.c: In function ?sgemv_?: gemv.c:219:42: error: ?GEMM_MULTITHREAD_THRESHOLD? undeclared (first use in this function) if ( MNK <= (500.0 * 100.0 * (double) GEMM_MULTITHREAD_THRESHOLD) ) ^ gemv.c:219:42: note: each undeclared identifier is reported only once for each function it appears in Makefile:815: recipe for target 'sgemv.o' failed make[1]: *** [sgemv.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory '/tmp/SBo/OpenBLAS-0.2.11/interface' Makefile:141: recipe for target 'libs' failed make: *** [libs] Error 1 Since I've built this before (on my current desktop) I've no idea where to look for a fix for this error and I would appreciate guidance. Rich From dpross1100 at msn.com Tue Oct 2 03:34:43 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Tue, 2 Oct 2018 03:34:43 +0000 Subject: [Slackbuilds-users] Small change to kodi.desktop Message-ID: Hi, I just installed Kodi for the first time in awhile, and I noticed that when using plank (a dock), I am not able to keep the Kodi icon in the dock as a launcher. Additionally, a generic icon is displayed in the dock when it is running, rather than the icon provided by the theme. It turns out that if you add this line: TryExec=kodi to kodi.desktop, both problems are resolved. Based on the freedesktop.org standards for desktop entries, TryExec seems pretty important, and therefore leaving it out may cause other applications in addition to plank to not handle it optimally. Can the SlackBuild be patched to add that line to kodi.desktop? https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#idm140676267060848 Thanks, Dan From chris.willing at iinet.net.au Tue Oct 2 06:58:55 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 2 Oct 2018 16:58:55 +1000 Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: References: Message-ID: On 2/10/18 6:36 am, Rich Shepard wrote: > ? I'm building all my SBo packages on a newly minted desktop running > -14.2/x86_64. I downloaded from the repository the *.tar.gz and build > directory so all files are fresh. > > ? Running the SlackBuild script stops with this: > > gemv.c: In function ?sgemv_?: > gemv.c:219:42: error: ?GEMM_MULTITHREAD_THRESHOLD? undeclared (first use > in this function) > ?? if ( MNK <= (500.0 * 100.0? * (double) GEMM_MULTITHREAD_THRESHOLD)? ) > ????????????????????????????????????????? ^ > gemv.c:219:42: note: each undeclared identifier is reported only once > for each function it appears in > Makefile:815: recipe for target 'sgemv.o' failed > make[1]: *** [sgemv.o] Error 1 > make[1]: *** Waiting for unfinished jobs.... > make[1]: Leaving directory '/tmp/SBo/OpenBLAS-0.2.11/interface' > Makefile:141: recipe for target 'libs' failed > make: *** [libs] Error 1 > > ? Since I've built this before (on my current desktop) I've no idea > where to > look for a fix for this error and I would appreciate guidance. > The missing GEMM_MULTITHREAD_THRESHOLD is (should be) set in Makefile.system which is called from the second line of the main Makefile. Something is definitely screwy if it hasn't been set. To check that, you could edit the main Makefile and add a blank line after "include ./Makefile.system"; then add a new target "atest" which prints out the value of the GEMM_MULTITHREAD_THRESHOLD variable i.e. confirms that it has been set e.g. atest: @echo "GEMM_MULTITHREAD_THRESHOLD = $(GEMM_MULTITHREAD_THRESHOLD)" Then another blank line. Now run 'make atest" from the directory that contains the Makefiles. By default GEMM_MULTITHREAD_THRESHOLD is set to 4 - if you don't see that result, I guess you could set it explicitly - run: GEMM_MULTITHREAD_THRESHOLD=4 make atest and when that works: GEMM_MULTITHREAD_THRESHOLD=4 make and see how far it builds. However the problem with this approach is that if GEMM_MULTITHREAD_THRESHOLD hasn't been set correctly in Makefile.system, then there are likely other things not being set correctly in there. chris From ts at websafe.pl Tue Oct 2 07:51:00 2018 From: ts at websafe.pl (Thomas Szteliga) Date: Tue, 2 Oct 2018 09:51:00 +0200 Subject: [Slackbuilds-users] Strange problem with KeePass 2.39.1 In-Reply-To: References: <939c4aec-a2db-106f-1f59-311c87b969eb@websafe.pl> Message-ID: <314a4352-cc3d-740e-ab22-6bd19bdd18b9@websafe.pl> W dniu 30/09/2018 o?12:55, Shrivats pisze: > I pushed an update for version 2.40 and included KeePass.config.xml in this > update. It's currently in pending queue and you can try it out once it's > uploaded. OK, thank you, I will try it :-) -- Thomas Szteliga From davidnchmelik at gmail.com Tue Oct 2 09:16:57 2018 From: davidnchmelik at gmail.com (David Melik) Date: Tue, 2 Oct 2018 02:16:57 -0700 Subject: [Slackbuilds-users] several builds crashing looking for old libwebp Message-ID: <78ea7b29-de96-b429-6593-434c7b09e99e@gmail.com> NotepadQQ and KVIRC (though newly compiled) both immediately crash for not finding libwebp.so.6.? Well, that file is now at libwebp.so.7.0.2.? King Beowulf told me this behaviour means libwebp is a runtime dependency (the SlackBuild maintainers should be aware of) and to link libwebp.so.6 to libwebp (which of course itself is a link to the 7.0.2.)? I did that, then both worked.? Previously the NotepadQQ maintainer said recompile/upgrade libwebp, then NotepadQQ... same thing happened.? Well, the problem appears to be poor source code in both NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong. From dchmelik at gmail.com Tue Oct 2 09:19:02 2018 From: dchmelik at gmail.com (David Melik) Date: Tue, 2 Oct 2018 02:19:02 -0700 Subject: [Slackbuilds-users] several builds crashing looking for old libwebp Message-ID: <6974fc11-139b-f9c6-c258-57d07b2837fa@gmail.com> NotepadQQ and KVIRC (though newly compiled) both immediately crash for not finding libwebp.so.6.? Well, that file is now at libwebp.so.7.0.2.? King Beowulf told me (when I finally had to upgrade libwebp for BOINC instead of keeping an old one) this behaviour means libwebp is a runtime dependency (the SlackBuild maintainers must become aware of) and to link libwebp.so.6 to libwebp (which of course itself is a link to the 7.0.2.)? I did that, then both worked.? Previously the NotepadQQ maintainer said recompile/upgrade libwebp, then NotepadQQ... same thing happened. Well, the problem appears to be poor source code in both NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong... or maybe the libwebp maintainer should become aware that some programs try to use a specific old version for some reason, and make a link in the SlackBuild. From matteo.bernardini at gmail.com Tue Oct 2 09:35:51 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 2 Oct 2018 11:35:51 +0200 Subject: [Slackbuilds-users] several builds crashing looking for old libwebp In-Reply-To: <6974fc11-139b-f9c6-c258-57d07b2837fa@gmail.com> References: <6974fc11-139b-f9c6-c258-57d07b2837fa@gmail.com> Message-ID: Il giorno mar 2 ott 2018 alle ore 11:19 David Melik ha scritto: > > NotepadQQ and KVIRC (though newly compiled) both immediately crash for > not finding libwebp.so.6. Well, that file is now at libwebp.so.7.0.2. > King Beowulf told me (when I finally had to upgrade libwebp for BOINC > instead of keeping an old one) this behaviour means libwebp is a runtime > dependency (the SlackBuild maintainers must become aware of) and to link > libwebp.so.6 to libwebp (which of course itself is a link to the > 7.0.2.) I did that, then both worked. Previously the NotepadQQ > maintainer said recompile/upgrade libwebp, then NotepadQQ... same thing > happened. Well, the problem appears to be poor source code in both > NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong... or > maybe the libwebp maintainer should become aware that some programs try > to use a specific old version for some reason, and make a link in the > SlackBuild. if you upgrade a library to a newer major release with a shared library version bump, like in your case, you should also rebuild whatever links against it: I suspect the error you got is because you have to rebuild qt5 and qt5-webkit (that you built against the old libwebp in the first place). From yalhcru at gmail.com Tue Oct 2 09:56:30 2018 From: yalhcru at gmail.com (B Watson) Date: Tue, 2 Oct 2018 05:56:30 -0400 Subject: [Slackbuilds-users] several builds crashing looking for old libwebp In-Reply-To: <78ea7b29-de96-b429-6593-434c7b09e99e@gmail.com> References: <78ea7b29-de96-b429-6593-434c7b09e99e@gmail.com> Message-ID: On 10/2/18, David Melik wrote: > Well, the problem appears to be poor source code in both > NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong. It means you upgraded libwebp, but didn't upgrade other library packages that depend on it. One of the libs in one of these packages was linked when building NotepadQQ and KVIRC... OK, a bit more investigation reveals that notepadqq and kvirc both require qt5-webkit. And qt5-webkit lists libwebp as an optional dependency, in its README. So what happened here is you built some version of libwebp, then built qt5-webkit afterwards... and then you (possibly months later) upgraded libwebp. But qt5-webkit was still trying to find the old libwebp, which is gone... In this situation, newly-compiled programs that link with qt5-webkit won't fail to compile or link... but they *will* fail at runtime in exactly the way you describe. It's a common problem when upgrading libraries: there's not an easy way to find out what *other* libraries depend on it and need to be upgraded. Especially when they're optional ones (not listed in REQUIRES in the .info file). Usually when I get bit by this, it's ffpmeg (because it just has *so* many deps, most of which are optional). Generally you can figure this kind of runtime linking problem out by using ldd... or, even better, get lddsafe from here: https://github.com/rg3/lddsafe ...and use its -n option, which shows only direct library dependencies... then use lddsafe -n on each of those libraries, until you hit a 'not found'. The other way to diagnose this would have been to look at the REQUIRES for both notepadqq and kvirc (which is what I did) and notice they both say qt5-webkit, and then find the shared libs in qt5-webkit and run regular ldd on them. You would have gotten a 'not found' for the old version of libwebp... The general solution is to rebuild the offending library (in this case, qt5-webkit). Or you can use sbopkg to check for updates to *all* your installed packages, and upgrade them all (takes longer, but you're less likely to run into problems like this). Hopefully the above has been helpful to you, and makes up for what you'll perceive as rudeness in the rest of the message. But I feel this must be said, so: It's not "poor source code" and it's not "SlackBuilds done wrong", and it's kinda rude of you to say that, considering you're lacking some fundamental knowledge that would qualify you to actually make that judgement. Your original post should probably have been a request for help, without trying to place the blame on anyone. In fact, the blame is on you, *your* system was in an inconsistent state. Hopefully I've helped you to fix it and learn how to diagnose and fix it on your own next time. Please try to take this as constructive criticism, not flaming. From idlemoor at slackbuilds.org Tue Oct 2 10:09:46 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Tue, 2 Oct 2018 11:09:46 +0100 Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: References: Message-ID: > ? I'm building all my SBo packages on a newly minted desktop running > -14.2/x86_64. I downloaded from the repository the *.tar.gz and build > directory so all files are fresh. > > ? Running the SlackBuild script stops with this: > > gemv.c: In function ?sgemv_?: > gemv.c:219:42: error: ?GEMM_MULTITHREAD_THRESHOLD? undeclared (first use > in this function) Hey Rich, I've had the same error in build testing recently and I don't know why But fortunately Mario has just updated OpenBLAS and the new version will be in the next public update :D Or (if you don't want to wait) you can grab the new version from here: https://git.slackbuilds.org/slackbuilds/tree/libraries/OpenBLAS?h=idlemoor&id=3eb342a21265826a61a9128906ab601565baec57 Cheers! and thanks to Mario for perfect timing! -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From davidnchmelik at gmail.com Tue Oct 2 10:36:35 2018 From: davidnchmelik at gmail.com (David Melik) Date: Tue, 2 Oct 2018 03:36:35 -0700 Subject: [Slackbuilds-users] several builds crashing looking for old libwebp In-Reply-To: References: <6974fc11-139b-f9c6-c258-57d07b2837fa@gmail.com> Message-ID: On 10/2/18 2:35 AM, Matteo Bernardini wrote: > Il giorno mar 2 ott 2018 alle ore 11:19 David Melik > ha scritto: >> NotepadQQ and KVIRC (though newly compiled) both immediately crash for >> not finding libwebp.so.6. Well, that file is now at libwebp.so.7.0.2. >> King Beowulf told me (when I finally had to upgrade libwebp for BOINC >> instead of keeping an old one) this behaviour means libwebp is a runtime >> dependency (the SlackBuild maintainers must become aware of) and to link >> libwebp.so.6 to libwebp (which of course itself is a link to the >> 7.0.2.) I did that, then both worked. Previously the NotepadQQ >> maintainer said recompile/upgrade libwebp, then NotepadQQ... same thing >> happened. Well, the problem appears to be poor source code in both >> NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong... or >> maybe the libwebp maintainer should become aware that some programs try >> to use a specific old version for some reason, and make a link in the >> SlackBuild. > if you upgrade a library to a newer major release with a shared > library version bump, like in your case, you should also rebuild > whatever links against it: I suspect the error you got is because you > have to rebuild qt5 and qt5-webkit (that you built against the old > libwebp in the first place). Okay; I had done that also but maybe in the wrong order... it's not clear again what built 'against' means rather than built 'from' (or 'depending on')... From matteo.bernardini at gmail.com Tue Oct 2 10:50:56 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 2 Oct 2018 12:50:56 +0200 Subject: [Slackbuilds-users] several builds crashing looking for old libwebp In-Reply-To: References: <6974fc11-139b-f9c6-c258-57d07b2837fa@gmail.com> Message-ID: Il giorno mar 2 ott 2018 alle ore 12:36 David Melik ha scritto: > > On 10/2/18 2:35 AM, Matteo Bernardini wrote: > > Il giorno mar 2 ott 2018 alle ore 11:19 David Melik > > ha scritto: > >> NotepadQQ and KVIRC (though newly compiled) both immediately crash for > >> not finding libwebp.so.6. Well, that file is now at libwebp.so.7.0.2. > >> King Beowulf told me (when I finally had to upgrade libwebp for BOINC > >> instead of keeping an old one) this behaviour means libwebp is a runtime > >> dependency (the SlackBuild maintainers must become aware of) and to link > >> libwebp.so.6 to libwebp (which of course itself is a link to the > >> 7.0.2.) I did that, then both worked. Previously the NotepadQQ > >> maintainer said recompile/upgrade libwebp, then NotepadQQ... same thing > >> happened. Well, the problem appears to be poor source code in both > >> NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong... or > >> maybe the libwebp maintainer should become aware that some programs try > >> to use a specific old version for some reason, and make a link in the > >> SlackBuild. > > if you upgrade a library to a newer major release with a shared > > library version bump, like in your case, you should also rebuild > > whatever links against it: I suspect the error you got is because you > > have to rebuild qt5 and qt5-webkit (that you built against the old > > libwebp in the first place). > > Okay; I had done that also but maybe in the wrong order... it's not > clear again what built 'against' means rather than built 'from' (or > 'depending on')... if qt5 and qt5-webkit depends on libwebp you should build first libwebp and then qt5 and then qt5-webkit (that depends on qt5), this is necessary for a program/library using a dependency to link to it at build-time. I wrote "built against it" meaning "built linking to it", both forms are often used on this mailing list, irc or the LQ forum. From rshepard at appl-ecosys.com Tue Oct 2 12:50:47 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 2 Oct 2018 05:50:47 -0700 (PDT) Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: References: Message-ID: On Tue, 2 Oct 2018, David Spencer wrote: > I've had the same error in build testing recently and I don't know why Dave, Interesting. I hit this wall on a clean 14.2 on a brand new system. > But fortunately Mario has just updated OpenBLAS and the new version will > be in the next public update :D > > Or (if you don't want to wait) you can grab the new version from here: > > https://git.slackbuilds.org/slackbuilds/tree/libraries/OpenBLAS?h=idlemoor&id=3eb342a21265826a61a9128906ab601565baec57 I need this library to build GRASS, and I need GRASS to run a spatial interpolation model that runs out of room on the current desktop. Thanks! Rich From fernando.lopezjr at gmail.com Tue Oct 2 19:52:22 2018 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 2 Oct 2018 13:52:22 -0600 Subject: [Slackbuilds-users] request to remove package: newlib-headers. Message-ID: i would like to remove this package: https://slackbuilds.org/repository/14.2/development/newlib-headers/ -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Tue Oct 2 21:56:21 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 2 Oct 2018 14:56:21 -0700 (PDT) Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: References: Message-ID: On Tue, 2 Oct 2018, David Spencer wrote: > But fortunately Mario has just updated OpenBLAS and the new version will > be in the next public update :D > > Or (if you don't want to wait) you can grab the new version from here: > https://git.slackbuilds.org/slackbuilds/tree/libraries/OpenBLAS?h=idlemoor&id=3eb342a21265826a61a9128906ab601565baec57 Dave/Mario: I downloaded the SlackBuild, info, desc, and README files. The build script is looking for version 0.3.3 while the SBo repo has version 0.2.20. The home page on github has all the development branch files and I did not see an 0.3.3 tarball. Did I miss it there? Regards, Rich From didier at slint.fr Tue Oct 2 22:09:01 2018 From: didier at slint.fr (Didier Spaier) Date: Wed, 3 Oct 2018 00:09:01 +0200 Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: References: Message-ID: On 10/2/18 11:56 PM, Rich Shepard wrote: > On Tue, 2 Oct 2018, David Spencer wrote: > >> But fortunately Mario has just updated OpenBLAS and the new version will >> be in the next public update :D >> >> Or (if you don't want to wait) you can grab the new version from here: >> https://git.slackbuilds.org/slackbuilds/tree/libraries/OpenBLAS?h=idlemoor&id=3eb342a21265826a61a9128906ab601565baec57 > > Dave/Mario: > > ? I downloaded the SlackBuild, info, desc, and README files. The build > script is looking for version 0.3.3 while the SBo repo has version 0.2.20. > > ? The home page on github has all the development branch files and I did not > see an 0.3.3 tarball. Did I miss it there? Yes, you missed to read OpenBLAS.info that you downloaded, which provides a link to the source tarball like this: DOWNLOAD="https://github.com/xianyi/OpenBLAS/archive/v0.3.3/OpenBLAS-0.3.3.tar.gz" I just checked the link, it is correct. Didier From rshepard at appl-ecosys.com Tue Oct 2 22:48:26 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 2 Oct 2018 15:48:26 -0700 (PDT) Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: References: Message-ID: On Wed, 3 Oct 2018, Didier Spaier wrote: > Yes, you missed to read OpenBLAS.info that you downloaded, which > provides a link to the source tarball like this: > DOWNLOAD="https://github.com/xianyi/OpenBLAS/archive/v0.3.3/OpenBLAS-0.3.3.tar.gz" > > I just checked the link, it is correct. Didier, My apologies for not reading the .info file. I'll do this now. Rich From didier at slint.fr Tue Oct 2 22:58:50 2018 From: didier at slint.fr (Didier Spaier) Date: Wed, 3 Oct 2018 00:58:50 +0200 Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: References: Message-ID: <7fd0c9b6-c79c-53c0-33fd-812a2500e9bc@slint.fr> On 10/3/18 12:48 AM, Rich Shepard wrote: > On Wed, 3 Oct 2018, Didier Spaier wrote: > >> Yes, you missed to read OpenBLAS.info that you downloaded, which >> provides a link to the source tarball like this: >> DOWNLOAD="https://github.com/xianyi/OpenBLAS/archive/v0.3.3/OpenBLAS-0.3.3.tar.gz" >> >> I just checked the link, it is correct. > > Didier, > > ? My apologies for not reading the .info file. I'll do this now. > > Rich No problem. For your information clicking on: https://github.com/xianyi/OpenBLAS/ displays a page where you see under the description a line including (at time of writing): 39 releases This is a link and clicking on it displays a page where you will find links to compressed archives of the source code for each release. A lot of projects on GitHub provides that. From rshepard at appl-ecosys.com Tue Oct 2 23:04:10 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 2 Oct 2018 16:04:10 -0700 (PDT) Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: References: Message-ID: On Wed, 3 Oct 2018, Didier Spaier wrote: > Yes, you missed to read OpenBLAS.info that you downloaded, which provides > a link to the source tarball like this: > DOWNLOAD="https://github.com/xianyi/OpenBLAS/archive/v0.3.3/OpenBLAS-0.3.3.tar.gz" > > I just checked the link, it is correct. Didier, Downloaded the tarball and tried building it. The error reported is: Makefile:135: *** OpenBLAS: Detecting CPU failed. Please set TARGET explicitly, e.g. make TARGET=your_cpu_target. Please read README for the detail.. Stop. README: OpenBLAS is an optimized BLAS library based on GotoBLAS2 1.13 BSD version. Added symbolic link to install a generic blas library that can be used by Octave and R. In OpenBLAS.SlackBuild the target looks at uname -m which here reports the processor type as x86_64. That target is not explicit in the build file, but I assume it's accepted in the last choice after i?586 and arm*. Should I add a target of x86_64 to the build script? Rich From rshepard at appl-ecosys.com Tue Oct 2 23:05:45 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 2 Oct 2018 16:05:45 -0700 (PDT) Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: <7fd0c9b6-c79c-53c0-33fd-812a2500e9bc@slint.fr> References: <7fd0c9b6-c79c-53c0-33fd-812a2500e9bc@slint.fr> Message-ID: On Wed, 3 Oct 2018, Didier Spaier wrote: > No problem. For your information clicking on: > https://github.com/xianyi/OpenBLAS/ > displays a page where you see under the description a line including > (at time of writing): 39 releases > This is a link and clicking on it displays a page where you will find > links to compressed archives of the source code for each release. > A lot of projects on GitHub provides that. Didier, Thanks for this knowledge. I did not explore that link but looked at the list of files for the tarball. Best regards, Rich From jbernts at broadpark.no Wed Oct 3 01:42:57 2018 From: jbernts at broadpark.no (Jostein Berntsen) Date: Wed, 3 Oct 2018 03:42:57 +0200 Subject: [Slackbuilds-users] A few scripts up for grab. In-Reply-To: <20180928184026.afd08a412f95dff7f1ae0f24@ythogtha.org> References: <20180928184026.afd08a412f95dff7f1ae0f24@ythogtha.org> Message-ID: <20181003014257.GD21452@jbsupah> On 28.09.18,18:40, Arnaud wrote: > Hello, > > Following the previous messages about warzone2100, I contacted both > Matthew and David Fillpot. Matthew answered for them both, and agrees to put all > of their scripts up for grabs, I quote : > > Yes, please notify the mailing list that the scripts for both maintainers > > are up for grabs. > Though he is also ok to resume his work as maintainer, in about a > month, for anything that remains. It seems he has a bit more time at the moment. > So those scripts doesn't require a new maintainer, but if you want to > take care of them, they are available ! > > Most of their scripts are for abandonwares, here they are, classified by > maintenance level : > * Nothing to do, mostly abandoned projects > academic/mathomatic : up-to-date, last upstream update 2012/10/30 > desktop/kcometen4 : up-to-date, last upstream update 2010/07/30 > system/freefont : up-to-date, last upstream update 2012/05/03 > games/lightyears : up-to-date, last upstream update 2011/09/27 > games/tuxkart : up-to-date, last upstream update unknown but >5 years old > libraries/GLee : up-to-date, last upstream update unknown but >5 years old > libraries/quesoglc : up-to-date, last upstream update 2013/08/23 > * active projects but SBo package is 5 years old > academic/gpredict : SBo version 1.3, upstream version 2.2.1 > network/axel : Sbo version 2.4, upstream version 2.16.1 > graphics/qrencode : Sbo version 3.4.0, upstream version 4.0.2 > games/pysolfc : SBo version 2.0, upstream version 2.4.0 > system/yakuake : SBo version 2.9.9, upstream version 3.0.5 > > And I'm ok taking ownership of warzone2100, having already done the > update work on it. > I can take the axel SlackBuild. Jostein From yalhcru at gmail.com Wed Oct 3 05:19:24 2018 From: yalhcru at gmail.com (B Watson) Date: Wed, 3 Oct 2018 01:19:24 -0400 Subject: [Slackbuilds-users] A few scripts up for grab. In-Reply-To: <20180928184026.afd08a412f95dff7f1ae0f24@ythogtha.org> References: <20180928184026.afd08a412f95dff7f1ae0f24@ythogtha.org> Message-ID: On 9/28/18, Arnaud wrote: > games/lightyears : up-to-date, last upstream update 2011/09/27 > games/tuxkart : up-to-date, last upstream update unknown but >5 years > games/pysolfc : SBo version 2.0, upstream version 2.4.0 I'll take these 3, if nobody's already claimed them. From dchmelik at gmail.com Wed Oct 3 07:08:46 2018 From: dchmelik at gmail.com (David Melik) Date: Wed, 3 Oct 2018 00:08:46 -0700 Subject: [Slackbuilds-users] several builds crashing looking for old libwebp In-Reply-To: References: <6974fc11-139b-f9c6-c258-57d07b2837fa@gmail.com> Message-ID: <3b1ad5bb-cf42-559c-64e5-4edf34920d7b@gmail.com> Thanks, B and Matteo for replies.? I hadn't seen the duplicate post until I checked Gmane; I wish listserv didn't accept posts from my other email address (not a member.)? Is it possible yet to post on Gmane? On Tue, 02 Oct 2018 05:56:30 -0400, B Watson wrote: > [...] OK, a bit more investigation reveals that notepadqq and kvirc both > require qt5-webkit. And qt5-webkit lists libwebp as an optional > dependency, in its README. > > So what happened here is you built some version of libwebp, then built > qt5-webkit afterwards... and then you (possibly months later) upgraded > libwebp. But qt5-webkit was still trying to find the old libwebp, which > is gone... > [...] > Generally you can figure this kind of runtime linking problem out by > using ldd... or, even better, get lddsafe from here: > > https://github.com/rg3/lddsafe Thanks; looking that up now. > [...] > It's not "poor source code" and it's not "SlackBuilds done wrong", > and it's kinda rude of you to say that, considering you're lacking some > fundamental knowledge that would qualify you to actually make that > judgement. > > Your original post should probably have been a request for help, without > trying to place the blame on anyone. In fact, the blame is on you, > *your* system was in an inconsistent state. Hopefully I've helped you to > fix it and learn how to diagnose and fix it on your own next time. > > Please try to take this as constructive criticism, not flaming. I'm not flaming, just paraphrasing 'If NotepadQQ looks for libwebp at runtime that is a "runtime dependency" and the idiots upstream (either NotepadQQ or qt5-webkit) should be looking for libwebp.so not libwebp.so.x. Install everything for BOINC, including libwebp-1.0.0. Then just create a libwebp.so.6 symlink to libwebp.so'--King Beowulf (on his LQ BOINC thread.) On Tue, 02 Oct 2018 12:50:56 +0200, Matteo Bernardini wrote: > if qt5 and qt5-webkit depends on libwebp you should build first libwebp > and then qt5 and then qt5-webkit (that depends on qt5), this is > necessary for a program/library using a dependency to link to it at > build-time. > I wrote "built against it" meaning "built linking to it", both forms are > often used on this mailing list, irc or the LQ forum. Ok, thanks; doing that now. From didier at slint.fr Wed Oct 3 08:00:50 2018 From: didier at slint.fr (Didier Spaier) Date: Wed, 3 Oct 2018 10:00:50 +0200 Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: References: Message-ID: <4cf5db61-f5fc-5990-5a61-732a2a3630a5@slint.fr> On 10/3/18 1:04 AM, Rich Shepard wrote: > ? Downloaded the tarball and tried building it. The error reported is: > > Makefile:135: *** OpenBLAS: Detecting CPU failed.? Please set TARGET > explicitly, e.g.? make TARGET=your_cpu_target.? Please read README for the > detail..? Stop. > > README: > > OpenBLAS is an optimized BLAS library based on GotoBLAS2 1.13 BSD version. > > Added symbolic link to install a generic blas library that can be used by > Octave and R. > > ? In OpenBLAS.SlackBuild the target looks at uname -m which here reports the > processor type as x86_64. That target is not explicit in the build file, but > I assume it's accepted in the last choice after i?586 and arm*. > > ? Should I add a target of x86_64 to the build script? The message from the Makefile probably refers to a file in the source archive, not the README provided by the SlackBuild maintainer... Didier From rshepard at appl-ecosys.com Wed Oct 3 14:46:26 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 07:46:26 -0700 (PDT) Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: <4cf5db61-f5fc-5990-5a61-732a2a3630a5@slint.fr> References: <4cf5db61-f5fc-5990-5a61-732a2a3630a5@slint.fr> Message-ID: On Wed, 3 Oct 2018, Didier Spaier wrote: > The message from the Makefile probably refers to a file in the source > archive, not the README provided by the SlackBuild maintainer... Didier, Untarring the source I read the README.md and TargetList.txt files. The CUP on this new desktop is an AMD Ryzen 7 7200 8-core and this specific model is not listed on the target list. The README.md file notes that specifying a target is possible, TARGET=XXXX. Should I try TARGET=Ryzen7? Also, if the configure file specifies USE_OPENMP=1 (haven't yet checked) I should add to ~/.bashrc, export OMP_NUM_THREADS=16. Both worth a try? Rich From rshepard at appl-ecosys.com Wed Oct 3 14:55:16 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 07:55:16 -0700 (PDT) Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: References: <4cf5db61-f5fc-5990-5a61-732a2a3630a5@slint.fr> Message-ID: On Wed, 3 Oct 2018, Rich Shepard wrote: > CUP on this new desktop is an AMD Ryzen 7 7200 8-core and this specific Oops! That should be CPU. Rich From didier at slint.fr Wed Oct 3 14:57:17 2018 From: didier at slint.fr (Didier Spaier) Date: Wed, 3 Oct 2018 16:57:17 +0200 Subject: [Slackbuilds-users] Error building OpenBLAS In-Reply-To: References: <4cf5db61-f5fc-5990-5a61-732a2a3630a5@slint.fr> Message-ID: <11e3c31c-ac18-1066-8533-caec69584f73@slint.fr> On 10/3/18 4:46 PM, Rich Shepard wrote: > On Wed, 3 Oct 2018, Didier Spaier wrote: > >> The message from the Makefile probably refers to a file in the source >> archive, not the README provided by the SlackBuild maintainer... > > Didier, > > ? Untarring the source I read the README.md and TargetList.txt files. The > CUP on this new desktop is an AMD Ryzen 7 7200 8-core and this specific > model is not listed on the target list. > > ? The README.md file notes that specifying a target is possible, > TARGET=XXXX. Should I try TARGET=Ryzen7? > > ? Also, if the configure file specifies USE_OPENMP=1 (haven't yet checked) I > should add to ~/.bashrc, export OMP_NUM_THREADS=16. > > ? Both worth a try? I don't know. Didier From rshepard at appl-ecosys.com Wed Oct 3 18:19:54 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 11:19:54 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error Message-ID: fontforge-20170731 built on my 14-2/x86 desktop but fails to complete on the new 14-2/x86_64 box (with AlienBOB's multilibs installed). The cause of the error is not obvious to me looking at the output: collabclientui.c:462:1: note: in expansion of macro ?G_DEFINE_TYPE? G_DEFINE_TYPE (CollabSessionCallbacks, collab_sessioncallbacks, G_TYPE_OBJECT) ^ In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0, from /usr/include/glib-2.0/glib/gtypes.h:32, from /usr/include/glib-2.0/glib/galloca.h:32, from /usr/include/glib-2.0/glib.h:30, from ../fontforge/ffglib.h:27, from ../fontforge/collabclientpriv.h:67, from collabclientui.c:29: /usr/include/glib-2.0/glib/gmacros.h:182:53: error: size of array ?_GStaticAssertCompileTimeAssertion_2? is negative #define G_STATIC_ASSERT(expr) typedef char G_PASTE (_GStaticAssertCompileTimeAssertion_, __COUNTER_ ^ /usr/include/glib-2.0/glib/gmacros.h:179:47: note: in definition of macro ?G_PASTE_ARGS? #define G_PASTE_ARGS(identifier1,identifier2) identifier1 ## identifier2 ^ /usr/include/glib-2.0/glib/gmacros.h:182:44: note: in expansion of macro ?G_PASTE? #define G_STATIC_ASSERT(expr) typedef char G_PASTE (_GStaticAssertCompileTimeAssertion_, __COUNTER_ ^ /usr/include/glib-2.0/glib/gthread.h:256:5: note: in expansion of macro ?G_STATIC_ASSERT? G_STATIC_ASSERT (sizeof *(location) == sizeof (gpointer)); \ ^ /usr/include/glib-2.0/gobject/gtype.h:1972:7: note: in expansion of macro ?g_once_init_leave? g_once_init_leave (&g_define_type_id__volatile, g_define_type_id); \ ^ /usr/include/glib-2.0/gobject/gtype.h:1729:117: note: in expansion of macro ?_G_DEFINE_TYPE_EXTENDED_END? ED(TN, t_n, T_P, _f_, _C_) _G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, _f_) {_C_;} _G_DEFINE_T ^ /usr/include/glib-2.0/gobject/gtype.h:1587:43: note: in expansion of macro ?G_DEFINE_TYPE_EXTENDED? #define G_DEFINE_TYPE(TN, t_n, T_P) G_DEFINE_TYPE_EXTENDED (TN, t_n, T_P, 0, {}) ^ collabclientui.c:462:1: note: in expansion of macro ?G_DEFINE_TYPE? G_DEFINE_TYPE (CollabSessionCallbacks, collab_sessioncallbacks, G_TYPE_OBJECT) ^ Makefile:2403: recipe for target 'libfontforgeexe_la-collabclientui.lo' failed make[3]: *** [libfontforgeexe_la-collabclientui.lo] Error 1 make[3]: Leaving directory '/tmp/SBo/fontforge-20170731/fontforgeexe' Makefile:2524: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/tmp/SBo/fontforge-20170731/fontforgeexe' Makefile:1580: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/fontforge-20170731' Makefile:1417: recipe for target 'all' failed make: *** [all] Error 2 Please suggest how I should proceed to fix this. Rich From rshepard at appl-ecosys.com Wed Oct 3 18:41:10 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 11:41:10 -0700 (PDT) Subject: [Slackbuilds-users] Another build error: glabels Message-ID: I would really like to understand why I'm having difficulties building SBo packages on my new desktop. It's running 14-2/x86_64, has an 8-core/16-thread CPU, 32G memory, and AlienBOB's multilibs for 14.2. This is the glabels error: lgl-db.c:134:1: note: in expansion of macro 'G_DEFINE_TYPE' G_DEFINE_TYPE (lglDbModel, lgl_db_model, G_TYPE_OBJECT); ^ In file included from /usr/include/glib-2.0/glib/gthread.h:32:0, from /usr/include/glib-2.0/glib/gasyncqueue.h:32, from /usr/include/glib-2.0/glib.h:32, from lgl-db.h:24, from lgl-db.c:23: /usr/include/glib-2.0/glib/gatomic.h:122:5: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] (gpointer) __atomic_load_4 ((atomic), __ATOMIC_SEQ_CST); \ ^ /usr/include/glib-2.0/glib/gthread.h:251:7: note: in expansion of macro 'g_atomic_pointer_get' (!g_atomic_pointer_get (location) && \ ^ /usr/include/glib-2.0/gobject/gtype.h:1958:7: note: in expansion of macro 'g_once_init_enter' if (g_once_init_enter (&g_define_type_id__volatile)) \ ^ /usr/include/glib-2.0/gobject/gtype.h:1729:60: note: in expansion of macro '_G_DEFINE_TYPE_EXTENDED_BEGIN' #define G_DEFINE_TYPE_EXTENDED(TN, t_n, T_P, _f_, _C_) _G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, ^ /usr/include/glib-2.0/gobject/gtype.h:1587:43: note: in expansion of macro 'G_DEFINE_TYPE_EXTENDED' #define G_DEFINE_TYPE(TN, t_n, T_P) G_DEFINE_TYPE_EXTENDED (TN, t_n, T_P, 0, {}) ^ lgl-db.c:134:1: note: in expansion of macro 'G_DEFINE_TYPE' G_DEFINE_TYPE (lglDbModel, lgl_db_model, G_TYPE_OBJECT); ^ In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0, from /usr/include/glib-2.0/glib/gtypes.h:32, from /usr/include/glib-2.0/glib/galloca.h:32, from /usr/include/glib-2.0/glib.h:30, from lgl-db.h:24, from lgl-db.c:23: /usr/include/glib-2.0/glib/gmacros.h:182:53: error: size of array '_GStaticAssertCompileTimeAssertion_2' is negative #define G_STATIC_ASSERT(expr) typedef char G_PASTE (_GStaticAssertCompileTimeAssertion_, __COUNTER_ ^ /usr/include/glib-2.0/glib/gmacros.h:179:47: note: in definition of macro 'G_PASTE_ARGS' #define G_PASTE_ARGS(identifier1,identifier2) identifier1 ## identifier2 ^ /usr/include/glib-2.0/glib/gmacros.h:182:44: note: in expansion of macro 'G_PASTE' #define G_STATIC_ASSERT(expr) typedef char G_PASTE (_GStaticAssertCompileTimeAssertion_, __COUNTER_ ^ /usr/include/glib-2.0/glib/gthread.h:256:5: note: in expansion of macro 'G_STATIC_ASSERT' G_STATIC_ASSERT (sizeof *(location) == sizeof (gpointer)); \ ^ /usr/include/glib-2.0/gobject/gtype.h:1972:7: note: in expansion of macro 'g_once_init_leave' g_once_init_leave (&g_define_type_id__volatile, g_define_type_id); \ ^ /usr/include/glib-2.0/gobject/gtype.h:1729:117: note: in expansion of macro '_G_DEFINE_TYPE_EXTENDED_END' ED(TN, t_n, T_P, _f_, _C_) _G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, _f_) {_C_;} _G_DEFINE_T ^ /usr/include/glib-2.0/gobject/gtype.h:1587:43: note: in expansion of macro 'G_DEFINE_TYPE_EXTENDED' #define G_DEFINE_TYPE(TN, t_n, T_P) G_DEFINE_TYPE_EXTENDED (TN, t_n, T_P, 0, {}) ^ lgl-db.c:134:1: note: in expansion of macro 'G_DEFINE_TYPE' G_DEFINE_TYPE (lglDbModel, lgl_db_model, G_TYPE_OBJECT); ^ Makefile:583: recipe for target 'lgl-db.lo' failed make[2]: *** [lgl-db.lo] Error 1 make[2]: Leaving directory '/tmp/SBo/glabels-3.4.0/libglabels' Makefile:509: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/glabels-3.4.0' Makefile:439: recipe for target 'all' failed make: *** [all] Error 2 All help welcome! Rich From sborg63 at disroot.org Wed Oct 3 18:58:25 2018 From: sborg63 at disroot.org (sborg63) Date: Wed, 3 Oct 2018 19:58:25 +0100 Subject: [Slackbuilds-users] Fontforge build error; SlackBuilds-users Digest, Vol 150, Issue 4 In-Reply-To: References: Message-ID: <20181003195825.2b97f347@knotsUL> On Wed, 03 Oct 2018 18:19:57 +0000 slackbuilds-users-request at slackbuilds.org wrote: > Date: Wed, 3 Oct 2018 11:19:54 -0700 (PDT) > From: Rich Shepard > To: slackbuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] Fontforge build error > Message-ID: > Content-Type: text/plain; format=flowed; charset=ISO-8859-7 > fontforge-20170731 built on my 14-2/x86 desktop but fails to > complete on the new 14-2/x86_64 box (with AlienBOB's multilibs > installed). .. > In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0, With multilib you could get confusion between /usr/lib and /usr/lib64. Maybe it should be looking in /usr/lib64. Have you considered this: https://www.slackbuilds.org/faq/#multilib Plus, if the new box is the latest of the latest hardware-wise, it is maybe worth considering running current because of its more 'current' kernel. I had to do this whenever I got a new laptop; the hardware was much better supported as well as more recent software (the openblas thread springs to mind). hth rob From rshepard at appl-ecosys.com Wed Oct 3 19:58:10 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 12:58:10 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: <20181003195825.2b97f347@knotsUL> References: <20181003195825.2b97f347@knotsUL> Message-ID: On Wed, 3 Oct 2018, sborg63 wrote: > With multilib you could get confusion between /usr/lib > and /usr/lib64. Maybe it should be looking in /usr/lib64. This could be, but glib is found in /usr/lib64. > Have you considered this: https://www.slackbuilds.org/faq/#multilib Don't see anything applicable. > Plus, if the new box is the latest of the latest hardware-wise, it is > maybe worth considering running current because of its more 'current' > kernel. I had to do this whenever I got a new laptop; the hardware was > much better supported as well as more recent software (the openblas thread > springs to mind). I have been thinking this is an issue. In the past I've always built systems that were back from the bleeding edge. This time my budget allowed me to buy components near the top, but below the 'gamers' level. Since I'm getting build errors on packages that built with no errors on portables with 64-bit CPUs (but not the fastest, most expensive models) the hardware newness might well be the factor. I'll look into upgrading to current. Thanks, Rich From willysr at slackbuilds.org Wed Oct 3 20:00:58 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 4 Oct 2018 03:00:58 +0700 Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: References: Message-ID: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> > ? I would really like to understand why I'm having difficulties building > SBo > packages on my new desktop. It's running 14-2/x86_64, has an > 8-core/16-thread CPU, 32G memory, and AlienBOB's multilibs for 14.2. glabels works fine here on pure x86_64 SUMMARY LOG Using the SBo repository for Slackware 14.2 Queue Process: Download and build glabels: MD5SUM check for glabels-3.4.0.tar.xz ... OK Building package glabels-3.4.0-x86_64-1_SBo.tgz ... OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Wed Oct 3 20:05:14 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 13:05:14 -0700 (PDT) Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> Message-ID: On Thu, 4 Oct 2018, Willy Sudiarto Raharjo wrote: > glabels works fine here on pure x86_64 Willy, I need the multilibs library for some applications I regularly use. I think that I need to upgrade to -current, upgrade Eric's multilibs, and try again. Regards, Rich From matteo.bernardini at gmail.com Wed Oct 3 20:07:24 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 3 Oct 2018 22:07:24 +0200 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181003195825.2b97f347@knotsUL> Message-ID: Il giorno mer 3 ott 2018 alle ore 21:58 Rich Shepard ha scritto: > > On Wed, 3 Oct 2018, sborg63 wrote: > > > With multilib you could get confusion between /usr/lib > > and /usr/lib64. Maybe it should be looking in /usr/lib64. > > This could be, but glib is found in /usr/lib64. > > > Have you considered this: https://www.slackbuilds.org/faq/#multilib > > Don't see anything applicable. in your log (for some reason that I won't investigate) you got this line "In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0," that file is much different compared to /usr/lib64/glib-2.0/include/glibconfig.h so it seems that in your case it is actually applicable: try building it on a pure 64 system (here I build my packages on virtual machines). Matteo From willysr at slackbuilds.org Wed Oct 3 20:08:27 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 4 Oct 2018 03:08:27 +0700 Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> Message-ID: > ? I need the multilibs library for some applications I regularly use. I > think that I need to upgrade to -current, upgrade Eric's multilibs, and try > again. I'm not sure whether upgrading to -current will solve the issue, but yeah, you can try it first on a vm -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Wed Oct 3 20:16:18 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 13:16:18 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181003195825.2b97f347@knotsUL> Message-ID: On Wed, 3 Oct 2018, Matteo Bernardini wrote: > so it seems that in your case it is actually applicable: try building it > on a pure 64 system (here I build my packages on virtual machines). Matteo, What makes a 64-bit system 'pure?' 14-2 was installed on a virgin disk and this morning I added the multilibs because adobe-reader works on only 32-bit systems. Rich From willysr at slackbuilds.org Wed Oct 3 20:16:57 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 4 Oct 2018 03:16:57 +0700 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181003195825.2b97f347@knotsUL> Message-ID: > ? What makes a 64-bit system 'pure?' 14-2 was installed on a virgin disk > and > this morning I added the multilibs because adobe-reader works on only > 32-bit > systems. Non Multilibs is a pure 64-bit system -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From dave at dawoodfall.net Wed Oct 3 20:21:33 2018 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 3 Oct 2018 21:21:33 +0100 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: Message-ID: <20181003202133.GB6835@blackswan> On Wednesday 3 October 2018 11:19, Rich Shepard put forth the proposition: > fontforge-20170731 built on my 14-2/x86 desktop but fails to complete on > the new 14-2/x86_64 box (with AlienBOB's multilibs installed). The cause of > the error is not obvious to me looking at the output: > > collabclientui.c:462:1: note: in expansion of macro ?G_DEFINE_TYPE? > G_DEFINE_TYPE (CollabSessionCallbacks, collab_sessioncallbacks, G_TYPE_OBJECT) > ^ > In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0, > from /usr/include/glib-2.0/glib/gtypes.h:32, > from /usr/include/glib-2.0/glib/galloca.h:32, > from /usr/include/glib-2.0/glib.h:30, > from ../fontforge/ffglib.h:27, > from ../fontforge/collabclientpriv.h:67, > from collabclientui.c:29: > /usr/include/glib-2.0/glib/gmacros.h:182:53: error: size of array ?_GStaticAssertCompileTimeAssertion_2? is negative > #define G_STATIC_ASSERT(expr) typedef char G_PASTE (_GStaticAssertCompileTimeAssertion_, __COUNTER_ > ^ > /usr/include/glib-2.0/glib/gmacros.h:179:47: note: in definition of macro ?G_PASTE_ARGS? > #define G_PASTE_ARGS(identifier1,identifier2) identifier1 ## identifier2 > ^ > /usr/include/glib-2.0/glib/gmacros.h:182:44: note: in expansion of macro ?G_PASTE? > #define G_STATIC_ASSERT(expr) typedef char G_PASTE (_GStaticAssertCompileTimeAssertion_, __COUNTER_ > ^ > /usr/include/glib-2.0/glib/gthread.h:256:5: note: in expansion of macro ?G_STATIC_ASSERT? > G_STATIC_ASSERT (sizeof *(location) == sizeof (gpointer)); \ > ^ > /usr/include/glib-2.0/gobject/gtype.h:1972:7: note: in expansion of macro ?g_once_init_leave? > g_once_init_leave (&g_define_type_id__volatile, g_define_type_id); \ > ^ > /usr/include/glib-2.0/gobject/gtype.h:1729:117: note: in expansion of macro ?_G_DEFINE_TYPE_EXTENDED_END? > ED(TN, t_n, T_P, _f_, _C_) _G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, _f_) {_C_;} _G_DEFINE_T > ^ > /usr/include/glib-2.0/gobject/gtype.h:1587:43: note: in expansion of macro ?G_DEFINE_TYPE_EXTENDED? > #define G_DEFINE_TYPE(TN, t_n, T_P) G_DEFINE_TYPE_EXTENDED (TN, t_n, T_P, 0, {}) > ^ > collabclientui.c:462:1: note: in expansion of macro ?G_DEFINE_TYPE? > G_DEFINE_TYPE (CollabSessionCallbacks, collab_sessioncallbacks, G_TYPE_OBJECT) > ^ > Makefile:2403: recipe for target 'libfontforgeexe_la-collabclientui.lo' failed > make[3]: *** [libfontforgeexe_la-collabclientui.lo] Error 1 > make[3]: Leaving directory '/tmp/SBo/fontforge-20170731/fontforgeexe' > Makefile:2524: recipe for target 'all-recursive' failed > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory '/tmp/SBo/fontforge-20170731/fontforgeexe' > Makefile:1580: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/fontforge-20170731' > Makefile:1417: recipe for target 'all' failed > make: *** [all] Error 2 > > Please suggest how I should proceed to fix this. > > Rich Hi I've just tested this on my multilib laptop and it built fine. It's not really obvious where the problem is from the output. Could you please make a build log and attach it to a reply here? You can make one by: ./fontforge.SlackBuild 2>&1 | tee build.log Thanks -- Dave Conscience is the inner voice that warns us somebody is looking -- H. L. Mencken .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dpross1100 at msn.com Wed Oct 3 20:24:24 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Wed, 3 Oct 2018 20:24:24 +0000 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: Message-ID: Did you try following the instructions in the FAQ yet? http://slackbuilds.org/faq/#multilib It that doesn't work, building in a VM or LXC container is much less disruptive than reinstalling the OS on your "production" machine. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Wed Oct 3 20:27:55 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 3 Oct 2018 22:27:55 +0200 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181003195825.2b97f347@knotsUL> Message-ID: Il giorno mer 3 ott 2018 alle ore 22:17 Willy Sudiarto Raharjo ha scritto: > > > What makes a 64-bit system 'pure?' 14-2 was installed on a virgin disk > > and > > this morning I added the multilibs because adobe-reader works on only > > 32-bit > > systems. > > Non Multilibs is a pure 64-bit system it could mean also that you: 1) create a virtual machine (with whatever hypervisor you prefer, but this is not the main scope of this answer so I won't elaborate on this); 2) install a full slackware64-14.2 and NOTHING ELSE; 3) update it to the latest patches; 4) shut it down; 5) copy the virtual machine file somewhere (or do a snapshot or whatever the hypervisor you use for your virtual machine allows, but this is not the main scope of this answer so I won't elaborate on this); 6) turn it on again; 7) build the package you need on the virtual machine and copy it where you need it; 8) turn it off again; 9) restore the virtual machine from the copy you have done. 10) start again from point 6) as needed. This way you will always have a "pure" platform to build your packages. In alternative to points 7 to 10 you can also install slackrepo in the virtual machine and use that (but this is not the main scope of this answer so I won't elaborate on this). good luck! From dave at dawoodfall.net Wed Oct 3 20:33:31 2018 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 3 Oct 2018 21:33:31 +0100 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181003195825.2b97f347@knotsUL> Message-ID: <20181003203331.GC6835@blackswan> On Wednesday 3 October 2018 12:58, Rich Shepard put forth the proposition: > On Wed, 3 Oct 2018, sborg63 wrote: > > > With multilib you could get confusion between /usr/lib > > and /usr/lib64. Maybe it should be looking in /usr/lib64. > > This could be, but glib is found in /usr/lib64. > > > Have you considered this: https://www.slackbuilds.org/faq/#multilib > > Don't see anything applicable. This line: LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \ Try adding that under the CXXFLAGS= line in the slackbuild. It's worth remembering as the first thing to try on a multilib system when a build fails. Dave > > Plus, if the new box is the latest of the latest hardware-wise, it is > > maybe worth considering running current because of its more 'current' > > kernel. I had to do this whenever I got a new laptop; the hardware was > > much better supported as well as more recent software (the openblas thread > > springs to mind). > > I have been thinking this is an issue. In the past I've always built > systems that were back from the bleeding edge. This time my budget allowed > me to buy components near the top, but below the 'gamers' level. Since I'm > getting build errors on packages that built with no errors on portables with > 64-bit CPUs (but not the fastest, most expensive models) the hardware > newness might well be the factor. > > I'll look into upgrading to current. > > Thanks, > > Rich -- Dave A physicist is an atom's way of knowing about atoms. -- George Wald .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Wed Oct 3 20:39:21 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 13:39:21 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181003195825.2b97f347@knotsUL> Message-ID: On Thu, 4 Oct 2018, Willy Sudiarto Raharjo wrote: > Non Multilibs is a pure 64-bit system Okay. Thanks, Rich From dave at dawoodfall.net Wed Oct 3 20:39:22 2018 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 3 Oct 2018 21:39:22 +0100 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181003195825.2b97f347@knotsUL> Message-ID: <20181003203922.GD6835@blackswan> On Wednesday 3 October 2018 13:16, Rich Shepard put forth the proposition: > On Wed, 3 Oct 2018, Matteo Bernardini wrote: > > > so it seems that in your case it is actually applicable: try building it > > on a pure 64 system (here I build my packages on virtual machines). > > Matteo, > > What makes a 64-bit system 'pure?' 14-2 was installed on a virgin disk and > this morning I added the multilibs because adobe-reader works on only 32-bit > systems. > > Rich You could try creating a 64 bit chrooted environment to build packages in. I do that for a few things that fail on multilib. Basically you install slackware into a directory. Once done, you can get a root login by typing: chroot /path/to/chroot /bin/bash installpkg has a --root option which you can use to installl packages anywhere you like. -- Dave Three great scientific theories of the structure of the universe are the molecular, the corpuscular and the atomic. A fourth affirms, with Haeckel, the condensation or precipitation of matter from ether -- whose existence is proved by the condensation or precipitation ... A fifth theory is held by idiots, but it is doubtful if they know any more about the matter than the others. -- Ambrose Bierce, "The Devil's Dictionary" .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Wed Oct 3 20:50:50 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 13:50:50 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: Message-ID: On Wed, 3 Oct 2018, Daniel Prosser wrote: > Did you try following the instructions in the FAQ yet? Dan, Yes. adding that additional library directive made no difference with fontforge; will try with the other packages now. > It that doesn't work, building in a VM or LXC container is much less > disruptive than reinstalling the OS on your "production" machine. The new host is not yet the production machine. I'm trying to get it there. :-) Regards, Rich From rshepard at appl-ecosys.com Wed Oct 3 20:52:51 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 13:52:51 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181003195825.2b97f347@knotsUL> Message-ID: On Wed, 3 Oct 2018, Matteo Bernardini wrote: > it could mean also that you: Thank you, Matteo, Rich From rshepard at appl-ecosys.com Wed Oct 3 20:54:27 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 13:54:27 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: <20181003203331.GC6835@blackswan> References: <20181003195825.2b97f347@knotsUL> <20181003203331.GC6835@blackswan> Message-ID: On Wed, 3 Oct 2018, David Woodfall wrote: > This line: > > LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \ > > Try adding that under the CXXFLAGS= line in the slackbuild. It's > worth remembering as the first thing to try on a multilib system when > a build fails. Dave, Didn't help with fontforge. Will try now with more important packages such as OpenBLAS. Thanks, Rich From rshepard at appl-ecosys.com Wed Oct 3 21:03:46 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 14:03:46 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error Message-ID: On Wed, 3 Oct 2018, David Woodfall wrote: > Could you please make a build log and attach it to a reply here? Dave, An xzipped build log is attached. I'm really interested in learning what insights are hidden from me in the log. Thanks, Rich -------------- next part -------------- A non-text attachment was scrubbed... Name: build.log.xz Type: application/octet-stream Size: 60940 bytes Desc: URL: From rshepard at appl-ecosys.com Wed Oct 3 21:42:56 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 3 Oct 2018 14:42:56 -0700 (PDT) Subject: [Slackbuilds-users] Error building OpenBLAS [FIXED] In-Reply-To: <14bfadd8-19ba-ae81-1456-05d3a6d398c1@gmail.com> References: <14bfadd8-19ba-ae81-1456-05d3a6d398c1@gmail.com> Message-ID: On Wed, 3 Oct 2018, M?rio Antunes wrote: > If you want you can add TARGET=ZEN to the slackbuild. > The line with make. > > Since this appears to be a issue I can write a improved version of the > slackbuild to let users select the Target cpu with a variable. Mario, I added it to the first make line and the library built. So it appears that the newness of the CPU compared with the 4.4.x kernel and supporting packages are causing the build errors I'm hitting. Thanks for the fix! Best regards, Rich From 414N at slacky.it Thu Oct 4 07:59:27 2018 From: 414N at slacky.it (414N) Date: Thu, 4 Oct 2018 09:59:27 +0200 Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> Message-ID: <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> Hi Rich, I've got no problems too building glabels on a Slackware64 14.2 system with Eric's multilib packages installed. The compilation process outputs a lot of warnings, but none of them blocks the build. What compiler is picked up by the configure script? Could it be LLVM? You can see it in the summary after all the configure "checking for ..." messages. If it is gcc, what version are you using? Is it? "gcc-5.5.0_multilib-x86_64-1alien"? Alan Alberghini SBo clone: GitHub On 03/10/2018 22:05, Rich Shepard wrote: > On Thu, 4 Oct 2018, Willy Sudiarto Raharjo wrote: > >> glabels works fine here on pure x86_64 > > Willy, > > ? I need the multilibs library for some applications I regularly use. I > think that I need to upgrade to -current, upgrade Eric's multilibs, > and try > again. > > Regards, > > Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Thu Oct 4 12:50:09 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 4 Oct 2018 05:50:09 -0700 (PDT) Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> Message-ID: On Thu, 4 Oct 2018, 414N wrote: > I've got no problems too building glabels on a Slackware64 14.2 system > with Eric's multilib packages installed. > If it is gcc, what version are you using? Is it? > "gcc-5.5.0_multilib-x86_64-1alien"? Alan, The issue seems to be the newness of the hardware, most likely the CPU; perhaps also the motherboard. Packages that have built with no issues on the three 64-bit portables here that are older will not build on this new system. A couple of examples. OpenBLAS (which I need for GRASS, the spatial analysis tool) would not build until I added a line to the build script specifying TARGET=ZEN. 'ZEN' is the codename for AMD's Ryzen line of high-performance CPUs that were first released last year. Adding that target allowed OpenBLAS to build. AlienBOB wrote that he, too, has a Ryzen CPU in a desktop and experienced some failure issues just running. He fixed that by uupgrading the 14.2's kernel to one in the 4.14 series. In order to build GnuCash I need goffice/goffice8, and neither will build on this new box. But, LyX, TeXlive, and JabRef built flawlessly (and quickly.) All this seems to point to support for a CPU released well after the basic (and fully patched) 14.2 was released. Unless Those Who Know tell me not to upgrade to -current, just upgrade the kernel (and it's been more than 15 years since I built a custom kernel from kernel.org source; not since 2003 when I switched from Red Hat 7.4 to Slackware-8.0) I'll do the upgrade this coming weekend. After learning how best to do this. Thanks, Rich From didier at slint.fr Thu Oct 4 13:23:54 2018 From: didier at slint.fr (Didier Spaier) Date: Thu, 4 Oct 2018 15:23:54 +0200 Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> Message-ID: <9f786416-b575-675b-5fe5-54431a9f2361@slint.fr> Do what you want, but you probably will spare yourself a lot of issues (and many among us a lot of support provided for free to no avail) trying first to just install a genuine (not multilib) Slackware 14.2 and build these packages. Then if you encounter issues due to a too old kernel, you will be able to install (not build) a newer kernel. IIRC you can just install a kernel for Slackware-current in Slackware 14.2, if I am wrong please someone corrects me. I am not convinced that you be well prepared to run neither -current nor multilib, finding yourself how to sort the issues that can arise. You would need to first make a lot of thorough reading, like e.g. http://docs.slackware.com/slackware:multilib Thorough reading means understand not only the "how" but also the "why" of what you read instead of just apply blindly a recipe. Best, Didier PS If you need to run some 32-bit applications, it's usually possible to find other ones providing very similar features, else it's much easier to fire up a virtual machine with a 32-bit Slackware than to maintain a multilib system. And with 32G of RAM running virtual machines is not an issue at all On 10/4/18 2:50 PM, Rich Shepard wrote: > On Thu, 4 Oct 2018, 414N wrote: > >> I've got no problems too building glabels on a Slackware64 14.2 system >> with Eric's multilib packages installed. > >> If it is gcc, what version are you using? Is it? >> "gcc-5.5.0_multilib-x86_64-1alien"? > > > Alan, > > ? The issue seems to be the newness of the hardware, most likely the CPU; > perhaps also the motherboard. Packages that have built with no issues on the > three 64-bit portables here that are older will not build on this new > system. > > ? A couple of examples. OpenBLAS (which I need for GRASS, the spatial > analysis tool) would not build until I added a line to the build script > specifying TARGET=ZEN. 'ZEN' is the codename for AMD's Ryzen line of > high-performance CPUs that were first released last year. Adding that target > allowed OpenBLAS to build. > > ? AlienBOB wrote that he, too, has a Ryzen CPU in a desktop and experienced > some failure issues just running. He fixed that by uupgrading the 14.2's > kernel to one in the 4.14 series. > > ? In order to build GnuCash I need goffice/goffice8, and neither will build > on this new box. But, LyX, TeXlive, and JabRef built flawlessly (and > quickly.) All this seems to point to support for a CPU released well after > the basic (and fully patched) 14.2 was released. > > ? Unless Those Who Know tell me not to upgrade to -current, just upgrade the > kernel (and it's been more than 15 years since I built a custom kernel from > kernel.org source; not since 2003 when I switched from Red Hat 7.4 to > Slackware-8.0) I'll do the upgrade this coming weekend. After learning how > best to do this. > > Thanks, > > Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From idlemoor at slackbuilds.org Thu Oct 4 13:24:29 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Thu, 4 Oct 2018 14:24:29 +0100 Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> Message-ID: > ? The issue seems to be the newness of the hardware, most likely the CPU; That is true *only* with your OpenBLAS build. You have found a really good solution, thank you, I'm sure this will be helpful for other people. > ? AlienBOB wrote that he, too, has a Ryzen CPU in a desktop and experienced > some failure issues just running. He fixed that by uupgrading the 14.2's > kernel to one in the 4.14 series. The failure issues with Ryzen CPUs were random segfaults and lockups, *not* repeatable build failures when building specific packages. The solutions for those random segfaults and lockups are - upgrade your motherboard's bios - in your bios, disable C6 power saving see https://www.google.com/search?q=ryzen+c6+bug - use a newer kernel But that *won't* fix your glabels and Fontforge build problems. Your glabels and Fontforge problems seem to have a single common cause > ? In order to build GnuCash I need goffice/goffice8, and neither will build > on this new box. -- and probably the same with goffice too, although you haven't shared a build log yet. It looks to me like maybe a problem with your glib2 package. What version of glib2 do you have installed? Have you upgraded some Gnome libraries? Is your glib2 compat32 package the same version as your main glib2 package? I'm wondering if, for example, you might have installed the -current version of multilib onto your 14.2 Slackware 64 system. Maybe it would be worth doing 'removepkg glib2-compat32' and then trying those builds again. > Unless Those Who Know tell me not to upgrade to -current Do not upgrade to -current. Upgrading to -current is the quickest known way of creating a lot of build failures that nobody has ever seen before and that nobody can fix. Cheers -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Oct 4 13:26:54 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 4 Oct 2018 20:26:54 +0700 Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> Message-ID: <2f7cbb94-a756-ea78-7bc7-5b6a5679f295@slackbuilds.org> > ? The issue seems to be the newness of the hardware, most likely the CPU; > perhaps also the motherboard. Packages that have built with no issues on > the > three 64-bit portables here that are older will not build on this new > system. > > ? A couple of examples. OpenBLAS (which I need for GRASS, the spatial > analysis tool) would not build until I added a line to the build script > specifying TARGET=ZEN. 'ZEN' is the codename for AMD's Ryzen line of > high-performance CPUs that were first released last year. Adding that > target > allowed OpenBLAS to build. > > ? AlienBOB wrote that he, too, has a Ryzen CPU in a desktop and experienced > some failure issues just running. He fixed that by uupgrading the 14.2's > kernel to one in the 4.14 series. > > ? In order to build GnuCash I need goffice/goffice8, and neither will build > on this new box. But, LyX, TeXlive, and JabRef built flawlessly (and > quickly.) All this seems to point to support for a CPU released well after > the basic (and fully patched) 14.2 was released. > > ? Unless Those Who Know tell me not to upgrade to -current, just upgrade > the > kernel (and it's been more than 15 years since I built a custom kernel from > kernel.org source; not since 2003 when I switched from Red Hat 7.4 to > Slackware-8.0) I'll do the upgrade this coming weekend. After learning how > best to do this. Hi Rich I have had the same issue on my main desktop which is Ryzen-based CPU. The issue was solved by upgrading the firmware for the motherboard to the latest version and now i have no more issue with the Ryzen. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Thu Oct 4 13:31:41 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 4 Oct 2018 06:31:41 -0700 (PDT) Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: <9f786416-b575-675b-5fe5-54431a9f2361@slint.fr> References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> <9f786416-b575-675b-5fe5-54431a9f2361@slint.fr> Message-ID: On Thu, 4 Oct 2018, Didier Spaier wrote: > Do what you want, but you probably will spare yourself a lot of issues > (and many among us a lot of support provided for free to no avail) > trying first to just install a genuine (not multilib) Slackware 14.2 > and build these packages. Then if you encounter issues due to a too old > kernel, you will be able to install (not build) a newer kernel. IIRC you > can just install a kernel for Slackware-current in Slackware 14.2, if I > am wrong please someone corrects me. Didier, I hit those build issues over the past week, well before I installed the multilib paackages yesterday. I installed the latter only to enable running adobe-reader (and, perhaps, jpilot), taking a break from the more important packages that wouldn't build. The BIOS version is no older than a year ago; I'd need to check it again but when installed I recall seeing the version data as earlier this year or late last autumn. Rich From rshepard at appl-ecosys.com Thu Oct 4 13:33:11 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 4 Oct 2018 06:33:11 -0700 (PDT) Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: <2f7cbb94-a756-ea78-7bc7-5b6a5679f295@slackbuilds.org> References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> <2f7cbb94-a756-ea78-7bc7-5b6a5679f295@slackbuilds.org> Message-ID: On Thu, 4 Oct 2018, Willy Sudiarto Raharjo wrote: > I have had the same issue on my main desktop which is Ryzen-based CPU. The > issue was solved by upgrading the firmware for the motherboard to the > latest version and now i have no more issue with the Ryzen. Thanks, Willy. The firmware is less than a year old, but I'll look for the most current and upgrade to it. Best regards, Rich From dave at dawoodfall.net Thu Oct 4 14:00:13 2018 From: dave at dawoodfall.net (David Woodfall) Date: Thu, 4 Oct 2018 15:00:13 +0100 Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> Message-ID: <20181004140013.GE6835@blackswan> On Thursday 4 October 2018 05:50, Rich Shepard put forth the proposition: > On Thu, 4 Oct 2018, 414N wrote: > > > I've got no problems too building glabels on a Slackware64 14.2 system > > with Eric's multilib packages installed. > > > If it is gcc, what version are you using? Is it? > > "gcc-5.5.0_multilib-x86_64-1alien"? Rich, Sorry to reiterate this point, and I apologise if it seems obvious to you, but just to be clear, I'm wondering how long ago you installed the multilib packages and if you check for updates? It's a good idea to do an rysnc of the multilib server from time-to-time to check if there have been any updates. Dave > Alan, > > The issue seems to be the newness of the hardware, most likely the CPU; > perhaps also the motherboard. Packages that have built with no issues on the > three 64-bit portables here that are older will not build on this new > system. > > A couple of examples. OpenBLAS (which I need for GRASS, the spatial > analysis tool) would not build until I added a line to the build script > specifying TARGET=ZEN. 'ZEN' is the codename for AMD's Ryzen line of > high-performance CPUs that were first released last year. Adding that target > allowed OpenBLAS to build. > > AlienBOB wrote that he, too, has a Ryzen CPU in a desktop and experienced > some failure issues just running. He fixed that by uupgrading the 14.2's > kernel to one in the 4.14 series. > > In order to build GnuCash I need goffice/goffice8, and neither will build > on this new box. But, LyX, TeXlive, and JabRef built flawlessly (and > quickly.) All this seems to point to support for a CPU released well after > the basic (and fully patched) 14.2 was released. > > Unless Those Who Know tell me not to upgrade to -current, just upgrade the > kernel (and it's been more than 15 years since I built a custom kernel from > kernel.org source; not since 2003 when I switched from Red Hat 7.4 to > Slackware-8.0) I'll do the upgrade this coming weekend. After learning how > best to do this. > > Thanks, > > Rich -- Dave Boston State House is the hub of the Solar System. You couldn't pry that out of a Boston man if you had the tire of all creation straightened out for a crowbar. -- O. W. Holmes .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Thu Oct 4 14:10:49 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 4 Oct 2018 07:10:49 -0700 (PDT) Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: <20181004140013.GE6835@blackswan> References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> <20181004140013.GE6835@blackswan> Message-ID: On Thu, 4 Oct 2018, David Woodfall wrote: > Sorry to reiterate this point, and I apologise if it seems obvious to you, > but just to be clear, I'm wondering how long ago you installed the > multilib packages and if you check for updates? Dave, Yesterday morning, Oct. 3rd, about 10:00 am PDT, using the lftp command for the 14.2 builds. I installed them to run adobe-reader, taking a break from trying to build libraries and other packages for the past week-and-a-half and encountering build errors. Regards, Rich From rshepard at appl-ecosys.com Thu Oct 4 14:20:15 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 4 Oct 2018 07:20:15 -0700 (PDT) Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: <2f7cbb94-a756-ea78-7bc7-5b6a5679f295@slackbuilds.org> References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> <2f7cbb94-a756-ea78-7bc7-5b6a5679f295@slackbuilds.org> Message-ID: On Thu, 4 Oct 2018, Willy Sudiarto Raharjo wrote: > I have had the same issue on my main desktop which is Ryzen-based CPU. The > issue was solved by upgrading the firmware for the motherboard to the > latest version and now i have no more issue with the Ryzen. Willy, I just downloaded the BIOS firmware from 2018-09-21. That's certainly newer than the installed version. Will upgrade this morning and try building some packages. I have a spatial interpolation model to run first so it will be a bit before I get to the hardware issues. Thanks again for the pointer, Rich From rshepard at appl-ecosys.com Thu Oct 4 16:50:54 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 4 Oct 2018 09:50:54 -0700 (PDT) Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> <2f7cbb94-a756-ea78-7bc7-5b6a5679f295@slackbuilds.org> Message-ID: On Thu, 4 Oct 2018, Rich Shepard wrote: > I just downloaded the BIOS firmware from 2018-09-21. That's certainly > newer than the installed version. Will upgrade this morning and try > building some packages. I have a spatial interpolation model to run first > so it will be a bit before I get to the hardware issues. Status update. The original BIOS firmware on the motherboard (an Asus Prime X470-Pro) was version 4018 dated 2018-07-12. I just upgraded it to version 4024 dated 2018-09-18. When I tried building the glabels package it quit when it didn't find a make target for a required file: lgl-db.c:134:1: note: in expansion of macro 'G_DEFINE_TYPE' G_DEFINE_TYPE (lglDbModel, lgl_db_model, G_TYPE_OBJECT); ^ Makefile:583: recipe for target 'lgl-db.lo' failed make[2]: *** [lgl-db.lo] Error 1 make[2]: Leaving directory '/tmp/SBo/glabels-3.4.0/libglabels' Makefile:509: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/glabels-3.4.0' Makefile:439: recipe for target 'all' failed make: *** [all] Error 2 There are no specific dependencies for glabels, and this does look like a resolveable hurdle and not a firmware issue. Of course, I may well be wrong about this. Regards, Rich From rshepard at appl-ecosys.com Thu Oct 4 17:11:30 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 4 Oct 2018 10:11:30 -0700 (PDT) Subject: [Slackbuilds-users] Another build error: glabels In-Reply-To: References: <89b815ee-5b28-7aed-df05-314ee6e3efa9@slackbuilds.org> <8f964e56-0032-efbe-9ea4-658bba9f915b@slacky.it> <2f7cbb94-a756-ea78-7bc7-5b6a5679f295@slackbuilds.org> Message-ID: On Thu, 4 Oct 2018, Rich Shepard wrote: > There are no specific dependencies for glabels, and this does look like a > resolveable hurdle and not a firmware issue. Of course, I may well be > wrong about this. Well, the BIOS firmware is the latest release and still packages won't build (e.g., wxPython-3.0.2.0; the same type of issues both before and after installation of multilibs.) I now know not to upgrade to -current. A kernel upgrade should not break anything as far as I know. Any other steps I should take? Rich From dave at dawoodfall.net Thu Oct 4 22:54:01 2018 From: dave at dawoodfall.net (David Woodfall) Date: Thu, 4 Oct 2018 23:54:01 +0100 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: Message-ID: <20181004225401.GF6835@blackswan> On Wednesday 3 October 2018 14:03, Rich Shepard put forth the proposition: > On Wed, 3 Oct 2018, David Woodfall wrote: > > > Could you please make a build log and attach it to a reply here? > > Dave, > > An xzipped build log is attached. I'm really interested in learning what > insights are hidden from me in the log. > > Thanks, > > Rich After doing some building and diffing what sticks out is that in your log make is including /usr/lib/glib-2.0/include/glibconfig.h Whereas my log shows /usr/lib64/glib-2.0/include/glibconfig.h This is also on a 14.2 multilib system. Can you test the following change in the slackbuild just after the CFLAGS= and CXXFLAGS= lines add: GLIB_CFLAGS="-I/usr/lib$LIBDIRSUFFIX/glib-2.0/include" \ If that doesn't work you could try exporting the variable and remove the '\' on the end. It's a bit of a long shot but it may help. Something in your environment seems to be causing the build process to think it's not x86_64 for some reason. As others have said, you may want to think about building packages in a non-multilib VM when this kind of thing happens. I tend to use a chrooted installation for this because it takes no extra software and you don't need to boot anything to use it either. -- Dave "I'm not under the alkafluence of inkahol that some thinkle peep I am. It's just the drunker I sit here the longer I get." .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at dawoodfall.net Thu Oct 4 22:55:59 2018 From: dave at dawoodfall.net (David Woodfall) Date: Thu, 4 Oct 2018 23:55:59 +0100 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: <20181004225401.GF6835@blackswan> References: <20181004225401.GF6835@blackswan> Message-ID: <20181004225559.GG6835@blackswan> On Thursday 4 October 2018 23:54, Dave Woodfall put forth the proposition: > On Wednesday 3 October 2018 14:03, > Rich Shepard put forth the proposition: > > On Wed, 3 Oct 2018, David Woodfall wrote: > > > > > Could you please make a build log and attach it to a reply here? > > > > Dave, > > > > An xzipped build log is attached. I'm really interested in learning what > > insights are hidden from me in the log. > > > > Thanks, > > > > Rich > > After doing some building and diffing what sticks out is that in your > log make is including > > /usr/lib/glib-2.0/include/glibconfig.h > > Whereas my log shows > > /usr/lib64/glib-2.0/include/glibconfig.h > > This is also on a 14.2 multilib system. > > Can you test the following change in the slackbuild just after the > CFLAGS= and CXXFLAGS= lines add: > > GLIB_CFLAGS="-I/usr/lib$LIBDIRSUFFIX/glib-2.0/include" \ > > If that doesn't work you could try exporting the variable and remove > the '\' on the end. If you export it, it needs to go somewhere /above/ the CFLAGS= line. > It's a bit of a long shot but it may help. Something in your > environment seems to be causing the build process to think it's not > x86_64 for some reason. As others have said, you may want to think > about building packages in a non-multilib VM when this kind of thing > happens. I tend to use a chrooted installation for this because it > takes no extra software and you don't need to boot anything to use > it either. > > -- > Dave -- Dave Ankh if you love Isis. .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From yth at ythogtha.org Fri Oct 5 13:33:13 2018 From: yth at ythogtha.org (Arnaud) Date: Fri, 5 Oct 2018 15:33:13 +0200 Subject: [Slackbuilds-users] brlcad, broken update submitted Message-ID: <20181005153313.fa3243c50980ed7b9351da73@ythogtha.org> Hi everybody, oops, I did it again... Well, I've submitted an update to brlcad, but it doesn't work. I throughly tested it, but for some reason, I retested the build and execution of the old version - which we already knew was working - instead of the new one, and the new one does not build. So, please, is it possible to - well... - remove it from next update ? I hope to make it work before tomorrow, but until then there'd better not be an update of brlcad tomorrow ^^ Pretty sorry... I do hope the game I added - which you'll be able to play with tomorrow's update, yay ! - will please you, and make up with sympathy what I'm today lacking in efficiency ^^ -- Arnaud From rshepard at appl-ecosys.com Fri Oct 5 14:41:50 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 5 Oct 2018 07:41:50 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: <20181004225559.GG6835@blackswan> References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> Message-ID: On Thu, 4 Oct 2018, David Woodfall wrote: > After doing some building and diffing what sticks out is that in your > log make is including > > /usr/lib/glib-2.0/include/glibconfig.h > > Whereas my log shows > > /usr/lib64/glib-2.0/include/glibconfig.h > > This is also on a 14.2 multilib system. > > Can you test the following change in the slackbuild just after the > CFLAGS= and CXXFLAGS= lines add: > > GLIB_CFLAGS="-I/usr/lib$LIBDIRSUFFIX/glib-2.0/include" \ > > If that doesn't work you could try exporting the variable and remove > the '\' on the end. Dave, That added GLIB_CFLAGS line is already in the build script. What I find puzzling is that so many other libraries are built before this one fails. If the makefile was looking in /usr/lib/ rather than /usr/lib64/ I'd expect the build to fail at the first library. Regardless, I don't need fontforge on the new desktop. Perhaps some time in the future it might be needed, but the probability is quite low. My focus is getting a working server/workstation and I need to focus on critical files. Perhaps when 15.0 comes out all these issues will go away. Thanks very much for your efforts with fontforge. Best regards, Rich From dave at dawoodfall.net Fri Oct 5 14:56:40 2018 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 5 Oct 2018 15:56:40 +0100 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> Message-ID: <20181005145640.GI6835@blackswan> On Friday 5 October 2018 07:41, Rich Shepard put forth the proposition: > On Thu, 4 Oct 2018, David Woodfall wrote: > > > After doing some building and diffing what sticks out is that in your > > log make is including > > > > /usr/lib/glib-2.0/include/glibconfig.h > > > > Whereas my log shows > > > > /usr/lib64/glib-2.0/include/glibconfig.h > > > > This is also on a 14.2 multilib system. > > > > Can you test the following change in the slackbuild just after the > > CFLAGS= and CXXFLAGS= lines add: > > > > GLIB_CFLAGS="-I/usr/lib$LIBDIRSUFFIX/glib-2.0/include" \ > > > > If that doesn't work you could try exporting the variable and remove > > the '\' on the end. > > Dave, > > That added GLIB_CFLAGS line is already in the build script. Eh? Which version and where did you get it? Current version for 14.2 is 20170731 and there is no GLIB_CFLAGS in there. I had to double check again that because I maintain it. Aside from that you could also try using CPPFLAGS with the setting. > What I find > puzzling is that so many other libraries are built before this one fails. If > the makefile was looking in /usr/lib/ rather than /usr/lib64/ I'd expect the > build to fail at the first library. No always true. I forced it to look in /usr/lib and it didn't fail until the point that yours did, quite far into the build. > Regardless, I don't need fontforge on the new desktop. Perhaps some time > in the future it might be needed, but the probability is quite low. Which application needed it? It's not the most user-friendly thing in the world, for new users anyway. Font editing is in a realm of its own. > My focus is getting a working server/workstation and I need to focus on > critical files. Perhaps when 15.0 comes out all these issues will go away. > > Thanks very much for your efforts with fontforge. > > Best regards, > > Rich -- Dave A copy of the universe is not what is required of art; one of the damned things is ample. -- Rebecca West .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Fri Oct 5 15:24:43 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 5 Oct 2018 08:24:43 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: <20181005145640.GI6835@blackswan> References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> <20181005145640.GI6835@blackswan> Message-ID: On Fri, 5 Oct 2018, David Woodfall wrote: > Eh? Which version and where did you get it? Current version for 14.2 is > 20170731 and there is no GLIB_CFLAGS in there. I had to double check again > that because I maintain it. Dave, From a suggestion provided by someone here for a different package. > Aside from that you could also try using CPPFLAGS with the setting. Okay. > Which application needed it? It's not the most user-friendly thing in the > world, for new users anyway. Font editing is in a realm of its own. Last year some time I needed to convert no-longer-supported fonts (Type1?) to .odf and fontforge did the trick. Also in realms of their own are typography, page layout, and similar arts best left to experts. :-) Best regards, Rich From dave at dawoodfall.net Fri Oct 5 15:29:48 2018 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 5 Oct 2018 16:29:48 +0100 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> <20181005145640.GI6835@blackswan> Message-ID: <20181005152948.GJ6835@blackswan> On Friday 5 October 2018 08:24, Rich Shepard put forth the proposition: > On Fri, 5 Oct 2018, David Woodfall wrote: > > > Eh? Which version and where did you get it? Current version for 14.2 is > > 20170731 and there is no GLIB_CFLAGS in there. I had to double check again > > that because I maintain it. > > Dave, > > From a suggestion provided by someone here for a different package. Ah well, I have no idea what is in that so I can't really help any further. > > Aside from that you could also try using CPPFLAGS with the setting. > > Okay. > > > Which application needed it? It's not the most user-friendly thing in the > > world, for new users anyway. Font editing is in a realm of its own. > > Last year some time I needed to convert no-longer-supported fonts (Type1?) to .odf > and fontforge did the trick. > > Also in realms of their own are typography, page layout, and similar arts > best left to experts. :-) > > Best regards, > > Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -- Dave "Laughter is the closest distance between two people." -- Victor Borge .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Fri Oct 5 15:35:29 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 5 Oct 2018 08:35:29 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: <20181005145640.GI6835@blackswan> References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> <20181005145640.GI6835@blackswan> Message-ID: On Fri, 5 Oct 2018, David Woodfall wrote: > Aside from that you could also try using CPPFLAGS with the setting. Dave, Unfortunately this makes no difference. Thanks again for all your efforts, Rich From dave at dawoodfall.net Fri Oct 5 16:12:27 2018 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 5 Oct 2018 17:12:27 +0100 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> <20181005145640.GI6835@blackswan> Message-ID: <20181005161227.GK6835@blackswan> On Friday 5 October 2018 08:24, Rich Shepard put forth the proposition: > On Fri, 5 Oct 2018, David Woodfall wrote: > > > Eh? Which version and where did you get it? Current version for 14.2 is > > 20170731 and there is no GLIB_CFLAGS in there. I had to double check again > > that because I maintain it. > > Dave, > > From a suggestion provided by someone here for a different package. Don't ask for support for slackbuilds that don't originate from slackbuilds.org. I spent a wasted few hours yesterday trying to find a solution to fix it since I maintain it. If you want help with someone else's build then go to them and don't waste my time. > > Aside from that you could also try using CPPFLAGS with the setting. > > Okay. > > > Which application needed it? It's not the most user-friendly thing in the > > world, for new users anyway. Font editing is in a realm of its own. > > Last year some time I needed to convert no-longer-supported fonts (Type1?) to .odf > and fontforge did the trick. > > Also in realms of their own are typography, page layout, and similar arts > best left to experts. :-) > > Best regards, > > Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -- Dave You will be surprised by a loud noise. .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rshepard at appl-ecosys.com Fri Oct 5 16:27:53 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 5 Oct 2018 09:27:53 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: <20181005161227.GK6835@blackswan> References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> <20181005145640.GI6835@blackswan> <20181005161227.GK6835@blackswan> Message-ID: On Fri, 5 Oct 2018, David Woodfall wrote: >> From a suggestion provided by someone here for a different package. > > Don't ask for support for slackbuilds that don't originate from > slackbuilds.org. I spent a wasted few hours yesterday trying to find > a solution to fix it since I maintain it. If you want help with > someone else's build then go to them and don't waste my time. Dave, I was not sufficiently clear. This was a suggestion offered for another SBo package. The package maintaier offered the same syntax for the slackbuild script, LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \, as you did. Several respondents on the mail list have offered suggestions for the few packages that won't build on this new hardware, including Willy's advice to upgrade the BIOS firmware, which I did. If a problem is not related to a slackbuild script I would not be asking for help from the SBo mail list. Rich From dave at dawoodfall.net Fri Oct 5 16:35:42 2018 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 5 Oct 2018 17:35:42 +0100 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> <20181005145640.GI6835@blackswan> <20181005161227.GK6835@blackswan> Message-ID: <20181005163542.GL6835@blackswan> On Friday 5 October 2018 09:27, Rich Shepard put forth the proposition: > On Fri, 5 Oct 2018, David Woodfall wrote: > > > > From a suggestion provided by someone here for a different package. > > > > Don't ask for support for slackbuilds that don't originate from > > slackbuilds.org. I spent a wasted few hours yesterday trying to find > > a solution to fix it since I maintain it. If you want help with > > someone else's build then go to them and don't waste my time. > > Dave, > > I was not sufficiently clear. This was a suggestion offered for another > SBo package. The package maintaier offered the same syntax for the > slackbuild script, LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \, as you did. I said to use GLIB_CFLAGS with '-I', not LDFLAGS with '-L'. Totally different things. You stated that the script already had GLIB_CFALGS in it. I have built and used fontforge on multilib many times with no problems at all. Something in your system is screwy. Anyway I've spent enough time on this. > Several respondents on the mail list have offered suggestions for the few > packages that won't build on this new hardware, including Willy's advice to > upgrade the BIOS firmware, which I did. > > If a problem is not related to a slackbuild script I would not be asking > for help from the SBo mail list. > > 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/ > -- Dave Cinemuck, n.: The combination of popcorn, soda, and melted chocolate which covers the floors of movie theaters. -- Rich Hall, "Sniglets" .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From didier at slint.fr Fri Oct 5 16:41:18 2018 From: didier at slint.fr (Didier Spaier) Date: Fri, 5 Oct 2018 18:41:18 +0200 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> <20181005145640.GI6835@blackswan> <20181005161227.GK6835@blackswan> Message-ID: <32e2ead5-3754-f562-7605-2654e55446b9@slint.fr> Rich, I am pretty sure you are *not* building an a *clean* 64-bit only system with *no multilib* but with all patches listed in the ChangeLog applied. Until you reinstall from scratch Slackware64-14.2 and do *not* install on it any package not shipped in Slackware but those built from SlackBuilds that you downloaded from https://slackwbuilds.org, you are just making people trying to help you on this list waste their time. Didier On 10/5/18 6:27 PM, Rich Shepard wrote: > On Fri, 5 Oct 2018, David Woodfall wrote: > >>> ? From a suggestion provided by someone here for a different package. >> >> Don't ask for support for slackbuilds that don't originate from >> slackbuilds.org. I spent a wasted few hours yesterday trying to find >> a solution to fix it since I maintain it. If you want help with >> someone else's build then go to them and don't waste my time. > > Dave, > > ? I was not sufficiently clear. This was a suggestion offered for another > SBo package. The package maintaier offered the same syntax for the > slackbuild script, LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \, as you did. > > ? Several respondents on the mail list have offered suggestions for the few > packages that won't build on this new hardware, including Willy's advice to > upgrade the BIOS firmware, which I did. > > ? If a problem is not related to a slackbuild script I would not be asking > for help from the SBo mail list. > > Rich From yth at ythogtha.org Fri Oct 5 17:08:25 2018 From: yth at ythogtha.org (Arnaud) Date: Fri, 5 Oct 2018 19:08:25 +0200 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: <32e2ead5-3754-f562-7605-2654e55446b9@slint.fr> References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> <20181005145640.GI6835@blackswan> <20181005161227.GK6835@blackswan> <32e2ead5-3754-f562-7605-2654e55446b9@slint.fr> Message-ID: <20181005190825.ea877f63fec820093ab57d05@ythogtha.org> > Rich, > > I am pretty sure you are *not* building an a *clean* 64-bit only system with > *no multilib* but with all patches listed in the ChangeLog applied. > > Until you reinstall from scratch Slackware64-14.2 and do *not* install on it > any package not shipped in Slackware but those built from SlackBuilds that > you downloaded from https://slackwbuilds.org, you are just making people > trying to help you on this list waste their time. > > Didier I'll go further : My suggestion, Rich, has been already presented in this thread. It is to create a chrooted clean 64-14.2 fully patched installation. * Create a destination directory, for example : /srv/slackware/ * Simply go to a source directory, remove all kdei languages you won't use (or all of kdei) : slackware64-14.2/slackware64$ installpkg --root=/srv/slackware/ */*.t?z * Then go inside it : $ chroot /srv/slackware/ bash -l * You'd better mount /proc /dev and /sys * Here you configure slackpkg, and update your all chrooted slackware for recent patches. (don't forget to copy /etc/resolv.conf into /srv/slackware/etc/resolv.conf to get network working inside the chroot). * Then you build whatever you need, installing dependencies. * And when you're finished, you remove all locally built installed packages for the next package you'll try to install. I'd advise installing python3 and leaving it there, many python SlackBuilds are silently building for python3 if it is installed, and it might be what you want for your box, and python3 being present does not pose any side problem anyway. The packages you built on the chrooted environment should work on your multilib box without any problem, if they don't then your slackware install is somehow broken. I started doing this after having troubles building too many packages, multilib is a problem for some slackbuilds (for some time I used to move /usr/lib/ into something like /usr/lib32/ before building a problematic packages, just to be sure it found only /usr/lib64/, but it *is* ugly). Furthermore you have a way better control over what you are building against. If *that* still fails, then you have a pretty good reason to ask for help. Else, trying to figure out what may be wrong with your specific box, with your specific environment, with your specific packages installed, is going to be very hard, and most of the time not very useful. The advantage of chroot over a VM is that it is waaaay easier to setup, and it takes less disk space too, and less resources (it's completely passive : it does nothing when you do nothing). And mostly, for what you're doing (build packages for your box) there are no disadvantages. I'll clean and send a script that does all this stuff automagically. -- Arnaud From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Fri Oct 5 17:10:33 2018 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Fri, 5 Oct 2018 19:10:33 +0200 Subject: [Slackbuilds-users] Atlas In-Reply-To: <0c6b5575-eea4-e028-c2e5-1f41508efde3@skmail.ikp.physik.tu-darmstadt.de> References: <20180910175458.GA18785@jdiamond-mb.acadiau.ca> <0c6b5575-eea4-e028-c2e5-1f41508efde3@skmail.ikp.physik.tu-darmstadt.de> Message-ID: On 09/11/2018 11:29 AM, Serban Udrea wrote: > On 09/10/2018 07:54 PM, Jim Diamond via SlackBuilds-users wrote: >> I am trying to build Atlas.? On my system (S64-14.2) the procedure it >> goes through to pick a compiler comes up with >> ???????? /usr/bin/g++-gcc-5.5.0 >> rather than >> ???????? /usr/bin/gcc-5.5.0 >> or >> ???????? /usr/bin/gcc >> ... > > Hello, > > this is an issue I know about. I'm pretty sure I proposed a patch to upstream but > never got an answer... Hello, It would be nice to know if this issue is solved or not. And I have to correct myself: on Sourceforge there is an answer to my sending the patch. Unfortunately I didn't notice it for a long time :-( Best regards, Serban Udrea From rshepard at appl-ecosys.com Fri Oct 5 17:46:10 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 5 Oct 2018 10:46:10 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: <32e2ead5-3754-f562-7605-2654e55446b9@slint.fr> References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> <20181005145640.GI6835@blackswan> <20181005161227.GK6835@blackswan> <32e2ead5-3754-f562-7605-2654e55446b9@slint.fr> Message-ID: On Fri, 5 Oct 2018, Didier Spaier wrote: > I am pretty sure you are *not* building an a *clean* 64-bit only system > with *no multilib* but with all patches listed in the ChangeLog applied. Didier, I installed the multilibs this past Wednesday. I had issues last week with SBo packages not building. > Until you reinstall from scratch Slackware64-14.2 and do *not* install on it > any package not shipped in Slackware but those built from SlackBuilds that > you downloaded from https://slackwbuilds.org, you are just making people > trying to help you on this list waste their time. I have an older desktop (never activeated) with an Asus Sabertooth 990fx motherboard and AMD FX-8150 CPU. I'll install 14.2 on it when the new hard drive arrives, apply all patches, and then try to build the SBo packages. This hardware is from 2011, not 2018 and I'm sure that will make a difference. Regards, Rich From rshepard at appl-ecosys.com Fri Oct 5 17:49:06 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 5 Oct 2018 10:49:06 -0700 (PDT) Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: <20181005190825.ea877f63fec820093ab57d05@ythogtha.org> References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> <20181005145640.GI6835@blackswan> <20181005161227.GK6835@blackswan> <32e2ead5-3754-f562-7605-2654e55446b9@slint.fr> <20181005190825.ea877f63fec820093ab57d05@ythogtha.org> Message-ID: On Fri, 5 Oct 2018, Arnaud wrote: > I'll go further : > My suggestion, Rich, has been already presented in this thread. > It is to create a chrooted clean 64-14.2 fully patched installation. Arnaud, Yesterday I ordered a hard drive for an unused, 7-year-old desktop system. I'll install 14.2 on it (including patches) and start installing SBo packages. If I need to hold this new box until 15.0 comes out, so be it. Regards, Rich From didier at slint.fr Fri Oct 5 18:13:20 2018 From: didier at slint.fr (Didier Spaier) Date: Fri, 5 Oct 2018 20:13:20 +0200 Subject: [Slackbuilds-users] Fontforge build error In-Reply-To: References: <20181004225401.GF6835@blackswan> <20181004225559.GG6835@blackswan> <20181005145640.GI6835@blackswan> <20181005161227.GK6835@blackswan> <32e2ead5-3754-f562-7605-2654e55446b9@slint.fr> Message-ID: <8b3dd073-617b-ba78-86ec-1befe50e9012@slint.fr> On 10/5/18 7:46 PM, Rich Shepard wrote: > ? I have an older desktop (never activeated) with an Asus Sabertooth 990fx > motherboard and AMD FX-8150 CPU. I'll install 14.2 on it when the new hard > drive arrives, apply all patches, and then try to build the SBo packages. > This hardware is from 2011, not 2018 and I'm sure that will make a > difference. None of the error messages you showed can lead to make such an assumption, let alone be sure of that. The *only* way to make sure would be to make a clean 14.2 installation with all patches applied and see what you get building the packages from the SBo slackbuilds. But yes ,make a clean install on the old box and see what happens. At least that will be a first step in the good direction. Didier From idlemoor at slackbuilds.org Fri Oct 5 18:41:44 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Fri, 5 Oct 2018 19:41:44 +0100 Subject: [Slackbuilds-users] brlcad, broken update submitted In-Reply-To: <20181005153313.fa3243c50980ed7b9351da73@ythogtha.org> References: <20181005153313.fa3243c50980ed7b9351da73@ythogtha.org> Message-ID: > Hi everybody, Hi Arnaud! > oops, I did it again... > Well, I've submitted an update to brlcad, but it doesn't work. > I throughly tested it, but for some reason, I retested the build and execution > of the old version - which we already knew was working - instead of the new one, > and the new one does not build. > > So, please, is it possible to - well... - remove it from next update ? > I hope to make it work before tomorrow, but until then there'd better not be an > update of brlcad tomorrow ^^ Errrr, I simply added gdal (and therefore proj) to REQUIRES and now it builds fine for me... ;-) Thanks for another good update ;-) *But* if you still think I should remove it, I can do that, no problem! Cheers -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From yth at ythogtha.org Fri Oct 5 23:55:40 2018 From: yth at ythogtha.org (Arnaud) Date: Sat, 6 Oct 2018 01:55:40 +0200 Subject: [Slackbuilds-users] brlcad, broken update submitted In-Reply-To: References: <20181005153313.fa3243c50980ed7b9351da73@ythogtha.org> Message-ID: <20181006015540.b8aa323e2002b915ff244340@ythogtha.org> > > Hi everybody, > > Hi Arnaud! > > > oops, I did it again... > > Well, I've submitted an update to brlcad, but it doesn't work. > > I throughly tested it, but for some reason, I retested the build and > > execution of the old version - which we already knew was working - instead > > of the new one, and the new one does not build. > > > > So, please, is it possible to - well... - remove it from next > > update ? I hope to make it work before tomorrow, but until then there'd > > better not be an update of brlcad tomorrow ^^ > > Errrr, I simply added gdal (and therefore proj) to REQUIRES and now it > builds fine for me... ;-) > > Thanks for another good update ;-) > > *But* if you still think I should remove it, I can do that, no problem! > > Cheers > -D. > Thank you ! Yeah, that'll work. So keep it that way, there'll be another update later with compilation options and things like that. Because, I don't really understand why that helps... I'm currently fiddling with build options and my tests are showing that it doesn't seem to find installed gdal when it's there. And there are a few undocumented configuration options, even a QT5 version that doesn't build (but fails at 50%, just to be sure you loose as much time as possible :)). So, go for it, and I'll investigate further on my side ! -- Arnaud From willysr at slackbuilds.org Sat Oct 6 01:03:24 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 6 Oct 2018 08:03:24 +0700 Subject: [Slackbuilds-users] Updates - 20181006.1 Message-ID: <0169659b-ea28-abfc-26f4-99e6519a28e1@slackbuilds.org> Hi, This is the first update in October and i think i made some tiny mistakes while doing this public update. newlib-headers was removed, but it was still referenced in the arm-gcc. I noticed this at the late phase of the public update, but as the new arm-gcc can be built without newlib-headers, we will remove them from arm-gcc REQUIREMENTS in the next batch of update. Thanks to all contributors/maintainers who had done a great job of adding more scripts and maintaining existing ones in our repository. A gentle reminder to maintainers who submitted via submission form, please make sure to grab the latest version of your SlackBuild files before pushing an update. We may have modified your scripts to comply with our templates and standards. Even better, start forking our public repositories in GitHub and GitLab and send us Merge Request / Pull Requests. Sat Oct 6 00:26:19 UTC 2018 academic/ladr: Switch homepage and download to https. academic/wxMaxima: Switch homepage to https. audio/xmms-pulse: Added (XMMS PulseAudio plugin). desktop/Zafiro-icons: Updated for version 0.6. desktop/jgmenu: Updated for version 1.3. desktop/obmenu-generator: Updated for version 0.85. desktop/oranchelo-icon-theme: Updated for version 0.7.8.1. desktop/wmalauncher: Updated for version 2018.1002. desktop/zuki-themes: Updated for version 3.28.3. development/arm-binutils: Updated for version 2.31. development/arm-gdb: Updated for version 8.2. development/diffoscope: Updated for version 103. development/dpkg: Updated for version 1.19.1. development/dwarf: Updated for version 20180809 development/eclipse-php: Updated for version 201809. development/fossil: Updated for version 2.7. development/hhvm: Updated for version 3.28.3 development/kforth: Switch homepage to archive.org. development/newlib-headers: Removed. development/newlib: Updated for version 3.0.0. development/universal-ctags: Updated for version d080788 development/yarn: Updated for version 1.10.1. games/edgar: Fix homepage. games/endless-sky: Added (2D space trading and combat game). games/gl-117: Fix homepage. games/stone_soup: Updated for version 0.22.1. gis/pgsql-ogr-fdw: Updated for version 1.0.7. gis/rasterio: Updated for version 1.0.8. graphics/brlcad: Updated for version 7.28.0. graphics/draw.io: Switch homepage to https. graphics/librecad: Updated for version 2.2.0rc1 + new maintainer. graphics/openimageio: Updated for version 1.8.15 graphics/qrencode: Updated for version 4.0.2 + new maintainer. libraries/CGAL: Updated for version 4.13. libraries/OpenBLAS: Updated for version 0.3.3. libraries/SDL2_mixer: Update README. libraries/SDL_kitchensink: Updated for version 1.0.6. libraries/exiftool: Updated for version 11.11. libraries/hoel: Updated for version 1.4.3. libraries/libfilezilla: Updated for version 0.14.0. libraries/libinput: Updated for version 1.12.0. libraries/libxls: Added (Extract Cell Data From Excel xls files). libraries/orcania: Updated for version 1.2.6. libraries/yder: Updated for version 1.4.2. misc/KeePass: Updated for version 2.40. misc/subsurface: Updated for version 4.8.3 multimedia/vgmplay: Added (the official player for VGM files). multimedia/x265: Updated for version 2.9. network/asterisk: Updated for version 13.23.1. network/axel: Updated for version 2.16.1 + new maintainer. network/filezilla: Updated for version 3.37.4. network/lighttpd: Updated for version 1.4.50. network/opera-developer: Updated for version 57.0.3090.0. network/opera: Updated for version 56.0.3051.31. network/otter: Switch homepage to https. network/prosody-mod-http-upload: Updated for version hg3341. network/qupzilla: Updated for version 2.2.6. network/riot-web: Updated for version 0.16.5. network/shorewall-core: Updated for version 5.2.1. network/shorewall6: Updated for version 5.2.1. network/shorewall: Updated for version 5.2.1. network/telegram: Updated for version 1.4.0. network/tor-browser: Updated for version 8.0.2. network/vivaldi: Updated for version 2.0.1309.37. network/yandex-browser-beta: Updated for version 18.9.1.882. network/zabbix_agentd: Updated for version 3.4.14 + new maintainer. network/zabbix_java_gateway: Added (distributed monitoring). network/zabbix_proxy: Updated for version 3.4.14 + new maintainer. network/zabbix_server: Updated for version 3.4.14 + new maintainer. office/gnucash-docs: Updated for version 3.3. office/gnucash: Updated for version 3.3. office/watson: Updated for version 1.6.0. perl/perl-File-Remove: Updated for version 1.58. perl/perl-Glib-Object-Introspection: Updated for version 0.046. perl/perl-glib: Updated for version 1.328. python/click: Updated for version 7.0. python/josepy: Updated for version 1.1.0. python/pickleshare: Updated for version 0.7.5. python/python-emoji: Updated for version 0.5.1. python/python-prometheus_client: Updated for version 0.4.0. python/python2-sip: Fix previously auto-renamed files python/python3-ipython: Updated for version 7.0.1. python/python3-jedi: Updated for version 0.13.1. python/python3-jupyter-ipykernel: Updated for version 5.0.0. python/python3-pickleshare: Updated for version 0.7.5. python/python3-prompt_toolkit: 2.0.4. python/scikit-learn: Updated for version 0.20.0. python/testpath: Updated for version 0.4.1. ruby/ruby-faraday: Updated for version 0.15.3. ruby/rubygem-mime-types-data: Updated for version 3.2018.0812. ruby/rubygem-mime-types: Updated for version 3.2.2. ruby/sequel: Updated for version 5.13.0. system/ansible: Updated for version 2.6.5. system/clamav: Updated for version 0.100.2. system/dosbox-dev: Updated for version 0.74.r4165. system/epson-inkjet-printer-escpr2: Updated for version 1.0.23. system/forkstat: Updated for version 0.02.06. system/heirloom-ed: Updated with extra build options. system/isdct: Updated for version 3.0.15. system/kitchen-sync: Updated for version 1.3. system/lbench: Updated for version 3.6. system/lynis: Updated for version 2.6.9. system/openrc: Removed branding. system/thermald: Updated for version 1.8. system/wine-staging: Updated for version 3.17. system/yakuake: Updated for version 2.9.9 + new maintainer. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From dpross1100 at msn.com Sat Oct 6 03:12:28 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 6 Oct 2018 03:12:28 +0000 Subject: [Slackbuilds-users] pavucontrol incompatible with new zuki-themes Message-ID: Hello, Today I upgraded to zuki-themes 3.28.3 that was included in the latest public update. Unfortunately, pavucontrol is garbled with the Zukitre theme included in this package, and also pasystray's menu is not displayed correctly. A screenshot of the pavucontrol window is attached. For my part, I have reverted back to 3.18.1. Is there a reason this was upgraded other than to have the latest and greatest? I am wondering if it is truly compatible with Slackware's version of gtk+3. Dan -------------- next part -------------- A non-text attachment was scrubbed... Name: zuki_incompatibility.png Type: image/png Size: 20967 bytes Desc: zuki_incompatibility.png URL: From markus.ka.rinne at gmail.com Sat Oct 6 06:38:26 2018 From: markus.ka.rinne at gmail.com (Markus Rinne) Date: Sat, 6 Oct 2018 09:38:26 +0300 Subject: [Slackbuilds-users] Updates - 20181006.1 In-Reply-To: <0169659b-ea28-abfc-26f4-99e6519a28e1@slackbuilds.org> References: <0169659b-ea28-abfc-26f4-99e6519a28e1@slackbuilds.org> Message-ID: <20181006063826.GA8708@tursas.sidaroth.foo> On Sat, Oct 06, 2018 at 08:03:24AM +0700, Willy Sudiarto Raharjo wrote: > A gentle reminder to maintainers who submitted via submission form, > please make sure to grab the latest version of your SlackBuild files > before pushing an update. We may have modified your scripts to comply > with our templates and standards. Even better, start forking our public > repositories in GitHub and GitLab and send us Merge Request / Pull Requests. Maybe the GitHub/GitLab workflow could be mentioned in slackbuilds.org web site? As far as I can see, it isn't currently. Markus From ole.andre.rodlie at gmail.com Sat Oct 6 11:43:39 2018 From: ole.andre.rodlie at gmail.com (=?UTF-8?Q?Ole-Andr=c3=a9_Rodlie?=) Date: Sat, 6 Oct 2018 13:43:39 +0200 Subject: [Slackbuilds-users] Updates - 20181006.1 In-Reply-To: <20181006063826.GA8708@tursas.sidaroth.foo> References: <0169659b-ea28-abfc-26f4-99e6519a28e1@slackbuilds.org> <20181006063826.GA8708@tursas.sidaroth.foo> Message-ID: Agree, I didn't even know github/gitlab was an alternative (why am I submitting tarballs when I can just do a pull request? :) ). Searching github ends up with: * https://github.com/Ponce/slackbuilds * https://github.com/willysr/slackbuilds Both marked as unoffical/mirror. The README refers to https://gitlab.com/SlackBuilds.org/slackbuilds.git (and of course slackbuilds.org). Where am I supposed to submit pull request on github? Ole-Andr? On 10/6/18 8:38 AM, Markus Rinne wrote > Maybe the GitHub/GitLab workflow could be mentioned in slackbuilds.org > web site? As far as I can see, it isn't currently. > > 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/ > From slackbuilds at jaxartes.net Sat Oct 6 11:51:11 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 6 Oct 2018 04:51:11 -0700 Subject: [Slackbuilds-users] Updates - 20181006.1 In-Reply-To: References: <0169659b-ea28-abfc-26f4-99e6519a28e1@slackbuilds.org> <20181006063826.GA8708@tursas.sidaroth.foo> Message-ID: On 2018-10-06 4:43 a.m., Ole-Andr? Rodlie wrote: > Agree, I didn't even know github/gitlab was an alternative (why am I > submitting tarballs when I can just do a pull request? :) ). > > Searching github ends up with: > > * https://github.com/Ponce/slackbuilds > > * https://github.com/willysr/slackbuilds > > Both marked as unoffical/mirror. The README refers to > https://gitlab.com/SlackBuilds.org/slackbuilds.git (and of course > slackbuilds.org). Where am I supposed to submit pull request on github? There may be mirrors on GitLab and GitHub, but the only git server that matters is the one that belongs to and is hosted by the SlackBuilds project: https://git.slackbuilds.org/. > On 10/6/18 8:38 AM, Markus Rinne wrote >> Maybe the GitHub/GitLab workflow could be mentioned in slackbuilds.org >> web site? As far as I can see, it isn't currently. >> >> ???? 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/ >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From willysr at slackbuilds.org Sat Oct 6 11:57:48 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 6 Oct 2018 18:57:48 +0700 Subject: [Slackbuilds-users] Updates - 20181006.1 In-Reply-To: <20181006063826.GA8708@tursas.sidaroth.foo> References: <0169659b-ea28-abfc-26f4-99e6519a28e1@slackbuilds.org> <20181006063826.GA8708@tursas.sidaroth.foo> Message-ID: <9dd1f91e-0b60-54ca-de7b-3c8468187837@slackbuilds.org> > Maybe the GitHub/GitLab workflow could be mentioned in slackbuilds.org > web site? As far as I can see, it isn't currently. I have posted the GitLab URL in the SBo's website As for GitHub, not all admins agreed on this yet, so currently only me that looks over PR over GitHub The URL is : https://github.com/SlackBuildsOrg/slackbuilds NOTE: GitHub/GitLab are only used for updating existing scripts, not for newly submission. New scripts must go through normal submission form as it must be saved in the database for searching purposes. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From yth at ythogtha.org Sat Oct 6 15:51:15 2018 From: yth at ythogtha.org (Arnaud) Date: Sat, 6 Oct 2018 17:51:15 +0200 Subject: [Slackbuilds-users] OpenAL has qt5 as optional dependency Message-ID: <20181006175115.e658268dc1df81adf00d5b4f@ythogtha.org> Hi ! I've just discovered that OpenAL has qt5 as optional dependency. For the binary : /usr/bin/alsoft-config It might be worth mentioning on the README. Or not. -- Arnaud From ozan.turkyilmaz at gmail.com Sun Oct 7 07:09:40 2018 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sun, 7 Oct 2018 12:09:40 +0500 Subject: [Slackbuilds-users] Updates - 20181006.1 In-Reply-To: <9dd1f91e-0b60-54ca-de7b-3c8468187837@slackbuilds.org> References: <0169659b-ea28-abfc-26f4-99e6519a28e1@slackbuilds.org> <20181006063826.GA8708@tursas.sidaroth.foo> <9dd1f91e-0b60-54ca-de7b-3c8468187837@slackbuilds.org> Message-ID: Willy Sudiarto Raharjo , 6 Eki 2018 Cmt, 16:57 tarihinde ?unu yazd?: > > I have posted the GitLab URL in the SBo's website > As for GitHub, not all admins agreed on this yet, so currently only me > that looks over PR over GitHub > The URL is : https://github.com/SlackBuildsOrg/slackbuilds > I have started moving my repos to gitlab. I even did the first update using gitlab merge request. We can send patches by email as well. -------------- next part -------------- An HTML attachment was scrubbed... URL: From arkadiusz at drabczyk.org Sun Oct 7 20:06:37 2018 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Sun, 7 Oct 2018 22:06:37 +0200 Subject: [Slackbuilds-users] Updates - 20181006.1 In-Reply-To: References: <0169659b-ea28-abfc-26f4-99e6519a28e1@slackbuilds.org> <20181006063826.GA8708@tursas.sidaroth.foo> <9dd1f91e-0b60-54ca-de7b-3c8468187837@slackbuilds.org> Message-ID: <20181007200637.GA5226@comp.lan> On Sun, Oct 07, 2018 at 12:09:40PM +0500, Ozan T?rky?lmaz wrote: > > Willy Sudiarto Raharjo , 6 Eki 2018 Cmt, 16:57 > tarihinde ?unu yazd?: > > > I have posted the GitLab URL in the SBo's website > As for GitHub, not all admins agreed on this yet, so currently only me > that looks over PR over GitHub > The URL is : https://github.com/SlackBuildsOrg/slackbuilds > > > I have started moving my repos to gitlab. I even did the first update using > gitlab merge request. We can send patches by email as well. That would be the best - git format-patch && mutt -H and you're done but some people don't like it https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-December/020398.html. There is also https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-September/017045.html, I use it like this: SBOSUBMIT_SUBMISSION_EMAIL= sbosubmit --comment="Upgrade to 6.6.2" --address=sbo -- Arkadiusz Drabczyk From harald.achitz at gmail.com Sun Oct 7 21:15:08 2018 From: harald.achitz at gmail.com (Harald Achitz) Date: Sun, 7 Oct 2018 23:15:08 +0200 Subject: [Slackbuilds-users] 3 Slackbuilds looking for new maintainer Message-ID: Hi, as a result of temporarily bans (several days) for nearly each post on LQ I did in the last months, I decided to cancel my paid LQ subscription. Now the LQ mod has banned me for ever. I knew already how horrible LQ is moderated from several mods, but this tells me the very rest I need to know about LQ. Since Slackware has decided to use this place, that I can not follow anymore, as it's community platform I have to wish Slackware all the best for it's future. No more development,or financial support from me for Slackware, Slackware developers or Slackware related projects. For Slackware this will not make any difference, other OS project and I can be happy about the resources available. However, one side effect is that the 3 Slackbuilds I maintain needs new maintainers. These are: slack https://slackbuilds.org/repository/14.2/network/slack/ slack desktop client I haven't updated this for a while since it's change to GTK3, and because if imho it uses insane amount of CPU/memory resources and the web client works much better. kcov https://slackbuilds.org/repository/14.2/development/kcov/ a code ocverage tool for C/C++, python and bash scripts nice talk from the author: https://www.youtube.com/watch?v=1QMHbp5LUKg sbbdep https://slackbuilds.org/repository/14.2/system/sbbdep/ The tool for exploring binary runtime dependencies on Slackware and Slackware based system. This build will barely ever change since what it does is final and works, I do not think that I now will ever finalise or release the features I have in the queue. All 3 builds are super simple, so there should not be any problems with them. If there are questions to them, I will for some time have a look at this thread and help if I can. Regards and all the best! -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Sun Oct 7 21:41:42 2018 From: didier at slint.fr (Didier Spaier) Date: Sun, 7 Oct 2018 23:41:42 +0200 Subject: [Slackbuilds-users] 3 Slackbuilds looking for new maintainer In-Reply-To: References: Message-ID: <28933cf9-2c48-f446-e10a-e3480ef23901@slint.fr> Hello Harald, On 10/7/18 11:15 PM, Harald Achitz wrote > as a result of temporarily bans (several days) for nearly each post on LQ I did in the last months, I decided to cancel my paid LQ subscription. Now the LQ mod has banned me for ever. > I knew already how horrible LQ is moderated from several mods, but this tells me the very rest I need to know about LQ. > Since Slackware has decided to use this place, that I can not follow anymore, as it's community platform I have to wish Slackware all the best for it's future. > No more development,or financial support from me for Slackware, Slackware developers or Slackware related projects. I can understand your feeling about LQ and its moderators. Meanwhile I am sad to see you leave the Slackware community, as I think that you provided useful contributions (as a4z, for those who don't know). I have still to look at sbbdep but will certainly do that. Which doesn't mean that I be ready to take it over though ;) If you want to contribute to Slint, just drop me a line. Best regards, Didier > For Slackware this will not make any difference, other OS project and I can be happy about the resources available. > > However, one side effect is that the 3 Slackbuilds I maintain needs new maintainers. > > These are: > > slack > https://slackbuilds.org/repository/14.2/network/slack/ > slack desktop client > I haven't updated this for a while since it's change to GTK3, and because if imho it uses insane amount of CPU/memory resources and the web client works much better. > > kcov > https://slackbuilds.org/repository/14.2/development/kcov/ > a code ocverage tool for C/C++, python and bash scripts > nice talk from the author: > https://www.youtube.com/watch?v=1QMHbp5LUKg > > sbbdep > https://slackbuilds.org/repository/14.2/system/sbbdep/ > The tool for exploring binary runtime dependencies on Slackware and Slackware based system. > This build will barely ever change since what it does is final and works, I do not think that I now will ever finalise or release the features I have in the queue. > > > All 3 builds are super simple, so there should not be any problems with them. > If there are questions to them, I will for some time have a look at this thread and help if I can. > > > Regards and all the best! > > > _______________________________________________ > 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 Oct 8 01:12:04 2018 From: yalhcru at gmail.com (B Watson) Date: Sun, 7 Oct 2018 21:12:04 -0400 Subject: [Slackbuilds-users] 3 Slackbuilds looking for new maintainer In-Reply-To: References: Message-ID: On 10/7/18, Harald Achitz wrote: > Hi, > > as a result of temporarily bans (several days) for nearly each post on LQ I > did in the last months, I decided to cancel my paid LQ subscription. Now > the LQ mod has banned me for ever. > I knew already how horrible LQ is moderated from several mods, but this > tells me the very rest I need to know about LQ. > Since Slackware has decided to use this place, that I can not follow > anymore, as it's community platform I have to wish Slackware all the best > for it's future. > No more development,or financial support from me for Slackware, Slackware > developers or Slackware related projects. LQ isn't run by the Slackware project. Please don't dump Slackware because of LQ. It's possible to be a part of the community without using LQ. I know because I never used it (I hate forums, never signed up for it in the first place). The various IRC channels and mailing lists are also 'the community' and generally have a higher singal to noise ratio than a forum anyway. Come to freenode IRC and talk to us on ##slackware and ##slackbuilds (and also ##slackware-offtopic). From willysr at slackbuilds.org Mon Oct 8 01:14:59 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 8 Oct 2018 08:14:59 +0700 Subject: [Slackbuilds-users] 3 Slackbuilds looking for new maintainer In-Reply-To: References: Message-ID: > slack > https://slackbuilds.org/repository/14.2/network/slack/ > slack desktop client > I haven't updated this for a while since it's change to GTK3, and > because if imho it uses insane amount of CPU/memory resources and the > web client works much better. I will take slack -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From dpross1100 at msn.com Mon Oct 8 02:21:37 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Mon, 8 Oct 2018 02:21:37 +0000 Subject: [Slackbuilds-users] 3 Slackbuilds looking for new maintainer In-Reply-To: References: Message-ID: I can take sbbdep. Thanks for your contributions. Dan On Sunday, October 07, 2018 11:15:08 PM Harald Achitz wrote: > Hi, > > as a result of temporarily bans (several days) for nearly each post on LQ I > did in the last months, I decided to cancel my paid LQ subscription. Now > the LQ mod has banned me for ever. > I knew already how horrible LQ is moderated from several mods, but this > tells me the very rest I need to know about LQ. > Since Slackware has decided to use this place, that I can not follow > anymore, as it's community platform I have to wish Slackware all the best > for it's future. > No more development,or financial support from me for Slackware, Slackware > developers or Slackware related projects. > > For Slackware this will not make any difference, other OS project and I can > be happy about the resources available. > > However, one side effect is that the 3 Slackbuilds I maintain needs new > maintainers. > > These are: > > slack > https://slackbuilds.org/repository/14.2/network/slack/ > slack desktop client > I haven't updated this for a while since it's change to GTK3, and because > if imho it uses insane amount of CPU/memory resources and the web client > works much better. > > kcov > https://slackbuilds.org/repository/14.2/development/kcov/ > a code ocverage tool for C/C++, python and bash scripts > nice talk from the author: > https://www.youtube.com/watch?v=1QMHbp5LUKg > > sbbdep > https://slackbuilds.org/repository/14.2/system/sbbdep/ > The tool for exploring binary runtime dependencies on Slackware and > Slackware based system. > This build will barely ever change since what it does is final and works, I > do not think that I now will ever finalise or release the features I have > in the queue. > > > All 3 builds are super simple, so there should not be any problems with > them. > If there are questions to them, I will for some time have a look at this > thread and help if I can. > > > Regards and all the best! From rshepard at appl-ecosys.com Mon Oct 8 19:02:25 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 8 Oct 2018 12:02:25 -0700 (PDT) Subject: [Slackbuilds-users] Error building OpenBLAS [FIXED] In-Reply-To: References: Message-ID: On Mon, 1 Oct 2018, Rich Shepard wrote: > I'm building all my SBo packages on a newly minted desktop running > -14.2/x86_64. I downloaded from the repository the *.tar.gz and build > directory so all files are fresh. Problem solved by upgrading the kernel packages to 4.14.74 from -current. The Ryzen 7 7200 CPU was not supported in kernels newer than the 4.9.x series. Rich From rshepard at appl-ecosys.com Mon Oct 8 19:12:15 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 8 Oct 2018 12:12:15 -0700 (PDT) Subject: [Slackbuilds-users] Another build error: glabels [FIXED] In-Reply-To: References: Message-ID: On Wed, 3 Oct 2018, Rich Shepard wrote: > I would really like to understand why I'm having difficulties building SBo > packages on my new desktop. It's running 14-2/x86_64, has an > 8-core/16-thread CPU, 32G memory, and AlienBOB's multilibs for 14.2. Fixed. Either the BIOS firmware of kernel upgrade cleared the blockage. Rich From rshepard at appl-ecosys.com Mon Oct 8 20:06:16 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 8 Oct 2018 13:06:16 -0700 (PDT) Subject: [Slackbuilds-users] No more Xpdf? Message-ID: Looking for xpdf in the repos I find only apviv. Is xpdf no longer supported by SBo? Rich From rshepard at appl-ecosys.com Mon Oct 8 20:07:46 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 8 Oct 2018 13:07:46 -0700 (PDT) Subject: [Slackbuilds-users] No more Xpdf? [RESOLVED] In-Reply-To: References: Message-ID: On Mon, 8 Oct 2018, Rich Shepard wrote: > Looking for xpdf in the repos I find only apviv. Is xpdf no longer > supported by SBo? Never mind. It's in the core distribution. Apologies, Rich From rellis at dp100.com Mon Oct 8 20:08:33 2018 From: rellis at dp100.com (Richard Ellis) Date: Mon, 8 Oct 2018 16:08:33 -0400 Subject: [Slackbuilds-users] No more Xpdf? In-Reply-To: References: Message-ID: <20181008200833.GG29609@d820.dp100.com> On Mon, Oct 08, 2018 at 01:06:16PM -0700, Rich Shepard wrote: > Looking for xpdf in the repos I find only apviv. Is xpdf no longer > supported by SBo? xpdf is supplied by Slackware itself. >From 'current's PACKAGES.TXT: PACKAGE NAME: xpdf-4.00-i586-3.txz PACKAGE LOCATION: ./slackware/xap PACKAGE SIZE (compressed): 2276 K PACKAGE SIZE (uncompressed): 14980 K PACKAGE DESCRIPTION: xpdf: xpdf (PDF viewer for X) xpdf: xpdf: Xpdf is a viewer for Portable Document Format (PDF) files. xpdf: xpdf: xpdf was written by Derek B. Noonburg. xpdf: From idlemoor at slackbuilds.org Mon Oct 8 20:12:08 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Mon, 8 Oct 2018 21:12:08 +0100 Subject: [Slackbuilds-users] Updates - 20181006.1 In-Reply-To: <9dd1f91e-0b60-54ca-de7b-3c8468187837@slackbuilds.org> References: <0169659b-ea28-abfc-26f4-99e6519a28e1@slackbuilds.org> <20181006063826.GA8708@tursas.sidaroth.foo> <9dd1f91e-0b60-54ca-de7b-3c8468187837@slackbuilds.org> Message-ID: Hi everybody, and sorry for the late reply -- On 06/10/2018 12:57, Willy Sudiarto Raharjo wrote: >> Maybe the GitHub/GitLab workflow could be mentioned in slackbuilds.org >> web site? As far as I can see, it isn't currently. > > I have posted the GitLab URL in the SBo's website > As for GitHub, not all admins agreed on this yet, so currently only me > that looks over PR over GitHub > The URL is : https://github.com/SlackBuildsOrg/slackbuilds I don't have any objections about pull requests from either Github or Gitlab. The main reason why I don't process them is that I turned off notifications from Github a couple of years ago because of too many emails from my work! and unfortunately I always forget to look :( I have no idea if there is a good way of collecting them automatically, but I'll investigate it. Thanks everybody -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Tue Oct 9 02:42:32 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 8 Oct 2018 22:42:32 -0400 Subject: [Slackbuilds-users] Fwd: audio/llcon on slackbuilds.org In-Reply-To: References: Message-ID: I'm getting ready to submit a build for jamulus... whose website is here: https://sourceforge.net/projects/llcon/ It turns out "llcon" is the previous name for the same software, and llcon is on SBo already. It hasn't been updated in years, so I mailed the maintainer, and this is the response I got: ---------- Forwarded message ---------- From: Andrei Date: Sat, 6 Oct 2018 23:04:20 +0300 Subject: Re: audio/llcon on slackbuilds.org To: B Watson Cc: Eu Hi, I wasn t maintaining anymore llcon. You can ask them to remove it. Thank you > On 28 Sep 2018, at 10:04, B Watson wrote: > > I was getting ready to submit a new SlackBuild for jamulus... which turns > out to be the new name for llcon. They renamed it a while back it seems. > > Your last update to audio/llcon was in July 2011. Your last SBo update at > all was in April 2012... Have you still got any interest in maintaining > llcon? If not, I'll submit my jamulus build and ask the admins to remove > the llcon directory. From ricardo at palmtx.com.ar Tue Oct 9 22:13:28 2018 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Tue, 9 Oct 2018 19:13:28 -0300 Subject: [Slackbuilds-users] 3 Slackbuilds looking for new maintainer In-Reply-To: References: Message-ID: <201810091913.28736.ricardo@palmtx.com.ar> El Domingo 07/10/2018 a las 22:12, B Watson escribi?: > On 10/7/18, Harald Achitz wrote: > > Hi, > > > > as a result of temporarily bans (several days) for nearly each post on LQ > > I did in the last months, I decided to cancel my paid LQ subscription. > > Now the LQ mod has banned me for ever. > > I knew already how horrible LQ is moderated from several mods, but this > > tells me the very rest I need to know about LQ. > > Since Slackware has decided to use this place, that I can not follow > > anymore, as it's community platform I have to wish Slackware all the best > > for it's future. > > No more development,or financial support from me for Slackware, Slackware > > developers or Slackware related projects. > > LQ isn't run by the Slackware project. Please don't dump Slackware > because of LQ. I second that! > It's possible to be a part of the community without using LQ. I know > because I never used it (I hate forums, never signed up for it in the > first place). This is also pretty much my case, I think I have a user on LQ but I only read the Slackware forum when there's some big news that I hear somewhere else. > The various IRC channels and mailing lists are also 'the community' > and generally have a higher singal to noise ratio than a forum anyway. > > Come to freenode IRC and talk to us on ##slackware and ##slackbuilds > (and also ##slackware-offtopic). I didn't know about those channels, not a big user of IRC but still better than forums for me :) Cheers, -- Ricardo J. Barberis Usuario Linux N? 250625: http://counter.li.org/ Usuario LFS N? 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com From brent at exitstatusone.com Thu Oct 11 22:29:27 2018 From: brent at exitstatusone.com (Brenton Earl) Date: Thu, 11 Oct 2018 16:29:27 -0600 Subject: [Slackbuilds-users] openscap slackbuild Message-ID: <30a80fcf-7676-0a1b-08d6-e2a8b21cc675@exitstatusone.com> Hello, Are there any Slackware system admins using openscap to audit their systems? It would be great if there was a way to use the oscap tool or the SCAP workbench to audit Slackware systems. I see that openscap is maintained by Vincent Bats, and that it was updated a few times by other people. Is this tool viable for Slackware? Or should I be using some other tool to meet auditing guidelines on Slackware? references: https://www.open-scap.org/ https://slackbuilds.org/repository/14.2/system/openscap/ https://www.open-scap.org/tools/scap-workbench/ Thanks, Brent From vbatts at hashbangbash.com Fri Oct 12 00:27:34 2018 From: vbatts at hashbangbash.com (Vincent Batts) Date: Fri, 12 Oct 2018 00:27:34 +0000 Subject: [Slackbuilds-users] openscap slackbuild In-Reply-To: <30a80fcf-7676-0a1b-08d6-e2a8b21cc675@exitstatusone.com> References: <30a80fcf-7676-0a1b-08d6-e2a8b21cc675@exitstatusone.com> Message-ID: oscap is a remediation tool that is largely tuned to rpm systems. I still don't know of any demand for remediation profiles for slackware systems. It would be an effort to create and maintain such. -------- Original Message -------- On Oct 11, 2018, 18:29, Brenton Earl wrote: > Hello, > > Are there any Slackware system admins using openscap to audit their > systems? It would be great if there was a way to use the oscap tool or > the SCAP workbench to audit Slackware systems. I see that openscap is > maintained by Vincent Bats, and that it was updated a few times by other > people. Is this tool viable for Slackware? Or should I be using some > other tool to meet auditing guidelines on Slackware? > > references: > https://www.open-scap.org/ > https://slackbuilds.org/repository/14.2/system/openscap/ > https://www.open-scap.org/tools/scap-workbench/ > > Thanks, > Brent > _______________________________________________ > 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 Oct 12 04:40:41 2018 From: dchmelik at gmail.com (David Melik) Date: Thu, 11 Oct 2018 21:40:41 -0700 Subject: [Slackbuilds-users] new VLC always crashes Message-ID: <7abfc531-e02e-f02c-db2b-3286f3c39153@gmail.com> after some version of VLC in the last year or so, it always crashes.? I did 'sboupgrade -z -f vlc' (rebuild it and all dependencies) and it still happens.? It's not an X driver issue as KPlayer and Rosa Player work fine (but most other media players, like Xine, MPlayer, Dragon Player now also don't.)? Here's the log, but I don't even have any Nvidia hardware. I open an .avi or .mp4, then get this sort of crash. d at 0.cosmos:~$ vlc VLC media player 3.0.4 Vetinari (revision 3.0.4-0-gf615db6332) [0000000001277a10] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-d' [0000000001309560] main playlist: playlist is empty Non-native QFileDialog supports only local files Non-native QFileDialog supports only local files Non-native QFileDialog supports only local files libEGL warning: DRI2: failed to authenticate Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory libEGL warning: DRI2: failed to authenticate Illegal instruction From chris.willing at exemail.com.au Fri Oct 12 05:26:36 2018 From: chris.willing at exemail.com.au (Christoph Willing) Date: Fri, 12 Oct 2018 15:26:36 +1000 Subject: [Slackbuilds-users] new VLC always crashes In-Reply-To: <7abfc531-e02e-f02c-db2b-3286f3c39153@gmail.com> References: <7abfc531-e02e-f02c-db2b-3286f3c39153@gmail.com> Message-ID: <97a03339-e3d4-0127-f287-0bb98b67614b@exemail.com.au> On 12/10/18 2:40 pm, David Melik wrote: > after some version of VLC in the last year or so, it always crashes.? I > did 'sboupgrade -z -f vlc' (rebuild it and all dependencies) and it > still happens.? It's not an X driver issue as KPlayer and Rosa Player > work fine (but most other media players, like Xine, MPlayer, Dragon > Player now also don't.)? Here's the log, but I don't even have any > Nvidia hardware. I open an .avi or .mp4, then get this sort of crash. > > d at 0.cosmos:~$ vlc > VLC media player 3.0.4 Vetinari (revision 3.0.4-0-gf615db6332) > [0000000001277a10] main libvlc: Running vlc with the default interface. > Use 'cvlc' to use vlc without interface. > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-d' > [0000000001309560] main playlist: playlist is empty > Non-native QFileDialog supports only local files > Non-native QFileDialog supports only local files > Non-native QFileDialog supports only local files > libEGL warning: DRI2: failed to authenticate > Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared > object file: No such file or directory > libEGL warning: DRI2: failed to authenticate > Illegal instruction > I googled for: vlc Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory which turned up a bunch of similar problems and some solutions (not all vlc related). I can't tell which of them may relate to your situation, so won't try to summarise all the possibilities here but suggest, if you haven't already, you do the same search and try some of the suggested solutions. chris From ozan.turkyilmaz at gmail.com Fri Oct 12 06:07:31 2018 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Fri, 12 Oct 2018 11:07:31 +0500 Subject: [Slackbuilds-users] new VLC always crashes In-Reply-To: <7abfc531-e02e-f02c-db2b-3286f3c39153@gmail.com> References: <7abfc531-e02e-f02c-db2b-3286f3c39153@gmail.com> Message-ID: David Melik , 12 Eki 2018 Cum, 09:40 tarihinde ?unu yazd?: > after some version of VLC in the last year or so, it always crashes. I > did 'sboupgrade -z -f vlc' (rebuild it and all dependencies) and it > still happens. It's not an X driver issue as KPlayer and Rosa Player > work fine (but most other media players, like Xine, MPlayer, Dragon > Player now also don't.) Here's the log, but I don't even have any > Nvidia hardware. I open an .avi or .mp4, then get this sort of crash. > > d at 0.cosmos:~$ vlc > VLC media player 3.0.4 Vetinari (revision 3.0.4-0-gf615db6332) > [0000000001277a10] main libvlc: Running vlc with the default interface. > Use 'cvlc' to use vlc without interface. > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-d' > [0000000001309560] main playlist: playlist is empty > Non-native QFileDialog supports only local files > Non-native QFileDialog supports only local files > Non-native QFileDialog supports only local files > libEGL warning: DRI2: failed to authenticate > Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared > object file: No such file or directory > libEGL warning: DRI2: failed to authenticate > Illegal instruction > > It looks more like a nvidia driver problem. Check wheater the dravier installed correctly. -- Ozan, BSc, BEng -------------- next part -------------- An HTML attachment was scrubbed... URL: From brent at exitstatusone.com Fri Oct 12 09:33:03 2018 From: brent at exitstatusone.com (Brenton Earl) Date: Fri, 12 Oct 2018 03:33:03 -0600 Subject: [Slackbuilds-users] openscap slackbuild In-Reply-To: References: <30a80fcf-7676-0a1b-08d6-e2a8b21cc675@exitstatusone.com> Message-ID: Thanks for the quick response. Is there some software slackware admins use to audit their systems for compliance? I've used lynis in the past but I am curious if there is other compatible software for Slackware. On 10/11/18 6:27 PM, Vincent Batts wrote: > oscap is a remediation tool that is largely tuned to rpm systems. I > still don't know of any demand for remediation profiles for slackware > systems. It would be an effort to create and maintain such. > > -------- Original Message -------- > On Oct 11, 2018, 18:29, Brenton Earl < brent at exitstatusone.com> wrote: > > > Hello, > > Are there any Slackware system admins using openscap to audit their > systems? It would be great if there was a way to use the oscap tool or > the SCAP workbench to audit Slackware systems. I see that openscap is > maintained by Vincent Bats, and that it was updated a few times by other > people. Is this tool viable for Slackware? Or should I be using some > other tool to meet auditing guidelines on Slackware? > > references: > https://www.open-scap.org/ > https://slackbuilds.org/repository/14.2/system/openscap/ > https://www.open-scap.org/tools/scap-workbench/ > > Thanks, > Brent From orbea at fredslev.dk Fri Oct 12 13:33:54 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Fri, 12 Oct 2018 06:33:54 -0700 Subject: [Slackbuilds-users] new VLC always crashes In-Reply-To: Message-ID: <20181012063354.71f7f164@Akita.witch.org> > It looks more like a nvidia driver problem. Check wheater the dravier installed correctly. Yes, the nvidia driver is incorrectly installed. The issue is specifically that libvdpau_nvidia.so does not exist. I would suggest removing nvidia, cleaning up any broken symlinks left behind (See the README), reinstalling xorg-server, mesa and then nvidia. Alternatively with an older gpu nouveau may work just fine. > Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared > object file: No such file or directory From brent at exitstatusone.com Fri Oct 12 18:42:11 2018 From: brent at exitstatusone.com (Brenton Earl) Date: Fri, 12 Oct 2018 12:42:11 -0600 Subject: [Slackbuilds-users] pyasn1 slackbuild Message-ID: <81f895f3-b917-9898-f5f0-0d4440969c83@exitstatusone.com> Hello, It looks like there is something wrong with the pyasn1 0.4.4 source tarball when I attempt to build it using slackrepo. Building with 0.4.3 works just fine. I attached the build log outlining the issue I ran into. It looks like something funny is going on with permissions. The command I ran is: slackrepo --very-verbose --lint --dry-run build pyasn1 Running the slackbuild directly yields the same error output from tar. Thanks, Brenton Earl brent at exitstatusone.com -------------- next part -------------- root at slackware64-142-sbo:/var/lib/slackrepo/SBo/slackbuilds/python/pyasn1# cat /var/log/slackrepo/SBo/python/pyasn1/build.log Building python/pyasn1 (add version 0.4.4) [dry run] 2018-10-12 12:33:13 Testing SlackBuild files ... Removing old source files ... Downloading source files ... Verifying source files ... Running pyasn1.SlackBuild ... ETA 12:33:?? env MAKEFLAGS='-j4' /usr/libexec/slackrepo/unbuffer nice -n 5 bash -x ./pyasn1.SlackBuild + PRGNAM=pyasn1 + VERSION=0.4.4 + BUILD=1 + TAG=_ble + '[' -z x86_64 ']' ++ pwd + CWD=/tmp/SBo/slackrepo.7AjD58/slackbuild_pyasn1 + TMP=/tmp/SBo/slackrepo.7AjD58/build_pyasn1 + PKG=/tmp/SBo/slackrepo.7AjD58/build_pyasn1/package-pyasn1 + OUTPUT=/tmp/SBo/slackrepo.7AjD58/output_pyasn1 + '[' x86_64 = i586 ']' + '[' x86_64 = i686 ']' + '[' x86_64 = x86_64 ']' + SLKCFLAGS='-O2 -fPIC' + LIBDIRSUFFIX=64 + set -e + rm -rf /tmp/SBo/slackrepo.7AjD58/build_pyasn1/package-pyasn1 + mkdir -p /tmp/SBo/slackrepo.7AjD58/build_pyasn1 /tmp/SBo/slackrepo.7AjD58/build_pyasn1/package-pyasn1 /tmp/SBo/slackrepo.7AjD58/output_pyasn1 + cd /tmp/SBo/slackrepo.7AjD58/build_pyasn1 + rm -rf pyasn1-0.4.4 + tar xvf /tmp/SBo/slackrepo.7AjD58/slackbuild_pyasn1/pyasn1-0.4.4.tar.gz pyasn1-0.4.4/ pyasn1-0.4.4/docs/ pyasn1-0.4.4/docs/Makefile tar: pyasn1-0.4.4/docs/Makefile: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/ pyasn1-0.4.4/docs/source/.static/ pyasn1-0.4.4/docs/source/.static/logo.svg tar: pyasn1-0.4.4/docs/source/.static/logo.svg: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/license.rst tar: pyasn1-0.4.4/docs/source/.static: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/docs/source/license.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/contents.rst tar: pyasn1-0.4.4/docs/source/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/download.rst tar: pyasn1-0.4.4/docs/source/download.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/example-use-case.rst tar: pyasn1-0.4.4/docs/source/example-use-case.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/conf.py tar: pyasn1-0.4.4/docs/source/conf.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/changelog.rst tar: pyasn1-0.4.4/docs/source/changelog.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/ pyasn1-0.4.4/docs/source/pyasn1/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/codec/ pyasn1-0.4.4/docs/source/pyasn1/codec/native/ pyasn1-0.4.4/docs/source/pyasn1/codec/native/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/codec/native/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/codec/cer/ tar: pyasn1-0.4.4/docs/source/pyasn1/codec/native: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/codec/cer/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/codec/cer/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/codec/der/ tar: pyasn1-0.4.4/docs/source/pyasn1/codec/cer: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/codec/der/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/codec/der/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/codec/ber/ tar: pyasn1-0.4.4/docs/source/pyasn1/codec/der: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/codec/ber/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/codec/ber/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/ tar: pyasn1-0.4.4/docs/source/pyasn1/codec/ber: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/docs/source/pyasn1/codec: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/useful/ pyasn1-0.4.4/docs/source/pyasn1/type/useful/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/useful/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/useful/objectdescriptor.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/useful/objectdescriptor.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/useful/utctime.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/useful/utctime.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/useful/generalizedtime.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/useful/generalizedtime.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/namedtype/ tar: pyasn1-0.4.4/docs/source/pyasn1/type/useful: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/namedtype/namedtypes.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/namedtype/namedtypes.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/namedtype/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/namedtype/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/namedtype/defaultednamedtype.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/namedtype/defaultednamedtype.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/namedtype/optionalnamedtype.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/namedtype/optionalnamedtype.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/namedtype/namedtype.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/namedtype/namedtype.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/ tar: pyasn1-0.4.4/docs/source/pyasn1/type/namedtype: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/t61string.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/t61string.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/visiblestring.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/visiblestring.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/videotexstring.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/videotexstring.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/bmpstring.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/bmpstring.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/ia5string.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/ia5string.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/universalstring.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/universalstring.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/generalstring.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/generalstring.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/teletexstring.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/teletexstring.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/utf8string.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/utf8string.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/printablestring.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/printablestring.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/iso646string.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/iso646string.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/numericstring.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/numericstring.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/char/graphicstring.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/char/graphicstring.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/opentype/ tar: pyasn1-0.4.4/docs/source/pyasn1/type/char: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/opentype/opentype.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/opentype/opentype.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/opentype/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/opentype/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/tag/ tar: pyasn1-0.4.4/docs/source/pyasn1/type/opentype: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/tag/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/tag/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/tag/tagset.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/tag/tagset.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/tag/tagmap.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/tag/tagmap.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/tag/tag.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/tag/tag.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/ tar: pyasn1-0.4.4/docs/source/pyasn1/type/tag: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/octetstring.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/octetstring.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/set.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/set.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/objectidentifier.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/objectidentifier.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/enumerated.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/enumerated.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/any.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/any.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/choice.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/choice.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/sequenceof.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/sequenceof.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/integer.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/integer.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/real.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/real.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/setof.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/setof.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/bitstring.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/bitstring.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/sequence.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/sequence.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/null.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/null.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/univ/boolean.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ/boolean.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/namedval/ tar: pyasn1-0.4.4/docs/source/pyasn1/type/univ: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/namedval/namedval.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/namedval/namedval.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/namedval/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/namedval/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/constraint/ tar: pyasn1-0.4.4/docs/source/pyasn1/type/namedval: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/constraint/constraintsintersection.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/constraint/constraintsintersection.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/constraint/permittedalphabet.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/constraint/permittedalphabet.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/constraint/contents.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/constraint/contents.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/constraint/constraintsunion.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/constraint/constraintsunion.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/constraint/containedsubtype.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/constraint/containedsubtype.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/constraint/valuesize.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/constraint/valuesize.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/constraint/valuerange.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/constraint/valuerange.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/constraint/constraintsexclusion.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/constraint/constraintsexclusion.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/docs/source/pyasn1/type/constraint/singlevalue.rst tar: pyasn1-0.4.4/docs/source/pyasn1/type/constraint/singlevalue.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/ tar: pyasn1-0.4.4/docs/source/pyasn1/type/constraint: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/docs/source/pyasn1/type: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/docs/source/pyasn1: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/docs/source: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/docs: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/test_debug.py tar: pyasn1-0.4.4/tests/test_debug.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/base.py tar: pyasn1-0.4.4/tests/base.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/ pyasn1-0.4.4/tests/codec/native/ pyasn1-0.4.4/tests/codec/native/test_decoder.py tar: pyasn1-0.4.4/tests/codec/native/test_decoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/native/test_encoder.py tar: pyasn1-0.4.4/tests/codec/native/test_encoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/native/__init__.py tar: pyasn1-0.4.4/tests/codec/native/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/native/__main__.py tar: pyasn1-0.4.4/tests/codec/native/__main__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/cer/ tar: pyasn1-0.4.4/tests/codec/native: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/cer/test_decoder.py tar: pyasn1-0.4.4/tests/codec/cer/test_decoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/cer/test_encoder.py tar: pyasn1-0.4.4/tests/codec/cer/test_encoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/cer/__init__.py tar: pyasn1-0.4.4/tests/codec/cer/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/cer/__main__.py tar: pyasn1-0.4.4/tests/codec/cer/__main__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/der/ tar: pyasn1-0.4.4/tests/codec/cer: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/der/test_decoder.py tar: pyasn1-0.4.4/tests/codec/der/test_decoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/der/test_encoder.py tar: pyasn1-0.4.4/tests/codec/der/test_encoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/der/__init__.py tar: pyasn1-0.4.4/tests/codec/der/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/der/__main__.py tar: pyasn1-0.4.4/tests/codec/der/__main__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/__init__.py tar: pyasn1-0.4.4/tests/codec/der: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/tests/codec/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/ber/ pyasn1-0.4.4/tests/codec/ber/test_decoder.py tar: pyasn1-0.4.4/tests/codec/ber/test_decoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/ber/test_encoder.py tar: pyasn1-0.4.4/tests/codec/ber/test_encoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/ber/__init__.py tar: pyasn1-0.4.4/tests/codec/ber/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/ber/__main__.py tar: pyasn1-0.4.4/tests/codec/ber/__main__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/codec/__main__.py tar: pyasn1-0.4.4/tests/codec/ber: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/tests/codec/__main__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/__init__.py tar: pyasn1-0.4.4/tests/codec: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/tests/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/compat/ pyasn1-0.4.4/tests/compat/test_binary.py tar: pyasn1-0.4.4/tests/compat/test_binary.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/compat/__init__.py tar: pyasn1-0.4.4/tests/compat/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/compat/test_octets.py tar: pyasn1-0.4.4/tests/compat/test_octets.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/compat/test_integer.py tar: pyasn1-0.4.4/tests/compat/test_integer.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/compat/__main__.py tar: pyasn1-0.4.4/tests/compat/__main__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/__main__.py tar: pyasn1-0.4.4/tests/compat: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/tests/__main__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/type/ pyasn1-0.4.4/tests/type/test_namedtype.py tar: pyasn1-0.4.4/tests/type/test_namedtype.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/type/test_tag.py tar: pyasn1-0.4.4/tests/type/test_tag.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/type/test_opentype.py tar: pyasn1-0.4.4/tests/type/test_opentype.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/type/test_constraint.py tar: pyasn1-0.4.4/tests/type/test_constraint.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/type/test_namedval.py tar: pyasn1-0.4.4/tests/type/test_namedval.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/type/test_char.py tar: pyasn1-0.4.4/tests/type/test_char.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/type/__init__.py tar: pyasn1-0.4.4/tests/type/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/type/test_useful.py tar: pyasn1-0.4.4/tests/type/test_useful.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/type/test_univ.py tar: pyasn1-0.4.4/tests/type/test_univ.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/tests/type/__main__.py tar: pyasn1-0.4.4/tests/type/__main__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/TODO.rst tar: pyasn1-0.4.4/tests/type: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/tests: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/TODO.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/LICENSE.rst tar: pyasn1-0.4.4/LICENSE.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/setup.cfg tar: pyasn1-0.4.4/setup.cfg: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1.egg-info/ pyasn1-0.4.4/pyasn1.egg-info/SOURCES.txt tar: pyasn1-0.4.4/pyasn1.egg-info/SOURCES.txt: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1.egg-info/top_level.txt tar: pyasn1-0.4.4/pyasn1.egg-info/top_level.txt: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1.egg-info/PKG-INFO tar: pyasn1-0.4.4/pyasn1.egg-info/PKG-INFO: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1.egg-info/zip-safe tar: pyasn1-0.4.4/pyasn1.egg-info/zip-safe: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1.egg-info/dependency_links.txt tar: pyasn1-0.4.4/pyasn1.egg-info/dependency_links.txt: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/setup.py tar: pyasn1-0.4.4/pyasn1.egg-info: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/setup.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/MANIFEST.in tar: pyasn1-0.4.4/MANIFEST.in: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/PKG-INFO tar: pyasn1-0.4.4/PKG-INFO: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/CHANGES.rst tar: pyasn1-0.4.4/CHANGES.rst: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/README.md tar: pyasn1-0.4.4/README.md: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/ pyasn1-0.4.4/pyasn1/debug.py tar: pyasn1-0.4.4/pyasn1/debug.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/error.py tar: pyasn1-0.4.4/pyasn1/error.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/ pyasn1-0.4.4/pyasn1/codec/native/ pyasn1-0.4.4/pyasn1/codec/native/decoder.py tar: pyasn1-0.4.4/pyasn1/codec/native/decoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/native/__init__.py tar: pyasn1-0.4.4/pyasn1/codec/native/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/native/encoder.py tar: pyasn1-0.4.4/pyasn1/codec/native/encoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/cer/ tar: pyasn1-0.4.4/pyasn1/codec/native: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/cer/decoder.py tar: pyasn1-0.4.4/pyasn1/codec/cer/decoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/cer/__init__.py tar: pyasn1-0.4.4/pyasn1/codec/cer/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/cer/encoder.py tar: pyasn1-0.4.4/pyasn1/codec/cer/encoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/der/ tar: pyasn1-0.4.4/pyasn1/codec/cer: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/der/decoder.py tar: pyasn1-0.4.4/pyasn1/codec/der/decoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/der/__init__.py tar: pyasn1-0.4.4/pyasn1/codec/der/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/der/encoder.py tar: pyasn1-0.4.4/pyasn1/codec/der/encoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/__init__.py tar: pyasn1-0.4.4/pyasn1/codec/der: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/pyasn1/codec/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/ber/ pyasn1-0.4.4/pyasn1/codec/ber/decoder.py tar: pyasn1-0.4.4/pyasn1/codec/ber/decoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/ber/__init__.py tar: pyasn1-0.4.4/pyasn1/codec/ber/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/ber/encoder.py tar: pyasn1-0.4.4/pyasn1/codec/ber/encoder.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/codec/ber/eoo.py tar: pyasn1-0.4.4/pyasn1/codec/ber/eoo.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/__init__.py tar: pyasn1-0.4.4/pyasn1/codec/ber: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/pyasn1/codec: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/pyasn1/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/compat/ pyasn1-0.4.4/pyasn1/compat/integer.py tar: pyasn1-0.4.4/pyasn1/compat/integer.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/compat/binary.py tar: pyasn1-0.4.4/pyasn1/compat/binary.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/compat/__init__.py tar: pyasn1-0.4.4/pyasn1/compat/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/compat/octets.py tar: pyasn1-0.4.4/pyasn1/compat/octets.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/compat/string.py tar: pyasn1-0.4.4/pyasn1/compat/string.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/compat/dateandtime.py tar: pyasn1-0.4.4/pyasn1/compat/dateandtime.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/compat/calling.py tar: pyasn1-0.4.4/pyasn1/compat/calling.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/ tar: pyasn1-0.4.4/pyasn1/compat: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/namedtype.py tar: pyasn1-0.4.4/pyasn1/type/namedtype.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/base.py tar: pyasn1-0.4.4/pyasn1/type/base.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/opentype.py tar: pyasn1-0.4.4/pyasn1/type/opentype.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/tag.py tar: pyasn1-0.4.4/pyasn1/type/tag.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/error.py tar: pyasn1-0.4.4/pyasn1/type/error.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/useful.py tar: pyasn1-0.4.4/pyasn1/type/useful.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/constraint.py tar: pyasn1-0.4.4/pyasn1/type/constraint.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/namedval.py tar: pyasn1-0.4.4/pyasn1/type/namedval.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/__init__.py tar: pyasn1-0.4.4/pyasn1/type/__init__.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/tagmap.py tar: pyasn1-0.4.4/pyasn1/type/tagmap.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/univ.py tar: pyasn1-0.4.4/pyasn1/type/univ.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument pyasn1-0.4.4/pyasn1/type/char.py tar: pyasn1-0.4.4/pyasn1/type/char.py: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/pyasn1/type: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4/pyasn1: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: pyasn1-0.4.4: Cannot change ownership to uid 26252, gid 26252: Invalid argument tar: Exiting with failure status due to previous errors python/pyasn1: pyasn1.SlackBuild failed (status 2) 12:33:13 :-( python/pyasn1 FAILED )-: From ml at mareichelt.com Fri Oct 12 22:21:52 2018 From: ml at mareichelt.com (Markus Reichelt) Date: Sat, 13 Oct 2018 00:21:52 +0200 Subject: [Slackbuilds-users] pyasn1 slackbuild In-Reply-To: <81f895f3-b917-9898-f5f0-0d4440969c83@exitstatusone.com> References: <81f895f3-b917-9898-f5f0-0d4440969c83@exitstatusone.com> Message-ID: <20181012222151.GA7131@pc21.mareichelt.com> * Brenton Earl wrote: > Running the slackbuild directly yields the same error output from > tar. I've just tried the buildscript with a fresh source download, everything works as expected. From davidnchmelik at gmail.com Sat Oct 13 00:48:09 2018 From: davidnchmelik at gmail.com (David Melik) Date: Fri, 12 Oct 2018 17:48:09 -0700 Subject: [Slackbuilds-users] new VLC always crashes Message-ID: On Fri, 12 Oct 2018 15:26:36 +1000, Christoph Willing wrote: > I googled for: > vlc Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared > object file: No such file or directory > which turned up a bunch of similar problems? and some solutions (not all > vlc related). I can't tell which of them may relate to your situation On Fri, 12 Oct 2018 11:07:31 +0500, Ozan T?rky?lmaz wrote: > It looks more like a nvidia driver problem. Check wheater the dravier > installed correctly. On Fri, 12 Oct 2018 06:33:54 -0700, orbea-zCudsq/yU5Nknbxzx/v8hQ at public.gmane.org wrote: > Yes, the nvidia driver is incorrectly installed. The issue is > specifically that libvdpau_nvidia.so does not exist. I would suggest > removing nvidia, cleaning up any broken symlinks left behind (See the > README), reinstalling xorg-server, mesa and then nvidia. Alternatively > with an older gpu nouveau [...] Chris, Ozab, orbea, reread my original post, particularly 'I don't even have any Nvidia hardware,' and I never had on this PC. None what you said has anything to do with it.? You all missed that there's an earlier line, 'libEGL warning: DRI2: failed to authenticate,' and other error lines.? VLC may now be built to use more parts of display hardware, and Nvidia is just something it checks for but is n/a. I'm using an AMD Radeon RX Vega 64 with kernel 4.18.11, but I don't think the AMD 3D drivers are ready for Slackware 14.2... and unfortunately VLC doesn't give me an option to not use such parts that make it crash. root at 0.cosmos:~# lspci|grep VGA 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 687f (rev c1) From willysr at slackbuilds.org Sat Oct 13 01:12:59 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 13 Oct 2018 08:12:59 +0700 Subject: [Slackbuilds-users] Updates - 20181013.1 Message-ID: <9d268929-4894-a82b-32c8-b41347db0372@slackbuilds.org> Sat Oct 13 01:03:47 UTC 2018 audio/jamulus: Added (real-time jam session client/server). desktop/anki: Updated for version 2.0.52. desktop/zuki-themes: Updated for version 3.18.1 + new maintainer. development/ShellCheck-bin: Added (shell script analysis tool). development/android-studio: Updated for v 3.2.0.26_181_5014246. development/arm-gcc: Update DEP. development/hopper: Updated for version 4.4.1. development/jupyter-nbdime: Updated for version 1.0.3. development/komodo-edit: Updated for version 11.1.0. development/komodo-ide: Updated for version 11.1.0. development/samurai: Updated for version 0.4. development/sqlcl: Updated for version 18.2.0. development/sqldeveloper: Updated for version 18.2.0.183.1748. games/RetroArch: Updated for version 1.7.5. gis/gpsd: Updated for version 3.18. gis/gpxsee: Updated for version 6.2. graphics/brlcad: Changes in build options and REQUIRES. graphics/converseen: Updated for version 0.9.7.1. graphics/feh: Updated for version 2.28. graphics/librecad: Fixed download. graphics/opencollada: Upgraded for version 1.6.64 libraries/bluez-alsa: Updated for version 1.3.1. libraries/hoel: Updated for version 1.4.4. libraries/libopusenc: Updated for version 0.2.1. libraries/libp11: Updated for version 0.4.9. libraries/libraqm: Added (text layout library). libraries/libupnp-legacy: Updated for version 1.6.25. libraries/libuv: Updated for version 1.23.2. libraries/live555: Updated for version 2018.10.10 libraries/marisa: Added (C++ Library). libraries/orcania: Fixed md5sum. libraries/qt5: Slightly modify find command in SlackBuild. libraries/ulfius: Updated for version 2.4.2. libraries/yder: Fixed md5sum. multimedia/flashplayer-plugin: Updated for version 31.0.0.122. multimedia/gpodder: Updated for version 3.10.5. multimedia/mkvtoolnix: Updated for version 27.0.0. multimedia/pepperflash-plugin: Updated for version 31.0.0.122. network/WireGuard: Updated for version 0.0.20181007. network/bro: Updated for version 2.5.5. network/davmail: Updated for version 4.9.0. network/imapfilter: Updated for version 2.6.12. network/oidentd: Updated for version 2.3.1. network/psi-plus: Update to 1.3.425 network/qutebrowser: Update to 1.5.0 network/telegram: Updated for version 1.4.2. office/MasterPDFEditor: Updated for version 5.1.60. office/smoffice2018: Updated for version 2018_938. perl/perl-Template-Toolkit: Updated for version 2.28. python/atomicwrites: Added support python3. python/bleach: Updated for version 3.0.1. python/entrypoints: Add Python 3 support. python/more-itertools: Added support python3. python/pluggy: Added support python3. python/py: Added support python3. python/python-nbxmpp: Added python3 support. python/python-webencodings: Add Python 3 support. python/python3-prompt_toolkit: 2.0.5. python/pywal: Updated for version 3.1.0. python/testpath: Updated for version 0.4.2. system/epson-inkjet-printer-escpr2: Updated for version 1.0.24. system/fzf: Updated for version 0.17.5. system/memtest86+: Update README with instructions for GRUB 2 system/memtest86: Update README with instructions for GRUB 2 system/qtfm: Updated for version 6.1.3. system/ranger: Update README system/sbbdep: New maintainer. system/softhsm: Updated for version 2.5.0. system/stow: Added (manage source installs). system/telegraf: Updated for version 1.8.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From orbea at fredslev.dk Sat Oct 13 03:29:45 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Fri, 12 Oct 2018 20:29:45 -0700 Subject: [Slackbuilds-users] new VLC always crashes In-Reply-To: Message-ID: <20181012202945.7059d02a@Akita.witch.org> > Chris, Ozab, orbea, reread my original post, particularly 'I don't even > have any > Nvidia hardware,' and I never had on this PC. None what you said has > anything to do with it. I did read it and I read it again, this is the first that you mentioned that you do not have nvidia hardware, but you are right that makes the issue sound different. I wonder why its trying to use libvdpau_nvidia.so regardless? Perhaps this is a red herring? I am not familiar with vlc. Another idea is that this is related to DRI2 in which case I would suggest trying the modesetting xorg driver (Part of xorg-server) and / or DRI3. You could also try newer versions of xorg and mesa, but this would be more involved to test. From lspencer31 at cfl.rr.com Sat Oct 13 14:35:29 2018 From: lspencer31 at cfl.rr.com (Lenard Spencer) Date: Sat, 13 Oct 2018 10:35:29 -0400 Subject: [Slackbuilds-users] new VLC always crashes In-Reply-To: <7abfc531-e02e-f02c-db2b-3286f3c39153@gmail.com> References: <7abfc531-e02e-f02c-db2b-3286f3c39153@gmail.com> Message-ID: <910f6f79-657f-4d42-d0b2-dced7f039836@cfl.rr.com> On 10/12/18 12:40 AM, David Melik wrote: > after some version of VLC in the last year or so, it always crashes.? > I did 'sboupgrade -z -f vlc' (rebuild it and all dependencies) and it > still happens.? It's not an X driver issue as KPlayer and Rosa Player > work fine (but most other media players, like Xine, MPlayer, Dragon > Player now also don't.)? Here's the log, but I don't even have any > Nvidia hardware. I open an .avi or .mp4, then get this sort of crash. > > d at 0.cosmos:~$ vlc > VLC media player 3.0.4 Vetinari (revision 3.0.4-0-gf615db6332) > [0000000001277a10] main libvlc: Running vlc with the default > interface. Use 'cvlc' to use vlc without interface. > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-d' > [0000000001309560] main playlist: playlist is empty > Non-native QFileDialog supports only local files > Non-native QFileDialog supports only local files > Non-native QFileDialog supports only local files > libEGL warning: DRI2: failed to authenticate > Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared > object file: No such file or directory > libEGL warning: DRI2: failed to authenticate > Illegal instruction What video hardware are you using?? I had brought this up before on LQ and it almost ignited a flame war.? The reason you are seeing the libvdpau_nvidia.so message is that it is hard-coded into libvdpau, and your video card is probably not supported by the kernel.? I had bought an Nvidia GTX-1050Ti card last year and got that message on both 14.2 and then-current (4.9 kernel).? My card wasn't supported in the kernel until 4.13. From lspencer31 at cfl.rr.com Sat Oct 13 14:37:32 2018 From: lspencer31 at cfl.rr.com (Lenard Spencer) Date: Sat, 13 Oct 2018 10:37:32 -0400 Subject: [Slackbuilds-users] new VLC always crashes In-Reply-To: <910f6f79-657f-4d42-d0b2-dced7f039836@cfl.rr.com> References: <7abfc531-e02e-f02c-db2b-3286f3c39153@gmail.com> <910f6f79-657f-4d42-d0b2-dced7f039836@cfl.rr.com> Message-ID: <1c0c3166-e27e-e2d9-81dd-2a08cca32c20@cfl.rr.com> On 10/13/18 10:35 AM, Lenard Spencer wrote: > On 10/12/18 12:40 AM, David Melik wrote: >> after some version of VLC in the last year or so, it always crashes.? >> I did 'sboupgrade -z -f vlc' (rebuild it and all dependencies) and it >> still happens.? It's not an X driver issue as KPlayer and Rosa Player >> work fine (but most other media players, like Xine, MPlayer, Dragon >> Player now also don't.)? Here's the log, but I don't even have any >> Nvidia hardware. I open an .avi or .mp4, then get this sort of crash. >> >> d at 0.cosmos:~$ vlc >> VLC media player 3.0.4 Vetinari (revision 3.0.4-0-gf615db6332) >> [0000000001277a10] main libvlc: Running vlc with the default >> interface. Use 'cvlc' to use vlc without interface. >> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-d' >> [0000000001309560] main playlist: playlist is empty >> Non-native QFileDialog supports only local files >> Non-native QFileDialog supports only local files >> Non-native QFileDialog supports only local files >> libEGL warning: DRI2: failed to authenticate >> Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared >> object file: No such file or directory >> libEGL warning: DRI2: failed to authenticate >> Illegal instruction > > What video hardware are you using?? I had brought this up before on LQ > and it almost ignited a flame war.? The reason you are seeing the > libvdpau_nvidia.so message is that it is hard-coded into libvdpau, and > your video card is probably not supported by the kernel.? I had bought > an Nvidia GTX-1050Ti card last year and got that message on both 14.2 > and then-current (4.9 kernel).? My card wasn't supported in the kernel > until 4.13. I forgot to mention it was the nouveau driver in the kernel that didn't support my card yet. From slacker6896 at gmail.com Sat Oct 13 15:08:47 2018 From: slacker6896 at gmail.com (Sebastien BALLET) Date: Sat, 13 Oct 2018 17:08:47 +0200 Subject: [Slackbuilds-users] new VLC always crashes In-Reply-To: <910f6f79-657f-4d42-d0b2-dced7f039836@cfl.rr.com> References: <7abfc531-e02e-f02c-db2b-3286f3c39153@gmail.com> <910f6f79-657f-4d42-d0b2-dced7f039836@cfl.rr.com> Message-ID: Hello, the driver name "nvidia" is hardcoded but you can override it using the environment variable VDPAU_DRIVER and more precisely in /etc/profile.d/ vdpau.sh/.csh, which, by default, only contains commented definitions of that variable : 8<----------------------------------------- #!/bin/sh # Disable debugging output of the vdpau backend export VDPAU_LOG=0 # Use the vdpau backend of the nvidia binary driver #export VDPAU_DRIVER="nvidia" # Use the vdpau backend of the nouveau driver #export VDPAU_DRIVER="nouveau" # Use the vdpau backend of the r300 driver #export VDPAU_DRIVER="r300" # Use the vdpau backend of the r600 driver #export VDPAU_DRIVER="r600" # Use the vdpau backend of the radeonsi driver #export VDPAU_DRIVER="radeonsi" # Use the va-api/opengl backend #export VDPAU_DRIVER="va_gl" %<------------------------------------------------- -- SeB Le sam. 13 oct. 2018 ? 16:35, Lenard Spencer a ?crit : > On 10/12/18 12:40 AM, David Melik wrote: > > after some version of VLC in the last year or so, it always crashes. > > I did 'sboupgrade -z -f vlc' (rebuild it and all dependencies) and it > > still happens. It's not an X driver issue as KPlayer and Rosa Player > > work fine (but most other media players, like Xine, MPlayer, Dragon > > Player now also don't.) Here's the log, but I don't even have any > > Nvidia hardware. I open an .avi or .mp4, then get this sort of crash. > > > > d at 0.cosmos:~$ vlc > > VLC media player 3.0.4 Vetinari (revision 3.0.4-0-gf615db6332) > > [0000000001277a10] main libvlc: Running vlc with the default > > interface. Use 'cvlc' to use vlc without interface. > > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-d' > > [0000000001309560] main playlist: playlist is empty > > Non-native QFileDialog supports only local files > > Non-native QFileDialog supports only local files > > Non-native QFileDialog supports only local files > > libEGL warning: DRI2: failed to authenticate > > Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared > > object file: No such file or directory > > libEGL warning: DRI2: failed to authenticate > > Illegal instruction > > What video hardware are you using? I had brought this up before on LQ > and it almost ignited a flame war. The reason you are seeing the > libvdpau_nvidia.so message is that it is hard-coded into libvdpau, and > your video card is probably not supported by the kernel. I had bought > an Nvidia GTX-1050Ti card last year and got that message on both 14.2 > and then-current (4.9 kernel). My card wasn't supported in the kernel > until 4.13. > > > > _______________________________________________ > 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 sam_web at yahoo.de Sat Oct 13 19:48:57 2018 From: sam_web at yahoo.de (Marek Srejma) Date: Sat, 13 Oct 2018 21:48:57 +0200 Subject: [Slackbuilds-users] Scribus 1.4.7 stable available Message-ID: <1196a971-4ade-f7f0-bd4a-ec3c7f53be7c@yahoo.de> Hi Heinz, here I attached a patch for the Scribus SlackBuild update from version 1.4.6 to 1.4.7, which is the latest stable release. Thanks in advance. Marek -------------- next part -------------- A non-text attachment was scrubbed... Name: scribus_1.4.6_to_1.4.7.patch Type: text/x-patch Size: 944 bytes Desc: not available URL: From orbea at fredslev.dk Sat Oct 13 20:15:44 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Sat, 13 Oct 2018 13:15:44 -0700 Subject: [Slackbuilds-users] new VLC always crashes In-Reply-To: <910f6f79-657f-4d42-d0b2-dced7f039836@cfl.rr.com> Message-ID: <20181013131544.217e35bc@Akita.witch.org> >What video hardware are you using? I had brought this up before on LQ >and it almost ignited a flame war. The reason you are seeing the >libvdpau_nvidia.so message is that it is hard-coded into libvdpau, and >your video card is probably not supported by the kernel. I had bought >an Nvidia GTX-1050Ti card last year and got that message on both 14.2 >and then-current (4.9 kernel). My card wasn't supported in the kernel >until 4.13. Thanks for the reminder, I have forgotten about this thread until now. I recall looking into this further after this and was informed that vdpau will fall back to nvidia as a last resort when all else fails. As you suggested a newer kernel could help. From jgraham at compukix.net Sun Oct 14 03:19:47 2018 From: jgraham at compukix.net (Jason Graham) Date: Sat, 13 Oct 2018 23:19:47 -0400 Subject: [Slackbuilds-users] nexcloud-server 14.0.0 requires php 7 Message-ID: Hi, nextcloud-server 14.0.0 requires php 7, and thus will not work on slackware 14.2 (will work on -current however). The following message is displayed when visiting the page of a nextcloud 14.0.0 installation: ? This version of Nextcloud requires at least PHP 7.0 ? You are currently running 5.6.37. Please update your PHP version. Seems that the update to version 14 will need to be reverted back to 13 (13.0.7 is the latest and still supported). Best, Jason From sam_web at yahoo.de Mon Oct 15 08:26:12 2018 From: sam_web at yahoo.de (Marek Srejma) Date: Mon, 15 Oct 2018 10:26:12 +0200 Subject: [Slackbuilds-users] mkvtoolnix.SlackBuild: missing example files Message-ID: The mkvtoolnix source package comes with example files, which aren't being installed by the SlackBuild. The mkvmerge man page says: > TAGS > ?? Introduction > ?????? Matroska(TM)'s tag system is similar to that of other > containers: a set of KEY=VALUE pairs. However, > ?????? in Matroska(TM) these tags can also be nested, and both the KEY > and the VALUE are elements of their > ?????? own. *The example file example-tags-2.xml shows how to use this > system.* IMHO it would be useful if the SlackBuild script would copy the example directory from the source package into /usr/doc/$PRGMAN-$VERSION/. Marek From sam_web at yahoo.de Mon Oct 15 11:39:09 2018 From: sam_web at yahoo.de (Marek Srejma) Date: Mon, 15 Oct 2018 13:39:09 +0200 Subject: [Slackbuilds-users] mkvtoolnix.SlackBuild: missing example files In-Reply-To: References: Message-ID: This message was meant to be sent to the mkvtoolnix SlackBuild maintainer as well as to this mailing list, but I misspelled the maintainer's email address when sending it. So I resent the mail to his correct address and got this answer: > Hello Marek, > > Thank you for your email, I added it to the to do list. > > > -- > Ozan, BSc, BEng Thanks. Marek Marek Srejma via SlackBuilds-users schrieb: > The mkvtoolnix source package comes with example files, which aren't > being installed by the SlackBuild. > > The mkvmerge man page says: >> TAGS >> ?? Introduction >> ?????? Matroska(TM)'s tag system is similar to that of other >> containers: a set of KEY=VALUE pairs. However, >> ?????? in Matroska(TM) these tags can also be nested, and both the >> KEY and the VALUE are elements of their >> ?????? own. *The example file example-tags-2.xml shows how to use >> this system.* > > IMHO it would be useful if the SlackBuild script would copy the > example directory from the source package into > /usr/doc/$PRGMAN-$VERSION/. > > Marek > _______________________________________________ > 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 lists at osh.id.au Wed Oct 17 02:56:28 2018 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 17 Oct 2018 10:56:28 +0800 Subject: [Slackbuilds-users] Legacy Signal-Desktop to be retired Message-ID: <5040f183-d92e-6aad-3cfa-535617f777a2@osh.id.au> Just a heads up that the Signal-Desktop SlackBuild (not signal-desktop) will no longer work after 15th Nov 2018: > After 380 days of extended support, the legacy Chrome version of > Signal Desktop will stop working on November 15, 2018. The new > standalone version of Signal Desktop is available now, and it has > received regular updates in the past year -- including numerous > feature enhancements and significant performance improvements. https://github.com/signalapp/Signal-Desktop/releases/tag/v0.47.0 There's a built-in tool in the final release (0.47.0) to migrate from legacy to the new stand-alone version (the signal-desktop binary SlackBuild). So Signal-Desktop should probably be updated and the README too to reflect the situation. I've cc'd the maintainer. -- Dave From ekinakoglu at tutanota.com Wed Oct 17 12:42:56 2018 From: ekinakoglu at tutanota.com (Ekin Akoglu) Date: Wed, 17 Oct 2018 14:42:56 +0200 (CEST) Subject: [Slackbuilds-users] runc does not build Message-ID: Hi, runc build quits with the error below. Do you have an idea? I tried with sbopkg and then directly with the SlackBuild script but both did not work. go build -buildmode=pie? -ldflags "-X main.gitCommit=4fc53a81fb7c994640722ac585fa9ca548971871 -X main.version=1.0.0-rc5 " -tags "seccomp" -o runc . flag provided but not defined: -buildmode usage: build [-o output] [-i] [build flags] [packages] Build compiles the packages named by the import paths, along with their dependencies, but it does not install the results. If the arguments are a list of .go files, build treats them as a list of source files specifying a single package. When the command line specifies a single main package, build writes the resulting executable to output. Otherwise build compiles the packages but discards the results, serving only as a check that the packages can be built. The -o flag specifies the output file name. If not specified, the output file name depends on the arguments and derives from the name of the package, such as p.a for package p, unless p is 'main'. If the package is main and file names are provided, the file name derives from the first file name mentioned, such as f1 for 'go build f1.go f2.go'; with no files provided ('go build'), the output file name is the base name of the containing directory. The -i flag installs the packages that are dependencies of the target. The build flags are shared by the build, clean, get, install, list, run, and test commands: ??? -a ??? ??? force rebuilding of packages that are already up-to-date. ??? ??? In Go releases, does not apply to the standard library. ??? -n ??? ??? print the commands but do not run them. ??? -p n ??? ??? the number of builds that can be run in parallel. ??? ??? The default is the number of CPUs available. ??? -race ??? ??? enable data race detection. ??? ??? Supported only on linux/amd64, freebsd/amd64, darwin/amd64 and windows/amd64. ??? -v ??? ??? print the names of packages as they are compiled. ??? -work ??? ??? print the name of the temporary work directory and ??? ??? do not delete it when exiting. ??? -x ??? ??? print the commands. ??? -ccflags 'arg list' ??? ??? arguments to pass on each 5c, 6c, or 8c compiler invocation. ??? -compiler name ??? ??? name of compiler to use, as in runtime.Compiler (gccgo or gc). ??? -gccgoflags 'arg list' ??? ??? arguments to pass on each gccgo compiler/linker invocation. ??? -gcflags 'arg list' ??? ??? arguments to pass on each 5g, 6g, or 8g compiler invocation. ??? -installsuffix suffix ??? ??? a suffix to use in the name of the package installation directory, ??? ??? in order to keep output separate from default builds. ??? ??? If using the -race flag, the install suffix is automatically set to race ??? ??? or, if set explicitly, has _race appended to it. ??? -ldflags 'flag list' ??? ??? arguments to pass on each 5l, 6l, or 8l linker invocation. ??? -tags 'tag list' ??? ??? a list of build tags to consider satisfied during the build. ??? ??? For more information about build tags, see the description of ??? ??? build constraints in the documentation for the go/build package. The list flags accept a space-separated list of strings. To embed spaces in an element in the list, surround it with either single or double quotes. For more about specifying packages, see 'go help packages'. For more about where packages and binaries are installed, run 'go help gopath'.? For more about calling between Go and C/C++, run 'go help c'. See also: go install, go get, go clean. Makefile:30: recipe for target 'runc' failed make: *** [runc] Error 2 Best, Ekin --Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgraham at compukix.net Wed Oct 17 13:16:12 2018 From: jgraham at compukix.net (Jason Graham) Date: Wed, 17 Oct 2018 09:16:12 -0400 Subject: [Slackbuilds-users] runc does not build Message-ID: Hi Ekin, I recently encountered this as well. You may need to source either go.sh or go.csh in /etc/profile.d, or get a new login shell. Best,Jason Sent from my Sprint Phone. -------- Original message --------From: Ekin Akoglu Date: 10/17/18 8:42 AM (GMT-05:00) To: slackbuilds-users at slackbuilds.org Subject: [Slackbuilds-users] runc does not build Hi, runc build quits with the error below. Do you have an idea? I tried with sbopkg and then directly with the SlackBuild script but both did not work. go build -buildmode=pie? -ldflags "-X main.gitCommit=4fc53a81fb7c994640722ac585fa9ca548971871 -X main.version=1.0.0-rc5 " -tags "seccomp" -o runc . flag provided but not defined: -buildmode usage: build [-o output] [-i] [build flags] [packages] Build compiles the packages named by the import paths, along with their dependencies, but it does not install the results. If the arguments are a list of .go files, build treats them as a list of source files specifying a single package. When the command line specifies a single main package, build writes the resulting executable to output. Otherwise build compiles the packages but discards the results, serving only as a check that the packages can be built. The -o flag specifies the output file name. If not specified, the output file name depends on the arguments and derives from the name of the package, such as p.a for package p, unless p is 'main'. If the package is main and file names are provided, the file name derives from the first file name mentioned, such as f1 for 'go build f1.go f2.go'; with no files provided ('go build'), the output file name is the base name of the containing directory. The -i flag installs the packages that are dependencies of the target. The build flags are shared by the build, clean, get, install, list, run, and test commands: ??? -a ??? ??? force rebuilding of packages that are already up-to-date. ??? ??? In Go releases, does not apply to the standard library. ??? -n ??? ??? print the commands but do not run them. ??? -p n ??? ??? the number of builds that can be run in parallel. ??? ??? The default is the number of CPUs available. ??? -race ??? ??? enable data race detection. ??? ??? Supported only on linux/amd64, freebsd/amd64, darwin/amd64 and windows/amd64. ??? -v ??? ??? print the names of packages as they are compiled. ??? -work ??? ??? print the name of the temporary work directory and ??? ??? do not delete it when exiting. ??? -x ??? ??? print the commands. ??? -ccflags 'arg list' ??? ??? arguments to pass on each 5c, 6c, or 8c compiler invocation. ??? -compiler name ??? ??? name of compiler to use, as in runtime.Compiler (gccgo or gc). ??? -gccgoflags 'arg list' ??? ??? arguments to pass on each gccgo compiler/linker invocation. ??? -gcflags 'arg list' ??? ??? arguments to pass on each 5g, 6g, or 8g compiler invocation. ??? -installsuffix suffix ??? ??? a suffix to use in the name of the package installation directory, ??? ??? in order to keep output separate from default builds. ??? ??? If using the -race flag, the install suffix is automatically set to race ??? ??? or, if set explicitly, has _race appended to it. ??? -ldflags 'flag list' ??? ??? arguments to pass on each 5l, 6l, or 8l linker invocation. ??? -tags 'tag list' ??? ??? a list of build tags to consider satisfied during the build. ??? ??? For more information about build tags, see the description of ??? ??? build constraints in the documentation for the go/build package. The list flags accept a space-separated list of strings. To embed spaces in an element in the list, surround it with either single or double quotes. For more about specifying packages, see 'go help packages'. For more about where packages and binaries are installed, run 'go help gopath'.? For more about calling between Go and C/C++, run 'go help c'. See also: go install, go get, go clean. Makefile:30: recipe for target 'runc' failed make: *** [runc] Error 2 Best, Ekin -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From slacker6896 at gmail.com Wed Oct 17 15:37:30 2018 From: slacker6896 at gmail.com (Sebastien BALLET) Date: Wed, 17 Oct 2018 17:37:30 +0200 Subject: [Slackbuilds-users] libreoffice.SlackBuild: request for enhancement Message-ID: Hello, The .desktop files installed in /opt/libreoffice/share/xdg and symlinks to that files in /usr/share/applications have version number in their name (ex libreoffice6.1-writer.desktop) which force user to re-create/update any links/reference (placed on KDE desktop for instance) to that files on each libreoffice version number increment. To avoid that, the patch below (also in attachment) creates symlinks without libreoffice version number in their names in /usr/share/applications. 8<--------------------------------------------------------------------------------------------- --- libreoffice.SlackBuild.orig 2018-09-29 02:53:10.000000000 +0200 +++ libreoffice.SlackBuild 2018-10-17 17:29:22.368225124 +0200 @@ -130,6 +130,17 @@ ln -sf ../../opt/libreoffice$SRCSHORT/program/swriter lowriter cd - + +# creates symlinks in /usr/share/applications to libreoffice .desktop files +# (found in /opt/libreoffice/share/xdg) without libreoffice version +# number in symlink names. +# +cd $PKG/usr/share/applications + for APP in base calc draw impress math startcenter writer ; do + ln -sf ../../../opt/libreoffice$SRCSHORT/share/xdg/$APP.desktop $PRGNAM-$APP.desktop + done +cd - + # Remove DejaVu and Liberation fonts - these are included in other packages rm -f opt/libreoffice$SRCSHORT/share/fonts/truetype/{DejaVu,Liberation}*.ttf 8<--------------------------------------------------------------------------------------------- -- SeB -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: libreoffice-symlinks-no-version.patch Type: text/x-patch Size: 775 bytes Desc: not available URL: From willysr at slackbuilds.org Wed Oct 17 15:36:11 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 17 Oct 2018 22:36:11 +0700 Subject: [Slackbuilds-users] runc does not build In-Reply-To: References: Message-ID: <67353eee-4df1-3b8e-9388-4c4d4c48abd3@slackbuilds.org> > runc build quits with the error below. Do you have an idea? I tried with > sbopkg and then directly with the SlackBuild script but both did not work. Have you used "su -" instead of regular "su" -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From jgraham at compukix.net Wed Oct 17 16:03:02 2018 From: jgraham at compukix.net (Jason Graham) Date: Wed, 17 Oct 2018 16:03:02 +0000 Subject: [Slackbuilds-users] runc does not build In-Reply-To: <67353eee-4df1-3b8e-9388-4c4d4c48abd3@slackbuilds.org> Message-ID: <20181017160302.Horde.GU82S_LsmZ8gD68_hubsnJu@nextcloud.compukix.net> In my case, I used "su -", but the issue I believe is that when I installed google-go-lang within the same session prior to building runc, the installed google-go-lang profile.d file had to be sourced to correctly setup the environment for the runc build. Best, Jason Willy Sudiarto Raharjo ? Wed, 17. October 2018 11:36 > > runc build quits with the error below. Do you have an idea? I tried with > > sbopkg and then directly with the SlackBuild script but both did not work. > > > Have you used "su -" instead of regular "su" > > > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - slackbuilds.org/faq/ From willysr at slackbuilds.org Wed Oct 17 17:13:42 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 18 Oct 2018 00:13:42 +0700 Subject: [Slackbuilds-users] libreoffice.SlackBuild: request for enhancement In-Reply-To: References: Message-ID: <071d3e7b-1be8-a2b9-5a37-1a153b712786@slackbuilds.org> > The .desktop files installed in /opt/libreoffice/share/xdg and > symlinks to that files in /usr/share/applications have version number? > in their name (ex libreoffice6.1-writer.desktop) which force user to > re-create/update any links/reference (placed on KDE desktop for instance) > to that files on each libreoffice version number increment. > > To avoid that, the patch below (also in attachment) creates symlinks > without libreoffice version number in their names in > /usr/share/applications. Hi Sebastien Thanks for the patch. I tested here and it creates a duplicate entries since the old .desktop files are still there :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From slacker6896 at gmail.com Wed Oct 17 18:36:17 2018 From: slacker6896 at gmail.com (Sebastien BALLET) Date: Wed, 17 Oct 2018 20:36:17 +0200 Subject: [Slackbuilds-users] libreoffice.SlackBuild: request for enhancement In-Reply-To: <071d3e7b-1be8-a2b9-5a37-1a153b712786@slackbuilds.org> References: <071d3e7b-1be8-a2b9-5a37-1a153b712786@slackbuilds.org> Message-ID: Hello, oh ! I forgot to mention that the patch does not remove the "original" symlinks found in /usr/share/applications (ie. those with version number). If you want to get rid of those and have only "unversioned" symlinks, the patch below (and in attachment) should do the trick: 8<------------------------------------------------------------------- --- libreoffice.SlackBuild.orig 2018-10-17 20:26:30.628052769 +0200 +++ libreoffice.SlackBuild 2018-10-17 20:26:30.628052769 +0200 @@ -130,6 +130,24 @@ ln -sf ../../opt/libreoffice$SRCSHORT/program/swriter lowriter cd - + +# the .desktop files installed in /opt/libreoffice/share/xdg and +# symlinks to that files in /usr/share/applications have version number +# in their name (ex libreoffice6.1-writer.desktop) which force user to +# re-create/update any link/reference (ex: on KDE/XFCE desktop, in fluxbox +# menu file, in wmalauncher configuration file,...) to that files on each +# libreoffice version number increment. +# +# To avoid that, the code below deletes the "versioned" symlinks +# and creates news without version number in their names. +# +cd $PKG/usr/share/applications + for APP in base calc draw impress math startcenter writer xsltfilter ; do + rm -f $PRGNAM$SRCSHORT-$APP.desktop + ln -sf ../../../opt/libreoffice$SRCSHORT/share/xdg/$APP.desktop $PRGNAM-$APP.desktop + done +cd - + # Remove DejaVu and Liberation fonts - these are included in other packages rm -f opt/libreoffice$SRCSHORT/share/fonts/truetype/{DejaVu,Liberation}*.ttf 8<------------------------------------------------------------------- With that, you'll only find "unversioned" symlinks : 8<------------------------------------------------------------------- $ ls -ld /usr/share/applications/libreoffice*.desktop lrwxrwxrwx 1 root root 50 oct. 17 20:22 /usr/share/applications/libreoffice-base.desktop -> ../../../opt/libreoffice6.1/share/xdg/base.desktop lrwxrwxrwx 1 root root 50 oct. 17 20:22 /usr/share/applications/libreoffice-calc.desktop -> ../../../opt/libreoffice6.1/share/xdg/calc.desktop lrwxrwxrwx 1 root root 50 oct. 17 20:22 /usr/share/applications/libreoffice-draw.desktop -> ../../../opt/libreoffice6.1/share/xdg/draw.desktop lrwxrwxrwx 1 root root 53 oct. 17 20:22 /usr/share/applications/libreoffice-impress.desktop -> ../../../opt/libreoffice6.1/share/xdg/impress.desktop lrwxrwxrwx 1 root root 50 oct. 17 20:22 /usr/share/applications/libreoffice-math.desktop -> ../../../opt/libreoffice6.1/share/xdg/math.desktop lrwxrwxrwx 1 root root 57 oct. 17 20:22 /usr/share/applications/libreoffice-startcenter.desktop -> ../../../opt/libreoffice6.1/share/xdg/startcenter.desktop lrwxrwxrwx 1 root root 52 oct. 17 20:22 /usr/share/applications/libreoffice-writer.desktop -> ../../../opt/libreoffice6.1/share/xdg/writer.desktop lrwxrwxrwx 1 root root 56 oct. 17 20:22 /usr/share/applications/libreoffice-xsltfilter.desktop -> ../../../opt/libreoffice6.1/share/xdg/xsltfilter.desktop 8<------------------------------------------------------------------- -- SeB Le mer. 17 oct. 2018 ? 19:13, Willy Sudiarto Raharjo < willysr at slackbuilds.org> a ?crit : > > The .desktop files installed in /opt/libreoffice/share/xdg and > > symlinks to that files in /usr/share/applications have version number > > in their name (ex libreoffice6.1-writer.desktop) which force user to > > re-create/update any links/reference (placed on KDE desktop for instance) > > to that files on each libreoffice version number increment. > > > > To avoid that, the patch below (also in attachment) creates symlinks > > without libreoffice version number in their names in > > /usr/share/applications. > > Hi Sebastien > > Thanks for the patch. > I tested here and it creates a duplicate entries since the old .desktop > files are still there :) > > > -- > 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: libreoffice-symlinks-no-version.patch Type: text/x-patch Size: 1185 bytes Desc: not available URL: From willysr at slackbuilds.org Wed Oct 17 21:04:28 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 18 Oct 2018 04:04:28 +0700 Subject: [Slackbuilds-users] libreoffice.SlackBuild: request for enhancement In-Reply-To: References: <071d3e7b-1be8-a2b9-5a37-1a153b712786@slackbuilds.org> Message-ID: > oh ! I forgot to mention that the patch does not remove the "original" > symlinks found in /usr/share/applications (ie. those with version > number). If you want to get rid of those and have only "unversioned" > symlinks, the patch below (and in attachment) should do the trick: Thanks pushed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From ts at websafe.pl Fri Oct 19 12:09:56 2018 From: ts at websafe.pl (Thomas Szteliga) Date: Fri, 19 Oct 2018 14:09:56 +0200 Subject: [Slackbuilds-users] jdk 8u181 not available? Message-ID: <6a986cd8-c727-834a-862d-99c088cfbfa7@websafe.pl> Hello. is there a problem with JDK 8u181, or is it just me? https://www.oracle.com/technetwork/java/javase/downloads/index.html 8u191 and 8u192 are available for download: + http://download.oracle.com/otn-pub/java/jdk/8u191-b12/2787e4a523244c269598db4e85c51e0c/jdk-8u191-linux-x64.tar.gz + http://download.oracle.com/otn-pub/java/jdk/8u192-b12/750e1c8617c5452694857ad95c3ee230/jdk-8u192-linux-x64.tar.gz but I can't find 181 anywhere... -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3757 bytes Desc: Kryptograficzna sygnatura S/MIME URL: From ts at websafe.pl Fri Oct 19 12:20:47 2018 From: ts at websafe.pl (Thomas Szteliga) Date: Fri, 19 Oct 2018 14:20:47 +0200 Subject: [Slackbuilds-users] TeamViewer - new version available - checksum mismatch Message-ID: <2e6f6ba8-a2d6-6dc8-2fda-76ae5804d901@websafe.pl> Hello, there's a new TeamViewer v13.2.26559 available https://www.teamviewer.com/en/download/linux/ teamviewer_amd64.deb and teamviewer_amd64.deb checksums have changed. -- Thomas Szteliga From slacker6896 at gmail.com Fri Oct 19 13:40:00 2018 From: slacker6896 at gmail.com (Sebastien BALLET) Date: Fri, 19 Oct 2018 15:40:00 +0200 Subject: [Slackbuilds-users] jdk 8u181 not available? In-Reply-To: <6a986cd8-c727-834a-862d-99c088cfbfa7@websafe.pl> References: <6a986cd8-c727-834a-862d-99c088cfbfa7@websafe.pl> Message-ID: Hello, you'll find it in the archive, here : https://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html Note that you can build jdk 191 (or 192) using the current slackbuild as below : $ VERSION=8u191 ./jdk.SlackBuild -- SeB Le ven. 19 oct. 2018 ? 14:10, Thomas Szteliga a ?crit : > Hello. > > is there a problem with JDK 8u181, or is it just me? > > https://www.oracle.com/technetwork/java/javase/downloads/index.html > > > 8u191 and 8u192 are available for download: > > + > > http://download.oracle.com/otn-pub/java/jdk/8u191-b12/2787e4a523244c269598db4e85c51e0c/jdk-8u191-linux-x64.tar.gz > > + > > http://download.oracle.com/otn-pub/java/jdk/8u192-b12/750e1c8617c5452694857ad95c3ee230/jdk-8u192-linux-x64.tar.gz > > but I can't find 181 anywhere... > > > -- > Thomas Szteliga > > > _______________________________________________ > 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 ekinakoglu at tutanota.com Fri Oct 19 13:34:40 2018 From: ekinakoglu at tutanota.com (Ekin Akoglu) Date: Fri, 19 Oct 2018 15:34:40 +0200 (CEST) Subject: [Slackbuilds-users] runc does not build In-Reply-To: <20181017160302.Horde.GU82S_LsmZ8gD68_hubsnJu@nextcloud.compukix.net> References: <<67353eee-4df1-3b8e-9388-4c4d4c48abd3@slackbuilds.org>> <20181017160302.Horde.GU82S_LsmZ8gD68_hubsnJu@nextcloud.compukix.net> Message-ID: Hi, Thank you, Jason. Sourcing the google-go-lang profile.d file solved my problem. Best, Ekin -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com 17. Oct 2018 19:03 by jgraham at compukix.net : > In my case, I used "su -", but the issue I believe is that when I installed google-go-lang within the same session prior to building runc, the installed google-go-lang profile.d file had to be sourced to correctly setup the environment for the runc build. > > Best, > Jason > > > Willy Sudiarto Raharjo ? Wed, 17. October 2018 11:36 >> > runc build quits with the error below. Do you have an idea? I tried with >> > sbopkg and then directly with the SlackBuild script but both did not work. >> >> >> Have you used "su -" instead of regular "su" >> >> >> >> >> -- >> Willy Sudiarto Raharjo >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - 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 ekinakoglu at tutanota.com Fri Oct 19 13:34:40 2018 From: ekinakoglu at tutanota.com (Ekin Akoglu) Date: Fri, 19 Oct 2018 15:34:40 +0200 (CEST) Subject: [Slackbuilds-users] runc does not build In-Reply-To: <20181017160302.Horde.GU82S_LsmZ8gD68_hubsnJu@nextcloud.compukix.net> References: <<67353eee-4df1-3b8e-9388-4c4d4c48abd3@slackbuilds.org>> <20181017160302.Horde.GU82S_LsmZ8gD68_hubsnJu@nextcloud.compukix.net> Message-ID: Hi, Thank you, Jason. Sourcing the google-go-lang profile.d file solved my problem. Best, Ekin -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com 17. Oct 2018 19:03 by jgraham at compukix.net : > In my case, I used "su -", but the issue I believe is that when I installed google-go-lang within the same session prior to building runc, the installed google-go-lang profile.d file had to be sourced to correctly setup the environment for the runc build. > > Best, > Jason > > > Willy Sudiarto Raharjo ? Wed, 17. October 2018 11:36 >> > runc build quits with the error below. Do you have an idea? I tried with >> > sbopkg and then directly with the SlackBuild script but both did not work. >> >> >> Have you used "su -" instead of regular "su" >> >> >> >> >> -- >> Willy Sudiarto Raharjo >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - 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 ts at websafe.pl Fri Oct 19 14:25:21 2018 From: ts at websafe.pl (Thomas Szteliga) Date: Fri, 19 Oct 2018 16:25:21 +0200 Subject: [Slackbuilds-users] jdk 8u181 not available? In-Reply-To: References: <6a986cd8-c727-834a-862d-99c088cfbfa7@websafe.pl> Message-ID: W dniu 19/10/2018 o?15:40, Sebastien BALLET pisze: > you'll find it in the archive, here : > https://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html Thank you. Downloading this requires now an ORACLE account, OMG! http://download.oracle.com/otn/java/jdk/8u181-b13/96a7b8442fe848ef90c96a2fad6ed6d1/jdk-8u181-linux-x64.tar.gz -- Thomas Szteliga From yalhcru at gmail.com Fri Oct 19 22:01:41 2018 From: yalhcru at gmail.com (B Watson) Date: Fri, 19 Oct 2018 18:01:41 -0400 Subject: [Slackbuilds-users] conflict Message-ID: audio/SAM and development/sam both install a /usr/bin/sam. At minimum, both READMEs should mention this. Or possibly audio/SAM could rename its binary to /usr/bin/SAM. From dpross1100 at msn.com Sat Oct 20 00:27:55 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 20 Oct 2018 00:27:55 +0000 Subject: [Slackbuilds-users] conflict In-Reply-To: Message-ID: Wow, two packages installing the sam file. (Sorry, couldn't help it.) On Oct 19, 2018 6:01 PM, B Watson wrote: audio/SAM and development/sam both install a /usr/bin/sam. At minimum, both READMEs should mention this. Or possibly audio/SAM could rename its binary to /usr/bin/SAM. _______________________________________________ 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 arkadiusz at drabczyk.org Sat Oct 20 14:22:38 2018 From: arkadiusz at drabczyk.org (arkadiusz at drabczyk.org) Date: Sat, 20 Oct 2018 16:22:38 +0200 Subject: [Slackbuilds-users] conflict In-Reply-To: References: Message-ID: <20181020142238.GA19206@comp.lan> On Sat, Oct 20, 2018 at 12:27:55AM +0000, Daniel Prosser wrote: > Wow, two packages installing the sam file. > > (Sorry, couldn't help it.) Yes, it happens - for example parallel from misc/moreutils that I maintain conflicts with system/parallel. README in both contain appropriate information. It's really unpleasant when you find out that the program you've just run is not what you think it is. We could have some automated scripts that could analyze list of files in all precompiled packages and find duplicates, slackonly.com repository could be used for this. -- Arkadiusz Drabczyk From sombragris at sombragris.org Sat Oct 20 14:51:34 2018 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sat, 20 Oct 2018 11:51:34 -0300 Subject: [Slackbuilds-users] Problem downloading pdfchain - may affect other packages Message-ID: I use -current but I believe this issue affects any Slackware verson so I report here. Today I tried to build pdfchain with sbopkg and I had a problem: the file name of the downloaded source file should have been 'pdfchain-0.4.4.2.tar.gz' but came as 'download' instead. Then, sbopkg promptly complained that it couldn't build the package since the source was nowhere to be found. I think this have to do with sourceforge.net's download system, which is unnecessarily convoluted and obfuscated, so maybe other packages with source downloaded from sf.net may be affected. Renaming the 'download' file to the appropriate name solves the problem and building can proceed without issue. Possible workarounds may involve using wget -O parameters. Thanks, Eduardo -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Oficina: https://goo.gl/maps/mccgBNM7Zw32 Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow - Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From arkadiusz at drabczyk.org Sat Oct 20 14:59:43 2018 From: arkadiusz at drabczyk.org (arkadiusz at drabczyk.org) Date: Sat, 20 Oct 2018 16:59:43 +0200 Subject: [Slackbuilds-users] Problem downloading pdfchain - may affect other packages In-Reply-To: References: Message-ID: <20181020145943.GA1853@comp.lan> On Sat, Oct 20, 2018 at 11:51:34AM -0300, Eduardo Sanchez wrote: > I use -current but I believe this issue affects any Slackware verson so > I report here. > > Today I tried to build pdfchain with sbopkg and I had a problem: the > file name of the downloaded source file should have been > 'pdfchain-0.4.4.2.tar.gz' but came as 'download' instead. > > Then, sbopkg promptly complained that it couldn't build the package > since the source was nowhere to be found. > > I think this have to do with sourceforge.net's download system, which > is unnecessarily convoluted and obfuscated, so maybe other packages > with source downloaded from sf.net may be affected. > > Renaming the 'download' file to the appropriate name solves the problem > and building can proceed without issue. It probably happens because it has the following line in .info: DOWNLOAD="http://sourceforge.net/projects/pdfchain/files/pdfchain-0.4.4.2/pdfchain-0.4.4.2.tar.gz/download" It should be changed to: DOWNLOAD="http://sourceforge.net/projects/pdfchain/files/pdfchain-0.4.4.2/pdfchain-0.4.4.2.tar.gz" -- Arkadiusz Drabczyk From willysr at slackbuilds.org Sat Oct 20 21:56:17 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 21 Oct 2018 04:56:17 +0700 Subject: [Slackbuilds-users] TeamViewer - new version available - checksum mismatch In-Reply-To: <2e6f6ba8-a2d6-6dc8-2fda-76ae5804d901@websafe.pl> References: <2e6f6ba8-a2d6-6dc8-2fda-76ae5804d901@websafe.pl> Message-ID: > there's a new TeamViewer v13.2.26559 available > https://www.teamviewer.com/en/download/linux/ > teamviewer_amd64.deb and teamviewer_amd64.deb > checksums have changed. I have pushed this change few days ago in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Oct 20 21:57:49 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 21 Oct 2018 04:57:49 +0700 Subject: [Slackbuilds-users] Problem downloading pdfchain - may affect other packages In-Reply-To: References: Message-ID: <4ff4460b-473c-9a6c-2585-d7b771ee2af2@slackbuilds.org> > I use -current but I believe this issue affects any Slackware verson so > I report here. > > Today I tried to build pdfchain with sbopkg and I had a problem: the > file name of the downloaded source file should have been > 'pdfchain-0.4.4.2.tar.gz' but came as 'download' instead. > > Then, sbopkg promptly complained that it couldn't build the package > since the source was nowhere to be found. > > I think this have to do with sourceforge.net's download system, which > is unnecessarily convoluted and obfuscated, so maybe other packages > with source downloaded from sf.net may be affected. > > Renaming the 'download' file to the appropriate name solves the problem > and building can proceed without issue. > > Possible workarounds may involve using wget -O parameters. Thanks for the report fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From idlemoor at slackbuilds.org Sat Oct 20 22:24:46 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Sat, 20 Oct 2018 23:24:46 +0100 Subject: [Slackbuilds-users] nexcloud-server 14.0.0 requires php 7 In-Reply-To: References: Message-ID: > Hi, > > nextcloud-server 14.0.0 requires php 7, and thus will not work on > slackware 14.2 (will work on -current however). > > The following message is displayed when visiting the page of a nextcloud > 14.0.0 installation: > > ? This version of Nextcloud requires at least PHP 7.0 > ? You are currently running 5.6.37. Please update your PHP version. > > Seems that the update to version 14 will need to be reverted back to 13 > (13.0.7 is the latest and still supported). HI Jason, thanks for spotting that, and sorry for my cockup, and sorry for the late reply :( I've been working on a php7.2 SlackBuild for SBo/14.2, but it's going to miss this week's public update, sorry :( Thanks again and sorry again -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Oct 21 00:53:28 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 21 Oct 2018 07:53:28 +0700 Subject: [Slackbuilds-users] Updates - 20181020.1 Message-ID: <41067766-32ba-8fa7-8657-84d411446dad@slackbuilds.org> Hi Due to traveling, this weekend's public update is almost 24h behind normal schedule, but we got plenty of updates in this batch and managed to fix more warnings due to https transitions. We have more than 180 commits, which is way beyond our normal commits per week. have a nice weekend Sat Oct 20 23:48:10 UTC 2018 academic/STAR: Updated for version 2.6.1c. academic/engauge: Updated for version 10.10. audio/SAM: Updated for version 20171105_bcf92b5. audio/faad2: Switch homepage to https. audio/mixxx: Updated for version 2.1.4. audio/opusfile: Updated for version 0.11. desktop/Alphacube-GTK: Fixed download. desktop/Ater-MPlayer-skin: Fixed download, updated homepage. desktop/Pulse-Glass: Fixed download, updated homepage. desktop/adwaita-qt: Updated for version 1.0. desktop/areao43-icon-theme: Fixed download, updated homepage. desktop/awesome-extra: Updated for version 2018101101. desktop/cwp: Fixed download. desktop/faenza-cupertino: Fixed download. desktop/gr1d: Fixed download, updated homepage. desktop/kcometen4: Fixed download, updated homepage. desktop/neutral: Fixed download. desktop/numix-pack: Fixed download. desktop/plasma-adjustable-clock: Fixed homepage. desktop/plasma-runner-browsefirefoxbookmarks: Fixed homepage. desktop/plasmaxplanet: Fixed download. desktop/smaragd: Fixed download. desktop/thunar-archive-plugin: Switch homepage+download to https. desktop/thunar-media-tags-plugin: Switch homepage+download to https. desktop/thunar-thumbnailers: Switch homepage and download to https. desktop/thunar-vcs-plugin: Switch homepage and download to https. desktop/vbox-runner: Fixed download. desktop/xfce4-battery-plugin: Switch homepage and download to https. desktop/xfce4-cpufreq-plugin: Switch homepage and download to https. desktop/xfce4-cpugraph-plugin: Switch homepage+download to https. desktop/xfce4-datetime-plugin: Switch homepage+download to https. desktop/xfce4-dict: Switch homepage and download to https. desktop/xfce4-diskperf-plugin: Switch homepage+download to https. desktop/xfce4-embed-plugin: Switch homepage and download to https. desktop/xfce4-eyes-plugin: Switch homepage and download to https. desktop/xfce4-fsguard-plugin: Switch homepage and download to https. desktop/xfce4-genmon-plugin: Switch homepage and download to https. desktop/xfce4-kbdleds-plugin: Switch homepage to https. desktop/xfce4-mailwatch-plugin: Switch homepage+download to https. desktop/xfce4-mount-plugin: Switch homepage and download to https. desktop/xfce4-mpc-plugin: Switch homepage and download to https. desktop/xfce4-netload-plugin: Switch homepage and download to https. desktop/xfce4-notes-plugin: Switch homepage and download to https. desktop/xfce4-places-plugin: Switch homepage and download to https. desktop/xfce4-quicklauncher-plugin: Switch homepage + dl to https. desktop/xfce4-sensors-plugin: Switch homepage and download to https. desktop/xfce4-smartbookmark-plugin: Switch homepage + dl to https. desktop/xfce4-timer-plugin: Switch homepage and download to https. desktop/xfce4-verve-plugin: Switch homepage and download to https. desktop/xfce4-wavelan-plugin: Switch homepage and download to https. desktop/xfce4-whiskermenu-plugin: Switch download to https. desktop/xfce4-windowck-plugin: Switch homepage to https. desktop/xfce4-xkb-plugin: Switch homepage and download to https. desktop/xfce4-xmms-plugin: Switch homepage and download to https. development/colm: Updated for version 0.13.0.6. development/d-tools: Updated for version 2.082.1 development/dmd: Updated for version 2.082.1 development/dpkg: Updated for version 1.19.2. development/extra-cmake-modules: Updated for version 5.51.0. development/glm: Updated for version 0.9.9.2. development/ioncube-loader: Updated for version 10.2.5 development/jupyter-qtconsole: Updated for version 4.4.2. development/pkgconf: Updated for version 1.5.4. development/ragel: Updated for version 7.0.0.11. development/rustup: Updated for version 1.14.0 development/sbcl: Updated for version 1.4.12. development/textadept: Updated for version 10.1. development/universal-ctags: Updated for version 45968ef development/valgrind: Updated for version 3.14.0. development/vile: Updated for version 9.8s. development/xtruss: Updated for version 20181001.82973f5. development/xvile: Updated for version 9.8s. games/mame: Updated for version 0.202. games/manaplus: Added (A free Open Source 2D MMORPG). games/pysolfc-extra-cardsets: Added (extra cards for pysolfc). games/pysolfc: Updated for version 2.4.0, new maintainer. gis/foxtrotgps: Fix build with gpsd-3.18.1. gis/geojson: Updated for version 2.4.1. gis/gpsd: Updated for version 3.18.1. gis/ossim: Updated for version 2.5.2. gis/viking: Fix build with gpsd-3.18.1. graphics/hugin: Updated for version 2018.0.0. graphics/nomacs: Updated for version 3.10.2. graphics/opencollada: Updated for version 1.6.66 graphics/ristretto: Switch homepage and download to https. libraries/SFML: Switch homepage and download to https. libraries/SOPE: Updated for version 4.0.3. libraries/aubio: Updated for version 0.4.7. libraries/gtk-aurora-engine: Fixed download. libraries/hoel: Updated for version 1.4.5. libraries/libcacard: Updated for version 2.6.1. libraries/libdockapp: New maintainer, minor fixes. libraries/libebml: Updated Libebml to 1.3.6. libraries/libversion: Updated for version 2.7.0. libraries/libxfcegui4: Switch homepage and download to https. libraries/live555: Updated for version 2018.10.17 libraries/orcania: Updated for version 1.2.7. libraries/pjproject-ring: Switch homepage and download to https. libraries/pjsip: Switch homepage and download to https. libraries/ulfius: Updated for version 2.4.3. libraries/virglrenderer: Updated for version 0.7.0. libraries/yder: Updated for version 1.4.3. multimedia/aces-dev: Switch homepage to https. multimedia/obs-studio: Update README (mention luajit) multimedia/opera-developer-ffmpeg-codecs: Updated for v 0.33.4. multimedia/opera-ffmpeg-codecs: Updated for version 0.33.4. multimedia/parole: Switch homepage and download to https. network/WireGuard: Updated for version 0.0.20181018. network/brave: Updated for version 0.25.2. network/clipgrab: Updated for version 3.7.1. network/driftnet: Updated for version 1.2.0. network/elinks: Update README network/falkon: Added (lightweight web browser). network/glewlwyd: Updated for version 1.4.7. network/hostapd: Patched to fix CVE-2018-14526. network/lighttpd: Updated for version 1.4.51. network/modemu2k: Updated for version 0.0.3. network/nextcloud-server: Updated for version 13.0.7. network/nikto: Fix CVE-2018-11652. network/opera-developer: Updated for version 58.0.3105.0. network/opera: Updated for version 56.0.3051.43. network/qupzilla: Removed (superseded by falkon). network/riot-web: Updated for version 0.17.0. network/signal-desktop: Updated for version 1.16.3. network/spice: Updated for version 0.14.1. network/sqlmap: Updated for version 1.2.10. network/teamviewer: Updated for version 13.2.13582. network/telegram: Updated for version 1.4.3. network/vivaldi: Updated for version 2.0.1309.42. network/wireshark: Updated for version 2.6.4. network/yandex-browser-beta: Updated for version 18.9.1.967. office/SOGo: Updated for version 4.0.3. office/calcurse: Update to 4.3.0. New maintainer. office/libreoffice: Remove version number in symlinks. office/mairix: Updated for version 0.24. office/notmuch: Updated for version 0.28. office/pdfchain: Fix DOWNLOAD. office/sc-im: Updated for version 0.7.0. perl/perl-Math-BigInt-GMP: Updated for version 1.6006. perl/perl-Math-BigInt: Updated for version 1.999814. perl/perl-libnet: Updated for version 3.11. python/Logbook: Switch homepage to https. python/PyGithub: Switch homepage to https. python/bleach: Updated for version 3.0.2. python/funcsigs: Switch homepage to https. python/mistune: Updated for version 0.8.4. python/python-prometheus_client: Updated for version 0.4.2. python/python3-jupyter-ipykernel: Updated for version 5.1.0. python/python3-prompt_toolkit: 2.0.6. python/thunarx-python: Switch homepage and download to https. python/tinycss: Switch homepage to https. ruby/ruby-build: Updated for version 20181019. ruby/rubygem-jaro_winkler: Added (Jaro-Winkler distance alg). ruby/rubygem-rubocop: Add missing dependency. ruby/rubygem-ruumba: Updated for version 0.1.6. ruby/rubygem-tins: Updated for version 1.17.0. system/Iosevka: Updated for version 2.0.1. system/adobe-source-serif-pro-font: Switch homepage to https. system/alacritty: Updated for version 0.2.1. system/avfs: Updated for version 1.0.6. system/epson-inkjet-printer-escpr2: Updated for version 1.0.26. system/fio: Updated for version 3.11. system/komparator4: Fixed download. system/loksh: Updated for version 6.4. system/lxterminal: Updated for version 0.3.2. system/monit: Updated for version 5.25.2. system/nano-syntax-highlighting: Updated for version 20181011. system/otf2bdf: Fix download and homepage links. system/posh: Updated for version 0.13.2. system/pstate-frequency: Updated for version 3.10.0. system/sleuthkit: Updated for version 4.6.2. system/tagtools: Added (tagfile separate in Slackware Linux). system/telegraf: Updated for version 1.8.2. system/ttf-zekton: Fixed download. system/usbredir: Updated for version 0.8.0. system/vagrant: Updated for version 2.2.0. system/vice: Updated for version 3.2. system/wine-staging: Updated for version 3.18. system/xfburn: Switch homepage and download to https. system/zstd: Updated for version 1.3.7. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From jgraham at compukix.net Sun Oct 21 03:34:14 2018 From: jgraham at compukix.net (Jason Graham) Date: Sat, 20 Oct 2018 23:34:14 -0400 Subject: [Slackbuilds-users] nexcloud-server 14.0.0 requires php 7 In-Reply-To: References: Message-ID: > HI Jason, thanks for spotting that, and sorry for my cockup, and sorry > for the late reply :( > > I've been working on a php7.2 SlackBuild for SBo/14.2, but it's going to > miss this week's public update, sorry :( > > Thanks again and sorry again > -D. > > Thanks David, no worries. I'll keep an eye out for the php7.2 SlackBuild and give the php7 + NC14 a try when ready. Cheers, Jason From belka at caraus.de Sun Oct 21 05:10:23 2018 From: belka at caraus.de (Eugen Wissner) Date: Sun, 21 Oct 2018 07:10:23 +0200 Subject: [Slackbuilds-users] nexcloud-server 14.0.0 requires php 7 In-Reply-To: References: Message-ID: <1540098623.2016.5.camel@caraus.de> Hello, I attach a build script for php 7.2.11. It builds/installs additionally pgsql and ioncube extensions, so it should be cleaned up a bit. The package also doesn't include apache module, only FPM. The script is production ready and doesn't conflict with php5. For the case someone finds it useful. Regards Eugene Am Samstag, den 20.10.2018, 23:24 +0100 schrieb David Spencer: > > Hi, > > > > nextcloud-server 14.0.0 requires php 7, and thus will not work on > > slackware 14.2 (will work on -current however). > > > > The following message is displayed when visiting the page of a > > nextcloud > > 14.0.0 installation: > > > > ? This version of Nextcloud requires at least PHP 7.0 > > ? You are currently running 5.6.37. Please update your PHP version. > > > > Seems that the update to version 14 will need to be reverted back > > to 13 > > (13.0.7 is the latest and still supported). > > HI Jason, thanks for spotting that, and sorry for my cockup, and > sorry > for the late reply :( > > I've been working on a php7.2 SlackBuild for SBo/14.2, but it's going > to > miss this week's public update, sorry :( > > Thanks again and sorry again > -D. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- A non-text attachment was scrubbed... Name: doinst.sh Type: application/x-shellscript Size: 974 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: php7.SlackBuild Type: application/x-shellscript Size: 7405 bytes Desc: not available URL: From kingbeowulf at gmail.com Sun Oct 21 21:34:37 2018 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 21 Oct 2018 14:34:37 -0700 Subject: [Slackbuilds-users] Nvidia drops 32-bit support after 390 series Message-ID: Nvidia has released the 410 drivers for x86_64. 32-bit is deprecated - no driver after the 390 series. The 410 series x86_64 driver will continue to have 32-bit libraries for multilib. I do not plane at this time to support a legacy-390 script, For those with 32-bit systems running Nvidia GPU, either stick with 390.87 on SBo, or use nouveau. https://nvidia.custhelp.com/app/answers/detail/a_id/4604/~/support-plan-for-32-bit-and-64-bit-operating-systems -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: OpenPGP digital signature URL: From ponce at slackbuilds.org Sat Oct 20 06:02:15 2018 From: ponce at slackbuilds.org (Matteo Bernardini) Date: Sat, 20 Oct 2018 08:02:15 +0200 Subject: [Slackbuilds-users] conflict In-Reply-To: References: Message-ID: <3e43222c-c738-2e9e-37fd-110dd71679ee@slackbuilds.org> On 20/10/18 00:01, B Watson wrote: > audio/SAM and development/sam both install a /usr/bin/sam. At minimum, > both READMEs should mention this. Or possibly audio/SAM could rename > its binary to /usr/bin/SAM. done the second, thanks for noticing! Matteo From rush830 at yahoo.com Mon Oct 22 06:55:19 2018 From: rush830 at yahoo.com (Diamond) Date: Mon, 22 Oct 2018 06:55:19 +0000 (UTC) Subject: [Slackbuilds-users] Open Al source download References: <414805754.13811456.1540191319629.ref@mail.yahoo.com> Message-ID: <414805754.13811456.1540191319629@mail.yahoo.com> Just an FYI, the source download link for OpenAl (http://slackbuilds.org/repository/14.2/libraries/OpenAL/) no longer works.? I have provided ones that do. http://www.openal-soft.org/#download http://www.openal-soft.org/openal-releases/openal-soft-1.18.0.tar.bz2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Oct 23 02:08:38 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 22 Oct 2018 22:08:38 -0400 Subject: [Slackbuilds-users] mhWaveEdit update In-Reply-To: <1536701450.2790284.1504805568.45ED88E2@webmail.messagingengine.com> References: <1536701450.2790284.1504805568.45ED88E2@webmail.messagingengine.com> Message-ID: On 9/11/18, jys wrote: > > Forwarding this response from the (no longer) maintainer of the mhWaveEdit > slackbuild. It should be pretty low maintenance for whoever wants to take it > over... Sure, I'll take it, it looks kinda useful. From duncan_roe at optusnet.com.au Tue Oct 23 06:37:41 2018 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Tue, 23 Oct 2018 17:37:41 +1100 Subject: [Slackbuilds-users] sage up for grabs UNMAINTAINED In-Reply-To: References: <3e1d444e-dc99-0524-20f3-11b76b8838d0@gmail.com> <9d4f6839-8a40-d700-e4ac-8fd997936428@gmail.com> <107bc49a-f99c-22e0-889b-1644933f99cc@slint.fr> <20180821234947.GA2263@dimstar.local.net> Message-ID: <20181023063741.GA31910@dimstar.local.net> Hi JCA, On Tue, Aug 21, 2018 at 06:13:21PM -0600, JCA wrote: > On Tue, Aug 21, 2018 at 5:49 PM, Duncan Roe > wrote: > > > On Mon, Aug 13, 2018 at 09:08:46AM -0600, JCA wrote: > > > Why not use the Debian binary tarball that is available in the Sage > > > website? I have just tried (for Sage 8.3) and it seems to work fine. Here > > > is what I did: > > > > > > 1. As root, unpacked the tarball in /opt. This create /opt/SageMath. > > > 2. cd /opt/SageMath. > > > 3. ./sage. This patches up Sage's files (black magic?) and launches Sage. > > > You end up at the Sage CLI. It can be checked out that it works, at least > > > for simple operations - like, e.g. an integration. > > > 4. Exit Sage. > > > 5. cd /usr/local/bin. > > > 6. ln -s /opt/SageMath/sage ./sage. > > > 7. Exit root. > > > 8. Assuming that /usr/local/bin is in your path, launch Sage by invoking > > > the sage command. > > > 9. Verify that it works. > > > > > > Assuming that the above keeps working when using more esoteric Sage > > > capabilities, getting a Slackbuilds script to do all that should be > > > straightforward. I haven't tried building for sources, but I find it > > > difficult to believe that the Debian binary tarball is created using some > > > knowledge available to members of the inner circle alone. > > > > > > If I am missing something here please let me know. > > > > > Hi JCA, > > > > Sounds like it should be easy enough to automate into a build script using > > mkchroot. I can give it a go (but I'm not a sage user). Could you please > > clarify a couple if items: > > > > 1. Does ./sage really work after cd-ing to a freshly created directory? > > > > I am not sure I understand your question. What I describe allows one to > install the Sage executable under /usr/local/bin, and launch it from > anywhere, provided that /usr/local/bin is in your path. You would only > invoked ./sage from /usr/local/bin, but - why would you want to that? > > > > > 2. I assume checking with an integration is not essential to the build > > process - > > is that correct? > > > > That integration is nothing but a very basic functional test of the > installed product. I just used the Debian package - I did not build Sage > myself, for it takes ages and a serious system. I am merely pointing out > that, following the steps I described above, one ends up with a Sage > environment that seems to work fine, and one does not have to suffer the > punishment that the original maintainer described in order to install it in > a sensible location. I have tried a few other things in the resulting Sage, > and they all seem to work. > > > > Cheers ... Duncan. > > > > > > On Fri, Aug 10, 2018 at 11:26 AM, Didier Spaier wrote: > > > > > > > I forgot: his user a set specific user "maths" for that. > > > > > > > > On 08/10/2018 07:23 PM, Didier Spaier wrote: > > > > > > > > > > On 08/10/2018 04:22 AM, Daniel Prosser wrote: > > > > >> Perhaps if upstream is fighting so hard to make it *not* possible to > > > > package > > > > >> sage, the best course of action is just to honor their intent and > > stop > > > > trying > > > > >> (take it off SBo). Just my two cents as someone who does not use it > > > > anyway (so > > > > >> maybe it's actually only worth one cent). > > > > > > > > > > I am not an user either, but I once compiled it as regular user just > > to > > > > check > > > > > its ability to make png files for graphs, for an actual (and blind) > > user. > > > > > I just asked this friend, he is currently using the 8.1 version. > > > > > > > > > > As for maths there is nothing close to sage's features I'd suggest > > > > > not providing a SlackBuild but a README explaining the situation. > > > > > > > > > > Just my 0.02???. Thanks for getting back with answers to my dumb questions and sorry for the noise. I went ahead and submitted (what became) sage-bin-8.3 (thanks for all the work, mods) and it's been on SBO for just over a month now. I guess I should have posted to this thread about that :/ It's a package of the Debian tarball as you suggested, installs (a symlink) in /usr/bin works from anywhere etc. etc. I did try some plots and they looked fine, but mostly I just (mis-)use it to do proper-fraction arithmetic - it's great! Cheers ... Duncan. From 1.41421 at gmail.com Tue Oct 23 17:03:24 2018 From: 1.41421 at gmail.com (JCA) Date: Tue, 23 Oct 2018 11:03:24 -0600 Subject: [Slackbuilds-users] sage up for grabs UNMAINTAINED In-Reply-To: <20181023063741.GA31910@dimstar.local.net> References: <3e1d444e-dc99-0524-20f3-11b76b8838d0@gmail.com> <9d4f6839-8a40-d700-e4ac-8fd997936428@gmail.com> <107bc49a-f99c-22e0-889b-1644933f99cc@slint.fr> <20180821234947.GA2263@dimstar.local.net> <20181023063741.GA31910@dimstar.local.net> Message-ID: Thanks for taking care of this. It sure beats having to build the beast from scratch - which, unless one has a rather beefy machine, will take forever. This aside from the relocation issues. On Tue, Oct 23, 2018 at 12:37 AM Duncan Roe wrote: > Hi JCA, > > On Tue, Aug 21, 2018 at 06:13:21PM -0600, JCA wrote: > > On Tue, Aug 21, 2018 at 5:49 PM, Duncan Roe > > wrote: > > > > > On Mon, Aug 13, 2018 at 09:08:46AM -0600, JCA wrote: > > > > Why not use the Debian binary tarball that is available in the Sage > > > > website? I have just tried (for Sage 8.3) and it seems to work fine. > Here > > > > is what I did: > > > > > > > > 1. As root, unpacked the tarball in /opt. This create /opt/SageMath. > > > > 2. cd /opt/SageMath. > > > > 3. ./sage. This patches up Sage's files (black magic?) and launches > Sage. > > > > You end up at the Sage CLI. It can be checked out that it works, at > least > > > > for simple operations - like, e.g. an integration. > > > > 4. Exit Sage. > > > > 5. cd /usr/local/bin. > > > > 6. ln -s /opt/SageMath/sage ./sage. > > > > 7. Exit root. > > > > 8. Assuming that /usr/local/bin is in your path, launch Sage by > invoking > > > > the sage command. > > > > 9. Verify that it works. > > > > > > > > Assuming that the above keeps working when using more esoteric Sage > > > > capabilities, getting a Slackbuilds script to do all that should be > > > > straightforward. I haven't tried building for sources, but I find it > > > > difficult to believe that the Debian binary tarball is created using > some > > > > knowledge available to members of the inner circle alone. > > > > > > > > If I am missing something here please let me know. > > > > > > > Hi JCA, > > > > > > Sounds like it should be easy enough to automate into a build script > using > > > mkchroot. I can give it a go (but I'm not a sage user). Could you > please > > > clarify a couple if items: > > > > > > 1. Does ./sage really work after cd-ing to a freshly created directory? > > > > > > > I am not sure I understand your question. What I describe allows one > to > > install the Sage executable under /usr/local/bin, and launch it from > > anywhere, provided that /usr/local/bin is in your path. You would only > > invoked ./sage from /usr/local/bin, but - why would you want to that? > > > > > > > > 2. I assume checking with an integration is not essential to the build > > > process - > > > is that correct? > > > > > > > That integration is nothing but a very basic functional test of the > > installed product. I just used the Debian package - I did not build Sage > > myself, for it takes ages and a serious system. I am merely pointing out > > that, following the steps I described above, one ends up with a Sage > > environment that seems to work fine, and one does not have to suffer the > > punishment that the original maintainer described in order to install it > in > > a sensible location. I have tried a few other things in the resulting > Sage, > > and they all seem to work. > > > > > > > Cheers ... Duncan. > > > > > > > > On Fri, Aug 10, 2018 at 11:26 AM, Didier Spaier > wrote: > > > > > > > > > I forgot: his user a set specific user "maths" for that. > > > > > > > > > > On 08/10/2018 07:23 PM, Didier Spaier wrote: > > > > > > > > > > > > On 08/10/2018 04:22 AM, Daniel Prosser wrote: > > > > > >> Perhaps if upstream is fighting so hard to make it *not* > possible to > > > > > package > > > > > >> sage, the best course of action is just to honor their intent > and > > > stop > > > > > trying > > > > > >> (take it off SBo). Just my two cents as someone who does not > use it > > > > > anyway (so > > > > > >> maybe it's actually only worth one cent). > > > > > > > > > > > > I am not an user either, but I once compiled it as regular user > just > > > to > > > > > check > > > > > > its ability to make png files for graphs, for an actual (and > blind) > > > user. > > > > > > I just asked this friend, he is currently using the 8.1 version. > > > > > > > > > > > > As for maths there is nothing close to sage's features I'd > suggest > > > > > > not providing a SlackBuild but a README explaining the situation. > > > > > > > > > > > > Just my 0.02???. > > Thanks for getting back with answers to my dumb questions and sorry for the > noise. > > I went ahead and submitted (what became) sage-bin-8.3 (thanks for all the > work, > mods) and it's been on SBO for just over a month now. > > I guess I should have posted to this thread about that :/ > > It's a package of the Debian tarball as you suggested, installs (a > symlink) in > /usr/bin works from anywhere etc. etc. > > I did try some plots and they looked fine, but mostly I just (mis-)use it > to do > proper-fraction arithmetic - it's great! > > 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 willysr at slackbuilds.org Sat Oct 27 02:36:17 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 27 Oct 2018 09:36:17 +0700 Subject: [Slackbuilds-users] Updates - 20181027.1 Message-ID: <489915f9-cb69-d159-c44b-8f3193a520e4@slackbuilds.org> Sat Oct 27 02:28:17 UTC 2018 academic/Gridcoin-Research: Updated for version 4.0.0.0. audio/accuraterip-checksum: Update HOMEPAGE and DOWNLOAD urls. audio/opus: Updated for version 1.3. audio/whipper: Updated for version 0.7.1. desktop/cairo-clock: Added (Analog Clock). desktop/jgmenu: Updated for version 1.4. development/adoptopenjdk: Added (Open Implementation of JDK). development/netbeans: Updated for version 9.0 + new maintainer. development/slibtool: Updated for version 0.5.26. games/lutris: Updated for version 0.4.21. gis/gpxsee: Updated for version 6.3. gis/openorienteering-mapper: Updated for version 0.8.3. gis/polyline: Require Python 3. gis/rasterio: Updated for version 1.0.9. gis/saga-gis: Updated for version 7.0.0. libraries/OpenAL: New homepage and download URLs. libraries/appstream-glib: Updated for version 0.7.14. libraries/libsigrok: Updated for version 0.5.1. libraries/ntl: Updated for version 11.3.1. multimedia/opera-developer-ffmpeg-codecs: Updated for v0.34.0. multimedia/opera-ffmpeg-codecs: Updated for version 0.34.0. multimedia/smplayer: Updated for version 18.10.0. multimedia/vivaldi-codecs-ffmpeg-extra: Updated for version 70.0. network/fail2ban: Updated for version 0.10.4. network/liferea: Fix source. network/opera-developer: Updated for version 58.0.3120.0. network/opera: Updated for version 56.0.3051.52. network/qutebrowser: Update to 1.5.1 network/signal-desktop: Updated for version 1.17.0. network/sslscan: Updated for version 1.11.12. network/vivaldi: Updated for version 2.1.1337.36. network/weechat: Updated for version 2.3. office/pdfstudio2018: Fixed md5sums. perl/perl-Math-BigInt: Updated for version 1.999815. perl/perl-Sidef: Updated for version 3.50. python/pycld2: Script clean up. system/ansible: Updated for version 2.6.6. system/btrbk: Updated for version 0.27.0. system/dar: Updated for version 2.5.17. system/nano-syntax-highlighting: Updated for version 20181023. system/powerkit: Added (desktop independent power manager). system/rear: Added (disaster recovery and system migration tool). system/rmw: Updated for version 0.4.05. system/sqldiff: Change to tgz. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From orbea at fredslev.dk Sat Oct 27 15:27:10 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Sat, 27 Oct 2018 08:27:10 -0700 Subject: [Slackbuilds-users] slibtool Message-ID: <20181027082710.235182a8@Akita.witch.org> Hi, I have been maintaining development/slibtool on SBo for a while which is a drop-in replacement for GNU libtool and working with its upstream to fix any build issues I can find with my limited setup. Slibtool ships with several different symlinks which generate different behaviors and with this recent update to 0.5.26 it now includes several new symlinks to add convenience for end users. Mainly the symlink 'rlibtool' which should fully respect the '--enable-shared' and similar configure arguments. To use it basically add this to your environment, it can be put in '/etc/profile' to make it default. The libtool package should not be uninstalled and is still needed for tools like autoreconf and similar. export 'MAKEFLAGS=LIBTOOL=rlibtool' or if you want to preserve the behavior of libtool to install (.la) files. export 'MAKEFLAGS=LIBTOOL=rclibtool' Both have more verbose debugging modes too. export 'MAKEAFLAGS=LIBTOOL=rdlibtool' export 'MAKEFLAGS=LIBTOOL=rdclibtool' In 14.2 its potentially safer to use rclibtool instead while current the (.la) files are almost never needed. Some exceptions I have found are games/pinball from SBo and imagemagick in the main tree. There are also a few cases where programs use libtool without autotools and rlibtool by design will fail. Another one of the symlinks like 'slibtool-shared' should be used in those cases. Please read the README at SBo and the upstream README installed in the documentation directory for more info. Some benefits are a significant increase in build speed and avoiding a whole range of issues, limitations and caveats with GNU libtool. In short my request is that if anyone is willing to test slibtool I would appreciate being informed of any build or other issues that do not occur with libtool in the main Slackware tree with either 14.2 or current. I do not have the capability to mass build large number of packages with my limited and already filled hard drive space. Alternatively any issues can be brought up in #midipix @ freenode if you use irc. Thanks, Hunter From yalhcru at gmail.com Mon Oct 29 04:18:00 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 29 Oct 2018 00:18:00 -0400 Subject: [Slackbuilds-users] six and python3-six Message-ID: Do we need separate six and python3-six builds? Right now, six will build & install python3 support if python3 is installed on the build box. python3-six is identical, except (a) it requires python3 in the .info file and (b) it builds only the python3 stuff. I'd say either these 2 builds should be combined, or else the six build should be modified so it's python2-only (get rid of optional python3 support). But, I'm not the maintainer of either of these, and I'm not even a Python programmer. Opinions? From yalhcru at gmail.com Mon Oct 29 04:38:50 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 29 Oct 2018 00:38:50 -0400 Subject: [Slackbuilds-users] conflict In-Reply-To: <20181020142238.GA19206@comp.lan> References: <20181020142238.GA19206@comp.lan> Message-ID: On 10/20/18, arkadiusz at drabczyk.org wrote: > > Yes, it happens - for example parallel from misc/moreutils that I > maintain conflicts with system/parallel. README in both contain > appropriate information. It's really unpleasant when you find out > that the program you've just run is not what you think it is. We > could have some automated scripts that could analyze list of files in > all precompiled packages and find duplicates, slackonly.com repository > could be used for this. I'm working on a script that does just this: parses the MANIFEST.bz2 from slackonly, and spits out a list of conflicting packages (and the files that conflict). It found 186 conflicts... each "conflict" is a set of 2 or more packages that installs one or more of the same file (so if 2 packages install the same 20 files, that's still only one conflict). Some of these are documented in the READMEs, and some aren't. Unfortunately there's no standard machine-friendly way to document conflicts, so I'm having to actually read all these READMEs myself and make notes. I'm working on whittling down the list, eliminating the documented conflicts. For now, if anyone's interested, here's the raw list of conflicts: http://urchlay.naptime.net/~urchlay/src/conflicts.wip.txt Using slackonly for this isn't perfect: the MANIFEST is about 3 months old at this point, and optional stuff isn't always included in the slackonly packages. Also MANIFEST doesn't list symlinks at all (those are in the doinst.sh for each package) so the script doesn't check them. However, this isn't meant to be a complaint about slackonly: I really appreciate the hard work that goes into creating & maintaining it, and without it, I'd have no way to even start on my conflict-finder script. So, a big "thank you" to Panagiotis Nikolaou. From yalhcru at gmail.com Mon Oct 29 04:41:18 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 29 Oct 2018 00:41:18 -0400 Subject: [Slackbuilds-users] six and python3-six In-Reply-To: References: Message-ID: On 10/29/18, B Watson wrote: > Do we need separate six and python3-six builds? Disregard previous email on this subject, I see that six has been updated to only install python2 modules. I was looking at the slackonly binary packages, not the latest SBo. Apologies if I raised anyone's blood pressure. From rshepard at appl-ecosys.com Mon Oct 29 12:44:15 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 29 Oct 2018 05:44:15 -0700 (PDT) Subject: [Slackbuilds-users] six and python3-six In-Reply-To: References: Message-ID: On Mon, 29 Oct 2018, B Watson wrote: > Do we need separate six and python3-six builds? > Right now, six will build & install python3 support if python3 is > installed on the build box. python3-six is identical, except (a) it > requires python3 in the .info file and (b) it builds only the python3 > stuff. I'm a Python end-user and support the idea of having one build that supports both Python2 and Python3. All my new code is Python3 but many applications remain bound to Python2. It will take a while for everyone to migrate to Python3. Rich From slackbuilds at jaxartes.net Mon Oct 29 16:52:53 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Mon, 29 Oct 2018 09:52:53 -0700 Subject: [Slackbuilds-users] six and python3-six In-Reply-To: References: Message-ID: <93ce53e1-de09-5642-a345-ce72d6e0be39@jaxartes.net> On 2018-10-29 5:44 a.m., Rich Shepard wrote: > On Mon, 29 Oct 2018, B Watson wrote: > >> Do we need separate six and python3-six builds? > >> Right now, six will build & install python3 support if python3 is >> installed on the build box. python3-six is identical, except (a) it >> requires python3 in the .info file and (b) it builds only the python3 >> stuff. > > ? I'm a Python end-user and support the idea of having one build that > supports both Python2 and Python3. All my new code is Python3 but many > applications remain bound to Python2. It will take a while for everyone to > migrate to Python3. For what it's worth, when 15.0 is released, I strongly advocate that Python SlackBuilds cover both Python 2 and 3 together in the same script - just like Pat is doing on current now. Yes, there are few cases where this won't be possible due to incompatibilities (for example IPython needs different versions for Python 2 and Python 3), but those are exceptions. For 14.2, there are several approaches being taken depending on the script maintainer, including various types of support for Python 3 in a Python 2 build script or having two scripts, one each for 2 and 3. My opinion is that we probably don't want to rock the boat too much during 14.2's lifetime but when we do switch to 15.0, I expect to see quite a bit of change in the Python SlackBuilds landscape. That being said, I have added *mandatory* Python 3 support to a few of my SlackBuild scripts to gauge whether it might make sense to start the conversion earlier (e.g. https://git.slackbuilds.org/slackbuilds/commit/?id=1ffc4da77ce21b851bb6dbb8fe01638a8b8d411b). So far no complaints. It's 2018 ... who still objects to having Python 3 installed? From yalhcru at gmail.com Mon Oct 29 21:26:41 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 29 Oct 2018 17:26:41 -0400 Subject: [Slackbuilds-users] liblinebreak and/or libunibreak Message-ID: liblinebreak's homepage at http://vimgadgets.sourceforge.net/liblinebreak/ says: Deprecation Notice: Liblinebreak has been superseded by libunibreak ...and we already have a build for libunibreak. I grepped the .info files, and nothing lists liblinebreak as a dependency. Unfortunately, liblinebreak and libunibreak conflict: they both install /usr/include/linebreak.h and /usr/include/linebreakdef.h, with different contents. Easiest solution here would be to remove liblinebreak. If that's not desired, the 2nd easiest solution would be to add text to the READMEs for liblinebreak and libunibreak stating that they conflict with each other. The 'proper' solution would be to modify one or both builds so they don't conflict. libunibreak uses pkg-config, so its includes could be moved to e.g. /usr/include/libunibreak and its .pc file modified to point there. Only one SBo build (fbreader) depends on libunibreak, so testing the modified build wouldn't be a lot of work. From dickson.tim at googlemail.com Tue Oct 30 16:55:59 2018 From: dickson.tim at googlemail.com (Tim Dickson) Date: Tue, 30 Oct 2018 16:55:59 +0000 Subject: [Slackbuilds-users] six and python3-six In-Reply-To: References: Message-ID: <01eb2908-426d-e4c3-9855-c99f0a4335a9@googlemail.com> On 29/10/2018 12:44, Rich Shepard wrote: > On Mon, 29 Oct 2018, B Watson wrote: > >> Do we need separate six and python3-six builds? > >> Right now, six will build & install python3 support if python3 is >> installed on the build box. python3-six is identical, except (a) it >> requires python3 in the .info file and (b) it builds only the python3 >> stuff. > > ? I'm a Python end-user and support the idea of having one build that > supports both Python2 and Python3. All my new code is Python3 but many > applications remain bound to Python2. It will take a while for everyone to > migrate to Python3. > > 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/ > > six is a special case, as it is provides compatibility for scripts running different versions of python. It is useful to be able to create 2 separate packages though, a python2 version, and a python3 version (with different package names), because you can have both installed at the same time. It would be hard to do that with only one package with options, unless the options changed the package name - which would then make it harder to manage with tools. Tim From rshepard at appl-ecosys.com Tue Oct 30 17:04:32 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 30 Oct 2018 10:04:32 -0700 (PDT) Subject: [Slackbuilds-users] six and python3-six In-Reply-To: <01eb2908-426d-e4c3-9855-c99f0a4335a9@googlemail.com> References: <01eb2908-426d-e4c3-9855-c99f0a4335a9@googlemail.com> Message-ID: On Tue, 30 Oct 2018, Tim Dickson via SlackBuilds-users wrote: > six is a special case, as it is provides compatibility for scripts running > different versions of python. It is useful to be able to create 2 separate > packages though, a python2 version, and a python3 version (with different > package names), because you can have both installed at the same time. It > would be hard to do that with only one package with options, unless the > options changed the package name - which would then make it harder to > manage with tools. Tim, Yes. I forgot that six is different from other python tools. Regards, Rich From falsetti at clansco.org Tue Oct 30 17:30:48 2018 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Tue, 30 Oct 2018 18:30:48 +0100 Subject: [Slackbuilds-users] qgis3.4 and python3-sip Message-ID: <20181030183048.7200fec245ef897693f703ad@clansco.org> Hi, I have qgis3-3.0.0-i586-1_SBo, slackware 14.2 I try to upgrade to qgis 3.4 https://github.com/bosth/qgis3-slackbuild build fails at QScintilla-qt5 step g++ -Wl,-O1 -shared -o libqscintillaplugin.so qscintillaplugin.o moc_qscintillaplugin.o -L/tmp/SBo/package-QScintilla-qt5/usr/lib -L/usr/lib -lqscintilla2_qt5 -lQt5Designer -lQt5PrintSupport -lQt5Widgets -lQt5Gui -lQt5Xml -lQt5Core -lGL -lpthread /usr/bin/qmake-qt5 -install qinstall -exe libqscintillaplugin.so /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillaplugin.so strip --strip-unneeded /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillaplugin.so /tmp/SBo/QScintilla_gpl-2.10.2 Usage: python configure.py [options] configure.py: error: '/usr/bin/sip3' is not an executable From matteo.bernardini at gmail.com Tue Oct 30 17:34:19 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 30 Oct 2018 18:34:19 +0100 Subject: [Slackbuilds-users] qgis3.4 and python3-sip In-Reply-To: <20181030183048.7200fec245ef897693f703ad@clansco.org> References: <20181030183048.7200fec245ef897693f703ad@clansco.org> Message-ID: Il giorno mar 30 ott 2018 alle ore 18:31 Fr?d?ric Falsetti ha scritto: > > Hi, > I have qgis3-3.0.0-i586-1_SBo, slackware 14.2 > I try to upgrade to qgis 3.4 https://github.com/bosth/qgis3-slackbuild > build fails at QScintilla-qt5 step > > g++ -Wl,-O1 -shared -o libqscintillaplugin.so qscintillaplugin.o moc_qscintillaplugin.o -L/tmp/SBo/package-QScintilla-qt5/usr/lib -L/usr/lib -lqscintilla2_qt5 -lQt5Designer -lQt5PrintSupport -lQt5Widgets -lQt5Gui -lQt5Xml -lQt5Core -lGL -lpthread > /usr/bin/qmake-qt5 -install qinstall -exe libqscintillaplugin.so /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillaplugin.so > strip --strip-unneeded /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillaplugin.so > /tmp/SBo/QScintilla_gpl-2.10.2 > Usage: python configure.py [options] > > configure.py: error: '/usr/bin/sip3' is not an executable Hi Fr?d?ric, in the repository you linked I read this in the README.md: "Instructions to build QGIS 3.x on Slackware current." From slackbuilds at jaxartes.net Tue Oct 30 17:49:45 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Tue, 30 Oct 2018 10:49:45 -0700 Subject: [Slackbuilds-users] qgis3.4 and python3-sip In-Reply-To: References: <20181030183048.7200fec245ef897693f703ad@clansco.org> Message-ID: On 2018-10-30 10:34 a.m., Matteo Bernardini wrote: > Il giorno mar 30 ott 2018 alle ore 18:31 Fr?d?ric Falsetti > ha scritto: >> >> Hi, >> I have qgis3-3.0.0-i586-1_SBo, slackware 14.2 >> I try to upgrade to qgis 3.4 https://github.com/bosth/qgis3-slackbuild >> build fails at QScintilla-qt5 step >> >> g++ -Wl,-O1 -shared -o libqscintillaplugin.so qscintillaplugin.o moc_qscintillaplugin.o -L/tmp/SBo/package-QScintilla-qt5/usr/lib -L/usr/lib -lqscintilla2_qt5 -lQt5Designer -lQt5PrintSupport -lQt5Widgets -lQt5Gui -lQt5Xml -lQt5Core -lGL -lpthread >> /usr/bin/qmake-qt5 -install qinstall -exe libqscintillaplugin.so /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillaplugin.so >> strip --strip-unneeded /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillaplugin.so >> /tmp/SBo/QScintilla_gpl-2.10.2 >> Usage: python configure.py [options] >> >> configure.py: error: '/usr/bin/sip3' is not an executable > > Hi Fr?d?ric, > > in the repository you linked I read this in the README.md: > "Instructions to build QGIS 3.x on Slackware current There's a separate README for 14.2: https://github.com/bosth/qgis3-slackbuild/blob/master/README-14.2.md They key point is to rename the sip executable in a couple of places. Also note that I haven't updated the README for the new qt SlackBuild! Ben From pprkut at liwjatan.at Tue Oct 30 17:57:03 2018 From: pprkut at liwjatan.at (Heinz Wiesinger) Date: Tue, 30 Oct 2018 18:57:03 +0100 Subject: [Slackbuilds-users] six and python3-six In-Reply-To: <01eb2908-426d-e4c3-9855-c99f0a4335a9@googlemail.com> References: <01eb2908-426d-e4c3-9855-c99f0a4335a9@googlemail.com> Message-ID: <1659493.vzhgsjPgov@titania.liwjatan.org> On Tuesday, 30 October 2018 17:55:59 CET Tim Dickson via SlackBuilds-users wrote: > On 29/10/2018 12:44, Rich Shepard wrote: > > On Mon, 29 Oct 2018, B Watson wrote: > >> Do we need separate six and python3-six builds? > >> > >> Right now, six will build & install python3 support if python3 is > >> installed on the build box. python3-six is identical, except (a) it > >> requires python3 in the .info file and (b) it builds only the python3 > >> stuff. > > > > I'm a Python end-user and support the idea of having one build that > > supports both Python2 and Python3. All my new code is Python3 but many > > applications remain bound to Python2. It will take a while for everyone to > > migrate to Python3. > > > > 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/ > > six is a special case, as it is provides compatibility for scripts > running different versions of python. > It is useful to be able to create 2 separate packages though, a python2 > version, and a python3 version (with different package names), because > you can have both installed at the same time. It would be hard to do > that with only one package with options, unless the options changed the > package name - which would then make it harder to manage with tools. We have both python2 and python3 versions of six in a single package in - current and it works just fine. I don't see why the package would need to be treated differently from other python libs. What am I missing here? Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part. URL: From slackbuilds at jaxartes.net Tue Oct 30 17:59:44 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Tue, 30 Oct 2018 10:59:44 -0700 Subject: [Slackbuilds-users] six and python3-six In-Reply-To: <1659493.vzhgsjPgov@titania.liwjatan.org> References: <01eb2908-426d-e4c3-9855-c99f0a4335a9@googlemail.com> <1659493.vzhgsjPgov@titania.liwjatan.org> Message-ID: <10c805d5-e455-c0b4-d4d5-0eaa469b5298@jaxartes.net> On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote: > > We have both python2 and python3 versions of six in a single package in - > current and it works just fine. I don't see why the package would need to be > treated differently from other python libs. What am I missing here? > > Grs, > Heinz I don't think you are missing anything. As long as the *version* of a Python module is the same for Python 2 and Python 3, then it makes sense to have them in a single package or SlackBuild. As I mentioned in my other email, there are rare cases where this isn't possible: IPython won't go above 5.x for Python 2 but is on 7.x for Python 3. Otherwise, keeping them together is usually the way to go. Ben From falsetti at clansco.org Tue Oct 30 19:15:28 2018 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Tue, 30 Oct 2018 20:15:28 +0100 Subject: [Slackbuilds-users] six and python3-six In-Reply-To: <10c805d5-e455-c0b4-d4d5-0eaa469b5298@jaxartes.net> References: <01eb2908-426d-e4c3-9855-c99f0a4335a9@googlemail.com> <1659493.vzhgsjPgov@titania.liwjatan.org> <10c805d5-e455-c0b4-d4d5-0eaa469b5298@jaxartes.net> Message-ID: <20181030201528.0dbcd97e9064858d2e28ea86@clansco.org> oups, sorry, thanks Matteo and Ben On Tue, 30 Oct 2018 10:59:44 -0700 Benjamin Trigona-Harany wrote: > On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote: > > > > We have both python2 and python3 versions of six in a single package in - > > current and it works just fine. I don't see why the package would need to be > > treated differently from other python libs. What am I missing here? > > > > Grs, > > Heinz > > I don't think you are missing anything. As long as the *version* of a > Python module is the same for Python 2 and Python 3, then it makes sense > to have them in a single package or SlackBuild. As I mentioned in my > other email, there are rare cases where this isn't possible: IPython > won't go above 5.x for Python 2 but is on 7.x for Python 3. > > Otherwise, keeping them together is usually the way to go. > > Ben > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From brent at exitstatusone.com Wed Oct 31 02:55:48 2018 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 30 Oct 2018 20:55:48 -0600 Subject: [Slackbuilds-users] SocksiPy removal Message-ID: Admins, I think it is time to remove SocksiPy. It has many problems, including a collision with the PySocks slackbuild. PySocks is an updated fork of SocksiPy. Any users can install PySocks if you need the same or similar functionality. Additionally, Python already ships with a socks module if PySocks is not desirable. I suggest that the PySocks README be updated with a link to the SocksiPy source forge page. That way users are not confused by the removal and the fact that SocksiPy is a keyword for PySocks. The home page is: https://sourceforge.net/projects/socksipy/ Thanks, Brenton From dickson.tim at googlemail.com Wed Oct 31 09:54:20 2018 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 31 Oct 2018 09:54:20 +0000 Subject: [Slackbuilds-users] six and python3-six In-Reply-To: <10c805d5-e455-c0b4-d4d5-0eaa469b5298@jaxartes.net> References: <01eb2908-426d-e4c3-9855-c99f0a4335a9@googlemail.com> <1659493.vzhgsjPgov@titania.liwjatan.org> <10c805d5-e455-c0b4-d4d5-0eaa469b5298@jaxartes.net> Message-ID: On 30/10/2018 17:59, Benjamin Trigona-Harany wrote: > On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote: >> >> We have both python2 and python3 versions of six in a single package >> in - >> current and it works just fine. I don't see why the package would >> need to be >> treated differently from other python libs. What am I missing here? >> >> Grs, >> Heinz > > I don't think you are missing anything. As long as the *version* of a > Python module is the same for Python 2 and Python 3, then it makes > sense to have them in a single package or SlackBuild. As I mentioned > in my other email, there are rare cases where this isn't possible: > IPython won't go above 5.x for Python 2 but is on 7.x for Python 3. > > Otherwise, keeping them together is usually the way to go. > > Ben > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > there seems to be a variation? of support in the python scripts. Having the script produce both pthon2 and python3 files would be useful. I am in the process of updating thonny ( a python ide) which has new deps, and pyserial is an example where it only does python2. Repeating the python setup.py install --root=$PKG in the slackbuild but changing python to python3 fixes that, but I created a separate slackbuild,(not yet submitted) because most of the python packages I have seen so fave have two separate packages, a pkgname and a python3-pkgname. Should I make new python packages create both sets of files, or create separate python2 and python3 packages ? (i'm working on mypy and mypy_extensions at the moment) regards, Tim From dave at dawoodfall.net Wed Oct 31 10:01:14 2018 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 31 Oct 2018 10:01:14 +0000 Subject: [Slackbuilds-users] six and python3-six In-Reply-To: References: <01eb2908-426d-e4c3-9855-c99f0a4335a9@googlemail.com> <1659493.vzhgsjPgov@titania.liwjatan.org> <10c805d5-e455-c0b4-d4d5-0eaa469b5298@jaxartes.net> Message-ID: <20181031100114.GA22119@blackswan.r0t.uk> On Wednesday 31 October 2018 09:54, Slackbuilds Users put forth the proposition: > On 30/10/2018 17:59, Benjamin Trigona-Harany wrote: > > On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote: > > > > > > We have both python2 and python3 versions of six in a single package in - > > > current and it works just fine. I don't see why the package would need to be > > > treated differently from other python libs. What am I missing here? > > > > > > Grs, > > > Heinz > > > > I don't think you are missing anything. As long as the *version* of a Python module is the same for > > Python 2 and Python 3, then it makes sense to have them in a single package or SlackBuild. As I > > mentioned in my other email, there are rare cases where this isn't possible: IPython won't go above 5.x > > for Python 2 but is on 7.x for Python 3. > > > > Otherwise, keeping them together is usually the way to go. > > > > Ben > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > > there seems to be a variation? of support in the python scripts. Having the script produce both pthon2 and > python3 files would be useful. I am in the process of updating thonny ( a python ide) which has new deps, > and pyserial is an example where it only does python2. Repeating the python setup.py install --root=$PKG in > the slackbuild > but changing python to python3 fixes that, but I created a separate slackbuild,(not yet submitted) because > most of the python packages I have seen so fave have two separate packages, a pkgname and a > python3-pkgname. > > Should I make new python packages create both sets of files, or create separate python2 and python3 > packages ? > (i'm working on mypy and mypy_extensions at the moment) > regards, Tim What I did with pudb, the python debugger, is have options for building either or both, so the user can decide. If someone only wants to debug python3 code I'm not going to foist an extra load of python2 code on them. Dave -- You or I must yield up his life to Ahrimanes. I would rather it were you. I should have no hesitation in sacrificing my own life to spare yours, but we take stock next week, and it would not be fair on the company. -- J. Wellington Wells -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dickson.tim at googlemail.com Wed Oct 31 19:39:40 2018 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 31 Oct 2018 19:39:40 +0000 Subject: [Slackbuilds-users] six and python3-six In-Reply-To: <20181031100114.GA22119@blackswan.r0t.uk> References: <01eb2908-426d-e4c3-9855-c99f0a4335a9@googlemail.com> <1659493.vzhgsjPgov@titania.liwjatan.org> <10c805d5-e455-c0b4-d4d5-0eaa469b5298@jaxartes.net> <20181031100114.GA22119@blackswan.r0t.uk> Message-ID: <60cedb6a-297d-12ce-69a9-297482a5602d@googlemail.com> On 31/10/2018 10:01, David Woodfall wrote: > On Wednesday 31 October 2018 09:54, > Slackbuilds Users put forth the proposition: >> On 30/10/2018 17:59, Benjamin Trigona-Harany wrote: >>> On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote: >>>> We have both python2 and python3 versions of six in a single package in - >>>> current and it works just fine. I don't see why the package would need to be >>>> treated differently from other python libs. What am I missing here? >>>> >>>> Grs, >>>> Heinz >>> I don't think you are missing anything. As long as the *version* of a Python module is the same for >>> Python 2 and Python 3, then it makes sense to have them in a single package or SlackBuild. As I >>> mentioned in my other email, there are rare cases where this isn't possible: IPython won't go above 5.x >>> for Python 2 but is on 7.x for Python 3. >>> >>> Otherwise, keeping them together is usually the way to go. >>> >>> Ben >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ -https://slackbuilds.org/faq/ >>> >>> >> there seems to be a variation? of support in the python scripts. Having the script produce both pthon2 and >> python3 files would be useful. I am in the process of updating thonny ( a python ide) which has new deps, >> and pyserial is an example where it only does python2. Repeating the python setup.py install --root=$PKG in >> the slackbuild >> but changing python to python3 fixes that, but I created a separate slackbuild,(not yet submitted) because >> most of the python packages I have seen so fave have two separate packages, a pkgname and a >> python3-pkgname. >> >> Should I make new python packages create both sets of files, or create separate python2 and python3 >> packages ? >> (i'm working on mypy and mypy_extensions at the moment) >> regards, Tim > What I did with pudb, the python debugger, is have options for > building either or both, so the user can decide. If someone only > wants to debug python3 code I'm not going to foist an extra load of > python2 code on them. > > Dave > -- > > You or I must yield up his life to Ahrimanes. I would rather it were > you. I should have no hesitation in sacrificing my own life to spare > yours, but we take stock next week, and it would not be fair on the > company. > -- J. Wellington Wells > > _______________________________________________ > 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 dave, currently i need python3 versions of docutils, pyserial, mypy and mypy_extensions. I am happy to submit separate python3 versions, or I could request Robby Workman and Cristiano Urban update? their builds to add python3 support (for the first 2). I'm just trying to find out what the "normal" should be. That also effects documentation, because if one script generates both (python2 and 3 files) you only need one set of documentation, but if you use two build scripts, the documentation would need to be in different places to avoid loosing it if you had both installed, and just removepkg one of them. regards, Tim Regards, Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Wed Oct 31 20:08:54 2018 From: yalhcru at gmail.com (B Watson) Date: Wed, 31 Oct 2018 16:08:54 -0400 Subject: [Slackbuilds-users] six and python3-six In-Reply-To: <60cedb6a-297d-12ce-69a9-297482a5602d@googlemail.com> References: <01eb2908-426d-e4c3-9855-c99f0a4335a9@googlemail.com> <1659493.vzhgsjPgov@titania.liwjatan.org> <10c805d5-e455-c0b4-d4d5-0eaa469b5298@jaxartes.net> <20181031100114.GA22119@blackswan.r0t.uk> <60cedb6a-297d-12ce-69a9-297482a5602d@googlemail.com> Message-ID: On 10/31/18, Tim Dickson via SlackBuilds-users wrote: > documentation, but if you use two build scripts, the documentation would > need to be in different places to avoid loosing it if you had both > installed, and just removepkg one of them. That wouldn't happen. removepkg would notice the files exist in another package and it wouldn't remove them. That said, it'd be cleaner for each package to have its own set. Since 15.0 is going to ship python3, maybe combining all the and python3- builds is the way to go. No more "this requires blahblah, built with python3 support" in READMEs, you'd be able to just look at the REQUIRES and install those packages. Speaking as someone who only installs python & its modules as dependencies for apps I want to run, that would make life simpler.