[pkg-kolab] kdepim and kolab

Paul Boddie paul at boddie.org.uk
Mon Jun 23 17:45:20 UTC 2014

On Monday 23. June 2014 12.54.38 Sandro Knauß wrote:
> > 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?
> Well yes i see the same issue here - actually upstream doesn't create this
> file. But you can easily create one (it is just an empty file, so touch
> should be your friend :) And you can use pykolab by using the direct
> import kolab.foo. The debian package should  ship an __init__.py.

What is the correct Debian way of creating it? I could add touch to the rules 
file somewhere, but I am assuming that some debhelper magic should have set 
the package up instead. Also, pykolab isn't python-kolab, but it is in the 
pykolab.xml package that I see this kolab importing going on.

Maybe I'll review what the Ubuntu people did, if anything, and I'll also check 
to make sure that python-kolab is a known dependency of pykolab.


More information about the pkg-kolab-devel mailing list