partitions without offset should be kept in yaml order
Bug #1631423 reported by
Steve Langasek
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Image |
Fix Released
|
High
|
Barry Warsaw | ||
Bug Description
The docs currently say:
offset
(optional) The offset in bytes from the beginning of the image. If not specified, placement of the structure within the disk image is implementation-
We want to tighten this to not be implementation-
| Changed in ubuntu-image: | |
| milestone: | none → 0.11 |
| assignee: | nobody → Barry Warsaw (barry) |
| importance: | Undecided → High |
| status: | New → In Progress |
Revision history for this message
| Barry Warsaw (barry) wrote | #1 |
Revision history for this message
| Barry Warsaw (barry) wrote | #2 |
| Changed in ubuntu-image: | |
| status: | In Progress → Fix Committed |
| Changed in ubuntu-image: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Some quick notes.
The official gadget.yaml documentation is now here: https:/
offset is now *not* implementation dependent. The spec says:
# The offset from the beginning of the image. Defaults to right after
# prior structure item. (optional)
offset: <bytes> | <bytes/2^20>M | <bytes/2^30>G
That doesn't change the need for this fix, just that we're making the code reflect the specification.