From: Simon Josefsson <simon@josefsson.org>
To: git@vger.kernel.org
Subject: Making bit-by-bit reproducible Git Bundles?
Date: Wed, 12 Mar 2025 12:40:05 +0100 [thread overview]
Message-ID: <871pv2jx4a.fsf@josefsson.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
Hi.
Thank you for the "git-archive" and "git-bundle" features, making it
easier to do source-based builds in a no-Internet environment.
I have published a Git bundle of Gnulib:
https://www.gnu.org/software/gnulib/manual/html_node/Gnulib-Git-Bundle.html
As you can see at the end, I struggle to come up with a recipe to allow
others to reproduce the git bundle that I created.
If I run the recipe above twice (including the clone), I get different
checksums. This even if nothing was committed in the remote repository
meanwhile.
Is it possible to create a bit-by-bit reproducible git bundle using some
other set of commands? If so, how? I'm using git 2.48.1 from Guix.
Can anyone explain what is causing the irreproducibility? Running
diffoscope is not helpful, since the bundle is compressed and diffoscope
doesn't seem to know how to untangle it.
If this is not possible today, what do you think about changes to make
this work?
Thanks,
/Simon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1251 bytes --]
next reply other threads:[~2025-03-12 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 11:40 Simon Josefsson [this message]
2025-03-12 16:02 ` Making bit-by-bit reproducible Git Bundles? Junio C Hamano
2025-03-13 3:09 ` Kyle Lippincott
2025-03-13 7:59 ` Simon Josefsson
2025-03-13 5:15 ` Jeff King
2025-03-13 13:36 ` Junio C Hamano
2025-03-13 20:16 ` Simon Josefsson
2025-03-13 21:07 ` Kyle Lippincott
2025-03-13 22:09 ` Junio C Hamano
2025-03-14 2:42 ` Jeff King
2025-03-14 22:24 ` 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=871pv2jx4a.fsf@josefsson.org \
--to=simon@josefsson.org \
--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).