fix(rpm): add vendor field to fpm config to avoid (none) vendor#3961
Merged
nekohasekai merged 1 commit intoSagerNet:testingfrom Mar 29, 2026
Merged
fix(rpm): add vendor field to fpm config to avoid (none) vendor#3961nekohasekai merged 1 commit intoSagerNet:testingfrom
nekohasekai merged 1 commit intoSagerNet:testingfrom
Conversation
5 tasks
Member
|
Thanks |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds the
--vendorfield to the Ruby fpm configuration .Generated RPM packages with
Vendor: (none)causes vendor change warnings in zypper on openSUSE.After this change, RPM metadata should correctly includes:
This will improve compatibility with openSUSE, which relies on the
Vendorfield for vendor stickiness and package upgrade decisions. This will fix #3962 .