Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[question] How to use--require-override? #10010

Closed
1 task done
madebr opened this issue Nov 13, 2021 · 2 comments · Fixed by #10013
Closed
1 task done

[question] How to use--require-override? #10010

madebr opened this issue Nov 13, 2021 · 2 comments · Fixed by #10013
Assignees
Milestone

Comments

@madebr
Copy link
Contributor

madebr commented Nov 13, 2021

Conan 1.39.0 added the --require-override argument.
How can I use it?

Let's create the following conanfile.txt:

[requires]
cubicinterpolation/0.1.4

Current cubicinterpolation has a dependency on boost/1.75.0.
Executing the following command does not bump the version of boost.
It remains at 1.75.0.

conan install .. --require-override=boost/1.77.0

It's unclear to me whether this is a bug or whether I use this command wrongly?

I used the same syntax as tested by this commit: ae7732b
Also, the test only tests conanfile.py recipes, no conanfile.txt recipes.

UPDATE:
It works when I convert conanfile.txt to conanfile.py.
So imho this is a bug: conanfile.txt has a different behavior then conanfile.py.

Tested with conan 1.40.4

@franramirez688
Copy link
Contributor

Hi @madebr

Yes, it looks like a bug. It's behaving differently between each mode.

franramirez688 added a commit to franramirez688/conan that referenced this issue Nov 15, 2021
@franramirez688 franramirez688 added this to the 1.43 milestone Nov 15, 2021
franramirez688 added a commit to franramirez688/conan that referenced this issue Nov 15, 2021
memsharded pushed a commit that referenced this issue Nov 15, 2021
…t` (#10013)

* Added test to reproduce issue #10010

* Fixed bug override_requires when using conanfile.txt
@memsharded
Copy link
Member

#10013 fixed this, will be in 1.43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants