Bill Lear <rael@zopyra.com> writes:

quoted text
> ... I did try doing this:
>
> 1) with 1.4.4.1 git, clone my public repo
> 2) in this new clone, make modifications to my files as before
> 3) with 1.5.0 git, do a commit
>
> and I got the same blowup on commit, and this on fsck, with 1.5.0 git:
>
> % git fsck-objects --full
> error: Packfile .git/objects/pack/pack-23d1a9af78b4b78d1f3750cf70f83cb91a20ba64.pack SHA1 mismatch with itself
> error: 00078437c23cbc04da52233f4f412219f88b8927: object corrupt or missing
> fatal: unknown object type 5 in .git/objects/pack/pack-23d1a9af78b4b78d1f3750cf70f83cb91a20ba64.pack

If you stop after cloning but before making a modification, is
the repository in good shape?

quoted text
> % ls -l objects/pack/
> total 85992
> -r--r--r--  1 blear software    77360 Feb 13 10:18 pack-23d1a9af78b4b78d1f3750cf70f83cb91a20ba64.idx
> -r--r--r--  1 blear software 87874337 Feb 14 10:00 pack-23d1a9af78b4b78d1f3750cf70f83cb91a20ba64.pack
>
> The .pack files have the same SHA, but different sizes (don't know
> what that means).

That is usually not a problem;  the name reflects the names of
objects contained in the pack (so both have the same set of
objects), but the actual raw contents (and the offsets recorded
in corresponding .idx file) depends on the packing parameters
(window, depth and deltabaseoffset).

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html