[boost-uuid] Download failure

[anubhavg64]

Operating system

Windows 11

Compiler

No response

Steps to reproduce the behavior

vcpkg install boost-uuid boost-uuid:x64-windows-static

Failure logs

-- Downloading https://github.com/boostorg/core/archive/boost-1.85.0.tar.gz -> boostorg-core-boost-1.85.0.tar.gz... [DEBUG] To include the environment variables in debug output, pass --debug-env [DEBUG] Disabling metrics because vcpkg.disable-metrics exists [DEBUG] Trying to load bundleconfig from C:\Users\Anubhav Gupta\vcpkg\vcpkg-bundle.json [DEBUG] Failed to open: C:\Users\Anubhav Gupta\vcpkg\vcpkg-bundle.json [DEBUG] Bundle config: readonly=false, usegitregistry=false, embeddedsha=nullopt, deployment=Git, vsversion=nullopt [DEBUG] Feature flag 'binarycaching' unset [DEBUG] Feature flag 'compilertracking' unset [DEBUG] Feature flag 'registries' unset [DEBUG] Feature flag 'versions' unset [DEBUG] Feature flag 'dependencygraph' unset Downloading https://github.com/boostorg/core/archive/boost-1.85.0.tar.gz [DEBUG] Trying to hash C:\Users\Anubhav Gupta\vcpkg\downloads\boostorg-core-boost-1.85.0.tar.gz.48784.part [DEBUG] C:\Users\Anubhav Gupta\vcpkg\downloads\boostorg-core-boost-1.85.0.tar.gz.48784.part has hash a1e774c98b537dd42018742af68f5889af1afd4e6c9809399987124e56a3b9ae2f20e8173170bc6fc0ad76fb95e2da7b9d385a4037e9ee12011fc02bf8f7e009 error: Failed to download from mirror set error: File does not have the expected hash: url: https://github.com/boostorg/core/archive/boost-1.85.0.tar.gz File: C:\Users\Anubhav Gupta\vcpkg\downloads\boostorg-core-boost-1.85.0.tar.gz.48784.part Expected hash: 3a7be75e52f5c20830fccb9e7391a1e4556ebb072e6324df95b1ba38bed46e24f4c9f27a62a1099eddc90f2ac1ede083f0c850e2dc27fd42375d028516f675b3 Actual hash: a1e774c98b537dd42018742af68f5889af1afd4e6c9809399987124e56a3b9ae2f20e8173170bc6fc0ad76fb95e2da7b9d385a4037e9ee12011fc02bf8f7e009 [DEBUG] D:\a_work\1\s\src\vcpkg\base\downloads.cpp(997): [DEBUG] Time in subprocesses: 0us [DEBUG] Time in parsing JSON: 6us [DEBUG] Time in JSON reader: 0us [DEBUG] Time in filesystem: 122us [DEBUG] Time in loading ports: 0us [DEBUG] Exiting after 941 ms (941317us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):

  Failed to download file with error: 1
  If you are using a proxy, please check your proxy setting. Possible causes are:

  1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
     to `https://address:port`. This is not correct, because `https://` prefix
     claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
     , etc..) is an HTTP proxy. Try setting `http://address:port` to both
     HTTP_PROXY and HTTPS_PROXY instead.

  2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings
     set by your proxy software. See https://github.com/microsoft/vcpkg-tool/pull/77
     The value set by your proxy might be wrong, or have same `https://` prefix issue.

  3. Your proxy's remote server is out of service.

  If you've tried directly download the link, and believe this is not a temporary
  download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
  to report this upstream download server failure.

Call Stack (most recent call first): scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail) scripts/cmake/vcpkg_from_github.cmake:106 (vcpkg_download_distfile) C:/Users/Anubhav Gupta/AppData/Local/vcpkg/registries/git-trees/195375664be82cbc16178de90096e451de070d80/portfile.cmake:3 (vcpkg_from_github) scripts/ports.cmake:191 (include)

Additional context

No response

[Neumann-A]

That is fallout of boost retagging releases. Please use a newer baseline... the hash already has been fixed.

[anubhavg64]

Hi @Neumann-A , Can you elaborate more on this, how to fix this? How to use the newer baseline?

[Neumann-A]

Just use a later commit of vcpkg than what you are currently using

[github-actions[bot]]

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.