Replies: 3 comments
-
@ras0219-msft, @vicroms, could you please take a look? I'm not sure where the 2 commits come from? |
Beta Was this translation helpful? Give feedback.
-
Ah, @Thieum, so csvhelper is a custom port in your local, we don't have that port in vcpkg now, the error should expect for me. Could you follow https://github.com/microsoft/vcpkg/blob/master/docs/maintainers/registries.md#adding-a-new-version, and see if it works for you? |
Beta Was this translation helpful? Give feedback.
-
@PhoebeHui Yes, those are custom packages in a private registry. I managed to fix my error, following the answer I got in the mentioned discussion. And It works now. My issue is more of a feature request, regarding a minimal self-validation around the vcpkg-configuration.json file. In my case, I would have like a warning or an error regarding the fact that I had the same registry as default, and in the subsequent registries list. |
Beta Was this translation helpful? Give feedback.
-
When configuring my vcpkg-configuration.json this way:
I was able to search for a package, but not install it, without much explanation about why it would fail.
It would be helpful to have a warning or an error in case of misconfiguration.
Discussed in #18852
Originally posted by Thieum July 7, 2021
I certainly made a mistake during the process of adding a new package in my registry.
I am able to find the package, but I cannot install it.
There is the git-tree that works for the search:
But when installing, another git-tree is pulled, which is older and not working:
My vcpkg-configuration.json is written this way:
I would expect search and install to work the same way, at least to pull the resources. I wonder what I'm missing here?
Edit:
using --debug I found that the git commands were using two different commit ids to grab the files - the first one for baseline,json is the good one, the second one for versions is too old:
Where the second one comes from? What could be the source of this old commit id beside from vcpkg-configuration.json?
Edit:
I managed to bypass this issue by:
It still feels like a hack, and not really sustainable if I have to create new port for every packages everytime I create a new package.
Beta Was this translation helpful? Give feedback.
All reactions