On 2006-10-08 18:53 +0200, martin f krafft wrote:
> Package: dpkg
> Version: 1.13.22
> Severity: important
>
> piper:~# dpkg -S /etc/logcheck/ignore.d.server/ntp
> logcheck-database: /etc/logcheck/ignore.d.server/ntp
> piper:~# ls -l /etc/logcheck/ignore.d.server/ntp
> -rw-r----- 1 root logcheck 45 2006-08-09 14:51
> /etc/logcheck/ignore.d.server/ntp
> piper:~# dpkg -c
> ~madduck/debian/pkg/logcheck/logcheck-database_1.2.48_all.deb | grep /ntp$
> -rw-r----- root/root 1009 2006-10-08 17:22
> ./etc/logcheck/ignore.d.server/ntp
> piper:~# dpkg -i --force-confnew
> ~madduck/debian/pkg/logcheck/logcheck-database_1.2.48_all.deb (Reading
> database ... 112370 files and directories currently installed.)
> Preparing to replace logcheck-database 1.2.48 (using
> .../logcheck-database_1.2.48_all.deb) ...
> Unpacking replacement logcheck-database ...
> Setting up logcheck-database (1.2.48) ...
>
> piper:~# ls -l /etc/logcheck/ignore.d.server/ntp
> [334]
> -rw-r----- 1 root logcheck 45 2006-08-09 14:51
> /etc/logcheck/ignore.d.server/ntp
>
>
> note how the file is still the old version.
This is actually expected, since --force-confnew only installs the new
version if it different from the file shipped in the previous version of
the package. Since you're reinstalling the same package version, this
is most probably not the case in your example. It has to be conceded
that the dpkg manpage is anything but clear about this.
In dpkg 1.15.8 a new option --force-confask was added to allow
overwriting locally modified conffiles with the files from the package,
even if the package does not contain new versions.
Cheers,
Sven
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
