conan-center-index: [bug] Version resolution seems broken: Version range is ignored

Describe the bug

Environment: Linux (Arch), gcc 14.2.1, conan 2.12.1. Profile (was auto-detected, clean home via CONAN_HOME to start on a clean slate):

[settings]
arch=x86_64
build_type=Release
compiler=gcc
compiler.cppstd=gnu20
compiler.libcxx=libstdc++11
compiler.version=14
os=Linux

Build command (ffmpeg I often deactivate as it increases the build time massively, doesn’t matter for this problem):

conan create 3.x --version=3.0.3.1 --build=missing -o:a '&:with_ffmpeg=False' --update

In the recipes/openimageio folder of my branch for OpenImageIO 3.0: https://github.com/conan-io/conan-center-index/pull/25672

I just also tried it with locally setting self.requires("libdeflate/1.22", override=True) into the requires which allows to solve the graph.

The problem

ERROR: Version conflict: Conflict between libdeflate/1.19 and libdeflate/1.22 in the graph.
Conflict originates from openexr/3.2.3

Run 'conan graph info ... --format=html > graph.html' and open 'graph.html' to inspect the conflict graphically.

The graph shows openexr depending on libdeflate/1.19 still. Which I don’t understand, as the recipe in the current master is using a version range (self.requires("libdeflate/[>=1.19 <=1.22]") since my MR https://github.com/conan-io/conan-center-index/pull/26364). Also with --build='*' or --build=openexr it still fails to resolve. Am I missing something or is there maybe a bug in dependency graph resolution?

How to reproduce it

Run build command or corresponding graph commands in the recipes/openimageio folder of my branch for OpenImageIO 3.0: https://github.com/conan-io/conan-center-index/pull/2567:

conan create 3.x --version=3.0.3.1 --build=missing --update

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (15 by maintainers)

Most upvoted comments

Additional feedback: https://github.com/conan-io/conan-center-index/pull/26520 solved the graph issue.

Also, guess I can close this. Although I have to say - as much as I love Conan - that the version management is rather dificult. For my local index, I have a list of dependencies with quite a number of force/override to ensure I get current versions. Works quite well so not too much to complain but managing the recipes in the center is rather difficult for larger packages with cross-dependencies. And due to the rule “please don’t do much version bumps for deps” I try to stay away from those for my MRs in general.