From willysr at slackbuilds.org Tue Sep 1 12:32:04 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 1 Sep 2015 19:32:04 +0700 Subject: [Slackbuilds-users] network/chromium fails to build on x64 and binds with obsolete Python In-Reply-To: <20150830165440.GA2655@comp.lan> References: <20150830165440.GA2655@comp.lan> Message-ID: <55E59AC4.4010303@slackbuilds.org> > The following error occurs when building chromium on Slackware 14.1 > x64: Tested fine here SUMMARY LOG Using the SBo repository for Slackware 14.1 Queue Process: Download and build chromium: MD5SUM check for chromium-31.0.1650.57.tar.xz ... OK Building package chromium-31.0.1650.57-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: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Tue Sep 1 14:08:33 2015 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 1 Sep 2015 15:08:33 +0100 Subject: [Slackbuilds-users] network/chromium fails to build on x64 and binds with obsolete Python In-Reply-To: <55E59AC4.4010303@slackbuilds.org> References: <20150830165440.GA2655@comp.lan> <55E59AC4.4010303@slackbuilds.org> Message-ID: Here it builds fine on 14.1, but on -current it fails with exactly the error Arkadiusz reports. I'll test your fix, thanks Arkadiusz, and send it to Matteo for his repo, although I guess a new version of chromium for 14.2 would be good. Thanks -D. From larryhaja at gmail.com Wed Sep 2 05:05:12 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Tue, 1 Sep 2015 22:05:12 -0700 Subject: [Slackbuilds-users] Source download for voxelands Message-ID: Hi, The download link for voxelands has changed. On SBo: http://www.voxelands.com/downloads/voxelands-1501.00-src.tar.bz2 New link: http://www.voxelands.com/downloads/old/voxelands-1501.00-src.tar.bz2 Thanks, Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Sep 2 06:39:56 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 2 Sep 2015 13:39:56 +0700 Subject: [Slackbuilds-users] Source download for voxelands In-Reply-To: References: Message-ID: <55E699BC.9080906@slackbuilds.org> > The download link for voxelands has changed. > > On SBo: http://www.voxelands.com/downloads/voxelands-1501.00-src.tar.bz2 > New link: > http://www.voxelands.com/downloads/old/voxelands-1501.00-src.tar.bz2 Thanks Fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Wed Sep 2 13:52:30 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Sep 2015 15:52:30 +0200 Subject: [Slackbuilds-users] bashisms? In-Reply-To: References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> <20150829121646.GA12197@jdiamond-nb2> <20150829162037.GA21308@jdiamond-nb2> Message-ID: <55E6FF1E.8030801@gmail.com> Hi, Today I was writing code to execute script from C code and I'd like to share with you what I've found. It stroke me, but should otherwise be obvious. It seems that shebang has only meaning if the script is invoked directly, that is: $ ./whatever.SlackBuild or $ sh -c ./whatever.SlackBuild otherwise, shebang is nothing more than a comment... If you run your script through sh (which links to bash), it doesn't matter what the shebang is, it can be #!/bin/csh, and the script is still going to be interpreted by sh. This might be important, as sbopkg uses sh to execute the build. -- Best regards, Andrzej Telszewski From jvogel4 at stny.rr.com Wed Sep 2 14:51:24 2015 From: jvogel4 at stny.rr.com (John Vogel) Date: Wed, 2 Sep 2015 10:51:24 -0400 Subject: [Slackbuilds-users] bashisms? In-Reply-To: <55E6FF1E.8030801@gmail.com> References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> <20150829121646.GA12197@jdiamond-nb2> <20150829162037.GA21308@jdiamond-nb2> <55E6FF1E.8030801@gmail.com> Message-ID: <20150902105124.2f27b96b@stygian.lan> On Wed, 2 Sep 2015 15:52:30 +0200 Andrzej Telszewski wrote: > Hi, > > Today I was writing code to execute script from C code and I'd like to > share with you what I've found. It stroke me, but should otherwise be > obvious. > > It seems that shebang has only meaning if the script is invoked > directly, that is: > $ ./whatever.SlackBuild > or > $ sh -c ./whatever.SlackBuild > > otherwise, shebang is nothing more than a comment... > > If you run your script through sh (which links to bash), it doesn't > matter what the shebang is, it can be #!/bin/csh, and the script is > still going to be interpreted by sh. > > This might be important, as sbopkg uses sh to execute the build. > > -- > Best regards, > Andrzej Telszewski Are you sure? I tried to test this using the following script (executable bit is set): -- start ./test_script #!/bin/bash printf '$0=%s\n' "$0" printf 'BASH_VERSION=%s' "$BASH_VERSION" -- end ./test_script When run by all the shells I have (ash,bash,dash,ksh,mksh,tcsh), they all output the same. I used the following loop to run the commands: for s in ash bash dash ksh mksh tcsh sh csh ; do /bin/$s -c ./test_script done The output for each is identical: $0=./test_script BASH_VERSION=4.3.39(1)-release But if I change the shebang line to '#!/bin/dash', then the output for all is: $0=./test_script BASH_VERSION= At the time of running this /bin/sh -> /bin/bash. Changing /bin/sh to point anything else (other than tcsh/csh, I never set /bin/sh to a c shell) did not change the results. I'm sure I could carry this testing further, but I think the point might be proved well enough. I didn't want to step into this discussion, as I have rather conservative opinion about proper use of shebang and would rather not go down this road here. But let's keep things accurate, as far as how things actually work. John From atelszewski at gmail.com Wed Sep 2 15:09:45 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Sep 2015 17:09:45 +0200 Subject: [Slackbuilds-users] bashisms? In-Reply-To: <20150902105124.2f27b96b@stygian.lan> References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> <20150829121646.GA12197@jdiamond-nb2> <20150829162037.GA21308@jdiamond-nb2> <55E6FF1E.8030801@gmail.com> <20150902105124.2f27b96b@stygian.lan> Message-ID: <55E71139.8030807@gmail.com> On 02/09/15 16:51, John Vogel wrote: > On Wed, 2 Sep 2015 15:52:30 +0200 > Andrzej Telszewski wrote: > >> Hi, >> >> Today I was writing code to execute script from C code and I'd like to >> share with you what I've found. It stroke me, but should otherwise be >> obvious. >> >> It seems that shebang has only meaning if the script is invoked >> directly, that is: >> $ ./whatever.SlackBuild >> or >> $ sh -c ./whatever.SlackBuild >> >> otherwise, shebang is nothing more than a comment... >> >> If you run your script through sh (which links to bash), it doesn't >> matter what the shebang is, it can be #!/bin/csh, and the script is >> still going to be interpreted by sh. >> >> This might be important, as sbopkg uses sh to execute the build. >> >> -- >> Best regards, >> Andrzej Telszewski > > Are you sure? I tried to test this using the following script > (executable bit is set): > Yes, I'm sure;) > -- start ./test_script > #!/bin/bash > printf '$0=%s\n' "$0" > printf 'BASH_VERSION=%s' "$BASH_VERSION" > -- end ./test_script > > When run by all the shells I have (ash,bash,dash,ksh,mksh,tcsh), > they all output the same. I used the following loop to run > the commands: > > for s in ash bash dash ksh mksh tcsh sh csh ; do > /bin/$s -c ./test_script > done That's it. If you use -c switch, then the script is executed as if you used ./, that is, the shebang is processed. Try running your test without the -c switch and placing some constructs that are only understood by one of the shells. $ sh -c ./whatever.SalckBuild is equivalent to: $ ./whatever.SalckBuild but $ sh ./whatever.SalckBuild will process the script by whichever shell is linked to the sh, without taking into account the shebang (maybe there are shells, that upon seeing shebang in the first line don't treat it as comment, but I don't know about it). > > The output for each is identical: > $0=./test_script > BASH_VERSION=4.3.39(1)-release > > But if I change the shebang line to '#!/bin/dash', then the > output for all is: > $0=./test_script > BASH_VERSION= > > At the time of running this /bin/sh -> /bin/bash. Changing > /bin/sh to point anything else (other than tcsh/csh, I never > set /bin/sh to a c shell) did not change the results. > > I'm sure I could carry this testing further, but I think > the point might be proved well enough. I didn't want to > step into this discussion, as I have rather conservative > opinion about proper use of shebang and would rather not > go down this road here. But let's keep things accurate, > as far as how things actually work. > > John > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Best regards, Andrzej Telszewski From jvogel4 at stny.rr.com Wed Sep 2 15:13:27 2015 From: jvogel4 at stny.rr.com (John Vogel) Date: Wed, 2 Sep 2015 11:13:27 -0400 Subject: [Slackbuilds-users] bashisms? In-Reply-To: <55E71139.8030807@gmail.com> References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> <20150829121646.GA12197@jdiamond-nb2> <20150829162037.GA21308@jdiamond-nb2> <55E6FF1E.8030801@gmail.com> <20150902105124.2f27b96b@stygian.lan> <55E71139.8030807@gmail.com> Message-ID: <20150902111327.53872fd2@stygian.lan> On Wed, 2 Sep 2015 17:09:45 +0200 Andrzej Telszewski wrote: > On 02/09/15 16:51, John Vogel wrote: > > On Wed, 2 Sep 2015 15:52:30 +0200 > > Andrzej Telszewski wrote: > > > >> Hi, > >> > >> Today I was writing code to execute script from C code and I'd like to > >> share with you what I've found. It stroke me, but should otherwise be > >> obvious. > >> > >> It seems that shebang has only meaning if the script is invoked > >> directly, that is: > >> $ ./whatever.SlackBuild > >> or > >> $ sh -c ./whatever.SlackBuild > >> > >> otherwise, shebang is nothing more than a comment... > >> > >> If you run your script through sh (which links to bash), it doesn't > >> matter what the shebang is, it can be #!/bin/csh, and the script is > >> still going to be interpreted by sh. > >> > >> This might be important, as sbopkg uses sh to execute the build. > >> > >> -- > >> Best regards, > >> Andrzej Telszewski > > > > Are you sure? I tried to test this using the following script > > (executable bit is set): > > > > Yes, I'm sure;) > > > -- start ./test_script > > #!/bin/bash > > printf '$0=%s\n' "$0" > > printf 'BASH_VERSION=%s' "$BASH_VERSION" > > -- end ./test_script > > > > When run by all the shells I have (ash,bash,dash,ksh,mksh,tcsh), > > they all output the same. I used the following loop to run > > the commands: > > > > for s in ash bash dash ksh mksh tcsh sh csh ; do > > /bin/$s -c ./test_script > > done > > That's it. If you use -c switch, then the script is executed as if you > used ./, that is, the shebang is processed. Try running your test > without the -c switch and placing some constructs that are only > understood by one of the shells. > > $ sh -c ./whatever.SalckBuild > is equivalent to: > $ ./whatever.SalckBuild > > but > > $ sh ./whatever.SalckBuild > will process the script by whichever shell is linked to the sh, without > taking into account the shebang (maybe there are shells, that upon > seeing shebang in the first line don't treat it as comment, but I don't > know about it). > > > > > The output for each is identical: > > $0=./test_script > > BASH_VERSION=4.3.39(1)-release > > > > But if I change the shebang line to '#!/bin/dash', then the > > output for all is: > > $0=./test_script > > BASH_VERSION= > > > > At the time of running this /bin/sh -> /bin/bash. Changing > > /bin/sh to point anything else (other than tcsh/csh, I never > > set /bin/sh to a c shell) did not change the results. > > > > I'm sure I could carry this testing further, but I think > > the point might be proved well enough. I didn't want to > > step into this discussion, as I have rather conservative > > opinion about proper use of shebang and would rather not > > go down this road here. But let's keep things accurate, > > as far as how things actually work. > > > > John > -- > Best regards, > Andrzej Telszewski Yes, indeed. Fair enough. I think I misread your first post wrong to mean the opposite. My apologies if I came off a bit harsh. You make a good point. Cheers, John From atelszewski at gmail.com Wed Sep 2 15:27:45 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Sep 2015 17:27:45 +0200 Subject: [Slackbuilds-users] bashisms? In-Reply-To: <20150902111327.53872fd2@stygian.lan> References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> <20150829121646.GA12197@jdiamond-nb2> <20150829162037.GA21308@jdiamond-nb2> <55E6FF1E.8030801@gmail.com> <20150902105124.2f27b96b@stygian.lan> <55E71139.8030807@gmail.com> <20150902111327.53872fd2@stygian.lan> Message-ID: <55E71571.8080705@gmail.com> On 02/09/15 17:13, John Vogel wrote: > On Wed, 2 Sep 2015 17:09:45 +0200 > Andrzej Telszewski wrote: > >> On 02/09/15 16:51, John Vogel wrote: >>> On Wed, 2 Sep 2015 15:52:30 +0200 >>> Andrzej Telszewski wrote: >>> >>>> Hi, >>>> >>>> Today I was writing code to execute script from C code and I'd like to >>>> share with you what I've found. It stroke me, but should otherwise be >>>> obvious. >>>> >>>> It seems that shebang has only meaning if the script is invoked >>>> directly, that is: >>>> $ ./whatever.SlackBuild >>>> or >>>> $ sh -c ./whatever.SlackBuild >>>> >>>> otherwise, shebang is nothing more than a comment... >>>> >>>> If you run your script through sh (which links to bash), it doesn't >>>> matter what the shebang is, it can be #!/bin/csh, and the script is >>>> still going to be interpreted by sh. >>>> >>>> This might be important, as sbopkg uses sh to execute the build. >>>> >>>> -- >>>> Best regards, >>>> Andrzej Telszewski >>> >>> Are you sure? I tried to test this using the following script >>> (executable bit is set): >>> >> >> Yes, I'm sure;) >> >>> -- start ./test_script >>> #!/bin/bash >>> printf '$0=%s\n' "$0" >>> printf 'BASH_VERSION=%s' "$BASH_VERSION" >>> -- end ./test_script >>> >>> When run by all the shells I have (ash,bash,dash,ksh,mksh,tcsh), >>> they all output the same. I used the following loop to run >>> the commands: >>> >>> for s in ash bash dash ksh mksh tcsh sh csh ; do >>> /bin/$s -c ./test_script >>> done >> >> That's it. If you use -c switch, then the script is executed as if you >> used ./, that is, the shebang is processed. Try running your test >> without the -c switch and placing some constructs that are only >> understood by one of the shells. >> >> $ sh -c ./whatever.SalckBuild >> is equivalent to: >> $ ./whatever.SalckBuild >> >> but >> >> $ sh ./whatever.SalckBuild >> will process the script by whichever shell is linked to the sh, without >> taking into account the shebang (maybe there are shells, that upon >> seeing shebang in the first line don't treat it as comment, but I don't >> know about it). >> >>> >>> The output for each is identical: >>> $0=./test_script >>> BASH_VERSION=4.3.39(1)-release >>> >>> But if I change the shebang line to '#!/bin/dash', then the >>> output for all is: >>> $0=./test_script >>> BASH_VERSION= >>> >>> At the time of running this /bin/sh -> /bin/bash. Changing >>> /bin/sh to point anything else (other than tcsh/csh, I never >>> set /bin/sh to a c shell) did not change the results. >>> >>> I'm sure I could carry this testing further, but I think >>> the point might be proved well enough. I didn't want to >>> step into this discussion, as I have rather conservative >>> opinion about proper use of shebang and would rather not >>> go down this road here. But let's keep things accurate, >>> as far as how things actually work. >>> >>> John > >> -- >> Best regards, >> Andrzej Telszewski > > Yes, indeed. Fair enough. I think I misread your first post > wrong to mean the opposite. My apologies if I came off a bit > harsh. You make a good point. Well, I re-read my post and it should be me who should be sorry as I didn't explain it well enough;) I was very harsh;) > > Cheers, > John > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From yalhcru at gmail.com Wed Sep 2 17:40:01 2015 From: yalhcru at gmail.com (B Watson) Date: Wed, 2 Sep 2015 13:40:01 -0400 Subject: [Slackbuilds-users] bashisms? In-Reply-To: <55E71139.8030807@gmail.com> References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> <20150829121646.GA12197@jdiamond-nb2> <20150829162037.GA21308@jdiamond-nb2> <55E6FF1E.8030801@gmail.com> <20150902105124.2f27b96b@stygian.lan> <55E71139.8030807@gmail.com> Message-ID: On 9/2/15, Andrzej Telszewski wrote: > taking into account the shebang (maybe there are shells, that upon > seeing shebang in the first line don't treat it as comment, but I don't > know about it). It's not a shell, but perl does this: $ cat 1.sh #!/bin/sh echo "Hello world" $ perl 1.sh Hello world $ sed -i '1c#!/usr/bin/perl' 1.sh $ cat 1.sh #!/usr/bin/perl echo "Hello world" $ perl 1.sh String found where operator expected at 1.sh line 2, near "echo "Hello world"" (Do you need to predeclare echo?) syntax error at 1.sh line 2, near "echo "Hello world"" Execution of 1.sh aborted due to compilation errors. ...not that that has anything to do with the original topic... From yavor at atanasov.us Fri Sep 4 19:44:43 2015 From: yavor at atanasov.us (Yavor Atanasov) Date: Fri, 04 Sep 2015 15:44:43 -0400 Subject: [Slackbuilds-users] Ladspa problem Message-ID: <20150904224446.ijNi4Nsq@smtp3h.mail.yandex.net> Hello guys I trying to install ladspa and getting the next error: "Unable to download/verify source file(s) for ladspa_sdk: md5sum failure for /usr/sbo/distfiles/ladspa_sdk_1.13.tgz." From hostmaster at slackonly.com Fri Sep 4 19:52:07 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Fri, 4 Sep 2015 22:52:07 +0300 Subject: [Slackbuilds-users] Ladspa problem In-Reply-To: <20150904224446.ijNi4Nsq@smtp3h.mail.yandex.net> References: <20150904224446.ijNi4Nsq@smtp3h.mail.yandex.net> Message-ID: <55E9F667.8000908@slackonly.com> On 09/04/2015 10:44 PM, Yavor Atanasov wrote: > Hello guys I trying to install ladspa and getting the next error: > > "Unable to download/verify source file(s) for ladspa_sdk: > md5sum failure for /usr/sbo/distfiles/ladspa_sdk_1.13.tgz." > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > Hi seems ladspa.org is down... Here is a alternative source: http://pkgs.fedoraproject.org/repo/pkgs/ladspa/ladspa_sdk_1.13.tgz/671be3e1021d0722cadc7fb27054628e/ladspa_sdk_1.13.tgz (md5sum match) From hostmaster at slackonly.com Fri Sep 4 20:09:30 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Fri, 4 Sep 2015 23:09:30 +0300 Subject: [Slackbuilds-users] owncloud-client Message-ID: <55E9FA7A.3050005@slackonly.com> Hi! owncloud-client failed to build here is the log from sbopkg: -- Installing: /tmp/SBo/package-owncloud-client/usr/share/nautilus-python/extensions/syncstate.py rmdir: failed to remove '/tmp/SBo/package-owncloud-client/usr/man': No such file or directory owncloud-client: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. (Y)es to continue, (N)o to abort, (R)etry the build?: n seems there is no $PKG/usr/man so after comment out: rmdir $PKG/usr/man sbopkg is able to build owncloud-client successfully... From larryhaja at gmail.com Fri Sep 4 22:22:42 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Fri, 4 Sep 2015 15:22:42 -0700 Subject: [Slackbuilds-users] owncloud-client In-Reply-To: <55E9FA7A.3050005@slackonly.com> References: <55E9FA7A.3050005@slackonly.com> Message-ID: I turns out if you just have the minimum dependencies installed (ie. qtkeychain) then you'll get the error that $PKG/usr/man doesn't exist. The following message during cmake step is seen when Sphinx isn't installed. -- Could NOT find Sphinx (missing: SPHINX_EXECUTABLE) Sphinx is used to create the documentation. However if Sphinx is installed and documentation isn't generated then $PKG/usr/man exists as an empty directory. I've created a diff of the owncloud-client.SlackBuild that will accommodate if Sphinx is installed or not. This patch also works on the new owncloud-client version 2.0.1. Thanks, Larry On Fri, Sep 4, 2015 at 1:09 PM, Panagiotis Nikolaou < hostmaster at slackonly.com> wrote: > Hi! > owncloud-client failed to build here is the log from sbopkg: > > -- Installing: > > /tmp/SBo/package-owncloud-client/usr/share/nautilus-python/extensions/syncstate.py > rmdir: failed to remove '/tmp/SBo/package-owncloud-client/usr/man': No > such file or directory > > owncloud-client: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. > > (Y)es to continue, (N)o to abort, (R)etry the build?: n > > seems there is no $PKG/usr/man so after comment out: > rmdir $PKG/usr/man > sbopkg is able to build owncloud-client successfully... > > > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- --- owncloud-client.SlackBuild.orig 2015-09-04 22:06:27.900243680 +0000 +++ owncloud-client.SlackBuild 2015-09-04 21:57:17.002226072 +0000 @@ -24,7 +24,7 @@ PRGNAM=owncloud-client VERSION=${VERSION:-1.8.4} -BUILD=${BUILD:-1} +BUILD=${BUILD:-2} TAG=${TAG:-_SBo} SRCNAM=owncloudclient @@ -83,6 +83,7 @@ -DCMAKE_BUILD_TYPE="Release" \ .. make VERBOSE=1 + make doc make install DESTDIR=$PKG cd .. @@ -95,7 +96,7 @@ $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild -rmdir $PKG/usr/man +[ -d "$PKG/usr/man" ] && find $PKG/usr/man -type f -exec gzip -9 '{}' \; mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc From willysr at slackbuilds.org Fri Sep 4 23:25:51 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Sep 2015 06:25:51 +0700 Subject: [Slackbuilds-users] owncloud-client In-Reply-To: References: <55E9FA7A.3050005@slackonly.com> Message-ID: <55EA287F.5050707@slackbuilds.org> > I turns out if you just have the minimum dependencies installed (ie. > qtkeychain) then you'll get the error that $PKG/usr/man doesn't exist. The > following message during cmake step is seen when Sphinx isn't installed. > > -- Could NOT find Sphinx (missing: SPHINX_EXECUTABLE) > > Sphinx is used to create the documentation. However if Sphinx is installed > and documentation isn't generated then $PKG/usr/man exists as an empty > directory. I've created a diff of the owncloud-client.SlackBuild that will > accommodate if Sphinx is installed or not. This patch also works on the > new owncloud-client version 2.0.1. Applied in the owncloud-client update 2.0.0 in my branch Thanks Larry -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kris240376 at gmail.com Fri Sep 4 23:55:33 2015 From: kris240376 at gmail.com (Christopher Walker) Date: Fri, 4 Sep 2015 18:55:33 -0500 Subject: [Slackbuilds-users] owncloud-client In-Reply-To: <55EA287F.5050707@slackbuilds.org> References: <55E9FA7A.3050005@slackonly.com> <55EA287F.5050707@slackbuilds.org> Message-ID: Thanks, I've been trying to track this down but haven't had too much time. Thanks for the heads up. I've already submitted an update for version 2.0.0 so can't fix this until it's flushed from the update queue. If you can send me the patch I'll make sure to incorporate it for the 2.0.1 update. On Fri, Sep 4, 2015 at 6:25 PM, Willy Sudiarto Raharjo wrote: >> I turns out if you just have the minimum dependencies installed (ie. >> qtkeychain) then you'll get the error that $PKG/usr/man doesn't exist. The >> following message during cmake step is seen when Sphinx isn't installed. >> >> -- Could NOT find Sphinx (missing: SPHINX_EXECUTABLE) >> >> Sphinx is used to create the documentation. However if Sphinx is installed >> and documentation isn't generated then $PKG/usr/man exists as an empty >> directory. I've created a diff of the owncloud-client.SlackBuild that will >> accommodate if Sphinx is installed or not. This patch also works on the >> new owncloud-client version 2.0.1. > > Applied in the owncloud-client update 2.0.0 in my branch > > Thanks Larry > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From kris240376 at gmail.com Sat Sep 5 00:01:59 2015 From: kris240376 at gmail.com (Christopher Walker) Date: Fri, 4 Sep 2015 19:01:59 -0500 Subject: [Slackbuilds-users] owncloud-client In-Reply-To: References: <55E9FA7A.3050005@slackonly.com> <55EA287F.5050707@slackbuilds.org> Message-ID: Ah, disregard my last message. Didn't bother to look at your e-mail addresses before clicking send. On Fri, Sep 4, 2015 at 6:55 PM, Christopher Walker wrote: > Thanks, I've been trying to track this down but haven't had too much > time. Thanks for the heads up. I've already submitted an update for > version 2.0.0 so can't fix this until it's flushed from the update > queue. If you can send me the patch I'll make sure to incorporate it > for the 2.0.1 update. > > On Fri, Sep 4, 2015 at 6:25 PM, Willy Sudiarto Raharjo > wrote: >>> I turns out if you just have the minimum dependencies installed (ie. >>> qtkeychain) then you'll get the error that $PKG/usr/man doesn't exist. The >>> following message during cmake step is seen when Sphinx isn't installed. >>> >>> -- Could NOT find Sphinx (missing: SPHINX_EXECUTABLE) >>> >>> Sphinx is used to create the documentation. However if Sphinx is installed >>> and documentation isn't generated then $PKG/usr/man exists as an empty >>> directory. I've created a diff of the owncloud-client.SlackBuild that will >>> accommodate if Sphinx is installed or not. This patch also works on the >>> new owncloud-client version 2.0.1. >> >> Applied in the owncloud-client update 2.0.0 in my branch >> >> Thanks Larry >> >> >> -- >> Willy Sudiarto Raharjo >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> From willysr at slackbuilds.org Sat Sep 5 12:21:12 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Sep 2015 19:21:12 +0700 Subject: [Slackbuilds-users] Updates - 20150905.1 Message-ID: <55EADE38.8060309@slackbuilds.org> Sat Sep 5 12:08:56 UTC 2015 academic/fet: Updated for version 5.27.8. academic/suitesparse: Update DOWNLOAD url. academic/sword-data-kjv: Updated for version 1.7.4. academic/xiphos: Updated for version 4.0.4. audio/ladspa_sdk: Fix DOWNLOAD url. desktop/lumina: Updated for version 0.8.6. desktop/luna-wallpapers: Add more wallpapers. development/J-Link: Added (software and documentation for J-Link). development/bas55: Updated for version 1.03. development/byacc: Updated for version 20150711. development/pycharm: Updated for version 4.5.4. development/textadept: Updated for version 8.2. development/zeal: Update script and README. games/freeciv: Updated for version 2.5.1. games/freeminer: Updated for version 0.4.13.7. games/freeorion: Updated for version 0.4.5_rc3 games/frotz: Updated for version 2.44. games/instead: Updated for version 2.2.5. games/openttd: Updated for version 1.5.2. games/pinball: Added (open source pinball simulator). games/triplea: Updated for version 1.8.0.9. games/voxelands: Update DOWNLOAD url. graphics/digikam: Patched against opencv 3.0.0. libraries/CGAL: Updated for version 4.6.2. libraries/exiftool: Updated for version 10.00. libraries/gtkhotkey: Added (hotkey handling for Gtk+ applications). libraries/jreen: Added (Asynchronious Jabber library). libraries/libpwquality: Added (password quality checking). libraries/libuv: Updated for version 1.7.3. libraries/libvirt-glib: Updated for version 0.2.2. libraries/libvirt-python: Updated for version 1.2.19. libraries/libvirt: Updated for version 1.2.19. libraries/msgpack-c: Updated for version 1.2.0. libraries/opencv: Updated for version 3.0.0. libraries/trilinos: Added (trilinos project). misc/dos2unix: Updated for version 7.3. misc/esniper: Added (a lightweight eBay sniping tool). multimedia/devede: Removed (replaced with devedeng). multimedia/devedeng: Added (create video CDs and DVDs). multimedia/farstream: Added (framework for conferencing protocols). multimedia/google-earth: Updated for latest version 7.1.4.1529. multimedia/mpv: Updated for version 0.10.0. multimedia/telepathy-farstream: Added (Telepathy client library). multimedia/telepathy-glib: Added (C library for Telepathy Clients). multimedia/telepathy-qt: Added (Library for Qt-based Telepathy). multimedia/tomahawk: Added (A new kind of music player). network/Electrum: Updated for version 2.4.4. network/cacti-spine: Updated for version 0.8.8f. network/cacti: Updated for version 0.8.8f. network/google-cli: Added (Google Search from command line). network/node: Updated for version 0.12.7. network/offlineimap: Updated for version 6.5.7. network/owncloud-client: Updated for version 2.0.0. network/owncloud-server: Updated for version 8.1.2. network/palemoon: Updated for version 25.7.0. network/purple-facebook: Updated for version 6a0a79182ebc. network/qTox: Updated for version 20150830. network/shibboleth-sp: Fix UID/GID. network/tor-browser: Updated for version 5.0.2. network/toxcore: Updated for version 20150808. network/vivaldi: Updated for version 1.0.258.3_1. network/zmap: Updated for version 2.1.0. office/MasterPDFEditor: Updated for version 3.3.20. office/fop: Updated for version 2.0. office/hunspell-pl: Added (Polish hunspell dictionary). perl/perl-ExtUtils-Install: Added (Handle perl modules). perl/perl-Text-Diff: Updated for version 1.43. perl/perl-extutils-makemaker: Updated for version 7.06. perl/perl-inc-latest: Update README about optional dependency. python/dulwich: Updated for version 0.10.1. python/hg-git: Updated for version 0.8.2. python/hgsubversion: Updated for version 1.8.2. python/path.py: Updated for version 8.1. python/pip: Updated for version 7.1.2. python/pysetuptools: Updated for version 18.2. python/virtualenv: Updated for version 13.1.2. ruby/passenger: Updated for version 5.0.16. ruby/rubygem-rack: Updated for version 1.6.4. system/Iosevka: Updated for version 0.1.10. system/adobe-source-serif-pro-font: Fix slack-desc. system/dar: Updated for version 2.4.18. system/exfat-utils: Updated for version 1.2.0. system/fuse-exfat: Updated for version 1.2.0. system/mlterm: Updated for version 3.5.1. system/mysql-utilities: Updated for version 1.6.2. system/pyarchey: Fix README typo. system/pycp: Added (cp and mv with a progressbar). system/redis: Updated for version 3.0.3. system/slpkg: Updated for version 2.8.2. system/spacefm: Updated for version 1.0.3. system/spl-solaris: Updated for version 0.6.4.2 + new maintainer. system/ttf-aller: Added (True Type Font). system/ttf-monaco: Added (True Type Font). system/ttf-mscorefonts: Removed (similar with webcore-fonts). system/ttf-open-sans: Added (True Type Font). system/ttf-roboto: Added (True Type Font). system/winetricks: Updated for version 20150826. system/zfs-on-linux: Updated for version 0.6.4.2 + new maintainer. system/zuluCrypt: Added (CLI and GUI frontend to cryptsetup). +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Sep 6 06:17:25 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 6 Sep 2015 13:17:25 +0700 Subject: [Slackbuilds-users] Updates - 20150906.1 Message-ID: <55EBDA75.80301@slackbuilds.org> Sun Sep 6 06:11:58 UTC 2015 audio/foo-yc20: Update HOMEPAGE and DOWNLOAD. games/opentyrian: Update HOMEPAGE. games/snes9x: Updated HOMEPAGE and DOWNLOAD. games/supermariowar: Updated HOMEPAGE. games/wolf4sdl: Updated HOMEPAGE and DOWNLOAD. libraries/libgit2: Updated for version 0.23.2. libraries/libvdpau: Updated for version 1.1.1. libraries/opencv: Fix path to opencv_contrib modules. network/dokuwiki: Updated for version 20150810a. network/vivaldi: Updated for version 1.0.264.3_1. python/python-certifi: Updated for version 2015.9.6.1. python/waitress: Updated for version 0.8.10. system/nvidia-driver: Updated for version 352.41. system/nvidia-kernel: Updated for version 352.41. system/nvidia-legacy304-driver: Updated for version 304.128. system/nvidia-legacy304-kernel: Updated for version 304.128. system/nvidia-legacy340-driver: Updated for version 340.93. system/nvidia-legacy340-kernel: Updated for version 340.93. system/qemu: Updated for version 2.4.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From dn2010 at gmail.com Sun Sep 6 08:43:21 2015 From: dn2010 at gmail.com (Daniil Bratashov) Date: Sun, 6 Sep 2015 11:43:21 +0300 Subject: [Slackbuilds-users] python3 builds of libraries Message-ID: <20150906114321.09d4c7f8@darkstar.example.net> I have to build and maintain a Gausssum software that require the python3 versions of matplotlib, numpy and all of its dependencies. May be it is worth to check if python3 is installed and build also python3 versions of libraries if so by default? WBR, Daniil Bratashov. From baildon.research at googlemail.com Sun Sep 6 12:01:41 2015 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 6 Sep 2015 13:01:41 +0100 Subject: [Slackbuilds-users] Ruby SlackBuilds on -current Message-ID: Hi folks, If anybody has tried any of the ruby builds on -current since the August 21 upgrade to ruby-2.2.3, you will know almost all of them are broken. This is because there is now a subdirectory named "default" under /usr/lib64/ruby/gems/2.2.0/specifications/. (As usual, nobody upstream thought this was worth putting in a changelog or documenting.) Anyway, a glob in the SlackBuild template picks up the subdirectory name and tries to process it as a gemspec. My suggested minimal fix is that "/specifications/*" needs to be changed to "/specifications/**/*.gemspec" in the template and in the SlackBuilds. Also, a lot of SlackBuilds have an incomplete fix for the previous "Config" -> "RbConfig" change. The line beginning "c =" should read "c = RbConfig::CONFIG" All the Ruby SlackBuilds will need to be fixed for 14.2, but these two fixes are backwards compatible with 14.1, so the maintainers can apply them now if they want to. Otherwise I'll send updated SlackBuilds to Matteo, for maintainers to review when we get nearer to 14.2. It would be nice to get rid of hard tabs in the template and SlackBuilds at the same time. I know no Ruby whatsoever beyond what was needed to find a fix for this, so anybody who has corrections, additions, improvements and rethinks is very welcome to take this forward. This is why I've not included patches with this email. Thanks for reading this -D. From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Mon Sep 7 07:00:54 2015 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Mon, 07 Sep 2015 09:00:54 +0200 Subject: [Slackbuilds-users] python3 builds of libraries In-Reply-To: <20150906114321.09d4c7f8@darkstar.example.net> References: <20150906114321.09d4c7f8@darkstar.example.net> Message-ID: <55ED3626.2050105@skmail.ikp.physik.tu-darmstadt.de> On 09/06/2015 10:43 AM, Daniil Bratashov wrote: > I have to build and maintain a Gausssum software that require the > python3 versions of matplotlib, numpy and all of its dependencies. May > be it is worth to check if python3 is installed and build also python3 > versions of libraries if so by default? > ... Hello! I have to admit that this is an old issue, I didn't get to solve until now. The main reason is, that I don't need a python3 build for the python packages I maintain and thus I just forget to address it. I'll do my best to get it sorted out during this week. Best regards Serban Udrea From atelszewski at gmail.com Mon Sep 7 09:07:14 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 7 Sep 2015 11:07:14 +0200 Subject: [Slackbuilds-users] Keywords in info file Message-ID: <55ED53C2.8030704@gmail.com> Hi, Would it be possible to include the keywords in the .info file? The point is that, at the moment I have to note down the keywords somewhere and it becomes sometimes messy, when e.g. I write 2 or 3 SlackBuilds at the same time (my notes keeper gets messy;)). The bigger point is that, it will generally take me 1 or 2 days to submit the SlackBuild after it has been written and during these few days I come with new keywords that I have to note somewhere, and this somewhere does not help with the workflow. Having the keywords in the SlackBuild directory itself would improve the situation. Maybe I'm a bit paranoid, but in general I'll try to add as many relevant keywords as possible, so that others that are thinking differently, have better chances of finding the SlackBuild. -- Best regards, Andrzej Telszewski From marc at mos6581.de Mon Sep 7 12:03:29 2015 From: marc at mos6581.de (Marcel Saegebarth) Date: Mon, 7 Sep 2015 14:03:29 +0200 Subject: [Slackbuilds-users] python3 builds of libraries In-Reply-To: <20150906114321.09d4c7f8@darkstar.example.net> References: <20150906114321.09d4c7f8@darkstar.example.net> Message-ID: <55ED7D11.40505@mos6581.de> On 09/06/2015 10:43 AM, Daniil Bratashov wrote: > I have to build and maintain a Gausssum software that require the > python3 versions of matplotlib, numpy and all of its dependencies. May > be it is worth to check if python3 is installed and build also python3 > versions of libraries if so by default? I'd like to see any of those libs separated into 'python-' and 'python3-' as it doesn't always makes sense having both installed. Some python2 projects have no support for python3 and vice versa and may never be. It's also annoying to rebuild all python packages in case it's the first time you want to install a python3 package and it depends on many other packages. I actually work on a SlackBuild that depends on some python SlackBuilds which don't support python3 yet. A lot of communication to the maintainers is needed. -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Mon Sep 7 12:16:34 2015 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Mon, 07 Sep 2015 14:16:34 +0200 Subject: [Slackbuilds-users] python3 builds of libraries In-Reply-To: <55ED7D11.40505@mos6581.de> References: <20150906114321.09d4c7f8@darkstar.example.net> <55ED7D11.40505@mos6581.de> Message-ID: <55ED8022.7080208@skmail.ikp.physik.tu-darmstadt.de> On 09/07/2015 02:03 PM, Marcel Saegebarth wrote: > On 09/06/2015 10:43 AM, Daniil Bratashov wrote: >> I have to build and maintain a Gausssum software that require the >> python3 versions of matplotlib, numpy and all of its dependencies. May >> be it is worth to check if python3 is installed and build also python3 >> versions of libraries if so by default? > > I'd like to see any of those libs separated into 'python-' and > 'python3-' as it doesn't always makes sense having both installed. > ... Hello! I agree. Best regards, Serban Udrea From citizen.anon.x at gmail.com Mon Sep 7 12:37:40 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Mon, 7 Sep 2015 08:37:40 -0400 Subject: [Slackbuilds-users] Cabextract account suspended Message-ID: while attempting to build libmspack, I got an error saying gzip: stdin: not in gzip format. Attempting to manually download, I went to the http://www.cabextract.org.uk/libmspack/ web site and was presented with a suspension page at http://www.cabextract.org.uk/cgi-sys/suspendedpage.cgi I did find a fork on github at https://github.com/cooljeanius/libmspack -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Sep 7 12:54:52 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 7 Sep 2015 19:54:52 +0700 Subject: [Slackbuilds-users] Keywords in info file In-Reply-To: <55ED53C2.8030704@gmail.com> References: <55ED53C2.8030704@gmail.com> Message-ID: <55ED891C.7000104@slackbuilds.org> > Would it be possible to include the keywords in the .info file? > > The point is that, at the moment I have to note down the keywords > somewhere and it becomes sometimes messy, when e.g. I write 2 or 3 > SlackBuilds at the same time (my notes keeper gets messy;)). > > The bigger point is that, it will generally take me 1 or 2 days to > submit the SlackBuild after it has been written and during these few > days I come with new keywords that I have to note somewhere, and this > somewhere does not help with the workflow. Having the keywords in the > SlackBuild directory itself would improve the situation. > > Maybe I'm a bit paranoid, but in general I'll try to add as many > relevant keywords as possible, so that others that are thinking > differently, have better chances of finding the SlackBuild. Any real benefit of adding this keyword in the info file? Currently, we store the keywords in the database so that it could be used for searching purpose and easily modified without having to submit a new package just to change the keywords. Also, i personally disagree to use info file to store all the keywords, since it would mean more checking during approval since a single mistake in the .info files could cause some problem during public update. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Mon Sep 7 13:01:49 2015 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 7 Sep 2015 14:01:49 +0100 Subject: [Slackbuilds-users] Cabextract account suspended In-Reply-To: References: Message-ID: > while attempting to build libmspack, I got an error saying gzip: stdin: not > in gzip format. Attempting to manually download, I went to the > http://www.cabextract.org.uk/libmspack/ web site and was presented with a > suspension page at http://www.cabextract.org.uk/cgi-sys/suspendedpage.cgi Ok I've pushed a copy to http://sourceforge.net/projects/slackbuildsdirectlinks/files/libmspack/libmspack-0.5alpha.tar.gz The md5sum should still be the same: 3aa3f6b9ef101463270c085478fda1da -D. From baildon.research at googlemail.com Mon Sep 7 13:09:45 2015 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 7 Sep 2015 14:09:45 +0100 Subject: [Slackbuilds-users] Cabextract account suspended In-Reply-To: References: Message-ID: Come to think of it -- the source for cabextract must also be unavailable, so I've uploaded that too. (It may take a few minutes for mirrors to synchronize.) http://sourceforge.net/projects/slackbuildsdirectlinks/files/cabextract/cabextract-1.4.tar.gz md5sum unchanged: 79f41f568cf1a3ac105e0687e8bfb7c0 -D. From atelszewski at gmail.com Mon Sep 7 13:27:46 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 7 Sep 2015 15:27:46 +0200 Subject: [Slackbuilds-users] Keywords in info file In-Reply-To: <55ED891C.7000104@slackbuilds.org> References: <55ED53C2.8030704@gmail.com> <55ED891C.7000104@slackbuilds.org> Message-ID: <55ED90D2.8030309@gmail.com> On 07/09/15 14:54, Willy Sudiarto Raharjo wrote: >> Would it be possible to include the keywords in the .info file? >> >> The point is that, at the moment I have to note down the keywords >> somewhere and it becomes sometimes messy, when e.g. I write 2 or 3 >> SlackBuilds at the same time (my notes keeper gets messy;)). >> >> The bigger point is that, it will generally take me 1 or 2 days to >> submit the SlackBuild after it has been written and during these few >> days I come with new keywords that I have to note somewhere, and this >> somewhere does not help with the workflow. Having the keywords in the >> SlackBuild directory itself would improve the situation. >> >> Maybe I'm a bit paranoid, but in general I'll try to add as many >> relevant keywords as possible, so that others that are thinking >> differently, have better chances of finding the SlackBuild. > > > Any real benefit of adding this keyword in the info file? As I explained before, it would save me from noting the keywords for new SlackBuilds on the back of the envelope... > > Currently, we store the keywords in the database so that it could be > used for searching purpose and easily modified without having to submit > a new package just to change the keywords. > > Also, i personally disagree to use info file to store all the keywords, > since it would mean more checking during approval since a single mistake > in the .info files could cause some problem during public update. I'm not going to insist, as I have already workaround for the issue;) From my point of view, including keywords would help me keep a little bit smaller mess on my notes. But if you say it might make approval more cumbersome, then I said nothing. My few SlackBuilds per year is not much comparing to what you have to check during the approval. > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Pozdrawiam, Best regards, Andrzej Telszewski From willysr at slackbuilds.org Mon Sep 7 16:01:47 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 7 Sep 2015 23:01:47 +0700 Subject: [Slackbuilds-users] Cabextract account suspended In-Reply-To: References: Message-ID: <55EDB4EB.2080902@slackbuilds.org> > Come to think of it -- the source for cabextract must also be > unavailable, so I've uploaded that too. (It may take a few minutes > for mirrors to synchronize.) > > http://sourceforge.net/projects/slackbuildsdirectlinks/files/cabextract/cabextract-1.4.tar.gz > md5sum unchanged: 79f41f568cf1a3ac105e0687e8bfb7c0 Thanks fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Mon Sep 7 21:49:44 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 8 Sep 2015 07:49:44 +1000 Subject: [Slackbuilds-users] Keywords in info file In-Reply-To: <55ED90D2.8030309@gmail.com> References: <55ED53C2.8030704@gmail.com> <55ED891C.7000104@slackbuilds.org> <55ED90D2.8030309@gmail.com> Message-ID: <55EE0678.8040803@iinet.net.au> On 07/09/15 23:27, Andrzej Telszewski wrote: > On 07/09/15 14:54, Willy Sudiarto Raharjo wrote: >>> Would it be possible to include the keywords in the .info file? >>> >>> The point is that, at the moment I have to note down the keywords >>> somewhere and it becomes sometimes messy, when e.g. I write 2 or 3 >>> SlackBuilds at the same time (my notes keeper gets messy;)). >>> >>> The bigger point is that, it will generally take me 1 or 2 days to >>> submit the SlackBuild after it has been written and during these few >>> days I come with new keywords that I have to note somewhere, and this >>> somewhere does not help with the workflow. Having the keywords in the >>> SlackBuild directory itself would improve the situation. >>> >>> Maybe I'm a bit paranoid, but in general I'll try to add as many >>> relevant keywords as possible, so that others that are thinking >>> differently, have better chances of finding the SlackBuild. >> >> >> Any real benefit of adding this keyword in the info file? > > As I explained before, it would save me from noting the keywords for new > SlackBuilds on the back of the envelope... > There is nothing preventing you from adding whatever you like to your own local .info files - just remember to remove anything additional before submitting to SBo. chris From yalhcru at gmail.com Mon Sep 7 21:55:50 2015 From: yalhcru at gmail.com (B Watson) Date: Mon, 7 Sep 2015 17:55:50 -0400 Subject: [Slackbuilds-users] Keywords in info file In-Reply-To: <55EE0678.8040803@iinet.net.au> References: <55ED53C2.8030704@gmail.com> <55ED891C.7000104@slackbuilds.org> <55ED90D2.8030309@gmail.com> <55EE0678.8040803@iinet.net.au> Message-ID: On 9/7/15, Christoph Willing wrote: > There is nothing preventing you from adding whatever you like to your > own local .info files - just remember to remove anything additional > before submitting to SBo. Or just include a file called keywords.txt in the tarball. I don't think it would cause any problems for the approval process (someone correct me if I'm wrong). You'd just have to remember to paste its contents into the submission form, when it comes time to submit the build. From atelszewski at gmail.com Mon Sep 7 22:17:30 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 8 Sep 2015 00:17:30 +0200 Subject: [Slackbuilds-users] Keywords in info file In-Reply-To: References: <55ED53C2.8030704@gmail.com> <55ED891C.7000104@slackbuilds.org> <55ED90D2.8030309@gmail.com> <55EE0678.8040803@iinet.net.au> Message-ID: <55EE0CFA.1090704@gmail.com> On 07/09/15 23:55, B Watson wrote: > On 9/7/15, Christoph Willing wrote: > >> There is nothing preventing you from adding whatever you like to your >> own local .info files - just remember to remove anything additional >> before submitting to SBo. Yep, but that requires additional work before submitting and probably often I would submit the .info with my own fields;) > > Or just include a file called keywords.txt in the tarball. I don't think > it would cause any problems for the approval process (someone correct > me if I'm wrong). You'd just have to remember to paste its contents into > the submission form, when it comes time to submit the build.-- I don't think it's a good idea. This way people would start to include whatever they liked and it would become a mess for SBo crew. I will keep the keywords in a separate file and just won't include it in the upload. -- Best regards, Andrzej Telszewski From baildon.research at googlemail.com Mon Sep 7 22:34:32 2015 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 7 Sep 2015 23:34:32 +0100 Subject: [Slackbuilds-users] Keywords in info file In-Reply-To: <55EE0CFA.1090704@gmail.com> References: <55ED53C2.8030704@gmail.com> <55ED891C.7000104@slackbuilds.org> <55ED90D2.8030309@gmail.com> <55EE0678.8040803@iinet.net.au> <55EE0CFA.1090704@gmail.com> Message-ID: > I will keep the keywords in a separate file and just won't include it in the > upload. How about using dokuwiki? It's how I keep all my maintaining info, including version numbers, upstream URLs to check for new versions, mailing list and bugtracker URLs, other distro's packaging repos for stealing patches ;-) lists of packages that depend on my packages ... and keywords. There's an SBo package for dokuwiki, and Giorgio the maintainer updated it just a couple of days ago :-) -D. From joshuakwood at gmail.com Mon Sep 7 22:41:33 2015 From: joshuakwood at gmail.com (JK Wood) Date: Mon, 7 Sep 2015 17:41:33 -0500 Subject: [Slackbuilds-users] Keywords in info file In-Reply-To: References: <55ED53C2.8030704@gmail.com> <55ED891C.7000104@slackbuilds.org> <55ED90D2.8030309@gmail.com> <55EE0678.8040803@iinet.net.au> <55EE0CFA.1090704@gmail.com> Message-ID: The other thing to keep in mind is this: the database keeps track of the keywords that have already been associated with the SlackBuild. The only reason you would need to worry about that after the original submission is if you come up with additional keywords, which shouldn't happen often unless you're dealing with systemd-level feature creep. --JK On Mon, Sep 7, 2015 at 5:34 PM, David Spencer < baildon.research at googlemail.com> wrote: > > I will keep the keywords in a separate file and just won't include it in > the > > upload. > > How about using dokuwiki? It's how I keep all my maintaining info, > including version numbers, upstream URLs to check for new versions, > mailing list and bugtracker URLs, other distro's packaging repos for > stealing patches ;-) lists of packages that depend on my packages ... > and keywords. > > There's an SBo package for dokuwiki, and Giorgio the maintainer > updated it just a couple of days ago :-) > > -D. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Mon Sep 7 22:44:20 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 8 Sep 2015 00:44:20 +0200 Subject: [Slackbuilds-users] Keywords in info file In-Reply-To: References: <55ED53C2.8030704@gmail.com> <55ED891C.7000104@slackbuilds.org> <55ED90D2.8030309@gmail.com> <55EE0678.8040803@iinet.net.au> <55EE0CFA.1090704@gmail.com> Message-ID: <55EE1344.8060900@gmail.com> On 08/09/15 00:34, David Spencer wrote: >> I will keep the keywords in a separate file and just won't include it in the >> upload. > > How about using dokuwiki? It's how I keep all my maintaining info, > including version numbers, upstream URLs to check for new versions, > mailing list and bugtracker URLs, other distro's packaging repos for > stealing patches ;-) lists of packages that depend on my packages ... > and keywords. > > There's an SBo package for dokuwiki, and Giorgio the maintainer > updated it just a couple of days ago :-) > And I just wanted to keep my keywords in place... You're on higher level, methinks ;) -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Mon Sep 7 22:46:49 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 8 Sep 2015 00:46:49 +0200 Subject: [Slackbuilds-users] Keywords in info file In-Reply-To: References: <55ED53C2.8030704@gmail.com> <55ED891C.7000104@slackbuilds.org> <55ED90D2.8030309@gmail.com> <55EE0678.8040803@iinet.net.au> <55EE0CFA.1090704@gmail.com> Message-ID: <55EE13D9.4010009@gmail.com> On 08/09/15 00:41, JK Wood wrote: > unless you're dealing with systemd-level feature creep. Please keep the list free from political issues ;) -- Best regards, Andrzej Telszewski From baildon.research at googlemail.com Mon Sep 7 22:47:45 2015 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 7 Sep 2015 23:47:45 +0100 Subject: [Slackbuilds-users] Keywords in info file In-Reply-To: <55EE1344.8060900@gmail.com> References: <55ED53C2.8030704@gmail.com> <55ED891C.7000104@slackbuilds.org> <55ED90D2.8030309@gmail.com> <55EE0678.8040803@iinet.net.au> <55EE0CFA.1090704@gmail.com> <55EE1344.8060900@gmail.com> Message-ID: > And I just wanted to keep my keywords in place... > You're on higher level, methinks ;) Lower level really -- it just doesn't fit in my head these days :-( Cheers -D. From miguel at thedeanda.com Tue Sep 8 06:52:40 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Mon, 7 Sep 2015 23:52:40 -0700 Subject: [Slackbuilds-users] Keywords in info file In-Reply-To: References: <55ED53C2.8030704@gmail.com> <55ED891C.7000104@slackbuilds.org> <55ED90D2.8030309@gmail.com> <55EE0678.8040803@iinet.net.au> <55EE0CFA.1090704@gmail.com> Message-ID: The other thing to keep in mind is this: the database keeps track of the keywords that have already been associated with the SlackBuild. The only reason you would need to worry about that after the original submission is if you come up with additional keywords, which shouldn't happen often unless you're dealing with systemd-level feature creep. --JK Well that's good to know. I always open existing SlackBuilds as I submit an update and copy paste all the fields. It would be nice to just have the form read in values from tgz upload though. M -------------- next part -------------- An HTML attachment was scrubbed... URL: From hostmaster at slackonly.com Tue Sep 8 10:05:04 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Tue, 8 Sep 2015 13:05:04 +0300 Subject: [Slackbuilds-users] virtualbox-kernel Message-ID: <55EEB2D0.5020009@slackonly.com> Hi! virtualbox-kernel failed to build with the new kernel 4.1.6 ... I have included a patch to build against new kernel if ! [ "${HARDENING:-yes}" = "yes" ]; then sed -i "s/ -DVBOX_WITH_HARDENING//g" \ {vboxdrv,vboxnetadp,vboxnetflt,vboxpci}/Makefile fi + patch -p1 < $CWD/VBoxPci-linux.c.patch make KERN_DIR=${KERNELPATH} Regards Panagiotis -------------- next part -------------- A non-text attachment was scrubbed... Name: VBoxPci-linux.c.patch Type: text/x-patch Size: 574 bytes Desc: not available URL: From info at microlinux.fr Fri Sep 11 11:56:35 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Fri, 11 Sep 2015 13:56:35 +0200 Subject: [Slackbuilds-users] VLC dependencies Message-ID: <55F2C173.6050605@microlinux.fr> Hi, As far as I understand, SBo's policy is to only list strict dependencies in the REQUIRES="" field. Those dependencies that are not strictly necessary are eventually listed in the text, but not as strict requirements. The VLC SlackBuild seems to be an exception to this policy. It lists an impressive list of dependencies, but only a fraction of these are actually strict dependencies. Suggestion: only list strict dependencies in the REQUIRES="" field, and list all the extra dependencies in a separate text in the README? This would spare the hassle of building jack-audio-connection-kit, avahi, freerdp, etc. just to have a basic VLC. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Fri Sep 11 11:57:23 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 11 Sep 2015 18:57:23 +0700 Subject: [Slackbuilds-users] VLC dependencies In-Reply-To: <55F2C173.6050605@microlinux.fr> References: <55F2C173.6050605@microlinux.fr> Message-ID: <55F2C1A3.9040404@slackbuilds.org> > As far as I understand, SBo's policy is to only list strict dependencies > in the REQUIRES="" field. Those dependencies that are not strictly > necessary are eventually listed in the text, but not as strict > requirements. > > The VLC SlackBuild seems to be an exception to this policy. It lists an > impressive list of dependencies, but only a fraction of these are > actually strict dependencies. > > Suggestion: only list strict dependencies in the REQUIRES="" field, and > list all the extra dependencies in a separate text in the README? This > would spare the hassle of building jack-audio-connection-kit, avahi, > freerdp, etc. just to have a basic VLC. Mandatory requirement is a must in REQUIRES, but if the maintainer thinks that a certain dependencies are needed in REQUIRES as well, it *may* be listed too (please give a good argument on the comment section during submission) ffmpeg in the past also includes lame, which was an optional dep. Of course, we don't want to have a bloated package, so it must be used with extra care. It's decided case-by-case. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Fri Sep 11 12:11:05 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 11 Sep 2015 14:11:05 +0200 Subject: [Slackbuilds-users] VLC dependencies In-Reply-To: <55F2C1A3.9040404@slackbuilds.org> References: <55F2C173.6050605@microlinux.fr> <55F2C1A3.9040404@slackbuilds.org> Message-ID: 2015-09-11 13:57 GMT+02:00 Willy Sudiarto Raharjo : >> As far as I understand, SBo's policy is to only list strict dependencies >> in the REQUIRES="" field. Those dependencies that are not strictly >> necessary are eventually listed in the text, but not as strict >> requirements. >> >> The VLC SlackBuild seems to be an exception to this policy. It lists an >> impressive list of dependencies, but only a fraction of these are >> actually strict dependencies. >> >> Suggestion: only list strict dependencies in the REQUIRES="" field, and >> list all the extra dependencies in a separate text in the README? This >> would spare the hassle of building jack-audio-connection-kit, avahi, >> freerdp, etc. just to have a basic VLC. > > Mandatory requirement is a must in REQUIRES, but if the maintainer > thinks that a certain dependencies are needed in REQUIRES as well, it > *may* be listed too (please give a good argument on the comment section > during submission) > > ffmpeg in the past also includes lame, which was an optional dep. > > Of course, we don't want to have a bloated package, so it must be used > with extra care. It's decided case-by-case. IMHO, the maintainer decides which dependencies are mandatory to have the best experience with the packaged application: if anybody thinks that something in REQUIRES shouldn't be there for any reason, it should report it to the maintainer and discuss it with him. vlc is an universal player so, still IMHO, it makes sense that the stuff presently in REQUIRES stay there. I quote from its README: "This build aims to support as many options as possible using the SlackBuilds listed in the REQUIRES field of the vlc.info file. No script changes are necessary to include particular options; if they are detected at build time, they will be included. Conversely if optional packages are not available at build time, vlc will continue to build with a reduced feature set." Matteo From citizen.anon.x at gmail.com Fri Sep 11 14:30:49 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Fri, 11 Sep 2015 10:30:49 -0400 Subject: [Slackbuilds-users] cracklib package Message-ID: can the maintainer of cracklib update please? I have my own already done locally as a dependency for a project but thought it might be worth updating online for SlackBuilds. It builds with no issues that I can see going through the output. Updated my local info file as such: PRGNAM="cracklib" VERSION="2.9.6" HOMEPAGE="http://sourceforge.net/projects/cracklib" DOWNLOAD=" https://github.com/cracklib/cracklib/releases/download/cracklib-2.9.6/cracklib-2.9.6.tar.gz \ https://github.com/cracklib/cracklib/releases/download/cracklib-2.9.6/cracklib-words-2.9.6.gz " MD5SUM="c52f463585d85924b28cdc1e373ae06d \ cae1257e3a9f95c917cc9dbbab852316" Updated my local script as such: PRGNAM=cracklib VERSION=${VERSION:-2.9.6} BUILD=${BUILD:-1} TAG=${TAG:-_ctzn} DICT=${DICT:-cracklib-words-2.9.6} Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From C.J.Theunissen at differ.nl Fri Sep 11 15:20:49 2015 From: C.J.Theunissen at differ.nl (Kees Theunissen) Date: Fri, 11 Sep 2015 17:20:49 +0200 (CEST) Subject: [Slackbuilds-users] perl-Image-Info: missing dependency Message-ID: Hello, Building "perl-Image-Info" version 1.38 requires IO::Scalar which is part of the "perl-IO-stringy" package. My sbopkg-build-log shows: [...] Warning: prerequisite IO::Scalar 0 not found. [...] PERL_DL_NONLAZY=1 /usr/bin/perl5.18.1 "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/00_basics.t .............................. ok t/bad_exif.t ............................... ok t/bmp.t .................................... ok t/exif.t ................................... ok t/fuji_s1000fd_substr_outside_of_string.t .. ok t/ico.t .................................... ok t/jpg_corruptchunk.t ....................... ok # Ignoring unknown type code 0 # Ignoring unknown type code 20 t/jpg_hang.t ............................... ok t/jpg_ignore_thumbnail.t ................... ok t/png.t .................................... ok t/pod.t .................................... ok t/pod_cov.t ................................ skipped: Test::Pod::Coverage 1.00 required for testing POD coverage t/string.t ................................. ok # Using SVG module Image::Info::SVG::XMLSimple # XML::Simple 2.20 t/svg.t .................................... ok t/tiff.t ................................... ok t/tiff_e.t ................................. ok t/tiff_segfault.t .......................... No subtests run t/tiny-pgm.t ............................... ok t/wbmp.t ................................... ok Test Summary Report ------------------- t/tiff_segfault.t (Wstat: 11 Tests: 0 Failed: 0) Non-zero wait status: 11 Parse errors: No plan found in TAP output Files=19, Tests=184, 1 wallclock secs ( 0.04 usr 0.00 sys + 0.39 cusr 0.03 csys = 0.46 CPU) Result: FAIL Failed 1/19 test programs. 0/184 subtests failed. make: *** [test_dynamic] Error 255 Building and installing perl-IO-stringy-2.111-x86_64-1_SBo.tgz solved this error. Regards, Kees Theunissen. -- Kees Theunissen, System and network manager, Tel: +31 (0)40-3334724 Dutch Institute For Fundamental Energy Research (DIFFER) e-mail address: C.J.Theunissen at differ.nl postal address: PO Box 6336, 5600 HH, Eindhoven, the Netherlands visitors address: De Zaale 20, 5612 AJ, Eindhoven, the Netherlands From willysr at slackbuilds.org Fri Sep 11 20:12:32 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 12 Sep 2015 03:12:32 +0700 Subject: [Slackbuilds-users] perl-Image-Info: missing dependency In-Reply-To: References: Message-ID: <55F335B0.6050206@slackbuilds.org> > Building and installing perl-IO-stringy-2.111-x86_64-1_SBo.tgz > solved this error. Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Fri Sep 11 20:24:41 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 12 Sep 2015 03:24:41 +0700 Subject: [Slackbuilds-users] cracklib package In-Reply-To: References: Message-ID: <55F33889.1030405@slackbuilds.org> > can the maintainer of cracklib update please? I have my own already done > locally as a dependency for a project but thought it might be worth > updating online for SlackBuilds. The maintainer hasn't submitted any update since 2 years ago. Anyway, i have update it to the latest version 2.9.6 on my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Sep 12 01:31:15 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 12 Sep 2015 08:31:15 +0700 Subject: [Slackbuilds-users] Updates - 20150912.1 Message-ID: <55F38063.2050707@slackbuilds.org> Sat Sep 12 01:12:12 UTC 2015 academic/parmetis: Added (parallel library). audio/apulse: Allow GPLv2. audio/cmt: Update homepage and download URLs. audio/flacon: Added (Audio File Encoder). audio/patchage: Allow GPLv2. audio/tagtool: Allow GPLv2. desktop/cellwriter: Allow GPLv2. desktop/enlightenment: Allow GPLv2. desktop/kde-gtk-config: Allow GPLv2. desktop/neutral: Allow GPLv2. desktop/py3status: Updated for version 2.6. desktop/sun: Updated for version 1.1.4. desktop/superkey-launch: Allow GPLv2. development/astyle: Allow GPLv2. development/bas55: Updated for version 1.04. development/bfg: Allow GPLv2. development/bigloo: Allow GPLv2. development/brackets: Allow GPLv2. development/colordiff: Allow GPLv2. development/enki: Allow GPLv2. development/gauche: Allow GPLv2. development/gisto: Allow GPLv2. development/gnustep-startup: Allow GPLv2. development/groovy: Allow GPLv2. development/hexedit: Allow GPLv2. development/jeex: Allow GPLv2. development/lighttable: Allow GPLv2. development/mcrl2: Allow GPLv2. development/mit-scheme: Allow GPLv2. development/mlton: Allow GPLv2. development/mono2: Allow GPLv2. development/rust: Updated for version 1.2.0. development/scons: Allow GPLv2. development/smalltalk: Allow GPLv2. development/spin: Allow GPLv2. development/src-vcs: Allow GPLv2. development/textadept: Allow GPLv2. development/thunderpad: Allow GPLv2. development/valgrind: Updated for version 3.10.1. development/xtruss: Updated for version 20150529.3149b74. games/KAdventure: Added (a simple 2D qt puzzle game). games/ValyriaTear: Allow GPLv2. games/doomsday: Updated for version 1.15.3. games/fgo: Update EMAIL. games/freeminer: Update script. games/gottet: Allow GPLv2. games/lgogdownloader: Updated for version 2.25. games/lutris: Allow GPLv2. games/xspacewarp: Allow GPLv2. games/yahtzee: Updated for version 1.6. games/yamagi-quake2: Updated for version 5.31. gis/pgrouting: Updated for version 2.1.0. graphics/autotrace: Added (Bitmap to vector graphics converter). graphics/digikam: Updated for version 4.13.0. graphics/jpegoptim: Allow GPLv2. graphics/mozjpeg: Allow GPLv2. graphics/pygraphviz: Updated for version 1.3.1. graphics/scrot: Allow GPLv2. libraries/batinfo: Update EMAIL. libraries/cracklib: Updated for version 2.9.6. libraries/dropbox-python: Updated for version 3.23. libraries/e_dbus: Allow GPLv2. libraries/ecore: Allow GPLv2. libraries/edje: Allow GPLv2. libraries/eet: Allow GPLv2. libraries/efreet: Allow GPLv2. libraries/eina: Allow GPLv2. libraries/eio: Allow GPLv2. libraries/embryo: Allow GPLv2. libraries/evas: Allow GPLv2. libraries/frei0r: Fix building against the newer opencv. libraries/ftplib: Update EMAIL. libraries/ganv: Allow GPLv2. libraries/jsoncpp: Updated for version 1.6.5. libraries/libdbusmenu: Added (library for passing menus over DBus). libraries/libuchardet: Added (encoding detector library). libraries/libucil: Update EMAIL. libraries/libunicapgtk: Update EMAIL. libraries/libva: Updated for version 1.6.1. libraries/libzdb: Updated for version 3.1. libraries/poco: Updated for version 1.6.1. libraries/pymdstat: Update EMAIL. libraries/python-e_dbus: Allow GPLv2. libraries/python-ecore: Allow GPLv2. libraries/python-edje: Allow GPLv2. libraries/python-elementary: Allow GPLv2. libraries/python-emotion: Allow GPLv2. libraries/python-ethumb: Allow GPLv2. libraries/python-evas: Allow GPLv2. libraries/qutepart: Allow GPLv2. misc/wcd: Allow GPLv2. multimedia/coriander: Update EMAIL. multimedia/dvdauthor: Patched for x86_64. multimedia/exaile: Allow GPLv2. multimedia/nightingale: Allow GPLv2. multimedia/picard-plugins: Updated for version 20150827. multimedia/spotify32: Allow GPLv2. multimedia/spotify64: Allow GPLv2. multimedia/ucview: Update EMAIL. multimedia/vlc: Patched for opencv 3.0. network/arno-iptables-firewall: Update EMAIL. network/bottle: Update EMAIL. network/connman: Allow GPLv2. network/copy: Allow GPLv2. network/econnman: Allow GPLv2. network/google-cli: Updated for version 1.6. network/hipchat: Allow GPLv2. network/iojs: Allow GPLv2. network/ipscan: Added (fast and friendly network scanner). network/irssi_otr: Handle github vXXX.tar.gz filename. network/licq: Allow GPLv2. network/openvswitch: Updated for version 2.3.2. network/owncloud-client: Updated for version 2.0.1. network/shorewall-core: Updated for version 4.6.13. network/shorewall6: Updated for version 4.6.13. network/shorewall: Updated for version 4.6.13. network/uget: Updated for version 2.0.1, updated script. network/vivaldi: Updated for version 1.0.270.16_1. network/youtube-dl: Updated for version 2015.09.03. network/yturl: Updated for version 1.20.0, update man page. office/mdp: Allow GPLv2. perl/perl-Image-Info: Update DEP. perl/perl-Sidef: Updated for version 0.09. perl/perl-Term-ReadLine-Gnu: Updated for version 1.27. perl/perl-data-dump: Updated for version 1.23. perl/perl-extutils-makemaker: Updated for version 7.08. python/easygui: Updated for version 0.97.4. python/path.py: Updated for version 8.1.1. python/psutil: Updated for version 3.2.1. python/py3sensors: Update EMAIL. python/pyglet: Updated for version 1.2.4. python/python-certifi: Updated for version 2015.9.6.2. python/python-future: Updated for version 0.15.1. python/python-lhafile: Updated for version 0.2.1. python/python-swiftclient: Updated for version 2.6.0. python/python3-defusedxml: Added (XML bomb protection). python/python3-dugong: Added (HTTP 1.1 communication API). python/python3-lhafile: Updated for version 0.2.1. python/python3-pycrypto: Added (The Python Cryptography Toolkit). system/betty: Allow GPLv2. system/cabextract: Fix DOWNLOAD url. system/ded: Updated for version 20150704. system/glances: Update EMAIL. system/inxi: Updated for version 2.2.28. system/komparator4: Allow GPLv2. system/luckybackup: Updated for version 0.4.8 + new maintainer. system/man-db: Updated for version 2.7.3. system/man-pages-ja: Updated for version 20150815. system/openrc-services: Updated for version 20150906. system/pdfgrep: Updated for version 1.4.0. system/s3ql: Added (Online Storage File System). system/slpkg: Updated for version 2.8.7. system/sysdig: Updated for version 0.1.104. system/the_silver_searcher: Updated for version 0.31.0. system/tinyterm: Updated for version 0.5.8. system/tinyvm: Allow GPLv2. system/trmaid: Updated for version 0.5.6. system/vinterm: Update download URL. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sat Sep 12 09:23:54 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 12 Sep 2015 11:23:54 +0200 Subject: [Slackbuilds-users] bashisms? In-Reply-To: References: <55DF64D6.7080802@slint.fr> <20150828112555.GC24396@jdiamond-nb2> <20150829121646.GA12197@jdiamond-nb2> <20150829162037.GA21308@jdiamond-nb2> <55E6FF1E.8030801@gmail.com> <20150902105124.2f27b96b@stygian.lan> <55E71139.8030807@gmail.com> Message-ID: <55F3EF2A.7090904@gmail.com> Hi, I'm sorry to bother you again, it's not a bashism, but I thought I'll share my finding with you. I have never read my shell's manual (probably applies to all the shells) and I was shocked by this behavior, particularly because I spent couple of hours debugging my script. I should have read my shell's manual, sigh... Test script: #!/bin/sh AAA=$'\n'$'\n'AAA$'\n'$'\n' print_aaa() { echo "$AAA" } echo "$AAA" echo ====== echo "$(print_aaa)" OUTPUT: $ ./test.sh AAA ====== AAA $ Basically, command substitution $() removes trailing newlines... I found it, when I was trying to check MD5 sum of variable, that contained 2 trailing newlines at the end. http://unix.stackexchange.com/questions/17747/why-does-shell-command-substitution-gobble-up-a-trailing-newline-char http://wiki.bash-hackers.org/syntax/expansion/cmdsubst Hope this helps. -- Best regards, Andrzej Telszewski From citizen.anon.x at gmail.com Sat Sep 12 18:50:02 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Sat, 12 Sep 2015 14:50:02 -0400 Subject: [Slackbuilds-users] EDE build stops Message-ID: Building Equinox Desktop Environment just stops toward end. The message at the end of output reads: XGettext evoke/locale/messages.pot AsciiDoc1 ./doc/manual/index.html AsciiDoc1 ./doc/manual/introduction.html AsciiDoc1 ./doc/manual/hacking.html AsciiDoc1 ./doc/manual/dbus-usage.html ...skipped all for lack of exe... ...failed updating 1 target(s)... ...skipped 1 target(s)... ...updated 239 target(s)... Hope this helps? -------------- next part -------------- An HTML attachment was scrubbed... URL: From edps.mundognu at gmail.com Tue Sep 15 15:08:20 2015 From: edps.mundognu at gmail.com (Edinaldo) Date: Tue, 15 Sep 2015 12:08:20 -0300 Subject: [Slackbuilds-users] libffado download link is broken Message-ID: Hello, please change the download link for " libffado " for one of these: http://pkgs.fedoraproject.org/repo/pkgs/libffado/libffado-2.1.0.tgz/26bce2be0b9c1fa4e614f2f494edf388/libffado-2.1.0.tgz or http://df.tld-linux.org/distfiles/by-md5/2/6/26bce2be0b9c1fa4e614f2f494edf388/libffado-2.1.0.tgz * the md5sum are the the same. Currently the download link is broken, the site is under maintenance. From willysr at slackbuilds.org Tue Sep 15 19:23:38 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Sep 2015 02:23:38 +0700 Subject: [Slackbuilds-users] libffado download link is broken In-Reply-To: References: Message-ID: <55F8703A.1090504@slackbuilds.org> On 09/15/2015 10:08 PM, Edinaldo wrote: > > Hello, please change the download link for " libffado " for one of these: > > http://pkgs.fedoraproject.org/repo/pkgs/libffado/libffado-2.1.0.tgz/26bce2be0b9c1fa4e614f2f494edf388/libffado-2.1.0.tgz > > > or > > http://df.tld-linux.org/distfiles/by-md5/2/6/26bce2be0b9c1fa4e614f2f494edf388/libffado-2.1.0.tgz > > > * the md5sum are the the same. > > Currently the download link is broken, the site is under maintenance. Fixed Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Tue Sep 15 20:40:33 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Sep 2015 03:40:33 +0700 Subject: [Slackbuilds-users] EDE build stops In-Reply-To: References: Message-ID: <55F88241.7030506@slackbuilds.org> > Building Equinox Desktop Environment just stops toward end. The message at > the end of output reads: > > XGettext evoke/locale/messages.pot > AsciiDoc1 ./doc/manual/index.html > AsciiDoc1 ./doc/manual/introduction.html > AsciiDoc1 ./doc/manual/hacking.html > AsciiDoc1 ./doc/manual/dbus-usage.html > ...skipped all for lack of exe... > ...failed updating 1 target(s)... > ...skipped 1 target(s)... > ...updated 239 target(s)... > > Hope this helps? Fixed in my branch Thanks for reporting -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From larryhaja at gmail.com Wed Sep 16 05:00:11 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Tue, 15 Sep 2015 22:00:11 -0700 Subject: [Slackbuilds-users] fftw Message-ID: I just noticed that fftw is in the ready queue. Slackware 14.1 already has fftw, so I'm wondering why it was approved. Thanks, Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Sep 16 05:22:22 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Sep 2015 12:22:22 +0700 Subject: [Slackbuilds-users] fftw In-Reply-To: References: Message-ID: <55F8FC8E.9090005@slackbuilds.org> > I just noticed that fftw is in the ready queue. Slackware 14.1 already > has fftw, so I'm wondering why it was approved. My mistake i checked SBo's repository only at that time and forgot that Slackware already have it. I will delete it from approved soon Thanks for spotting Larry -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Wed Sep 16 06:14:59 2015 From: yalhcru at gmail.com (B Watson) Date: Wed, 16 Sep 2015 02:14:59 -0400 Subject: [Slackbuilds-users] JabRef download URL Message-ID: Happened to notice this one: office/JabRef is missing the http:// in its download URL: DOWNLOAD="downloads.sourceforge.net/project/jabref/jabref/2.9.2/JabRef-2.9.2.jar" From willysr at slackbuilds.org Wed Sep 16 06:23:13 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Sep 2015 13:23:13 +0700 Subject: [Slackbuilds-users] JabRef download URL In-Reply-To: References: Message-ID: <55F90AD1.1030509@slackbuilds.org> > Happened to notice this one: office/JabRef is missing the > http:// in its download URL: > > DOWNLOAD="downloads.sourceforge.net/project/jabref/jabref/2.9.2/JabRef-2.9.2.jar" Fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From citizen.anon.x at gmail.com Thu Sep 17 00:54:35 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Wed, 16 Sep 2015 20:54:35 -0400 Subject: [Slackbuilds-users] popcorntime md5sum Message-ID: was fetching the popcorntime files with slapt-src and recieved: MD5SUM mismatch for Popcorn-Time-0.3.7.2-Linux64.tar.xz original md5sum 918fdc08c4380563243a9a8b26fb45df correct md5sum d81918e168d0eaaf16f58c4708a4e002 Wurd! -------------- next part -------------- An HTML attachment was scrubbed... URL: From citizen.anon.x at gmail.com Thu Sep 17 00:59:23 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Wed, 16 Sep 2015 20:59:23 -0400 Subject: [Slackbuilds-users] Google Music Manager Issues Message-ID: I ran into a version mismatch when attempting to build the package. This is the output: WARNING: The source version (1.0.221.5230) does not match the VERSION variable (1.0.182.3607). To build anyway, run the SlackBuild like this: VERSION=1.0.221.5230 ./google-musicmanager.SlackBuild Also, the md5sums were wrong in the info file. These are the correct ones DOWNLOAD=" https://dl.google.com/linux/direct/google-musicmanager-beta_current_i386.deb " MD5SUM="54648a52a04b0113145f14e69d254ee8" DOWNLOAD_x86_64=" https://dl.google.com/linux/direct/google-musicmanager-beta_current_amd64.deb " MD5SUM_x86_64="e8305efe6035e12b06ea02620896a67e" Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Sep 17 01:06:58 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 17 Sep 2015 08:06:58 +0700 Subject: [Slackbuilds-users] popcorntime md5sum In-Reply-To: References: Message-ID: <55FA1232.5070204@slackbuilds.org> On 09/17/2015 07:54 AM, Citizen X wrote: > was fetching the popcorntime files with slapt-src and recieved: > > MD5SUM mismatch for Popcorn-Time-0.3.7.2-Linux64.tar.xz > > original md5sum 918fdc08c4380563243a9a8b26fb45df > > correct md5sum d81918e168d0eaaf16f58c4708a4e002 Weird sbopkg doesn't seem to complaint here popcorntime: MD5SUM check for Popcorn-Time-0.3.7.2-Linux64.tar.xz ... OK Building package popcorntime-0.3.7.2-x86_64-1_SBo.tgz ... OK Installing package popcorntime-0.3.7.2-x86_64-1_SBo.tgz ... OK md5sum /var/cache/sbopkg/Popcorn-Time-0.3.7.2-Linux64.tar.xz 918fdc08c4380563243a9a8b26fb45df Popcorn-Time-0.3.7.2-Linux64.tar.xz -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Sep 17 01:08:42 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 17 Sep 2015 08:08:42 +0700 Subject: [Slackbuilds-users] Google Music Manager Issues In-Reply-To: References: Message-ID: <55FA129A.9090907@slackbuilds.org> > I ran into a version mismatch when attempting to build the package. > > This is the output: > WARNING: The source version (1.0.221.5230) does not match the VERSION > variable (1.0.182.3607). > To build anyway, run the SlackBuild like this: > > VERSION=1.0.221.5230 ./google-musicmanager.SlackBuild > > Also, the md5sums were wrong in the info file. These are the correct ones > DOWNLOAD=" > https://dl.google.com/linux/direct/google-musicmanager-beta_current_i386.deb > " > MD5SUM="54648a52a04b0113145f14e69d254ee8" > DOWNLOAD_x86_64=" > https://dl.google.com/linux/direct/google-musicmanager-beta_current_amd64.deb > " > MD5SUM_x86_64="e8305efe6035e12b06ea02620896a67e" It's already mentioned on the README Note: When a new version is released, the downloads will change and the md5sums won't match. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From citizen.anon.x at gmail.com Thu Sep 17 01:32:35 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Wed, 16 Sep 2015 21:32:35 -0400 Subject: [Slackbuilds-users] popcorntime md5sum In-Reply-To: <55FA1232.5070204@slackbuilds.org> References: <55FA1232.5070204@slackbuilds.org> Message-ID: Yeah, I checked it again and came back with that md5sum too. Random bad fetching? Thanks again On Wed, Sep 16, 2015 at 9:06 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > On 09/17/2015 07:54 AM, Citizen X wrote: > > was fetching the popcorntime files with slapt-src and recieved: > > > > MD5SUM mismatch for Popcorn-Time-0.3.7.2-Linux64.tar.xz > > > > original md5sum 918fdc08c4380563243a9a8b26fb45df > > > > correct md5sum d81918e168d0eaaf16f58c4708a4e002 > > Weird > sbopkg doesn't seem to complaint here > popcorntime: > MD5SUM check for Popcorn-Time-0.3.7.2-Linux64.tar.xz ... OK > Building package popcorntime-0.3.7.2-x86_64-1_SBo.tgz ... OK > Installing package popcorntime-0.3.7.2-x86_64-1_SBo.tgz ... OK > > md5sum /var/cache/sbopkg/Popcorn-Time-0.3.7.2-Linux64.tar.xz > 918fdc08c4380563243a9a8b26fb45df Popcorn-Time-0.3.7.2-Linux64.tar.xz > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Thu Sep 17 23:07:11 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 18 Sep 2015 01:07:11 +0200 Subject: [Slackbuilds-users] Android/Qt development environment Message-ID: <55FB479F.3070000@gmail.com> Hi, I'm thinking of trying to write an example application for Android using Qt. Per this page: http://doc.qt.io/qt-5/androidgs.html there are several components required. My question is, does it make sense to make SlackBuilds for all this stuff or are they of the type that you have to keep them somewhere in your home directory? Does anybody here have experience on that matter? -- Best regards, Andrzej Telszewski From thedoogster at gmail.com Fri Sep 18 21:03:15 2015 From: thedoogster at gmail.com (Doogster) Date: Fri, 18 Sep 2015 14:03:15 -0700 Subject: [Slackbuilds-users] Orphaning compiz-boxmenu Message-ID: I'm orphaning the compiz-boxmenu SlackBuild, effective immediately. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thedoogster at gmail.com Fri Sep 18 21:04:37 2015 From: thedoogster at gmail.com (Doogster) Date: Fri, 18 Sep 2015 14:04:37 -0700 Subject: [Slackbuilds-users] Offer: Dia SlackBuild ownership Message-ID: I'd like to offer ownership of the Dia SlackBuild to anyone who wants it. If I get no takers, I'll continue to maintain it as best I can. -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackph at posteo.de Fri Sep 18 21:27:16 2015 From: slackph at posteo.de (Philip Lacroix) Date: Fri, 18 Sep 2015 23:27:16 +0200 Subject: [Slackbuilds-users] Offer: Dia SlackBuild ownership In-Reply-To: References: Message-ID: <74d03efe0d1d0768ba48035ba013df29@posteo.de> Hi Doogster Am 18.09.2015 23:04 schrieb Doogster: > I'd like to offer ownership of the Dia SlackBuild to anyone who wants > it. > > If I get no takers, I'll continue to maintain it as best I can. If no one else is interested I'd be glad to maintain it. Cheers Philip From atelszewski at gmail.com Fri Sep 18 22:00:31 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 19 Sep 2015 00:00:31 +0200 Subject: [Slackbuilds-users] libbonobo-2.32.1 fails to build Message-ID: <55FC897F.3020504@gmail.com> Hi, libbonobo-2.32.1 fails to build with the error message: (...) tests/Makefile.am:57: error: using '$(srcdir)' in TESTS is currently broken: '$(srcdir)/test-properties.sh' (...) autoreconf: automake failed with exit status: 1 Adding this patch: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713695 solves the problem. Which is funny, because the patch dates back to: 06 Nov 2013. Is there something wrong with my system?:) -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Fri Sep 18 22:06:30 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 19 Sep 2015 05:06:30 +0700 Subject: [Slackbuilds-users] libbonobo-2.32.1 fails to build In-Reply-To: <55FC897F.3020504@gmail.com> References: <55FC897F.3020504@gmail.com> Message-ID: <55FC8AE6.2000509@slackbuilds.org> > libbonobo-2.32.1 fails to build with the error message: > > (...) > tests/Makefile.am:57: error: using '$(srcdir)' in TESTS is currently > broken: '$(srcdir)/test-properties.sh' > (...) > autoreconf: automake failed with exit status: 1 > > > Adding this patch: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713695 > > solves the problem. > > Which is funny, because the patch dates back to: 06 Nov 2013. > Is there something wrong with my system?:) works fine here ORBit2: MD5SUM check for ORBit2-2.14.19.tar.bz2 ... OK Building package ORBit2-2.14.19-x86_64-3_SBo.tgz ... OK Installing package ORBit2-2.14.19-x86_64-3_SBo.tgz ... OK libbonobo: MD5SUM check for libbonobo-2.32.1.tar.bz2 ... OK Building package libbonobo-2.32.1-x86_64-2_SBo.tgz ... OK Installing package libbonobo-2.32.1-x86_64-2_SBo.tgz ... OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From edps.mundognu at gmail.com Fri Sep 18 22:50:56 2015 From: edps.mundognu at gmail.com (Edinaldo) Date: Fri, 18 Sep 2015 19:50:56 -0300 Subject: [Slackbuilds-users] libbonobo-2.32.1 fails to build Message-ID: After: # Apply patch from upstream to build with the newer glib patch -p1 < $CWD/remove_use_of_G_DISABLE_DEPRECATED.patch Add this: sed -i '58s/\$(srcdir)\/.*.sh//' tests/Makefile.am full log: http://hastebin.com/recosojako * tested in Slack Current i686. From h4rd3r at ymail.com Fri Sep 18 22:49:35 2015 From: h4rd3r at ymail.com (Edinaldo) Date: Fri, 18 Sep 2015 19:49:35 -0300 Subject: [Slackbuilds-users] libbonobo-2.32.1 fails to build Message-ID: After: # Apply patch from upstream to build with the newer glib patch -p1 < $CWD/remove_use_of_G_DISABLE_DEPRECATED.patch Add this: sed -i '58s/\$(srcdir)\/.*.sh//' tests/Makefile.am full log: http://hastebin.com/recosojako * tested in Slack Current i686. From atelszewski at gmail.com Sat Sep 19 09:39:39 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 19 Sep 2015 11:39:39 +0200 Subject: [Slackbuilds-users] libbonobo-2.32.1 fails to build In-Reply-To: References: Message-ID: <55FD2D5B.406@gmail.com> On 19/09/15 00:50, Edinaldo wrote: > > After: > > # Apply patch from upstream to build with the newer glib > patch -p1 < $CWD/remove_use_of_G_DISABLE_DEPRECATED.patch > > Add this: > > sed -i '58s/\$(srcdir)\/.*.sh//' tests/Makefile.am > > > full log: http://hastebin.com/recosojako > > > * tested in Slack Current i686. I'm running almost 14.1. I wonder why Willy can compile properly and I cannot. Two things that come to my mind are: automake-1.14.1-noarch-1_cslack make-3.82-x86_64-5_cslack That is I have newer versions of make and automake (taken from -current some time ago). -- Best regards, Andrzej Telszewski From ryan.q at linux.com Sat Sep 19 11:09:25 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sat, 19 Sep 2015 04:09:25 -0700 Subject: [Slackbuilds-users] libbonobo-2.32.1 fails to build In-Reply-To: <55FD2D5B.406@gmail.com> References: <55FD2D5B.406@gmail.com> Message-ID: > I'm running almost 14.1. I wonder why Willy can compile properly and I cannot. > > Two things that come to my mind are: > automake-1.14.1-noarch-1_cslack > make-3.82-x86_64-5_cslack > > That is I have newer versions of make and automake (taken from -current some time ago). And your error showed that automake was failing, you do realize that current is not officially supported? Have you tried Ponce's repo? https://github.com/Ponce/slackbuilds Also, why did this thread get duplicated? -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Sat Sep 19 11:43:50 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 19 Sep 2015 13:43:50 +0200 Subject: [Slackbuilds-users] libbonobo-2.32.1 fails to build In-Reply-To: References: <55FD2D5B.406@gmail.com> Message-ID: <55FD4A76.4060209@gmail.com> On 19/09/15 13:09, Ryan P.C. McQuen wrote: > > I'm running almost 14.1. I wonder why Willy can compile properly and > I cannot. > > > > Two things that come to my mind are: > > automake-1.14.1-noarch-1_cslack > > make-3.82-x86_64-5_cslack > > > > That is I have newer versions of make and automake (taken from > -current some time ago). > > And your error showed that automake was failing, you do realize that > current is not officially supported? Have you tried Ponce's repo? I know perfectly that -current is not supported. I didn't remember that I upgraded automake, but I'm yet to check if automake is the problem here. I didn't try Ponce's repo: I actually don't know his repo and at the moment I don't see the reason to use it. Why do you suggest it? > > https://github.com/Ponce/slackbuilds > > Also, why did this thread get duplicated? What do you mean? -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Sat Sep 19 13:02:25 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 19 Sep 2015 20:02:25 +0700 Subject: [Slackbuilds-users] Updates - 20150919.1 Message-ID: <55FD5CE1.3070500@slackbuilds.org> Sat Sep 19 12:50:32 UTC 2015 academic/Xyce: Added (Xyce Parallel Electronic Simulator). academic/galculator: Updated for version 2.1.4. audio/gmusicbrowser: Updated for version 1.1.14. audio/pulseaudio: Make bash completion script posix friendly. audio/sbc: Added (Bluetooth low-complexity, subband codec). audio/tta: Added (TTA lossless audio codec). audio/ttaenc: Updated for version 3.4.1. desktop/ede: Fix build with jam. desktop/faba-icon-theme: Updated for version 4.0.8. desktop/faba-mono-icons: Update README and DEPS. desktop/j4-dmenu-desktop: Updated for version 2.13. desktop/moka-icon-theme: Updated for version 5.0.11. desktop/moka-minimal: Update script. desktop/moka-themes: Update script. desktop/orchis-gtk-theme: Added (Modern GTK Theme for Linux). desktop/xdgmenumaker: Updated for version 0.8. development/eric: Update DOWNLOAD url. development/p4: Updated for version 2015.1.1227227. development/smartgit: Updated for version 7.0.2. development/wheel: Updated for version 0.25.0. games/alephone: Updated for version 20150620. games/chocolate-doom: Updated for version 2.2.1. games/chocolate_duke3D: Updated for version dd8db65. games/freeorion: Updated for version 0.4.5. games/marathon-data: Updated for version 20150620. games/marathon-infinity-data: Updated for version 20150620. games/marathon2-data: Updated for version 20150620. games/pybik: Added (puzzle game). games/qstat: Updated for version 8a7b2d9. games/xroar: Updated for version 0.33.2. gis/pdal: Updated for version 1.0.1. graphics/dia: Updated for version 0.97.3 + new maintainer. graphics/grafx2: Added (256-color bitmap paint program). graphics/openimageio: Updated for version 1.5.19. haskell/hscolour: Updated for version 1.23. libraries/DevIL: Builts ILU and ILUT. libraries/botocore: Updated for version 1.2.3. libraries/discogs-client: Updated for version 2.2.1. libraries/dropbox-python: Updated for version 3.27. libraries/jbig2dec: Updated for version 0.12, updated HOMEPAGE. libraries/libffado: Update DOWNLOAD url. libraries/libgme: Added (a video game music library). libraries/libharu: Added (library for generating PDF files). libraries/libva-intel-driver: Updated for version 1.6.1. libraries/pyPEG2: Added (simple intrinsic parser interpreter). libraries/qt5: Updated for version 5.5.0. libraries/trilinos: Downgraded for version 11.10.2. libraries/unixODBC: Updated for version 2.3.4. misc/jstock: Updated for version 1.0.7.10. multimedia/ExMplayer: Updated for version 5.0.1. multimedia/Mopidy: Updated for version 1.1.1. multimedia/lives: Updated for version 2.4.2. multimedia/whistle: Added (ncurses audio player). network/awscli: Updated for version 1.8.5. network/bmon: Updated for version 3.8. network/flexget: Updated for version 1.2.352. network/sftp-cloudfs: Added (SFTP interface). network/sphinx: Updated for version 2.2.10. network/teamviewer: Updated for version 10.0.46203. network/vivaldi: Updated for version 1.0.275.3_1. network/weathercli: Update script. network/youtube-dl: Updated for version 2015.09.09. office/JabRef: Update DOWNLOAD url. office/MasterPDFEditor: Updated for version 3.4.03. office/fbpdf: Fix build with mupdf-1.7a. office/mupdf: Fix build with jbig2dec-0.12 office/texmacs: Updated for version 1.99.2. office/texmaker: Fix for Qt 5.5.x and newer. office/texstudio: Updated for version 2.10.0. office/zathura-pdf-mupdf: Updated for version 0.2.8. perl/perl-Sidef: Updated for version 0.10. perl/perl-TeX-Hyphen: Added (hyphenate words using TeX's patterns). perl/perl-extutils-makemaker: Updated for version 7.10. python/pymysql: Updated for version 0.6.6. python/pytest: Updated for version 2.7.3. python/python-future: Updated for version 0.15.2. python/python-keyring: Added (Python keyring library). python/python-requests-kerberos: Added (authentication handler). python/regex: Updated for version 2015.09.15. python/selenium: Updated for version 2.47.3. system/Iosevka: Updated for version 0.1.11. system/fio: Updated for version 2.2.10. system/goaccess: Updated for version 0.9.4. system/mongo-tools: Updated for version 3.1.7. system/mongodb: Updated for version 3.0.6. system/monitorix: Updated for version 3.8.0. system/ofono: Added (open source telephony). system/refind: Updated for version 0.9.1. system/s3ql: Updated for vesion 2.15. system/scanmem: Updated for version 0.15.2. system/sdl-jstest: Updated for version 20150806git. system/slpkg: Updated for version 2.9.1. system/spl-solaris: Updated for version 0.6.5. system/sysdig: Fix building against newer jsoncpp. system/trmaid: Updated for version 0.5.7. system/zfs-on-linux: Updated for version 0.6.5. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Sat Sep 19 13:15:59 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 19 Sep 2015 15:15:59 +0200 Subject: [Slackbuilds-users] Prosody vs. SSL/TLS Message-ID: <55FD600F.5030505@microlinux.fr> Hi, I'm currently playing with Prosody (XMPP server) on a sandbox server. As far as I can tell, the default configuration (prosody.SlackBuild on SBo) doesn't allow secure (SSL/TLS) connections. Correct me if I'm wrong. My first attempt was to simply build the listed dependencies and the Prosody package. I had to manually add/configure some stuff, like adding a PID file and setting some permissions. Logfiles came in handy for this. Curiously enough, I can't create an account on Pidgin. He simply won't accept my self-signed certificate for my domain (slackbox.fr). I understand Pidgin had a problem with that up to version 2.10.10, but that was officially corrected with 2.10.11 (which is what I'm running). I took a peek in prosody.SlackBuild and in the source code. I ran ./configure --help | less, and here's an option to activate SSL: --with-ssl=LIB The name of the SSL to link with. Default is crypto This option is nowhere to be found in the SlackBuild, which makes me wonder if SSL support is built in or not. Unfortunately, ./configure output doesn't say anything about it. Any suggestions? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Sat Sep 19 13:20:27 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 19 Sep 2015 15:20:27 +0200 Subject: [Slackbuilds-users] Prosody vs. SSL/TLS In-Reply-To: <55FD600F.5030505@microlinux.fr> References: <55FD600F.5030505@microlinux.fr> Message-ID: <55FD611B.9040405@microlinux.fr> Le 19/09/2015 15:15, Nicolas Kovacs a ?crit : > My first attempt was to simply build the listed dependencies and the > Prosody package. An important side remark to this. Once I configured Prosody and tried to run the demon, it complained about a missing LuaSEC component. So I installed the luasec package and rebuilt Prosody. Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From atelszewski at gmail.com Sat Sep 19 13:19:48 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 19 Sep 2015 15:19:48 +0200 Subject: [Slackbuilds-users] libbonobo-2.32.1 fails to build In-Reply-To: <55FD4A76.4060209@gmail.com> References: <55FD2D5B.406@gmail.com> <55FD4A76.4060209@gmail.com> Message-ID: <55FD60F4.2090804@gmail.com> On 19/09/15 13:43, Andrzej Telszewski wrote: > On 19/09/15 13:09, Ryan P.C. McQuen wrote: >> > I'm running almost 14.1. I wonder why Willy can compile properly and >> I cannot. >> > >> > Two things that come to my mind are: >> > automake-1.14.1-noarch-1_cslack >> > make-3.82-x86_64-5_cslack >> > >> > That is I have newer versions of make and automake (taken from >> -current some time ago). >> >> And your error showed that automake was failing, you do realize that >> current is not officially supported? Have you tried Ponce's repo? > > > I didn't remember that I upgraded automake, but I'm yet to check if > automake is the problem here. Well, sorry for the mess. It was the newer automake that was preventing the libbonobo from compiling. -- Best regards, Andrzej Telszewski From rshepard at appl-ecosys.com Sat Sep 19 14:40:49 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 19 Sep 2015 07:40:49 -0700 (PDT) Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 Message-ID: I tried (three times) to build qgis-2.10.1 in order to upgrade from -2.4.0. But, there are errors that I don't think I can fix here. A week ago I wrote the maintainer but have not received a response. Dependencies -- at least for the 2.4.0 version -- are installed as that was built using the SlackBuilds script. If prerequisite libraries needed updating, sbopkg would have picked them up. The last few errors and the results: CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsCodeEditorSQL[_ZTV16QgsCodeEditorSQL]+0xf8): undefined reference to `QsciScintilla::findFirst(QString const&, bool, bool, bool, bool, bool, int, int, bool, bool)' CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsCodeEditorSQL[_ZTV16QgsCodeEditorSQL]+0x154): undefined reference to `QsciScintilla::replaceSelectedText(QString const&)' CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsCodeEditorSQL[_ZTV16QgsCodeEditorSQL]+0x17c): undefined reference to `QsciScintilla::setAutoCompletionUseSingle(QsciScintilla::AutoCompletionUseSingle)' collect2: error: ld returned 1 exit status make[2]: *** [output/lib/libqgis_gui.so.2.10.1] Error 1 make[2]: Leaving directory /tmp/SBo/qgis-2.10.1' make[1]: *** [src/gui/CMakeFiles/qgis_gui.dir/all] Error 2 make[1]: Leaving directory /tmp/SBo/qgis-2.10.1' make: *** [all] Error 2 Can you suggest how to fix these errors? TIA, Rich From willysr at slackbuilds.org Sat Sep 19 14:53:49 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 19 Sep 2015 21:53:49 +0700 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: Message-ID: <55FD76FD.6070709@slackbuilds.org> > I tried (three times) to build qgis-2.10.1 in order to upgrade from > -2.4.0. But, there are errors that I don't think I can fix here. A week ago > I wrote the maintainer but have not received a response. > > Dependencies -- at least for the 2.4.0 version -- are installed as that > was built using the SlackBuilds script. If prerequisite libraries needed > updating, sbopkg would have picked them up. > > The last few errors and the results: > > CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsCodeEditorSQL[_ZTV16QgsCodeEditorSQL]+0xf8): > > undefined reference to `QsciScintilla::findFirst(QString const&, bool, > bool, > bool, bool, bool, int, int, bool, bool)' > CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsCodeEditorSQL[_ZTV16QgsCodeEditorSQL]+0x154): > > undefined reference to `QsciScintilla::replaceSelectedText(QString const&)' > CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsCodeEditorSQL[_ZTV16QgsCodeEditorSQL]+0x17c): > > undefined reference to > `QsciScintilla::setAutoCompletionUseSingle(QsciScintilla::AutoCompletionUseSingle)' > > collect2: error: ld returned 1 exit status > make[2]: *** [output/lib/libqgis_gui.so.2.10.1] Error 1 > make[2]: Leaving directory /tmp/SBo/qgis-2.10.1' > make[1]: *** [src/gui/CMakeFiles/qgis_gui.dir/all] Error 2 > make[1]: Leaving directory /tmp/SBo/qgis-2.10.1' > make: *** [all] Error 2 > > Can you suggest how to fix these errors? Have you tried to rebuilt all the prerequisite as well? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From slackbuilds at jaxartes.net Sat Sep 19 15:24:59 2015 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 19 Sep 2015 08:24:59 -0700 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: Message-ID: <2204122.O3FaYDdh2N@wintermute> On September 19, 2015 07:40:49 Rich Shepard wrote: > I tried (three times) to build qgis-2.10.1 in order to upgrade from > -2.4.0. But, there are errors that I don't think I can fix here. A week ago > I wrote the maintainer but have not received a response. Sorry, missed your message. > CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsCo > deEditorSQL[_ZTV16QgsCodeEditorSQL]+0xf8): undefined reference to > `QsciScintilla::findFirst(QString const&, bool, bool, bool, bool, bool, > int, int, bool, bool)' > CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsCo > deEditorSQL[_ZTV16QgsCodeEditorSQL]+0x154): undefined reference to > `QsciScintilla::replaceSelectedText(QString const&)' > CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsC > odeEditorSQL[_ZTV16QgsCodeEditorSQL]+0x17c): undefined reference to > `QsciScintilla::setAutoCompletionUseSingle(QsciScintilla::AutoCompletionUse > Single)' collect2: error: ld returned 1 exit status > make[2]: *** [output/lib/libqgis_gui.so.2.10.1] Error 1 > make[2]: Leaving directory /tmp/SBo/qgis-2.10.1' > make[1]: *** [src/gui/CMakeFiles/qgis_gui.dir/all] Error 2 > make[1]: Leaving directory /tmp/SBo/qgis-2.10.1' > make: *** [all] Error 2 Often the actual error is not right at the end. Can you provide the entire build log? Also, what version of Slackware are you using? If I recall correctly, some of your previous build issues have been due to a mix of packages from different Slackware versions and this certainly could be the case here too. Ben From baildon.research at googlemail.com Sat Sep 19 15:31:41 2015 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 19 Sep 2015 16:31:41 +0100 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: Message-ID: > Dependencies -- at least for the 2.4.0 version -- are installed as that > was built using the SlackBuilds script. If prerequisite libraries needed > updating, sbopkg would have picked them up. > > The last few errors and the results: > > CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsCodeEditorSQL[_ZTV16QgsCodeEditorSQL]+0xf8): > undefined reference to `QsciScintilla::findFirst(QString const&, bool, bool, > bool, bool, bool, int, int, bool, bool)' > CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsCodeEditorSQL[_ZTV16QgsCodeEditorSQL]+0x154): > undefined reference to `QsciScintilla::replaceSelectedText(QString const&)' > CMakeFiles/qgis_gui.dir/moc_qgscodeeditorsql.cxx.o:(.data.rel.ro._ZTV16QgsCodeEditorSQL[_ZTV16QgsCodeEditorSQL]+0x17c): > undefined reference to > `QsciScintilla::setAutoCompletionUseSingle(QsciScintilla::AutoCompletionUseSingle)' > collect2: error: ld returned 1 exit status > make[2]: *** [output/lib/libqgis_gui.so.2.10.1] Error 1 > make[2]: Leaving directory /tmp/SBo/qgis-2.10.1' > make[1]: *** [src/gui/CMakeFiles/qgis_gui.dir/all] Error 2 > make[1]: Leaving directory /tmp/SBo/qgis-2.10.1' > make: *** [all] Error 2 Are you running -current? If so, *please* say so up front. The QScintilla package in -current was updated on 14th August. Anything you built before then that uses QScintilla will have linked the old QScintilla, and will need to be rebuilt. sbopkg won't show this, indeed to the best of my knowledge, none of the various package building tools will show this. That's life with -current. The error message is a fairly clear indication that this is your problem, so rebuild all qgis's deps. But I could be wrong. -D. From info at microlinux.fr Sat Sep 19 15:52:17 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 19 Sep 2015 17:52:17 +0200 Subject: [Slackbuilds-users] Prosody vs. SSL/TLS In-Reply-To: <55FD611B.9040405@microlinux.fr> References: <55FD600F.5030505@microlinux.fr> <55FD611B.9040405@microlinux.fr> Message-ID: <55FD84B1.3000509@microlinux.fr> Le 19/09/2015 15:20, Nicolas Kovacs a ?crit : > An important side remark to this. Once I configured Prosody and tried to > run the demon, it complained about a missing LuaSEC component. So I > installed the luasec package and rebuilt Prosody. After some more experimenting, I found out there's actually a problem with the Pidgin client, and not with Prosody. This being said, I think it's safe to add luasec to Prosody's dependencies, since it's needed for encryption. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From rshepard at appl-ecosys.com Sat Sep 19 16:16:27 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 19 Sep 2015 09:16:27 -0700 (PDT) Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: <55FD76FD.6070709@slackbuilds.org> References: <55FD76FD.6070709@slackbuilds.org> Message-ID: On Sat, 19 Sep 2015, Willy Sudiarto Raharjo wrote: > Have you tried to rebuilt all the prerequisite as well? Willy, No. But, I will do this. Rich From rshepard at appl-ecosys.com Sat Sep 19 16:18:00 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 19 Sep 2015 09:18:00 -0700 (PDT) Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: Message-ID: On Sat, 19 Sep 2015, David Spencer wrote: > Are you running -current? > If so, *please* say so up front. 14.1. > The QScintilla package in -current was updated on 14th August. > Anything you built before then that uses QScintilla will have linked > the old QScintilla, and will need to be rebuilt. Hmm-m. OK. Rich From rshepard at appl-ecosys.com Sat Sep 19 16:35:42 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 19 Sep 2015 09:35:42 -0700 (PDT) Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: Message-ID: On Sat, 19 Sep 2015, Rich Shepard wrote: >> The QScintilla package in -current was updated on 14th August. >> Anything you built before then that uses QScintilla will have linked >> the old QScintilla, and will need to be rebuilt. > > Hmm-m. OK. The version installed here is: Mar 9 2014 QScintilla-2.6.1-i486-4. I'll check other dependencies. Rich From rshepard at appl-ecosys.com Sat Sep 19 16:44:24 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 19 Sep 2015 09:44:24 -0700 (PDT) Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: <2204122.O3FaYDdh2N@wintermute> References: <2204122.O3FaYDdh2N@wintermute> Message-ID: On Sat, 19 Sep 2015, Benjamin Trigona-Harany wrote: > Often the actual error is not right at the end. Can you provide the entire > build log? Benjamin, Where do I find that? I don't see a log in /tmp/SBo/qgis-2.10.1/, /tmp/SBo/package-qgis/, or elsewhere. > Also, what version of Slackware are you using? 14.1 Rich From rshepard at appl-ecosys.com Sat Sep 19 16:45:57 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 19 Sep 2015 09:45:57 -0700 (PDT) Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: <55FD76FD.6070709@slackbuilds.org> References: <55FD76FD.6070709@slackbuilds.org> Message-ID: On Sat, 19 Sep 2015, Willy Sudiarto Raharjo wrote: > Have you tried to rebuilt all the prerequisite as well? They're all the current versions: QScintilla-2.6.1-i486-4 libspatialindex-1.7.1-i486-1_SBo qwt-6.0.2-i486-1_SBo psycopg2-2.5.3-i486-1_SBo gdal-1.11.2-i486-1_SBo numpy-1.9.1-i486-1_SBo libspatialite-4.2.0-i486-1_SBo Rich From slackbuilds at jaxartes.net Sat Sep 19 16:51:34 2015 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 19 Sep 2015 09:51:34 -0700 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: <2204122.O3FaYDdh2N@wintermute> Message-ID: <3921893.Rd6L4CFRKc@wintermute> On September 19, 2015 09:44:24 Rich Shepard wrote: > On Sat, 19 Sep 2015, Benjamin Trigona-Harany wrote: > > Often the actual error is not right at the end. Can you provide the entire > > build log? > > Benjamin, > > Where do I find that? I don't see a log in /tmp/SBo/qgis-2.10.1/, > /tmp/SBo/package-qgis/, or elsewhere. It's in /var/logs/sbopkg/sbopkg-build-log. You'll need to trim it down since it's probably grown quite large (or you can delete the file and then just run the QGIS build once). From thomas at beingboiled.info Sat Sep 19 18:08:35 2015 From: thomas at beingboiled.info (Thomas Morper) Date: Sat, 19 Sep 2015 20:08:35 +0200 (CEST) Subject: [Slackbuilds-users] Prosody vs. SSL/TLS In-Reply-To: <55FD84B1.3000509@microlinux.fr> References: <55FD600F.5030505@microlinux.fr> <55FD611B.9040405@microlinux.fr> <55FD84B1.3000509@microlinux.fr> Message-ID: On Sat, 19 Sep 2015, Nicolas Kovacs wrote: > This being said, I think it's safe to add luasec to Prosody's > dependencies, since it's needed for encryption. Technically the *.info is correct as luasec is an optional depedency and Prosody will happily build and run without it. However, unless you're running an isolated server Prosody is pretty much useless without encryption as TLS has become mandatory for S2S connections more than a year ago. Unfortunately the SlackBuild hasn't been maintained for longer than that and I wouldn't recommend to use it as it is. Prosody versions after 0.9.4 have improved encryption and fix several bugs, one interoperability issue and one CVE. -- From rshepard at appl-ecosys.com Sat Sep 19 18:37:47 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 19 Sep 2015 11:37:47 -0700 (PDT) Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: <3921893.Rd6L4CFRKc@wintermute> References: <2204122.O3FaYDdh2N@wintermute> <3921893.Rd6L4CFRKc@wintermute> Message-ID: On Sat, 19 Sep 2015, Benjamin Trigona-Harany wrote: > It's in /var/logs/sbopkg/sbopkg-build-log. I was thinking it would be similar to config.log in the build directory. > You'll need to trim it down since it's probably grown quite large (or you > can delete the file and then just run the QGIS build once). This is interesting. I deleted the 3+M of the log file since July 2011 and re-ran the qgis slackbuild script. Failed the same way after 20 minutes, but there's no log file in /var/log/sbopkg/. Restored the file from last night's backup. It ends with entries from a week ago. Nothing from today. The entry for qgis reads: qgis: MD5SUM check for qgis-2.10.1.tar.bz2 ... OK Error occurred with build. Please check the log. This is strange as that entry is in sbopkg-build-log. Rich From info at microlinux.fr Sun Sep 20 13:44:42 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Sun, 20 Sep 2015 15:44:42 +0200 Subject: [Slackbuilds-users] libtorrent and cppunit Message-ID: <55FEB84A.6090004@microlinux.fr> Hi, I just built libtorrent 0.9.4 on Slackware 14.1. During ./configure, it complains about a missing cppunit. I suggest this package to be added to the list of dependencies. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Sun Sep 20 14:53:10 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 20 Sep 2015 21:53:10 +0700 Subject: [Slackbuilds-users] libtorrent and cppunit In-Reply-To: <55FEB84A.6090004@microlinux.fr> References: <55FEB84A.6090004@microlinux.fr> Message-ID: <55FEC856.4040005@slackbuilds.org> > I just built libtorrent 0.9.4 on Slackware 14.1. During ./configure, it > complains about a missing cppunit. I suggest this package to be added to > the list of dependencies. It works without cppunit here libsigc++: MD5SUM check for libsigc++-2.2.11.tar.xz ... OK Building package libsigc++-2.2.11-x86_64-1_SBo.tgz ... OK Installing package libsigc++-2.2.11-x86_64-1_SBo.tgz ... OK libtorrent: MD5SUM check for libtorrent-0.13.4.tar.gz ... OK Building package libtorrent-0.13.4-x86_64-2_SBo.tgz ... OK Installing package libtorrent-0.13.4-x86_64-2_SBo.tgz ... OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Sun Sep 20 15:20:41 2015 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 20 Sep 2015 16:20:41 +0100 Subject: [Slackbuilds-users] libtorrent and cppunit In-Reply-To: <55FEC856.4040005@slackbuilds.org> References: <55FEB84A.6090004@microlinux.fr> <55FEC856.4040005@slackbuilds.org> Message-ID: >> I just built libtorrent 0.9.4 on Slackware 14.1. 0.9.4??? Do you mean rtorrent, not libtorrent, which is version 0.13.4? For both libtorrent and rtorrent, the configure script prints this: checking for cppunit-config... no checking for Cppunit - version >= 1.9.6... no But that's not an error. cppunit is for unit testing. It builds fine without cppunit. > libsigc++: > MD5SUM check for libsigc++-2.2.11.tar.xz ... OK > Building package libsigc++-2.2.11-x86_64-1_SBo.tgz ... OK > Installing package libsigc++-2.2.11-x86_64-1_SBo.tgz ... OK You might want to regenerate your queue files Willy, you dropped the libsigc++ dep back in February :-) Tarra -D. From willysr at slackbuilds.org Sun Sep 20 15:25:03 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 20 Sep 2015 22:25:03 +0700 Subject: [Slackbuilds-users] libtorrent and cppunit In-Reply-To: References: <55FEB84A.6090004@microlinux.fr> <55FEC856.4040005@slackbuilds.org> Message-ID: <55FECFCF.4070300@slackbuilds.org> > You might want to regenerate your queue files Willy, you dropped the > libsigc++ dep back in February :-) Hm.. i always ran sqg -a after public update sqg should have overwriten the old queue files, but i still got the old dep. Looks like i will have to rebuild all queue Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From citizen.anon.x at gmail.com Sun Sep 20 16:41:11 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Sun, 20 Sep 2015 12:41:11 -0400 Subject: [Slackbuilds-users] shorewall-core update Message-ID: Downloaded the slackbuild, checked build version against available versions. Newer version 4.6.13.1 Listed corrections http://baltimore.shorewall.net/pub/4.6/shorewall-4.6.13/known_problems.txt 1) On systems running Upstart, shorewall-init cannot reliably secure the firewall before interfaces are brought up. 2) When one or more chain names are given in a 'reset' command, the command fails. Corrected in Shorewall 4.6.13.1 3) The Tinc macro and tinc entries in the tunnels file only enable the UDP data connection; they do not enable the TCP meta-connection. Corrected in Shorewall 4.6.13.1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at microlinux.fr Sun Sep 20 17:28:34 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Sun, 20 Sep 2015 19:28:34 +0200 Subject: [Slackbuilds-users] libtorrent and cppunit In-Reply-To: References: <55FEB84A.6090004@microlinux.fr> <55FEC856.4040005@slackbuilds.org> Message-ID: <55FEECC2.2010309@microlinux.fr> Le 20/09/2015 17:20, David Spencer a ?crit : > 0.9.4??? > Do you mean rtorrent, not libtorrent, which is version 0.13.4? > > For both libtorrent and rtorrent, the configure script prints this: > checking for cppunit-config... no > checking for Cppunit - version >= 1.9.6... no > But that's not an error. cppunit is for unit testing. It builds fine > without cppunit. I guess I found the culprit. The SBo script doesn't use vanilla libtorrent and rtorrent source, but a different tarball from some weird Fedora mirror. I just built libtorrent 0.13.6 and rtorrent 0.9.6 from the author's download site on Github (release tarballs), and they work differently. You have to launch ./autogen.sh before ./configure, and the latter complains indeed about a missing cppunit. Why not use vanilla tarballs for these? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From slackbuilds at jaxartes.net Sun Sep 20 17:35:25 2015 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sun, 20 Sep 2015 10:35:25 -0700 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: <3921893.Rd6L4CFRKc@wintermute> Message-ID: <3380416.7Vibuj8Ij9@wintermute> On September 19, 2015 11:37:47 Rich Shepard wrote: > This is interesting. I deleted the 3+M of the log file since July 2011 > and re-ran the qgis slackbuild script. Failed the same way after 20 > minutes, but there's no log file in /var/log/sbopkg/. Restored the file > from last night's backup. It ends with entries from a week ago. Nothing > from today. You may just need to quit sbopkg, restart it and then run the build again. Failing that, can you check /etc/sbopkg/sbopkg.conf to ensure what the log file location hasn't been changed? From baildon.research at googlemail.com Sun Sep 20 18:02:03 2015 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 20 Sep 2015 19:02:03 +0100 Subject: [Slackbuilds-users] libtorrent and cppunit In-Reply-To: <55FEECC2.2010309@microlinux.fr> References: <55FEB84A.6090004@microlinux.fr> <55FEC856.4040005@slackbuilds.org> <55FEECC2.2010309@microlinux.fr> Message-ID: > I guess I found the culprit. The SBo script doesn't use vanilla > libtorrent and rtorrent source, but a different tarball from some weird > Fedora mirror. [...] > Why not use vanilla tarballs for these? If you look at the git history you will see that those *are* the exact original vanilla tarballs. http://slackbuilds.org/cgit/slackbuilds/log/libraries/libtorrent http://slackbuilds.org/cgit/slackbuilds/commit/libraries/libtorrent?id=5bf1f14506fcfc868f1e4a1f07c87eb90ea52934 http://slackbuilds.org/cgit/slackbuilds/log/network/rtorrent http://slackbuilds.org/cgit/slackbuilds/commit/network/rtorrent?id=b1c28f6a34f677e5c3cf32d90eb6f0ed5b99e83c As you can see the md5sums are unchanged, those tarballs are exactly the same as originally on the author's site. No doubt this was done because the author removed the original tarballs from the original tarball's download site. The author has every right to do that, but it is a massive pain for everyone. Thanks to Edinaldo and Willy for finding alternative downloads and fixing the .info files. > I just built libtorrent 0.13.6 and rtorrent 0.9.6 from the author's > download site on Github (release tarballs), and they work differently. > You have to launch ./autogen.sh before ./configure, and the latter > complains indeed about a missing cppunit. So you've built newer versions than the SlackBuilds support at the moment. These kinds of changes from upstream are routine. No doubt when the SlackBuilds are updated the maintainer will take those changes into account. Thanks -D. From didier at slint.fr Sun Sep 20 18:19:17 2015 From: didier at slint.fr (Didier Spaier) Date: Sun, 20 Sep 2015 20:19:17 +0200 Subject: [Slackbuilds-users] libtorrent and cppunit In-Reply-To: References: <55FEB84A.6090004@microlinux.fr> <55FEC856.4040005@slackbuilds.org> <55FEECC2.2010309@microlinux.fr> Message-ID: <55FEF8A5.4040608@slint.fr> On 20/09/2015 20:02, David Spencer wrote: > As you can see the md5sums are unchanged, those tarballs are exactly > the same as originally on the author's site. No doubt this was done > because the author removed the original tarballs from the original > tarball's download site. The author has every right to do that, but > it is a massive pain for everyone. Thanks to Edinaldo and Willy for > finding alternative downloads and fixing the .info files. Oftentimes RH/Fedora or Debian host orphans and I am grateful they do. Only issue: they often both store it and it can be hard hard at times to know which maintainer consider oneself upstream. As a result some bugs can be fixed on a repo but not the other (and some patches can be applied by one distribution but not the other). As an example a patch to link newt to the bidi library was discarded by Fedora because it caused an issue with their installer, but is applied by Debian to allow bidi in dialog that they use in their text installer, e.g. for a mix of English and Arabic. Cheers, Didier From edps.mundognu at gmail.com Sun Sep 20 18:54:01 2015 From: edps.mundognu at gmail.com (Edinaldo) Date: Sun, 20 Sep 2015 15:54:01 -0300 Subject: [Slackbuilds-users] libtorrent and cppunit Message-ID: In this question... the Fedora repository is more reliable and they do not rename the source packages. Before open old thread about sources of rtorrent and libtorrent, i went to the Debian repos, but the md5sums did not coincide, and still then... only rtorrent have the same md5: http://http.debian.net/debian/pool/main/r/rtorrent/rtorrent_0.9.4.orig.tar.gz http://http.debian.net/debian/pool/main/libt/libtorrent/libtorrent_0.13.4.orig.tar.gz md5sum rtorrent_0.9.4.orig.tar.gz fd9490a2ac67d0fa2a567c6267845876 rtorrent_0.9.4.orig.tar.gz md5sum libtorrent_0.13.4.orig.tar.gz 82ea0fc99736fe32c527e7a409790cd2 libtorrent_0.13.4.orig.tar.gz In SlackBuilds and Fedora repo: MD5SUM="fd9490a2ac67d0fa2a567c6267845876" MD5SUM="e82f380a9d4b55b379e0e73339c73895" My suggestion is: use the Fedora repositories whenever possible. Debian repositories are very good to look for patches, diffs, etc. From citizen.anon.x at gmail.com Sun Sep 20 19:42:04 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Sun, 20 Sep 2015 15:42:04 -0400 Subject: [Slackbuilds-users] shorewall-core Message-ID: disregard previous update request, thx -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at microlinux.fr Sun Sep 20 21:45:29 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Sun, 20 Sep 2015 23:45:29 +0200 Subject: [Slackbuilds-users] libtorrent and cppunit In-Reply-To: <55FEF8A5.4040608@slint.fr> References: <55FEB84A.6090004@microlinux.fr> <55FEC856.4040005@slackbuilds.org> <55FEECC2.2010309@microlinux.fr> <55FEF8A5.4040608@slint.fr> Message-ID: <55FF28F9.2090704@microlinux.fr> Le 20/09/2015 20:19, Didier Spaier a ?crit : > Oftentimes RH/Fedora or Debian host orphans and I am grateful they do. I understand, but neither libtorrent nor rtorrent are orphaned. They've both been updated less than three weeks ago. https://github.com/rakshasa/libtorrent/releases https://github.com/rakshasa/rtorrent/releases Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From edps.mundognu at gmail.com Sun Sep 20 21:45:34 2015 From: edps.mundognu at gmail.com (Edinaldo) Date: Sun, 20 Sep 2015 18:45:34 -0300 Subject: [Slackbuilds-users] libtorrent and cppunit Message-ID: Are new versions for libtorrent and rtorrent in: http://rakshasa.github.io/rtorrent/ and: https://github.com/rakshasa/libtorrent/releases https://github.com/rakshasa/rtorrent/releases But MD5s are differents for both. -------------------------------- I get sources from http://rakshasa.github.io/rtorrent http://rtorrent.net/downloads/libtorrent-0.13.6.tar.gz http://rtorrent.net/downloads/rtorrent-0.9.6.tar.gz MD5SUMS: 66f18044432a62c006c75f6d0bb4d7dc libtorrent-0.13.6.tar.gz 5e7550f74e382a6245412c615f45444d rtorrent-0.9.6.tar.gz And build both on Slack Current: http://hastebin.com/moboriwuna http://hastebin.com/zahulelacu If someone with Slack 14.1 could test... it would be great! It would be enough to change the versions and MD5SUM and return homepage to: http://rakshasa.github.io/rtorrent/ []'s From artourter at gmail.com Mon Sep 21 12:20:16 2015 From: artourter at gmail.com (Greg' Ar Tourter) Date: Mon, 21 Sep 2015 13:20:16 +0100 Subject: [Slackbuilds-users] shorewall-core update In-Reply-To: References: Message-ID: Hi, This has been on my todo list but I was away for the weekend so postponed it to things to do this week instead. Just to clarify, the first fix does not apply to slackware as we do not have upstart, and shorewall-init is currently not packaged (I have not been using it but have been thinking about bringing it in at some point as it may be useful) While we are talking about shorewall, the new version 5 will be out at some point. However, it seems that a lot has changed in the way it works and is configured. Therefore I was thinking of leaving shorewall 4 for slackware 14.1 and update to version 5 for the next stable release (and maybe bring shorewall-init then). Does that sound acceptable? Or would people would prefer to use it as soon as it is out? Cheers Greg On 20 September 2015 at 17:41, Citizen X wrote: > Downloaded the slackbuild, checked build version > against available versions. > Newer version 4.6.13.1 > Listed corrections > http://baltimore.shorewall.net/pub/4.6/shorewall-4.6.13/known_problems.txt > > 1) On systems running Upstart, shorewall-init cannot reliably secure > the firewall before interfaces are brought up. > > 2) When one or more chain names are given in a 'reset' command, the > command fails. > > Corrected in Shorewall 4.6.13.1 > > 3) The Tinc macro and tinc entries in the tunnels file only enable the > UDP data connection; they do not enable the TCP meta-connection. > > Corrected in Shorewall 4.6.13.1 > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerardo.zamudio at linux.com Sun Sep 20 15:31:49 2015 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Sun, 20 Sep 2015 10:31:49 -0500 Subject: [Slackbuilds-users] Prosody vs. SSL/TLS In-Reply-To: <55FD84B1.3000509@microlinux.fr> References: <55FD600F.5030505@microlinux.fr> <55FD611B.9040405@microlinux.fr> <55FD84B1.3000509@microlinux.fr> Message-ID: <55FED165.5070804@linux.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/19/2015 10:52 AM, Nicolas Kovacs wrote: > Le 19/09/2015 15:20, Nicolas Kovacs a ?crit : >> An important side remark to this. Once I configured Prosody and >> tried to run the demon, it complained about a missing LuaSEC >> component. So I installed the luasec package and rebuilt >> Prosody. > > After some more experimenting, I found out there's actually a > problem with the Pidgin client, and not with Prosody. > > This being said, I think it's safe to add luasec to Prosody's > dependencies, since it's needed for encryption. > > Cheers, > > Niki > Hey Niki, I saw your post on LQ asking for XMPP server suggestions but didn't get a chance to respond. I would have recommended Prosody as well since that's what I run on jabber.com.mx (public server, no landing page yet). I have the packages listed in the .info file from SlackBuilds as well as luasec (SSL/TLS support) and luadbi (SQL support). Those two are listed here: https://prosody.im/doc/depends Client registration with Pidgin 2.10.11 is working fine here, but I am not using a self-signed certificate. The Prosody docs state you can create a self-signed one with their own tool, which may be a good idea for testing. You can also try verifying the proper intermediate certificate is added to the end of your existing certificate file. Note the certificates need to be in PEM format: https://prosody.im/doc/certificates - -- Gerardo Zamudio -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJV/tFlAAoJEPbPpamee1lXZxUQAJSNs0mhhjLuj/2Op76bvYTZ CxXi8Gmvl1q+JpydQu/A/8gUrW63yXsIgMHhX01z+ZQty/u5ZcXAtjnVjVr1MuIs qxyegupb5RjfU01QIoM50TRldQzc1yGoOS543IQlh/kOXp4435QCNhm6QmhCRJwM CEM65lIBXlRHCRjiwU9YgMiK2W9O/vEX7Zu6rOGZEdCfnQ8oY0tsJa12Dr7SBIl6 gnndtUoUGJ6Muo+sU04he4hbyGVckBZGGwZSby+P2Gc5YwfUTc/pynpFU4CPVjR1 Mae0AnPKdQDETlK80NS88S/11IwjZTfRQBgVs7YzW4T4myRVUK8xlwkCC7MQqBVC W5cCl0h3/59Dd5ZQKmpySKaWgT+yFEOsZxLyGe5w/RtHBDFSERuqzQNPlAOA9i0P hDPO3MDvbxQyeOLXmW2Mc8JVJD149zGM+3hCsUYpPq3u744S48W+2+unMW3geNcH 4qAMBx4FwRaoBOifVQt55ZmGNEUeni6qSyzGUi8FORZv5OzbHOwuefmVI5Q8UfIB IGltHzRTEa+BkOBsezLKQckSgW9qKRL4zErF+e+WumlHktQxBD4U5gKXp4ih8yHB LC9Dkjbj97nQtaPx64jjRJO4b3hRxhl2WYMJDTICHEnQYzXEi+oDUzrTlzcWkbHe nsBVkHGwiTuts7CAvIt6 =mGeF -----END PGP SIGNATURE----- From rshepard at appl-ecosys.com Sun Sep 20 20:35:10 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 20 Sep 2015 13:35:10 -0700 (PDT) Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: <3380416.7Vibuj8Ij9@wintermute> References: <3921893.Rd6L4CFRKc@wintermute> <3380416.7Vibuj8Ij9@wintermute> Message-ID: On Sun, 20 Sep 2015, Benjamin Trigona-Harany wrote: > You may just need to quit sbopkg, restart it and then run the build again. > Failing that, can you check /etc/sbopkg/sbopkg.conf to ensure what the log > file location hasn't been changed? Ben, Mea culpa! I tried building qgis outside of sbopkg which explains why there was no sbopkg-build-log file. Unfortunately, I found no other build log file, either. Now I've re-run sbopkg and selected qgis as the only package to build. The log file is attached. (I've trimmed the list of unpacked files.) The error seems to be on line 32 because the sip module is too new for PyQt4.Qsci. Interesting. Seems to me the fix is to have PyQt4.Qsci accept a newer sip version. Thanks, Rich -------------- next part -------------- A non-text attachment was scrubbed... Name: sbopkg-build-log Type: application/octet-stream Size: 1749724 bytes Desc: URL: From rshepard at appl-ecosys.com Wed Sep 23 14:41:12 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 23 Sep 2015 07:41:12 -0700 (PDT) Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: Message-ID: On Sat, 19 Sep 2015, David Spencer wrote: > Are you running -current? > If so, *please* say so up front. Again, it't 14.1. > The error message is a fairly clear indication that this is your > problem, so rebuild all qgis's deps. > But I could be wrong. Been there; done that. Rich From citizen.anon.x at gmail.com Wed Sep 23 21:32:18 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Wed, 23 Sep 2015 17:32:18 -0400 Subject: [Slackbuilds-users] Frostwire Update Message-ID: Frostwire is up to version 6.1.4, however, on both the main site and the sourceforge site, there did not seem to be a 32bit client. PRGNAM="frostwire" VERSION="6.1.4" HOMEPAGE="http://www.frostwire.com/" DOWNLOAD_x86_64=" http://dl3.frostwire.com/frostwire/6.1.4/frostwire-6.1.4.x86_64.tar.gz" MD5SUM_x86_64="507960645122b301321699c21af4bd6e" -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Wed Sep 23 22:00:26 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Thu, 24 Sep 2015 08:00:26 +1000 Subject: [Slackbuilds-users] Frostwire Update In-Reply-To: References: Message-ID: <560320FA.6030704@iinet.net.au> On 24/09/15 07:32, Citizen X wrote: > Frostwire is up to version 6.1.4, however, on both the main site and the > sourceforge site, there did not seem to be a 32bit client. > > PRGNAM="frostwire" > VERSION="6.1.4" > HOMEPAGE="http://www.frostwire.com/" > DOWNLOAD_x86_64="http://dl3.frostwire.com/frostwire/6.1.4/frostwire-6.1.4.x86_64.tar.gz" > MD5SUM_x86_64="507960645122b301321699c21af4bd6e" Following the development link (http://www.frostwire.com/development), source code is at github and releases at: https://github.com/frostwire/frostwire-desktop/releases Perhaps the SlackBuild could build from the source tarball available there. chris From citizen.anon.x at gmail.com Wed Sep 23 22:17:46 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Wed, 23 Sep 2015 18:17:46 -0400 Subject: [Slackbuilds-users] Frostwire Update In-Reply-To: <560320FA.6030704@iinet.net.au> References: <560320FA.6030704@iinet.net.au> Message-ID: Thanks for the link. The build is maintained by Edward Koenig kingbeowulf at gmail.com. I will attempt a source build and see what happens. Thanks On Wed, Sep 23, 2015 at 6:00 PM, Christoph Willing < chris.willing at iinet.net.au> wrote: > On 24/09/15 07:32, Citizen X wrote: > >> Frostwire is up to version 6.1.4, however, on both the main site and the >> sourceforge site, there did not seem to be a 32bit client. >> >> PRGNAM="frostwire" >> VERSION="6.1.4" >> HOMEPAGE="http://www.frostwire.com/" >> DOWNLOAD_x86_64=" >> http://dl3.frostwire.com/frostwire/6.1.4/frostwire-6.1.4.x86_64.tar.gz" >> MD5SUM_x86_64="507960645122b301321699c21af4bd6e" >> > > > Following the development link (http://www.frostwire.com/development), > source code is at github and releases at: > https://github.com/frostwire/frostwire-desktop/releases > > Perhaps the SlackBuild could build from the source tarball available there. > > chris > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From citizen.anon.x at gmail.com Wed Sep 23 22:54:35 2015 From: citizen.anon.x at gmail.com (Citizen X) Date: Wed, 23 Sep 2015 18:54:35 -0400 Subject: [Slackbuilds-users] Frostwire Update In-Reply-To: References: <560320FA.6030704@iinet.net.au> Message-ID: Building from source fails with major errors. I see why he was using a pre-compiled package. There is far more than below. With the update, there is still only a 64bit package. So I guess that means leave it alone? 100 errors 17 warnings :compileJava FAILED :compileJava (Thread[Daemon worker Thread 2,5,main]) completed. Took 19.301 secs. FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':compileJava'. On Wed, Sep 23, 2015 at 6:17 PM, Citizen X wrote: > Thanks for the link. The build is maintained by Edward Koenig > kingbeowulf at gmail.com. I will attempt a source build and see what happens. > Thanks > > On Wed, Sep 23, 2015 at 6:00 PM, Christoph Willing < > chris.willing at iinet.net.au> wrote: > >> On 24/09/15 07:32, Citizen X wrote: >> >>> Frostwire is up to version 6.1.4, however, on both the main site and the >>> sourceforge site, there did not seem to be a 32bit client. >>> >>> PRGNAM="frostwire" >>> VERSION="6.1.4" >>> HOMEPAGE="http://www.frostwire.com/" >>> DOWNLOAD_x86_64=" >>> http://dl3.frostwire.com/frostwire/6.1.4/frostwire-6.1.4.x86_64.tar.gz" >>> MD5SUM_x86_64="507960645122b301321699c21af4bd6e" >>> >> >> >> Following the development link (http://www.frostwire.com/development), >> source code is at github and releases at: >> https://github.com/frostwire/frostwire-desktop/releases >> >> Perhaps the SlackBuild could build from the source tarball available >> there. >> >> chris >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Thu Sep 24 04:51:03 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Thu, 24 Sep 2015 14:51:03 +1000 Subject: [Slackbuilds-users] Frostwire Update In-Reply-To: References: <560320FA.6030704@iinet.net.au> Message-ID: <56038137.6080002@iinet.net.au> On 24/09/15 08:54, Citizen X wrote: > Building from source fails with major errors. I see why he was using a > pre-compiled package. There is far more than below. With the update, > there is still only a 64bit package. > So I guess that means leave it alone? > > 100 errors > 17 warnings > :compileJava FAILED > :compileJava (Thread[Daemon worker Thread 2,5,main]) completed. Took > 19.301 secs. > > FAILURE: Build failed with an exception. > > * What went wrong: > Execution failed for task ':compileJava'. I built it OK in a 32but VM and it runs, sort of ... It starts up with a configuration wizard at the end of which it crashes with a message that "lib/native/libjlibtorrent.so might have disabled stack guard" with recommendations to fix with "execstack -c" (which didn't work) or to link it with "-z noexecstack" (which I don't know how to do with the gradle build framework that is used). Unfortunately the libjlibtorrent.so file is not built locally but part of the git clone and its unclear how to regenerate it. Interestingly, at http://forum.frostwire.com/viewtopic.php?f=1&t=17512 is a message from one of their developers that "we're going to make it so that the next frostwire releases are 32-bit compatible in Linux once again". Maybe just wait a while ... chris From kingbeowulf at gmail.com Thu Sep 24 08:17:34 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 24 Sep 2015 01:17:34 -0700 Subject: [Slackbuilds-users] Frostwire Update In-Reply-To: <56038137.6080002@iinet.net.au> References: <560320FA.6030704@iinet.net.au> <56038137.6080002@iinet.net.au> Message-ID: <5603B19E.7060707@gmail.com> On 09/23/2015 09:51 PM, Christoph Willing wrote: > On 24/09/15 08:54, Citizen X wrote: >> Building from source fails with major errors. I see why he was using a >> pre-compiled package. There is far more than below. With the update, >> there is still only a 64bit package. >> So I guess that means leave it alone? >> >> 100 errors >> 17 warnings >> :compileJava FAILED >> :compileJava (Thread[Daemon worker Thread 2,5,main]) completed. Took >> 19.301 secs. >> >> FAILURE: Build failed with an exception. >> >> * What went wrong: >> Execution failed for task ':compileJava'. > > I built it OK in a 32but VM and it runs, sort of ... > > It starts up with a configuration wizard at the end of which it crashes > with a message that "lib/native/libjlibtorrent.so might have disabled > stack guard" with recommendations to fix with "execstack -c" (which > didn't work) or to link it with "-z noexecstack" (which I don't know how > to do with the gradle build framework that is used). Unfortunately the > libjlibtorrent.so file is not built locally but part of the git clone > and its unclear how to regenerate it. > > Interestingly, at > http://forum.frostwire.com/viewtopic.php?f=1&t=17512 is a message from > one of their developers that "we're going to make it so that the next > frostwire releases are 32-bit compatible in Linux once again". Maybe > just wait a while ... > > chris > Ugh. Yes, they dropped 32 bit a while back, and have gone Ubuntu Unity centric. I never did get it to compile to my liking on Slack. It looks like libjlibtorrent has its own github repo so you have to build that separately, I think. Anyway, I doubt I'll revisit the issue. I haven't used it in ages. Quite some time ago, I posted in this list that SBo Frostwire maintenance is up for grabs. If anyone wants it, take it, and may the compiles be ever in your favor. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Fri Sep 25 03:41:13 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 25 Sep 2015 13:41:13 +1000 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: <55FD76FD.6070709@slackbuilds.org> Message-ID: <5604C259.2080803@iinet.net.au> On 20/09/15 02:45, Rich Shepard wrote: > On Sat, 19 Sep 2015, Willy Sudiarto Raharjo wrote: > >> Have you tried to rebuilt all the prerequisite as well? > > They're all the current versions: > > QScintilla-2.6.1-i486-4 > libspatialindex-1.7.1-i486-1_SBo > qwt-6.0.2-i486-1_SBo > psycopg2-2.5.3-i486-1_SBo > gdal-1.11.2-i486-1_SBo > numpy-1.9.1-i486-1_SBo > libspatialite-4.2.0-i486-1_SBo > Those are all the current versions in the SBo repo but some of them are out of date and should be updated. Doing so is not entirely straightforward - here are the issues: 1. latest qwt is 6.1.2 (this is where I started since I needed it for a separate project). There is another problem with qwt - it installs its .prf & .pri files in the wrong location (this is due to qwt itself, not the maintainer) so that when building related software, qmake can't find necessary config & installation information about qwt. I'll email the maintainer separately about that. 2. libspatialite is now at 4.3.0a. Actually, wget of 4.2.0 returned "ERROR 404: Not Found.", so this should be updated regardless. 3. freexl is required by libspatialite (not sure why it doesn't appear in the list above) but the version 1.0.0i in the repo is not acceptable to libspatialite-4.3.0a. Latest freexl is 1.0.2 which is good for libspatialite so freexl version should be updated in the repo. 4. qgis itself doesn't immediately like the updated qwt-6.1.2. This is really because it has its own (now outdated) version of qwtpolar software. By configuring qgis not to use its internal qwtpolar and pointing to location of an up to date installed version of qwtpolar, qgis is able to build to completion. However there is no qwtpolar in SBo at the moment. I have a qwtpolar SlackBuild ready to submit (or for someone else to submit/maintain is they want it) but it depends on the changes to qwt mentioned in point 1 above. All these issues are interrelated and should be fixed at roughly the same so that everything will keep working. Actually, its not working right now unless you happen to have an old version of libspatialite handy. I'll email qwt & qgis maintainers about potential changes. Can version updates of libspatialite and freexl be done directly in SBo repo, or will they need updates from maintainers? chris From rshepard at appl-ecosys.com Fri Sep 25 12:32:08 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 25 Sep 2015 05:32:08 -0700 (PDT) Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: <5604C259.2080803@iinet.net.au> References: <55FD76FD.6070709@slackbuilds.org> <5604C259.2080803@iinet.net.au> Message-ID: On Fri, 25 Sep 2015, Christoph Willing wrote: > Those are all the current versions in the SBo repo but some of them are > out of date and should be updated. Doing so is not entirely > straightforward - here are the issues: Chris, Looks like a busy weekend for me. Any working slackbuild scripts or hints on what to move where would be very helpful. > I'll email qwt & qgis maintainers about potential changes. Ben, the qgis maintainer, is unavailable for a bit (new job, moving, out of the country). But, when he settles down he'll get to addressing issues. Thanks very much, Rich From chris.willing at iinet.net.au Fri Sep 25 12:55:18 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 25 Sep 2015 22:55:18 +1000 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: <55FD76FD.6070709@slackbuilds.org> <5604C259.2080803@iinet.net.au> Message-ID: <56054436.7010006@iinet.net.au> On 25/09/15 22:32, Rich Shepard wrote: > On Fri, 25 Sep 2015, Christoph Willing wrote: > >> Those are all the current versions in the SBo repo but some of them are >> out of date and should be updated. Doing so is not entirely >> straightforward - here are the issues: > > Chris, > > Looks like a busy weekend for me. > > Any working slackbuild scripts or hints on what to move where would be > very helpful. > All the changes are in the "new-qwtpolar" branch at: https://github.com/cwilling/slackbuilds/tree/new-qwtpolar If you click on the little "Compare" button (next to "Pull Request" button) immediately above file listing on the right hand side, it'll give you all the changes compared with SBo master branch i.e. updating qwt, freexl & libspatialite, adding qwtpolar and adding external qwtpolar usage to qgis itself. chris From rhintze at gmail.com Fri Sep 25 03:33:50 2015 From: rhintze at gmail.com (Rich-n-Rachel Hintze) Date: Thu, 24 Sep 2015 23:33:50 -0400 Subject: [Slackbuilds-users] Suggestion for asterisk Slackbuild Message-ID: I noticed the "make" line 83 should be moved below section about changing ADDONS (say line 91). Otherwise the changes don't seem to get into the menuselect.makeopts in time. the only other thing I noticed is to exactly match the menuselect.makeopts format maybe add one whitespace character. (this part is likely non-sense but just an observation, don't this it matters but...) suggestion: add space line 83 to end like this (space after mp3) chan_mobile chan_ooh323 format_mp3 /' \ -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Fri Sep 25 13:19:55 2015 From: baildon.research at googlemail.com (David Spencer) Date: Fri, 25 Sep 2015 14:19:55 +0100 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: <5604C259.2080803@iinet.net.au> References: <55FD76FD.6070709@slackbuilds.org> <5604C259.2080803@iinet.net.au> Message-ID: > Actually, its not working right now > unless you happen to have an old version of libspatialite handy Apparently they've moved it to a subdirectory. The md5sum is the same. Willy, could you please do your usual magic? TIA ! libraries/libspatialite/libspatialite.info DOWNLOAD="http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-4.2.0.tar.gz" The SBo versions of everything in qgis's dependencies all work fine together, and qgis builds ok using clean builds of its deps. Rich, any problems you have must be due to nonstandard builds you already have on your system (just like all the other times you've had problems). Upgrading those deps might cause even more problems of this kind in the long run. If you would like to put a log of your problem builds of qgis on pastebin, I'll have a look. Thank Bob nobody has mentioned gdal-2.0.1 yet ;-) -D. From slackbuilds at jaxartes.net Fri Sep 25 14:21:52 2015 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Fri, 25 Sep 2015 07:21:52 -0700 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: <5604C259.2080803@iinet.net.au> References: <5604C259.2080803@iinet.net.au> Message-ID: <4995218.l56nfT1OGn@wintermute> On September 25, 2015 13:41:13 Christoph Willing wrote: > On 20/09/15 02:45, Rich Shepard wrote: > 4. qgis itself doesn't immediately like the updated qwt-6.1.2. This is > really because it has its own (now outdated) version of qwtpolar > software. By configuring qgis not to use its internal qwtpolar and > pointing to location of an up to date installed version of qwtpolar, > qgis is able to build to completion. However there is no qwtpolar in SBo > at the moment. I have a qwtpolar SlackBuild ready to submit (or for > someone else to submit/maintain is they want it) but it depends on the > changes to qwt mentioned in point 1 above. Within the last month, I built QGIS on a fresh Slackware 64 system and none of the proposed changes were required for it to run. Can anyone else confirm that the QGIS SlackBuild as it stands needs any changes? Thanks, Ben From rshepard at appl-ecosys.com Fri Sep 25 16:35:59 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 25 Sep 2015 09:35:59 -0700 (PDT) Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: <55FD76FD.6070709@slackbuilds.org> <5604C259.2080803@iinet.net.au> Message-ID: On Fri, 25 Sep 2015, David Spencer wrote: > Rich, any problems you have must be due to nonstandard builds you already > have on your system (just like all the other times you've had problems). > Upgrading those deps might cause even more problems of this kind in the > long run. If you would like to put a log of your problem builds of qgis on > pastebin, I'll have a look. There are no duplicate or nonstandard builds of anything on this system. All dependencies came from the SBo depository, and the earlier version of qgis built and ran. Rich From willysr at slackbuilds.org Fri Sep 25 16:39:51 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 25 Sep 2015 23:39:51 +0700 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: <55FD76FD.6070709@slackbuilds.org> <5604C259.2080803@iinet.net.au> Message-ID: <560578D7.3010706@slackbuilds.org> > Apparently they've moved it to a subdirectory. The md5sum is the same. > Willy, could you please do your usual magic? TIA ! > libraries/libspatialite/libspatialite.info > DOWNLOAD="http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-4.2.0.tar.gz" Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Fri Sep 25 21:16:52 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 26 Sep 2015 07:16:52 +1000 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: <55FD76FD.6070709@slackbuilds.org> <5604C259.2080803@iinet.net.au> Message-ID: <5605B9C4.7000907@iinet.net.au> On 25/09/15 23:19, David Spencer wrote: >> Actually, its not working right now >> unless you happen to have an old version of libspatialite handy > > Apparently they've moved it to a subdirectory. The md5sum is the same. > Willy, could you please do your usual magic? TIA ! > libraries/libspatialite/libspatialite.info > DOWNLOAD="http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-4.2.0.tar.gz" > From that download directory: libspatialite-4.2.0.tar.gz 25-Jul-2014 14:04 4.0M .... (several other versions) libspatialite-4.3.0a.tar.gz 07-Sep-2015 16:21 4.2M From the freexl download directory at the same site: freexl-1.0.0i.tar.gz 05-Mar-2015 18:36 911K .... freexl-1.0.2.tar.gz 14-Jul-2015 19:09 917K From qwt download site: qwt-6.0.1.tar.bz2 2014-09-17 2.4 MB .... qwt-6.1.2.tar.bz2 2014-12-11 3.5 MB qgis has internal versions of qwtpolar available, 0.1 and 1.0 - lets assume 1.0 is being used. Then, from the qwtpolar download site: qwtpolar-1.0.0.tar.bz2 2011-08-08 414.0 kB .... qwtpolar-1.1.1.tar.bz2 2014-09-19 565.5 kB If we have two collections of software versions that both work, I'd prefer this year's versions not last year's, or earlier, versions. > The SBo versions of everything in qgis's dependencies all work fine > together, and qgis builds ok using clean builds of its deps. Rich, any > problems you have must be due to nonstandard builds you already have > on your system (just like all the other times you've had problems). > Upgrading those deps might cause even more problems of this kind in > the long run. If you would like to put a log of your problem builds of > qgis on pastebin, I'll have a look. When that's done, could we move on to this year's versions please? chris From willysr at slackbuilds.org Fri Sep 25 23:17:45 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 26 Sep 2015 06:17:45 +0700 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: <4995218.l56nfT1OGn@wintermute> References: <5604C259.2080803@iinet.net.au> <4995218.l56nfT1OGn@wintermute> Message-ID: <5605D619.5090107@slackbuilds.org> > Within the last month, I built QGIS on a fresh Slackware 64 system and none of > the proposed changes were required for it to run. Can anyone else confirm that > the QGIS SlackBuild as it stands needs any changes? Finished building qgis from scratch and i can confirm that it works as normal -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Sep 26 03:27:39 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 26 Sep 2015 10:27:39 +0700 Subject: [Slackbuilds-users] Updates - 20150926.1 Message-ID: <560610AB.2030701@slackbuilds.org> Sat Sep 26 03:06:45 UTC 2015 academic/copasi: Updated for version 4.16.104. desktop/LX-Colors-themes: Added (GTK2/GTK3/Openbox themes). desktop/jwm: Updated for version 2.3.2. desktop/perwindowlayoutd: Added (Keeps per window keyboard layout). desktop/plank: Added (Elegant, simple, clean dock). desktop/seafile-gui: Updated for version 4.3.4. desktop/superkey-launch: Updated for version 1.6.3. development/atom: Updated for version 1.0.19. development/kaaedit: Updated for version 0.44.0. development/pyvim: Updated for version 0.0.10. development/qt-creator3: Updated for version 3.5.0. development/rust: Updated for version 1.3.0. development/simulavr: Added (Atmel AVR Family Simulator). development/wheel: Updated for version 0.26.0. games/KAdventure: Fix DOWNLOAD url. games/astromenace: Added patch for newer freetype2. games/instead: Updated for version 2.2.7. games/mgba: Updated for version 0.3.0. games/minetest: Updated for version 0.4.13. games/minetest_game: Updated for version 0.4.13. games/naev: Updated for version 0.6.0. games/vbam: Update README. gis/Fiona: Updated for version 1.6.2. gis/SFCGAL: Updated for version 1.2.0. gis/gdal: Updated for version 1.11.3. graphics/gnofract4d: Update .info and script. libraries/CGAL: Updated for version 4.6.3. libraries/bamf: Added (Window matching library). libraries/botocore: Updated for version 1.2.5. libraries/dropbox-python: Updated for version 3.28. libraries/libjpeg-turbo: Updated for version 1.4.2. libraries/libspatialite: Update DOWNLOAD url. libraries/libwnck3: Added (Window Navigator Construction Kit). libraries/live555: Updated for version 2015.09.24. libraries/php-memcached: Added (PHP extension for memcached). misc/mosquitto: Updated for version 1.4.4. misc/rarcrack: Added (Password cracker for rar archives). multimedia/flashplayer-plugin: Updated for version 11.2.202.521. multimedia/plexmediaserver: Updated for version 0.9.12. multimedia/yarock: Updated for version 1.1.4. network/Flootty: Updated for version 3.1.7. network/awscli: Updated for version 1.8.7. network/ccnet: Updated for version 4.4.0. network/connman: Updated for version 1.30. network/flexget: Updated for version 1.2.354. network/iojs: Updated for version 4.1.1. network/owncloud-server: Updated for version 8.1.3. network/pidgin-opensteamworks: Updated for version 1.6.1. network/seafile-client: Updated for version 4.4.0. network/seafile-server: Updated for version 4.4.0. network/speedtest-cli: Updated for version 0.3.4. network/tor-browser: Updated for version 5.0.3. network/vivaldi: Updated for version 1.0.279.3_1. network/you-get: Updated for version 0.3.35. network/youtube-dl: Updated for version 2015.09.22. network/youtube-upload: Added (YouTube command-line upload utility). office/libreoffice-helppack: Updated for version 5.0.2. office/libreoffice-langpack: Updated for version 5.0.2. office/libreoffice: Updated for version 5.0.2. office/texstudio: Updated for version 2.10.2. perl/perl-Term-ReadLine-Gnu: Updated for version 1.28. python/APScheduler: Updated for version 3.0.3. python/autopep8: Updated for version 1.2.1. python/google-api-python-client: Updated for version 1.5.1. python/jmespath: Updated for version 0.8.0. python/prompt_toolkit: Updated for version 0.52. python/ptpython: Updated for version 0.24. python/purl: Updated for version 1.1. python/python-oauth2client: Added (YouTube CL upload utility). python/python-unicodecsv: Updated for version 0.14.0. python/python-uri-templates: Added (URI Template). python/regex: Updated for version 2015.09.23. system/adobe-source-han-sans-fonts: Updated for version 1.004R. system/fs-uae-arcade: Updated for version 2.6.1. system/fs-uae-launcher: Updated for version 2.6.1. system/fs-uae: Updated for version 2.6.1. system/geoclue: Fix download url. system/gitolite: Fix helper script. system/parallel: Updated for version 20150922. system/pyarchey: Updated for version 0.6.6. system/secure-delete: Update patch. system/slackchlog: Added (Slackware's ChangeLog viewer). system/slpkg: Updated for version 2.9.4. system/spl-solaris: Updated for version 0.6.5.1. system/zfs-on-linux: Updated for version 0.6.5.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Sat Sep 26 08:44:02 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 26 Sep 2015 18:44:02 +1000 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: <5605D619.5090107@slackbuilds.org> References: <5604C259.2080803@iinet.net.au> <4995218.l56nfT1OGn@wintermute> <5605D619.5090107@slackbuilds.org> Message-ID: <56065AD2.8040607@iinet.net.au> On 26/09/15 09:17, Willy Sudiarto Raharjo wrote: >> Within the last month, I built QGIS on a fresh Slackware 64 system and none of >> the proposed changes were required for it to run. Can anyone else confirm that >> the QGIS SlackBuild as it stands needs any changes? > > Finished building qgis from scratch and i can confirm that it works as > normal > Since the download link to the _old_ libspacialite version has been fixed, I can also build the existing qgis from scratch too. Therefore, as things stand, I agree that no changes are needed to the SlackBuild for qgis. However, as I mentioned in my first foray into this thread, I use qwt for another project and the existing version at SBo is an old version which does not meet my needs, whereas the latest available version does, one important difference between the two versions being qt4/qt5 compatibility. When I looked into what impact an update to qwt might have on other SlackBuilds I found a bunch of relevant others that also need updating. I'm just looking for a path to being able to use the latest version of qwt. In order to do that, I have found, tested and described the updates to various qgis build dependencies, as well as the two line addition to qgis.SlackBuild itself that would be required. Having done that, I am somewhat perplexed at the opposition to any change at all. Apart from the satisfaction of being able to build qgis as it is with these heirloom versioned dependencies, can anyone suggest a reason not to update them? If there are no other reasons, can we update them? chris From baildon.research at googlemail.com Sat Sep 26 09:37:56 2015 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 26 Sep 2015 10:37:56 +0100 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: <56065AD2.8040607@iinet.net.au> References: <5604C259.2080803@iinet.net.au> <4995218.l56nfT1OGn@wintermute> <5605D619.5090107@slackbuilds.org> <56065AD2.8040607@iinet.net.au> Message-ID: > However, as I mentioned in my first foray into this thread, I use qwt for > another project and the existing version at SBo is an old version which does > not meet my needs, whereas the latest available version does, one important > difference between the two versions being qt4/qt5 compatibility. When I > looked into what impact an update to qwt might have on other SlackBuilds I > found a bunch of relevant others that also need updating. > > I'm just looking for a path to being able to use the latest version of qwt. > In order to do that, I have found, tested and described the updates to > various qgis build dependencies, as well as the two line addition to > qgis.SlackBuild itself that would be required. Having done that, I am > somewhat perplexed at the opposition to any change at all. With respect, it might feel like opposition, but it's actually a roadmap for how to get where you want to be. (1) Identify all other packages that have qwt as a dependency (2) Test build them all, find fixes for the ones that are broken (3) Contact the maintainers, explain any problems you found with fixes, allow them to do their things in their own ways (4) Where maintainers are unresponsive, consult with this list, if necessary take on long term maintenance obligations yourself That's all work for someone. If you want to be that person, go for it, because when you've finished qwt there's a whole repo that needs exactly this kind of loving. Thanks -D. From contact at jeaye.com Sat Sep 26 02:49:01 2015 From: contact at jeaye.com (jeaye) Date: Sat, 26 Sep 2015 10:49:01 +0800 Subject: [Slackbuilds-users] SBCL looks unmaintained; needs updating Message-ID: <20150926024901.GE14280@jeaye.com> Folks, I just ran into some issues trying to use SBCL which, after some help on freenode, were resolved by updating. After a bit of searching, it seems that there have been *43 releases* since 1.0.50, which is what's currently in SBo. It seems like we're due for an update. With that said, there's a script floating around #lisp, on freenode, which does a brilliant job of bringing in SBCL from source. It's available here: http://plaster.tymoon.eu/view/85 and it worked wonders for me. Cheers, Jeaye From chris.willing at iinet.net.au Sat Sep 26 13:46:36 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 26 Sep 2015 23:46:36 +1000 Subject: [Slackbuilds-users] Build Errors: qgis-2.10.1 In-Reply-To: References: <5604C259.2080803@iinet.net.au> <4995218.l56nfT1OGn@wintermute> <5605D619.5090107@slackbuilds.org> <56065AD2.8040607@iinet.net.au> Message-ID: <5606A1BC.3030502@iinet.net.au> On 26/09/15 19:37, David Spencer wrote: >> However, as I mentioned in my first foray into this thread, I use qwt for >> another project and the existing version at SBo is an old version which does >> not meet my needs, whereas the latest available version does, one important >> difference between the two versions being qt4/qt5 compatibility. When I >> looked into what impact an update to qwt might have on other SlackBuilds I >> found a bunch of relevant others that also need updating. >> >> I'm just looking for a path to being able to use the latest version of qwt. >> In order to do that, I have found, tested and described the updates to >> various qgis build dependencies, as well as the two line addition to >> qgis.SlackBuild itself that would be required. Having done that, I am >> somewhat perplexed at the opposition to any change at all. > > With respect, it might feel like opposition, but it's actually a > roadmap for how to get where you want to be. Sorry if I misjudged the level of enthusiasm :) > (1) Identify all other packages that have qwt as a dependency > (2) Test build them all, find fixes for the ones that are broken > (3) Contact the maintainers, explain any problems you found with > fixes, allow them to do their things in their own ways > (4) Where maintainers are unresponsive, consult with this list, if > necessary take on long term maintenance obligations yourself > > That's all work for someone. If you want to be that person, go for it, > because when you've finished qwt there's a whole repo that needs > exactly this kind of loving. I emailed the relevant maintainers yesterday. I'll wait a week or so for some response before doing anything more on it. chris From info at microlinux.fr Sun Sep 27 10:29:02 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Sun, 27 Sep 2015 12:29:02 +0200 Subject: [Slackbuilds-users] luaexpat Message-ID: <5607C4EE.6000107@microlinux.fr> Hi, luaexpat has a hardcoded 1.2.0 version in the slack-desc, but the current version is 1.3.0. I suggest removing the versioning information from the slack-desc. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Sun Sep 27 13:47:28 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 27 Sep 2015 20:47:28 +0700 Subject: [Slackbuilds-users] luaexpat In-Reply-To: <5607C4EE.6000107@microlinux.fr> References: <5607C4EE.6000107@microlinux.fr> Message-ID: <5607F370.20009@slackbuilds.org> > luaexpat has a hardcoded 1.2.0 version in the slack-desc, but the > current version is 1.3.0. I suggest removing the versioning information > from the slack-desc. Fixed -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From bkirkp at gmail.com Mon Sep 28 16:29:47 2015 From: bkirkp at gmail.com (Bill Kirkpatrick) Date: Mon, 28 Sep 2015 11:29:47 -0500 Subject: [Slackbuilds-users] Orphaning gramps Message-ID: I've decided to orphan gramps. For me, it is easier to run the gramps CD than it is to keep a SlackBuild up to date. Anyone who wants it may have it. Regards, Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: From edps.mundognu at gmail.com Wed Sep 30 12:24:40 2015 From: edps.mundognu at gmail.com (Edinaldo) Date: Wed, 30 Sep 2015 09:24:40 -0300 Subject: [Slackbuilds-users] pyalsaaudio link is broken Message-ID: Hello, link for download pyalsaaudio is broken, on sourceforge site the latest version is 0.5: http://sourceforge.net/projects/pyalsaaudio/files/pyalsaaudio/ But, with MD5SUM i found package with 0.6 version on Fedora host: https://pkgs.fedoraproject.org/repo/pkgs/python-alsaaudio/pyalsaaudio-0.6.tar.gz/94811fc4de883996eac4046d36fe2364/pyalsaaudio-0.6.tar.gz Log: http://hastebin.com/exajotinev Cheers. From info at microlinux.fr Wed Sep 30 12:46:27 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 30 Sep 2015 14:46:27 +0200 Subject: [Slackbuilds-users] Suggestions for Prosody Message-ID: <560BD9A3.9090301@microlinux.fr> Hi, I just built Prosody for one of my public servers. I have two suggestions for the package. 1. Version 0.9.4 is quite outdated. Prosody is currently at 0.9.8. 2. The package is missing an rc.prosody file. I have one in my own SlackBuild: http://www.microlinux.fr/microlinux/server-14.1-source/prosody/ Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From crculver at christopherculver.com Wed Sep 30 13:18:03 2015 From: crculver at christopherculver.com (Christopher Culver) Date: Wed, 30 Sep 2015 16:18:03 +0300 Subject: [Slackbuilds-users] Unable to build qt5 5.5.0 Message-ID: <87k2r8qc50.fsf@aura.christopherculver.com> When I attempt to build qt5 5.5.0 from the SBo Slackbuild, the build fails at the make install stage with the error: can't read /media/BUILD/sbotmp//package-qt5/usr/lib64/pkgconfig/Qt5WebKit.pc: No such file or directory Now, I am invoking qt5 as root as follows: TMP=/media/BUILD/ ./qt5.SlackBuild because I don?t have so much space in /tmp/ and prefer to use another drive for Slackbuilds, but I don?t think that is the problem here ? all other SBo Slackbuilds compile fine. What could be the cause of this error? From willysr at slackbuilds.org Wed Sep 30 15:29:01 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 30 Sep 2015 22:29:01 +0700 Subject: [Slackbuilds-users] pyalsaaudio link is broken In-Reply-To: References: Message-ID: <560BFFBD.40808@slackbuilds.org> > link for download pyalsaaudio is broken, on sourceforge site the latest > version is 0.5: > > http://sourceforge.net/projects/pyalsaaudio/files/pyalsaaudio/ > > But, with MD5SUM i found package with 0.6 version on Fedora host: > > https://pkgs.fedoraproject.org/repo/pkgs/python-alsaaudio/pyalsaaudio-0.6.tar.gz/94811fc4de883996eac4046d36fe2364/pyalsaaudio-0.6.tar.gz Fixed Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From larryhaja at gmail.com Wed Sep 30 15:29:27 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Wed, 30 Sep 2015 08:29:27 -0700 Subject: [Slackbuilds-users] Unable to build qt5 5.5.0 In-Reply-To: <87k2r8qc50.fsf@aura.christopherculver.com> References: <87k2r8qc50.fsf@aura.christopherculver.com> Message-ID: On Wed, Sep 30, 2015 at 6:18 AM, Christopher Culver < crculver at christopherculver.com> wrote: > When I attempt to build qt5 5.5.0 from the SBo Slackbuild, the build > fails at the make install stage with the error: > > can't read > /media/BUILD/sbotmp//package-qt5/usr/lib64/pkgconfig/Qt5WebKit.pc: No > such file or directory > > Now, I am invoking qt5 as root as follows: > > TMP=/media/BUILD/ ./qt5.SlackBuild > > because I don?t have so much space in /tmp/ and prefer to use another > drive for Slackbuilds, but I don?t think that is the problem here > ? all other SBo Slackbuilds compile fine. > > What could be the cause of this error? I'm not sure. Did you run out of space in /media/BUILD? Do you have a full Slackware64 install? --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From crculver at christopherculver.com Wed Sep 30 15:41:26 2015 From: crculver at christopherculver.com (Christopher Culver) Date: Wed, 30 Sep 2015 18:41:26 +0300 Subject: [Slackbuilds-users] Unable to build qt5 5.5.0 References: <87k2r8qc50.fsf@aura.christopherculver.com> Message-ID: <87a8s3rk2h.fsf@aura.christopherculver.com> Larry Hajali writes: > I'm not sure. Did you run out of space in /media/BUILD? No, there are still gigabytes free on the disc with the build directory. > Do you have a full Slackware64 install? Yes. And the last version of qt5 compiled with no problems. It is only this upgrade to 5.5.0 that is giving me the aforementioned error. Christopher Culver From atelszewski at gmail.com Wed Sep 30 15:48:45 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 30 Sep 2015 17:48:45 +0200 Subject: [Slackbuilds-users] Unable to build qt5 5.5.0 In-Reply-To: <87k2r8qc50.fsf@aura.christopherculver.com> References: <87k2r8qc50.fsf@aura.christopherculver.com> Message-ID: <560C045D.1070601@gmail.com> On 30/09/15 15:18, Christopher Culver wrote: > When I attempt to build qt5 5.5.0 from the SBo Slackbuild, the build > fails at the make install stage with the error: > > can't read /media/BUILD/sbotmp//package-qt5/usr/lib64/pkgconfig/Qt5WebKit.pc: No > such file or directory > > Now, I am invoking qt5 as root as follows: > > TMP=/media/BUILD/ ./qt5.SlackBuild > > because I don?t have so much space in/tmp/ and prefer to use another > drive for Slackbuilds, but I don?t think that is the problem here > ? all other SBo Slackbuilds compile fine. > > What could be the cause of this error? Do you have any previous qt5 installation? This might be a blind shot, but if you happen to have it, try first uninstalling and then building. I always do it this way, because for whatever reason builds fail if I have previous version installed. -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Wed Sep 30 16:36:49 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 30 Sep 2015 23:36:49 +0700 Subject: [Slackbuilds-users] Suggestions for Prosody In-Reply-To: <560BD9A3.9090301@microlinux.fr> References: <560BD9A3.9090301@microlinux.fr> Message-ID: <560C0FA1.1090101@slackbuilds.org> > I just built Prosody for one of my public servers. I have two > suggestions for the package. > > 1. Version 0.9.4 is quite outdated. Prosody is currently at 0.9.8. > > 2. The package is missing an rc.prosody file. I have one in my own > SlackBuild: > > http://www.microlinux.fr/microlinux/server-14.1-source/prosody/ I talked to the maintainer and he is busy with his study so if anyone would step up and become a maintainer for this package, he's OK with that. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From gerardo.zamudio at linux.com Wed Sep 30 16:47:44 2015 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Wed, 30 Sep 2015 11:47:44 -0500 Subject: [Slackbuilds-users] Suggestions for Prosody In-Reply-To: <560C0FA1.1090101@slackbuilds.org> References: <560BD9A3.9090301@microlinux.fr> <560C0FA1.1090101@slackbuilds.org> Message-ID: <560C1230.6060704@linux.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/30/2015 11:36 AM, Willy Sudiarto Raharjo wrote: >> I just built Prosody for one of my public servers. I have two >> suggestions for the package. >> >> 1. Version 0.9.4 is quite outdated. Prosody is currently at >> 0.9.8. >> >> 2. The package is missing an rc.prosody file. I have one in my >> own SlackBuild: >> >> http://www.microlinux.fr/microlinux/server-14.1-source/prosody/ > > I talked to the maintainer and he is busy with his study so if > anyone would step up and become a maintainer for this package, he's > OK with that. > > Niki's SlackBuild looks OK to me. I can take over if he or someone else is not interested. - -- Gerardo Zamudio -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJWDBIwAAoJEPbPpamee1lXvFQP/RxsEdOEJK8w7l1ZRQLmUUD+ HynGtlBDFbgdCKkF3m3MhniobfPjjWF528K6538ODasH4EVz7oE3calCTAnAZH9W FGYrHXN9r8yBKp80S1R90cmbSSsazGI5rmXJPIK1kRH7BCbYVW/2Yt/gmWHFHBqU MNIm91NPpdLqzFcVXV8e/Cl7+fBbjHJSInkk1WsIZ0FAZDLxaCLkqRDVLdU2Gbb2 4F03aISxOp4bEQ6VgDN6NM6JlNkbgjHsM0XBBub6W9v0aSdQPqFY6Vkwitvd2BSH HKS8xS8rWQAhfQBUHFaaBsVfqpc0wo7xzf1AQ68fTa4Quacq0UFOHGumgGzffOGu 0W0r0zGXPOAAQlmxKE4EQCIQx0Fbi+fxzXQ0pKrUbfRYnX9qgScmyVbe3ThNeoXe SuyD0qEX9myCMx6sr2IDrxAvup30uYEnE1tqqDzz+2aEOAu5QaHpA//LMZTqSZwq 0twpzpgnxnfrG8SdBrfj0Ajd0IAPoLCX+9+LSVwRy6tT/GX7wU8awyE1ZsCmzTb7 hZBiCyhO+K6QNQxNDTYtazV1w3+8MynYi7GoatsLn4J3zogeeVZfDCUxeD/QAzx1 /63lD0HkdrkTBq4e1Ant9TtKxiCPf1Y1ofref80k5le6KXx2lw3NC9Tck5Ny1WDX CbG54Ry8glTGKnAfwcJM =dRtQ -----END PGP SIGNATURE----- From info at microlinux.fr Wed Sep 30 17:57:10 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 30 Sep 2015 19:57:10 +0200 Subject: [Slackbuilds-users] Suggestions for Prosody In-Reply-To: <560C1230.6060704@linux.com> References: <560BD9A3.9090301@microlinux.fr> <560C0FA1.1090101@slackbuilds.org> <560C1230.6060704@linux.com> Message-ID: <560C2276.8030708@microlinux.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 30/09/2015 18:47, Gerardo Zamudio a ?crit : > Niki's SlackBuild looks OK to me. I can take over if he or someone > else is not interested. As far as I can tell, two things in my SlackBuild are not "orthodox" compared to SBo's policy. 1. Downloading the source tarball is taken care of automatically. 2. Creating the prosody system user and group is also taken care of automatically, in the SlackBuild as well as in the doinst.sh file. Cheers, Niki - -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJWDCJ2AAoJEGFf3UBYz3LZzxsIAKxHSw0SxZjCzgXrjVj9IK2p ++2E3IFW6hOLxFmQKxQPhTa6dtcRlNg7TgKTJUSKpaNcVPyihQUBGZV9WuuRhv9F NJzNddKt3BVZ1r9QLVSGWLnwLsgRTLQ0rG7iqqCHKHSoZALi6rstLkCFonF6+0ST RNPKdkuQ1cqlm/XomkUIR6iRJIazSyqykFw9WDc5gSPaSWLAo8phdUjzXDi+zLkb JLI5AcEhsNYVced8v+hiQXIuAxQjd671gmkcteA4t/rgG8q+vBcJSY4vts01IRMI E+fLZaxKjlrQQuUzNpVgqbGKtWnhQQJxW7gbBKJ9gPLwHMsHdD2tMSWWDc5fXKQ= =27k7 -----END PGP SIGNATURE----- From edps.mundognu at gmail.com Wed Sep 30 19:13:23 2015 From: edps.mundognu at gmail.com (Edinaldo) Date: Wed, 30 Sep 2015 16:13:23 -0300 Subject: [Slackbuilds-users] libvpx build error Message-ID: make[1]: Nada a ser feito para `install'. cp: imposs?vel obter estado de ?build-tmp/docs/html?: Arquivo ou diret?rio n?o encontrado Cleaning up... libvpx: ... (Y)es to continue, (N)o to abort, (R)etry the build?: So, i simply remove "build-tmp/docs/html" from libvpx.SlackBuild, changing the line: cp -a AUTHORS CHANGELOG LICENSE PATENTS README build-tmp/docs/html \ $PKG/usr/doc/$PRGNAM-$VERSION to: cp -a AUTHORS CHANGELOG LICENSE PATENTS README $PKG/usr/doc/$PRGNAM-$VERSION build log: http://hastebin.com/zetobadini * there is no "doc" folder on /tmp/SBo/libvpx-v1.3.0/build-tmp/ From anddt at ukr.net Wed Sep 30 19:47:42 2015 From: anddt at ukr.net (Andrew) Date: Wed, 30 Sep 2015 22:47:42 +0300 Subject: [Slackbuilds-users] Suggestions for Prosody In-Reply-To: <560C2276.8030708@microlinux.fr> References: <560BD9A3.9090301@microlinux.fr> <560C0FA1.1090101@slackbuilds.org> <560C1230.6060704@linux.com> <560C2276.8030708@microlinux.fr> Message-ID: <20150930224742.6dea9111059ceacd5c249f3f@ukr.net> On Wed, 30 Sep 2015 19:57:10 +0200 Nicolas Kovacs wrote: > 2. Creating the prosody system user and group is also taken care of > automatically, in the SlackBuild as well as in the doinst.sh file. Take a look at this: https://raw.githubusercontent.com/AndDT/SlackBuilds/master/uid_gid.sh It would be nice to have it at http://slackbuilds.org/uid_gid.sh instead of /uid_gid.txt. -- WBR, Andrew From matteo.bernardini at gmail.com Wed Sep 30 19:54:44 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 30 Sep 2015 21:54:44 +0200 Subject: [Slackbuilds-users] libvpx build error In-Reply-To: References: Message-ID: 2015-09-30 21:13 GMT+02:00 Edinaldo : > > make[1]: Nada a ser feito para `install'. > cp: imposs?vel obter estado de ?build-tmp/docs/html?: Arquivo ou diret?rio > n?o encontrado > Cleaning up... > > libvpx: > ... > (Y)es to continue, (N)o to abort, (R)etry the build?: > > > So, i simply remove "build-tmp/docs/html" from libvpx.SlackBuild, changing > the line: > > cp -a AUTHORS CHANGELOG LICENSE PATENTS README build-tmp/docs/html \ > $PKG/usr/doc/$PRGNAM-$VERSION > > to: > > cp -a AUTHORS CHANGELOG LICENSE PATENTS README $PKG/usr/doc/$PRGNAM-$VERSION > > build log: http://hastebin.com/zetobadini > > * there is no "doc" folder on /tmp/SBo/libvpx-v1.3.0/build-tmp/ hi Edinaldo, I had similar reports in the past about missing docs during libvpx compiling and they were all related on running the SlackBuild on a Slackware partial installation: is it your case too? remember that only full install are supported/tested for the scripts on SBo. Matteo From edps.mundognu at gmail.com Wed Sep 30 20:09:15 2015 From: edps.mundognu at gmail.com (Edinaldo) Date: Wed, 30 Sep 2015 17:09:15 -0300 Subject: [Slackbuilds-users] libvpx build error Message-ID: hi Matteo, sorry (unnecessary post), i really run Slack with minimal install. Thanks!