Fix import errors on osx by adding upstream patch#16
Conversation
|
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 ( |
|
@conda-forge-admin, please rerender |
…da-forge-pinning 2020.06.24.16.31.11
|
@isuruf |
|
Thanks |
|
I just realised I forgot to bump the build number on this. 😬 Any follow-ups we should do? Revert this PR on master (so the previous version gets published again with build number 0), and then reissue the PR with a bumped build number? |
|
Thanks. But will 21e687c not have replaced the original buildnum=0 builds already? In any case, sorry for the extra work. 😞 |
|
No, there's no uploading if the same build (with same hash) exists. |
|
Seems there is another (windows-specific) problem: It already kept retrying a couple of times, but that permission error is not gonna go away, I presume... |
|
I checked on anaconda.org, and the packages did get uploaded. However, the build-number thing caused an extra upload of 0.7.0*_0 for windows, since apparently the package hash had changed (due to the compiler bump to vs2017?). I don't think that has a huge impact, but just FYI. |
Closes #15.
Follows recommendation by @isuruf.