git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: MIDX woes, was Re: [ANNOUNCE] Git v2.54.0-rc2

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 15, 2026, 21:04 UTC
Message-ID
<xmqq5x5s540j.fsf@gitster.g>
In-Reply-To
<8c1def10-9039-aecd-4ce4-fb4676b47e9b@gmx.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 17 quoted lines
>>  * Further work on incremental repacking using MIDX/bitmap
>
> I just noticed that a fetch with v2.54.0-rc2 into an existing repository
> rendered it unusable for Git v2.53.0:
>
>   fatal: multi-pack-index version 2 not recognized
>
> Is it possible that v2.54.0-rc2 forcefully uses a MIDX version that has
> _just_ been introduced?
>
> If so, that might have been a premature bump of the default MIDX version,
> if even the preceding Git version fails to handle that MIDX version. It is
> guaranteed to cause substantial problems in setups where e.g. libgit2 or
> JGit is expected to be used interchangeably with Git. It also causes
> problems when users have to downgrade Git, or use several Git versions
> side by side (e.g. using GitHub Desktop, which bundles its own version of
> Git).

Is b2ec8e90 (midx: do not require packs to be sorted in lexicographic order, 2026-02-24), which says

    This change produces MIDXs which may not be correctly read with external
    tools or older versions of Git. Though older versions of Git know how to
    gracefully degrade and ignore any MIDX(s) they consider corrupt,
    external tools may not be as robust. To avoid unintentionally breaking
    any such tools, guard this change behind a version bump in the MIDX's
    on-disk format.
    
relevant?  The version bump seems to be doing more harm to "older
versions of Git" that "know how to gracefully degrade" by not
allowing them to degrade.

Taylor, perhaps you would want to add some instructions on how to recover? Like "rm -f .git/objects/pack/*.midx" or something?

Thanks, all.
Previous: Johannes SchindelinNext: Jeff King
Message 3 of 30 in “[ANNOUNCE] Git v2.54.0-rc2”
  1. Junio C HamanoApr 14, 2026
  2. MIDX woes, was Re: [ANNOUNCE] Git v2.54.0-rc2Johannes Schindelin, Apr 15, 2026
  3. Junio C HamanoApr 15, 2026
  4. Jeff KingApr 16, 2026
  5. Jeff KingApr 16, 2026
  6. Derrick StoleeApr 16, 2026
  7. Junio C HamanoApr 16, 2026
  8. Taylor BlauApr 16, 2026
  9. Derrick StoleeApr 19, 2026
  10. Junio C HamanoApr 20, 2026
  11. Taylor BlauApr 16, 2026
  12. Jeff KingApr 16, 2026
  13. Junio C HamanoApr 16, 2026
  14. Junio C HamanoApr 16, 2026
  15. Jeff KingApr 16, 2026
  16. Junio C HamanoApr 16, 2026
  17. Jeff KingApr 16, 2026
  18. Junio C HamanoApr 17, 2026
  19. MIDX: revert the default version to v1Junio C Hamano, Apr 16, 2026
  20. Junio C HamanoApr 16, 2026
  21. Junio C HamanoApr 16, 2026
  22. Taylor BlauApr 16, 2026
  23. Jeff KingApr 16, 2026
  24. Junio C HamanoApr 16, 2026
  25. Jeff KingApr 16, 2026
  26. Jeff KingApr 16, 2026
  27. Taylor BlauApr 16, 2026
  28. Jeff KingApr 16, 2026
  29. Junio C HamanoApr 17, 2026
  30. Elijah NewrenApr 17, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.