From: Jakub Narebski <jnareb@gmail.com>
To: Robert Garrigos <robert@garrigos.cat>
Cc: git@vger.kernel.org
Subject: Re: unable to get type of object
Date: Wed, 01 Jun 2011 02:39:24 -0700 (PDT) [thread overview]
Message-ID: <m3ei3dyjqe.fsf@localhost.localdomain> (raw)
In-Reply-To: <4DE5E60B.2030903@garrigos.cat>
Robert Garrigos <robert@garrigos.cat> writes:
> I'm having one of those nasty 128 errors which I cannot debug:
>
> ************
> predircam@eduab:~/public_html/idosing> git pull
> Generating pack...
> Done counting 117 objects.
> error: unable to find c3117d23df0c01ba8558bad81ad3488f0e8d430a
> fatal: unable to get type of object c3117d23df0c01ba8558bad81ad3488f0e8d430a
> fatal: early EOF
> fatal: git-unpack-objects died with error code 128
> Fetch failure: /home/predircam/gitrepos/idosing.git
> ***************
>
> google suggests me to run git fsck to get a list of corrupted
> files. Besides that I'm running git 1.2.4 and that the git command for
> that version is fsck-objects, I'm not having any result at all.
>
> Could this be a compatibility problem? As I said, I run git 1.2.4 on
> the repo server and git 1.7.0.2 on my development server. BTW, on my
> devel server running the git command fsck gives no result either.
Do this repository uses submodules? IIRC pre 1.4.x (or even later)
git didn't understand modules.
Or it might be problem with deltabaseoffset, i.e. when objects is
stored in pack as a difference (delta) from other objects, it refers
to base by offset in pack, and not by sha-1 id. I don't remember if
ancient 1.2.4 supports this feature. This is more likely.
Why don't you upgrade git (perhaps installing it locally in your home
directory)?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-06-01 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 7:11 unable to get type of object Robert Garrigos
2011-06-01 9:39 ` Jakub Narebski [this message]
2011-06-01 10:05 ` Robert Garrigos
2011-06-01 16:04 ` Jeff King
2011-06-01 18:18 ` Tomas Carnecky
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=m3ei3dyjqe.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=robert@garrigos.cat \
/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).