Yes that was my conclusion, thanks Peter.
As a result I switched to a new table named (shapeit2_ref) and a new tool
name (data_manager_shapeit2_reference) and from planemo side upload seemed
to succeed but the tool is in an error state. I resorted to manually
editing the tool-data table.
Data
Hi Peter vH,
I wonder if adding columns is not supported - because some tools
would define the table without the extra column? You might have
to define a new data table instead (with largely the same content).
But to be clear, I am not an expert in this area of Galaxy.
However, it does seem the
A bit more tracing leads me to suspect that what is happening is that a
merge is being called here:
https://github.com/galaxyproject/galaxy/blob/dev/lib/galaxy/tools/data/__init__.py#L120
from:
https://github.com/galaxyproject/galaxy/blob/dev/lib/tool_shed/tools/data_table_manager.py#L88
i.e.
Thanks - which is probably because of the previous failures with
`shed_update` - which relate back to the topic of my original email. I
suspect that failure from `planemo shed_update` has led to this "not
installable" state. And I don't know how to solve the problem from
`shed_update` which
Hi Peter,
if you open the page for data_manager_shapeit_reference in the test
ToolShed you will see that revision 5 and 6 are not installable, they
both have "*This revision can be installed:* False" . If you instead
select revision 3 it is installable.
Cheers,
Nicola
On 17/09/18 11:51,
I'm following up on my previous email. I somehow managed to get `planemo
shed_update` to work but now I seem to have an inconsistent view of the
Test toolshed. This is how it looks from the Admin panel of my Galaxy
server:
[image: https://files.gitter.im/galaxyproject/Lobby/k2qH/image.png]
Notice
