# Bcc: control retitle 183642 please check for malformed email address in .changes file reassign 183642 lintian thanks
Hi Robert, On 03/03/13 00:35 +0100, Robert Millan said ... > On Wed, Mar 12, 2003 at 10:23:12PM +0100, Christian Kurz wrote: > > Hm, lintian doesn't catch such problems? Did you try linda so far and > > talked with Steven about it? I think it might be worth to include a > > check for broken e-Mail addresses in linda/lintian and then have them > > report an error. lintian has sanity checks for the format of email addresses in the control fields and in the changelog file. lintian also checks the .changes file as the first thing. > > [...] > > I'm not sure if it's really worth to add such a check. So let me first > > thank you Thomas for writing the code. But I think we should consider if > > it's worth to include it in dput or not. At least dput shouldn't be > > another tool like lintian. ;-) > > I understand your point. but i think lintian/linda are meant for a different > situation than what i had. I was manualy building a package of another > maintainer for binary-only upload. If i run lintian/linda on that package, > it will come up with bugs the package has, but i'm not particularly interested > on them as i'm not the maintainer (if the maintainer uploaded the sources, > i should assume they're sane enough) > > So i think that while lintian is meant to be useful to maintainers by > verifying the package sanity, dput should take care of checking upload-related > stuff like the changes file. lintian has sets of checks (see the -C/-X options and the CHECKS section in lintian(1)) and one can avoid doing a whole bunch of checks or only check for a few things. I would say that it is a lintian wishlist to implement a 'CHECK' for binary only uploads. Cheers, Giridhar -- Y Giridhar Appaji Nag | http://appaji.net/
signature.asc
Description: Digital signature
