-
Notifications
You must be signed in to change notification settings - Fork 993
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
[bug] build order produces not buildable build arguments in specific override scenario #16116
Comments
Hi @nicosmd Thanks very much for reporting this. I haven't dropped this, this is indeed a bug, but it is proving a very challenging it. I have been working on this since then, and I'll try to fix it for next 2.3 |
Hey @memsharded, thank you for the update and for working on this. If there is anything I can do to support you on this, please let me know! |
Update: this is the ticket that I have been investing more time in a long time 😅 It happened to be quite complicated, I had to try many different approaches, failed in all of them. Finally a relatively easy solution seems workable in #16235, I am proposing it for next patch 2.3.1 release. I'll probably add a few more tests, but in case you want to give it a try and run from source for your project and see how it goes. |
Hey @memsharded , I have just tested the solution with the repository I have created and it works without any issues! |
Excellent, thanks for the feedback! |
Maybe I have found a regression but I'm not sure yet. In production I am using [replace_requires] to override some dependencies to be found in a sysroot. Using the bugfix branch I'm getting the error 2.3.0:
fix branch: "overrides": {
...
"openssl/1.1.1s": [
"openssl/1.1.1t#1fd1eb221ddba2f48d5abf4d9a50058e",
null
]
... I would need some time to reproduce and create a minimal demo for the issue if needed. Do you have any idea what could went wrong? |
No idea, I am trying to reproduce, adding further tests like 70e58cf, but so far I haven't manage to make it fail. |
I have managed to find a small issue that seems related to your case, and did a fix in bdb8bd0, including a very large test. If you can update the code and try again, please let me know. |
Hey @memsharded thank you very much! The issue disappeared now :) |
Closed by #16235 to be released in 2.3.1 very soon |
Describe the bug
Hi!
I'm using conan 2.2.2 and I'm currently having an issue with the output of
conan graph build-order
in a specific override scenario. The issue appears as soon as I try to build packages using the build order output. I have created a repository to demonstrate and reproduce the issue: https://github.com/nicosmd/conan2-build-order-override-failedPlease let me know if you need further information.
Thank you very much!
How to reproduce it
clone https://github.com/nicosmd/conan2-build-order-override-failed and run
build.sh
The text was updated successfully, but these errors were encountered: