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

Arch Migrator #67

Conversation

regro-cf-autotick-bot
Copy link

This feedstock is being rebuilt as part of the aarch64/ppc64le migration.

Feel free to merge the PR if CI is all green, but please don't close it
without reaching out the the ARM migrators first at @conda-forge/arm-arch.

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 regro-cf-autotick-bot.
The regro-cf-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://github.com/regro/autotick-bot/actions/runs/840165127, 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.

kkraus14
kkraus14 previously approved these changes May 13, 2021
@kkraus14 kkraus14 added the automerge Merge the PR when CI passes label May 13, 2021
Copy link
Member

@leofang leofang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should keep this PR open, as it's not doing anything real and the rest of infrastructure is not ready yet.

@jakirkham
Copy link
Member

Yeah that's right. This isn't actually ready to merge despite the green checkmark.

@kkraus14 kkraus14 removed the automerge Merge the PR when CI passes label May 14, 2021
@kkraus14 kkraus14 dismissed their stale review May 14, 2021 00:54

I apparently don't know what I'm doing :)

@jakirkham
Copy link
Member

For context Keith, I think we are missing cudatoolkit ( conda-forge/cudatoolkit-feedstock#56 ) and Docker images currently. The latter might not be strictly needed to merge this though. The former is needed as we have it in run_exports:

run_exports:
strong:
- cudatoolkit {{ cuda_compiler_version }}|{{ cuda_compiler_version }}.*

Think that is it, but correct me if you see something else missing Leo

@leofang
Copy link
Member

leofang commented May 14, 2021

Thanks John for filling in the context! Yes I think it's right. The order of getting nvcc or the docker image done first does not matter, as long as they're done before we fire up a global migrator IIUC.

@regro-cf-autotick-bot
Copy link
Author

I see that this PR has conflicts, and I'm the only committer. I'm going to close this PR and will make another one as appropriate. This was generated by https://github.com/regro/autotick-bot/actions/runs/1286090543

@regro-cf-autotick-bot regro-cf-autotick-bot deleted the bot-pr_arch_h2e0309 branch September 29, 2021 09:13
@jakirkham
Copy link
Member

ppc64le was addressed in PR ( #66 ) and aarch64 in PR ( #70 )

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