For an administrator, it's easy to miss or forget the part of tlinstaller where it tells you to "migrate your configuration files" when upgrading to a newer version of ThinLinc.
There has been discussions about having tl-setup look for .rpmsave (or the equivalent dpkg variant) files and require the administrator to migrate the configuration settings to the new files before proceeding. The benefit of this would be that the administrator would be forced to deal with the new configuration before tl-setup updates the configuration files with the current version, effectively blocking the updated services from starting until the configuration situation has been handled.
Removing target milestone to put this up for discussion. According to me, this bug is solved w.r.t the work made on bug 1760.
In order for us to consider this bug done we also want the interface to be clear when it is a good time to look over your config files. There are comments about this on bug 1760, but we don't have the final implementation yet. As such we cannot yet determine if bug 1760 will resolve this bug.
Bug 1760 is closed now, tl-setup now tells that the proper time to migrate manually is before proceeding with any migration-choice. tl-setup says: "cancel this wizard to migrate manually" Are we satisfied with this or should the TAG say something wrt this as well?
We think bug 1760 is sufficient to consider this problem solved.
