Try only documented requirements#22
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, please rerender |
…nda-forge-pinning 2024.06.21.08.07.40
|
Well it at least built successfully. Thoughts on this one @bgruening @dschreij ? |
|
Friendly ping @bgruening @dschreij 🙂 |
|
To give a bit more of motivation of this PR, |
|
@conda-forge/core The PR is blocking libopencv 4.10 migration (see conda-forge/bipedal-locomotion-framework-feedstock#69) and per https://conda-forge.org/docs/maintainer/maintainer_faq/#a-feedstock-has-been-abandoned-and-i-would-like-to-take-over-maintenance the period of ~1 week without any maintainer response have passed. Furthermore, the last PR merged by a mantainer (as opposed to a core member) dates back to 2020, see #11 . Given that, it would be great to merge this PR to unblock libopencv migration and other zlib==1.3 related conflicts, and if a new maintainer is necessary I am happy to volunteer (see #24) |
|
Thanks @ocefpaf! |
Checklist
Reset the build number to0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)At least according to https://xiph.org/theora/ which links to the 1.1.1 source:
So it doesn't seem like
zliborlibpngdependencies should be needed to be specified. But this is a bit of a shot in the dark from my end. Hopefully the CIs will tell us. 🤷Closes #21