From: Larry Finger <Larry.Finger@lwfinger.net>
To: Daniel Drake <dsd@gentoo.org>
Cc: Michael Buesch <mb@bu3sch.de>,
"John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: wireless-2.6 git repos broken
Date: Sun, 23 Jul 2006 10:59:09 -0500 [thread overview]
Message-ID: <44C39CCD.70702@lwfinger.net> (raw)
In-Reply-To: <44C39B4F.9020002@gentoo.org>
Daniel Drake wrote:
> Michael Buesch wrote:
>> mb@ppc1:/tmp$ git --version
>> git version 1.4.1
>> mb@ppc1:/tmp$ git clone
>> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git
>> Generating pack...
>> Done counting 290305 objects.
>> Deltifying 290305 objects.
>> 100% (290305/290305) done
>> fatal: unexpected EOF) fatal: packfile
>> '/tmp/wireless-2.6/.git/objects/pack/tmp-DuBFrs' SHA1 mismatch
>> error: git-fetch-pack: unable to read from git-index-pack
>> error: git-index-pack died with error code 128
>> fetch-pack from
>> 'git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git'
>> failed.
>>
>> I tried several times on two different machines and also (as you can see)
>> with different git versions.
>> Could it be a git bug?
>
> Do you have the same problem on other git trees?
> I saw some people running into this error when cloning Linus'
> linux-2.6.git. I couldn't reproduce it, using exactly the same git version.
I had the same error when pulling from Linus's tree. It was fixed with a 'git fsck-objects --full'
command.
Larry
next prev parent reply other threads:[~2006-07-23 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 15:22 wireless-2.6 git repos broken Michael Buesch
2006-07-23 15:52 ` Daniel Drake
2006-07-23 15:59 ` Larry Finger [this message]
2006-07-23 16:07 ` Michael Buesch
2006-07-23 16:13 ` Larry Finger
2006-07-24 16:14 ` John W. Linville
2006-07-25 0:17 ` Larry Finger
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=44C39CCD.70702@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dsd@gentoo.org \
--cc=junkio@cox.net \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.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 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).