Package Details: sogo2 2.3.23-1

Git Clone URL: (read-only, click to copy)
Package Base: sogo2
Description: groupware server built around (OGo) and the SOPE application server
Upstream URL:
Licenses: GPL
Conflicts: sogo, sogo-openchange, sogo2-openchange
Provides: sogo-activsync, sogo2-activesync
Replaces: sogo-activesync, sogo2-activesync
Submitter: DJ_L
Maintainer: deons
Last Packager: deons
Votes: 14
Popularity: 0.000000
First Submitted: 2016-04-26 03:48
Last Updated: 2018-01-21 02:12

Dependencies (18)

Required by (0)

Sources (4)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

DJ_L commented on 2014-11-23 19:28

kwirkie, how much trouble would it be to add the default apache configuration to the package?

Basically it amounts to:

+backup=(etc/sogo/sogo.conf etc/httpd/conf/extra/SOGo.conf)
package() {
+install -D -m 0600 "${srcdir}"/SOGo-${pkgver}/Apache/SOGo.conf "${pkgdir}"/etc/httpd/conf/extra/SOGo.conf


kwirkie commented on 2014-10-11 11:58

ochi - The packges did include the tmpfiles.d file for creating the directory, but you need to run this manually when first installing, as was only created on boot. However, with the latest package, the service file to use the systemd service "RuntimeDirectory" ( option, so people shouldn't have any issues now. ☺

ochi commented on 2014-10-08 19:37

When trying to start a freshly installed sogo 2.2.7, it tells me that the pid file /var/run/sogo/ doesn't exist:

> systemctl status -l sogo
sogod[5551] File NSData.m: 1440. In -[NSData writeToFile:options:error:] Open (/var/run/sogo/ failed - No such file or directory
sogod [5551]: [ERROR] <0x0x7f86594a9fb0[NSUserDefaults]> unable to open pid file: /var/run/sogo/

Indeed this file doesn't exist. Creating a directory /var/run/sogo and chowning it to sogo:sogo seems to work, but shouldn't the package or service deal with this somehow?

francoism commented on 2014-03-25 14:54

v2.2.2 released. :)

DJ_L commented on 2013-12-15 06:06

FYI, working flawlessly now. Thanks!

kwirkie commented on 2013-11-30 12:27

Updated with path to resolve Mailer issue. Patch taken from pointers from

DJ_L commented on 2013-11-28 07:03

Yes, seeing the same problem with all since 2.0.7....2.1.0, 2.1.1, 2.1.1a. There was a promising commit just prior to 2.1.1a release, but not fixed completely. I'm holding at 2.0.7 now as this makes sogo unusable for me ATM, but will continue digging as I have the time to do so.

kwirkie commented on 2013-11-27 08:14

Updated. I'm having issues with Mailer element functioning again, as per my previous post.
Thanks DJ_L for the ideas, but they unfortunately don't resolve the issue…☹

DJ_L commented on 2013-11-03 08:37

Shooting from the hip here as I'm not anywhere near to the point where I can test, but I suspect that the paths are incorrect as stuff was moved around in the source tree. Something like:

sed 's@Mailer/SOGoMailBodyPart.h@SoObjects/Mailer/SOGoMailBodyPart.h@' \
-i `grep -Rl "<Mailer/SOGoMailBodyPart.h>"`

will probably "fix" the first one if I'm correct. If that works, the real "fix" is to correct the include directories, but I don't know squat about gnustep.

I don't see anything obvious on the second message (of course, I don't even know if the first is correct yet). I don't know if "../path/file.h" is valid for #import, but it appears only once in the format <MailPartViewers/UIxMailRenderContext.h> in UI/MailerUI/UIxMailView.m. If '#import "../MailPartViewers/UIxMailRenderContext.h"' is valid syntax, then maybe there. This (ugly, but functional workaround might fix the second):

sed -e 's@<MailPartViewers@"../MailPartViewers@' \
-e 's@Context.h>@Context.h"@' \
-i UI/MailerUI/UIxMailView.m

I included those changes in the PKGBUILD locally (just before configure) and it builds without error, but again, I'm a couple of days away from testing, and neither are the right way to fix the problem (if that is even the problem). Hopefully that helps rather than hurts.

kwirkie commented on 2013-06-24 18:27

Updated. I'm having issues with Mailer element functioning. Is anyone else on Arch Linux having this issue?