Open giles45 opened 10 months ago
Confirmed, I can repro this in my side.
https://github.com/microsoft/vcpkg/pull/33215 But you can continue to use the old port version.
Confirmed, I can repro this on my side.
Same error
Current workaround for manifest mode is:
"builtin-baseline": "7476f0d4e77d3333fbb249657df8251c28c4faae",
"overrides": [
{
"name": "winpcap",
"version": "4.1.3#10"
}
]
I can also reproduce it on my side.
@andymylex I'm not sure how to use this workaround, can you please elaborate?
Is there a resolution to this? Im having the same issue.
@seladb example vcpkg.json
file used by my project:
{
"dependencies":
[
"winpcap"
],
"builtin-baseline": "7476f0d4e77d3333fbb249657df8251c28c4faae",
"overrides":
[
{
"name": "winpcap",
"version": "4.1.3#10"
}
]
}
It makes use of previous winpcap port which builds without error. builtin-baseline
is a hash of vcpkg commit from which ports versions are resolved.
https://learn.microsoft.com/en-us/vcpkg/users/examples/versioning.getting-started
@seladb example
vcpkg.json
file used by my project:{ "dependencies": [ "winpcap" ], "builtin-baseline": "7476f0d4e77d3333fbb249657df8251c28c4faae", "overrides": [ { "name": "winpcap", "version": "4.1.3#10" } ] }
It makes use of previous winpcap port which builds without error.
builtin-baseline
is a hash of vcpkg commit from which ports versions are resolved.https://learn.microsoft.com/en-us/vcpkg/users/examples/versioning.getting-started
Thank you @andymylex ! Is it possible to use overrides
in ports also?
We're currently working on updating the PcapPlusPlus port to the latest version and this is kind of a blocker for us.
cc @clementperon
@seladb no, it is not possible. so the only way to fix your port is to fix/rollback winpcap port i guess
Operating system
Windows
Compiler
MSVC
Steps to reproduce the behavior
Failure logs
D:\workspace\vcpkg\buildtrees\winpcap\build-x86-windows-rel-out.log
:Additional context
We have overnight vcpkg build for all our vcpkg dependencies.
The last overnight build that was successful was Aug 15, 2023 (576f3f1ad13bf2c3bd06520adfe41b69448cc033) The next overnight build failed with the above error. Aug 16, 2023 (77ed341f9fa24185a1540b2bd4f32e45c9f7c4cb)
I assume it was related to this change: e5ce4b6244360610be4512c961c7dc8976a50591