Russ Allbery wrote: > Raphael Geissert <atomo64+deb...@gmail.com> writes: >> Lucas Nussbaum wrote: > >>> Then how about sending a mail if one of the packages has (serious, >>> certain) lintian errors? > >> Lintian currently still uses the EWI code when generating the report >> which later udd imports. This file lacks the severity and certainty >> information, which means it would be necessary to keep a local copy of >> lintian in sync with lintian.d.o's version so that they both match. >> Not impossible, but doesn't feel right. > > We can make available a better file, too. I've thought about that off > and on, but never had time to figure out just what should be in the file.
Maybe an XML report should be generated; that way it could be easier to implement #512901 > >> I think I agree with zack; issues should be reported or the certainty >> and severity tweaked. > > I think there's quite a bit that's wrong about the certainty right now. > The severity I'm more confident about, but there are a bunch of > certainty: certain tags with a bunch of overrides, which is clearly > wrong. > Of course something is wrong, but that might either be the package or lintian, or both :) But despite all that my original question hasn't quite been answered. Gregor is in favour of sending messages even if only lintian issues exist, but Lucas doesn't like the idea. What about something in between? only errors if another issue exists for the same given package? or only errors if there's an issue for any of the co-/maintained packages? Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
