The trigger in your Debian packages

2011-06-03 Thread Raphael Hertzog
Hello, you're maintaining a Debian package which provides a trigger file. Currently a package that activates a trigger is put in the triggers-awaited status where it doesn't fulfill dependencies. The trigger must first be processed and only then is the package considered as installed. I believe

Bug#629056: false-postive: Java jars containing Maven plugins should not generate missing-classpath

2011-06-03 Thread James Page
Package: lintian Version: 2.5.0 Severity: normal JAR files containing maven plugins should not really generate a missing-classpath warning; plugins should only ever be used by the maven build system (which uses XML files for dependency management) and hence are not used at runtime which is the

Re: The trigger in your Debian packages

2011-06-03 Thread Colin Watson
On Fri, Jun 03, 2011 at 10:24:23AM +0200, Raphael Hertzog wrote: 1/ If your package uses the interest directive in the triggers files, is it important that the triggering packages that activate your triggers be considered as not configured (and thus not satisfying dependencies) until the

Bug#629161: lintian: Outdated groff version used on lintian.debian.org

2011-06-03 Thread Guillem Jover
Package: lintian Hi! It seems the groff package being used on lintian.debian.org is outdated and lintian reports errors from man-db due to unknown BSD version strings (such as FreeBSD or NetBSD). Can be easily seen in http://lintian.debian.org/tags/manpage-has-errors-from-man.html by searching