From: Scott Garman <scott.a.garman@intel.com>
To: <yocto@yoctoproject.org>
Subject: Re: problem with fetching?
Date: Wed, 10 Nov 2010 10:32:51 -0800 [thread overview]
Message-ID: <4CDAE553.7040304@intel.com> (raw)
In-Reply-To: <D10D6A3E-F997-489A-8921-83E5B33EE764@kernel.crashing.org>
On 11/10/2010 05:31 AM, Kumar Gala wrote:
>
> On Nov 10, 2010, at 7:29 AM, Richard Purdie wrote:
>
>> On Wed, 2010-11-10 at 06:32 -0600, Kumar Gala wrote:
>>> ERROR: Task failed: Fetch failed: Unable to fetch URL cvs://anonymous@cvs.sv.gnu.org/cvsroot/config;module=config;method=pserver;date=20080123 from any source.
>>> NOTE: package gnu-config-native-0.1+cvs20080123-r1: task do_fetch: Failed
>>> ERROR: Task 211 (virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gnu-config_20080123.bb, do_fetch) failed with 1
>>> ERROR: 'virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gnu-config_20080123.bb' failed
>>>
>>> Attached is the full log.
>>
>> Are you behind some kind of proxy/firewall? Its interesting its a cvs
>> based recipe that is failing so it could be your cvs setup.
>
> Yes, behind a proxy/firewall. cvs is not normally allowed out.
If you're behind a SOCKS proxy, these instructions might be helpful to
get CVS checkouts working:
https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
Scott
--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
prev parent reply other threads:[~2010-11-10 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 6:41 problem with fetching? Kumar Gala
2010-11-10 12:20 ` Tian, Kevin
2010-11-10 12:32 ` Kumar Gala
2010-11-10 13:29 ` Richard Purdie
2010-11-10 13:31 ` Kumar Gala
2010-11-10 13:50 ` Richard Purdie
2010-11-10 14:22 ` Kumar Gala
2010-11-10 14:40 ` Richard Purdie
2010-11-10 18:32 ` Scott Garman [this message]
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=4CDAE553.7040304@intel.com \
--to=scott.a.garman@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.