try to restore group_humann2_uniref_abundances_to_go recipe #53474
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
currently fails for me with ``` [Jan 25 12:41:44] SERR [Jan 25 12:41:44] SERR LibMambaUnsatisfiableError: Encountered problems while solving: [Jan 25 12:41:44] SERR - package humann2-2.8.1-py27_0 requires python >=2.7,<2.8.0a0, but none of the providers can be installed [Jan 25 12:41:44] SERR [Jan 25 12:41:44] SERR Could not solve for environment specs [Jan 25 12:41:44] SERR The following package could not be installed [Jan 25 12:41:44] SERR └─ group_humann2_uniref_abundances_to_go 1.3.0** is not installable because it requires [Jan 25 12:41:44] SERR ├─ goatools with the potential options [Jan 25 12:41:44] SERR │ ├─ goatools 1.2.3 would require [Jan 25 12:41:44] SERR │ │ └─ python_abi 3.10.* *_cp310, which can be installed; [Jan 25 12:41:44] SERR │ ├─ goatools 1.2.3 would require [Jan 25 12:41:44] SERR │ │ └─ python_abi 3.7.* *_cp37m, which can be installed; [Jan 25 12:41:44] SERR │ ├─ goatools 1.2.3 would require [Jan 25 12:41:44] SERR │ │ └─ python_abi 3.8.* *_cp38, which can be installed; [Jan 25 12:41:44] SERR │ ├─ goatools 1.2.3 would require [Jan 25 12:41:44] SERR │ │ └─ python_abi 3.9.* *_cp39, which can be installed; [Jan 25 12:41:44] SERR │ ├─ goatools [1.3.1|1.3.11|...|1.4.9] would require [Jan 25 12:41:44] SERR │ │ └─ python >=3.7 with the potential options [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.0|3.10.1|...|3.9.9], which can be installed; [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.0|3.10.1|...|3.9.9] would require [Jan 25 12:41:44] SERR │ │ │ └─ openssl >=1.1.1l,<1.1.2a , which can be installed; [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.4|3.8.13|3.9.12] would require [Jan 25 12:41:44] SERR │ │ │ └─ openssl >=1.1.1n,<1.1.2a , which can be installed; [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.5|3.9.13] would require [Jan 25 12:41:44] SERR │ │ │ └─ openssl >=1.1.1o,<1.1.2a , which can be installed; [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.6|3.11.0] would require [Jan 25 12:41:44] SERR │ │ │ └─ openssl >=1.1.1q,<1.1.2a , which can be installed; [Jan 25 12:41:44] SERR │ │ ├─ python [3.7.0|3.7.1|...|3.8.8], which can be installed; [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.15|3.11.10|...|3.8.20] would require [Jan 25 12:41:44] SERR │ │ │ └─ openssl >=3.3.2,<4.0a0 , which can be installed; [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.16|3.11.11|3.12.8|3.13.0|3.13.1] would require [Jan 25 12:41:44] SERR │ │ │ └─ openssl >=3.4.0,<4.0a0 , which can be installed; [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.7|3.10.8|...|3.9.15] would require [Jan 25 12:41:44] SERR │ │ │ └─ openssl >=1.1.1s,<1.1.2a , which can be installed; [Jan 25 12:41:44] SERR │ │ └─ python [3.12.0rc3|3.13.0rc1|3.13.0rc2|3.13.0rc3] would require [Jan 25 12:41:44] SERR │ │ └─ _python_rc, which does not exist (perhaps a missing channel); [Jan 25 12:41:44] SERR │ ├─ goatools 1.4.12 would require [Jan 25 12:41:44] SERR │ │ └─ python >=3.9 with the potential options [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.0|3.10.1|...|3.9.9], which can be installed; [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.0|3.10.1|...|3.9.9], which can be installed (as previously explained); [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.4|3.8.13|3.9.12], which can be installed (as previously explained); [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.5|3.9.13], which can be installed (as previously explained); [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.6|3.11.0], which can be installed (as previously explained); [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.15|3.11.10|...|3.8.20], which can be installed (as previously explained); [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.16|3.11.11|3.12.8|3.13.0|3.13.1], which can be installed (as previously explained); [Jan 25 12:41:44] SERR │ │ ├─ python [3.10.7|3.10.8|...|3.9.15], which can be installed (as previously explained); [Jan 25 12:41:44] SERR │ │ └─ python [3.12.0rc3|3.13.0rc1|3.13.0rc2|3.13.0rc3], which cannot be installed (as previously explained); [Jan 25 12:41:44] SERR │ ├─ goatools [0.5.9|0.6.10|...|1.2.3] conflicts with any installable versions previously reported; [Jan 25 12:41:44] SERR │ └─ goatools 0.7.11 would require [Jan 25 12:41:44] SERR │ └─ pywget, which does not exist (perhaps a missing channel); [Jan 25 12:41:44] SERR ├─ humann2, which requires [Jan 25 12:41:44] SERR │ └─ python [2.7* |>=2.7,<2.8.0a0 ] but there are no viable options [Jan 25 12:41:44] SERR │ ├─ python [2.7.12|2.7.13|2.7.14|2.7.15] would require [Jan 25 12:41:44] SERR │ │ ├─ openssl 1.0.* , which conflicts with any installable versions previously reported; [Jan 25 12:41:44] SERR │ │ └─ python_abi * *_cp27mu, which conflicts with any installable versions previously reported; [Jan 25 12:41:44] SERR │ ├─ python 2.7.15 would require [Jan 25 12:41:44] SERR │ │ └─ python_abi * *_cp27mu, which conflicts with any installable versions previously reported; [Jan 25 12:41:44] SERR │ ├─ python 2.7.15 would require [Jan 25 12:41:44] SERR │ │ └─ python_abi 2.7.* *_cp27mu, which conflicts with any installable versions previously reported; [Jan 25 12:41:44] SERR │ └─ python 2.7.15 would require [Jan 25 12:41:44] SERR │ ├─ openssl >=1.0.2o,<1.0.3a , which conflicts with any installable versions previously reported; [Jan 25 12:41:44] SERR │ └─ python_abi * *_cp27mu, which conflicts with any installable versions previously reported; [Jan 25 12:41:44] SERR └─ python <3 but there are no viable options [Jan 25 12:41:44] SERR ├─ python [2.7.12|2.7.13|2.7.14|2.7.15], which cannot be installed (as previously explained); [Jan 25 12:41:44] SERR ├─ python 2.7.15, which cannot be installed (as previously explained); [Jan 25 12:41:44] SERR ├─ python 2.7.15, which cannot be installed (as previously explained); [Jan 25 12:41:44] SERR ├─ python 2.7.15, which cannot be installed (as previously explained); [Jan 25 12:41:44] SERR └─ python [1.0.1|1.2|...|2.6.9] conflicts with any installable versions previously reported. ```
since 0.6.4 is excluded by strict repo priority
|
Impossible due to strict-repo priority:
For the Galaxy project where we could need this (bgruening/galaxytools#1568) we might solve this with: galaxyproject/galaxy#19425 Edit: But the post-link.sh will still fail -- i.e. also trying non-strict solving will not help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
currently fails for me with
Describe your pull request here
Please 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>.