-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
ENH support .conda format #182
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 rerender |
…nda-forge-pinning 2022.01.29.15.10.18
@conda-forge/core Is this recipe supposed to generate ~76 variants? I guess yes, it just seems like a lot. |
I guess we could build some downstream CUDA tests for all of the variants and list them here. We'd have to update the list here manually which kind of stinks. I think the right answer here is some sort of intrinsic testing loop over variants within conda build, but who has the time! Moving on. |
@conda-forge-admin rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you but ran into some issues. Please check the output logs of the latest rerendering GutHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or try re-rendering locally. This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-ci-setup-feedstock/actions/runs/1879574153. |
@conda-forge-admin rerender |
…nda-forge-pinning 2022.02.21.21.55.10
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
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 rerender |
1 similar comment
@conda-forge-admin rerender |
…nda-forge-pinning 2022.11.07.13.22.21
Thanks @xhochy. This needs to be tested before it is merged. |
Code was looking but I was under the impression that this would simply be for preparation and we could not really test this yet? |
We can copy the package wholesale to our test feedstock and it will get run live there. Not going to do that today but will do before we merge. |
This one is being tested here: conda-forge/cf-autotick-bot-test-package-feedstock#439 |
@conda-forge/core This one is ready for review. It lets us upload .conda artifacts by setting a key in the conda-forge.yml. This key is not read by smithy, but is instead used by the ci setup code the builds the |
Should we go ahead and add that key to feedstocks, but set it to |
You would want to set it to |
Or at least we don't gain anything by setting it to |
Sorry Edit: Am guessing at some point in the future we would want |
I'm not following sorry. The possible values are
The code here does
Once we want to move the default, we change
to
So the current default of tar.bz2 is hard coded into our scripts until we change it. Does that answer your question? |
@conda-forge/core any more comments here? |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)This PR adds support for .conda artifacts.