[Debichem-devel] cclib

[Daniel Leidert]

Am Mittwoch, den 13.04.2011, 15:20 +0200 schrieb Karol M. Langner:

[..]
> After my last commits, lintian outputs just warnings:

If you run lintian with the -I switch, it will explain its output.

> W: python-cclib: wrong-section-according-to-package-name python-cclib => python

easy -> debian/control

> W: python-cclib: new-package-should-close-itp-bug
> W: cclib: new-package-should-close-itp-bug

Can both be ignored.

> W: cclib: binary-without-manpage usr/bin/ccget
> W: cclib: binary-without-manpage usr/bin/cda

If you provide the information about switches, environment variables,
etc. I can write the manual page in GROFF for you. Check e.g.
apbs/debian/apbs.1 or pymol/debian/pymol.1 (call `man -l ...file...') to
see, which information is usually provided by a manual page. Or check
this howto:
http://www.schweikhardt.net/man_page_howto.html

I also wrote a small howto for writing a manual page for Debian
packages: http://www.wgdd.de/?p=65

> W: cclib: package-contains-upstream-install-documentation usr/share/doc/cclib/INSTALL
> W: cclib: extra-license-file usr/share/doc/cclib/LICENSE.gz

Both can probably be fixed in debian/patches/fix_setup by removing them
from the install targets. Or remove them after the installation step,
which doesn't equire patching setup.py. Call

$(RM) debian/cclib/usr/share/doc/cclib/LICENSE ...

in debian/rules. Your choice.

Usually the upstream installation information is useless for the Debian
user, because he gets an ready-to-install package. So we check this file
for further important information (besides installation information) and
put this information into debian/README.Debian and don't install the
upstream file.

We also don't ship extra license files. The common license files can be
found in /usr/share/common-licenses/ and debian/copyright (installed
as /usr/share/doc/{package}/copyright) links to these common files. If
the license is not shipped in /usr/share/common-licenses/, then it must
be fully reproduced in debian/copyright.

> Do I need to act on any of these?

Usually you should act on all errors and warnings. The
new-package-should-close-itp-bug can be ignored. Usually one opens an
ITP (intend to package) bug report, which is then closed with the first
upload of the package. So this warning only appears for the initial
package upload. All others should be fixed. A few can cause the Debian
FTP masters to reject the package until they are fixed.

Regards, Daniel