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.
r-stringi and r-stringr R 3.5 win64 packages being pulled from defaults instead of conda-forge
See original GitHub issueIn several R recipes that specify r-stringi and r-stringr as dependencies, in the Windows R3.5 build those packages are being pulled from defaults instead of conda-forge, leading to build errors. For R 3.4 build they are pulled from conda-forge as they should.
Examples:
https://ci.appveyor.com/project/conda-forge/r-recipes-feedstock/build/1.0.7/job/8jyn8ky5eef97vlf https://ci.appveyor.com/project/conda-forge/r-reprex-feedstock/build/1.0.2/job/ikd87p47gemnvko1
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (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
Thanks @jdblischak, I restarted the other builds but had forgotten about
r-recipes.Option 1) from John for now and option 2) for later/next r-base update? I don’t see any reason to not have iuc for Windows by default.