julia-0.5.2 #3503

dfornika · 2017-08-10T22:09:18Z

Fixes #1618

conda-forge-linter · 2017-08-10T22:09:26Z

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/julia) and found some lint.

Here's what I've got...

For recipes/julia:

The top level meta keys are in an unexpected order. Expecting ['package', 'source', 'build', 'requirements', 'test', 'about'].
The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
Selectors are suggested to take a <two spaces>#<one space>[<expression>] form.

conda-forge-linter · 2017-08-10T22:15:51Z

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/julia) and found some lint.

Here's what I've got...

For recipes/julia:

The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
Selectors are suggested to take a <two spaces>#<one space>[<expression>] form.
There are 2 too many lines. There should be one empty line at the end of the file.

conda-forge-linter · 2017-08-10T22:29:17Z

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/julia) and found some lint.

Here's what I've got...

For recipes/julia:

The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
Selectors are suggested to take a <two spaces>#<one space>[<expression>] form.

conda-forge-linter · 2017-08-10T22:30:42Z

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/julia) and found some lint.

Here's what I've got...

For recipes/julia:

The recipe could do with some maintainers listed in the extra/recipe-maintainers section.

conda-forge-linter · 2017-08-10T22:32:20Z

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/julia) and found it was in an excellent condition.

bgruening

@dfornika thanks a bunch. Small review inline.

bgruening · 2017-08-11T06:44:55Z

recipes/julia/meta.yaml

+    - libgcc  # [linux]
+    - libgit2 0.24.*
+    - gmp 0.5.*
+    - openblas


can you pin openblas to openblas 0.2.19|0.2.19.*

I think I've got gmp wrong too. Will use gmp 6.1.*

bgruening · 2017-08-11T06:45:29Z

recipes/julia/meta.yaml

+    - libgit2 0.24.*
+
+  run:
+    - zlib


can you pin zlib to zlib 1.2.8 both run and build environments.

bgruening · 2017-08-11T06:46:04Z

recipes/julia/meta.yaml

+    - mpfr
+    - curl
+    - libssh2 1.7.*
+    - libxml2


please pin this to libxml2 2.9.*
A complete list can be found here: https://github.com/conda-forge/conda-forge.github.io/blob/0661e2ecf4b213ddf36350ca100a5a820eb17eb7/scripts/pin_the_slow_way.py#L40-L85

bgruening · 2017-08-11T06:46:38Z

recipes/julia/meta.yaml

+    - llvmdev 3.9.*
+    - fftw
+    - gmp 0.5.*
+    - mpfr


mpfr 3.1.*

bgruening · 2017-08-11T06:47:07Z

recipes/julia/meta.yaml

+  - rpath.patch
+
+build:
+  skip: True  # [osx]


This needs to be combined in one like [py3k or osx]

Skip windows builds too? (ie:)

build: skip: True # [py3k or osx or win]

The AppVeyor CI build fails with message:

Packages missing in current win-32 channels: - autoconf 2.69 pl5.* - automake 1.15 pl5.* - openblas - gmp 0.5.*

...and

Packages missing in current win-64 channels: - autoconf 2.69 pl5.* - automake 1.15 pl5.* - openblas - gmp 0.5.*

(I realized the gmp version is wrong anyways, but not sure about the others)

bgruening · 2017-08-11T06:48:59Z

recipes/julia/build.sh

+export LIBRARY_PATH=${PREFIX}/lib
+export CMAKE_PREFIX_PATH=${PREFIX}
+
+make -j 2 prefix=${PREFIX} MARCH=core2 sysconfigdir=${PREFIX}/etc NO_GIT=1 \


Is there something like make test which we can run?

There is a test target in the Makefile. Can you suggest how to include that in the build script? Would we just run the make test command first then make install after, with the same env variables and flags? (ie:)

