github changed the method of forming automatically generated archives “.TAR .gz “and” .tgz “on pages with releases,
that led to change their control amounts and mass failures in automated assembly systems, which to confirm the integrity of the GITHB -loaded archives with previously saved control amounts, for example, placed in metadata packets or in assembly scenarios.
Starting with the release of 2.38 in the GIT tools was included according to The default is the built -in implementation of the GZIP, which made it possible to unify the support of this compression method in different operating systems and increase the performance of archives. GitHub picked up a change after updating the Git version in its infrastructure. The problem was caused by the fact that the compressed archives generated by the built -in implementation of the GZIP based on ZLIB are binarously differ from the archives created by the GZIP utility, which led to the difference of control sums for the archives created by different versions of GIT when performing the Git Archive command.
, The problem is appeared in various assembly systems, continuous integration systems and in the assembly tools of packets from arched texts. For example, the assembly of about 5800 ports FreeBSD was violated, the original texts for which were loaded from GitHub.
in answer The first complaints about the failures at first They referred to the fact that the constant control amounts for archives were never guaranteed. After it was shown that to restore the performance of the assembly systems, which which the change has affected, colossal work will be required to update metadata in various ecosystems, GITHUB representatives changed their minds, canceled the change and returned the old method of generating archives.
GIT developers have not yet come to some kind of solution and only discuss possible Actions