Skip to content

Conversation

@JonLiu1993
Copy link
Contributor

Fix #27993

Update 7zip to the latest version 22.01

Note: no feature need to test.

@JonLiu1993 JonLiu1993 added info:internal category:port-update The issue is with a library, which is requesting update new revision labels Nov 24, 2022
github-actions[bot]
github-actions bot previously approved these changes Nov 24, 2022
"name": "7zip",
"version": "22.0",
"port-version": 1,
"version-string": "22.01",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I use the original "version", powershell tells me

error: while loading F:\Feature-test\v8\vcpkg\ports\7zip\vcpkg.json:
$ (a manifest): 'version' text was not a relaxed version:
error: `22.01` is not a valid relaxed version (semver with arbitrary numeric element count).

When I try to use "version-semver", I get the error again:

error: while loading F:\Feature-test\v8\vcpkg\ports\7zip\vcpkg.json:
$ (a manifest): 'version-semver' text was not a semantic version:
error: `22.01` is not a valid semantic version, consult

So in the end I chose "version-string"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is the problem with "versions": "22.1"?
vcpkg's unwillingness to handle leading zeros causes similar fuzziness for version-date in port poppler et al. Today, it also limits the usability of ${VERSION}.

@JonLiu1993 JonLiu1993 marked this pull request as ready for review November 24, 2022 12:35
@MonicaLiu0311 MonicaLiu0311 added the info:needs-maintainer-attention Lets the current 'on rotation' vcpkg maintainer know they need to look at this. label Nov 25, 2022
"name": "7zip",
"version": "22.0",
"port-version": 1,
"version-string": "22.01",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is the problem with "versions": "22.1"?
vcpkg's unwillingness to handle leading zeros causes similar fuzziness for version-date in port poppler et al. Today, it also limits the usability of ${VERSION}.

@JavierMatosD
Copy link
Contributor

Thank you!

@JavierMatosD JavierMatosD merged commit 37eb767 into microsoft:master Nov 28, 2022
@dg0yt
Copy link
Contributor

dg0yt commented Nov 28, 2022

IMO this PR needlessly degraded the version scheme.

@JonLiu1993 JonLiu1993 deleted the dev/Jon/7zip branch November 29, 2022 02:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

category:port-update The issue is with a library, which is requesting update new revision info:needs-maintainer-attention Lets the current 'on rotation' vcpkg maintainer know they need to look at this.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants