From: Sassy Natan <sassyn@gmail.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Xen List <xen-users@lists.xensource.com>
Subject: Re: Xen 4.0 RC4 Error on Compile
Date: Mon, 22 Feb 2010 10:44:33 +0200 [thread overview]
Message-ID: <529a12f41002220044x940fb52ie7f8a7f95afc63a9@mail.gmail.com> (raw)
In-Reply-To: <C7A7F070.ADD0%keir.fraser@eu.citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 808 bytes --]
Maybe,
But is for 5 days now
Any Idea?
On Mon, Feb 22, 2010 at 10:27 AM, Keir Fraser <keir.fraser@eu.citrix.com>wrote:
> On 22/02/2010 08:09, "Sassy Natan" <sassyn@gmail.com> wrote:
>
> > walk 6d2c51466e694895ed6cfe4b4bc8cd40300947bd
> > error: transfer closed with 4347 bytes remaining to read (curl_result =
> 18,
> > http_code = 200, sha1 = 1f315155ba20a2c30598f682eee482d08fe80280)
> > error: Unable to find 1f315155ba20a2c30598f682eee482d08fe80280 under
> > http://xenbits.xensource.com/git-http/qemu-xen-unstable.git
> > Cannot obtain needed blob 1f315155ba20a2c30598f682eee482d08fe80280
> > while processing commit 6d2c51466e694895ed6cfe4b4bc8cd40300947bd.
> > fatal: Fetch failed.
>
> Failed to fully download the qemu repository. It's probably a temporary
> network error.
>
> -- Keir
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 1417 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-02-22 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 8:09 Xen 4.0 RC4 Error on Compile Sassy Natan
2010-02-22 8:27 ` Keir Fraser
2010-02-22 8:44 ` Sassy Natan [this message]
2010-02-22 9:57 ` Keir Fraser
2010-02-23 18:01 ` [Xen-devel] " Ian Jackson
2010-02-23 18:03 ` Sassy Natan
2010-02-23 18:17 ` [Xen-devel] " Brendan Cully
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=529a12f41002220044x940fb52ie7f8a7f95afc63a9@mail.gmail.com \
--to=sassyn@gmail.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).