On 2011-06-04 14:39, Eric Lavarde wrote: > Package: lintian > Version: 2.5.0 > Severity: normal > > > Hello, >
Hey, > my description will sound like a question (and is also one) but I think it > should be better explained in the documentation > file:///usr/share/doc/lintian/lintian.html/section-2.4.html > > The question is how to make the difference between a binary and a source > issue. For example, I get always the same result with the 3 following calls > (knowing that source and binary have the same package name): > You are not the first to run into this issue; we had a similar bug about this recently. To answer your immediate question; the tag in question is a binary-only (.deb) check only and should be overridden in the binary package freeplane. I do not know the exact reason for it (but I do have my guesses), but Lintian does not emit the type when it is a binary package. > $ lintian freeplane_1.1.3-1_i386.changes > W: freeplane: missing-classpath libcommons-lang-java, libjgoodies-forms-java, > libbatik-java, libxerces2-java, libxml-commons-external-java, > libjaxp1.3-java, libjlatexmath-java, libknopflerfish-osgi-framework-java, > libjortho-freeplane-java > $ lintian -b freeplane_1.1.3-1_i386.changes > W: freeplane: missing-classpath libcommons-lang-java, libjgoodies-forms-java, > libbatik-java, libxerces2-java, libxml-commons-external-java, > libjaxp1.3-java, libjlatexmath-java, libknopflerfish-osgi-framework-java, > libjortho-freeplane-java > $ lintian -s freeplane_1.1.3-1_i386.changes > W: freeplane: missing-classpath libcommons-lang-java, libjgoodies-forms-java, > libbatik-java, libxerces2-java, libxml-commons-external-java, > libjaxp1.3-java, libjlatexmath-java, libknopflerfish-osgi-framework-java, > libjortho-freeplane-java > > So, how do I know what I have for an issue type? and if the issue is > considered > to impact binary _and_ source, should I override both? > > OK, I ran lintian in debug mode, so I guess that it's a binary issue, but > I think my questions remain valid, AND why does then '-s' give a result? > I think the manpage might be outdated on this, but -s and -b only seems to be useful for interactions with a (static) lab or the with the special "packages" files. That being said - I believe a --verbose would be enough to give you something like: """ N: Processing binary package freeplane (version 1.1.1-1) ... """ > Final question: why not output binary|source information in the same format > as for the override file? That would make things a lot easier... > > Thanks, Eric > > [...] > Technically the override file does not require you to actually write the package name nor package type. A simple "<tag>" is enough; however, I personally would not mind if we always printed the type of the package. Even if there some (legacy?) reason why we cannot do that, I believe we can still output this information along with a tag description (outputted by lintian -i or lintian-info). I suspect most people will at least look up the tag description before deciding to override it (and as an added bonus, they will know which check to file a bug against). But in the end, none of the above is an excuse for not updating the manual. ~Niels
0001-Emit-check-name-and-type-with-lintian-i-or-lintian-i.patch
Description: application/wine-extension-patch
