tags 914135 + moreinfo thanks Hi Rebecca,
> > libnfs (2.0.0-1~exp1) experimental; urgency=medium [..] > > Is this something that may be notified by lintian?> > In theory, > https://lintian.debian.org/tags/distribution-and-changes-mismatch.html , > but since it didn't trigger on libnfs, it would appear to be broken. ^^^^^^^^^^^^^^^^^^^^^^^^^^^ I do note that there was a mismatch for this specific upload, ie: https://tracker.debian.org/news/946971/accepted-libnfs-200-1exp1-source-amd64-into-unstable-unstable/ … but what is the evidence for Lintian not seeing this? The maintainer could have uploaded anyway and/or they had an old version of Lintian, etc. If you are wondering why it does not appear on: https://lintian.debian.org/tags/distribution-and-changes-mismatch.html ... that is because that requires the .changes file to be around, whilst lintian.debian.org processes source packages (ie. that particular webpage is pretty useless). Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
