Hi, thanks for your work. Note, that I forgot one more issue which came me in mind later when I already posted a patch. When transitioning to the new conffiles you also possibly need to update the symlink in /etc/apache2/mods-enabled, as it may be dangling otherwise.
Everything else should be fine though, although your binary package should be called libapache2-mod-security2. Your .so is called mod_security2.so, so the corresponding binary package should be libapache2-mod-security2, and the .load/.conf files should be named like the .so, too (which is what you did by applying my patch). Note you can check this using Lintian: $ lintian --profile debian/extra-apache2 -IE --pedantic modsecurity-apache_2.6.6-7.1_amd64.changes ... W: libapache2-modsecurity: non-standard-apache2-module-package-name libapache2-modsecurity != libapache2-mod-security2 Lintian will have these checks in th default profile for the next upload. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D
signature.asc
Description: OpenPGP digital signature
