Bug#305192: [CONFFILE][TRIVIAL] dpkg allow overwrite files by default
On Monday, April 18, 2005 4:07 PM, Olleg Samoylov <olleg@mipt.ru> wrote:
> Default dpkg.conf include force-overwrite. This is improper. All
> "force" options must be setted by admin explicitly.
>
> Severity is grave because this can lead to significant data lost in
> unstable distrib. For instance, package ia32libs version 1.1 in amd64
> distr suddenly overwrite many /bin/* files from coreutils.
This is only the case on the first install of the dpkg package, when the
package is being configured. Since d-i does not use dpkg to install dpkg,
the postinst is never called with --configure, and as such an install using
d-i will not create the file.
> Also add /etc/dpkg/dpkg.cfg as conf file instead of copy in
> dpkg.postinst.
> It is strange to see such vilolation package packing in package dpkg.
Policy does not require that /etc/dpkg/dpkg.cfg be a confile. The file is
only copied in postinst if dpkg was not previously installed, and the file
does not already exist.
This is by design, so that the installer can modify the contents of the file
if required. Since the file is never modified by the maintainer scripts
after the initial install, local modifications are respected, and there is
no need for it to be flagged as a conffile.
Regards,
Adam
Reply to: