Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rebuild for python38 #50

Merged

Conversation

regro-cf-autotick-bot
Copy link
Contributor

This PR has been triggered in an effort to update python38.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.
    Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

This package has the following downstream children:
pyhum
And potentially more.
If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one.

This PR was created by the cf-regro-autotick-bot.
The cf-regro-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.
Finally, feel free to drop us a line if there are any issues!
This PR was generated by https://circleci.com/gh/regro/circle_worker/11887, please use this URL for debugging

@conda-forge-linter
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@djhoese
Copy link
Contributor

djhoese commented Nov 4, 2019

From what I can tell the py3.8 builds are failing because of missing dependencies, but the output isn't the easiest to parse yet.

@dopplershift
Copy link
Member

@conda-forge-admin, please restart ci

@djhoese
Copy link
Contributor

djhoese commented Nov 4, 2019

Looks like some dependency is still missing for OSX (maybe a failed build somewhere):

numpy[version='>=1.14.6,<2.0a0'] -> mkl_fft -> python[version='2.7.*|3.5.*|3.6.*']
pykdtree[version='>=1.3.1'] -> python[version='>=2.7,<2.8.0a0|>=3.5,<3.6.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0']
pykdtree[version='>=1.3.1'] -> numpy[version='>=1.9.3,<2.0a0'] -> python[version='2.7.*|3.5.*|3.6.*']
six -> python[version='2.7.*|3.4.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.5,<3.6.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0|>=3.8,<3.9.0a0']
python[version='>=3.8,<3.9.0a0']
pyproj[version='>=1.9.5.1'] -> python[version='>=2.7,<2.8.0a0|>=3.5,<3.6.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0|>=3.8,<3.9.0a0']
configobj -> six -> python[version='2.7.*|3.4.*|3.5.*|3.6.*|>=3.8,<3.9.0a0']
pyproj[version='>=1.9.5.1'] -> aenum -> python[version='2.7.*|3.5.*|3.6.*']
pykdtree[version='>=1.3.1'] -> numpy[version='>=1.9.3,<2.0a0'] -> numpy-base==1.15.2=py37ha711998_0 -> python[version='>=3.8,<3.9.0a0']
pyyaml -> python[version='2.7.*|3.4.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.5,<3.6.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0|>=3.8,<3.9.0a0']
configobj -> python[version='>=2.7,<2.8.0a0|>=3.5,<3.6.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0']
numpy[version='>=1.14.6,<2.0a0'] -> python[version='>=2.7,<2.8.0a0|>=3.5,<3.6.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0|>=3.8,<3.9.0a0']

@djhoese
Copy link
Contributor

djhoese commented Nov 4, 2019

Ah looks like pykdtree on OSX failed: https://circleci.com/gh/conda-forge/pykdtree-feedstock

@djhoese
Copy link
Contributor

djhoese commented Nov 4, 2019

@conda-forge-admin, please restart ci

@ocefpaf ocefpaf merged commit d3f1d90 into conda-forge:master Nov 5, 2019
@regro-cf-autotick-bot regro-cf-autotick-bot deleted the rebuild-python3801 branch November 5, 2019 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants