Package: dpkg
Severity: important

Hi,

as I've already written to [EMAIL PROTECTED] I figured that dpkgs behaviour
when conffiles are conflicting is somewhat broken. To cite the original
mail:

On Tue, 2008-12-09 at 13:19:30 +0100, Patrick Schoenfeld wrote:
> What I figured is that:
> If Package A contains the conffile /etc/foobar and Package B contains
> another conffile /etc/foobar and noone of the packages diverts the file
> or has a Replaces field set in control, the configuration file is silently
> replaced by the package that is installed last in installation order.
> In effect the dpkg -L output for the first installed package does not
> contain the file anymore.

> What I expected is that on installation of Package B a warning would
> have been issued that Package B tries to replace a (configuration) file
> which also belongs to another Package A (and that the installation would
> fail). Just like it is for normal files in the package. From my point of
> view this _is_ the right behaviour.

Best Regards,
Patrick



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to