Bug#23712: conflicting packages with the same conffile
Yann Dirson <firstname.lastname@example.org> writes:
> Richard Braakman writes:
>> Yesterday I noticed that Debian policy is incorrect on this:
>> Only packages that are tagged *conflicting* with each other may
>> specify the same file as `conffile'. A package may not modify a
>> configuration file of another package.
>> (section 3.3.7)
> Yes, this should be raised on deb-policy I think.
This is now 10.7.4, but the same issue is still there. The concern is
that conffiles remain even after the package is removed, so conflicts may
be insufficiently strong and packages may simply never be able to use the
same conffile as another package whether they declare conflicts or not.
What happens if you have a package on the system that's removed but not
purged and you install another package (conflicting with the first) that
contains the same conffile? I suspect the conffile will be treated as
locally modified and the newly installed package will get the conffile
from the old removed package, but I'm not sure.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>