[bug] unable to install openssl/3.2.1 recipe with conan version: 2.0.17

[chenyongquan2]

Describe the bug

Environment details

Operating System+version: windows 11
Compiler+version: msvc 2022
Conan version: 2.0.17
Python version: 3.12.1

Steps to reproduce

Just using xmake to configure my project
xmake f -p windows -a x64 -m debug --toolchain=msvc -vyD
And my xmake.lua require conan::openssl/3.1.2
package:add("deps", "conan::openssl/3.1.2", { configs = package:configs() })

Logs

======== Input profiles ========
Profile host:
[settings]
arch=x86_64
build_type=Release
compiler=msvc
compiler.cppstd=14
compiler.runtime=dynamic
compiler.runtime_type=Debug
compiler.version=193
os=Windows

Profile build:
[settings]
arch=x86_64
build_type=Release
compiler=msvc
compiler.cppstd=14
compiler.runtime=dynamic
compiler.runtime_type=Debug
compiler.version=193
os=Windows


======== Computing dependency graph ========
Graph root
    conanfile.txt: C:\workspace\saas-mt-opencloud\build\.conan\libcurl\8.4.0\conanfile.txt
Requirements
    libcurl/8.4.0#eb46919147288a8c34589793b184d0f2 - Cache
Resolved version ranges
    openssl/[>=1.1 <4]: openssl/3.2.1
*********************************************************
Recipe 'openssl/3.2.1' seems broken.
It is possible that this recipe is not Conan 2.0 ready
If the recipe comes from ConanCenter, report it at https://github.com/conan-io/conan-center-index/issues
If it is your recipe, check if it is updated to 2.0
*********************************************************

ERROR: Package 'openssl/3.2.1' not resolved: openssl/3.2.1: Cannot load recipe.
Error loading conanfile at 'C:\Users\cyq\.conan2\p\opens838c21f04ce59\e\conanfile.py': C:\Users\cyq\.conan2\p\opens838c21f04ce59\e\conanfile.py not found!.
error: @programdir\core\sandbox\modules\os.lua:378: execv(conan install . -g XmakeGenerator --profile:build=profile_build.txt --profile:host=profile_host.txt --build=missing) failed(1)
stack traceback:
    [C]: in function 'error'
    [@programdir\core\base\os.lua:957]:
    [@programdir\core\sandbox\modules\os.lua:378]:
    [@programdir\core\sandbox\modules\os.lua:291]: in function 'vrunv'
    [...dir\modules\package\manager\conan\v2\install_package.lua:331]:
    [...ramdir\modules\package\manager\conan\install_package.lua:41]:
    [@programdir\modules\package\manager\install_package.lua:111]:
    [@programdir\core\package\package.lua:2765]: in function 'script'
    [...dir\modules\private\action\require\impl\utils\filter.lua:114]: in function 'call'
    [...\modules\private\action\require\impl\actions\install.lua:342]:

  => install conan::libcurl/8.4.0 latest .. failed
error: @programdir\core\main.lua:306: @programdir\modules\async\runjobs.lua:320: ...\modules\private\action\require\impl\actions\install.lua:474: install failed!
stack traceback:
    [C]: in function 'error'
    [@programdir\core\base\os.lua:957]:
    [...\modules\private\action\require\impl\actions\install.lua:474]: in function 'catch'
    [@programdir\core\sandbox\modules\try.lua:123]: in function 'try'
    [...\modules\private\action\require\impl\actions\install.lua:333]:
    [...modules\private\action\require\impl\install_packages.lua:479]: in function 'jobfunc'
    [@programdir\modules\async\runjobs.lua:237]:

stack traceback:
        [C]: in function 'error'
        @programdir\core\base\os.lua:957: in function 'os.raiselevel'
        (...tail calls...)
        @programdir\core\main.lua:306: in upvalue 'cotask'
        @programdir\core\base\scheduler.lua:404: in function <@programdir\core\base\scheduler.lua:397>

How to reproduce it

No response

[memsharded]

Hi @chenyongquan2

Thanks for your question.

I am not sure this is a Conan bug, this could be like something is not correctly configured.
The first step would be to isolate Conan, and try to reproduce with bare Conan commands.
It seems that the Conan remote is not configured, so please try checking:

$ conan remote list
$ conan list openssl/* -r=conancenter
$ conan install . --profile:build=profile_build.txt --profile:host=profile_host.txt --build=missing

And report the result.

Then, there are a couple of details, for example in general you don't want to use build_type=Debug for the "build" profile and context, but build_type=Release. You might want to report that to xmake repos.

[memsharded]

Hi @chenyongquan2

Any feedback here? Did you manage to try the above?

[chenyongquan2]

Hi  你好@chenyongquan2

Any feedback here? Did you manage to try the above?有什么反馈意见吗？您尝试过上述方法吗？

@memsharded
Thank you very much for your reply.

C:\Users\cyq>conan remote list
conancenter: https://center.conan.io [Verify SSL: True, Enabled: True]

C:\Users\cyq>conan list openssl/* -r=conancenter
conancenter
  openssl
    openssl/1.0.2s
    openssl/1.0.2t
    openssl/1.0.2u
    openssl/1.1.0k
    openssl/1.1.0l
    openssl/1.1.1c
    openssl/1.1.1d
    openssl/1.1.1e
    openssl/1.1.1f
    openssl/1.1.1g
    openssl/1.1.1h
    openssl/1.1.1i
    openssl/1.1.1j
    openssl/1.1.1k
    openssl/1.1.1l
    openssl/1.1.1m
    openssl/1.1.1n
    openssl/1.1.1o
    openssl/1.1.1p
    openssl/1.1.1q
    openssl/1.1.1s
    openssl/1.1.1t
    openssl/1.1.1u
    openssl/1.1.1v
    openssl/1.1.1w
    openssl/3.0.0
    openssl/3.0.1
    openssl/3.0.2
    openssl/3.0.3
    openssl/3.0.4
    openssl/3.0.5
    openssl/3.0.7
    openssl/3.0.8
    openssl/3.0.9
    openssl/3.0.10
    openssl/3.0.11
    openssl/3.0.12
    openssl/3.0.13
    openssl/3.1.0
    openssl/3.1.1
    openssl/3.1.2
    openssl/3.1.3
    openssl/3.1.4
    openssl/3.1.5
    openssl/3.2.0
    openssl/3.2.1

C:\Users\cyq>conan install . --profile:build=profile_build.txt --profile:host=profile_host.txt --build=missing
ERROR: Conanfile not found at C:\Users\cyq\conanfile.txt

[memsharded]

You should have a conanfile.txt, somewhere, like in your output above is: conanfile.txt: C:\workspace\saas-mt-opencloud\build\.conan\libcurl\8.4.0\conanfile.txt

You can try with conan install --requires=openssl/3.2.1 instead.

This doesn't seem a Conan issue so far, but an xmake one. I would recommend to open a ticket in the xmake repos, they might be able to help better.