Bug#441636: lintian: Doesn't check command line arguments properly
Package: lintian Version: 1.23.28 Severity: minor Hi, I tried verifying a package using lintian *.dsc and was very happy that lintian did not report errors. Now I noticed that I have to call it with the .changes file! Why isn't my error not detected? Jens -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages lintian depends on: ii binutils 2.17cvs20070426-5 The GNU assembler, linker and bina ii diffstat 1.43-2produces graph of changes introduc ii dpkg-dev 1.13.25 package building tools for Debian ii file 4.17-5etch2 Determines file type using magic ii gettext0.16.1-1 GNU Internationalization utilities ii intltool-debian0.35.0+20060710.1 Help i18n of RFC822 compliant conf ii libparse-debianchangel 1.0-1 parse Debian changelogs and output ii man-db 2.4.3-6 The on-line manual pager ii perl [libdigest-md5-pe 5.8.8-7 Larry Wall's Practical Extraction lintian recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441636: lintian: Doesn't check command line arguments properly
Jens Seidel [EMAIL PROTECTED] writes: Package: lintian Version: 1.23.28 Severity: minor I tried verifying a package using lintian *.dsc and was very happy that lintian did not report errors. Now I noticed that I have to call it with the .changes file! Why isn't my error not detected? Because lintian supports checking different things. If you run it on a *.dsc file, it checks the source package. If you run it on a *.deb file, it checks a binary package. If you run it on *.changes, it checks everything listed in that *.changes file. All of those ways of running lintian are valid. Running it directly on source and .deb files is used when checking the whole archive. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441636: lintian: Doesn't check command line arguments properly
On Mon, Sep 10, 2007 at 12:29:45PM -0700, Russ Allbery wrote: Jens Seidel [EMAIL PROTECTED] writes: Package: lintian Version: 1.23.28 Severity: minor I tried verifying a package using lintian *.dsc and was very happy that lintian did not report errors. Now I noticed that I have to call it with the .changes file! Why isn't my error not detected? Because lintian supports checking different things. If you run it on a *.dsc file, it checks the source package. If you run it on a *.deb file, it checks a binary package. If you run it on *.changes, it checks everything listed in that *.changes file. All of those ways of running lintian are valid. Running it directly on source and .deb files is used when checking the whole archive. Mmh, is the manpage still up-to-date? There are three ways to specify binary, udeb or source packages for Lintian to process: by file name, by package name, or by naming a .changes file. *.dsc is not a package name and not a .changes file. So it has to be a file name? But does .dsc differ from .changes, both are similar files (no package names, ...)? If .dsc is an file name this is true for .changes as well. Please rephrase it. OK, feel free to close the bug. I just used lintian wrong and missed a lot of errors ... Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441636: lintian: Doesn't check command line arguments properly
Jens Seidel [EMAIL PROTECTED] writes: Mmh, is the manpage still up-to-date? So far as I know. There are three ways to specify binary, udeb or source packages for Lintian to process: by file name, by package name, or by naming a .changes file. *.dsc is not a package name and not a .changes file. So it has to be a file name? Right. But does .dsc differ from .changes, both are similar files (no package names, ...)? No, the *.dsc file represents a source package. A *.changes file can represent a wide variety of things (usually, but not necessarily, a source file and some accompanying binaries). If .dsc is an file name this is true for .changes as well. Please rephrase it. Okay, I'll take another stab at it. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
