[Debian-eeepc-devel] Bug#541426: /etc/default/eeepc-acpi-scripts not classified as configfile?
Damyan Ivanov
dmn at debian.org
Fri Aug 14 07:49:40 UTC 2009
tags 541426 moreinfo
thanks
-=| Björn Wiberg, Fri, Aug 14, 2009 at 06:31:30AM +0200 |=-
> Package: eeepc-acpi-scripts
> Version: 1.1.1
> Severity: normal
>
> The file /etc/default/eeepc-acpi-scripts does not seem to be considered a configuration file.
They are conffiles, which is a special type of a configuration files.
By design, the admin is prompted when the new package ships different
conffile and the local file was changed. There is nothing the package
itself can do about it.
> I have /etc/default/eeepc-acpi-scripts.dpkg-new in place and
> 'apt-get upgrade' does not automatically consider leaving my
> modified version of the file in place and replacing the .dpkg-new
> one with the new file from the package, like other packages do.
The whole point of dpkg conffile handling is that in general you need
to know about the fact that the conffile was changed in the package
and may want to integrate the changes in the local version. Otherwise
the package may break.
Can you give an example of a package that blindly ignores new versions
of modified conffiles?
--
dam
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/attachments/20090814/90d76e68/attachment.pgp>
More information about the Debian-eeepc-devel
mailing list