[bug] Alias resolution bug when mixing fix-version and alias

[Doome161]

conan_mix_fix_versions_with_alias.zip

The bug occurs when using fixed versions and aliases in a dependency tree. The order of the requirements in the conanfiles plays a decisive role. If, for example, the requires are swapped in component CD, everything runs through successfully. It seems that this issue is related to #2576 which is already marked as fixed.

I have tested various conan versions and was able to reproduce the bug: 1.19, 1.22, 1.26, 1.35 and 1.36.

Environment Details (include every applicable attribute)

• Operating System+version: Linux
• Compiler+version: gcc+7
• Conan version: 1.35.0
• Python version: 3.6.5

Steps to reproduce (Include if Applicable)

To reproduce the bug I have attached a zipfile. Just run the build.sh and the bug will appear.
The script executes a conan create . user/test for each component and then creates an alias via conan alias ....

Logs (Executed commands with output) (Include/Attach if Applicable)

WARN: CB/1.0.0@user/test: requirement CA/1.0.0@user/test overridden by CC/1.0.0@user/test to CA/RELEASE@user/test 
ERROR: CB/1.0.0@user/test: Incompatible requirements obtained in different evaluations of 'requirements'
    Previous requirements: [CA/1.0.0@user/test]
    New requirements: [CA/RELEASE@user/test]

[monsdar]

We also get many of these warnings: WARN: geotiff/1.6.0@thirdparty/release: requirement libtiff/4.1.0@thirdparty/release overridden by gdal/3.1.2 to libtiff/LATEST@thirdparty/release where the LATEST-alias points to the exact same version that is required (LATEST == 4.1.0).

Seems that the timepoint where alias-resolution happens is not correct.

[memsharded]

#9217 implemented new alias syntax that would resolve this issue, in 1.39.
Thanks for reporting this, let us know how it works!