You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2016/12/19 18:11:58 UTC

[jira] [Updated] (ARROW-429) git-archive SHA-256 checksums are changing

     [ https://issues.apache.org/jira/browse/ARROW-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wes McKinney updated ARROW-429:
-------------------------------
    Summary: git-archive SHA-256 checksums are changing  (was: Git archives SHA-256 checksums are changing)

> 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)