cleanup v1.6 LTS

[ngam]

Fixes #171
Fixes #166
Fixes #167

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

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 (recipe) and found it was in an excellent condition.

[ngam]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/julia-feedstock/actions/runs/1624803404.

[mkitti]

Also this fixes the 1.6 branch. I have not checked what openlibm version Julia 1.6.5 uses.

[ngam]

Also this fixes the 1.6 branch. I have not checked what openlibm version Julia 1.6.5 uses.

https://github.com/JuliaLang/julia/blob/96a99c268a96ee61f6ff8fe4c2d53208f0cb042a/deps/Versions.make#L86-L89

V0.7.3 --- submitting a build for that. But generally, the differences between the 0.7.x builds are very minor. That's partly why hard pinning is discouraged --- why pin so hard if you can be relax stuff? Upstream should relax their pinnings and give ranges, rather than exact pinning. Oh I forgot ... they vendor it all... 🤣

[ngam]

Also this fixes the 1.6 branch. I have not checked what openlibm version Julia 1.6.5 uses.

https://github.com/JuliaLang/julia/blob/96a99c268a96ee61f6ff8fe4c2d53208f0cb042a/deps/Versions.make#L86-L89

V0.7.3 --- submitting a build for that. But generally, the differences between the 0.7.x builds are very minor. That's partly why hard pinning is discouraged --- why pin so hard if you can be relax stuff? Upstream should relax their pinnings and give ranges, rather than exact pinning. Oh I forgot ... they vendor it all... 🤣

update: not going to build v0.7.3 --- will require a significant patch to work that will only basically make it v0.7.4. So we can safely use v0.7.4 or v0.7.5 here.

JuliaMath/openlibm@v0.7.3...v0.7.4

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[SylvainCorlay]

This appears to cause some breakage downstream.

Julia is looking for PREFIX/lib/julia/libopenlibm.so (or dylib) at runtime and not finding it.

[SylvainCorlay]

Logs of a failing CI build downstream: https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/432647/logs/14

[mkitti]

@SylvainCorlay the logs show you are using 1.6.5-h132cb31_0 and not the builds produced about 29 hours ago ( osx-64/julia-1.6.5-h132cb31_1.tar.bz2 )

[SylvainCorlay]

Thanks, it seems to be fixed with the newest build indeed.

[SylvainCorlay]

@mkitti I am seeing the latest build of Julia segfault when doing Pkg.install.

https://github.com/xtensor-stack/xtensor-julia/runs/4738787473?check_suite_focus=true

[mkitti]

The segfaults are occurring in libcurl ... and 7.81 was just released on conda-forge.