arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe L. Korn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARROW-429) git-archive SHA-256 checksums are changing
Date Mon, 19 Dec 2016 20:25:58 GMT

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

Uwe L. Korn commented on ARROW-429:
-----------------------------------

Made a follow-up story: https://issues.apache.org/jira/browse/ARROW-430

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

Mime
View raw message