[Packaging][RPM] Mismatch between package version and library version in naming #41784
Comments
kou
changed the title
|
We should use |
kou
added a commit
to kou/arrow
that referenced
this issue
May 27, 2024
kou
added a commit
to kou/arrow
that referenced
this issue
May 27, 2024
kou
added a commit
to kou/arrow
that referenced
this issue
May 27, 2024
kou
added a commit
to kou/arrow
that referenced
this issue
May 27, 2024
kou
added a commit
that referenced
this issue
May 28, 2024
) ### Rationale for this change We should use `arrow${SO_VERSION}-libs` not `arrow${MAJOR_VERSION}-libs` to co-exist newer versions and older versions. ### What changes are included in this PR? Use SO version not major version. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * GitHub Issue: #41784 Authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
|
Issue resolved by pull request 41838 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug, including details regarding any error messages, version, and platform.
Version: 16.1.0
Platform: Red Hat Enterprise Linux release 9.4 (Plow)
Summary: The version number in the library name does not match the version of the package that is installed. This causes load time issues where we fail to find library dependencies even when version mismatch is only on minor version change, which should backwards compatible.
Steps to Reproduce:
ls /lib64/libarrow.so*)Expected Result: The libraries should be labeled with the correct version number (16.1.0) with symlinks for major version and non versioned.
For example, I would expect to find:
Actual Result: The libraries are labeled with an incorrect version number (1601.0.0)
Component(s)
Packaging
The text was updated successfully, but these errors were encountered: