update recipe Dec 2020

[hmaarrfk]

Closes #17 #18 #19

Apparently an updated version fixes compilation errors
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971106

Many image processing librarires have already migrated to newer hdf5. I had to force the migration myself to install this package in conjunction with my other ones.

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.

I do have some suggestions for making it better though...

For recipe:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[hmaarrfk]

it seems many pinnings were due to some unknown issues with particular versions of the library:

#5

[hmaarrfk]

@conda-forge/help-c-cpp does anybody know why the following error is appearing:

dyld: Library not loaded: @rpath/libgobject-2.0.0.dylib
  Referenced from: /Users/runner/miniforge3/conda-bld/libvips_1607387342067/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib/libMagickCore-7.Q16HDRI.7.dylib
  Reason: Incompatible library version: libMagickCore-7.Q16HDRI.7.dylib requires version 6501.0.0 or later, but libgobject-2.0.0.dylib provides version 0.0.0

[hmaarrfk]

glib 2.58 is a pretty old package conda-forge/glib-feedstock#41
https://anaconda.org/conda-forge/glib/files?page=2

[hmaarrfk]

@conda-forge/help-osx-arm64 (ok, i know this isn't arm, but I figure you know the most about Apple).

How do we feel about moving the OSX pinning up to 10.10. 10.9 is becoming increasingly harder to support for graphical applications.

[xhochy]

@hmaarrfk Not sure why you have bumped glib to a much higher version than the pinning here. Keeping it at 2.58 would avoid the OSX update.

[hmaarrfk]

@xhochy thanks for chiming in.

Please see the build logs of 467e687 and the error reported in:
#20 (comment)

tschoonj suggested applying the migration. conda-forge/glib-feedstock#77 (comment)

Lets see what happens.

[hmaarrfk]

This needs:

• Dependen on glib imagemagick-feedstock#161 (which passed)
• Glib 2.64 migration imagemagick-feedstock#162

[hmaarrfk]

thanks everybody. this is ready to go now.

[hmaarrfk]

@conda-forge/libvips i've added myself as a maintainer to help along if that is ok.

Let me know if there is antyhing else i can change.

[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.

[hmaarrfk]

@conda-forge/libvips a review would be greatly appreciated. The previous pinnings stop this package from getting installed smoothly with recent migrations.

[sebastian-luna-valero]

Hi @hmaarrfk

Many thanks for your contribution!

I am happy with the changes and having you on board as a recipe maintainer would be great.

Can I just double check whether @jcupitt is happy before merging?

Best regards,
Sebastian

[hmaarrfk]

Thanks @sebastian-luna-valero

[sebastian-luna-valero]

Welcome @hmaarrfk !

[jcupitt]

Sure, I'm more than happy. Thank you for your hard work!