make -j 2 prefix=${PREFIX} MARCH=core2 sysconfigdir=${PREFIX}/etc NO_GIT=1 \ USE_SYSTEM_LIBGIT2=1 USE_LLVM_SHLIB=0 USE_SYSTEM_CURL=1 USE_SYSTEM_MPFR=1 \ USE_SYSTEM_PATCHELF=1 USE_SYSTEM_LIBSSH2=1 USE_SYSTEM_LLVM=1 USE_SYSTEM_BLAS=1 \ USE_SYSTEM_FFTW=1 USE_SYSTEM_GMP=1 USE_SYSTEM_LAPACK=1 LIBBLAS=-lopenblas \ LIBBLASNAME=libopenblas.so LIBLAPACK=-lopenblas LIBLAPACKNAME=libopenblas.so \ test make -j 2 prefix=${PREFIX} MARCH=core2 sysconfigdir=${PREFIX}/etc NO_GIT=1 \ USE_SYSTEM_LIBGIT2=1 USE_LLVM_SHLIB=0 USE_SYSTEM_CURL=1 USE_SYSTEM_MPFR=1 \ USE_SYSTEM_PATCHELF=1 USE_SYSTEM_LIBSSH2=1 USE_SYSTEM_LLVM=1 USE_SYSTEM_BLAS=1 \ USE_SYSTEM_FFTW=1 USE_SYSTEM_GMP=1 USE_SYSTEM_LAPACK=1 LIBBLAS=-lopenblas \ LIBBLASNAME=libopenblas.so LIBLAPACK=-lopenblas LIBLAPACKNAME=libopenblas.so \ install

bgruening · 2017-08-11T06:50:00Z

recipes/julia/meta.yaml

+
+test:
+  commands:
+    - "julia -v"


the quotes can be removed

bgruening · 2017-08-11T06:50:09Z

recipes/julia/meta.yaml

+
+extra:
+  recipe-maintainers:
+    - dfornika


Feel free to add me.

Thanks, I'm going to add @acaprez too.

dfornika · 2017-08-11T20:04:14Z

CircleCI build failed with error below. Same error as seen here:

JuliaLang/julia#22407

The Julia github page says that libgit2 >= 0.23 should be compatible, and we're pulling libgit2 = 0.24.5 from conda-forge, so I'm not sure what the problem is.

Exception running test libgit2 :
On worker 3:
LoadError: There was an error during testing
 in record at ./test.jl:397
 in do_test at ./test.jl:281
 in include_string at ./loading.jl:441
 in include_from_node1 at ./loading.jl:491
 in macro expansion at ./util.jl:230 [inlined]
 in runtests at /staged-recipes/build_artefacts/julia_1502474743960/work/julia-0.5.2/test/testdefs.jl:7
 in #16 at /staged-recipes/build_artefacts/julia_1502474743960/work/julia-0.5.2/test/runtests.jl:44
 in #645 at ./multi.jl:1421
 in run_work_thunk
 at ./multi.jl:1001
 in macro expansion at ./multi.jl:1421 [inlined]
 in #644 at ./event.jl:68
