Hi, I've uploaded the jscoverage package you did to debian. There still are a few warnings and here are the comments that suggest how you can fix them. Did you inform the jscoverage authors about your work ?
Cheers Uploading (ftp) to ftp-master.debian.org:/pub/UploadQueue [ job jscoverage_0.3.1-1_i386 from jscoverage_0.3.1-1_i386.changes jscoverage_0.3.1.orig.tar.gz, md5sum ok jscoverage_0.3.1-1.dsc, md5sum ok jscoverage_0.3.1-1_i386.deb, md5sum ok jscoverage_0.3.1-1.diff.gz, md5sum ok jscoverage_0.3.1-1_i386.changes ok ] N: Setting up lab in /tmp/eSxk7HCSFj ... N: Processing 1 packages... N: ---- N: Processing binary package jscoverage (version 0.3.1-1) ... W: jscoverage: manpage-has-bad-whatis-entry usr/share/man/man1/js-config.1.gz N: N: Each manual page should start with a `NAME' section, which lists the N: name and a brief description of the page seperated by '\-'. These N: sections are parsed by `mandb' and stored in a database for the use of N: `apropos' and `whatis', so they must be in a certain format. This N: manual page apparently uses the wrong format and cannot be parsed by N: `mandb'. N: N: For information on how `NAME' sections should be written see N: lexgrog(1). See also groff_man(7) and groff_mdoc(7) for general N: information on writing manual pages. N: W: jscoverage: manpage-has-bad-whatis-entry usr/share/man/man1/js.1.gz W: jscoverage: manpage-has-bad-whatis-entry usr/share/man/man3/js.3.gz W: jscoverage: non-dev-pkg-with-shlib-symlink usr/lib/libjs.so.1.0.6 usr/lib/libjs.so N: N: Although this package is not a `-dev' package, it installs a N: `libsomething.so' symbolic link referencing the corresponding shared N: library. When the link doesn't include the version number, it is used N: by the linker when other programs are built against this shared N: library. N: N: Shared libraries are supposed to place such symbolic links in their N: respective `-dev' packages, so it is a bug to include it with the main N: library package. N: N: However, if this is a small package which includes the runtime and the N: development libraries, this is not a bug. In the latter case, please N: override this warning. N: N: Refer to Policy Manual, section 8.4 for details. N: W: jscoverage: package-name-doesnt-match-sonames libjs1 N: N: The package name of a library package should usually reflect the N: soname of the included library. The package name can determined from N: the library file name with the following code snippet: N: N: $ objdump -p /path/to/libfoo-bar.so.1.2.3 | sed -n -e's/^[[:space:]]*SONAME[[:space:]]*//p' | sed -e's/\([0-9]\)\.so\./\1-/; s/\.so\.//' N: N: Refer to Library Packaging guide 5 for details. N: _______________________________________________ Pokersource-users mailing list [email protected] https://mail.gna.org/listinfo/pokersource-users
