Package: lintian Version: 1.23.8 Severity: important (is important appropriate for error messages about non-errors?)
E: tetex-bin: bad-version-in-relation conflicts: aleph (<< 1:0) N: N: The version number used in this relationship does not match the N: defined format of a version number. N: N: Refer to Policy Manual, section 5.6.12 for details. N: I see nothing in the policy manual that would forbid an upstream version number of 0 together with an epoch. It doesn't make much sense for a real upstream version number, but why does lintian care? In fact 0 isn't an upstream version number, rather the "aleph" project has been renamed, and the package for the new software will produce a transitional package for aleph, with epoch 1: and an unknown upstream version number, the maintainer told me. Since the transitional package doesn't contain any files, I need no longer conflict with it. Regards, Frank -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages lintian depends on: ii binutils 2.15-6 The GNU assembler, linker and bina ii diffstat 1.39-1 produces graph of changes introduc ii file 4.12-1 Determines file type using "magic" ii gettext 0.14.4-2 GNU Internationalization utilities ii intltool-debian 0.30+20040213 Help i18n of RFC822 compliant conf ii man-db 2.4.2-21 The on-line manual pager ii perl [libdigest-md5-perl] 5.8.4-8 Larry Wall's Practical Extraction -- no debconf information -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer