Re: [galaxy-dev] corrupted binary file

2012-02-25 Thread Greg Von Kuster
It is highly recommended that you get the latest source from our Galaxy distribution repository using mercurial. As Peter stated, this will enable you to get regular updates as new Galaxy distribution releases occur. Your downloaded zip file contains what we consider a very old release. The G

Re: [galaxy-dev] corrupted binary file

2012-02-25 Thread Peter Cock
On Sat, Feb 25, 2012 at 9:40 AM, Yingwei HU wrote: > Dear Peter, > > I am sorry I do not know the version of my galaxy by using hg. I directly > downloaded the zip file from the address: > http://dist.g2.bx.psu.edu/galaxy-dist.tip.zip That would be fine for a one-off test installation, but it wil

Re: [galaxy-dev] corrupted binary file

2012-02-25 Thread Yingwei HU
Dear Peter, I am sorry I do not know the version of my galaxy by using hg. I directly downloaded the zip file from the address: http://dist.g2.bx.psu.edu/galaxy-dist.tip.zip The zipped files are compressed on 2011-06-29. Is this version too old? Thank you for your help. Best Regards, HU Yingwei

Re: [galaxy-dev] corrupted binary file

2012-02-25 Thread Peter Cock
On Saturday, February 25, 2012, Yingwei HU wrote: > Dear Peter, > > Thank you for your response. > Yes. it is a custom binary file type. I attached the sample binary files. > humanK562C_d2.splib is the original one. > temp.splib is the uploaded and corrupted one. > For definition in Galaxy, I just

Re: [galaxy-dev] corrupted binary file

2012-02-24 Thread Peter Cock
On Fri, Feb 24, 2012 at 4:03 PM, Yingwei HU wrote: > Dear all, > > I found one of my binary files was corrupted after its uploading through > "Get data'. I used editplus to check its hex code and found some "0D" is > changed to "0A" and also one byte is lost. May I ask how to solve this > problem?

[galaxy-dev] corrupted binary file

2012-02-24 Thread Yingwei HU
Dear all, I found one of my binary files was corrupted after its uploading through "Get data'. I used editplus to check its hex code and found some "0D" is changed to "0A" and also one byte is lost. May I ask how to solve this problem? Thank you for your help. Best Regards, HU Yingwei __