You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On certain scenarions, the scoop update script will call a specific powershell command, that will ask for confirmation or will hang until an input is given. This behaviour, that shoule be able to be easily fixed by adding the argument that the prompt refers to, can block unattended runs or integrations, as it did in the WingetUI app. (repost from martinet101/WingetUI#207)
Expected Behavior
scoop updates the package without further confirmation
Additional context/output
This issue might occurr when calling powershell -Command scoop update package
It won't occur when directly calling scoop update package (don't know why, it just happens like this).
Bug Report
Current Behavior
On certain scenarions, the scoop update script will call a specific powershell command, that will ask for confirmation or will hang until an input is given. This behaviour, that shoule be able to be easily fixed by adding the argument that the prompt refers to, can block unattended runs or integrations, as it did in the WingetUI app.
(repost from martinet101/WingetUI#207)
Expected Behavior
scoop updates the package without further confirmation
Additional context/output
This issue might occurr when calling
powershell -Command scoop update package
It won't occur when directly calling
scoop update package
(don't know why, it just happens like this).further details can be found here: marticliment/UniGetUI#207
Possible Solution
Add that argument that will make the process unattended
System details
W10 and W11 affected (not tested on any other platforms)
Windows version: 10/11
OS architecture: 64bit
PowerShell version:
Additional software:
git installed for scoop updating
Scoop Configuration
The text was updated successfully, but these errors were encountered: