This "fix" caused me a massive headache, and one that I consider unjustified, because my workflow never could have actually triggered this issue, but I was still forced to format.
My workflow when reinstalling is to mount the target partition, make a /old directory, and move the entire contents of the filesystem into that directory, before proceeding to unmount the target and install without formatting. This way, I have a totally clean new system, but can access my old files post-install as needed and restore what I want. I have done this many times, across decades of using linux, across multiple distros. For me to be forced to format out of fear that I might make a mistake seems... not in the spirit of linux. This could have easily been a warning noting that the functionality of installing over an existing install is not currently working. Or if that still feels too risky, perhaps the workaround should actually check whether any expected system directories are present at all, and only force formatting in that case. There could be various other reasons for someone to need to install without formatting, such as if they had a need to choose a block size based on the intended use case for that machine/filesystem. I don't understand why it seemed like an acceptable option to *force* users like this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058638 Title: User account is missing from /etc/shadow & /etc/passwd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2058638/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
