<div dir="ltr"><div>My 2 cents. I use Mongo quite a bit. I can't see myself ever not installing both. So, for convenience I'd like to see them together. But, being more true to upstream sources, they should be separate. I suppose I lean towards having them together because of my own selfish perspective.<br><br></div>scott<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 6, 2015 at 7:54 AM, <span dir="ltr"><<a href="mailto:slackbuilds-users-request@slackbuilds.org" target="_blank">slackbuilds-users-request@slackbuilds.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send SlackBuilds-users mailing list submissions to<br>
<a href="mailto:slackbuilds-users@slackbuilds.org">slackbuilds-users@slackbuilds.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:slackbuilds-users-request@slackbuilds.org">slackbuilds-users-request@slackbuilds.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:slackbuilds-users-owner@slackbuilds.org">slackbuilds-users-owner@slackbuilds.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of SlackBuilds-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: libraries/ogre: upstream updated download file<br>
(Willy Sudiarto Raharjo)<br>
2. nginx permissions? (Miguel De Anda)<br>
3. Re: VLC?2.2.1 configure warnings (Christoph Willing)<br>
4. Re: VLC?2.2.1 configure warnings (Lemin)<br>
5. Re: call for testing - mongodb (Christoph Willing)<br>
6. Re: call for testing - mongodb (Miguel De Anda)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 06 May 2015 07:14:58 +0700<br>
From: Willy Sudiarto Raharjo <<a href="mailto:willysr@slackbuilds.org">willysr@slackbuilds.org</a>><br>
To: <a href="mailto:slackbuilds-users@slackbuilds.org">slackbuilds-users@slackbuilds.org</a><br>
Subject: Re: [Slackbuilds-users] libraries/ogre: upstream updated<br>
download file<br>
Message-ID: <<a href="mailto:55495D02.30009@slackbuilds.org">55495D02.30009@slackbuilds.org</a>><br>
Content-Type: text/plain; charset=windows-1252<br>
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
> The source file for ogre has been updated after a recent branch<br>
> merge. The new md5sum is 'c41950f13cf4a8b6e83894920c1ea898'. The<br>
> new top level directory for the tarball is<br>
> 'sinbad-ogre-55e89ae88219', so the SRCNAM variable in the<br>
> SlackBuild also needs to be updated.<br>
<br>
Fixed in my branch<br>
<br>
Thanks<br>
<br>
<br>
- --<br>
Willy Sudiarto Raharjo<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2<br>
<br>
iEYEAREIAAYFAlVJXQIACgkQiHuDdNczM4HXQACgjp4whMpiyjTt8Hmb/3nPQZda<br>
JpMAn3WY3vDAc6RUTie8MW7NusnClERo<br>
=xiMC<br>
-----END PGP SIGNATURE-----<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 5 May 2015 22:01:45 -0700<br>
From: Miguel De Anda <<a href="mailto:miguel@thedeanda.com">miguel@thedeanda.com</a>><br>
To: "SlackBuilds.org Users List" <<a href="mailto:slackbuilds-users@slackbuilds.org">slackbuilds-users@slackbuilds.org</a>>,<br>
<a href="mailto:larryhaja@gmail.com">larryhaja@gmail.com</a><br>
Subject: [Slackbuilds-users] nginx permissions?<br>
Message-ID:<br>
<<a href="mailto:CAA62KfSUsQXoZMYUYDyp4ReSxMiwjdBKeaOCJvPvkyC1gbS7fA@mail.gmail.com">CAA62KfSUsQXoZMYUYDyp4ReSxMiwjdBKeaOCJvPvkyC1gbS7fA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
i've installed nginx from the slackbuild and i have it run as a proxy for<br>
tomcat with a config something like this...<br>
<br>
sever {<br>
server_name <a href="http://example.com" target="_blank">example.com</a>;<br>
location / {<br>
proxy_pass <a href="http://localhost:8080" target="_blank">http://localhost:8080</a>;<br>
proxy_set_header X-Real-IP $remote_addr;<br>
proxy_set_header X-Forwarded-For $remote_addr;<br>
proxy_set_header Host $host;<br>
}<br>
}<br>
<br>
when it tries to load some files, it fails with the following error:<br>
<br>
2015/05/05 14:59:31 [crit] 25274#0: *5 open()<br>
"/var/lib/nginx/proxy/3/00/0000000003" failed (13: Permission denied) while<br>
reading upstream, client: 192.168.1.2, server: <a href="http://example.com" target="_blank">example.com</a>, request: "GET<br>
/foo-file.css HTTP/1.1", upstream: "<a href="http://127.0.0.1:8080/foo-file.css" target="_blank">http://127.0.0.1:8080/foo-file.css</a>",<br>
host: "<a href="http://example.com" target="_blank">example.com</a>", referrer: "<a href="http://example.com/index.html" target="_blank">http://example.com/index.html</a>"<br>
<br>
it seems to kind of work if i add a<br>
<br>
user mdeanda users;<br>
<br>
to the config and change the permission to /var/lib/nginx/* to my local<br>
user (and create lots of folders in the proxy directory) but that's<br>
obviously not the correct way. has anybody dealt with this? i know ubuntu<br>
and others tend to run nginx as a www-data user, is that what we need for<br>
nginx? a new user?<br>
<br>
-m<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150505/66e43bd0/attachment-0001.html" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150505/66e43bd0/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 06 May 2015 16:19:50 +1000<br>
From: Christoph Willing <<a href="mailto:chris.willing@iinet.net.au">chris.willing@iinet.net.au</a>><br>
To: <a href="mailto:slackbuilds-users@slackbuilds.org">slackbuilds-users@slackbuilds.org</a><br>
Subject: Re: [Slackbuilds-users] VLC?2.2.1 configure warnings<br>
Message-ID: <<a href="mailto:5549B286.7080803@iinet.net.au">5549B286.7080803@iinet.net.au</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
<br>
<br>
On 05/05/2015 05:53 PM, Lemin wrote:<br>
> On 2015-05-05 05:29, Christoph Willing wrote:<br>
>><br>
>><br>
>> On 05/05/2015 10:10 AM, Willy Sudiarto Raharjo wrote:<br>
>>> -----BEGIN PGP SIGNED MESSAGE-----<br>
>>> Hash: SHA256<br>
>>><br>
>>>> The latest VLC update would like libraries that are not provided by<br>
>>>> 14.1: - requires TagLib 1.9.0 but slackware-14.1 has 1.8.0. -<br>
>>>> requires cairo >= 1.13.1 but slackware-14.1 has 1.12.16. - requires<br>
>>>> libdvdread >= 4.9.0 but slackware-14.1 has 4.2.0.<br>
>>>><br>
>>>> You could also add these packages as options: libssh2, gstreamer1,<br>
>>>> x265.<br>
>>><br>
>>> i built the VLC on slackware64-14.1 and it worked fine<br>
>>><br>
>><br>
>> Yes, I was pretty sure I'd built and tested vlc-2.2.1 on 14.1 just<br>
>> recently but couldn't check right now as my dev machine is deeply into<br>
>> rebuilding lots of packages in -current, so thanks for confirming Willy.<br>
>><br>
>> However I was able to build 2.2.1 on -current with the additional<br>
>> options that Lemin has suggested (although what used to be gstreamer1<br>
>> is now just plain gstreamer in stock -current) and it all went fine.<br>
>> I'll check it again on 14.1 soon and, all being well, I'll submit an<br>
>> updated SlackBuild sometime this week.<br>
>><br>
>> chris<br>
>> _______________________________________________<br>
>> SlackBuilds-users mailing list<br>
>> <a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
>> <a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
>> Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
>> FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
>><br>
> It works fine for playing most files, but I encountered an issue when<br>
> trying to play a DVD, perhaps for libdvdread support was not built:<br>
><br>
> Your input can't be opened:VLC is unable to open the MRL 'dvd:///...'<br>
><br>
> The prior vlc could read it with libdvdread built. For now I encode<br>
> using HandBrake then play with vlc.<br>
><br>
> Without TagLib, vlc is not reading the tag informations of mp3 files I<br>
> also witnessed.<br>
> I could not say how vlc uses cairo, and if the lack of it brings any issue.<br>
><br>
> I have been using 2.2.1 with the addiotional options (gstreamer1 from<br>
> SBo), and did not notice any issue.<br>
><br>
<br>
I've confirmed these problems with vlc-2.2.1 on 14.1 and since its most<br>
improbable that lidvdread and taglib versions will be updated in<br>
official 14.1, I think we should revert to the latest version of vlc<br>
that is able to use those versions. That is vlc-2.1.6 which I've tested<br>
to confirm operation with dvd:///... and cdda:///... MRL's.<br>
<br>
I'm just about to submit the SlackBuild for it, with libssh2,<br>
gstreamer1, gst1-plugins-base and x265 packages added to REQUIRES.<br>
<br>
Thanks for reporting the problem and suggesting the extra options Lemin.<br>
<br>
chris<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 06 May 2015 09:58:47 +0200<br>
From: Lemin <<a href="mailto:slackware@lemintown.eu">slackware@lemintown.eu</a>><br>
To: "SlackBuilds.org Users List" <<a href="mailto:slackbuilds-users@slackbuilds.org">slackbuilds-users@slackbuilds.org</a>><br>
Subject: Re: [Slackbuilds-users] VLC?2.2.1 configure warnings<br>
Message-ID: <<a href="mailto:5549C9B7.8050803@lemintown.eu">5549C9B7.8050803@lemintown.eu</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
<br>
On 2015-05-06 08:19, Christoph Willing wrote:<br>
><br>
><br>
> On 05/05/2015 05:53 PM, Lemin wrote:<br>
>> On 2015-05-05 05:29, Christoph Willing wrote:<br>
>>><br>
>>><br>
>>> On 05/05/2015 10:10 AM, Willy Sudiarto Raharjo wrote:<br>
>>>> -----BEGIN PGP SIGNED MESSAGE-----<br>
>>>> Hash: SHA256<br>
>>>><br>
>>>>> The latest VLC update would like libraries that are not provided by<br>
>>>>> 14.1: - requires TagLib 1.9.0 but slackware-14.1 has 1.8.0. -<br>
>>>>> requires cairo >= 1.13.1 but slackware-14.1 has 1.12.16. - requires<br>
>>>>> libdvdread >= 4.9.0 but slackware-14.1 has 4.2.0.<br>
>>>>><br>
>>>>> You could also add these packages as options: libssh2, gstreamer1,<br>
>>>>> x265.<br>
>>>><br>
>>>> i built the VLC on slackware64-14.1 and it worked fine<br>
>>>><br>
>>><br>
>>> Yes, I was pretty sure I'd built and tested vlc-2.2.1 on 14.1 just<br>
>>> recently but couldn't check right now as my dev machine is deeply into<br>
>>> rebuilding lots of packages in -current, so thanks for confirming Willy.<br>
>>><br>
>>> However I was able to build 2.2.1 on -current with the additional<br>
>>> options that Lemin has suggested (although what used to be gstreamer1<br>
>>> is now just plain gstreamer in stock -current) and it all went fine.<br>
>>> I'll check it again on 14.1 soon and, all being well, I'll submit an<br>
>>> updated SlackBuild sometime this week.<br>
>>><br>
>>> chris<br>
>>> _______________________________________________<br>
>>> SlackBuilds-users mailing list<br>
>>> <a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
>>> <a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
>>> Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
>>> FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
>>><br>
>> It works fine for playing most files, but I encountered an issue when<br>
>> trying to play a DVD, perhaps for libdvdread support was not built:<br>
>><br>
>> Your input can't be opened:VLC is unable to open the MRL 'dvd:///...'<br>
>><br>
>> The prior vlc could read it with libdvdread built. For now I encode<br>
>> using HandBrake then play with vlc.<br>
>><br>
>> Without TagLib, vlc is not reading the tag informations of mp3 files I<br>
>> also witnessed.<br>
>> I could not say how vlc uses cairo, and if the lack of it brings any<br>
>> issue.<br>
>><br>
>> I have been using 2.2.1 with the addiotional options (gstreamer1 from<br>
>> SBo), and did not notice any issue.<br>
>><br>
><br>
> I've confirmed these problems with vlc-2.2.1 on 14.1 and since its most<br>
> improbable that lidvdread and taglib versions will be updated in<br>
> official 14.1, I think we should revert to the latest version of vlc<br>
> that is able to use those versions. That is vlc-2.1.6 which I've tested<br>
> to confirm operation with dvd:///... and cdda:///... MRL's.<br>
><br>
> I'm just about to submit the SlackBuild for it, with libssh2,<br>
> gstreamer1, gst1-plugins-base and x265 packages added to REQUIRES.<br>
><br>
> Thanks for reporting the problem and suggesting the extra options Lemin.<br>
><br>
> chris<br>
><br>
<br>
It seems vlc-2.1.6 does not provide x265 and gstreamer1 support yet,<br>
quoting from the vlc-git NEWS file:<br>
<br>
Changes between 2.1.6 and 2.2.0:<br>
--------------------------------<br>
[...]<br>
Access:<br>
* Added TLS support for ftp access and sout access<br>
New schemes for implicit (ftps) and explicit (ftpes) modes<br>
[...]<br>
Encoder:<br>
[...]<br>
* Support for HEVC/H.265 encoding using x265<br>
<br>
Confirmed with local compile of 2.1.6, however libssh2 is indeed in<br>
vlc-2.1.6, my apologies for reporting that late in the conversation... I<br>
agree with your decision of reverting to a version fully compatible with<br>
14.1.<br>
<br>
Thanks for your work<br>
Lemin<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 06 May 2015 23:18:58 +1000<br>
From: Christoph Willing <<a href="mailto:chris.willing@iinet.net.au">chris.willing@iinet.net.au</a>><br>
To: <a href="mailto:slackbuilds-users@slackbuilds.org">slackbuilds-users@slackbuilds.org</a><br>
Subject: Re: [Slackbuilds-users] call for testing - mongodb<br>
Message-ID: <<a href="mailto:554A14C2.6040905@iinet.net.au">554A14C2.6040905@iinet.net.au</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
<br>
<br>
On 04/14/2015 04:22 PM, Miguel De Anda wrote:<br>
> hi all,<br>
><br>
> i've modified the mongodb build script to actually build mongo from<br>
> source instead of just repackaging the binaries. if i can get a couple<br>
> of confirmed builds i'll submit the update.<br>
><br>
<br>
Firstly, its great to see Miguel's effort to change a SlackBuild from<br>
simply repackaging someone else's work to building it ourselves.<br>
Repackaging always looks like we're not able to build it ourselves, or<br>
couldn't be bothered ("slack" in the worst meaning of the word).<br>
<br>
After the last lot of updates which included the new "build from source"<br>
SlackBuild for mongodb, I ran the script but found that the contents of<br>
the new package's /usr/bin directory contained only some of the binaries<br>
that exist in the repackaged version i.e.<br>
mongo<br>
mongod<br>
mongoperf<br>
mongos<br>
mongosniff<br>
<br>
compared with:<br>
mongostat<br>
mongod<br>
mongofiles<br>
mongorestore<br>
mongo<br>
mongoperf<br>
bsondump<br>
mongooplog<br>
mongos<br>
mongodump<br>
mongotop<br>
mongoimport<br>
mongoexport<br>
<br>
After unsuccessfully trying various scons incantations in an attempt to<br>
produce the missing binaries, I eventually read the documentation. It<br>
seems, according to docs/<a href="http://building.md" target="_blank">building.md</a>, that the "missing" pieces are now<br>
kept separately at <a href="https://github.com/mongodb/mongo-tools" target="_blank">https://github.com/mongodb/mongo-tools</a><br>
<br>
The question then is whether a separate mongo-tools SlackBuild should be<br>
made for them or whether building them could be added into the existing<br>
SlackBuild (since this is how the mongo people are preparing their own<br>
release packages - the ones we used to repackage)?<br>
<br>
chris<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 6 May 2015 07:54:26 -0700<br>
From: Miguel De Anda <<a href="mailto:miguel@thedeanda.com">miguel@thedeanda.com</a>><br>
To: "SlackBuilds. org Users List" <<a href="mailto:slackbuilds-users@slackbuilds.org">slackbuilds-users@slackbuilds.org</a>><br>
Subject: Re: [Slackbuilds-users] call for testing - mongodb<br>
Message-ID:<br>
<<a href="mailto:CAA62KfQuSYjPbrVGKxMbgADJ7x1Era8Mjd5J8AguD7GK2YLjAA@mail.gmail.com">CAA62KfQuSYjPbrVGKxMbgADJ7x1Era8Mjd5J8AguD7GK2YLjAA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Ahh good point. I had full intentions of creating a separate SlackBuilds<br>
for those tools and completely forgot. I was thinking of keeping them<br>
separate as it'll make getting the sources easier - no need for repackaging<br>
the vanilla sources.<br>
<br>
Thoughts?<br>
On May 6, 2015 6:19 AM, "Christoph Willing" <<a href="mailto:chris.willing@iinet.net.au">chris.willing@iinet.net.au</a>><br>
wrote:<br>
<br>
><br>
><br>
> On 04/14/2015 04:22 PM, Miguel De Anda wrote:<br>
><br>
>> hi all,<br>
>><br>
>> i've modified the mongodb build script to actually build mongo from<br>
>> source instead of just repackaging the binaries. if i can get a couple<br>
>> of confirmed builds i'll submit the update.<br>
>><br>
>><br>
> Firstly, its great to see Miguel's effort to change a SlackBuild from<br>
> simply repackaging someone else's work to building it ourselves.<br>
> Repackaging always looks like we're not able to build it ourselves, or<br>
> couldn't be bothered ("slack" in the worst meaning of the word).<br>
><br>
> After the last lot of updates which included the new "build from source"<br>
> SlackBuild for mongodb, I ran the script but found that the contents of the<br>
> new package's /usr/bin directory contained only some of the binaries that<br>
> exist in the repackaged version i.e.<br>
> mongo<br>
> mongod<br>
> mongoperf<br>
> mongos<br>
> mongosniff<br>
><br>
> compared with:<br>
> mongostat<br>
> mongod<br>
> mongofiles<br>
> mongorestore<br>
> mongo<br>
> mongoperf<br>
> bsondump<br>
> mongooplog<br>
> mongos<br>
> mongodump<br>
> mongotop<br>
> mongoimport<br>
> mongoexport<br>
><br>
> After unsuccessfully trying various scons incantations in an attempt to<br>
> produce the missing binaries, I eventually read the documentation. It<br>
> seems, according to docs/<a href="http://building.md" target="_blank">building.md</a>, that the "missing" pieces are now<br>
> kept separately at <a href="https://github.com/mongodb/mongo-tools" target="_blank">https://github.com/mongodb/mongo-tools</a><br>
><br>
> The question then is whether a separate mongo-tools SlackBuild should be<br>
> made for them or whether building them could be added into the existing<br>
> SlackBuild (since this is how the mongo people are preparing their own<br>
> release packages - the ones we used to repackage)?<br>
><br>
> chris<br>
> _______________________________________________<br>
> SlackBuilds-users mailing list<br>
> <a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
> <a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
> Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
> FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150506/f769777a/attachment.html" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150506/f769777a/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
<br>
<br>
------------------------------<br>
<br>
End of SlackBuilds-users Digest, Vol 109, Issue 6<br>
*************************************************<br>
</blockquote></div><br></div>