| Summary: | Kernel checkout requires master branch | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Steve Pomeroy <steve> | ||||
| Component: | kernel | Assignee: | Bruce Ashfield <bruce.ashfield> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Undecided | CC: | bruce.ashfield, tom.zanussi | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Steve Pomeroy
2015-04-17 22:24:28 UTC
This is already fixed in master (as mentioned on the mailing list). The logic was inverted, but we'll now only fall back to master if the machine branch doesn't exist. In particular, I'm not all that concerned about working with repositories with no master. If we handled every single repository variant, the complexity becomes to much. Having a well known (and sane) fallback of master is appropriate in nearly every case. Ah. I didn't see af691920c0e289fd0eb13d94cad03c799375af21 as I was only looking on the dizzy branch. Is this a change that can make it to 1.7.2? Just leaving it be the "master" branch sounds good to me. I'll post the patch for a backport to stable. Thanks for working through this, and sorry for issues it may be causing for your builds! (In reply to comment #3) > Ah. I didn't see af691920c0e289fd0eb13d94cad03c799375af21 as I was only > looking on the dizzy branch. Is this a change that can make it to 1.7.2? > > Just leaving it be the "master" branch sounds good to me. send the patch to the list. Patch posted for backport. |