[Package Issue]: Jackaudio.JACK2 has superflous 'v' prepending version number and should be renamed

[luzpaz]

Please confirm these before moving forward

• I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
• I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

Other

Brief description of your issue

Per repology jack2 is showing a superfluous 'v' before the version name

This is how the package is listed in winget-pkgs

Note: this seems like an anomaly in winget-pkgs. Usually version numbers don't have a 'v' prepended.

This has been reported to repology

Per repology's answer, this needs to be corrected in this repo

Steps to reproduce

See above

Actual behavior

See above

Expected behavior

See above

Environment

n/a

Screenshots and Logs

See above

[Trenly]

When the package is installed, it writes v1.9.22 to the control panel, so the v is not superflous and is, in fact, required for matching the available version to the installed version.

--> Installing the Manifest v1.9.22

Found JACK2 [Jackaudio.JACK2] Version v1.9.22
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/jackaudio/jack2-releases/releases/download/v1.9.22/jack2-win64-v1.9.22.exe
  ██████████████████████████████  19.2 MB / 19.2 MB
Successfully verified installer hash
Starting package install...
Successfully installed

--> Refreshing environment variables

--> Comparing ARP Entries

DisplayName           DisplayVersion Publisher     ProductCode Scope
-----------           -------------- ---------     ----------- -----
JACK2 version v1.9.22 v1.9.22        jackaudio.org JACK2_is1   Machine

[luzpaz]

Not disputing that. It's just that, per repology, winget is the anomaly in comparison to the the rest of the packaging ecosystem. No other downstream packager prepends the 'v'.

[stephengillie]

• Improve version parsing to better support "preambles" winget-cli#2394

[luzpaz]

@stephengillie @Trenly looks the preamble issues has been resolved. Can you take a stab at this issue now?

[luzpaz]

soft bump

[Trenly]

It has been resolved in 1.9, but there could still be a significant portion of users who have not updated to the latest version of WinGet. The renames should wait until after the 1.9 manifest support is released into the pipelines, as that only happens after a majority of users have moved to the newer versions of WinGet

[luzpaz]

The renames should wait until after the 1.9 manifest support is released into the pipelines, as that only happens after a majority of users have moved to the newer versions of WinGet

Is there a way to determine when this moment arrives ?

[Trenly]

Is there a way to determine when this moment arrives ?

Yes, this issue will close when 1.9 manifests are supported in the pipelines -

• [New Feature]: WinGet 1.9 Schema support in Validation #186398