Hello Kyle,
The Galaxy main tool shed tracks the Galaxy-dist repo on bitbucket, and it
looks like you are tracking Galaxy-central in your local Galaxy instance.
Tool shed features have evolved rapidly over the past year, which has made it
difficult to keep a stable communication layer
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)
