An unexpected error occurred while executing the command:
Download request status is not success.
0x80190194 : Not found (404).
#Winget package broken
raw dove
lunar pelican
damn that's ancient
arctic locust
That's an old build that's no longer supported, you can try opening an issue on the WinGet repo requesting that they update to v2.4.62.
lunar pelican
That's an old build that's no longer supported, you can try opening an issue on ...
i did one better https://github.com/files-community/Files/issues/12099
wait hold up
arctic locust
@lunar pelican We don't need to continuously update WinGet because the app will auto update. The issue in this case was that I forgot it was being used by WinGet and I removed the old version from the endpoint.
lunar pelican
<@684428788481917044> We don't need to continuously update WinGet because the ap...
well yeah but why add that extra layer of indirection
arctic locust
Unless we keep old packages around forever, users will see old versions on WinGet and wonder why they don't install.
I'd rather have one good package that always works
lunar pelican
Unless we keep old packages around forever, users will see old versions on WinGe...
the exe installer downloads the latest version at runtime, right?
lunar pelican
Can we use that?
we can, but the version info will be broken if it isn't updated manually
lunar pelican
Unless we keep old packages around forever, users will see old versions on WinGe...
not necessarily, you're in control of that
i think?
yeah
although i'm a bit confused about 'one version per pr', does that mean removal and addition must be separate? in any case it's probably fine to host at most two versions at a time
yep, that does appear to be the case
arctic locust
although i'm a bit confused about 'one version per pr', does that mean removal a...
It means you have to open separate PRs
lunar pelican
fine with being broken or fine with updating manually
arctic locust
With the version number being wrong
But honestly, it's probably better to just leave an old version around and rely on auto update
lunar pelican
auto update won't trigger for at least 8 hours after install right
or does files have a special ui telling you to update
arctic locust
auto update won't trigger for at least 8 hours after install right
It'll trigger as soon as the app is opened the first time
lunar pelican
that works
arctic locust
or does files have a special ui telling you to update
There is a toolbar button
lunar pelican
cool
lmao this is actually a bit of a regression because the previously free store version automatically showed up
arctic locust
I think this brings us back to the first solution to update the package to v2.4.62 and just rely on auto update.
lunar pelican
mhm