arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wes McKinney (JIRA)" <>
Subject [jira] [Commented] (ARROW-429) git-archive SHA-256 checksums are changing
Date Mon, 19 Dec 2016 18:18:58 GMT


Wes McKinney commented on ARROW-429:

The {{.git_archival.txt}} file has some oddness in it:

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

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:
>             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.
> from a prior passing build with the same commit hash and SHA256
> I suggest that we drop setuptools_scm_git_archive and revert to manual versioning. 

This message was sent by Atlassian JIRA

View raw message