search

conda-forge / pycapnp-feedstock

A conda-smithy repository for pycapnp.
BSD 3-Clause "New" or "Revised" License
1 stars 7 forks source link

Update meta.yaml #2

Closed szs8 closed 7 years ago

szs8 commented 8 years ago

Updated md5 for 0.5.9

conda-forge-linter commented 8 years ago

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.

szs8 commented 8 years ago

Seems to fail because something external to pycapnp.

frol commented 8 years ago

@jakirkham I see that there was an issue in conda-smithy and conda-build 2.0 (https://github.com/conda-forge/conda-smithy/issues/282). I also see that the pinning was applied. How should I proceed with this PR? Merging it now seems to me like a bad idea since the packages won't be published anyway.

ocefpaf commented 8 years ago

@frol and @szs8 you need to rerender the feedstock with latest conda-smithy.

conda install -c conda-forge conda-smithy
conda smithy rerender  # from the recipe root dir
frol commented 8 years ago

@ocefpaf This conda-build 2.0 compatibility issue seems to be common for every single feedstock. Should the conda-forge bot rerender all feedstocks then?

ocefpaf commented 8 years ago

Indeed. That would be better. Ping @pelson.

On Sep 2, 2016 2:13 AM, "Vlad Frolov" notifications@github.com wrote:

@ocefpaf https://github.com/ocefpaf This conda-build 2.0 compatibility issue seems to be common for every single feedstock. Should the conda-forge bot rerender all feedstocks then?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/conda-forge/pycapnp-feedstock/pull/2#issuecomment-244284969, or mute the thread https://github.com/notifications/unsubscribe-auth/AA6BL-XyCV1mMlYXMz28Hme1Yvql371Aks5ql7COgaJpZM4Jy7CG .

jakirkham commented 8 years ago

The bot is running as far as I know. It isn't running with the newest conda-smithy (unless it got updated), but it is new enough to have that fix. Though we could try to amp up the rate that it generates the re-rendering PRs at. Would need to discuss that first though.

frol commented 7 years ago

Updated to 0.5.10 in #6.