Jenkins build is back to normal : lintian-tests_jessie #1086

See

[lintian] branch master updated (4d2ef25 -> f23f5e6)

This is an automated email from the git hooks/post-receive script. pabs pushed a change to branch master in repository lintian. from 4d2ef25 Consistently use the same "Debian style" RFC 822 date format for both "Mirror timestamp" and "Last updated" on the index page. (Closes: #828720)

[lintian] 01/01: spelling: Add several corrections

This is an automated email from the git hooks/post-receive script. pabs pushed a commit to branch master in repository lintian. commit f23f5e6a9f85d25396aa807b1df30ce67d577f0c Author: Paul Wise Date: Fri Jul 14 08:58:11 2017 +1000 spelling: Add several corrections ---

Bug#825348: lintian: check for packages containing upstart configuration in /etc/init/

On Thu, 2017-07-13 at 09:23 +0100, Chris Lamb wrote: > Sorry, I should have written a much better question; what actually > *are* the markers of a package shipping upstart configuration? As I understand it, shipping files in the /etc/init/ directory. > Is it simply the package checking

Bug#823190: lintian: Please error out on orig tarball sigs for source 1.0

Hi Guillem, > […] Thanks for the explanation :) > The report would still make sense for anything targetting a stable > release though, so it perhaps still has some merit? I'll leave the question of closing it up to you but I'll at least bump this bug down my own "priority" list. Thanks again.

Bug#825348: lintian: check for packages containing upstart configuration in /etc/init/

Hi Paul, > > Are you referring to anything beyond, say: > > > >   > > http://sources.debian.net/src/binfmt-support/2.1.7-1/debian/init/?hl=51#L31 > > In my initial report I was only thinking of files in /etc/init/ Sorry, I should have written a much better question; what actually *are* the