| Summary: | gitsm.py doesn't seem to work as expected | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Chris Morgan <chmorgan> |
| Component: | bitbake | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | poky.bs.watcher, poky.watcher |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Chris Morgan
2014-05-18 01:44:58 UTC
I was in the process of creating a recipe and a test repository on github (which has the same syntax as bitbucket) and my test case didn't reproduce. I ran: bitbake -c clean mybitbucketrecipe and then bitbake mybitbucketrecipe and it works. I suspect the issue is that I had originally used a git:// path and then switched to a gitsm:// path without cleaning in between. Does this make sense? I ran a few times cleaning and rebuilding and it looks like everything is good now so I'm inclined to say so... Marking as resolved. I was able to get patches in to improve the gitsm:// fetcher documentation and testing here indicates that everything is working as expected with gitsm://. |