Changed SONAME in 1.4.4 creates problems downstream

[zklaus]

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

The SONAME change introduced in 1.4.4 creates problems downstream, see e.g. conda-forge/cmake-feedstock#192. Perhaps a migrator would be a good idea? Also repodata patches for downstream packages could be needed.

Installed packages

-

Environment info

-

[xylar]

I believe we're seeing this in:
conda-forge/gdal-feedstock#803
conda-forge/netcdf-fortran-feedstock#84

At the very lease, these PRs are seeing issues with rhash that seem to be new since yesterday.

[zklaus]

@xylar, I think you are right, but it is by proxy via Cmake. The latest Cmake build (which is only 1 hour old) should work, so I believe for the immediate problem it's enough to restart the ci.

[h-vetinari]

Should we not raise an issue for this upstream? Why was the SONAME bumped in a patch release?

[zklaus]

Hm. I guess as long as the project hasn't committed to a certain versioning strategy, there isn't really anything wrong with it, though it certainly is a bit surprising.

Anyway, I am gonna close this issue because @isuruf solved it with repodata patches. In fact he thought of the issue before it occurred and was careful enough to put the appropriate patch (conda-forge/conda-forge-repodata-patches-feedstock#531) in before making the SONAME/SOVERSION change. Unfortunately a small problem crept in which was then later rectified by conda-forge/conda-forge-repodata-patches-feedstock#533, so now all should be good.