Hi Petter, On Sa 17 Dez 2016 13:09:09 CET, Petter Reinholdtsen wrote:
[Mike Gabriel]The observation:[...]- normally conf upgrades are fine, but gosa.conf is an exception...There is nothing special about gosa.conf. Any conffile that is edited automatically experience this problem, and it commonly come up in Debian.
Yes, there is something special about gosa.conf. During the TJENER setup process, the gosa.conf as shipped in d-e-c gets modified (e.g. credentials for LDAP admin get added).
So a TJENER never has the gosa.conf as found in d-e-c. It ships a modified version, tweaked by ldap-debian-edu-install .
Proposal: - My suggestion is to rename gosa.conf to gosa.conf.in - Use gosa.conf.in during TJENER setup / installation and copy the result to a file named gosa.conf - on d-e-c pkg upgrades, the gosa.conf.in template file gets updated. - changes to gosa.conf.in need to be worked into gosa.conf manually thenAnother option is to use ucf. It avoid the need to manually apply changes. The "gosa.conf.in" file should probably anyway reside in /usr/share/ and be named gosa-template.conf or something like that.
For gosa.conf, I highly prefer manual adaptions. But that's a personal preference. Also I wonder if using ucf for just one file would make the conffile handline in d-e-c unnecessarily complex.
I agree about having the gosa.conf.in in /usr/share somewhere and I am also fine with gosa-template.conf as name. It would be nice providing the patch between last gosa-template.conf and next gosa-template.conf somehow, so that people can review and patch changes easily. Still in brainstorming mode here, though...
Greets, Mike https://anonscm.debian.org/cgit/debian-edu/debian-edu-config.git/tree/ldap-tools/ldap-debian-edu-install#n300
-- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: email@example.com, http://das-netzwerkteam.de
Description: Digitale PGP-Signatur