Differences between revisions 29 and 31 (spanning 2 versions)
Revision 29 as of 2015-04-25 22:58:56
Size: 3322
Revision 31 as of 2015-04-27 05:17:24
Size: 3439
Comment: Adding hint to maintaining ML
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
 * Mailing List: https://lists.alioth.debian.org/mailman/listinfo/pkg-giraffe-discuss  * Mailing List (Discussing): https://lists.alioth.debian.org/mailman/listinfo/pkg-giraffe-discuss
 * Mailing List (Maintaining/Packaging): https://lists.alioth.debian.org/pipermail/pkg-giraffe-maintainers
Line 18: Line 19:
 * repackage [[http://www.vmime.org/|libvmime]] (removed from Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774306 , gcrypt bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638651)  * repackage [[http://www.vmime.org/|libvmime]] (removed from Debian DebianBug:774306, gcrypt bug DebianBug:638651)
Line 51: Line 52:
 * Package webapp (which seems possible since it is AGPL3, too).
 * !WebApp tarball ships jQuery, extjs (3.4) and TinyMCE 4.0. (TinyMCE does not seem to be in the debian repositories)
 * 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. (DebPkg:TinyMCE is --(does not seem to be)-- in the Debian repositories)

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 Debconf to generate the initial configuration
    • database name
    • database user
    • database login
    • place of the database (local or remote)
    • more needed?
  • 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
  • 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, but for all packages)
  • check pre-/postinstall scripts
  • z-push upstream update
  • do not run as UID 0 (problematic for zarafa-search, otherwise it is configurable in the config files)


  • 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)

    • Lintian is complaining about jquery-1.6.2.min.js, player.swf, moxieplayer.swf, ext-{base,all}.js, prettify.js

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


We have currently a re branded artwork made by René Heinen. The graphics are used inside the web application.

The main login window.


The graphic on the left side on top.