Package Details: kopano-core 8.6.1-7

Git Clone URL: https://aur.archlinux.org/kopano-core.git (read-only, click to copy)
Package Base: kopano-core
Description: Open Source Groupware Solution
Upstream URL: https://www.kopano.com/
Licenses: AGPL3
Replaces: zarafa-server, zarafa-server-arm
Submitter: martimcfly
Maintainer: martimcfly
Last Packager: martimcfly
Votes: 6
Popularity: 0.000000
First Submitted: 2018-05-30 22:36
Last Updated: 2018-09-03 15:32

Dependencies (56)

Sources (2)

Latest Comments

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

martimcfly commented on 2016-01-05 17:34

Hey Jelly!

Thank's for that information! I'll set the php dependency below v7.

After compilation I regularly add all direct and transitiv dependencies to my archlinux repository. So hopefully everybody's able to install and run this package ;)

Marti

jelly commented on 2016-01-04 19:11

Note that PHP7 is not going to happen soon since the whole PHP extension needs to be ported to a whole new C API. I can't really provide an estimate when it's finished.

martimcfly commented on 2015-07-01 14:20

gcc 5 is breaking the zarafa configure script and the compiled result.

=> You'll need to install gcc4 from Archlinux Rollback Maschine:

http://seblu.net/a/arm/2015/06/01/core/os/

=> Or build and install gcc4 with gcc5 for arm from repo

git clone https://github.com/archlinuxarm/PKGBUILDs.git
cd PKGBUILD
git checkout b1884b6d1950422a32f9ced0be6d5492e4315547


jelly commented on 2015-04-29 19:37

Also notice that you will have to change your SSL settings https://community.zarafa.com/pg/blog/read/28319/zcp-7112-final

jelly commented on 2015-04-29 19:36

Just noticed the package was out of date. I've updated it to 7.1.12. I am not sure if people are interested in updating to 7.2.0 yet, but I have to package the new search and make it somehow work with the current python-{daemon,lockfile}.

rolek commented on 2014-12-18 08:33

We're running Zarafa on Slackware and we have the same problem. We've seen that the problem occurs a lot less often if we ensure no connections are made to the zarafa-server process before it is fully started. So, our Zarafa startup procedure now looks like:
- Stop postfix
- Disable access to the unix socket**
- With iptables, drop incoming traffic to ports 236 and 237
- Start zarafa-server
- Wait for 10 seconds
- Start the other zarafa daemons
- Allow incoming traffic to ports 236 and 237
- Allow access to the unix socket
- Start postfix

** On our system, the socket path is /var/run/zarafa/zarafa, so this is easily done by changing the access right on the /var/run/zarafa dir. On Arch, this might be different.

I hope this is useful to you.

jelly commented on 2014-11-03 19:03

Got the same problem here, not sure what the issue is. Looking into it with upstream :-)

martimcfly commented on 2014-10-29 17:54

On ARM 7.1.11 just exited right after start. That's why I didn't integrate it.

sushifrick commented on 2014-10-29 16:06

Does anyone else have the problem, that the zarafa-server deamon dies quite often since the last update?

"Caught SIGABRT (6), out of memory or unhandled exception, traceback"

It also happens, when there is plenty of memory left (>2GB), using loglevel 5 does not give me any extra information.

I tried increasing some cache sizes in the server.cfg but without any luck. zarafa-stats shows me there should be enough cache size left.

martimcfly commented on 2014-10-02 14:48

You can contribute to this package: https://git.pietma.com/pietma/com-pietma-zarafa