Hello Kevyin,
As you stated, the build directory was not being tracked in your
fastq_groomer_parallel repository in the tool shed - running hg status on your
repository produced this:
%hg status
? build/README
? build/fastq_groomer_parallel.py
? build/fastq_groomer_parallel.xml
? build/ipython/
Hi Greg,
Thanks for the toolshed links I'll make sure to go over them.
I think when the upload failed, mercurial didn't get to the point of
tracking the build folder.
>From a mercurial point of view there seems to be no issue, pulling/cloning
or even installing is fine because it's not tracked.
B
Hello Kevin,
On Sep 14, 2012, at 3:48 AM, kevyin wrote:
> Hi,
> I have a tool on the main galaxy toolshed called fastq_groomer_parallel.
> During an update, with a new tar.gz upload I accidentally included in an
> unrelated big folder of stuff under the folder build/
>
> The upload failed (wit
Hi,
I have a tool on the main galaxy toolshed called fastq_groomer_parallel.
During an update, with a new tar.gz upload I accidentally included in an
unrelated big folder of stuff under the folder build/
The upload failed (with no helpful error message, only to turn on debug
mode)
I went and brows
