From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org, "Mats Kärrman" <Mats.Karrman@tritech.se>,
openembedded-devel@lists.openembedded.org
Subject: Re: [yocto] exmap-console access forbidden
Date: Sun, 29 Jan 2012 10:48:02 +0000 [thread overview]
Message-ID: <1327834082.7807.11.camel@ted> (raw)
In-Reply-To: <2431052.r2DnJ7okSu@helios>
On Sat, 2012-01-28 at 14:58 +0000, Paul Eggleton wrote:
> On Friday 27 January 2012 09:34:26 Mats Kärrman wrote:
> > Does anyone know why the downloads server at yoctoproject.org has the source
> > tars of exmap-console as "Access Forbidden"? Other tars from the same
> > server is OK to download.
>
> I seem to be able to download the tarballs from
> http://downloads.yoctoproject.org/releases/exmap-console/... are you still
> experiencing this problem?
I did forward the email to Michael and Beth who looked into it and did
find and resolve a permissions problem. I think they were trying to
figure out the root cause before replying.
Anyhow, it should be resolved now.
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org, "Mats Kärrman" <Mats.Karrman@tritech.se>,
openembedded-devel@lists.openembedded.org
Subject: Re: [oe] exmap-console access forbidden
Date: Sun, 29 Jan 2012 10:48:02 +0000 [thread overview]
Message-ID: <1327834082.7807.11.camel@ted> (raw)
In-Reply-To: <2431052.r2DnJ7okSu@helios>
On Sat, 2012-01-28 at 14:58 +0000, Paul Eggleton wrote:
> On Friday 27 January 2012 09:34:26 Mats Kärrman wrote:
> > Does anyone know why the downloads server at yoctoproject.org has the source
> > tars of exmap-console as "Access Forbidden"? Other tars from the same
> > server is OK to download.
>
> I seem to be able to download the tarballs from
> http://downloads.yoctoproject.org/releases/exmap-console/... are you still
> experiencing this problem?
I did forward the email to Michael and Beth who looked into it and did
find and resolve a permissions problem. I think they were trying to
figure out the root cause before replying.
Anyhow, it should be resolved now.
Cheers,
Richard
next prev parent reply other threads:[~2012-01-29 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 9:34 exmap-console access forbidden Mats Kärrman
2012-01-28 14:58 ` Paul Eggleton
2012-01-28 14:58 ` [oe] " Paul Eggleton
2012-01-29 10:48 ` Richard Purdie [this message]
2012-01-29 10:48 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1327834082.7807.11.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Mats.Karrman@tritech.se \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.