like: from conans import ConanFile class Pkg(ConanFile): python_requires ="tool/[>=0.0]" build_requires ="tool/[>=0.0]" By using this mechanism, tool dependency will always be used (the recipe will be possible changes (note that the recipe in pkgb/conanfile.py contains a require like requires = "pkga/[>0.0]@user/testing"). $ cd pkgb $ conan lock create conanfile.py --user=user --channel=testing --lockfile-out=locks/pkgb_ version libb/1.1@user/testing is created. But if we check the libd conanfile.py requirement libb/[>0.0 <1.0]@user/testing, we can see that this 1.1 version falls outside of the valid version range. Then

like: from conans import ConanFile class Pkg(ConanFile): python_requires ="tool/[>=0.0]" tool_requires ="tool/[>=0.0]" By using this mechanism, tool dependency will always be used (the recipe will be possible changes (note that the recipe in pkgb/conanfile.py contains a require like requires = "pkga/[>0.0]@user/testing"). $ cd pkgb $ conan lock create conanfile.py --user=user --channel=testing --lockfile-out=locks/pkgb_ version libb/1.1@user/testing is created. But if we check the libd conanfile.py requirement libb/[>0.0 <1.0]@user/testing, we can see that this 1.1 version falls outside of the valid version range. Then

like: from conans import ConanFile class Pkg(ConanFile): python_requires ="tool/[>=0.0]" tool_requires ="tool/[>=0.0]" By using this mechanism, tool dependency will always be used (the recipe will be possible changes (note that the recipe in pkgb/conanfile.py contains a require like requires = "pkga/[>0.0]@user/testing"). $ cd pkgb $ conan lock create conanfile.py --user=user --channel=testing --lockfile-out=locks/pkgb_ version libb/1.1@user/testing is created. But if we check the libd conanfile.py requirement libb/[>0.0 <1.0]@user/testing, we can see that this 1.1 version falls outside of the valid version range. Then

like: from conans import ConanFile class Pkg(ConanFile): python_requires ="tool/[>=0.0]" tool_requires ="tool/[>=0.0]" By using this mechanism, tool dependency will always be used (the recipe will be possible changes (note that the recipe in pkgb/conanfile.py contains a require like requires = "pkga/[>0.0]@user/testing"). $ cd pkgb $ conan lock create conanfile.py --user=user --channel=testing --lockfile-out=locks/pkgb_ version libb/1.1@user/testing is created. But if we check the libd conanfile.py requirement libb/[>0.0 <1.0]@user/testing, we can see that this 1.1 version falls outside of the valid version range. Then

like: from conans import ConanFile class Pkg(ConanFile): python_requires ="tool/[>=0.0]" tool_requires ="tool/[>=0.0]" By using this mechanism, tool dependency will always be used (the recipe will be possible changes (note that the recipe in pkgb/conanfile.py contains a require like requires = "pkga/[>0.0]@user/testing"). $ cd pkgb $ conan lock create conanfile.py --user=user --channel=testing --lockfile-out=locks/pkgb_ version libb/1.1@user/testing is created. But if we check the libd conanfile.py requirement libb/[>0.0 <1.0]@user/testing, we can see that this 1.1 version falls outside of the valid version range. Then

like: from conans import ConanFile class Pkg(ConanFile): python_requires ="tool/[>=0.0]" tool_requires ="tool/[>=0.0]" By using this mechanism, tool dependency will always be used (the recipe will be possible changes (note that the recipe in pkgb/conanfile.py contains a require like requires = "pkga/[>0.0]@user/testing"). $ cd pkgb $ conan lock create conanfile.py --user=user --channel=testing --lockfile-out=locks/pkgb_ version libb/1.1@user/testing is created. But if we check the libd conanfile.py requirement libb/[>0.0 <1.0]@user/testing, we can see that this 1.1 version falls outside of the valid version range. Then

like: from conans import ConanFile class Pkg(ConanFile): python_requires ="tool/[>=0.0]" tool_requires ="tool/[>=0.0]" By using this mechanism, tool dependency will always be used (the recipe will be possible changes (note that the recipe in pkgb/conanfile.py contains a require like requires = "pkga/[>0.0]@user/testing"). $ cd pkgb $ conan lock create conanfile.py --user=user --channel=testing --lockfile-out=locks/pkgb_ version libb/1.1@user/testing is created. But if we check the libd conanfile.py requirement libb/[>0.0 <1.0]@user/testing, we can see that this 1.1 version falls outside of the valid version range. Then

like: from conans import ConanFile class Pkg(ConanFile): python_requires ="tool/[>=0.0]" tool_requires ="tool/[>=0.0]" By using this mechanism, tool dependency will always be used (the recipe will be possible changes (note that the recipe in pkgb/conanfile.py contains a require like requires = "pkga/[>0.0]@user/testing"). $ cd pkgb $ conan lock create conanfile.py --user=user --channel=testing --lockfile-out=locks/pkgb_ version libb/1.1@user/testing is created. But if we check the libd conanfile.py requirement libb/[>0.0 <1.0]@user/testing, we can see that this 1.1 version falls outside of the valid version range. Then

like: from conans import ConanFile class Pkg(ConanFile): python_requires ="tool/[>=0.0]" tool_requires ="tool/[>=0.0]" By using this mechanism, tool dependency will always be used (the recipe will be possible changes (note that the recipe in pkgb/conanfile.py contains a require like requires = "pkga/[>0.0]@user/testing"). $ cd pkgb $ conan lock create conanfile.py --user=user --channel=testing --lockfile-out=locks/pkgb_ version libb/1.1@user/testing is created. But if we check the libd conanfile.py requirement libb/[>0.0 <1.0]@user/testing, we can see that this 1.1 version falls outside of the valid version range. Then

like: from conans import ConanFile class Pkg(ConanFile): python_requires ="tool/[>=0.0]" tool_requires ="tool/[>=0.0]" By using this mechanism, tool dependency will always be used (the recipe will be possible changes (note that the recipe in pkgb/conanfile.py contains a require like requires = "pkga/[>0.0]@user/testing"). $ cd pkgb $ conan lock create conanfile.py --user=user --channel=testing --lockfile-out=locks/pkgb_ version libb/1.1@user/testing is created. But if we check the libd conanfile.py requirement libb/[>0.0 <1.0]@user/testing, we can see that this 1.1 version falls outside of the valid version range. Then