All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Bill Lear <rael@zopyra.com>
Cc: git@vger.kernel.org
Subject: Re: Error "fatal: cannot pread pack file: Success"
Date: Wed, 28 Feb 2007 12:43:39 -0500	[thread overview]
Message-ID: <20070228174339.GE5924@spearce.org> (raw)
In-Reply-To: <17893.47007.136145.112498@lisa.zopyra.com>

Bill Lear <rael@zopyra.com> wrote:
> Yes: 1.4.x worked fine.  This was actually my attempt to re-do the 1.4
> clone I had laying around, as I wanted my backup done with 1.5.  I
> still have the 1.4 cloned repo, just moved it out of the way...

OK, is ~/devel/project fully packed?  If it isn't can you repack
it (or a clone of it) so that it is?

Then take the packfile and try to feed it right into index-pack:

	mkdir /austin/users/rael/repos/git/project-test
	cd /austin/users/rael/repos/git/project-test
	git --bare init
	git --bare index-pack --stdin --fix-thin \
	  <~/devel/project/.git/objects/pack/pack-*.pack

Now while that is running it should be creating pack_XXXXXX as a
temporary file (where XXXXXX is replaced with the temp string).
Its this file that we are seeing magically truncate to 0 in the
middle of running.

But I fail to see anything in index-pack that would cause this,
and its the only program that knows about this file at this stage
of the clone.

-- 
Shawn.

  reply	other threads:[~2007-02-28 17:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28  3:45 Error "fatal: cannot pread pack file: Success" Bill Lear
2007-02-28  3:57 ` Shawn O. Pearce
2007-02-28  4:47   ` Shawn O. Pearce
2007-02-28  5:55     ` Junio C Hamano
2007-02-28 15:47       ` Linus Torvalds
2007-02-28 15:28     ` Bill Lear
2007-02-28 15:48       ` Bill Lear
2007-02-28 15:54         ` Shawn O. Pearce
2007-02-28 16:12           ` Bill Lear
2007-02-28 16:23             ` Bill Lear
2007-02-28 16:32               ` Shawn O. Pearce
2007-02-28 16:40                 ` Bill Lear
2007-02-28 16:48                   ` Shawn O. Pearce
2007-02-28 16:42                 ` Morten Welinder
2007-02-28 16:49                   ` Shawn O. Pearce
2007-02-28 16:55                     ` Bill Lear
2007-02-28 17:06                       ` Shawn O. Pearce
2007-02-28 17:10                         ` Bill Lear
2007-02-28 17:43                           ` Shawn O. Pearce [this message]
2007-02-28 17:50                             ` Nicolas Pitre
2007-02-28 17:58                               ` Shawn O. Pearce
2007-02-28 19:18                             ` Bill Lear
2007-02-28 19:23                               ` Bill Lear
2007-02-28 19:40                                 ` Nicolas Pitre
2007-03-01 15:23                                   ` Bill Lear
2007-02-28 16:34             ` Linus Torvalds
2007-02-28 16:36               ` Bill Lear
2007-02-28 16:47                 ` Linus Torvalds
2007-02-28 16:52                   ` Bill Lear
2007-02-28 17:13                     ` Linus Torvalds
2007-02-28 18:18                       ` Nicolas Pitre
2007-02-28 18:37                         ` Linus Torvalds
     [not found]                           ` <17893.53091.452962.414271@lisa.zopyra.com>
2007-02-28 19:22                             ` Linus Torvalds
2007-02-28 17:42               ` Nicolas Pitre

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=20070228174339.GE5924@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=rael@zopyra.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.