Partman reports changes to a disk when there are none.
Bug #287660 reported by
Evan
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| partman-base (Ubuntu) |
Fix Released
|
High
|
Colin Watson | ||
Bug Description
Binary package hint: partman-base
In ubiquity, I opted to resize an existing partition on the first disk. The summary page reports that changes will be made to both disks, when in fact only the first disk will be changed:
Name: partman/confirm
Template: partman/confirm
Value: false
Owners: ubiquity
Variables:
ITEMS = The partition tables of the following devices are changed:\n SCSI1 (0,0,0) (sda)\n SCSI1 (0,1,0) (sdb)\n\nThe following partitions are going to be formatted:\n partition #6 of SCSI1 (0,0,0) (sda) as ext3\n partition #7 of SCSI1 (0,0,0) (sda) as swap\n
Related branches
| Changed in partman-base: | |
| importance: | Undecided → Low |
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| Changed in partman-base: | |
| assignee: | nobody → kamion |
| importance: | Low → High |
| status: | New → Triaged |
| Changed in partman-base: | |
| status: | Triaged → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in partman-base: | |
| status: | Fix Committed → Fix Released |
| tags: | added: iso-testing |
To post a comment you must log in.
I think what happens here is that it autouses swap, using the CHANGE_FILE_SYSTEM command to "change" the swap partition to swap in the process, and has no way to realise that it was already swap and nothing has changed.