[
https://issues.apache.org/jira/browse/ARROW-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rok Mihevc updated ARROW-3415:
------------------------------
External issue URL: https://github.com/apache/arrow/issues/19742
> [Packaging] dev/release/verify-release-cndidate.sh fails in "conda activate
> arrow-test"
> ---------------------------------------------------------------------------------------
>
> Key: ARROW-3415
> URL: https://issues.apache.org/jira/browse/ARROW-3415
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Packaging
> Reporter: Kouhei Sutou
> Assignee: Kouhei Sutou
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.11.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code}
> + conda activate arrow-test
> CommandNotFoundError: Your shell has not been properly configured to use
> 'conda activate'.
> If your shell is Bash or a Bourne variant, enable conda for the current user
> with
> $ echo ".
> /tmp/arrow-0.11.0.a5PLj/apache-arrow-0.11.0/test-miniconda/etc/profile.d/conda.sh"
> >> ~/.bashrc
> or, for all users, enable conda with
> $ sudo ln -s
> /tmp/arrow-0.11.0.a5PLj/apache-arrow-0.11.0/test-miniconda/etc/profile.d/conda.sh
> /etc/profile.d/conda.sh
> The options above will permanently enable the 'conda' command, but they do NOT
> put conda's base (root) environment on PATH. To do so, run
> $ conda activate
> in your terminal, or to put the base environment on PATH permanently, run
> $ echo "conda activate" >> ~/.bashrc
> Previous to conda 4.4, the recommended way to activate conda was to modify
> PATH in
> your ~/.bashrc file. You should manually remove the line that looks like
> export
> PATH="/tmp/arrow-0.11.0.a5PLj/apache-arrow-0.11.0/test-miniconda/bin:$PATH"
> ^^^ The above line should NO LONGER be in your ~/.bashrc file! ^^^
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
