Is the galaxy main toolshed compatible with local installs of galaxy-dist?
I was wondering whether the general policy is to keep the toolshed at toolshed.g2.bx.psu.edu compatible with galaxy-dist or galaxy-central. The reason I ask is that I went to install a tool from a production server I'm trying to setup based on galaxy-dist ... but got an error; The resource could not be found. No action for /admin_toolshed/prepare_for_install Searching for this in the source code, I found that it exists in galaxy-central ... but not in galaxy-dist Am I right in guessing that this error is due to toolshed.g2.bx.psu.edu being powered by a recent toolshed version that is incompatible with galaxy-dist? If so, it would be great to get clarification as to whether this is to be expected in future. My personal feeling is that the main toolshed would be much more useful if kept compatible with galaxy-dist. Cheers Ira
Hi Ira, Both public Galaxy tool sheds track Galaxy central, and not Galaxy dist. This in unfortunate, but has been required over the past 2 years because the development activity at both the tool shed end and the Galaxy end has been extremely signifiant. Since development changes in the Galaxy environment must be compatible with development changes in the tool shed environment (and vice versa) in order for the 2 entities to function together, it has been impossible for the tool sheds to track the Galaxy dist repository, which generally is 8 - 10 weeks behind the Galaxy central repository. However, as the development of new features in the tool shed winds down (we're at the edge of that happening), the compatibility of the 2 entities becomes less of a problem. I believe a new Galaxy releases is planned for the near future, so dist will be compatible with the tool sheds (for a short time). However, issues may continue to crop up until the next dist release 2 months from now that could force the tools sheds to continue to track Galaxy central until that time. It's fairly likely that after the next dist release, maybe in September, that the tool sheds will able to begin tracking Galaxy dist. Ultimately that will happen, it's just a matter of when. I will, in fact, try to have the tool sheds track dist at this upcoming release, but I cannot guarantee that fixes won't be necessary within the 8 to 10 week time frame between dist updates. Greg Von Kuster On Jul 12, 2012, at 1:32 AM, Ira Cooke wrote:
I was wondering whether the general policy is to keep the toolshed at toolshed.g2.bx.psu.edu compatible with galaxy-dist or galaxy-central.
The reason I ask is that I went to install a tool from a production server I'm trying to setup based on galaxy-dist ... but got an error;
The resource could not be found. No action for /admin_toolshed/prepare_for_install
Searching for this in the source code, I found that it exists in galaxy-central ... but not in galaxy-dist
Am I right in guessing that this error is due to toolshed.g2.bx.psu.edu being powered by a recent toolshed version that is incompatible with galaxy-dist? If so, it would be great to get clarification as to whether this is to be expected in future. My personal feeling is that the main toolshed would be much more useful if kept compatible with galaxy-dist.
Cheers Ira
___________________________________________________________ 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:
Hi Greg, Thanks very much for the clarification. I'll just use a local toolshed for now since there are not many tools we need to install. When the official policy changes it would be great if that could be flagged in the announcement for a new release so we could start safely installing tools from the main toolshed to our production instance. Cheers Ira On 12/07/2012, at 8:54 PM, Greg Von Kuster wrote:
Hi Ira,
Both public Galaxy tool sheds track Galaxy central, and not Galaxy dist. This in unfortunate, but has been required over the past 2 years because the development activity at both the tool shed end and the Galaxy end has been extremely signifiant. Since development changes in the Galaxy environment must be compatible with development changes in the tool shed environment (and vice versa) in order for the 2 entities to function together, it has been impossible for the tool sheds to track the Galaxy dist repository, which generally is 8 - 10 weeks behind the Galaxy central repository.
However, as the development of new features in the tool shed winds down (we're at the edge of that happening), the compatibility of the 2 entities becomes less of a problem. I believe a new Galaxy releases is planned for the near future, so dist will be compatible with the tool sheds (for a short time). However, issues may continue to crop up until the next dist release 2 months from now that could force the tools sheds to continue to track Galaxy central until that time. It's fairly likely that after the next dist release, maybe in September, that the tool sheds will able to begin tracking Galaxy dist. Ultimately that will happen, it's just a matter of when.
I will, in fact, try to have the tool sheds track dist at this upcoming release, but I cannot guarantee that fixes won't be necessary within the 8 to 10 week time frame between dist updates.
Greg Von Kuster
On Jul 12, 2012, at 1:32 AM, Ira Cooke wrote:
I was wondering whether the general policy is to keep the toolshed at toolshed.g2.bx.psu.edu compatible with galaxy-dist or galaxy-central.
The reason I ask is that I went to install a tool from a production server I'm trying to setup based on galaxy-dist ... but got an error;
The resource could not be found. No action for /admin_toolshed/prepare_for_install
Searching for this in the source code, I found that it exists in galaxy-central ... but not in galaxy-dist
Am I right in guessing that this error is due to toolshed.g2.bx.psu.edu being powered by a recent toolshed version that is incompatible with galaxy-dist? If so, it would be great to get clarification as to whether this is to be expected in future. My personal feeling is that the main toolshed would be much more useful if kept compatible with galaxy-dist.
Cheers Ira
___________________________________________________________ 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:
Hello Ira and Galaxy-dev followers, Going forward from the current Galaxy release, mercurial change set revision ec29ce8e27a1 available in the Galaxy dist repository, the main Galaxy tool shed will track the Galaxy releases and the galaxy-dist repository on bitbucket. This announcement is included in the News Brief for the current Galaxy release - see http://wiki.g2.bx.psu.edu/DevNewsBriefs/2012_07_20. Greg Von Kuster On Jul 15, 2012, at 7:19 PM, Ira Cooke wrote:
Hi Greg,
Thanks very much for the clarification. I'll just use a local toolshed for now since there are not many tools we need to install. When the official policy changes it would be great if that could be flagged in the announcement for a new release so we could start safely installing tools from the main toolshed to our production instance.
Cheers Ira
___________________________________________________________ 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:
participants (2)
-
Greg Von Kuster -
Ira Cooke