I agree some of the points you mentioned but that leads to problems. Situation
actually depends on what user plans to do. No change of UUID is needed if the
new partition will not be used in the same computer with the old one and no
further editing of destination partition will now be done. The other effect of
that situation is that Gparted will show destination mounted, does not allow to
dismount "sdb" and as a result no further action for "sdb" is possible (unless
you understand to change manually UUID for the destination disk). I regard
that a confusing situation for users, too. Problem with further editing with
Dparted could be avoided by generating new UUID for the new copy just to keep
Unique = Unique i.e. what that UUID stands for. Some users could be surpised
but I can not see any technical problem resulting from that approach.
I prefer giving users a choice (tickbox, menu, what ever) to select "Keep
oroginal UUID" with some short warning about results but just to avoid problems
the default should be "Unique = Unique" i.e. old UUID kept intact if it
exists on destination or a new one generated otherwise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737387
Title:
Gparted: "Copy" creates duplicate UUID to another disk
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
