[Pkg-giraffe-discuss] update/how to proceed?

[Guido Günther]

Hi Mark!

Welcome back!

On Sun, May 31, 2015 at 08:50:27PM +0200, Mark Dufour wrote:
[..snip..]
> -the SCM mentioned on the wiki does not seem to have recent commits? where can we find your 'master' branch? (based on our 7.2..?)

I think the most up to date stuff is currently in my github repo (if
nobody else forked it yet and pushed patches on top of it) on the master
branch:

    git at github.com:agx/zarafa-debian.git

I'd be happy to push this over to alioth. Matthias, Carsten, any objections?

> -would it be possible to divide the issues on the wiki into essential
> and nice-to-have? for example, complete systemd support might be quite
> some effort, but is it absolutely needed for a first version? would it
> be enough for now to just be 'compatible'..?

I think we're mostly done. I vaguely remember that I wanted to be able
to rerun autoreconf to update to a newer libtool. This is more
complicated than it should be since there are missing lots of "if !
OSS_ONLY" in the Makefile.ams, seems it got never tested in the OSS so I
drifted to other projects. From what I remember before a upload we
should fix:

* Running autoreconf
* Libraries need to have proper sonames or be moved to a private dir
* zarafa-client needs to be renamed to libzarafa-client-<soname> since
  it's a library package
* The daemon must not run as root per default
* zarafa-webaccess.postinst needs to get the same care as -server did
  (don't overwrite user data, don't do stuff there that can be done via dh_*)
* We should really switch to the dh sequencer before doing the upload
  but that should be relatively simple once we have everything else in place
* Stopping the zarafa server didn't work reliably in Essen. 
 
> -which of the issues would be hard or annoying to solve for a non zarafa developer?

The autoreconf stuff but having the zarafa-client package renamed
upstream would help too. Having a look at the stop issue would be good
too.

> -which of the (necessary) issues could be considered the nastiest to
> solve?

I think it's mostly busy work and lots of testing. Nothing too nasty
that I can see from here.

> -it looks like some of you are actually looking into packaging webaccess (not webapp). my personal thought about this is (and I've mentioned this before here): please drop it. because it's end-of-life and webapp is its successor..

Not having webaccess is o.k. but I think there's little point in
uploading it until we have a proper alternative working GUI packaged
then.

> -in a similar vain, outlook is still mentioned on the wiki, while we
> are also dropping support for it in the near term (at least, using the
> current plugin method).

I don't care about Outlook but shouldn't we then remove all the MAPI
stuff as well?

> I'd personally love to put in quite a bit of time over the next two
> weeks or so to help solve issues. I just installed jessie in a VM and
> am looking forward to running your build and start looking around. if
> anyone on the debian side also has time, please contact me or let's
> talk in #debian-groupware.

Great! Knock your self out! Catch me on #debian-groupware in case of any
questions. We also need to sort out how to handle long term maintenance
of the package. 

Cheers,
 -- Guido

>  
> 
> thanks again for the work everyone has put in so far, and let's finish this..! ;-) 
> mark.
> 
> -----Original message-----
> > From:Mark Dufour <m.dufour at zarafa.com>
> > Sent: Sunday 31st May 2015 17:48
> > To: Jelle van der Waa <j.vanderwaa at zarafa.com>; pkg-giraffe-discuss at lists.alioth.debian.org
> > Subject: RE: [Pkg-giraffe-discuss] Missing manpages
> > 
> > hi all,
> > 
> > > > Compared to last Saturday lintian is already quiet happy now. We need to
> > > > rework the lib and python packaging anyway and once done most of this
> > > > should be covered.
> > 
> > great to hear, and thanks to all involved. sorry it took a while to get my feet back on the ground after my vacation. I hope to start contributing again from now on, and will post a general update shortly. 
> > 
> > about the following lintian errors:
> >  
> > > >  W: zarafa-dagent: binary-without-manpage usr/bin/zarafa-mr-accept    
> > 
> > this is not really a binary that a user would start manually. it can be configured in dagent.cfg to deal with meeting requests. would it be a problem to leave this as-is for now..?
> > 
> > > >  W: zarafa-server: manpage-has-errors-from-man usr/share/man/man5/zarafa-ldap.cfg.5.gz 964: warning [p 11, 5.5i]: can't break line    
> > > 
> > > Spotted the error here:
> > > Optional for OpenLDAP installations: \
> > > fI(|(mail=%s*)(uid=%s*)(cn=*%s*)(fullname=*%s*)(givenname=*%s*)(lastname=*%s*)(sn=*%s*))\fR
> > > 
> > > I'm not an expert on man pages, but adding a space in the LDAP query resolves it but makes the query harder to copy/paste. So I am not certain what the correct solution is.
> > 
> > adding an 'invisible space', &#x200B; into the respective line in doc/manual.xml seems to solve the problem. no more error, copy-pastability.
> > 
> > > >  W: zarafa-search-plus: binary-without-manpage usr/bin/zarafa-search
> > 
> > I updated the search and search cfg manpages for the new search just now and added them to our packages. thanks for spotting this problem!
> > 
> > > I've created a ticket for these three issues in our internal bugtracker, when we have patches for these issues I'll send them to the list.
> > 
> > I personally don't think we will be done with this very soon, so I suggest we just put as many fixes as possible into 7.2.1, which should be released in a few weeks, at least as a beta2..? (we can always provide a tarball earlier).
> > 
> > 
> > cheers,
> > mark.
> 
> _______________________________________________
> Pkg-giraffe-discuss mailing list
> Pkg-giraffe-discuss at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-giraffe-discuss