On Thu, 20 Aug 2009 at 23:07:38 -0700, Russ Allbery wrote:
> While we can't easily check for mismatches between the *.changes file
> and the debian/changelog file in the source package, the latter is
> copied into *.changes as the Changes field. We can therefore check
> whether the distribution in
On Thu, 27 May 2010 at 13:22:31 +0100, Simon McVittie wrote:
> Having managed to upload an experimental package to unstable *again*, I've
> written a Lintian check for this.
... which I then failed to attach.
From e6d3e117882c97af2dd5748c95d78eec98e574bd Mon Sep 17 00:00:00 2001
From: Simon McVitt
On Sun, 06 Dec 2009 at 05:04:49 +0100, Cyril Brulebois wrote:
> Russ Allbery (20/08/2009):
> > I think we only want to do this check if the first line of the
> > Changes file says UNRELEASED, since there are valid use cases for a
> > mismatch otherwise.
>
> Personally, I would have *really* ***lo
Russ Allbery (20/08/2009):
> I think we only want to do this check if the first line of the
> Changes file says UNRELEASED, since there are valid use cases for a
> mismatch otherwise.
Personally, I would have *really* ***loved*** to have such a check in
place. #559659 led me to upload a few dozen
Package: lintian
Version: 2.2.14
Severity: wishlist
While we can't easily check for mismatches between the *.changes file
and the debian/changelog file in the source package, the latter is
copied into *.changes as the Changes field. We can therefore check
whether the distribution in the first lin
5 matches
Mail list logo
