[Slackbuilds-users] SlackBuilds-users Digest, Vol 109, Issue 6

Richard Scott Smith pilbender at gmail.com
Wed May 6 16:07:17 UTC 2015 

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.

scott

On Wed, May 6, 2015 at 7:54 AM, <slackbuilds-users-request at slackbuilds.org>
wrote:

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

More information about the SlackBuilds-users mailing list