[Pkg-giraffe-discuss] workaround to get zarafa-7.2.0 build?

Carsten Schoenert c.schoenert at t-online.de
Mon Jun 15 20:23:28 UTC 2015


Hello Guido,

Am 15.06.2015 um 09:24 schrieb Guido Günther:
> Hi Carsten,
> On Sun, Jun 14, 2015 at 09:32:38PM +0200, Carsten Schoenert wrote:
>> If started to pick up the latest beta release from Zarafa,
>> zarafa-7.2.1-49597.tar.gz.
>> You added a branch upstream/7.2 into gbp.conf which doesn't exist right
>> now. It would be surly the current branch, but from which commit we
> 
> I missed to push that one (which I cloned originally from Matthias
> repo). Pushed now, sorry for the mess up.

no problem at all. The branch starts exactly there I have started it
too. So nothing to rework for me.

So as written I have imported Guidos WIP branch and made some more small
commits before I was importing the beta release 7.2.1 by Zarafa. Mark
has written in another private Mail that most of the spelling errors,
rpath issues and soname issues are fixed in the current development.

The warning about apache2-deprecated-auth is a false positive I think,
the apache configuration contains a part for !mod_athz_core.c which is
true for apache 2.2, so the apache configuration is right to be usable
on apache 2.2 and 2.4.

http://blog.plee.me/tag/mod_authz_core/

I pushed the whole stuff to

  https://github.com/tijuca/Giraffe

-- 
Regards
Carsten Schoenert



More information about the Pkg-giraffe-discuss mailing list