Packaging pykolab for Debian

"Jeroen van Meeuwen (Kolab Systems)" <[email protected]>
Newsgroups gmane.comp.kde.devel.kolab,gmane.comp.kde.kolab.devel
Message-ID <[email protected]>
Hi there,

I would appreciate the help of some Debian packaging experts about the 
following messages I'm getting from lintian, while attempting to package 
pykolab (comments inline);

Now running lintian...
W: pykolab source: changelog-should-mention-nmu
W: pykolab source: source-nmu-has-incorrect-version-number 0.4.3-1

^ These I couldn't care less about.

E: pykolab: extended-description-is-empty

^ This one I think I can fix.

E: pykolab: copyright-file-contains-full-gpl-license
E: pykolab: copyright-should-refer-to-common-license-file-for-gpl

^ I have no clue what this means I should do.

W: pykolab: new-package-should-close-itp-bug

^ This usually is the case...

W: pykolab: binary-without-manpage usr/sbin/kolab
W: pykolab: binary-without-manpage usr/sbin/kolab-conf
W: pykolab: binary-without-manpage usr/sbin/kolab-saslauthd
W: pykolab: binary-without-manpage usr/bin/kolab-test
W: pykolab: binary-without-manpage usr/sbin/kolab_parse_telemetry
W: pykolab: binary-without-manpage usr/sbin/kolabd
W: pykolab: binary-without-manpage usr/sbin/setup-kolab
W: pykolab: binary-without-manpage usr/sbin/wallaced

^ This indeed is a problem, but an upstream problem. I need no help 
with this now.

E: pykolab: dir-or-file-in-var-run var/run/kolab-saslauthd/
E: pykolab: dir-or-file-in-var-run var/run/kolabd/
E: pykolab: dir-or-file-in-var-run var/run/saslauthd/
E: pykolab: dir-or-file-in-var-run var/run/wallaced/

^ These I don't understand. I need directories writeable for non-root 
for writing out the PID file(s). Do I just insert a lintian override 
somewhere?

Finished running lintian.

*pfew*

Kind regards,

Jeroen van Meeuwen

-- 
Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.