3.2 years ago by
United States
Hello,
It seems like both of these issues are rooted in the same problem - managed dependencies are not installing correctly.
To answer the original question, the devteam wrapper for v14 should install dependencies including the binary. Make certain that you check this option when installing. If there are issues, the error messages associated with the install should note what is wrong. In particular, is a dependency is missing or is unable to be "checked" for managed install, it means that your galaxy.ini must be modified to specify where managed dependencies should be installed (path to a Galaxy accessible, existing directory).
That said, using the updated tool wrapper is a better choice. So going forward with troubleshooting that is worth it unless you really need to use the older version for some reason (to reproduce a prior analysis, etc).
Thanks, Jen, Galaxy team
Why not using the MACS2 version from the IUC?
Hi Bjoern,
I installed MACS2
After the whole install when I try to test I keep getting this error
Hi David, Just jumping in here, Bjoern will know the most about the MAC2 wrapper as he was involved in writing it, but I am wondering if you are using managed dependencies when installing from the Tool Shed into your local. If so, are those dependency package(s) installed correctly when you review them through the Admin tools? Maybe this will help, Jen, Galaxy team
Hi,
can you provide us a few more informations? Are other dependencies installable on your system? How do you test these wrappers? You are running it from within Galaxy right?