Stricter pinning on libtiff

[hmaarrfk]

Comment:

I would like to pin libtiff a littler harder than it currently is.

While the ABI is compatible between builds, it seems that the returned values from the libraries often change by a very small amount to make it so that downstream projects need to patch before they become compatible with libtiff.

This is, for example, what is happening with pillow at the moment with:

• libtiff v4.4.0 #76
• Build with compatibility for libtiff 4.4 pillow-feedstock#119

[ocefpaf]

I'm OK with that. We should updated the run_exports here and the global pin. What to you suggest x.x or x.x.x?

[hmaarrfk]

x.x

[hmaarrfk]

the problem is, that without a widespreading repodata patch, old packages that are build will be "chosen" over new packages that are claimed to be incompatible with a new release.

[ocefpaf]

the problem is, that without a widespreading repodata patch, old packages that are build will be "chosen" over new packages that are claimed to be incompatible with a new release.

Indeed :-(

[hmaarrfk]

For now, I did a "widespread" patch for pillow, but you know, this is less than ideal.

[hmaarrfk]

an other one bites the dust: #78

[hmaarrfk]

libtiff 4.5.0 broke abi compatibility with 4.4. I'm going to pin harder today

@conda-forge-admin please rerender

[conda-forge-linter]

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

I just wanted to let you know that I rerendered the recipe in #86.