[jira] [Resolved] (ARROW-6577) Dependency conflict in conda packages

["Uwe L. Korn (Jira)" <ji...@apache.org>]

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

Uwe L. Korn resolved ARROW-6577.
--------------------------------
    Resolution: Not A Bug

Closing as this is not an Arrow bug.

> Dependency conflict in conda packages
> -------------------------------------
>
>                 Key: ARROW-6577
>                 URL: https://issues.apache.org/jira/browse/ARROW-6577
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Packaging
>    Affects Versions: 0.14.1
>         Environment: kernel: 5.2.11-200.fc30.x86_64
> conda 4.6.13
> Python 3.7.3
>            Reporter: Suvayu Ali
>            Priority: Major
>         Attachments: pa-conda.txt
>
>
> When I install pyarrow on a fresh environment, the latest version (0.14.1) is picked up. But installing certain packages downgrades pyarrow to 0.13.0 or 0.12.1. I think a common dependency is causing the downgrade, my guess is boost or protobuf. This is based on several instances of this issue I encountered over the last few weeks. It took me a while to find a somewhat reproducible recipe.
> {code:java}
> $ conda create -n test pyarrow pandas numpy
> ...
> Proceed ([y]/n)? y
> ...
> $ conda install -n test ipython
> ...
> Proceed ([y]/n)? n
> CondaSystemExit: Exiting.
> {code}
> I have attached a mildly edited (to remove progress bars, and control characters) transcript of this session. Here {{ipython}} triggers the problem, and downgrades {{pyarrow}} to 0.12.1, but I think there are other common packages who also conflict in this way. Please let me know if I can provide more info.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)