This should now be working in change set 6668:84baec18959c, which is available in our central repository.  Please let me know if you bump into any problems.

To use the latest features related to tool versioning, update your local tool shed as well as your local Galaxy instance ( both require updating the database schema ).  In your local tool shed, reset all metadata for each repository using the Repository Actions pop-up for each repository.  Since you already have repositories in your tool shed, you'll need to do this once for each existing repository.  Any updates to the repository will automatically do this.  New repositories created from here on will handle this automatically as well.



Then, in your local Galaxy instance, set tool versions for each installed tool shed repository using the repository's pop-up.





On Feb 3, 2012, at 11:05 AM, Greg Von Kuster wrote:

Hi Alex,

The ToolSectionLabel element is causing the problem as it is not currently supported in the new tool shed repository installation implementation.  I'll try to get a fix for this today.  In the meantime, eliminating the section label from your tool config should work as a temporary workaround.  I'll send you a note when I have the fix - sorry for the inconvenience.

FYI - I have a fairly complex change set coming today that will introduce tool versioning for Galaxy tools, whether they are installed from a tool shed, or are available with the distribution.  This will affect the tool shed as well as repositories installed from tool sheds that contain tools.  This versioning feature will provide a chain of ancestor tool versions and descendant tool versions for any tool instance.  

It would be great if you and others that have set up local Galaxy tool sheds can test this out.  I will get fixes for issues (if any exist) as fast as possible.  My hope is that this will be the last major feature introduced until we get everything stabilized a bit more between the tool shed and Galaxy.

Thanks!

Greg Von Kuster

On Feb 3, 2012, at 10:20 AM, Bossers, Alex wrote:

Somehow I seem to miss something when configuring our latest up-to-date galaxy_central version to use the galaxy toolshed.
When as admin I want to install a tool I can browse the given 2 repositories and select view tools.
When I select install to local galaxy it drops an error on 2 tools I tested thus far:
 
---------------------------
Error Traceback:
View as:   Interactive  |  Text  |  XML (full)
⇝ AttributeError: 'ToolSectionLabel' object has no attribute 'name'
Module weberror.evalexception.middleware:364 in respond         view
>>  app_iter = self.application(environ, detect_start_response)
Module paste.debug.prints:98 in __call__         view
>>  environ, self.app)
Module paste.wsgilib:539 in intercept_output         view
>>  app_iter = application(environ, replacement_start_response)
Module paste.recursive:80 in __call__         view
>>  return self.application(environ, start_response)
Module paste.httpexceptions:632 in __call__         view
>>  return self.application(environ, start_response)
Module galaxy.web.framework.base:160 in __call__         view
>>  body = method( trans, **kwargs )
Module galaxy.web.framework:173 in decorator         view
>>  return func( self, trans, *args, **kwargs )
Module galaxy.web.controllers.admin_toolshed:322 in install_repository         view
>>  tool_panel_section_select_field = build_tool_panel_section_select_field( trans )
Module galaxy.web.controllers.admin_toolshed:804 in build_tool_panel_section_select_field         view
>>  options.append( ( tool_section.name, tool_section.id ) )
AttributeError: 'ToolSectionLabel' object has no attribute 'name'
---------------------------
 
 
The steps I took:
Updated the universe to load the extra shed_tool_conf.xml file.
Set the toolpath to "../toolshedtools" in shed_tool_conf.xml
Gave the directory read write permissions for galaxy user:dev_group
Restarted galaxy.
 
Any additional configs to make somewhere? In the original tool_conf.xml file?
 
Alex
 
 
___________________________________________________________
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:

 http://lists.bx.psu.edu/

Greg Von Kuster
Galaxy Development Team



___________________________________________________________
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:

 http://lists.bx.psu.edu/

Greg Von Kuster
Galaxy Development Team
greg@bx.psu.edu