Git archive checksums may change
github.blog
Git archive checksums may change
1–10 of 255 posts
Re: Git archive checksums may change
#2Now please give us compression options beyond gzip? :) Some zstd & lz4 please?
Re: Git archive checksums may change
#3See https://github.com/orgs/community/discussions/45830 for the fallout.
Re: Git archive checksums may change
#4Ah, this will presumably break some Arch Linux AUR packages. Preparing for bug reports.
Re: Git archive checksums may change
#5GitHub will need to revert this change. They've just crippled pretty much every "from source" package manager out there.
Re: Git archive checksums may change
#6Re: Git archive checksums may change
#7They have broken almost every open source project that builds external deps. Also broke homebrew apparently.
Re: Git archive checksums may change
#8Did people not know this? Honest question. I did run into this few times already before this change, so I assumed this would be wide-spread knowledge and mirrored everything.
Re: Git archive checksums may change
#9GitHub will need to revert this change. They've just crippled pretty much every "from source" package manager out there.
I prefer that tool be adapted to be more resilient and not depend on github particular implementation.
Re: Git archive checksums may change
#10GitHub will need to revert this change. They've just crippled pretty much every "from source" package manager out there.
I prefer that tool be adapted to be more resilient and not depend on github particular implementation.
Using SHA hashes when building guarantees that the code that you are building is what you think it is. How else would you verify dependencies like this, GPG signatures would have the same issue if you change the underlying bits.