Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
conda-smithy adds R 3.4.2 to build matrix
See original GitHub issueconda-forge has r-base 3.3.2 and 3.4.1 available:
https://anaconda.org/conda-forge/r-base/files
However, conda smithy rerender sometimes adds R 3.4.2 to the build matrix. This is presumably because R 3.4.2 is now available in the r channel:
https://anaconda.org/r/r-base/files
Here’s an an example rerendering PR that adds R 3.4.2:
https://github.com/conda-forge/r-ape-feedstock/pull/1
A similar issue is happening on staged-recipes, where recipes for new R packages are being built with R 3.4.2:
https://github.com/conda-forge/staged-recipes/issues/4320
Is it possible to limit the build matrix to only include R versions available on the conda-forge channel?
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (12 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
You guys rock!
And a follow-up question, what version of conda smithy is used by staged-recipes? This problem is currently blocking multiple R recipes from being merged: https://github.com/conda-forge/staged-recipes/issues/4320