After a debug marathon with Ludovic, it was discovered that the nightly builds for Debian Lenny are not suitable for Ubuntu 10.04 LTS (ABI issues, apparently). Building SOPE and SOGo from sources works correctly.

The plan of attack is that Inverse will be working on nightly builds specifically for Ubuntu 10.04. In the interim, SOPE/SOGO can be built as described below:

First, remove all SOPE/SOGo related packages (this step will leave all configuration in place):

# apt-get remove sogo
# apt-get autoremove

You may still have some SOPE packages installed after the autoremove, as I did. (I installed some of them manually for Postgresql support) To list any SOPE packages:

# dpkg -l | grep sope

These can be apt-get remove'd as well.

Next, install the build environment:

# apt-get install subversion monotone build-essential gnustep-make \
libxml++2.6-dev libxml2-dev libssl-dev libldap2-dev libpq-dev patch \
libldap2-dev libxml2-dev libldap2-dev libssl-dev libpq-dev gobjc-4.4 \
libgnustep-base-dev apache2-prefork-dev libapr1-dev libaprutil1-dev \
libdb4.8-dev libexpat1-dev libpcre3-dev libsqlite3-dev uuid-dev \
libmysqlclient16-dev libmysqlclient15off mysql-common

This may not cover every package, but it gets the majority of dependencies that you will need.

Build instructions are available here: http://www.sogo.nu/english/support/faq/article/how-do-i-compile-sogo-2.html

After successful build, you may need to modify your Apache SOGo.conf to point to the new WebResources install location, depending on how it was configured.

According to Ludovic, starting your SOGo build goes something like this:

# sudo -u sogo /usr/local/sbin/sogod -WONoDetach YES -WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid


Some additional build information can be found here, though it a bit out-of-date: http://wiki.mhcsoftware.de/SOGo_1.0.1_on_Ubuntu_9.04


And another big THANK YOU! to Ludovic for his time and effort working on this issue.


On 07/01/2010 10:24 AM, Jason Oster wrote:
On 07/01/2010 09:39 AM, Jason Oster wrote:
I found a "solution" to the Postgresql connection problem. I had to
change my SOGoProfileURL to drop the table name (?!):

Filed Bug 675 on this: http://www.sogo.nu/bugs/view.php?id=675

<<attachment: jason_oster.vcf>>

-- 
[email protected]
https://inverse.ca/sogo/lists

Reply via email to