Closed (fixed)
Project:
Hostmaster (Aegir)
Version:
6.x-2.x-dev
Component:
Debian package
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
10 Dec 2013 at 17:56 UTC
Updated:
18 Mar 2014 at 19:01 UTC
Jump to comment: Most recent
Comments
Comment #1
helmo commentedThanks for figuring this out.
Comment #2
anarcat commentedWow, okay, is this the same in Debian jessie/unstable or this is some fancy Ubuntu thing?
Comment #3
helmo commentedI just debootstraped a jessie and it also has the conf-enabled/ dir.
Comment #4
ldc711 commentedI am having this issue when I run "sudo apt-get install aegir2" on Ubuntu
So how do I get passed this error?
Comment #5
ldc711 commentedHere 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)
Comment #6
ergonlogicWe should try to get this fixed for the next release.
Comment #7
anarcat commentedWell, 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. :(
Comment #8
anarcat commentedI 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.