Open redactedscribe opened 5 months ago
I was under the wrong impression when writing this issue: I don't think WingetUI uses aria2c for downloading by default. It is only being used because I had enabled it for Scoop itself. Disabling it for Scoop causes the update to succeed using WingetUI. Therefore download errors using aria2c are unrelated to WingetUI, however it still remains that it would be convenient to be able to toggle using aria2c or not via WingetUI itself.
All that should be needed is reading the returned value of scoop config aria2-enabled
and then setting the opposite e.g. scoop config aria2-enabled false
before initialising the update. It can be immediately set back after the update begins I believe so that the next Scoop package uses aria2c again.
I have decided to disable aria2c since this issue occurs too regularly for me. I will see how it goes, but implementation of this temporary toggle shouldn't be too much of a challenge:
I previously suggested:
the right-click content menu could have an additional menu entry: "Update (without aria2c)", or similar.
Better would be a checkbox option to temporarily disable downloading using aria2c via the Installation options popup. This option only need be visible if scoop config aria2-enabled
returns true
(because it might be set via the command line rather than any UI toggle which you provide).
scoop config aria2-enabled
to false
.scoop config aria2-enabled
can be immediately set back to true
for the next download. It doesn't need to wait until the download has been completed. This way if the download is cancelled, scoop config aria2-enabled
won't remain false
by mistake.If the user wants to disable aria2c (not temporarily), you could offer a toggle via UniGetUI's preferences for Scoop.
Thanks.
Please confirm these before moving forward
Describe the improvement
Sometimes Scoop updates fail when trying to download them because of an aria2c error. WingetUI uses aria2c for Scoop updates by default and I don't think can be disabled (via the UI at least). I have encountered the same issue using aria2c quite a few times in the past (before using WingetUI), enough times that I decided to disable aria2c (which isn't enabled by default for Scoop).
In this particular case, I could not update emacs via WingetUI because of aria2c. Here is essentially the same output I saw in WingetUI but from running
scoop update emacs
manually:Then after disabling aria2c for Scoop (
scoop config aria2-enabled false
),scoop update emacs
:For this reason, I'd like a way to enable/disable using aria2c for all Scoop updates via WingetUI's preferences. Also, for updates which have Scoop as their source, and when aria2c is enabled, the right-click content menu could have an additional menu entry: "Update (without aria2c)", or similar.
Describe how this improvement could help users.
No need to resort back to the CLI to work around these aria2c download/update issues.
List of Scoop packages I've found to fail to update when aria2c is enabled