> # Major upgrade (0.6.0) > if [ -n "$2" ] && dpkg --compare-versions "$2" lt 0.6.0-1 > then > db_input medium suphp-common/upgrade0.6.0 || true > db_go || true > fi > > > > > I don't think I can check the config files as this is apache config > files (could use many includes), and it will not be usefull, as this > configuration option didn't exists before, so users will add it after > upgrade. I just need to warn them to add it soon after upgrade, if they > don't do so, suphp will not work anymore.
Wel, then I'd say "turn the template type to error". A short term solution would be raising the priority to "high" as you obviously want to show this note to as many users as possible when they're hit by the problem. > Template: suphp-common/upgrade0.6.0 > Type: note > _Description: A new directive (suPHP_AddHandler) is now required > This new release introduce a runtime configuration file > (/etc/suphp/suphp.conf) and > a new configuration option for apache/apache2. > . > You must now add the following line in your apache/apache2 > configuration to make suphp active for php scripts: > . > suPHP_AddHandler x-httpd-php Why don't you provided a file to be put in /etc/apache/conf.d ? I'm not very used to the Apache packages policy but that seems the option to do, indeed.
signature.asc
Description: Digital signature
