git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Subject: [BUG?] 'git verify-pack -v' on multiple packs fails for all but the first pack
Date: Fri, 22 Aug 2008 14:39:31 +0200	[thread overview]
Message-ID: <200808221439.31219.johan@herland.net> (raw)

(I don't have time to look into this right now, but will do so later if 
nobody comes up with a solution in the meantime...)

When running 'git verify-pack -v' on multiple packs (.idx files), it 
fails for all packs, except the first, with exit code 128, and the 
following single line:

	fatal: internal error: pack revindex fubar

This does not happen when given only a single pack, or when given 
multiple packs, but without '-v' option.

To reproduce, simply do:

	git verify-pack -v .git/objects/pack/*.idx

in any repo with more than one pack file.

This happens with a fairly current 'next' (1.6.0.96.g2fad1). AFAICS, it 
also happens in v1.6.0.


...Johan


PS: Does someone knows a better way to generate a sorted list of all the 
blob objects (by SHA1 sum) in a packed repo?

-- 
Johan Herland, <johan@herland.net>
www.herland.net

             reply	other threads:[~2008-08-22 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22 12:39 Johan Herland [this message]
2008-08-22 13:27 ` [BUG?] 'git verify-pack -v' on multiple packs fails for all but the first pack Johan Herland
2008-08-22 13:45   ` [PATCH] Selftest for verifying 'git verify-pack -v' with multiple arguments Johan Herland
2008-08-22 13:49   ` [BUG?] 'git verify-pack -v' on multiple packs fails for all but the first pack Nicolas Pitre
2008-08-22 19:45   ` [PATCH] discard revindex data when pack list changes Nicolas Pitre
2008-08-22 21:57     ` Johan Herland

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=200808221439.31219.johan@herland.net \
    --to=johan@herland.net \
    --cc=git@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).