Re:Git archive checksums may change
by nilsbunger on Monday January 30, 2023 @06:02PM
(#34587905)
This is especially true of something like a git SHA, which is drilled into your head as THE stable hash of your code and git tree at a certain state. It should be expected that lots of tools use it as an identifier -- heck, I've done so myself to confirm which version of a piece of software is deployed on a particular machine, etc.
[ Parent
| on HN ]
Re:Git archive checksums may change
by Denvercoder9 on Monday January 30, 2023 @06:15PM
(#34588064)
The Git commit hashes didn't change (that'd actually be a serious problem). The hash of a compressed archive of the contents of a Git commit changed.
Re:Git archive checksums may change
by vlovich123 on Monday January 30, 2023 @06:14PM
(#34588048)
To be fair this isn't the git SHA. This is the generated archive (apparently dynamically per request) when you ask for a source tarball.
[dead]
Re:Git archive checksums may change
by thirtyseven on Monday January 30, 2023 @07:43PM
(#34589124)
The people that this broke weren't directly depending on the output of git archive being stable, but were assuming that the response data for a particular URL would stay constant. Maybe not a great idea either but not entirely unreasonable IMO.
Re:Git archive checksums may change
by nilsbunger on Tuesday January 31, 2023 @05:04AM
(#34593343)
Oh interesting. But if an archive hash isn’t stable, how is it meant to be used? What’s it good for?