git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: kpcyrd <kpcyrd@archlinux.org>
To: rb-general@lists.reproducible-builds.org,
	arch-dev-public@lists.archlinux.org, git@vger.kernel.org
Cc: gitster@pobox.com, l.s.r@web.de
Subject: git 2.38.0: Change in `git archive` output
Date: Sun, 16 Oct 2022 23:57:40 +0200	[thread overview]
Message-ID: <20b14207-a6f2-033f-3419-271662bffba9@archlinux.org> (raw)

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

             reply	other threads:[~2022-10-16 22:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 21:57 kpcyrd [this message]
2022-10-16 23:21 ` git 2.38.0: Change in `git archive` output brian m. carlson
2022-10-17  0:02 ` Jeff King
2022-10-17  0:51   ` brian m. carlson
2022-10-17 17:03     ` Jeff King
2022-10-17 19:14 ` Konstantin Ryabitsev

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20b14207-a6f2-033f-3419-271662bffba9@archlinux.org \
    --to=kpcyrd@archlinux.org \
    --cc=arch-dev-public@lists.archlinux.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=l.s.r@web.de \
    --cc=rb-general@lists.reproducible-builds.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).