-
Notifications
You must be signed in to change notification settings - Fork 354
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
can't repo sync #27
Comments
Hey nevion, The reason we use ssh by default is to avoid numerous password prompts when cloning multiple repositories. Github users without commit access should be able to clone without issue. But non-GitHub users are left out in the dust if they want to repo sync. I can understand your desire for performing an anonymous http clone. I'll add this to my todo list. If you need this urgently, we'll gladly accept a pull request that adds a secondary manifest that uses anonymous http. |
I hacked the repo manifest remote urls to this:
And it mostly successfully clone'd the repos, although I got some curl 404 errors along the way (I don't know what for yet), such as curl: (22) The requested URL returned error: 404 Not Found I'm not sure how to switch manifest files without ln -s'ing another file in or overwriting manifest.xml, or if this is the best way for ROCm, but it seems to have worked. I'll update if I get build errors from it. |
The cur: (22) error codes are a well known curl defect, and have nothing to do with the repositories. |
The repo configuration is set to use ssh, which makes it unusable for people for people who are not github users (at the least) and I believe github users who don't have commit access (like myself).
Perhaps I missed something that lets ssh cloning work in these cases?
ps. Please support and build binaries for OpenSUSE!
The text was updated successfully, but these errors were encountered: