Hello Brian,

I have just tried to install and uninstall NVC on my development machine multiple times and was not able to replicate the problem. However I have seen similar things before. Let me ask you few questions:

Are you using Admin UI for installation or API scripts?
Does the 'installed tool shed repos' page show multiple installations of the same package (with the same changesets)? If so what are the states of these?
If you check on the filesystem in the {{configured_dependency_dir}}/path/to/duplicated/package do you see any strange stuff/duplication?
How big is your Galaxy in terms of installed tools, complexity of setup and traffic?

Sorry for the many questions but I hope it might help us track down the problems.

Thank you

Martin, Galaxy Team

On Mon Feb 23 2015 at 10:38:08 PM Brian Claywell <bclaywel@fredhutch.org> wrote:
First, I'm at a bit of a loss to even describe what's going on, so I apologize in advance for a rambling bug report. Please bear with me! 

The naive_variant_caller tool was failing on our instance with "Failed to resolve dependency" errors on numpy, pyBamParser, and pyBamTools, despite the tool dependencies and their respective dependency packages being installed. 

I attempted to use the "repair repository" action on naive_variant_caller with no success. I then uninstalled naive_variant_caller, package_numpy_1_7, package_pybamparser_0_0_1, and package_pybamtools_0_0_1 and attempted to reinstall naive_variant_caller from scratch, again allowing Galaxy to manage the dependencies.

This time, the dependencies resolved (at least as far as the "Building dependency shell command" messages were concerned), but naive_variant_caller still failed, this time with an import error:

ImportError: No module named pyBamTools.genotyping.naive

Digging around a little I found that the env.sh that was sourced for pyBamTools was looking for an env.sh in another pyBamTools revision directory, but the revision it was looking for didn't exist.

Then I looked in the admin interface and saw that package_pybamtools_0_0_1 and package_pybamparser_0_0_1 were each installed twice; each had both the most recent revision and an older revision with the "updates are available" icon.

At this point I uninstalled naive_variant_caller and all of its dependency packages again. I then installed naive_variant_caller from the toolshed *without* dependency management, and manually installed the required revisions of numpy, pybamparser, and pybamtools. Finally naive_variant_caller started working.

However, naive_variant_caller is now shown in the admin interface as "Installed, missing repository dependencies", and the installed repository page shows that the dependencies are a very strange state (see attached screenshot). That is, the same revision of numpy is listed as installed twice, and the pybamparser and pybamtools dependencies are each listed as simultaneously installed and uninstalled.

Can anyone shed some light on what could be happening and what to do about it? Is there some external way to verify the consistency of a tool and its dependencies?




Brian Claywell | programmer/analyst
Matsen Group   | http://matsen.fredhutch.org
Fred Hutchinson Cancer Research Center
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

To search Galaxy mailing lists use the unified search at: