[
https://issues.apache.org/jira/browse/ARROW-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761888#comment-15761888
]
Wes McKinney commented on ARROW-429:
------------------------------------
The {{.git_archival.txt}} file has some oddness in it:
{code}
cat .git_archival.txt
ref-names: refs/__gh__/pull/237/rebase, refs/__gh__/pull/234/rebase,
refs/__gh__/pull/233/rebase, refs/__gh__/pull/231/rebase,
refs/__gh__/pull/226/rebase, refs/__gh__/pull/225/rebase,
refs/__gh__/pull/220/rebase
{code}
I'm going to prepare a patch reverting ARROW-379 until we can investigate this
further
> 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)
