Hello all,
There looks to be an egg problem with the latest galaxy-central,
here are excepts from a failed Galaxy install on my TravisCI test
setup,
https://travis-ci.org/peterjc/pico_galaxy/builds/41233860
Here's another project build with the same error:
https://travis-ci.org/peterjc/galaxy_bla
The release is definitely official - many sites have upgraded and
usegalaxy.org has been running it since September - I'm not sure if
there will release notes or not for the October release. We have not
abandoned release notes - the next release will have release notes.
I think there may be one da
Dear all,
I've uploaded to the test tool shed a pscan_chip_test repository and I'm
looking for help in testing it since it's my first time setting up a
Galaxy repository.
Pscan-ChIP is a motif enrichment analysis tool. The stand-alone web
interface is available here:
www.beaconlab.it/pscan
I have had the same issue. A little debugging here:
https://travis-ci.org/saketkc/galaxy_tools/builds/41209515#L84
I first thought that there was a conflict with system installed
paramiko, but it is not:
https://travis-ci.org/saketkc/galaxy_tools/builds/41210153#L60
A clean install of galaxy-cent
Ummm... I think it is that the VM started shipping with an
incompatible paramkio. Saket I think you were using -m like it were
-c?
> python -m "import string" # what you had
/usr/bin/python: No module named import string
> python -c "import string
> python -m "string"
>
Anyway - planemo's TravisC
On 17 November 2014 11:23, John Chilton wrote:
> Ummm... I think it is that the VM started shipping with an
> incompatible paramkio. Saket I think you were using -m like it were
> -c?
>
>> python -m "import string" # what you had
> /usr/bin/python: No module named import string
>> python -c "impor
