Bug#964381: marked as done (lintian: Detecting bogus email address)
Your message dated Wed, 8 Jul 2020 21:29:11 +1000
with message-id <CAN9Bcdv0RTrdgfBR1kkCYJf+w1kQZZ+3qpibUUkjVVns=vr=DQ@mail.gmail.com>
and subject line Re: Bug#964381: lintian: Detecting bogus email address
has caused the Debian Bug report #964381,
regarding lintian: Detecting bogus email address
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
964381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964381
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.82.0
Severity: normal
Dear Maintainer,
Since commit 6dda6b02dc83b454a576717c888307df1f2ebbb6, lintian has detected two
identical entries in yaz's debian/changelog as bogus.
The entries are adam@flurry.index.
I'm not sure how to address this.
Should I ignore lintian, override the tag or change the problem email addresses
to the upstream author's actual email address (also found all over the
changelog)?
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages lintian depends on:
ii binutils 2.34-8
ii bzip2 1.0.8-3
ii diffstat 1.63-1
ii dpkg 1.20.3
ii dpkg-dev 1.20.3
ii file 1:5.38-5
ii gettext 0.19.8.1-10
ii gpg 2.2.20-1
ii intltool-debian 0.35.0+20060710.5
ii libapt-pkg-perl 0.1.36+b3
ii libarchive-zip-perl 1.68-1
ii libcapture-tiny-perl 0.48-1
ii libclass-xsaccessor-perl 1.19-3+b5
ii libclone-perl 0.45-1
ii libconfig-tiny-perl 2.24-1
ii libcpanel-json-xs-perl 4.19-1
ii libdata-validate-domain-perl 0.10-1
ii libdevel-size-perl 0.83-1+b1
ii libdpkg-perl 1.20.3
ii libemail-address-xs-perl 1.04-1+b2
ii libfile-basedir-perl 0.08-1
ii libfile-find-rule-perl 0.34-1
ii libfont-ttf-perl 1.06-1
ii libhtml-parser-perl 3.72-5
ii libio-async-loop-epoll-perl 0.21-1
ii libio-async-perl 0.77-3
ii libjson-maybexs-perl 1.004002-1
ii liblist-compare-perl 0.53-1
ii liblist-moreutils-perl 0.416-1+b5
ii liblist-utilsby-perl 0.11-1
ii libmoo-perl 2.004000-1
ii libmoox-aliases-perl 0.001006-1
ii libnamespace-clean-perl 0.27-1
ii libpath-tiny-perl 0.114-1
ii libsereal-decoder-perl 4.014+ds-1
ii libsereal-encoder-perl 4.014+ds-1
ii libtext-levenshtein-perl 0.13-1
ii libtimedate-perl 2.3300-1
ii libtry-tiny-perl 0.30-1
ii libtype-tiny-perl 1.010002-1
ii libunicode-utf8-perl 0.62-1+b1
ii liburi-perl 1.76-2
ii libxml-libxml-perl 2.0134+dfsg-2
ii libxml-writer-perl 0.625-1
ii libyaml-libyaml-perl 0.82+repack-1
ii man-db 2.9.3-2
ii patchutils 0.3.4-3
ii perl [libdigest-sha-perl] 5.30.3-4
ii t1utils 1.41-4
ii xz-utils 5.2.4-1+b1
Versions of packages lintian recommends:
ii libperlio-gzip-perl 0.19-1+b6
Versions of packages lintian suggests:
pn binutils-multiarch <none>
pn libtext-template-perl <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, 8 Jul 2020 at 01:52, Felix Lechner wrote:
> Adam confirmed via private email that changing the address is okay. An
> internal address appeared by mistake.
Thanks for following this up, Felix. I've pushed the relevant commit
to the yaz repo on salsa.
> Alternatively, you could wait until a new version of
> Data::Validate::Domain is uploaded. At that point, the TLD validation
> will probably be turned off (although it worked well in your case).
> The use of that feature is worth a discussion somewhere.
Indeed. It did catch this issue, so it definitely seems useful.
> Please feel free to close this bug report.
Will do. Thanks again.
--- End Message ---
Reply to: