Thanks for looking into this Greg. The environment where I'm having
this problem is our testing and production systems.
Both environments are CentOS release 5.8 (Final) with Mercurial version
2.4.1.
Interestingly, when I tried the same thing with a development setup on
my OSX box (10.6.8) w
Hi Lance,
I tried several scenarios today in an attempt to reproduce this but I was not
able to. Have you tried uninstalling the repository (check the checkbox to
completely uninstall it) and then reinstall it? I'm trying to reproduce this
on a mac running mercurial version 2.2.3 and Python 2
Since I've had issues with workflow and the toolshed in the past, I have
changed my workflow so that my only interaction with the toolshed is
either via uploading a tarball via the web interface or installing a
tool into my local Galaxy via the web interface (or occasionally just
downloading ta
Hi Lance,
What process did you use for updating the tool shed repository and how many
separate repositories did you use? You should not be updating a local
repository, pushing the changes to the tool shed repository, and then
attempting to pull the changes back to the same repository. Your re
I recently updated the htseq-count tool in the Galaxy toolshed to
version 0.3. This version has some functional changes and thus the tool
version was incremented. I installed this new version of the tool in my
local Galaxy instance.
However, I realized later that I missed updating one part o
