Univention Bugzilla – Bug 45639
Make upstream Debian config file changes detectable
Last modified: 2020-07-13 20:08:30 CEST
It would be helpful to have a mechanism to detect when and how an *upstream* Debian config file changed which has been diverted and replaced by a UCR template. I'm not talking about *local* config file changes here, see below. This mechanism should provide a diff for us which we can use to detect when a UCR template might need an update, because the upstream file changed. Technically we may be able to do this by wrapping the dpkg-divert calls and copy the (to be) diverted file to a backup location. Once we find a stored copy, we can diff. When you think about it, a version control system would be ideal for this, e.g. git. If that's not possible, then we could simply use filenames for the backup copies that have the Debian package version in the filename, a bit like /var/univention-backup/. Once we have this information, it may additionally offer us a way to also discover customer initiated *local* config file changes like frequently found in the case of the S4- and AD-Connector mapping (see Bug 45220). Ideally a 3-way-merge would be possible. Note: We currently have univention-check-templates to find .dpkg-dist and .dpkg-new files which are generated by dpkg in case a config file has been changed *locally*. The proposal here is complementary to that.
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.