hi all. just joined as maintainer for
pyro-ppl-feedstock which depends on pytorch. Yesterday there was a new release of both packages and pyro-ppl depends on the latest release of pytorch, which is not yet on conda-forge (it is available on the pytorch channel). I updated the feedstock but I'm wondering if it will be available, given that the build fails?
you may be able to configure the feedstock to use the pytorch channel
I have lost track of this detail
someone else from core may be able to help
but if it's possible that works
there are multiple outstanding PRs on
pytorch-cpu-feedstock and I am not eager to become a maintainer there...but I can open a PR
unfortunately if the pytorch builds timeout, then we have to build by hand
and that process is annoying
the pytorch maintainers are the best ppl to ask on this
BTW @jamestwebber we have jax so numpyro would be cool to have around if it is not already
i'm not sure who maintains it
oh it's one of the Pyro maintainers, that makes sense
Question, based on the discussion further up: Is
From what I can find in conda-forge/importlib_metadata-feedstock#47 there was an idea but I cannot find it implemented here: https://github.com/conda-forge/importlib_metadata-feedstock/blob/master/recipe/meta.yaml
importlib-metadata actually empty for >3.7?From what I can find in conda-forge/importlib_metadata-feedstock#47 there was an idea but I cannot find it implemented here: https://github.com/conda-forge/importlib_metadata-feedstock/blob/master/recipe/meta.yaml
Or am I missing something?
(I have the same problem as above so I was just looking this up :smile: )
I just merged a PR to a Cython package, adding osx-arm64 builds. The builds passed but it appears that the osx-arm64 builds fail on import. I should mark as broken and remove
build_platform: {osx_arm64: osx_64} from conda-forge.yml right? Just making sure I don't miss a step since I'm "un-migrating."
8 replies
Can somebody from core take a look at conda-forge/defusedxml-feedstock#6 - I opened a separate pull request to fix the failing tests conda-forge/defusedxml-feedstock#7 and another one for adding myself as a maintainer to continue updating the package in future conda-forge/defusedxml-feedstock#8
Regarding C++17 on macOS please see conda-forge/clang-compiler-activation-feedstock#17
this could be a fun addition to conda-build / conda-forge linters: https://github.com/koalaman/shellcheck
I mistakenly published a release candidate of https://github.com/conda-forge/pyscaffold-feedstock to the main channel. Can I change the label to rc with repodata-patches, or should I mark it as broken?
(it will take a while for the CDN to update and it to be removed from the main channel)
Thanks so much!!!!! (I was feeling bad for messing that up.)
Shortly before asking for help, I tried to solve the problem myself by creating a new
Shortly before asking for help, I tried to solve the problem myself by creating a new
rc branch, adding pyscaffold_rc as the channel target in recipe/conda_build_config.yaml, making an empty commit and corresponding pull request to request a rerender. Was I on the right track? Should I keep or delete this branch?
That's the right thing to do, but it doesn't have any affect one a build has already been uploaded. We have this repo for marking packages as "broken" but I don't think there is anything automated for moving things to dev or rc channels
Could someone help me troubleshoot why conda-forge/pytkdocs-feedstock#7? I've documented a few things in conda-forge/pytkdocs-feedstock#9 as well. I'm encountering some odd errors that I don't understand. Thank you!
Hi, just in case someone is around, here is a new staged recipe ready for merging: conda-forge/staged-recipes#14178
This one (LAPACK++) is a follow-up of a similar one for BLAS++ merged yesterday