Bug#23712: conflicting packages with the same conffile
Raphael Hertzog <email@example.com> writes:
> On Fri, 20 Aug 2010, Russ Allbery wrote:
>> + <p>
>> + A package that declares the same <tt>conffile</tt> as another,
>> + conflicting package may see left-over configuration files from
>> + that other package.
> EPARSE on this sentence, it looks like some words are missing.
Hm. All the words that I had intended to be there are there. I clearly
need to rephrase it somehow, though, if it's not clear. How about:
When two packages both declare the same <tt>conffile</tt>, they may
see left-over configuration files from each other even though they
conflict with each other.
>> If a user removes (without purging) one
>> + of the packages and installs the other, the new package will
>> + take over the <tt>conffile</tt> from the old package. If the
>> + file was modified by the user, it will be treated the same as
>> + any other locally modified <tt>conffile</tt> during an
>> + upgrade.
>> + </p>
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>