Bug#576083: lintian: debhelper-overrides-need-versioned-build-depends (= 7.0.50~)

2010-03-31 Thread Jari Aalto
Package: lintian Version: 2.3.4 Severity: minor When using in debian/rules: override_CH_COMMAND: Lintian displays warnings: debhelper-overrides-need-versioned-build-depends (= 7.0.50~) if debian/control reads: Build-Depends: debhelper (= 7) SUGGESITON The warning

Bug#576083: lintian: debhelper-overrides-need-versioned-build-depends (= 7.0.50~)

2010-03-31 Thread Russ Allbery
Jari Aalto jari.aa...@cante.net writes: When using in debian/rules: override_CH_COMMAND: Lintian displays warnings: debhelper-overrides-need-versioned-build-depends (= 7.0.50~) if debian/control reads: Build-Depends: debhelper (= 7) SUGGESITON The warning is

Bug#576083: lintian: debhelper-overrides-need-versioned-build-depends (= 7.0.50~)

2010-03-31 Thread Russ Allbery
Jari Aalto jari.aa...@cante.net writes: Russ Allbery r...@debian.org writes: That doesn't make any sense to me. Why would we replace a tag which is accurate with one that isn't? Why is an incorrect dependency on = 7.1 more descriptive to the reader than a correct dependency on = 7.0.50~?

Bug#576083: lintian: debhelper-overrides-need-versioned-build-depends (= 7.0.50~)

2010-03-31 Thread Jari Aalto
Russ Allbery r...@debian.org writes: The debhelper is already in version of 7.4.15 in Debian/testing, so perhaps the message could be relaxed to a nearest round number: debhelper-overrides-need-versioned-build-depends (= 7.1) That doesn't make any sense to me. Why would we replace a

Bug#576083: lintian: debhelper-overrides-need-versioned-build-depends (= 7.0.50~)

2010-03-31 Thread Jari Aalto
Russ Allbery r...@debian.org writes: debhelper (7.0.50) unstable; urgency=low * This release is designed to be easily backportable to stable, to support the new style of rules file that I expect many packages will use. backports.org I think now has an even newer version, but