[question] Conan list not showing all builds available on artifactory (conan 2.0.7)

[robindegen]

What is your question?

Version: 2.0.7

I have various packages built on Artifactory for both linux and windows (4 profiles on windows, 2 on linux). However when i run:
conan list "zlib:*" --remote aleya-thirdparty-conan

I only see the 4 Windows profiles:

robindegen@Aleya:~$ conan list "zlib:*" --remote aleya-thirdparty-conan
aleya-thirdparty-conan
  zlib
    zlib/1.2.13
      revisions
        175fa43529ac965636f349db727444db (2023-06-28 08:36:20 UTC)
          packages
            daa3ab746b6b0fe8a2dcca3a3c31e8392c817a9a
              info
                settings
                  arch: x86_64
                  build_type: Debug
                  compiler: msvc
                  compiler.cppstd: 23
                  compiler.runtime: dynamic
                  compiler.runtime_type: Debug
                  compiler.version: 193
                  os: Windows
                options
                  shared: False
                python_requires
                  aleya-conan-base/1.0.Z
            03c994ad8866d90138e628a32428f7778e643119
              info
                settings
                  arch: x86
                  build_type: Release
                  compiler: msvc
                  compiler.cppstd: 23
                  compiler.runtime: dynamic
                  compiler.runtime_type: Release
                  compiler.version: 193
                  os: Windows
                options
                  shared: False
                python_requires
                  aleya-conan-base/1.0.Z
            72c17c9d31cfc6342c6a901592e70ca951b69939
              info
                settings
                  arch: x86
                  build_type: Debug
                  compiler: msvc
                  compiler.cppstd: 23
                  compiler.runtime: dynamic
                  compiler.runtime_type: Debug
                  compiler.version: 193
                  os: Windows
                options
                  shared: False
                python_requires
                  aleya-conan-base/1.0.Z
            d43fbd36c5ef1efa190ecefd8c69a52a03573340
              info
                settings
                  arch: x86_64
                  build_type: Release
                  compiler: msvc
                  compiler.cppstd: 23
                  compiler.runtime: dynamic
                  compiler.runtime_type: Release
                  compiler.version: 193
                  os: Windows
                options
                  shared: False
                python_requires
                  aleya-conan-base/1.0.Z

The same happens when I run this command on my linux machine. However I did deploy the linux binaries to artifactory. If I look there manually I do see them, just under a different hash:

The conan file is exactly the same. I did a full rebuild and redeploy of all packages on linux to be sure of this. Am I missing something? Is this intended behavior, or a bug?

The artifactory is public, in case you need this for additional info.
https://artifactory.aleya.dev/ui/repos/tree/General/aleya-thirdparty-conan

Repo with conanfiles and infra can be found here:
https://github.com/aleya-dev/devops/tree/master/Conan

[robindegen]

As a sidenote I also find the 1.0.Z a bit strange for aleya-conan-base/1.0.Z. I'm assuming that is because this package simply is versioned 1.0 and the Z is just appended? Would that cause any problems or is it intended behavior and should I always use a minimum of X.Y.Z version numbers?

[robindegen]

Update: I think this could be related to conanfile line endings? If I download the conan files from artifactory they look identical, however the conanmanifest mentions a different hash for each. Then there might be another issue. I would consider that a bug, since lineendings are typically handled automatically in git, so this would cause a lot of problems otherwise.

But either way I would expect "conan list" to still show all versions, and then just mention that they were built with a different conan file right?

[robindegen]

Update 2:
Using

conan list "zlib/1.2.13#*:*" --remote aleya-thirdparty-conan

Does give me all the packages, but that still doesn't really explain the different supposed package version/hash

[czoido]

Hi @robindegen,
Thanks for the question. Indeed it seems that the problem is related with the line endings, please check this section of the conan docs: https://docs.conan.io/2/knowledge/faq.html#error-obtaining-different-revisions-in-linux-and-windows
What's happening there is that you have two different recipe revisions because of that problem, and if you don't specify anything only the latest will be listed. Please check these docs and ping us back if you make it work.

[robindegen]

Thank you.

If you intend to keep that behavior, it should be more clearly documented. For example I would expect this to be clearly stated in the "Revisions" chapter. (https://docs.conan.io/2/tutorial/versioning/revisions.html?highlight=revisions)

[czoido]

Thank you @robindegen, for the feedback. I think adding a note in the revisions section would make this more visible, I'll transfer this to the docs repository.

[robindegen]

Perhaps it can be added to the "important" box, where it is explained how the hashes are generated

[czoido]

Closed by #3346