7 months ago by
Update: I asked the IUC developers (at their gitter channel) if there were any known issues and was informed that a conda bug is impacting some tool installs (https://github.com/conda/conda/issues/6269). The devs are working to correct this. I couldn't determine, for Galaxy tool installs, and specifically bcftools, if this means that directly installing the correct version of the conda dependency(ies) is a potential solution or not. I asked for feedback and will post back here once there is a confirmed workaround (if any).
Meanwhile, you could also review the conda ticket and if you want and/or see if installing the dependencies directly with conda solves the problem. Under the Admin tab, section Tool Management > Manage dependencies, do a "find" with your web browser will locate those associated with bcftools. I suspect you will find that some are not installed or were installed but with an incompatible version (if I understood that part of the conda ticket correctly!).
This could be a bit tedious to do (install, set paths, etc) - so the best workaround, for now, is probably to instead install a version of bcftools stats that did not use conda dependencies. That would be the wrapper version 1.3 from Jan 2017. It is here in Main Tool Shed and you can also navigate to this earlier version during admin install: https://toolshed.g2.bx.psu.edu/view/iuc/bcftools_stats/f8e9951c94b1 (note: the tabix warning on the repo can be ignored). Or if you are installing the entire bcftools suite, use the same version from Jan 2017.
You should probably uninstall the current version of bcftools first so that it is clear in the tool panel which tools are usable without having to click on them to review the version. Or you could create/name a new tool group, in an informative way, to place the earlier version into during install (full suite or just this tool).
This tool is not installed at Galaxy Main (https://usegalaxy.org), but it is at Galaxy Test (https://test.galaxyproject.org/). This is also the earlier version 1.3. Not all of the dependencies are installed, so using the stats tool there might be problematic, but you could try just to see how the tool works. We really do testing on that server and configuration can change at any time, so it is not recommended to do analysis there beyond trying out tools/tool versions not on Main (to see how they work - when working!) or when getting involved in new tool testing.
Hope that one of these choices will work out for you! Jen, Galaxy team