[bug] Conan downloads the wrong hash from JFrog artifactory

[3pol]

Describe the bug

Bug:

Environment: AWS t4g.xlarge VM
OS: ubuntu 20.04
Conan version: 2.2.2
Profile:

Profile host:
[settings]
arch=armv8
build_type=Debug
compiler=gcc
compiler.cppstd=gnu17
compiler.libcxx=libstdc++11
compiler.version=10
os=Linux
[options]
coverage=True
protobuf/*:debug_suffix=False
[conf]
tools.cmake.cmaketoolchain:generator=Ninja
tools.cmake.cmaketoolchain:user_toolchain=['/home/ubuntu/workspace/link_monitor_aarch64_PR-2/build/../toolchain/aarch64.cmake']

Description:

When I attempt to install a repo that I have with conan.
It fails when trying to build a dependency of said repo, due to the wrong package hash (and sources by proxy) being downloaded from JFrog.

In my JFrog, I have a package that matches this profile that I need, but for some reason that's beyond me - it tries to download another package hash for x86_64.
Then, when the dependecy package attempts to build (due to—-build missing), it fails because the sources are wrong.

I already had that issue with other repos a while ago.
other than deleting the package hash, I didn't find any other solution.
How does conan decides which package hash to download from JFrog? because it seems like the last one always gets picked.

How to reproduce it

Not sure how, since it's private repos.
I can provide logs and check whatever is necessary.

[memsharded]

Hi @3pol

Thanks for your question.

The first thing I'd recommend is try to update to latest Conan 2.X.

Then, providing logs will help. It would be useful:

• The existing packages in the server or cache, with conan list "mypkg/myversion:*"
• The full command and output of the failing conan install command that would print a missing binary error
• Following the error message of the conan install command, you can run a conan graph explain command that will tell the differences between the requested package and the existing packages, please provide that output too.