2.8 years ago by
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