question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[question] How do you install packages from the new conan center remote?

See original GitHub issue

I am trying to install the boost/1.72.0 package from the new conan center remote (https://conan.io/center/).

My current remotes are:

conan-center: https://conan.bintray.com [Verify SSL: True]
conan-community: https://api.bintray.com/conan/conan-community/conan [Verify SSL: True]
bincrafters: https://api.bintray.com/conan/bincrafters/public-conan [Verify SSL: True]

The conan install command I am using is:

conan install boost/1.72.0@conan/stable

The current output is:

conan install boost/1.72.0@conan/stable
Configuration:
[settings]
arch=x86_64
arch_build=x86_64
build_type=Release
compiler=gcc
compiler.libcxx=libstdc++11
compiler.version=9
os=Linux
os_build=Linux
[options]
[build_requires]
[env]

boost/1.72.0@conan/stable: Not found in local cache, looking in remotes...
boost/1.72.0@conan/stable: Trying with 'conan-center'...
boost/1.72.0@conan/stable: Trying with 'conan-community'...
boost/1.72.0@conan/stable: Trying with 'bincrafters'...
ERROR: Unable to find 'boost/1.72.0@conan/stable' in remotes

I did not see anything in the documentation about the new conan center changing it’s remote URL. Is there a new URL or is the new conan center not yet available to the public?

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

4reactions
Croydoncommented, Feb 6, 2020

No, the remote is the same for conan-center

You need to remove the @user/channel

Instead of boost/1.72.0@conan/stable it is boost/1.72.0 for conanfiles

Or in the command it is conan install boost/1.72.0@

PS: @ericLemanissier was faster PSS: the @conan/stable ending is for packages originating from conan-community

3reactions
Croydoncommented, Feb 6, 2020

Adding just the @ is just for CLI commands. If you have a conanfile.py or conanfile.txt you don’t need the @ for recipe references

The reason is backwards compatibility for existing CLI calls. A command like conan create . bincrafters/stable interprets the last argument as user/branch, while calls with @ like conan create . boost/1.72.0@ are interpreted as recipe/version

Read more comments on GitHub >

github_iconTop Results From Across the Web

Remotes — conan 1.56.0 documentation
Conan packages can be uploaded to different remotes previously configured with a name and a URL. The remotes are just servers used as...
Read more >
0 - Stack Overflow
It is very possible to build the packages you want from source in your infra, cloning the github.com/conan-io/conan-center-index repo and doing ...
Read more >
Conan packages in the Package Registry - GitLab Docs
To run conan commands, you must add the Package Registry as a Conan remote for your project or instance. Then you can publish...
Read more >
Conan Repositories - JFrog - JFrog Documentation
In the New Repository dialog, set the Package Type to Conan, set the Repository Key value, and specify the URL to the remote...
Read more >
Barbarian, an open and distributed Conan package index!
Simply set CPM_USE_LOCAL_PACKAGES or CPM_LOCAL_PACKAGES_ONLY and it'll switch over to find_package . · Configure on a machine that has network ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found