-
-
Notifications
You must be signed in to change notification settings - Fork 200
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
Problem updating by winget on Windows #431
Comments
I can see that the package is missing the commit sem ver label in the winget packages. Although, I cannot replicate the issue myself since the update works for me |
This is still a problem, and fairly easy to recreate (for me, your mileage may differ). Start with a system that does not have GalaxyBudsClient installed. Then install it as shown below - following the successful install, a list command will show the version mismatch, and update will re-download and re-install even though you just installed the latest copy a moment ago.
A tangential error to point out - the latest version available via winget is 4.5.4 (a.k.a. 4.5.4-1dfedf), it hasn't been updated to 4.6.0 yet. |
This will be fixed in the next version. A while back, my CI build script stopped setting the correct version information. |
Fixed, see #522 (comment) |
Launching an update via winget, it constantly find the installed version is different from the git hub version:
Name Id Available Version
Galaxy Buds Manager (Unofficial) 4.5.4-1dfedf (64bit) ThePBone.GalaxyBudsClient 4.5.4-1dfedf 4.5.4
The package from the Windows installer has a "-1dfedf" at the end of the id that triggers the difference.
The installer available on github and the one downloaded by winget are the same.
Obviously, versions should be the same.
The text was updated successfully, but these errors were encountered: