Don't generate build-id files in RPM packages #1050
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
build-id metadata is only there in case someone wants to use debugger tools. When left enabled, build-id files are created in /usr/lib/.build-id on RHEL 8 systems. This can lead to potential conflict when multiple packages have the same build-id file. This conflict prevents the second package from installing. This conflict has been seen when installing Chef Infra Client 17.1.35+ and Chef Workstation 21.8.555+. Signed-off-by: Jeremiah Snapp <jeremiah@chef.io>
tas50
approved these changes
Dec 10, 2021
tas50
deleted the
jsnapp/stop-generating-build-id-files-in-rpm-packages
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
build-id metadata is only there in case someone wants to use debugger tools. When left enabled, build-id files are created in /usr/lib/.build-id on RHEL 8 systems. This can lead to potential conflict when multiple packages have the same build-id file. This conflict prevents the second package from installing. This conflict has been seen when installing Chef Infra Client 17.1.35+ and Chef Workstation 21.8.555+.