[pkg-kolab] kdepim and kolab

[Paul Boddie]

On Saturday 31. May 2014 01.33.51 Sandro Knauß wrote:
> Hey,
> 
> I tried to compile libkolabxml and libkolab from master git without
> modification and can just say: "It works out of the box".
> 
> > I then built libkolab again with the updated libkolabxml package
> > available in the local dependencies for pbuilder, and with the small
> > build dependency adjustments I mentioned earlier (libboost-system-dev,
> > libboost-thread-dev, libossp-uuid-dev, libxerces-c-dev), and this build
> > also went without incident.
> 
> I didn't have to adjust the build deps (i used sbuild to built). Maybe you
> didn't update pbuilder before?

I think it may have something to do with me building in a wheezy chroot and 
not a sid one.

> @Paul Klos: are there any outstanding issues, why the new versions aren't
> publish? For me it looks like you did all necessary  work. Looking at the
> package, the only thing I see is a bump of the standards version. Or do you
> "only" need an uploader?

One strange thing I encountered with the updated libkolab source packaging is 
the lack of an __init__.py file in the kolab Python package provided by the 
python-kolab Debian package. This means that it isn't possible to import from 
kolab in a Python program, affecting pykolab. Do you see that problem as well?

The python-kolab.install file within libkolab looks like this:

usr/lib*/python*/*-packages/kolab/_shared.so
usr/lib*/python*/*-packages/kolab/shared.py
usr/lib*/python*/*-packages/kolab/_calendaring.so
usr/lib*/python*/*-packages/kolab/calendaring.py
usr/lib*/python*/*-packages/kolab/_icalendar.so
usr/lib*/python*/*-packages/kolab/icalendar.py
usr/lib*/python*/*-packages/kolab/_kolabobject.so
usr/lib*/python*/*-packages/kolab/kolabobject.py

Adding an entry for the __init__.py file fails because there isn't one already 
present or subsequently generated. What am I missing here?

Paul