[Bug 1296071] Re: install over existing does not delete old - result in corrupt install

[codeslinger]

hmm, that's interesting/confusing, it is doing some amount of
deleting... just not complete.

Before the install, I did this:

sudo su
touch /home/test/this-should-be-deleted
touch /bin/this-should-be-deleted
touch /boot/this-should-be-deleted
touch /etc/this-should-be-deleted
touch /lib/this-should-be-deleted
touch /lib64/this-should-be-deleted
touch /sbin/this-should-be-deleted
touch /selinux/this-should-be-deleted
touch /usr/this-should-be-deleted
touch /var/this-should-be-deleted

and after the install these still existed

/boot/this-should-be-deleted
/home/test/this-should-be-deleted
/selinux/this-should-be-deleted


but the bottom line is that installing over the top of an existing os does not actually work properly, you must either manually delete it or else format the partition.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1296071

Title:
  install over existing does not delete old - result in corrupt install

Status in “ubiquity” package in Ubuntu:
  Incomplete

Bug description:
  when you do a manual install and choose a partition which already has an os on it.
  then you get warned that the os will be erased...  good that is what I want...
  but then it does not actually erase the old os instead it adds files to it and the result is unbootable.

  steps to reproduce:
  1) on an empty partition install an os such as 14.04
  2) do all the ususal stuff... such as installing updates, fini

  now decide to start over with a clean version of the os
  3) manually install a new os, select the partition that was used before
  4) see the nice warning about how the old files will be erased.... ok
  5) watch as it ~appears~ to make an inventory of all the files already present on the partition huh?
  6) watch as it ~appears~ to selectivly add files and or overwrite existing files
  7) fini, attempt to boot the newly installed os

  result: fails to boot, os is corrupt

  expected: it should have erased the relevant directories, basically
  everything except home...  before adding new files.

  now, confirm problem by manually erasing everything from the partition
  and reinstalling and then everything works.

  Note: your actualy milage will vary depending on what os you are
  installing on top of what os.  for instance if you instal the same
  bits on top of the same bits, then your os will work and you won't
  notice the problem.  you have to have oses that are similar but not
  quite compatibile in order for this failure to become apparent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1296071/+subscriptions