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

can't repo sync #27

Closed
nevion opened this issue Aug 31, 2016 · 3 comments
Closed

can't repo sync #27

nevion opened this issue Aug 31, 2016 · 3 comments

Comments

@nevion
Copy link

nevion commented Aug 31, 2016

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!

@ghost
Copy link

ghost commented Aug 31, 2016

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.

@nevion
Copy link
Author

nevion commented Aug 31, 2016

I hacked the repo manifest remote urls to this:

remote name="roc-github"
        fetch="https://github.com/RadeonOpenCompute/" />
<remote name="pctools-github"
         fetch="https://github.com/GPUOpen-ProfessionalCompute-Tools/" />

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
Server does not provide clone.bundle; ignoring.

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.

@jedwards-AMD
Copy link
Contributor

The cur: (22) error codes are a well known curl defect, and have nothing to do with the repositories.

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

No branches or pull requests

2 participants