Re: Package uploaded with UNRELEASED distribution.
On Thu, Aug 20, 2009 at 04:54:29PM -0700, Russ Allbery wrote:
> Michal Čihař <firstname.lastname@example.org> writes:
> > Russ Allbery <email@example.com> napsal(a):
> >> We had a specific request for Lintian to not warn about UNRELEASED as
> >> the distribution so that people could run it on each build and know
> >> that any output meant a problem. Unfortunately, that creates the
> >> possibility for something like this to happen, since dput and dupload
> >> only look at the *.changes file and don't care about what's in the
> >> changelog, and Lintian's architecture makes it very hard for it to see
> >> a mismatch between the *.changes file and the package.
> > Well for this case it would be enough to catch mismatch in changes which
> > did contain untable as distribution, but UNRELEASED in the changes
> > entry. Not sure how useful such check would be though.
> The difficulty is that Lintian checks binary packages, source packages,
> and changes files in isolation from each other, so there's no way in
> Lintian in its current architecture to recognize mismatches between two
> different types of package or between the *.changes file and one of the
> packages. No part of Lintian has the data from both at the same time.
He meant that in this particular case, the UNRELEASED and unstabler
discrepancy *is* in the .changes file. See