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.
Possible build number issue with conda smithy 3.1.12
See original GitHub issueBuilding the recipe fails on circleci and travis-ci for https://github.com/conda-forge/fastscapelib-feedstock, which has just been created, with the following error:
ValueError("More than one build number found, giving up")
(note: all tests passed on staged-recipes PR)
The recipe of this feedstock has the particularity of using custom compilers on linux and having two outputs, although only one build number is defined in the top build section in meta.yaml.
The error above causes aborting the build on circleci, but on travis-ci the packages seem to be still correctly built/uploaded.
I suspect that this related to #836. I’ve re-rendered with conda-smithy 3.1.11 just to check (see https://github.com/conda-forge/fastscapelib-feedstock/pull/2) and the error is gone.
Is this a conda-smithy bug or is there anything wrong in the recipe?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 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
Opened https://github.com/conda/conda-build/issues/3095.
Any workaround?