| Summary: | git fetcher does not support non git url format based requests | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | claude | ||||
| Component: | bitbake | Assignee: | Richard Purdie <richard.purdie> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | poky.bs.watcher, poky.watcher | ||||
| Version: | 2.2 | ||||||
| Target Milestone: | 2.1 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | Don't know | |||||
| Attachments: |
|
||||||
|
Description
claude
2015-12-31 15:49:38 UTC
I don't like the idea of a "none" type, not sure that makes sense since it really is using the ssh backend. Two different syntaxes for the same thing is bad.
It appears its actually the bitbucket server which can't cope with this (which is why there is a mention of conq in the error message).
Your patch happens to work by having the ":" in the SRC_URI when combined with the protocol=none parameter which is also a bit ugly.
I'm wondering if a better solution is simple to modify _get_repo_url like this:
username = ""
+ if ud.proto == "ssh":
+ # Some servers, e.g. bitbucket.org can't cope with ssh://
+ # and removing that means we need a : before path.
+ return "%s%s:%s" % (username, ud.host, ud.path)
return "%s://%s%s%s" % (ud.proto, username, ud.host, ud.path)
which then change all ssh urls to use the other syntax. This is more in line with what people use from the commandline.
I would maintain that its the bitbucket server which is broken here mind since git does usually accept this syntax, e.g.:
$ git ls-remote ssh://git@git.yoctoproject.org/psplash
88343ad23c90fa1dd8d79ac0d784a691aa0c6d2b HEAD
88343ad23c90fa1dd8d79ac0d784a691aa0c6d2b refs/heads/master
Upon further investigation we've reverted the patch. I suspect the original problem was a ":" in the url where there should be a "/" character. If you continue to have issues when using a "/" and protocol=ssh, please reopen the bug. |