@jerowe the perl-app-cpanminus easyconfig still works fine, so why is this required?

Is there a similar fix for the gencore_variant_detection easyconfig, which is broken (cfr. easybuilders/easybuild-easyblocks#1082 (comment)).

@jerowe how did you fix gencore_variant_detection, I don't see any changes to the easyconfig?

@jerowe please change the target branch to develop?

Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in this PR)
node2623.swalot.os - Linux centos linux 7.2.1511, Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz, Python 2.7.5
See https://gist.github.com/a79b1ccc3d219e24a5551fa4202cd3f6 for a full test report.

lgtm

Going in, thanks @jerowe!

@jerowe installing gencore_variant_detection is still troublesome, error is now different though:

PaddingError: Placeholder of length '80' too short in package r::r-base-3.3.1-5.                                                                                                                               The package must be rebuilt with conda-build > 2.0.

@boegel , looking into this now.

@boegel , I pinned a few more versions. That might help. It builds on our docker image at least.

I think I've asked this before, but how could I go about testing things locally? A docker image that simulates travis would be really handy to have. I could do some testing locally to hopefully leave you with less testing. ;-)

@jerowe still the same problem I'm afraid... I'm just using the existing easyconfig for gencore_variant_detection 1.0

@boegel , what is the prefix you are installing to? I know at some point I was having trouble with some modules, because the --prefix command supplied to conda was too long. I think this might have been the same error you are seeing.

@jerowe Hah, seems like you're spot on. My default install prefix is rather long, and with a really short install prefix (/tmp/$USER), it installs just fine...

So, we should have a check in conda.py on the length of the install prefix or something like that?

That would be best, but I think the exact allowed prefix name depends upon the version of conda-build that was used to build the package. Packages are often build and rebuild, and there is no way of telling the version of conda-build used to build a package without going and hunting through the actual builds on travis.

Maybe we could catch any 'prefix blahblah' errors, and give a helpful warning that the prefix is probably too long?

Yes, the latter would certainly be useful, since it wasn't clear quickly what the problem was even for us...