-
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
Error message "printing with scope==virtual" after successfull package creation #5043
Comments
I've been trying different things but I'm not able to reproduce the error. It looks like you are calling I'll keep trying, but any hint will be really appreciated. Thanks! |
Hi @fourbft I have been checking the code too, and I can't see where this could happen. It would help to be able to reproduce it, if you don't want to post here private information, you could write to info@conan.io with further details. Thanks. |
Related: #4987 (comment) |
Hi all, |
Ok, another insight: |
Ok, could reproduce the bug with three trivial components (only conanfile.py files). (See attached tar.gz, untar, cd to conan_printing_with_scope_virtual_bug_demo and start build_CA_through_CC.sh script.) |
Thanks a lot for the example! There are a lot of tests, but no one like yours 😞. I've seen it is an issue related to build requires when they are involved in diamond dependency, it also depends on the order of those build requires... We'll try to fix it asap. Thanks again! |
Hi @memsharded just checked out your fix. Works, both for the example above and for our real world code. Problem solved! Thanks a lot! |
Closed by #5056 to be released at 1.14.5 |
If you detect this still fail in some situations please comment and we will reopen! thanks |
For some of our sources a "conan create . user/channel" gives the following error after successfull creation of the conan package:
...
This happens with Conan version 1.14.4. This error does not occur with Conan 1.13.1.
OS is Linux using Python 2.7.6.
As I said above, it does only occur with some (few) of our packages. Might be related to a specific (common?) upstream package, but not sure. Couldn't nail it down any further, yet, but maybe you have an idea.
The text was updated successfully, but these errors were encountered: