You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Konstantin Boudnik <co...@apache.org> on 2016/04/28 20:01:10 UTC
Re: Bigtop and fresh Ubuntu
John
We don't set +x bit on the directories in s3, so the listing doesn't work.
There's nothing special about these permissions - it has just happened this
way. We either can fix the permissions (easy to do), or do as Evans suggested,
which might be ok in the interim, but is a hassle in the long run.
If there's no objections, I can just go ahead and try to fix the permissions
first.
Cos
On Wed, Apr 27, 2016 at 12:15PM, John Dison wrote:
> Nice to hear!
> BTW, it is possible to mirror the whole Bigtop repo to local machine?
> When I use URL from http://www.apache.org/dist/bigtop/bigtop-1.1.0/repos/trusty/bigtop.listhttp://bigtop-repos.s3.amazonaws.com/releases/1.1.0/ubuntu/trusty/x86_64
> I can't browse directory, I get access denied error. So i can't get list of files.
> Thanks in advance.
> From: MrAsanjar . <af...@gmail.com>
> To: user@bigtop.apache.org; John Dison <jd...@yahoo.com>
> Sent: Tuesday, April 26, 2016 8:26 PM
> Subject: Re: Bigtop and fresh Ubuntu
>
> not sure on precise, however my team has successfully installed and tested these packages
> on ubuntu 15.04 and 15.10 .
> Currently testing on 16.04.
>
>
>
>
>
Re: Bigtop and fresh Ubuntu
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, May 2, 2016 at 12:31 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Yeah, you're right - dunno what I was thinking about... S3 isn't a subject to
> the normal permission laws. So, if browsing is a real big deal for our users -
> we need to address it differently.
>
> The repo use case was always simple - to enable repository manager to install
> the packages. Web-browsing wasn't a part of it like ever. Which, honestly,
> makes all the sense for me.
Right. Well, we can also do a Groovy script than generates a bunch of
index.html.
Thanks,
Roman.
P.S. And I agree with you -- by "we" I really mean those who think it may
be important ;-)
Re: Bigtop and fresh Ubuntu
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, May 2, 2016 at 12:31 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Yeah, you're right - dunno what I was thinking about... S3 isn't a subject to
> the normal permission laws. So, if browsing is a real big deal for our users -
> we need to address it differently.
>
> The repo use case was always simple - to enable repository manager to install
> the packages. Web-browsing wasn't a part of it like ever. Which, honestly,
> makes all the sense for me.
Right. Well, we can also do a Groovy script than generates a bunch of
index.html.
Thanks,
Roman.
P.S. And I agree with you -- by "we" I really mean those who think it may
be important ;-)
Re: Bigtop and fresh Ubuntu
Posted by Konstantin Boudnik <co...@apache.org>.
Yeah, you're right - dunno what I was thinking about... S3 isn't a subject to
the normal permission laws. So, if browsing is a real big deal for our users -
we need to address it differently.
The repo use case was always simple - to enable repository manager to install
the packages. Web-browsing wasn't a part of it like ever. Which, honestly,
makes all the sense for me.
Cos
On Sun, May 01, 2016 at 05:07PM, Roman Shaposhnik wrote:
> On Thu, Apr 28, 2016 at 11:01 AM, Konstantin Boudnik <co...@apache.org> wrote:
> > John
> >
> > We don't set +x bit on the directories in s3, so the listing doesn't work.
> > There's nothing special about these permissions - it has just happened this
> > way. We either can fix the permissions (easy to do), or do as Evans suggested,
> > which might be ok in the interim, but is a hassle in the long run.
> >
> > If there's no objections, I can just go ahead and try to fix the permissions
> > first.
>
> While I don't think there are any objections, I don't actually think S3 works
> that way. Could you please try set +x and see it if it helps? It it doesn't we
> can always do an indexing step and generate a whole bunch of index.html
Re: Bigtop and fresh Ubuntu
Posted by Konstantin Boudnik <co...@apache.org>.
Yeah, you're right - dunno what I was thinking about... S3 isn't a subject to
the normal permission laws. So, if browsing is a real big deal for our users -
we need to address it differently.
The repo use case was always simple - to enable repository manager to install
the packages. Web-browsing wasn't a part of it like ever. Which, honestly,
makes all the sense for me.
Cos
On Sun, May 01, 2016 at 05:07PM, Roman Shaposhnik wrote:
> On Thu, Apr 28, 2016 at 11:01 AM, Konstantin Boudnik <co...@apache.org> wrote:
> > John
> >
> > We don't set +x bit on the directories in s3, so the listing doesn't work.
> > There's nothing special about these permissions - it has just happened this
> > way. We either can fix the permissions (easy to do), or do as Evans suggested,
> > which might be ok in the interim, but is a hassle in the long run.
> >
> > If there's no objections, I can just go ahead and try to fix the permissions
> > first.
>
> While I don't think there are any objections, I don't actually think S3 works
> that way. Could you please try set +x and see it if it helps? It it doesn't we
> can always do an indexing step and generate a whole bunch of index.html
Re: Bigtop and fresh Ubuntu
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Thu, Apr 28, 2016 at 11:01 AM, Konstantin Boudnik <co...@apache.org> wrote:
> John
>
> We don't set +x bit on the directories in s3, so the listing doesn't work.
> There's nothing special about these permissions - it has just happened this
> way. We either can fix the permissions (easy to do), or do as Evans suggested,
> which might be ok in the interim, but is a hassle in the long run.
>
> If there's no objections, I can just go ahead and try to fix the permissions
> first.
While I don't think there are any objections, I don't actually think S3 works
that way. Could you please try set +x and see it if it helps? It it doesn't we
can always do an indexing step and generate a whole bunch of index.html
Thanks,
Roman.
Re: Bigtop and fresh Ubuntu
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Thu, Apr 28, 2016 at 11:01 AM, Konstantin Boudnik <co...@apache.org> wrote:
> John
>
> We don't set +x bit on the directories in s3, so the listing doesn't work.
> There's nothing special about these permissions - it has just happened this
> way. We either can fix the permissions (easy to do), or do as Evans suggested,
> which might be ok in the interim, but is a hassle in the long run.
>
> If there's no objections, I can just go ahead and try to fix the permissions
> first.
While I don't think there are any objections, I don't actually think S3 works
that way. Could you please try set +x and see it if it helps? It it doesn't we
can always do an indexing step and generate a whole bunch of index.html
Thanks,
Roman.