Am 16.04.2018 um 10:17 schrieb Jonas Smedegaard:
> Excerpts from Philipp Huebner's message of april 16, 2018 9:38 am:
>> On Tue, 10 Apr 2018 19:39:14 +0200 Jonas Smedegaard <d...@jones.dk> wrote:
>>> The file /etc/default/ejabberd is registered as a conffile, but is
>>> also manipulated using ucf in postinst script. That is illegal,
>>> according to Policy § 10.7.3
>>
>> thanks for pointing this out!
>>
>> However, this is rather unfortunate, the current setup has been well
>> tested and in use for ages.
>>
>> Do you have an idea on how to achieve this in a policy-conform way?
>>
>> Not touching ejabberd.yml would mean to remove the debconf templates
>> for configuring ejabberd, not declaring ejabberd.yml a conffile would
>> mean putting in some extra effort for handling changes. Are
>> non-conffiles even allowed in /etc ?
>
> Debian Policy distinguishes between "configuration file" and "conffile"
> and describes, particular at §10.7.3, how to handle either. I believe
> the first step is to *not* ship the configuration file below /etc if it
> should not be a conffile ("man dh_installdeb" documents how any file
> below /etc shipped with a package is registered as a conffile).
>
> "man ucf" contains some documentation on transitioning from conffile to
> non-conffile. I believe that involves collecting md5sums of most
> possible previous pristine states (i.e. configfile as shipped unedited
> with the package) as possible.
>
>
> Hope that helps,It does, and only now I realized you're talking about /etc/default/ejabberd and not ejabberd.yml, so the problem is only a fraction as tough as I thought, because we're already handling ejabberd.yml the correct way and can simply duplicate that. Should be fixed soon(ish)! Thx again, -- .''`. Philipp Huebner <debala...@debian.org> : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `-
signature.asc
Description: OpenPGP digital signature
