You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using a python dependency (base class) in our conanfiles, which is located on a generic publicly available conan repo (conan-remote-a).
The package to be created will be uploaded to a different remote (conan-remote-b).
When trying to upload the build info, I will get an error '400' complaining that the properties for conan_base cannot be set currectly. Which is understandable as it searches (according to the error message) in the wrong remote (conan-remote-b).
Interestingly art:build_info create will always add the dependency of the python base class into the build info json file - even if I don't specify --with-dependencies. Maybe a bug there as well?
The text was updated successfully, but these errors were encountered:
Please note that I tried with and without --with-dependencies. Reading the source code it seems that --with-dependencies is supposed to disable dependency processing?
However I was not able to find any specific handling for a python_requires in the source code. However if I simply rename it to something like _python_requires it will no longer get included in the build_info.json
We are using a python dependency (base class) in our conanfiles, which is located on a generic publicly available conan repo (conan-remote-a).
The package to be created will be uploaded to a different remote (conan-remote-b).
When trying to upload the build info, I will get an error '400' complaining that the properties for
conan_base
cannot be set currectly. Which is understandable as it searches (according to the error message) in the wrong remote (conan-remote-b).Interestingly
art:build_info create
will always add the dependency of the python base class into the build info json file - even if I don't specify--with-dependencies
. Maybe a bug there as well?The text was updated successfully, but these errors were encountered: