In the nethforge-testing repository are (self build) packages for SOGo 3.2.0 4.
It are strait-forward un-patched builds against epel-7, Sope is a build dependency of Sogo.
Still struggling with the release tag of sope as described here
They need testing!
To update: yum upgrade --enablerepo=nethforge-testing sogo* sope*
One issue i have encountered once is sending mail from firefox did not work. Emptying the cache of firefox fixed it.
Thanx in advance!
EDIT: bumped to 3.2.4 Note: The netserver-sogo package it self is still WIP, and not included in this testing-update.
hey mark,
have installed the 3.2 and everything seems to be good. No probs with access, also active sync works well, will give you a shout if i got something what does not work. have a great day !
well i fix it with the information from you, so again thanks for that and for you in the case “testing 3.2” also the active sync works with your workaround on 3.2
It seems to be memcached or httpd, sogod restarts the after update. memcached should clear its cache, not sure if it does. Httpd should see the webresources are new, we give them a new timestamp while updating.
Still looking in to this.
This works for me, instead! And no display artifacts, too, on Firefox 49.0.2. Perhaps you’ve cached an older stylesheet or Javascript? They updated AngularJS between 3.0 and 3.2 IIRC.
I think so: I did a fresh installation of Nethserver 7rc1, did upgrades in Software center, installed several packages including Sogo Groupware. Then, I’ve issued yum upgrade --enablerepo=nethforge-testing sogo* sope* as per your instructions to upgrade to 3.2.0.
I’m going to do some tests on a single core VM this afternoon/evening, i have a hunch SOGo tries to spawn multiple workers and this could cause troubles on a single core. (just thinking out loud here, i’ll report back)
In this case you did not update the nethserver-sogo package, you don’t need to.
ahah: now get your question, yes it’s 644 by design and i am going to solve this in the new nethserver-sogo package.
We need group read permissions for the the sogo group for easy use of sogo-tool. sogo.conf should be owned by root:sogo, others should not have read permissions.