From dh at dotlan.net Thu Dec 1 00:19:11 2016 From: dh at dotlan.net (Daniel Hoffend) Date: Thu, 1 Dec 2016 00:19:11 +0100 Subject: [Kolab-devel] Kolab 16 for Debian In-Reply-To: <20161129214250.2eca2704@tbb-phenom.lan> References: <644de45d43c83fba9d72d1403d8cfb3c@mykolab.com> <20161125085753.6ce97afe@tbb-phenom.lan> <589B1FED-9025-4DB6-972B-50E2EBC087B1@dotlan.net> <20161129214250.2eca2704@tbb-phenom.lan> Message-ID: <20161130231911.GA9030@dotCarbon> Hi hede thanks for your answer, but I was more concerned about Jereons Call to get Kolab:16 for Debian tested and fixed. Therefore I was looking around what has changed in the last half year. In the end there hasn't changed much to be fair :-) Especially not the laggy OBS :-) I really haven't missed it. In the mean time I've already fixed couple packages in Kolab:16 and Winterfell which are already pushed through and live. At least a default Debian Installation should now go through without any major drawbacks. But there's still some packages and components missing to be feature complete compared to the Centos Release. -- Regards Daniel On 2016-11-29 21:42, hede wrote: > Am Sun, 27 Nov 2016 09:30:37 +0100 schrieb Daniel Hoffend : > > > What's the correct way to fix package bugs nowadays? Send patch requests to kolab16 in obs or winterfell or both or what? > > Good question. > > AFAIK there are 2 ways: > > 1: > - branch/fork the corresponding project/package in OBS[1] > - fix errors in your personal home project > - file a submit request to the upstream maintainer (within obs) > - the package maintainer will hopefully include your work > > [1] https://obs.kolabsys.com/ > > 2: Submit a patch in fabricator[2] > - create a task > - add your patch/diff to the task > - the upstream developer will hopefully include your work > > [2] https://git.kolab.org/ > > With way 1 you get your working packages in [3] (at least for AMD64). Incredibly handy for direct inclusion within some local kolab installation. With way 2 you'll better reach upstream developers. > > [3] http://obs.kolabsys.com:82/Kolab:/ > > regards > hede > _______________________________________________ > devel mailing list > devel at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/devel From mihai at badici.ro Sat Dec 17 13:59:22 2016 From: mihai at badici.ro (Mihai Badici) Date: Sat, 17 Dec 2016 14:59:22 +0200 Subject: [Kolab-devel] kolab and real-time communication (chat, etc) Message-ID: <2959613.nApXTaqCLu@slackware-14> It is a little bit ironic, but few days after we talk about the real time communication i had a request to install rocket chat for a company where I manage the servers ( and where, btw, I have kolab installed). So i configured the chat to use the ldap directory; I'm not so sure how the ldap integration is implemented but as i see this part is very basic. But that part can be improved if needed ( and maybe i can contribute here). This install give me the opportunity to update my knowledge in the real-time chat area ( I was not fully aware of how webrtc works in my previous message); well, probably is better first to read about the subject and then talk about but sometime it is not the case :) So, i have now, regarding kolab, a new dilemma : we can use webrtc to obtain peer to peer chat and voice; but we can have the case when somebody use the web client and the other one is on , let's say, pidgin, connected to the jabber server. How can we manage that? We need to bridge the webrtc protocol to the xmpp server somehow ... i think this is possible but there is some work /documentation about that? From kolab at klos2day.nl Thu Dec 22 16:29:37 2016 From: kolab at klos2day.nl (Paul Klos) Date: Thu, 22 Dec 2016 16:29:37 +0100 Subject: [Kolab-devel] Kontact/Kmail, Kolab and KF5 Message-ID: <6675953.rFA44nkyiu@apollo> Hi all, I'm running Gentoo on my desktop. Recently libkolab and libkolabxml were removed from the portage tree. I saved those ebuilds locally, so I still have them, but I expect it's going to get increasingly difficult keeping my Kmail with Kolab support running, especially since Kmail 16, built on KF 5 just hit the tree. I'd like, obviously, to keep my Kolab support in Kmail (akonadi) but I'd also like, and will probable need to at some point, upgrade to the latest and greatest Kmail. So, I have a few questions: - What's going to happen with libkolab(xml)? - Will these libs still be needed for local Kolab support in akonadi? - Is work being done porting Kolab support to KF5? - Can I help in any way? I hope someone closer to the core development can shed some light on the situation. Thanks, Paul From javitonino at gmail.com Sun Dec 25 01:22:57 2016 From: javitonino at gmail.com (Javier Torres) Date: Sun, 25 Dec 2016 01:22:57 +0100 Subject: [Kolab-devel] Kolab on Ubuntu 16.04: swig with support for PHP7 In-Reply-To: References: Message-ID: Hi! I have been playing around with the newest SWIG and PHP7 and I'm happy to report that it works without issue to me. I just had to update the libkolabxml CMakeLists.txt to pass `-php7` to swig (instead of `-php`) and recompile libkolabxml PHP bindings. After that I switched Apache to PHP7 and everything keeps working, but in PHP7. I tested the webadmin, chwala and all roundcube modules, and I detected no issues. All of the tests were performed in Arch Linux, using the AUR packages for Kolab. I already updated them to use PHP7 using swig from git master ( https://aur.archlinux.org/packages/php-kolabformat/). Happy to help if anyone wants to try it as well, Best, Javier On Wed, Nov 30, 2016 at 8:15 AM, Timotheus Pokorra wrote: > Hello all, > > following up on https://kanarip.wordpress.com/ > 2016/05/25/php-7-support-for-swig/ > > I have been following the issue on Github: > https://github.com/swig/swig/issues/571 > Now support for PHP7 has been merged into the master of swig! > > If anyone feels up to it, please can someone test that? > I won't have time for it anytime soon. > > Timotheus > _______________________________________________ > devel mailing list > devel at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From timotheus at kolab.org Tue Dec 27 15:57:11 2016 From: timotheus at kolab.org (Timotheus Pokorra) Date: Tue, 27 Dec 2016 15:57:11 +0100 Subject: [Kolab-devel] Kolab on Ubuntu 16.04: swig with support for PHP7 In-Reply-To: References: Message-ID: Hello Javier, > I have been playing around with the newest SWIG and PHP7 and I'm happy to > report that it works without issue to me. I just had to update the > libkolabxml CMakeLists.txt to pass `-php7` to swig (instead of `-php`) and > recompile libkolabxml PHP bindings. After that I switched Apache to PHP7 and > everything keeps working, but in PHP7. I tested the webadmin, chwala and all > roundcube modules, and I detected no issues. Thank you for working on this, and reporting on the success! I have been trying the same for Fedora 25, but I have issues with the PHP modules, causing php to segfault. See https://kolab.org/hub/topic/91/kolab-16-winterfell-on-ubuntu-16-04-dependencies/14 and https://github.com/swig/swig/issues/859 I will have to dig into this after the holidays. It is good to know that it works on Arch Linux. I wonder if my snapshot of Swig is a couple of commits too old, I will try that first to build with a more recent snapshot. All the best, Timotheus From javitonino at gmail.com Wed Dec 28 23:28:38 2016 From: javitonino at gmail.com (Javier Torres) Date: Wed, 28 Dec 2016 23:28:38 +0100 Subject: [Kolab-devel] Kolab on Ubuntu 16.04: swig with support for PHP7 In-Reply-To: References: Message-ID: Hi again Timotheus, I tried to run `php --version` and I'm seeing the same error (zend_mm_heap corrupted). However, in my case, it does not cause PHP to segfault, and all applications build and run nicely. I tried running valgrind, as suggested in the swig ticket and I am seeing some errors when loading the kolabformat extension that are not there without it, so there is definitely something going on here. If I had to guess, maybe PHP for Fedora is built with some flags that make it crash when encountering a corrupt heap, while in Arch it tries to continue. But anyway, something is wrong on the swig/libkolabxml side, so I'll try to look at the valgrind errors if I get the time. Best, Javier On Tue, Dec 27, 2016 at 3:57 PM, Timotheus Pokorra wrote: > Hello Javier, > > > I have been playing around with the newest SWIG and PHP7 and I'm happy to > > report that it works without issue to me. I just had to update the > > libkolabxml CMakeLists.txt to pass `-php7` to swig (instead of `-php`) > and > > recompile libkolabxml PHP bindings. After that I switched Apache to PHP7 > and > > everything keeps working, but in PHP7. I tested the webadmin, chwala and > all > > roundcube modules, and I detected no issues. > Thank you for working on this, and reporting on the success! > > I have been trying the same for Fedora 25, but I have issues with the > PHP modules, causing php to segfault. > See https://kolab.org/hub/topic/91/kolab-16-winterfell-on- > ubuntu-16-04-dependencies/14 > and https://github.com/swig/swig/issues/859 > I will have to dig into this after the holidays. > It is good to know that it works on Arch Linux. > I wonder if my snapshot of Swig is a couple of commits too old, I will > try that first to build with a more recent snapshot. > > All the best, > Timotheus > _______________________________________________ > devel mailing list > devel at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From babatoko at gmail.com Fri Dec 30 14:43:51 2016 From: babatoko at gmail.com (Martial Paupe) Date: Fri, 30 Dec 2016 14:43:51 +0100 Subject: [Kolab-devel] kolab 16 on armel architecture Message-ID: Hi, Hi there, I'm trying to compile kolab for armel architecture and i'm stuck on a build-dependency wich is univention-config-dev. How I can get that dependency resolved ? Where to find the source code to build up ? Thanks for all your clue! Babatoko -------------- next part -------------- An HTML attachment was scrubbed... URL: From machniak at kolabsys.com Fri Dec 30 15:38:31 2016 From: machniak at kolabsys.com (Aleksander Machniak) Date: Fri, 30 Dec 2016 15:38:31 +0100 Subject: [Kolab-devel] kolab 16 on armel architecture In-Reply-To: References: Message-ID: <3095f74d-b13f-81b9-a847-d2484d8cb020@kolabsys.com> On 12/30/2016 02:43 PM, Martial Paupe wrote: > I'm trying to compile kolab for armel architecture and i'm stuck on a > build-dependency wich is univention-config-dev. What exactly are you compiling and where did you get that dependency from? -- Aleksander Machniak Software Developer Kolab Systems AG: http://kolabsys.com PGP: 19359DC1 From babatoko at gmail.com Fri Dec 30 16:23:17 2016 From: babatoko at gmail.com (Martial Paupe) Date: Fri, 30 Dec 2016 16:23:17 +0100 Subject: [Kolab-devel] kolab 16 on armel architecture In-Reply-To: <3095f74d-b13f-81b9-a847-d2484d8cb020@kolabsys.com> References: <3095f74d-b13f-81b9-a847-d2484d8cb020@kolabsys.com> Message-ID: I'm building kolab and here is the control files header Source: kolab Section: mail Priority: extra Maintainer: Jeroen van Meeuwen (Kolab Systems) Uploaders: Paul Klos Build-Depends: debhelper (>= 8), univention-config-dev | bash (>= 1.0) Standards-Version: 3.9.6 Vcs-Browser: http://git.kolabsys.com/apt/kolab/ Vcs-Git: git://git.kolabsys.com/git/apt/kolab Homepage: http://www.kolab.org/ On 30 December 2016 at 15:38, Aleksander Machniak wrote: > On 12/30/2016 02:43 PM, Martial Paupe wrote: > > I'm trying to compile kolab for armel architecture and i'm stuck on a > > build-dependency wich is univention-config-dev. > > What exactly are you compiling and where did you get that dependency from? > > -- > Aleksander Machniak > Software Developer > Kolab Systems AG: http://kolabsys.com > PGP: 19359DC1 > _______________________________________________ > devel mailing list > devel at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From timotheus at kolab.org Fri Dec 30 20:12:25 2016 From: timotheus at kolab.org (Timotheus Pokorra) Date: Fri, 30 Dec 2016 20:12:25 +0100 Subject: [Kolab-devel] kolab 16 on armel architecture In-Reply-To: References: <3095f74d-b13f-81b9-a847-d2484d8cb020@kolabsys.com> Message-ID: Hello Babatoko, > univention-config-dev | bash (>= 1.0) I think the pipe means OR. So you need bash, and you should be fine without univention-config-dev. Timotheus From babatoko at gmail.com Fri Dec 30 20:33:34 2016 From: babatoko at gmail.com (Martial Paupe) Date: Fri, 30 Dec 2016 20:33:34 +0100 Subject: [Kolab-devel] kolab 16 on armel architecture In-Reply-To: References: <3095f74d-b13f-81b9-a847-d2484d8cb020@kolabsys.com> Message-ID: Hello Timotheus, Thanks for replying, Yes, I thought the same things when I read that statement. I've got of course bash in place, but the building failed just because it can't resolve univention-config-dev. So the OR statement not working. Is that dependence used for building UCS version ? Is it safe to remove that depedencie for my build? On 30 December 2016 at 20:12, Timotheus Pokorra wrote: > Hello Babatoko, > > > univention-config-dev | bash (>= 1.0) > > I think the pipe means OR. So you need bash, and you should be fine > without univention-config-dev. > > Timotheus > _______________________________________________ > devel mailing list > devel at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From timotheus at pokorra.de Fri Dec 30 21:29:44 2016 From: timotheus at pokorra.de (Timotheus Pokorra) Date: Fri, 30 Dec 2016 21:29:44 +0100 Subject: [Kolab-devel] kolab 16 on armel architecture In-Reply-To: References: <3095f74d-b13f-81b9-a847-d2484d8cb020@kolabsys.com> Message-ID: Hello Babatoko, > Thanks for replying, Yes, I thought the same things when I read that > statement. I've got of course bash in place, but the building failed just > because it can't resolve univention-config-dev. So the OR statement not > working. > > Is that dependence used for building UCS version ? Is it safe to remove that > depedencie for my build? Yes I think so. I checked the build log https://obs.kolabsys.com/package/live_build_log/Kolab:16/kolab/Debian_8.0/x86_64 it does not install any univention package. Which OS are you targetting? Is that in the generation of Debian Jessie, or older? Timotheus From timotheus at kolab.org Sat Dec 31 08:51:27 2016 From: timotheus at kolab.org (Timotheus Pokorra) Date: Sat, 31 Dec 2016 08:51:27 +0100 Subject: [Kolab-devel] Kolab on Ubuntu 16.04: swig with support for PHP7 In-Reply-To: References: Message-ID: Hello Javier, > If I had to guess, maybe PHP for Fedora is built with some flags that make > it crash when encountering a corrupt heap, while in Arch it tries to > continue. But anyway, something is wrong on the swig/libkolabxml side, so > I'll try to look at the valgrind errors if I get the time. Thank you for looking into this! The fix provided at https://github.com/swig/swig/issues/859 works for php -version, great! I still see a segfault when building kolab-freebusy, see https://github.com/TBits/lbs-kolab/blob/Kolab_16TestFedora25/kolab-freebusy/kolab-freebusy.spec#L80 this call fails: composer -vvv dumpautoload --optimize but the workaround with export USE_ZEND_ALLOC=0 solves it. And during setup-kolab and production operation, there is no issue anymore, as far as I can see. I have now packages for Fedora25, and they pass my nightly tests: http://www.pokorra.de/2016/12/kolab-16-for-fedora-25/ All the best, Timotheus From daniel.morlock at awesome-mail.de Thu Dec 22 17:08:14 2016 From: daniel.morlock at awesome-mail.de (Daniel Morlock) Date: Thu, 22 Dec 2016 16:08:14 -0000 Subject: [Kolab-devel] Kontact/Kmail, Kolab and KF5 In-Reply-To: <6675953.rFA44nkyiu@apollo> References: <6675953.rFA44nkyiu@apollo> Message-ID: <0f211571450109a7e78ae278c433af77@awesome-mail.de> Hi, we have an overlay with libkolab and libkolabxml here: https://gitlab.awesome-it.de/overlays/kolab/tree/master/net-libs Unfortunately, we drop the Gentoo support since the effort for maintaining the packages is too large. So the Kolab overlay is outdated but maybe you can use the libkolab/libkolabxml ebuilds. Regards, Daniel On 2016-12-22 16:29, Paul Klos wrote: > Hi all, > > I'm running Gentoo on my desktop. Recently libkolab and libkolabxml > were removed from the portage tree. I saved those ebuilds locally, so > I still have them, but I expect it's going to get increasingly > difficult keeping my Kmail with Kolab support running, especially > since Kmail 16, built on KF 5 just hit the tree. > > I'd like, obviously, to keep my Kolab support in Kmail (akonadi) but > I'd also like, and will probable need to at some point, upgrade to the > latest and greatest Kmail. > > So, I have a few questions: > > - What's going to happen with libkolab(xml)? > - Will these libs still be needed for local Kolab support in akonadi? > - Is work being done porting Kolab support to KF5? > - Can I help in any way? > > I hope someone closer to the core development can shed some light on > the situation. > > Thanks, > > Paul > _______________________________________________ > devel mailing list > devel at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/devel From daniel.morlock at awesome-it.de Thu Dec 22 17:18:47 2016 From: daniel.morlock at awesome-it.de (Daniel Morlock) Date: Thu, 22 Dec 2016 16:18:47 -0000 Subject: [Kolab-devel] Kontact/Kmail, Kolab and KF5 In-Reply-To: <6675953.rFA44nkyiu@apollo> References: <6675953.rFA44nkyiu@apollo> Message-ID: <7a03cbaeaedb71b27892531a41462605@awesome-mail.de> Hi, we have an overlay with libkolab and libkolabxml here: https://gitlab.awesome-it.de/overlays/kolab/tree/master/net-libs Unfortunately, we drop the Gentoo support since the effort for maintaining the packages is too large. So the Kolab overlay is outdated but maybe you can use the libkolab/libkolabxml ebuilds. Regards, Daniel On 2016-12-22 16:29, Paul Klos wrote: > Hi all, > > I'm running Gentoo on my desktop. Recently libkolab and libkolabxml > were removed from the portage tree. I saved those ebuilds locally, so > I still have them, but I expect it's going to get increasingly > difficult keeping my Kmail with Kolab support running, especially > since Kmail 16, built on KF 5 just hit the tree. > > I'd like, obviously, to keep my Kolab support in Kmail (akonadi) but > I'd also like, and will probable need to at some point, upgrade to the > latest and greatest Kmail. > > So, I have a few questions: > > - What's going to happen with libkolab(xml)? > - Will these libs still be needed for local Kolab support in akonadi? > - Is work being done porting Kolab support to KF5? > - Can I help in any way? > > I hope someone closer to the core development can shed some light on > the situation. > > Thanks, > > Paul > _______________________________________________ > devel mailing list > devel at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/devel