-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[many ports] Update existing KF5 frameworks to 5.75 #13467
Conversation
kf5crash - make x11 patch exclusive to linux - enable win/macOS builds kf5syntaxhighlighting - fix building on non-Win by removing the cli tool from all platforms
My apologies, I pushed a new kf5auth port by mistake. |
This reverts commit 8703c24.
@NancyLi1013 FYI, I reverted the new kf5auth I accidentally added |
This reverts commit f1ac3db.
There is also another new port Edit: I noticed that you have removed just now. Please ignore this comment. |
LGTM now. Thanks for your PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM other than one question
@ras0219 @NancyLi1013 similarly to what I reported under PR #13469, I see that all the modified ports in this PR were also labeled as CASCADE by the CI run, which to my understanding implies they were skipped due to a missing/failing dependency. In this case it looks that for some reason |
Your understanding is right. The build results are related with those dependencies. |
@NancyLi1013 so I just run those builds locally on my Windows VM after learning they aren't actually being tested by the CI and I already had some failures. I don't believe I can consciously push this PR into the master unless we can actually have your CI to properly test all the supported triplets – I don't have the means to do so locally. @ras0219-msft I see that the ecm was excluded as part of this change of yours. May we know wat was wrong with ecm? The pull request doesn't mention anything specific about it. |
Hi @wrobelda I'm so sorry for updates many times, I reviewed this PR again and gave some extra suggestions. Please address them if you're free. LGTM now except for these review suggestions. The only problem is the failure on Linux, which is not related with the changes in this PR, but we still recommend to merge this PR after all CI checks passed. So we need to wait for the PR #15808 merged. |
Co-authored-by: NancyLi1013 <[email protected]>
Co-authored-by: NancyLi1013 <[email protected]>
Co-authored-by: NancyLi1013 <[email protected]>
Absolutely, nothing to apologize for! I totally understand we're held to high standards here and I appreciate your continuous feedback. All suggestions were addressed. |
There is nothing need to be done on your sides now, Let's wait for the PR #15808 merged. |
@NancyLi1013 it looks like #15808 has stalled. Is there anything else that can be done to obtain an unobstructed Linux CI/CD run and have this merged? |
Sorry, there is nothing to do except for waiting it merged. Unless the errors on Linux will disappear. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Will be fixed by another PR #16954 |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
LGTM now, thanks for your hard work and patience @wrobelda. |
* Add meson from microsoft/vcpkg#12860 * Add autoconf-archive from microsoft/vcpkg#13081 * Add kf5windowsystem libs from microsoft/vcpkg#13467 * Open the FTP and SFTP ports from microsoft/vcpkg#14412 * Add libxcb-util0-dev from microsoft/vcpkg#14678 * Add libasound2-dev from microsoft/vcpkg#14774 * Remove no longer necessary apt-mark calls. * Update nasm on Linux. * Fix longstanding bug where Storage was publicly accessible and change to generate SAS token rather than File Share * Delete no longer necessary azure storage firewall rules. * Install the newer Windows SDK with the VS installer instead of manually. * Install the VS2015 and VS2017 compilers. * Update Powershell-Core to 7.1.0. * Update source of WDK. * Update pools. * [opentracing] Repair arm64-windows failures caused by mojibake in `expected.hpp` and errors in opentracing-cpp's lint for arm64 where it thinks exceptions are disabled when they are enabled. Fixes: C:\Dev\vcpkg\buildtrees\opentracing\src\b67575dab0-0250653c81.clean\3rd_party\include\opentracing/expected/expected.hpp(1): warning C4828: The file contains a character starting at offset 0x4a77 that is illegal in the current source character set (codepage 65001). Fixes: D:\buildtrees\opentracing\src\b67575dab0-0250653c81.clean\include\opentracing/tracer.h:223:5: error: cannot use 'try' with exceptions disabled [clang-diagnostic-error] try { ^ * [mmloader] Patch out overrides of CMAKE_C_FLAGS and CMAKE_CXX_FLAGS that inserted /WX. Note that this port sets /GS-, possibly because it may be for authoring shellcode. * Bump storage API version to 2020-04-08.
Describe the pull request
Which triplets are supported/not supported? Have you updated the CI baseline?
No change in triplets supported.
Does your PR follow the maintainer guide?
Yes