search

chocolatey-community / chocolatey-packages

Chocolatey Community Maintainers Team Packages - packages that are managed and maintained by core community team for community package repository (https://community.chocolatey.org/packages)
https://community.chocolatey.org/profiles/chocolatey-community
Apache License 2.0
446 stars 376 forks source link

(codelite) Package upgrades/uninstalls are not silent #2181

Closed brogers5 closed 1 year ago

brogers5 commented 1 year ago

Chocolatey Version

1.3.1

Chocolatey License

None

Package Version

8.0.0+

Current Behaviour

During both package upgrades and uninstalls, the user is prompted to either keep or remove their current user settings, and requires manual user input to proceed:

Codelite Uninstall Prompt

The uninstall instances in particular are causing CI validation failures, due to the process timing out during testing.

Expected Behaviour

Package upgrades/uninstalls should complete successfully without requiring manual user input.

This will likely require a chocolateyuninstall.ps1 script to be added to the package, ideally to pass the required arguments to implement a silent uninstallation, or alternatively, utilize an AutoHotkey script to at least make the process unattended.

A similar approach may be required for software upgrades.

Steps To Reproduce

Upgrade

  1. Install a previous version of codelite (e.g. choco install codelite --version=15.0.0).
  2. Upgrade to a later package version (i.e. choco upgrade codelite).

Uninstall

  1. Install an affected version of codelite (e.g. choco install codelite --version=16.0.0).
  2. Uninstall the previously installed package (i.e. choco uninstall codelite).

Environment

- Operating System: Microsoft Windows NT 10.0.22621.0
- PowerShell Version: 5.1.22621.963
- Shell: Windows PowerShell

Chocolatey Log

Upgrade: https://gist.github.com/brogers5/81a84356fd0e4d482033ab20ec679a3d
Uninstall: https://gist.github.com/brogers5/54590a34a371269530d4de03d6041bea

Anything else?

No response

github-actions[bot] commented 1 year ago

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue will be closed in 14 days if it continues to be inactive.

brogers5 commented 1 year ago

Yes, this is still an issue. Lack of time and interest in fixing this is the primary blocker.

Core maintainers, I'd recommend marking this one as Up for Grabs.

pauby commented 1 year ago

@brogers5 Every issue is up for grabs by default as this is a community maintained repository, but I have added the label. Maybe we add this by default ...

github-actions[bot] commented 1 year ago

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue will be closed in 14 days if it continues to be inactive.

github-actions[bot] commented 1 year ago

Dear contributor,

As this issue seems to have been inactive for quite some time now, I've automatically closed it. If you feel this is a valid issue, please feel free to re-open the issue if/when a pull request has been added. Thank you for your contribution.