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

testpath v0.4.2 #8

Merged
merged 11 commits into from
Oct 5, 2018
Merged

testpath v0.4.2 #8

merged 11 commits into from
Oct 5, 2018

Conversation

regro-cf-autotick-bot
Copy link
Contributor

It is very likely that the current package version for this feedstock is out of date.
Notes and instructions for merging this PR:

  1. Please check that the dependencies have not changed.
  2. Please merge the PR only after the tests have passed.
  3. Feel free to push to the bot's branch to update this PR if needed.
  4. The bot will almost always only open one PR per version.

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!

@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.

@ocefpaf
Copy link
Member

ocefpaf commented Oct 2, 2018

@conda-forge-admin, please rerender

@takluyver
Copy link
Contributor

There was a build failure on Appveyor which looked spurious (traceback coming from pip), so I prodded it to restart. Looks like there's quite a queue on Appveyor at the moment, though.

@takluyver
Copy link
Contributor

Should we try making this a noarch package? I think it meets the requirements, and the delays on Appveyor are kind of extreme.

@takluyver
Copy link
Contributor

@conda-forge-admin, please add noarch: python

@takluyver
Copy link
Contributor

Looks like we're running into pypa/pip#5679 , which is due to be fixed in pip 18.1.

This can probably be restored when pip 18.1 is available
@takluyver
Copy link
Contributor

I forgot about the binary file there... back to regular packages

@takluyver
Copy link
Contributor

@conda-forge-admin, please rerender

@jasongrout
Copy link

Thanks for your work on this! Is there anything I can do to help this get published? If I understand things right, this fixes the errors that are cropping up from installing testpath 0.4 noted at #6?

jasongrout added a commit to jasongrout/jupyter-renderers that referenced this pull request Oct 5, 2018
I think this may solve the error at https://travis-ci.org/jupyterlab/jupyter-renderers/builds/437449573#L431. See conda-forge/testpath-feedstock#6 and conda-forge/testpath-feedstock#8 for details. Once testpath 4.2 is released, hopefully this is fixed.
jasongrout added a commit to jasongrout/jupyter-renderers that referenced this pull request Oct 5, 2018
Immediately, this solves the error at https://travis-ci.org/jupyterlab/jupyter-renderers/builds/437449573#L431. See conda-forge/testpath-feedstock#6 and conda-forge/testpath-feedstock#8 for details.

In general, I think it's good to test against the open conda-forge packages.
@minrk
Copy link
Member

minrk commented Oct 5, 2018

Latest build is fixed. Thanks @takluyver!

@minrk minrk merged commit ad4f3f3 into conda-forge:master Oct 5, 2018
@jasongrout
Copy link

Thanks!

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.

7 participants