From: <rsbecker@nexbridge.com>
To: "'Taylor Blau'" <me@ttaylorr.com>
Cc: <git@vger.kernel.org>
Subject: RE: [BUG] 2.46.0 t7701.09 fails on NonStop ia64
Date: Sun, 4 Aug 2024 12:38:38 -0400 [thread overview]
Message-ID: <04f101dae68c$c57574b0$50605e10$@nexbridge.com> (raw)
In-Reply-To: <Zq+qHRwHC3sD14eN@nand.local>
On Sunday, August 4, 2024 12:20 PM, Taylor Blau wrote:
>On Sun, Aug 04, 2024 at 12:15:41PM -0400, rsbecker@nexbridge.com wrote:
>> After git repack -d --cruft --max-cruft-size=1M &&...
>>
>> ./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index <
>.git/objects/pack/pack-68c6c8c8538900694c32380ac1484201c8b60d8d.pack
>> fatal: unable to read index
>> ./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index <
>.git/objects/pack/pack-8f53f837597ebbdfc6f8ed173349e5cecbcfb97e.pack
>> fatal: corrupt index file
>> ./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index <
>.git/objects/pack/pack-b8dc9aadaadc12c82b0053fdee0039ae1025a8f8.pack
>> fatal: corrupt index file
>> ./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index <
>.git/objects/pack/pack-c2357b2b204fda52bc1f5515de94227e1db012af.pack
>> fatal: corrupt index file
>>
>> Apparently, something is wrong. This is an ia64 Big Endian. Not sure that matters.
>
>show-index expects the contents of the *.idx file on stdin, not the *.pack.
This is what I get for being 1/2 asleep on Sunday.
./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index < .git/objects/pack/pack-68c6c8c8538900694c32380ac1484201c8b60d8d.idx
138 ce6131022c3a48a15f4b7a68afb6ecf3b3bcb0cd (03c2fd95)
12 d1ff1c9224ae5e58a7656fb9ecc95865d42ed71e (64dd3dba)
183 df967b96a579e45a18b8251732d16804b2e56a55 (879729b5)
./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index <.git/objects/pack/pack-8f53f837597ebbdfc6f8ed173349e5cecbcfb97e.idx
12 ad16bed54cc61cf036075879deeff95ae977514b (239ee6ff)
./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index <.git/objects/pack/pack-b8dc9aadaadc12c82b0053fdee0039ae1025a8f8.idx
12 4f336f3df31054eabc05ac05f98bc024c8e05423 (24bc6ce2)
./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index <.git/objects/pack/pack-c2357b2b204fda52bc1f5515de94227e1db012af.idx
12 bd44d8aa2d22eb47ff70cef4b0bb45d1549ee49c (c2c93868)
next prev parent reply other threads:[~2024-08-04 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 18:03 [BUG] 2.46.0 t7701.09 fails on NonStop ia64 rsbecker
2024-08-01 19:23 ` Taylor Blau
2024-08-01 22:25 ` rsbecker
2024-08-02 0:58 ` Taylor Blau
2024-08-02 1:51 ` rsbecker
2024-08-02 22:07 ` rsbecker
2024-08-04 16:02 ` Taylor Blau
2024-08-04 16:15 ` rsbecker
2024-08-04 16:19 ` Taylor Blau
2024-08-04 16:38 ` rsbecker [this message]
2024-08-04 18:12 ` Taylor Blau
2024-08-04 19:15 ` rsbecker
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='04f101dae68c$c57574b0$50605e10$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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 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).