This causes the Aegir installation to fail when linking aegir.conf. In Saucy and above, the new directory is /etc/apache2/conf-enabled.

Comments

helmo’s picture

Thanks for figuring this out.

anarcat’s picture

Wow, okay, is this the same in Debian jessie/unstable or this is some fancy Ubuntu thing?

helmo’s picture

I just debootstraped a jessie and it also has the conf-enabled/ dir.

ldc711’s picture

I am having this issue when I run "sudo apt-get install aegir2" on Ubuntu

So how do I get passed this error?

ldc711’s picture

Here is my full error - there is also mention of other issues:

Setting up aegir2-hostmaster (2.0) ...
'drush' cache was cleared [success]
Aegir frontend (@hostmaster) site detected in /var/aegir/hostmaster-6.x-2.0
it seems to be the same version as the one we're trying to install, not upgrading
ln: failed to create symbolic link ‘/etc/apache2/conf.d/aegir.conf’: No such file or directory
dpkg: error processing aegir2-hostmaster (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of aegir2:
aegir2 depends on aegir2-hostmaster (>= 2.0); however:
Package aegir2-hostmaster is not configured yet.

dpkg: error processing aegir2 (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
aegir2-hostmaster
aegir2
E: Sub-process /usr/bin/dpkg returned an error code (1)

ergonlogic’s picture

Version: 6.x-2.0-rc5 » 6.x-2.x-dev
Priority: Normal » Major
Issue tags: +Aegir 2.1

We should try to get this fixed for the next release.

anarcat’s picture

Well, note that this will not be enough for Aegir to work with Apache 2.4 (which is what this is really about), we would need at least #1477098: Accommodate updated syntax on Apache 2.4 as well. And *that* issue is much more difficult to fix as it involves having different configs for 2.2 and 2.4. :(

anarcat’s picture

Component: Code » Debian package
Status: Active » Fixed

I believe this is related only to the Debian package. I have implemented a fix in the postinst of provision which should now do the right thing.

Pushed to all three branches.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.