Differences between revisions 38 and 39
Revision 38 as of 2015-06-02 16:54:02
Size: 6479
Comment: hrhr, fixing some code source code markup
Revision 39 as of 2015-06-02 16:57:47
Size: 6390
Comment: libvmime is repackaged and now within the repos
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
== To Do ==
Line 19: Line 18:
 * repackage [[http://www.vmime.org/|libvmime]] (removed from Debian DebianBug:774306, gcrypt bug DebianBug:638651)
  * ITP DebianBug:783603
 * repackage done [[http://www.vmime.org/|libvmime]]
Line 23: Line 21:
== To Do ==

Packaging Giraffe

Giraffe is the free open source variant of the Zarafa Collaboration Platform packaged for Debian.


Current State

The packages are not available by the Debian repositories, the packaging process is not yet finished.


To Do

zarafa-server, ...

  • import upstream version 7.2.0 (./)

  • Fix Lintian errors and warnings
  • Review and forward patches against libical (and libvmime, see above) on upstream. For now it seems we can run with the versions of the revitalized package.

  • Move dlopen'ed libs to private directory
  • Remove embedded copies of fckeditor via the dfsg-clean branch in git, (use fckeditor package)

    • To be re done with version 7.2
  • Use dbconfig-common/Debconf to generate the initial configuration (./)

    • database name
    • database user
    • database login
    • place of the database (local or remote)
  • Use dbconfig-common to generate the initial database configuration

    • installing zarafa-server breaks without this (./)

    • zarafa-server shouldn't create the database on it owns (it needs to much mysql rights for this -> CREATE DATABASE is needed)

      • we can do the creation of the database by dbconfig-common and the setup of zarafa-server by the postinst script

  • Test full functionality
    • We'd need some Outlook users here, too...
  • fix init script
    • systemd compatibility
    • error out when database is missing
    • often hangs on stop
  • systemd unit
  • clean up packages (empty packages etc.)
  • MTA integration
  • check package descriptions
  • logrotate (upstream available in installer/linux/zarafa.logrotate, put in zarafa-common, split it per package)
  • check pre-/postinstall scripts: they do no error handling, don't include debhelper snippets
  • z-push upstream update
  • do not run as UID 0 (problematic for zarafa-search, otherwise it is configurable in the config files)
  • zarafa-client:
    • Rename zarafa-client to libzarafa-client since it contains no client programs
    • make libzarafaclient a proper versioned shared lib (or a private one)
  • zarafa-libarchiver: rename to libzarafa-archiver
  • zarafa-common: kill it with fire, no useful parts


  • Package webapp (which seems possible since it is AGPL3, too). prepared git repo: https://github.com/tijuca/zarafa-webaccess

  • WebApp tarball ships jQuery, extjs (3.4) and TinyMCE 4.0. (TinyMCE is does not seem to be in the Debian repositories, but to old)

    • Lintian is complaining about
      • jquery-1.6.2.min.js (./) (removed and symlinked to libjs-jquery)

      • player.swf and moxieplayer.swf (asked Upstream if this is removable)
      • ext-{base,all}.js, prettify.js (./) (removed and symlinked to libjs-extjs libjs-jac libjs-prettify)

      • tinymce (currently overriden as Debian version is to old)

The origin of this list is provided by GuidoGünther in https://honk.sigxcpu.org/piki/agx/publications/2011-06-debian-groupware-zs.pdf

Using KVM for testing

You probably wont use your current system to test the zarafa packages and that's a good idea so far. KVM is a good alternative for testing because it's supporting snapshot mechanism for easy using and resetting of installations.

Installing needed KVM components

Installation is easy as it's simply a oneliner.

$ sudo apt-get install qemu-kvm libvirt-bin bridge-utils virt-manager virtinst

Further preparations

After this ensure you are a member of the group 'libvirt'

$ sudo usermod -aG libvirt [YOUR_USERNAME]

The virtual network adapter inside the libvirt environment is disabled per default so befor to continue start it.

$ virsh -c qemu:///system net-autostart default

The next calls maybe not really needed, but on the other hand it's no problem if the storage pools allreday up, so just to throw possible issues away.

$ virsh -c qemu:///system pool-start default
$ virsh -c qemu:///system pool-start boot-scratch

Installation of a virtual image

After the finishing of the preparation from above you can install a first image. The installation can be as known done fully automated by a preseed file, Guido has prepared file preseed.cfg. Download the file for example to the 'Downloads' folder within your home directory.

$ wget -P $HOME/Downloads http://honk.sigxcpu.org/projects/libvirt/preseed/preseed.cfg

Next you can set up a install, for example based on the Jessie release amd64 and named jessie-amd64-zarafa.

$ RELEASE=jessie
$ NAME=zarafa
$ DIST=amd44
$ virt-install --connect=qemu:///system \
               --location=http://ftp.us.debian.org/debian/dists/$RELEASE/main/installer\-$DIST \
               --initrd-inject=$HOME/Downloads/preseed.cfg \
               --extra-args="auto" \
               --name $RELEASE-$DIST-$NAME --ram=512 \

This will install a image named 'jessie-amd64-zarafa.qcow2' with a size of 10GB under /var/lib/libvirt/images/. After the install the image will boot automatically.

Usage of KVM images

to fill out


We have currently a re branded artwork made by René Heinen. With the change of the parts for redistribution license this is not needed any longer. Just for completeness.

The main login window.


The graphic on the left side on top.