[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#662026: RFS: shotdetect/1.0.86-1 [ITP]



Hi Giulio,

On Sun, 3 Jun 2012, Giulio Paci wrote:
You are right, that link still points to the upload you reviewed the
first time: new uploads did not overwrote those file, due to the section
change.

oh, no, this has been my first time looking at that package.


The right url is:
http://mentors.debian.net/debian/pool/main/s/shotdetect/shotdetect_1.0.86-1.dsc

Is there a reason to use debhelper 7? The pedantic info from lintian goes away with something like: debhelper (>=9), (of course you need to change debian/compat as well). If you use 'dh' in the rules file, dh9 should automatically take care of the hardening-stuff (this is a release goal for wheezy). I am sure that there is also a way for cdbs.

So if you don't have a sponsor yet and let those complaints from lintian disappear, I will upload the package.

  Thorsten


P: shotdetect source: package-lacks-versioned-build-depends-on-debhelper 7
N:
N:    The package either doesn't declare a versioned build dependency on
N:    debhelper or does not declare a versioned build dependency on a new
N:    enough version of debhelper to satisfy the declared compatibility level.
N:
N:    Recommended practice is to always declare an explicit versioned
N:    dependency on debhelper equal to or greater than the compatibility level
N:    used by the package, even if the versioned dependency isn't strictly
N:    necessary. Having a versioned dependency also helps with backports to
N:    older releases and correct builds on partially updated systems.
N:
N:    Refer to the debhelper(7) manual page for details.
N:
N:    Severity: pedantic, Certainty: certain
N:
N:    Check: debhelper, Type: source
N:
W: shotdetect: hardening-no-fortify-functions usr/bin/shotdetect
N:
N:    This package provides an ELF binary that lacks the use of fortified libc
N:    functions. Either there are no potentially unfortified functions called
N:    by any routines, all unfortified calls have already been fully validated
N:    at compile-time, or the package was not built with the default Debian
N:    compiler flags defined by dpkg-buildflags. If built using
N:    dpkg-buildflags directly, be sure to import CPPFLAGS.
N:
N:    NB: Due to false-positives, Lintian ignores some unprotected functions
N:    (e.g. memcpy).
N:
N:    Refer to http://wiki.debian.org/Hardening and
N:    http://bugs.debian.org/673112 for details.
N:
N:    Severity: normal, Certainty: possible
N:
N:    Check: binaries, Type: binary, udeb
N:





Reply to: