Ebuilds for SOGo 1.1.0 and an Ebuild for the trunk (from their Monotone repository) version. Reproducible: Always
Created attachment 211987 [details] files/sogo.envd
Created attachment 211988 [details] files/sogod.confd
Created attachment 211990 [details] files/sogod.initd
Created attachment 211991 [details] files/sogod.initd-r3
Created attachment 211993 [details] sogo-1.1.0.ebuild SOGo 1.1.0 Ebuild
Created attachment 211994 [details] sogo-999999.ebuild SOGo trunk version
The older Ebuilds from the GNUstep overlay where to chaotic (IMHO) so I rewrote them completely. Both of them are now EAPI 2 Ebuilds. There are still some open issues with SOGo that need to be addressed upstream. All of the patches that I have posted here are as well submitted upstream. If you want then I can post links to each of them. Just let me know. I have not added any patches/information to the Ebuilds regarding documentation. The documentation is in some parts wrong. For example: If some one is using SQL for authentication then SOGoAuthenticationMethod should be set to LDAP regardless what the documentation is saying. Without setting it to LDAP the SQL authentication will not work. Their documentation is not mentioning that but you find that info in their mailing list. And, and, and... it's just a huge mess. And since Gentoo is using GNUstep make >= 2 things get even more complicated. I have submitted all the patches upstream but somehow they only care for Debian (which is using ancient gnustep make) and for Red Hat. All other distros (beside Ubuntu) do not seem to exist in SOGo land.
Thanks a lot for both reports! I'll try to review it ASAP. Does this give you a fully working SOGo? (apart from the documentation errors)
(In reply to comment #8) > Thanks a lot for both reports! I'll try to review it ASAP. > > Does this give you a fully working SOGo? (apart from the documentation errors) > YES! SOPE and SOGo are a PIA to set up. It took me days of testing and fiddling around with the whole build system to get it up and running. The whole build process they use is just a full mess. Errors all over the place. And then when I finally got it to compile I had issues installing it. Damn! Again fiddling around to get it to install the proper way. And after all that stress... still not working. Turned out that SOPE/SOGo is ultra sensitive when you have custom LDFLAGS (that's the reason I added those additional tests inside the Ebuild to help other Gentoo users to not run into the same issue as I did). But wait! That's not all! The code has issues as well. Agr! Just an example: using MySQL 5 with UTF8 and what do I see? They create a field with 256 characters and declare it as the primary key. BANG! MySQL can't make primary keys longer then 1000 bytes (and it seems that I am the first one to run into this. Yeah. I know. We are in 2009 and UTF8 is not something introduced a bunch of days ago. But what should I say?). When that happened the first time I did not understand the whole GNUstep stuff enough to find the error. But I did not give up and found error by error and fixed each of them to get SOGo up and running on Gentoo. Posting on their bug tracker is fruitless. The guys from Inverse are so overloaded that you don't get any response. Very frustrating. The guys from SOPE don't care much either. But anyway... here are now the Ebuilds and Gentoo users can with the help of those Ebuilds install very easy SOPE/SOGo. btw: Their new packages don't build the module for Apache. And I have not forced the build since I don't use Apache but nginx. IMHO we should make a separate Ebuild just for the Apache module. Nginx works flawless with SOGo. Just a bunch of rewrites and a proxy statement to SOGo and that's it. Fast, lean, sexy. Perfect! What does one want more?
(In reply to comment #8) > Thanks a lot for both reports! I'll try to review it ASAP. > > Does this give you a fully working SOGo? (apart from the documentation errors) > Did you had the chance to test both ebuilds? Any feedback/news?
Created attachment 213053 [details] sogo-1.1.0.ebuild
Created attachment 213054 [details] sogo-999999.ebuild
Created attachment 215656 [details] gnustep-apps/sogo/sogo-999999-r2.ebuild
Created attachment 215657 [details] gnustep-apps/sogo/sogo-1.1.0-r1.ebuild
Created attachment 215659 [details] gnustep-apps/sogo/files/sogod.initd-r4
(In reply to comment #8) > Thanks a lot for both reports! I'll try to review it ASAP. > > Does this give you a fully working SOGo? (apart from the documentation errors) > btw: Here another user that was/is able to build SOPE and SOGo with the help of the Ebuilds -> http://bugs.gentoo.org/show_bug.cgi?id=295634#c47 Would be really nice if you could look at the Ebuilds and if possible push them to the GNUstep overlay. IMHO they are on par (if not better since they handle so many cases that the old Ebuilds don't do) with the older Ebuilds for SOPE/SOGo. I hate to see them lurking here in b.g.o for months without status change. It makes me feel to have wasted so much time on building them and un-bugging both apps only to see them being not widely used. Give me at least some feedback about their progress and what else you need me to fix in order to get them in the GNUstep overlay.
Steve, The new ebuild it'ok.No problem to build it.Still a problem with init.d script samba init.d # /etc/init.d/sogod start * Starting SOGo service ... /sbin/start-stop-daemon: unrecognized option '--stdout' Try `/sbin/start-stop-daemon --help' for more information. [ !! ] The file sogod is not copied in to /etc/conf.d Sogo needs apache to be compiled with proxy and proxy_balancer module, so is needed a patch for this. and add -D PROXY in conf.d/apache Also sogo need SOGo.conf for apache With a little work it will be ready soon I guess
Created attachment 215711 [details] /etc/apache2/modules.d/50_mod_proxy.conf
Created attachment 215713 [details] The SOGo configuration file for Apache
Thanks to Steve the ebuild it's working. I already synced Thunderbird addresbook and read my email with sogo
Created attachment 215717 [details] The SOGo configuration file for Apache
> Still a problem with init.d script > > samba init.d # /etc/init.d/sogod start > * Starting SOGo service ... > /sbin/start-stop-daemon: unrecognized option '--stdout' > Try `/sbin/start-stop-daemon --help' for more information. [ !! > ] > Okay. This tells me you are using the 1.1.0 Ebuild and not the 999999 Ebuild. Right? > The file sogod is not copied in to /etc/conf.d > Need to check that. > Sogo needs apache > That is not true. I have no Apache installed and am running SOGo. I use nginx instead of Apache. > to be compiled with proxy and proxy_balancer module, so is > needed a patch for this. > Who needs a patch for this? SOGo? > and add -D PROXY in conf.d/apache > > Also sogo need SOGo.conf for apache > > With a little work it will be ready soon I guess > Aha. Now I see. Yes. If you go with Apache then you need to configure it in order to be able to act as an Proxy / Load Balancer.
(In reply to comment #21) > Created an attachment (id=215717) [details] > The SOGo configuration file for Apache > This is not needed. It is already the standard in Gentoo Apache to have those settings in httpd.conf. The only thing needed is to add "-D PROXY" to APACHE2_OPTS in /etc/conf.d/apache2
(In reply to comment #17) > The file sogod is not copied in to /etc/conf.d > That is right for the SOGo 1.1.0 Ebuilds. The SOGo 999999 Ebuild is only using that file. The 1.1.0 Ebuild and init.d script does not need nor use that file.
Created attachment 215761 [details] gnustep-apps/sogo/files/sogod.initd
Created attachment 215762 [details] gnustep-apps/sogo/sogo-1.1.0-r2.ebuild
Created attachment 215764 [details] gnustep-apps/sogo/sogo-999999-r3.ebuild
The new Ebuilds do now install an Apache configuration as a document and the init.d script for the 1.1.0 branch now does not use any more the option "--stdout" for the log.
Created attachment 215766 [details] gnustep-apps/sogo/sogo-999999-r3.ebuild Fixed an error in the Ebuild with newdoc.
Created attachment 215767 [details] gnustep-apps/sogo/sogo-1.1.0-r2.ebuild Fixed an error in the Ebuild with newdoc.
(In reply to comment #22) > Okay. This tells me you are using the 1.1.0 Ebuild and not the 999999 Ebuild. > Right? Right > That is not true. I have no Apache installed and am running SOGo. I use nginx > instead of Apache. You're right > Aha. Now I see. Yes. If you go with Apache then you need to configure it in > order to be able to act as an Proxy / Load Balancer. Yes
(In reply to comment #23) > The only thing needed is to add "-D PROXY" to APACHE2_OPTS in > /etc/conf.d/apache2 ok
Created attachment 215786 [details] gnustep-apps/sogo/sogo-999999-r3.ebuild Added note about configuring Apache for SOGo.
Created attachment 215788 [details] gnustep-apps/sogo/sogo-1.1.0-r2.ebuild Added note about configuring Apache for SOGo.
The attachment 50 [details]_mod_proxy.conf is not needed because the Ebuild installs now an example SOGo-Apache.conf.
(In reply to comment #16) Delay in reviewing is caused by the usual: me being the only one working on this, other Gentoo (NX,ftp,chromium,...) taking time, real life (especially in december), ... you name it! But your work is definitly much much appreciated, even if progress on my part can be slow sometimes :/ As I don't think I'll have time soon to really check this, I've juste cleaned a few lines and added the ebuild as 1.1.0-r1 in the gnustep overlay Same remarks as sope ebuild btw, also I've dropped env.d file, as it sets the same paths as sope env file (also sope env file would be better if dnynamically generated in the ebuild from the real current gnustep environment)
(In reply to comment #36) > (In reply to comment #16) > Delay in reviewing is caused by the usual: me being the only one working on > this, other Gentoo (NX,ftp,chromium,...) taking time, real life (especially in > december), ... you name it! But your work is definitly much much appreciated, > even if progress on my part can be slow sometimes :/ > > As I don't think I'll have time soon to really check this, I've juste cleaned a > few lines and added the ebuild as 1.1.0-r1 in the gnustep overlay > Same remarks as sope ebuild btw, also I've dropped env.d file, as it sets the > same paths as sope env file (also sope env file would be better if dnynamically > generated in the ebuild from the real current gnustep environment) > Thanks for the feedback. One issue however. SOPE must be build with LDAP else SOGo will not work. So you should have this in the Ebuild: DEPEND="gnustep-libs/sope[ldap,mysql?,postgres?]
Thanks, fixed! I had made it conditional to test the compilation, and forgot to revert it.
Created attachment 216233 [details] gnustep-apps/sogo/sogo-999999.ebuild Processing feedback from Bernard Cafarelli.
Created attachment 216234 [details] gnustep-apps/sogo/sogo-1.1.0.ebuild Processing feedback from Bernard Cafarelli.
I think those bug reports should be changed to only include the live Ebuilds.
(In reply to comment #38) > Thanks, fixed! I had made it conditional to test the compilation, and forgot to > revert it. > No problem. We make a good team :)
Same as sope, -9999 is in overlay too now. Thanks a lot for your hard work, next stop after gnustep-make is fixed, move it in tree :)
(In reply to comment #43) > Same as sope, -9999 is in overlay too now. Thanks a lot for your hard work, > next stop after gnustep-make is fixed, move it in tree :) > Looks okay to me. I am now going to close this bug report.
