-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
snappy-1.2.0
provides libsnappy.so.1.1.10
with different function signatures.
#35
Comments
snappy-1.2.0
provides lib/libsnappy.so.1.1.10
but with different function signatures.
snappy-1.2.0
provides lib/libsnappy.so.1.1.10
but with different function signatures.snappy-1.2.0
provides libsnappy.so.1.1.10
with different function signatures.
I am seeing this too. I suppose we should request for the packages to be marked broken? https://conda-forge.org/docs/maintainer/updating_pkgs/#maint-fix-broken-packages |
This completely breaks pyarrow, leading to segfaults. |
I am too observing an |
#36 has been opened to fix the runtime requirements accordingly. |
I just opened conda-forge/admin-requests#973 to mark it as broken. Should that still happen if updating the runtime requirements in #36? (I would think so given that results in new builds, and the packages with build 0 would still give the problems described here?) |
If #36 is merged, a repodata patch also has to be added for the already-published builds of snappy-dependent projects to depend on snappy <1.2.0. |
The package has been marked as broken. I think the next steps are:
|
conda-forge/conda-forge-repodata-patches-feedstock#699 is ready for review. |
google/snappy#178 fixes it. |
google/snappy@766d24c broke the ABI |
#37 and conda-forge/conda-forge-pinning-feedstock#5730 fixe further things. |
Should those PRs in this repo have already been merged? Because that now again results in the original issue, i.e. creating a fresh environment installs pyarrow with snappy which then gives an ImportError (because the new build 1 for snappy 1.2.0 is not marked as broken) |
Or does it take a while before the repodata-patches are propagated? |
The initial repodata patch was faulty but should be fixed since 30min but probably not yet fully migrated through the CDN. |
Everything seems fine now. |
Looks like issue is still isn't resolved and Google released 1.2.1: https://github.com/google/snappy/releases/tag/1.2.1 Can someone update package for conda too, please? |
Solution to issue cannot be found in the documentation.
Issue
Is it expected that
snappy-1.2.0
would be based onlibsnappy.so.1.1.10
? Wondering if it is an error that it is namedlibsnappy.so.1.10
instead oflibsnappy.so.1.2.0
.What seems problematic is that it is not really the same underlying version of
libsnappy.so
.When I look at
libsnappy.so.1.1.10
fromsnappy-1.2.0
, I see:When I look at
libsnappy.so.1.1.10
fromsnappy-1.1.10
, I see:Anything expecting the latter will fail a symbol lookup with the newer version.
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: