On 2020-11-14 23:12, James Le Cuirot wrote:
I'm not claiming this has never actually happened but I use these
GitHub tarballs*a lot* and I don't recall ever seeing it. Does anyone
know for sure that it's happened in, say, the last 3 years? It's a lot
of extra work for a problem that may no longer exist or is so rare that
it's just not worth the effort.
I am aware of three incidents:
In 2011 but I cannot find details at the moment.
In 2013, a bugfix in git
(https://github.com/git/git/commit/22f0dcd9634a818a0c83f23ea1a48f2d620c0546)
caused such a change.
In second half of 2017, GitHub was rolling out a GZIP update across
their fleet which caused such a change. It mostly hit rarely downloaded
packages which were cleaned from CDN so tarball had to be re-generated.
You can use GitHub Actions for example to automate this or include it in
existing release workflows. But yes, you have to get upstream's
attention to implement this.
And it's not just GitHub, don't forget about GitLab and those
self-hosted GitLab instances which often don't support to upload
arbitrary assets...
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
