Skip to content
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

[miniupnpc] Update to 2.3.0 #43233

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

MonicaLiu0311
Copy link
Contributor

Fixes #40552. Update miniupnpc to 2.3.0.

No feature needs to be tested, the usage test succesfully on x64-windows(header file found).

In PR #40552, I changed REF "miniupnpc_${MINIUPNPC_VERSION}" to "miniupnpd_${MINIUPNPC_VERSION}". I forgot the reason, it may be a mistake, I'm sorry. The good thing is that I found that miniupnpc has no upstream or downstream in vcpkg, and there has been no related issues since PR #40552, so it can be assumed that it has not affected any other ports and users during this period. Sorry again.

  • Changes comply with the maintainer guide.
  • SHA512s are updated for each updated download.
  • The "supports" clause reflects platforms that may be fixed by this new version.
  • Any fixed CI baseline entries are removed from that file.
  • Any patches that are no longer applied are deleted from the port's directory.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Only one version is added to each modified port's versions file.

@MonicaLiu0311 MonicaLiu0311 added info:internal This PR or Issue was filed by the vcpkg team. category:port-update The issue is with a library, which is requesting update new revision labels Jan 13, 2025
@MonicaLiu0311 MonicaLiu0311 mentioned this pull request Jan 13, 2025
7 tasks
@MonicaLiu0311 MonicaLiu0311 marked this pull request as ready for review January 13, 2025 07:59
Comment on lines -4 to +5
"git-tree": "7cd06d47cb0cbaf659be8195bf06f2aef1980746",
"version": "2.3.7",
"git-tree": "1df0846b7dbe04a4f9904be58d30759b16f119f0",
"version": "2.3.0",
Copy link
Contributor Author

@MonicaLiu0311 MonicaLiu0311 Jan 13, 2025

Choose a reason for hiding this comment

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

The removal was done because there is no 2.3.7 version on the miniupnpc branch.

@dg0yt
Copy link
Contributor

dg0yt commented Jan 13, 2025

AFAIU manifest mode version constraints are broken for miniupnpc as long as there is a bad 2.3.7 entry in versions/m-/miniupnpc.json, with the implementation being older than 2.3.0.

@MonicaLiu0311
Copy link
Contributor Author

AFAIU manifest mode version constraints are broken for miniupnpc as long as there is a bad 2.3.7 entry in versions/m-/miniupnpc.json, with the implementation being older than 2.3.0.

Yes, it happens during this period...

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:internal This PR or Issue was filed by the vcpkg team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants