Comment 2 for bug 1247116

Ben Hockley (oohbuntu) wrote :

The underlying problem seems to be that the package installer assumes the existence of the (recently deprecated?) /etc/apache2/conf.d/ directory - so installation likely to be broken on fresh installations or upgrades from recent versions.

From googling, it looks like /etc/apache2/conf.d/ was replaced by /etc/apache2/conf-available/ in apache 2.4 - so it is the change to apache that has broken this package, I guess?