Conversation
No idea if this is a bug in the conda recipe? |
| <expand macro="requirements"/> | ||
| <expand macro="version_command"/> | ||
| <command detect_errors="aggressive"><![CDATA[ | ||
| ln -s '$input' ./input.{$input.ext} && |
There was a problem hiding this comment.
@pavanvidem this is just a guess. I hope this helps with https://github.com/usegalaxy-eu/issues/issues/978
There was a problem hiding this comment.
Its not clear if its working and if we need this for all tools here.
|
latest conda version that works v2.7.0. For now, keeping it to v2.7.0. I tried to fix the recipe, but no luck so far. When I compiled v2.7.2 independently of conda, it worked, though. |
|
Good for me, if the tests are passing :) |
| <description>Simulate cotranscriptional folding of RNAs</description> | ||
| <macros> | ||
| <token name="@EXECUTABLE@">kinwalker</token> | ||
| <token name="@TOOL_VERSION@">2.6.4</token> |
There was a problem hiding this comment.
@pavanvidem I downgraded kinwalker here. Its not working for me in 2.7.
@RaumZeit is this known? We get corrupted files or segfaults using the conda package/conatainer in version 2.7.x
FOR CONTRIBUTOR:
There are two labels that allow to ignore specific (false positive) tool linter errors:
skip-version-check: Use it if only a subset of the tools has been updated in a suite.skip-url-check: Use it if github CI sees 403 errors, but the URLs work.