while loading /staged-recipes/build_artefacts/julia_1502474743960/work/julia-0.5.2/test/libgit2.jl, in expression starting on line 21ERROR: LoadError: Some tests exited with errors.
 in (::##11#19)() at /staged-recipes/build_artefacts/julia_1502474743960/work/julia-0.5.2/test/runtests.jl:72
 in cd(::##11#19, ::String) at ./file.jl:59
 in include_from_node1(::String) at ./loading.jl:488
 in process_options(::Base.JLOptions) at ./client.jl:265
 in _start() at ./client.jl:321
while loading /staged-recipes/build_artefacts/julia_1502474743960/work/julia-0.5.2/test/runtests.jl, in expression starting on line 26
make[1]: *** [all] Error 1
make: *** [test] Error 2
Traceback (most recent call last):
  File "/opt/conda/bin/conda-build-all", line 6, in <module>
    sys.exit(conda_build_all.cli.main())
  File "/opt/conda/lib/python3.6/site-packages/conda_build_all/cli.py", line 93, in main
    b.main()
  File "/opt/conda/lib/python3.6/site-packages/conda_build_all/builder.py", line 280, in main
    built_dist_location = self.build(meta, build_config)
  File "/opt/conda/lib/python3.6/site-packages/conda_build_all/builder.py", line 209, in build
    conda_build.api.build(meta.meta, config=config)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/api.py", line 97, in build
    need_source_download=need_source_download, config=config)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/build.py", line 1524, in build_tree
    config=config)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/build.py", line 1147, in build
    utils.check_call_env(cmd, env=env, cwd=src_dir)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/utils.py", line 628, in check_call_env
    return _func_defaulting_env_to_os_environ(subprocess.check_call, *popenargs, **kwargs)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/utils.py", line 624, in _func_defaulting_env_to_os_environ
    return func(_args, **kwargs)
  File "/opt/conda/lib/python3.6/subprocess.py", line 291, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/bin/bash', '-x', '-e', '/staged-recipes/build_artefacts/julia_1502474743960/work/julia-0.5.2/conda_build.sh']' returned non-zero exit status 2.
Exited with code 1

acaprez · 2017-08-11T21:13:37Z

It looks like the issue is that the libgit2 package in conda-forge was built without SSH support. The Julia test script (test/libgit2.jl) is running the following check:

#@testset "Check library features" begin
    f = LibGit2.features()
    @test findfirst(f, LibGit2.Consts.FEATURE_SSH) > 0
    @test findfirst(f, LibGit2.Consts.FEATURE_HTTPS) > 0
#end

Running LibGit2.features() manually using v0.24.5 shows:

julia> f = LibGit2.features()
2-element Array{Base.LibGit2.Consts.GIT_FEATURE,1}:
 FEATURE_THREADS
 FEATURE_HTTPS

So the first test for FEATURE_SSH fails and causes the error.

dfornika · 2017-08-11T21:20:57Z

@acaprez Thanks for the insight, I would have had trouble tracking that down.

Would you recommend setting USE_SYSTEM_LIBGIT2=0, and removing the conda libgit2 dependency from the meta.yaml file?

Or would it be better to use the conda libgit2, and (somehow) skip that specific test?

acaprez · 2017-08-11T21:47:52Z

I don't actually contribute to conda-forge, so I'm unsure of what their guidelines are. For bioconda at least, I think the goal is to explicitly list and use conda packages for all the dependencies.

You might try removing the version pinning for libgit2 and see if it will build ok. The 0.25.1 version of libgit2 was built with SSH support.

tkelman · 2017-08-11T23:39:54Z

recipes/julia/meta.yaml

+    - autoconf 2.69 pl5.*
+    - automake 1.15 pl5.*
+    - openblas 0.2.19|0.2.19.*
+    - llvmdev 3.9.*


llvm 3.9 with julia 0.5.x is not a recommended configuration that would be supported in upstream bug reports

What version would be recommended?

llvm 3.7.1 (heavily patched) with julia 0.5.x, or llvm 3.9.1 (also heavily patched) with julia 0.6.0

Is there any news on when these patches might move upstream?

We can include patches for llvm. There is a mechanism for it, but I haven't kept up with the latest details. Maybe @SylvainCorlay can comment.

We upstream everything we can. See all the "Remove for" comments here https://github.com/JuliaLang/julia/blob/4c5cc04156ba074a8baa028c2a8a41b9e70d56ee/deps/llvm.mk#L432-L482 that mean things were successfully upstreamed. The problem is LLVM breaks other things before their next release and we haven't tested or ifdef-ed code sufficiently to work with anything else. We also haven't tested backporting our patches against other LLVM-using projects, they may cause issues in use cases that Julia doesn't care about. Realistically LLVM does not work well as a shared dependency.

Can I get some advice on how to solve this? Should I remove llvm and llvmdev from meta.yaml? My understanding is that the julia build system would pull down its own copy if we don't list it as a dependency and set USE_SYSTEM_LLVM=0 in the build.sh script.

