[Bug 678454] Re: How should the 'replace existing Ubuntu installation' option look?

Matthew Paul Thomas mpt at canonical.com
Thu Sep 27 09:58:46 UTC 2012

Currently if you choose "Upgrade Ubuntu", "Reinstall Ubuntu", or "Erase
Ubuntu and reinstall", the new installation uses the same disks and
partitions as the old one, so the resize step does not appear. I think
this is correct behavior -- if you want to use a different disk and/or
partitions, you can choose "Erase everything and (re)install Ubuntu" or
"Something else".

The resize screen would also serve as a confirmation of what you're
about to do. But there's no reason this particular choice needs
confirmation more than others, and confirmation in general is bug

** Changed in: ubiquity (Ubuntu)
       Status: New => Invalid

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.

  How should the 'replace existing Ubuntu installation' option look?

Status in “ubiquity” package in Ubuntu:

Bug description:
  Binary package hint: ubiquity

  There are two pages for automatic partitioning in ubiquity.  The first
  page allows the user to select some general choice like "resize to
  install Ubuntu" or "advanced partitioning".  The second page allows
  the user to define what disk to act on for the aforementioned choice,
  and lets them switch between actions available for the disk (so if
  they selected resize on the first page, they can still elect to wipe
  the entire disk or partition).

  How should the "replace existing Ubuntu installation" option fit into
  this?  Michael Forrest specified that the first page should have a
  "replace existing Ubuntu installation, keeping my files" radio button.
  But what should the state of the buttons look like on the second page,
  as the user applies them to iterate between resize, use disk, use
  partition, and replace existing install modes?

  For reference, here are the mockups of the automatic partitioning


To manage notifications about this bug go to:

More information about the foundations-bugs mailing list