Hi, > If a file in /etc/ is shipped in the package (i.e., not created or > copied in the postinstall script) then it will be managed by dpkg, and > the above command line arguments will work. The logrotate file is > created by the postinst script, and conffile handling is done > with ucf. Ok, I wasn't aware of that. Why is the logrotate file not part of the package, but created by postinst instead?
> Since there is currently no way for ucf to know anything about dpkg's > command line, I'm afraid this just isn't going to work for now. Can you document this situation in README.Debian with a pointer to conf_force_conffold in /etc/ucf.conf? This behaviour was entirely unexpected for me. Especially in a package such as this, which is prone to be automatically installed by some distribution system, it can lead to frustration on the part of the admin trying to make the system shut up and just do it :) > I am not sure that this is a bug, since the files in question aren't > managed by dpkg, but it's up to you if you want to keep it > open or not. Well, the ultimate cause is different than what I thought it was, but the behaviour of the package isn't what one would expect. If it's ok with you, I'd like to move this bugreport to the priority "Wishlist" to the effect of having /etc/logrotate.d/clamav-daemon being handled by dpkg. OTOH, if there are reasons for not doing that, and the situation is documented, I see no reason to keep this bug report open. Regs, Sven
