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

ipykernel v5.2.0 #56

Merged
merged 3 commits into from
Mar 22, 2020
Merged

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 for merging this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version.
    Checklist before merging this PR:
  • Dependencies have been updated if changed
  • Tests have passed
  • Updated license if changed and license_file is packaged

Note that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.

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. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

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/15258, please use this URL for debugging

@conda-forge-linter
Copy link

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

  • Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

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

@blink1073 blink1073 mentioned this pull request Mar 22, 2020
@blink1073
Copy link
Member

Thanks @bollwyvl, miss your face my friend!

@bollwyvl
Copy link
Contributor

I think the win37 fail was flake...

@blink1073 thanks for keeping the ship moving! my FOSS time is somewhat... limited at present 😷, but I'm hoping to be able to bring some more stuff online soon through $DAY_JOB... JCon might be a stretch this year (again, 😷, but also just time, which is sad, as I love 🐻lin) but maybe we can raise our distributed-events-as-normal game as a side-effect of all this...

@bollwyvl bollwyvl closed this Mar 22, 2020
@bollwyvl bollwyvl reopened this Mar 22, 2020
@bollwyvl
Copy link
Contributor

Ok, it's happy: I'll merge and watch the build for ❄️...

@bollwyvl bollwyvl merged commit ec2a845 into conda-forge:master Mar 22, 2020
@bollwyvl
Copy link
Contributor

Looks good:

| linux-64/ipykernel-5.2.0-py36h95af2a2_0.tar.bz2
| linux-64/ipykernel-5.2.0-py37h43977f1_0.tar.bz2
| linux-64/ipykernel-5.2.0-py38h23f93f0_0.tar.bz2
| linux-aarch64/ipykernel-5.2.0-py36hac0dd68_0.tar.bz2 
| linux-aarch64/ipykernel-5.2.0-py37hc6149b9_0.tar.bz2
| linux-aarch64/ipykernel-5.2.0-py38h1cdfbd6_0.tar.bz2
| linux-ppc64le/ipykernel-5.2.0-py36hac0dd68_0.tar.bz2
| linux-ppc64le/ipykernel-5.2.0-py37hc6149b9_0.tar.bz2
| linux-ppc64le/ipykernel-5.2.0-py38h1cdfbd6_0.tar.bz2
| osx-64/ipykernel-5.2.0-py36h95af2a2_0.tar.bz2
| osx-64/ipykernel-5.2.0-py37h43977f1_0.tar.bz2
| osx-64/ipykernel-5.2.0-py38h23f93f0_0.tar.bz2
| win-64/ipykernel-5.2.0-py36h5ca1d4c_0.tar.bz2
| win-64/ipykernel-5.2.0-py37h5ca1d4c_0.tar.bz2
| win-64/ipykernel-5.2.0-py38h5ca1d4c_0.tar.bz2

@blink1073
Copy link
Member

Best to you and your family. I suspect Scipy and JCon will both be remote, following PyCon's lead.

@jakirkham
Copy link
Member

They might move the dates further out.

bollwyvl pushed a commit to bollwyvl/ipykernel-feedstock that referenced this pull request Dec 27, 2022
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.

5 participants