-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repair an App that is behaving badly #148
Comments
The easiest way to repair something is usually to uninstall the package and install the same version again. |
@denelon if it is not too much of an addition though, perhaps the addition of an --all or --tags options to the repair command? I think that would be useful to have in the of chances you are looking to repair your environment or a specific set of tools. I would also think that since this would vary wildly between each package we would need to make sure that winget can understand and make the correct changes based on how it was installed. might be useful to consider a sort of package maintainer side doc/script/template that winget could follow in which they add this information. |
Add YAML manifest entries for winget repair behavior Manifest Entries includes: - The `Repair `switch, within `InstallerSwitch,` allows for custom repair of a package. - The `RepairBehavior` enum field, present in the Installer & root level field, determines the repair behavior for the source package used to repair a package. - Updated the test manifest (ManifestV1_7-MultiFile-Installer.yaml) and the test code that validate the Repair switch and RepairBehavior fields. **[How Validated:]** - Made the necessary changes to the manifest - Ran the ManifestValidation tests that are part of AppInstallerCLITests and verified that all the tests passed **[Test Result:]** ``` Filters: [ManifestValidation] =============================================================================== All tests passed (4008 assertions in 30 test cases) Filters: [ManifestCreation] =============================================================================== All tests passed (1309 assertions in 7 test cases) ``` **TODO's:** - [ ] Determine the interdependency validation between the "RepairBehavior" and "Repair" fields. Should this be a semantic validation or a validation at the time of workflow execution as an early validation step? <!-- To check a checkbox place an "x" between the brackets. e.g: [x] --> - [x] I have signed the [Contributor License Agreement](https://cla.opensource.microsoft.com/microsoft/winget-pkgs). - [x] This pull request is related to an issue. Related to : * #148 ----- ###### Microsoft Reviewers: [Open in CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com/microsoft/winget-cli/pull/4041)
This PR introduces the Design specification for the repair functionality in Windows Package Manager. This new feature will allow users to repair installed packages using the Windows Package Manager. <!-- To check a checkbox place an "x" between the brackets. e.g: [x] --> - [x] I have signed the [Contributor License Agreement](https://cla.opensource.microsoft.com/microsoft/winget-pkgs). - [x] This pull request is related to an issue. Related to: * #148 ----- ###### Microsoft Reviewers: [Open in CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com/microsoft/winget-cli/pull/3943)
As a user I want to be able to repair my app if it is not working correctly.
Client:
winget repair <appname>
Repair can only be done as a single apps as it doesn't seem to make sense to do this for all installed applications.
Most installers have a repair mode.
The text was updated successfully, but these errors were encountered: