Package Details: sogo 4.0.2-1

Git Clone URL: (read-only)
Package Base: sogo
Description: groupware server built around (OGo) and the SOPE application server
Upstream URL:
Licenses: GPL
Replaces: sogo2
Submitter: DJ_L
Maintainer: deons
Last Packager: deons
Votes: 7
Popularity: 0.926644
First Submitted: 2016-05-05 01:05
Last Updated: 2018-09-01 08:53

Dependencies (16)

Required by (0)

Sources (4)

Latest Comments

1 2 3 4 Next › Last »

DJ_L commented on 2018-09-02 06:06

Also, if still happening, what happens with version mismatch? SOPE-4.0.2 with SOGo-4.0.1? Another, any customizations for WebUI?

DJ_L commented on 2018-09-01 15:31

Yes, Is it working for you now?

deons commented on 2018-09-01 09:12

I have updated package to 4.0.2

DJ_L that report that you found is the exact problem that I am having, thanks for sharing. Are you using LDAP for your authentication?

DJ_L commented on 2018-09-01 04:45

FYI, the most recent instance I can find is this:

DJ_L commented on 2018-09-01 04:32

I built with existing patches, updated only version, release, and sha256sums. I am not seeing the problem. I had not been using the web GUI and hadn't yet run the update script /usr/lib/sogo/scripts/, so I was getting the scrolling quick_update for the contacts list. Ran that script, and all was well with contacts view. My environment is per the current Arch wiki article, with Samba, MariaDB, Postfix, Dovecot, and Apache for the web server.

Where does the error occur, on the login screen, immediately after (MailerUI), or somewhere else?

Try and see if anything interesting in say 'journalctl -r -u sogo | head -n 100 | grep "ERROR" '

deons commented on 2018-08-31 08:45


This is the current error that I am trying to track down.

An error occurred during object publishing the requested object could not be found!

If I downgrade back to 4.0.1 then everything works as expected.

DJ_L commented on 2018-08-31 04:49

What kind of issues are you running into? I currently have a pending release for Saturday and my outstanding blockers will be done in about 10 minutes. Barring any major issues, I should have a few days available for Arch (CDT) if there is anything I can do to assist.

deons commented on 2018-08-29 07:23

Hi all,

I am aware sogo 4.0.2 is available, but in my testing I am experiencing problems when upgrading from 4.0.1 to 4.0.2. As soon as I have managed to resolve the problem I will upgrade this package.

DJ_L commented on 2018-08-07 22:09

The dependency on SOPE should be 'sope>=4.0.1' both to avoid this issue in the future, and just in general. The sogo package holds the dependency, a greater sope version is not very likely to cause an issue, especially since it is very likely that it'll be updated shortly after.

As to yauort, I don't use any of the AUR helpers personally, but can it not catch the error, see that sogo will be later in the queue, then force the installation in that instance? If that can be done, you can even make it record the missing dep and if the dep is not met later by build failure (or any other reason), then roll back the dependent package from cache.

deons commented on 2018-08-05 10:30

Hi schickel,

The only solution that I have for you at the moment is to first remove sogo then install it again. I am looking into solving this problem when using yaourt.