Hi! * Holger Levsen <hol...@layer-acht.org> [101114 01:02]:
> But this is not the real problem, the real problem is that this prompt > shows up in the first place, as there was nobody modifying this > conffile at all, the package has just been installed and upgraded... It seems that upon installation of snort-pgsql or snort-mysql /etc/snort/snort.conf is changed. As this file actually belongs to snort-common, upgrade of that package fails. So, to solve this bug, snort-common should remove these entries in it's preinst, while snort-pgsql and snort-mysql add their configuration snippets in a policy conform way. It seems the easiest way to do this would be to include an /etc/snort/snort-database.conf by default, and let that file be a non-configuration file handled by snort-*sql... It also seems that it must be at least an empty file, as snort doesn't start if one of it's configuration files doesn't exists. I think I could try to prepare an NMU for that, but would like to ask for comments before doing so. Best regards, Alexander
signature.asc
Description: Digital signature
