FAQ

How to install SOGo on Ubuntu ?

Installation

If you're using Ubuntu Precise Pangolin (12.04), add to your apt source list (/etc/apt/sources.list):

deb http://inverse.ca/ubuntu precise precise

If you prefer using the nightly builds, simply use instead:

deb http://inverse.ca/ubuntu-nightly precise precise

If you're using Ubuntu Oneiric Ocelot (11.10), add to your apt source list (/etc/apt/sources.list):

deb http://inverse.ca/ubuntu oneiric oneiric

If you prefer using the nightly builds, simply use instead:

deb http://inverse.ca/ubuntu-nightly oneiric oneiric

If you're using Ubuntu Natty Narwhal (11.04), add to your apt source list (/etc/apt/sources.list):

deb http://inverse.ca/ubuntu natty natty

If you prefer using the nightly builds, simply use instead:

deb http://inverse.ca/ubuntu-nightly natty natty

If you're using Ubuntu Maverick Meerkat (10.10), add to your apt source list (/etc/apt/sources.list):

deb http://inverse.ca/ubuntu maverick maverick

If you prefer using the nightly builds, simply use instead:

deb http://inverse.ca/ubuntu-nightly maverick maverick

If you're using Ubuntu Lucid Lynx (10.04), add to your apt source list (/etc/apt/sources.list):

deb http://inverse.ca/ubuntu lucid main

If you prefer using the nightly builds, simply use instead:

deb http://inverse.ca/ubuntu-nightly lucid main

Then, do:

sudo apt-get update
sudo apt-get install sogo

To install SOGo under Ubuntu Intrepid (8.10), add to your apt source list (/etc/apt/sources.list):

deb http://inverse.ca/debian lenny lenny

If you prefer using the nightly builds, simply use instead:

deb http://inverse.ca/debian-nightly lenny lenny

For Jaunty (9.04) and Karmic (9.10) versions, simply use "squeeze" instead of "lenny".

Please note that Debian Squeeze will be a moving target as long as it has not been released, causing version mismatches from time to time. For example, Ubuntu Karmic/9.10 requires libssl0.9.8 from Ubuntu Lucid/10.04. Additional adjustments will be added to this FAQ as we learn them.

Signed builds

Since 2011-05-17, the builds are signed.  In order to verify their signature, our GPG public key has to be added into apt keyring. To do so, run the following commands:

sudo apt-key adv --keyserver keys.gnupg.net --recv-key 0x810273C4
sudo apt-get update

From that point, apt-get should not complain about package signatures anymore.