[gpgme] add Qt feature, update to 1.18, add Windows support#26424
[gpgme] add Qt feature, update to 1.18, add Windows support#26424wrobelda wants to merge 57 commits intomicrosoft:masterfrom
Conversation
There was a problem hiding this comment.
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: checked-in files for gpgme have changed but the version was not updated
version: 1.14.0#2
old SHA: f037926ddc1a092f0db7089609e65ff9f221fa77
new SHA: fe3470e26541a9e5abd8b970a4483bebac4e1bff
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
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: checked-in files for gpgme have changed but the version was not updated
version: 1.18.0
old SHA: bb83ca2020b962e5d2daf4b0435e5b954d69a393
new SHA: 51f508a2bb7b0143e1218cf56bcc0751f314223b
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
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: checked-in files for gpgme have changed but the version was not updated
version: 1.18.0
old SHA: bb83ca2020b962e5d2daf4b0435e5b954d69a393
new SHA: 2260ea21cbfaec6d0daa09109006bf112dc829d5
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
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: checked-in files for gpgme have changed but the version was not updated
version: 1.18.0
old SHA: bb83ca2020b962e5d2daf4b0435e5b954d69a393
new SHA: fad7f5093dbde0c893a1aebe9fea1cf71789c517
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
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: checked-in files for gpgme have changed but the version was not updated
version: 1.18.0
old SHA: bb83ca2020b962e5d2daf4b0435e5b954d69a393
new SHA: d485e048a430c15768dc87fe27e4ef17453818a5
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
GitHub mirror is out of sync, so use GnuPG's own
There was a problem hiding this comment.
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: checked-in files for gpgme have changed but the version was not updated
version: 1.18.0
old SHA: bb83ca2020b962e5d2daf4b0435e5b954d69a393
new SHA: 50c026d801c00e441f7ac3d7923aadc78828288a
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
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: checked-in files for gpgme have changed but the version was not updated
version: 1.18.0
old SHA: bb83ca2020b962e5d2daf4b0435e5b954d69a393
new SHA: 50c026d801c00e441f7ac3d7923aadc78828288a
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
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: checked-in files for gpgme have changed but the version was not updated
version: 1.18.0
old SHA: bb83ca2020b962e5d2daf4b0435e5b954d69a393
new SHA: 50c026d801c00e441f7ac3d7923aadc78828288a
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
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: checked-in files for gpgme have changed but the version was not updated
version: 1.18.0
old SHA: bb83ca2020b962e5d2daf4b0435e5b954d69a393
new SHA: 50c026d801c00e441f7ac3d7923aadc78828288a
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
|
Pinging @wrobelda for response. Is work still being done for this PR? |
|
Closing this PR since it seems that no progress is being made. Please ping us to reopen if work is still being done. |
|
@Adela0814 please do reopen this, I was temporarily drawn to other work, but will return to it next week. Also, this depends on other PRs, as mentioned in the description. |
There was a problem hiding this comment.
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: checked-in files for gpgme have changed but the version was not updated
version: 1.18.0
old SHA: bb83ca2020b962e5d2daf4b0435e5b954d69a393
new SHA: 50c026d801c00e441f7ac3d7923aadc78828288a
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/gpgme/vcpkg.json
Valid values for the license field can be found in the documentation
|
Pinging @wrobelda for response. Is work still being done for this PR? |
|
@Adela0814 yes, I very much intend to finish this sometime soon. |
|
Is work still being done for this PR? please fix the conflicts. |
|
Closing this PR since it seems that no progress is being made. Please ping us to reopen if work is still being done. |
Describe the pull request
Depends on:
[qt5] libtool chokes at -framework in dependency_libs in libQt5Core.la #26467
[gpg-error, libassuan] update versions, add native Windows support #26433
[vcpkg] add updated compile wrapper for clang-cl #26340 (not merging to this branch as it triggers world rebuild)
[windres-rc] support --define, --include-dir #26454
What does your PR fix?
Fixes #...
Which triplets are supported/not supported? Have you updated the CI baseline?
<all / linux, windows, ...>, <Yes/No>
Does your PR follow the maintainer guide?
Your answerIf you have added/updated a port: Have you run
./vcpkg x-add-version --alland committed the result?<Yes / I am still working on this PR>
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/