Re: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT
Did we ever get an *update* to the SOGo/Openchange question? On 03/24/2015 05:19 PM, Ludovic Marcotte wrote: On 24/03/2015 14:27, Scott Jordahl wrote: Me too. I have 3+ clients that are still on Outlook 2007/2010 that I'm still waiting to upgrade I *should* have an update in the 24 hours about this. Thanks! -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT
thanks, by the way, for answering my question . . . I appreciate all you (and Inverse) do! On 03/24/2015 12:54 PM, Ludovic Marcotte wrote: On 23/03/2015 13:17, Steve Ankeny wrote: Does that mean waiting until September? http://openchange.org/developers/roadmap.html That page is based on this: https://github.com/openchange/website/blob/master/src/developers/roadmap.md Which was modified 8 months ago - so I guess it was initially targeted for September 2014. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT
Me too. I have 3+ clients that are still on Outlook 2007/2010 that I'm still waiting to upgrade On 03/24/2015 10:09 AM, Steve Ankeny wrote: ok, I guess the frustration mounts . . . When will we be able to use ocsmanager/rpcproxy? When will support resume for Debian, pg. 14 note? On 03/24/2015 12:54 PM, Ludovic Marcotte wrote: On 23/03/2015 13:17, Steve Ankeny wrote: Does that mean waiting until September? http://openchange.org/developers/roadmap.html That page is based on this: https://github.com/openchange/website/blob/master/src/developers/roadmap.md Which was modified 8 months ago - so I guess it was initially targeted for September 2014. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT
Does that mean waiting until September? http://openchange.org/developers/roadmap.html On 03/19/2015 11:45 AM, Ludovic Marcotte wrote: On 19/03/2015 10:38, Ozy de Jong wrote: - Openchange server 2.3 current GIT This is of course unreleased - and if you want to use openchange from git, you must also apply this patch: https://github.com/inverse-inc/sogo/pull/65.diff It might not apply cleanly. The best thing to do is to wait until OpenChange v2.3 is released. Then the SOGo-OpenChange backend will be updated and all the related stuff. Thanks, -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT
On 23/03/2015 13:17, Steve Ankeny wrote: Does that mean waiting until September? http://openchange.org/developers/roadmap.html That page is based on this: https://github.com/openchange/website/blob/master/src/developers/roadmap.md Which was modified 8 months ago - so I guess it was initially targeted for September 2014. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT
ok, I guess the frustration mounts . . . When will we be able to use ocsmanager/rpcproxy? When will support resume for Debian, pg. 14 note? On 03/24/2015 12:54 PM, Ludovic Marcotte wrote: On 23/03/2015 13:17, Steve Ankeny wrote: Does that mean waiting until September? http://openchange.org/developers/roadmap.html That page is based on this: https://github.com/openchange/website/blob/master/src/developers/roadmap.md Which was modified 8 months ago - so I guess it was initially targeted for September 2014. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT
On 24/03/2015 14:27, Scott Jordahl wrote: Me too. I have 3+ clients that are still on Outlook 2007/2010 that I'm still waiting to upgrade I *should* have an update in the 24 hours about this. Thanks! -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT
Am 19.03.2015 um 15:38 schrieb Ozy de Jong: Hello, I've been working on getting SOGO and Openchange to work on RHEL / CentOS 7. What i have successfully compiled yet and should work: - Samba 4 DC with Heimdal Kerberos - Openchange server 2.3 current GIT - SOPE 4.9.2 current GIT - Sogo 2.2.16 current GIT The samba domain runs, the openchange schema has been provisionned, users can be added and mapi profiles work. There's only the Openchange client included with sogo which i can't get to compile. I guess it's because the code is supposed to work with Samba 4.1.11 and not 4.1.17, can anyone confirm this considering the following compile errors ? This is gnustep-make 2.6.6. Type 'make print-gnustep-make-help' for help. Python executable: /usr/bin/python Making all for bundle SOGoBackend... Compiling file MAPIStoreContext.m ... MAPIStoreContext.m: In function â+[MAPIStoreContext listAllContextsForUser:withIndexing:inMemCtx:]â: MAPIStoreContext.m:127:42: erreur: expected expression before âvoidâ DLIST_CONCATENATE(list, current, void); ^ MAPIStoreContext.m: In function â-[MAPIStoreContext getNewChangeNumber]â: MAPIStoreContext.m:552:3: erreur: too few arguments to function âopenchangedb_get_new_changeNumberâ if (openchangedb_get_new_changeNumber (connInfo-oc_ctx, newVersionNumber) ^ In file included from MAPIStoreContext.m:57:0: /usr/local/samba/include/libmapiproxy.h:202:17: note: declared here enum MAPISTATUS openchangedb_get_new_changeNumber(struct openchangedb_context *, const char *, uint64_t *); ^ MAPIStoreContext.m: In function â-[MAPIStoreContext getNewChangeNumbers:]â: MAPIStoreContext.m:571:43: erreur: too few arguments to function âopenchangedb_get_new_changeNumbersâ memCtx, max, numbers) ^ In file included from MAPIStoreContext.m:57:0: /usr/local/samba/include/libmapiproxy.h:203:17: note: declared here enum MAPISTATUS openchangedb_get_new_changeNumbers(struct openchangedb_context *, TALLOC_CTX *, const char *, uint64_t, struct UI8Array_r **); ^ make[3]: *** [obj/SOGoBackend.obj/MAPIStoreContext.m.o] Erreur 1 make[2]: *** [internal-bundle-run-compile-submake] Erreur 2 make[1]: *** [SOGoBackend.all.bundle.variables] Erreur 2 make: *** [internal-all] Erreur 2 According to the openchange wiki, the current 2.3 HEAD can be compiled against any Samba 4.1.x release. So if the sogo openchange connector won't compile because of my Samba version 4.1.17, then i'd try to recompile too with 4.1.11. My goal is to make some samba and openchange server rpms for x64 that would be compatible with future SOGO EL7 releases. Any look into this compile error would be appreciated. Regards, Ozy. Hallo Ozy, try this patch. It helps me to compile the OpenChange part of SOGo. -88888--- diff -uNr a/OpenChange/GNUmakefile b/OpenChange/GNUmakefile --- a/OpenChange/GNUmakefile--2015-02-12 17:13:15.0 +0100 +++ b/OpenChange/GNUmakefile--2015-02-21 11:03:41.497106361 +0100 @@ -171,7 +171,7 @@ $(LIBMAPISTORE_LIBS) ADDITIONAL_INCLUDE_DIRS += \ - -Werror -Wall \ + -fobjc-exceptions -Wall \ -DSAMBA_PRIVATE_DIR=@\$(SAMBA_PRIVATE_DIR)\ \ $(LIBMAPI_CFLAGS) \ $(LIBMAPISTORE_CFLAGS) \ -88888--- Greetings Sven -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT
On 19/03/2015 10:38, Ozy de Jong wrote: - Openchange server 2.3 current GIT This is of course unreleased - and if you want to use openchange from git, you must also apply this patch: https://github.com/inverse-inc/sogo/pull/65.diff It might not apply cleanly. The best thing to do is to wait until OpenChange v2.3 is released. Then the SOGo-OpenChange backend will be updated and all the related stuff. Thanks, -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
RE: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT
Hi Sven, I was able to sort that out without a patch, making usage of the following build command: PYTHONPATH=/usr/lib64/python2.7/site-packages/:/usr/local/samba/lib64/python2.7/site-packages make CPPFLAGS=-w I guess it's more or less the same, but thanks, this might make things more automatic. Regards, Ozy. Hallo Ozy, try this patch. It helps me to compile the OpenChange part of SOGo. -88888--- diff -uNr a/OpenChange/GNUmakefile b/OpenChange/GNUmakefile --- a/OpenChange/GNUmakefile--2015-02-12 17:13:15.0 +0100 +++ b/OpenChange/GNUmakefile--2015-02-21 11:03:41.497106361 +0100 @@ -171,7 +171,7 @@ $(LIBMAPISTORE_LIBS) ADDITIONAL_INCLUDE_DIRS += \ - -Werror -Wall \ + -fobjc-exceptions -Wall \ -DSAMBA_PRIVATE_DIR=@\$(SAMBA_PRIVATE_DIR)\ \ $(LIBMAPI_CFLAGS) \ $(LIBMAPISTORE_CFLAGS) \ -88888--- Greetings Sven -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
RE: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT
Patch 65.diff works great, applied without problems, and compiles well, thanks ! I'll now have to investigate usage, and see if there are any downpits using CentOS 7. Once this is done, i'll make some samba RPMs so whenever openchange 2.3 gets released and the PR #65 merged into sogo, there will be a possibility to use RHEL 7 / CentOS 7. Thanks. -Message initial- De:Ludovic Marcotte lmarco...@inverse.ca Envoyé: jeudi 19 mars 2015 16:45 À: users@sogo.nu Sujet: Re: [SOGo] Compiling SOGO / Openchange Connector against Samba 4.1.17 and Openchange 2.3 GIT On 19/03/2015 10:38, Ozy de Jong wrote: - Openchange server 2.3 current GIT This is of course unreleased - and if you want to use openchange from git, you must also apply this patch: https://github.com/inverse-inc/sogo/pull/65.diff It might not apply cleanly. The best thing to do is to wait until OpenChange v2.3 is released. Then the SOGo-OpenChange backend will be updated and all the related stuff. Thanks, -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
