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

Posted to issues@arrow.apache.org by "Phillip Cloud (JIRA)" <ji...@apache.org> on 2018/07/15 18:38:00 UTC

[jira] [Commented] (ARROW-2847) [Packaging] Fix artifact name matching for conda forge packages

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

Phillip Cloud commented on ARROW-2847:
--------------------------------------

What the pros/cons of removing pins vs using pattern matching?

> [Packaging] Fix artifact name matching for conda forge packages
> ---------------------------------------------------------------
>
>                 Key: ARROW-2847
>                 URL: https://issues.apache.org/jira/browse/ARROW-2847
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Krisztian Szucs
>            Assignee: Krisztian Szucs
>            Priority: Major
>
> With the recently introduced conda recipe changes and version pinning the artifact names are not known before the build, they contain a hash too.
> `arrow-cpp-0.9.1.dev366-py36_0.tar.bz2` => `arrow-cpp-0.9.1.dev366-py36_vc14h12fa3ca_0.tar.bz2`
> We need to either remove the pins or use pattern matching in the status and sign commands.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)