tkelman · 2017-08-11T23:41:05Z

recipes/julia/meta.yaml

+
+test:
+  commands:
+    - julia -v


please run all of the tests. julia -e 'Base.runtests("all"); Base.runtests("pkg libgit2-online")'
(the ones that need network access aren't included under "all" by default, and if you build julia 0.6.x then "download" should be added to that list)

Certainly a good idea to run more tests, but could you please provide us an idea of the runtime for the full test suite? Asking partially as we have to be practical if this goes over the CI time limits.

Depends on the CI service. 20 minutes to an hour probably. You don't necessarily need to run them all on every minor commit, but do at least run them locally.

I'd also recommend setting TAGGED_RELEASE_BANNER to indicate that this build of Julia comes from conda-forge, as if it fails any tests the first response from upstream will likely be that it was built in a non-recommended configuration. Passing all the tests is the best way to be confident of the build configuration, especially when it differs a lot from a normal upstream source build.

Oh I missed that the tests are actually running in build.sh, that's encouraging.

Should the test be run from both the build.sh script and from the meta.yaml file, or just one of those?

Running in either place is fine. Though picking one is good. There is a slight preference to running the tests in the test section. However if that isn't practical, running them in build.sh is fine.

tkelman · 2017-08-11T23:42:44Z

recipes/julia/rpath.patch

+ 	# Overwrite JL_SYSTEM_IMAGE_PATH in julia library
+-	$(call stringreplace,$(DESTDIR)$(libdir)/libjulia.$(SHLIB_EXT),sys.$(SHLIB_EXT)$$,$(private_libdir_rel)/sys.$(SHLIB_EXT))
+-	$(call stringreplace,$(DESTDIR)$(libdir)/libjulia-debug.$(SHLIB_EXT),sys-debug.$(SHLIB_EXT)$$,$(private_libdir_rel)/sys-debug.$(SHLIB_EXT))
+	#$(call stringreplace,$(DESTDIR)$(libdir)/libjulia.$(SHLIB_EXT),sys.$(SHLIB_EXT)$$,$(private_libdir_rel)/sys.$(SHLIB_EXT))


why are you commenting this out? I would expect this to break things

I don't know much about the purpose of that patch. It was written by @acaprez for the bioconda package:

bioconda/bioconda-recipes@dae9e67

This may make it impossible for Julia to run except via the wrapper script.

I don't think that's true, because the julia-0.5.2 package on bioconda uses that patch but doesn't use a wrapper script.

https://anaconda.org/bioconda/julia

Then is this condition even true in your build? If not, you don't need to be patching it at all.

I don't know, but I removed the patch and re-built on my system and it seemed to work fine. It passed the test suite. I created a new conda env based on that build and ran julia, installed a simple package ("ArgParse") and imported it. Everything seemed to work.

jakirkham · 2017-08-12T02:30:08Z

Thanks @dfornika for putting this together. Also thanks for helping review this, @tkelman.

tkelman · 2017-08-17T16:53:26Z

recipes/julia/meta.yaml

+    - zlib 1.2.8
+    - python 2.7.*
+    - autoconf 2.69 pl5.*
+    - automake 1.15 pl5.*


what were you needing autotools for? likewise with libxml2, don't usually expect that to be a build-dep

I didn't write the original meta.yaml file, so all I can say is that they were there in the bioconda recipe.

tkelman · 2017-08-17T16:56:01Z

recipes/julia/meta.yaml

+    - gmp 6.1.*
+    - mpfr 3.1.*
+    - curl
+    - libssh2 1.7.*


if libgit2 depends on this at run time, then I suspect Julia's Pkg would too for handling ssh remotes (though it'll only do so through libgit2 and depend how libgit2 was built, we don't link or call libssh2 directly)

So are you suggesting to add libssh2 as a runtime requirement?

It looks like the pkg tests pass.

* pkg INFO: Initializing package repository /tmp/Zpu2ogMF/v0.5 INFO: Cloning METADATA from https://github.com/JuliaLang/METADATA.jl INFO: No packages to install, update or remove INFO: Cloning cache of Example from notarealprotocol://github.com/JuliaLang/Example.jl.git INFO: Cloning cache of Example from https://github.com/JuliaLang/Example.jl.git INFO: Installing Example v0.4.1 INFO: Package database updated INFO: Checking out Example master... INFO: Pulling Example latest master... INFO: No packages to install, update or remove INFO: Freeing Example INFO: No packages to install, update or remove INFO: Checking out Example master... INFO: Pulling Example latest master... INFO: No packages to install, update or remove INFO: Freeing Example INFO: No packages to install, update or remove INFO: Removing Example v0.4.1 INFO: Package database updated INFO: Nothing to be done INFO: Cloning Example from https://github.com/JuliaLang/Example.jl.git INFO: Computing changes... INFO: No packages to install, update or remove INFO: Package database updated INFO: Freeing Example INFO: No packages to install, update or remove INFO: Checking out Example master... INFO: Pulling Example latest master... INFO: No packages to install, update or remove INFO: Freeing Example INFO: No packages to install, update or remove INFO: Cloning Example2 from /tmp/Zpu2ogMF/v0.5/Example INFO: Computing changes... INFO: No packages to install, update or remove INFO: Cloning Example3 from /tmp/Zpu2ogMF/v0.5/Example INFO: Computing changes... INFO: No packages to install, update or remove INFO: Checking out Example2 test-branch-1... INFO: Pulling Example2 latest test-branch-1... INFO: No packages to install, update or remove INFO: Checking out Example3 test-branch-1... INFO: Pulling Example3 latest test-branch-1... INFO: No packages to install, update or remove INFO: Checking out Example master... INFO: Pulling Example latest master... INFO: No packages to install, update or remove INFO: Cloning Example4 from /tmp/Zpu2ogMF/v0.5/Example INFO: Computing changes... INFO: No packages to install, update or remove INFO: Checking out Example4 test-branch-2... INFO: Pulling Example4 latest test-branch-2... INFO: No packages to install, update or remove INFO: Updating METADATA... INFO: Updating Example2 test-branch-1... INFO: Updating Example4 test-branch-2... INFO: Updating Example3 test-branch-1... INFO: Computing changes... INFO: No packages to install, update or remove INFO: Removing Example v0.4.1 INFO: Package database updated INFO: Freeing Example INFO: Upgrading ColorTypes: v0.2.12 => v0.5.2 INFO: Upgrading Colors: v0.6.4 => v0.7.4 INFO: Upgrading FixedPointNumbers: v0.2.1 => v0.3.9 INFO: Removing Example v0.4.1 INFO: Package database updated WARNING: FixedPointNumbers is fixed at 0.0.6+ conflicting with requirement for ColorTypes: [0.3.0,∞) WARNING: FixedPointNumbers is fixed at 0.0.6+ conflicting with requirement for Colors: [0.3.0,∞) WARNING: ColorTypes is fixed at 0.0.0- conflicting with requirement for Colors: [0.3.0,∞) WARNING: Compat is fixed at 0.2.12+ conflicting with requirement for FixedPointNumbers: [0.17.0,∞) WARNING: Compat is fixed at 0.2.12+ conflicting with requirement for ColorTypes: [0.26.0,∞) WARNING: Compat is fixed at 0.2.12+ conflicting with requirement for Colors: [0.18.0,∞) INFO: Installing Example v0.4.0 INFO: Package database updated INFO: METADATA is out-of-date — you may not have the latest version of Example INFO: Use `Pkg.update()` to get the latest versions of your packages in 240.46 seconds, maxrss 434.51 MB * libgit2-online in 0.47 seconds, maxrss 434.51 MB SUCCESS

I'd probably leave it as an indirect dependency, if libgit2 is built against it then libgit2 will have a runtime dependency on it right? Pkg will work but with degraded functionality if libgit2 happens to get built without libssh2 support. I think there are tests that would fail if that happened.

You can remove libssh2 as it is only needed as a indirect dependency of libgit2

dfornika · 2017-08-17T20:14:48Z

Green checkmark!

dfornika · 2017-08-17T20:17:42Z

How can I skip both the appveyor and travis builds?

isuruf · 2017-08-17T20:20:53Z

recipes/julia/meta.yaml

+    - gmp 6.1.*
+    - mpfr 3.1.*
+    - openblas 0.2.19|0.2.19.*
+    - blas 1.1 {{ variant }}


You probably need curl here

libcurl is also indirect at runtime (for proxies in libgit2 if it's built with that support), though curl or wget is used for downloads at build and test time

can keep it for the Base.download function though (edit: on non-windows platforms, since we use something else on windows)

isuruf · 2017-08-17T20:21:52Z

recipes/julia/meta.yaml

+    - libgit2
+
+  run:
+    - zlib 1.2.8


@tkelman, is zlib used? Or is it used by a dependency?

indirect I believe

isuruf · 2017-08-17T20:25:41Z

How can I skip both the appveyor and travis builds?

You can't. Only appveyor has a CI specific message. Others can use [ci skip] but this skips all CI.

jakirkham · 2017-08-17T20:27:35Z

Also issue ( travis-ci/travis-ci#5032 ) is relevant.

tkelman · 2017-08-17T22:01:10Z

Guess conda doesn't have a pcre2 package yet? If that were available and had shared libraries then it would make sense to use conda's there too (build time and run time).

isuruf · 2017-08-18T01:16:26Z

No, there's not. Only pcre2, openspecfun, openlibm, dSFMT are missing. We can add those later as separate feedstocks and update the julia feedstock. I'll merge this after tests pass if there's no objections.

isuruf · 2017-08-18T02:37:45Z

recipes/julia/meta.yaml

@@ -52,7 +52,8 @@ requirements:

 test:
  commands:
-    - julia -e 'Base.runtests("all"); Base.runtests("pkg libgit2-online")'
+    - julia -e 'Base.runtests("all"); Base.runtests("pkg libgit2-online")':
+        timeout: 1800s


How does this work?

I'm trying to do this:

https://stackoverflow.com/questions/36173553/how-to-extend-timeout-for-tests-in-circleci
https://circleci.com/docs/1.0/configuration/#modifiers

That's CircleCI.yml functionality. This file is for conda-build

tkelman · 2017-08-18T06:08:45Z

Suppose replacing the wrapper script with a juliarc modification can be done in the feedstock

isuruf · 2017-08-18T13:29:31Z

Thanks. Can you open 2 issues for the missing dependencies and the wrapper script in the julia-feedstocks repo once it is created?

jakirkham · 2017-08-18T14:23:09Z

Thanks so much for you persistence @dfornika. Also thanks to all of the reviewers. Thanks for picking this up on the last leg, @isuruf.

jakirkham · 2017-09-12T12:35:10Z

Looks like you have been maintaining a similar build of julia, @tkf, which likely shares some history with this one. Figured you would be interested to know that we have added julia to conda-forge. This will allow users to easily install this with conda ( conda install -c conda-forge julia ). The maintenance burden here is light as all releases are built and deployed automatically with CIs. Changes to how it is being built can be controlled by changing the recipe in this feedstock (repo). If you have any interest in helping maintain the recipe, we would certainly appreciate your expertise and would be more than happy to add you to the maintainers list (providing you the needed permissions).

Julia-0.5.2

9d1ec7c

dfornika added 2 commits August 10, 2017 15:10

Update meta.yaml

ee165c0

Update meta.yaml

6e4a9ef

dfornika added 2 commits August 10, 2017 15:16

Update meta.yaml

a765a18

Update meta.yaml

329ecf4

Update meta.yaml

0399205

Update meta.yaml

b59d56c

bgruening reviewed Aug 11, 2017

View reviewed changes

recipes/julia/meta.yaml Outdated

test:

commands:

- "julia -v"

Copy link

Contributor

bgruening Aug 11, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the quotes can be removed

bgruening reviewed Aug 11, 2017

View reviewed changes

Addressed review by @bgruening

fb78a2f

Removed libgit2 dependency

09ea8b4

dfornika added 2 commits August 11, 2017 15:11

Added libgit2 dependency, un-pinned version

79a24de

Set JULIA_HISTORY inside conda env

cd8c0f3

dfornika mentioned this pull request Aug 11, 2017

Add Julia #1618

Closed

tkelman reviewed Aug 11, 2017

View reviewed changes

dfornika and others added 2 commits August 12, 2017 10:35

Pinned llvmdev 3.7.1. Run all tests

060bf17

Add TAGGED_RELEASE_BANNER

056cb20

tkelman reviewed Aug 17, 2017

View reviewed changes

dfornika added 3 commits August 17, 2017 09:56

[skip appveyor] Removed automake, autoconf and libxml2

9e15f34

[skip appveyor] Added perl as build requirement

747d101

[skip appveyor] Missing space before package name perl

8c6810f

isuruf reviewed Aug 17, 2017

View reviewed changes

[skip appveyor travis] Added arpack

d15efd2

isuruf reviewed Aug 17, 2017

View reviewed changes

[skip appveyor] [skip travis] Added curl as runtime requirement

e41adf6

dfornika added 2 commits August 17, 2017 13:37

[skip appveyor] Removed libssh2

a2b0fbe

[skip appveyor] Added suitesparse

79e1f4e

[skip appveyor] Added timeout modifier

0a95d04

isuruf reviewed Aug 18, 2017

View reviewed changes

[skip appveyor] Removed timeout modifier

6cb50af

isuruf merged commit ce8835c into conda-forge:master Aug 18, 2017

dfornika mentioned this pull request Aug 18, 2017

Julia 0.5.2 bioconda/bioconda-recipes#5500

Closed

4 tasks

SylvainCorlay mentioned this pull request Sep 9, 2017

WIP Add recipe for cxxwrap #3925

Closed

jakirkham mentioned this pull request Sep 12, 2017

Remove wrapper script conda-forge/julia-feedstock#10

Closed

jakirkham mentioned this pull request Sep 17, 2017

Require openspecfun conda-forge/julia-feedstock#26

Merged

jakirkham mentioned this pull request Nov 14, 2017

Suggestion to use the pre-built julia binaries conda-forge/julia-feedstock#41

Closed

julia-0.5.2 #3503

julia-0.5.2 #3503

Conversation

dfornika commented Aug 10, 2017 • edited by jakirkham Loading

conda-forge-linter commented Aug 10, 2017

conda-forge-linter commented Aug 10, 2017

conda-forge-linter commented Aug 10, 2017

conda-forge-linter commented Aug 10, 2017

conda-forge-linter commented Aug 10, 2017

bgruening left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dfornika commented Aug 11, 2017 • edited Loading

acaprez commented Aug 11, 2017

dfornika commented Aug 11, 2017

acaprez commented Aug 11, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tkelman Aug 11, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tkelman Aug 12, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dfornika Aug 12, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jakirkham commented Aug 12, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dfornika commented Aug 17, 2017

dfornika commented Aug 17, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tkelman Aug 17, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

isuruf commented Aug 17, 2017

jakirkham commented Aug 17, 2017

tkelman commented Aug 17, 2017

isuruf commented Aug 18, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tkelman commented Aug 18, 2017

isuruf commented Aug 18, 2017

jakirkham commented Aug 18, 2017

jakirkham commented Sep 12, 2017

dfornika commented Aug 10, 2017 •

edited by jakirkham

Loading

dfornika commented Aug 11, 2017 •

edited

Loading

tkelman Aug 11, 2017 •

edited

Loading

tkelman Aug 12, 2017 •

edited

Loading

dfornika Aug 12, 2017 •

edited

Loading

tkelman Aug 17, 2017 •

edited

Loading