[
https://issues.apache.org/jira/browse/ARROW-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762044#comment-15762044
]
Uwe L. Korn commented on ARROW-429:
-----------------------------------
Ok, this needs some digging into the inner workings of Git's {{export-subst}}.
For now I would prefer if we just switch the source of the tarball to
https://git-wip-us.apache.org/repos/asf?p=arrow.git;a=snapshot;h=f4737d7faf6daefbfa17c7175187adcde0d711ae;sf=tgz
as there aren't those github specific tags (but sadly also no subsitutions)
> git-archive SHA-256 checksums are changing
> ------------------------------------------
>
> Key: ARROW-429
> URL: https://issues.apache.org/jira/browse/ARROW-429
> Project: Apache Arrow
> Issue Type: Bug
> Reporter: Wes McKinney
> Priority: Blocker
>
> [~xhochy] since we added the git-archive business, I'm getting
> non-deterministic SHA256 checksums from the archives on GitHub, e.g.
> https://circleci.com/gh/conda-forge/arrow-cpp-feedstock/15
> from a prior passing build with the same commit hash and SHA256
> https://circleci.com/gh/wesm/arrow-cpp-feedstock/3
> I suggest that we drop setuptools_scm_git_archive and revert to manual
> versioning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
