Restrict ome-zarr version range in meta.yaml#33
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 ( |
jdblischak
left a comment
There was a problem hiding this comment.
This will require a repodata patch as well. I can submit that once the other maintainers approve and merge this PR.
Some thoughts:
- Can we add a simple test that would catch this incompatibility if it arises in the future?
- Has this been reported upstream in the spatialdata and/or ome-zarr repositories?
|
@jdblischak thanks. The ome-zarr update was made 2 days ago. |
|
@LucaMarconato please review |
|
LGTM thanks! I'm working on merging a fix for it, that will be included in the next release (scverse/spatialdata#1092). But until then this patch will fix the install. |
|
I submitted a repodata patch in conda-forge/conda-forge-repodata-patches-feedstock#1176. Please review/approve |
Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)Spatialdata does not work with the latest ome-zarr version 0.14.0.
It fails with this error:
or
@pavanvidem found it when we were testing the spatialdata wrapper on Galaxy. (here)