On Fri, 2015-05-08 at 13:43 +0200, Andreas Cadhalpun wrote: > I see three ways forward: > a) Basically ignore the remaining cases and tell anyone who asks about > the warning that he can safely remove the PidFile setting. > b) Bump the version in the postinst check and hope it works this time. > c) Remove the version check and unconditionally remove the PidFile > setting, if it uses the default path. > > Does anyone have preferences? I'd probably prefer it in the order b,c,a.
The disadvantage with (a) is, that we'll certainly miss some installations which will then never reach the "up to date" state. The disadvantage with (c) is, that IMHO it's generally a bad idea to remove settings the user might have intentionally and manually set (even if it matches the default). So I guess the best thing would be (b), but the bump would need to be big enough to cover all current versions from any "older" suites (including backports, proposed-updates, and so on). And obviously, if any updates would make it in the future to any of these "older" suite, which would result in a newer version being there than the one you're bumping to,... the then same situation would exist again (i.e. for people who migrate then to jessie or higher). However, ff such future update contain the cleanup code as well, than this would be solved. Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pkg-clamav-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-clamav-devel
