-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
[Package Issue]: EPOS.EposConnect #174756
Comments
It appears that version In this situation, the package manager displays the less-than chevron This is closer to a feature request, to display the version number in Registry instead of the "chevron-lowest version number" system currently used. |
I think a manifest change does also solve this though @stephengillie - Since there is only one version in the Repo, there should be no need for AppsAndFeaturesEntries |
@Trenly I've initially added the ARP entries as EPOS does not use the full display versions on their website and in the changelogs, but besides that I don't see any reason why we shouldn't use the full versioning as PackageVersion. Additionally, setting a different publisher in the AppsAndFeatures entries was quite unfortunate. However on a technical level I'm genuinly interested why removing the ARP entry leads to better package matching here. |
As far as I know, there isn't a ton of great documentation outside of a few comments on threads here or there. The basics of it is that normally,
However, when the This is what introduces the problem, though. By creating the VersionRange, WinGet switches to a mapping logic instead of an ordering logic. Normally, WinGet just compares to see if Version A is greater than Version B. When using the VersionRange, WinGet checks to see if Version A is greater than, less than, or within the range specified for Version B. Since the ranges are being used, WinGet can't map the |
@Trenly Thank you for the very detailed explanation! Apprecciate it! |
This documents the situation very clearly. Were this to go into the documentation, where would be the best place? Would you be willing to add a section like this? |
Please confirm these before moving forward
Category of the issue
Other
Brief description of your issue
when I run winget upgrade the installed version of EPOS.EposConnect is not displaying the current version.
EPOS Connect
EPOS. EposConnect
< 7.9.0 (installed version)
7.9.0
Steps to reproduce
install a previous version of Epos (for example 7.8.2) and run winget upgrade and you will see that the installed version detected shows like "< 7.9.0"
Actual behavior
run winget upgrade and you will see that the installed version detected shows like "< 7.9.0"
Expected behavior
run winget upgrade and you will see that the installed version detected shows like "7.8.2"
Environment
Screenshots and Logs
The text was updated successfully, but these errors were encountered: