[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#966295: lintian: False positive with bogus email address



Hello Eriberto,

On Sat, Jul 25, 2020 at 9:45 PM Eriberto Mota <eriberto@debian.org> wrote:
>
> Dear Maintainer,
>
> lintian produces a false positive in mmorph package. I think the problem is a
> comma used by an old maintainer.
>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG <tb@becket.net>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG <tb@debian.org>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG <tb@debian.org>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG <tb@debian.org>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG <tb@debian.org>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG <tb@debian.org>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG <tb@debian.org>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG <tb@debian.org>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG <tb@debian.org>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG <tb@debian.org>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG <tb@debian.org>

I ran into the same problem with the lilypond package too, though
after adding double quotes around the display name of the email
address like so:

    "Thomas Bushnell, BSG" <tb@debian.org>

the Lintian errors went away.

This makes sense to me because the comma is used for separating
multiple email recipients, so Lintian is right in splitting it up at
the comma, i.e. trying to parse the string "Thomas Busnell" as an
email address, and "BSG <tb@debian.org>" as another.

That said, perhaps the Lintian info message could be a little more
explicit, as the current text:

   The changelog file contains an invalid email address: the domain needs
   at least one dot. This looks like a mistake.

does not say that a comma isn't allowed anywhere in the display name.

Just my two cents.  :-)

Cheers,
Anthony


Reply to: