James

What you say is correct. But it doesn't invalidate what I explained above: - Having more than 1 package-revision for the same ``pkg/version#recipe_revision:package_id`` is a model/flow/process error, and should be...

Hi @grafikrobot, can you relate some of the changes in latest ``b2/5.2.0`` to that potential issue with ``GLIBCXX_3.4.29``?

Hi all, It seems this is working, with the new Conan versions, the new binaries, at least as reported by some users. Other reporters haven't provided sufficient details to reproduce,...

Hi @sastel Thanks for your question. I think the first error is expected: ``` $ conan build . -pr:h=../profiles/myboard-myconfig --build-require ``` The ``--build-require`` puts the current package being created as...

The ``test_package`` itself is always a pure consumer in the "host" context. As such, it will not define ``settings_target`` for itself, but that line with the ``match`` is in the...

Hi @sastel Any further feedback here? Is this still an issue? If it is, updating the code to reproduce the issue would help.

I am closing the ticket as staled, but please re-open, let us know or create a new ticket if you have updated feedback and code to reproduce the issue. Thanks...

Hi @mohamed-omara39 The ``requirements()`` method is evaluated to compute what will be the dependencies. But the dependencies are not there yet, they are typically in the server side, they haven't...

And visibility cannot simply be restricted by ``visible=False`` trait, that is just a declaration for Conan that some special logic is already implemented in the packages. The packages source code...

There is no such thing as the "options of a dependency of a recipe". You can have a recipe, like ``myapp/1.0`` that contains a ``requires("mylib/1.0")``. You can easily have 2,...