linux-ti-omap4 ftbfs in raring
Bug #1163443 reported by
Matthias Klose
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-ti-omap4 (Ubuntu) |
Won't Fix
|
High
|
Tim Gardner | ||
| Raring |
Won't Fix
|
High
|
Tim Gardner | ||
Bug Description
| Changed in linux-ti-omap4 (Ubuntu Raring): | |
| assignee: | nobody → Tim Gardner (timg-tpi) |
| status: | Triaged → In Progress |
Revision history for this message
| Adam Conrad (adconrad) wrote | #1 |
| Changed in linux-ti-omap4 (Ubuntu Raring): | |
| status: | In Progress → Won't Fix |
| Changed in linux-ti-omap4 (Ubuntu): | |
| status: | In Progress → Won't Fix |
To post a comment you must log in.
This is a direct copy from quantal, and always will be, so the FTBFS is meaningless. There will never be (and never need to be) a ti-omap4 upload directly to raring, since raring's support window is shorter than quantal's, and we're relying on the quantal SRU process to feed us the raring kernel.