Reputation: 465
A conda package I rely on is available in the conda-forge channel (=there exists a feedstock already) but not yet for the Python version x.y
. Which steps need to be taken to bring it to that version on conda-forge?
Upvotes: 3
Views: 717
Reputation: 465
As pointed out by Anthony Scopatz one needs to locally update the feedstock with conda-smithy
and bring these changes to the appropriate branch on GitHub.
The steps in detail are:
Clone the repo.
Install (or update) conda-smithy
in your root environment:
conda (source) deactivate
conda install conda-smithy
conda install conda=4.2 # see below
Rerender the feedstock from your root environment:
cd <feedstock-repo>/
conda smithy rerender
You might see warnings about missing tokens to CI services and anaconda, but you can safely ignore these.
Commit all changes, push them to your Github fork, and open a pull request.
After the pull request gets merged, the package gets build by the CI servers which might take several hours depending on their queues. Eventually the package should be available for the Python version x.y
.
The currently most recent version of conda, 4.3.14 is not supported by conda-smithy
. Hence as a workaround, a downgrade to conda 4.2 is currently necessary.
Upvotes: 3
Reputation: 3627
You should run conda smithy rerender
in the feedstock repo locally on a new branch, push it up to your fork, and open a pull request.
Upvotes: 3