When running tl-setup after installing to the current build I get complaints about the following files in config migration step: > /opt/thinlinc/etc/tlwebaccess/server.crt.rpmsave > /opt/thinlinc/etc/tlwebaccess/server.key.rpmsave Migrating things here quite obviously does not make sense This is fallout from bug 5513, which is the first time we've changed the default files.
We have decided to limit the configuration migration step in tl-setup to only work on Hiveconf files (instead of all files that RPM/DEB considers to be 'configuration'). This means we should also make our documentation in the TAG more specific.
This problem is twofold: * Firstly, during the package upgrade we could get .rpmsave or .dpkgold files meaning the original certificate was replaced and renamed, and a basic self-signed certificate would be active instead. This was handled on bug 5773. * Secondly, regular migration isn't a suitable approach for certificates. Our configuration migration step in tl-setup would highlight the certificates and ask the admin how he wanted them to be handled. The answer should always be to keep the old certificate, presenting a question is unnecessary. This bug is about the second problem.
Fixed. ThinLinc Setup no longer offers to migrate non-Hiveconf files, and the documentation has been clarified to reflect this change.
Looks mostly good. Tested on RHEL 8 by changing passwdaliases, homecreatefilter.conf and vsmserver.hconf. I'm a bit concerned about this new addition though: > Note that these choices only affect Hiveconf files that are > marked as conflicting by the package upgrade. Conflicting files > are files that are changed both in the saved configuration and in > the new release. Conflicting files that aren't Hiveconf files are > not affected by tl-setup. The phrasing of this suggests some files are ignored and left broken rather than that they are fine as they are. "changed in the saved configuration" is also unclear. Saved where and by whom? Cendio or the admin? "modified on this system" or some variation thereof like we have in ThinLinc Setup is much more clear. (We should also refer to "ThinLinc Setup" rather than the name of the script)
I have improved the documentation now, and it should hopefully be more clear as to what is happening regarding non-hiveconf files. I also included a commit that adds consistency in the way we talk about "ThinLinc Setup".
After a few minor phrasing adjustments everything looks fine now. Closing.
