Update b2bTools to v3.0.7 #48749
Update b2bTools to v3.0.7 #48749
Conversation
|
@BiocondaBot please fetch artifacts |
|
Package(s) built are ready for inspection:
Docker image(s) built:
|
|
@BiocondaBot please fetch artifacts |
|
No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped. |
|
@BiocondaBot please fetch artifacts |
|
No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped. |
|
|
||
| build: | ||
| number: 0 | ||
| script: "{{ PYTHON }} -m pip install . --ignore-installed --no-deps -vv" | ||
| noarch: python | ||
| skip: true # [py >= 311] |
There was a problem hiding this comment.
I think this is the reason why nothing has been built.
There was a problem hiding this comment.
Thanks for your help @martin-g, really appreciated. We are trying to finish this recipe as soon as possible.
Unfortunately there is a dependency (pomegranate) that doesn't support neither Py311 nor Py312 for the version we need to install >=0.14.8, <0.14.10. That limits our support to both Py311 and Py312 :/ The only way we found to install it using conda was requesting the dependency from pip, but that is not a possibility in bioconda recipes, isn't it ? Otherwise we could try to build that dependency from the sources, but I couldn't figure out how to make it. Would it be possible to do it in the build script ? Basically we would need to do:
pip install "cython~=0.29.14" "scipy>=0.17.0"
git clone -b v0.14.9 --single-branch https://github.com/jmschrei/pomegranate.git
cd pomegranate
python setup.py install
|
@BiocondaBot please fetch artifacts |
|
@BiocondaBot please add label |
|
Package(s) built are ready for inspection:
Docker image(s) built:
|
Update b2bTools package to v3.0.7 published on 24th April 2024 on PyPi.
What's new?
pomegranate<1.0pomegranate<1.0Please read the guidelines for Bioconda recipes before opening a pull request (PR).
General instructions
@BiocondaBot please add labelcommand.@bioconda/corein a comment.Instructions for avoiding API, ABI, and CLI breakage issues
Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify
run_exports(see here for the rationale and comprehensive explanation).Add a
run_exportssection like this:with
...being one of:{{ pin_subpackage("myrecipe", max_pin="x") }}{{ pin_subpackage("myrecipe", max_pin="x.x") }}{{ pin_subpackage("myrecipe", max_pin="x.x") }}(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin="x.x.x") }}(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin=None) }}while replacing
"myrecipe"with eithernameif aname|lowervariable is defined in your recipe or with the lowercase name of the package in quotes.Bot commands for PR management
Please use the following BiocondaBot commands:
Everyone has access to the following BiocondaBot commands, which can be given in a comment:
@BiocondaBot please update@BiocondaBot please add labelplease review & mergelabel.@BiocondaBot please fetch artifactsYou can use this to test packages locally.
Note that the
@BiocondaBot please mergecommand is now depreciated. Please just squash and merge instead.Also, the bot watches for comments from non-members that include
@bioconda/<team>and will automatically re-post them to notify the addressed<team>.