All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xen-unstable/staging: qemu git file corrupt
Date: Tue, 15 Nov 2011 11:33:39 +0100	[thread overview]
Message-ID: <4EC24003.907@ts.fujitsu.com> (raw)
In-Reply-To: <1321351536.3664.110.camel@zakaz.uk.xensource.com>

On 11/15/2011 11:05 AM, Ian Campbell wrote:
> On Tue, 2011-11-15 at 07:25 +0000, Juergen Gross wrote:
>> error: File efd594c960330cc3eee44e65f5fee258c798e610
>> (http://xenbits.xensource.com/git-http/qemu-xen-unstable.git/objects/8a/d9c9e46bb1fea94e589c0ae062dab921ad86a5)
>> corrupt
>> error: Unable to find 8ad9c9e46bb1fea94e589c0ae062dab921ad86a5 under
>> http://xenbits.xensource.com/git-http/qemu-xen-unstable.git
>> Cannot obtain needed blob 8ad9c9e46bb1fea94e589c0ae062dab921ad86a5
>> while processing commit 249139f4e6e9ff8dfd2086d4e3fdfda8b1c53bac.
>> fatal: Fetch failed.
> Seems ok to me right now, via both http:// and git://. a transient issue
> or problem on your end perhaps?

Strange. The problem occurs always at the same line. I have to use http:// via
a proxy. A test with another proxy (slower connection) works.

So it IS a problem on my end, but finding it will be hard, I guess.

Thanks for checking!


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
PDG ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

      reply	other threads:[~2011-11-15 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15  7:25 xen-unstable/staging: qemu git file corrupt Juergen Gross
2011-11-15 10:05 ` Ian Campbell
2011-11-15 10:33   ` Juergen Gross [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=4EC24003.907@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@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 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.