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

[stftpitchshift] Update to 1.4.1 #24599

Merged
merged 19 commits into from
May 10, 2022
Merged

[stftpitchshift] Update to 1.4.1 #24599

merged 19 commits into from
May 10, 2022

Conversation

jurihock
Copy link
Contributor

@jurihock jurihock commented May 7, 2022

Describe the pull request

  • What does your PR fix?

    update stftpitchshift to v1.4.1

  • Which triplets are supported/not supported? Have you updated the CI baseline?

    all, yes

  • Does your PR follow the maintainer guide?

    yes

  • If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

    yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

After committing all other changes, the version database must be updated
git add -u && git commit
git checkout a5d6d145164e82e67fbf91a4a30f98699d30de63 -- versions
./vcpkg x-add-version --all
Diff
diff --git a/versions/s-/stftpitchshift.json b/versions/s-/stftpitchshift.json
index d04954f..25dbd50 100644
--- a/versions/s-/stftpitchshift.json
+++ b/versions/s-/stftpitchshift.json
@@ -1,5 +1,10 @@
 {
   "versions": [
+    {
+      "git-tree": "74b15f8fdcad37aed9e50f2570ef361b362cf8bf",
+      "version": "1.4.1",
+      "port-version": 0
+    },
     {
       "git-tree": "1f4a495416b6e2e3a830c8ba72eb5cf9034c68cc",
       "version": "1.3.2",

@jurihock jurihock marked this pull request as ready for review May 7, 2022 21:04
@jurihock jurihock changed the title [stftpitchshift] release 1.4.1 [stftpitchshift] Update to 1.4.1 May 8, 2022
@Cheney-W Cheney-W added the category:port-update The issue is with a library, which is requesting update new revision label May 9, 2022
Funny suggestion, to use some kind of hidden ${PORT} variable just in one place and still the port name string otherwise...

Co-authored-by: Cheney Wang <38240633+Cheney-W@users.noreply.github.com>
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

PRs must add only one version and must not modify any published versions

When making any changes to a library, the version or port-version in vcpkg.json or CONTROL must be modified.

Error: Local changes detected for stftpitchshift but no changes to version or port version.
-- Version: 1.4.1
-- Old SHA: 74b15f8fdcad37aed9e50f2570ef361b362cf8bf
-- New SHA: 306cc6bce6fac599f2a15f6550994db455fad690
-- Did you remember to update the version or port version?
-- Pass `--overwrite-version` to bypass this check.
***No files were updated.***

@jurihock
Copy link
Contributor Author

jurihock commented May 9, 2022

@Cheney-W My original commit 1513d67 was successful, but after your suggestion 8c82315 there is a build error. Please troubleshoot...

@Cheney-W
Copy link
Contributor

Cheney-W commented May 9, 2022

You need run the following commands in your branch:
• .\vcpkg.exe x-add-version {port name} --overwrite-version
• git add .
• git commit -m "update json"
• git push

and not just in one place like suggested by Cheney-W
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

PRs must add only one version and must not modify any published versions

When making any changes to a library, the version or port-version in vcpkg.json or CONTROL must be modified.

Error: Local changes detected for stftpitchshift but no changes to version or port version.
-- Version: 1.4.1
-- Old SHA: 306cc6bce6fac599f2a15f6550994db455fad690
-- New SHA: e403812b23bdb6f86651104d3be9c001bea821fd
-- Did you remember to update the version or port version?
-- Pass `--overwrite-version` to bypass this check.
***No files were updated.***

@jurihock
Copy link
Contributor Author

jurihock commented May 9, 2022

Now I put the ${PORT} variable everywhere instead of the port name, although I don't understand what kind of issue it should fix.

Are there any further questions to the author of this port e.g. requirements for the "requires:author-response" label?

@@ -14,6 +14,17 @@ vcpkg_cmake_configure(

vcpkg_cmake_install()

file(INSTALL "${SOURCE_PATH}/LICENSE" DESTINATION "${CURRENT_PACKAGES_DIR}/share/stftpitchshift" RENAME copyright)
vcpkg_cmake_config_fixup(
PACKAGE_NAME "${PORT}"
Copy link
Contributor

@Cheney-W Cheney-W May 10, 2022

Choose a reason for hiding this comment

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

PACKAGE_NAME "${PORT}"
Thie sentence could be removed, PACKAGE_NAME defaults to ${PORT}.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

PRs must add only one version and must not modify any published versions

When making any changes to a library, the version or port-version in vcpkg.json or CONTROL must be modified.

Error: Local changes detected for stftpitchshift but no changes to version or port version.
-- Version: 1.4.1
-- Old SHA: e403812b23bdb6f86651104d3be9c001bea821fd
-- New SHA: 36932b4bd7c57fdc63ae75ec5117f6321e3c2ca6
-- Did you remember to update the version or port version?
-- Pass `--overwrite-version` to bypass this check.
***No files were updated.***

@jurihock
Copy link
Contributor Author

So what else?

@Cheney-W Cheney-W added info:reviewed Pull Request changes follow basic guidelines and removed requires:author-response labels May 10, 2022
@Cheney-W
Copy link
Contributor

Thanks for your prompt reply, now just waiting for merge.

@BillyONeal BillyONeal merged commit 0e26d20 into microsoft:master May 10, 2022
@BillyONeal
Copy link
Member

Thanks for the update!

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:reviewed Pull Request changes follow basic guidelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants