I'm sure this won't cause anyone any headaches:
"Since DEFLATE is the underlying compression used in archive/zip, compress/gzip, compress/zlib, and image/png, the outputs from those packages may also have changed."
go.devGo 1.27 Release Notes - The Go Programming Language
@andrewnez
I hope no software forge uses go to generate git-archive tarballs on the fly, that are later used by distros to build packages,and checked against a known-good hash...
Replying to @wolf480pl@mstdn.io
@wolf480pl @andrewnez archive tarballs should be among the releases' files
Replying to @SRAZKVT@tech.lgbt
@SRAZKVT
some upstreams (eg. bfdd) don't have releases, so some distro's (eg. OpenWrt) packages use the "generate tarball from commit" endpoint as a source download url
@andrewnez
Replying to @wolf480pl@mstdn.io
@wolf480pl @SRAZKVT @andrewnez
Huh, they could use git clone --depth 1 and diff the contents instead of relying on tarball integrity.
This keeps coming up again and again.
Commit hashes ought to remain stable.
Replying to @CyReVolt@mastodon.social
@CyReVolt @wolf480pl @andrewnez a git clone and a digest of the tree should suffice, but i don't know of a message digest for filesystem trees
maybe @hipsterelectron ?
Replying to @SRAZKVT@tech.lgbt
@SRAZKVT @CyReVolt @wolf480pl @andrewnez this is a fascinating topic and i believe deserves a new checksum algorithm to minimize recomputation upon change. in particular all the SHAs are actively designed against this since they are used in cryptography to hide information and cannot be computed in parallel (hence requiring hacks like sorting directory entries). hash bucketing entries by
Replying to @hipsterelectron@circumstances.run
@hipsterelectron @SRAZKVT @CyReVolt @wolf480pl the go proxy sumdb uses dirhash to avoid this problem: https://pkg.go.dev/golang.org/x/mod/sumdb/dirhash
