[ 
https://issues.apache.org/jira/browse/ARROW-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17657463#comment-17657463
 ] 

Rok Mihevc commented on ARROW-429:
----------------------------------

This issue has been migrated to [issue 
#16077|https://github.com/apache/arrow/issues/16077] on GitHub. Please see the 
[migration documentation|https://github.com/apache/arrow/issues/14542] for 
further details.

> 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
>          Components: Developer Tools, Packaging
>            Reporter: Wes McKinney
>            Priority: Blocker
>             Fix For: 0.2.0
>
>
> [~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
(v8.20.10#820010)

Reply via email to