Skip to content
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

[feature] Conan 1.x & 2.x packages coexistence in the same remote #13588

Closed
1 task done
db4 opened this issue Apr 1, 2023 · 1 comment · Fixed by #13590
Closed
1 task done

[feature] Conan 1.x & 2.x packages coexistence in the same remote #13588

db4 opened this issue Apr 1, 2023 · 1 comment · Fixed by #13590
Assignees
Milestone

Comments

@db4
Copy link
Contributor

db4 commented Apr 1, 2023

What is your suggestion?

Uploading a Conan package without a channel (package/1.0@user) makes the whole repo completely unusable for Conan 1.x. E.g. conan search -r all * fails with

ERROR: Specify the 'user' and the 'channel' or neither of them. [Remote: conan-private]

It would be great if Conan 1.x just ignore packages that it cannot handle.

Have you read the CONTRIBUTING guide?

  • I've read the CONTRIBUTING guide
@memsharded
Copy link
Member

Fixed by #13590 for next 1.60

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants