@nsoranzo I have wondered about dropping testing against master in place of testing on a couple of release branches (which would require periodic updating when a new release happens). I had been assuming master would be a reasonable substitute for the latest release branch, but that does not seem to be quite the case?
@peterjc Most of the times
master is updated when a new release is tagged, but not kept in sync with the corresponding release_XX.XX branch until someone asks for it. We could do a better job here (e.g. automate syncing), but for the time being my suggestion above should give you a smoother experience.
can you provide more data?
@/all any idea how we can review this: galaxyproject/tools-iuc#1905 galaxyproject/tools-iuc#1897
I have ask the EDAM people and ELIXIR people and hope they will help as well.
how does it fare with edam-hand-annotated tools?
Would it be enough if everyone of us takes 5 tools and checks if they are coorect.
Random tools?
What is the risk if it is wrongly annotated? It has no impact on Galaxy's functionality now, does it?
Problem report when installing samtools from MTS with certain versions of ubunto as the OS. Known? Could someone help troubleshoot? https://biostar.usegalaxy.org/p/28213/
@nsoranzo The user replied at https://biostar.usegalaxy.org/p/28213/. They are trying to install an older version that is required by other tools as a dependency. Would you be able to help with a reply?
I'm running the test command on a tool I've been working on but it fails each time saying "History item different than expected, difference (using diff):". My output when I execute the command myself appears to have an extra space at the beginning of each line so I'm fairly certain that's what's causing my issue. Is there a way I can tell the test to ignore the spaces?
for example searching with a regex in your expected output
Hi, we have a homemade tool that we try to update (to integrate in toolshed by the end hopefully!) written in PERL. One script.pl A, calling one script.pl B requiring one module.pm asking for dependency as use Statistics::R. In the tool.xml, I added dependency : <requirement type="package" version="0.34" >perl-statistics-r</requirement>. Dependency is well installed as I can see in the admin interface. However, I have the error "Can't locate Statistics/R.pm in @INC ... " unless I add at the begining of script.pl B the 2 libraries from _conda folder : use lib "/storage/galaxydev/aubi/deps/_conda/envs/mulled-v1-a13c90f5fb8d14af93747bd7e50940f3368a06c26204eb3e68d6595d645d5073/lib/perl5/site_perl/5.22.0";
use lib "/storage/galaxydev/aubi/deps/_conda/envs/mulled-v1-a13c90f5fb8d14af93747bd7e50940f3368a06c26204eb3e68d6595d645d5073/lib/perl5/site_perl/5.22.0/x86_64-linux-thread-multi";
use lib "/storage/galaxydev/aubi/deps/_conda/envs/mulled-v1-a13c90f5fb8d14af93747bd7e50940f3368a06c26204eb3e68d6595d645d5073/lib/perl5/site_perl/5.22.0/x86_64-linux-thread-multi";
any clue on how can I solve this problem ?
@davebx fire away! I'm working on fixing this diffbind control file issue atm https://github.com/galaxyproject/usegalaxy-playbook/issues/127#issuecomment-395073384
Any plans to wraps Trinity's "SuperTranscript" utility for Galaxy? Or did I miss it in the MTS? Question asked here about it: https://biostar.usegalaxy.org/p/28312
there's a broken link in the toolshed for iuc's package_graphicsmagick_1_3_20 (latest version):
http://sourceforge.net/projects/graphicsmagick/files/graphicsmagick/1.3.20/GraphicsMagick-1.3.20.tar.gz
which has since been fixed in the tools-iuc repo of galaxy:
https://github.com/galaxyproject/tools-iuc/blob/1fe103338548dd65731a5a0887be59745370debd/packages/package_graphicsmagick_1_3_20/tool_dependencies.xml#L6
what's the cause of the disparity, and is there a way to update the toolshed.g2.bx.psu.edu version? thanks!
What is the decision for GATK 4? Will it be wrapped? I didn't find anything in tools-iuc but may have missed it. Question about if & status asked at Biostars today: https://biostar.usegalaxy.org/p/28327/
Linked the reply back here since I wasn't sure and though you all might know more, but please comment back at the message board if you prefer. Thanks!
in case anyone is around: I'm looking to doing some work on the picard tools since they do not use $TEMP but rather a
/tmp based path, yielding out-of-disk errors on my system. They are originally from devteam and do not follow IUC recommendations. I'm wondering how much to change though...