Package: duck
Version: 0.7
Severity: normal

Dear Simon,

I'm currently running (once again) duck over all packages maintained by
the Debian Perl Team.

One thing I noticed is that it tends to regard message-ids as e-mail
addresses. Example from libaudio-cd-perl as currently in Git:

[…]erl/libaudio-cd-perl # duck
E: debian/copyright:30: Email: 
[email protected]: ERROR 
(Certainty:possible)
   [email protected]: No MX entry 
found.
   [email protected]: No A entry found.
   [email protected]: No AAAA entry 
found.

The offending lines is:

" Message-ID: <[email protected]>"

I think at least if a maybe-email-address is prepended by "Message-ID:"
in some way, it can be ignored.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (111, 'buildd-unstable'), 
(111, 'buildd-experimental'), (110, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages duck depends on:
ii  libconfig-inifiles-perl              2.83-3
ii  libfile-which-perl                   1.18-1
ii  libmailtools-perl                    2.13-1
ii  libnet-dns-perl                      0.81-2
ii  libparse-debcontrol-perl             2.005-4
ii  libpath-class-perl                   0.35-1
ii  libregexp-common-email-address-perl  1.01-4
ii  libregexp-common-perl                2013031301-1
ii  libstring-similarity-perl            1.04-1+b2
ii  libwww-curl-perl                     4.17-1+b1
ii  libxml-xpath-perl                    1.13-7
ii  libyaml-libyaml-perl                 0.41-6
ii  perl                                 5.20.2-6

duck recommends no packages.

Versions of packages duck suggests:
ii  bzr         2.6.0+bzr6602-2
ii  git         1:2.1.4-2.1
ii  mercurial   3.1.2-2
ii  subversion  1.8.13-1

-- no debconf information


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to