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

git 2.38.0: Change in `git archive` output

From
Kkpcyrd <kpcyrd@archlinux.org>
Date
Oct 16, 2022, 21:57 UTC
Message-ID
<20b14207-a6f2-033f-3419-271662bffba9@archlinux.org>
hello,

multiple people in Arch Linux noticed the output of our `git archive` command doesn't match the tarball served by github anymore.

First I suspected an update in our gzip package until I found this line in the git 2.38.0 release notes:

 > * Teach "git archive" to (optionally and then by default) avoid
 >   spawning an external "gzip" process when creating ".tar.gz" (and
 >   ".tgz") archives.

I've then found this commit that could be considered a breaking change in `git archive`:

https://github.com/git/git/commit/4f4be00d302bc52d0d9d5a3d4738bb525066c710

I don't know if there's some kind of gzip standard that could be used to align the git internal gzip implementation with gnu gzip.

I'm not saying this is necessarily a bug or regression but it makes it harder to reproduce github tar balls from a git repository. Just sharing what I've debugged. :)

cheers, kpcyrd

Next: brian m. carlson
Message 1 of 6 in “git 2.38.0: Change in `git archive` output”
  1. kpcyrdOct 16, 2022
  2. brian m. carlsonOct 16, 2022
  3. Jeff KingOct 17, 2022
  4. brian m. carlsonOct 17, 2022
  5. Jeff KingOct 17, 2022
  6. Konstantin RyabitsevOct 17, 2022

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.