[release/6.0-staging] Define installer-owned directories in dotnet-runtime RPM package #98246
Conversation
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
ghost
added
the
NikolaMilosavljevic
added
the
Servicing-consider
jkoritzinsky
approved these changes
Feb 9, 2024
NikolaMilosavljevic
added
Servicing-approved
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #97183 to release/6.0-staging
Customer Impact
dotner-runtimeRPM package does not define any directories it owns. This causes versioned directory to be left on the machine after uninstall or package upgrade. Presence of the old directory triggers S360 warning about unsecure, stale .NET version.There are no issues with other .NET packages -
dotnet-hostfxrandaspnetcore-runtimepackages contain versioned directories which are properly deleted on package uninstall or upgrade.Regression
Not a regression - the issue always existed.
Testing
Built a private package with the fix and tested on Mariner 2.0.
Risk
Low. Already tested and present in 9.0.