Looking into this some more, the maintainer scripts are following the Debian guidance for enabling config for Apache 2.4. For example, in openstack-dashboard.postinst we have:
if [ -e /usr/share/apache2/apache2-maintscript-helper ] ; then # apache 2.4 . /usr/share/apache2/apache2-maintscript-helper apache2_invoke enconf $CONF || exit $? elif ... which follows the guidance from: https://wiki.debian.org/Apache/PackagingFor24 This is intended to exit if the package's apache config can't be enabled when the package is installed, which is the case when apache2 is not running at package install time. So we are doing the right thing to exit if config can't be enabled. However I wonder if we could help alleviate this bug by attempting to start apache2 if it's not already started. I'll consult with some fellow package maintainers and see what they think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574144 Title: package openstack-dashboard-ubuntu-theme 2:9.0.0-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1574144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
