Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Impossible to install successfully new ports after a custom port has been installed strikes back #15836

Closed
traversaro opened this issue Jan 23, 2021 · 6 comments · Fixed by microsoft/vcpkg-tool#516 or #25226
Closed

Impossible to install successfully new ports after a custom port has been installed strikes back #15836

traversaro opened this issue Jan 23, 2021 · 6 comments · Fixed by microsoft/vcpkg-tool#516 or #25226
Assignees
@ras0219-msft @JackBoosY
Labels
category:vcpkg-bug The issue is with the vcpkg system (including helper scripts in `scripts/cmake/`) requires:tool-release An issue that has been fixed in the microsoft/vcpkg-tool repo and is waiting for a release thereof

Comments

@traversaro
Copy link
Contributor

traversaro commented Jan 23, 2021 •
edited
Loading

Describe the bug
With the current master branch since the PR has been merged #15709 the use of custom ports at some point prevents to install any further non-custom port from vcpkg.

Environment

  • OS: Windows
  • Compiler: VS2019

To Reproduce

git clone https://github.com/microsoft/vcpkg  C:/vcpkg
git clone https://github.com/robotology/robotology-vcpkg-binary-ports C:/robotology-vcpkg-binary-ports
C:/vcpkg/bootstrap-vcpkg.sh
C:/vcpkg/vcpkg.exe --overlay-ports=C:/robotology-vcpkg-binary-ports install --triplet x64-windows ipopt-binary
C:/vcpkg/vcpkg.exe  install --triplet x64-windows asio

The last command will fail with the following error:

Computing installation plan...
Error: while loading  ipopt-binary:
The port directory (C:\vcpkg\ports\ipopt-binary) does not exist
Error: failed to load port from C:\vcpkg\ports\ipopt-binary
Note: Updating vcpkg by rerunning bootstrap-vcpkg may resolve this failure.

Expected behavior
The asio port should be installed correctly, even if the custom port ipopt-binary had been installed before.

Failure logs
See robotology/robotology-vcpkg-ports#18 for more details and the bisection that lead to identify the PR #15709 . This is a regression that re-created the already existing issue #10119 .
@traversaro traversaro mentioned this issue Jan 23, 2021
Closed
@JackBoosY JackBoosY added the category:vcpkg-bug The issue is with the vcpkg system (including helper scripts in `scripts/cmake/`) label Jan 25, 2021
@viromer viromer mentioned this issue Jan 26, 2021
Closed
@traversaro traversaro mentioned this issue Mar 29, 2021
Closed
@traversaro traversaro mentioned this issue Jul 26, 2021
Merged
@glindsey
Copy link

glindsey commented Sep 7, 2021

I am running into the same issue when attempting to update Boost. I'm getting the following error message:
Error: while loading boost-disjoint-sets: The port directory (D:\personal\projects\vcpkg\ports\boost-disjoint-sets) does not exist Error: failed to load port from D:\personal\projects\vcpkg\ports\boost-disjoint-sets Note: Updating vcpkg by rerunning bootstrap-vcpkg may resolve this failure.

(Re-running bootstrap-vcpkg does not help.)

@JackBoosY
Copy link
Contributor

@glindsey Although this is a vcpkg bug, I prefer you to use the manifest mode to avoid this temporary.

@wrobelda
Copy link
Contributor

Personally, this is the biggest annoyance right now when working with vcpkg and actively developing ports while often switching branches.

@niyue
Copy link
Contributor

niyue commented Oct 16, 2021

Is it possible for us to remove the cached custom port location so that vcpkg stops reporting such an error?

@traversaro traversaro mentioned this issue Oct 26, 2021
Closed
This was referenced Apr 22, 2022
Closed
Merged
@JackBoosY
Copy link
Contributor

Requires next release.

@JackBoosY JackBoosY reopened this May 24, 2022
@JackBoosY JackBoosY added the requires:tool-release An issue that has been fixed in the microsoft/vcpkg-tool repo and is waiting for a release thereof label May 24, 2022
@BillyONeal BillyONeal mentioned this issue Jun 15, 2022
Merged
BillyONeal added a commit that referenced this issue Jun 15, 2022
@BillyONeal
Update vcpkg-tool to 2022-06-15 (#25226)
0abb2b2 
* Update vcpkg-tool to 2022-06-15. See https://github.com/microsoft/vcpkg-tool/releases/tag/2022-06-15
* Add `=pass` entries from microsoft/vcpkg-tool#579
* Cherry pick XUnit output from #23477 which hooks up microsoft/vcpkg-tool#585 (Thanks again @dg0yt !)
* Update release process document now that we can do the full tree rebuild to test the tool release before signing.

Thank you:

@autoantwort 
@christophe-calmejane 
@JackBoosY 
@benmcmorran
@hmoffatt 
@klalumiere 
@Thomas1664 
@Neumann-A 
@AenBleidd

for your contributions!

Fixes #22686 .
Fixes #21800 .
Fixes #16216 .
Fixes #15836 .

Full tree rebuild testing this update is: https://dev.azure.com/vcpkg/public/_build/results?buildId=73664&view=results
@traversaro traversaro mentioned this issue Jun 17, 2022
Closed
@traversaro
Copy link
Contributor Author

Thanks a lot @BillyONeal @ras0219-msft @JackBoosY !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ras0219-msft ras0219-msft

@JackBoosY JackBoosY

Labels
category:vcpkg-bug The issue is with the vcpkg system (including helper scripts in `scripts/cmake/`) requires:tool-release An issue that has been fixed in the microsoft/vcpkg-tool repo and is waiting for a release thereof
Projects
None yet
Milestone
No milestone
6 participants
@niyue @glindsey @wrobelda @traversaro @ras0219-msft @JackBoosY