Fail the RPM build if FPM tool is not present#20633
Merged
marcpopMSFT merged 2 commits intodotnet:release/8.0.1xxfrom Oct 13, 2025
Merged
Fail the RPM build if FPM tool is not present#20633marcpopMSFT merged 2 commits intodotnet:release/8.0.1xxfrom
marcpopMSFT merged 2 commits intodotnet:release/8.0.1xxfrom
Conversation
Member
Author
|
Failure in source-build and regular (non-pkg) Linux leg - neither of these should even attempt to build RPM packages, but that's what's happening. More changes are needed. |
Member
Author
|
Pushed a fix. |
jkoritzinsky
approved these changes
Oct 13, 2025
Member
Author
|
This is now passing all checks - @marcpopMSFT is there a reason not to merge this yet? Same for 9.0 change: dotnet/sdk#51170 |
Member
|
Branch is still open so we can merge. |
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
3 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.
Currently, if the build is supposed to produce RPM packages, but the tooling (i.e.
fpm) is missing, a message will be logged and the build will skip the RPM package generation. This can result in successful builds that are missing the required artifacts.Additional changes were needed, as RPM targets were being executed for any build that was running on RPM-based distro due to:
installer/src/redist/targets/GenerateRPMs.targets
Line 19 in fa82557
The use of property
IsRPMBasedDistrowas overloaded to mean both that the distro is RPM-based and that we want to build installers.Property was set here:
installer/src/redist/targets/GetRuntimeInformation.targets
Lines 27 to 28 in fa82557
For installer build we were passing this same property, which was already being set on rpm-based distros, so this wasn't correct:
installer/.vsts-pr.yml
Line 250 in fa82557
I am now setting a different property,
BuildSdkRpm, in scenarios where RPM packaging is desired. This matches DEB build experience, where we have a similar pair of properties:BuildSdkDebandIsDebianBaseDistro.Notes
Fix for 8.0.1xx - will be backported to other 8.0.x branches in support. Separate fix will be made for 9.0.
Contributes to #20561