[vcpkg baseline] [forest] Remove forest#16836
[vcpkg baseline] [forest] Remove forest#16836strega-nil-ms merged 4 commits intomicrosoft:masterfrom
Conversation
|
Since this is a request from the library author I think we should honor it. |
|
@vicroms, could you help merge this PR? |
|
I'll discuss this with the rest of the team today. |
|
This is the first time we're removing a port since enabling versioning. We need to remove forest from the
@PhoebeHui Can you run through each of these 8 scenarios and report back with the behavior? |
|
@vicroms @ras0219-msft, here is test results, could you please take a look?
|
|
@vicroms This is blocked by versioning misbehaving. See failures: #16836 (comment) |
|
Case 1.i. is unfortunate, but is not related to versioning. It's due to our non-set-installed algorithm requiring portfiles to be available for all currently installed ports. All other cases are functioning as intended (missing sources notwithstanding). I think this LGTM. |
|
Can we remove the package completely? I ended up giving up on the project. |
|
@xorz57, sure, I also remove forest from ci.baseline, the failure cases doesn't relate to versioning feature, as Robert said. I think this PR is ready for merge. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Thanks y'all ❤️ |
Fixes #16735
We need to wait for the new port, and add the new port as a dependency. Or we remove this port directly, @vicroms, what do you think? Currently this issue also affect the CI unstable run, the hash of the forest changed.