Automatic install on Debian

Tagged:

Debian packages have been uploaded to http://debian.koumbit.net/, currently in the "unstable" distribution during the test period. We eventually want to upload those packages to the official archives, but this will take some adaptation and time to sponsor the packages in.

Those are the installation instructions that are recommended on Debian. If you wish to install Debian packages over an existing manual install, it's possible, see the Debian upgrade procedures.

1. Adding the Koumbit repositories

Add the following line to /etc/apt/sources.list.d/koumbit-unstable.list:

.. then run apt-get update.

2. Adding the archive key to your keyring

This archive self-signs packages uploaded to it (and packages uploaded are verified against a whitelist of trusted uploaders) using OpenPGP (GnuPG, to be more precise).

The key of the archive is in the key.asc file. You should add the key using something like this:

3. Adding backports

You should also configure backports repositories, for Drush. 4.4 is now in Debian unstable, wheezy, squeeze-backports and Ubuntu Natty.

So if you are running Debian wheezy or later, or Ubuntu Natty or later, you don't need to do anything here. If you are running Debian Squeeze, add the following line to /etc/apt/sources.list :

deb http://www.backports.org/debian/ squeeze-backports main

If you are running Debian lenny or Ubuntu Maverick or Ubuntu versions before Lucid, we recommend downloading and installing the Drush package manually.

For users in Ubuntu LTS (Lucid 10.04), you can instead use Brian Mercer's PPA (Personal Package Archive) using the following command:

sudo add-apt-repository ppa:brianmercer/drush

(Ubuntu synced Drush 4.4 in Natty Narwhal 11.04, which should be released by the end of april, but we're still looking for a Ubuntu MOTU to handle the backporting on the Ubuntu side of things. See the followup for the backport.)

4. Manual sudo configuration

If you are running sudo versions previous to 1.7.2p1-1 (in Debian squeeze and Ubuntu Lucid), you will need to manually modify your /etc/sudoers file to add the following line:

aegir ALL=NOPASSWD: /usr/sbin/apache2ctl

5. Installing Aegir

To install aegir, frontend and backend, use the following command:

apt-get install aegir

This will prompt you for the required information and go ahead with the install.

6. Troubleshooting the install

To make the install smoother, the install command is run without much debugging information, which can make diagnostics pretty hard. For this there's a special environment variable you can set that will trigger debugging output. Install aegir with this:

env DEBUG=yes apt-get install aegir

You can build your own Debian packages from our repositories using those instructions.

#1

On Squeeze, I tried to install aegir2, but have some dependency errors, firstly stating I need hostmaster2 and provision2, then stating I need drush5.5 or greater. I have installed drush5.8 using php-pear package, but apt-get mustn't know about this.

  • What is the 2.x procedure for the automatic installation?
  • Is there a method to add a higher version of drush than 4.5 to squeeze-backports so that apt-get knows the correct drush version?

I thought that running 'apt-get install aegir2' would have picked up the correct hostmaster and provision (aegir-provision2 and aegir-hostmaster2), as I think it does for 'apt-get install aegir'.

root@aegir2:~# apt-get install aegir2
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
aegir2 : Depends: aegir-provision2 (>= 2.0~alpha1) but it is not going to be installed
          Depends: aegir-hostmaster2 (>= 2.0~alpha1) but it is not going to be installed
E: Broken packages
root@aegir2:~# apt-get install aegir-provision2 aegir-hostmaster2
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
aegir-hostmaster2 : Depends: drush (>= 5.5) but 4.5-2~bpo60+1 is to be installed
aegir-provision2 : Depends: drush (>= 5.5) but 4.5-2~bpo60+1 is to be installed
E: Broken packages

Thanks in advance for any help with this.

#2

@mccrodp: I had a similar experiance, and opend this issue: http://drupal.org/node/1920152

#3

Would it be possible to add "profile" as an option, just like "makefile"?

#4

Sure. It would have to be added to the drush hostmaster-install and possibly hostmaster-migrate commands. Feel free to open an issue. Patches welcome ;)

#5

Thanks to jonpugh @ #32 and #33 for helping me get aegir 1.9 going with a fresh install of Debian Wheezy. The default wheezy version of drush is now too new (v5.x) for aegir 1.x. You need version 4.x, available in squeeze-backports. If you've already tried to install and run into "The drush command '@hostmaster status' could not be found." you must purge aegir and drush before attempting to reinstall with the correct drush version pinned.

#6

I had problem installing aegir2 on debian 7. Warning was

ERROR: Module ssl does not exist!

This can be solved with enabling mod_ssl on your apache2. For my case I needed to create /etc/apache2/mods-available/ssl.load with content

LoadModule ssl_module /usr/lib/apache2/modules/mod_ssl.so

After creating that file and restarting apache enable module sudo a2enmod ssl.