just reading through the various reports.
To summarize the situation:
Upgrading Kopano to 220.127.116.118 will make the entire system unusable
Old releases aren’t available, only to paying customers, the community edition is just as is, and always the nightly build with potential bugs/issues, up to being like now completely useless.
one year ago we’ve decided to move away from Zarafa to Kerio and Kopano, using Kopano for non-commercial users. Especially as Zarafa isn’t open source.
I do understand, that QA is time consuming, and you have to make a living as well. And bugs are always acceptable. But in this case - the entire system is broken, no way to recover.
In another thread - there was the kind hint to use the source. Tried this, downloaded, ./configure and ./make
python -external-runtime spooler/PythonSWIGRuntime.h
Unknown option: -e
usage: python [option] … [-c cmd | -m mod | file | -] [arg] …
So - what should we do now?
It is very risky to use the distribution. The shared sources aren’t usuable, so that in the end the only way to use Kopano is to pay for support to get access at least to packages aren’t broken. Not sure, if this is company policy to enforce people