Comment 1 for bug 352986

$ lintian -iIv checkbox_0.7.1_source.changes
N: Setting up lab in /tmp/Zbxx8A0z7u ...
N: Processing changes file checkbox_0.7.1_source.changes ...
N: Processing 1 packages...
N: ----
N: Processing source package checkbox (version 0.7.1) ...
W: checkbox source: debian-watch-file-in-native-package
N:
N: The package ships a watch file although it is a Debian native package.
N: DEHS does not process watch files in native packages based on the
N: reasoning that native packages do not have upstreams to check for new
N: releases.
N:
N: Refer to http://wiki.debian.org/DEHS for details.
N:
N: Severity: normal, Certainty: certain
N:
W: checkbox source: debhelper-but-no-misc-depends hwtest-gtk
N:
N: The source package uses debhelper but it does not use ${misc:Depends} in
N: the given binary package's debian/control entry. This is required so the
N: dependencies are set correctly in case the result of a call to any of
N: the dh_ commands cause the package to depend on another package.
N:
N: Refer to the debhelper(7) manual page for details.
N:
N: Severity: normal, Certainty: certain
N:
W: checkbox source: debhelper-but-no-misc-depends hwtest
W: checkbox source: debhelper-but-no-misc-depends hwtest-cli
W: checkbox source: debhelper-but-no-misc-depends checkbox-gtk
W: checkbox source: debhelper-but-no-misc-depends checkbox-cli
W: checkbox source: debhelper-script-needs-versioned-build-depends dh_icons (>= 5.0.51~)
N:
N: The given debhelper script was introduced in a later version of
N: debhelper than the package Build-Depends on. The package Build-Depends
N: should be updated to require that version of debhelper. Giving the
N: version followed by ~ is recommended so that backports will satisfy the
N: dependency.
N:
N: etch was released with debhelper version 5.0.42, so every package that
N: assumes a newer version should explicitly declare so for the sake of
N: etch backports.
N:
N: Severity: normal, Certainty: certain
N:
I: checkbox source: no-complete-debconf-translation
N:
N: Even though this package provides debconf translation support, there are
N: no translations or none of the translations are complete. This may mean
N: that translators weren't properly warned about new strings.
N:
N: Translators may be notified of changes using podebconf-report-po, for
N: example:
N:
N: podebconf-report-po --call --withtranslators --deadline="+10 days" \
N: --languageteam
N:
N: Refer to Debian Developer's Reference section 6.5.2.2 (Be kind to
N: translators) for details.
N:
N: Severity: wishlist, Certainty: possible
N:
W: checkbox source: out-of-date-standards-version 3.7.3 (current is 3.8.0)
N:
N: The source package refers to a Standards-Version older than the one that
N: was current at the time the package was created (according to the
N: timestamp of the latest debian/changelog entry). Please consider
N: updating the package to current Policy and setting this control field
N: appropriately.
N:
N: If the package is already compliant with the current standards, you
N: don't have to re-upload the package just to adjust the Standards-Version
N: control field. However, please remember to update this field next time
N: you upload the package.
N:
N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the
N: debian-policy package for a summary of changes in newer verisons of
N: Policy.
N:
N: Severity: normal, Certainty: certain
N:
W: checkbox source: stronger-dependency-implies-weaker checkbox depends -> recommends hal
N:
N: In the debian/control stanza for the given package, a stronger
N: dependency field implies one of the dependencies in a weaker dependency
N: field. In other words, the Depends field of the package requires that
N: one of the packages listed in Recommends or Suggests be installed, or a
N: package is listed in Recommends as well as Suggests.
N:
N: Current versions of dpkg-gencontrol will silently fix this problem by
N: removing the weaker dependency, but it may indicate a more subtle bug
N: (misspelling or forgetting to remove the stronger dependency when it was
N: moved to the weaker field).
N:
N: Refer to Debian Policy Manual section 7.2 (Binary Dependencies -
N: Depends, Recommends, Suggests, Enhances, Pre-Depends) for details.
N:
N: Severity: normal, Certainty: certain
N:
I: checkbox source: build-depends-without-arch-dep python-distutils-extra
N:
N: The control file lists the given package in Build-Depends, but no
N: architecture-dependent packages are built. If all the packages built are
N: architecture-independent, the only packages that should be listed in
N: Build-Depends are those required to run the clean target (such as
N: debhelper if you use dh_clean). Other build dependencies should be
N: listed in Build-Depends-Indep instead.
N:
N: Refer to Debian Policy Manual section 7.7 (Relationships between source
N: and binary packages - Build-Depends, Build-Depends-Indep,
N: Build-Conflicts, Build-Conflicts-Indep) for details.
N:
N: Severity: minor, Certainty: possible
N:
W: checkbox source: unknown-field-in-dsc original-maintainer
N:
N: See the Policy Manual for a list of the possible fields in a source
N: package control file.
N:
N: Refer to Debian Policy Manual section 5.4 (Debian source control files
N: -- .dsc) for details.
N:
N: Severity: minor, Certainty: certain
N:
W: checkbox source: diff-contains-bzr-control-dir .bzr
N:
N: The Debian diff or native package contains files in a .bzr directory.
N: These are usually artifacts of the revision control system used by the
N: Debian maintainer and not useful in a diff or native package. Passing -i
N: to dpkg-buildpackage or the equivalent will automatically exclude them.
N:
N: Severity: normal, Certainty: certain
N:
N: Removing /tmp/Zbxx8A0z7u ...