Michal Čihař <ni...@debian.org> writes: > Russ Allbery <r...@debian.org> 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. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
