Package: lintian Version: 2.0.0 Severity: normal For some strange reason, the latest version of libmodule-build-perl doesn't work for zim and thus I added a Build-Conflict to force the usage of version of the module that is provided by perl-modules:
Build-Depends: debhelper (>= 5.0), perl-modules (>= 5.10.0) | libmodule-build-perl (>= 0.2800) Build-Conflicts: libmodule-build-perl (>= 0.3000) But this combination leads to lintian improperly complaining: E: zim source: missing-build-dependency libmodule-build-perl Not sure if the Build-Conflicts is at fault or if the change advised by the lintian warning is the sole responsible: W: zim source: versioned-dependency-satisfied-by-perl build-depends: libmodule-build-perl (>= 0.28) -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lintian depends on: ii binutils 2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii diffstat 1.46-1 produces graph of changes introduc ii dpkg-dev 1.15.0 Debian package development tools ii file 4.26-1 Determines file type using "magic" ii gettext 0.17-4 GNU Internationalization utilities ii intltool-debian 0.35.0+20060710.1 Help i18n of RFC822 compliant conf ii libparse-debianchan 1.1.1-2 parse Debian changelogs and output ii libtimedate-perl 1.1600-9 Time and date functions for Perl ii liburi-perl 1.35.dfsg.1-1 Manipulates and accesses URI strin ii man-db 2.5.2-3 on-line manual pager ii perl [libdigest-sha 5.10.0-17 Larry Wall's Practical Extraction lintian recommends no packages. Versions of packages lintian suggests: pn binutils-multiarch <none> (no description available) ii libtext-template-perl 1.44-1.2 Text::Template perl module ii man-db 2.5.2-3 on-line manual pager -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
